JP6494721B2 - IMAGING DEVICE, IMAGE PROCESSING DEVICE, IMAGING DEVICE CONTROL METHOD, IMAGE PROCESSING DEVICE CONTROL METHOD, AND PROGRAM - Google Patents

Description

  The present invention relates to an imaging apparatus capable of transmitting a captured image to the outside, and more particularly to a technique capable of superimposing information such as an image on a captured image.

  2. Description of the Related Art Conventionally, a technique is known in which characters and images are superimposed on a predetermined position of a video and transmitted. 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.

  Recently, a technique for dynamically changing a position where information such as a character or an image 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 in accordance with the direction in which the housing is moved when the housing of the camera is moved in the pan or tilt direction. .

JP-A-7-131684

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

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

  For such a plurality of superposition methods, there is a need to select which superposition method to use depending on the user or application.

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

In order to solve the above-described problem, an imaging apparatus according to the present invention receives, from a client apparatus, an information acquisition request regarding a superposition method option for selecting a superimposition method of image superposition by an imaging device from a plurality of superposition methods. And receiving means for transmitting information related to the choice of the superposition method of the image superimposition by the imaging device when receiving the information acquisition request regarding the superposition method option of the image superposition by the imaging device. Have

In order to solve the above-described problem, an image processing apparatus according to the present invention is an image processing apparatus that displays an image output by an imaging apparatus . A transmission unit that transmits an acquisition request for information on a superimposition method option for selecting from among the imaging device, and a reception that receives information on the superimposition method option for image superposition by the imaging device from the imaging device And display control means for displaying a user interface for selecting a parameter relating to image superimposition based on information relating to options for the superimposition method of image superposition by the imaging device received by the receiving means , The transmission unit transmits the parameter selected by the user interface to the imaging device.

  According to the present invention, there is an effect that setting according to various superposition methods can be performed.

  In addition, according to the present invention, even when the imaging apparatus supports a plurality of superposition methods, there is an effect that it is possible to reduce complicated operations by the user.

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. 1 is a system configuration diagram including a monitoring camera and a client device of an embodiment. It is a sequence chart figure which shows the command transaction of a present Example. It is a figure which shows OSD setting GUI of the client apparatus of a present Example. It is a figure which shows 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 a definition of the OSDConfiguration type of a present Example. It is a figure which shows the example of a definition of the OSDConfiguration type of a present Example. It is a figure which shows the example of a definition of the OSDConfigurationOptions type of a present Example. It is a figure which shows the example of a definition of the OSDConfigurationOptions type of a present Example. It is a figure which shows the structure of a GetOSDConfigurationOptions command and a response of a present Example. It is a figure which shows the structure of a GetOSDConfigurationOptions command and a response of a present Example. It is a figure which shows 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 the present embodiment.

  In FIG. 1, reference numeral 1001 denotes an imaging optical system, 1003 denotes an imaging device, 1005 denotes an image processing circuit, 1007 denotes a first synthesis circuit, 1009 denotes a pixel number conversion circuit, and 1011 denotes a pixel number conversion memory. Reference numeral 1013 denotes a second synthesis circuit, 1015 denotes an encoding circuit (compression encoding processing circuit), 1017 denotes an encoding memory, 1019 denotes a communication circuit (hereinafter referred to as IF circuit), 1021 denotes a communication buffer, and 1023 denotes communication. Port. Further, 1025 is an OSD circuit, 1027 is a central processing circuit (hereinafter referred to as CPU), 1029 is an electrically erasable nonvolatile memory (hereinafter referred to as EEPROM), 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.

  Light rays from the subject to be imaged enter the image sensor 1003 via the imaging optical system 1001 and are photoelectrically converted. The image sensor 1003 in this embodiment is configured by a CCD, a CMOS, or the like. The image sensor 1003 in this 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, an I / F circuit 1019 receives an OSD setting command from a client device to be described later. The OSD setting command is analyzed by the CPU 1027, and OSD setting information is input to the OSD circuit 1025. The OSD circuit 1025 generates an OSD according to the input OSD setting information.

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

  The encoding setting information includes, for example, designation information related to the image size or image resolution. When the image size of the image output from the image sensor 1003 is different from the designated image size, the pixel number conversion circuit 1009 performs an enlargement process or a reduction process of the image and the like. Generate an image. When the image is enlarged or reduced, pixel interpolation processing is also performed.

  By operating as described above, in the surveillance camera of the present embodiment, it is possible to transmit image streams of different image sizes in the same scene and with the same encoding method almost simultaneously. That is, images of the same scene and different image sizes generated by the pixel number conversion circuit 1009 are input to the encoding circuit 1015 in a time division manner, and are output after being subjected to the same encoding method. 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 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, 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 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, for example, a pointing device such as a keyboard and a mouse is used. 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 user operations on the input unit 2008. An intermediate result of calculation 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 this embodiment, the operation of the external client described above is realized by the above operation.

  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, and 1102 is a tilt direction, and 1103 is a zoom mechanism.

  FIG. 3B is a system configuration diagram including the monitoring 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 such as imaging parameter change, pan head drive, and video streaming start described later to the monitoring camera 1000. The monitoring camera 1000 transmits responses to these commands and video streaming to the client device 2000.

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

  In FIG. 3C, reference numeral 1200 denotes another monitoring camera according to the present embodiment, and the monitoring camera 1200 and the client device 2000 are connected to each other through an IP network 1500 so that they can communicate with each other. The client device 2000 transmits various commands such as imaging parameter change (described later) and video streaming start to the monitoring camera 1200. The monitoring camera 1200 transmits a response to these commands and video streaming to the client device 2000.

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

  FIG. 4 is a sequence chart showing a command transaction between the monitoring camera 1000 and the client device 2000.

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

  In FIG. 4A, reference numeral 7100 denotes a transaction of the GetVideoSourceConfigurations command. With this command, the client apparatus 2000 acquires a list of VideoSourceConfigurations held by the monitoring camera 1000.

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

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

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

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

  With each command, the client device can 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 distribution stream based on the specified MediaProfile setting.

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

  Reference numeral 7109 denotes a setup command transaction. 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.

  Reference numeral 7110 denotes 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.

  Reference numeral 7111 denotes a distribution stream. The monitoring camera 1000 distributes the stream requested to start in 7110 by the transmission method shared in 7109.

  Reference numeral 7112 denotes a Teardown command transaction. 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 this embodiment will be described.

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

  In FIG. 4B, reference numeral 7200 denotes a GetOSDs command transaction. The GetOSDs command is a command for the client device 2000 to instruct the monitoring camera 1000 to return all OSDConfigurations 6105 associated with the specified OSDReference.

  Reference numeral 7201 denotes a CreateOSD command transaction. The CreateOSD command is a command for the client device 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 OSDToken, which is the ID of the generated OSD, to the client apparatus 2000.

  7202 is a transaction of GetOSDConfigurationOptions.

  The GetOSDConfigurationOptions command is a command for instructing the client device 2000 to return the selection range or option of each parameter of OSDConfiguration to the monitoring camera 1000. Note that the selection range or options of each parameter of OSDConfiguration can be set by a SetOSD command to be described later.

  The client apparatus according to 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 composite processing capabilities of the image processing apparatus of the present invention. Further, the GetOSDConfigurationOptions response reception performed by the client device of the present embodiment corresponds to a step of receiving a response of capability relating 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 device 2000 to instruct the monitoring camera 1000 to return an OSDConfiguration having a specified OSDToken.

  Reference numeral 7204 denotes a SetOSD transaction. The SetOSD command is a command for the client device 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 the OSDConfiguration having the OSDToken specified by the client apparatus 2000. With this operation, the client apparatus 2000 can instruct the monitoring camera 1000 to display a new OSD, and to change the color, size, position, etc. of the OSD being displayed.

  The transmission operation of 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 device 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 specified by the client device 2000 from the storage unit of the monitoring camera.

  Next, an OSD setting graphical user interface (hereinafter sometimes referred to as GUI) of the client apparatus according to the present embodiment will be described with reference to FIGS.

  5A and 5B are diagrams illustrating the configuration of the GUI.

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

  In the client device of this embodiment, the user can set OSD display settings for the connected surveillance camera 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 images that can be received by the client of this embodiment can be displayed, and the images are displayed in a reduced size.

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

  In the OSD setting GUI, the user selects the OSD setting window 6802 after selecting one of the first stream display window 6804 to the fourth stream display window 6810, so that the user can set the OSD setting for a desired video. It can be carried out.

  FIG. 5B 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. Reference numeral 7003 denotes a text setting frame, and 7004 denotes an image setting frame. Reference numeral 7005 denotes an OSD creation button, 7006 denotes an OSD update button, 7007 denotes an OSD delete button, and 7010 denotes 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, and SnapshotURI.

  The VideoSource Configuration operates as an image source of the present invention. The Video Encoder Configuration operates as an encoder according to the present invention.

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

  The StreamURI and the SnapshotURI also operate as one piece of stream specifying 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, by setting the OSD only for the image stream having the administrator authority, the OSD can be observed only by the client apparatus operating with the administrator authority. With this operation, in the present invention, it is possible to set the OSD without disclosing information effective only for a user having a certain authority, such as debug information, to a user who does not need the information.

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

  In this embodiment, the transmission timing of the GetOSDConfigurationOptions command is set 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. It may also be transmitted when the client device of this embodiment is activated.

  Furthermore, a 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 GetOSDConfigurationOptions command may be transmitted at a 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 is obtained, which is convenient.

  In the GetOSDConfigurationOptionsResponse, references that can set the OSD are listed for the monitoring camera according to the present embodiment. The reference list is data of the OSDReferenceOptions type. The OSDReferenceOptions type data includes the OSD setting target information.

  The operation of transmitting the GetOSDConfigurationOptions command corresponds to the step of inquiring about the ability regarding a plurality of composition processing methods in the present invention. Further, the GetOSDConfigurationOptionsResponse includes capability information related to a plurality of synthesis processing methods in the present invention. In addition, the reception operation of the above-described GetOSDConfigurationOptionsResponse corresponds to a step of receiving a response of capability related to the synthesis processing method.

  The client device according to the present embodiment displays only options transmitted from the monitoring camera as the OSD setting target. As shown in FIG. 5B, only the Video Source Configuration, Video Encoder Configuration, Media Profile, and Stream URI transmitted by the surveillance camera are displayed as options. In this embodiment, a reference selection box 7010 is displayed in the vicinity of the selected OSD setting target check box. A reference selection box 7010 is a selection box for selecting an individual target on which OSD settings are actually made among the selected OSD setting targets. In FIG. 5B, Video Source Configuration is selected. Accordingly, in the reference selection box 7010 of FIG. 5B, the Video Source Configuration Tokens that the surveillance camera has are listed.

  As described above, when the video source configuration is selected, the video source configuration token is listed in the reference selection box 7010. In addition, when Video Encoder Configuration is selected, Video Encoder Configuration Token is listed. In addition, when Media Profile is selected, Media Profile Token is listed.

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

  The client display operation described above includes the step of analyzing the response of the capability related to the composition processing method of the present invention. Further, the operation in which the user selects from the displayed options includes a step of selecting one or a plurality of synthesis processing methods from the plurality of synthesis processing methods of the present invention.

  The OSD type setting frame 7001 is a part for selecting the type of OSD to be overlaid, that is, OSDType. In FIG. 5B, since TEXT is selected, for example, the detailed setting of the text setting frame 7003 is valid. The image setting frame 7004 is invalidated and cannot be set by the user.

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

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

  For example, the user can designate 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, it is possible to simultaneously designate the display target video for displaying the OSD and the display coordinates on the video.

  As described above, the text setting frame 7003 is a part for setting detailed data when TEXT is selected in the OSD type setting frame. As the 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 specified by a 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 an image file to be displayed as an 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 monitoring camera, and then uses the returned OSDToken to send the SetOSD command to the monitoring camera according to the contents input by the user on the screen of this figure. Run.

  In addition, when the OSD update button 7006 is pressed, the client apparatus 2000 executes a SetOSD command to the monitoring camera 1000 according to the contents 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 apparatus 2000 executes a DeleteOSD command to the monitoring camera 1000 using the OSDToken stored in advance.

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

  As described above, in the client device of the above-described embodiment, the OSD setting target selection frame 7000 displays only OSD setting targets that can be set in the monitoring camera to be controlled. However, in the present invention, among the OSD setting objects displayed in the OSD setting object selection frame 7000, only the OSD setting object that can be set in the monitoring camera may be set on the client. In this case, for the OSD setting target that cannot be set in the monitoring camera, for example, items that cannot be set are grayed out, indicating that the user cannot set them.

  Hereinafter, the above operation will be described with reference to FIG.

  In FIG. 5-2 (c), the same reference numerals as 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), the video source configuration and the video encoder configuration are transmitted from the target monitoring camera as a reference capable of setting the OSD.

  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 this embodiment, as illustrated in FIG. 5-2 (c), Media Profile and Stream are not specified as a reference that can set the OSD, and thus are grayed out and cannot be set. Is displayed.

  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 monitoring camera to be controlled. In this case, the OSD setting target selection frame 7000 may not be displayed in the OSD setting GUI of the client device.

  The OSD setting target information that can be set in the monitoring camera is performed by transmitting the GetOSDConfigurationOptions command and receiving the GetOSDConfigurationOptionsResponse. The operation of transmitting the GetOSDConfigurationOptions command corresponds to the step of inquiring about the ability regarding a plurality of composition processing methods in the present invention. Further, the GetOSDConfigurationOptionsResponse includes capability information related to a plurality of synthesis processing methods in the present invention. In addition, the reception operation of the above-described GetOSDConfigurationOptionsResponse corresponds to a step of receiving a response of capability related to the synthesis processing method.

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

  For example, when the OSD is set for the video source, the OSD is set for the video source, so the OSD is displayed for all the videos to be distributed.

  Further, for example, when the OSD is set in the Video Encoder, the OSD is set only in the selected encoded video. For example, the encoding scheme to be set for OSD is H.264. When H.264 video is selected, H.264 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 monitoring camera in the order of Video Source, Video Encoder, Media Profile, Stream, or Snapshot. Then, it operates to select a matching setting target.

  For example, when the surveillance camera of the present embodiment has Video Source, Video Encoder, and Stream as targets that can be set for OSD, the client device of the present embodiment automatically selects the video source and performs OSD Set up. For example, when the surveillance camera has the Video Encoder and the Stream as OSD setting targets that can be set, the client device automatically selects the Video Encoder and performs the OSD setting.

  In addition, when the monitoring camera has a plurality of setting target subtypes in the same setting target category, the client apparatus according to the present embodiment selects the setting target subtype so that the range of influence is maximized. . For example, if the surveillance camera has a Video Encoder as an OSD setting target and supports a plurality of encoding methods, for example, the encoding method that outputs the most video streams is the OSD setting target. Automatically select as subtype. For example, in the above case, the surveillance camera has two MJPEG streams, H.264, and H.264. When four H.264 streams are distributed, the client apparatus according to the present embodiment is H.264. H.264 is automatically selected as the sub-type of the OSD setting target.

  In the above-described embodiment, the client device is configured to automatically select the OSD setting target so that it is displayed in a larger number of stream videos, but is displayed in a smaller number of stream videos. 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 monitoring camera in the order of Stream or Snapshot, Media Profile, Video Encoder, and Video Source. Then, it operates to select a matching setting target.

  For example, it is assumed that the surveillance camera of the present embodiment has Video Source, Video Encoder, and Stream as targets that can be set for OSD. In that case, the client device that automatically selects the stream image to be displayed in a smaller number of stream images operates to automatically select the Stream and perform the OSD setting.

  In addition, the client device according to the present exemplary embodiment provides a selection box on the OSD setting GUI for selecting whether the influence range of the OSD setting is to be wide or narrow. May be configured to be automatically selected. In this case, when the user makes a selection in a wide range, as described above, the client device selects the OSD setting target so that it is displayed in more stream images. In addition, when the user makes a selection within a narrow range, as described above, the OSD setting target is automatically selected so as to be displayed in a smaller stream video.

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

  An example of the OSD setting GUI configuration of the client apparatus described above is shown in FIG.

  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. Either the Wide selection check box or the Narrow selection check box is configured to be selectable by the user. In addition, the check box selected by the user displays an instruction indicating that it is selected. For example, in FIG. 5D, an instruction is displayed indicating that the Wide selection check box is selected.

  As illustrated in FIG. 5D, when the user selects the Wide selection check box, the client apparatus according to the present exemplary embodiment displays in more stream images from the setting target information transmitted by the monitoring camera. As described above, the OSD setting target is selected. In addition, when the user selects the “Narrow” selection check box, the client apparatus according to the present exemplary embodiment sets the OSD setting target so that it is displayed in fewer stream images from the setting target information transmitted by the monitoring camera. select.

  When the OSD creation button 7005 is pressed, the client apparatus 2000 issues a CreateOSD command to the monitoring camera 1000. Subsequently, using the returned OSDToken, a SetOSD command is executed on the monitoring camera 1000 in accordance with the contents input by the user on the screen of FIG.

  In addition, when the OSD update button 7006 is pressed, the client apparatus 2000 executes a SetOSD command to the monitoring camera 1000 according to the contents 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 apparatus 2000 executes a DeleteOSD command to the monitoring camera 1000 using the OSDToken stored in advance.

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

  Hereinafter, the OSD setting target selection processing of the client apparatus in the present embodiment will be described with reference to FIG.

  FIG. 6A is a flowchart illustrating a GUI display process for selecting an OSD setting target in the client device according to the present embodiment. The client device user of this embodiment selects an 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, a GetOSDConfigurationOptions command is transmitted from the client device of this embodiment. In the next step S8006, GetOSDConfigurationOptionsResponse is transmitted from the monitoring camera of the present embodiment, and the client apparatus receives the response.

  The operation of transmitting the GetOSDConfigurationOptions command corresponds to the step of inquiring about the ability regarding a plurality of composition processing methods in the present invention. Further, the GetOSDConfigurationOptionsResponse includes capability information related to a plurality of synthesis processing methods in the present invention. In addition, the reception operation of the above-described GetOSDConfigurationOptionsResponse corresponds to a step of receiving a response of capability related to the synthesis processing method.

  In the next step S8008, the received GetOSDConfigurationOptionsResponse is analyzed by the client device of this embodiment. The analysis operation of the received GetOSDConfigurationOptionsResponse includes a step of analyzing a response of capability related to the composition processing method of the present invention. Note that OSD setting target selection frame display processing is performed based on 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 regarding the video source configuration. If it is determined in step S8010 that the GetOSDConfigurationOptionsResponse includes an option related to the video source configuration, the control moves to step S8012. In step S8012, a display process related to Video Source Configuration is performed, and the GUI is updated.

  In a succeeding step S8014, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option related to the Video Encoder Configuration. If it is determined in step S8014 that GetOSDConfigurationOptionsResponse includes an option related to Video Encoder Configuration, control proceeds to step S8016. In step S <b> 8016, display processing related to Video Encoder Configuration is performed, and the GUI is updated.

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

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

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

  In the next step S8030, the OSD setting target selection frame display process of this embodiment is completed.

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

  In addition, when the OSD update button 7006 is pressed, the client apparatus 2000 executes a SetOSD command to the monitoring camera 1000 according to the contents 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 apparatus 2000 executes a DeleteOSD command to the monitoring camera 1000 using the OSDToken stored in advance.

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

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

  In FIG. 6B, in step S8102, the OSD setting target automatic selection process of this embodiment is started. In the next step S8104, a GetOSDConfigurationOptions command is transmitted from the client device of this embodiment. In the next step S8106, GetOSDConfigurationOptionsResponse is transmitted from the monitoring camera of the present embodiment, and the client apparatus receives the 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, the control shifts to step S8110. If the Narrow selection check box is selected, the control moves to step S8130.

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

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

  If the received GetOSDConfigurationOptionsResponse does not include an option related to Video Source Configuration in step S8110, the control moves to step S8114.

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

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

  If it is determined in step S8114 that GetOSDConfigurationOptionsResponse does not include an option related 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 related to the Media Profile.

  If it is determined in step S8118 that the GetOSDConfigurationOptionsResponse includes an option related to the Media Profile, the control moves to step S8120. In step S8120, processing for 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 an option related to the Media Profile, the control moves to step S8122.

  In a succeeding step S8122, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option related to the Stream URI.

  If it is determined in step S8122 that GetOSDConfigurationOptionsResponse includes an option related to the Stream URI, control proceeds to step S8124. In step S8124, the OSD setting target is set to the Stream URI, and the GUI is updated.

  In a succeeding step S8126, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option relating to the Snapshot URI.

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

  If it is determined in step S8126 that the GetOSDConfigurationOptionsResponse includes an option related to the snapshot URI, control proceeds to step S8128. In step S8128, processing for 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 an option related to the snapshot URI, in the next step S8160, the OSD setting target automatic selection process of the present example ends.

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

  In step S8130, as in step S8126, it is determined whether the received GetOSDConfigurationOptionsResponse includes an option related to the Snapshot URI.

  If it is determined in step S8130 that the GetOSDConfigurationOptionsResponse includes an option related to the snapshot URI, control proceeds to step S8132. In step S8132, processing for setting the OSD setting target to the Snapshot URI is performed, and the GUI is updated.

  If it is determined in step S8130 that GetOSDConfigurationOptionsResponse does not include an option related to the snapshot URI, control proceeds to step S8134.

  In a succeeding step S8134, it is determined whether or not the received GetOSDConfigurationOptionsResponse includes an option related to the Stream URI.

  If it is determined in step S8134 that GetOSDConfigurationOptionsResponse includes an option related to the Stream URI, control proceeds to step S8136. In step S8136, the OSD setting target is set to the Stream URI, and the GUI is updated.

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

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

  If it is determined in step S8138 that the GetOSDConfigurationOptionsResponse includes an option related to the Media Profile, the control moves to step S8140. In step S 8140, a process for 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 an option related to the Media Profile, the control moves to step S8142.

  In step S8142, it is determined whether the received GetOSDConfigurationOptionsResponse includes an option related to Video Encoder Configuration.

  If it is determined in step S8142 that the option related to Video Encoder Configuration is included in GetOSDConfigurationOptionsResponse, control proceeds to step S8144. In step S8144, processing for setting the OSD setting target to Video Encoder Configuration is performed, and the GUI is updated.

  If it is determined in step S8142 that GetOSDConfigurationOptionsResponse does not include an option related to 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 related to the video source configuration.

  If it is determined in step S8146 that the GetOSDConfigurationOptionsResponse includes an option related to the video source configuration, the control moves to step S8148. In step S8148, processing for 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 monitoring camera. Subsequently, using the returned OSDToken, a SetOSD command is executed on the surveillance camera according to the content input by the user on the screen of this figure.

  In addition, when the OSD update button 7006 is pressed, the client apparatus 2000 executes a SetOSD command to the monitoring camera 1000 according to the contents 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 apparatus 2000 executes a DeleteOSD command to the monitoring camera 1000 using the OSDToken stored in advance.

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

  FIG. 7A and FIG. 7B are diagrams for explaining the configuration of the OSDConfiguration that is a data type according to the present embodiment.

  The data types shown in FIGS. 7A and 7B 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 a definition example of the OSDConfiguration type.

  As shown in FIG. 7-1 (a), the OSDConfiguration type is defined as a complex type by the XML complexType declaration. In addition, the OSDConfiguration type is an extended type obtained by extending the DeviceEntity type by the complexContent element, the extension element, and its base attribute. Further, in the OSDConfiguration type, the sequence element indicates that data expansion in which the order appears as defined is performed.

  Further, 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. 7B is a diagram illustrating a definition example of the OSDReference type.

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

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

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

  FIG. 7C is a diagram illustrating a definition example of the OSDType type.

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

  FIG. 7A is a diagram illustrating 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. In addition, the sequence element indicates that the data type appears in the order as defined.

  FIG. 7B is a diagram illustrating a definition example 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. In addition, the sequence element indicates that the data type appears in the order as defined.

  FIG. 7B is a diagram illustrating the OSDIimageConfiguration type. In the definition example of the OSDIimageConfiguration type, the complexType element indicates that the type is defined as a complex type. In addition, the sequence element indicates that the data type appears in the order as defined.

  FIG. 7B is a diagram illustrating a definition example of the Vector type. The Vector type has a configuration in which a float type attribute x and y can be described by an attribute element.

  FIG. 7B is a diagram illustrating a definition example of the Color type. The color type has a configuration in which the float type attributes X, Y, and Z can be described by the attribute element. Further, the attributes X, Y, and Z indicate that they are indispensable configurations in the Color type by specifying use = “required”. In addition, the color type has a configuration in which an any URI type attribute ColorSpace can be described by an attribute element.

  FIG. 7-2 (i) is a diagram illustrating a definition example of BackgroundColor type. In the BackgroundColor type, the complexType element indicates that the type is defined as a complex type. In addition, the sequence element indicates that the data type appears in the order as defined. The sequence element has a configuration in which color-type data can be described as an element. In addition, the type has a configuration in which an int type attribute Transparent can be described.

  The client apparatus of the present invention acquires OSD setting information from the imaging apparatus of the present embodiment using the above-described OSDConfiguration type data. In addition, the client device of the present invention is configured to perform OSD setting on the imaging device of the present embodiment using the OSDConfiguration type data.

  Next, a definition example of the OSDConfigurationOptions type will be described with reference to FIGS. 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. In addition, the sequence element indicates that the data type appears in the order as defined.

  The OSDConfigurationOptions type is, for example, a data type used for the GetOSDConfigurationOptions response in FIG. 4B. With the GetOSDConfigurationOptions response, the client apparatus according to the present exemplary embodiment acquires information on the capability related to 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 an OSDType type. The next field is a string-type PositionOption. The next field is a TextOption of type OSDTextOptions. The last field is an ImageOption of the OSDIImageOptions type.

  The OSDReferenceOptions type is a data type that is used in order to transfer capabilities related to an OSD setting target in this embodiment.

  A plurality of fields of Type and PositionOption can be present in the OSDConfigurationOptions type by the maxOccurs = “unbounded” specifier. Further, each field of OSDReferenceOptions, TextOption, and ImageOption can be omitted by a minOccurs = "0" specifier.

  FIG. 8B is a diagram illustrating a definition example of the OSDReferenceOptions type. The OSDReferenceOptions type is a data type used for the 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. In addition, the sequence element indicates that the data type appears in the order as defined. In the OSDReferenceOptions type, the first field is an OSDReference type OSDReference. The maxOccurs = “unbounded” specifier indicates that a plurality of such fields can exist inside the OSDReference type.

  The OSDReferenceType 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, the OSDReference type indicates a configuration in which one of the choice elements is selected by the choice element. For example, in the OSDReference type data, only one ReferenceToken type data or any URI type data appears in the type.

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

  In the present embodiment, a StreamURI or a SnapshotURI can be specified as the anyURI type.

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

  Also, as described above, since the OSDReferenceOptions type can store a plurality of OSDReferenceType data, the OSDConfigurationOptions type can list a plurality of OSD setting targets.

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

  FIG. 8C is a diagram illustrating a definition example of the OSDTextOptions type. In the OSDTextOptions type, the complexType element indicates that the type is defined as a complex type. In addition, the sequence element indicates that the data type appears in the order as defined.

  In the OSDTextOptions type, the first field is an OSDType type field. The next field is the IntRange type FontSizeRange 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.

  A plurality of the Type field, the DateFormat field, and the TimeFormat field can be present in the OSDTextOptions type by the maxOccurs = “unbounded” specifier.

  In addition, the DateFormat field, the TimeFormat field, the Color field, and the transparent field can be omitted by a minOccurs = "0" specifier.

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

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

  FIG. 8B is a diagram illustrating a definition example of the IntRange type. In the IntRange type, the complexType element indicates that the type is defined as a complex type. In addition, the sequence element indicates that the data type appears in the order 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. 8B is a diagram illustrating a definition example of the ColorOptions type. In the ColorOptions type, the complexType element indicates that the type is defined as a complex type. In addition, the sequence element indicates that the data type appears in the order as defined. Further, it is indicated that one of the choice elements is selected by the choice element inside the sequence element. 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 a ColorList field of Color type. Another option is a ColospaceRange type ColospaceRange field. A plurality of the ColorList field and the ColospaceRange field can be indicated by a maxOccurs = “unbounded” specifier.

  FIG. 8-2 (g) is a diagram illustrating a definition example of the ColospaceRange type. In the ColospaceRange type, the complexType element indicates that the type is defined as a complex type. In addition, the sequence element indicates that the data type appears in the order 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 Float Range type data. The last field of the ColospaceRange type is an anyURI type Colorspace field.

  FIG. 8B is a diagram illustrating 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. In addition, the sequence element indicates that the data type appears in the order 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 the OSD information that can be set in the imaging device of the present embodiment from the imaging device using the OSDConfigurationOptions type data. In the imaging apparatus of the present embodiment, the OSDConfigurationOptions type data is used for transmitting capability information related to OSD in the imaging apparatus.

  Next, the GetOSDConfigurationOptions command according to the present embodiment and the GetOSDConfigurationOptionsResponse that is a response will be described with reference to FIGS.

  As described above, the OSD setting target information that can be set in the monitoring camera is performed by the transmission of the GetOSDConfigurationOptions command and the GetOSDConfigurationOptionsResponse reception operation. The operation of transmitting the GetOSDConfigurationOptions command corresponds to the step of inquiring about the ability regarding a plurality of composition processing methods in the present invention. Further, the GetOSDConfigurationOptionsResponse includes capability information related to a plurality of synthesis processing methods in the present invention. In addition, the reception operation of the above-described GetOSDConfigurationOptionsResponse corresponds to a step of receiving a response of capability related to the synthesis 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 a list of setting options related to the OSD from the monitoring camera. In response to the GetOSDConfigurationOptions command, the monitoring camera according to the present embodiment returns capability information related to the OSD to the client device.

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

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

  FIG. 9A is a diagram illustrating a definition example of GetOSDConfigurationOptionsResponse. As described above, the monitoring camera according to the present embodiment transmits the capability information related to the OSD setting to the client using the GetOSDConfigurationOptionsResponse.

  As illustrated in FIG. 9-1 (b), GetOSDConfigurationOptionsResponse includes an OSDConfigurationOptions field as a parameter. This 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 optional OSDReference field described above is not included.

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

  As illustrated in FIG. 9-2 (d), the monitoring camera according to the present embodiment notifies the client device of the OSD setting target permitted by the monitoring camera through the plurality of OSDReference fields listed in the OSDReferenceOptions field.

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

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

  Also, the Video Encoder Configuration Token selection box 7014 includes MJPEG0, MJPEG1, H.264, and the like. 264_0, H.264. H.264_1 and MPEG4_0 are displayed as options. Also, 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 without suffixes. The

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

  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 that is a Video Source Configuration Token is selected as an OSD setting target. In addition, 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 can also be 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 apparatus via a network or various storage media, and the computer (or CPU, MPU, etc.) of the system or apparatus reads the program. Process to be executed.

1000 Monitoring Camera 2000 Client Device 2008 Input Unit 2014 Digital Interface Unit 2016 Interface Terminal 2022 Display Unit 2026 CPU
2028 memory

Claims (16)

Receiving means for receiving from the client device an acquisition request for information related to a superposition method option for selecting a superposition method for image superposition by the imaging device from a plurality of superposition methods ;
A transmission unit configured to transmit information related to the selection method of the superimposition method of the image superimposition by the imaging device when receiving the information acquisition request regarding the superposition method option of the image superimposition by the imaging device; An imaging device.   The imaging apparatus according to claim 1, further comprising: an imaging unit; and a superimposing unit that superimposes superimposition information on a captured image captured by the imaging unit.   The imaging apparatus according to claim 2, wherein the superimposition information superimposed by the superimposing unit includes at least one of text or an image. An image processing device that displays an image output by an imaging device,
A transmission means for transmitting an acquisition request for information on a choice of a superposition method for selecting a superposition method of image superposition by the image pickup device from a plurality of superposition methods ;
Receiving means for receiving, from the imaging device, information relating to the choice of the superimposing method of image superposition by the imaging device;
Display control means for displaying a user interface for selecting a parameter relating to image superimposition based on information relating to the choice of the superposition method of image superposition by the imaging device received by the receiving means;
Have
The image processing apparatus , wherein the transmission unit transmits the parameter selected by the user interface to the imaging apparatus. Parameters for the previous SL image superimposing an image processing apparatus according to claim 4, superimposition information to be superimposed by the imaging apparatus is characterized in that it comprises whether the image is text. The image processing apparatus according to claim 4, wherein the parameter related to the image superimposition includes a position where superimposition information is superimposed by the imaging apparatus. An image pickup apparatus control method comprising an image pickup means,
A receiving step of receiving from the client device an acquisition request for information on a superposition method option for selecting a superposition method of image superposition by an imaging device from a plurality of superposition methods ;
A transmission step of transmitting, when receiving an acquisition request for information on the superimposition method options for image superimposition by the imaging device in the reception step, transmitting information on the superposition method options for image superimposition by the imaging device. Control method.   The control method according to claim 7, further comprising a superimposition step of superimposing superimposition information on a captured image captured by the imaging unit. The control method according to claim 7, wherein the superimposition information to be superimposed in the image superposition includes at least one of text or an image. An image processing device control method for displaying an image output by an imaging device,
A first transmission step of transmitting, to the imaging device, an acquisition request for information relating to a superposition method option for selecting a superposition method of image superposition by the imaging device from a plurality of superposition methods ;
A reception step of receiving, from the imaging device, information relating to options of the superposition method of image superposition by the imaging device;
A display control step of displaying a user interface for selecting a parameter related to image superimposition based on the information regarding the choice of the superimposition method of the image superposition by the imaging device received in the reception step;
And a second transmission step of transmitting the parameter selected by the user interface to the imaging device. Parameters for the previous SL image superimposing control method according to claim 10, superimposition information to be superimposed by the imaging apparatus is characterized in that it comprises whether the image is text.   The control method according to claim 10, wherein the parameter related to the image superimposition includes a position where superimposition information is superimposed by the imaging device. On the computer,
A receiving step of receiving from the client device an acquisition request for information on a superposition method option for selecting a superposition method of image superposition by an imaging device from a plurality of superposition methods ;
Upon receiving a request for information about the choices of the method of superimposing an image superimposed by the image pickup apparatus in said receiving step, for executing a transmission step of transmitting information about the choice of the method of superimposing an image superimposed by the imaging device program. On the computer,
A first transmission step of transmitting, to the imaging device, an acquisition request for information relating to a superposition method option for selecting a superposition method of image superposition by an imaging device from a plurality of superposition methods ;
A reception step of receiving, from the imaging device, information relating to options of the superposition method of image superposition by the imaging device;
A display control step of displaying a user interface for selecting a parameter related to image superimposition based on the information regarding the choice of the superimposition method of the image superposition by the imaging device received in the reception step;
A second transmission step of transmitting the parameter selected by the user interface to the imaging apparatus. Parameters for the previous SL image superimposing a program according to claim 14, superimposition information to be superimposed by the imaging apparatus is characterized in that it comprises whether the image is text.   The program according to claim 14, wherein the parameter related to the image superimposition includes a position where superimposition information is superimposed by the imaging device.

Images