JP2002094472A - Data acquisition device and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data acquisition device for efficiently acquiring and supplying a large amount of data, according to a number of data acquisition requests that are generated from diversified applications under the restriction of strict hardware resources. SOLUTION: The data acquisition device comprises a data acquisition section 507, that receives the setting of data acquisition conditions, and acquires data by extracting the data when data for satisfying either of request conditions, that have been set are included in data being transmitted; a data acquisition request reception section 501 for receiving a request for acquiring specific data long with conditions for specifying the data from a plurality of applications; a request condition setting scheduling section 113, that generates a request queue by scheduling data acquisition to all received requests; and sets the corresponding conditions to the data acquisition section 507, in accordance with the queue for controlling the start for acquiring data, and the like.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus for extracting and acquiring data satisfying a specific condition from a transmitted data stream, and more particularly, to efficiently acquire a large amount of data under the constraints of hardware resources. To a data acquisition device.

[0002]

2. Description of the Related Art A data acquisition device such as a digital broadcast receiver can efficiently transmit broadcast data transmitted from a transmission side that satisfies a specific condition under limited hardware resources and time constraints. It is required to extract and obtain well. FIG. 28 is a functional block diagram showing a configuration of a conventional data acquisition device. The data acquisition device 500 receives, demultiplexes, and receives broadcast data in a digital broadcast receiver.
Data acquisition requests from various application programs (hereinafter, simply referred to as “applications”) that correspond to hardware and software that perform basic processing related to reception such as decoding and filtering and that implement various functions of the receiver. A data acquisition request receiving unit 501 that acquires the request, a data acquisition request setting unit 509 that converts the acquired request into parameters suitable for the data acquisition unit 507, and sets the data acquisition unit 507, and satisfies the set data acquisition request. The data acquisition unit 507 extracts data from broadcast data and acquires the data, and the data transmission unit 508 returns the acquired data to the requesting application.

FIG. 29 is a flowchart showing a flow of data acquisition processing by the conventional data acquisition device 500 shown in FIG. When the data acquisition request receiving unit 501 receives a data acquisition request from the application to acquire data such as specific program information and control information, the data acquisition request receiving unit 501 transmits the data acquisition request to the data acquisition request setting unit 509 (step S100). . Data acquisition request setting unit 509
Converts the notified data acquisition request into parameters suitable for the data acquisition unit 509 and sets the parameters in the data acquisition unit 507 (step S101).

[0004] The data acquisition unit 507 starts acquiring data corresponding to the set parameters (step S10).
2). For example, it monitors whether or not the broadcast data contains program information that satisfies certain conditions. Data acquisition unit 507
Determines whether the target data has been obtained (step S103), and if not, repeats this determination until it can be obtained (step S1).
03: No). If it can be obtained (step S10
3: Yes), the data acquisition unit 507 passes the data to the data transmission unit 508, and the data transmission unit 508 returns the passed data to the requesting application (Step S104).

[0005] In this manner, the conventional data acquisition device responds to a data acquisition request from an application.
By executing data acquisition faithfully, we respond to individual data acquisition requests.

[0006]

However, in such a conventional data acquisition apparatus, once data acquisition for a certain data acquisition request is started, the data acquisition is not performed unless the data acquisition is canceled by some explicit method. When multiple data acquisition requests from many applications are complicated or when data acquisition for data that is transmitted only infrequently is started, etc. This results in extremely inefficient (low data acquisition rate) data acquisition.

As a countermeasure, there is a method of programming in consideration of an internal processing procedure, a timing of generating a data acquisition request, and the like in advance so that unnecessary waiting time does not occur for each application.
Similar problems remain because it is difficult to design in consideration of the mutual influence of applications (contention with data acquisition requests issued from other applications).

Accordingly, the present invention has been made in view of such a problem,
An object of the present invention is to provide a data acquisition apparatus and method capable of efficiently acquiring and supplying a large amount of data in response to many data acquisition requests issued from various applications under severe hardware resource constraints. Aim.

[0009]

In order to achieve the above object, a data acquisition apparatus according to the present invention responds to each request from a transmitted data stream based on each request from a plurality of data processing apparatuses. A data acquisition device that extracts and acquires data that satisfies specific conditions and returns the acquired data to the requesting data processing device, and from the plurality of data processing devices, A request receiving means for receiving, a condition generating means for receiving the request from the request receiving means and generating the corresponding condition, and accepting a setting of the generated condition;
Data extraction means for monitoring whether or not data satisfying any of the set conditions is included in the data stream, and if included, extracting and acquiring the data; and A queue of the condition corresponding to the request is generated, and according to the queue, the setting is performed in the data extracting unit, so that data acquisition is started, and the setting is deleted from the data extracting unit. It is characterized by comprising a scheduling means for terminating the acquisition and scheduling the data acquisition, and an output means for outputting the data acquired by the data extracting means to the data processing apparatus of the request source.

Further, the present invention can be realized as a data acquisition method in which each unit in the data acquisition device is a step, or as a program including such steps. Further, the data acquisition device of the present invention, based on each request from a plurality of data processing devices, extracts and acquires data that satisfies a specific condition corresponding to the request from the transmitted data stream, and acquires the acquired data. A data acquisition device that returns data to each of the requesting data processing devices, from a plurality of data processing devices, an acquisition unit that acquires the condition corresponding to the request, and accepts the setting of the condition, and sets the set condition. A data extracting unit that monitors whether data satisfying any of the conditions is included in the data stream, and if the data is included, extracts and obtains the data; Setting information indicating whether the setting of the condition is "present" or "not present" in the means, and a value corresponding to the acquisition order of the condition,
A table holding unit for holding a table indicating a correspondence relationship with an order value initialized to a value indicating the newest acquisition order when the setting of the condition is deleted from the data extraction unit; Each time the condition is acquired, the newly acquired condition, the setting information of the condition, and the order value indicating the newest acquisition order are recorded in the table as a set, A scheduling unit for controlling the setting of the condition in the data extracting unit by referring to the setting information and the order value recorded in a table, and a data processing device of a request source for the data acquired by the data extracting unit And an output means for outputting the data to the computer.

[0011]

Embodiments of the present invention will be described below in detail with reference to the drawings. (Embodiment 1) FIG. 1 is a functional block diagram showing a configuration of a data acquisition device 110 according to Embodiment 1 of the present invention. The data acquisition device 110 transmits a data acquisition request issued from a plurality of data processing devices (this device also includes an application realized by software; hereinafter, simply referred to as an “application”).
A data acquisition apparatus characterized in that scheduling is performed according to priority, and specifically, hardware that performs basic processing related to reception, demultiplexing, decoding, filtering, and the like of broadcast data in a digital broadcast receiver And a software part, and includes a data acquisition request receiving unit 501, a request condition generating unit 112, a request condition setting scheduling unit 113, a request condition recording unit 114, a timer unit 115, a request condition setting unit 116, a data acquisition unit 507, and data transmission. 508. Note that the same components as those of the conventional data acquisition device 500 shown in FIG. 28 are denoted by the same reference numerals.

In the present embodiment, each application includes, in addition to a data acquisition request including header information and information for specifically specifying data to be acquired, information specifying a degree of priority in the data acquisition. The data acquisition request is requested by notifying the data acquisition device 110 (data acquisition request receiving unit 501) of the priority.

More specifically, the data acquisition request is, for example,
Information (table ID, section number, etc.) for designating a specific table from among various tables, which are program arrangement information included as packets in a transport stream (TS) transmitted from a broadcast station. is there.
Here, the various tables include, for example, an NIT that includes information relating transmission channel information such as a modulation frequency and a broadcast program.
(Network InformationTable) and EIT consisting of information related to the program, such as the name of the program, the broadcast date and time, and a description of the contents
(Event Information Table) and SDT (Service Description Table) including information on the organization channel such as the name of the organization channel and the name of the broadcaster. These are all sections defined by the MPEG-2 System. This is data that uses a data structure of the form.

The priority indicates one selected from a plurality of predetermined priorities (here, “1”, “2”, “3” in descending order of priority). The data acquisition request receiving unit 501 receives a set of a data acquisition request and a priority notified from each application, and notifies the request condition generation unit 112 of the contents.
10 is an input interface. Note that, when the data acquisition request receiving unit 501 collectively receives a plurality of sets of data acquisition requests and priorities from one or a plurality of applications, the data acquisition request receiving unit 501 collectively sends them to the request condition generation unit 112.

The request condition generating unit 112 generates a request condition indicating the contents of each set of the data acquisition request and the priority passed from the data acquisition request receiving unit 501, and sets the generated request condition to the request condition setting. It notifies the scheduling unit 113 or stores it in the request condition recording unit 114. Here, the “request condition” refers to an information record corresponding to each data acquisition request to be scheduled and managed by the data acquisition device 110. In the present embodiment, at least the information record is an object of the acquisition request. A data acquisition condition indicating a condition for specifying data and a priority are included.

FIG. 2 is a diagram showing an example of a list of request conditions generated by the request condition generator 112. Here, eight request conditions generated according to the order in which the data acquisition requests are generated are shown. Each request condition 1101 includes a data acquisition condition 1102 and a priority 1103. Request condition recording unit 114
Is composed of a flash memory or the like and has a request condition 11
01 is a rewritable storage device.

The timer unit 115 includes a calendar timer, a preset counter, and the like. The timer unit 115 outputs the current date and time, and outputs a notification or an interrupt signal indicating that a predetermined time has elapsed, once or repeatedly. Output. The data acquisition unit 507 extracts a specific TS packet from the transport stream based on a PID (Packet ID) or the like, and decodes the TS packet into an elementary stream.
Here, it is a decoder or the like, and has a capability of simultaneously processing (standby reception) a maximum of 20 data acquisition requests. That is, the data acquisition unit 507 has a capability of accepting the setting of up to 20 request conditions by the request condition setting unit 116, and the state of data acquisition corresponding to each set request condition (whether or not acquired). Is reported to the request condition setting scheduling unit 113 as data acquisition information, or the acquired data is sent to the data transmission unit 508.

It should be noted that once the request condition is set by the request condition setting unit 116, the data acquisition unit 507
The data acquisition corresponding to the set request condition is continued unless it is deleted by 13. The request condition setting unit 116 sets the request condition notified from the request condition setting scheduling unit 113 in the data acquisition unit 507. Specifically, the post-scheduling request condition sent from the request condition setting scheduling unit 113 is converted into a dedicated parameter (such as a PID) that can be understood by the data acquisition unit 507 and set in the data acquisition unit 507.

The data transmitting unit 508 is connected to the data acquiring unit 50.
7, the request source application is specified by referring to the request condition and the like recorded in the request condition recording unit 114, and the acquired data is returned to the application. The request condition setting scheduling unit 113 includes a CPU, a ROM storing a control program, and the like. The request condition setting scheduling unit 113 communicates with each component to collectively schedule data acquisition corresponding to the request condition generated by the request condition generating unit 112. For this purpose, the data acquisition state (“executable state”, “executing”, “waiting state”, “executing stopped”) for each request condition is determined using the request condition recording unit 114. It monitors and manages, schedules newly generated request conditions at regular intervals according to priorities according to a notification from the timer unit 115, and registers request conditions in an executable state where certain conditions are met in a request condition recording unit. 114
And notifies the request condition setting unit 116 of the request.

FIG. 3 shows the state transition of the request condition, that is, the data acquisition apparatus 1 for each request condition.
10 is a diagram showing a data acquisition state (execution state) and its transition according to FIG. Here, “executing” means a state in which the request condition is set in the data acquisition unit 507 (a state that is always acquired when target data is transmitted), and an “executable state” , Data acquisition unit 50
7 means a state in the queue before being set to “7”. “Waiting state” means that the setting in the data acquisition unit 507 is temporarily set because it has been set in the data acquisition unit 507 until immediately before, but a certain time has elapsed. And "executing suspended" means a state in which data is temporarily excluded from data acquisition due to a cause such as a combination of request conditions described later.

All state transitions except for the generation of the request condition by the request condition generation unit 112 are performed under the control of the request condition setting scheduling unit 113. For example, when the number of executing request conditions is less than 20, the request condition setting scheduling unit 113 reads the request conditions from the top of the queue of request conditions in the “executable state” for the vacant request conditions and executes “executable”. Transitions to "Medium", transitions to "Waiting state" if a certain period of time has elapsed without obtaining data corresponding to the request condition in "Executing", and "Executes" if a certain period of time has elapsed State, and if a request condition with a higher priority than the "executing" request condition occurs, the "executing" request condition is shifted to the "executable state", and the "executing" request. When data corresponding to the condition is obtained or when an explicit deletion command is issued from another application, the request condition is Quest condition recording unit 1
14 ("deleted state").

FIG. 4 shows a state after the request conditions shown in FIG. 2 are scheduled by the request condition setting scheduling unit 113, that is, after the requests are rearranged in order of priority. Here, request conditions with high priority are arranged so as to be located at the top (upper). Request condition setting scheduling unit 113
Causes the upper part of the queue to be prioritized, reads out the request condition in the “executable state” from the request condition recording unit 114, and notifies the request condition setting unit 116 to start data acquisition (“ To "running").

Next, the operation of the data acquisition device 110 configured as described above will be described. FIG. 5 is a flowchart showing the flow of the entire data acquisition process by the data acquisition device 110. A plurality of data acquisition requests from one or more applications are collectively received by the data acquisition request receiving unit 501 of the data acquisition device (step S20).
0). The received data acquisition request is transmitted to the request condition generation unit 112, where a request condition for acquiring data is generated for each data acquisition request (step S201).

Subsequently, the request condition setting scheduling unit 113 includes a timer unit 115 set in advance.
(Step S202), and if there is no interrupt, the process of step S202 is repeated (step S202: N).
o). If there is an interrupt (step S202: Ye
s) The timing (order) for setting the data acquisition for the request condition passed from the request condition generation unit 112 is scheduled based on the priority (step S203). Then, it is confirmed whether or not there is a request condition that can be set for data acquisition, that is, a request condition that can be immediately executed (step S20).
4) If not, the request condition is recorded in the request condition recording unit 114 (Step S205: No). If there is (Step S204: Yes), the request condition is recorded in the request condition recording unit 114 (Step S20).
6) Subsequently, the request condition is set in the request condition setting unit 116 (step S207), and data acquisition by the data acquisition unit 507 is started (step S20).
8).

The data acquisition unit 507 checks whether or not data has been acquired (step S209), and if no data has been acquired, repeats step S209 (step S209: No). If the data has been acquired (step S209: Yes), the data acquisition unit 507 passes the acquired data to the data transmission unit 508, and the data transmission unit 5
08 transmits the obtained data to the request source (step S210).

FIG. 6 is a flowchart showing a processing procedure centered on the scheduling of the request condition based on the priority by the data acquisition device 110. Upon receiving the new data acquisition request and the priority of each data acquisition request, the data acquisition request receiving unit 501 passes them to the request condition generation unit 112 (step S300).

After receiving the data acquisition request and the priority, the request condition generator 112 generates request conditions corresponding to each data acquisition request (step S3).
01), as shown in FIG.
It is added to each request condition just generated (step S302). Subsequently, the request condition setting scheduling unit 113 checks whether there is an interrupt from the timer unit 115 (step S303), and if there is no interrupt, repeats the process of step S303 (step S303: No).

If there is an interrupt (step S303: Y
es), the existing request condition is extracted from the request condition recording unit 114 (step S304), and the priority of the new request condition is compared with the priority of the existing request condition (step S305). When the priority of the request condition is not higher than the priority of the existing request condition (step S305: No), the new request condition is processed after the existing request condition. 114 and rearrange them (step S306).

When the priority of the new request condition is higher than the priority of the existing request condition (step S3)
05: Yes), the new request conditions are stored in the request condition recording unit 114 and rearranged so that the new request conditions are processed earlier than the existing request conditions (step S307). When the rearrangement of the new and existing request conditions is completed, the request condition setting scheduling unit 113
Issues a data acquisition registration request to the request condition setting unit 116 in order from the top of those for which data acquisition can be set (step S308).
Specifically, the corresponding request condition is read from the request condition recording unit 114 and the request condition setting unit 1
Send to 16.

Then, upon receiving the request condition, the request condition setting unit 116 converts the request condition into setting parameters,
This is set in the data acquisition unit 507. Thus, data acquisition for the request condition by the data acquisition unit 507 is started (step S309). As described above, according to the data acquisition device 110 of the present embodiment, even when a large number of data acquisition requests are issued from a plurality of applications at the same time, the complicated data acquisition requests are processed by the request condition setting scheduling. Since the scheduling is performed collectively by the unit 113 and mutual adjustment is achieved, efficient data acquisition is realized as a whole.

Further, since each data acquisition request is scheduled so as to be processed earlier as the priority is higher, the urgency or the importance is low because the data acquisition with the lower urgency or importance is started first. It is possible to avoid occurrence of a problem that the data is kept waiting without starting high-accuracy data acquisition, and efficient data acquisition is realized. Next, in the data acquisition control by the data acquisition apparatus 110, the execution state for the data acquisition request is changed from “in execution” to “waiting state”.
The control for transiting to the “executable state” via the above will be described in detail.

Request condition setting scheduling section 1
Reference numeral 13 sets a timeout time for each request condition, and transitions to a “waiting state” when the timeout time arrives for a request condition that is “executing”. Then, at the same time as the transition, a time-out recovery time is provided, and the request condition in the “waiting state” is changed to the “executable state” when the time-out recovery time comes.

For example, for a request having a priority of “1”, the request is changed from “executable state” to “executing”, and
The time at which 10 seconds have passed since the transition from "executing" to the "waiting state" is set as the timeout time and the timeout resurrection time, respectively. Similarly, for the request of “3”, the time when 30 seconds have elapsed is set as the timeout time and the timeout recovery time, respectively.

In order to realize such management, the request condition setting scheduling unit 113 stores management information such as an execution state, a timeout time and a timeout recovery time for each of the request conditions stored in the request condition recording unit 114. It controls data acquisition of each request condition while additionally recording and updating.

FIG. 7 is a diagram showing an example of a list of request conditions to which various types of management information have been added by the request condition setting scheduling unit 113. Each request condition 1
101 includes execution state information 1104, a timeout time 1105, and a timeout recovery time 1106. FIG. 8 is a diagram illustrating an example of the current time read from the timer unit 115. Here, the current time in year, month, day, hour, minute, and second is shown.

FIG. 9 shows that the execution state for the data acquisition request is changed from “in execution” to “executable state” through “waiting state”.
6 is a flowchart showing a processing procedure of the data acquisition device 110 when the state is changed to. The request condition setting scheduling unit 113 includes the request condition recording unit 1
14 is extracted from the request condition (step S70).
0), it is checked whether the execution state information 1104 of the request condition is “executing” (step S701),
If it is not "executing" (step S701: No), the process ends as not being subjected to the timeout control.

On the other hand, when the execution status information 1104 is “executing”
If so, the timer unit 1 based on a preset time interval
It is checked whether or not there is an interrupt from the server 15 (step S702). If there is no interrupt, the process of step S702 is repeated (step S702). If there is an interrupt (Step S702: Yes), the current time is read from the timer unit 115 (Step S703), and the current time and the timeout time 1 added to the request condition are read.
105 (step S704),
It is checked whether or not the timing for performing the timeout process (the current time has exceeded the timeout time) (step S705). As a result, when it is not time to perform the timeout process, the processes of steps S702 to S704 are repeated (step S705: No).

When it is time to perform the timeout process (step S705: Yes), the execution status information 1104 of the request condition is updated to "waiting status" (step S706), and after the timeout recovery time 1106 is added to the request condition. (Step S707), a request to delete the data acquisition setting for the request condition is issued to the request condition setting unit 116 (Step S70).
8). As a result, the acquisition of the data of the request condition is stopped (step S709), and the execution state is substantially changed from “in execution” to “waiting state”.

In the same manner, the request condition setting scheduling unit 113 changes the request condition in the “waiting state”, for which the time-out recovery time has arrived, to the “executable state”. That is, if the execution state information 1104 of the request condition read from the request condition recording unit 114 is “waiting state”, after confirming that the current time has exceeded the timeout resurrection time 1106, the execution state of the request condition is checked. Information 1
104 is updated to an "executable state" and enqueued according to the priorities described above. As a result, the “waiting state” of the request condition is released, and the execution state is substantially changed from the “waiting state” to the “executable state”.

As described above, according to the data acquisition device 110 of the present embodiment, even if the data acquisition request is “executing”, if the data is not acquired within a certain period of time, a timeout occurs. The state is returned to the "executable state" via the "wait state" and is enqueued. This avoids the occurrence of a problem that the hardware resources continue to be occupied unnecessarily because the scheduled broadcast data is not transmitted due to equipment failure or program change at the broadcasting station, and efficient data Acquisition is realized.

Next, among the data acquisition control performed by the data acquisition apparatus 110, the control for transitioning the execution state for the data acquisition request from the “executable state” to the “execution suspended” will be described in detail. Request condition generator 11
2. In addition to generating request conditions corresponding to the new data acquisition request, the request condition recording unit 114 searches the request condition recording unit 114 for existing request conditions that can be combined with the generated request conditions. To generate a new request condition.

More specifically, if the data acquisition conditions 1102 of each of the plurality of request conditions include a common condition, it is determined that the request conditions can be combined, and only the common conditions are used. Create new request condition (the conditions are combined by OR). FIG. 10 is a diagram illustrating a state of the request condition combining unit 112 combining request conditions. Here, a request condition request1 for requesting acquisition of a table with ID1 (for example, table ID) = 0x0001 and ID2 (for example, section number) = 0x01, and ID1 = 0x
0001 and a request condition request2 requesting acquisition of a table with ID2 = 0x02 is combined with ID1 = 0x0001
A new request condition requestA requesting this table is generated.

Here, for example, if it is assumed that any one of ID2 = 0x00 to 0x09 is given to the table with ID1 = 0x0001, the request condition generated by the combination
requestA has 10 types of tables, that is, ID1 = 0x0001
, And a table requesting acquisition of 10 tables of ID2 = 0x00, a table of ID1 = 0x0001 and ID2 = 0x01,..., ID1 = 0x0001 and ID2 = 0x09 It means that it is an acquisition request.

Request condition setting scheduling section 1
13, when the request conditions are combined by the request condition generation unit 112, for each of the original request conditions used for the combination, the execution state is transited to “executable state” via the “executable state” and the “executable state”. For the new request condition generated by the combination, control is performed to change the execution state to “executing” via the “executable state”.

FIG. 11 is a flowchart showing the flow of the request condition combining process by the data acquisition device 110. Upon generating a new request condition (step S600), the request condition generation unit 112 extracts the existing request condition stored in the request condition recording unit 114 (step S601), and extracts the data acquisition condition 1102 of those two request conditions. By comparing (step S602), it is determined whether the two request conditions can be combined (step S603).
If there is no common condition, the combining process is abandoned (step S603: No).

If a common condition exists (step S603: Yes), a new request condition is generated by combining the request conditions (step S604), and stored in the request condition recording unit 114, and A registration request is sent to the condition setting scheduling unit 113 to add the newly generated request condition as a control target (step S60).
5).

Upon receiving the registration request, the request condition setting scheduling unit 113 sets the execution state of the two original request conditions used for the combination to “running”.
If it is, an execution stop request is issued to the data acquisition unit 507 (step S606), and for the request condition for which the registration request has been made, the execution state of the request condition is set to “executed” in order to start data acquisition. Possible state ''
(Step S607).

Then, the request condition setting scheduling unit 113 changes the two original request conditions that have returned to the “executable state” to “executing suspended” (step S608). That is, these request conditions are excluded from data acquisition until the request conditions described below are divided. As described above, according to the data acquisition device 110 in the present embodiment, a plurality of request conditions having a common condition in the data acquisition condition 1102 are logically integrated into one, and the plurality of request conditions are combined. Data acquisition is performed comprehensively in place of. As a result, the number of request conditions set in the data acquisition unit 507 is reduced, so that data acquisition for more data acquisition requests is performed simultaneously under limited hardware resources.

Next, among the data acquisition control performed by the data acquisition apparatus 110, the control for returning the execution state for the data acquisition request from “executing suspended” to the “executable state” will be described in detail. If the request condition setting scheduling unit 113 confirms that the data corresponding to the request condition “executing suspended” due to the combination of the request conditions has not yet been acquired even after a certain time has elapsed, the request condition setting scheduling unit 113 breaks the above-described combination. Control to return to the original state. This is fine if the data corresponding to the original request condition is acquired by the data acquisition by the new request condition generated by the join,
As described above, since the request condition generated by the combination is the same or a loose condition as the original request condition, an inconvenient state may occur in which data corresponding to the original request condition is not obtained forever. .
This is to allow for that.

For this purpose, the request condition generator 112
Generates the request identification information, the request generation time, and the combined request identification information when the request condition is generated, adds the request identification information to the corresponding request condition, notifies the request condition setting scheduling unit 113 of the request condition, records the request condition Or stored in the unit 114. The request condition setting scheduling unit 113 records management information such as data acquisition determination information based on the data acquisition information obtained from the data acquisition unit 507 for each of the request conditions stored in the request condition recording unit 114. Control the data acquisition of each request condition while performing or updating.

Here, “request identification information” is information for identifying each request condition, “request generation time” is the time when the request condition is newly generated, and The “request identification information after” is the request identification information of the request condition generated by the combination when used in the above-described combination, and the “data acquisition determination information” is stored in the request condition recording unit 114. This is information indicating whether or not data has been acquired (“data acquisition completed” or “data acquisition in progress”) for the requested request condition.

FIG. 12 is a diagram showing an example of a list of request conditions to which various management information has been added by the request condition setting scheduling unit 113. Each request condition 1101 includes request identification information 1110, data acquisition condition 1102, request generation time 1111, execution state information 1104, and request identification information 1112 after combination.
And data acquisition determination information 1113.

Here, the request identification information is
The three request conditions of 0x0004,0x0005,0x0008 are:
In each case, the request conditions are combined to generate a request condition with the request identification information of 0x0001, and the status is "suspended" .The data acquisition for the request condition with the request identification information of 0x0001 is continued. Indicates that data with request identification information of 0x0004 has been acquired, but data with request identification information of 0x0005 and 0x0008 has not been acquired yet.

FIG. 13 is a flowchart showing the flow of the process of dividing the request conditions combined by the data acquisition device 110. The request condition setting scheduling unit 113 extracts the original request condition used for the combination from the request condition recording unit 114 (Step S
800), it is checked whether or not the data acquisition determination information 1113 of the original request condition is “unfinished” (not “data acquired”) (step S801). It is determined that it is not present, and is excluded from the target of this processing (step S801: No).

On the other hand, if it is "unfinished" (step S
801: Yes), and confirms whether there is an interrupt from the timer unit 115 set in advance (step S80).
2) If there is no interruption, the processing of step S802 is repeated (step S802: No). If there is an interrupt (step S802: Yes), the current time is extracted from the timer unit 115 (step S803), and the current time is compared with the request generation time 1111 of the request condition (step S804). As a result, it is confirmed whether or not a fixed time has elapsed without acquiring data (step S805). If the fixed time has not elapsed, the processing of steps S802 to S804 is repeated (step S805: No).

If the predetermined time has elapsed (step S8)
05: Yes), in order to divide the combined request condition and restore it, the execution condition information 11 of the request condition
04 is updated to "execution suspended" (step S806),
A request to delete the data acquisition setting of the request condition is issued to the request condition setting unit 116 (step S
807). Furthermore, the execution status information 1 of the original request condition
104 is set to the “executable state” (step S80)
8) At the head of the queue, a request for registration of data acquisition of the original request condition is issued to the request condition setting unit 116 (step S809), and data acquisition is started (step S810).

As a result, for example, the data acquisition corresponding to the request condition whose request identification information is 0x0001 shown in FIG. 12 is changed from “executing” to “executable” through “waiting” and The data acquisition corresponding to the request condition whose identification information is 0x0005 and 0x0008, respectively, is transited from “during execution” to “during execution” via “executable state”.

As described above, according to the data acquisition apparatus 110 of the present embodiment, after the data acquisition request is combined, the data corresponding to the original request condition has not been acquired even after a certain period of time has elapsed. , The connection is released and the state is returned to the data acquisition state according to the original request condition. As a result, it is possible to avoid a problem caused by the combination of the request conditions, that is, a problem that data corresponding to the original request condition is not obtained forever, and efficient data acquisition is realized.

(Embodiment 2) Next, Embodiment 2 of the present invention will be described. FIG. 14 is a functional block diagram showing a configuration of the data acquisition device 120 according to Embodiment 2 of the present invention. The data acquisition device 120 changes the execution frequency of data acquisition in accordance with an instruction from an application. The data acquisition device 120 includes a data acquisition request receiving unit 501, a request condition generating unit 122, a request condition setting scheduling unit 123, It includes a request condition recording unit 114, a timer unit 115, a request condition setting unit 116, a data acquisition unit 507, and a data transmission unit 508. Note that the same components as those of the data acquisition device 110 according to the first embodiment shown in FIG.

In this embodiment, in addition to the data acquisition request, each application sends the data acquisition monitoring state information, which is information for specifying the mode of data acquisition, to the data acquisition device 120 (data acquisition request receiving unit 501). By notifying, data acquisition is requested. Here, the “data acquisition monitoring status information” includes “continuous monitoring acquisition” that continuously performs data acquisition, “intermittent monitoring acquisition” that periodically performs data acquisition at fixed time intervals, and target data. "Observation unnecessary", which is data acquisition that does not perform any further monitoring (attempt to acquire data)
Is information indicating any of the following.

These three aspects are used, for example, as follows depending on the application. In other words, when transmitted, it is obliged to receive the data without overlooking it, and for NITs transmitted at a short frequency, the data acquisition monitoring state information is set to “always monitor acquisition”.
It is not necessary to constantly acquire the data because the data size is large, but it is necessary to repeatedly acquire the data at an appropriate frequency.
For IT, etc., the data acquisition monitoring status information is set to "intermittent monitoring acquisition", and for SDTs, etc., which are repeatedly transmitted at a constant frequency but whose content is updated very infrequently, the data acquisition monitoring status information is set to "monitoring unnecessary acquisition". Then, the data acquisition device 120 (data acquisition request receiving unit 501) is requested to acquire data.

The request condition generation unit 122 generates a request condition to which data acquisition monitoring state information is added for each set of the data acquisition request and the data acquisition monitoring state information passed from the data acquisition request receiving unit 501. Request condition setting scheduling unit 1
23, or stored in the request condition recording unit 114.

FIG. 15 is a diagram showing an example of a list of request conditions generated by the request condition generator 122. Here, 8 generated in accordance with the order of generation of the data acquisition requests
Request conditions are shown. Each request condition 1201 includes a data acquisition condition 1102 and data acquisition monitoring status information 1202. The request condition setting scheduling unit 123 controls the acquisition of data corresponding to the request condition generated by the request condition generating unit 122 by communicating with each component, and therefore, the request condition recording unit 1
14 to monitor and manage the data acquisition status for each request condition, and to obtain data corresponding to the newly generated request condition by using the data acquisition monitoring status information 12.
02 is controlled so as to be performed in the mode specified by the user.

FIG. 16 shows the request condition setting scheduling section 12 for the request condition shown in FIG.
3 shows a state of data acquisition control, that is, a state in which data acquisition is performed by scheduling in a certain procedure for each monitoring state specified by the data acquisition monitoring state information 1202. Here, request conditions belonging to the same data acquisition monitoring state information 1202 are summarized.

Request condition setting scheduling section 1
23, the request condition of “always monitoring acquisition”, once set to “running”, keeps the state unless an explicit command such as deletion from another application is received, and “intermittent monitoring”. As for the request condition of "acquisition", the transition from "executing" to "executing" via "waiting state" and "executable state" in a fixed time cycle is repeated. After the target data is once obtained, control is performed so that the state is changed from “in execution” to “deletion state”.

Next, the operation of the data acquisition device 120 configured as described above will be described. FIG. 17 is a flowchart showing the flow of the entire data acquisition process by the data acquisition device 120. The data acquisition request receiving unit 501 receives the new data acquisition request and the data acquisition monitoring status information 1202 corresponding to each data acquisition request and passes them to the request condition generation unit 122 (Step S400).

The request condition generating unit 1 that receives the data acquisition request and the data acquisition monitoring status information 1202
22 generates request conditions corresponding to each data acquisition request (step S401), adds the corresponding data acquisition monitoring state information 1202 to each generated request condition, and stores them in the request condition recording unit 114. Together with the request condition setting scheduling unit 12
3 is notified (step S402).

Request condition setting scheduling section 1
23 checks whether or not the data acquisition monitoring status information 1202 for the notified request condition is “always monitor acquisition” (step S403). (Step S404). In particular,
The request condition is set in the data acquisition unit 507 via the request condition setting unit 116, and the setting is maintained until any explicit deletion instruction is received.

Subsequently, the request condition setting scheduling unit 123 determines that the data acquisition monitoring status information 1202 is not “continuous monitoring acquisition” (step S403: N).
o), it is confirmed whether the received data acquisition monitoring status information 1202 is "intermittent monitoring acquisition" (step S405),
If “intermittent monitoring acquisition” (step S405: Ye)
s) Control is performed so as to periodically acquire data (step S406). Specifically, the request conditions
Data acquisition unit 50 via request condition setting unit 116
After setting the request condition to 7, the timer unit 115 monitors the elapse of a certain period of time, so that the request condition that has been “executing” for a certain period of time is forcibly transited to the “waiting state”, and then for a further certain period of time. After the time elapses, the control of transitioning to “executing” via the “executable state” is repeated.

Further, the request condition setting scheduling unit 123 determines that the data acquisition monitoring status information 1202 is not “intermittent monitoring acquisition” (step S 405: N
o), it is checked whether the received data acquisition monitoring state information 1202 is "monitoring unnecessary acquisition" (step S407),
If “obtain unnecessary” (Step S407: Ye
s) Control is performed so as to acquire data only once (steps S408 to S409).

That is, the request condition setting scheduling unit 123 waits for an interruption from the timer unit 115 at a preset time interval (step S408), and when the interruption occurs (step S40).
8: Yes), the request condition is scheduled, and data is acquired irregularly (step S409).
Specifically, after the request condition is set in the data acquisition unit 507 via the request condition setting unit 116, by monitoring the acquisition state in the data acquisition unit 507, data corresponding to the request condition is obtained. When it is detected that the acquired data has been returned, the request condition is deleted from the request condition recording unit 114.

If the data acquisition monitoring state information 1202 is not "monitoring unnecessary" (step S407: N
o), request condition setting scheduling section 123
Is not applicable to any of the scheduled monitoring states, and ends without further controlling the data acquisition. As described above, according to the data acquisition device 120 in the present embodiment, data acquisition is performed in accordance with the monitoring state requested by the application. There is no need to adjust the frequency or timing of the issuance.

Further, it is possible to avoid a problem that the same type of data acquisition request is repeatedly issued, and to obtain detailed data according to the size (band) of transmission data, transmission frequency, necessity of reception, and the like. With the limited hardware resources, the amount of data that can be acquired per unit time is improved. Next, of the data acquisition control performed by the data acquisition device 120, the details of the control (transition from “waiting state” to “executable state”) for the request condition in which the data acquisition monitoring state information 1202 is “monitoring unnecessary acquisition” will be described in detail. Will be described.

Request condition setting scheduling unit 1
Reference numeral 23 denotes a request condition in which the data acquisition monitoring status information 1202 is “monitoring unnecessary acquisition” and the execution status information 1104 is “waiting status”, and monitors whether a timeout recovery time has arrived. Performs control to transition to “executing” via the “executable state”.
Therefore, the request condition setting scheduling unit 1
23 records and updates not only the data acquisition monitoring state information 1202 but also management information such as execution state information and timeout recovery time for each of the request conditions stored in the request condition recording unit 114. While controlling the data acquisition of each request condition.

FIG. 18 is a diagram showing an example of a list of request conditions to which various types of management information have been added by the request condition setting scheduling unit 123. Each request condition 1201 includes a data acquisition condition 1102, data acquisition monitoring status information 1202, execution status information 1104, and a timeout recovery time 1106. Here, for example, in the request condition in which the data acquisition condition 1102 is “request2”, the data acquisition monitoring status information 1202 is “monitoring unnecessary acquisition” and the execution status information 1104
Is in the “waiting state” and the time-out recovery time 1106
(1999/4/1 1:00:50) indicates that it should be returned to the “executable state”.

FIG. 19 shows the data acquisition monitoring status information 1202 out of the data acquisition control by the data acquisition device 120.
13 is a flowchart showing a flow of control (transition from a “waiting state” to an “executable state”) for a request condition for which “monitoring is unnecessary”. When the request condition setting scheduling unit 123 receives from the request condition generation unit 122 a notification that the request condition based on the data acquisition request issued by the application is generated (step S900), the data acquisition monitoring state added to the request condition It is checked whether or not the information 1202 is "monitoring unnecessary acquisition" (step S901).
01: No).

If “monitoring unnecessary” (step S9)
01: Yes), execution status information 110 of the request condition
It is confirmed whether or not No. 4 is in the "waiting state" (step S902). If not, the processing ends as a target of the processing (step S902: No). If it is in the “waiting state” (step S902: Yes), the current time is extracted from the timer unit 115 (step S9).
03), request condition timeout recovery time 110
6 is compared with the current time (step S904). By this, it is confirmed whether it is time to re-execute the timed out request condition (step S
905), if it is not time to re-execute the process, the process is terminated and the process ends (step S905: No).

If it is time to re-execute (step S905: Yes), the execution state information 1104 of the request condition is set to "executable state" (step S9).
06), when the queue is at the head of the queue, a request for registration of data acquisition setting for the request condition is issued to the request condition setting unit 116 (step S907).
Data acquisition is started (step S908).

As described above, according to the data acquisition apparatus 120 of the present embodiment, a data acquisition request whose data acquisition monitoring state information is “monitoring unnecessary acquisition” is changed from “in execution” to “waiting state” due to timeout. ”And then, after a certain period of time,
And is restored to “in progress”, and data acquisition is repeatedly attempted. As a result, even when the target data is not transmitted, inefficient data acquisition in which hardware resources are occupied unnecessarily is avoided.

Next, of the data acquisition control by the data acquisition device 120, the control for the request condition in which the data acquisition monitoring state information 1202 is “monitoring unnecessary acquisition” (transition between “executable state” and “executing”) ) Will be described in detail. The request condition setting scheduling unit 123 determines that the request condition in which the data acquisition monitoring status information 1202 is “monitoring unnecessary acquisition”
If there is a request condition that is “executing” and “data has been acquired”, the request condition has a higher priority than the priority of the request condition, is in an “executable state”, and has “data”. It searches for request conditions that are not "acquired", and if found, performs control to replace the execution states of those request conditions.

For this purpose, the request condition setting scheduling unit 123 performs, for each of the request conditions stored in the request condition recording unit 114, not only the data acquisition monitoring status information and the execution status information but also the data acquisition determination information, the priority, and the like. The acquisition of the data of each request condition is controlled while adding or recording the management information of the request.

FIG. 20 is a diagram showing an example of a list of request conditions to which various types of management information have been added by the request condition setting scheduling unit 123. Each request condition 1201 includes a data acquisition condition 1102, data acquisition monitoring status information 1202, execution status information 1104, data acquisition determination information 1113, and priority 1103.

Here, for example, the data acquisition condition 110
The request condition “executing” in which the request 2 is “request3” is a data acquisition condition 1102 having a higher priority.
It indicates that the request condition is in the “executable state” in which “request6” is set, and the execution state is in a state to be replaced. FIG. 21 shows the data acquisition monitoring status information 1 in the data acquisition control by the data acquisition device 120.
Control for a request condition for which 202 is "monitoring unnecessary" (transition from "waiting state" to "executable state")
It is a flowchart which shows the flow of.

Request condition setting scheduling section 1
23 fetches an arbitrary request condition from the request condition recording unit 114 (step S1000), and confirms whether the data acquisition monitoring status information 1202 of the request condition is “monitoring unnecessary acquisition” (step S10).
01), if it is not “monitoring unnecessary”, the process ends as being out of the processing target (step S1001: No).

If “monitoring unnecessary” (step S1)
001: Yes), and confirms whether the execution state information 1104 of the request condition is “executing” (step S1002). No). If “executing” (step S1002: YES), it is checked whether the data acquisition determination information 1113 of the request condition is “data acquired” (step S100).
3) If the data is not “acquired”, the processing is not performed and the process ends (step S1003: NO).

If the data has been acquired (step S1)
003: Yes), the request condition recording unit 114 checks whether there is a request condition having a higher priority than the priority 1103 of the request condition (step S1004). Terminates as not existing (step S10)
04: No).

If there is a request condition having a higher priority (step S1004: YES), the request condition is retrieved from the request condition recording unit 114 (step S1005), and the data acquisition monitoring status information 1202 of the retrieved request condition is It is confirmed whether or not it is “monitoring unnecessary acquisition” (step S1006). If it is not “monitoring unnecessary acquisition” (step S1006: No), it is determined that the execution state is not a target to be replaced, and the process ends.

If “monitoring unnecessary” (step S1)
006: Yes), and confirms whether or not the execution state information 1104 of the request condition is “executable state” (step S1007). (Step S1007: No). When it is in the “executable state” (step S1007: Yes), the execution state information 1104 of the request condition is set to “executing” (step S1008), and the request condition setting unit 116 obtains data for the request condition. By issuing a setting registration request (step S1009), data acquisition for the request condition is started (step S1010).

The execution status information 1104 of the “executing” request condition that has already been extracted is returned to the “executable state” (step S1011), and the request condition setting unit 116 obtains the data of the request condition. By issuing a setting deletion request (step S10
12), the data acquisition for the request condition is stopped (step S1013).

As described above, according to the data acquisition device 120 of the present embodiment, when there is a request condition that is “executing” in spite of “data acquisition completed”, The request condition in the “executable state” having a higher priority than the request condition is replaced with the execution state. As a result, it is possible to prevent a problem that the acquisition of high-priority data is not started until a low-priority data acquisition is repeated, and efficient data acquisition is realized.

(Embodiment 3) Next, Embodiment 3 of the present invention will be described. FIG. 22 is a functional block diagram showing a configuration of the data acquisition device 130 according to Embodiment 3 of the present invention. The data acquisition device 130 is a data acquisition device that performs data acquisition time-out processing according to the type of data acquisition request from an application. It comprises a condition setting scheduling unit 133, a request condition recording unit 114, a timer unit 115, a request condition setting unit 116, a data acquisition unit 507, and a data transmission unit 508. In addition,
Data acquisition device 1 according to Embodiment 1 shown in FIG.
The same components as those in 10 are denoted by the same reference numerals, and the following description focuses on the differences.

The request condition generating unit 132 determines the timeout time based on the header information included in the data acquisition request passed from the data acquisition request receiving unit 501, in addition to generating the request condition. Add to condition. Note that the timeout time in the present embodiment is used for forcibly transiting the request condition being “executing” to “waiting state” and then transiting to “deletion state”.

FIG. 23 is a diagram showing an example of a list of request conditions generated by the request condition generator 132. Here, six request conditions generated according to the order of generation of the data acquisition requests are shown. Each request condition 1301 includes header discrimination information 1302, which is identification information indicating the type of the data acquisition request constituting the header information, a data acquisition condition 1102, and a timeout time 1303.

The request condition generating unit 132
If the header discrimination information 1302 indicates a request for acquiring a table of high importance such as NIT, a relatively short time (for example,
When the header determination information 1302 indicates a request to acquire a table of low importance such as SDT, the time when 10 seconds has elapsed is set as the timeout time. The time when a long time (for example, 30 seconds) has elapsed is added as a timeout time.

Request condition setting scheduling section 1
33 communicates with each component to collectively control data acquisition corresponding to the request condition generated by the request condition generation unit 122. For this purpose, each request is recorded using the request condition recording unit 114. In addition to monitoring and managing the data acquisition status of the condition, for the request condition to which a timeout time has been added by the request condition generation unit 132, a timeout occurs when the data acquisition is started and becomes “executing”. It monitors whether the time has arrived, and when it arrives, the request condition is transited from “in execution” to “deletion state” via “waiting state”.

Next, the operation of the data acquisition device 130 configured as described above will be described. FIG. 24 is a flowchart showing the flow of the generation of the timeout time and the timeout process by the data acquisition device 130, that is, the flow of the process of transitioning the data acquisition state of “executing” to the “waiting state”. The data acquisition request receiving unit 501 receives a data acquisition request including header information from each application and passes it to the request condition generation unit 132 (Step S50).
0).

The request condition generating unit 132 outputs the header information of the new data acquisition request passed from the data acquisition request receiving unit 501 and the header discrimination information 130 of all the request conditions already stored in the request condition recording unit 114.
By comparing the header determination information 1302 with the header information of the new data acquisition request (step S501), it is determined whether or not the header identification information 1302 already held has the same header information as that of the new data acquisition request.

As a result, if there is not the same one (step S502: No), a new request condition is generated without providing a time-out time, and the same processing as a normal new data acquisition request is performed. Part 1
14 and notify the request condition setting scheduling unit 133. As a result, the request condition setting scheduling unit 133 puts the request condition into the queue of the “executable state” and starts the data acquisition control.

On the other hand, the header discrimination information 1 already held
If there is the same header information of the new data acquisition request in 302 (step S502: Yes), it is recognized that duplicate data acquisition requests have been issued continuously, and the request condition generation unit 132 After the request condition is generated and stored in the request condition recording unit 114 (step S503), a timeout time corresponding to the type of the data acquisition request determined by the header determination information 1302 is set for the generated new request condition. It is added (step S504).

For such a request condition,
The request condition setting scheduling unit 133, after temporarily transiting to “executing”, requests the request condition recording unit 1
By referring to the timer 14 and the timer unit 115, the timeout time added to the request condition is compared with the current time, and it is confirmed whether it is time to timeout (step S505).

If it is not time to time out, the process of step S505 is repeated (step S505: N
o). When the time-out time has arrived (step S5
05: Yes), the execution state of the request condition is forcibly changed from “executing” to “waiting state” (step S506), and then is changed to “deletion state” (step S507). Specifically, the request condition setting scheduling unit 133 issues a request to delete the data acquisition setting for the request condition to the request condition setting unit 116 (step S507), and stores the request condition from the request condition recording unit 114. The data acquisition is stopped by deleting the data (step S50).
8).

As described above, according to data acquisition apparatus 130 of the present embodiment, it is determined whether a data acquisition request has been issued repeatedly based on header information included in a data acquisition request requested by an application. Is determined,
If they are issued in duplicate, data acquisition is performed only for a certain period of time. As a result, even when an application repeatedly issues a data acquisition request because the frequency at which target data is transmitted is extremely low, data acquisition for obtaining such data with a low transmission frequency can be performed. The occurrence of a problem that hardware resources are occupied by data acquisition processing for a request is prevented, and efficient data acquisition is realized.

(Embodiment 4) Next, Embodiment 4 of the present invention will be described. FIG. 25 is a functional block diagram showing a configuration of the data acquisition device 140 according to Embodiment 4 of the present invention. By referring to the version information included in the transmitted data, the data acquisition device 140 determines that the version update count is the maximum for the “executable state” request condition in which the priority and the data acquisition state are the same. A data acquisition device characterized by acquiring data with priority given to data requesting,
Data acquisition request receiving unit 501, request condition generating unit 1
12, the request condition setting scheduling unit 143,
It includes a request condition recording unit 114, a timer unit 115, a request condition setting unit 116, a data acquisition unit 507, and a data transmission unit 508. Note that the same components as those of the data acquisition device 110 according to the first embodiment shown in FIG.

In the present embodiment, it is assumed that the header section of the data acquired by the data acquisition section 507 contains version information. Here, the “version information” is information for specifying a version attached to each transmitted data unit (for example, a table or the like), and even if the data units have the same identification information, If it is different, it means that the content is different (revised).

When the request condition setting unit 116 receives the request condition setting, the data acquisition unit 507 also receives request identification information for specifying the request condition, and obtains the data acquisition status based on the request identification information. Etc., and output them to the outside. The request condition setting scheduling unit 143 controls the acquisition of data corresponding to the request condition generated by the request condition generation unit 122 by communicating with each component, and uses the request condition recording unit 114. In addition to monitoring and managing the data acquisition status for each request condition,
The request condition recording unit 114 adds and updates information on the version of each request condition. For a request condition in the “executable state” in which the priority and the data acquisition state are the same, the version update frequency of the request data is the maximum. Is controlled so as to give priority to “executing”.

For this purpose, the request condition setting scheduling unit 143 determines, for each of the request conditions stored in the request condition recording unit 114, request identification information, data acquisition condition, data acquisition monitoring state information, execution state information, data acquisition judgment Data acquisition of each request condition is controlled while adding and recording not only information and priority but also management information such as version information, version update determination information and version update count information, and the like.

Here, the “version update determination information” indicates whether or not the requested data has been updated at least once (“updated” or “not updated”) since the request condition was generated. Information.
“Version update count information” is information indicating the number of updates. FIG. 26 is a diagram illustrating an example of a list of request conditions to which various types of management information have been added by the request condition setting scheduling unit 143. Each request condition 1401 includes request identification information 1110, data acquisition condition 1102, data acquisition monitoring status information 120
2, execution status information 1104, data acquisition determination information 111
3, priority 1103, version information 1402, version update determination information 1403, version update count information 1404, and the like.

Here, for example, the request identification information 1
Regarding the two request conditions where 110 is 0x0006 and 0x0007, the data acquisition monitoring status information 1202 is “monitoring unnecessary acquisition”, the execution status information 1104 is “executable status”, and the data acquisition monitoring status information 1104 is “executable status”. Judgment information 1
It is shown that 113 and the priority 1103 have the same contents, but the version update count information 1403 is different.

Next, the operation of the data acquisition device 140 configured as described above will be described. FIG. 27 is a flowchart showing the flow of processing related to the version of the received data in the data acquisition control by the data acquisition device 140. Request condition setting scheduling unit 143
Receives the data request identification information and the acquired data from the data acquisition unit 507 (step S110).
0), the version information included in the header information of the data is extracted (step S1101), and it is confirmed whether or not the request condition recording unit 114 has a request condition corresponding to the currently received request identification information (step S1102). If there is no corresponding request condition, the process ends (Step S1102: No).

If there is a corresponding request condition (step S1102: YES), the version information is added to the request condition as version information 1401 (step S1103), and new version update determination information 1402 and version update number information 14
03 is generated / updated and added to the request condition (step S1104), and the request condition is registered in the request condition recording unit 114 (step S110).
5).

Further, from the request condition recording unit 114,
An optional request condition is extracted (step S110)
6), data acquisition monitoring status information 1 of the request condition
It is confirmed whether or not 202 is “monitoring unnecessary acquisition” (step S1107). If it is not “monitoring unnecessary acquisition”, the process of step S1106 is repeated (step S110).
7: No).

If “monitoring unnecessary” (step S1)
107: Yes), it is confirmed whether or not the execution state information 1104 of the request condition is “executable state” (step S1108). If not, the processing of steps S1106 to S1107 is repeated (step S1108). S1108: No). If it is “executable state” (step S1108: YES), it is checked whether the priority 1103 of the request condition is the same as the priority 1103 of the already extracted request condition (step S1109). Step S11
06 to S1108 are repeated (step S110)
9: No).

If the priorities 1103 are the same (step S1109: YES), it is checked whether the data acquisition judgment information 1113 of the request condition is the same as the data acquisition judgment information 1113 of the already extracted request condition (step S1109: Yes). If not the same (step S1110), the process ends (step S1110: No). If the data acquisition determination information 1113 is the same (step S1110: Ye
s), it is checked whether the version update count 1403 of the request condition is the maximum (step S1111),
If it is not the maximum, the processes of steps S1106 to S1110 are repeated (step S1111: No).

If the version update count information 1403 is the maximum (step S1111: YES), a request to register data acquisition settings for the request condition is issued to the request condition setting unit 116 (step S1112). Start acquisition (step S
1113). As a result, for example, if two request conditions in which the request identification information 1110 shown in FIG. 26 is 0x0006 and 0x0007 are compared, data acquisition for the large request condition 0x0006 of the version update frequency information 1403 is not performed. Be started.

As described above, according to data acquisition apparatus 140 of the present embodiment, the version of data requested by each application is updated at any frequency by referring to the version information included in the transmitted data. Is recorded. Then, as for the request conditions in the “executable state” having the same data acquisition state and priority, the one that requests the data whose version is updated most frequently is given the highest priority and the data acquisition is started. . As a result, data whose contents change frequently is preferentially acquired, so that it is possible to avoid the occurrence of a problem that hardware resources are wastefully occupied by repeatedly acquiring data of the same contents, which is efficient. Data acquisition is realized.

(Embodiment 5) FIG. 30 shows Embodiment 5 of the present invention.
2 is a functional block diagram showing a configuration of a data acquisition device 200 in FIG. The data acquisition device 200 includes information for specifically specifying data to be acquired, which is issued from a plurality of data processing devices (this device also includes an application realized by software; hereinafter, simply referred to as an “application”). Receiving the data acquisition request (hereinafter referred to as an acquisition condition), and storing and managing the received acquisition conditions in a table in order, and in response to a request to replace the acquisition condition from the application, obtains the acquisition condition stored in the table. A data acquisition device that controls the exchange of conditions in order and efficiently acquires data in accordance with the exchanged order. Specifically, a digital broadcast receiver receives, demultiplexes, and decodes broadcast data.・
It corresponds to a hardware and software part for performing basic processing related to reception such as filtering, and includes an acquisition condition receiving unit 201, a data acquisition unit 507, a data transmission unit 508, an acquisition condition storage unit 202, an acquisition condition replacement request unit 203, and an acquisition It comprises a condition setting scheduling unit 204. The same components as those of the data acquisition device 110 according to the first embodiment shown in FIG.
Hereinafter, differences will be mainly described.

The acquisition condition receiving unit 201 receives the acquisition condition requested from each application, and passes the received acquisition condition to the acquisition condition scheduling unit 204. The data acquisition unit 507 includes an acquisition condition setting scheduling unit 204
When the acquisition condition is set by the acquisition condition setting unit 204, the reception of the data satisfying the acquisition condition is continuously monitored unless the acquisition condition is deleted by the acquisition condition setting scheduling unit 204. Perform the extraction.

[0118] The data transmitting unit 508 is
Receiving the data acquired in step 7,
A request source application is specified by referring to the acquisition conditions and the like stored in the application 2 and the acquired data is returned to the application. The acquisition condition storage unit 202 stores an acquisition condition, setting information, and an order value as a set in a table. Here, the “setting information” refers to information indicating whether the stored acquisition conditions are set in the data acquisition unit 507 by “valid” and “invalid”. "Valid" indicates that the acquisition condition is set in the data acquisition unit 507, and "Invalid" indicates that the acquisition condition is not set in the data acquisition unit 507. The “order value” is a value corresponding to the order in which the acquisition conditions are received by the acquisition condition receiving unit 201. When the acquisition conditions are received and newly stored in the table by the acquisition condition setting scheduling unit 204, An initial value 0 indicating that the receiving order is the latest is added to the acquisition condition, and after that, other acquisition conditions are stored in the table, and the acquisition condition exchange request unit 203 requests the acquisition condition exchange. When a set of acquisition conditions whose setting information indicates “invalid” is stored in the acquisition condition storage unit 202 at the time or when an acquisition condition that succeeds in data extraction is notified (described later in Embodiment 6), After the acquisition condition is set in the data acquisition unit 507 by the acquisition condition setting scheduling unit 204 and the setting of the acquisition condition is deleted, the value is returned to the initial value 0 again. It refers to the value.

The acquisition condition replacement requesting unit 203 prepares the timing of replacement of the acquisition condition set in the data acquisition unit 507, and requests the acquisition condition setting scheduling unit 204 to replace the acquisition condition in accordance with a request from the application. do. Note that the acquisition condition replacement request unit 203 may make a replacement request according to a periodic notification such as a timer.

Acquisition condition setting scheduling section 203
Comprises a CPU and a ROM storing a control program, and monitors the registration information and the order value of each data acquisition condition stored in the table of the acquisition condition storage unit 202, thereby obtaining the data acquisition unit 507 of each acquisition condition. Is set, and the exchange of the data acquisition conditions set in the data acquisition unit 507 is controlled in accordance with the acquisition condition exchange request from the acquisition condition exchange request unit 203.

Acquisition condition setting scheduling section 204
When the data acquisition condition is passed from the acquisition condition receiving unit 201, the order value of each acquisition condition already stored in the table of the acquisition condition storage unit 202 is incremented by 1, and then the data acquisition unit 507 is notified. The total number of sets of acquisition conditions (acquisition conditions set in the data acquisition unit 507) in which the setting information stored in the table indicates "valid" is determined by the data acquisition unit 507 as to whether or not the acquired acquisition conditions can be set. Upper limit for which acquisition conditions can be set (here, three for convenience of explanation)
It is determined by whether or not it is less than. If the total number of sets of acquisition conditions for which the setting information indicates "valid" is less than three, the received acquisition conditions are stored in a table of the acquisition condition storage unit 202, the registration information is validated, and the order value is initialized to the initial value. The value is set to 0, and the received acquisition condition is registered in the data acquisition unit 507.
If the total number of sets of acquisition conditions for which the setting information indicates "valid" is 3, the received acquisition conditions are stored in a table of the acquisition condition storage unit 202, the setting information is set to "invalid", and the order value is initialized. Set to the value 0.

In addition, in response to the acquisition condition replacement request, the order value of the acquisition condition already stored in the table of the acquisition condition storage unit 202 is incremented by one, and subsequently, the data acquisition unit 507
Replaces the acquisition conditions registered in. Hereinafter, FIG.
1. The processing performed by the acquisition condition setting scheduling unit 204 to schedule the setting of the acquisition condition received from the application in the data acquisition unit 507 will be described with reference to the flowchart in FIG.

FIG. 31 is a flowchart showing a process for storing the acquisition conditions received from the application in the table of the acquisition condition storage unit 202. Upon receiving the acquisition condition from the acquisition condition receiving unit 201 (step S1201), the acquisition condition setting scheduling unit 204 determines whether one or more acquisition conditions are stored in the table of the acquisition condition storage unit 202 (step S1202). If it is stored (step S1202: Y), its order value is increased by 1 (step S1203), and if it is not stored (step S1202: N).
Does not increase the order value.

Next, the acquisition condition setting scheduling section 20
4 is a data acquisition unit 50 based on whether the total number of acquisition condition sets whose setting information indicates “valid” is less than 3 among the acquisition condition sets already stored in the table of the acquisition condition storage unit 202.
It is determined whether the acquisition condition can be set in step 7 (step S1).
204), if setting is possible (step S1204: Y),
The received acquisition condition is stored in the table of the acquisition condition storage unit 202, and the setting information paired with the acquisition condition is set to “valid”,
The order value is set to the initial value 0, and the acquisition condition is set in the data acquisition unit 507 (step S1205). If it is not possible to set the acquisition condition in the data acquisition unit 507 (step S1204: N), the received acquisition condition is stored in the acquisition condition storage unit 20.
2, the setting information of the received set of acquisition conditions is set to "invalid", and the order value is set to the initial value 0 (step S1).
206), wait until the next acquisition condition is received, and upon receipt, repeat the above processing.

FIG. 32 is a flowchart showing a process in which the acquisition condition setting scheduling unit 204 sets the acquisition conditions stored in the table of the acquisition condition storage unit 202 in the data acquisition unit 507. Acquisition condition schedule part 2
When the acquisition condition exchange request unit 203 requests the acquisition condition exchange request (step S1301), the acquisition condition storage unit 2
02 of the set of acquisition conditions stored in the table No. 02
It is determined whether there is a set of acquisition conditions whose setting information indicates “invalid” (step S1302). If there is no set of acquisition conditions whose setting information indicates “invalid” (step S1302: N), the input of the acquisition condition is performed. Since the exchange is not required, the process waits for the next acquisition condition exchange request, and repeats the above processing unless a set of data acquisition conditions whose setting information indicates “invalid” is stored in the table.

If a set of data acquisition conditions whose setting information indicates "invalid" is stored (step S1302: Y), the order of all sets of data acquisition conditions stored in the table of the acquisition condition storage unit 202 Increment the value by 1 (step S130
3) Depending on whether the total number of data acquisition condition sets whose setting information indicates “valid” is less than 3 among the data acquisition condition sets stored in the table of the acquisition condition storage unit 202, It is determined whether a new data acquisition condition can be set in the acquisition unit 507 (step S1304).

If it is not possible to set the acquisition condition in the data acquisition unit 507 (step S1304: N), the table of the acquisition condition storage unit 202 indicates that the setting information is “valid” and the order value is the largest. Select an acquisition condition and set the data acquisition unit 50
7, the setting of the selected acquisition condition is deleted, the setting information of the selected set of acquisition conditions stored in the table is set to "invalid", and the order value is set to the initial value 0 (step S130).
Five). Next, from the table, the setting information is "invalid" and
The data acquisition condition of the set having the largest order value is selected, the setting information of the set is set to “valid”, the order value is set to the initial value 0 (step S1306), and the selected acquisition condition is set to the data acquisition unit 507.
Set to.

If the acquisition condition can be set in the data acquisition unit 507 (step S1304: Y), the acquisition condition of the set whose setting information is “invalid” and the order value is the largest is selected from the table, and The setting information of the group is set to “valid”, the order value is set to the initial value 0 (step S1306), and the selected acquisition condition is set to the data acquisition unit 507. The above processing (step
S1301 to S1306) will be described with further specific examples.

FIG. 33 shows an example of a table in the acquisition condition storage unit 202 storing sets of acquisition conditions, setting information, and order values. FIG. 33 shows that six acquisition conditions 1 to 6 are stored in a table, and among them, acquisition conditions 1 to 3 are set in the data acquisition unit 507. FIG. 34 illustrates an example of the table in FIG. 33 updated by the acquisition condition setting scheduling unit 204 performing the above processing. In the table of FIG. 33, the acquisition conditions 4 to 6 indicating that the setting information indicates “invalid” are stored (step S1302: Y).
The acquisition condition setting scheduling unit 204 increments the order value of each set stored in the table by one, and since the total number of acquisition conditions whose setting information indicates “valid” is three, the data acquisition unit 507 It is determined that the setting of the acquisition condition is impossible (step S1304: N), and the data acquisition condition 1 of the set whose setting information is “valid” and the order value is the largest is selected from the table of FIG. Acquisition condition 1 from 507
Setting is deleted and the acquisition condition 1 stored in the table
Is set to "invalid" and the order value is set to the initial value 0 (step S1305). Next, from the table, the acquisition condition 4 of the set whose setting information is “invalid” and the sequence value is the largest is selected, the setting information of the acquisition condition 4 is set to “valid”, and the sequence value is set to the initial value 0 (step S1306), the selected acquisition condition 4 is set in the data acquisition unit 507. As a result of this processing, FIG.
The table shown in FIG. 3 is updated as shown in FIG.

Next, the acquisition condition setting scheduling unit 2
The processing performed by the data acquisition unit 507 after the acquisition conditions have been set in the data acquisition unit 507 in step 04 will be described. FIG. 35 is a flowchart illustrating a process performed by the data acquisition device 200 after the acquisition condition is set in the data acquisition unit 507. Upon receiving the data (step S1401), the data acquisition unit 507 determines whether the received data satisfies the set acquisition condition (step S140).
2) If the acquisition condition is satisfied (step S1402: Y), the data is extracted (step S1403). If the acquisition condition is not satisfied (step S1402: N), the above determination is continued until data satisfying the acquisition condition is received (step S1402).
1402). The data acquisition unit 507 passes the extracted data to the data transmission unit 508, and the data transmission unit 508 specifies the request source application by referring to the acquisition conditions and the like stored in the acquisition condition storage unit 202, and specifies the request source application. Transmit the acquired data (step S140
Four).

In the present embodiment, if the acquisition condition received in the data acquisition unit 507 cannot be set in step S1206 in FIG. 31, the acquisition condition is not set in the data acquisition unit 507, and the The acquisition condition is stored in the table of the acquisition condition storage unit 202, and the setting information of the received acquisition condition set is set to “invalid” and the order value is set to the initial value 0. Instead of step S1206, the acquisition condition storage unit From the table 202, a set of acquisition conditions whose setting information is “valid” and the order value is the largest is selected, the setting of the acquisition condition selected from the data acquisition unit 507 is deleted, and the selected acquisition condition stored in the table is selected. Step S1207 of setting the setting information of the set of acquisition conditions to “invalid” and setting the order value to the initial value 0
Is inserted into the flowchart of FIG. 31. After this step, the received acquisition condition is stored in the table of the acquisition condition storage unit 202, the setting information of the set of the data acquisition condition is enabled, and the order value is set to the initial value 0. Then, it may be set in the data acquisition unit 507 (step S1205). FIG. 36 shows a flowchart in this case. Steps S1201 to S1205 other than step S1207 are the same as those in the flowchart of FIG. 31, and therefore, description of these steps will be omitted.

As a result, the data acquisition is preferentially executed as soon as the acquisition condition requested by the application is received, so that the response to the request from the application can be expedited. As described above, according to the data acquisition device 200 of the present embodiment, it is possible to receive more acquisition conditions than the number of actual acquisition conditions that can simultaneously extract and monitor data. Also, by giving a timing for changing the acquisition conditions, it is possible to automatically adjust the schedule for data extraction and monitoring using all the acquisition conditions.

(Embodiment 6) FIG. 37 is a functional block diagram showing a configuration of a data acquisition device 300 according to Embodiment 6. The data acquisition apparatus 300 receives acquisition conditions issued from a plurality of applications, stores and manages the received acquisition conditions in a table in order, and, at the timing of successful data acquisition, obtains the acquisition conditions stored in the table. A data acquisition device characterized by performing a permutation of the order and efficiently acquiring data in accordance with the permuted order, and specifically, receiving, demultiplexing, decoding, filtering, and the like of broadcast data in a digital broadcast receiver. It is equivalent to a hardware and software part for performing basic processing related to reception of the data, and includes an acquisition condition receiving unit 201, a data acquisition unit 507, a data transmission unit 508, an acquisition condition storage unit 202, and an acquisition condition setting scheduling unit 204. Note that the same components as those of the data acquisition device 200 according to the fifth embodiment illustrated in FIG. 30 are denoted by the same reference numerals, and the following description focuses on the differences.

Acquisition condition setting scheduling section 204
When receiving the notification of the acquisition condition that the data has been successfully extracted from the data acquisition unit 507, the acquisition condition storage unit 202
If there is a set of acquisition conditions in which the setting information stored in the table indicates “invalid”, the order values of all the sets stored in the table are incremented by 1, and the data acquisition unit 507 newly adds It is determined whether or not the setting is possible. If the setting is possible, a new acquisition condition is set. If the setting is not possible, the set acquisition condition is replaced.

The processing performed by the acquisition condition scheduling unit 204 to schedule the setting of the acquisition condition received from the application will be described below with reference to the flowcharts of FIGS. FIG. 31 has been described in the fifth embodiment, and a description thereof will not be repeated. FIG. 38 shows an acquisition condition setting scheduling unit 204.
9 is a flowchart showing a process for setting an acquisition condition stored in a table of the acquisition condition storage unit 202 in the data acquisition unit 507. Acquisition condition setting scheduling unit 2
When receiving the notification of the acquisition condition that the data has been successfully extracted from the data acquisition unit 507 (step S1501), the setting information “invalid” of the set of acquisition conditions stored in the table of the acquisition request storage unit 202 is “invalid”. It is determined whether there is a set of acquisition conditions indicating "" (step S1502). If there is no set of acquisition conditions indicating that the setting information is "invalid" (step S1)
502: N) Since the replacement of the acquisition conditions is not necessary, the next notification is waited, and the above processing is repeated unless a set of the acquisition conditions whose setting information is “invalid” is stored in the table.

When a set of acquisition conditions indicating that the setting information indicates "invalid" is stored (step S1502: Y), the order value of all the sets stored in the table of the acquisition request storage unit 202 is increased by one. (Step S1503), acquisition condition storage unit 20
2, a new acquisition condition can be set in the data acquisition unit 507 depending on whether or not the total number of the acquisition condition sets whose setting information indicates “valid” is less than three out of the sets stored in the second table. It is determined whether or not it is (step S1504).

If it is not possible to set the acquisition conditions in the data acquisition unit 507 (step S1504: N), the table of the acquisition request storage unit 202 indicates that the setting information is "valid" and the order value is the largest. Select an acquisition condition and set the data acquisition unit 50
7, the setting of the selected acquisition condition is deleted, the setting information of the selected acquisition condition set stored in the table is set to "invalid", and the order value is set to the initial value 0 (step S150).
Five). Next, from the table, the setting information is "invalid" and
The acquisition condition of the group having the largest sequence value is selected, the setting information of the group is set to “valid”, and the sequence value is set to the initial value 0 (step S1).
506), the selected acquisition condition is set in the data acquisition unit 507.

If the acquisition condition can be set in the data acquisition unit 507 (step S1504: Y), the acquisition condition of the set whose setting information is “invalid” and the maximum order value is selected from the table, and The setting information of the group is set to “valid”, the order value is set to the initial value 0 (step S1506), and the selected acquisition condition is set to the data acquisition unit 507. The acquisition condition is set to the data acquisition unit 50 by the acquisition condition setting scheduling unit 204.
The processing performed by the data acquisition device 300 after the setting is set to 7 is the same as that in the case of the fifth embodiment (the flowchart of FIG. 35), and a description thereof will be omitted.

In the present embodiment, when the received acquisition condition cannot be set in the data acquisition unit 507, the reception condition is not set in the data acquisition unit 507 in step S1206 in FIG. The acquisition condition is stored in the table of the acquisition condition storage unit 202, and the setting information of the received acquisition condition set is set to “invalid” and the order value is set to the initial value 0. Instead of step S1206, the acquisition condition storage unit From the table 202, a set of acquisition conditions whose setting information is “valid” and the order value is the largest is selected, the setting of the acquisition condition selected from the data acquisition unit 507 is deleted, and the selected acquisition condition stored in the table is selected. Step S1207 of setting the setting information of the set of acquisition conditions to “invalid” and setting the order value to the initial value 0
May be inserted in the flowchart of FIG. FIG. 36 shows a flowchart in this case. Steps S1201 to S1205 other than step S1207 are described in FIG.
1, the description of these steps is omitted.

As a result, as soon as the acquisition condition is received from the application, the data acquisition based on the acquisition condition is preferentially executed, so that the response to the acquisition condition can be expedited. In the present embodiment,
In FIG. 38, when the acquisition condition received in the data acquisition unit 507 cannot be set, in step S1505, from the table of the acquisition condition storage unit 202, the acquisition condition of the set whose setting information is “valid” and the order value is the largest Is selected, the setting of the selected acquisition condition is deleted from the data acquisition unit 507, the setting information of the selected acquisition condition set stored in the table is set to "invalid", and the order value is set to the initial value 0. In place of step S1505, the setting of the acquisition condition for which data has been successfully extracted is deleted from the data acquisition unit 507,
Step S1507 for invalidating the registration information of the set of the data acquisition request in the table of the acquisition condition storage unit 202 and setting the order value to the initial value 0 may be inserted. FIG. 39 shows a flowchart in this case. Steps S1501 to S1506 other than step S1507 are the same as those in the flowchart of FIG. 38, and thus description of these steps will be omitted.

As a result, the acquisition conditions for which data acquisition succeeds are preferentially deleted from data monitoring and extraction targets by the data acquisition unit 507, and data acquisition is efficiently performed for other acquisition conditions for which data acquisition has not succeeded. Can give the opportunity. When the acquisition condition scheduling unit 204 performs a process of scheduling the setting of the acquisition condition received from the application according to the flowcharts of FIGS. 36 and 39, the acquisition condition scheduling unit 204 performs the acquisition conditions between steps S1503 and S1504 of the flowchart of FIG. Storage unit 202
Step S1508 may be inserted to increase the order value of the set of acquisition conditions for which the extraction of the data of the table has succeeded by 2. FIG. 40 shows a flowchart in this case. Steps S1501 to S1504 other than step S1508, S1506 to S150
Step 7 is the same as that in the flowchart of FIG. 39, and the description of these steps is omitted.

As a result, in S1504, it is possible to set the acquisition conditions in the data acquisition unit 507. Therefore, in S1507, even if the settings of the acquisition conditions for which the data has been successfully extracted are not deleted from the data acquisition unit 507, the data acquisition unit 507 is not required. Acquisition conditions for which the data acquisition unit 507 succeeds can be removed earlier from data monitoring and extraction targets by the data acquisition unit 507. As described above, the data acquisition device according to the present invention has been described based on the embodiments. However, it goes without saying that the present invention is not limited to these embodiments.

For example, in these embodiments, a case has been described in which the data acquisition apparatus of the present invention is applied to a digital broadcast receiver. However, the present invention is not limited to this, and a computer connected to a communication network such as the Internet can be used. And CAT
V. It can also be applied to a receiver or the like in a video distribution system. In the first embodiment, the request condition generation unit 1
The request condition generated by the request condition generation unit 112 is passed to the request condition setting scheduling unit 113 and stored in the request condition recording unit 114 after being scheduled by the request condition setting scheduling unit 113. The data flow may be that the condition is passed to the request condition setting scheduling unit 113 via the request condition recording unit 114. That is, the request condition recording unit 114 may be used as a storage location of request conditions before and after scheduling in the data acquisition device.

Also, the request condition generation unit 112
When one request condition includes a common condition, it is determined that the request conditions can be combined, and a new request condition expressed by a logical sum of those conditions is generated. A request condition expressed by a logical product with respect to the condition may be generated. This is because, when various types of independent applications request acquisition of common data, giving priority to acquisition of common data that meets all of those requests can lead to efficient data acquisition as a whole.

[0145] In order to combine as many request conditions as possible into one, all the request conditions recorded in the request condition recording unit 114 can be combined. It may be possible to consider and optimize the performance. Further, in the present data acquisition device, the request condition generation unit generates additional information such as request identification information, request generation time, and combined request identification information when generating the request condition. The storing process may be entrusted to the request condition setting scheduling unit altogether.

The request condition setting scheduling unit performs time scheduling based on the absolute time such as the request generation time, the timeout time, and the timeout recovery time. Instead, time information such as the timeout time and the timeout recovery time are used. Is generated and added to the request condition, the elapsed time (relative time)
May be used as the time scheduling.

Further, by combining the functions of the request condition generation unit and the request condition setting scheduling unit in the first to fourth embodiments, a data acquisition device that performs more sophisticated and diverse scheduling can be realized. For example, a method in which the request condition setting scheduling unit having the scheduling function in these embodiments dynamically selects and adopts any optimal one may be adopted.

The request condition setting scheduling unit may put the request condition for which data has been acquired at the end of the queue instead of deleting it. For example, the data acquisition device does not limit the data acquisition to the request condition in which the monitoring status information is “monitoring unnecessary acquisition” as described in the present embodiment. It may be repeated.

When the status monitoring information is "always-monitoring acquisition", the data-acquisition device may switch the data-acquisition at high-speed between the data-acquisitions that are always-monitoring-acquisition. Further, the request condition setting scheduling unit may change the data acquisition monitoring state information added to the request condition depending on factors such as a state of a state transition in data acquisition and a residence time in a specific state. As a result, the monitoring state is dynamically determined based on the data acquisition state and the like, and a data acquisition device that can follow changes in the content and frequency of transmitted data is realized.

Furthermore, the characteristic configuration of the present invention (such as the request condition generation unit and the request condition setting scheduling unit of the data acquisition device) can be realized not only by hardware such as a dedicated electronic circuit but also by a general-purpose hardware. It can also be realized as a program executed by the CPU. In the fifth and sixth embodiments, the number of data acquisition conditions that can be set in the data acquisition unit 507 is three, but the number of acquisition conditions that can be set is not limited to three.
Furthermore, in the example of the fifth embodiment (FIGS. 33 and 34), six acquisition conditions are stored in the acquisition condition storage unit 202, but the number of data acquisition conditions that can be stored is not limited to six.

In the fifth and sixth embodiments, the order value is set in such a manner that 0 is set as the initial value and the value is incremented by 1 in order from 0, but a numerical value other than 0 may be set as the initial value. Further, when other acquisition conditions are stored in the table, when the acquisition condition exchange request unit 203 issues an acquisition condition exchange request, or when an acquisition condition for which data extraction is successful is notified, the setting information is changed. The number of order values that are increased when a set of acquisition conditions indicating “invalid” is stored in the acquisition condition storage unit 202 is not limited to one. Further, the order value may be decreased instead of being increased.

[0152]

In order to achieve the above object, the present invention provides:
Based on each request from a plurality of data processing devices, data that satisfies specific conditions corresponding to each request is extracted and obtained from a transmitted data stream, and the obtained data is returned to the requesting data processing device. An acquisition device, from the plurality of data processing devices, a request receiving unit that receives the request to acquire specific data,
A condition generating unit that receives the request from the request receiving unit and generates the corresponding condition; accepts the generated setting of the condition; and data that satisfies any of the set conditions is included in the data stream. Monitoring whether or not it is included, if included, data extraction means to extract and obtain the data, and generate a queue of the conditions corresponding to the received request, according to the queue, A scheduling unit for starting the data acquisition by performing the setting in the data extraction unit, terminating the data acquisition by deleting the setting from the data extraction unit, and scheduling the data acquisition; And output means for outputting the data acquired by (1) to the data processor of the request source. .

With this configuration, data acquisition in response to a data acquisition request from a plurality of data processing devices is performed after the scheduling is performed by the scheduling means provided in the data acquisition device that receives the data stream that is the data source. Since it is executed, efficient data acquisition is realized under limited hardware resources. Further, each data processing device can issue a data acquisition request to the data acquisition device at its own convenience without considering a conflict with a data acquisition request issued from another data processing device.

Here, the request receiving means receives the request and the priority of data acquisition for the request, and the scheduling means gives priority to data acquisition according to the condition corresponding to the received request with a high priority. The queue may be generated as described above. With this configuration, it is possible to avoid a problem that the high-priority data acquisition is not performed and the user waits because the low-priority data acquisition is continued.

Further, the request receiving means receives, together with the request, monitoring status information designating a mode of data acquisition for the request, and the scheduling means designates that the received monitoring status information designates data acquisition by constant monitoring. Is set, the conditions are set in the data extracting means so that data acquisition corresponding to the request is continued, and when the received monitoring state information specifies data acquisition by intermittent monitoring, Sets and deletes the condition to the data extracting means so that data acquisition for the request is started periodically, and when the received monitoring state information specifies data acquisition without monitoring required, Setting and deleting the condition in the data extracting means so that data acquisition for the request is performed only once. .

With this configuration, it is possible to obtain fine and efficient data depending on the characteristics (repetition, frequency, band, etc.) of the transmitted data and the monitoring mode (frequency, urgency, etc.) for the data. . Further, the data acquisition device further includes a recording unit for temporarily recording the condition, the condition generation unit records the generated condition in the recording unit, the scheduling unit, The queue may be generated by reading and rearranging the conditions recorded in the recording unit and then writing back to the recording unit.

According to this configuration, a common storage location for storing requests to be scheduled is secured, so that various functional means can easily communicate with each other via this storage location. Further, the request receiving means receives, together with the request, header information indicating a type of the request, and the condition generating means receives the request and the header information from the request receiving means, and responds to the received request. Generating the condition, and recording the generated condition and the received header information in the recording unit in association with each other;
The data acquisition for a specific request may be terminated by deleting the condition set in the data extraction unit based on the header information recorded in the recording unit. The data acquisition device further includes a timer unit that indicates a current time, and the request receiving unit includes:
Along with the request, receiving header information indicating the type of the request, the condition generating means receives the request and the header information from the request receiving means, generates the condition corresponding to the received request, Based on the header information, generates a time-out time indicating a time at which data acquisition is interrupted, records the time-out time in the recording means in association with the generated condition, and the scheduling means
For the condition set in the data extraction means, it is determined whether or not the time-out time has arrived by comparing the current time indicated by the timer means with the corresponding time-out time recorded in the recording means. The data acquisition may be terminated by deleting the condition determined to have arrived from the setting in the data extracting means.

With this configuration, it is possible to control the execution of data acquisition depending on the type of data acquisition request, for example, when data acquisition requests of the same type are issued, interrupt data acquisition for old data acquisition requests. In addition, continuous useless data acquisition is prevented. Also,
The data acquisition device further includes timer means for indicating a current time, and the condition generating means, when receiving the request from the request receiving means, requests the condition corresponding to the request and the time indicating the time. Generating generation time information and recording the request generation time information in the recording unit in association with the generated condition, wherein the scheduling unit calculates the current time indicated by the timer unit and the request generation time recorded in the recording unit The elapsed time from when the request was received may be calculated by comparing the time indicated by the information, and the scheduling may be performed based on the elapsed time.

With this configuration, data acquisition control is performed based on the time elapsed since the data acquisition request was issued. Therefore, it is possible to avoid a problem that a data acquisition request for which data acquisition is not executed forever remains. it can. Further, upon receiving the request from the request receiving unit, the condition generating unit generates the condition corresponding to the request, and compares the generated condition with a condition already recorded in the recording unit. Thereby, it is determined whether or not they can be combined, and when it is determined that the conditions can be combined, a new condition in which the conditions are combined is generated and recorded in the recording unit, and the scheduling unit includes: A new condition generated by the combination is read out from the recording unit, and the new condition is put into the queue, and then set in the data extraction unit to start data acquisition. The data acquisition may be terminated by deleting the setting from the data extraction unit. At this time, the condition generating means, from the request receiving means,
When the request is received, the condition corresponding to the request is generated, identification information for identifying the condition is generated, and when a new condition is generated by the connection, the condition used for the connection is generated. Generating, using the identification information, association information for associating the identification information with the condition generated by the association, and recording the identification information and the association information in the recording unit in association with the condition corresponding to the identification information; Specifies the condition newly generated by the combination and the condition used for the combination based on the identification information and the combination information recorded in the recording unit, and controls the start and end of the data acquisition, respectively. Good. The condition generating means determines that, when the common content is included in each of the two or more conditions to be combined, it is possible to combine the conditions, and determines only the common content as the condition. May be generated.

According to this configuration, a plurality of conditions are combined into one condition that satisfies the conditions at the same time. Therefore, the number of conditions to be set in the data extracting means is reduced, and hardware resources are effectively used. . Further, the data acquisition device further includes timer means for indicating a current time, and when the data acquisition is started, the scheduling means generates a time-out time indicating a time after a lapse of a fixed time from the start time. Then, the time is recorded in the recording unit in association with the corresponding condition, and the current time indicated by the timer unit is compared with the corresponding timeout time recorded in the recording unit to determine whether or not the timeout time has arrived. When it is determined that the time-out time has arrived, the data acquisition is terminated by deleting the condition set in the data extracting means, and the time indicating that a certain time has elapsed from the end time is indicated. Generate a time-out resurrection time, record in the recording means in association with the corresponding condition, When it is determined whether the time-out recovery time has arrived by comparing the current time indicated by the timer means with the corresponding time-out recovery time recorded in the recording means, and it is determined that the time-out recovery time has arrived. Alternatively, the data acquisition may be started by setting the conditions in the queue and then setting the conditions in the data extracting means.

With this configuration, even if the target data is not transmitted, the data acquisition is interrupted and resumed after a certain period of time, so that the hardware resources are continuously occupied unnecessarily. Can be prevented. The data extraction unit outputs data acquisition information indicating whether data has been acquired for the set condition, and the scheduling unit includes:
Based on the data acquisition information, for the condition recorded in the recording unit, data acquisition determination information indicating whether data has been acquired is generated and recorded in the recording unit in association with the corresponding condition. In addition, the scheduling may be performed based on the generated data acquisition determination information.

With this configuration, it is possible to obtain data efficiently depending on whether or not target data has been obtained. In addition, the data acquisition device further includes a timer unit that indicates a current time, and the condition generation unit includes:
From the request receiving means, when the request is received, while generating the condition corresponding to the request,
Condition generation time information indicating the time is generated, and the condition generation time information is recorded in the recording unit in association with the generated condition, and the scheduling unit corresponds to the condition set in the data extraction unit. For the data acquisition to be performed, by comparing the current time indicated by the timer means and the time indicated by the condition generation time information recorded in the recording means, and by referring to the data acquisition determination information recorded in the recording means, It may be determined whether or not the recording unit has the condition that data has not been acquired for more than a predetermined time after receiving the request, and the scheduling may be performed based on a result of the determination.

According to this configuration, since the target data is not transmitted, it is possible to avoid a problem that the hardware resources are continuously occupied unnecessarily without obtaining the data. Further, upon receiving the request from the request receiving unit, the condition generating unit generates the condition corresponding to the request, and compares the generated condition with a condition already recorded in the recording unit. Thereby, it is determined whether or not they can be combined, and when it is determined that the conditions can be combined, a new condition in which the conditions are combined is generated and recorded in the recording unit together with the condition generation time information. The scheduling means reads out a new condition generated by the combination from the recording means, sets the condition in the data extraction means after enqueuing the new condition in the queue, starts data acquisition, and uses the data for the combination. The data acquisition is terminated by deleting the set condition from the setting in the data extracting means, and the new condition is obtained by combining. When it is determined that data has not been acquired for a generated condition for a certain period of time after receiving the request, the condition set in the data extraction unit is deleted to satisfy the new condition. The data acquisition may be terminated by terminating the corresponding data acquisition, reading the conditions used for the combination from the recording means, setting the conditions in the data extraction means after enqueuing the conditions in the queue, and starting the data acquisition.

According to this configuration, even if the data acquisition state is not improved by the data acquisition based on the combined data acquisition conditions, the data is repaired and restored to the original data acquisition state. In addition, the request receiving unit receives, together with the request, monitoring state information that specifies a mode of data acquisition for the request, priority of data acquisition, and identification information for identifying the request,
The condition generating unit receives the request, the monitoring state information, and the identification information from the request receiving unit, generates the condition corresponding to the request, associates the monitoring state information with the generated condition, and The identification information is recorded in the recording unit, and the data extraction unit refers to the header information included in the data stream to indicate the identification information corresponding to the data included in the data stream and the version thereof. The scheduling unit extracts and outputs version information, and the scheduling unit acquires corresponding data for each of the conditions recorded in the recording unit based on the identification information and the version information output by the data extraction unit. Data acquisition determination information indicating whether or not the latest version of the corresponding data The latest version information and the version update number information indicating the number of times the latest version has been updated are generated and recorded in the recording means, and the monitoring status information indicates data acquisition without monitoring, and the priority Are the same, and when a plurality of the conditions having the same content of the data acquisition determination information are in the queue, the number of the corresponding version update times recorded in the recording means among the conditions. Data acquisition may be started by setting the condition that the number of updates of the version indicated by the information is large in the data extracting means with priority.

With this configuration, data acquisition corresponding to data whose content is frequently updated is prioritized and executed, so that efficient data acquisition for acquiring more content is realized. Further, based on each request from a plurality of data processing devices, data that satisfies a specific condition corresponding to the request is extracted and obtained from a transmitted data stream, and the obtained data is processed by each data processing of the request source. A data acquisition device to be returned to the device, and from a plurality of data processing devices,
Acquiring means for acquiring the condition corresponding to the request, accepting the setting of the condition, monitoring whether or not data satisfying any of the set conditions is included in the data stream; The data extraction means for extracting and acquiring the data if the condition is satisfied, setting information indicating whether the condition is set to “present” or “not present” in the data extracting means, and A table that indicates a value corresponding to an acquisition order, and holds a table indicating a correspondence relationship with an order value that is initialized to a newest value indicating the acquisition order when the setting of the condition is deleted from the data extraction unit. Holding means, each time the condition is newly acquired by the acquisition means, the newly acquired condition, the setting information of the condition, and the order indicating the newest acquisition order. A scheduling unit for controlling the setting of the condition to the data extracting unit by referring to the setting information and the sequence value recorded in the table as a set of values and the data extraction; Output means for outputting the data obtained by the means to the data processing device of the request source.

With this configuration, it is possible to receive more acquisition conditions than the number of actual acquisition conditions at which data can be simultaneously extracted and monitored. In addition, the scheduling unit may be configured such that the setting is “present” in the table.
By determining whether or not the number of conditions forming a pair with the setting information indicating that the condition is less than the upper limit of the number of conditions that can be set in the data extraction unit, the data extraction unit newly sets the condition. Setting determining means for determining whether setting is possible; and when the setting determining means determines that the setting is possible, newly setting the determined condition in the data extracting means; In the case where it is determined that “the setting is impossible”, in the table, the condition to be deleted from the data extraction unit is selected from among the conditions forming a pair with the setting information indicating that the setting is “present” And setting control means for deleting the selected condition from the data extracting means and newly setting the condition determined by the determining means in the data extracting means.

With this configuration, it is possible to preferentially give a data acquisition opportunity to an acquisition condition for which data has not been extracted and monitored. In addition, in the table, in the table, among the conditions forming a pair with the setting information indicating that the setting is “absent”, the order value indicating that the acquisition order is the oldest is included in the set. Conditions are determined as the conditions to be newly set in the data extraction means,
When it is determined that “setting is impossible”, the setting control unit indicates the oldest acquisition order in the table, from among the conditions forming a pair with the setting information indicating that the setting is “present”. The condition having a set of order values may be selected, and the setting of the selected condition may be deleted from the data extracting unit. With this configuration, data acquisition under the acquisition conditions requested by the data processing device is performed in the order requested, so that it is possible to respond to requests from the data acquisition device at appropriate intervals.

In addition, the determining means sets the order value indicating that the acquisition order is the latest among the conditions forming a set with the setting information indicating that the setting is “absent” in the table. Is determined as the condition to be newly set in the data extraction unit, and the setting control unit determines that the setting is "present" in the table when it is determined that "setting is impossible". Out of the conditions forming a pair with the setting information indicating the condition, selecting the condition having the order value indicating the oldest acquisition order in the set, and deleting the setting of the selected condition from the data extracting unit. Good.

According to this configuration, data acquisition under the acquisition condition newly requested from the data processing device is preferentially executed, so that a response to a request from a specific data acquisition device can be hastened. Further, the data processing device further includes, in response to a request from the data processing device, a replacement request unit that requests the schedule unit to replace the condition set in the data extraction unit, and the schedule unit includes: When the exchange is requested, the exchange of the condition set in the data extracting means may be controlled by referring to the setting information and the order value recorded in the table.

According to this configuration, it is possible to provide a timing for changing the acquisition conditions in response to a request from the data processing device. Therefore, the schedule of data extraction and monitoring is automatically adjusted using all the data acquisition conditions. Can be. Further, when the data extraction unit succeeds in the data extraction under the set condition, the data extraction unit notifies the schedule unit of the condition, and the schedule unit includes
When the notification is received, the replacement of the condition set in the data extracting means may be controlled by referring to the setting information and the order value recorded in the table.

According to this configuration, the timing for changing the data acquisition conditions can be given by the success of the data extraction. Therefore, it is not necessary to change the acquisition conditions from the data processing device, and all the acquisition conditions can be changed. With it, data extraction and monitoring can be automatically scheduled.

[Brief description of the drawings]

FIG. 1 is a functional block diagram illustrating a configuration of a data acquisition device according to Embodiment 1 of the present invention.

FIG. 2 is a diagram illustrating an example of a list of request conditions generated by a request condition generation unit.

FIG. 3 is a state transition diagram of a data acquisition state for each request condition.

FIG. 4 is a diagram showing a state after request conditions are sorted in priority order by request condition setting scheduling.

FIG. 5 is a flowchart showing a flow of an entire data acquisition process by the device.

FIG. 6 is a flowchart showing a processing procedure centering on scheduling of a request condition based on a priority by the apparatus.

FIG. 7 is a diagram illustrating an example of a list of request conditions to which various management information has been added by a request condition setting scheduling unit;

FIG. 8 is a diagram illustrating an example of a current time read from a timer unit.

FIG. 9 shows the execution state of the data acquisition request as “executing”
It is a flowchart which shows the co-located processing procedure when it changes to "executable state" through "waiting state".

FIG. 10 is a diagram illustrating a state of a request condition combining process performed by a request condition generation unit.

FIG. 11 is a flowchart showing a flow of a data acquisition request combining process by the device.

FIG. 12 is a diagram illustrating an example of a list of request conditions to which various management information has been added by a request condition setting scheduling unit;

FIG. 13 is a flowchart showing a flow of a division process of a data acquisition request combined by the same device.

FIG. 14 is a functional block diagram illustrating a configuration of a data acquisition device according to a second embodiment of the present invention.

FIG. 15 is a diagram illustrating an example of a list of request conditions generated by a request condition generation unit.

FIG. 16 is a diagram illustrating a state in which data acquisition is performed by scheduling according to a fixed procedure for each monitoring state specified by the data acquisition monitoring state information.

FIG. 17 is a flowchart showing a flow of an entire data acquisition process by the device.

FIG. 18 is a diagram illustrating an example of a list of request conditions to which various management information has been added by a request condition setting scheduling unit;

FIG. 19 shows control of a request condition in which data acquisition monitoring state information is “monitoring unnecessary acquisition” (from “waiting state” to “executable state”) in data acquisition control by the apparatus.
FIG.

FIG. 20 is a diagram illustrating an example of a list of request conditions to which various management information has been added by a request condition setting scheduling unit;

FIG. 21 shows control of a request condition whose data acquisition monitoring status information is “monitoring unnecessary acquisition” (from “waiting status” to “executable status”) in data acquisition control by the same device.
FIG.

FIG. 22 is a functional block diagram illustrating a configuration of a data acquisition device according to Embodiment 3 of the present invention.

FIG. 23 is a diagram illustrating an example of a list of request conditions generated by a request condition generation unit.

FIG. 24 is a flowchart showing a flow of generation of a timeout time and a timeout process by the device.

FIG. 25 is a functional block diagram showing a configuration of a data acquisition device according to Embodiment 4 of the present invention.

FIG. 26 is a diagram illustrating an example of a list of request conditions to which various management information has been added by a request condition setting scheduling unit;

FIG. 27 is a flowchart showing a flow of processing related to a version of received data in data acquisition control by the device.

FIG. 28 is a functional block diagram showing a configuration of a conventional data acquisition device.

FIG. 29 is a flowchart showing the flow of a data acquisition process by a conventional data acquisition device.

FIG. 30 is a functional block diagram showing a configuration of a data acquisition device 200.

FIG. 31 is a flowchart illustrating a process of storing an acquisition condition received from an application in a table of an acquisition condition storage unit 202;

FIG. 32 is a flowchart illustrating a process in which the acquisition condition setting scheduling unit 204 sets acquisition conditions stored in a table of the acquisition condition storage unit 202 in the data acquisition unit 507.

FIG. 33 illustrates an example of a table in an acquisition condition storage unit 202 that stores sets of acquisition conditions, setting information, and order values.

34 illustrates an example of the table in FIG. 33 updated by the acquisition condition setting scheduling unit 204 performing processing of setting the acquisition conditions stored in the table of the acquisition condition storage unit 202 in the data acquisition unit 507. .

FIG. 35 is a flowchart illustrating a process performed by the data acquisition device 200 after the acquisition condition is set in the data acquisition unit 507.

FIG. 36 is an example in which the setting information is “valid” from the table of the acquisition condition storage unit 202 instead of step S1206 in FIG. 31;
In addition, the acquisition condition of the set having the largest order value is selected, the setting of the acquisition condition selected from the data acquisition unit 507 is deleted, and the setting information of the selected acquisition condition set stored in the table is set to “invalid”. Step S120 for setting the order value to the initial value 0
7 is a flowchart illustrating a process of storing an acquisition condition received from an application in a table of an acquisition condition storage unit 202 when 7 is inserted.

FIG. 37 is a functional block diagram showing a configuration of a data acquisition device 300.

FIG. 38 is a flowchart showing a process in which the acquisition condition setting scheduling unit 204 sets acquisition conditions stored in a table of the acquisition condition storage unit 202 in the data acquisition unit 507.

FIG. 39 is a diagram illustrating an example of a data acquisition unit 507 that sets acquisition conditions for which data has been successfully extracted in place of step S1505 in FIG. 38;
, The registration information of the data acquisition request set in the table of the acquisition condition storage unit 202 is invalid, and the order value is set to the initial value 0.
In step S1507, the acquisition condition setting scheduling unit 204 inserts the acquisition condition stored in the table of the acquisition condition storage unit 202 into the data acquisition unit 50.
7 is a flowchart illustrating a process for setting the number to 7;

40 shows steps S1503 and S150 in the flowchart of FIG. 39.
During step 1504, the acquisition condition setting scheduling unit 204 inserts step S1508, which increases the order value of the set of acquisition conditions for which the data of the table of the acquisition condition storage unit 202 has been successfully extracted by two, by the acquisition condition storage unit 202. 9 is a flowchart illustrating a process of setting an acquisition condition stored in a table in a data acquisition unit 507.

[Explanation of symbols]

110, 120, 130, 140, 200, 300, 5
00 Data acquisition device 112, 122, 132 Request condition generation unit 113, 123, 133, 143 Request condition setting scheduling unit 114 Request condition recording unit 115 Timer unit 116 Request condition setting unit 201 Acquisition condition reception unit 202 Acquisition condition storage unit 203 Acquisition Condition replacement requesting unit 204, 304 Acquisition condition setting scheduling unit 501 Data acquisition request receiving unit 507 Data acquiring unit 508 Data transmitting unit

 ────────────────────────────────────────────────── ─── Continued on the front page (72) Inventor Yoshiro Ishikawa 1006 Kadoma Kadoma, Osaka Pref. Matsushita Electric Industrial Co., Ltd. (72) Takashi Kodera 1006 Odakadoma Kadoma, Osaka Pref. Matsushita Sofh Research F-term (Reference) 5B098 GA04 GB13 GC03 5C025 BA11 BA14 BA28 BA30 CA03 CA06 CA09 CA10 CA20 CB06 CB07 CB08 CB09 CB10 DA01 DA04 DA05 5C064 BA01 BB05 BB07 BB10 BC06 BC07 BC10 BC16 BC20 BC23 BC27 BD02 BD05 BD08 BD09 BD16

Claims (35)

[Claims] 1. A method for extracting and acquiring data satisfying a specific condition corresponding to each request from a transmitted data stream based on each request from a plurality of data processing apparatuses, and acquiring the acquired data as data of a request source. A data acquisition device to be returned to a processing device, a request receiving unit receiving the request to obtain specific data from the plurality of data processing devices, and a request receiving unit receiving the request from the request receiving unit, and the corresponding condition A condition generating means for generating the condition, accepting the generated setting of the condition, monitoring whether or not data satisfying any of the set conditions is included in the data stream, and if the data is included A data extracting means for extracting and obtaining the data, and generating a queue of the condition corresponding to the received request, Therefore, by performing the setting in the data extraction unit, the data acquisition is started, and by deleting the setting from the data extraction unit, the data acquisition is terminated, and a scheduling unit that schedules the data acquisition, Output means for outputting the data obtained by the extraction means to the data processing apparatus of the request source. 2. The request receiving means receives a priority of data acquisition for the request together with the request, and the scheduling means gives priority to data acquisition according to the condition corresponding to the received high priority request. Generating the queue as described above.
The data acquisition device according to 1. 3. The request receiving means receives, together with the request, monitoring status information specifying a data acquisition mode for the request, and the scheduling means specifies that the received monitoring status information specifies data acquisition by constant monitoring. If you have
The conditions are set in the data extracting means so that data acquisition corresponding to the request is continued. If the received monitoring state information specifies data acquisition by intermittent monitoring, the data corresponding to the request is acquired. The conditions are set and deleted from the data extraction means so that the acquisition is started periodically. If the received monitoring status information specifies data acquisition without monitoring, data acquisition for the request is performed. 2. The data acquisition apparatus according to claim 1, wherein the setting and deletion of the condition in the data extraction unit are performed so that the operation is performed only once. 4. The data acquisition apparatus further includes a recording unit for temporarily recording the condition, the condition generation unit records the generated condition on the recording unit, 2. The data acquisition apparatus according to claim 1, wherein the means generates the queue by reading and rearranging the conditions recorded in the recording means and then writing back the conditions to the recording means. 5. The request receiving means receives header information indicating the type of the request together with the request, and the condition generating means receives the request and the header information from the request receiving means, and The condition corresponding to the request is generated, and the generated condition and the received header information are associated with each other and recorded in the recording unit.The scheduling unit, based on the header information recorded in the recording unit, The data acquisition apparatus according to claim 4, wherein the data acquisition for a specific request is terminated by deleting the condition set in the data extraction unit. 6. The data acquisition device further includes timer means for indicating a current time, the request receiving means receives header information indicating a type of the request together with the request, and the condition generating means includes From the request receiving means, received the request and the header information, generated the condition corresponding to the received request, based on the header information, generated a time-out time indicating a time to interrupt data acquisition, generated The scheduling unit records the condition set in the data extraction unit in association with the condition, the current time indicated by the timer unit and the corresponding timeout time recorded in the recording unit. To determine whether the time-out time has arrived. The data acquisition apparatus according to claim 4, wherein the data acquisition is terminated by deleting the disconnected condition from the setting in the data extraction unit. 7. The data acquisition device further includes timer means for indicating a current time, wherein the condition generating means, when receiving the request from the request receiving means, receives the condition corresponding to the request and Request generation time information indicating the time is generated, and the request generation time information is recorded in the recording unit in association with the generated condition; the scheduling unit records the current time indicated by the timer unit and the recording unit The method according to claim 4, wherein an elapsed time from when the request is received is calculated by comparing a time indicated by the received request generation time information, and the scheduling is performed based on the elapsed time. Data acquisition device. 8. The condition generating means, when receiving the request from the request receiving means, generates the condition corresponding to the request, and determines the generated condition and the condition already recorded in the recording means. By comparing whether or not they can be combined, if it is determined that they can be combined, a new condition combining those conditions is generated and recorded in the recording means, and the scheduling is performed. The means is used for reading the new condition generated by the combination from the recording means, starting the data acquisition by setting the new condition in the queue, and then setting the data in the data extracting means, and used for the combination. The data acquisition is terminated by deleting the set condition from the setting in the data extracting means. Over data acquisition device. 9. The condition generating means, upon receiving the request from the request receiving means, generates the condition corresponding to the request, generates identification information for identifying the condition, and generates In the case where a new condition is generated by using the above-described identification information, a combination information that associates the condition used for the combination with the condition generated by the combination is generated using the identification information. The recording unit records the condition in association with the corresponding condition, and the scheduling unit newly generates the condition by the combination and the condition used for the combination based on the identification information and the combination information recorded in the recording unit. To identify
9. The data acquisition device according to claim 8, wherein start and end of data acquisition are respectively controlled. 10. When two or more conditions to be combined include contents common to each of the conditions, the condition generating unit determines that the conditions can be combined, and determines only the common contents. 10. The data acquisition device according to claim 9, wherein a new condition is generated under the following condition. 11. The data acquisition device further includes timer means for indicating a current time, and when the data acquisition is started, the scheduling means sets a time-out indicating a time that has elapsed from the start time by a fixed time. A time is generated, recorded in the recording means in association with the corresponding condition, and the time-out time has arrived by comparing the current time indicated by the timer means with the corresponding time-out time recorded in the recording means. When it is determined that the time-out time has arrived, the data acquisition is terminated by deleting the condition set in the data extracting means, and a predetermined time has elapsed from the end time. Generating a time-out resurrection time indicating a time, and correlating with the corresponding condition, Record, and determine whether the time-out recovery time has arrived by comparing the current time indicated by the timer means and the corresponding time-out recovery time recorded in the recording means, and that the time-out recovery time has arrived If you decide,
5. The data acquisition apparatus according to claim 4, wherein the data acquisition is started by setting the condition in the queue and setting the data in the data extraction unit. 12. The data extraction unit outputs data acquisition information indicating whether data has been acquired for the set condition, and the scheduling unit performs the recording based on the data acquisition information. For the condition recorded in the means, generate data acquisition determination information indicating whether or not data has been acquired, record the information in the recording means in association with the corresponding condition, and, based on the generated data acquisition determination information, 5. The data acquisition device according to claim 4, wherein the scheduling is performed. 13. The data acquisition device further includes timer means for indicating a current time, and the condition generating means, when receiving the request from the request receiving means, sets the condition corresponding to the request. Generating, generating condition generation time information indicating the time, recording the condition generation time information in the recording unit in association with the generated condition, and the scheduling unit is set in the data extraction unit. Regarding data acquisition corresponding to the condition,
By comparing the current time indicated by the timer means with the time indicated by the condition generation time information recorded in the recording means, and by referring to the data acquisition determination information recorded in the recording means, receiving the request 13. The data according to claim 12, wherein it is determined whether or not the condition that data has not been acquired for more than a predetermined time exists in the recording unit, and the scheduling is performed based on the determination result. Acquisition device. 14. The condition generating means, upon receiving the request from the request receiving means, generates the condition corresponding to the request, and determines the generated condition and the condition already recorded in the recording means. By comparing
It is determined whether or not they can be combined, and if it is determined that they can be combined, a new condition in which those conditions are combined is generated and recorded in the recording unit together with the condition generation time information, and the scheduling is performed. The means reads the new condition generated by the combination from the recording means, starts the data acquisition by setting the condition in the data extracting means after enqueuing the new condition, and starts the data acquisition by using the condition used for the combination. Is terminated from the setting in the data extraction means to terminate the data acquisition, and for the condition newly generated by the combination, when it is determined that data has not been acquired for more than a predetermined time after receiving the request. Deletes the condition set in the data extracting means to meet the new condition. Ending the data acquisition to be performed, reading out the conditions used for the combination from the recording unit, setting the conditions in the data extraction unit after enqueuing the conditions into the queue, and starting the data acquisition. Item 14. The data acquisition device according to item 13. 15. The data acquisition device further includes timer means for indicating a current time, wherein the request receiving means receives, together with the request, monitoring status information designating a data acquisition mode for the request, If the monitoring status information corresponding to the request for terminating the data acquisition due to the arrival of the timeout time specifies data acquisition without monitoring, a timeout indicating a time that has elapsed by a fixed time from the end time is provided. After generating the resurrection time, determine whether the timeout resurrection time has arrived by comparing the current time indicated by the timer means and the timeout resurrection time, when it is determined that the timeout resurrection time has arrived, After enqueuing the condition corresponding to the request into the queue, Data acquisition apparatus according to claim 1, wherein to initiate data acquisition by setting the data extracting means. 16. The request receiving means receives, together with the request, monitoring state information designating a mode of data acquisition for the request and a priority of data acquisition, and the scheduling means is set in the data extracting means. If the monitoring status information corresponding to the condition specifies data acquisition by not requiring monitoring, and the data has not been acquired, and a condition having a higher priority than the priority corresponding to the condition. When is in the queue, the data acquisition is terminated by deleting the condition set in the data extraction means, and the condition in the queue is set in the data extraction means. The data acquisition device according to claim 1, wherein data acquisition is started by the data acquisition device. 17. The request receiving means receives, together with the request, monitoring status information designating a mode of data acquisition for the request, priority of data acquisition, and identification information for identifying the request, The means receives the request, the monitoring state information, and the identification information from the request receiving means, generates the condition corresponding to the request, and associates the monitoring state information with the identification information in association with the generated condition. Is recorded in the recording unit, and the data extraction unit refers to the header information included in the data stream, thereby obtaining the identification information corresponding to the data included in the data stream and version information indicating the version thereof. Extracting and outputting, wherein the scheduling means outputs the identification information output by the data extracting means. And, based on the version information, for each of the conditions recorded in the recording means, data acquisition determination information indicating whether the corresponding data has been acquired, and the latest version information indicating the latest version of the corresponding data, Generating version update count information indicating the number of times the latest version has been updated and recording the update count information in the recording unit, and the monitoring status information indicates data acquisition without monitoring,
In the case where the plurality of conditions having the same priority and the same content of the data acquisition determination information are in the queue, among the conditions, the correspondence recorded in the recording means 5. The data acquisition apparatus according to claim 4, wherein data acquisition is started by setting a condition in which the version update count indicated by the version update count information is high in the data extraction unit with priority. 18. Based on each request from a plurality of data processing devices, data that satisfies specific conditions corresponding to each request is extracted and acquired from a transmitted data stream,
A data acquisition method for returning acquired data to a requesting data processing device, comprising: a request receiving step of receiving, from the plurality of data processing devices, a request to acquire specific data; and A request generating step of receiving the request and generating the corresponding condition; and accepting the generated setting of the condition, and determining whether data satisfying any of the set conditions is included in the data stream. Monitoring, and if included, a data extraction step of extracting and obtaining the data, and generating a queue of the condition corresponding to the received request, and according to the queue, the data extraction step By setting, start data acquisition,
A scheduling step of terminating the data acquisition by deleting the setting from the data extraction unit and scheduling the data acquisition; and an output step of outputting the data acquired in the data extraction step to a data processing device of the request source. A data acquisition method comprising: 19. Data that, based on requests from a plurality of data processing devices, extracts and obtains data that satisfies specific conditions from a transmitted data stream, and returns the obtained data to the requesting data processing device. A computer-readable recording medium recording a program for an acquisition device, wherein the program receives, from the plurality of data processing devices, a request for receiving the request to acquire specific data; A condition generating step of receiving the request from the receiving step and generating the corresponding condition; and accepting the generated setting of the condition, and data satisfying any of the set conditions is included in the data stream. Data extraction that monitors whether or not it is included and if it is included, extracts the data and acquires it Generating a queue of the conditions corresponding to the received request, and performing the setting in the data extraction step according to the queue, thereby starting data acquisition;
A scheduling step of terminating the data acquisition by deleting the setting from the data extraction unit and scheduling the data acquisition; and an output step of outputting the data acquired in the data extraction step to a data processing device of the request source. A recording medium comprising: 20. Based on each request from a plurality of data processing devices, data that satisfies a specific condition corresponding to the request is extracted and obtained from a transmitted data stream, and the obtained data is A data acquisition device returned to each data processing device, comprising: an acquisition unit for acquiring the condition corresponding to the request from a plurality of data processing devices; and accepting a setting of the condition, and setting any one of the set condition. Monitoring whether or not the data that satisfies is included in the data stream, and if included, data extracting means for extracting and obtaining the data; and the condition; and The setting information indicating whether the setting is “present” or “not present” and a value corresponding to the acquisition order of the condition are indicated, and the setting of the condition is deleted from the data extracting unit. A table holding unit for holding a table indicating a correspondence relationship with an order value initialized to a value indicating the newest acquisition order, and a newly acquired condition every time the condition is newly acquired by the acquisition unit. The condition, the setting information of the condition, and the order value indicating the newest acquisition order are recorded as a set in the table, and the setting information and the order value recorded in the table are referred to. A data acquisition device comprising: a scheduling unit that controls setting of the condition in the data extraction unit; and an output unit that outputs data acquired by the data extraction unit to a requesting data processing device. apparatus. 21. A condition judging means for judging whether or not the condition forming a set with the setting information indicating that the setting is “absent” is recorded in the table, and the condition judging means. By the means, when it is determined that the condition paired with the setting information indicating that the setting is “absent” is recorded, in the table, the setting information indicating that the setting is “absent” Determining means for determining the condition to be newly set in the data extracting means by referring to the order value forming a pair with the condition from among the conditions forming the set. Item 21. The data acquisition device according to item 20. 22. The scheduling means, wherein in the table, the number of conditions forming a pair with the setting information indicating that the setting is “present” is an upper limit value of the number of conditions that can be set in the data extracting means. By determining whether or not the condition is less than, a setting determining unit that determines whether the condition can be newly set in the data extracting unit, and when the setting determining unit determines that “setting is possible”, The determined condition is newly set in the data extraction unit, and the setting determination unit sets “not settable”.
When it is determined that, in the table, the condition to be deleted from the data extraction unit is selected from among the conditions forming a pair with the setting information indicating that the setting is "present", and the selected condition is selected. 22. The data acquisition apparatus according to claim 21, further comprising: a setting control unit that deletes the condition from the data extraction unit and newly sets the condition determined by the determination unit in the data extraction unit. 23. The determining means sets, in the table, the order value indicating that the acquisition order is the oldest among the conditions forming a set with the setting information indicating that the setting is “absent”. Is determined as the condition to be newly set in the data extraction unit, and the setting control unit determines that the setting is “present” in the table when it is determined that “setting is impossible”. Out of the conditions forming a pair with the setting information indicating the condition, selecting the condition having the order value indicating the oldest acquisition order in the set, and deleting the setting of the selected condition from the data extracting unit. The data acquisition device according to claim 22, characterized in that: 24. The setting means sets, in the table, the order value indicating that the acquisition order is the latest among the conditions forming a set with the setting information indicating that the setting is “absent”. Is determined as the condition to be newly set in the data extraction unit, and the setting control unit determines that the setting is “present” in the table when it is determined that “setting is impossible”. Out of the conditions forming a pair with the setting information indicating the condition, selecting the condition having the order value indicating the oldest acquisition order in the set, and deleting the setting of the selected condition from the data extracting unit. The data acquisition device according to claim 22, characterized in that: 25. The data processing device further includes a replacement requesting unit that requests the schedule unit to replace the condition set in the data extracting unit, in response to a request from the data processing device, The scheduling means controls the replacement of the condition set in the data extracting means by referring to the setting information and the sequence value recorded in the table when the replacement is requested. 21. The data acquisition device according to claim 20, wherein: 26. The scheduling means, when the replacement is requested, determines whether or not the condition paired with the setting information indicating that the setting is “absent” is recorded in the table. When the condition determining unit determines that the condition paired with the setting information indicating that the setting is “absent” is recorded by the condition determining unit, the setting in the table is “ Determining means for determining the condition to be newly set in the data extracting means by referring to the sequence value forming a pair with the condition from among the conditions forming a pair with the setting information indicating "not present" 26. The data acquisition device according to claim 25, comprising: 27. The scheduling unit, further comprising: in the table, the number of the conditions paired with the setting information indicating that the setting is “present” is an upper limit of the number of the conditions that can be set in the data extracting unit. A setting determining unit that determines whether the condition can be newly set in the data extracting unit by determining whether the value is smaller than a value, and when the setting determining unit determines that “setting is possible”, , The determined condition is newly set in the data extracting means, and the setting determining means sets
When it is determined that, in the table, the condition to be deleted from the data extraction unit is selected from among the conditions forming a pair with the setting information indicating that the setting is "present", and the selected condition is selected. 27. The data acquisition device according to claim 26, further comprising: a setting control unit that deletes the condition from the data extraction unit and newly sets the determined condition in the data extraction unit. 28. The setting means sets, in the table, the order value indicating that the acquisition order is the oldest among the conditions forming a set with the setting information indicating that the setting is “absent”. Is determined as the condition to be newly set in the data extraction unit, and the setting control unit determines that the setting is “present” in the table when it is determined that “setting is impossible”. Out of the conditions forming a pair with the setting information indicating the condition, selecting the condition having the order value indicating the oldest acquisition order in the set, and deleting the setting of the selected condition from the data extracting unit. 28. The data acquisition device according to claim 27, wherein: 29. When the data extraction unit succeeds in data extraction under the set conditions, the data extraction unit notifies the schedule unit of the condition. When the schedule unit receives the notification, the schedule unit records the information in the table. 21. The data acquisition apparatus according to claim 20, wherein the replacement of the condition set in the data extraction unit is controlled by referring to the set information and the order value. 30. Upon receipt of the notification, the scheduling means determines whether or not the condition paired with the setting information indicating that the setting is “absent” is recorded in the table. Means, if the condition determining means determines that the condition forming a pair with the setting information indicating that the setting is “not present” is recorded, the setting is “absent” in the table. And determining means to determine the condition to be newly set in the data extracting means by referring to the order value forming a pair with the condition from among the conditions forming a pair with the setting information indicating 30. The data acquisition device according to claim 29, wherein: 31. The scheduling unit, further comprising: in the table, the number of the conditions paired with the setting information indicating that the setting is “present” is an upper limit of the number of the conditions that can be set in the data extracting unit. A setting determining unit that determines whether the condition can be newly set in the data extracting unit by determining whether the value is smaller than a value, and when the setting determining unit determines that “setting is possible”, , The determined condition is newly set in the data extracting means, and the setting determining means sets
When it is determined that, in the table, the condition to be deleted from the data extraction unit is selected from among the conditions forming a pair with the setting information indicating that the setting is "present", and the selected condition is selected. 31. The data acquisition apparatus according to claim 30, further comprising: a setting control unit that deletes the condition from the data extraction unit and newly sets the determined condition in the data extraction unit. 32. The determining unit sets the order value indicating that the acquisition order is the oldest among the conditions forming a set with the setting information indicating that the setting is “absent” in the table. Is determined as the condition to be newly set in the data extraction unit, and the setting control unit determines that the setting is “present” in the table when it is determined that “setting is impossible”. Out of the conditions forming a pair with the setting information indicating the condition, selecting the condition having the order value indicating the oldest acquisition order in the set, and deleting the setting of the selected condition from the data extracting unit. The data acquisition device according to claim 31, characterized in that: 33. The determining means sets, in the table, the order value indicating that the acquisition order is the latest among the conditions forming a set with the setting information indicating that the setting is “absent”. Is determined as the condition to be newly set in the data extraction unit, and the setting control unit determines that the setting is “present” in the table when it is determined that “setting is impossible”. Out of the conditions forming a pair with the setting information indicating the condition, selecting the condition having the order value indicating the oldest acquisition order in the set, and deleting the setting of the selected condition from the data extracting unit. The data acquisition device according to claim 31, characterized in that: 34. The determining means sets the order value indicating that the acquisition order is the oldest among the conditions forming a set with the setting information indicating that the setting is “absent” in the table. Is determined as the condition to be newly set in the data extraction unit, and the setting control unit determines that the setting is “present” in the table when it is determined that “setting is impossible”. 32. The method according to claim 31, wherein the notified condition is selected from the conditions forming a pair with the setting information indicating the condition, and the setting of the selected condition is deleted from the data extracting unit. Data acquisition device. 35. The determination means, in the table, sets the order value indicating that the acquisition order is the newest among the conditions forming a set with the setting information indicating that the setting is “absent”. Is determined as the condition to be newly set in the data extraction unit, and the setting control unit determines that the setting is “present” in the table when it is determined that “setting is impossible”. 32. The method according to claim 31, wherein the notified condition is selected from the conditions forming a pair with the setting information indicating the condition, and the setting of the selected condition is deleted from the data extracting unit. Data acquisition device.