JP2003153248A - Total by camera control information in internet open camera and total information disclosure system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system that totalizes utilizing states of an Internet open camera in real time and discloses the result to customers. SOLUTION: A relaying totalizing server connected between a camera server apparatus and a client apparatus always totalizes distributed information so as to totalize operations particular to the camera server and to immediately disclose the results.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a total information disclosure technique based on camera control information in Internet public cameras.

[0002]

2. Description of the Related Art There is a system in which an image of a video camera can be observed from multiple points in a remote place, and not only the image of the camera can be observed but also the pan / tilt angle and zoom magnification of the camera can be remotely controlled. For example, a system has been developed that connects a computer-controllable camera to a WWW (World Wide Web) server on the Internet, not only delivers a real-time image captured by the camera to an access person but also allows control of the camera. ing.

Further, these camera servers need to be installed in many places physically in a very wide range.
Therefore, there are many cases where a line with a relatively low bandwidth and a low unit price is used. Therefore, by installing a server (relay server) connected to a higher speed line, the video request to the camera server connected only to a low bandwidth line is relayed and delivered by the server connected to the high speed line. , Systems for distributing video information and camera information have been developed.

[0004]

Such camera control is possible and video distribution to a plurality of people is possible, and moreover, WWW.
If the camera is a public camera that is widely disclosed to customers on the server, etc., in order to know how much these cameras are used, the camera server grasps from the situation such as log files recorded. There was only means.

Further, even if these log files are manually collected and totaled, it is very troublesome. Even if the log file could be collected automatically, it may be collected after the information is accumulated in the log file, so that there may be a delay between the total status and the actual status. In particular, this situation causes a very remarkable problem when the camera server is stopped for some reason. Because the introduction information of the camera server based on the total information is WW
This is because there is a possibility that the camera server may be stopped even if the camera server is introduced, such as when it is published on the W server.

As described above, in the conventional system, in order to efficiently introduce the camera server to the customer, it is always necessary to manually check the camera server, so that the camera server can flexibly handle a large number of camera servers installed in a wide range. I had to say that it was insufficient to respond.

[0007]

[Means for Solving the Problems] In view of the problems as described above, in the present proposal, in order to constantly grasp the state of the camera server in real time, information is transmitted to the server which relays and delivers the above-mentioned video. This problem can be solved by providing the aggregation function of.

A server for relaying and delivering this video and for analyzing and summing the information (hereinafter, relay aggregation server) is intended to relay the video information and camera control information of a large number of camera servers and at the same time. By interpreting the information inside the relayed information and totaling it, it is possible to deal in real time with delays in totaling information that cannot be solved only by collecting the log files of the camera server. In other words, grasp the usage status of the camera server in real time,
The information can be aggregated and uploaded to a WWW server or the like, and the information can be widely disclosed to customers.

Further, by analyzing and summing the camera control information to be relayed, the state (pan / tilt / zoom) of the camera used in the camera server can be grasped. Therefore, the state can also be reported to the WWW server in real time. It is possible to publish.

It is also possible to confirm whether or not the camera server is working effectively by connecting to the client or periodically accessing the camera server. By these means, it becomes possible to solve the problems that cannot be solved by the conventional techniques.

Further, according to Japanese Patent Laid-Open No. 11-177569, a relay server constantly monitors the status of the camera server on the network and notifies the client of the status. It only reports whether or not there is a connection and the instantaneous state, and does not have a means to perform statistical processing such as the number of client connections.

The purpose of this proposal is to provide the operation of the camera server and the operation history status to the customer, and is not limited to the presence or absence of connection. Because the purpose of the customer is to browse the video of the camera server that suits the customer's taste from a large number of camera servers scattered in the network such as the Internet, statistics such as the number of client connections and frequent camera operation as proposed in this proposal are used. It can be said that the information of the camera server obtained by the statistical aggregation processing based on the state such as the size is very effective for selecting the camera server that provides the customer's desired image desired by the customer.

The effect of this portion will be described in JP-A-11-17756.
No. 9 publication is not provided.

Therefore, the present proposal provides a means for solving this object in the first place.

Hereinafter, a system, an apparatus, and a mechanism for accumulating information and disclosing the information in real time will be described.

[0016]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS (First Embodiment) FIG. 1 is a schematic view showing the entire system.

Reference numeral 100-001 indicates a network. Reference numerals 100-002 to 100-007 denote various devices.

In the present embodiment, the network indicated by 100-001 is a TCP / IP network, and a LAN or the Internet is used. However, as long as the devices connected to the network can realize a one-to-one or one-to-many communication mode, other networks such as an ATM network may be used, and wired or wireless may be used. Reference numeral 100-003 denotes a camera server, which indicates a system that enables viewing of images from cameras connected to the network. Therefore, the camera server is connected with a camera indicated by 100-002. It also has a device that digitizes the image from the camera. In particular, it may be built-in rather than externally connected. The camera server compresses and processes video data so that the video can be captured and transmitted to the client.

Reference numerals 100-004 to 100-007 denote client devices. The client device may be a normal PC or a small terminal such as a mobile terminal.
These terminals are devices that can connect to a network and have the ability to browse video. In the example of the present embodiment, since it is a live camera device, the client device has a capability of displaying and operating a display device for displaying an image, HTML data disclosed by a WWW server, and the like. Is.

FIG. 2 is a schematic diagram showing the entire system of the present proposal.

Reference numeral 200-001 indicates a network similar to 100-001. Reference numeral 200-002 indicates the relay aggregation server presented in this proposal. 20
Reference numeral 0-003 indicates a WWW server for disclosing total information and the like. 200-004 to 200-006 are
As shown in FIG. 1, the client device is shown. Reference numeral 200-007 denotes a camera server device, as shown in FIG.

In this proposal, by using the relay aggregation server, it is possible to aggregate information in real time. A WWW server is used to provide the accumulated information to the customer. This WWW server may be operated on the same device as the relay aggregation server. In some cases, it may be operated on the same device as the camera server, and the installer can install it freely according to the line conditions. The relay aggregation server can relay the video information and camera control information of the camera server. This makes it possible to provide the video information and camera control information to the client device instead of the camera server. At this time, the relay aggregation server recognizes a portion that overlaps a request from another client device in the video information request information or the camera control request information from the client device, and makes the minimum required request to the camera server. Then, it operates so as to provide the information received from the camera server to each client device.

Such an operation is very useful for reducing the bandwidth used by the line connecting the camera server to the network. Because many camera servers are arranged on the network in many cases, a low-bandwidth line with relatively low cost is often selected as the line. When a client server directly requests a camera server connected to a low-bandwidth line to provide video information and camera control information, the bandwidth used by the line will soon exceed the capacity of the line. Therefore, it is necessary to operate like a relay aggregation server.

When the relay function is realized, the relay aggregation server interprets the contents of the video request information and the camera control request information from the client and the video information and the camera control information from the camera server. By analyzing and accumulating the results of interpreting, it is possible to calculate the information provided to the customer.

FIG. 3 shows the internal structure of the camera server device.

Reference numerals 3-1 to 3-9 show the outline of the devices in the camera server device. Inside the device, an image output device 3-1 and an input device (keyboard, mouse, etc.) 3
-2, the central processing unit 3-3, the main memory 3-4,
It has an external storage device 3-10, a network interface 3-6, and the like. As for these devices, other client devices and relay aggregation servers have the same mechanism. These devices are connected by a connection called a bus and operate. Furthermore, by connecting the display device 3-9, it is possible to display the image of the camera and the internal information of the device. Further, in particular, the camera server device has the moving image input device 3-5, and the
The camera indicated by 8 is connected. With these devices, the camera server device can digitize an image captured by the camera and process it as data. The network 3-7 is connected to the network interface 3-6. As a result, it is possible to communicate with another device. The provision of this embodiment can operate by including such devices.

FIG. 4 shows an outline of a camera capable of pan / tilt and zoom.

The camera server includes 400-001 to 40
A camera capable of pan / tilt and zoom realized by a device as shown in 0-005 is connected.
Reference numeral 400-001 indicates a camera portion. This camera is equipped with a zoom device, and is capable of zooming and widening the camera. The camera is connected to the platform (head) that supports it by 400-002. This device enables pan / tilt operation. These controls are entirely controlled by the control unit 400-003, and the connection unit 40 between the control unit and an external device is used.
0-004 enables camera control such as pan / tilt / zoom operation of the camera. Also, the video output unit 4
00-005 keeps providing the video information to the external device at any time.

A camera capable of pan / tilt / zoom operations is constructed by such a device, and it is possible to connect to the camera server in the present embodiment, and it is possible to browse and operate from a remote location.

FIG. 5 shows a schematic diagram of the internal software structure of the camera server and the relay aggregation server.

The camera server is composed of the processes 5-1 to 5-3. 5-6 has shown the relay total server. The outline of the internal structure of this software will be described in more detail with reference to FIG. 5-5 has shown the client process in a client apparatus.

The camera server has registers (temporary information storage memory) 5-7 to 5-9, through which information is shared among processes to perform a linked operation.

5-1 shows a camera control process. In this process, management such as control of the external camera device is performed. This is a process for actually performing camera control by a camera control request protocol from the client process. 5-2 shows a camera status notification process. In this process, in order to provide the client process with the change in the state of the camera caused by the camera control process, it is responsible for monitoring the state of the camera and notifying when there is a change. 5-3 shows a video server process. In this process, when the image information is requested by the image request protocol from the client means, the request state is grasped and the process for acquiring the image information from the camera device is performed.

Reference numeral 5-4 indicates a video acquisition / transmission process. In this process, the video from the camera is actually input, the video information is compressed, and provided to the connected client process.

These processes are performed by the camera status register 5-
Information such as No. 7 and the destination list 5-9 is shared by the processes to perform cooperative operation. For example, it is possible to prevent unnecessary video information from being sent to the client process by grasping the presence or absence of the power source of the camera by the camera status register, and by the information such as the destination list, the IP
It becomes possible to set the connection limitation of the client means by the address or the like.

As described above, the camera image transmission / reception processing and the camera control information transmission / reception processing are performed between the camera server and the client, but a relay totalizing server may be inserted therebetween. In this case, the relay aggregation server performs the same operation as the client process for the camera server and the same operation as the camera server for the client process. By such a pseudo operation, the video information and the camera control information can be propagated without making a special request to the camera server and the client.

FIG. 6 shows the camera total information output to the image output device of the client device.

Reference numeral 600-002 indicates an image output device connected to the client device. This device is.
It is provided in the client device and may be an external device connected. Reference numeral 600-001 indicates client software that provides WWW server information.

In the software (hereinafter referred to as browser software) for displaying the WWW server information indicated by 600-001, the totaled result of the relay totalizing server is displayed. This information is real-time total information provided by the WWW server 200-003 or the like. This information is HT
It is described in an information notation language such as an ML file, and the data is calculated by the relay aggregation server 200-00.
2 does. Furthermore, the relay aggregation server sends the information to the WW.
By transferring the data to the W server or the like, it is possible to freely present it to the customer from the client device.

In the present proposal, a means for providing information to a customer using a WWW server is disclosed, but this method may use any other unspecified number of information providing methods. For example,
A mobile terminal language WAP, a data description language XML, or the like may be used, or a NEWS server, an FTP server, or the like may be used instead of the WWW server.

FIG. 7 shows an outline of the camera control GUI in the client device.

Reference numeral 7-1 indicates an image taken by the camera server. Reference numerals 7-2 and 7-4 are GUIs for performing pan / tilt operations of the camera server connected to the camera server. 7-5 is a GUI for performing a zoom operation of the camera server connected to the camera server.
These camera operations may be requested at once from multiple client devices. If this is all performed at the same time, the operation of the camera of the camera server will be in a situation where the intended operation of all client devices cannot be performed. Therefore, this situation is avoided by giving each client authority to control the camera at regular intervals. The authority to control the camera is called a camera control authority, and is used to allow only one client to operate among all the clients to be connected in response to the request from the client. The GUI for requesting acquisition of the camera control right is a camera control right request button shown in 7-3.

Since the client device has these GUIs, the client device can operate the camera of the camera server.

Further, FIG. 8 shows an outline of a GUI in another type of client device.

For example, the function shown in FIG. 7 can be realized by assigning the function shown in FIG. 7 to each button shown in 8-2 even in a mobile phone terminal as shown in 8-1. Will be possible. Also, depending on the platform-independent client process such as Java (registered trademark), various types of platforms (Windows (registered trademark), UN
IX (registered trademark), mobile phone device, mobile terminal device) or the like can be used.

FIG. 9 shows the flow of the camera control server process and the camera status notification process.

When the camera control server process 5-1 is activated (S400), a camera state notification process 5-2 is generated (S402), and a camera control connection request from the client process 5-5 (FIG. 12 (1)). ) (S40
3). When there is a connection request from the client process 5-5, connection acceptance processing (returning Ack) is performed (S40
4), the camera control command (FIG. 12 (2)-
Wait for (4)) (S405). The connection acceptance process S4
In 04, a timer is set so that the camera control connection is cut off after a certain fixed time (referred to as "control holding time") (S407).

Camera control command (Fig. 12 (2)-
(4)) comes, the camera control unit 40 responds to the command.
The zoom magnification of the camera 3-8 and the pan / tilt angle of the movable platform device 400-002 are controlled through 0-002 (S409). A camera control command is accepted from the client process 5-5 until the control time limit expires, and camera control according to the command is performed through the control unit 400-003. It should be noted that here, as the camera control command, for the sake of explanation in the present embodiment, the following command is assumed.

Pan angle change command (PAN θ), tilt angle change command (TIL φ), zoom magnification change command (Z
OM α) However, θ, φ, and α are parameters that represent the pan angle, the tilt angle, and the zoom magnification, respectively, and this camera control command also includes backlight compensation, autofocus, manual focus value setting, etc. There are various kinds,
The description is omitted here.

When the control time is over, a connection disconnection process (S407) is performed, and in the process of S407, the camera control connection end command (FIG. 12 (7)) is returned to the client process 5-5. Then, it waits for another connection request (S403). The camera control server process 5-11 implements camera control by accepting a camera control connection request from an arbitrarily executed client process.

While the camera status notification process 5-2 generated in S402 is operating, the camera status is constantly checked. That is, the pan / tilt angle of the camera and the zoom magnification (= (p, t, z)) are set in the camera control section 400-
When it is read into the camera 5-5 by inquiring 003, it is written in the camera status register 5-7 (S422), and compared with the camera information set in 5-8. If the user does not want to show it, the camera is controlled by the process of S425. Also, the client process that is transmitting the video 5-
5 is notified of the camera status (the format of FIG. 12 (8)) (S
426). The process of S425 will be described in detail later.

Next, the video server process and the video acquisition / transmission process will be described using the flow of FIG.

When the video server process 5-3 is activated (S500), a video acquisition / transmission process 5-4 is generated (S502), and an event from the client process 5-5 is waited for (S503). Here, if the event is a video display start request command ((6) in FIG. 12), (S50
4) Check the source address of the packet included in the video display request packet and add it to the video destination list 5-9. If the command is a video display end request command (S50
6) Similarly, the sender address of the packet included in the video display request packet is confirmed, and the video destination list 5
Delete from -9. The video transmission destination list 5-9 holds the addresses of video transmission destinations in a list format.

When the image acquisition / transmission process 5-4 is started, the following operations are repeated. That is, it is captured as a frame of a camera image (S522) and compressed (S522).
523), and compressing this compressed video data as shown in FIG.
Packetized in the format of (9), and the video destination list 5-4
To a plurality of addresses in (S52
5).

FIG. 11 shows the operation of the client process 5-5. First, when the process is started and the address (IP address, here, "ADDR_C") of the camera server device 100-003 to be connected is specified and activated, a video display start request is transmitted to the camera server device corresponding to ADDR_C. . The packet format is (5) in FIG. Here, if Ack is not returned from the camera server device corresponding to ADDR_C (S603), the operation is abnormal such as an incorrect address, so the client process is terminated (S604). If Ack is returned, the display is successful (S603), and therefore an event, that is, user operation of the user interface or various packets from the camera server device 1-1 is waited for (S605).

Here, when the user presses the operation start button 7-3 (S606), it is determined whether or not the user has already started the camera control, that is, the control right flag 5 which is one parameter of the camera status register. Confirm with -7 (S60
7) If it is already under control, return to S605. If not in operation, issue a camera control connection request (FIG. 12 (1)) to the camera control server process (S608) and permit (A).
ck) is waited for (S609). If Ack is returned here, connection is established to the camera control server process,
The control right flag in the storage unit 3-4 of the client device is turned on (S611), and the camera control client GUI
Enable the operation (Fig. 7). It should be noted that the camera control server process accepts the connection request only during the camera control connection request waiting S403.

Further, when the connection is established and the "control time limit" ends, the camera control server process returns a camera control connection end request (FIG. 12 (7)). When this is received (S614), control right is given. Turn off the flag (S
615), and the operation of the camera control client GUI (FIG. 7) is invalidated (S616).

While the operation of the camera control GUI (FIG. 7) is valid, a camera control command corresponding to the operation of the camera control GUI (FIG. 7) is generated and issued to the camera server process 5-1. (S618). The instruction generation process is omitted here.

In response to a client process termination request (S626) issued by operating a menu or the like,
A video display end request (Fig. 12 (7)) is issued (S62).
7) The client process is terminated (S628).

When the packet arrives (S62
5), if it is video data (Fig. 12 (9)) (S6
29), after reading the compressed video data in the video data and performing decompression processing, using this video frame data,
The display image on the image display panel of 7-1 is updated (S63
0).

The arrival packet indicates the camera state (see FIG. 12).
In the case of (8)) (S636), scroll bars 7-2 and 7- for operating the pan / tilt angle and the zoom magnification.
Change the display positions of the knobs 4 and 7-5 to the corresponding positions using the parameters included in the packet (this updates the information when another client process is controlling the camera). You are doing).

FIG. 13 shows a database held by the relay aggregation server. The relay tally server has a database of connection history, upload destination list, information HTML creation data, etc. as data necessary for tallying information and disclosing information.

As the connection history, as shown in FIG. 15, it is possible to leave history information having almost the same contents as the protocol with the camera server and the client. In this proposal, all information is left as history information, but the minimum amount of information to be aggregated may be recorded. For example,
If you want to collect the connection history, please refer to Fig. 15 (9) and Fig. 15
All that is left is (10).

In the upload destination list database,
It has the information for transmitting the information HTML data that is created by totaling. By this information, the relay aggregation server is provided with a method for disclosing information by designating an address, directory name, etc. of an FTP server or the like that works with the WWW server.

Any publicly known means may be used as a method of disclosing the totalized information. In this proposal, WWW server and F
Although a TP server is assumed, other means such as mail delivery by an SMTP server may be used.

FIG. 17 shows an outline of the information HTML creation database.

In this database, the information about the items and the way to be totaled by the relay totaling server are recorded.

In FIG. 17 (1), the total population to be totaled is recorded. In this proposal, the number of connections per unit time, the number of camera operation events per unit time, the number of access towns per unit time of the camera control access queue, and the time during which connection to the camera server was possible A large amount (specifically, the frequency of connection errors per unit time) can be specified.

These aggregation methods are set by the camera server administrator, and it is possible to select the aggregation method according to the customer needs.

Further, these tabulation work is shown in FIG. 17 (2).
As shown in, the aggregation time can be set to daytime, nighttime, or any time. This is because in a camera server that captures a landscape or the like, the subject to be photographed changes greatly depending on the time zone, and therefore, it is often considered separately as the information to be aggregated.

By selecting and providing the totaling method that the customer wants to know according to the customer's needs, it becomes possible to provide a more efficient camera server providing service of the camera server.

FIG. 18 shows an outline of an example of an HTML file created by the relay camera server for making information and disclosing the information.

Reference numeral 18-2 is an example of total information displayed on the display device connected to the client device. The relay aggregation server displays the top 5 camera servers in the aggregation information of the number of connections per unit time.

Each camera server information contains 18-
As shown in FIG. 1, it is possible to embed a pointer called a high power link, which is a resource unique to the HTML language on the Internet. The relay aggregation server registers the pointer of the resource on the Internet as a camera server.

Reference numeral 18-14 is an HTML information data file created by the relay tally server. The high power link called by 18-1 is embedded with connection destination information to the camera server in a format as shown in 18-3.

For this reason, the relay aggregation server can convert the aggregated data into a form that can be published and publish the aggregated data through the WWW server.

FIG. 14 shows an outline of the process configuration of the relay aggregation server.

The relay aggregation servers are 14-3 to 14-14.
It consists of the process shown in. These processes are started at the same time when the relay summary server is started. The relay aggregation server is internally divided into a camera control data relay unit, a video data relay unit, and a data aggregation and upload unit.

The relay of the camera control data is started by the camera control protocol shown in 14-15 to the camera control notification request reception process from the client. This request requests the camera server side to notify the camera control and status by the camera control protocol shown in FIG. For more information on this protocol,
As described in the camera control process of the camera server described above. Such a camera control and status notification request is once passed to the 14-8 camera control relay process. At this time, the duplication of the request contents is checked so that the same request as the other clients is not requested to the camera server a plurality of times. The camera control and status notification request optimized by the process is notified to the camera control server through the camera control notification request transmission process. At this time, the camera control relay process transfers the same content of the camera control request history on the client side to the log storage process. The camera control server 14-2 which has received the camera control and status notification request notifies the camera status notification by the camera control protocol (FIG. 12). The relay aggregation server receives this in the camera control notification receiving process and passes the information to the camera control relay process. In the camera control relay process, the notified contents are copied and notified to all the clients waiting for the acquisition of the notified contents. Finally, the notification of the camera status is passed to the camera control notification transmission process, and is transmitted to all the client means requesting the information.

The relay of the video data is started by the video request protocol to the video request receiving process from the client shown in 14-9. This request is made to the camera server side by the video protocol shown in FIG. The details of this protocol are as described in the video server process of the camera server. Such a video request is once passed to the 14-7 video relay process. At this time, the duplication of the request contents is checked so that the same request as the other clients is not requested to the camera server a plurality of times. The video request optimized by the process is notified to the video server through the video request transmission process. At this time, the video relay process transfers the same video request history on the client side to the log storage process.

The video server 14-1 which has received the video request,
Video information is transmitted by the video protocol (FIG. 12). The relay aggregation server receives the information in the video reception process and passes the information to the video relay process. In the video relay process, the contents of the notified image information are copied to all the clients waiting for the acquisition of the notified contents, and the notification is given to all the clients. Finally, the video information is passed to the video transmission process and sent to all clients requesting the information.

Reference numeral 14-13 indicates a log accumulation process. This process is a process for recording video information and camera control history information from the video relay process and the camera control relay process. The data is recorded in a database such as the aggregation server history data 14-17 described above. The log accumulation process also passes the data to the log total information upload process 14-14. In the log aggregation information upload process, the information HT
Data for aggregation and disclosure is created based on the ML creation data.

FIG. 19 shows an outline of the process flow of the relay aggregation server.

The processing is started from S191, and the entire initialization is performed in S192. After that, S193 to S19
Up to 14, all processes shown in FIG. 14 are created. After that, in S1913, the process waits for the end of the whole process and ends.

FIG. 20 shows the flow of the video relay process and the camera control relay process.

The video relay process confirms in step S202 whether or not the video request comes from the video request reception process. If there is a request, the request content is acquired in S2017, and the request information is passed to the video request transmission process in S203. In step S203, it is determined whether the request is duplicated with a request from another client, minimum necessary request information is created, and the request is passed to the video request transmission process. Also, in S204, the history information is passed to the log accumulation process.

If there is a request for video information in S205, the video information is acquired from the video receiving process in S206. Then, in S207, when the video information is acquired from a plurality of clients, the video data is created for each client here, and the video data is passed to the video transmission process in S207. Also, S208
At, the history information is passed to the log accumulation process.

In step S2010, the camera control relay process confirms whether the camera control request comes from the camera control notification request process. If you have a request,
The request content is acquired in step S2011, and the request information is passed to the camera control request transmission process in step S2012. In step S2011, it is determined whether or not the request is overlapped with a request from another client, necessary minimum required information is created, and the request is passed to the camera control notification request transmission process. Also, S2
At 013, the history information is passed to the log accumulation process.

If the camera control notification information is received in S2014, the camera control notification information is acquired from the camera control notification receiving process in S2015. And
In step S2016, when there are camera control notification information requests from a plurality of clients, camera control notification data is created for each client, and the camera control notification data is sent to the camera control notification transmission process in step S2016. hand over. In S2017, the history information is passed to the log accumulation process.

FIG. 22 shows the flow of the video request transmission process and the camera control notification request transmission process.

The video request transmission process waits for video request transmission information from the video relay process in S222.
If there is information, the information is acquired in S223,
At S224, the information is transmitted to the video server.

The camera control notification request transmission process is performed in S2.
At 26, the process waits for camera control notification request transmission process information from the camera relay process. If you have the information,
The information is acquired in S227, and the information is transmitted to the camera control server in S228.

FIG. 23 shows the flow of the video reception process and the camera control notification reception process.

The video reception process waits for the video information to be received from the video server in S232. Upon reception, the video information is received in S233, and S234
Pass the information to the video relay process.

The process for receiving the camera control notification is S236.
At, it waits for the camera control notification reception information to be received from the camera control server. Upon reception, the camera control notification information is received in S237, and the information is passed to the camera control relay process in S238.

FIG. 24 shows the flow of the video transmission process and the camera control notification transmission process.

The video transmission process waits for video information from the video relay process in S242. When the video information is acquired, the video information is received in S243, and S
At 244, the message is transmitted to the client.

The camera control notification transmission process is executed in S246.
At this time, it is waiting for the camera control notification transmission information from the camera control relay process. When the camera control notification information is acquired, the camera control notification information is received in S248, and S
At 248, it sends to the client.

FIG. 25 shows the flow of the video request reception process and the camera control notification request reception process.

The video request receiving process waits for video request information from the client in S252. When the image request information is acquired, the image request information is received in S253, and is transmitted to the image relay process in S254.

The process for receiving the camera control notification request is S2.
At 56, waiting for camera control notification request information from the client. When the camera control notification request information is acquired, the camera control notification request information is received in S257, and is transmitted to the camera control relay process in S258.

FIG. 21 shows the flow of the log accumulation process.

The log accumulation process waits for the accumulation information to be sent from another process in S212. If notified of the accumulated information, the accumulated information is actually acquired in S2143, and the information is recorded in the total server history data in S214. Further, in S215, the history information is sent to the log aggregation information upload process.

The log total information upload process is S
Waiting for historical information from the stored information process at 217. If there is notification of the accumulated information, the information is actually acquired in S218. Then, in S2110, the actual tabulation process is performed. This method is as described above. The total data is read in the upload destination list in S2111, the upload destination is determined, and S21
The information HTML creation data is read in 13 and S211 is executed.
Create the actual upload data in 3. Then, in step S2114, information is uploaded to the FTP server.

By operating in this way, it becomes possible to smoothly publish real-time total information.

[0106]

As described above, according to the present invention,
It is possible to solve the problem by using the system, device and mechanism for accumulating information and releasing it in real time.

[Brief description of drawings]

FIG. 1 is a schematic diagram of the entire system.

FIG. 2 is a schematic diagram of the entire system showing the present proposal.

FIG. 3 is an internal schematic diagram of a camera server and a client device.

FIG. 4 is a schematic diagram of a camera capable of pan / tilt / zoom.

FIG. 5 is a schematic diagram of an internal configuration of a camera server.

FIG. 6 is an example of client device output.

FIG. 7 is a schematic diagram of a client device GUI.

FIG. 8 is a schematic diagram of a client device GUI.

FIG. 9 is a flow of a camera control server process.

FIG. 10 is a flow of a video server process.

FIG. 11 is a flow of a client process.

FIG. 12 is a camera control and video transfer protocol.

FIG. 13 is a database in the relay aggregation server.

FIG. 14 is a schematic diagram of an internal software configuration of a relay aggregation server.

FIG. 15 is relay aggregation server history data.

FIG. 16 is upload destination list data.

FIG. 17 is information HTML creation data.

FIG. 18: Information HTML.

FIG. 19 is a flow 1 of an internal process of the relay aggregation server.

FIG. 20 is a flow 2 of an internal process of the relay aggregation server.

FIG. 21 is a flowchart 3 of the internal process of the relay aggregation server.

FIG. 22 is a flowchart 4 of the internal process of the relay aggregation server.

FIG. 23 is a flowchart 5 of an internal process of the relay aggregation server.

FIG. 24 is a flowchart 6 of an internal process of the relay aggregation server.

FIG. 25 is a flowchart 7 of the internal process of the relay aggregation server.

Claims (4)

[Claims] 1. An apparatus and means capable of, in an internet public camera, totaling data in real time based on connection / disconnection information of a client, creating public data, and publicizing the totalized result. 2. An apparatus and means for an internet public camera, capable of totaling data in real time based on a camera operation frequency of a client, creating public data, and publicizing the totaled result. 3. An apparatus and means capable of, in an Internet public camera, performing real-time totaling based on an error frequency of connection to a camera server to be publicized, creating public data, and publicizing the totalized result. 4. The method according to any one of claims 1 to 3, wherein the totaling time is set to daytime and nighttime or an arbitrary time,
An apparatus and means for totaling data based on the results of totaling during the period and creating public data.