JP6287561B2 - Base station equipment - Google Patents

Description

  The present invention relates to a base station apparatus having a plurality of function cards.

  Some base station apparatuses are configured by providing a common card commonly used in the apparatus and a plurality of functional unit cards for performing control of the base station apparatus, wireless transmission / reception processing, and the like. The common card and the plurality of functional unit cards are processing units of a computer including a processor, a memory, and the like, and exchange data with each other via an inter-card interface.

  Conventionally, activation data such as activation of a base station device (BOOT) and firmware includes nonvolatile memory (for example, FLASH memory) on each functional unit card and large-scale nonvolatile memory (for example, SSD: Solid State Drive) on a common card. ) Stored in both. The large-scale non-volatile memory of the common card holds the activation data of each functional unit card as a master file, and this master file is updated as appropriate. The activation data includes data related to hardware functions such as FPGAs possessed by each card, and each card reads and activates the activation data in the non-volatile memory on its own card.

  In the above configuration, when the master file of the common card has been updated, the common card is requested to distribute the latest data, the startup data in its own nonvolatile memory is updated, and the latest data is restarted. Here, 1. When the entire base station device (common card and each functional unit card) is activated / reset at the same time, the common card is activated first, and the common card becomes the master of the entire base station device and sends the activation data to each functional unit. Distribute to the card and activate each functional unit card.

  In addition, the base station apparatus may perform addition of a functional unit card by resetting (restarting) a specific functional unit card, adding a function, or the like. In some cases, the functional unit cards are activated individually. Even in this case, the common card becomes the master, and the activation data is distributed individually to the corresponding functional unit card. However, in this case: Unlike the start / reset status of the entire device, the base station device is already in operation (communication service is being provided), and the common card itself is also performing processing related to base station operation functions Thus, activation data distribution is performed individually for the corresponding functional unit card.

  For example, as a conventional technique, each functional unit card has a common card and each functional unit card, and the activation data acquired from the common card is individually held in each functional unit card. There is a base station device to hold (for example, see Patent Document 1 below). In addition, there is a program download method that distributes activation data that is collectively held by a download device as a main device to a plurality of devices in a network by hop-transferring between the devices (see, for example, Patent Document 2 below) .)

JP 2008-17245 A Japanese Patent Laid-Open No. 06-60046

  However, the activation data held by each functional unit card is a copy of the activation data of each functional unit card held by the common card, and the activation data exists redundantly in the base station apparatus. In this case, the non-volatile memory for storing the activation data has the disadvantages that the bit unit price is high and the cost is high, and the rewriting time is long.

  In addition, when a common card in operation performs activation data distribution processing for each functional unit card, the processing load on the common card increases. At this time, non-operational packet communication occurs on the inter-card interface, resulting in a problem of obstructing communication of operation packets.

  In the technique of Patent Document 1, when the activation data and each unique data of the functional unit card are updated, a process of updating the activation data on each functional unit card occurs, and the activation time of the functional unit card is delayed. Arise. In the technique of Patent Document 2, each device must provide a distribution server function for distributing data, as with a download device. Each device also operates in a standby state (non-operational state) before acquisition of startup data. Because of this, power consumption cannot be reduced. Furthermore, when a failure or error occurs in a device in the middle of the transfer route, data cannot be normally distributed to the subsequent devices (the latter stage).

  In one aspect, an object of the present invention is to prevent activation data redundancy in an apparatus and to efficiently perform data distribution processing for a plurality of cards.

  In one plan, the base station apparatus is a base station apparatus including a plurality of functional unit cards and a common card that holds activation data of the functional unit cards, and the common card includes the plurality of functional units. A transfer list creating unit for creating a transfer list including destination information of each of the plurality of functional unit cards, which is distributed together with activation data for the card, and for the one functional unit card among the plurality of functional unit cards A distribution control unit that distributes the activation data to which the transfer list is added, and the functional unit card acquires the transfer list from the transferred activation data and is not excluded from the transfer list. Is left as the transfer destination, and the transfer list is selected from the transfer list. A transfer list processing unit that updates the transfer list so as to exclude destination information of a previous functional unit card, adds the transfer list to the activation data, and transfers the transfer list to the functional card of the transfer destination Is a requirement.

  According to one embodiment, redundancy of data between a plurality of cards can be prevented, and data distribution processing to a plurality of cards can be performed efficiently.

FIG. 1 is a diagram for explaining distribution of activation data of the base station apparatus according to the first embodiment. FIG. 2 is a diagram of a hardware configuration example of the base station apparatus according to the first embodiment. FIG. 3 is a block diagram of a configuration related to a data distribution function of the base station apparatus according to the first embodiment. FIG. 4 is a diagram illustrating a configuration example of distribution data according to the first embodiment. FIG. 5 is a sequence diagram of an example of activation data distribution according to the first embodiment. FIG. 6 is a diagram for explaining memory access during activation data distribution according to the first embodiment. FIG. 7 is a sequence diagram illustrating an example of redistribution when activation data distribution fails according to the first embodiment. FIG. 8 is a flowchart of a common card activation data distribution process example according to the first embodiment. FIG. 9 is a flowchart of an example of activation data transfer processing of the functional unit card according to the first embodiment. FIG. 10 is a diagram illustrating a configuration example of distribution data according to the second embodiment. FIG. 11 is a diagram for explaining memory access during activation data distribution according to the second embodiment. FIG. 12 is a diagram illustrating a configuration example of distribution data according to the third embodiment. FIG. 13 is a diagram for explaining memory access during start-up data distribution according to the third embodiment. FIG. 14 is a sequence diagram illustrating an example of activation data distribution using an existing transfer method.

  Hereinafter, preferred embodiments of the disclosed technology will be described in detail with reference to the accompanying drawings.

(Embodiment 1)
(Base station device startup data distribution example)
FIG. 1 is a diagram for explaining distribution of activation data of the base station apparatus according to the first embodiment. Base station apparatus 100 includes a common card 101, a plurality of functional unit cards 111, and an inter-card interface 121.

  The common card 101 is commonly used in the apparatus, for example, and assists the processing of the functional unit card 111. The functional unit card 111 performs a predetermined process for each card. In FIG. 1, a plurality of functional units # A-1 to #Am, # B-1 to # B-n are classified according to function types #A to #B. Including cards. The function types include, for example, a card that performs data transmission / reception processing for each communication layer, a card that controls the base station apparatus 100, and the like. The function unit cards 111 of the function types #A and #B can be activated using different activation data A and B corresponding to each.

  The common card 101 and the plurality of functional unit cards 111 are computer processing cards each including a processor, a memory, and the like, and exchange data with each other via an inter-card interface 121. For example, an SRIO (Serial RapidIO) switch card is used as the inter-card interface 121.

  With reference to FIG. 1, distribution of activation data during operation of the base station apparatus 100 to each functional unit card 111 will be described. The common card 101 stores activation data of the base station device 100, that is, activation data of all the functional unit cards 111 in the SSD 102. The SSD 102 stores start-up data of a field-programmable gate array (FPGA) and a micro-processing unit (MPU) mounted on the functional unit card 111.

  Here, it is assumed that the common card 101 performs data processing of the operating base station apparatus 100 (in operation state), and the functional unit card 111 is in a non-operation state.

  In the first embodiment, the common card 101 directly activates the functional unit card 111 using the activation data held in the SSD 102. Further, the distribution of activation data to the functional unit card 111 that occurs in the common card 101 equipped with the SSD 102 is shared (distributed) by the functional unit card (group) 111 in the non-operating (unactivated) state waiting for activation data distribution. )

  The common card 101 does not repeat the distribution to each function unit card 111 that has not been activated. The common card (#C) 101 transfers activation data for only one time to a predetermined functional unit card (# A-1) 111 of a predetermined function type (group) via the inter-card interface 121 (step). S101). For example, a case where the FPGA activation data 131a of the functional unit card group (#A) 111 is transferred will be described.

  Thereafter, the functional unit card (# A-1) 111 that has received the transfer transfers the activation data 131a to the other functional unit card (# A-2) via the inter-card interface 121 (step S102). Thereafter, the functional unit card (# A-2) 111 that has received the transfer transfers the activation data 131a to the other functional unit card (# A-m) via the inter-card interface 121 (step S10m). In this way, the hop transfer of the activation data 131a is performed between the m functional unit cards (# A-1 to # A-m) (the transfer count is m-1).

  Transfer of activation data (for example, activation data 141b for MPU of function unit card group (#B) 111) to function unit cards (# B-1 to #B to n) 111 of other function types (groups) Similarly, the common card 101 transfers the activation data 141b only once to the predetermined functional unit card (# B-1) (step S201). Thereafter, hop transfer of the activation data 141b is performed between n functional unit cards (# B-1 to # B-n) (the transfer count is n-1 times, step S202 to step S20n).

  As a result, the number of activation data transfers performed under the initiative of the common card 101 is greatly reduced, and even if the common card 101 is in operation, the processing load on the transfer process of the common card 101 can be reduced to other levels. It is possible to distribute the function unit cards 111 in the non-operating state.

  FIG. 2 is a diagram of a hardware configuration example of the base station apparatus according to the first embodiment. The same components as those in FIG. 1 are denoted by the same reference numerals.

  First, the common card (#C) 101 includes an SSD 102, a PLD (Programmable Logic Device) 203, a non-volatile memory (for example, FLASH memory) 204, an FPGA 205, an MPU 206, and a volatile memory (for example, RAM) 207. And including.

  The SSD 102 holds activation data for all cards provided in the base station apparatus 100. That is, the SSD 102 includes activation data for the common card (#C) 101 (activation data for FPGA 205 and MPU 206) and activation data for each functional unit card 111 (for FPGA and MPU of function type groups #A to #C). Data).

  The PLD 203 controls the nonvolatile memory 204. The nonvolatile memory 204 stores activation data (activation data for FPGA 205 and MPU 206) for updating the common card (#C). Then, the PLD 203 transfers the FPGA data (FPGA startup data) on the nonvolatile memory 204 to the FPGA 205, and transfers the software data (MPU startup data) on the nonvolatile memory 204 to the MPU 206. Activation processing of the FPGA 205 and the MPU 206 is performed.

  The FPGA 205 has functions such as a controller for controlling the SSD 102 and a driver for the SRIO switch card 121. The MPU 206 controls the overall processing of the common card 101, and at this time, uses the volatile memory 207 as a work data area.

  Next, each functional card (eg, # A-1) 111 includes a PLD 213, a nonvolatile memory (eg, FLASH memory) 214, an FPGA 215, an MPU 216, and a volatile memory (eg, RAM) 217, respectively. Including.

  The PLD 213 controls the nonvolatile memory 214. The nonvolatile memory 214 stores data such as communication control used by the FPGA 215 and the MPU 216. In the first embodiment, the startup data of the FPGA 215 and the MPU 216 is not stored in the nonvolatile memory 214, but is stored in the volatile memory 217. Therefore, the nonvolatile memory 214 can have a minimum memory capacity. The capacity can be reduced to the minimum.

  The FPGA 215 has a function of a driver for the SRIO switch card 121. When the activation data is received from the common card 101, the activation data is stored in the volatile memory 217 by, for example, DMA (Direct Memory Access).

  The MPU 216 controls the entire processing of the functional unit card 111, and at this time, a part of the area of the volatile memory 217 is used as a work data area. The other functional unit cards (# A-2, # B-1) 111 have the same configuration as the functional unit card (# A-1) 111.

  FIG. 3 is a block diagram of a configuration related to a data distribution function of the base station apparatus according to the first embodiment. The common card 101 includes a data management function unit 301, a distribution server function unit 302, and an SRIO function unit 303.

  The data management function unit 301 includes an SSD control unit 301 a that controls reading and writing of data with respect to the SSD 102.

  The distribution server function unit 302 includes a distribution request reception processing unit 302a, an activation data distribution control unit 302b, and a transfer list creation function unit 302c. When the distribution request reception processing unit 302a receives a distribution request for activation data of the same type (function type #A in FIG. 3) from the functional unit card 111, the distribution request reception processing unit 302a causes the activation data distribution control unit 302b to perform distribution control of activation data. . The activation data distribution control unit 302b reads the activation data of the function type #A from the SSD 102 to the SSD control unit 301a and outputs it to the SRIO function unit 303. The transfer list creation function unit 302c creates a transfer list of activation data to the plurality of function units 111 (# A-1 and # A-2 in FIG. 3) related to the read function type #A, and stores it in the SRIO function unit 303. Output.

  The SRIO function unit 303 includes a reception processing unit 303a and a transmission processing unit 303b. The SRIO function unit 303 transmits / receives data to / from the function unit card (# A-1, # A-2) 111 via the inter-card interface (SRIO). The reception processing unit 303a receives data (activation data distribution request) from the functional unit card (# A-1, # A-2) 111. The transmission processing unit 303b transmits data (activation data) to the function unit card (# A-1, # A-2) 111, and the transfer list created by the transfer list creation function unit 302c is stored in the function unit card (# A-1) Transmit to 111.

  In the first embodiment, among the plurality of function unit cards (# A-1, # A-2) 111 of the function type #A, the highest one being distributed is the common card 101 representing the function type #A. Send and receive data to and from. For example, the functional unit card (# A-1) 111 of number # 1 transmits and receives data to and from the common card 101 first.

  The functional unit card (# A-1) 111 includes an SRIO functional unit 311 and a distribution client functional unit 312.

  The SRIO function unit 311 includes a reception processing unit 311a and a transmission processing unit 311b. The SRIO function unit 311 transmits and receives data to and from the common card 101 via an inter-card interface (SRIO). The reception processing unit 311a receives data (activation data) from the common card 101 and a transfer list. The transmission processing unit 311 b transmits data (activation data distribution request) to the common card 101.

  The distribution client function unit 312 includes a distribution request transmission processing unit 312a, an activation data reception processing unit 312b, and a transfer list processing function unit 312c.

  The distribution request transmission processing unit 312a inquires of the common card 101 about the activation data of the function unit card (# A-1, # A-2) 111 of the function type #A, and asks the common card 101 whether the latest version of activation data exists. If there is activation data, a distribution request for activation data is made to the common card 101.

  The activation data reception processing unit 312b receives the activation data transmitted from the common card 101. The transfer list processing function unit 312c performs transfer processing by updating the transfer list transmitted from the common card 101 or the like. The transfer list processing function unit 312c updates the received activation data and transfer list based on the transfer list, and performs a process of transferring to the next functional unit card (# A-2) 111 (details will be described later).

  The other functional unit card (# A-2) 111 has the same configuration as that of the functional unit card (# A-1) 111.

  In the configuration example of FIG. 3, the transfer list creation function unit 302 c of the common card 101 is provided in the MPU 206 and creates a transfer list by executing software of the MPU 206. The transfer list processing function unit 312c of the function unit card 111 is provided in the MPU 216, and processes the transfer list by executing software of the MPU. Further, the transfer list processing function unit 312c of the functional unit card 111 may be provided in the FPGA 215 to process the transfer list by hardware (circuit).

  In FIG. 3, the transfer list created by the common card 101 is transmitted to the function unit card (# A-1) 111 in accordance with the transfer order described in the transfer list, and then the function unit card (# A-1) 111. Is transferred to (# A-2) 111. The function unit card (# A-1) 111 also transfers the activation data together with the transfer list to the other function unit card (# A-2) 111.

  Although details will be described later, the transfer list processing function unit 312c of each functional unit card (for example, # A-1) 111 receives the activation data by the own card and then deletes the transfer list to which the transfer list addressed to the own card is deleted. It transmits to the functional unit card (# A-2) 111 of the next transfer destination.

  FIG. 4 is a diagram illustrating a configuration example of distribution data according to the first embodiment. FIG. 4 shows an example of the function type #A activation data 401 distributed by the activation data distribution control unit 302b and the function type #A transfer list 402 created by the transfer list creation function unit 302c of the common card 101. is there.

  As shown in FIG. 4, distribution data 400 is distributed by linking transfer list 402 to activation data 401. The activation data 401 includes header information 411 including a transfer data size 411a and an activation data size 411b. In the transfer list 402, for each function type #A, each functional unit card (# A-1 to # A-3) 111 that has requested activation data distribution is set as destination information.

  Here, the transfer list creation function unit 302c of the common card 101 positions the destination information 421a of the function unit card (# A-1) 111 having the highest delivery order to be delivered first from the activation data 401. Place at (end of address). Further, the destination information 421c of the functional unit card (# A-3) 111 having the lowest distribution order distributed by the common card 101 is arranged at a position (address) next to the activation data 401.

  The transfer list processing function unit 312c of the transmission side card, for example, the functional unit card (# A-1) 111, deletes the destination information 421b addressed to the next functional unit card (# A-2) 111. 402 is transferred to the functional unit card (# A-2) 111 of the next transfer destination. As a result, each time the activation data 401 is transferred, the destination information 421a to 421c is deleted, and the transfer data size can be reduced (variable).

  Further, since the transfer list 402 (destination information 421) at the end of the address is deleted every time the activation data 401 is transferred, there is no free space between the activation data 401 and the transfer list 402, and the data size of the distribution data 400 is always set to be the same. Can be minimized.

  FIG. 5 is a sequence diagram of an example of activation data distribution according to the first embodiment. Assume that both the common card 101 and the functional unit cards (# A-1, # A-2) 111 are in operation. Thereafter, the functional unit card (# A-1, # A-2) 111 is reset (step S501), and the functional unit card (# A-1, # A-2) 111 becomes non-operating ( In step S502), it is assumed that the activation data distribution request is made to the common card 101 (step S503).

  The common card 101 confirms the request for distribution of the activation data A of the function type #A (step S504), and creates the transfer list 402 of the activation data A of the function type #A (step S505). Then, the common card 101 distributes the activation data A and the transfer list 402 to the function unit card (# A-1) 111 of the function type #A higher in the transfer list (step S506). At this time, the common card 101 deletes the destination information 421a of the functional unit card (# A-1) 111 of the current transfer destination (the destination information of the transfer list 402 is one item 421b), and the distribution data 400 is stored in the functional unit card. (# A-1) Data is distributed to 111.

  The functional unit card (# A-1) 111 receives the distribution data 400 and takes in the activation data 401 into its own device. Also, it is determined from the header information 411 whether or not the transfer list 402 is linked to the distribution data 400. If there is the transfer list 402, the function of the next transfer destination is excluded except for one item at the end of the transfer list 402. The distribution data 400 is transferred to the copy card (# A-2) 111 (step S507). That is, the functional unit card (# A-1) 111 deletes the destination information 421b of the functional unit card (# A-2) 111 of the transfer destination (there is no destination information in the transfer list 402), and the distribution data 400 is stored in the functional unit card. (# A-2) Data is distributed to 111.

  Thereafter, the functional unit card (# A-1) 111 performs a startup process (BOOT) based on the received startup data 401 (step S508), enters an operating state (step S509), and Notify the operating status.

  The functional unit card (# A-2) 111 receives the distribution data 400, takes in the activation data 401 into its own device, and based on the transfer list 402 of the distribution data 400, there is no next distribution destination. Transfer processing is not performed.

  Thereafter, the functional unit card (# A-2) 111 performs a startup process (BOOT) based on the received startup data 401 (step S510), enters an operating state (step S511), and Notify the operating status.

  FIG. 5 further shows a case where all the function unit cards (# B-1, # B-2) 111 of the function type #B are newly mounted (inserted into the card slot of the base station apparatus 100, etc.). The process at the time of mounting will be described.

  In the state where the common card 101 is in operation, all of the functional unit cards (# B-1, # B-2) 111 of the function type #B are newly mounted (step S521), and these functional unit cards (# B-1, # B-2) Assume that 111 is in a non-operational state (step S522), and a request for distribution of activation data is made to the common card 101 (step S523).

  The common card 101 confirms the request for distribution of the activation data B of the function type #B (step S524), and creates the transfer list 402 of the activation data B of the function type #B (step S525). Then, the common card 101 distributes the activation data B and the transfer list to the functional unit card (# B-1) 111 of the function type #B higher in the transfer list (step S526). At this time, the common card 101 deletes the destination information of the functional unit card (# B-1) 111 of the current transfer destination (the destination information of the transfer list 402 is one item of the functional unit card (# B-2) 111. ) Distribute the distribution data 400 to the functional unit card (# B-1) 111.

  The functional unit card (# B-1) 111 receives the distribution data 400, takes in the activation data 401 into its own device, and based on the transfer list 402 of the distribution data 400, the functional unit that is the next distribution destination Data is transferred to the card (# B-2) 111 (step S527). At this time, the functional unit card (# B-1) 111 deletes the destination information of the transfer destination functional unit card (# B-2) 111 (there is no destination information in the transfer list 402) and the distribution data 400 is stored in the functional unit card. (# B-2) Data is distributed to 111.

  Thereafter, the functional unit card (# B-1) 111 performs the activation process (BOOT) based on the received activation data 401 (step S528), enters the operating state (step S529), and Notify the operating status.

  The functional unit card (# B-2) 111 receives the distribution data 400, takes in the activation data 401 into its own device, and has no next distribution destination based on the transfer list 402 of the distribution data 400. Transfer processing is not performed.

  Thereafter, the functional unit card (# B-2) 111 performs the activation process (BOOT) based on the received activation data 401 (step S530), enters the operating state (step S531), and the common card 101 Notify the operating status.

  With the transfer process described above, the distribution data 400 from the common card 101 to a plurality of functional unit cards only needs to be transferred once for each function type, and the common card 101 has more resources that can be allocated to the operation process. Can be secured. At the same time, the waiting state of the distribution data 400 from the common card 101 can be mitigated also on the functional unit card 111 side.

  Further, based on the configuration of the transfer list 402 created by the common card 101, a specific functional unit card 111 can process a plurality of pieces of destination information. Also, the common card 101 creates a transfer list 402 including activation data 401 of the functional unit card group 111 of different function types #A and #B, and activates different function types #A and #B in one delivery. Distribution of the data 401 can also be performed (details will be described later).

  FIG. 6 is a diagram for explaining memory access during activation data distribution according to the first embodiment. The memory space on the inter-card interface (SRIO switch card) 121 used between the common card 101 and each functional unit card (# A-1 to #An) 111 is shown. FIG. 6 shows one memory space, but it is set individually on the common card 101 and on each functional unit card (# A-1 to #An) 111.

  In the memory space 601 of the common card 101, the activation data 401 of the function type #A and the transfer list 402 of the functional unit cards (distribution order # A-1, # A-2, # A-4) 111 of the distribution destination It is assumed that the destination information 421a, 421b, 421d has been created.

  In this case, the common card 101 excludes the destination information 421a of one case at the end of the transfer list 402 (functional unit card (# A-1) 111), and the functional unit card (# A-2, #A) of the distribution destination. -4) The destination information 421b and 421d of 111 is set as the transfer list 402. The common card 101 transfers the transfer list 402 and the activation data 401 as distribution data 400a to the functional unit card (# A-1) 111 via the inter-card interface (SRIO switch card) 121 (1).

  As described above, in the first embodiment, the common card 101 only needs to perform the transfer of the distribution data 400a in the first (1). (2) Subsequent transfers are executed by the transfer destination functional unit cards (# A-1, # A-2, # A-4) 111, respectively. The functional unit card (# A-1) 111 excludes the destination information 421b of one item (functional unit card (# A-2) 111) at the end of the transfer list 402 at the next transfer. Then, the functional unit card (# A-1) 111 transmits the distribution data 400b in which the destination information 421d of the functional unit card (# A-4) 111 of the distribution destination is the transfer list 402 to the functional unit card (# A-2). 111.

  Similarly, the functional unit card (# A-2) 111 excludes the destination information 421d of one item (functional unit card (# A-4) 111) at the end of the transfer list 402 at the next transfer. Then, the functional unit card (# A-2) 111 transfers the distribution data 400b having only the activation data 401 without destination information in the transfer list 402 to the functional unit card (# A-4) 111.

  In this way, the distribution data 400 reduces the data in the transfer list 402 and sends it to the inter-card interface (SRIO switch card) 121 for each transfer. Can be reduced.

  Further, by using SRIO for the inter-card interface 121, additional information related to communication (delivery and transfer of startup data) can be reduced, and the common card 101 and each functional unit card (# A-1 to #An) 111 can be reduced. The communication processing load can be reduced. In addition, by using SRIO for the inter-card interface 121, for example, the common card 101 side performs distribution processing of activation data by executing software of the MPU 206, and the functional unit card 111 performs transfer processing with a hardware-only configuration. You can also.

  As described above, the activation data 401 (distribution data 400) transfer process using the transfer list 402 in the functional unit cards (# A-1 to #An) 111 is performed by the hardware of the FPGA 215 and the volatile memory 217. Can be implemented in cooperation with DMA control (see FIG. 2). In this case, the transfer of the distribution data 400 can be realized with a minimum amount of hardware and firmware (equivalent to a boot loader).

  In the first embodiment, the distribution data 400 (activation data 401) is the common card 101 → the functional unit card (# A-1) 111 → the functional unit card (# A-2) 111 → the functional unit card (#A). -4) As shown in 111, it is basically implemented by a single serial distribution route. That is, there is only one distribution route to a certain card. If there are multiple routes to the same destination, the transfer processing (including determination of whether or not the transfer has been completed and transfer stop processing) of the route that has arrived later will be wasted. This waste can be prevented in the processing of the first embodiment. Here, the processing when an abnormality occurs in the middle of one delivery route will be described below.

  FIG. 7 is a sequence diagram illustrating an example of redistribution when activation data distribution fails according to the first embodiment. It is assumed that the common card 101 and the function unit cards (# A-1, # A-2, # A-4) 111 are all in operation. Thereafter, the function unit cards (# A-1, # A-2, # A-4) 111 are reset (step S701), and these function unit cards (# A-1, # A-2, #A) are generated. -4) Assume that 111 is in a non-operational state (step S702), and a distribution request for activation data is made to the common card 101 (step S703).

  The common card 101 confirms the request for distribution of the activation data A of the function type #A (step S704), and creates the transfer list 402 of the activation data A of the function type #A (step S705). Then, the common card 101 distributes the activation data A and the transfer list 402 to the functional unit card (# A-1) 111 of the function type #A higher in the transfer list (step S706). At this time, the common card 101 deletes the destination information 421a of the functional unit card (# A-1) 111 of the current transfer destination (the destination information of the transfer list 402 is two cases of 421b and 421d), and the distribution data 400 functions. Data is distributed to the copy card (# A-1) 111.

  As described above, the common card 101 in the operating state distributes the distribution data 400 (activation data 401) to the specific functional unit card (# A-1) 111 at a predetermined time between the operation processes. I do.

  The functional unit card (# A-1) 111 receives the distribution data 400 and takes in the activation data 401 into its own device. Also, it is determined from the header information 411 whether or not the transfer list 402 is linked to the distribution data 400. If there is the transfer list 402, the function of the next transfer destination is excluded except for one item at the end of the transfer list 402. The distribution data 400 is transferred to the copy card (# A-2) 111 (step S707). That is, the functional unit card (# A-1) 111 deletes the destination information 421b of the functional unit card (# A-2) 111 of the transfer destination (the destination information of the transfer list 402 is one item 421d). Is distributed to the functional unit card (# A-2) 111.

  Thereafter, the functional unit card (# A-1) 111 performs a startup process (BOOT) based on the received startup data 401 (step S708), enters an operating state (step S709), and Perform operation start notification.

  The functional unit card (# A-2) 111 receives the distribution data 400 and takes in the activation data 401 into its own device. At this time, an error occurs in the received data (step S711), and the own device cannot be activated. Assume that a failure state is reached (step S712). In this case, the functional unit card (# A-2) 111 cannot distribute the distribution data 400 to the next functional unit card (# A-4) 111. However, this functional unit card (# A-2) 111 can be restored by restarting in the case of a recoverable error (failure). For this reason, the functional unit card (# A-2) 111 performs reset / restart (step S713), enters a non-operational state (step S714), and requests the common card 101 to distribute start data again (step S714). Step S715).

  Then, the functional unit card (# A-4) 111 monitors the distribution waiting time T at the timing when the activation data distribution request is made, and determines that a timeout occurs if the distribution data 400 is not distributed after a predetermined time. (Step S721). Then, the functional unit card (# A-4) 111 issues a startup data distribution request to the common card 101 (step S722).

  The common card 101 confirms the request for distribution of the activation data A of the function type #A from the functional unit card (# A-4) 111 (step S724), and creates the transfer list 402 of the activation data A (step S725). ). Then, the common card 101 distributes the activation data A and the transfer list to the functional unit card (# A-4) 111 of the function type #A higher in the transfer list (step S726). At this time, since the common card 101 is only one of the functional unit cards (# A-4) 111 of the current transfer destination, the distribution data 400 without destination information in the transfer list 402 is transferred to the functional unit card (# A- 4) Data is distributed to 111.

  After this, the functional unit card (# A-4) 111 performs the activation process (BOOT) based on the received activation data 401 (step S730), enters the operating state (step S731), and the common card 101 Notify the operating status.

  As described above, in the case where distribution is not possible in the middle of one distribution route, the common card 101 is again undistributed functional unit in the time-out process on the functional unit card (# A-4) 111 side that receives distribution data. The activation data 401 can be distributed to the card (# A-4) 111.

(Common card activation data distribution processing)
FIG. 8 is a flowchart of a common card activation data distribution process example according to the first embodiment. In FIG. 8, the distribution request reception processing (step S800A) performed by the distribution request reception processing unit 302a of the common card 101, the transfer list generation processing (step S800B) performed by the transfer list generation function unit 302c, and the activation data distribution control unit 302b. The startup data distribution control process (step S800C) to be performed is shown.

  First, the common card 101 executes distribution request reception processing (step S800A) by the distribution request reception processing unit 302a, and checks whether or not a distribution request for activation data has been received (step S801). Then, it is determined whether there is a request for distribution of one or more activation data (one card) from the functional unit card 111 (step S802). If there is no activation data distribution request, the process returns to step S801 to wait for the activation data distribution request (step S802: No). For example, the distribution request reception processing unit 302a periodically executes step S801 to confirm the activation data distribution request.

  If there is one or more (one card) activation data distribution request from the functional unit card 111 (step S802: Yes), the distribution request reception processing unit 302a transmits information (contents) of the activation data distribution request. Analysis is performed (step S803). Then, the distribution request reception processing unit 302a determines whether there is a distribution request from a plurality of functional unit cards (# A-1, # A-2, etc.) 111 of the same function type (for example, #A) (step S804). ).

  If there is a distribution request from a plurality of functional unit cards 111 of the same function type (for example, #A) (step S804: Yes), the processes after step S805 are performed. If there is no distribution request from a plurality of functional unit cards 111 of the same function type (for example, #A) (step S804: No), the processing after step S811 is performed.

  In step S805, the distribution request reception processing unit 302a reads and controls the activation data A of the corresponding same function type (for example, #A) from the SSD 102 to the SSD control unit 301a (step S805). Then, the distribution request reception processing unit 302a passes the activation data A to the transfer list creation function unit 302c, and performs transfer list creation processing (step S800B).

  In the transfer list creation process (step S800B), the transfer list creation function unit 302c first (1) creates the distribution data 400 (step S806). In (1) creation of distribution data 400, transfer destination information (functional unit card 111) is extracted, transfer order is determined, and transfer list 402 is generated.

  Next, the transfer list creation function unit 302c creates (2) delivery data 400 (step S807). In the creation of (2) distribution data 400, the transfer list 402 is stored at the end of the read activation data 401 (see FIG. 4).

  Next, the transfer list creation function unit 302c creates (3) delivery data 400 (step S808). (3) In creating the distribution data 400, header information (transfer data size 411a, activation data size 411b) at the head of the distribution data 400 is set. Then, the transfer list creation function unit 302c passes the delivery data 400 created by the above processing to the activation data delivery control unit 302b.

  In the activation data distribution control process (step S800C), the activation data distribution control unit 302b first prepares for data transfer (step S809). In this data transfer preparation, one item in the transfer list 402 at the end of the distribution data 400 (for example, the destination information 421a in FIG. 4) is set as transmission control information. Then, the activation data distribution control unit 302b transmits the distribution data 400 (activation data 401 and transfer list 402) to the functional unit card (for example, # A-1) 111 of the transfer list 402 (destination information 421a in FIG. 4). Transmission is executed (step S810).

  In step S804, if there is no distribution request from a plurality of functional unit cards 111 of the same function type (for example, #A) (step S804: No), the distribution request reception processing unit 302a sends a request to the SSD control unit 301a. The activation data A of one corresponding item (for example, the functional unit card 111 of # A-1) is read from the SSD 102 and controlled (step S811). In the subsequent processing, the transfer list creation processing (step S800B) is not performed, and the process proceeds to the startup data distribution control processing (step S800C).

  Then, the distribution request reception processing unit 302a passes the activation data A to the activation data distribution control unit 302b to perform activation data distribution control processing. Then, the activation data distribution control unit 302b first prepares for data transfer (step S812). In this data transfer preparation, the activation data distribution control unit 302b sets the function unit card (for example, # A-1) 111 of one received request source (destination information 421a in FIG. 4) as transmission destination in the transmission control information. . The transmission control information includes, for example, an identifier of the destination functional unit card 111, received data storage destination information (memory size, etc.), transfer data size, and the like.

  Then, the activation data distribution control unit 302b transmits the distribution data 400 (activation data 401 and transfer list 402) to the destination functional unit card (for example, # A-1) 111 (step S810).

(Function data card startup data transfer process)
FIG. 9 is a flowchart of an example of activation data transfer processing of the functional unit card according to the first embodiment. FIG. 9 shows a distribution request transmission process (step S900A) performed by the distribution request transmission processing unit 312a of the functional unit card 111, an activation data reception process (step S900B) performed by the activation data reception processing unit 312b, and a transfer list processing function unit 312c. The transfer list process (step S900C) and the like to be performed are respectively shown.

  First, the functional unit card 111 transmits a distribution request for activation data to the common card 101 by the distribution request transmission processing unit 312a when necessary (step S901), and distributes the activation data 401 (distribution data 400) from the common card 101. Wait (step S902). If the activation data 401 (distribution data 400) is not distributed from the common card 101 (step S902: No), the distribution is retried to the common card 101 (return to step S901).

  If the activation data 401 is distributed from the common card 101 (step S902: Yes), the distribution data 400 (activation data 401 and transfer list 402) is received and processed by the activation data reception processing unit 312b (step S903). Then, the activation data reception processing unit 312b checks the header information 411 of the distribution data 400 (Step S904).

  Then, the transfer list processing function unit 312c determines whether the transfer list 402 is added to the activation data 401 (step S905). If the transfer list 402 is added to the activation data 401 (step S905: Yes), the transfer list processing function unit 312c executes the processing from step S906 onward for the transfer list processing (step S900C), and stores the activation data 401 in the activation data 401. If the transfer list 402 is not assigned (step S905: No), the transfer list process (step S900C) is not executed, and the process proceeds to step S910.

  In step S906, the transfer list processing function unit 312c performs distribution data analysis (step S906). In this distribution data analysis, one item in the transfer list 402 at the end of the received distribution data 400 (for example, the destination information 421b in FIG. 4) is extracted. Then, the transfer list processing function unit 312c updates the header information (transfer data size 411a, activation data size 411b) at the top of the distribution data 400 (step S907). At this time, the transfer list 402 for one transfer destination (# A-2) to which the own function unit card (# A-1) is responsible for transfer from the data size received by the own function unit card (# A-1) 111. The size obtained by subtracting (destination information 421b) is updated and set as a new data size.

  Next, the transfer list processing function unit 312c prepares for distribution data transfer (step S908). In this distribution data transfer preparation, one transfer list at the end of distribution data 400 to be transferred (for example, destination information 421b in FIG. 4) is set as transmission control information. The transmission control information includes, for example, an identifier of the destination functional unit card 111, received data storage destination information (memory size, etc.), transfer data size, and the like.

  Then, the transfer list processing function unit 312c transmits the distribution data 400 (activation data 401 and transfer list 402) to the destination function unit card (for example, # A-2) 111 (step S909).

  Thereafter, the functional unit card 111 loads the activation data 401 and starts activation of the own functional unit card 111 (step S910). Then, after the activation is completed, the functional unit card 111 notifies the common card 101 that operation is in progress (operation start) (step S911).

(Embodiment 2: Another configuration example of distribution data)
FIG. 10 is a diagram illustrating a configuration example of distribution data according to the second embodiment. By changing the structure of the transfer list 402 of the distribution data 400, a specific functional unit card 111 can be configured to distribute to a plurality of functional unit cards 111.

  For example, in the example illustrated in FIG. 10, the transfer list creation function unit 302 c of the common card 101 uses the destination information 421 a of the function unit card (# A-1) 111 with the highest delivery order to be delivered first as the activation data. It is arranged at a position farthest from 401 (address end).

  Also, two destinations (# A-2, # A-3) are set in the destination information 421b of the specific functional unit card (# A-2, # A-3) 111 to be distributed next. Further, two destinations (# A-4, # A-6) are set in the destination information 421c of the specific functional unit card (# A-4, # A-6) 111 to be distributed next.

  Further, the destination information 421d of the functional unit card (# A-5) 111 having the lowest delivery order delivered by the common card 101 is arranged at a position (address) next to the activation data 401.

  FIG. 11 is a diagram for explaining memory access during activation data distribution according to the second embodiment. Based on the transfer list 402 shown in FIG. 10, the simultaneous execution (parallel processing) of the distribution data 400 to a plurality of functional unit cards (# A-1 to #An) is shown. The vertical axis in the figure is the time axis.

  In the memory space 601 of the common card 101, the activation data 401 of the function type #A and the functional unit card of the distribution destination (distribution order is # A-1, # A-2 and # A-3, # A-4 and # It is assumed that the destination information 421a to 421d is created as the transfer list 402 of A-6, # A-5) 111.

  In this case, the common card 101, except for the destination information 421a of one case (functional unit card (# A-1) 111) at the end of the transfer list 402, is the functional unit card (# A-2 and #A) of the distribution destination. -3, # A-4 and # A-6, # A-5) 111 destination information 421b to 421d is a transfer list 402. The common card 101 transfers the transfer list 402 and the activation data 401 as distribution data 400a to the functional unit card (# A-1) 111 via the inter-card interface (SRIO switch card) 121 (1).

  At the next transfer, the functional unit card (# A-1) 111 receives the distribution data except for the destination information 421b of the last item (functional unit cards # A-2 and # A-3) 111 in the transfer list 402. 400b is distributed to the functional unit card (# A-2) 111 of the distribution destination (2).

  Thereafter, the functional unit card (# A-1) 111 removes the destination information 421c of the last item (functional unit cards # A-4 and # A-6) 111 of the transfer list 402 at the next transfer. Then, the distribution data 400c is distributed to the functional unit card (# A-3) 111 of the distribution destination (3).

  In the functional unit card (# A-2) 111, at the time of the next transfer, the destination information 421c of the last item (functional unit cards # A-4 and # A-6, # A-5) 111 for the transfer list 402, With the exception of 421d, the distribution data 400d is distributed to the functional unit card (# A-4) 111 of the distribution destination (3). Thereafter, the functional unit card (# A-2) 111 distributes the distribution data 400d (only the activation data 401) to the functional unit card (# A-6) 111 of another distribution destination (4).

  In the functional unit card (# A-3) 111, at the time of the next transfer, the distribution data 400d (activation data 401) is excluded except for the destination information 421d of the last item (functional unit card # A-5) 111 in the transfer list 402. Only) is distributed to the functional unit card (# A-5) 111 of the distribution destination (4).

  According to the transfer process of the second embodiment, since each functional unit card 111 shares and transfers the distribution data 400, the processes (3) and (4) can be executed simultaneously (parallel process). In the above example, the distribution of the activation data 401a to the six functional unit cards (# A-1 to # A-6) 111 can be completed in four transfer times. For example, when the number of functional unit cards 111 as distribution destinations is large, the time required to complete distribution to all the functional unit cards 111 can be shortened.

(Embodiment 3: Other configuration examples of distribution data)
FIG. 12 is a diagram illustrating a configuration example of distribution data according to the third embodiment. By changing the structure of the transfer list 402 of the distribution data 400, the specific functional unit card 111 can be configured to distribute the activation data A and B to a plurality of function types #A and #B.

  Transfer data size 411a and start data size 411b are assigned to start data (A) 401a and start data (B) 401b, respectively.

  For the transfer list 402 of the distribution data 400, the destination information 421a of the functional unit card (# A-1) 111 that performs distribution first is set in the transfer list (#C) 402c at the end of the address.

  In the upper address adjacent to the destination information 421a, the destination information 421b of the functional unit card 111 when the functional unit card (# A-1) 111 transfers is set. The destination information 421b distributes the activation data 401a of the function type #A to the function unit card (# A-2) 111 and the activation data 401b of the function type #B to the function unit card (# B-1) 111, respectively. It is a setting.

  At a higher address adjacent to the transfer list (#C) 402c, a transfer list (#B) 402b for transferring the activation data 401b of the function type #B is arranged, and the functional unit card (# B- 2) The destination information 421c of 111 and the destination information 421d of the functional unit card (# B-3) 111 to be distributed next are set.

  To the upper address adjacent to the transfer list (#B), the function list card (# A-3) that performs the distribution first is included in the transfer list (#A) 402a that transfers the activation data 401a of the function type #A. 111 destination information 421e and destination information 421f of the functional unit card (# A-4) 111 to be distributed next are set.

  FIG. 13 is a diagram for explaining memory access during start-up data distribution according to the third embodiment. The distribution of the activation data A and B to the functional unit cards 111 of the function types #A and #B based on the distribution data 400 shown in FIG. 12 will be described.

  The common card 101 functions via the inter-card interface (SRIO switch card) 121 using the distribution data 400a excluding the destination information 421a of one item at the end of the transfer list 402 (functional unit card (# A-1) 111). To the copy card (# A-1) 111 (1).

  The function unit card (# A-1) 111 excludes the data of the function type #B for the transfer of the activation data 401a to the function unit card (#A) 111 of the function type #A. At this time, the activation data 401b of the function type #B, the destination information 421b of the last item (the functional unit card (# A-2 and # B-1) 111) of the transfer list 402, and a different function type #B. The destination information 421c and 421d are excluded. The functional unit card (# A-1) 111 receives the distribution data 400c including the activation data 401a of the functional type #A and the transfer list 402a (destination information 421e and 421f) of the functional type #A. A-2) Deliver to 111 (2).

  Thereafter, the function unit card (# A-1) 111 excludes the data of the function type #A for the transfer of the activation data 401b to the function unit card (#B) 111 of the function type #B. At this time, the activation data 401a of the function type #A, the destination information 421b of one item at the end of the transfer list 402 (functional unit cards (# A-2 and # B-1) 111), and a different function type #A. The destination information 421e and 421f are excluded. The functional unit card (# A-1) 111 receives the distribution data 400d including the activation data 401b of the functional type #B and the transfer list 402b (destination information 421c, 421d) of the functional type #B as the functional unit card (# B-1) Deliver to 111 (3).

  In the functional unit card (# A-2) 111, at the time of the next transfer, the distribution data 400e excluding the destination information 421e for one item at the end of the transfer list 402 (functional unit card (# A-3) 111) is distributed to the distribution destination. To the functional unit card (# A-3) 111 (3). Thereafter, similarly, the activation data 401a of the function type #A is transferred to the functional unit card (# A-4) 111 (4).

  In the functional unit card (# B-1) 111, the distribution data 400f excluding the destination information 421c of the last item (the functional unit card (# B-2) 111) in the transfer list 402 is transferred to the distribution destination at the next transfer. To the functional unit card (# B-2) 111 (4). Thereafter, similarly, the activation data 401b of the function type #B is transferred to the functional unit card (# B-3) 111 (5).

  According to the transfer process of the third embodiment, only the functional unit card (# A-1) 111 that has received distribution directly from the common card 101 receives the activation data 401a and 401b of the function types #A and #B, and functions. Transfer to the function unit card 111 of the type #A group and the function unit card 111 of the function type #B group is performed twice. Thereafter, each function unit card (# A-2 to # A-4) 111 of the function type #A group and each function unit card (# B-2, # B-3) 111 of the function type #B group are The same transfer processing as that in the second embodiment is performed.

  Also in the third embodiment, since the functional unit cards 111 share and execute the transfer of the distribution data 400, the processes (3) and (4) can be executed simultaneously (parallel processing). In the above example, distribution to seven functional unit cards (# A-1 to # A-4, # B-1 to # B-3) 111 can be completed in a transfer time of five times.

  The third embodiment is effective in that efficient distribution can be performed even when distribution requests are concentrated from a plurality of types (function types) of functional unit card groups 111 to the common card 101 in an operational state. The common card 101 can distribute appropriate activation data corresponding to the function type to a plurality of types of function unit cards 111 by only transferring the function unit card 111 once.

(Contrast with existing transfer method)
FIG. 14 is a sequence diagram illustrating an example of activation data distribution using an existing transfer method. Assume that a reset has occurred in the function unit cards (# A-1, # A-2) while both the common card and the function unit cards (# A-1, # A-2) are in operation (step S1401). ). In this case, the functional unit cards (# A-1 and # A-2) are in a non-operational state, and the activation data is requested to be distributed to the common card 101.

  Also, when the common card is in operation and both of the function type cards (# B-1, # B-2) of the function type #B are newly installed (step S1404), these function unit cards ( # B-1 and # B-2) become non-operational and request activation data distribution to the common card.

  In the existing transfer method, the common card individually distributes activation data to each functional unit card (# A-1, # A-2, # B-1, # B-2) (step S1402, Step S1403, Step S1405, Step S1406).

  For this reason, the number of times the activation data is distributed to each functional unit card by the common card increases, the processing load of the common card in operation increases, and the ratio of distribution processing increases. In addition, startup data (non-operational communication packets) that are not directly related to the operation are transferred on the inter-card interface, and the transmission efficiency of the interface is reduced. As a result, there is a possibility that the operation processing (operation packet) of the base station apparatus may be hindered.

  In the example shown in FIG. 14, the common card transfers the activation data to the function unit card a total of four times. However, if the number of function unit cards increases, the number of transfers corresponding to the number of function units is required. In this regard, according to the embodiment, the activation data may be transferred to the functional unit card twice in the same state. Even if the number of functional unit cards increases, the transfer from the common card to the specific functional unit card may be performed twice, and the subsequent transfer processing is performed between the functional unit cards. Thereby, it is possible to reduce non-operational communication packets on the inter-card interface in the base station apparatus (suppressing factors that obstruct operation packets). In addition, the time and processing load required for the common card transfer process can be reduced.

  According to each embodiment described above, the startup data that has been redundantly held in a plurality of cards in the base station apparatus is managed by only one nonvolatile memory (for example, SSD) on the common card. . Since the activation data is distributed directly from the non-volatile memory on the common card to each functional unit card and each functional unit card is activated, the capacity of the non-volatile memory on each functional unit card in the base station apparatus is greatly increased. Can be reduced. Further, by reducing the nonvolatile memory, the size of the functional unit card can be reduced, and mounting can be easily performed at low cost.

  For example, the capacity of the entire nonvolatile memories 102 and 214 in the entire base station apparatus 100 can be reduced by several tens of percent. In addition, the rewriting time can be reduced to several tenths. For example, the startup data of 12800 KBytes is stored in the volatile memory (RAM) without using the nonvolatile memory (FLASH) 214 on the functional unit card 111 as in the embodiment (the startup data is Stored in the SSD 102). In this case, the FLASH memory takes about 190 sec (write processing is required after erase), whereas the SSD 102 only takes about a few seconds. Data read / write speed can be increased, and the functional unit card 111 can be activated at high speed.

  In addition, since activation data is distributed between cards in a non-operating state, processing resources can be effectively used without impeding the provision of communication services for cards in the operating state. As a result, the functional unit card can be added or restarted without impeding service provision during operation of the base station apparatus, and a flexible system can be realized.

  According to the base station apparatus of the embodiment, the distribution process of the activation data can be load-balanced in cooperation with the common card and the functional unit card without the activation data distribution process being loaded only on the common card. The power consumption of the functional unit card in the previous non-operating state can be reduced.

  The traffic processing amount of mobile communication is not always constant, and varies depending on, for example, the time of day. Therefore, it is possible to dynamically change the number of functional unit cards that change to the operating state in the base station device according to the situation, thereby reducing the power consumption of the base station device and smoothing the processing amount for each functional unit card. It is essential to realize. In this regard, according to the base station apparatus of the embodiment, it is possible to flexibly cope with an increase / decrease in the number of activation cards even in an operating state.

  In addition, by switching distribution data (software) according to the operation status, it is possible to operate the functional unit cards of the same hardware as different functional cards. That is, the function unit card can be configured by common hardware, and the function type of the function unit card can be switched by distributing activation data to a plurality of function unit cards.

  The following additional notes are disclosed with respect to the above-described embodiments.

(Supplementary note 1) A base station apparatus comprising a plurality of functional unit cards and a common card for holding activation data of the functional unit cards,
The common card is
A transfer list creating unit that creates a transfer list including destination information of each of the plurality of functional unit cards, which is distributed together with activation data for the plurality of functional unit cards;
A distribution control unit that distributes the activation data to which the transfer list is added to one functional unit card among the plurality of functional unit cards;
The functional unit card is
When the transfer list is acquired from the transferred activation data and destination information that is not excluded from the transfer list remains, any one of the plurality of function units cards shown in the transfer list Select the card as a transfer destination, update the transfer list so as to exclude the destination information of the functional card of the transfer destination from the transfer list, add the transfer list to the activation data, and the function of the transfer destination Transfer list processing unit to transfer to the copy card,
A base station apparatus comprising:

(Appendix 2) The common card is
A reception processing unit that receives a start-up data distribution request from the functional unit card;
The base station apparatus according to supplementary note 1, wherein the transfer list creating unit creates a transfer list including destination information of the functional unit card requested to be distributed.

(Appendix 3) The functional unit card is
A distribution request unit that transmits a distribution request for startup data in a non-operational state;
A reception processing unit that receives the activation data in a non-operating state from the common card or another functional unit card in response to the distribution request,
The base station apparatus according to appendix 1 or 2, wherein after the transfer process of transferring the received activation data to another functional unit card, the activation data is used to shift to an activation state.

(Appendix 4) The transfer list creation unit of the common card is
A plurality of pieces of destination information of the functional unit card requested to be distributed are arranged adjacent to the activation data on an address, and the beginning of the distribution order of the activation data is arranged at the end address farthest from the activation data And
Any one of appendices 1 to 3, wherein for each transfer of the activation data, a transfer list is created to exclude destination information of the functional card at the transfer destination arranged at the end address of the transfer list. Base station apparatus as described in one.

(Supplementary Note 5) The transfer list creation unit of the common card is
When receiving the activation data distribution request from a plurality of functional unit cards activated based on the activation data of the same function type, the predetermined one functional unit card sends the activation data to a plurality of functional unit cards. The base station apparatus according to any one of appendices 1 to 4, wherein the transfer list to be distributed is created.

(Appendix 6) The transfer list creation unit of the common card is
The base station apparatus according to appendix 5, wherein the destination information of a plurality of functional unit cards is set in one destination information of the transfer list.

(Appendix 7) The plurality of functional unit cards include a plurality of functional unit cards that are activated based on activation data of different function types,
The transfer list creation unit of the common card, when receiving activation data from each of the function unit cards of the different function types, generates a transfer list including destination information of each of the function unit cards of the different function types. make,
The distribution control unit adds a transfer list including destination information of each of the function unit cards of different function types to the activation data, and distributes to one function unit card among the plurality of function unit cards,
The reception processing unit of the functional unit card receives the activation data corresponding to the function type of the own device based on the transfer list of the transferred activation data,
The transfer list processing unit distributes the activation data corresponding to the function type of the own device to another function unit card of the same function type as the own device among the transferred activation data, and is different from the own device Distribute the activation data different from the function type of the own device to each of the other function unit cards of the function type,
In the distribution process, when there is remaining destination information that is not excluded in the transfer list for each function type, any one of the plurality of function unit cards shown in the transfer list Is selected as a transfer destination, the transfer list is updated so as to exclude the destination information of the transfer function card from the transfer list, and the transfer list is added to the activation data to add the transfer function unit. The base station apparatus according to any one of appendices 3 to 6, wherein the base station apparatus transfers to a card.

(Appendix 8) The functional unit card is
The base station apparatus according to any one of appendices 1 to 7, wherein the transferred activation data is held in a volatile memory.

(Supplementary Note 9) The distribution request unit of the functional unit card is
The base station apparatus according to any one of appendices 3 to 8, wherein the distribution request for the activation data to the common card is made again by a timeout of a distribution waiting time after the distribution request for the activation data.

(Supplementary Note 10) The distribution request unit of the functional unit card is
The base station apparatus according to any one of appendices 3 to 9, wherein the activation data distribution request is made when the functional unit card is reset and mounted on the base station apparatus.

100 Base station apparatus 101 Common card 102 Non-volatile memory (SSD)
111 Function Unit Card 121 Inter-Card Interface (SRIO)
131a, 141b Startup data 203, 213 PLD
204,214 Non-volatile memory (FLASH)
205,215 FPGA
206,216 MPU
207,217 Volatile memory (RAM)
301 Data Management Function Unit 301a SSD Control Unit 302 Distribution Server Function Unit 302a Distribution Request Acceptance Processing Unit 302b Activation Data Distribution Control Unit 302c Transfer List Creation Function Unit 303, 311 SRIO Function Unit 303a, 311a Reception Processing Unit 303b, 311b Transmission Processing Unit 312 Distribution client function unit 312a Distribution request transmission processing unit 312b Activation data reception processing unit 312c Transfer list processing function unit 400 Distribution data 401 (401a, 401b) Activation data 402 (402a-402c) Transfer list 421 (421a-421f) Destination information

Claims (8)

A base station device comprising a plurality of functional unit cards and a common card for holding activation data of the functional unit cards,
The common card is
A transfer list creating unit that creates a transfer list including destination information of each of the plurality of functional unit cards, which is distributed together with activation data for the plurality of functional unit cards;
A distribution control unit that distributes the activation data to which the transfer list is added to one functional unit card among the plurality of functional unit cards;
The functional unit card is
When the transfer list is acquired from the transferred activation data and destination information that is not excluded from the transfer list remains, any one of the plurality of function units cards shown in the transfer list Select the card as a transfer destination, update the transfer list so as to exclude the destination information of the functional card of the transfer destination from the transfer list, add the transfer list to the activation data, and the function of the transfer destination Transfer list processing unit to transfer to the copy card,
A base station apparatus comprising: The common card is
A reception processing unit that receives a start-up data distribution request from the functional unit card;
The base station apparatus according to claim 1, wherein the transfer list creating unit creates a transfer list including destination information of the functional unit card requested to be distributed. The functional unit card is
A distribution request unit that transmits a distribution request for startup data in a non-operational state;
A reception processing unit that receives the activation data in a non-operating state from the common card or another functional unit card in response to the distribution request,
The base station apparatus according to claim 1, wherein after the transfer process of transferring the received activation data to another functional unit card, the activation data is used to shift to an activation state. The transfer list creation unit of the common card is
A plurality of pieces of destination information of the functional unit card requested to be distributed are arranged adjacent to the activation data on an address, and the beginning of the distribution order of the activation data is arranged at the end address farthest from the activation data And
4. A transfer list that excludes destination information of the functional card of the transfer destination arranged at the last address of the transfer list is created for each transfer of the activation data. The base station apparatus as described in one. The transfer list creation unit of the common card is
When receiving the activation data distribution request from a plurality of functional unit cards activated based on the activation data of the same function type, the predetermined one functional unit card sends the activation data to a plurality of functional unit cards. The base station apparatus according to claim 1, wherein the transfer list to be distributed is created. The transfer list creation unit of the common card is
The base station apparatus according to claim 5, wherein destination information of a plurality of functional unit cards is set in one destination information of the transfer list. The plurality of functional unit cards include a plurality of functional unit cards that are activated based on activation data of different function types,
The transfer list creation unit of the common card, when receiving activation data from each of the function unit cards of the different function types, generates a transfer list including destination information of each of the function unit cards of the different function types. make,
The distribution control unit adds a transfer list including destination information of each of the function unit cards of different function types to the activation data, and distributes to one function unit card among the plurality of function unit cards,
The reception processing unit of the functional unit card receives the activation data corresponding to the function type of the own device based on the transfer list of the transferred activation data,
The transfer list processing unit distributes the activation data corresponding to the function type of the own device to another function unit card of the same function type as the own device among the transferred activation data, and is different from the own device Distribute the activation data different from the function type of the own device to each of the other function unit cards of the function type,
In the distribution process, when there is remaining destination information that is not excluded in the transfer list for each function type, any one of the plurality of function unit cards shown in the transfer list Is selected as a transfer destination, the transfer list is updated so as to exclude the destination information of the transfer function card from the transfer list, and the transfer list is added to the activation data to add the transfer function unit. The base station apparatus according to claim 3, wherein the base station apparatus transfers to a card. The functional unit card is
The base station apparatus according to claim 1, wherein the transferred activation data is held in a volatile memory.

Images