System and method of data transmission/reception

[0002] The present invention relates to a system and method of data transmission/reception for transmitting/receiving a large amount of data via network.

[0003] Various monitoring systems are in the actual use to watch an unattended shop or office at night and protect it from suspicious people or invaders or to monitor a place that is dangerous or inaccessible by people. In this kind of monitoring system, a data transmission/reception system of a so-called client-server type is used.

[0004] This type of data transmission/reception system is made of at least one data-transmitting terminal and a data-receiving server connected thereto via cable or wireless network.

[0005] In this data transmission/reception system, various sensors that detect various states of subjects to be monitored, such as a camera and thermometer, are mounted on its data transmitter. The data collected from such a sensor is transmitted to the data-receiving server. The data-receiving server shapes the data transmitted by the data-transmitting terminal into predetermined formats and accumulates them in its database.

[0006] Some patent applications of monitoring systems have been filed. Japanese Patent Application Non-Examined Publication No. H09-288684 discloses a monitoring system that regularly transmits to an image-collecting server image data acquired by a camera disposed at a place to be monitored, and automatically updates image data on a Web page.

[0007] European Patent Application EP0986259A2 discloses a structure of a network camera monitoring system having a motion detection means. In this structure, image data are transmitted when the motion detection means detects a moving object.

[0008] Japanese Patent Application Non-Examined Publication No. 2000-59759 discloses a monitoring camera system that processes images taken by a monitoring camera, and displays and accumulates the image data only when an abnormality is detected.

[0009] Japanese Patent Application Non-Examined Publication No. 2000-4272 shows a data transmission/reception system utilizing meta data and discloses a structure that coverts accumulated meta data into a format suitable for transmission.

[0010] In these conventional monitoring systems, the format of the data accumulated in the database is defined as a format inherent in each system and thus general use of the accumulated data is difficult.

[0011] The data-receiving server performs analysis (e.g. format conversion) on received data for accumulation in the database. When a large number of data-transmitting terminals that collect different types of data are connected, the data analysis imposes a heavy load on the server.

[0012] In addition, when encoded image data are transmitted or received, how to control attribute information attached to the image data, such as the encoding scheme, image size, recording time, recording period of time and imaging position, poses a problem. In a conventional data transmission/reception system, a header including the image attribute information is added to the head of the image, or image attribute information including information linked to the image data is generated and the image attribute information is managed in a database independently of the image data. However, with these methods, the data format having high dependability on the system deteriorates mutual connectivity with other data transmission/reception system.

[0013] Furthermore, when a data transmission/reception system is used for remote supervision, a huge amount of image data put a large burden on an operator monitoring the image and make the amount of image data accumulated in the database huge.

[0014] Therefore, it is an object of the present invention to reduce the amount of static image data or motion image data (hereinafter referred to as images generically), alleviate the load on a data-receiving server that accumulates the received data in its database, facilitate the accumulation and search of the image data in the database and ease the burden on an operator monitoring the images.

[0015] The system in accordance with the present invention encodes picture signals to generate image data, acquires the attribute information of the image data, generates meta data from the attribute information of the image data, and separates the image data and meta data for transmission.

[0016] At this time, the amount of data can be reduced by transmitting image data and meta data only when predetermined conditions are satisfied, for example, a moving body is detected or abnormal data or data including significant information are detected. This can reduce the amount of data accumulated in a data recipient and thus alleviate the load of data analysis. In addition, this can ease the burden on an operator who visually monitors the image data and prevent inadvertent failure in checking abnormal data and data including significant information.

[0017] Furthermore, the meta data can be made to less system-dependable text-based data with tags by making them compliant with an extensible data description language specification similar to the eXtensible Markup Language (XML). Therefore, mutual cooperation and exchange of such meta data with other systems are easy.

[0018] Inclusion of information acquired by picture analysis operation or instrument data acquired by sensors in the attribute information of the image data allows efficient data analysis and data search of a data recipient.

[0019] FIG. 1 is a block diagram of a data transmission/reception system in accordance with one embodiment of the present invention.

[0020] FIG. 2 is a flowchart illustrating a data transmission procedure in accordance with a first exemplary embodiment of the present invention.

[0021] FIG. 3 is an example of data made by formatting instrument data acquired by a sensor in accordance with the first embodiment of the present invention.

[0022] FIG. 4 is a flowchart illustrating a data reception procedure in accordance with the first embodiment of the present invention.

[0023] FIG. 5 is a flowchart illustrating a procedure for generating static image data in accordance with a second exemplary embodiment of the present invention.

[0024] FIG. 6 is an example of meta data for use in the second embodiment of the present invention.

[0025] FIG. 7 is a flowchart illustrating a procedure for transmitting meta data and static image data in accordance with the second embodiment of the present invention.

[0026] FIG. 8 is a flowchart illustrating a procedure for receiving meta data and static image data in accordance with the second embodiment of the present invention.

[0027] FIG. 9 is a flowchart illustrating a data transmission procedure in accordance with a third exemplary embodiment of the present invention.

[0028] FIG. 10 is an example of meta data for use in the third embodiment of the present invention.

[0029] FIG. 11 is a flowchart illustrating a data transmission procedure in accordance with a fourth exemplary embodiment of the present invention.

[0030] FIG. 12 is a flowchart illustrating a procedure for generating motion image data in accordance with a fifth embodiment of the present invention.

[0031] FIG. 13 is an example of meta data for use in the fifth embodiment of the present invention.

[0032] FIG. 14 is a flowchart illustrating a procedure for transmitting meta data and motion image data in accordance with the fifth embodiment of the present invention.

[0033] FIG. 15 is a flowchart illustrating a procedure for transmitting meta data and motion image data in accordance with a sixth exemplary embodiment of the present invention.

[0034] FIG. 16 is an example of meta data for use in the sixth embodiment of the present invention.

[0035] Exemplary embodiments of the present invention are hereinafter demonstrated with reference to the accompanying drawings.

[0036] 1. First Exemplary Embodiment

[0037] FIG. 1 is a block diagram of a data transmission/reception system in accordance with the present invention. Data transmitters 100-a, 100-b, 100-c, 100-d, and 100-e(hereinafter referred to as data transmitter 100 generically) are disposed at different positions, and acquire data of atmospheres at the different positions. Data transmitter 100 is connected to data-receiving server 201 data via network 301. Disposed in a monitoring center, data-receiving server 201 accumulates received data in database 204, an image recording/encoding unit and the like, and reproduces predetermined data on display 202 of a monitor unit and the like. Details are described afterwards. Network 301 allows mutual communication between data-transmitting terminal 101 and data-receiving server 201. The network includes a wide area network (WAN), local area network (LAN), wireless network, and combinations thereof.

[0038] Data transmitter 100 is made of data-transmitting terminal 101, camera 102 that is connected thereto and acquires picture signals, and at least one sensor 103 for acquiring various instrument data. Data-transmitting terminal 101 has a general interface capable of connecting to an arbitrary sensor 103. Sensors 103 include a thermometer, hygrometer, seismometer, infrared sensor, weight sensor and so on, each of which is capable of connecting to the general interface and used for intended purposes.

[0039] Camera 102 images the atmosphere thereof at the position where the camera 102 is placed and feeds the picture signals into image processor 104. Image processor 104 encodes the picture signals supplied from camera 102 and generates encoded static or motion image data. Encoding schemes of image data are selected for intended purposes, as required. Image formats compliant with the standards can be employed (e.g. JPEG for static pictures, and H.263, MPEG2, or MPEG4 for motion pictures). Image data need not be compressed necessarily. Image processor 104 performs image processing, e.g. analysis for detecting motions of such moving bodies as a person or moving object.

[0040] Image processor 104 has functions of outputting the identifier of image data (file name), image format, data size, recording time, recording period of time (for motion pictures) and image analysis results, together with generated image data. Such information accompanying image data is hereinafter referred to as image attribute information. Such image attribute information is fed into meta data processor 106.

[0041] On the other hand, sensor 103 measures various physical quantities at the positions to be monitored and feeds measured data into instrument data processor 105. A specific kind of sensors 103 is selected in accordance with the physical quantities to be measured, as required. The instrument data measured at sensor 103 is analyzed in instrument data processor 105, and the instrument data or analysis results thereof are fed into meta data processor 106.

[0042] Meta data processor 106 combines the image attribute information and the information linked to image data supplied from image processor 104 with the instrument data supplied from instrument data processor 105 into meta data.

[0043] The information linked to image data is an identifier for specifying the image data, such as a file name of the image data, or address information indicating where the image data are. The meta data are data describing data. In this embodiment, the meta data are the image attribute information associated with the image data generated in image processor 104. The instrument data supplied from instrument data processor 105 are included in the meta data because these instrument data are assumed to be the data associated with image data. For example, it is assumed that these instrument data are acquired at the same time as the generation of the image data, or image data are acquired when the instrument data satisfy predetermined conditions.

[0044] Meta data can be added to the header of image data. However, adding a header inherent in a system to the head of image data deteriorates general versatility of the image data. Therefore, in the present invention, image data and meta data are separated and the information linked to the image data is included in the meta data in order to maintain the correspondence between the image data and the meta data. As a format of the meta data, a standardized extensible data description language similar to the eXtensible Markup Language (XML) is employed. In other words, meta data processor 106 generates text-based meta data having tags.

[0045] Data memory 107 temporarily accumulates image data supplied from image processor 104 and meta data supplied from meta data processor 106, and communication unit 108 sends control messages and data via network 301.

[0046] Data memory 107 is not necessarily required. When data memory 107 does not exist, image data supplied from image processor 104 and meta data supplied from meta data processor 106 are delivered directly to communication unit 108.

[0047] Communication control unit 109 not only controls the communication between data transmitter 100 and data-receiving server 201 but also each of the units in data-transmitting terminal 101. In addition, the communication control unit 109 can also has a function of outputting to meta data processor 106 various kinds of information to be inserted in the meta data. Concrete examples of various kinds of information include the identifier of data-transmitting terminal 101, the position information of data-transmitting terminal 101 utilizing the global positioning system (GPS).

[0048] Data transmitting-terminal 101 can be structured so as to transmit no image data and only instrument data measured at sensor 103. In this case, meta data processor 106 does not generate meta data and formats the instrument data to be transmitted.

[0049] Next, the monitoring center is described below. The monitoring center has data-receiving server 201 and display 202 placed therein. Display 202 is connected to data-receiving server 201 and displays the text data and image data supplied from data-receiving server 201 so that the data are monitored.

[0050] Data-receiving server 201 receives control messages and data at communication unit 203 via network 301. The received data are classified in data control unit 205, where meta data are decoded. The image data and meta data are accumulated in database 204 and fed into image decoder 206. Data control unit 205 also has a function of outputting image data and meta data that have been converted into a user-readable format.

[0051] Image decoder 206 decodes the image data supplied from data control unit 205 and feeds the data into display 202. Communication control unit 207 controls communication unit 203, database 204, data control unit 205 and image decoder 206, each of which constitutes data-receiving server 201, and controls communication with data transmitter 100.

[0052] The main function of data-receiving server 201 is accumulation and control of image data and meta data. Thus, display 202 and image decoder 206 are not essential components of data-receiving server 201.

[0053] FIG. 2 is a flowchart illustrating a data transmission procedure in data transmitter 100. Described in this flowchart is an example of real-time data transmission in which data measurement is performed using sensor 103 and instrument data processor 105, the instrument data is formatted in meta data processor 106, and then the data is transmitted to data-receiving server 201 via communication unit 108 without being accumulated in data memory 107.

[0054] In step S201, if predetermined data transmission start conditions are satisfied or not is determined. When the conditions are satisfied, the procedure goes to step 202 so that data transmission is started. The data transmission start conditions can be arbitrary ones including the following cases:

[0055] (i) where data transmission time is predetermined and the time is reached; and

[0056] (ii) where data transmissions request is given by data-receiving server 201.

[0057] Of Course, Data Transmission Can be Always Performed by Omitting Step 201 of determining if data transmission start conditions are satisfied.

[0058] Step S202 is a data-measuring step, which corresponds to data acquisition of instrument data processor 105 from sensor 103. The instrument data is not only acquired but also can be analyzed and the analysis results can be used as data measurements.

[0059] Next, in step 203, the instrument data are formatted into text data with tags. It is desirable that a standardized extensible data description language, such as the XML, is used as a data format, considering general versatility.

[0060] FIG. 3 shows an example of formatted data measured in step S202. In this example, instrument data are combined on measuring time basis and formatted into text data with tags.

[0061] In step S204, data transmitter 100 sends to data-receiving server 201 a message requesting a permission of data transmission. This message includes information for data-receiving server 201 on whether to permit or refuse data transmission. Such information includes kinds of data (static image data, motion image data, instrument numerical data), a data size, data transfer rate, and data transfer method (file transfer or real-time transfer).

[0062] In step S205, the transmitter waits for a response to the message requesting a permission of data transmission sent in step S204, which is to be given from data-receiving server 201. When no response is given within a predetermined period of time, the procedure goes to step S208 for time-out processing. When a response from data-receiving server 201 is given, the procedure goes to step S206.

[0063] In step S206, the response from data-receiving server 201 is checked. When the response is a permission of data transmission, the procedure goes to step S207 and data transmission to data-receiving sever 201 is executed. When the response is a refusal of data transmission, data transmission is cancelled and the procedure goes to step S208. When the data transmission is cancelled, the instrument data may be abandoned immediately. Alternatively, the instrument data may temporarily be stored and transmitted together with the next instrument data.

[0064] In step S208, whether predetermined end conditions are satisfied or not is determined. When the end conditions are not satisfied, the procedure returns to step S201 and a series of steps are repeated. When the end conditions are satisfied, data transmission is completed. For example, when data transmitter 100 is set to execute data transmission from 6 a.m. to 6 p.m., the predetermined end condition in this case is “it has passed 6 p.m.”

[0065] As mentioned above, a series of steps S201 to S208 allow the data measured in data transmitter 100 to be transmitted to data-receiving server 201.

[0066] In FIG. 2, when the amount of data transmitted to data-receiving server 201 is small and the load on data-receiving server 201 or network 301 is small, steps S204 to S206 can be omitted.

[0067] FIG. 2 describes real-time transmission in which data is not accumulated in data memory 107 and direct data transmission is performed. However, it is also possible to accumulate in data memory 107 the data measured within a predetermined period of time and perform a file transfer of the accumulated data at a time. The information on which method to perform, real-time transfer or file transfer, is transmitted in step S204.

[0068] FIG. 4 is a flowchart illustrating a data receiving procedure executed in data-receiving server 201.

[0069] Step S401 is a step of determining whether to start data reception. In this step, if a message data transmitter 100 has sent in step S204 is received or not is checked. When a message has been received, the procedure goes to step S402. When no message has been received, the data-receiving server continues to wait for a massage from transmitter 100 in the loop in step S401.

[0070] In step S402, the message received from transmitter 100 is analyzed, and whether or not to permit data transmission from transmitter 100 is determined. The criteria of determination are arbitrary. For instance, in a case where the load on data-receiving server 201 is heavy or securing resources for data reception is difficult, data transmission is refused. In other cases, data transmission is permitted. Moreover, authorization of data transmitter 100 can be combined with data transmission and data transmission from unauthorized transmitter 100 can be refused.

[0071] When transmitter 100 is permitted to transmit data in step S402, the procedure goes to step S403. When the transmitter is refused to transmit data, the procedure goes to step S404.

[0072] In step S403, after data-receiving server 201 has prepared for data reception, the communication control unit 207 transmits to transmitter 100 a message for permitting data transmission therefrom and then the procedure goes to step S405. On the other hand, in step S404, data-receiving server 201 transmits to transmitter 100 a message for refusing data transmission therefrom and then the procedure goes to step S407 of determining whether to end.

[0073] In step S405, the data-receiving server receives the data that have been transmitted from data transmitter 100, analyzes the received data, and then the procedure goes to step 406. In step S406, the data-receiving server stores in database 204 the received data that have been analyzed in step S405. These received data are text data with tags as shown in FIG. 3 and shaped into a format appropriate for data search.

[0074] When no data is transmitted within a predetermined period of time although a permission of data transmission is given to data transmitter 100, the communication control unit 207 performs error processing and the procedure goes to step S407. This processing is not shown in the drawing.

[0075] Step S407 is a step of determining whether to end. In this step, if predetermined end conditions are satisfied or not is determined. When the end conditions are not satisfied, the procedure returns to step S401 and a series of steps are repeated. When the end conditions are satisfied, data transmission is completed. Similar to step S208, when data-receiving server 201 is set to operate from 6 a.m. to 6 p.m., the predetermined end condition is “it has passed 6 p.m.”

[0076] When data-receiving server 201 can receive data from a plurality of data transmitters 100, the data-receiving server is made to execute the steps S405 and 406 in parallel for each of data transmitters 100.

[0077] As mentioned above, when the data transmission/reception system executes processing as shown in the flowcharts of FIGS. 2 and 3, the load of received data analysis on data-receiving server 201 can be alleviated because data transmitter 100 formats instrument data into text data with tags before transmitting them to data-receiving server 201. In addition, since the text data with tags are less system-dependable, cooperation and exchange of such data with other systems are easy.

[0078] The first embodiment can be used as a multi-point meteorological observation system, for example. Meteorological observation terminals corresponding to data transmitters 100 are distributed in many places and are connected to a meteorological data collecting server corresponding to data-receiving server 201 via communication network 301. The meteorological observation terminals regularly measure observation data, such as air temperature, humidity, wind velocity, precipitation and seismic intensity, at sensor 103 and transmit the instrument data to the meteorological data collecting server. On the other hand, the meteorological data collecting server accumulates the received data in database 204.

[0079] This system is characterized in that the meteorological data collecting server can accumulate the data without formatting because the instrument data are transmitted as formatted text data with tags from meteorological observation terminals.

[0080] This embodiment can also be constructed as a multi-point meteorological observation system that collects instrument data described by the hyper text markup language (HTML), automatically generates a Web page concerning to meteorological data, and immediately uploads them to the Internet.

[0081] 2. Second Exemplary Embodiment

[0082] In this embodiment, data transmitter 100 transmits to data-receiving server 201 static image data, the meta data thereof, and no instrument data of sensor 103.

[0083] FIG. 5 is a flowchart illustrating a procedure for generating static image data. In step S501, if conditions for starting static image data transmission are satisfied or not is determined. In this step, if predetermined conditions for starting static image data transmission are satisfied or not is determined. When the conditions are satisfied, the procedure goes to step 502 so that static image data transmission is started. For example, when data transmitter 100 is set to transmit data at regular time intervals, data transmission starts at the predetermined time.

[0084] Step S502 is an image encoding step and executed in image processor 104. Image processor 104 encodes picture signals supplied from camera 102 to generate static image data, and feeds them into data memory 107. In step S502, the image processor also performs image analysis to detect if static image data contain such moving bodies as a person or not, and outputs the result thereof to meta data processor 106 together with image attribute information (e.g. the name of a image data file, encoding scheme of the image, width and height of the image, and recording time of the image data).

[0085] Step S503 is a meta data generation step, in which meta data concerning to the image data is generated using image attribute information and image analysis results generated in step S502. The generated meta data are fed into data memory 107 and the procedure goes to step S504. FIG. 6 shows an example of meta data generated in step S503.

[0086] Step S504 is an image data and meta data transmission step. This step is detailed afterwards.

[0087] Step S505 is a step of determining whether to end, in which if predetermined end conditions are satisfied or not is determined after the completion of step S504. When the end conditions are not satisfied, the procedure returns to step S501 and a series of steps are repeated. When the end conditions are satisfied, data transmission is completed.

[0088] Next, step S504 is detailed below with reference to FIG. 7.

[0089] Each of steps S701 to 703 is preprocessing for meta data transmission and executed in communication control unit 109. In step S701, the communication control unit 109 transmits to data-receiving server 201 a message for informing that meta data transmission is about to start. In step S702, the communication control unit 109 waits for a response to the message, which is to given from data-receiving server 201. There are two kinds of responses from data-receiving server 201, i.e. “permission of meta data transmission” and “refusal of meta data transmission”. When no response is received within a predetermined period of time, a heavy load on data-receiving server 201 or communication network 301 is considered and the meta data transmission is cancelled. When a response is received, the procedure goes to step S703.

[0090] Step S703 is a response-checking step. When the response from data-receiving server 201 is a permission of meta data transmission, the procedure goes to step S704. When the response is a refusal, the data transmission is cancelled. In step S704, meta data transmission to data-receiving server 201 is executed.

[0091] Each of steps S705 to 707 is preprocessing for image data transmission and executed in communication control unit 109. In step S705, the communication control unit 109 sends to data-receiving server 201 a message for informing that image transmission is about to start. In step S706, the communication control unit 109 waits for a response to the message, which is to be given from data-receiving server 201. When no response is received within a predetermined period of time, a heavy load on data-receiving server 201 or communication network 301 is considered and the data transmission is cancelled. When a response is given from data-receiving server 201, the procedure goes to step S707.

[0092] Step S707 is a response-checking step. When the response from data-receiving server 201 is a permission of image data transmission, the procedure goes to step S708. When the response is a refusal, the data transmission is cancelled.

[0093] Step S708 is an image data transmission step, in which image data transmission to data-receiving server 201 is executed.

[0094] In FIG. 7, when the amount of data transmitted to data-transmitting server 201 is small and the load on data-receiving server 201 and network 301 is small, steps S701 to S703 and steps S706 and 707 can be omitted and meta data and image data can be transmitted to the server without confirmation.

[0095] FIG. 8 is a flowchart illustrating a meta data and image data receiving procedure executed in data-receiving server 201. Each of steps S801 to 803 and 809 is preprocessing for meta data reception and executed in communication control unit 207.

[0096] In step 801, the communication control unit 207 checks if a communication message has been received from data transmitter 100 or not. When a message has been received, the procedure goes to step S802. When no message has been received, the control unit continues to wait for a communication massage from transmitter 100 in the loop in step S801.

[0097] In step S802, the communication control unit 207 analyzes the message received from transmitter 100 and determines whether or not to permit data transmission therefrom. The criteria of determination are arbitrary. For example, in the case where the load on data-receiving server 201 is heavy or securing resources for data reception is difficult, data transmission is refused. In other cases, data transmission is permitted. Moreover, data transmission from unauthorized transmitter 100 can be refused. When the communication control unit 207 determines to permit data transmission from transmitter 100 in step S802, the procedure goes to step S803. When the communication control unit 207 determines to refuse the data transmission, the procedure goes to step S809.

[0098] Step S803 is a step of notifying a permission of data transmission. After data-receiving server 201 has prepared for data reception, the communication control unit 207 sends to transmitter 100 a message for permitting meta data transmission therefrom.

[0099] Step S804 is a meta data reception step, in which data-receiving server 201 receives meta data (see FIG. 6) from data transmitter 100, and analyzes them. When no data is transmitted within a predetermined period of time although a permission of data transmission is given to data transmitter 100, the communication control unit 207 performs error processing (not shown).

[0100] Step S805 is a database-updating step, in which the meta data analyzed in step S804 is stored in database 204.

[0101] Each of steps S806 to 809 is preprocessing for image data reception and executed in communication control unit 207.

[0102] In step 806, the communication control unit 207 checks if a communication message has been received from data transmitter 100 or not. When a message has been received, the procedure goes to step S807. When no message has been received, the communication control unit 207 continues to wait for a communication massage from transmitter 100 in the loop in step S806. However, when no communication message is received from data transmitter 100 within a predetermined period of time, the communication control unit 207 performs error processing and the procedure goes to step 813.

[0103] Step S807 is a step of determining whether to receive data, in which the communication control unit 207 analyzes the message received from transmitter 100 and determines whether or not to permit data transmission from transmitter 100. When the communication control unit 207 determines to permit data transmission from transmitter 100, the procedure goes to step S808. When the communication control unit 207 determines to refuse the data transmission, the procedure goes to step S809.

[0104] Step S808 is a step of notifying a permission of data transmission. Similar to step S803, in this step, after data-receiving server 201 has prepared for data reception, the communication control unit 207 sends to transmitter 100 a message for permitting data transmission therefrom.

[0105] Step S809 is a step of notifying a refusal of data transmission. In this step, the communication control unit 207 sends to data transmitter 100 a message for refusing the data transmission therefrom and the procedure goes to step S813. In this case, since the received meta data, i.e. the meta data concerning to the image data of which transmission is refused, is unnecessary, the meta data is deleted from database 204.

[0106] Step S810 is a image data reception step, in which data-receiving server 201 receives static image data or motion image data from data transmitter 100 and temporarily accumulates them in a temporary memory, and the procedure goes to step S811. When meta data have been received and no image data is transmitted from data-transmitting terminal 101 within a predetermined period of time although a permission of image data transmission is given to data transmitter 100, data reception is cancelled and the procedure goes to step S814.

[0107] In step S811, the data-receiving server 201 analyzes the meta data received in step S804 and determines if the meta data satisfy predetermined data display conditions or not. When the data display conditions are satisfied in step S811, the procedure goes to step S812. When the data display conditions are not satisfied, the procedure goes to step S813. The data display conditions are arbitrary. For example, when image analysis results or instrument data are found abnormal or data including significant information exist, the data are displayed. This prevents inadvertent failure in checking abnormal data and data including significant information.

[0108] Step S812 is a data display step, in which the image data received in step S810 are decoded, the meta data received in step S804 are converted into user-readable information and fed into display 202.

[0109] Step S813 is a database-updating step, in which the image data received in step S810 are stored in database 204. When the image data is not normally received, the stored meta data concerning to the image data are abandoned.

[0110] Step S814 is a step of determining whether to end, in which if predetermined end conditions are satisfied or not is determined. When the end conditions are not satisfied, the procedure returns to step S801 and a series of steps are repeated. When the end conditions are satisfied, data transmission is completed.

[0111] With this embodiment, attribute information attached to image data is formatted into meta data in data transmitter 100, and the meta data and image data are separately transmitted to data-receiving server 201. This alleviates the load of received data analysis on data-receiving server 201, facilitates image data accumulation and search in the database, and moreover enhances the general versatility of the data.

[0112] This embodiment can be utilized as an image data collecting system using monitoring cameras, for example. Camera terminals corresponding to data transmitters 100 are distributed in many different places and are connected to an image data collecting server corresponding to data-receiving server 201 via communication network. Each of the camera terminals regularly generates image data and the meta data thereof and transmits them to the image data collecting server.

[0113] On the other hand, the image data collecting server accumulates the received image data and meta data into its database without reprocessing. Including the encoding scheme of the image data, data size, imaging positions of fixed cameras, imaging time, and image analysis results, the meta data can be used for searching image data.

[0114] Accumulation of such meta data including the description of image data attributes together with image data facilitates the update of image database. Therefore, this embodiment is appropriate for a data-collecting system involving recording by image data, for observation of natural phenomena (e.g. volcanic activities) and animals and plants, astronomical observation, measurement of volume of traffic, and the like.

[0115] 3. Third Exemplary Embodiment

[0116] This embodiment relates to a monitoring and observation system that transmits and receives static image data including significant information. This embodiment can be applied to an invader detection system and other crime prevention purposes.

[0117] FIG. 9 is a flowchart illustrating a data transmission procedure in case that picture analized results of the data transmitter 100 satisfy predetermined conditions.

[0118] In FIG. 9, step S901 is processing for determining if predetermined conditions for starting data transmission are satisfied or not. When the conditions are satisfied, the procedure goes to step 902 so that data transmission is started. For example, when data transmitter 100 is set to transmit data at five-second intervals, the condition for starting data transmission is “five seconds has elapsed since previous data measurement”.

[0119] In step S902, image processor 104 encodes picture signals supplied from camera 102 to generate static image data. The generated image data are accumulated in data memory 107 and the attribute information of the image data is fed into meta data processor 106.

[0120] In step S903, the image data generated in step S902 are analyzed and the image analysis results are fed into meta data processor 106. In this embodiment, it is assumed, for the description of the following steps, that the image analysis operation is “detection of a person in the image” and the analysis results are supplied as “existence/non-existence of a person”.

[0121] Step S904 is a step of checking an image analysis results, in which if the image analysis results supplied in step S903 satisfy predetermined conditions or not is determined. When the conditions are satisfied, the procedure goes to step S905. When the conditions are not satisfied, the procedure returns to step S901. The determining condition to be satisfied is “existence of a person”.

[0122] Step S905 is a data-measuring step, which corresponds to data acquisition of instrument data processor 105 from sensor 103. The instrument data is not only acquired but also can be analyzed and the analysis results can be used as data measurements. After the completion of step S905, the procedure goes to step S906.

[0123] Step S906 is a meta data generation step. In this step, meta data concerning to the image data are generated using the attribute information of the image data generated in step S902, the image analysis results generated in step S903, and the instrument data generated in step S905. The generated meta data are accumulated in data memory 107, and the procedure goes to step S907.

[0124] FIG. 10 shows an example of meta data supplied from data transmitter 100. The meta data include the name of an image data file, encoding scheme of the image, width and height of the image, imaging date, identifier of a camera used, detection of a person, detection results of an infrared sensor, measurements of a weight sensor.

[0125] Step S907 is an image data and meta data transmission step. Since the details are the same as those shown in FIG. 7, the description is omitted.

[0126] After the completion of steps S907, if predetermined end conditions are satisfied or not is determined in step S908. When the conditions are not satisfied, the procedure returns to step S901 and a series of steps are repeated. When the conditions are satisfied, the data transmission is completed.

[0127] On the other hand, since the procedure for data reception in data-receiving server 201 is the same as that shown in FIG. 8, the description is omitted.

[0128] In this embodiment, since the meta data transmitted from data transmitter 100 include image data analysis results, data-receiving server 201 need not execute image analysis. This alleviates the load on the data-receiving server 201.

[0129] In addition, image data can be searched from database 204 using the image analysis results as a key. Similarly, since the meta data include instrument data acquired at the same time as the generation of the image data, the image data can be searched from the database using the instrument data as a key.

[0130] Furthermore, only when the image analysis results satisfy predetermined conditions, data transmission is executed. This can effectively reduce the amount of image data accumulated in database 204 and alleviate the load on data-receiving server 201 and network 301.

[0131] This embodiment can be used as an invader monitoring system using fixed cameras, for example. Monitoring camera terminals corresponding to data transmitter 100 are distributed at the positions to be monitored and connected to a monitoring center via communication network. Each of the monitoring camera terminals always performs image analysis operation, and transmits image data and the meta data thereof to the monitoring center only when existence of a person is detected in the image. Therefore, in the monitoring center, an operator need not focus on the monitoring operation all the time and can check the image data only when image data is transmitted from the monitoring camera terminals.

[0132] In addition, this embodiment can be used as a vehicle monitoring system. This system reads license plates on running vehicles to be monitored and transmits image data to a monitoring center only when the vehicle bearing a specified license plate is detected.

[0133] 4. Fourth Exemplary Embodiment

[0134] In this embodiment, when instrument data in data transmitter 100 satisfies predetermined conditions, static image data and the meta data thereof are transmitted to data-receiving server 201. In this embodiment, image processing in camera 102 and image processor 104 and data measurement in sensor 103 and instrument data processor 105 are executed in parallel.

[0135] In FIG. 11, step S1101 is processing for determining if predetermined conditions for starting data transmission are satisfied or not. When the conditions are satisfied, the procedure goes to step S1102 so that data transmission is started. When data transmitter 100 is set to perform data measurement at five-second intervals, for example, the predetermined condition for starting data transmission is “five seconds have elapsed since previous data measurement”.

[0136] Step S1102 is a data-measuring step, which corresponds to data acquisition of instrument data processor 105 from sensor 103. In this case, the instrument data is not only acquired but also can be analyzed and the analysis results can be used as data measurements. After the completion of step S1102, the procedure goes to step S1103.

[0137] In step S1103, if the instrument data supplied in step S1102 satisfy predetermined conditions or not is determined. When the conditions are satisfied, the procedure goes to step S1104. When the conditions are not satisfied, the procedure returns to step S1101. An example of the conditions of the instrument data is as follows: temperature data is acquired using a temperature sensor as sensor 103 and “the measured temperature is 30° C. or more”.

[0138] In step S1104, picture signals are fed into image processor 104, in which image data are encoded to generate static image data and image attribute information. The generated image data is accumulated in data memory 107, the image attribute information is supplied to meta data processor 106, and the procedure goes to step S1105.

[0139] In step S1105, the image data generated in step S1102 are analyzed. The image analysis results of the image data are fed into meta data processor 106. Step S1105 is not essential and it can be omitted.

[0140] In step S1106, meta data concerning to the image data are generated using the image attribute information generated in step S1104, the image analysis results generated in step S1105, and the instrument data generated in step S1102, and then fed into data memory 107. Thereafter, the procedure goes to step S1107. An example of the meta data is as shown in FIG. 10.

[0141] Step S1107 is an image data and meta data transmission step. Since the details of this step are the same as the flowchart of FIG. 5, the description is omitted. After the completion of step S1107, the procedure goes to step S1108.

[0142] In step S1108, if predetermined end conditions are satisfied or not is determined. When the conditions are not satisfied, the procedure returns to step S1101 and a series of steps are repeated. When the conditions are satisfied, data transmission is completed.

[0143] On the other hand, since the procedure for data reception in data-receiving server 201 is the same as that of FIG. 8, the description is omitted.

[0144] In this embodiment, data transmission is performed only when the instrument data satisfy predetermined conditions. This can efficiently reduce the amount of image data accumulated in database 204 and alleviate the load on data-receiving server 201 and network 301.

[0145] In addition, since the meta data include instrument data acquired at the same time as the generation of the image data, the image data can be searched from database 204 using the instrument data as a key.

[0146] This embodiment can be used as a system for recording a person's entry into/exit from a room. Monitoring terminals (corresponding to data transmitters 100) that incorporate sensors (e.g. an infrared sensor or a weight sensor) for detecting a person's entry into/exit from a room and imaging cameras are distributed at a doorway of each room in a building. The monitoring terminals are connected to an image-recording server (corresponding to data-receiving server 201) via communication network. When sensor responds, the monitoring terminal acquires the image data of a person who enters into or exits from the room and transmits the image data together with the meta data thereof. The image-recording server accumulates the received image data and the meta data thereof in its database. Since the meta data include the image recording time and analysis results other than the instrument data acquired by sensors, the image including the person entering in/exiting from the room can easily be searched using this information.

[0147] Using sensors with small power consumption and setting the imaging cameras so as to operate only when the sensors respond can reduce the power consumption of the entire system.

[0148] 5. Fifth Exemplary Embodiment

[0149] In this embodiment, motion image data and the meta data thereof are transmitted to data-receiving server 201 when instrument data satisfy predetermined conditions. This embodiment is appropriate for the application to an active volcano observation system. In this embodiment, image processing in camera 102 and image processor 104 and data measurement in sensor 103 and instrument data processor 105 are executed in parallel.

[0150] FIG. 12 is a flowchart illustrating a procedure for generating motion image data in case that instrument data analized results of the data transmitter 100 satisfy predetermined conditions.

[0151] In FIG. 12, steps S1201 to 1203 are processing for determining if the data measured at sensor 103 satisfy predetermined conditions or not. In this embodiment, sensor 103 is made of a seismometer, thermometer, and hygrometer. These sensors 103 perform data measurement and processing in the steps after S1203 when the seismometer senses an earthquake. Since the details performed in steps S1201 to 1203 are the same as those of steps S1101 to 1103 in FIG. 11, the description is omitted.

[0152] In step S1204, image attribute information constituting meta data is generated as preprocessing for motion picture encoding that is to be performed in step S1206.

[0153] In step 1205, meta data concerning to the image data are generated using the image attribute information generated in step S1204 and the instrument data generated in step S1202.

[0154] FIG. 13 shows an example of meta data supplied from data transmitter 100. The meta data include the name of a image file, encoding scheme of the image, width and height of the image, bit rate, imaging date, identifier of a camera used, measurements of the seismometer, temperature, and humidity.

[0155] After the completion of step S1205, the procedure goes to step S1206, in which motion image data and meta data are transmitted. The details are described afterwards.

[0156] After the completion of step S1206, if predetermined end conditions are satisfied or not is determined in step S1207. When the conditions are not satisfied, the procedure returns to step S1201 and a series of steps are repeated. When the conditions are satisfied, data transmission is completed.

[0157] Next, the details of step S1206 are described with reference to FIG. 14. Steps S1401 to 1407 are different from steps S701 to 707 in FIG. 7 in that image data to be transmitted are motion image data instead of static image data, however, basically the same processing is performed in these steps. Therefore, the description is omitted. In steps S1401 to 1407, permission of meta data transmission is confirmed and meta data is transmitted.

[0158] Steps S1408 to 1410 are processing for executing real-time transfer of motion image data. Step S1408 is a motion picture encoding step, in which motion picture signals are supplied from camera 102 into image processor 104 and encoded. The motion image data encoded in step S1408 are a frame or a series of a plurality of frames of motion image data.

[0159] Step S1409 is a motion image data transmission step, in which motion image data generated in step S1408 are transmitted to data-receiving server 201 via data memory 107 and communication unit 108.

[0160] Step S1410 is a step of determining whether to end motion image data transmission, in which if predetermined motion image data transmission end conditions are satisfied or not is determined. When the conditions are not satisfied, the procedure returns to step S1408 and a series of steps are repeated. When the conditions are satisfied, motion image data transmission is completed. For example, when the transmission period of time is set to one minute, transmission of motion image data is stopped after one minute has elapsed since the start of the transmission.

[0161] Since the procedure for data reception in data receiving server 201 is basically the same as that shown in FIG. 8 except for some difference between static pictures and motion pictures, the description is omitted.

[0162] In this embodiment, data transmission is performed only when the instrument data satisfy predetermined conditions. This can efficiently reduce the amount of motion image data accumulated in database 204 and alleviate the load on data-receiving server 201 and network 301. In addition, when data transmitter 100 is used as a monitoring camera, the burden on an operator who observes the received motion image data in data-receiving server 201 can be eased. Furthermore, since the meta data include instrument data acquired at the same time as the generation of the motion image data, the motion image data can be searched from the database using the instrument data as a key.

[0163] In order to use this embodiment as an active volcano observation system using fixed cameras, observation terminals (corresponding to data transmitters 100) that incorporate observation cameras for imaging an active volcano and various sensors, such as a seismometer, are distributed at the positions to be monitored. The terminals are connected to an observation center (corresponding to data-receiving server 201) via communication network. The observation center receives no data from the observation terminals at ordinary times when no earthquake occurs. The observation terminals transmit data to the observation center only when the seismometer senses an earthquake. At this time, the observation terminals transmit to the observation center meta data, i.e. the combination of instrument data acquired by various sensors such as a seismometer. Successively, the observation terminals perform real-time transmission of image data of the active volcano acquired by the observation cameras for a given period of time. Upon receipt of the data from the observation terminals, the observation center gives a warning to the operator and reproduces the received image data and accumulates the image data in the database.

[0164] 6. Six Exemplary Embodiment

[0165] This embodiment is a monitoring and observation system for transmission/reception of temporarily stored motion image data. While the system in accordance with Fifth Exemplary Embodiment performs real-time transfer of motion image data, this embodiment is characterized by transferring temporarily accumulated motion image data.

[0166] FIG. 15 is a flowchart illustrating a procedure for transmitting stored meta data and motion image data in case that picture processing results of the data transmitter 100 satisfy predetermined conditions.

[0167] In FIG. 15, steps S1501 to 1504 are processing for analyzing image data and determining if the image analysis results satisfy predetermined conditions or not. Since processing performed in steps S1501 to 1504 is basically the same as that performed in steps S901 to 904 of FIG. 9 except for the difference between motion pictures and static pictures, the description is omitted.

[0168] Steps S1505 to 1511 are a series of processing for accumulating motion image data and meta data. Step S1505 is a motion picture encoding step, in which picture signals are supplied from camera 102 into image processor 104, a frame of motion image data is encoded, and image attribute information is fed into meta data processor 106. The attribute information includes the name of a motion image data file, encoding scheme, image size and recording time of the motion image data, and bit rate (bps).

[0169] Step S1506 is a motion picture analysis step, in which arbitrary image analysis is performed on the motion image data acquired in step S1505. Step S1506 is executed in image processor 104 and the motion picture analysis results are supplied to meta data processor 106. In this embodiment, it is assumed, for the description of the following steps, that the image analysis operation is “detection of a person in the image” and the analysis results are supplied as “existence/non existence of a person”.

[0170] Step S1507 is a motion image data accumulation step, in which the motion image data generated in step S1505 is accumulated in data memory 107 temporarily.

[0171] Step S1508 is a data-measuring step, which corresponds to data acquisition of instrument data processor 105 from sensor 103. The instrument data is not only acquired but also can be analyzed and the analysis results can be used as data measurements. For example, when sensor 103 is a thermometer, air temperature data are data measurements.

[0172] Step S1509 is a meta data updating step, in which newly acquired motion picture analysis results and instrument data are added to the meta data being generated. Thus change in the motion picture analysis results and instrument data over time is recorded in the meta data.

[0173] Step S1510 is a meta data accumulation step, in which the meta data updated in step S1509 is accumulated in data memory 107. FIG. 16 shows an example of meta data. This meta data include the name of an motion picture file, encoding scheme of the motion picture, width and height of the motion picture, bit rate, imaging date of the motion picture, identifier of a camera used, air temperature data at each measuring time.

[0174] Step S15011 is a step of determining whether to end data accumulation, in which predetermined accumulation end conditions are satisfied or not is determined. When the conditions are not satisfied, the procedure returns to S1505 and a series of steps are repeated. When the condition are satisfied, the data accumulation is completed and the procedure goes to step S1512. For example, when the data accumulation end condition is set so that motion image data is recorded for one minute, data accumulation is stopped after one minute has elapsed since the start of accumulation of the motion image data. A series of processing in steps S1505 to 1511 allows motion image data and the meta data thereof to be stored in data memory 107.

[0175] Step S1512 is a step of transmitting accumulated motion image data and meta data. Since the procedure is basically the same as that described in FIG. 7 except for the difference between motion pictures and static pictures, the description is omitted.

[0176] Step S1513 is a step of determining whether to end, in which if predetermined end conditions are satisfied or not is determined. When the conditions are not satisfied, the procedure returns to S1501 and a series of steps are repeated. When the condition are satisfied, data transmission is completed.

[0177] On the other hand, since the data reception procedure performed in data-receiving server 201 is basically the same as that shown in FIG. 8, the description is omitted.

[0178] In this embodiment, data transmission is performed only when the instrument data satisfy predetermined conditions. This can efficiently reduce the amount of image data accumulated in the database. Moreover, the motion image data are not transferred on real-time basis but they are temporarily accumulated together with meta data and then transferred using a reliable transport protocol. This can alleviate constraints to the communication bandwidth and prevent data loss that may occur during transmission/reception of motion image data.

[0179] This embodiment can be used as a remote image data recording system that must record high definition images. Camera terminals equipped with recording means having a large data capacity (corresponding to data transmitting-terminals 101) are distributed in many places, and connected to a image recording server (corresponding to data receiving-server 201) via communication network. In real-time transfer of high-definition image data, a wide bandwidth must be secured so as to prevent the lack of data; thus the communication cost is high. In this embodiment, high-definition image data are temporarily accumulated and then transmitted to the image-recording server. When accumulated data are transmitted, real-time transfer need not be performed and the data can be transmitted via inexpensive communication routes.

[0180] In each of the above-mentioned embodiments, the data transmission procedure shown in respective flowchart can be implemented as hardware. In addition, all or part of the transmission procedure can be implemented as a software program to simplify the structure of the hardware. Recording this program on a computer-installable recording medium and installing the recording medium into each of a plurality of various computers allow each computer to perform the procedure via software.

[0181] As mentioned above, in accordance with the present invention, data transmitter 100 transmits image data to data-receiving server 201 together with the meta data including various kinds of information concerning to the image data. This can alleviate the load of data analysis on data-receiving server 201 and facilitate maintenance of the image database, such as updating data.

[0182] In addition, in accordance with the present invention, data transmission is performed only when image analysis results or instrument data satisfy predetermined conditions. This can efficiently reduce the amount of image data accumulated in the database and alleviate the load on data-receiving server 210 and network.

[0183] Furthermore, in accordance with the present invention, motion image data and the meta data thereof are accumulated when the instrument data satisfy predetermined conditions, and the accumulated data are transferred on a file transfer basis using a reliable transport protocol. This has advantageous effects of alleviating the constraints to the communication bandwidth and achieving data transmission/reception without any data loss.