JP4206076B2 - Data storage / delivery server system - Google Patents

Description

  The present invention relates to a data storage / delivery server system used in, for example, a remote monitoring system.

  In the remote monitoring system, for example, imaging devices such as Web cameras are arranged at a plurality of sites to be monitored, and time series image data captured by these imaging devices is received by a data storage / delivery server and stored in a storage device. . The accumulated image data is read from the storage device, and the read image data is distributed to a remote monitor device via a communication network.

  A data storage / delivery server used in this type of system includes, for example, one main program, and the main program is executed by a computer to receive image data, and write received image data to a storage device. A process for reading the recorded image data from the storage device and a process for distributing the read image data to a remote monitor device are controlled in an integrated manner (for example, see Patent Document 1).

Japanese Patent Application No. 2004-355724

  However, such a data storage / delivery server has the following problems to be solved. That is, imaging devices such as Web cameras have been improved year by year, and communication protocols and video formats are frequently changed. In addition, communication protocols and video formats are different for each manufacturer, and there is generally no compatibility between them. Therefore, it is necessary to increase the types of imaging devices that can be handled by the data storage / delivery server as the imaging devices advance.

  However, in the configuration of the data storage / delivery server described above, if the number of types of imaging devices that can be handled is increased, the entire main program must be changed and replaced with a new one, which increases the development man-hours and maintenance labor. In general, since a monitoring system needs to perform monitoring work in real time, once the operation of the data storage and distribution server is started, it is not easy to add new functions or increase the types of imaging devices that can be handled. There's a problem. Further, since one main program performs image data reception processing, writing / reading processing, and distribution processing, if heavy processing with a large amount of calculation is executed in reception processing or distribution processing, other processing is performed during that time. Is interrupted or the processing speed is lowered, so that there is a problem that the processing capacity of the entire server is lowered.

  The present invention has been made paying attention to the above circumstances, and the object of the present invention is to make it possible to easily cope with the addition of functions and changes or additions of imaging devices, and the increase in specific processing load in other processing. An object of the present invention is to provide a data storage / delivery server system in which the processing efficiency of the entire apparatus is improved without adversely affecting the apparatus.

In order to achieve the above object, the present invention provides a data storage / delivery server system that receives data transmitted from an information source, stores the data in a storage device, reads the stored data from the storage device, and transmits the data to a monitor device. The following configuration is provided.
That is, a first plug-in process for executing processing for receiving data transmitted from the information source, and a second plug-in for executing processing for writing and reading data received from the storage device. A process and a third plug-in process that executes a process of transmitting data read from the storage device to the monitor device are operated simultaneously, and the first, second, and third plug-in processes Each includes at least one of a PULL type input interface, a PULL type output interface, a PUSH type input interface, and a PUSH type output interface, and transfer of data to and from other plug-in processes using these interfaces. To do .
Further, at least one of communication between the information source by the first plug-in process and communication with the monitor device by the third plug-in process is TCP / IP (Transmission Control Protocol / This is performed according to Internet Protocol (UDP) or UDP / IP (User Datagram Protocol // Internet Protocol), and socket communication is used for data transfer between the communication and the plug-in process.
Further, a schedule setting plug-in process is provided. When sensor information from an external sensor is received via the digital I / O by the schedule setting plug-in process, video data is received from the information source according to the information. When the first plug-in process is instructed to change the data rate to a value set higher than normal, and the emergency recording instruction from the information source is received via the communication network, the emergency recording It is determined whether or not the instruction is generated from an authorized place for changing the schedule, and when it is confirmed that the instruction is issued from an authorized place, the information source according to the emergency recording instruction Instructions to change the data rate for receiving video data to a value set higher than normal So as to provide the first plug-in process.

Therefore, according to the present invention, the first, second, and third plug-in process units perform the data reception process, the received data write and read process to the storage device, and the read data distribution process, respectively. It is executed in a distributed manner. For this reason, when it is necessary to add functions or change the model of the imaging device, it is possible to respond by changing or adding only the plug-in process unit, which is compared to changing the entire main program. , Development man-hours and maintenance work can be greatly reduced.
Further, since it is possible to change or add in units of plug-in process units, it is possible to easily cope with addition of new functions and change of model of an imaging apparatus that can be handled or addition during operation of the server apparatus. Furthermore, when the server device is composed of a plurality of server personal computers, it is possible to change the arrangement of plug-in process units according to the processing load, that is, which server personal computer is executed. It is. For this reason, even if a specific processing load increases, this does not adversely affect other processing, thereby improving the processing efficiency of the entire server device.

Further in the present invention, each of the first, second and third plug improvisation cell scan includes PULL type input interface, PULL type output interface, at least one of the PUSH type input interface and PUSH-type output interface uses these interfaces so that the transfer of data to and from other plug improvisation cell scan. Therefore, first, the second and third plug improvisation cell scan output interface of, can be common to a general-purpose interface, thereby each plug improvisation cell scan can be realized by simple and inexpensive.

  In short, according to the present invention, the first, second, and third plug-in process units perform the data reception process, the received data write and read process to the storage device, and the read data distribution process, respectively. By performing the processing in a distributed manner, it becomes possible to easily cope with the addition of functions and the change or addition of the imaging device, and the device in which the increase in the specific processing load does not adversely affect other processing. It is possible to provide a data storage / delivery server system that improves the overall processing efficiency.

(First embodiment)
FIG. 1 is a block diagram showing a configuration of a monitoring system including a data storage / delivery server according to the first embodiment of the present invention.
The monitoring system of this embodiment connects a plurality of Web cameras C1 to Cn arranged at a monitoring target location to a data storage / delivery server SV0 via a communication network NW, and monitors the data storage / distribution server SV0. Are connected via the communication network NW to a plurality of playback client terminals TM1 to TMm and a management client terminal MM. A sensor group such as a door sensor DS is also connected to the data storage / delivery server SV0 via the communication network NW or the digital I / O 17.

  As the communication network NW, for example, an IP network using a wired LAN (Local Area Network) is used. However, the network is not necessarily limited to a wired LAN, and other computer networks such as the Internet, a CATV (Cable Television) network, and a wireless LAN can be used. It is also possible to use it.

  The Web cameras C1 to Cn are obtained by adding an encoder and a data communication function to the camera body. For example, a JPEG (Joint Photographic Experts Group) video Web camera or an MPEG-4 (Motion Picture Experts Group) is used depending on the encoding method of the encoder. -4) Operates as a video Web camera.

  The JPEG video Web camera (for example, C1) communicates with the data storage / delivery server SV0 according to HTTP / TCP / IP (Hyper Text Transport Protocol / Transmission Control Protocol / Internet Protocol) via the communication network NW. In the transmission of JPEG video data, first, the data storage / delivery server SV0 issues a CGI request for video acquisition to the JPEG video Web camera C1, and the JPEG video Web camera C1 responds to this request to the data storage / delivery server SV0. This is done by transmitting one frame of JPEG video data. That is, the CGI request issuance and video transmission are performed for each frame.

  The MPEG-4 video Web camera (for example, Cn) communicates with the data storage / delivery server SV0 according to RTSP-RTP / UDP (or TCP / IP) via the communication network NW. In the transmission of MPEG-4 video data, first, the data storage / delivery server SV0 requests the MPEG-4 video Web camera 3 to acquire video by RTSP, and in response to this request, the MPEG-4 video Web camera Cn stores and distributes the data. This is done by transmitting MPEG-4 video data to the server SV0 by RTP. This transmission of video data is continued until the data storage / delivery server SV0 issues a stop command to the MPEG-4 video Web camera Cn by RTSP.

On the other hand, the reproduction client terminals TM1 to TMm are constituted by, for example, a workstation or a personal computer, and operate as a JPEG reproduction client terminal or an MPEG-4 reproduction client terminal depending on the type of decoder owned.
The JPEG playback client terminal (eg, TM1) communicates with the data storage / delivery server SV0 according to HTTP / TCP / IP via the communication network NW. For the distribution of JPEG video data, first, a CGI request for video acquisition is issued from the JPEG playback client TM1 to the data storage / delivery server SV0, and the data storage / delivery server SV0 responds to this request to the JPEG playback client terminal TM1. This is done by transmitting one frame of JPEG video data. That is, transmission of JPEG video data is performed for each frame. The JPEG playback client terminal TM1 decompresses the received JPEG video data by a decoder and displays it on the display.

  The MPEG-4 playback client terminal (for example, TMm) communicates with the data storage / delivery server SV0 according to HTTP / TCP / IP via the communication network NW. For the delivery of MPEG-4 video data, first, a CGI request for video acquisition is issued from the MPEG-4 playback client terminal TMm to the data storage / delivery server SV0, and the data storage / delivery server SV0 requests in response to the CGI request. This is done by transmitting MPEG-4 video data for 1 GOV (Group Of VOP (Video Object Plane)) to the original MPEG-4 playback client terminal TMm. That is, transmission of MPEG-4 video data is performed every 1 GOV. The MPEG-4 playback client terminal TMm decompresses the received MPEG-4 video data by the decoder and displays it on the display.

  The management client terminal MM performs the following communication with the data storage / delivery server SV0 according to HTTP / TCP / IP via the communication network NW. That is, the data storage / delivery server SV0 accepts only a command from a specific person having authority by checking a password or the like. The instructions include an instruction for instructing downloading of setting information (setting file), an instruction for instructing uploading of the setting file, and an instruction for instructing change of operation according to the contents of the setting file uploaded to the data storage / delivery server SV0.

  The data storage / delivery server SV0 is constituted by, for example, a personal computer. FIG. 2 is a block diagram showing the hardware configuration. The data storage / delivery server SV0 includes a CPU (Central Processing Unit) 101. A network interface (network I / F) 103, a serial interface (serial I / F) 104, and a memory 106 are connected to the CPU 101 via a bus 102. And a hard disk drive interface (HDD I / F) 107 connected to each other.

  The network I / F 103 performs an interface operation for performing communication with the communication network NW. A digital I / O 105 is connected to the serial I / F 104, and the digital I / O 105 receives detection data of the door sensor DS. The memory 106 is used for the CPU 101 to execute a program. The HDD I / F 107 performs data writing and reading processing with the hard disk drive (HDD) 21.

  FIG. 3 shows the configuration of the recording area in the HDD 21. The HDD 21 includes an OS area 211 for storing an operating system (OS) program group, a video data area 212 for storing video data sent from the Web cameras C1 to Cn, and a video recording program group area 213. Is provided. In the video recording program group area 213, an execution file directory 2131, a setting file directory 2132, and a status information output directory 2133 are stored. The execution file directory 2131 is used to hold an execution file of a program. The setting file directory 2132 is used to hold setting information. The status information output directory 2133 holds a status information file that is output by a plurality of plug-in processes, which will be described later, to indicate their operation status.

  By the way, the data storage / delivery server SV0, as a general system of programs for handling video data, executes a process for receiving video data transmitted from the Web cameras C1 to Cn, and the received data to the HDD 21. A program for executing writing and reading processing; and a program for executing processing for transmitting the video data read from the HDD 21 to the reproduction client terminals TM1 to TMm. These programs are called plug-in processes (hereinafter abbreviated as PP).

  FIG. 1 shows the types of PP provided in the data storage / delivery server SV0 of this embodiment. A master control plug-in process (master control PP) 11, a JPEG reception PP12, an MPEG reception PP13, and a JPEG transmission PP14. MPEG transmission PP15, PreHTTP-PP16, user management PP18, schedule setting PP19, and storage service PP20. The data storage / delivery server SV0 includes a digital I / O 17 in addition to the above PPs.

  Each PP and digital I / O 17 transfers data via the system network 10 in the server. There are two data transfer methods using the system network 10 in the server: a PULL method and a PUSH method.

  The PULL type scheme is a scheme in which the receiving side A has a transmission start trigger as shown in FIG. At the timing when A wants data, a video transmission request is transmitted (1) to the transmitting side B, and data is transmitted from B to A in response to this request (2). Here, receiving data in the PULL type as indicated by A in FIG. 5A is referred to as “PULL type input” and is described as “PULL-IN”. Also, as shown in B of FIG. 5A, transmitting data in the PULL type is referred to as “PULL type output” and is described as “PULL-OUT”.

  The PUSH type method is a method in which the transmission side B has a trigger for starting data transmission as shown in FIG. Data is transmitted (1) to the receiving side A at a timing when the transmitting side B wants to transmit data. Here, as indicated by A in FIG. 5B, receiving data in the push type is referred to as “push type input” and described as “push-in”. Further, as shown in B of FIG. 5B, transmitting data in the push type is called “push type output” and is described as “push-out”.

  As shown in FIG. 4, each PP provided in the data storage / delivery server SV0 transfers the video data in the server SV0, as shown in FIG. 4, the “PULL-IN”, “PULL-OUT”, “PUSH-IN” and “PUSH-IN”. Data transfer interfaces 31 to 34 for “PUSH-OUT” are provided. Each of these data transfer interfaces 31 to 34 has a plurality of channels.

  For example, the PULL-IN interface 31 has channels from ch-0 to ch-n1, and the PUSH-IN interface 33 has channels from ch-0 to ch-n3. The PULL-OUT 32 has channels from ch-0 to ch-n2, and the PUSH-OUT 34 has channels from ch-0 to ch-n4.

  Further, each PP 11-20 is provided with a control port 35 in addition to the video data transfer interfaces 31-34. The control port 35 is for communicating PP control commands, and there is one or more channels for each PP.

  Depending on the application of the plug-in process, a specific data transfer interface may not have the number of channels (= 0). For example, there may be zero “PUSH-IN” and “PUSH-OUT” channels, or zero “PULL-IN” and “PULL-OUT” channels. In addition, although it has input / output channels for video data specific to PP, it does not have the general types of “PUSH-IN”, “PUSH-OUT”, “PULL-IN”, and “PULL-OUT” 31 to 34 channels. There is also a form. Furthermore, as will be described later, there is also a plug-in process that handles only management information of the data storage / delivery server SV0 without handling video data.

  Each of the plug-in processes (PP) 11 to 20 is installed in the data storage / delivery server SV0 in an executable file format, and is activated by executing the installed executable file. The execution files of the plug-in processes (PP) 11 to 20 are stored in the execution file directory 2131 in the HDD 21 shown in FIG. An identification name is given to the plug-in process in operation. However, since multiple plug-in processes of the same type may operate in one data storage / delivery server SV0, the execution file name of the plug-in process is not used as an identification name as it is, and is unique to all plug-in processes. A unique identifier is given. The assignment of the identification name is performed by the administrator's input operation at the management client terminal MM.

  For the plug-in process in operation, a status information file 350 describing the status information is generated, and this status information file 350 is output from the status information output directory 2133 in the HDD 21 shown in FIG. The status information file 350 includes, for example, control port information 351 and a status flag 352 as shown in FIG. The control port information 351 indicates a socket port number when the plug-in process delivers an instruction. The status flag 352 is used to display each status of “in operation”, “abnormal end”, and “normal end”. As will be described later, each plug-in process acquires a socket port number used by itself when it is activated. The PreHTTP-PP 16 checks the status information file 350 to know the operating status of the plug-in process provided in the data storage / delivery server SV0.

Next, functions of each plug-in process provided in the data storage / delivery server SV0 according to this embodiment will be described.
[Master control PP11]
The master control PP11 is a program that operates on the data storage / delivery server SV0. Based on the information described in the setting file 22, the master control PP11 transmits a start command to each PP, sends setting information to each PP, and a setting manager. Receive instructions from each. The master control PP11 is automatically activated when the data storage / delivery server SV0 is activated, and is always operating during the operation of the data storage / delivery server SV0. One master control PP11 exists in the data storage / delivery server SV0. When the data storage / delivery server device is composed of a plurality of servers, one master control PP11 operates on any one of the servers.

[Storage service PP20]
The storage service PP20 is a program that operates on the data storage / delivery server SV0. The storage service PP20 records video data in the HDD 21 and executes processing for reading video data from the HDD 21. This storage service PP20 has a plurality of PUSH-IN channels in the input interface and a plurality of PULL-OUT channels in the output interface.

  In the HDD 21 provided in the data storage / delivery server SV0, a video data area 212 is prepared as shown in FIG. 3, and the video data area 212 is divided into a plurality of videos divided for holding video data. There is a recording channel. Recording video data to the video recording channel is a circular recording method for each channel, that is, video data is recorded from the beginning of the area, and when the video is recorded to the end of the area, the video data is overwritten from the beginning. It is done by a method.

  When the storage service PP20 records video data on each video recording channel, the storage service PP20 attaches the video data to the video data by adding a unique frame number (serial number from 1) independent for each video recording channel. to manage. When the client designates desired video data from the recorded video data, the video data is designated using the video recording channel number and the frame number.

  As shown in FIG. 6, the storage service PP20 of this embodiment has four PUSH-IN channels, four video recording channels (not shown) in the HDD 21, and five PULL-OUT channels. Each PUSH-IN, video recording channel, and each channel number of PULL-OUT are associated with each other.

  On the PUSH-IN side of the storage service PP20, the video data is recorded on the video recording channel having the same number as the channel number of the PUSH-IN that has received the video data. For example, video data input to the 0 channel of the PUSH-IN is recorded on the 0 channel of the video recording channel. On the PULL-OUT side of the storage service PP20, video data is read from the same video recording channel as the channel number of the PUSH-OUT that has received the video data request. For example, when a video request is received on the 0 channel of the PULL-OUT, the video data is read from the 0 channel of the video recording channel, and the read video data is sent from the 0 channel of the PULL-OUT to the request source. Returned to the sending PP.

  The unit of video data input from PUSH-IN and the unit of video data output from PULL-OUT are the same. When the video data to be handled is JPEG video data, the video data is input in units of one frame in PUSH-IN, and the video data is read out in units of one frame in PULL-OUT and returned to the requesting transmission PP. The On the other hand, when the video data to be handled is MPEG-4 video data, the video data is input in units of 1 GOV in PUSH-IN, and the video data is read out in units of 1 GOV in PULL-OUT. Sent to.

  In the storage service PP20, the setting of which receiving PPs 12 and 13 each PUSH-IN channel accepts video data and which transmission PPs 14 and 15 each PULL-OUT channel is permitted to transmit video data is set as a master. It follows the setting information sent from the control PP11.

[JPEG reception PP12]
The JPEG reception PP12 is a program that operates on the data storage / delivery server SV0. The JPEG reception PP12 communicates with the JPEG video Web camera C1 via the communication network NW, and executes processing for receiving JPEG video data and transferring it to the storage service PP20. To do.

  As shown in FIG. 6, the JPEG reception PP 12 of this embodiment includes an input channel (PULL-IN + Thread channel) unique to this PP 12, and further includes a plurality of PUSH-OUT channels and a plurality of PULL-OUT channels. Although not shown in FIG. 6, the JPEG reception PP 12 has a control port (35 in FIG. 4). The PULL-IN + Thread channel is used to communicate with a JPEG video Web camera (for example, C1).

  The communication procedure is set as follows. That is, first, a login command is issued to the JPEG video Web camera to start communication, and then a timely video acquisition request is transmitted according to the reception frame rate of the video data. Then, JPEG video data sent from the JPEG video Web camera is received in response to the video acquisition request, and when reception of the desired video data is completed, a logout command is issued and communication is terminated.

  The JPEG reception PP 12 transmits the received video data from the PUSH-OUT channel to the storage service PP 20 in synchronization with the timing at which the video data is received from the JPEG video Web camera C 1. The JPEG reception PP 12 holds the latest video data received from the JPEG video Web camera C 1 in the memory 106. When a video request is received from the JPEG transmission PP 14 in the PULL-OUT channel of the JPEG reception PP 12, the video data held in the memory 106 is returned to the JPEG transmission PP 14. This enables so-called direct service in which video data captured by the JPEG video Web camera C1 is distributed to the client terminals TM1 to TMm without being accumulated.

  The frame rate at which the JPEG reception PP 12 receives video data from the JPEG video Web camera C 1 depends on the setting information sent from the master control PP 11. Similarly, for the setting of the identification information (IP address information) of the JPEG video Web camera C1 and the video output destination in PUSH-OUT, that is, the identification information of the storage service PP20 and the PUSH-IN channel number of the storage service PP20, According to the setting information sent from the master control PP11.

  The JPEG reception PP 12 of this embodiment communicates with one JPEG video Web camera for each PP. When the data storage / delivery server SV0 receives video from a plurality of JPEG video Web cameras, a plurality of JPEG reception PPs are prepared in the data storage / delivery server SV0. Then, these JPEG reception PPs are operated in a one-to-one correspondence with the plurality of JPEG video Web cameras. Note that one JPEG reception PP set to communicate with each of a plurality of JPEG video Web cameras may be prepared.

  In general, the communication method with the JPEG video Web camera is a unique method that is different for each manufacturer of the JPEG video Web camera. Therefore, for example, when a product of a plurality of manufacturers is used as a JPEG video Web camera, it is necessary to prepare a unique JPEG reception PP 12 for each manufacturer's JPEG video Web camera.

[MPEG reception PP13]
The MPEG reception PP13 is a program that operates on the data storage / delivery server SV0. The MPEG reception PP13 communicates with an MPEG video Web camera (for example, Cn) via the communication network NW to receive MPEG-4 video data. A process of transferring the MPEG-4 video data to the storage service PP20 is executed.

  As shown in FIG. 6, the MPEG reception PP13 of this embodiment includes an input channel unique to the PP13, and further includes a plurality of PUSH-OUT channels and a plurality of PULL-OUT channels. The unique input channel is used for communication with the MPEG video Web camera.

  The MPEG receiving PP 13 transfers the received video data from the PUSH-OUT channel to the storage service PP 20 in synchronization with the timing of receiving the video data from the MPEG video Web camera Cn. The MPEG reception PP 13 holds the latest video data received from the MPEG video Web camera Cn in the memory 106. When a video request is received from the MPEG transmission PP 15 on the PULL-OUT channel of the MPEG reception PP 13, the video data held in the memory 106 is returned to the MPEG transmission PP 15. This enables so-called direct service in which video data captured by the MPEG video Web camera Cn is distributed to the client terminals TM1 to TMm without being accumulated.

  The setting of the identification information (IP address information) of the MPEG video Web camera as the communication partner, the video output destination in PUSH-OUT, that is, the identification information of the storage service PP20, and the PUSH-IN channel number of the storage service PP20 is as follows. According to the setting information sent from the master control PP11.

  Further, the MPEG receiving PP 13 of this embodiment communicates with one MPEG video Web camera for each PP. When the data storage / delivery server SV0 receives video data from a plurality of MPEG video Web cameras, a plurality of MPEG reception PPs are prepared in the data storage / delivery server SV0. These MPEG reception PPs are operated in a one-to-one correspondence with the plurality of MPEG video Web cameras. One MPEG reception PP set to communicate with a plurality of MPEG video Web cameras may be prepared.

[JPEG transmission PP14]
The JPEG transmission PP14 is a program that operates on the data storage / delivery server SV0. When a video request is received from a JPEG playback client terminal (eg, TM1) via the communication network NW, the video is sent to the storage service PP20 or the JPEG reception PP12. Issue a request. Then, in response to this request, a process of transmitting the video data transferred after being read from the storage service PP20 or the video data transferred after being received by the JPEG reception PP12 to the JPEG playback client terminal TM1 is performed. Execute.

  As shown in FIG. 6, the JPEG transmission PP 14 of this embodiment includes a plurality of output channels specific to the PP, and further includes a plurality of PULL-IN channels. Each of the plurality of output channels is used for communication with a JPEG playback client.

  The JPEG transmission PP 14 issues a video request from the PULL-IN channel to the storage service PP 20 or the JPEG reception PP 12 in synchronization with the timing at which the video request is received from the JPEG playback client terminal TM 1. Judgment information for designating the issue destination of the video request, that is, information designating whether the video request is the storage service PP20 or JPEG reception PP12 is included in the argument of the video request sent from the JPEG playback client terminal TM1. ing.

[MPEG transmission PP15]
The MPEG transmission PP15 is a program that operates on the data storage / delivery server SV0. When a video request is received from the MPEG playback client terminal (for example, TMm) via the communication network NW, the MPEG transmission PP15 is sent to the storage service PP20 or the MPEG reception PP13. Issue a video request. In response to this request, the transferred video data read from the storage service PP20 or the video data transferred after being received by the MPEG reception PP13 is transmitted to the requesting MPEG playback client terminal TMm. Execute the process.

  As shown in FIG. 6, the MPEG transmission PP 15 of this embodiment includes a plurality of output channels specific to the PP, and further includes a plurality of PULL-IN channels. Each of the unique output channels is used to communicate with an MPEG playback client terminal.

  The MPEG transmission PP15 issues a video request from the PULL-IN channel to the storage service PP20 or the MPEG reception PP13 in synchronization with the timing at which the video request is received from the MPEG playback client terminal TMm. Judgment information for designating the video request issue destination, that is, information designating whether the video request is the storage service PP20 or the MPEG reception PP13 is included in the video request argument sent from the MPEG playback client terminal TMm. ing.

[PreHTTP-PP16]
The PreHTTP-PP 16 is a program that operates on the data storage / delivery server SV0, and receives a request from the reproduction client terminals TM1 to TMm, and executes a process of transferring the request to each active transmission PP.
There is one program that can wait on port 80 in socket communication. Therefore, in the present embodiment, PreHTTP-PP 16 waits for request communication from the reproduction client terminals TM1 to TMm at the 80th port. If the request communication from the reproduction client terminals TM1 to TMm is addressed to the currently operating transmission PP, for example, the JPEG transmission PP14 or the MPEG transmission PP15, the request communication is taken over by the transmission PP. That is, descriptor passing is used.

After the takeover, communication is possible between the transmission PP of the takeover destination and the reproduction client terminals TM1 to TMm of the request source without going through the PreHTTP-PP16. If the request communication from the reproduction client terminals TM1 to TMm is not addressed to the active transmission PP, the same operation as that of a general HTTP server is performed. For example, the authority check for the requested directory is performed, and the request file is returned or CGI processing is performed.
Moreover, although mentioned later, PreHTTP-PP16 performs the process for starting each PP based on the starting command from master control PP11.

[User management PP18]
The user management PP 18 is a program that operates on the data storage / delivery server SV0, and sets user access authority for each channel. Information indicating which user has what authority for which channel, that is, access authority information is described in the setting file 22. The user management PP18 acquires access authority information from the master control PP11. The access authority determination of the data storage / delivery server SV0 is performed by the user management PP18.

  For example, the following process is performed in order to limit viewing users. That is, when the viewing target is JPEG video data, the JPEG playback client terminal accepts input of user identification information and desired channel viewing information by the user before performing login processing for the JPEG transmission PP 14. In this embodiment, the user identification information is a user name and a password. When the user identification information is input, the JPEG playback client terminal transfers the user identification information to the data storage / delivery server SV0 together with a login request. The user identification information received by the data storage / delivery server SV0 is transferred to the JPEG transmission PP14.

  The JPEG transmission PP 14 does not hold user authority information inside, but sends user identification information to the user management PP 18 to request an authority check. In response to this request, if the response from the user management PP 18 is “authoritative”, the JPEG transmission PP 14 returns a login success to the JPEG playback client terminal. Then, before logging out, the JPEG transmission PP 14 responds to the video request to the designated channel at the time of login sent from the JPEG playback client terminal. In contrast, it is assumed that the response from the user management PP 18 is “no authority”. In this case, the JPEG transmission PP 14 returns a login failure to the JPEG playback client terminal and ends the communication.

  The authority determination process described above and the signal notification process according to the determination result are similarly performed in the case of MPEG video. The MPEG transmission PP 15 receives user identification information in the login process from the MPEG client terminal, and determines whether the login is successful or unsuccessful based on the result of an inquiry to the user management PP 18.

[Schedule setting PP19]
The schedule setting PP19 is a program that operates on the data storage / delivery server SV0, receives information from an external sensor, and instructs the JPEG reception PP12 or the MPEG reception PP13 to change the reception rate based on the received information. . Information such as which received PP is changed to which rate when which signal is received is described in the setting file 22. The data storage / delivery server SV0 of this embodiment receives a sensor signal generated from the door sensor DS or the like by the network I / F 103 shown in FIG. 2 via the communication network NW, and further receives it by the digital I / O 17.

[Digital I / O17]
The digital I / O 17 is a program that operates on the data storage / delivery server SV0, and monitors the digital I / O interface 105 connected to the serial interface 104 shown in FIG. Then, according to an instruction described in a setting file 22 described later, a change in the digital I / O 105 is notified to other PPs.

  Each plug-in process (PP) described above executes processing based on the setting information described in the setting file 22. The setting file 22 is stored in the HDD 21 in the data storage / delivery server SV0. FIG. 7 shows the configuration of the setting information described in the setting file 22.

The setting file 22 includes a setting information group 220 that belongs to the hierarchy L1 and a plurality of setting information groups 221 to 228 that belong to the hierarchy L2.
Of these, first, the setting information group 220 of the layer L1 describes setting information used by the master control PP11, and includes PP existence information 2201, inter-PP connection information 2202, and service channel information 2203.

The PP presence information 2201 describes a list of PPs operating in the data storage / delivery server SV0 (a list of PPs to be activated). When each PP is distributed and arranged in a plurality of data storage / delivery servers as in the second embodiment to be described later, information indicating which server each PP exists in is also described.
In the inter-PP connection information 2202, information indicating which PP's input / output interface (PULL-IN, PULL-OUT, PUSH-IN, PUSH-OUT) is connected to which PP is connected is described. The
The service channel information 2203 describes information indicating which PP's input / output interface is assigned to which service's number channel.

  On the other hand, in layer L2, setting information group 221 for JPEG reception PP, setting information group 222 for MPEG reception PP, setting information group 223 for storage service PP, and setting information group 224 for JPEG transmission PP The setting information group 225 for MPEG transmission PP, the setting information group 226 for PreHTTP-PP, the setting information group 227 for user management PP, and the setting information group 228 for schedule setting PP belong.

  The setting information group 221 for JPEG reception PP includes a “connection Web camera IP address” 2211 indicating the IP address of the JPEG video Web camera C1 as a connection destination, and a reception data rate of video data received from the JPEG video Web camera C1. A “video acquisition rate” 2212 shown and an “output rate table for each output channel” 2213 showing the output data rate to each output channel are described.

  The MPEG reception PP setting information group 222 includes a “connection Web camera IP address” 2221 indicating the IP address of the MPEG video Web camera Cn that is the connection destination, and “output by output channel” indicating the output data rate to each output channel. A “rate table” 2222 is described.

  The storage service PP setting information group 223 includes an “input channel / recording channel correspondence table” 2231 indicating correspondence between input channels and channels on the HDD 21, and an “output channel” indicating correspondence between output channels and channels on the HDD 21. “Recording channel correspondence table” 2232 and “transmission channel / connection permission PP correspondence table” 2233 indicating to which transmission PP the output channel permits transmission of video data are described.

  In the setting information group 224 for JPEG transmission PP, an “output channel / processing content correspondence table” 2241 indicating processing content for each output channel is described. Here, the processing content means, for example, processing for changing the size of video data or processing for applying a mosaic to a part of video.

In the MPEG transmission PP setting information group 225, an “output channel / processing content correspondence table” 2251 indicating processing content for each output channel is described.
The PreHTTP-PP setting information group 226 includes a “request URL / transfer destination PP” indicating a correspondence between the URL specified in the request text from the reproduction client terminals TM1 to TMm serving as a distribution request source and the transfer destination PP. A “correspondence table” 2261 is described. That is, information indicating to which PP the PreHTTP-PP 16 can take over the requested communication from each of the reproduction client terminals TM1 to TMm is described.

  The user management PP setting information group 227 includes “user presence information” 2271 indicating a list of users who can access the data storage / delivery server SV0, and “users by service channel” indicating which users can access which service channels. "Authorization table" 2272 is described.

In the schedule setting PP setting information group 228, a “sensor information / processing response table” 2281 indicating what command is issued to which reception PP when detection data is input from the sensor is described.
As described above, the setting information is divided into the L1 for the master control PP11 and the L2 for other PPs, so that the master control PP11 can have extensibility when the types of PP are increased.

  That is, since the layer L1 is an item of the common format, the same information may be added when the types of PP are increased in the future. The layer L2 is an item that differs depending on the type of PP, but is handled as a black box by the master control PP11. In other words, as will be described later, the master control PP11 performs processing for sending the setting information described in the setting information groups 221 to 228 of the layer L2 to the PPs 12 to 20, but the master control PP11 itself enters the layer L2. No processing is executed based on the setting information described. For this reason, even if the number of types of PP is increased in the future, there is no need to change the master control PP11. This means that PP can be added later to the operating data storage / delivery server SV0.

Next, the operation of the data storage / delivery server SV0 configured as described above will be described.
(1) Operation at startup
FIG. 8 shows the processing procedure and processing contents of the server SV0 at the time of activation.
The data storage / delivery server SV0 first starts up the OS in step 8a, and then starts up the master control PP11 and PreHTTP-PP16, respectively, according to the information described in the batch processing file when the OS is started up.

  When activated, the master control PP11 reads the setting information group 220 in the hierarchy L1 of the setting file 22 in step 8b. Then, from the setting information group 220 of the read setting file 22, it is determined how many servers the data storage / delivery server SV0 is configured. In this embodiment, since the data storage / delivery server SV0 is composed of one server, the server is recognized as one by the determination based on the setting information group 220.

  Next, in step 8c, the master control PP11 inquires of the pre-HTTP-PP 16 about the operational status of the PP, and creates a list of currently active PPs. In this list, the socket port number of each PP is also described. If the data storage / delivery server SV0 is composed of a plurality of servers, the operating status of the PP is inquired to the PreHTTP-PP of all these servers.

  Subsequently, in step 8d, the master control PP11 compares the PP information to be started described in the setting file 22 with the operation status of each PP. As a result of this comparison, if a certain PP exists in the PP information to be activated and is in operation, the PP is left unchanged.

  On the other hand, if a certain PP exists in the PP information to be activated and is not in operation, the PreHTTP-PP 16 is instructed to activate the PP. When the data storage / delivery server SV0 is configured by a plurality of servers, the information of the server where the PP exists is referred to from the setting file 22 and the corresponding PP is activated with respect to the PreHTTP-PP of the corresponding server. Give instructions. When the PreHTTP-PP 16 receives the above command, the PreHTTP-PP 16 performs activation processing of the activation target PP.

  Note that the PP acquires the socket port number used by the PP and outputs the status information file 350 when starting. In addition, the PreHTTP-PP 16 refers to the status information file 350 output by the PP, and transfers the operating status of each PP and the socket port number of the operating PP to the master control PP 11.

On the other hand, when a certain PP does not exist in the PP information to be activated and is in operation, the master control PP 11 instructs the PP to end.
For example, since the data storage / delivery server SV0 is configured as a single unit in this embodiment, the PreHTTP-PP 16 replies to the inquiry from the master control PP11 to the PreHTTP-PP16 that there is no active PP. In response to this reply, the master control PP11 instructs the PreHTTP-PP16 to start the JPEG reception PP12, the MPEG reception PP13, the storage service PP20, the JPEG transmission PP14, the MPEG transmission PP15, the user management PP18, and the schedule PP19. In response to this command, the PreHTTP-PP 16 executes the execution file of the PP to be started and starts the PP.
Thus, all PPs described in the setting file 22 are activated, and unnecessary PPs are stopped.

  When the activation process of each PP is completed, the master control PP11, in step 8e, starts the preHTTP-PP16, JPEG reception PP12, MPEG reception PP13, storage service PP20, JPEG transmission PP14, MPEG transmission PP15, user management PP18, The setting information groups 221 to 228 of the hierarchy L2 of the setting file 22 are sent to the schedule setting PP19.

At this time, the master control PP11 extracts information corresponding to each PP from the inter-PP connection information 2202 of the layer L1, and also sends the extracted connection information to the PP. For each PP, which information should be extracted from the inter-PP connection information 2202 is described in the PP existence information 2201 of the layer L1. Further, the socket port numbers of other PPs to which each PP is connected are also sent from the master control PP11 to each PP.
Thereafter, each PP starts a processing operation according to the setting information 221 to 228 of the layer L2 of the setting file 22 sent from the master control PP11.

  In the present embodiment, 1ch of the JPEG storage service is associated with 1ch of the PULL-OUT of the storage service PP20, 1ch of the MPEG-4 recording service is associated with 2ch of the PULL-OUT of the storage service PP20, and the JPEG direct service. An example will be described in which 1ch of JPEG reception PP12 of JPEG reception PP12 is associated with 1ch of PULL-OUT and 1ch of MPEG direct service is associated with 1ch of PULL-OUT of MPEG reception PP13.

(2) Accumulation and distribution of JPEG video data during normal operation
In the setting information 221 of the layer L2 addressed to the JPEG reception PP12, a table indicating the relationship between the IP address 2211 of the Web camera to be connected, the reception frame rate 2212 of the video data, the output destination PP and its input channel is described. .

  The JPEG reception PP 12 receives JPEG video data from the JPEG video Web camera C 1 indicated by the IP address 2211 at a frame rate specified by the reception frame rate 2212. Then, the received JPEG video data is transferred from the output channel to the PULL-IN of the storage service PP. For example, in FIG. 6, the data is transferred from the output channel ch0 to the push-in (input channel ch1) of the storage service PP20.

  On the other hand, in the setting information 223 of the layer L2 sent from the master control PP11 to the storage service PP20, a correspondence table between the PUSH-IN number, the PULL-OUT number, and the recording channel of the HDD 21 is described. For example, in the example of FIG. 6, the PUSH-IN number (input channel ch1), the PULL-OUT number (output channel ch1), and the recording channel number of the HDD 21 correspond to the same number. When the JPEG video data is transferred from the JPEG reception PP 12, the storage service PP 20 receives this video data through the PUSH-IN input channel ch 1, and this received video data is recorded in the video data area 212 in the HDD 21. Record in ch1.

  The viewing user inputs service channel information and log-in information (user identification information) that he / she wishes to view on a playback client terminal (eg, TM1). The client terminal for playback is provided with JPEG video playback client software, and the terminal executes this software and sends the service channel and login information to the data storage / delivery server SV0.

  The data storage / delivery server SV0 receives the service channel and login information by the PreHTTP-PP 16 and transfers the received service channel and login information to the JPEG transmission PP 14 serving as a service channel window. In this transfer, the management information of socket communication is notified from the PreHTTP-PP 16 to the JPEG transmission PP 14. That is, the descriptor passing described above is performed. Thereafter, direct communication is performed between the client terminal TM1 for reproduction and the JPEG transmission PP14 without going through the PreHTTP-PP16. It is assumed that the service channel desired by the user is 1ch of the JPEG storage service.

  When the JPEG transmission PP 14 receives the service channel and login information from the PreHTTP-PP 16, it makes an inquiry to the user management PP 18. When the user management PP 18 receives the service channel and login information from the JPEG transmission PP 14, the user management PP 18 compares the received login information with the user presence information 2271 of the layer L 2, and returns the comparison result, that is, right / no-right information of the authority to the JPEG transmission PP 14. .

  The JPEG transmission PP14 notifies the reproduction client terminal TM1 of the authority success / failure information received from the user management PP17. For example, when successful, a key indicating authority is issued and sent to the client terminal TM1 as success / failure information. Thereafter, the client terminal TM1 performs communication using the key until logout. On the other hand, if unsuccessful, a message indicating that there is no authority is transmitted to the client terminal TM1, and the communication is disconnected.

  Next, the client terminal TM1 sends the key and the frame number of the video to be received (a value uniquely determined in the service channel) to the JPEG transmission PP14. The JPEG transmission PP 14 determines whether or not it is in a login state based on the key transmitted from the client terminal TM1. If not logged in, the communication is immediately cut off.

On the other hand, if it is in the login state, a frame having the frame number is requested to the corresponding output channel ch1 among the output channels provided in the JPEG storage service PP20. The storage service PP20 reads the video data of the frame number requested from the JPEG transmission PP14 from the recording channel ch1 on the HDD 21, and transfers the read JPEG video data to the JPEG transmission PP14. The JPEG transmission PP14 transmits the JPEG video data transferred from the storage service PP20 from the corresponding PULL-OUT to the requesting client terminal TM1.
When JPEG video data is continuously acquired from the data storage / delivery server SV0 and reproduced as a moving image, the client terminal TM1 requests the JPEG transmission PP14 for video data for each frame.

(3) MPEG video data storage and distribution
In the setting information 222 of the layer L2 addressed to the MPEG reception PP13, a correspondence table between the IP address 2221 of the Web camera to be connected, the output destination PP, and the input channel is described. The MPEG reception PP 13 receives MPEG video data from the MPEG video Web camera Cn indicated by the IP address 2221. Then, the received MPEG video data is transferred from the output channel to the PULL-IN of the storage service PP20. For example, in FIG. 6, the data is transferred to PUSH-IN (input channel ch2) of the storage service PP20 indicated by the output destination PP and its input channel.

When the video data is transferred from the MPEG reception PP13, the storage service PP20 receives the video data on the second channel of PUSH-IN. The received video data is recorded on the recording channel ch2 on the HDD 21.
The viewing user inputs service channel information and login information (user identification information) that he / she wishes to view on a client terminal for reproduction (for example, TMm). The client terminal for reproduction is provided with MPEG video reproduction client software, and the terminal executes the software and sends the service channel and login information to the data storage / delivery server SV0.

  The data storage / delivery server SV0 receives the service channel and login information in the PreHTTP-PP 16 and transfers the received service channel and login information to the MPEG transmission PP 15 serving as a service channel window. In this transfer, socket communication management information is notified from the PreHTTP-PP 16 to the MPEG transmission PP 15. That is, the descriptor passing described above is performed. Thereafter, direct communication is performed between the client terminal TMm for reproduction and the MPEG transmission PP15 without going through the PreHTTP-PP16. The service channel desired by the user is assumed to be 1ch of the MPEG storage service.

  The MPEG transmission PP 15 receives the service channel and login information from the PreHTTP-PP and inquires of the user management PP 17. When the user management PP 18 receives the service channel and login information from the MPEG transmission PP 15, the user management PP 18 compares it with the user presence information 2271 of the layer L 2, and returns the comparison result, that is, right / wrong information of the authority to the MPEG transmission PP 15.

  The MPEG transmission PP15 notifies the reproduction client terminal TMm of the authority success / failure information received from the user management PP18. For example, when successful, a key indicating authority is issued and sent to the client terminal TMm as success / failure information. Thereafter, the client terminal TMm performs communication using the key until logout. On the other hand, if unsuccessful, a message indicating that there is no authority is transmitted to the client terminal TMm, and the communication is disconnected.

  Next, the client terminal TMm sends the key and the GOV number of the video to be received (a value uniquely determined in the service channel) to the MPEG transmission PP15. The MPEG transmission PP15 determines whether or not it is in a login state based on the key transmitted from the client terminal TMm. As a result, if the user is not logged in, the communication is immediately cut off.

On the other hand, in the login state, a frame number frame is requested to 2ch of PULL-OUT of the storage service PP20. The storage service PP20 reads the MPEG-4 video data of the GOV number requested from the MPEG transmission PP15 from the recording channel ch2 on the HDD 21 and transfers it to the MPEG transmission PP15. The MPEG transmission PP15 transmits the MPEG-4 video data transferred from the storage service PP20 from the corresponding PULL-OUT to the requesting client terminal TMm.
When MPEG-4 video data is continuously acquired from the data storage / delivery server SV0 and reproduced as a moving image, the client terminal TMm requests the MPEG transmission PP15 for video data every 1 GOV.

(4) Distribution of JPEG video data using direct service
In order not to make the user viewing the video using the client PC aware of the configuration of the PP inside the data storage / delivery server SV0, a channel number can be specified for each service separately from the PP output channel. This is called a service channel.

  A service exists for each type of function provided to a user. In this embodiment, there are a storage and distribution service for viewing the stored video data and a direct service for viewing the video data received by the receiving PPs 12 and 13 without storing them.

  Here, the direct service is a service for distributing the video data of the Web cameras C1 to Cn to the reproduction client terminals TM1 to TMm in real time as described above. In general, the data storage / delivery server SV0 has higher performance than the Web cameras C1 to Cn. For this reason, if the client terminals TM1 to TMm for reproduction directly access the Web cameras C1 to Cn, the processing load of the Web cameras C1 to Cn increases and distribution becomes difficult. In order to prevent this, real-time video distribution processing for the client PC is performed by the direct service via the data storage / delivery server SV0. Depending on the application, only the direct service may be provided without mounting the video recording HDD 21 in the data storage / delivery server SV0.

  If a PP that performs video data conversion processing is added in the future, a function to be provided to the user as a video conversion service is added, and a PP that processes video data by image recognition and a database that holds the recognition result are managed. If PP is added, a function provided to the user as a recognition service is added. In the storage service PP20, the service may be divided into a channel used for recording JPEG video data and a channel used for recording MPEG-4 video data.

  When receiving the distribution of JPEG video data using the direct service, the viewing user inputs information on the service channel to be viewed and log-in information (user identification information) on a client terminal for reproduction (for example, TM1). The client terminal TM1 for reproduction is provided with JPEG video reproduction client software, and the terminal executes this software and sends the service channel and login information to the data storage / delivery server SV0.

  The data storage / delivery server SV0 receives the service channel and login information by the PreHTTP-PP 16 and transfers the received service channel and login information to the JPEG transmission PP 14 serving as a service channel window. Here, the service channel desired by the viewing user is 1ch of the JPEG direct service.

  The JPEG transmission PP 14 receives the service channel and login information from the PreHTTP-PP 16 and makes an inquiry to the user management PP 18. When the user management PP 18 receives the service channel and login information from the JPEG transmission PP 14, the user management PP 18 compares it with the user presence information 2271 of the layer L 2, and returns the result, that is, right / no-right information of authority to the JPEG reception PP 14.

  The JPEG transmission PP14 notifies the requesting reproduction client terminal TM1 of the authority success / failure information received from the user management PP18. For example, when successful, a key indicating authority is issued and sent to the client terminal TM1 as success / failure information. Thereafter, the client terminal TM1 performs communication using the key until logout. On the other hand, if unsuccessful, a message indicating that there is no authority is transmitted to the client terminal TM1, and the communication is disconnected.

  Next, the reproduction client terminal TM1 sends the key to the JPEG transmission PP14. The JPEG transmission PP 14 determines whether or not it is in a login state based on the key received from the client terminal TM1. As a result, if the user is not logged in, the communication is immediately cut off.

  On the other hand, if it is in the login state, the transfer of video data is requested to 1ch of PULL-OUT of JPEG reception PP12. The JPEG reception PP 12 transfers the latest JPEG video data received from the JPEG video camera C 1 to the JPEG transmission PP 14. The JPEG transmission PP14 transmits the JPEG video data transferred from the JPEG reception PP12 to the reproduction client terminal TM1.

When JPEG video data is continuously acquired from the data storage / delivery server SV0 and reproduced as a moving image, the client terminal TM1 requests the JPEG transmission PP14 for video data for each frame.
One service may be straddled by a plurality of PPs. For example, if there are two or more JPEG receiving PPs, 1ch of the JPEG direct service is set to 1ch of the PULL-OUT of the first JPEG receiving PP, and 2ch of the JPEG direct service is set to the second JPEG receiving PP. Assigned to 1ch of PULL-OUT.

  One service channel may straddle a plurality of PPs, and a plurality of output channels may be assigned to service channels even within the same PP. For example, when there are a plurality of storage services PP, 1ch and 2ch of PULL-OUT of the first storage service PP are assigned to 1ch and 2ch of the JPEG storage service 1ch of PULL-OUT of the second storage service PP. And 2ch are allocated to 3ch and 4ch of the JPEG storage service. The channel number of the service channel may be discrete but not duplicated.

(5) Distribution of MPEG-4 video data using direct service
The viewing user inputs service channel information and login information (user identification information) that he / she wishes to view on a client terminal for reproduction (for example, TMm). The reproduction client terminal TMm is provided with MPEG video reproduction client software, and the terminal TMm executes the software and sends the service channel and login information to the data storage / delivery server SV0.

  The data storage / delivery server SV0 receives the service channel and login information by the PreHTTP-PP 16 and transfers the received service channel and login information to the MPEG transmission PP 15 serving as a service channel window. Here, the service channel desired by the viewing user is assumed to be 1ch of the MPEG direct service.

  The MPEG transmission PP 15 receives the service channel and login information from the PreHTTP-PP 16 and makes an inquiry to the user management PP 18. When the user management PP 18 receives the service channel and login information from the MPEG transmission PP 15, the user management PP 18 compares it with the user presence information 2271 of the layer L 2, and returns the comparison result, that is, right / no-right information of the authority to the MPEG transmission PP 15.

  The MPEG transmission PP15 notifies the requesting reproduction client terminal TMm of the authority success / failure information received from the user management PP18. For example, when successful, a key indicating authority is issued and sent to the client terminal TMm as success / failure information. Thereafter, the client terminal TMm performs communication using the key until logout. On the other hand, if unsuccessful, a message indicating that there is no authority is transmitted to the client terminal TMm, and the communication is disconnected.

  Next, the reproduction client terminal TMm sends the key to the MPEG transmission PP15. The MPEG transmission PP 15 determines whether or not it is in a login state based on the key received from the client terminal TMm. As a result, if the user is not logged in, the communication is immediately cut off.

  On the other hand, if the user is in the login state, the transfer of video data is requested to 1ch of PULL-OUT of the MPEG reception PP13. The MPEG reception PP 13 transfers the latest MPEG video data received from the MPEG video camera Cn to the MPEG transmission PP 15. The MPEG transmission PP15 transmits the MPEG video data transferred from the MPEG reception PP13 to the reproduction client terminal TMm.

  When MPEG video data is continuously acquired from the data storage / delivery server SV0 and reproduced as a moving image, the client terminal TMm requests the MPEG transmission PP15 for video data every 1 GOV.

(6) Operation at the end
FIG. 10 shows the processing procedure and processing contents of the data storage / delivery server SV0 at the end.
A person with administrator authority inputs an end command and login information (user identification information) at the management client terminal MM. The management client terminal MM sends the input termination command and login information to the data storage / delivery server SV0.

  When the master control PP11 of the data storage / delivery server SV0 receives the termination command and the login information via the PreHTTP-PP16, it makes an inquiry to the user management PP18 in step 10a. The user management PP 18 compares the login information received from the master control PP 11 with the user presence information 2271 of the hierarchy L2, and determines the validity of the authority. Then, the determination result is returned to the master control PP11. When the authority is denied by the user management PP 18, the master control PP 11 transmits a message indicating that the authority is not granted to the client terminal MM and disconnects the communication.

  On the other hand, if it is determined that there is an authority, the master control PP11 inquires the pre-HTTP-PP 16 about the operating states of all PPs in step 10b, and creates a list of operating PPs according to the response information. Next, in step 10c, end commands are issued to all PPs in operation based on the created list. For example, if the JPEG reception PP12, the MPEG reception PP13, the storage service PP20, the JPEG transmission PP14, the MPEG transmission PP15, the user management PP18, and the schedule setting PP19 are in operation, an end command is issued to each of these PPs.

  Upon receipt of the termination command, each PP executes termination processing, notifies the master control PP11 that termination is performed immediately before termination, erases the status output file, and terminates. The master control PP11 waits for the response of the end command from each PP, and ends after receiving the response of the end command from all PPs except the PreHTTP-PP16. Even if the end command response is not returned from all the PPs, the process ends after a certain time from the end command issuance. Note that PreHTTP-PP 16 is terminated in the OS termination process of the server SV0.

  In the case where the data storage / delivery server SV0 is an appliance product, the above-described termination process is executed by the master control PP11 even when the power switch is pressed during operation.

(7) Change of plug-in process operation
The operation changing process of the data storage / delivery server SV0 includes (1) changing the setting file 22, (2) notifying the master control PP11 of the change, (3) notifying the change from the master control PP11 to each PP, (4) each The PP is executed according to the procedure of changing the operation according to the description of the new setting file 22.

  The setting file 22 can be changed by “starting a text editor on the data storage / delivery server SV0 and rewriting the setting file 22”, “downloading the setting file 22 to the setting change client 6 once, GUI screen, etc. There are two types of methods: “method of uploading to the data storage / delivery server SV0 after making a change with a tool provided with or directly rewriting with a text editor”.

In this embodiment, the latter method will be described. FIG. 9 is a flowchart showing the operation change processing procedure and processing contents.
First, in step 9a, the administrator performs login processing from the management client terminal MM to the master control PP11 of the data storage / delivery server SV0. At this time, the master control PP11 performs an authentication process using a password or the like in order to determine whether or not a person with administrator authority is operating. At this time, the master control PP11 does not accept another login request after the administrator has logged in or until the administrator logs out or times out without accessing for a certain period of time. That is, the acceptance of the setting change process is exclusive. When another login request is generated during the setting change processing period, an error message is returned to the generation source.

  In step 9b, the management client terminal MM requests the master control PP11 to transmit the setting file (setting information) to be changed, and the master control PP11 reads the requested setting information from the HDD 21 and manages the request source. Download to the client terminal MM.

  The administrator performs an input operation for changing the description content of the downloaded setting information in the management client terminal MM. In order to change the setting information, a tool with a GUI may be prepared and used, or may be changed using a text editor or the like. The management client terminal MM uploads the changed setting file (setting information) to the master control PP11 in step 9c. The master control PP 11 stores the received changed setting file in the setting file directory 2132 in the HDD 21.

  Subsequently, when the administrator inputs an instruction to reflect the changed setting file at the management client terminal MM, the reflection instruction is sent from the management client terminal MM to the PreHTTP-PP 16, and from the PreHTTP-PP 16 to the master control PP 11. Transferred. In accordance with this reflection command, the master control PP11 executes a process of reflecting the changed setting information on the corresponding PP in step 9d.

  Next, the master control PP11 reads the setting information group 220 in the hierarchy L1 of the setting file 22 in step 9e, as in the start-up operation, and the data storage / delivery server SV0 from the setting information group 220 of the setting file 22 thus read. It is determined how many servers are configured. In step 9f, the pre-HTTP-PP 16 is inquired about the operating status of the PP, and a list of currently operating PPs is created.

  Subsequently, in step 9g, the master control PP11 compares the list information of PPs to be activated described in the setting file 22 with the operation status of each PP. As a result of this comparison, if a certain PP exists in the PP information to be activated and is in operation, the PP is left unchanged.

  On the other hand, if a certain PP exists in the PP information to be activated and is not in operation, the PreHTTP-PP 16 is instructed to activate the PP. When the data storage / delivery server SV0 is configured by a plurality of servers, the information of the server where the PP exists is referred to from the setting file 22 and the corresponding PP is activated with respect to the PreHTTP-PP of the corresponding server. Give instructions. When the PreHTTP-PP 16 receives the above command, the PreHTTP-PP 16 performs activation processing of the activation target PP. Further, when a certain PP does not exist in the PP information to be activated and is in operation, the master control PP 11 instructs the PP to end.

  Then, when the activation process of each PP is completed, the master control PP11 performs the activated PreHTTP-PP16, JPEG reception PP12, MPEG reception PP13, storage service PP20, JPEG transmission PP14, MPEG transmission PP15, in step 9h. The setting information groups 221 to 228 of the layer L2 of the changed setting file 22 are sent to the user management PP18 and the schedule setting PP19, respectively.

  Before transmitting each setting information group 221 to 228 of the layer L2 to each PP, the time stamp of the changed setting file is passed from the master control PP11 to each PP, and the setting information is updated in each PP. To determine whether or not Then, only when updated, each PP may request the master control PP11 to transmit the setting file, and the master control PP11 may transmit the setting file hierarchy L2 to the PP.

  Upon receiving the changed setting information, each PP operates in accordance with the description of the received setting information in step 9i. Finally, when the administrator inputs a logout request at the management client terminal MM, the logout request is sent from the management client terminal MM to the master control PP11. The master control PP11 ends the setting information change process in accordance with the logout request.

(8) Operation when adding a plug-in process
The operation when the plug-in process is added to expand the function of the data storage / delivery server SV0 will be described below. Here, a case will be described as an example in which a new JPEG conversion PP for resizing and outputting input JPEG video data is created and this JPEG conversion PP is added to the data storage / delivery server SV0 in operation.

  The execution file of JPEG conversion PP is stored in the PP execution file directory 2131 in the HDD 21 provided in the data storage / delivery server SV0. The executable file is stored on the management client terminal MM by uploading it to the data storage / delivery server SV0, or the executable file created by another personal computer or the like is recorded on a recording medium such as a CD-ROM. And the administrator reads the execution file from the recording medium and copies it to the PP execution file directory 2131 of the data storage / delivery server SV0.

  In addition, along with the addition of the JPEG conversion PP, presence information, connection information, and service channel information of the JPEG conversion PP added to the layer L1 of the setting file 22 are added. It consists of presence information, an execution file name of JPEG conversion PP, and an identification name, and these are described in the setting information group 220 in the hierarchy L1 of the setting file 22.

  The connection information includes, for example, the PUSH-OUT 2ch output destination provided in the JPEG reception PP12 as 1ch of the JPEG conversion PP PUSH-IN, and the PUSH-OUT 1ch output destination of the JPEG conversion PP as the PUSH of the storage service PP20. -IN is set to 3ch, and this information is described in the setting information group 220 in the hierarchy L1 of the setting file 22.

  The service channel information is set so that, for example, 2ch included in the JPEG reception PP12 is associated with 3ch of PULL-OUT of the storage service PP20, and 2ch of JPEG direct service is associated with 1ch of PULL-OUT of JPEG conversion PP. The information is described in the setting information group 220 in the hierarchy L1 of the setting file 22.

  The setting information for the added JPEG conversion PP is also added to the hierarchy L2 of the setting file 22. For example, a method for converting video data input in the push-in ch 1 and information indicating that the output destination of the converted data is output in the push-out ch 1 are added to the hierarchy L 2 of the setting file 22. It is described in the setting information for the converted PP. In this embodiment, the conversion method is resize.

  When the administrator finishes rewriting the configuration file 22 in the management client terminal MM and subsequently inputs a reflection command for the changed setting file, the reflection command is sent from the management client terminal MM to the PreHTTP of the data storage / delivery server SV0. -It is sent to PP16 and is transferred from this PreHTTP-PP16 to the master control PP11. This reflection command may be issued as a signal using a KILL command or the like from the command line of the data storage / delivery server SV0, or may be issued by setting management software on the management client terminal MM. .

  The master control PP11 reads the setting information group 220 in the hierarchy L1 of the setting file 22 as in the operation at the time of starting, and the data storage / delivery server SV0 determines how many servers from the setting information group 220 of the read setting file 22 It is determined whether it is configured. In step 9f, the pre-HTTP-PP 16 is inquired about the operating status of the PP, and a list of currently operating PPs is created.

  Subsequently, the master control PP 11 compares the list information of PPs to be activated described in the setting file 22 with the operation status of each PP. As a result of this comparison, if a certain PP exists in the PP information to be activated and is in operation, the PP is left unchanged. On the other hand, if a certain PP exists in the PP information to be activated and is not in operation, the PreHTTP-PP 16 is instructed to activate the PP. When the data storage / delivery server SV0 is configured by a plurality of servers, the information of the server where the PP exists is referred to from the setting file 22 and the corresponding PP is activated with respect to the PreHTTP-PP of the corresponding server. Give instructions. When the PreHTTP-PP 16 receives the above command, the PreHTTP-PP 16 performs activation processing of the activation target PP. Further, when a certain PP does not exist in the PP information to be activated and is in operation, the master control PP 11 instructs the PP to end.

  When the activation process of each PP is completed, the master control PP 11 sends the changed setting information group L2 of the setting file 22 to each activated PP. It should be noted that the sending of the setting information group in the layer L2 of the setting file 22 may be performed only for the newly operated JPEG conversion PP.

  Upon receiving the changed setting information, each PP operates according to the description of the received setting information. Further, the JPEG conversion PP in which the setting information group is newly added to the hierarchy L2 of the setting file 22 also operates. Finally, when the administrator inputs a logout request at the management client terminal MM, the logout request is sent from the management client terminal MM to the master control PP11. The master control PP11 ends the function addition process in accordance with the logout request.

(9) Operation when deleting a plug-in process
The deletion process of the plug-in process is necessary to limit the function of the data storage / delivery server SV0. An example of deleting the plug-in process will be described taking as an example the case of deleting the added JPEG conversion PP.

  The administrator uses the management client terminal MM to delete the presence information, connection information, and service channel information related to the JPEG conversion PP from the setting information group 220 of the layer L1 for the setting file 22 downloaded from the data storage / delivery server SV0. I do. At the same time, an operation for deleting the setting information group for JPEG conversion PP in the layer L2 of the setting file 22 is performed.

  After the deletion operation of the setting information group is finished and the changed setting file is uploaded to the data storage / delivery server SV0, when the administrator inputs a setting file reflection command, the reflection command is sent from the management client terminal MM. It is sent to the PreHTTP-PP16 of the data storage / delivery server SV0, and transferred from the PreHTTP-PP16 to the master control PP11.

  Upon receiving this reflection command, the master control PP11, as with the operation at the time of startup, grasps the operating status of the server, inquires the operating status of the PP from the PreHTTP-PP16, and creates a list of currently operating PPs. To do. Subsequently, the master control PP 11 compares the PP list information to be activated described in the setting file 22 with the operation status of each PP, and performs activation processing for each PP based on the comparison result. Then, the setting information group of the layer L2 of the setting file 22 is sent to the operating PP. At this time, the execution file of the JPEG conversion PP to be deleted is deleted. Note that the executable file may be left for later use.

(10) When acquiring sensor signals via the communication network NW
If the JPEG reception PP 12 transfers the received video data to the channel ch 1 of the storage service PP 20 and receives it normally from the JPEG video Web camera C 1 at 1 fps, and 30 fps when an emergency recording instruction is received. Suppose that it is described as receiving.

  Normally, the JPEG reception PP 12 receives JPEG video data from the JPEG video Web camera C 1 at 1 fps, and transmits the received video data to the channel ch 1 of the storage service PP 20. The JPEG video Web camera C1 sends an emergency recording instruction to the data storage / delivery server when the conditions are met according to an internal determination routine (whether the video change has exceeded a threshold value, or a specific area has moved). Issued to SV0.

  The emergency recording instruction is received by the PreHTTP-PP 16 of the data storage / delivery server SV0 via the communication network NW. The PreHTTP-PP 16 transfers the received emergency recording instruction to the schedule setting PP 19. The schedule setting PP19 determines whether or not the emergency recording instruction is generated from a place where the schedule change authority is authorized. Here, it is determined whether or not the image originates from the JPEG video Web camera C1.

  When issued from the JPEG video Web camera C1, since there is an authority, the schedule setting PP 19 instructs the JPEG reception PP 12 to record JPEG video data at a recording rate of 30 fps at the time of emergency recording instruction. The JPEG reception PP 12 receives the instruction of the schedule setting PP 19 and changes the reception data rate to 30 fps. An instruction from the schedule setting PP 19 is received by a control port (not shown in FIG. 6) of the JPEG reception PP 12.

  Similarly, the cancellation instruction of the emergency recording instruction is issued from the JPEG video Web camera C1, and the JPEG reception PP 12 receives an instruction at 1 fps which is a normal recording rate via the PreHTTP-PP 16 and the schedule setting PP 19. .

(11) When receiving sensor signals via digital I / O
Temporarily, the JPEG reception PP 12 transfers the received video data to the channel ch 1 of the storage service PP 20, and normally receives it at 1 fps from the JPEG video Web camera C 1, and receives an emergency recording instruction from the digital I / O 17. In this case, it is assumed that reception is performed at 30 fps.

  The digital I / O 17 is connected to the door sensor DS. The door in which the door sensor DS is installed is normally closed, and the JPEG video Web camera C1 is installed at an angle for photographing the door in which the door sensor DS is installed, and records video data during the period when the door is open.

  Each time the door is opened and closed, the sensor signal of the door sensor DS changes, and the sensor information input to the digital I / O 17 changes accordingly. The schedule setting PP 19 monitors sensor information input to the digital I / O 17. In this state, if the sensor information of the digital I / O 17 changes to a state indicating that the door is open, the schedule setting PP 19 instructs the JPEG reception PP 12 to receive video at 30 fps. Similarly, if the sensor information of the digital I / O 17 changes to a state indicating that the door is closed, the schedule setting PP 19 instructs the JPEG reception PP 12 to receive video at 1 fps.

  As described above, in the first embodiment, the data storage / delivery server SV0 includes the master control PP11, PreHTTP-PP16, JPEG reception PP12, MPEG reception PP13, storage service PP20, JPEG transmission PP14, MPEG transmission PP15, and user management PP18. , And schedule setting PP19 are provided so as to be operable independently of each other. Each PP has an input / output interface suitable for the use among PULL-IN, PULL-OUT, PUSH-IN, and PUSH-OUT, and video data and control between the PPs by these input / output interfaces. Data is transferred.

  Accordingly, reception processing of video data from the Web cameras C1 to Cn, writing processing and reading processing of the received video data to the HDD 21, and processing of distributing the read video data to the reproduction client terminals TM1 to TMm. Are executed in a distributed manner in each PP. For this reason, when it becomes necessary to add a new function or to change or add a camera model, it is possible to respond by changing or adding only the PP, thereby developing compared to changing the entire program. Man-hours and maintenance work can be greatly reduced. In addition, since changes or additions in units of PP are possible, it is possible to easily cope with addition of new functions and change of camera models and additions that can be handled even during operation of the data storage / delivery server SV0.

  A JPEG output Web camera reception PP is prepared for the JPEG output Web camera, and an MPEG-4 Web camera reception PP is prepared for the MPEG-4 output Web camera. Furthermore, since the JPEG output Web camera also has a different communication protocol depending on the manufacturer, a reception PP is prepared for each protocol.

  The input data is not limited to video data, but may be audio data or sensor information. In this case, a dedicated reception PP is prepared for each data type and communication protocol for audio data and sensor data. Also on the video data output side, a dedicated communication PP is prepared for each type of data and communication protocol handled by the monitor device for connection with the monitor device.

  In connection with an external device such as a Web camera or a monitor device, communication is performed using a communication protocol for each device, but communication between PPs and communication within a server uses a communication protocol for PPs. For this reason, in communication between PPs, it is not necessary to be aware of the difference in protocol between manufacturers and models.

  Even when a new PP is added, communication is performed using a protocol for communication between PPs. Therefore, the existing PP can communicate with a new PP without change. When developing a new PP, an existing routine can be used for a part for communication between PPs, and therefore a part that can be newly developed is only a protocol part for communicating with an external device. For this reason, development is simplified, and man-hour reduction and cost reduction can be realized. A large number of dedicated multi-functional PPs are prepared, and which PPs are operated and which PPs are used for video data can be changed by setting information. A high storage and distribution server can be realized.

(Second Embodiment)
FIG. 12 is a schematic configuration diagram of a monitoring system including a data storage / delivery server device according to the present invention. In the figure, the same parts as those in FIG.
The data storage / delivery server apparatus according to this embodiment connects a plurality of (four in the figure) servers SV1 to SV4 via a communication network NW, and processes a plurality of PPs necessary for the apparatus to each of the servers SV1 to SV4. Is configured so as to be distributed.

  The server SV1 is responsible for the overall control function of the entire data storage / delivery server device and the storage function for JPEG video data, and includes a hard disk drive (HDD) 115 for JPEG recording as shown in FIG. As plug-in processes, a master control PP110, a PreHTTP-PP111, a user management PP112, a schedule setting PP113, and a storage service PP114 are provided. The HDD 115 stores a setting file 116 for managing PP operations of the entire apparatus. The setting file 116 is hierarchized into hierarchies L1 and L2, similar to the one shown in FIG. 7. The setting information group used by the master control PP 110 is in the hierarchy L1, and all other PPs are in the hierarchy L2. Each group of setting information is stored.

  The server SV2 has an MPEG video data storage function, and includes a hard disk drive (HDD) 122 for MPEG recording as shown in FIG. In addition to the PreHTTP-PP 120, a storage service PP121 is provided as a plug-in process.

  The server SV3 has a function of receiving JPEG video data and MPEG video data from the Web cameras C1 to Cn. As shown in FIG. 15, in addition to the PreHTTP-PP130, a plurality of JPEG reception PP131 to the plug-in process are provided. 13i and a plurality of MPEG reception PPs 141 to 14j.

  The server SV4 has a function of transmitting JPEG video data and MPEG video data to the reproduction client terminals TM1 to TMm. As shown in FIG. 15, in addition to PreHTTP-PP150, JPEG transmission PP151 and MPEG transmission are performed as a plug-in process. PP152 is provided.

  Each PP provided in each of the servers SV1 to SV4 is selected from PULL-IN, PULL-OUT, PUSH-IN, and PUSH-OUT in accordance with the application, as in the first embodiment. It has a general-purpose input / output interface. By performing socket communication using these input / output interfaces, communication can be performed not only between PPs in the same server but also between PPs of different servers via the communication network NW.

Next, the operation of the apparatus configured as described above will be described.
In the server SV1, the master control PP110 and the PreHTTP-PP111 are activated after the OS is activated. The user management PP 112, the schedule management PP 113, and the storage service PP 114 are activated by the PreHTTP-PP 111 when the master control PP 110 commands the Pre HTTP-PP 111 to start the operations of the PPs 112 to 114.

  In the server SV2, the PreHTTP-PP 120 is first activated after the OS is activated. The storage service PP121 is activated by the PreHTTP-PP 120 when the master control PP110 of the server SV1 instructs the PreHTTP-PP 120 to start the operation of the storage service PP121.

  In the server SV3, the PreHTTP-PP 130 is first activated after the OS is activated. In the JPEG reception PP groups 131 to 13i and the MPEG reception PP groups 141 to 14j, the master control PP110 of the server SV1 instructs the PreHTTP-PP 130 to start the operations of the JPEG reception PP groups 131 to 13i and the MPEG reception PP groups 141 to 14j. Is activated by the PreHTTP-PP 130.

  In the server SV4, the PreHTTP-PP 150 is first activated after the OS is activated. The JPEG transmission PP 151 and the MPEG transmission PP 152 are activated by the PreHTTP-PP 150 when the master control PP 110 of the server SV 1 commands the Pre HTTP-PP 150 to start the operations of the JPEG transmission PP 151 and the MPEG transmission PP 152.

  The master control PP110 of the server SV1 sends setting information for each PP (setting information group belonging to the layer L2 of the setting file 116) to each activated PP via the intra-server network or the communication network NW. Each PP stores the setting information group sent from the master control PP 110 of the server SV1, and thereafter starts processing according to the contents of the setting information of this setting information group.

(1) Accumulation and distribution of JPEG video data
Each of the JPEG reception PPs 131 to 13i receives JPEG video data from the JPEG video Web camera specified by its own setting information belonging to the level L2 of the setting file 116. The JPEG video data is transferred to the storage service PP114 of the server SV1 via the communication network NW, and is recorded on the recording channel of the HDD 115 by the storage service PP114.

  Further, when a video distribution request is transmitted from the playback client terminal (eg, Tm1) in this state, the video distribution request is received by the PreHTTP-PP 150 of the server SV4 and transferred from the PreHTTP-PP 150 to the JPEG transmission PP 151. . The JPEG transmission PP 151 inquires of the user management PP 112 of the server SV1 via the communication network NW whether or not the viewing user who uses the requesting reproduction client terminal has the authority to access the channel. As a result of the response, if there is authority, JPEG video data is acquired from the storage service PP114 of the server SV1 via the communication network NW, and this JPEG video data is transmitted to the requesting reproduction client terminal Tm1. When the requesting viewing user does not have the channel access right, a message to that effect is transmitted to the requesting reproduction client terminal TM1.

(2) MPEG video data storage and distribution
Each of the MPEG reception PPs 141 to 14j receives MPEG video data from an MPEG video Web camera designated by its own setting information belonging to the hierarchy L2 of the setting file 116. The received MPEG video data is transferred to the storage service PP121 of the server SV2 via the communication network NW, and is recorded on the recording channel of the HDD 122 by the storage service PP121.

  In this state, when a video distribution request is transmitted from a playback client terminal (eg, TMm), the video distribution request is received by the PreHTTP-PP 150 of the server SV4 and transferred from the PreHTTP-PP 150 to the MPEG transmission PP 152. . The MPEG transmission PP 152 inquires of the user management PP 112 of the server SV1 via the communication network NW whether or not the viewing user who uses the requesting reproduction client terminal has the authority to access the channel. As a result of the response, if there is an authority, MPEG video data is acquired from the storage service PP121 of the server SV2 via the communication network NW, and this MPEG video data is transmitted to the requesting reproduction client terminal TMm. When the requesting viewing user does not have the channel access right, a message to that effect is transmitted to the requesting reproduction client terminal TMm.

  As described above, in the second embodiment, four servers SV1 to SV4 are connected via the communication network NW, and a plurality of PPs are distributed to each of the servers SV1 to SV4 in consideration of the processing load. I have to. For this reason, compared with the case where all PPs are processed by one server, efficient processing can be realized without using an expensive server with high processing capability. Further, even if one of the servers SV2 to SV4 goes down, it is possible to execute other functions excluding the functions of the server without any trouble as before, thereby maintaining high system reliability. be able to.

(Third embodiment)
(1) Examples of PP to be added
[PP receiving video data from multiple cameras]
FIG. 17 shows an example of the functional configuration of a multi-camera video reception PP that receives video data from a plurality of Web cameras.
The plurality of camera video reception PPs are programs that operate on a data storage / delivery server connected to a plurality of Web cameras (three in the figure) C1 to C3 via a communication network NW.

  The activation of the multi-camera video reception PP is activated by the PreHTTP-PP when an activation command for the multi-camera video reception PP is issued from the master control PP in the data storage / delivery server to the PreHTTP-PP. After startup, the master control PP sends a set information group addressed to itself belonging to the layer L2 to the multi-camera video reception PP.

  The multi-camera video reception PP includes PP individual communication control units 41 to 43 corresponding to the Web cameras C1 to C3, a control port 44, a PULL-OUT channel group 45, and a PUSH-OUT channel group 46. Is provided. The setting information for the multi-camera video reception PP describes the number of Web cameras, the IP address of each Web camera, the frame rate, and output destination PP information.

  The multi-camera video reception PP receives video data from each of the plurality of Web cameras C1 to C3 in accordance with the instruction of the setting information, and receives the received video data from the PULL-OUT channel group 45 or the PUSH-OUT channel group 46 as an output destination. To the PP. Note that an output destination may be set for each of the Web cameras C1 to C3, and the video data received from each of the Web cameras C1 to C3 may be transferred to the set output destination. Further, the video data received from the plurality of Web cameras C1 to C3 may be processed and converted into one video data, and then transferred to the output destination PP.

  When the PUSH-OUT 46 is used as an output interface, video data is sent to an output destination specified by the PUSH-OUT 46, triggered by input from the Web cameras C1 to C3. On the other hand, when PULL-OUT45 is used as an output interface, the latest video data is held in PULL-OUT45. When the video request is received from the JPEG transmission PP or the MPEG transmission PP, the held latest video data is transmitted to the JPEG transmission PP or the MPEG transmission PP.

  When the multi-camera video reception PP is used, for example, video data of two Web cameras arranged on both sides of the door are combined or multiplexed and held as one system of video data. Then, this one system of video data can be transmitted to the transmission PP. It is also possible to replace some Web cameras with microphones, synthesize video data and audio data, and transmit them to the transmission PP. Furthermore, data other than video data and audio data, for example, data such as sensor information and position information can be combined or multiplexed in the multi-camera video reception PP and transmitted to the transmission PP.

[Transmission PP with multicast distribution function]
FIG. 18 is a diagram illustrating an example of a functional configuration of a multicast transmission PP that multicasts the same video data to a plurality of reproduction client terminals TM1 to TMm.
The multicast transmission PP is a program that operates on a data storage / delivery server in which a plurality of reproduction client terminals TM1 to TMm are connected via a communication network NW.

  The multicast transmission PP is activated by the PreHTTP-PP when a master transmission PP in the data storage / delivery server issues a multicast transmission PP activation command to the PreHTTP-PP. After the activation, a set information group belonging to the layer L2 is sent from the master control PP to the multicast transmission PP.

  The multicast transmission PP includes a control port 51, a PULL-IN channel 52, a PUSH-IN channel 53, and a PP individual communication control unit 54. The PP individual communication control unit 54 has a communication protocol for performing communication with the reproduction client terminals TM1 to TMm via the communication network NW.

  The video data input to the PULL-IN 52 may be distributed by the PP individual communication control unit by multicast. However, when the PP individual communication control unit actively operates, the video data from other PPs can be transmitted using the PULL-IN 52. Data may be received, and the received video data may be distributed by multicast. This multicast transmission PP is used, for example, when it is desired to show the same video data to several hundred people at the same time.

[Transfer type PP]
19, 20, 21, and 22 are diagrams showing different embodiments of the transfer conversion type PP.
The transfer conversion type PP is a program that operates in a data storage / delivery server having a communication interface for connecting to the communication network NW.

  The activation of the transfer conversion type PP is activated by the PreHTTP-PP when a transfer conversion type PP activation command is issued from the master control PP in the data storage / delivery server to the PreHTTP-PP. After the activation, the master control PP sends its own setting information belonging to the layer L2 to the transfer conversion type PP.

  In the embodiment shown in FIG. 19, the transfer conversion type PP includes a PULL-IN 61 that receives video data, a control port 62, a PULL-OUT group 63, a PUSH-OUT group 64, and a conversion routine 65. This transfer conversion type PP acquires video data from another PP using PULL-IN 61 and converts this video data into a predetermined data format by a conversion routine 65. Then, the converted video data is transmitted from the PUSH-OUT 64 to the transmission destination PP designated by the setting information, or is transmitted to the PP that has requested the PULL-OUT 63 to transfer the video.

  In the conversion routine 65, for example, resizing of JPEG video data and changing of the bit rate of MPEG video data are performed. Note that it is also possible to transfer the input video data as it is to the output destination PP without converting the video data by the conversion routine 65. For example, video data transferred from a specified channel of the storage service PP can be used to transfer to another channel. The other output destination channel may be another channel in the same storage service PP or another storage service PP.

  In the embodiment shown in FIG. 20, the transfer conversion type PP includes a plurality (three in the figure) of PULL-INs 71 to 73 as input interfaces for receiving video data. Other components are the same as those in FIG. The transfer conversion type PP acquires video data from other PPs using the PULL-INs 71 to 73, and combines or converts the acquired video data by a conversion routine 74. Then, the converted video data is sent from the PUSH-OUT 64 to the destination PP designated by the setting information, or sent to the PP that has requested the PULL-OUT 63 to transfer the video.

  The transfer conversion type PP of this embodiment has a function of synthesizing video data recorded in different channels of the storage service PP, or synthesizing different data such as video data and audio data, and outputting the synthesized video data. Used as PP.

  In the embodiment shown in FIG. 21, the transfer conversion PP includes a PUSH-IN 81 that receives video data, a control port 62, a PULL-OUT group 63, a PUSH-OUT group 64, and a conversion routine 82. This transfer conversion type PP acquires video data from another PP using the PUSH-IN 81 and converts this video data into a predetermined data format by a conversion routine 82. Then, the converted video data is transmitted from the PUSH-OUT 64 to the transmission destination PP designated by the setting information, or is transmitted to the PP that has requested the PULL-OUT 63 to transfer the video.

  The transfer conversion type PP of this embodiment is used as a PP having a function of converting the format of video data received by the receiving PP and transferring the video data having the converted format to the storage service PP, for example.

  In the embodiment shown in FIG. 22, the transfer conversion type PP includes a plurality (three in the figure) of PUSH-IN 91 to 93 as input interfaces for receiving video data. Other components are the same as those in FIG. The transfer conversion type PP acquires video data from other PPs using the PUSH-IN 91 to 93, and synthesizes or converts the acquired video data by a conversion routine 94. Then, the converted video data is sent from the PUSH-OUT 64 to the destination PP designated by the setting information, or sent to the PP that has requested the PULL-OUT 63 to transfer the video.

  The transfer conversion type PP of this embodiment is used, for example, to capture video data, audio data, and sensor information from the receiving PP, synthesize or multiplex them into multimedia data, and transfer the multimedia data to the storage service PP. It is done.

Although not shown, other transfer conversion type PP has multiple PULL-INs and PUSH-INs, and acquires video data from other PPs by PULL-IN in synchronization with the video input trigger to PUSH-IN. Then, a composition to synthesize can be considered.
In addition, by freely combining the input / output interfaces of PULL-IN31, PUSH-IN33, PULL-OUT32, and PUSH-OUT34 shown in FIG. 4 and PP having the input / output of the individual communication control unit for PP. A wide variety of PPs can be configured depending on the application.

(Other embodiments)
The present invention is not limited to the above embodiments. For example, in each of the above embodiments, the case where the data storage / delivery server apparatus is configured by one server has been described as an example. However, the present invention is not limited thereto, and includes a plug-in process unit for data reception processing, a plug-in process unit for writing and reading received data to a storage device, and a plug-in process unit for distribution processing of read data. The system may be configured so that data is transferred between the plug-in process units via a communication network that is provided separately on separate servers and connects these servers.

  In this case, not all the plug-in process units are individually distributed to the servers, but only the unit with the largest processing load among the plug-in process units is provided in one independent server, and the other units are provided in another one. You may make it provide in one server. Each plug-in process unit may be divided into two groups according to the processing load, and these groups may be provided in different servers. Also in these cases, data transfer between plug-in process units is performed via a communication network connecting servers.

  Furthermore, in the above-described embodiment, the case where a Web camera is used as the imaging apparatus has been described as an example. However, the present invention is not limited to this. A camera that outputs an analog video signal is used as an imaging device, and the data storage / delivery server receives the analog video signal sent from the camera, and then performs A / D conversion and compression encoding. Thus, JPEG or MPEG encoded video data may be generated, and the generated encoded video data may be stored and distributed.

Furthermore, data handled by the data storage / delivery server is not limited to video data, but may be audio data or attached data. As the attached data, data detected by various sensors such as temperature, vibration, water level, wind speed, and infrared rays can be considered.
Further, in the above-described embodiment, each Web camera and the data storage / delivery server and each client terminal and the data storage / delivery server are connected via a common communication network NW. However, they are connected via separate communication networks. You may make it do.

  Further, although cases have been described with the above embodiments as examples where the function of each plug-in process (PP) is realized by software, it may be realized by hardware. In each of the above embodiments, the case where the data storage / delivery server device of the present invention is used in a monitoring system has been described as an example. However, the present invention is applied to a system other than the monitoring system such as a system for collecting and distributing contents and various information. Also good.

In addition, the functions, configurations, operation contents, and the like of each plug-in process unit can be variously modified and implemented without departing from the gist of the present invention.
In short, the present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying the components without departing from the scope of the invention in the implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in each embodiment. Furthermore, you may combine suitably the component covering different embodiment.

The block diagram which shows the structure of the monitoring system provided with the data storage delivery server concerning 1st Embodiment of this invention. The block diagram which shows the hardware constitutions of the data storage delivery server shown in FIG. The figure which shows the structure of the recording area of HDD provided in the data storage delivery server shown in FIG.1 and FIG.2. The figure which shows the general structure of the data transfer interface used for the data transfer in a server in each plug-in process shown in FIG. The figure for demonstrating a PULL type | mold transmission system and a PUSH type | mold transmission system. The figure for demonstrating the data transfer path | route in the data storage delivery server shown in FIG. The figure which shows the structure of the setting file for operating each PP shown in FIG. The flowchart which shows the starting process procedure and processing content of PP in the data storage delivery server SV0 shown in FIG. The flowchart which shows the operation change processing procedure of PP, and the processing content in the data storage delivery server SV0 shown in FIG. The flowchart which shows the completion | finish processing procedure and processing content of PP in the data storage delivery server SV0 shown in FIG. The figure which shows the structure of a status output file. The block diagram which shows the structure of the monitoring system provided with the data storage delivery server concerning 2nd Embodiment of this invention. The block diagram which shows the structure of the plug-in process with which one of the data storage delivery servers shown in FIG. 12 is equipped. The block diagram which shows the structure of the plug-in process with which the other one of the data storage delivery servers shown in FIG. 12 is equipped. The block diagram which shows the structure of the plug-in process with which another one of the data storage delivery servers shown in FIG. 12 is equipped. The block diagram which shows the structure of the plug-in process with which another one of the data storage delivery servers shown in FIG. 12 is equipped. The block diagram which shows the 1st example of the structure of PP concerning the 3rd Embodiment of this invention. The block diagram which shows the 2nd example of the structure of PP concerning the 3rd Embodiment of this invention. The block diagram which shows the 3rd example of the structure of PP concerning the 3rd Embodiment of this invention. The block diagram which shows the 4th example of the structure of PP concerning the 3rd Embodiment of this invention. The block diagram which shows the 5th example of a structure of PP concerning the 3rd Embodiment of this invention. The block diagram which shows the 6th example of a structure of PP concerning the 3rd Embodiment of this invention.

Explanation of symbols

  C1 to Cn ... Web camera, DS ... Door sensor, TM1 to TMm ... Client terminal for reproduction, MM ... Client terminal for management, NW ... Communication network, SV0, SV1 to SV4 ... Data storage / delivery server, 10 ... System network in the server 11, 110 ... Master control PP, 12, 131 to 13i ... JPEG reception PP, 13, 141 to 14j ... MPEG reception PP, 14, 151 ... JPEG transmission PP, 15, 152 ... MPEG transmission PP, 16, 111, 120 , 130, 150 ... PreHTTP-PP, 17 ... Digital I / O, 18, 112 ... User management PP, 19, 113 ... Schedule setting PP, 20, 114, 121 ... Storage service PP, 21, 122 ... Hard disk driver (HDD) ), 22 ... Setting information (setting file) 101 ... CPU, 102 ... bus, 103 ... network I / F, 104 ... serial I / F, 105 ... digital I / O, 106 ... memory, 107 ... HDD I / F, 211 ... area for OS, 212 ... Video data area, 213... Video recording program group area, 2131... Execution file directory, 2132... Setting file directory, 2133.

Claims (7)

In a data storage and delivery server system that receives data transmitted from an information source and accumulates it in a storage device, reads the accumulated data from the storage device, and transmits it to the monitor device.
A first plug-in process for executing processing for receiving data transmitted from the information source; and a second plug-in process for executing processing for writing and reading data received from the storage device. And a third plug-in process that executes a process of transmitting data read from the storage device to the monitor device,
Each of the first, second, and third plug-in processes includes at least one of a PULL type input interface, a PULL type output interface, a PUSH type input interface, and a PUSH type output interface, and uses these interfaces. There line the transfer of data to and from other plug-in process and,
At least one of communication with the information source by the first plug-in process and communication with the monitor device by the third plug-in process is TCP / IP (Transmission Control Protocol / Internet Protocol). ) Or UDP / IP (User Datagram Protocol // Internet Protocol), socket communication is used to transfer data between the communication and the plug-in process.
When sensor information from an external sensor is received via digital I / O, an instruction to change the data rate for receiving video data from the information source to a value set higher than normal is received according to the information. If the emergency recording instruction is given to the first plug-in process and the emergency recording instruction from the information source is received via the communication network, is the emergency recording instruction generated from a place where the schedule change authority is granted? When it is confirmed that it has been generated from an authorized place, the data rate for receiving video data from the information source is set higher than normal in response to the emergency recording instruction. scheduling plug process which gives an instruction to change the value in the first plug-in process, characterized by further comprising Data accumulation and distribution server system. A fourth plug-in process for executing processing for receiving data encoded by the Motion Picture Experts Group (MPEG) method from the information source by RTSP (Real Time Streaming Protocol);
A fifth plug-in process for executing a process of transmitting data read from the storage device to the monitor device in units of 1 GOV (Group Of VOP (Video Object Plane));
The data transmitted from the information source is video data,
The first plug-in process receives data encoded by a JPEG (Joint Photographic Experts Group) method using an HTTP (Hyper Text Transport Protocol) protocol,
The third plug-in process transmits data read from the storage device to the monitor device according to a method of transmitting video data by issuing a request for each frame,
The first and fourth plug-in processes each have a unique input interface for each type of information source,
The third and fifth plug-in processes include an output interface specific to each type of the monitor device,
The communication between the first, second, third, fourth, and fifth plug-in processes is executed according to a predetermined protocol for inter-plug-in process communication. Data storage and delivery server system. Wherein the first plug-in process, the third plug-in process, the data storing and delivering server system according to claim 1, characterized in that it is executed each on a separate server device. Wherein the second plug process, the first or the third plug process, according to claim 1 data storing and delivering server system, wherein the respectively performed in separate server device. A first server device that executes the first and second plug-in processes;
3. The data storage / delivery server system according to claim 2 , further comprising a second server device that executes the third and fifth plug-in processes and is separate from the first server device. . When there is a direct service request from the monitoring device,
The third plug-in process requests the first plug-in process to transfer data;
The first plug-in process, according to claim 1 data storing and delivering server system, wherein the transfer of the most recent data received on the third plug-in process from the information source. A seventh plug-in process having an HTTP server function and receiving a request from the monitor device;
If the requested communication is addressed to the third or fifth plug-in process, the seventh plug-in process takes over the requested communication by descriptor passing to the third or fifth plug-in process. ,
The data storage / delivery server system according to claim 2, wherein the third or fifth plug-in process directly communicates with the monitor device after taking over the requested communication.

Images