JP7410688B2 - Imaging device and its control method - Google Patents

Description

The present invention relates to drive control of an imaging device.

In recent years, video transmission systems using Internet Protocol (IP) have become widely used as systems for distributing video captured by cameras. It is also common to use a control device called a controller for changing camera settings and remotely controlling pan-tilt-zoom (PTZ). If the camera and controller conform to a common standard, it can be used not only with controllers manufactured by the same manufacturer as the camera, but also with controllers made by other companies. For example, the Open Network Video Interface Forum (ONVIF) is used as a standard for connecting cameras and control devices.

However, when using a plurality of different controllers, the user may experience a difference in operational feel depending on the controller. For example, if the operating tools (joysticks, etc.) are physically different, or if the algorithm for sending PTZ operation commands when operating the operating tool is different for each controller, the PTZ addition may be different even if the operating tool is operated with the same force or angle. There will be a difference in deceleration.

In Patent Document 1, in order to unify the operational feel between the zoom operation via the input section of the camera and the zoom operation via the external device, the zoom operation speed is reduced during the zoom operation via the external device. The method has been disclosed.

Japanese Patent Application Publication No. 2018-77481

However, although Patent Document 1 discloses a method for reducing differences in operational feel related to zoom control, it does not disclose differences in operational feel related to pan/tilt control.

The present invention has been made in view of such problems, and aims to provide a technique for reducing differences in operational feel regarding PTZ control when a plurality of different controllers are used.

In order to solve the above-mentioned problems, an imaging device according to the present invention has the following configuration. In other words, an imaging device configured to be able to change the imaging direction is
receiving means for receiving a predetermined command from a control device for controlling the imaging device based on an operation by a user ;
determining means for determining a setting value that defines an acceleration when driving a mechanism for changing the imaging direction in the imaging device , based on identification information that identifies the control device included in the predetermined command ;
has .

According to the present invention, it is possible to provide a technique for reducing differences in operational feel regarding PTZ control when a plurality of different controllers are used.

FIG. 1 is a diagram showing the overall configuration of the system. FIG. 2 is a block diagram showing the internal configuration of the camera. FIG. 2 is a block diagram showing the internal configuration of a controller. FIG. 3 is a diagram showing an operation sequence of the system in the first embodiment. It is a flowchart showing the operation of the camera in the first embodiment. It is a figure showing an example of a combination table in a 1st embodiment. FIG. 7 is a diagram showing an operation sequence of a system in a second embodiment. It is a flowchart which shows operation of a camera (updating processing of acceleration designation value) in a 2nd embodiment. It is a figure which shows the example of the combination table in 2nd Embodiment. It is a flowchart which shows operation of a camera (PTZ drive control processing) in a 2nd embodiment. It is a flowchart which shows operation of the camera in a 3rd embodiment. It is a figure showing an example of a parameter list and a combination table in a 3rd embodiment.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments are not intended to limit the claimed invention. Although a plurality of features are described in the embodiments, not all of these features are essential to the invention, and the plurality of features may be arbitrarily combined. Furthermore, in the accompanying drawings, the same or similar components are designated by the same reference numerals, and redundant description will be omitted.

<Summary>
In the standard ONVIF, a Ramp parameter is specified as a parameter indicating the acceleration of the camera during PTZ driving. However, since it is not an essential parameter, some controllers do not support it, and since Ramp is a list-type parameter, it cannot indicate what kind of acceleration it is. Furthermore, in common protocols for camera control such as ONVIF, there are many standards in which a control device unilaterally sends control commands to a camera, and in that case, the camera cannot acquire controller information.

Therefore, in the present invention, each controller is identified by a Mac address (device identification information) on the camera side, and an optimal Ramp value (acceleration) is determined according to the controller. This makes it possible to control the acceleration of the PTZ drive using ONVIF commands, and realizes an imaging system with a unified operational feel.

(First embodiment)
As a first embodiment of the imaging device according to the present invention, a camera configured to accept ONVIF-compliant control from a controller and change the imaging direction will be described below as an example. In particular, in the first embodiment, a mode will be described in which the controller is identified by the Mac address included in a command for requesting configuration information related to PTZ driving sent from the controller, and the response acceleration information (Ramp value) is changed.

<System and device configuration>
FIG. 1 is a diagram showing the overall configuration of an imaging system. The imaging system includes a camera 1000, a controller 2000A, and a controller 2000B, and these devices are connected to each other via a network 3000 so that they can communicate with each other. The controllers 2000A and 2000B transmit control commands to the camera 1000 to perform PTZ control and the like. Camera 1000 transmits a response to the received control command to controllers 2000A and 2000B. In the following, the controllers 2000A and 2000B will be expressed as a controller 2000.

FIG. 2 is a block diagram showing the internal configuration of camera 1000. The control unit 1001 is composed of, for example, a CPU, and controls the entire camera. The storage unit 1002 is composed of, for example, a RAM, and is used as a storage area for programs and data for implementing camera-side processing, which will be described later, and as a work area when executing the programs. The data includes data such as image data generated by the imaging unit 1003 and setting values used by the imaging mechanism control unit 1005 (direction of the imaging mechanism, value of acceleration when driving the imaging mechanism, etc.). Note that a part of the storage unit 1002 may be configured with a ROM, an HDD, or the like.

The imaging unit 1003 outputs an image signal obtained by capturing the subject image formed by the imaging mechanism 1004 to the storage unit 1002 as a captured image. The imaging mechanism 1004 includes an imaging optical system including a lens, an image sensor, etc., and a pan-tilt-zoom (PTZ) mechanism that controls the imaging direction and angle of view. The imaging mechanism control unit 1005 drives and controls the PTZ mechanism of the imaging mechanism 1004 and outputs to the storage unit 1002 values related to the imaging area (direction and angle of view) changed by the drive control.

The communication unit 1006 transmits and receives various data via the network 3000. For example, it is used to receive control commands from the controller 2000, and to transmit various data such as responses to the control commands and image data stored in the storage unit 1002 to the controller 2000.

Note that the configuration shown in FIG. 2 is an example, and the camera 1000 is not limited to the configuration shown in FIG. 2. For example, further functional units such as a video analysis unit, an audio input unit, an audio output unit, etc. may be additionally provided.

FIG. 3 is a block diagram showing the internal configuration of controller 2000. The control unit 2001 is composed of, for example, a CPU, and controls the entire controller. The storage unit 2002 is composed of, for example, a RAM, and is used as a storage area for programs and data for implementing processing on the controller side, which will be described later, and as a work area when executing the programs. The data includes data such as information on cameras currently connected to the network 3000 and connectable to the controller 2000. Note that a part of the storage unit 2002 may be configured with a ROM, an HDD, or the like.

The display unit 2003 is composed of, for example, an LCD, and displays various setting screens, data acquisition/display screens, various messages, etc. to the user of the controller 2000. The input unit 2004 is configured with, for example, a button, a touch panel, a joystick for PTZ operation, etc., accepts operations by the user, and notifies the control unit 2001 of the accepted contents.

The communication unit 2005 transmits and receives various data via the network 3000. For example, it is used to transmit control commands to the camera 1000 and to receive responses to control commands, image data, etc. from the camera 1000.

Note that the configuration shown in FIG. 3 is an example, and the controller 2000 is not limited to the configuration shown in FIG. 3. For example, further functional units such as a received video display unit, an image analysis processing unit, a video storage unit, etc. may be additionally provided.

<Device operation>
FIG. 4 is a diagram showing the operation sequence of the system in the first embodiment. Specifically, it shows a sequence in which the controller 2000 acquires the designated acceleration value for PTZ driving of the camera 1000 via a command requesting acquisition of configuration information regarding PTZ driving in ONVIF.

In S1001, the controller 2000 transmits a GetPTZConfiguration command to the camera 1000. Here, the GetPTZConfiguration command is a command for inquiring and acquiring the PTZConfiguration held by the camera. PTZConfiguration is a setting value related to PTZ drive standardized by ONVIF. The Ramp parameter, which is a parameter indicating the acceleration during PTZ driving, is also included in the PTZConfiguration. The Ramp parameter is a parameter that indicates each stage of acceleration as an integer value.

In S1002, upon receiving the GetPTZConfiguration command, the camera 1000 determines setting values to be transmitted (response) to the controller 2000. The GetPTZConfiguration command is given token information (identifier) called Token in order to identify the Configuration that the camera has. The camera 1000 uses the Token and the Mac address given to GetPTZConfiguration to determine the setting value to respond to the controller 2000. In S1003, the camera 1000 transmits the setting values determined in S1002 to the controller 2000.

FIG. 5 is a flowchart showing the operation of the camera in the first embodiment. Specifically, it shows the control executed by the camera 1000 when receiving the GetPTZConfiguration command.

In S1101, the camera 1000 receives a GetPTZConfiguration command from the controller 2000 via the communication unit 1006. As described above in S1001, the GetPTZConfiguration command is a command that requests acquisition of the PTZConfiguration that the camera 1000 has.

In S1102, the camera 1000 obtains the Mac address included in the GetPTZConfiguration command received in S1101. Specifically, the GetPTZConfiguraiton command received in S1101 is a command based on an HTTP request, and after being received by the communication unit 1006, the control unit 1001 performs decoding processing to interpret the command. Since the Ethernet (registered trademark) header added to the HTTP request includes a Mac address, the Mac address is also acquired during the decoding process. The Mac address may be obtained by obtaining it from the Ethernet header, or by memorizing the combination of IP address and Mac address and determining it from the IP address.

In S1103, the camera 1000 determines whether there is a Ramp value stored in association with the combination of the Mac address acquired in S1102 and the Token included in the command. If a command related to PTZConfiguration has been sent previously, there is a linked Ramp value in the process of linking each parameter in S1107, which will be described later, so the process advances to S1104. On the other hand, if there is no linked Ramp value, the process advances to S1105.

In S1104, the camera 1000 transmits PTZConfiguration including the linked Ramp value to the controller 2000 as a response value.

In S1105, the camera 1000 determines whether a default value (initial value) of Ramp suitable for the Mac address acquired in S1102 is stored. If the Mac address acquired in S1102 is included in the table, the process advances to S1106, and if the acquired Mac address is not included in the table, the process advances to S1108. For example, as a default value, a suitable combination table of Mac address and Ramp is stored in advance in the storage unit 1002 in the camera 1000.

FIG. 6 is a diagram showing an example of a combination table in the first embodiment. The combination table is a table that defines combinations of Ramp and Mac addresses. As a method of determining a suitable Ramp from a Mac address using a table, prepare a table in which all digits of a Mac address are registered as shown in Figure 6 (a), search for a completely matching Mac address, and select a suitable Ramp. A method of determining Ramp may also be used. Alternatively, as shown in FIG. 6(b), a table may be prepared in which only a part of the upper four digits is registered, and the part may be searched to determine an appropriate Ramp.

In S1106, the camera 1000 newly stores the association between the Token included in the GetPTZConfiguration command received in S1102, the Mac address, and Ramp. In S1107, the camera 1000 transmits PTZConfiguration including a suitable Ramp value to the controller 2000 as a response value.

In S1108, the camera 1000 transmits the PTZConfiguration associated with the Token included in GetPTZConfiguration to the controller 2000 as a response value.

In the above description, the camera 1000 stores a combination table of Ramp and Mac address (FIG. 6) in advance, but the combination table may be registered externally.

As described above, according to the first embodiment, the camera identifies the controller based on the Mac address included in the GetPTZConfiguration command sent from the controller. Then, the Ramp value that responds is changed according to the Mac address. With this configuration, it is possible to set the acceleration of the PTZ drive according to each controller, and it is possible to reduce differences in operational feel when using a plurality of different controllers.

Note that in the above description, identification was performed based on the Mac address included in the configuration information acquisition request command (predetermined command), but the configuration may be such that identification is performed based on the Mac address included in other commands. . For example, identification may be performed based on a Mac address included in a drive request command (PTZMove command, etc.).

(Second embodiment)
In the second embodiment, a configuration will be described in which a configuration information setting command related to PTZ driving and a PTZ driving command transmitted from a controller are used to determine a Ramp value to be used for driving. As will be described in detail later, the controller is identified by the Mac address included in the configuration information setting command related to PTZ driving, and the combination of the Mac address, Token, and acceleration (Ramp value) is registered. After that, when a PTZ drive command is received, the acceleration during driving is determined from the combination of the Mac address and Token. Note that the configuration of the system and each device is the same as that of the first embodiment (FIGS. 1 to 3), so a description thereof will be omitted.

<Device operation>
FIG. 7 is a diagram showing the operation sequence of the system in the second embodiment. Specifically, this is a control sequence for configuration information setting and driving regarding PTZ driving in ONVIF.

In S2001, the controller 2000 transmits a SetPTZConfiguration command to the camera 1000. As described above, PTZConfiguration is a setting value related to PTZ drive standardized by ONVIF. The SetPTZConfiguration command is a command that requests updating of the PTZConfiguration of the camera 1000.

In S2002, upon receiving the SetPTZConfiguration command, the camera 1000 executes setting value update processing. The SetPTZConfiguration command is given an identifier called Token in order to identify the Configuration that the camera has. Using this identifier and the Mac address given to SetPTZConfiguration, the setting values including the Ramp value are updated. After that, in S2003, the camera 1000 transmits the success or failure of the setting update command to the controller 2000.

In S2004, the controller 2000 transmits a PTZMove command to the camera 1000. The PTZMove command is a command that requests the camera 1000 to perform PTZ driving according to PTZConfiguration.

In S2005. When the camera 1000 receives the PTZMove command, it determines the acceleration setting to be used for driving. Specifically, the identifier specified by the PTZMove command and the Mac address given to the PTZMove command are used to determine the acceleration setting during driving including the Ramp value. After that, in S2006, the camera 1000 performs PTZ driving based on the acceleration setting determined in S2005. In S2007, the camera 1000 transmits a response (for example, success or failure) to the PTZMove command to the controller 2000.

FIG. 8 is a flowchart showing the operation of the camera in the second embodiment. Specifically, this is a flowchart corresponding to the setting value update process corresponding to S2001 to S2003 in FIG.

In S2101, the camera 1000 receives a SetPTZConfiguration command from the controller 2000. As described above, the SetPTZConfiguration command is a command that requests updating of the PTZConfiguration of the camera 1000. Here, PTZConfiguration includes a Ramp parameter. The camera 1000 receives the SetPTZConfiguration command via the communication unit 1006.

In S2102, the camera 1000 obtains the Mac address included in the SetPTZConfiguration command received in S2101. Specifically, the SetPTZConfiguraiton command received in S2101 is a command based on an HTTP request, and after being received by the communication unit 1006, the control unit 1001 performs decoding processing to interpret the command. Since the Ethernet header added to the HTTP request includes a Mac address, the Mac address is also acquired during the decoding process. The Mac address may be obtained by obtaining it from the Ethernet header, or by memorizing the combination of IP address and Mac address and determining it from the IP address.

In S2103, the camera 1000 determines whether there is a Ramp value stored in association with the combination of the Mac address acquired in S2102 and the Token included in the command. If a command related to SetPTZConfiguration has been sent previously, the process advances to S2104 since there is a Ramp value associated with the Token and Mac address in the process of associating each parameter in S2105, which will be described later. On the other hand, if there is no linked Ramp value, the process advances to S2105.

In S2104, the camera 1000 updates the linked Ramp value and PTZConfiguration, and proceeds to S2106.

In S2105, the camera 1000 associates the specified Ramp value with the combination of the Mac address and Token acquired in S2102 and newly registers the combination. In the camera 1000, a table in which the Mac address, Token, and Ramp are registered is held in the storage unit 1002. In S2106, the camera 1000 transmits to the controller 2000 a response indicating the success or failure of the SetPTZConfiguraiton command.

FIG. 9 is a diagram showing an example of a combination table in the second embodiment. The combination table is a table that stores combinations of Token, Ramp, and Mac addresses. As shown in FIG. 9, Ramp values are registered one by one for each combination of Mac address and Token.

FIG. 10 is a flowchart showing the operation of the camera in the second embodiment. Specifically, this is a flowchart corresponding to PTZ drive control processing corresponding to S2004 to S2007 in FIG.

In S2201, the camera 1000 receives a PTZMove command from the controller 2000. As described above, the PTZMove command is a command that requests the camera 1000 to perform PTZ drive according to the PTZConfiguration (including the Ramp parameter). Camera 1000 receives the PTZMove command via communication unit 1006.

In S2202, the camera 1000 acquires the Mac address included in the PTZMove command received in S2201. Specifically, the PTZMove command received in S2201 is a command based on an HTTP request, and after being received by the communication unit 1006, the control unit 1001 performs decoding processing to interpret the command. Since the Ethernet header added to the HTTP request includes a Mac address, the Mac address is also acquired during the decoding process. The Mac address may be obtained by obtaining it from the Ethernet header, or by memorizing the combination of IP address and Mac address and determining it from the IP address.

In S2203, the camera 1000 determines whether there is a Ramp value stored in association with the combination of the Mac address acquired in S2202 and the Token included in the command. If there is a Ramp value linked to the Token and Mac address, the process advances to S2204; if there is no linked Ramp value, the process advances to S2205.

In S2204, the camera 1000 performs PTZ driving using the linked Ramp value. On the other hand, in S2205, PTZ driving is performed using the Ramp value tied only to the token. After that, in S2206, the camera 1000 transmits a response (for example, success or failure) to the PTZMove command to the controller 2000.

As described above, according to the second embodiment, the camera identifies the controller based on the Mac address included in the configuration information setting command related to PTZ driving transmitted from the controller. Then, the combination of the Mac address, Token, and Ramp value is registered (updated). After that, when a PTZ drive command is received, the acceleration (Ramp value) used for drive is determined from the combination of the Mac address and Token. With this configuration, similarly to the first embodiment, it is possible to set the acceleration of the PTZ drive according to each controller, and it is possible to reduce differences in operational feel when using a plurality of different controllers. Furthermore, even when configuration information setting commands are received from multiple controllers using the same token, it is possible to perform PTZ control with an acceleration that corresponds to each controller.

(Third embodiment)
In the third embodiment, a mode will be described in which a controller is identified by a Mac address included in a PTZ drive command transmitted from the controller, and an acceleration setting value used for drive is determined. Note that the configuration of the system and each device is the same as that of the first embodiment (FIGS. 1 to 3), so the description thereof will be omitted.

<Device operation>
FIG. 11 is a flowchart showing the operation of the camera in the third embodiment. Specifically, control executed by the camera 1000 when receiving a PTZ drive command from the controller 2000 is shown.

In S3001, the camera 1000 receives a PTZMove command from the controller 2000. As described above, the PTZMove command is a command that requests the camera 1000 to perform PTZ drive according to the PTZConfiguration (including the Ramp parameter). Camera 1000 receives the PTZMove command via communication unit 1006.

In S3002, the camera 1000 acquires the Mac address included in the PTZMove command received in S3001. Specifically, the PTZMove command received in S1001 is a command based on an HTTP request, and after being received by the communication unit 1006, the control unit 1001 performs decoding processing to interpret the command. Since the Ethernet header added to the HTTP request includes a Mac address, the Mac address is also acquired during the decoding process. The Mac address may be obtained by obtaining it from the Ethernet header, or by memorizing the combination of IP address and Mac address and determining it from the IP address.

In S3003, the camera 1000 determines the acceleration to be used for PTZ driving based on the combination of the Mac address acquired in S3002 and the Token included in the command. Specifically, the acceleration is determined based on an acceleration determination table to be described later, and PTZ driving is performed. After that, in S3004, the camera 1000 transmits a response (for example, success or failure) to the PTZMove command to the controller 2000.

FIG. 12(a) shows a list of available acceleration parameters. Here, it is assumed that the acceleration in the imaging mechanism section 1005 can be specified in 100 steps. In this case, as shown in list 3001, the unique command registers that the specified acceleration value (second acceleration setting value) can be set as an integer value in the range of 1 to 100. Furthermore, as shown in list 3002, ONVIF registers that the acceleration specified value (first acceleration setting value) can be set as a Ramp value (an integer value in the range of 1 to 3).

FIG. 12(b) shows a combination table of Mac address, Ramp, and acceleration. This combination table is a table that associates the first specified acceleration value (Ramp value) in ONVIF with the second specified acceleration value in the unique command for each Mac address. Using this table, in S3003 described above, the Ramp value specified by the PTZMove command and the Mac address given to the command are converted into the second acceleration setting value of the unique command. At this time, as illustrated in FIG. 12(b), by specifying the correspondence for each controller (for each Mac address), it becomes possible to specify the acceleration specified value in more detail. Then, the camera 1000 performs PTZ driving using the converted second acceleration setting value. Note that the configuration may be such that the association between the Ramp value and the second acceleration specified value in the unique command can be registered from outside.

As explained above, according to the third embodiment, it is possible to set the acceleration of the PTZ drive according to each controller. In particular, when it is possible to specify the acceleration in the imaging mechanism unit 1005 more precisely, it is possible to further reduce differences in operational feel.

(Other examples)
The present invention provides a system or device with a program that implements one or more of the functions of the embodiments described above via a network or a storage medium, and one or more processors in the computer of the system or device reads and executes the program. This can also be achieved by processing. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

The invention is not limited to the embodiments described above, and various changes and modifications can be made without departing from the spirit and scope of the invention. Therefore, the following claims are hereby appended to disclose the scope of the invention.

1000 cameras; 2000 controllers; 3000 networks

Claims (5)

An imaging device configured to be able to change an imaging direction,
receiving means for receiving a predetermined command from a control device for controlling the imaging device based on an operation by a user ;
determining means for determining a setting value that defines an acceleration when driving a mechanism for changing the imaging direction in the imaging device , based on identification information that identifies the control device included in the predetermined command ;
An imaging device comprising : further comprising a storage means for storing a table defining combinations of identification information and setting values of the control device;
The imaging device according to claim 1, wherein the determining unit determines, as the setting value, a setting value corresponding to identification information of the control device included in the table. 3. The imaging apparatus according to claim 1, wherein the predetermined command is a command to request acquisition of the set value or a command to request driving to change an imaging direction. A method for controlling an imaging device configured to be able to change an imaging direction, the method comprising:
a receiving step of receiving a predetermined command from a control device for controlling the imaging device based on an operation by a user ;
a determination step of determining a setting value that defines an acceleration when driving a mechanism for changing the imaging direction in the imaging device , based on identification information that identifies the control device included in the predetermined command ;
A control method characterized by comprising : A program for causing a computer to function as each means of the imaging device according to claim 1 .

Images