WO2020129434A1 - 画像ファイル生成装置、画像ファイル生成方法、及びプログラム - Google Patents

画像ファイル生成装置、画像ファイル生成方法、及びプログラム Download PDF

Info

Publication number
WO2020129434A1
WO2020129434A1 PCT/JP2019/043118 JP2019043118W WO2020129434A1 WO 2020129434 A1 WO2020129434 A1 WO 2020129434A1 JP 2019043118 W JP2019043118 W JP 2019043118W WO 2020129434 A1 WO2020129434 A1 WO 2020129434A1
Authority
WO
WIPO (PCT)
Prior art keywords
metadata
image file
image
item
stored
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2019/043118
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
昌敬 深田
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Canon Inc
Original Assignee
Canon Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Canon Inc filed Critical Canon Inc
Publication of WO2020129434A1 publication Critical patent/WO2020129434A1/ja
Priority to US17/345,004 priority Critical patent/US20210303616A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
    • G06F16/58—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/583—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using metadata automatically derived from the content
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/164—File meta data generation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
    • G06F16/51—Indexing; Data structures therefor; Storage structures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
    • G06F16/55—Clustering; Classification
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
    • G06F16/58—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/583—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using metadata automatically derived from the content
    • G06F16/5846—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using metadata automatically derived from the content using extracted text
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
    • G06F16/58—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/5866—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using information manually generated, e.g. tags, keywords, comments, manually generated location and time information

Definitions

  • the present invention relates to a technique for storing one or more image data in an image file.
  • MPEG Moving Pictures Experts Group
  • HEIF High Efficiency Image File Format
  • ISO base media file format ISO Base Media File Format
  • HEIF is being standardized under the name "Image File Format" in ISO/IEC 23008-12.
  • HEIF also defines a normative structure including metadata, a method of associating metadata with an image, and a configuration of metadata of a specific format.
  • Patent Document 1 describes that a derivative image is stored in an image file conforming to HEIF.
  • image generation apparatuses with image generation functions such as cameras and smartphones have various functions in recent years, and not only shooting date and time, image size and image quality, but also information at the time of shooting and image data taken. It is possible to generate various information such as metadata of. For example, various information associated with the image data such as shooting position information, what the subject or scene of the image data is, and an image pickup mode at the time of shooting is generated together with the image data. Information about such image data can be stored in the HEIF file as metadata.
  • an image file for example, HEIF file
  • an image file for example, HEIF file
  • the metadata is stored for each image. Therefore, the device that processes the HEIF file cannot confirm that the metadata of each image is common unless the metadata of each image and its configuration information are sequentially confirmed. Therefore, when a plurality of images in the HEIF file all correspond to common metadata, or when two or more of the plurality of images correspond to common metadata, batch processing is performed on each image. The processing load when performing was large.
  • each tile image is stored as a derived image
  • metadata such as Exif data for each derived image is inefficient in terms of file generation load and file size. ..
  • Exif is an abbreviation for Exchangeable image file format. That is, although the metadata of each tile image (for example, image size, color information, encoding information, etc.) is often common, conventionally, the metadata is defined for each of a plurality of (derived) images. It was not efficient.
  • the information when constructing the metadata adapted (corresponding) to the image only the information as to whether or not the metadata is essential can be stored. That is, in the case of adapting a plurality of metadata to one image, it was not possible to select any one from the same kind of metadata and adapt it.
  • the text information for each language can be selectively applied to the image. ..
  • HTML Long desc information for acquiring information from other URIs is stored and multilingual is supported.
  • the information corresponding to each language is stored in the file. Need to be kept. At that time, it was not possible to select any one of the text information in a plurality of languages and adapt it to the image.
  • the present disclosure provides a technique for efficiently performing a process related to image file generation.
  • the image file generation device of the present invention has the following configuration. That is, an image file generation device for storing one or more images in an image file according to a predetermined image file format, and an acquisition unit for acquiring a plurality of metadata to be stored in the image file; Among the metadata, the grouping means for grouping according to the type of metadata, and the storage means for storing the grouped metadata in the image file.
  • the accompanying drawings are included in and constitute a part of the specification, illustrate the embodiments of the present invention, and are used together with the description to explain the principle of the present invention.
  • the figure which shows an example of the ItemPropertyAssociationBox structure in the image file format in embodiment The figure which shows another example of the ItemPropertyAssociationBox structure in the image file format in embodiment.
  • the figure which shows an example of the ItemPropertyBox structure in the image file format in embodiment The figure which shows an example of ItemReferenceBox in the image file format in embodiment.
  • the figure which shows another example of the ItemPropertyAssociation structure in the image file format in embodiment The figure which shows an example of the ItemPropertyToGroupPropertyBox structure in the image file format in embodiment.
  • the figure which shows the processing flow of the image file generation apparatus in 3rd Embodiment The figure which shows the processing flow of the image file generation apparatus in 3rd Embodiment.
  • the figure which shows an example of ItemPropertyBox in the image file format in 3rd Embodiment The figure which shows another example of ItemPropertyBox in the image file format in 3rd Embodiment.
  • FIG. 1 shows the configuration of an image file generation device 101 of this embodiment.
  • the image file generation device 101 of FIG. 1 is a communication device having a photographing function such as a camera, a smartphone, a tablet PC, or the like.
  • the image file generation device 101 of this embodiment generates an image file conforming to a predetermined image file format.
  • the image file generation device 101 has a system bus 102, and has a nonvolatile memory 103, a ROM 104, a RAM 105, a control unit 106, an imaging unit 107, and an operation unit 108.
  • the image file generation device 101 further includes a file output unit 109, a metadata processing unit 110, an encoding unit 111, a display unit 112, an image recognition unit 113, and a LAN control unit 114, each of which is connected to the system bus 102. It has a hardware configuration.
  • the system bus 102 transfers data between the connected blocks.
  • image is mainly used, but this is not intended to be limited to a still image.
  • the control unit 106 is composed of one or more CPUs and executes a program stored in the ROM 104.
  • the programs executed by the control unit 106 include an OS (operating system), drivers, applications, and the like.
  • the control unit 106 executes the program to perform overall control of the image file generation device 101.
  • the control unit 106 controls the display on the display unit 112 based on an instruction input by the user from the operation unit 108, issues an image capturing instruction to the image capturing unit 107, and issues a connection instruction to the LAN control unit 114. Perform processing such as.
  • the imaging unit 107 has an image sensor such as a CMOS sensor, and inputs an image signal according to an instruction from the control unit 106.
  • the input image signal is encoded into digital data by the encoding unit 111.
  • the image file generation device 101 may also function to decrypt the image file.
  • the control unit 106 causes a decoding unit (not shown) to decode the image file according to a user operation related to the reproduction process via the operation unit 108, and displays the decoded image data on the display unit 112. Display it.
  • the metadata processing unit 110 acquires the data encoded by the encoding unit 111 and generates an image file that complies with a predetermined file format (for example, HEIF). It should be noted that the metadata processing unit 110 is not limited to HEIF, and can also generate a file conforming to, for example, another moving image file format defined in MPEG or a format such as JPEG. In addition, the metadata processing unit 110 may acquire encoded data from another device, not limited to the encoding unit 111, and generate an image file.
  • a predetermined file format for example, HEIF
  • HEIF a predetermined file format
  • the metadata processing unit 110 may acquire encoded data from another device, not limited to the encoding unit 111, and generate an image file.
  • the file output unit 109 outputs the image file generated by the metadata processing unit 110.
  • the output destination is not particularly limited, but may be output to, for example, a display device that displays an image based on an image file or a printing device that prints an image based on the image file.
  • the image file may be output to a storage device that stores the image file or a storage medium (nonvolatile memory 103) that stores the image file.
  • the non-volatile memory 103 is an SD card, compact flash (registered trademark), flash memory, or the like.
  • the image recognition unit 113 executes recognition processing of a person, an object, a scene, etc.
  • the control unit 106 sends an instruction to the display unit 112 based on the result of the recognition process, or issues an instruction to the image pickup unit 107 to automatically release the shutter.
  • the control unit 106 also performs processing such as notifying the metadata processing unit 110 of the metadata to be stored in the image file. In the present embodiment, the description will be made assuming that the metadata and the property information have almost the same meaning.
  • each functional block is configured by a separate circuit in the present embodiment, the processing (operation) of at least one functional block may be realized by executing a program by the control unit 106 or the like.
  • the RAM 105 is a main storage unit of the image file generation apparatus 101, and is mainly used as a temporary storage area for data when processing of each functional block is executed.
  • the ROM 104 is a non-volatile storage unit that stores a software program executed by each functional block. The program stored in the ROM 104 is transferred to the RAM 105, read by each functional block, and executed.
  • the LAN control unit 114 is a communication interface connected to the LAN and executes communication control of a wired LAN or a wireless LAN. For example, when the image file generation device 101 is connected to another device via a wired LAN, the LAN control unit 114 includes PHY and MAC (transmission media control) hardware circuits of transmission media.
  • the LAN control unit 114 corresponds to an Ethernet (registered trademark) NIC (Network Interface Card).
  • the LAN control unit 114 has a controller, an RF circuit, an antenna that executes wireless LAN control such as IEEE 802.11a/b/g/n/ac. including.
  • FIG. 2 is a diagram showing a flow of image file generation processing according to the present embodiment. This processing flow can be executed by each circuit shown in FIG. 1 according to a user operation. Alternatively, the present processing flow can be realized by the control unit 106 executing a program stored in the ROM 104 in a timely manner, calculating and processing information, and controlling each hardware.
  • the image file generation device 101 acquires an image to be stored in the HEIF file. Specifically, the image signal acquired by the image capturing unit 107 is encoded by the encoding unit 111, and the encoded image signal (digital data) is input to the metadata processing unit 110.
  • the image file generation device 101 can acquire image signals corresponding to a plurality of images. For example, when the image capturing unit 107 performs burst shooting (continuous shooting), a plurality of continuously shot images are acquired. When the image captured by the image capturing unit 107 is divided into tiles and encoded by the encoding unit 111, each tile image is acquired as a plurality of images.
  • the image file generation device 101 can acquire not only the image capturing unit 107 but also one or a plurality of images from other devices.
  • the metadata processing unit 110 analyzes the metadata of the encoded image signal.
  • the metadata processing unit 110 acquires (extracts) metadata corresponding to the image acquired in step S201.
  • the metadata processing unit 110 acquires an image file conforming to ISOBMFF (ISO base media file format) as an encoded image signal.
  • the metadata processing unit 110 acquires the property information stored in the item property box (iprp) in the image file and the property information referred to by the item in the image property association box.
  • the metadata processing unit 110 acquires Exif data when, for example, an image file including Exif data is acquired as an encoded image signal. Not limited to Exif data, XMP (Extensible Metadata Platform) and MPEG-7 metadata may be used. Further, for example, a part of the Exif data may be acquired in S203.
  • the image recognition unit 113 recognizes what kind of scene the image is, whether a specific subject is included in the image, and the result (scene recognition result or subject information) as metadata. May be input to the metadata processing unit 110. Metadata based on the result of the recognition process can also be the target of common metadata described later.
  • the metadata processing unit 110 determines whether or not one or more images are already stored in the HEIF file, and if so, the process proceeds to S205, and if not, the process proceeds to S207.
  • the metadata processing unit 110 determines whether the metadata already stored in the HEIF file matches the metadata corresponding to the image acquired this time, or whether the metadata is within a predetermined range. If they match, or if they are within a predetermined range, the process proceeds to S206, where the metadata processing unit 110 adds the item ID (image identification) of the image acquired this time to the metadata (that is, common metadata) already stored in the HEIF file. (Information) are stored in association with each other.
  • the metadata processing unit 110 stores the item ID of the image acquired this time in association with the metadata of the image as the common metadata acquired this time in the new HEIF file. ..
  • the metadata processing unit 110 stores the item of the image acquired this time in the generated HEIF file in association with the metadata of the image as the common metadata acquired this time. ..
  • step S208 the metadata processing unit 110 determines whether there is an unprocessed image. If no unprocessed image exists, the process proceeds to S209, and if an unprocessed image exists, the process proceeds to S201. Note that the determination in S208 may be made based on the setting of the shooting conditions (for example, the number of burst shootings), the number of images set by the user, and other predetermined conditions.
  • the metadata processing unit 110 deletes metadata that is not common to two or more images from the common metadata storage area.
  • the metadata that is not common to two or more images is deleted, but the deletion may be determined by a threshold value other than two.
  • the metadata corresponding to only a single image may be stored in the common metadata storage area.
  • Such a configuration is effective, for example, in a case where only one image is stored in the HEIF file, or in a use case where an image item in which specific metadata is recorded is to be quickly taken out. That is, the information stored in the common metadata storage area can be used as an index of an image associated with specific metadata.
  • the metadata processing unit 110 stores the common metadata in the HEIF file.
  • the timing of storing the common metadata in the HEIF file may be S206 or S207. If the metadata of each image becomes unnecessary by storing the common metadata in the HEIF file, the metadata processing unit 110 deletes the metadata from the HEIF file. For example, when the item property associations are grouped, the item property associations for each item are unnecessary and are deleted.
  • FIG. 3 shows an example of the format of the HEIF file.
  • a general and simple HEIF file 301 is composed of a management data section 302 and a media data section 303.
  • the management data unit 302 stores file management data including information regarding encoding of media data and information regarding a method of storing in a HEIF file.
  • the media data section 303 stores data (media data) obtained by encoding content data (moving image, still image, and audio), metadata that refers to an external standard, and the like.
  • a coded image, Exif data, and the like are stored in a box called MediaDataBox.
  • Storage areas 316, 317, and 318 indicate storage areas for each image
  • storage areas 319, 320, and 321 indicate storage areas for metadata such as Exif data defined by an external standard.
  • the management data section 302 has a box structure, and each box is identified by a type identifier.
  • Box 304 is a FileTypeBox identified by the identifier ftyp.
  • FileTypeBox is used to identify the type of file, and the file format is identified by a four-character identifier called brand.
  • the HEIF file is represented by using a 4-character identifier for identifying a brand such as mif1 or msf1.
  • Box 305 is called MetaBox and is identified by the identifier meta.
  • Various boxes are further stored in the box 305 (MetaBox). For example, a box for storing untimed metadata such as an image (image item) and a metadata item related to the image (image item) is included in the box 305 (MetaBox).
  • Box 306 is called the HandlerReferenceBox and is identified by the identifier hdrlr.
  • the structure and format of the content included in the box 305 (MetaBox) is identified by the handler type in the HandlerReferenceBox.
  • the 4-character identification code "pict" is applied to the type of this handler.
  • Box 307 is called the ItemLocationBox and is identified by the identifier iloc.
  • ItemLocationBox information indicating the ID (identification information of each image) of each item and the storage location (location) is described.
  • the metadata processing unit 110 can know where the data of the item defined in the management data unit 302 exists by referring to this information.
  • the box 308 is called ItemInformationBox and is identified by the identifier iinf.
  • An ItemInformationEntry is defined for each item in a box 308 (ItemInformationBox), and information such as an item ID, an item type, and an item name is stored in this entry.
  • the box 309 is called ItemReferenceBox and is identified by the identifier iref.
  • a box 309 (ItemReferenceBox) stores information such as a reference type regarding association of items having a reference relationship.
  • the item IDs to be referred to are described in order. For example, when the thumbnail image of item 1 is item 2, thmb indicating a thumbnail image is stored as a reference type, item_item_id stores the item ID indicating item 1, and to_item_id stores the item ID indicating item 2. .. Further, when one image is divided into a plurality of tiles and stored in the HEIF file, the box 309 (ItemReferenceBox) stores information indicating the relationship between them.
  • the whole image is item 1, and the plurality of tile images is item 2, item 3, item 4, and item 5.
  • information that item 1 is an image formed by item 2, item 3, item 4, and item 5 is stored.
  • dim indicating a derived image is stored as a reference type
  • ID indicating item 1 is stored in from_item_id.
  • to_item_id stores all item IDs indicating item 2, item 3, item 4, and item 5.
  • a box 309 (ItemReferenceBox) can also describe a reference relationship between metadata defined by an external standard such as Exif data and an image item.
  • cdsc is used as the reference type
  • the item ID indicating the Exif data is stored in the from_item_id
  • the item ID indicating the image item is stored in the to_item_id.
  • the box 310 is called ItemPropertyBox and is identified by the iprp identifier.
  • a box 310 (ItemPropertyBox) stores a box of property information applied to each item and a method of configuring the property.
  • the box 311 is called ImagePropertyContainerBox and is identified by the identifier ipco.
  • a box for describing each property is stored in the box 311.
  • the box 311 (ImagePropertyContainerBox) has various boxes. For example, a box indicating the size of an image, a box indicating color information, a box indicating pixel information, a box storing HEVC parameters, etc. are stored as necessary. It These file formats are common with the box structure defined in ISO/IEC23008-12.
  • the box 312 is called ItemPropertyAssociationGroupBox, and is identified by an ipag identifier.
  • a box 312 (ItemPropertyAssociationGroupBox) is defined by the structure shown in FIG. 7.
  • FIG. 7 is a diagram showing an example of the ItemPropertyAssociationGroupBox structure in the file format.
  • the box 312 is a box for grouping ItemProperty associations for each item defined by the entry of the ItemPropertyAssociationBox defined in ISO/IEC23008-12. By using this ItemPropertyAssociationGroupBox, items to which common item properties are applied can be grouped. The grouped items can be identified by item_association_group_id.
  • the box 313 is called ItemPropertyAssociationBox, and is identified by the ipma identifier.
  • Box 313 is defined by the structure shown in FIG.
  • FIG. 8 is a diagram showing an example of the ItemPropertyAssociationBox structure in the image file format.
  • the group bit is set to 0, and the index of the property applied to the item is described in order.
  • setting the group bit to 1 makes it clear that the property configuration for the item group is described.
  • the property configuration applied to the group identified by the item_association_group_ID is described in order.
  • the box shown in Fig. 7 is newly defined.
  • the method of similarly grouping and describing may be adopted by using the EntityToGroupBox defined in ISO/IEC23008-12 and expanding the box of FIG. 8 accordingly.
  • the box structure of FIG. 7 shown in this embodiment has a structure in which the number of bits used can be reduced, so that the metadata can be more efficiently associated with the image.
  • the existing EntityToGroupBox can be used to achieve the purpose of defining the grouping of items.
  • grouping_type is newly defined.
  • the grouping of items is defined in the ItemPropertyBox.
  • FIG. 9 is a diagram showing another example of the ItemPropertyAssociationBox structure in the image file format
  • FIG. 10 is a diagram showing another example of the ItemPropertyAssociationGroupBox structure in the image file format.
  • This is not a method of grouping items, but a method of grouping and describing item properties applied to an image. That is, in this method, a part of the property information described for each item is described as a property group.
  • an identifier indicating a grouping type may be defined and stored.
  • the identifier indicating the group type a value such as “join” indicating that the properties are combined and adapted to all images is used for identification.
  • the 4-character code of the group type may be stored instead of the'ipag' shown in the box type, or the group type may be defined and stored as one of the structure members.
  • the box structure shown in FIG. 10 is defined in the ItemPropertyBox, but it may be defined in the GroupListBox defined in ISO/IEC23008-12. This makes it possible to reduce the amount of data when describing in the file format.
  • FIG. 17 is a diagram showing an example of the ItemPropertyToGroupPropertyBox structure in the image file format.
  • the box shown in FIG. 17 is an ItemPropertyToGroupPropertyBox, which is equivalent to the above-mentioned ItemPropertyAssociationGroupBox.
  • an identifier indicating the type of group can be stored in the four-character code indicating the box type. This makes it possible to determine what kind of group the item property is.
  • num_properties_in_group indicates the number of item properties to be grouped.
  • the essential information indicates whether or not the item property indicated by each property_index is essential.
  • the item information in the ItemPropertyAssociationBox when the index information indicating the ItemPropertyToGroupPropertyBox is stored in the ItemPropertyAssociationBox indicates whether or not the item group itself is required.
  • the property_index describes the item property information indicated by the index order starting from 1 in the ItemPropertyContainerBox, as in the ItemPropertyAssociationBox. Index number 0 is reserved.
  • the ItemPropertyToGroupPropertyBox itself is also shown in the same index order, but information indicating the self-indexing order should not be stored in this box. If your index is stored, ignore it. This makes it possible to avoid an infinite loop. Since this box is defined as one of the item properties, the property type is the Descriptive type. In addition, it is desirable, but not limited to, that the Descriptive type and the Transformative type are grouped separately for each item property grouped by the list of property_index. At that time, the Item property of the Descriptive type is described, and then the ItemPropertyToGroupPropertyBox in which the Descriptive types are grouped is described.
  • the Transformative item property it is preferable to describe the Transformative item property, and then describe the ItemPropertyToGroupPropertyBox in which the Transformative type item properties are grouped. It should be noted that the Grouping_type or flags of the ItemPropertyToGroupPropertyBox may be used to distinguish between the Descritive type group and the Transformative type group.
  • FIG. 16 is a diagram showing another example of the ItemPropertyAssociationBox structure in the image file format. According to the box structure shown in FIG. 16, a plurality of item properties can be applied to a plurality of items. That is, it is possible to group the items in each entry of the ItemPropertyAssociationBox without explicitly grouping the item properties and the items, and to describe the properties applicable thereto.
  • Box 314 is called CommonItemPropertyBox and is identified by the cipr identifier. Box 314 is defined by the structure shown in FIG. FIG. 11 is a diagram illustrating an example of a CommonItemPropertyBox structure.
  • a box 314 (CommonItemPropertyBox) is a box for indicating item properties commonly applied to all items. By using the box 314, properties (metadata) that are commonly applied to all items are easily extracted. That is, if the common metadata is stored using the box 314, the common metadata can be extracted without searching all the entries of the ItemPropertyAssociationBox. This improves the search efficiency when accessing the file.
  • the search efficiency is improved by defining a box indicating a property commonly applied to all items.
  • the present invention is not limited to this example, and information that can be identified as being applicable to all such items may be stored in the box of each item property defined in the ItemPropertyContainerBox.
  • the box 315 is called CommonItemPropertyGroupBox, and is identified by the identifier cipg.
  • Box 315 is defined by the structure shown in FIG. FIG. 12 is a diagram illustrating an example of a CommonItemPropertyGroupBox structure.
  • a box 315 (CommonItemPropertyGroupBox) is a box that makes it possible to identify items to which common properties (metadata) are applied.
  • box 315 (CommonItemPropertyGroupBox) is a box that describes a list of items to which common properties apply.
  • the metadata processing unit 110 can specify the item to which the specific property is applied without checking all entries of the ItemPropertyAssociationBox.
  • the efficiency in the case of reading the image file and picking up and processing only the items to which the specific property is applied is improved, and the search efficiency in accessing the file is improved.
  • batch operation becomes easy when editing a file or the like.
  • the item property indicated by property_index is a property indicating the image size
  • the plurality of image items to which the image properties defined in the ItemPropertyContainerBox are applied are represented by the box 315, so that the metadata processing unit 110 can easily identify the plurality of images to which the common properties are applied.
  • a box 310 (ItemPropertyBox) for storing a box representing a common property has a structure shown in FIG.
  • FIG. 13 is a diagram illustrating an example of an ItemPropertyBox (ItemPropertiesBox) structure.
  • the box 310 (ItemPropertyBox) specifically stores the ItemPropertyAssociationBox in the ItemPropertiesBox identified by the identifier iprp. Further, the ItemPropertyContainerBox, ItemPropertyAssociationGroupBox, CommonItemPropertyBox, and CommonItemPropertyGroupBox are stored.
  • FIG. 14 is a description example of the box 309 (ItemReferenceBox) of FIG.
  • FIG. 15 is a description example of the box 308 (ItemInformationBox) of FIG.
  • FIG. 4 shows Exif data blocks 401, 402, 403, 404, 405.
  • the ItemInformationBox shown in FIG. 15 is made up of nine entries, and item_IDs 1, 2, 3, and 4 are image items.
  • the image item with item_ID 5 is in the Exif data block 401
  • the image item with item_ID 6 is in the Exif data block 402
  • the image item with item_ID 7 is in the Exif data block 403
  • the image item with item_ID 8 is in the Exif data block 404.
  • Item_ID of 9 corresponds to the Exif data block 405, respectively.
  • the ItemReferenceBox shown in FIG. 14 indicates the reference relationship of each item. It can be read from FIGS. 14 and 15 that item_ID5 is an Exif data block relating to the image of item_ID1.
  • item_ID6 is an Exif data block related to the image of item_ID2
  • item_ID7 is an Exif data block related to the image of item_ID3.
  • item_ID8 is an Exif data block relating to the image of item_ID4.
  • item_ID9 refers to item_ID5, 6, 7, and 8. This description indicates that item_ID9 is an Exif data block obtained by extracting a common part (common metadata) from the Exif data blocks of item_ID5, 6, 7, and 8.
  • the Exif data block 401 shown in FIG. 4 includes an image width 410, an image height 411, an X resolution 412, a Y resolution 413, a maker name 414, a model name 415, a shooting date and time 416, an ISO sensitivity 417, and an Exif tag (meta information 418) Data).
  • These tags are generated at the time of imaging. Further, tags may be added, changed, or deleted by a separate editing process.
  • the Exif data block 405 is a block that stores common data (common metadata) of the Exif data blocks 401, 402, 403, and 404.
  • the value “320pixel” is stored in the image width tag 450 in the Exif data block 405.
  • the value “240pixel” is stored in the image height tag 451 in the Exif data block 405.
  • “96 dpi” indicated by the X resolutions 412, 422, 432, and 442 is stored in the area 452.
  • “96 dpi” indicated by the Y resolutions 413, 423, 433, and 443 is stored in the area 453.
  • “Company A” indicated by manufacturer names 414, 424, 434, and 444 is stored in area 454.
  • “11” indicated by the model names 415, 425, 435, and 445 is stored in the area 455.
  • the shooting date and time varies depending on the image.
  • the (shooting) date and time 416 and 426 is “June 13, 2018”
  • the date and time 436 is “June 14, 2018”
  • the date and time 446 is “June 15, 2018”. is there. Therefore, the shooting date/time is not stored in the Exif data block 405 in which the common data of each Exif data block is extracted.
  • the metadata common to all image items is stored in the Exif data block 405.
  • the ISO sensitivity values 417, 427, 437, and 447 have different values, they are not stored in the Exif data block 405.
  • the time information is omitted at the dates 416, 426, 436, 446.
  • the GPS information 418, 428, 438, 448 which is the position information, is stored in the Exif data block 405 if it is within the predetermined range even if the values do not completely match. .. This is because the GPS information 418, 428, 438, and 448 match as information indicating a specific location, even if they do not completely match. That is, the GPS information 418, 428, 438, and 448 all indicate the location of the company A, and the locations derived by geocode etc. are all the company A and coincide with each other.
  • the metadata processing unit 110 of the present embodiment treats a plurality of GPS information within a specific range as common metadata.
  • some types of metadata for example, GPS information
  • which range is common may be specified separately by the user or may be appropriately determined according to the settings of a specific system.
  • all the GPS information on the premises of the company A is treated as common metadata
  • the GPS information stored in the GPS information 458 is a representative of the company A represented by a geocode or the like. Represents a point. For example, when the GPS information in Tokyo is treated as common GPS information, the position information of the representative point in Tokyo is stored in the GPS information 458.
  • the HEIF file of this embodiment does not store information indicating at what granularity the GPS information is handled, but it may be stored in the file.
  • FIG. 4 shows an example in which data common to all Exif data blocks of each image is stored in the common Exif data block.
  • the Exif data block common to two or more Exif data blocks may be stored in the common Exif data block.
  • the Exif data block to be referred to may be defined in the ItemReferenceBox shown in FIG.
  • the (shooting) dates and times 416 and 426 are also included in the extraction target because they are common Exif data.
  • the metadata processing unit 110 of the present embodiment extracts all the common data in the Exif data block corresponding to each image
  • the common data may be extracted only for certain specific Exif data. You can For example, it may be a determination target whether or not only the shooting date and time is common. Further, for example, the commonality of the shooting dates and times may be determined only for images whose shooting dates and times fall within a specific range. As described above, it should be noted that the commonality may be determined only for a specific type of metadata, and that there are various variations in determining the specific type.
  • the image file generation device 101 generates common metadata from metadata (property information) associated with each of a plurality of images stored in an image file (HEIF file) conforming to the image file format. Extract. Then, the image file generation device 101 stores the extracted metadata as common metadata in the metadata area. Further, the image file generation device 101 may store in the HEIF file information indicating whether the metadata is common metadata common to all images or common metadata to some of a plurality of images. .. In the case of common metadata common to some images, the item ID (image identification information) of the some images is stored. Further, the image file generation apparatus 101 also extracts common metadata from the metadata of each image and holds it as common metadata for metadata based on an external standard (for example, Exif data).
  • an external standard for example, Exif data
  • the processing load can be reduced when specific processing is performed only on one or more images associated with specific metadata among the plurality of images stored in the HEIF file.
  • the processing of searching for a specific image from the plurality of images stored in the HEIF file can be performed with a low load.
  • the size of the image file can be reduced by sharing the metadata for each image in common.
  • the configuration of the image file generation device 501 of this embodiment is shown in FIG.
  • the image file generation device 501 of FIG. 5 is a communication device having a file editing function, such as a server device that performs processing by a Web service such as a tablet PC, desktop PC, or cloud.
  • the components having the same reference numerals as those in FIG. 1 are the same as those in FIG.
  • the metadata processing unit 502 performs processing for editing an image file and extracting common metadata from images and metadata stored in the image file.
  • the image file generation device 501 according to the present embodiment is characterized by editing an image file, and thus may be configured without the imaging unit 107.
  • FIG. 6 is a diagram showing a processing flow of the image file generation device 501 in the second embodiment.
  • This processing flow can be executed by each circuit shown in FIG. 5 according to a user operation.
  • the present processing flow can be realized by the control unit 106 executing a program stored in the ROM 104 in a timely manner, calculating and processing information, and controlling each hardware. It is assumed that an image file (HEIF file) conforming to one or more image file formats is stored in the image file generating device 501 in advance.
  • step S ⁇ b>601 the metadata processing unit 502, based on the metadata associated with each of the plurality of images stored in the HEIF file, information regarding the metadata to be extracted, such as the metadata value, range, and type. Determine (extraction target metadata). This determination may be made based on a user designation via the operation unit 108, or may be made based on a predetermined system setting or the like. Also, multiple decisions may be made.
  • the metadata processing unit 502 acquires the metadata of each of the plurality of images stored in the HEIF file.
  • the metadata processing unit 502 is not limited to one HEIF file, but may process a plurality of HEIF files. Further, not only the HEIF file but also a JPEG file or the like may be processed. In addition, the metadata processing unit 502 may acquire only the metadata already recorded in the HEIF file, or may acquire the metadata newly generated by the processing of the image recognition unit 506 as the acquisition target.
  • step S603 the metadata processing unit 502 determines whether the metadata acquired in step S602 matches the extraction target metadata determined in step S601. If they match, the process proceeds to S604, and if they do not match, the process proceeds to S605.
  • step S603 the metadata processing unit 502 determines whether the range of both metadata is within a predetermined range. If the range is within the predetermined range, the process proceeds to step S604. If the range is not within the predetermined range, the process proceeds to step S605. Is also good.
  • step S604 the metadata processing unit 502 extracts matching metadata as common metadata, stores the common metadata in the storage area of the common metadata in association with the item ID for identifying the image.
  • the metadata processing unit 502 creates a new HEIF file and stores the image item and the item ID corresponding to the HEIF file.
  • step S605 the metadata processing unit 502 determines whether processing has been completed for all images for which metadata is to be acquired. When it is completed, the process proceeds to S606, and when it is not completed, the process proceeds to S602 and is repeated.
  • step S606 the metadata processing unit 502 deletes metadata that is not common to other images from the extracted common metadata. That is, the metadata processing unit 502 does not store the metadata applied to only a single image as the common metadata.
  • step S607 the metadata processing unit 502 stores the common metadata in the HEIF file.
  • the metadata processing unit 502 stores the common metadata in the HEIF file according to the formats shown in FIGS. 7 to 17 based on the common metadata and the item ID of the image.
  • the metadata corresponding to only a single image is not stored as the common metadata, but the metadata common only to the images of which the number is smaller than the predetermined threshold is not stored as the common metadata. You may do it.
  • the metadata corresponding to only a single image may be stored in the area for storing the common metadata.
  • Such a configuration is effective, for example, in a case where only one image is stored in the HEIF file, or in a use case where an image item in which specific metadata is recorded is to be quickly taken out. That is, the information stored in the common metadata storage area can be used as an index of an image associated with specific metadata.
  • the image file generation device 501 of the present embodiment extracts common metadata from the generated image file and newly generates a HEIF file in which the common metadata is stored. This makes it possible to generate an image file storing common metadata from an image file not recorded as common metadata.
  • the image file generation device 501 according to the present embodiment extracts common metadata from a plurality of images (including videos) stored in a plurality of image files (including video files) and stores the common metadata. Generate a new file.
  • the image file generation apparatus 101 also extracts common metadata from the metadata of each image and holds it as common metadata for metadata based on an external standard (for example, Exif data). This can reduce the processing load when handling a plurality of images stored in the HEIF file.
  • the processing load can be reduced when specific processing is performed only on one or more images associated with specific metadata among the plurality of images stored in the HEIF file. Further, the processing of searching for a specific image from the plurality of images stored in the HEIF file can be performed with a low load. Further, the size of the image file can be reduced by sharing the metadata for each image in common.
  • FIGS. 18A and 18B are flowcharts showing the image file generation processing flow in this embodiment.
  • This processing flow is typically started in response to the input of an editing instruction from the user.
  • this processing flow is performed by the image file generation device 501 shown in FIG.
  • a user operation, each circuit shown in FIG. 5, or the control unit 106 executes a program stored in the ROM 104 in a timely manner to execute information calculation and processing and control of each hardware.
  • step S1801 the metadata processing unit 502 acquires the metadata (metadata to be added) to be stored in the HEIF file.
  • the metadata processing unit 502 may acquire the addition target metadata based on a user designation via the operation unit 108, or may acquire the metadata based on a predetermined system setting or the like.
  • step S1802 the metadata processing unit 502 acquires one or more pieces of metadata stored in the HEIF file, and acquires the type of each metadata. Details of the type of metadata will be described later.
  • step S1803 the metadata processing unit 502 determines whether the HEIF file includes the same type of metadata as the addition target metadata acquired in step S1801. That is, the metadata processing unit 502 determines whether or not there is one that matches the type of the addition target metadata acquired in S1801 among the one or more metadata types acquired in S1802. When it exists, it progresses to S1804, and when it does not exist, it progresses to S1805. It should be noted that the determination can be made based on a knowledge base such as a dictionary stored in advance in the image file generation device 502. Further, instead of the type of metadata, other information such as the property or attribute of metadata may be compared.
  • the metadata processing unit 502 has applied (applied) the same type of metadata determined to exist in S1803 to the image to which the addition target metadata is applied (the image to which the addition target metadata is applied). To confirm. If it has been adapted, the process proceeds to S1807, and if it has not been adapted, the process proceeds to S1805. If there are a plurality of images to which the addition target metadata is applied, the metadata processing unit 502 confirms each image, and if any one is applied, the process proceeds to step S1807.
  • step S1805 the metadata processing unit 502 stores information on the metadata to be added in the HEIF file. This mainly corresponds to storing as ItemProperty in the element of ItemPropertyContainerBox.
  • step S1806 the metadata processing unit 502 stores the association information between the stored addition target metadata and the image (the image adapted to the addition target metadata), and ends the processing. This mainly corresponds to the storage of the association information for each image item in the ItemPropertyAssociationBox.
  • the metadata processing unit 502 stores the index order of ItemPropertyContainerBox of item properties as an association of each item ID.
  • the metadata processing unit 502 confirms whether metadata of the same type applied to the same image has already been grouped. If the same type of metadata is grouped, the process advances to step S1806. If not grouped, the process proceeds to S1810. It should be noted that even if the metadata is of the same type, it is not selectively applied, and if it is applied in a different meaning, it is not considered as the same type of metadata, and the process proceeds to S1810.
  • step S1808 the metadata processing unit 502 stores the information of the addition target metadata in the HEIF file as in step S1805.
  • step S1809 the metadata processing unit 502 adds the information of the addition target metadata stored in step S1808 to the already grouped metadata group, and ends the processing. As a result, the options within the group of item properties that are already associated with the item ItemItemBox are added to the image item.
  • the metadata processing unit 502 stores the information of the addition target metadata in the HEIF file, as in S1805 and S1808.
  • the metadata processing unit 502 stores information for grouping metadata adapted to the same image into the same type of metadata. That is, the metadata processing unit 502 stores information for grouping the metadata applied to the image to which the addition target metadata is applied and the addition target metadata as the same kind of metadata.
  • the metadata processing unit 502 deletes the previously stored information that associates the same type of metadata with the image item. Specifically, it corresponds to deleting the corresponding index information in the item property in the ItemAssociationBox.
  • the metadata processing unit 502 stores information that associates the grouped metadata with the image item. Specifically, it corresponds to storing the association information indicating the item property group in the ItemAssociationBox.
  • the property (metadata) applied to the image from the plurality of properties selectively adapt the property (metadata) applied to the image from the plurality of properties (selectively associate the property related to the image from the plurality of properties). ..
  • the property of may be grouped and stored. At that time, when an image to be stored in the image file format of S201 is input, the same kind of metadata group information is stored when the related metadata is stored. Further, in the present embodiment, the grouping of properties is shown by the above box structure, but any box structure that can achieve this object may be used.
  • FIG. 19 is a diagram showing an example of the AccessibilityTextPropertyBox structure
  • FIGS. 20 and 21 show an example of the ItemPropertyBox.
  • the box shown in FIG. 19 is AccessibilityTextPropertyBox.
  • This box is a box for storing the information of the alternative text character string of the HTML specification.
  • Alt_text stored in this box is a parameter for storing the alternative text of the HTML specification.
  • alt_lang is a character string of a language tag conforming to RFC4646 or BCP47, and stores an identifier indicating a language such as'en-US','fr-FR','zh-CN', or'ja-JP'. Text information in the language indicated by alt_lang is stored in alt_text.
  • this box it is possible to store text information such as what kind of content the image item has.
  • this box as an item property for each language in which it is desired to store, it becomes possible to store text information corresponding to the language.
  • the alternative text of the HTML specification is stored in the present embodiment, the text information may be stored without being limited to the HTML specification.
  • the ItemPropertiesBox shown in FIG. 20 is a diagram showing an example of applying the item properties stored in the image file to the image.
  • this image file four sub-pictures are stored as item IDs 1 to 4, and one image item that configures it as a grid derived image is configured as item ID 5.
  • the four sub-pictures are images having an image size of 512 in width and 512 in height, and one image which is a derivative image thereof stores an image of 1024 in width and 1024 in height.
  • Common properties are applied to the four sub-pictures, and one derived image stores text information indicating what the image is (indexes 1 to 6).
  • an ItemPropertyContainerBox and an ItemPropertyAssociationBox are stored in the ItemPropertiesBox. Further, the ItemPropertyContainerBox stores six various item properties.
  • the first HEVCConfigurationBox is a box indicated by the identifier hvcC, and stores the encoding parameter of the image item.
  • the second ImageSpacialExtentsPropertyBox is a Box indicated by the identifier ispe, and stores information indicating the size of the image.
  • the third to fifth AccessibilityTextPropertyBoxes are boxes having the structure shown in FIG. 19 and are identified by'altt'.
  • en-US is stored in alt_lang, which indicates English in the American region.
  • alt_text an English text character string'dog' is stored.
  • ja-JP is stored in alt_lang, which indicates Japanese in the Japanese region.
  • a Japanese text character string "dog" is stored in alt_lang.
  • fr-FR is stored in alt_lang, which indicates French in the French region.
  • a French text character string'chien' is stored in the alt_text.
  • a text character string having the same meaning is stored in each language. That is, the types of the text information related to the same image have the same meaning.
  • the image file generating device 501 (or 101) stores learning data and a knowledge base such as a dictionary in advance and can determine whether or not the types of metadata are the same.
  • property_index which is the index order of ItemPropertyContainerBox, indicates 3, 4, and 5, and the above-mentioned AccessibilityTextPropertyBox is grouped.
  • the three AccessibilityTextPropertyBoxes can be grouped together using the ItemPropertyToGroupPropertyBox, and the ItemPropertyToGroupPropertyBox can be adapted as a group to the item using the ItemPropertyToGroupPropertyBox.
  • ItemPropertyAssociationBox is a box indicated by the identifier ipma, and stores information indicating the relationship between each image item and item property.
  • the entry_count indicates 1, indicating that the item property association of one image is stored.
  • the association_count indicates that the image whose item_ID is 1 is associated with three item properties.
  • essential indicates 1 and indicates that it is an essential property.
  • 1 in property_index indicates that the above-mentioned HEVCConfigurationBox, which is 1 in the order of index of ItemPropertyContainerBox, is associated.
  • the essential indicates 0, indicating that the property is not essential.
  • 2 in property_index indicates that the above-mentioned ImageSpacialExtentsPropertyBox is associated.
  • the essential indicates 0, indicating that the property is not essential.
  • the property_index indicates 6, and the ItemPropertyToGroupPropertyBox is associated with the property_index. Accordingly, the device that reads the image file can refer to the image item to which the ItemPropertyToGroupPropertyBox is applied by the group type altr by selecting one of the three AccessibilityTextPropertyBoxes.
  • any one of the item properties grouped by altr is selectively applied to the image item, but a plurality of properties may be selectively applied.
  • the item properties are explicitly grouped by using ItemPropertyToGroupPropertyBox and adapted to the image item.
  • ItemPropertyAssociationBox when the same kind of item property is adapted to ItemPropertyAssociationBox, the image is implicitly and selectively selected.
  • the configuration may be adapted to the item.
  • not only the alternative text information but also related text may be stored as a label. In that case, it is also possible to apply a plurality of pieces of text information grouped according to meaning and selectively apply label information for each group.
  • item properties of the Transformative type can also be grouped in the same manner. At that time, it is desirable to group the properties of the Descriptive type and the Transformative type without mixing them. At that time, flags may be used to indicate what type of property is to be grouped, or grouping_type may be used to define the group type so that it can be identified. Further, by describing the Descriptive type property and then describing the Descriptive type group, it is possible to describe the index number described in advance. Further, after that, the Transform type item property is described. After that, it is preferable to describe ItemPropertyToGroupPropertyBox in which item properties of the Transformative type are similarly grouped. As a result, it becomes possible to adapt without changing the constraint condition when adapting the item property.
  • the ItemPropertyContainerBox and the ItemPropertyAssociationBox are stored in the ItemPropertiesBox. Further, the ItemPropertyContainerBox stores nine various item properties.
  • the first HEVCConfigurationBox is a box indicated by the identifier hvcC, and stores the encoding parameter of the image item. Different coding parameters are stored in the second HEVCConfigurationBox.
  • the third and fourth ImageSpacialExtentsPropertyBoxes are Boxes indicated by the identifier ispe, and information indicating the size of the image is stored. Information of different image sizes is stored in each of the two Image Spatial Extenders PropertyBoxes.
  • the fifth to seventh AccessibilityTextPropertyBoxes are boxes having the structure shown in FIG. 19 and are identified by'altt'. Texts in different languages are stored in the three AccessibilityTextPropertyBoxes.
  • the ItemPropertyToGroupPropertyBox identified by the group type'altr', groups three item properties. In this embodiment, AccessibilityTextProperty of index order 5, 6, and 7 is grouped as a property of the same type. Further, in the ItemPropertyToGroupPropertyBox indicated by the group type'join', two item properties are grouped.
  • the HEVCConfigurationBox with an index order of 1 and the ImageSpatialExtentsPropertyBox with an index order of 3 are grouped as a common item property.
  • ItemPropertyAssociationBox property related information of five items is stored. Items having item_IDs 1 to 4 are applied to the item group of the “join” type, which is the ninth index order item, and the first and third item properties in the index order item are all commonly applied. Further, the item property of item ID 5 is adapted to the item properties of index order 2, 4, and 8.
  • the 8th item property in the index order is an item property group of the altr type, and the 5th, 6th, and 7th item properties in the index order are selectively applied.
  • AccessibilityTextPropertyBox is defined as the item property of the same type in the present embodiment, other item properties may be selectively applicable.
  • different versions may be stored as properties of the same type, and may be adapted as a box of a version supported by the reading device.
  • the CleanApertureBox for each of a plurality of specific persons can be defined, and the reading device can selectively display only the specific person.
  • Various other expansions are also possible.
  • the image file generation device 101 or 501 of the present embodiment uses common or similar metadata among a plurality of metadata (property information) related to an image stored in an image file (HEIF file) conforming to the image file format. To extract. Then, the extracted metadata is grouped and stored in the metadata area. At that time, an identifier capable of determining the grouped type is stored. The grouped metadata is stored in the image file in association with the image in the same manner as other ungrouped metadata. This makes it possible to handle a plurality of metadata (property information) stored in the HEIF file as a group, reduce the processing load when handling an image, and selectively adapt metadata. The selective adaptation makes it possible to adaptively handle the image based on the situation, conditions, and judgment of the device that reads the image file. Further, the size of the image file can be reduced by sharing the metadata for each image in common.
  • the processing relating to the image file can be efficiently performed.
  • the metadata is selectively applied to the image file. It can be performed.
  • the present invention supplies a program that implements one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program. It can also be realized by the processing. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.
  • a circuit for example, ASIC

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Library & Information Science (AREA)
  • Human Computer Interaction (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Television Signal Processing For Recording (AREA)
PCT/JP2019/043118 2018-12-18 2019-11-01 画像ファイル生成装置、画像ファイル生成方法、及びプログラム Ceased WO2020129434A1 (ja)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/345,004 US20210303616A1 (en) 2018-12-18 2021-06-11 Image file generation apparatus, image file generation method, and computer-readable storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2018-236722 2018-12-18
JP2018236722A JP7303625B2 (ja) 2018-12-18 2018-12-18 画像ファイル生成装置、画像ファイル生成方法、及びプログラム

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/345,004 Continuation US20210303616A1 (en) 2018-12-18 2021-06-11 Image file generation apparatus, image file generation method, and computer-readable storage medium

Publications (1)

Publication Number Publication Date
WO2020129434A1 true WO2020129434A1 (ja) 2020-06-25

Family

ID=71101261

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2019/043118 Ceased WO2020129434A1 (ja) 2018-12-18 2019-11-01 画像ファイル生成装置、画像ファイル生成方法、及びプログラム

Country Status (3)

Country Link
US (1) US20210303616A1 (enExample)
JP (2) JP7303625B2 (enExample)
WO (1) WO2020129434A1 (enExample)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112667114A (zh) * 2020-12-21 2021-04-16 北京小早科技有限公司 一种信息处理方法、装置以及计算机存储介质
CN114727001A (zh) * 2021-01-05 2022-07-08 北京小米移动软件有限公司 一种处理图像数据的方法、装置及介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113302944B (zh) * 2018-12-28 2023-10-27 索尼集团公司 信息处理装置和信息处理方法
CN114128249B (zh) * 2019-07-30 2024-11-15 索尼集团公司 文件处理设备、文件处理方法和介质
KR102595278B1 (ko) * 2020-12-29 2023-10-27 부산대학교 산학협력단 표면결함검출 스캐너를 위한 이미지 데이터 저장 장치 및 방법
JP2024044783A (ja) * 2022-09-21 2024-04-02 キヤノン株式会社 画像処理装置、画像処理方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005038006A (ja) * 2003-07-15 2005-02-10 Fujitsu Ltd 情報共有装置および情報共有処理プログラム
JP2007013939A (ja) * 2005-05-30 2007-01-18 Matsushita Electric Ind Co Ltd メタデータ付与装置及びメタデータ付与方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4072302B2 (ja) * 1999-04-13 2008-04-09 キヤノン株式会社 データ処理方法及び装置及び記憶媒体
US7197158B2 (en) 2002-06-28 2007-03-27 Microsoft Corporation Generation of metadata for acquired images
JP5121285B2 (ja) 2007-04-04 2013-01-16 キヤノン株式会社 被写体メタデータ管理システム
KR20090088772A (ko) * 2008-02-15 2009-08-20 삼성전자주식회사 슬라이드 쇼를 위한 영상파일을 생성 및 재생하기 위한시스템 및 방법
JP2010176429A (ja) * 2009-01-29 2010-08-12 Dainippon Printing Co Ltd 電子コンテンツ配信システム
JP5381437B2 (ja) * 2009-07-14 2014-01-08 富士ゼロックス株式会社 画像情報送信装置及び画像情報送信プログラム
US10291561B2 (en) * 2015-02-09 2019-05-14 Nokia Technologies Oy Apparatus, a method and a computer program for image coding and decoding
GB201502205D0 (en) 2015-02-10 2015-03-25 Canon Kabushiki Kaisha And Telecom Paris Tech Image data encapsulation
US9922680B2 (en) * 2015-02-10 2018-03-20 Nokia Technologies Oy Method, an apparatus and a computer program product for processing image sequence tracks
GB2539461B (en) 2015-06-16 2020-01-08 Canon Kk Image data encapsulation
EP3107011B1 (en) * 2015-06-16 2018-12-12 Nokia Technologies Oy Method, apparatus, and computer program product for storage of dynamically derived images in an image container file
JP6848358B2 (ja) * 2016-05-12 2021-03-24 株式会社リコー 情報処理システム、情報処理装置、プログラム及び画面生成方法
CN113302944B (zh) * 2018-12-28 2023-10-27 索尼集团公司 信息处理装置和信息处理方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005038006A (ja) * 2003-07-15 2005-02-10 Fujitsu Ltd 情報共有装置および情報共有処理プログラム
JP2007013939A (ja) * 2005-05-30 2007-01-18 Matsushita Electric Ind Co Ltd メタデータ付与装置及びメタデータ付与方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MISKA M. ET AL.: "ITU-T SG 16 WP3 and ISO/IEC JTC1/SC29/WG11", JCTVC-V0072, 7 October 2015 (2015-10-07), pages 1 - 12 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112667114A (zh) * 2020-12-21 2021-04-16 北京小早科技有限公司 一种信息处理方法、装置以及计算机存储介质
CN114727001A (zh) * 2021-01-05 2022-07-08 北京小米移动软件有限公司 一种处理图像数据的方法、装置及介质
CN114727001B (zh) * 2021-01-05 2024-01-19 北京小米移动软件有限公司 一种处理图像数据的方法、装置及介质

Also Published As

Publication number Publication date
JP2020098499A (ja) 2020-06-25
JP7303625B2 (ja) 2023-07-05
US20210303616A1 (en) 2021-09-30
JP2023112059A (ja) 2023-08-10
JP7483102B2 (ja) 2024-05-14

Similar Documents

Publication Publication Date Title
JP7483102B2 (ja) 画像ファイル生成装置および方法、画像ファイル再生装置、プログラム
CN103119595B (zh) 通过快门按击的自动媒体共享
JP6562289B2 (ja) 映像編集装置
CN100592294C (zh) 内容管理设备及方法、Web服务器和网络系统
KR101832680B1 (ko) 참석자들에 의한 이벤트 검색
US20070226169A1 (en) Smart share technologies for automatically processing digital information
JP7267703B2 (ja) 画像データ格納装置、画像データ格納方法、及び、プログラム
CN113615158A (zh) 文件生成设备、文件生成方法、文件再现设备、文件再现方法和程序
JP6234146B2 (ja) 記録制御装置、記録制御方法、及び、プログラム
US11157546B2 (en) Information processing apparatus, control method, and storage medium
CN105208262A (zh) 网络摄影数据管理系统与方法
JP5849177B2 (ja) 画像情報処理システム
CN110119380B (zh) 一种可缩放矢量图文件的存储、读取方法及装置
KR20220108063A (ko) 데이터 처리 장치, 데이터 처리 방법, 및 프로그램
JP5909734B2 (ja) 画像表示方法
US8161086B2 (en) Recording device, recording method, computer program, and recording medium
US11792334B2 (en) System for efficiently migrating content data
JP2023112455A (ja) 情報処理装置および情報処理方法
KR101990689B1 (ko) 클라우드 서버의 이미지 데이터 제공 방법
JP2006195807A (ja) 映像検索システム、映像検索方法及びプログラム
CN119336926A (zh) 一种图像元数据处理方法、装置、设备及存储介质
JP2014203347A (ja) 文書検索システム、文書検索装置、文書検索方法及びプログラム
JP2005149483A (ja) ファイル生成方法及びファイル検索方法
KR20090017124A (ko) 영상표시기기 및 그 제어방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19898421

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19898421

Country of ref document: EP

Kind code of ref document: A1