JP6736715B2 - Imaging device, image processing device, control method of imaging device, control method of image processing device, and program - Google Patents

Description

The present invention relates to an image pickup apparatus capable of transmitting a picked-up image to the outside, and particularly to a technique capable of superimposing information such as an image on the picked-up image.

2. Description of the Related Art Conventionally, there is known a technique of superimposing characters and images on a predetermined position of a video and transmitting the superimposed image. For example, an On Screen Display function (hereinafter referred to as an OSD function) that displays information such as characters and images at a fixed position of a video is known.

In addition, recently, a technique of dynamically changing a position where information such as characters and images is superimposed on a video is known. For example, Patent Document 1 discloses an imaging device that moves the position of a cursor on a display screen according to the direction in which the housing is moved when the housing of the camera is moved in the pan or tilt direction. ..

Japanese Unexamined Patent Publication No. 7-131684

In the conventional OSD function, various superimposing methods such as a method of specifying an encoder for superimposing on a video source to perform superimposition and a method of specifying a stream received by a user to perform superposition have been considered. It was

For example, when superimposing on the video source, the OSD function is superposed on all the videos transmitted from the imaging device. Further, when superimposing the stream to be transmitted, only the user who is receiving the stream can observe information such as characters and images.

There is a need to select which superimposing method to use for such a plurality of superimposing methods depending on the user or application.

However, the conventional OSD function setting method has a problem that various superimposing methods cannot be selected.

In order to solve the above problems, an image processing device according to the present invention is an image processing device that displays an image output by an imaging device, and provides options regarding superimposition information that the imaging device can superimpose on the image. A transmission unit that transmits an acquisition request for the information to the image capturing apparatus; a receiving unit that receives information indicating the options of the image capturing apparatus from the image capturing apparatus; and information that indicates the options received by the receiving unit. A display control unit that displays a user interface for selecting a parameter related to the superimposition information based on the information, and the display control unit is information indicating the option among the parameters related to the superposition information to be superimposed on an image. Is displayed on the user interface in which parameters not included in are not selectable, and the transmitting unit transmits the parameters selected on the user interface to the imaging device.

According to the present invention, there is an effect that it is possible to notify an external device of options of superimposition information that can be superimposed on an image by an imaging device .

Further, according to the present invention, even when the image pickup apparatus supports a plurality of superposition methods, there is an effect that the user's complicated operation can be reduced.

It is a block diagram which shows the structure of the surveillance camera in a present Example. It is a block diagram which shows the structure of the client apparatus in a present Example. FIG. 1 is a system configuration diagram including a surveillance camera and a client device of this embodiment. It is a sequence chart figure which shows the command transaction of a present Example. It is a figure which shows the OSD setting GUI of the client apparatus of a present Example. It is a figure which shows the OSD setting GUI of the client apparatus of a present Example. It is a flowchart figure which shows the OSD setting object selection process of the client apparatus of a present Example. It is a flowchart figure which shows the OSD setting object selection process of the client apparatus of a present Example. It is a figure which shows the example of definition of the OSDConfiguration type of a present Example. It is a figure which shows the example of definition of the OSDConfiguration type of a present Example. It is a figure which shows the example of definition of the OSDConfigurationOptions type of a present Example. It is a figure which shows the example of definition of the OSDConfigurationOptions type of a present Example. It is a figure which shows the structure of the GetOSDConfigurationOptions command and response of a present Example. It is a figure which shows the structure of the GetOSDConfigurationOptions command and response of a present Example. It is a figure which shows the OSD setting GUI of the client apparatus of a present Example.

FIG. 1 is a block diagram showing the configuration of the surveillance camera in this embodiment.

In FIG. 1, 1001 is an image pickup optical system, 1003 is an image pickup element, 1005 is an image processing circuit, 1007 is a first combining circuit, 1009 is a pixel number conversion circuit, and 1011 is a pixel number conversion memory. Further, 1013 is a second synthesis circuit, 1015 is an encoding circuit (compression encoding processing circuit), 1017 is an encoding memory, 1019 is a communication circuit (hereinafter referred to as an IF circuit), 1021 is a communication buffer, and 1023 is communication. It is a port. Further, 1025 is an OSD circuit, 1027 is a central processing circuit (hereinafter referred to as CPU), 1029 is a non-volatile memory (hereinafter referred to as EEPROM) that can be electrically written and erased, and 1031 is a CPU memory.

The operation of the surveillance camera according to the present embodiment will be described below with reference to FIG.

A light ray from a subject to be imaged is incident on the image sensor 1003 via the image pickup optical system 1001 and photoelectrically converted. The image sensor 1003 in this embodiment is composed of a CCD, a CMOS or the like. The image sensor 1003 according to the present embodiment corresponds to an image capturing unit that captures an image of a subject formed by the image capturing optical system 1001 and outputs the image as a video signal.

In FIG. 1, the I/F circuit 1019 receives an OSD setting command from a client device described later. The OSD setting command is analyzed by the CPU 1027, and the OSD setting information is input to the OSD circuit 1025. The OSD circuit 1025 generates an OSD according to the input OSD setting information.

Further, the I/F circuit 1019 outputs the image stream coded by the coding circuit 1015 as desired by the user to the outside. The setting information regarding the encoding is transmitted from the client device described later and is received by the I/F circuit 1019. The CPU 1027 instructs the encoding circuit 1015 to perform encoding based on the relevant encoding setting information. In the present embodiment, for example, Motion JPEG (hereinafter referred to as MJPEG), H.264, or the like. H.264, MPEG4, MPEG2, H.264. Encoding such as H.265 is performed.

The coding setting information also includes, for example, designation information relating to the image size or the image resolution. When the image size of the image output by the image sensor 1003 is different from the specified image size, the pixel number conversion circuit 1009 performs image enlargement processing or reduction processing to obtain the specified image size. Generate an image. Pixel interpolation processing is also performed when the image is enlarged or reduced.

By operating as described above, in the surveillance camera of this embodiment, it is possible to transmit image streams of different image sizes in the same scene and in the same encoding method almost at the same time. That is, the images of the same scene and different image sizes generated by the pixel number conversion circuit 1009 are time-divisionally input to the encoding circuit 1015, subjected to the same encoding method, and output. The image stream is output to the outside via the I/F circuit 1019.

Next, the configuration of the client device according to the present exemplary embodiment will be described with reference to FIG.

FIG. 2 is a block diagram showing the configuration of the client device according to the embodiment of the present invention.

In FIG. 2, reference numeral 2008 is an input unit, 2014 is a digital interface unit (hereinafter referred to as I/F), 2016 is an interface terminal, 2022 is a display unit, 2026 is a central processing unit (hereinafter referred to as CPU), and 2028 is It is a memory.

The client device shown in FIG. 2 is typically a general-purpose computer such as a personal computer (hereinafter referred to as a PC). As the input unit 2008, a pointing device such as a keyboard or a mouse is used, for example. As the display unit 2022, for example, a liquid crystal display device, a plasma display display device, a cathode ray tube (hereinafter referred to as CRT) display device such as a cathode ray tube, or the like is used.

The GUI of the client is displayed on the display unit 2022. The user of the client device operates the GUI via the input unit 2008. The CPU 2026 executes software for displaying the GUI and detecting a user operation on the input unit 2008. An intermediate result of the operation in the CPU 2026, a data value that needs to be referred to later, and the like are temporarily stored in the memory 2028 and referred to. In the present embodiment, the above-described operation realizes the above-described operation of the external client.

The network configuration according to this embodiment will be described below with reference to FIG.

Reference numeral 1000 in FIG. 3A is a diagram showing a surveillance camera according to an embodiment of the present invention.

1101 is a mechanism for changing the lens direction to the pan direction, 1102 is a mechanism for changing the tilt direction, and 1103 is a zoom mechanism.

FIG. 3B is a system configuration diagram including the surveillance camera 1000.

Reference numeral 2000 denotes a client device indicating an external device according to the present invention. The monitoring camera 1000 and the client device 2000 are connected to each other via an IP network 1500 so that they can communicate with each other. The client apparatus 2000 transmits various commands to the surveillance camera 1000, such as changing imaging parameters, driving a pan head, and starting video streaming, which will be described later. Surveillance camera 1000 transmits responses to these commands and video streaming to client device 2000.

FIG. 3C is a diagram showing another surveillance camera of this embodiment.

In FIG. 3C, reference numeral 1200 is another monitoring camera according to this embodiment, and the monitoring camera 1200 and the client device 2000 are connected to each other via the IP network 1500 so that they can communicate with each other. The client device 2000 transmits various commands to the surveillance camera 1200, such as changing imaging parameters described later and starting video streaming. Surveillance camera 1200 transmits responses to these commands and video streaming to client device 2000.

Next, the command transaction of this embodiment will be described with reference to FIG.

FIG. 4 is a sequence chart diagram showing a command transaction between the surveillance camera 1000 and the client apparatus 2000.

FIG. 4A shows a typical command transaction from the setting start to the video distribution.

In FIG. 4A, 7100 is a transaction of the GetVideoSourceConfigurations command. With this command, the client apparatus 2000 acquires the list of VideoSourceConfiguration held by the surveillance camera 1000.

Reference numeral 7101 denotes a transaction of the GetVideoEncoderConfigurations command. With this command, the client apparatus 2000 acquires the list of VideoEncoderConfiguration held by the monitoring camera 1000.

Reference numeral 7102 denotes a transaction of the GetConfigurations command. With this command, the client apparatus 2000 acquires the list of PTZConfiguration held by the monitoring camera 1000.

Reference numeral 7103 denotes a transaction of CreateProfile command. With this command, the client apparatus 2000 creates a new MediaProfile in the surveillance camera 1000 and obtains the ProfileToken.

Reference numerals 7104, 7105, and 7106 denote transactions of the AddVideoSourceConfiguration command, the AddVideoEncoderConfiguration command, and the AddPTZConfiguration command, respectively.

Each command allows the client device to associate a desired VideoSourceConfiguration, VideoEncoderConfiguration, and PTZConfiguration with the specified MediaProfile.

Reference numeral 7107 denotes a transaction of the GetStreamUri command. With this command, the client apparatus 2000 acquires an address (URI) for the monitoring camera 1000 to acquire a delivery stream based on the specified MediaProfile setting.

Reference numeral 7108 denotes a Describing command transaction. By executing this command using the URI acquired in 7107, the client apparatus 2000 requests and acquires information on the content streamed by the monitoring camera 1000.

7109 is a transaction of the Setup command. By executing this command using the URI acquired in 7107, the transmission method of the stream including the session number is shared between the client apparatus 2000 and the monitoring camera 1000.

7110 is a Play command transaction. By executing this command using the session number acquired in 7109, the client apparatus 2000 requests the monitoring camera 1000 to start a stream.

7111 is a delivery stream. The monitoring camera 1000 distributes the stream requested to be started in 7110 by the transmission method shared in 7109.

7112 is a transaction of a Teardown command. By executing this command using the session number acquired in 7109, the client apparatus 2000 requests the monitoring camera 1000 to stop the stream.

Next, with reference to FIG. 4B, an OSD setting command transaction according to the present embodiment will be described.

FIG. 4B is a sequence chart showing a typical OSD setting command transaction (acquisition request transaction) between the surveillance camera 1000 and the client apparatus 2000.

In FIG. 4B, 7200 is a transaction of the GetOSDs command. The GetOSDs command is a command for the client apparatus 2000 to instruct the monitoring camera 1000 to return all the OSDConfiguration 6105 associated with the specified OSDReference.

Reference numeral 7201 denotes a CreateOSD command transaction. The CreateOSD command is a command for the client apparatus 2000 to instruct the monitoring camera 1000 to newly create the OSDConfiguration 6105 in association with the specified OSDReference. By executing the CreateOSD command, the monitoring camera 1000 returns the OSDToken, which is the generated OSD ID, to the client apparatus 2000.

Reference numeral 7202 denotes a transaction of GetOSDConfigurationOptions.

The GetOSDConfigurationOptions command is a command for the client apparatus 2000 to instruct the monitoring camera 1000 to send back a selection range or options of each parameter of OSDConfiguration. The selection range or options of each parameter of OSDConfiguration can be set by a SetOSD command described later.

The client device of the present embodiment receives a GetOSDConfigurationOptions response as a response to the GetOSDConfigurationOptions command.

The transmission of the GetOSDConfigurationOptions command corresponds to a capability inquiry step regarding a plurality of composition processing capabilities of the image processing apparatus of the present invention. Further, the reception of the GetOSDConfigurationOptions response performed by the client device of this embodiment corresponds to the step of receiving the response of the capability related to the composition processing method of the present invention.

Reference numeral 7203 denotes a GetOSD transaction. The GetOSD command is a command for the client apparatus 2000 to instruct the monitoring camera 1000 to return the OSDConfiguration having the designated OSDToken.

Reference numeral 7204 denotes a SetOSD transaction. The SetOSD command is a command for the client apparatus 2000 to instruct the monitoring camera 1000 to edit each parameter included in OSDConfiguration. By executing SetOSD, the monitoring camera 1000 edits the contents of OSDConfiguration having the OSDToken designated by the client apparatus 2000. By this operation, the client apparatus 2000 can instruct the monitoring camera 1000 to display a new OSD and change the color, size, position, etc. of the OSD being displayed.

The operation of transmitting the SetOSD command corresponds to the transmission of OSD information according to the present invention.

Reference numeral 7205 denotes a DeleteOSD command transaction. The DeleteOSD command is a command for the client apparatus 2000 to instruct the monitoring camera 1000 to delete the OSDConfiguration created by the CreateOSD command. By executing DeleteOSD, the monitoring camera 1000 deletes the OSDConfiguration having the OSDToken designated by the client apparatus 2000 from the storage unit of the monitoring camera.

Next, the OSD setting graphical user interface (hereinafter sometimes referred to as GUI) of the client device according to the present embodiment will be described with reference to FIGS. 5-1 and 5-2.

5-1 and 5-2 are diagrams showing the configuration of the GUI.

In FIG. 5A, 6800 is a client application window, and 6802 is an OSD setting window (window for setting an image superimposing method). Reference numerals 6804, 6806, 6808, and 6810 are a first stream display window, a second stream display window, a third stream display window, and a fourth stream display window, respectively. Further, 6812 is a stream selection window.

In the client device of this embodiment, the user can set the OSD display settings for the connected surveillance cameras by setting each item in the OSD setting window 6802.

In the first stream display window 6804 to the fourth stream display window 6810, the stream video selected by the client device of this embodiment is displayed. In the stream selection window 6812, all stream videos that can be received by the client of this embodiment can be displayed, and the videos are displayed in a reduced size.

In the client apparatus of this embodiment, the user can scroll the reduced display window in the stream selection window 6812 left and right and then select a desired stream video. The selected video can be enlarged and displayed in the first stream display window 6804 to the fourth stream display window 6810.

Further, in the OSD setting GUI, after selecting any of the first stream display window 6804 to the fourth stream display window 6810 and then selecting the OSD setting window 6802, the user sets the OSD setting for the desired video. It can be carried out.

FIG. 5-1(b) is a diagram for explaining the function of the OSD setting window 6802.

In FIG. 5B, 7000 is an OSD setting target selection frame, 7001 is an OSD type setting frame, and 7002 is an OSD display position setting frame. Also, 7003 is a text setting frame, and 7004 is an image setting frame. Furthermore, 7005 is an OSD creation button, 7006 is an OSD update button, 7007 is an OSD deletion button, and 7010 is a reference selection box.

The OSD setting target selection frame 7000 is a part for selecting an OSD setting target in the surveillance camera. In the present embodiment, the OSD setting target is, for example, Video Source Configuration, Video Encoder Configuration, Media Profile, StreamURI, SnapshotURI.

The Video Source Configuration operates as the image source of the present invention. Further, the Video Encoder Configuration operates as the encoder of the present invention.

The Media Profile is a concept that includes a combination of information such as a combination information of an image source and an encoder, additional information such as an audio stream and a metadata stream, and information such as image capturing direction information of an image, and identifies the stream of the present invention. It works as one of the information to do.

Also, the StreamURI and the SnapshotURI also operate as one of the stream identification information. The StreamURI is information for specifying a moving image stream, and the SnapshotURI is information for specifying a still image stream. By using the StreamURI and the SnapshotURI, it is possible to control the OSD setting for each user having different user authority. For example, in this embodiment, the OSD is set only for the image stream having the administrator authority, so that the OSD can be observed only by the client device operating with the administrator authority. With this operation, according to the present invention, it is possible to set the OSD without disclosing information such as debug information, which is effective only to a user having a certain authority, to a user who does not need the information.

Prior to displaying the OSD setting window 6802, the client device according to the present embodiment transmits, for example, a GetOSDConfigurationOptions command to the surveillance camera. In response to the command, the surveillance camera returns a settable range of each parameter value and a list of selectable values for OSDConfiguration to the client apparatus as GetOSDConfigurationOptionsResponse.

In the present embodiment, the transmission timing of the GetOSDConfigurationOptions command is before the display of the OSD setting window 6802, but it may be any time. For example, it may be transmitted at the timing when the GUI of the client device of this embodiment is displayed. Also, it may be transmitted when the client device of this embodiment is activated.

Further, the GetOSDConfigurationOptions command may be transmitted from the first stream display window 6804 to the fourth stream display window 6810 when a stream is selected by the user.

Further, the GetOSDCConfigurationOptions command may be transmitted at the timing when a desired stream is selected from the reduced display window in the stream selection window 6812.

In this case, the latest OSD information regarding the selected stream can be obtained, which is convenient.

The GetOSDConfigurationOptionsResponse lists the References with which the OSD can be set for the surveillance camera according to the present embodiment. The list of References is OSDReferenceOptions type data. The OSDReferenceOptions type data includes the information of the OSD setting target.

The operation of transmitting the GetOSDConfigurationOptions command corresponds to the step of inquiring the capabilities regarding the plurality of composition processing methods in the present invention. Further, the GetOSDConfigurationOptionsResponse in question contains capability information regarding a plurality of composition processing methods in the present invention. Further, the reception operation of the GetOSDConfigurationOptionsResponse described above corresponds to the step of receiving the response of the capability regarding the composition processing method.

The client device of the present embodiment displays only the options transmitted from the surveillance camera as the OSD setting target. As illustrated in FIG. 5B, only the video source configuration, the video encoder configuration, the media profile, and the stream URI transmitted by the surveillance camera are displayed as options. In this embodiment, a reference selection box 7010 is displayed near the selected OSD setting target check box. The reference selection box 7010 is a selection box for selecting an individual target for which the OSD is actually set, from the selected OSD setting targets. In FIG. 5-1(b), Video Source Configuration is selected. Therefore, in the reference selection box 7010 of FIG. 5B, the video source configuration tokens that the surveillance camera has are listed.

When the video source configuration is selected as described above, the reference source selection box 7010 lists the video source configuration tokens. When Video Encoder Configuration Token is selected, Video Encoder Configuration Token is listed. In addition, when Media Profile is selected, Media Profile Token is listed.

When the StreamURI is selected, the corresponding URI is listed when there are a plurality of streams received by the client. If only one stream is being received, the URI of that stream is displayed.

The above-mentioned display operation of the client includes the step of analyzing the response of the capability regarding the composition processing method of the present invention. The operation of the user selecting from the displayed options includes the step of selecting one or a plurality of combining processing methods from the plurality of combining processing methods of the present invention.

The OSD type setting frame 7001 is a part for selecting the type of OSD to be superimposedly displayed, that is, OSDType. Since TEXT is selected in FIG. 5A, for example, the detailed setting of the text setting frame 7003 is valid. Further, the image setting frame 7004 is invalidated and configured so that the user cannot set it.

The OSD display position setting frame 7002 is a part for designating the OSD display position. UPPER_LEFT (upper left of screen), UPPER_RIGHT (upper right of screen), LOWER_LEFT (lower left of screen), LOWER_RIGHT (lower right of screen), and CUSTOM (coordinate designation) can be selected. In FIG. 5B, the upper left of the screen is selected.

Further, in this embodiment, when CUSTOM is selected in the OSD display position setting frame 7002, coordinates can be designated by dragging the pointer on the target stream display window.

For example, the user can specify two points on the first stream display window 6804 after selecting the CUSTOM check box in the OSD display position setting frame 7002. By the designation, the display target video for displaying the OSD and the display coordinates on the video can be designated at the same time.

As described above, the text setting frame 7003 is a portion for setting detailed data when TEXT is selected in the OSD type setting frame. As a type of TEXT, Time and Date (date and time), Bitrate (bit rate), and Text String (character string) can be selected. In the case of Text String, an arbitrary character string can be designated by the text input box.

The OSD setting process in this embodiment corresponds to the step of setting OSD information in the present invention.

The image setting frame 7004 is a part for setting detailed data when IMAGE is selected in the OSD type setting frame 7001. In the image setting frame 7004, the user sets the address of the image file to be displayed as the OSD in the text input box of the Image File Path.

When the OSD creation button 7005 is pressed, the client device issues a CreateOSD command to the surveillance camera, and then uses the returned OSDToken to issue a SetOSD command to the surveillance camera according to the content input by the user on the screen of this figure. Execute.

Further, when the OSD update button 7006 is pressed, the client apparatus 2000 executes the SetOSD command to the monitoring camera 1000 according to the content input by the user on the screen of this figure using the OSDToken stored in advance.

When the OSD delete button 7007 is pressed, the client device 2000 executes the DeleteOSD command to the surveillance camera 1000 using the OSDToken stored in advance.

The operation of transmitting the SetOSD command and the operation of transmitting the DeleteOSD command described above include the step of transmitting the OSD information to the image processing apparatus according to the selected combination processing method according to the present invention.

As described above, in the client device of the above-described embodiment, the OSD setting target selection frame 7000 displays only the OSD setting targets that can be set in the surveillance camera to be controlled. However, in the present invention, of the OSD setting targets displayed in the OSD setting target selection frame 7000, only the OSD setting targets that can be set in the surveillance camera may be settable on the client. In this case, for the OSD setting target that cannot be set in the surveillance camera, for example, items that cannot be set are grayed out, which indicates to the user that setting is not possible.

The above operation will be described below with reference to FIG.

In FIG. 5-2(c), the same reference numerals as those in FIG. 5-1(b) indicate the same functions.

In FIG. 5-2(c), 7012 is a Video Source Configuration Token selection box, and 7014 is a Video Encoder Configuration Token selection box.

In the GUI of FIG. 5-2(c), as a reference in which the OSD can be set, Video Source Configuration and Video Encoder Configuration are transmitted from the target surveillance camera.

Further, in FIG. 5-2(c), the OSD setting reference that has not been transmitted from the surveillance camera is grayed out and cannot be set. For example, in the present embodiment, as illustrated in FIG. 5-2(c), the Media Profile and the Stream are not designated as the reference in which the OSD can be set, and thus are grayed out and cannot be set. Is displayed.

Further, in the present invention, the client device may be configured to automatically select the OSD setting target based on the information of the OSD setting target that can be set in the surveillance camera to be controlled. In this case, the OSD setting target selection frame 7000 may not be displayed on the OSD setting GUI of the client device.

The information of the OSD setting target that can be set in the surveillance camera is performed by transmitting the GetOSDConfigurationOptions command and receiving the GetOSDConfigurationOptionsResponse operation. The operation of transmitting the GetOSDConfigurationOptions command corresponds to the step of inquiring the capabilities regarding the plurality of composition processing methods in the present invention. Further, the GetOSDConfigurationOptionsResponse in question contains capability information regarding a plurality of composition processing methods in the present invention. Further, the reception operation of the GetOSDConfigurationOptionsResponse described above corresponds to the step of receiving the response of the capability regarding the composition processing method.

In such a case, the client device according to the present exemplary embodiment selects the OSD setting target so that the OSD is displayed in more stream videos, for example. In this embodiment, the influence range of the OSD setting becomes narrower in the order of Video Source, Video Encoder, Media Profile, Stream or Snapshot.

For example, when OSD is set in the Video Source, the OSD is set in the video source, so the OSD is displayed in all distributed videos.

Further, for example, when the OSD is set in the Video Encoder, the OSD is set only in the video of the selected coding. For example, the H.264 standard is used as the encoding method of the OSD setting target. H.264 video is selected, H.264 video is selected. The OSD is displayed only on the video distributed by H.264.

Therefore, the client device searches for OSD setting targets that can be set for the surveillance camera in the order of Video Source, Video Encoder, Media Profile, Stream or Snapshot. Then, it operates to select the matching setting target.

For example, when the surveillance camera of the present embodiment has Video Source, Video Encoder, and Stream as OSD-configurable targets, the client device of the present embodiment automatically selects Video Source and OSD. Make settings. In addition, for example, when the surveillance camera has Video Encoder and Stream as settable OSD setting targets, the client device automatically selects the Video Encoder and performs OSD setting.

Further, in the case where the surveillance camera has a plurality of setting target subtypes in the same setting target category, the client device of the present embodiment selects the setting target subtype so as to have the largest influence range. .. For example, when the surveillance camera has Video Encoder as an OSD setting target and supports a plurality of coding methods, for example, the coding method outputting the most video streams is set as the OSD setting target. Automatically select as a subtype. For example, in the above case, the surveillance camera may send two MJPEG streams, H.264 streams, and so on. When four H.264 streams are distributed, the client device according to the present exemplary embodiment is an H.264 standard. H.264 is automatically selected as the OSD setting target subtype.

In the above-described embodiment, the client device is configured to automatically select the OSD setting target so as to be displayed in more stream videos, but it is displayed in less stream videos. Alternatively, the OSD setting target may be automatically selected.

In such a case, the client device searches for OSD setting targets that can be set for the surveillance camera in the order of Stream or Snapshot, Media Profile, Video Encoder, and Video Source. Then, it operates to select the matching setting target.

For example, it is assumed that the surveillance camera of the present embodiment has a video source, a video encoder, and a stream as OSD-configurable targets. In that case, the client device that automatically selects to be displayed in less stream video operates to automatically select Stream and perform OSD setting.

Further, the client device of the present embodiment provides a selection box on the OSD setting GUI for selecting whether the range of influence of the OSD setting is wide or narrow, and sets the OSD setting target according to the user's instruction. May be automatically selected. In this case, the client device selects the OSD setting target so that it is displayed in more stream video, as described above, when the user selects the wide range. In addition, when the user selects a narrow range, as described above, the OSD setting target is automatically selected so as to be displayed in a smaller number of stream videos.

The above-described automatic selection operation of the OSD setting target corresponds to the step of automatically selecting one combination processing method from the plurality of combination processing methods in the present invention.

An example of the OSD setting GUI configuration of the client device described above is shown in FIG. 5-2(d).

In the configuration example, a Wide selection check box and a Narrow selection check box are provided on the OSD setting target selection frame 7000. One of the Wide selection check box and the Narrow selection check box is configured to be selectable by the user. The check box selected by the user is displayed with an instruction display indicating that the check box is selected. For example, in FIG. 5-2(d), it is indicated that the Wide selection check box is selected.

As shown in FIG. 5-2(d), when the user selects the Wide selection check box, the client apparatus according to the present exemplary embodiment displays the stream information in more stream images from the setting target information transmitted by the surveillance camera. As described above, the OSD setting target is selected. Further, when the user selects the Narrow selection check box, the client apparatus of the present embodiment selects the OSD setting target from the setting target information transmitted by the surveillance camera so that the OSD setting target is displayed in a smaller stream video. select.

When the OSD creation button 7005 is pressed, the client device 2000 issues a CreateOSD command to the monitoring camera 1000. Then, using the returned OSDToken, the SetOSD command is executed for the surveillance camera 1000 according to the content input by the user on the screen of this figure.

Further, when the OSD update button 7006 is pressed, the client apparatus 2000 executes the SetOSD command to the monitoring camera 1000 according to the content input by the user on the screen of this figure using the OSDToken stored in advance.

When the OSD delete button 7007 is pressed, the client device 2000 executes the DeleteOSD command to the surveillance camera 1000 using the OSDToken stored in advance.

The operation of transmitting the SetOSD command and the operation of transmitting the DeleteOSD command described above include the step of transmitting the OSD information to the image processing apparatus according to the selected combination processing method according to the present invention.

The OSD setting target selection process of the client device according to this embodiment will be described below with reference to FIG.

FIG. 6A is a flowchart showing a GUI display process for selecting an OSD setting target in the client device in the present embodiment. The user of the client device according to the present exemplary embodiment selects the OSD setting target using the GUI.

In FIG. 6A, the OSD setting target selection frame display process of the present embodiment is started in step S8002. In the next step S8004, the GetOSDConfigurationOptions command is transmitted from the client device of this embodiment. In the next step S8006, GetOSDConfigurationOptionsResponse is transmitted from the surveillance camera of the present embodiment, and the client device receives the corresponding Response.

The operation of transmitting the GetOSDConfigurationOptions command corresponds to the step of inquiring the capabilities regarding the plurality of composition processing methods in the present invention. Further, the GetOSDConfigurationOptionsResponse in question contains capability information regarding a plurality of composition processing methods in the present invention. Further, the reception operation of the GetOSDConfigurationOptionsResponse described above corresponds to the step of receiving the response of the capability regarding the composition processing method.

In the next step S8008, the received GetOSDConfigurationOptionsResponse is analyzed by the client device of the present embodiment. The analysis operation of the received GetOSDConfigurationOptionsResponse includes the step of analyzing the response of the capability regarding the composition processing method of the present invention. The OSD setting target selection frame display process is performed according to the analysis result of step S8008. The OSD setting target selection frame display process will be described below.

In a succeeding step S8010, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option relating to Video Source Configuration. If it is determined in step S8010 that the GetOSDConfigurationOptionsResponse includes an option relating to Video Source Configuration, the control proceeds to step S8012. In step S8012, display processing related to Video Source Configuration is performed, and the GUI is updated.

In subsequent step S8014, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding Video Encoder Configuration. If it is determined in step S8014 that GetOSDConfigurationOptionsResponse includes an option regarding Video Encoder Configuration, the control proceeds to step S8016. In step S8016, display processing related to Video Encoder Configuration is performed, and the GUI is updated.

In subsequent step S8018, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding Media Profile. If it is determined in step S8018 that GetOSDConfigurationOptionsResponse includes an option relating to Media Profile, control proceeds to step S8020. In step S8020, display processing related to Media Profile is performed, and the GUI is updated.

In subsequent step S8022, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding the Stream URI. If it is determined in step S8022 that the GetOSDConfigurationOptionsResponse includes an option regarding the Stream URI, the control proceeds to step S8024. In step S8024, display processing related to the Stream URI is performed and the GUI is updated.

In subsequent step S8026, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding Snapshot URI. If it is determined in step S8026 that the GetOSDConfigurationOptionsResponse includes the option related to the Snapshot URI, the control proceeds to step S8028. In step S8028, display processing related to Snapshot URI is performed, and the GUI is updated.

In next step S8030, the OSD setting target selection frame display process of the present embodiment ends.

In this embodiment, when the OSD creation button 7005 is pressed after the above operation, the client device issues a CreateOSD command to the surveillance camera. Then, using the returned OSDToken, the SetOSD command is executed for the surveillance camera according to the contents input by the user on the screen of this figure.

Further, when the OSD update button 7006 is pressed, the client apparatus 2000 executes the SetOSD command to the monitoring camera 1000 according to the content input by the user on the screen of this figure using the OSDToken stored in advance.

When the OSD delete button 7007 is pressed, the client device 2000 executes the DeleteOSD command to the surveillance camera 1000 using the OSDToken stored in advance.

The operation of transmitting the SetOSD command and the operation of transmitting the DeleteOSD command described above include the step of transmitting the OSD information to the image processing apparatus according to the selected combination processing method according to the present invention. Further, as described above, in the present invention, the client device may be configured to automatically select the OSD setting target. The OSD setting target selection process of the client device in such a case will be described below with reference to FIG.

FIG. 6B is a flowchart showing the OSD setting target selection processing of the GUI.

In FIG. 6B, in step S8102, the OSD setting target automatic selection processing of this embodiment is started. In next step S8104, the GetOSDConfigurationOptions command is transmitted from the client device of the present embodiment. In next step S8106, GetOSDConfigurationOptionsResponse is transmitted from the surveillance camera of the present embodiment, and the client device receives the corresponding Response.

In the next step S8108, the received GetOSDConfigurationOptionsResponse is analyzed by the client device of this embodiment.

In the next step S8109, the states of the Wide selection check box and the Narrow selection check box on the OSD setting GUI are checked. If the Wide selection check box is selected, control proceeds to step S8110. If the Narrow selection check box is selected, control moves to step S8130.

In subsequent step S8110, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option relating to Video Source Configuration.

If it is determined in step S8110 that GetOSDConfigurationOptionsResponse includes an option relating to Video Source Configuration, control proceeds to step S8112. In step S8112, the process of setting the OSD setting target to Video Source Configuration is performed, and the GUI is updated.

In the above step S8110, when the received GetOSDConfigurationOptionsResponse does not include the option regarding Video Source Configuration, the control proceeds to step S8114.

In step S8114, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option relating to Video Encoder Configuration.

If it is determined in step S8114 that the GetOSDConfigurationOptionsResponse includes an option relating to Video Encoder Configuration, the control proceeds to step S8116. In step S8116, the process of setting the OSD setting target to Video Encoder Configuration is performed, and the GUI is updated.

If, in step S8114, the GetOSDConfigurationOptionsResponse does not include an option relating to Video Encoder Configuration, control proceeds to step S8118.

In the following Step S8118, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding Media Profile.

If it is determined in step S8118 that the GetOSDConfigurationOptionsResponse includes the options related to Media Profile, the control proceeds to step S8120. In step S8120, the process of setting the OSD setting target to Media Profile is performed, and the GUI is updated.

If it is determined in step S8118 that the GetOSDConfigurationOptionsResponse does not include the option related to Media Profile, the control proceeds to step S8122.

In next step S8122, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding the Stream URI.

If it is determined in step S8122 that the GetOSDConfigurationOptionsResponse includes the option regarding the Stream URI, the control proceeds to step S8124. In step S8124, the process of setting the OSD setting target to the Stream URI is performed, and the GUI is updated.

In subsequent step S8126, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding Snapshot URI.

If it is determined in step S8122 that the GetOSDConfigurationOptionsResponse does not include an option regarding the Stream URI, the control proceeds to step S8126.

When it is determined in step S8126 that the GetOSDConfigurationOptionsResponse includes the option related to the Snapshot URI, the control proceeds to step S8128. In step S8128, a process of setting the OSD setting target to the Snapshot URI is performed, and the GUI is updated.

If it is determined in step S8126 that the GetOSDConfigurationOptionsResponse does not include the option related to the Snapshot URI, in step S8160, the OSD setting target automatic selection process of the present embodiment ends.

When it is determined in step S8109 that the Narrow selection check box is selected, control is passed to step S8130 as described above.

In step S8130, similarly to step S8126, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding Snapshot URI.

If it is determined in step S8130 that the GetOSDConfigurationOptionsResponse includes the option regarding the Snapshot URI, the control proceeds to step S8132. In step S8132, the process of setting the OSD setting target to the Snapshot URI is performed, and the GUI is updated.

In step S8130, if GetOSDConfigurationOptionsResponse does not include an option regarding Snapshot URI, control proceeds to step S8134.

In subsequent step S8134, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding the Stream URI.

If it is determined in step S8134 that the GetOSDConfigurationOptionsResponse includes the option regarding the Stream URI, the control proceeds to step S8136. In step S8136, the process of setting the OSD setting target to the Stream URI is performed, and the GUI is updated.

If it is determined in step S8134 that the GetOSDConfigurationOptionsResponse does not include the option regarding the Stream URI, the control proceeds to the next step S8138.

In subsequent step S8138, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding Media Profile.

If it is determined in step S8138 that GetOSDConfigurationOptionsResponse includes an option related to Media Profile, control proceeds to step S8140. In step S8140, the process of setting the OSD setting target to Media Profile is performed, and the GUI is updated.

If it is determined in step S8138 that the GetOSDConfigurationOptionsResponse does not include the option related to Media Profile, the control proceeds to step S8142.

In Step S8142, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option regarding Video Encoder Configuration.

If it is determined in step S8142 that the GetOSDConfigurationOptionsResponse includes an option regarding Video Encoder Configuration, the control proceeds to step S8144. In step S8144, the process of setting the OSD setting target to Video Encoder Configuration is performed, and the GUI is updated.

In step S8142, if GetOSDConfigurationOptionsResponse does not include an option regarding Video Encoder Configuration, control proceeds to step S8146.

In a succeeding step S8146, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option relating to Video Source Configuration.

If it is determined in step S8146 that the GetOSDConfigurationOptionsResponse includes an option relating to Video Source Configuration, the control proceeds to step S8148. In step S8148, a process of setting the OSD setting target to Video Source Configuration is performed, and the GUI is updated.

If the GetOSDConfigurationOptionsResponse received in step S8146 does not include an option related to Video Source Configuration, the OSD setting target automatic selection process ends in step S8160.

After the above-described operation, in this embodiment, when the OSD creation button 7005 is pressed, the client device issues a CreateOSD command to the surveillance camera. Then, using the returned OSDToken, the SetOSD command is executed for the surveillance camera according to the contents input by the user on the screen of this figure.

Further, when the OSD update button 7006 is pressed, the client apparatus 2000 executes the SetOSD command to the monitoring camera 1000 according to the content input by the user on the screen of this figure using the OSDToken stored in advance.

When the OSD delete button 7007 is pressed, the client device 2000 executes the DeleteOSD command to the surveillance camera 1000 using the OSDToken stored in advance.

The operation of transmitting the SetOSD command and the operation of transmitting the DeleteOSD command described above include the step of transmitting the OSD information to the image processing apparatus according to the selected combination processing method according to the present invention.

7-1 and 7-2 are diagrams for explaining the configuration of OSDConfiguration which is a data type according to the present embodiment.

The data types shown in FIGS. 7-1 and 7-2 are defined using, for example, the XML Schema Definition language (hereinafter referred to as XSD). The OSDConfiguration type is a data type used in the step of setting OSD information in the present invention.

FIG. 7A is a diagram illustrating an example of definition of the OSDConfiguration type.

As shown in FIG. 7-1(a), the OSDConfiguration type is defined as a complex type by the complexType declaration of XML. Further, the OSDConfiguration type is shown to be an extended type that extends the DeviceEntity type by the complexContent element, the extension element and its base attribute. Further, the OSDConfiguration type is shown by the sequence element that data expansion is performed so that its order appears as defined.

The OSDConfiguration type shown in FIG. 7A is a data type used in the GetOSD response or the SetOSD command shown in FIG. 4B, for example.

FIG. 7-1(b) is a diagram showing a definition example of the OSDReference type.

In the OSDReference type data, the choice element indicates a configuration in which one of the choice elements is selected. For example, in the OSDReference type data shown in FIG. 7-1(b), it is shown that only one of the ReferenceToken type or anyURI type data appears in the type.

As the ReferenceToken type, Video Source Configuration Token, Video Encoder Configuration Token, or Media Profile Token can be designated.

Further, as the above anyURI type, in the present embodiment, StreamURI or SnapshotURI can be designated. The OSDReference type is a data type for designating an OSD setting target in this embodiment.

FIG. 7-1(c) is a diagram showing a definition example of the OSDType type.

In the definition example of the OSDType type, the simpler type element indicates that it is an XML simple type, and the restriction element and its base attribute indicate that the type is a string type value-restricted type. In the example of FIG. 7-1(c), the OSDType type is shown to be TEXT or IMAGE as its value.

FIG. 7-1(d) is a diagram showing a definition example of the OSDPosConfiguration type.

In the definition example of the OSDPosConfiguration type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined.

FIG. 7-2(e) is a diagram showing an example definition of the OSDTextConfiguration type.

In the definition example of the OSDTextConfiguration type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined.

FIG. 7-2(f) is a diagram showing an OSDIimageConfiguration type. In the definition example of the OSDImageConfiguration type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined.

FIG. 7-2(g) is a diagram showing a definition example of the Vector type. The Vector type has a configuration in which the attributes x and y of the float type can be described by the attribute element.

FIG. 7-2(h) is a diagram showing a definition example of the Color type. In the Color type, the attribute X, Y, and Z of the float type can be described by the attribute element. Further, the above attributes X, Y, and Z are indicated by the use=“required” designation, indicating that they are indispensable configurations in the Color type. Further, in the relevant Color type, the attribute element of anyURI type ColorSpace can be described by the attribute element.

FIG. 7-2(i) is a diagram showing a definition example of the BackgroundColor type. In the relevant BackgroundColor type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined. In the sequence element, Color type data can be described as an element. In addition, in this type, the int type attribute Transparent can be described.

The client apparatus of the present invention acquires the OSD setting information from the image pickup apparatus of the present embodiment using the OSDConfiguration type data described above. Further, the client apparatus of the present invention is configured to set the OSD in the image pickup apparatus of the present embodiment using the OSDConfiguration type data.

Next, a definition example of the OSDConfigurationOptions type will be described with reference to FIGS. 8A and 8B. The OSDConfigurationOptions type is a data type used in the step of receiving the response of the capability related to the composition processing method in the present invention.

FIG. 8A is a diagram illustrating a definition example of the OSDConfigurationOptions type. In the OSDConfigurationOptions type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined.

The OSDConfigurationOptions type is a data type used for the GetOSDConfigurationOptions response in FIG. 4B, for example. With the GetOSDConfigurationOptions response, the client device of the present embodiment acquires the capability information regarding the OSD setting target that the target monitoring camera has.

In the OSDConfigurationOptions type, the first field is OSDReferenceOptions whose data type is OSDReferenceOptions type. The next field is an int type MaximumNumberOfOSDs. The next field is the OSDType type. The next field is a string type PositionOption. The next field is a TextOption of type OSDTextOptions. The last field is the ImageOptions of type OSDIImageOptions.

The OSDReferenceOptions type is a data type used for giving and receiving the capability relating to the OSD setting target in the present embodiment.

The MaxOccurs=“unbounded” specifier indicates that a plurality of each of the Type and PositionOption fields can exist inside the OSDConfigurationOptions type. Also, the OSDReferenceOptions, TextOption, and ImageOption fields are indicated by the minOccurs=“0” specifier, which indicates that the fields can be omitted.

FIG. 8-1(b) is a diagram showing a definition example of the OSDReferenceOptions type. The OSDReferenceOptions type is a data type used for OSDReferenceOptions, which is the first field in FIG. 8-1(b) described above. In the OSDReferenceOptions type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined. In the OSDReferenceOptions type, the first field is the OSDReference type OSDReference. The maxOccurs=“unbounded” specifier indicates that a plurality of fields can exist inside the OSDReference type.

The OSDReference type used for the OSDReferenceOptions type in FIG. 8-1(b) is the same data type as the type shown in FIG. 7-1(b). As described above, in the OSDReference type, the choice element indicates a configuration in which one of the choice elements is selected. For example, in the OSDReference type data, only one of the ReferenceToken type data or the anyURI type data appears in the type.

As the ReferenceToken type, Video Source Configuration Token, Video Encoder Configuration Token, or Media Profile Token can be designated.

Further, as the above anyURI type, in the present embodiment, StreamURI or SnapshotURI can be designated.

As described above, in the OSD Reference type, one of the OSD setting targets can be designated by the ReferenceToken type data or the anyURI type data.

Further, as described above, in the OSDReferenceOptions type, since a plurality of OSDReference type data can be stored, it is possible to list a plurality of OSD setting targets in the OSDConfigurationOptions type.

In the GetOSDConfigurationOptions analysis in step S8008 of FIG. 6A described above, the OSDReferenceOptions type field is mainly analyzed. Further, in the GetOSDConfigurationOptions analysis in step S8108 of FIG. 6B, the OSDReferenceOptions type field is mainly analyzed.

FIG. 8-1(c) is a diagram showing a definition example of the OSDTextOptions type. In the OSDTextOptions type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined.

In the OSDTextOptions type, the first field is the OSDType type Type field. The next field is a FontSizeRange type of IntRange type. The next field is a string type DateFormat field. The next field is also a string type TimeFormat field. The next field is a ColorOptions type Color field. The last field is an IntRange type transparent field.

By the maxOccurs=“unbounded” specifier, it is shown that a plurality of Type fields, DateFormat fields, and TimeFormat fields can exist inside the OSDTextOptions type.

Further, the DateFormat field, the TimeFormat field, the Color field, and the transparent field are indicated by the minOccurs="0" specifier, which can be omitted.

FIG. 8-1(d) is a diagram showing an example of definition of the OSDIimageOptions type. In the OSDImageOptions type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined.

In the OSDIImageOptions type, the first field is an anyURI type ImagePath field. A plurality of ImagePath fields can be present in the OSDImageOptions type by the maxOccurs=“unbounded” specifier.

FIG. 8-2(e) is a diagram showing a definition example of the IntRange type. In the IntRange type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined.

In the IntRange type, the first field is an int type Min field, and the last field is an int type Max field.

FIG. 8-2(f) is a diagram showing a definition example of the ColorOptions type. In the relevant ColorOptions type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined. In addition, the choice element inside the sequence element indicates that one of the choice elements is selected. Specifically, in the ColorOptions type, one is selected from a ColorList field or a ColorspaceRange field described later.

As described above, one of the options in the ColorOptions type is the Color type ColorList field. Further, another option is a ColospaceRange field of the ColospaceRange type. It is indicated by the maxOccurs=“unbounded” specifier that a plurality of ColorList fields and ColospaceRange fields can exist.

FIG. 8-2(g) is a diagram showing a definition example of the ColospaceRange type. In the ColospaceRange type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined.

The first field of the ColospaceRange type is the X field, the next field is the Y field, and the third field is the Z field. The X field, Y field, and Z field are FloatRange type data. The last field of the ColospaceRange type is a colorspace field of anyURI type.

FIG. 8-2(h) is a diagram showing a definition example of the FloatRange type. In the definition of the FloatRange type, the complexType element indicates that the type is defined as a complex type. Also, the sequence element indicates that the order is a data type that appears as defined.

In the FloatRange type, the first field is a float type Min field, and the last field is a float type Max field.

In the present invention, the client device acquires OSD information that can be set in the image pickup apparatus of the present embodiment from the image pickup apparatus by using the OSDConfigurationOptions type data. Further, in the image pickup apparatus of the present embodiment, the OSDConfigurationOptions type data is used for transmitting capability information regarding OSD in the image pickup apparatus.

Next, the GetOSDConfigurationOptions command and its response, GetOSDConfigurationOptionsResponse, according to the present embodiment will be described with reference to FIGS. 9A and 9B.

As described above, the OSD setting target information that can be set in the surveillance camera is performed by transmitting the GetOSDConfigurationOptions command and receiving the GetOSDConfigurationOptionsResponse operation. The operation of transmitting the GetOSDConfigurationOptions command corresponds to the step of inquiring the capabilities regarding the plurality of composition processing methods in the present invention. Further, the GetOSDConfigurationOptionsResponse in question contains capability information regarding a plurality of composition processing methods in the present invention. Further, the reception operation of the GetOSDConfigurationOptionsResponse described above corresponds to the step of receiving the response of the capability regarding the composition processing method.

FIG. 9A is a diagram illustrating a definition example of the GetOSDConfigurationOptions command. The GetOSDConfigurationOptions command is a command for the client of this embodiment to inquire of the surveillance camera about a list of setting options regarding OSD. The surveillance camera of the present embodiment returns the capability information regarding the OSD to the client device in response to the GetOSDConfigurationOptions command.

As shown in FIG. 9A, the GetOSDConfigurationOptions command can include an OSDReference type OSDReference field as a parameter. In the OSDReference field, the minOccurs="0" specifier indicates that the field is optional. In the OSDReference field, Token for which the OSD is set is specified.

The OSDReference field allows the client device to request a setting option relating only to the OSD setting target desired by the client as a response to the GetOSDConfigurationOptions command.

FIG. 9-1(b) is a diagram showing a definition example of GetOSDConfigurationOptionsResponse. As described above, the surveillance camera of the present embodiment uses the GetOSDConfigurationOptionsResponse to send the capability information regarding the OSD setting to the client.

As shown in FIG. 9-1(b), GetOSDConfigurationOptionsResponse includes an OSDConfigurationOptions field as a parameter. The field is OSDConfigurationOptions type data.

FIG. 9-1(c) shows a configuration example of the GetOSDConfigurationOptions command. FIG. 9-1(c) is a configuration example of the GetOSDConfigurationOptions command when the above-mentioned optional OSDReference field is not included.

FIG. 9-2(d) shows a configuration example of GetOSDConfigurationOptionsResponse with respect to the GetOSDConfigurationOptions command.

As shown in FIG. 9-2(d), the surveillance camera of the present embodiment notifies the client device of the OSD setting targets allowed by the surveillance camera by a plurality of OSDReference fields listed in the OSDReferenceOptions field.

In the example illustrated in FIG. 9B, the OSD setting target is VSC0 for Video Source Configuration Token. In addition, Video Source and Video Encoder Configuration Token are MJPEG0, MJPEG1, and H.264. H.264_0, H.264. 264_1 and MPEG4_0. Also, the Video Encoder and the Stream URI are “rtsp:/192.168.100.1/OSDstream/”, which is the Stream.

When the GetOSDConfigurationOptionsResponse shown in FIG. 9-2(d) is received, VSC0 is displayed as an option in the selection box 7012 in the GUI of FIG. 5-2(c), for example.

Also, in the Video Encoder Configuration Token selection box 7014, MJPEG0, MJPEG1, H.264, and so on. H.264_0, H.264. H.264_1 and MPEG4_0 are displayed as options. In addition, the Stream selection box is displayed without being grayed out, and "rtsp:/192.168.100.1/OSDstream/" is displayed as an option in the Video Encoder and Stream URI selection boxes with no serial number. It

By the display operation, the GUI of the client device is displayed as shown in FIG. 10, for example.

Further, when the GetOSDConfigurationOptionsResponse shown in FIG. 9-2(d) is received, the OSD setting target selection GUI of the client device shown in FIG. 5-2(d) operates as follows.

For example, when the Wide selection check box is selected by the user, VSC0 which is the Video Source Configuration Token is selected as the OSD setting target. When the Narrow selection check box is selected by the user, the Stream URI “rtsp:/192.168.100.1/OSDstream/” is selected as the OSD setting target.

<Other Examples>
The present invention is also realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is provided to a system or device via a network or various storage media, and the computer (or CPU, MPU, etc.) of the system or device reads the program. There is a process to execute.

1000 monitoring camera 2000 client device 2008 input unit 2014 digital interface unit 2016 interface terminal 2022 display unit 2026 CPU
2028 memory

Claims (13)

An image processing device for displaying an image output by an imaging device,
A transmission unit that transmits an acquisition request of information indicating options regarding superimposition information that the imaging device can superimpose to the image to the imaging device;
Receiving means for receiving from the image pickup device information indicating the options of the image pickup device;
Display control means for displaying a user interface for selecting a parameter relating to the superimposition information based on information indicating the option received by the receiving means,
The display control means displays the user interface in which a parameter not included in the information indicating the option among the parameters related to the superimposition information to be superimposed on an image cannot be selected
The image processing apparatus, wherein the transmitting unit transmits the parameter selected on the user interface to the image capturing apparatus. The image processing apparatus according to claim 1, wherein the display control unit displays the user interface that does not display a parameter that is not included in the information indicating the option. The image processing apparatus according to claim 1, wherein the display control unit displays the user interface in which a parameter not included in the information indicating the option is grayed out. The information indicating the option includes information for selecting a position to superimpose the superimposition information from positions on the image where the imaging device can superimpose the superimposition information on the image. The image processing apparatus according to any one of claims 1 to 3 . The image processing apparatus according to claim 4 , wherein the position on the image is UPPER_LEFT, UPPER_RIGHT, LOWER_LEFT, or LOWER_RIGHT. Information indicating the choice, the image processing apparatus according to any one of claims 1乃 optimum 5, characterized in that it comprises information indicating options for the imaging apparatus can superimpose text to the image. The image processing apparatus according to claim 6 , wherein the options include options regarding the color, size, and transparency of the text. The information indicating the option is information indicating an option for selecting the type of the superimposition information to be superimposed on the image from the types of the superimposition information that the imaging device can superimpose on the image. the image processing apparatus according to any one of claims 1乃 optimum 7, characterized in that it comprises. The image processing apparatus according to claim 8 , wherein the options include text and images as options of the type of the superimposition information. Information indicating the choice, the image processing according to any one of claims 1乃 optimum 9, characterized in that includes information indicating options for background of the imaging apparatus can superimpose text to the image apparatus. Wherein the selection, the image processing apparatus according to claim 1 0, characterized in that it comprises a choice regarding the color of the background. A method of controlling an image processing apparatus for displaying an image output by an imaging device, comprising transmitting to the imaging device an acquisition request for information indicating options regarding superimposition information that the imaging device can superimpose on the image. Transmission process,
A receiving step of receiving information indicating the options of the imaging device from the imaging device;
A display control step of displaying a user interface for selecting a parameter relating to the superimposition information based on the information indicating the option received in the receiving step,
In the display control step, among the parameters related to the superimposition information to be superimposed on the image, the user interface in which the parameters not included in the information indicating the options cannot be selected is displayed,
In the transmitting step, the parameter selected on the user interface is transmitted to the image capturing apparatus. Program for causing to function as each means of the image processing apparatus according to computer to any one of claims 1乃 optimum 1 1.

Images