JP5245866B2 - Management apparatus and management method - Google Patents

Description

  The present invention relates to a management device that manages common data that is commonly used in a plurality of terminal devices, and a management method thereof, and more particularly to a management device that can shorten the access time of a terminal device and a management method thereof. is there.

  2. Description of the Related Art Conventionally, a system composed of a management device that stores system common data and an expandable individual device group that acquires the common data stored in the management device and executes various types of processing is various fields (for example, Mobile phone base stations). FIG. 12 is a block diagram showing a configuration of a conventional system.

  As shown in FIG. 12, in the conventional system, individual devices 10 to 30 are connected to a management device 50 that stores common data a, b, and c (here, for convenience of explanation, the individual devices 10 to 30 are connected). As shown, this system also includes other individual devices). The common data a, b, and c are logically composed of one memory, and the management device 50 serially executes processing for an access that is a common data read request.

  Each of the individual devices 10 to 30 includes a card that acquires common data and executes predetermined processing. Specifically, the individual device 10 includes cards 10a to 10c, the individual device 20 includes cards 20a and 20b, and the individual device 30 includes cards 30a and 30c. Here, for example, the cards 10a, 20a, and 30a perform processing using the common data “a”, the cards 10b and 20b perform processing using the common data “b”, and the cards 10c and 30c are common. It is assumed that processing is performed using the data “c”.

  In the above-described system, when the management device 50 receives access from the individual devices 10 to 30 and transfers common data when the system is started (or restarted), the management device 50 performs serial processing. Execute. For example, the management device 50 first transfers the common data a, b, c to the individual device 10, then transfers the common data a, b to the individual device 20, and finally the common data a, c to the individual device 30. Forward. After the common data a and c are transferred to the individual device 30, the system starts up.

  Patent Document 1 includes a plurality of memories having the same logical address space for storing common data taught to each other by a plurality of information processing means, and writing occurs in any one of the memories In addition, a technique for simplifying access to common data by rewriting data in another memory corresponding to the written data to the same content is disclosed.

JP-A-6-259316

  However, in the above-described conventional technology, when access is simultaneously generated from the individual device group at the time of starting (or restarting) the system, the response to the access request is processed sequentially as described above. There was a problem that waiting time occurred.

  FIG. 13 is a diagram (1) showing a timing image according to a conventional system. As shown in the figure, when the individual devices 10 to 30 access the management device 50 at the same time, for example, the common data is transferred in the order of the individual devices 10, 20, and 30 (sequentially processed). For this reason, waiting occurs in the individual devices 20 and 30, and the system startup time is greatly delayed.

  Note that even if access adjustment is performed on the individual device 10 to 30 side in order to shorten the waiting time, the access time for each individual device does not decrease, so it is necessary for the individual device to acquire common data. The time cannot be shortened.

  FIG. 14 is a diagram (2) showing a timing image according to the conventional system. In the example shown in the figure, access adjustment is performed and the management apparatus 50 is accessed in the order of the individual apparatuses 10, 20, and 30 to acquire common data. However, as compared with FIG. It takes the same time to acquire, and the system startup time cannot be shortened.

  On the other hand, measures such as providing a cache on the management device side to shorten the access time have been taken, but since the response processing for access requests is serial, the access time increases as the number of connections of individual devices increases. The current situation is that sufficient shortening cannot be performed because of the addition.

  The present invention has been made to solve the above-described problems caused by the prior art, and an object of the present invention is to provide a management apparatus and a management method capable of reducing the access time for common data.

  In order to solve the above-described problems and achieve the object, this management device is a management device that manages common data that is commonly used in a plurality of terminal devices, and divides the common data into types. A common data storage means for storing; a management means for managing the access request and the type of the common data in association with each other when an access request for the common data is received from the plurality of terminal devices; It is a requirement that a plurality of terminal devices that are transmission sources of access requests associated with types include transmission means for collectively transmitting common data of the corresponding types.

  In addition, the management apparatus is characterized in that, in the management apparatus, the transmission unit transmits the common data based on an order in which the access requests are received from the terminal device.

  Further, in the above management apparatus, when the priority is set in the access request transmitted from the terminal device, the transmission unit transmits the common data based on the priority. It is a requirement to determine the order in which to perform.

  In addition, the management device receives the access request from another terminal device while the transmission unit collectively transmits common data of a type corresponding to a plurality of terminal devices. In this case, it is a requirement that after the common data is transmitted with the other terminal device added to the transmission destination, a retransmission means is further provided for retransmitting the insufficient common data to the other terminal device.

  Further, in this management apparatus, in the above management apparatus, when the retransmission means retransmits untransmitted common data to a plurality of terminal apparatuses, the amount of data among the common data to be retransmitted is maximized. The requirement is to retransmit the common data to a plurality of terminal devices.

  In addition, this management method is a management method for managing common data that is commonly used in a plurality of terminal devices, and the management device divides the common data by type into a storage device. A common data storage step for storing, a management step for managing the access request and the type of the common data in association with each other when an access request for the common data is received from the plurality of terminal devices; It is a requirement to include a transmission step of collectively transmitting common data of a corresponding type to a plurality of terminal devices that are transmission sources of access requests associated with the type.

  Further, in this management method, in the management method described above, when a priority is set in an access request transmitted from the terminal device, the transmission step transmits the common data based on the priority. It is a requirement to determine the order in which to perform.

  According to this management apparatus, common data that is commonly used in the system is divided and stored for each type, and when an access request for common data is received from a plurality of terminal apparatuses, the received access request and the common data are stored. Are managed in association with each other, and the corresponding types of common data are transmitted collectively to a plurality of terminal devices that are the transmission source of access requests associated with the common data types (multicast transfer) Therefore, even when an access request is received from a plurality of terminal devices at the time of system startup or the like, common data can be transmitted efficiently and the access time of each terminal device can be shortened.

  Also, according to this management device, since common data is transmitted based on the order in which access requests are received from the terminal device, an access response in accordance with the request on the system side in response to the different access requests from the terminal device Can be returned.

  Further, according to this management device, when priority is set for an access request transmitted from a terminal device, the order in which the common data is transmitted is determined based on the priority. In response to various access requests, an access response according to the request from the system side can be returned.

  Further, according to this management device, when an access request is received from another terminal device while the common data of the type corresponding to the terminal device is being transmitted in a batch, Then, after transmitting the common data from the middle, the untransmitted common data is retransmitted to another terminal device, so that the data transfer time when there is a terminal device that makes an access request with a delay can be shortened.

  Further, according to this management apparatus, when retransmitting common data that has not been transmitted to a plurality of terminal apparatuses, among the common data to be retransmitted, the common data having the maximum data amount is retransmitted to the plurality of terminal apparatuses. Therefore, even when access requests by a plurality of terminal devices are delayed, data transfer can be completed by one retransmission.

FIG. 1 is a diagram illustrating the configuration of the system according to the first embodiment. FIG. 2 is a functional block diagram of the configuration of the management apparatus according to the first embodiment. FIG. 3 is a diagram illustrating an example of a data structure of common data stored in the common data storage unit. FIG. 4 is a diagram illustrating an example of the data structure of the multicast group ID buffer. FIG. 5 is a diagram illustrating an example of the data structure of the management table held by the access content determination unit. FIG. 6 is a diagram illustrating an example of the data structure of the processing wait FIFO. FIG. 7 is a diagram for explaining data changes in the multicast group ID buffer. FIG. 8 is a flowchart (1) illustrating the processing procedure of the management apparatus according to the first embodiment. FIG. 9 is a flowchart (2) illustrating the processing procedure of the management apparatus according to the first embodiment. FIG. 10A is a diagram of a timing image according to the system of the first embodiment. FIG. 10-2 is a diagram for explaining a specific effect in the first embodiment. FIG. 11 is a diagram illustrating a hardware configuration of a computer that configures the management apparatus according to the embodiment. FIG. 12 is a block diagram showing a configuration of a conventional system. FIG. 13 is a diagram (1) showing a timing image according to a conventional system. FIG. 14 is a diagram (2) showing a timing image according to the conventional system. FIG. 15 is a diagram for explaining the effect of the second embodiment. FIG. 16 is a diagram illustrating the configuration of the system according to the second embodiment. FIG. 17 is a diagram illustrating the configuration of the management apparatus according to the second embodiment. FIG. 18 is a diagram illustrating an example of the data structure of the multicast group ID buffer according to the second embodiment. FIG. 19 is a diagram illustrating an example of the data structure of the transfer management table. FIG. 20 is a diagram for explaining the data change in the multicast group ID buffer according to the second embodiment. FIG. 21 is a flowchart (1) illustrating the processing procedure of the management apparatus according to the second embodiment. FIG. 22 is a flowchart (2) illustrating the processing procedure of the management apparatus according to the second embodiment. FIG. 23 is a diagram for explaining a difference in transfer time between the first and second embodiments. FIG. 24 is a diagram illustrating an example of a data structure of a multicast group ID buffer when access requests are delayed from a plurality of individual apparatuses.

  Embodiments of a management apparatus and a management method disclosed in the present application will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  First, an outline of the management apparatus according to the first embodiment will be described. The management apparatus according to the first embodiment stores common data that is commonly used in the system by dividing the data for each type, and receives an access request received when an access request for the common data is received from a plurality of individual apparatuses. And the type of common data are managed in association with each other, and the corresponding type of common data is collectively transmitted to a plurality of individual devices that are transmission sources of access requests associated with the type of common data ( Multicast transmission).

  As described above, the management apparatus according to the first embodiment manages the access request and the common data type in association with each other, and manages the plurality of individual apparatuses serving as the transmission source of the access request associated with the common data type. On the other hand, because the common type of common data is sent in a lump, even when an access request is received from a plurality of individual devices at the time of starting the system, the common data can be sent efficiently. The access time of the individual device can be shortened.

  Next, the configuration of the system according to the first embodiment will be described. FIG. 1 is a diagram illustrating the configuration of the system according to the first embodiment. As shown in the figure, in this system, individual devices 60 to 80 are connected to a management device 100 that stores common data. Here, for convenience of explanation, only the individual devices 60 to 80 are shown, but this system also includes other individual devices.

  Each of the individual devices 60 to 80 includes a card that acquires common data and executes predetermined processing. Specifically, the individual device 60 includes cards 60a to 60c, the individual device 70 includes cards 70a and 70b, and the individual device 80 includes cards 80a and 80c.

  Here, for example, the cards 60a, 70a, and 80a perform processing using the common data “a”, the cards 60b and 70b perform processing using the common data “b”, and the cards 60c and 80c are common. It is assumed that a predetermined process is performed using the data “c”.

  The individual devices 60 to 80 transmit an access request for acquiring common data to the management device 100 when the system is started (or restarted). When the common data corresponding to the access request is acquired from the management apparatus 100, the acquired common data is output to the corresponding card, and each card executes a predetermined process.

  In the access request transmitted from the individual devices 60 to 80 to the management device, individual device identification information for identifying the individual device, access request identification information (the description of the access request identification information will be described later), and if necessary, It is assumed that priority information (for example, priority setting ON / OFF and priority information) indicating the priority of the access request is included.

  In this embodiment, as an example, the priority information is indicated by numerical values “1, 2, 3,...”, And the smaller the numerical value is, the higher the priority is the access request. The administrator of each of the individual devices 60 to 80 sets in advance whether or not to include priority information in the access request, and sets the value of the priority information in advance when including the priority information. Shall.

  The management apparatus 100 divides and stores common data used in common in the system for each type, and when receiving an access request for common data from a plurality of individual apparatuses, the received access request and the type of common data Are managed in association with each other, and multicast data of the corresponding type of common data is transmitted to a plurality of individual devices that are transmission sources of access requests associated with the type of common data.

  FIG. 2 is a functional block diagram of the configuration of the management apparatus 100 according to the first embodiment. As shown in the figure, this management device 100 is common to a common data storage unit 110, a multicast group ID buffer 120, an individual device group IF unit 130, an access content determination unit 140, and a processing wait FIFO 150. And a data management unit 160.

  The common data storage unit 110 is a storage unit that divides and stores common data for each type. FIG. 3 is a diagram illustrating an example of a data structure of common data stored in the common data storage unit 110. As shown in the figure, common data is divided and stored in common data “a”, “b”, and “c”, and each common data is associated with a multicast group ID.

  Specifically, the common data “a” is associated with the multicast group ID “A”, the common data “b” is associated with the multicast group ID “B”, and the common data “c” is associated with the multicast group ID “C”. "Is associated. Here, the multicast group ID is information for identifying a set of individual devices to be multicast-transferred when corresponding common data is multicast-transferred.

  The multicast group ID buffer 120 is storage means for storing access request identification information in association with each multicast group ID. FIG. 4 is a diagram illustrating an example of the data structure of the multicast group ID buffer 120.

  As shown in FIG. 4, the multicast group ID buffer 120 includes a buffer 120a corresponding to the multicast group ID “A”, a buffer 120b corresponding to the multicast group ID “B”, and a buffer corresponding to the multicast group ID “C”. 120c, and each of the buffers 120a to 120c stores access request identification information corresponding to each multi-group ID.

  In the example shown in FIG. 4, the buffer 120a stores access request identification information “x, v, s”, the buffer 120b stores access request identification information “y, w”, and the buffer 120c stores access request identification information. Information “t, z” is stored. The access request identification information of each of the buffers 120a to 120c is registered by the access content determination unit 140 described later.

  Here, the access request identification information “x” is information for identifying an access request for the card 60a, and the access request identification information “y” is information for identifying an access request for the card 60b. “z” is information for identifying an access request of the card 60c.

  The access request identification information “v” is information for identifying an access request for the card 70a, and the access request identification information “w” is information for identifying an access request for the card 70b. The access request identification information “s” is information for identifying an access request for the card 80a, and the access request identification information “t” is information for identifying an access request for the card 80c.

  In the example illustrated in FIG. 4, the multicast group ID is directed toward the individual devices 60 to 80 having the cards 60 a, 70 a, and 80 a corresponding to the access request identification information “x, v, s” stored in the buffer 120 a. The common data “a” (see FIG. 3) corresponding to “A” is multicasted.

  Further, the common data “b” corresponding to the multicast group ID “B” is directed toward the individual devices 60 and 70 having the cards 60 b and 70 b corresponding to the access request identification information “y, w” stored in the buffer 120 b. (See FIG. 3) is multicasted.

  Further, the common data “c” corresponding to the multi-group ID “C” is directed toward the individual devices 60 and 80 including the cards 60 c and 80 c corresponding to the access request identification information “t, z” stored in the buffer 120 c. (See FIG. 3) is multicasted.

  Returning to the description of FIG. 2, the individual device group IF unit 130 is a unit that mainly controls communication with the individual devices 60 to 80.

  When the access request is acquired from the individual devices 60 to 80, the access content determination unit 140 registers access request identification information in the multicast group ID buffer 120 and registers a request corresponding to the access request in the processing wait FIFO 150. It is means to do. In the following, after describing the process of registering access request identification information in the multicast group ID buffer 120 by the access content determination unit 140, the process of registering a request in the processing wait FIFO 150 will be described.

  First, a process for registering access request identification information in the multicast group ID buffer 120 will be described. The access content determination unit 140 holds a management table, and compares the management table with the individual device identification information and the access request identification information included in the access request when the access request is acquired from the individual devices 60 to 80. By doing so, the access request identification information registered in each of the buffers 120a to 120c of the multicast group ID buffer 120 is identified and registered.

  FIG. 5 is a diagram illustrating an example of the data structure of the management table held by the access content determination unit 140. As shown in the figure, this management table stores individual device identification information, access request identification information, and a multicast group ID in association with each other.

  Specifically, the individual device identification information “k1001” corresponds to the access request identification information “x”, “y”, “z”, and the access request identification information “x” corresponds to the multicast group ID “A”. Correspondingly, the access request identification information “y” corresponds to the multicast group ID “B”, and the access request identification information “z” corresponds to the multicast group ID “C”.

  The individual device identification information “k1002” corresponds to the access request identification information “v” and “w”, and the access request identification information “v” corresponds to the multicast group ID “A”, and the access request identification The information “w” corresponds to the multicast group ID “B”.

  The individual device identification information “k1003” corresponds to the access request identification information “s” and “t”, and the access request identification information “s” corresponds to the multicast group ID “A”, and the access request identification information The information “t” corresponds to the multicast group ID “C”.

  For example, when the access content determination unit 140 acquires an access request including the individual device identification information “k1001” and the access request identification information “x” from the individual device 60, the access content determination unit 140 corresponds to the multicast group ID “A”. Therefore, the access request identification information “x” is registered in the buffer 120a.

  Next, processing in which the access content determination unit 140 registers a request in the processing wait FIFO 150 will be described. Further, this process will be described separately for “when the priority information is not included in the access request” and “when the priority information is included in the access request”. The access content determination unit 140 determines whether priority is set based on the header information of the access request.

(When the priority information is not included in the access request)
When the access content determination unit 140 acquires an access request from the individual devices 60 to 80 and the acquired access request does not include priority information, the priority flag of the processing wait FIFO 150 is set to “off”. To do.

  Then, the access content determination unit 140 creates a request corresponding to the access request based on the individual device identification information included in the access request and the management data (see FIG. 5). As shown in FIG. 3, when there are three types of multicast group IDs (common data), there are also three types of requests.

  In the first embodiment, as an example, a request corresponding to the multicast group ID “A” (common data “a”) is “request A”, and a request corresponding to the multicast group ID “B” (common data “b”) is “ A request corresponding to request B ”and multicast group ID“ C ”(common data“ c ”) is referred to as“ request C ”.

  When the access content determination unit 140 acquires an access request from the individual devices 60 to 80, the access content determination unit 140 compares the individual device identification information and the access request identification information included in the access request with the management data and creates a request. . For example, when the access content determination unit 140 acquires an access request having the individual device identification information “k1001” and the access request identification information “x”, the access content determination unit 140 corresponds to the multicast group ID “A”, and thus creates the request A. To do.

  The access content determination unit 140 registers the requests in the processing wait FIFO 150 in the order in which the requests are created. In addition, when registering a request, the access content determination unit 140 does not register a request if the same request is already registered in the processing wait FIFO 150.

  For example, when the request A is registered in the processing-waiting FIFO 150 when the request A is registered in the processing-waiting FIFO 150, the request A is not newly registered.

(When access request includes priority information)
When the access content determination unit 140 acquires an access request from the individual devices 60 to 80 and the acquired access request includes priority information, the priority flag of the processing wait FIFO 150 is set to “on”. To do.

  Then, the access content determination unit 140 generates a request corresponding to the access request and associates the generated request with the priority information in the same manner as in the case where the access request does not include priority information. The request is registered in the processing wait FIFO 150.

  The access content determination unit 140 may register the requests in the processing-waiting FIFO 150 in order from the request with the highest priority based on the priority information associated with the request. In addition, when registering the request A in the processing-waiting FIFO 150, the access content determination unit 140 does not newly register the request A if the request A is already registered in the processing-waiting FIFO 150.

  The access content determination unit 140 holds the system configuration information shown in FIG. 1 and manages the number of individual devices connected to the management device 100. Accordingly, by counting the types and number of requests from the individual devices 60 to 80, it is determined whether or not the access from the individual devices 60 to 80 has been completed. The individual devices 60 to 80 output the determination result to the common data management unit 160.

  The processing wait FIFO 150 is a storage unit (FIFO) that stores a request registered by the access content determination unit 140. FIG. 6 is a diagram illustrating an example of a data structure of the processing wait FIFO 150.

  As shown in the figure, this processing-waiting FIFO 150 stores a request ID for identifying a request and priority information in association with each other. When priority information is not associated with a request, priority information corresponding to the request is blank.

  The processing waiting FIFO 150 has a priority flag (not shown), and when the priority flag is “ON”, the common data management unit 160 in order from the request with the highest priority. Read out. On the other hand, when the priority flag is “off”, the requests are registered in order from the previously registered request.

  After acquiring the access completion notification from the access content determination unit 140, the common data management unit 160 acquires a request from the processing wait FIFO 150, reads the common data corresponding to the request from the common data storage unit 110, and Based on information stored in the ID buffer 120, the common data is multicast-transferred.

  Hereinafter, processing of the common data management unit 160 will be described. The processing of the common data management unit 160 is roughly divided into processing for reading common data from the common data storage unit 110 and processing for multicast transfer of common data. First, processing for reading common data from the common data storage unit 110 is performed. After the description, a process for multicast transfer of common data will be described.

  A process in which the common data management unit 160 reads the common data from the common data storage unit 110 will be described. The common data management unit 160 refers to the priority flag of the processing-waiting FIFO 150, and when the priority flag is “off”, obtains the request in order from the request previously registered in the processing-waiting FIFO 150.

  On the other hand, when the priority flag is “ON”, the requests registered in the processing wait FIFO 150 are acquired in order from the request with the highest priority. For example, when the priority information is set as shown in FIG. 6, requests are acquired from the processing wait FIFO 150 in the order of requests A, B, and C.

  Then, the acquired request is compared with the common data (see FIG. 3) stored in the common data storage unit 110, and the common data corresponding to the request is acquired from the common data storage unit 110. The requests A to C correspond to the multicast groups IDA to C, respectively. Therefore, the common data management unit 160 reads the common data “a” when acquiring the request A, reads the common data “b” when acquiring the request B, and acquires the request C. Reads the common data “c”.

  Next, a process in which the common data management unit 160 multicasts the common data will be described. When the common data management unit 160 acquires the common data, the common data management unit 160 refers to the buffer (any one of the buffers 120a to 120c) corresponding to the multicast group ID of the acquired common data, and the access request included in the referred buffer Based on the identification information, the common data is multicast-transferred to the corresponding individual device.

  Specifically, when the common data management unit 160 acquires the common data “a”, the buffer 120 a corresponding to the multicast group ID “A” is referred to. Then, the common data management unit 160 transmits the common data “a” to the individual devices 60 to 80 (for example, see FIG. 5) corresponding to the access request identification information “x, v, s” included in the buffer 120a. Multicast transfer.

  The common data management unit 160 deletes the access request identification information stored in the buffer 120a after multicast transmission of the common data “a”.

  Further, when the common data management unit 160 acquires the common data “b”, the buffer 120 b corresponding to the multicast group ID “B” is referred to. Then, the common data management unit 160 multicasts the common data “b” to the individual devices 60 and 70 (for example, see FIG. 5) corresponding to the access request identification information “y, w” included in the buffer 120b. To do.

  The common data management unit 160 deletes the access request identification information stored in the buffer 120b after multicast transfer of the common data “b”.

  When the common data management unit 160 acquires the common data “c”, the buffer 120 c corresponding to the multicast group ID “C” is referred to. Then, the common data management unit 160 multicasts the common data “c” to the individual devices 60 and 80 (for example, see FIG. 5) corresponding to the access request identification information “t, z” included in the buffer 120c. To do.

  The common data management unit 160 deletes the access request identification information stored in the buffer 120c after multicast transfer of the common data “c”. It is assumed that the common data management unit 160 holds individual devices corresponding to the access request identification information, destination information of each individual device, and the like.

  Next, the multicast group ID buffer 120 that changes with the processing of the access content determination unit 140 and the common data management unit 160 will be described. FIG. 7 is a diagram for explaining data changes in the multicast group ID buffer 120.

  When acquiring an access request from the individual devices 60 to 80, the access content determination unit 140 first registers the access request identification information “x, v, s” in the buffer 120a (see the first row in FIG. 7). Subsequently, the access request identification information “y, w” is registered in the buffer 120b, and the access request identification information “t” is registered in the buffer 120c (see the second row in FIG. 7). Thereafter, the access request identification information “z” is registered in the buffer 120c (see the third row in FIG. 7).

  Further, after the common data management unit 160 multicasts the common data “a”, the access request identification information “x, v, s” stored in the buffer 120a is deleted (see the fourth row in FIG. 7). After multicast transfer of the common data “b”, the access request identification information “y, w” stored in the buffer 120b is deleted (see the fifth row in FIG. 7), and after the common data “c” is multicast transferred, The access request identification information “t, z” stored in the buffer 120c is deleted (see the sixth row in FIG. 7).

  Next, a processing procedure of the management apparatus 100 according to the first embodiment will be described. FIGS. 8 and 9 are flowcharts illustrating the processing procedure of the management apparatus 100 according to the first embodiment. As shown in the figure, in the management apparatus 100, the access content determination unit 140 receives an access request from each individual apparatus 60 to 80 (step S101), determines an access destination, and identifies a corresponding multicast group ID ( Step S102).

  Then, the access content determination unit 140 stores the access request identification information in the multicast group ID buffer 120 (step S103), and determines whether priority information is set for the access request (step S104).

  If priority information is not set in the access request (No in step S105), it is determined whether or not the first request (the same request as the request to be registered; the same applies hereinafter) exists in the processing wait FIFO 150. If there is a first-arrival request (step S107, Yes), the process proceeds to step S113.

  On the other hand, if there is no first-arrival request (step S107, No), the request is stored in the processing-waiting FIFO 150, the priority flag of the processing-waiting FIFO 150 is set to off (step S108), and the process proceeds to step S113. To do.

  By the way, when priority information is set in the access request in step S105 (step S105, Yes), it is determined whether there is a first request in the processing waiting FIFO 150 (step S109). If no request exists (step S110, No), the request is stored in the processing-waiting FIFO 150, the priority flag of the processing-waiting FIFO 150 is set to ON (step S111), and the process proceeds to step S113.

  On the other hand, if there is a first-arrival request (step S110, Yes), the priority flag of the processing wait FIFO 150 is set to on (step S112), and it is determined whether or not reception of the access request has been completed (step S112). If the reception of the access request has not been completed (step S113), the process proceeds to step S102.

  On the other hand, when reception of the access request is completed (step S114, Yes), it is determined whether or not the priority flag of the processing wait FIFO 150 is turned on (step S115), and the priority flag is turned on. If yes (step S116, Yes), based on the priority information, the request is read from the processing wait FIFO 150 (step S117), and the common data is multicast to the corresponding individual device (step S118).

  Then, it is determined whether or not the reading of the processing-waiting FIFO 150 is completed (step S119). If the reading is not completed (step S120, No), the process proceeds to step S117. On the other hand, when the reading is completed (step S120, Yes), the process is terminated.

  By the way, when the priority flag of the processing wait FIFO 150 is turned off in step S116 (step S116, No), the requests stored in the processing wait FIFO 150 are read in order (step S121). Multicast common data to individual devices (step S122).

  Then, it is determined whether or not the reading of the processing wait FIFO 150 is completed (step S123). If the reading is not completed (No in step S124), the process proceeds to step S121. On the other hand, if the reading has been completed (step S124, Yes), the process is terminated.

  FIG. 10A is a diagram of a timing image according to the system of the first embodiment. As shown in the figure, even when the individual devices 60 to 80 request access to the management device 100 at the same time, the management device 100 multicasts the common data, so the waiting time of the individual devices 60 to 80 is eliminated. It becomes possible to start up the system quickly.

  Here, specific effects in the first embodiment will be described numerically. FIG. 10-2 is a diagram for explaining a specific effect in the first embodiment. As preconditions, there are individual devices 60, 70, 80. The individual device 60 is equipped with cards 10a, 10b, 10c, the individual device 70 is equipped with cards 20a, 20b, and the individual device 80 is equipped with cards 30a, 30c. To do.

  In addition, the size of the common data of the system is 120 MByte. There are three card types, and 40 MByte (120 MByte ÷ 3) data is used for each type of card. The access speed to the system common data is 16 MByte. A compact flash (registered trademark) is assumed as a memory for storing a common system.

  Further, the path access speed between the management apparatus 100 and the individual apparatuses 60 to 80 is set to 160 Mbytes. Assume a serial bus (SERDES) with a clock of 100 MHz and a data width of 16 bits. Since the access request packet size is small, transfer time cannot be entered.

Based on the above preconditions, the time required for the data transfer process for one type of card is calculated.
The data read time for one type of card from the system common data is
40Mbyte ÷ 16Mbyte / sec = 2.5sec
It becomes. The data transfer time between the management device 100 and the individual devices 60 to 80 is
40Mbyte ÷ 160Mbps = 40Mbyte ÷ 20Mbps / sec = 2.0sec
It becomes.

  Next, the time required for all data transfer in the conventional configuration is calculated. Since all the management devices perform transfer processing by serial processing, each transfer processing time is added. That is, the transfer time according to the conventional configuration is a time obtained by adding the transfer times of the individual devices 60 to 80, respectively.

Since the individual device 60 includes the cards 10a to 10c, the data read time is 2.5 sec × 3. Since the individual device 70 includes the cards 20a and 20b, the data read time is 2.5 sec × 2. Since the individual device 80 includes the cards 30a and 30c, the data read time is 2.5 sec × 2. Therefore, the transfer time according to the conventional configuration is a value obtained by adding the data transfer time 2.0 sec to the above-described data read time.
2.5sec × 7 + 2.0sec = 19.5sec
(Refer to the upper part of FIG. 10-2).

On the other hand, in the first embodiment, the transfer time for the card type is sufficient regardless of the number of individual devices connected. That is, the transfer time according to the first embodiment is obtained by adding the data read time of the common data “a”, the data read time of the common data “b”, the data read time of the common data “c”, and the data transfer time. So that
2.5sec × 3 + 2.0sec = 10sec
(Refer to the lower part of FIG. 10-2).

  As shown in FIG. 10-2, when the transfer time according to the conventional configuration is compared with the transfer time according to the first embodiment, the transfer time according to the first embodiment is shortened by 10 seconds, so the data transfer time is shortened. be able to.

  As described above, in the management apparatus 100 according to the first embodiment, the common data storage unit 110 divides and stores common data that is commonly used in the system for each type, and there are a plurality of access content determination units 140. When the access request for the common data is received from each individual device, the received access request identification information and the multicast group ID are associated with each other and registered in the multicast group ID buffer 120, and the common data management unit 160 Since the common data of the corresponding type is multicast-transferred to the plurality of individual devices that are the transmission source of the access request associated with the type, the access request is accepted from the plurality of individual devices 60 to 80 at the time of starting the system. Even in the case of data transfer, common data can be transmitted efficiently, and the It is possible to shorten the time Seth.

  Further, since the management apparatus 100 according to the first embodiment groups and manages access to the same common data, even if the number of access requests to the same common data increases (individual devices are added and access is increased). Even if the number of requests increases), an increase in access time can be prevented.

  In the first embodiment, since the management apparatus 100 prevents an increase in the access time of each individual apparatus, it is not necessary to perform a special process between the individual apparatuses. It can be reduced.

  In addition, since the management apparatus 100 according to the first embodiment registers the transfer destination in the multicast group ID buffer 120 and executes multicast transfer, the transfer preparation processing load can be reduced.

  In addition, the management apparatus 100 according to the first embodiment stores the request in the processing waiting FIFO 150, and the common data management unit 160 reads the request according to the previously registered request order or priority information, Since data is transmitted, it is possible to return an access response according to a request on the system side in response to a separate access request from an individual device.

  By the way, among the processes described in the first embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed. All or a part of the above can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  Further, each component of the management apparatus 100 shown in FIG. 2 is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. Furthermore, each processing function performed by each device may be realized by a CPU and a program that is analyzed and executed by the CPU, or may be realized as hardware by wired logic.

  FIG. 11 is a diagram illustrating a hardware configuration of the computer 200 configuring the management apparatus 100 according to the embodiment. As shown in FIG. 11, the computer (management apparatus) 200 includes an input device 201, a monitor 202, a multicast group ID buffer 203 (corresponding to the multicast group ID buffer 120 shown in FIG. 2), and a process waiting queue. A FIFO 204 (corresponding to the processing wait FIFO 150 shown in FIG. 2), a RAM (Random Access Memory) 205, a ROM (Read Only Memory) 206, a medium reading device 207 for reading data from a storage medium, and other devices (for example, A communication device 208 that transmits and receives data to and from the individual devices 60 to 80), a CPU (Central Processing Unit) 209, and an HDD (Hard Disk Drive) 210 are connected by a bus 211.

  The HDD 210 stores a management program 210b that exhibits the same functions as the functions of the management apparatus 100 described above. The management process 209a is started when the CPU 209 reads and executes the management program 210b. Here, the management process 209a corresponds to the access content determination unit 140 and the common data management unit 160 illustrated in FIG.

  The HDD 210 stores common data 210a. The CPU 209 reads the common data 210 a stored in the HDD 210, stores it in the RAM 205, and executes multicast transfer using the common data 205 a stored in the RAM 205.

  By the way, the management program 210b shown in FIG. 11 is not necessarily stored in the HDD 210 from the beginning. For example, a “portable physical medium” such as a flexible disk (FD), a CD-ROM, a DVD disk, a magneto-optical disk, or an IC card inserted into a computer, or a hard disk drive (HDD) provided inside or outside the computer. The management program 210b is stored in the “fixed physical medium” of the computer, and “another computer (or server)” connected to the computer via a public line, the Internet, a LAN, a WAN, or the like. However, the management program 210b may be read from these and executed.

  Next, a management apparatus according to the second embodiment will be described. When the management apparatus according to the second embodiment receives an access request from another individual apparatus while collectively transmitting data of a type corresponding to a plurality of individual apparatuses, After the common data is transmitted from the middle, the untransmitted common data is retransmitted to another terminal device.

  FIG. 15 is a diagram for explaining the effect of the second embodiment. Here, as an example, a case will be described in which the individual apparatuses 60 and 70 transmit an access request for the common data “a” and then the individual apparatus 80 transmits an access request for the common data “a”. If a time difference due to reset release timing or the like exists in the individual devices 60 to 80, the timing at which each individual device 60 to 80 transmits an access request for the common data “a” to the management device is shifted.

  As shown in the lower part of FIG. 15, in the second embodiment, when an access request for common data is received from the individual devices 60 and 70, the management device is ready for multicast transfer of the common data “a”. Multicast transfer of the common data “a” is started to the individual devices 60 and 70. The multicast transfer of the common data “a” is started even when an access request from the individual device 80 is not accepted. It should be noted that the management device manages how far the data has been transferred among all the data of the common data “a” by multicast transfer.

  When the management device receives an access request for the common data “a” from the individual device 80 during the execution of the multicast transfer, the management device adds the individual device 80 to the transfer destination, and the individual devices 60 to 80. The common data “a” is continuously transferred to. That is, the individual device 80 acquires the common data “a” from the middle. Then, after the multicast transfer is completed once and the preparation for transferring the common data “a” is completed, the management device transfers only the shortage of the common data “a” to the individual device 80.

  According to the method of the second embodiment, after the individual devices 60 and 70 make the access request, when the individual device 80 makes the access request with a delay, the common data “a” is stored in the individual devices 60 to 80. The time until complete transfer is time A.

  On the other hand, as shown in the upper part of FIG. 15, in the first embodiment, when an access request for common data is received from the individual device 60 and the individual device 70, the management device 100 prepares for multicast transfer of the common data “a”. Is ready, multicast transmission of the common data “a” is started. The multicast transfer of the common data “a” is started even when the access request from the individual device 80 is not received.

  When the management device 100 receives an access request for the common data “a” from the individual device 80 during the execution of the multicast transfer, the management device 100 completes the multicast transfer for the individual devices 60 and 70. Then, after completing the multicast transfer to the individual devices 60 and 70, the management device 100 starts transmission of the common data “a” to the individual device 80 from the beginning.

  As described above, since the management apparatus 100 collectively transfers the common data “a” to the individual apparatus 80 after the multicast transfer to the individual apparatuses 60 and 70 is completed, the management apparatus 100 transfers the common data to all the individual apparatuses. The time until is time B. Comparing Example 1 and Example 2, it can be seen that the end time of multicast transfer is shortened by time C in Example 2 compared to Example 1.

  Next, the configuration of the system according to the second embodiment will be described. FIG. 16 is a diagram illustrating the configuration of the system according to the second embodiment. As shown in the figure, in this system, individual devices 60 to 80 are connected to a management device 300 that stores common data. Here, for convenience of explanation, only the individual devices 60 to 80 are shown, but this system also includes other individual devices. In addition, the description regarding the individual apparatuses 60-80 is the same as that of the individual apparatus shown in FIG.

  The management device 300 is a device that multicasts common data corresponding to each individual device when an access request is received from the individual device. In addition, when the management apparatus 300 receives an access request from another individual apparatus while collectively transmitting common data corresponding to the individual apparatus, the management apparatus 300 can share the common data to the other individual apparatus from the middle. Is transmitted, the untransmitted common data is retransmitted to another terminal apparatus.

  FIG. 17 is a diagram illustrating the configuration of the management apparatus 300 according to the second embodiment. As shown in FIG. 17, this management device 300 is common to a common data storage unit 310, a multicast group ID buffer 320, an individual device group IF unit 330, an access content determination unit 340, and a processing wait FIFO 350. A data management unit 360.

  The common data storage unit 310 is a storage unit that divides and stores common data for each type. Note that the data structure of the common data stored in the common data storage unit 310 is the same as the common data shown in FIG.

  The multicast group ID buffer 320 is storage means for storing access request identification information in association with each multicast group ID. FIG. 18 is a diagram illustrating an example of a data structure of the multicast group ID buffer 320 according to the second embodiment.

  As shown in FIG. 18, this multicast group ID buffer 320 includes a buffer 320a corresponding to the multicast group ID “A”, a buffer 320b corresponding to the multicast group ID “B”, and a buffer corresponding to the multicast group ID “C”. 320c.

  Also, each of the buffers 320a to 320c stores access request identification information and a retransmission size in association with each other. Here, the retransmission size indicates the size of common data to be retransmitted to the associated access request identification information. The retransmission size is registered by the access content determination unit 340 described later.

  Returning to the description of FIG. 17, the individual device group IF unit 330 is a unit that mainly controls communication with the individual devices 60 to 80.

  The access content determination unit 340 is means for registering access request identification information in the multicast group ID buffer 320 when an access request is acquired from the individual devices 60 to 80. Further, the access content determination unit 340 registers a request corresponding to the access request in the processing wait FIFO 350.

  In the following, after the process of the access content determination unit 340 registering the access request identification information in the multicast group ID buffer 320, the process of registering the request in the processing wait FIFO 350 will be described.

  First, a process for registering access request identification information in the multicast group ID buffer 320 will be described. The access content determination unit 340 holds a management table, and when the access request is acquired from the individual devices 60 to 80, the individual device identification information and the access request identification information included in the access request are compared with the management table. As a result, the access request identification information to be registered in each of the buffers 320a to 320c of the multicast group ID buffer 320 is identified and registered. The data structure of the management table held by the access content determination unit 340 is the same as the data structure of the management table shown in FIG.

  In addition, when registering access request identification information in each of the buffers 320a to 320c, the access content determination unit 340 registers the retransmission size together with the transfer management table.

  Here, the transfer management table is a table for managing the transfer size of the transferred common data. FIG. 19 is a diagram illustrating an example of the data structure of the transfer management table. As shown in FIG. 19, the transfer management table stores the multicast group ID and the transferred data size in association with each other. Assume that the access management table 340 holds the transfer management table.

  For example, when registering the access request identification information “x” in the buffer 320a, the access content determination unit 340 refers to the transferred data size of the multicast group ID in the transfer management table. Here, if the transferred data is “0”, the multicast transfer has not been performed yet, so the access request identification information “x” and the retransmission size “0” are associated with each other and registered in the buffer 320a.

  In addition, when registering access request identification information “s” in the buffer 320a, the access content determination unit 340 refers to the transferred data size of the multicast group ID in the transfer management table. If the transferred data is “50”, the access request identification information “s” and the retransmission size “50” are associated with each other and registered in the buffer 320a.

  In the transfer management table, the initial value of the transferred data size is “0”. The access content determination unit 340 counts up the data size of the transferred common data from the time when the multicast transfer of the common data is started, and sequentially updates the transferred data size in the transfer management table.

  The transferred data size corresponding to the multicast group ID “A” is the transferred data size of the common data “a”. The transferred data size corresponding to the multicast group ID “B” is the transferred data size of the common data “b”. The transferred data size corresponding to the multicast group ID “C” is the transferred data size of the common data “c”.

  Next, processing in which the access content determination unit 340 registers a request in the processing wait FIFO 350 will be described. Further, this process will be described separately for “when the priority information is not included in the access request” and “when the priority information is included in the access request”. The access content determination unit 340 determines whether priority is set based on the header information of the access request.

(When the priority information is not included in the access request)
The access content determination unit 340 acquires an access request from the individual device, and when the acquired access request does not include priority information, sets the priority flag of the processing wait FIFO 350 to “off”.

  Then, the access content determination unit 340 creates a request corresponding to the access request based on the individual device identification information included in the access request and the management data (see FIG. 5). As shown in FIG. 3, when there are three types of multicast group IDs (common data), there are also three types of requests.

  For example, when the access content determination unit 340 acquires an access request having the individual device identification information “k1001” and the access request identification information “x”, it corresponds to the multicast group ID “A”, and therefore creates the request A. To do.

  The access content determination unit 340 registers the requests in the processing wait FIFO 350 in the order in which the requests are created. In addition, when registering a request, the access content determination unit 340 does not register a request if the same request is already registered in the processing wait FIFO 350.

  For example, when the request A is registered in the processing-waiting FIFO 350 when the request A is registered in the processing-waiting FIFO 350, the request A is not newly registered.

(When access request includes priority information)
The access content determination unit 340 acquires an access request from the individual device, and when the acquired access request includes priority information, sets the priority flag of the processing wait FIFO 350 to “on”.

  Then, the access content determination unit 340 generates a request corresponding to the access request and associates the generated request with the priority information in the same manner as in the case where the access request does not include priority information. The request is registered in the processing wait FIFO 350.

  The access content determination unit 340 may register the requests in the processing wait FIFO 350 in order from the request with the highest priority based on the priority information associated with the request. In addition, when registering the request A in the processing wait FIFO 350, the access content determination unit 340 does not register the request A newly if the request A is already registered in the processing wait FIFO 350.

  The processing wait FIFO 350 is a storage unit (FIFO) that stores a request registered by the access content determination unit 340. The data structure of the processing wait FIFO 350 is the same as the data structure of the processing wait FIFO 150 shown in FIG.

  The processing wait FIFO 350 has a priority flag (not shown), and when the priority flag is “ON”, the common data management unit 360 sequentially receives requests with the highest priority. Read out. On the other hand, when the priority flag is “off”, the requests are registered in order from the previously registered request to the common data management unit 360.

  The common data management unit 360 is a unit that acquires a request from the processing-waiting FIFO 350 and multicast-transfers common data corresponding to the request to the corresponding individual device. When the common data management unit 360 reads the common data corresponding to the request from the common data storage unit 310, the common data management unit 360 multicasts the common data based on the information stored in the multicast group ID buffer 320.

  If the transfer destination is added during the multicast transfer, the common data management unit 360 adds the added transfer destination and continues the multicast transfer. Then, after the multicast transfer is completed, the common data management unit 360 retransmits the insufficient common data to the transfer destination that started the transfer from the middle.

  Hereinafter, processing of the common data management unit 360 will be described. The processing of the common data management unit 360 is roughly divided into processing for reading common data from the common data storage unit 310 and processing for multicast transfer of common data. First, processing for reading common data from the common data storage unit 310 is performed. After the description, a process for multicast transfer of common data will be described.

  A process in which the common data management unit 360 reads the common data from the common data storage unit 310 will be described. The common data management unit 360 refers to the priority flag of the processing wait FIFO 350 and, when the priority flag is “off”, obtains the requests in order from the request previously registered in the processing wait FIFO 350.

  On the other hand, if the priority flag is “ON”, the requests registered in the processing wait FIFO 350 are acquired in order from the request with the highest priority. For example, when the priority information is set as shown in FIG. 6, requests are acquired from the processing wait FIFO 350 in the order of requests A, B, and C.

  Then, the common data management unit 360 compares the acquired request with the common data stored in the common data storage unit 310 (see FIG. 3), and acquires the common data corresponding to the request from the common data storage unit 310. .

  The requests A to C correspond to the multicast groups IDA to C, respectively. Therefore, the common data management unit 360 reads the common data “a” when acquiring the request A, reads the common data “b” when acquiring the request B, and acquires the request C. Reads the common data “c”.

  Next, a process in which the common data management unit 360 performs multicast transfer of common data will be described. When the common data management unit 360 acquires the common data, the common data management unit 360 refers to the buffer (any one of the buffers 320a to 320c) corresponding to the multicast group ID of the acquired common data, and the access request included in the referred buffer Based on the identification information, the common data is multicast-transferred to the corresponding individual device.

  Here, the multicast group ID buffer 320 that changes with the processing of the access content determination unit 340 and the common data management unit 360 will be described. FIG. 20 is a diagram for explaining data changes in the multicast group ID buffer 320 according to the second embodiment. As an example, FIG. 20 illustrates a case where the individual device 80 transmits a request for the common data “a” behind the request for the common data “a” of the individual devices 60 and 70.

  When the access content determination unit 340 acquires an access request corresponding to the common data “a” from the individual devices 60 and 70, the access content determination unit 340 registers the access request identification information “x, y” in the buffer 320a. At this time, since the multicast transfer of the common data “a” has not started, the retransmission size corresponding to the access request identification information “x, y” becomes “0” (step S10).

  When the access content determination unit 340 acquires an access request corresponding to the common data “b” from the individual devices 60 and 70, the access content determination unit 340 registers the access request identification information “y, w” in the buffer 320b. At this time, since the multicast transfer of the common data “b” has not started, the retransmission size corresponding to the access request identification information “y, w” becomes “0” (step S11).

  When the access content determination unit 340 acquires an access request corresponding to the common data “c” from the individual devices 60 and 80, the access content determination unit 340 registers the access request identification information “z, t” in the buffer 320c. At this time, since the multicast transfer of the common data “c” is not started, the retransmission size corresponding to the access request identification information “z, t” is “0”. When the common data “a” is ready to be transferred, the common data management unit 360 refers to the buffer 320a and starts multicast transfer to the corresponding individual devices 60 and 70 (step S12).

  When the access content determination unit 340 obtains an access request for the common data “a” from the individual device 80 while the common data management unit 360 is performing the multicast transfer of the common data “a”, The access request identification information “s” is registered in the buffer 320a. At this time, when the transferred data size corresponding to the multicast group ID “A” in the transfer management table (see FIG. 19) is “50”, the retransmission size corresponding to the access request identification information “s” is “50”. "

  The common data management unit 360 multicasts the common data “a” to the individual devices 60, 70, and 80 from the time when the access request identification information “s” is registered in the buffer 320a with a delay (step S13). That is, the common data management unit 360 transfers the common data “a” to the individual device 80 from the middle.

  When the transfer of the common data “a” is completed, the common data management unit 360 has access request identification information “x, v” whose retransmission size is “0” among the access request identification information registered in the buffer 320a. Is deleted. Then, when the common data “b” is ready to be transferred, the common data management unit 360 refers to the buffer 320b and starts multicast transfer to the corresponding individual devices 60 and 70 (step S14).

  When the transfer of the common data “b” is completed, the common data management unit 360, among the access request identification information registered in the buffer 320b, the access request identification information “y, w” whose retransmission size is “0”. Is deleted. When the common data “c” is ready to be transferred, the common data management unit 360 refers to the buffer 320c and starts multicast transfer to the corresponding individual devices 60 and 80 (step S15).

  When the transfer of the common data “c” is completed, the common data management unit 360 has access request identification information “z, t” whose retransmission size is “0” among the access request identification information registered in the buffer 320c. Is deleted. Then, the common data management unit 360 detects access request identification information to be retransmitted from the buffer 320a, and transfers untransmitted retransmission data to the corresponding individual device 80 (step S16).

  When the retransmission to the individual device 80 is completed, the common data management unit 360 deletes the access request identification information “s” to be retransmitted from the buffer 320a (Step S17).

  Next, a processing procedure of the management apparatus 200 according to the second embodiment will be described. FIGS. 21 and 22 are flowcharts illustrating the processing procedure of the management apparatus 200 according to the second embodiment. As shown in FIG. 21, in the management device 200, the access content determination unit 340 receives an access request from each individual device (step S201), determines an access destination, and identifies a corresponding multicast group ID (step S202).

  The access content determination unit 340 stores the access request identification information in the multicast group ID buffer 320 (step S203), and determines whether priority information is set for the access request (step S204).

  When priority information is not set in the access request (No at Step S205), the access content determination unit 340 determines whether or not the first request exists in the processing-waiting FIFO 350 (Step S206). When the first-arrival request exists (step S207, Yes), the process proceeds to step S213.

  On the other hand, if there is no first-arrival request (step S207, No), the access content determination unit 340 stores the request in the processing wait FIFO 350 and sets the priority flag of the processing wait FIFO 350 to off (step S208), the process proceeds to step S213.

  By the way, when priority information is set in the access request in step S205 (step S205, Yes), the access content determination unit 340 determines whether there is a first request in the processing wait FIFO 350. (Step S209). If there is no first-arrival request (step S210, No), the request is stored in the processing wait FIFO 350, the priority flag of the processing wait FIFO 350 is set to on (step S211), and the process proceeds to step S213.

  On the other hand, if there is a first-arrival request (step S210, Yes), the priority flag of the processing wait FIFO 350 is set to on (step S212), and it is determined whether or not preparation for transferring common data is completed. (Step S213). If the common data transfer preparation is not completed (No in step S214), the process proceeds to step S202.

  When the preparation for transferring the common data is completed (step S214, Yes), the common data management unit 360 determines whether the priority flag is on (step S215). If the priority flag is off (step S216, No), the requests are sequentially read from the requests registered in the processing wait FIFO 350, multicast is started to the individual device (step S217), and the process proceeds to step S219. .

  On the other hand, when the priority flag is on (step S216, Yes), the common data management unit 360 reads the request from the processing wait FIFO 350 based on the priority information, and multicasts the corresponding individual information. Start (step S218).

  The access content determination unit 340 counts the transfer data size of the common data (step S219), and determines whether an access request is received during multicast transfer (step S220). When the access request is not received during the multicast transfer (No at Step S221), the common data management unit 360 ends the multicast after completing the transmission of the common data (Step S222).

  On the other hand, when an access request is received during multicast transfer (step S221, Yes), the common data management unit 360 adds a new transfer destination and continues multicast (step S223). Then, the common data management unit 360 retransmits the untransmitted common data to the individual device after the end of the multicast transfer (step S224).

  Next, a difference in transfer time between the management apparatus 100 according to the first embodiment and the management apparatus 200 according to the second embodiment will be described. FIG. 23 is a diagram for explaining a difference in transfer time between the first and second embodiments. As preconditions, there are individual devices 60, 70, 80. The individual device 60 is equipped with cards 10a, 10b, 10c, the individual device 70 is equipped with cards 20a, 20b, and the individual device 80 is equipped with cards 30a, 30c. To do.

  In addition, the size of the common data of the system is 120 MByte. There are three card types, and 40 MByte (120 MByte ÷ 3) data is used for each type of card. The access speed to the system common data is 16 MByte. A compact flash (registered trademark) is assumed as a memory for storing a common system.

  Further, the path access speed between the management apparatus 100 and the individual apparatuses 60 to 80 is set to 160 Mbytes. Assume a serial bus (SERDES) with a clock of 100 MHz and a data width of 16 bits. Since the access request packet size is small, transfer time cannot be entered. Further, it is assumed that an access request from the individual device 80 is generated 1 sec after the management device starts data transfer to the individual devices 60 and 70.

When the management apparatus 100 according to the first embodiment receives an access request from the individual apparatus 80 while transferring the common data “a”, the management apparatus 100 transfers the common data “a” to “c”. After completion, the common data “a” is transferred to the individual device 80 from the beginning. Therefore, the transfer time according to the first embodiment includes the data read time of the common data “a” × 2, the data read time of the common data “b”, the data read time of the common data “c”, and the data transfer time. Since it becomes the added value,
2.5sec × 4 + 2.0sec = 12sec
(See the upper part of FIG. 23).

  On the other hand, when the management apparatus 200 shown in the second embodiment receives an access request from the individual apparatus 80 while the common data “a” is being transferred, the management apparatus 200 individually processes the common data “a”. Transfer to device 80. Then, after the transfer of the common data “a” to “c” is completed, the remaining common data “a” is transferred to the individual device 80.

Therefore, the transfer time according to the second embodiment includes the data read time for the common data “a” × 2, the data read time for the common data “b”, the data read time for the common data “c”, and the common data “c”. c ”is the value obtained by subtracting 1 sec from the value obtained by adding the data read time and the data transfer time.
2.5sec × 4 + 2.0sec-1.0sec = 11sec
(See the lower part of FIG. 23).

  As shown in FIG. 23, when the transfer time by the management apparatus according to the first embodiment is compared with the transfer time by the management apparatus according to the second embodiment, when the individual apparatus 80 outputs an access request with a delay, the second embodiment. Since the management apparatus 1 is shorter by 1 sec, the data transfer time can be shortened.

  As described above, the management device 200 according to the second embodiment receives an access request from another individual device while collectively transmitting data of a type corresponding to a plurality of individual devices. In addition, after the common data is transmitted to other individual devices from the middle, the untransmitted common data is retransmitted to other terminal devices, so that the data transfer time can be shortened.

  By the way, in the second embodiment, in order to simplify the operation, the case where the access request of one individual device (for example, the individual device 80) is delayed among the access requests of the individual devices 60 to 80 has been described. However, when access requests from a plurality of individual apparatuses are delayed, the retransmission sizes of the delayed ones are compared, and the common data is retransmitted with the larger retransmission size.

  FIG. 24 is a diagram illustrating an example of a data structure of a multicast group ID buffer when access requests are delayed from a plurality of individual apparatuses. In the example shown in FIG. 24, the data structure of the multicast group ID buffer when an access request is received from the individual devices 70 and 80 during the multicast transfer of the common data “a” to the individual device 60 is shown. Show. However, it is assumed that the individual device 70 has made an access request before the individual device 80.

  When resending the common data “a”, the common data management unit 360 compares the retransmission size of the access request identification information “v” with the retransmission size of the access request identification information “s”. As a result of the comparison, since the retransmission size of the access request identification information “s” is larger, the common data management unit 360 retransmits the common data “a” having the retransmission size “50” to the individual devices 70 and 80.

  In this way, by setting the retransmission size of the common data in accordance with the larger retransmission size, it is possible to compensate for the data that is insufficient in each individual device by one retransmission.

  In addition, before transmitting an access request to the management apparatus, the individual apparatus starts reception of common data from the management apparatus, and when all the common data has been received, outputs a reception end report to the management apparatus. Also good. The management apparatus that has received the reception completion report skips the retransmission processing for the individual apparatus that is the transmission base of the reception completion report. In this manner, the data transfer time can be further reduced by skipping the retransmission process.

  In addition, the management apparatus 100 according to the first embodiment stores the request in the processing waiting FIFO 150, and the common data management unit 160 reads the request according to the previously registered request order or priority information, Since data is transmitted, it is possible to return an access response according to a request on the system side in response to a separate access request from an individual device.

  By the way, among the processes described in the second embodiment, all or part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed. All or a part of the above can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  Moreover, each component of the management apparatus 300 shown in FIG. 17 is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. Further, each processing function performed by each device is realized by a CPU and a program that is analyzed and executed by the CPU, in the same manner as the management device 100 shown in the first embodiment. Alternatively, it can be realized as hardware by wired logic.

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

(Supplementary note 1) A management device that manages common data used in common in a plurality of terminal devices,
Common data storage means for dividing and storing the common data for each type;
A management unit that manages the access request and the type of the common data in association with each other when an access request for the common data is received from the plurality of terminal devices;
Transmission means for collectively transmitting common data of a corresponding type to a plurality of terminal devices that are transmission sources of an access request associated with the type of the common data;
A management apparatus comprising:

(Supplementary note 2) The management device according to supplementary note 1, wherein the transmission unit transmits the common data based on an order in which the access request is received from the terminal device.

(Additional remark 3) When the priority is set to the access request transmitted from the said terminal device, the said transmission means determines the order which transmits the said common data based on the said priority. The management apparatus according to Supplementary Note 1 or 2.

(Additional remark 4) When the said transmission means receives the said access request from another terminal device while collectively transmitting the common data of the classification applicable to several terminal devices, the said other terminal device The management apparatus according to appendix 1, 2, or 3, further comprising: a retransmission unit that retransmits the common data for the shortage to the other terminal apparatus after transmitting the common data in addition to the transmission destination .

(Supplementary Note 5) When retransmitting untransmitted common data to a plurality of terminal devices, the retransmission means retransmits the common data having the maximum data amount to the plurality of terminal devices among the common data to be retransmitted. The management apparatus according to appendix 4, wherein

(Supplementary note 6) A management device management method for managing common data used in common in a plurality of terminal devices,
The management device
A common data storage step of dividing the common data into types and storing them in a storage device;
A management step of managing the access request and the type of the common data in association with each other when an access request for the common data is received from the plurality of terminal devices;
A transmission step of collectively transmitting common data of a corresponding type to a plurality of terminal devices that are transmission sources of an access request associated with the type of the common data;
A management method characterized by including

(Supplementary note 7) The management method according to supplementary note 6, wherein the transmission step transmits the common data based on an order in which the access requests are received from the terminal device.

(Additional remark 8) When the priority is set to the access request transmitted from the said terminal device, the said transmission step determines the order which transmits the said common data based on the said priority. The management method according to appendix 6 or 7.

10, 20, 30, 60, 70, 80 Individual devices 10a, 10b, 10c, 20a, 20b, 30a, 30c, 60a, 60b, 60c, 70a, 70b, 80a, 80c Card 50, 100 Management device 110 Common data storage Unit 120 multicast group ID buffer 120a, 120b, 120c buffer 130 individual device group IF unit 140 access content determination unit 150 processing wait FIFO
160 Common Data Management Unit 200 Computer 201 Input Device 202 Monitor 203 Multicast Group ID Buffer 204 Processing Waiting FIFO
205 RAM
205a, 210a Common data 206 ROM
207 Medium reading device 208 Communication device 209 CPU
209a Management process 210 HDD
210b management program 211 bus

Claims (7)

A management device for managing common data used in common in a plurality of terminal devices,
Common data storage means for dividing and storing the common data for each type;
When the access request for the common data is received from the plurality of terminal devices, the preparation for transferring the common data of the type corresponding to the access request is started, and during the transfer preparation, the same as the common data being prepared for transfer A management means for storing information on other terminal information in a buffer in addition to information on a plurality of terminal devices that initially made access requests when an access request for common data of a type is received from another terminal device ;
And a transmission means for collectively transmitting common data of a type corresponding to the access request to a plurality of terminal devices stored in the buffer when the transfer preparation is completed. apparatus.   The management apparatus according to claim 1, wherein the transmission unit transmits the common data based on an order in which the access request is received from the terminal device.   2. The transmission unit according to claim 1, wherein when a priority order is set in an access request transmitted from the terminal device, the order of transmitting the common data is determined based on the priority order. Or the management apparatus of 2.   When the access means accepts the access request from another terminal device while the transmission unit is collectively transmitting common data of a type corresponding to a plurality of terminal devices, the other terminal device is set as the transmission destination. 4. The management apparatus according to claim 1, 2 or 3, further comprising: a retransmission unit that retransmits the shortage of common data to the other terminal apparatus after transmitting the common data.   The retransmission means, when retransmitting untransmitted common data to a plurality of terminal devices, retransmits the common data having the maximum data amount to the plurality of terminal devices among the common data to be retransmitted. The management apparatus according to claim 4. A management device management method for managing common data commonly used in a plurality of terminal devices,
The management device
A common data storage step of dividing the common data into types and storing them in a storage device;
When the access request for the common data is received from the plurality of terminal devices, the preparation for transferring the common data of the type corresponding to the access request is started, and during the transfer preparation, the same as the common data being prepared for transfer A management step of storing information on other terminal information in a buffer in addition to information on a plurality of terminal devices that initially made access requests when receiving an access request for common data of a type from another terminal device ;
A transmission step of collectively transmitting common data of a type corresponding to the access request to a plurality of terminal devices stored in the buffer when the transfer preparation is completed. Method.   The transmission step, when a priority is set for an access request transmitted from the terminal device, determines an order of transmitting the common data based on the priority. The management method described in 1.

Images