Method and apparatus for encapsulating a panoramic image in a file

By describing the panorama as a derived image and embedding it into the HEIF file, the problem of low storage efficiency of panoramic images in HEIF and MIAF formats is solved, and efficient storage and reading of panoramic images is achieved, improving the file capability Readability and organization.

CN114097249BActive Publication Date: 2024-11-12CANON KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080046446.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-06-26
Filing Date
2020-06-10
Publication Date
2024-11-12
Estimated Expiration
2040-06-10

AI Technical Summary

Technical Problem

HEIF and MIAF file formats do not provide an efficient way to store panoramic images, and lack an effective storage mechanism for human-readable text descriptions and timing information.

Method used

Describe a panorama as a derived image. By generating a collection of image items, association information and parameter data structures, the parameters of the panorama are associated with the derived image items and embedded in a file. It supports panoramic direction, size and type indications, providing humans with the ability to use it. Storage of read tags and timing information.

Benefits of technology

It realizes efficient storage and reading of panoramic images, provides a way to store human-readable text description and timing information, and improves the readability and organization of files.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114097249B_ABST
    Figure CN114097249B_ABST
Patent Text Reader

Abstract

The present invention relates to a method for encapsulating media data in a file, wherein the method comprises: encoding a reference image set; generating an image item set to describe the reference image set; generating an image item describing a derived image corresponding to a panorama based on the reference image set; generating association information associating the image item describing the derived image with the image item set; generating a parameter data structure containing parameters of the panorama, the parameter data structure being associated with the image item describing the derived image; and embedding the image item set, the image item describing the derived image, and the association information into the file.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to methods and apparatus for packaging multiple images in a file. Background Art

[0002] Modern cameras provide different shooting modes for capturing images. Some of these shooting modes enable a series of images to be captured. For example, modern cameras provide a bracketing mode for capturing several images, where the value of a parameter of the capture is different between one captured image and another captured image. For example, the parameter may be exposure time, white value, or focus. Another shooting mode may be a panoramic mode, which allows a series of superimposed images to be obtained to reconstruct a large viewing angle of a scene. Modern cameras are capable of combining these different shooting modes, for example, for each shooting angle of view used to construct a panorama, a modern camera is capable of capturing a series of images according to a bracketing mode. For example, this allows the creation of a high dynamic range (HDR) panorama by performing auto-exposure bracketing for each angle of view that will constitute the panorama. Another example is the creation of a focus stacked panorama by performing focus bracketing for each angle of view that constitutes the panorama.

[0003] For example, images captured by a camera are stored on a storage device such as a memory card. Images are usually encoded to reduce the size of the data on the storage device. Many encoding standards can be used, such as JPEG or the newer HEVC standard.

[0004] The HEVC standard defines a profile for encoding still images and describes specific tools for compressing a single still image or a sequence of still images. An extension to the ISO Base Media File Format (ISOBMFF) for such image data has been proposed for inclusion in Part 12 of the ISO / IEC 23008 standard, under the name "HEIF or High Efficiency Image File Format".

[0005] HEIF (High Efficiency Image File Format) is a standard developed by the Moving Picture Experts Group (MPEG) for storing and sharing one or more images and image sequences.

[0006] MIAF (Multiple Image Application Format) is a standard developed by MPEG as ISO / IEC 23000 standard part 22 that defines a set of constraints for the HEIF specification targeting precise interoperability points for the creation, reading, parsing and decoding of images embedded in the High Efficiency Image File (HEIF) format.

[0007] The HEIF and MIAF file formats do not provide an efficient way to store panoramas.

[0008] The HEIF and MIAF file formats do not provide an efficient way to store human-readable text descriptions of images or groups of images (including panoramas).

[0009] The HEIF and MIAF file formats do not provide an efficient way to store timing information for images and groups of images (including panoramas). Summary of the invention

[0010] The present invention aims to solve one or more of the above problems.The present invention relates to describing a panorama as a derived image.

[0011] According to one aspect of the present invention, a method for encapsulating media data in a file is provided, wherein the method comprises:

[0012] - encoding a set of reference images;

[0013] - generating a set of image items to describe the set of reference images;

[0014] - generating, based on said set of reference images, image items describing derived images corresponding to the panorama;

[0015] - generating association information associating said image item describing said derived image with said set of image items;

[0016] - generating a parameter data structure containing parameters of said panorama, said parameter data structure being associated with said image item describing said derived image;

[0017] - embedding said set of image items, said image items describing said derived images and said associated information in said file.

[0018] According to an embodiment, the method further comprises:

[0019] - generating a parameter data structure containing parameters of said panorama, said parameter data structure being associated with said image item describing said derived image; and

[0020] - embedding said parameter data structure in said file.

[0021] According to the embodiment:

[0022] - said image item describing said derived image is a derived image item;

[0023] - the derived image item has a dedicated item type indicating that the derived image item is panoramic;

[0024] -The parameter data structure is stored in the media part of the file.

[0025] According to the embodiment:

[0026] - the method further comprises encoding a derivative image corresponding to the panorama, the encoded derivative image being stored in the media part of the file;

[0027] - said picture item describing said derived picture is a pre-derivative coded picture item; and

[0028] - said parameter data structure is stored as an item attribute associated with a pre-derivative coded image item.

[0029] According to an embodiment, the parameter data structure comprises a panorama direction.

[0030] According to an embodiment, the parameter data structure further comprises a plurality of rows and columns.

[0031] According to an embodiment, the parameter data structure comprises the size of the derived image corresponding to the panorama.

[0032] According to an embodiment, the parameter data structure comprises a type indication of a derived type.

[0033] According to an embodiment, at least some of the image items in the set of image items constitute an image item group.

[0034] According to an embodiment, at least some of the image items are associated with item attributes comprising at least one human-readable label.

[0035] According to an embodiment, at least some of the image items are associated with item attributes comprising timing information.

[0036] According to another aspect of the present invention, a method for reading media data in a file is provided, wherein the method comprises:

[0037] - reading an image item describing a derived image corresponding to the panorama based on the set of reference images;

[0038] - reading association information associating said image item describing said derived image with said set of image items;

[0039] - read a set of image items describing a set of reference images;

[0040] - obtaining said derived image corresponding to said panorama.

[0041] According to an embodiment, the method further comprises:

[0042] - reading a parameter data structure containing parameters of said panorama, said parameter data structure being associated with said image item describing said derived image;

[0043] According to the embodiment:

[0044] - said image item describing said derived image is a derived image item;

[0045] - the derived image item has a dedicated item type indicating that the derived image item is panoramic;

[0046] -The parameter data structure is stored in the media part of the file.

[0047] According to the embodiment:

[0048] - The method further comprises: decoding a derivative image corresponding to the panorama, the encoded derivative image being stored in the media part of the file;

[0049] - said picture item describing said derived picture is a pre-derivative coded picture item; and

[0050] - said parameter data structure is stored as an item attribute associated with a pre-derivative coded image item.

[0051] According to an embodiment, the parameter data structure comprises a panorama direction.

[0052] According to an embodiment, the parameter data structure further comprises a plurality of rows and columns.

[0053] According to an embodiment, the parameter data structure comprises the size of the derived image corresponding to the panorama.

[0054] According to an embodiment, the parameter data structure comprises a type indication of a derived type.

[0055] According to an embodiment, at least some of the image items in the set of image items constitute an image item group.

[0056] According to another aspect of the present invention, an apparatus for encapsulating media data in a file is provided, wherein the apparatus comprises a circuit configured to:

[0057] - encoding a set of reference images;

[0058] - generating a set of image items to describe the set of reference images;

[0059] - generating, based on said set of reference images, image items describing derived images corresponding to the panorama;

[0060] - generating association information associating said image item describing said derived image with said set of image items;

[0061] - embedding said set of image items, said image items describing said derived images and said associated information in said file.

[0062] According to another aspect of the present invention, an apparatus for reading media data in a file is provided, wherein the apparatus comprises a circuit configured to:

[0063] - reading an image item describing a derived image corresponding to the panorama based on said set of reference images;

[0064] - reading association information associating said image item describing said derived image with said set of image items;

[0065] - read a set of image items describing a set of reference images;

[0066] - obtaining said derived image corresponding to said panorama.

[0067] According to another aspect of the invention, a computer program product for a programmable device is proposed, the computer program product comprising a sequence of instructions for implementing the method according to the invention when loaded into and executed by the programmable device.

[0068] According to another aspect of the present invention, a computer-readable storage medium is proposed, which stores instructions of a computer program for implementing the method according to the present invention.

[0069] According to another aspect of the invention, a computer program is proposed which, when executed, causes the method of the invention to be performed.

[0070] At least part of the method according to the invention may be computer-implemented. Thus, the invention may take the form of a fully hardware embodiment, a fully software embodiment (including firmware, resident software, microcode, etc.), or a combination of software and hardware embodiments, which may all be generally referred to herein as "circuits," "modules," or "systems." Furthermore, the invention may take the form of a computer program product embodied in any tangible medium of expression having a computer-usable program code embodied in the medium.

[0071] Since the present invention can be implemented in software, the present invention can be embodied as computer readable code for providing to a programmable device on any suitable carrier medium. Tangible non-transitory carrier media may include storage media such as floppy disks, CD-ROMs, hard disk drives, magnetic tape devices, or solid-state memory devices. Transient carrier media may include signals such as electric signals, electronic signals, optical signals, acoustic signals, magnetic signals, or electromagnetic signals (e.g., microwave or RF signals). BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Embodiments of the present invention will now be described, by way of example only, and with reference to the following drawings, in which:

[0073] Figure 1An example of a HEIF file containing several images or a sequence of images is shown;

[0074] Figure 2 illustrates storage of a panorama in a derived image item according to an embodiment of the present invention;

[0075] Figure 3 shows the storage of a panorama in a pre-derived coded image item according to another embodiment of the present invention;

[0076] Figure 4 shows storage of a panorama in an entity group according to another embodiment of the present invention;

[0077] Figure 5 shows the main steps of a process for encapsulating one or more images forming a panorama in one file using the HEIF format according to some embodiments of the present invention;

[0078] Figure 6 is a schematic block diagram of a computing device for implementing one or more embodiments of the present invention. DETAILED DESCRIPTION

[0079] The HEVC standard defines a profile for encoding still images and describes specific tools for compressing a single still image or a sequence of still images. An extension to the ISO Base Media File Format (ISOBMFF) for such image data has been proposed for inclusion in Part 12 of the ISO / IEC 23008 standard, under the name "HEIF or High Efficiency Image File Format".

[0080] The HEIF and MIAF standards cover two forms of storage corresponding to different use cases:

[0081] - storage of a sequence of pictures, each picture being represented by samples with timing information optionally used at a decoder, and wherein the pictures may depend on other pictures, and

[0082] - Storage of single images, as well as collections of independently coded images.

[0083] In the first case, the encapsulation is close to that of video tracks in the ISO base media file format (see document Information technology—Coding of audio-visual objects—Part 12: ISO basemedia file format, ISO / IEC 14496-12:2015, Fifth Edition, December 2015), and uses similar tools and concepts, such as the file-level "moov" box, the "trak" box (encapsulated in the "moov" box), and sample grouping for describing samples and sample groups, etc. A sample represents all timing data associated with a single time (e.g., a frame in a video or an image in an image sequence).

[0084] A box (also called a container) is a metadata structure provided to describe the data in a file. A box is an object-oriented building block defined by a unique type identifier (usually a four-character code, also called FourCC or 4CC) and a length. All the data in a file (media data and metadata describing the media data) is contained in a box. There is no other data in the file. A file-level box is a box that is not contained in other boxes.

[0085] The "moov" box is a file format box containing "trak" sub-boxes, each "trak" box describing a track, that is, a timed sequence of related samples.

[0086] In the second case, a collection of ISOBMFF boxes, the file-level "meta" box and its subboxes are used. These boxes and their hierarchy provide fewer descriptive tools than the "track-related" boxes (the "trak" box hierarchy), and refer to "information items" or "items" instead of related samples. It should be noted that the word "box" and the word "container" may be used in the same meaning to refer to metadata structures that contain metadata describing the organization and / or properties of the image data in a file. The same word "box" and the word "container" may also be used in the same meaning to refer to metadata structures that contain image data in a file (e.g., an "mdat" or "idat" box).

[0087] Figure 1An example of a HEIF file 101 is shown, which contains media data such as one or more still images and possibly a video or image sequence. The file contains a first "ftyp" box (FileTypeBox) 111, which contains an identifier of the file type (usually a set of four-character codes). The file contains a second box (MetaBox) 102 called "meta", which is used to contain general non-periodic metadata including a metadata structure describing one or more still images. The "meta" box 102 contains an "iinf" box (IteminfoBox) 121 describing several individual images. Each individual image is described by a metadata structure ItemInfoEntry also represented as items 1211 and 1212. Each item has a unique 32-bit identifier item_id. The media data corresponding to these items is stored in a container for media data ("mdat" box 104). The "iloc" box (ItemLocationBox) 122 provides the offset and length of its associated media data in the "mdat" box 104 for each item. An "iref" box (ItemReferenceBox) 123 may also be defined to describe the linkage of an item to other items via typed references.

[0088] Optionally, in order to describe the storage of an image sequence or video, the HEIF file 101 may contain a third box (MovieBox) 103 called "moov", which describes several image sequences or video tracks 131 and 132. Typically, track 131 is an image sequence ("pict") track designed to describe a collection of images for which temporal information is not necessarily meaningful, and 132 is a video ("vide") track designed to describe video content. These two tracks describe a series of image samples, which are sets of pixels taken at the same time, such as frames of a video sequence. The main difference between the two tracks is that in the "pict" track, the timing information is not necessarily meaningful, while for the "vide" track, the timing information is intended to constrain the timing of the display of the samples. The data corresponding to these samples are stored in a container ("mdat" box) 104 for media data.

[0089] The “mdat” container 104 stores untimed coded images corresponding to the items represented by data portions 141 and 142 and timed coded images corresponding to the samples represented by data portion 143 .

[0090] HEIF file 101 provides different alternatives to store multiple images. For example, we can store multiple images as items or as tracks that can be samples of a "pict" track or a "vide" track. The actual choice is usually made by the application or device generating the file based on the type of image and the intended use of the file.

[0091] The HEIF standard also provides some mechanisms designed to specify properties associated with images, in particular some metadata structures to declare or store properties of images and, more generally, properties of items (of any kind of media type). Typically, the "meta" box 102 may contain an "iprp" box (itemPropertiesBox) 125, which enables any item to be associated with an ordered set of item properties. The "iprp" box 125 contains an "ipco" box (ItemPropertyContainerBox) 1251, which is a property container data structure containing all property data structures (ItemProperty and ItemFullProperty) 1253 that describe the properties of all items described in the HEIF file. The "iprp" box also contains a collection of "ipma" boxes (ItemPropertyAssociationBox) 1252, which is an association data structure that actually associates one or more item properties with a given item. The same property can then be associated with several items.

[0092] In addition, the ISO base media file format specifies a grouping mechanism suitable for grouping items and / or tracks. The "meta" box 102 may contain a container box "gprl" (GroupsListBox) 124, which may contain a collection of metadata structures describing entity groups 1241 and 1242, which all inherit from a grouping data structure called EntityToGroupBox (also denoted as entity group) defined below:

[0093]

[0094]

[0095] where group_id is a unique identifier for the entity group, unique in this case must be understood as unique within the file. It should not be equal to any group_id value of any EntityToGroupBox, any item_ID value of the hierarchy (file, animation or track) containing the GroupsListBox, or any track_ID value (when the GroupsListBox is contained in the file level). The list of entity_id then gives the identifiers of all entities belonging to the group.

[0096] In this mechanism, the word "entity" is used to refer to an item (any type of item, for example, an image or a metadata item) or a track (for example, a video track "vide", a picture sequence track "pict", an audio track or any other type of track), and grouping_type is used to specify the type of grouping. HEIF actually defines a limited number of grouping_type values.

[0097] The ISO base media file format also specifies a grouping mechanism suitable for grouping samples within a track.

[0098] The mechanism relies on two dedicated boxes. The first box, named SampleToGroupBox, allows to associate one or more samples with one or more group descriptions. The second box, named SampleGroupDescriptionBox, includes one or more sample group description entries that provide alternative descriptions of the properties of the sample group. When these two boxes are declared with the same grouping_type, they provide, respectively, the association of a sample with one of the group description entries, and a list of alternative group description entries for a given type of sample group identified by the common grouping_type.

[0099] The present invention provides a mechanism that provides a means for describing the group of items that were photographed or edited to form a panorama. A means is provided to describe the shooting or collection mode that has been used. According to some embodiments, some additional information or attributes about the shooting can be described for an entity or group of entities.

[0100] The standard provides the concept of derived images. A derived image is an image generated by a derivation based on one or several reference images. There are two different types of derived images in the standard. The first type is a derived image item in which an image item is linked to a reference image set. The derived image item does not include image data in the media part of the file. Instead of image data, the media data part may include some parameters to be used in the derivation process. The second type of derived image is a pre-derived coded image item. The pre-derived coded image item is also linked to a reference image set. The difference between the pre-derived coded image item and the derived image item is mainly that the pre-derived coded image item includes image data generated by the derivation in the media part of the file. In the case of a derived image item, a player that needs to access the derived image needs to derive based on the reference image, while in the pre-derived coded image item, the derived image is directly accessible. The standard currently considers derived images to store image grids and superimposed images. This article proposes a solution that describes a panoramic image as a derived image. The first embodiment is based on a derived image item, while the second embodiment is based on a pre-derived coded image item. According to the proposed solution, the panorama is represented by an item in the file. One advantage of using items to describe the panorama is that it allows the panorama to be specified as the primary item in the HEIF file (via PrimaryItemBox "pitm"), i.e., the panorama is specified as the default item intended to be drawn by a HEIF reader.

[0101] The third embodiment describes a panoramic image as a reference image group.

[0102] According to a first embodiment, a panorama is described as a derived image item. An item is a derived image item when it includes a "dimg" item that references one or more other image items as input to the derivation. The derived image itself does not contain media data representing a coded image bitstream, but a reconstructed image representing the derived image item is obtained by operating on one or more input images (coded images or other derived images). The exact operation performed to obtain the reconstructed image is identified by the item_type of the item.

[0103] According to this embodiment, an item with an item_type value of "pano" defines a derived image item by superimposing and stitching one or more input images in a given order to obtain a higher resolution panorama. The input images are listed in a SingleItemTypeReferenceBox of type "dimg" for the derived image item within the ItemReferenceBox in scan order.

[0104] Contrary to the grid derived image item (item_type="grid"), the panorama derived image item does not enforce that the input images should have a consistent size without overlay. And contrary to the overlay derived image (item_type="iovl"), the panorama derived image item indicates that the derivation operation implies an additional processing step for stitching the input images and correcting alignment and deformation in the panorama. Furthermore, the scan order of the input images matches the order in which they were taken by the user, thus avoiding reordering of the images before encapsulating them in the HEIF file.

[0105] If desired, parameters associated with the panorama (such as the panorama direction) can be stored in the media data section of the file associated with the derived image item. Such media data associated with a panoramic derived image item (or the body of an item) can be described in a parameter data structure as follows:

[0106]

[0107] in,

[0108] version and flags shall be equal to 0. Both attributes are defined to support future extensions of panorama derived image items. The version parameter may be used to conditionally define a new syntax attribute for the value of the version parameter, and the flags parameter may allow a map of flags to be defined to conditionally represent / activate optional features or parameters for the value of the flags parameter.

[0109] panorama_direction is an unsigned integer, e.g. 8 bits, indicating the type of panorama used and the scanning order of the input images in the panorama:

[0110] -0: horizontal panorama from left to right

[0111] -1: horizontal panorama from right to left

[0112] -2: Vertical panorama from bottom to top

[0113] -3: Vertical panorama from top to bottom

[0114] -4: Grid panorama in raster scan order, i.e. rows and columns are organized from left to right and top to bottom starting from the upper left corner.

[0115] -5: Grid panorama in continuous order, i.e., starting from the upper left corner, the first row is organized from left to right, then the second row is organized from right to left, the third row is organized from left to right, and so on.

[0116] -Other values ​​are undefined.

[0117] rows_minus_one is an unsigned integer specifying the number of rows in the grid minus one.

[0118] columns_minus_one is an unsigned integer specifying the number of columns in the grid minus 1. In an embodiment, this parameter is not present and the number of columns is calculated from the total number and number of rows of the input image.

[0119] When no parameter data structure is present in the media file, a horizontal left-to-right panoramic view is assumed.

[0120] In the alternative, additional values ​​of panorama_direction can be defined to support grid panoramas with raster scan or continuous scan order starting from different corners (e.g., top right, bottom left, or bottom right). For example, starting from the bottom right corner, the raster scan order will be organized from right to left and bottom to top for each row, and the continuous scan order will start from right to left on the last row, then from left to right on the previous row, and so on.

[0121] In a variation, the media data associated with a panoramic derived image item may be defined as follows:

[0122]

[0123] in,

[0124] Two additional parameters and flags are defined to indicate the size of the reconstructed panoramic image.

[0125] (flags&1) equal to 0 specifies that the length of the fields output_width, output_height is 16 bits. (flags&1) equal to 1 specifies that the length of the fields output_width, output_height is 32 bits. Flag values ​​greater than 1 are reserved.

[0126] output_width, output_height specify the width and height of the reconstructed panoramic image respectively.

[0127] In an alternative, the width and height of the reconstructed panoramic image may be represented by associating an ImageSpatialExtensProperty (using 4cc "ispe") with the panoramic derived image item (via ItemPropertyAssociationBox ("ipma")).

[0128] According to an embodiment, the capturing of the panoramic image is combined with another exposure bracketing mode, for example, with automatic exposure bracketing to create a high dynamic range (HDR) panorama, or with focus exposure bracketing to create a focus stacked panorama, or with any other type of exposure bracketing mode. Thus, the panoramic derived image item may include a "dimg" item that references one or more entity groups as input to the derivation (e.g., an EntityToGroupBox with a grouping type "aebr" for automatic exposure bracketing or a grouping type "fobr" for focus exposure bracketing, etc. as an entity group defined in Working Draft of Amendment to ISO / IEC 23008-12, w18430, April 2019).

[0129] To include "dimg" items that reference one or more groups, the definition of the existing SingleItemTypeReferenceBox can be extended so that the existing attribute to_item_ID can also reference the group_id of the entity group. The attribute to_item_ID can be renamed to_item_or_group_ID and defined as follows:

[0130]

[0131] in,

[0132] reference_type contains an indication of the reference type

[0133] from_item_ID contains the item_ID of the item that references the other item

[0134] reference_count is the number of references

[0135] to_item_or group_ID contains the item_ID of the item or the group_id of the entity group being referenced.

[0136] For each viewing angle constituting the panorama, an EntityToGroupBox with a grouping type identifying a bracketing exposure mode is defined to describe a bracketing exposure set of an image corresponding to the viewing angle. In addition, an item property corresponding to the bracketing exposure mode (e.g., AutoExposureProperty or FocusProperty, etc.) can be associated with each image item to specify the properties of the bracketing exposure for the image item (e.g., the exposure value stop of the image item).

[0137] Figure 2 An example of this first embodiment is shown.

[0138] A panorama is represented by a derived image item 201. A new item type is proposed to identify a derived image item that is a panorama, for example "pano".

[0139] In the "iref" box, a structure SingleItemTypeReferenceBox 202 of reference type "dimg" contains a list of reference images 204 and 205 and references to image groups, such as a bracketed exposure set 208. The image group itself contains references to the image items 206 and 207 that make up the group. It should be noted that the "dimg" box can only reference items, only reference entity groups, or a mixture of reference items and entity groups.

[0140] The derived image item 201 representing the panorama can be linked to an optional structure 210 in the media data via an "iloc" box 209. This structure 210 in the media data does not include any image data according to the general derived image item properties. This structure 210 contains some parameters for the derivation of the panorama, typically an imagePanorama box as described above.

[0141] A feature of the first embodiment is that the derived image items describe the derivation operation to be applied to the set of input image items (here building a panorama), but the resulting reconstructed image is not actually stored in the HEIF file and will be reconstructed whenever a HEIF reader processes the HEIF file.

[0142] According to a second embodiment, a panorama is described as a pre-derived coded image item. An item is a pre-derived coded image item when it specifies a coded image bitstream that is actually stored in the HEIF file and also includes a "base" item that references one or more other image items from which it is derived. The current HEIF standard does not allow description of the precise derivation process used to produce a pre-derived coded image item. Thus, for example, it is not possible to distinguish a pre-derived coded image item representing a panorama from a pre-derived coded image item representing an HDR image.

[0143] According to the proposed embodiment, an optional item property DerivationOperationProperty may be defined as follows and associated with a pre-derived item to describe the derivation operation applied to the input image item. It should be noted that the proposed item property may be used to define the derivation operation of any kind of pre-derived coded image item, not just panoramas.

[0144] Box type: "dopr"

[0145] Attribute type: Descriptive item attribute

[0146] Container: ItemPropertyContainerBox

[0147] Mandatory (for each item): No

[0148] Amount (per entry): zero or one for pre-derived coded pictures

[0149] The DerivationOperationProperty records the derivation operation applied to an input image item or group of image items to generate a pre-derived coded image item. The input image items or groups of image items are ordered in the order in which they are referenced by item references of type "base" from the pre-derived coded image item.

[0150]

[0151] in,

[0152] derivation_operation_4cc is the four-character code (4CC) of the derivation operation. For example, you can specify the following list of derivation operations:

[0153] Derivation Operation 4cc Code High Dynamic Range (HDR) 'hdr' Focus Stacking 'fost' Flash exposure stacking 'afst' Depth of Field Stacking 'dost' panoramic 'pano' Super-resolution stacking 'sres'

[0154] When the derivation operation is a panoramic derivation, an additional parameter is provided to characterize the type of panorama.

[0155] The parameters panorama_direction, rows_minus_one and columns_minus_one are defined as specified in the first embodiment described above.

[0156] The DerivationOperationProperty can be easily extended to support further derivation operation four-character codes and parameters.

[0157] According to this embodiment, when the capture of an image for a panorama is combined with another exposure bracketing mode, such as with automatic exposure bracketing to create a high dynamic range (HDR) panorama, or with focus exposure bracketing to create a focus stacked panorama, or with any other type of exposure bracketing mode, the panoramic pre-derived coded image item may include a "base" item that references one or more entity groups used as input to the panoramic derivation (e.g., an EntityToGroupBox with a grouping type "aebr" for automatic exposure bracketing or a grouping type "fobr" for focus exposure bracketing, etc. as the entity groups defined in WorkingDraft of Amendment to ISO / IEC 23008-12, w18430, April 2019). Similar to the first embodiment described above, the SingleGroupTypeReferenceBox may be extended to allow an item to reference an entity group. For each viewing angle constituting the panorama, an EntityToGroupBox with a grouping type identifying the exposure bracketing mode is defined to describe a set of exposure bracketing images corresponding to the viewing angle. The grouping_type of EntityToGroupBox specifies the purpose of the grouping and implicitly indicates the type of the derivation operation that is applied to the image items from the group to obtain an intermediate reconstructed image that is used as input for generating the panoramic pre-derived encoded image. In addition, item properties corresponding to the bracketing exposure mode (e.g., AutoExposureProperty or FocusProperty, etc.) can be associated with each image item belonging to EntityToGroupBox to specify the properties of the bracketing exposure of the image item (e.g., the exposure value level of the image item).

[0158] One advantage when a panoramic pre-derived coded picture item directly includes a “base” item that references one or more entity groups is that it avoids declaring pre-derived coded picture items derived from individual entity groups and avoids storing corresponding intermediate reconstructed images in the HEIF file when they are not needed.

[0159] According to this embodiment, the width and height of the reconstructed panoramic image may be represented by associating ImageSpatialExtensProperty (using 4CC "ispe") with the panoramic pre-derived coded image item (via ItemPropertyAssociationBox ("ipma")).

[0160] Figure 3 An example of a panorama described as a pre-derived coded image item is shown.

[0161] The panorama is represented by a pre-derived coded picture item 301, where item_type identifies the coding format of the pre-derived coded picture (eg "hvc1" for a picture in HEVC coding format or "jpeg" for a picture in JPEG coding format).

[0162] In the "iref" box, a structure SingleItemTypeReferenceBox 302 of reference type "base" contains reference images 304 and 305 and a list 303 of references to groups of images, such as a set of bracketed exposures 308. The group of images itself contains references to the image items 306 and 307 that make up the group. It should be noted that the "base" box can only reference items, only reference entity groups, or a mixture of reference items and entity groups.

[0163] The pre-derived coded image item 301 representing the panorama is linked to the image data 310 corresponding to the derivation result in the media data via the "iloc" box 309. Box 311 is an optional attribute describing the derivation operation, which is linked to the pre-derived coded image item 301 via the associated information 312 in the box "ipma". Box 311 is typically a "dopr" box as described above.

[0164] According to a third embodiment, we can only record the relationship between the images that make up the panorama, rather than defining specific terms to describe the panorama. This will not create a panorama object in the HEIF file itself, but provide enough information that the HEIF reader can use to create a panorama.

[0165] According to this third embodiment, a new grouping_type "pano" is defined.

[0166] A panoramic entity group ("pano") indicates a collection of images (stored as samples in items, item groups, or tracks) taken to create a panorama by associating the EntityToGroupBox with a new grouping_type "pano". The entity_id of the EntityToGroupBox is expanded to be resolved as an item identifier, a track identifier, or an identifier (group_id) of the EntityToGroupBox representing the set of bracketed exposure images.

[0167] The latter can be used to describe enhanced panoramas (eg, HDR panoramas).

[0168] Then you can define the syntax of EntityToGroupBox as follows:

[0169]

[0170] in,

[0171] When an item with item_ID equal to entity_or_group_id exists in the hierarchy (file, animation, or track) containing the GroupsListBox, entity_or_group_id is resolved to the item, or when a track with track_ID equal to entity_or_group_id exists and the GroupsListBox is contained in the file hierarchy, entity_or_group_id is resolved to the track, or when an entity group with group_ID equal to entity_or_group_id exists in the same GroupsListBox, entity_or_group_id is resolved to the entity group.

[0172] The other parameters remain the same as defined previously.

[0173] In an alternative, define a new box to describe a group within an entity group as follows:

[0174]

[0175]

[0176] in,

[0177] group_id is a non-negative integer assigned to a specific group and should not be equal to any group_id value of any other GroupToGroupBox and EntityToGroupBox, any item_ID value of the level (document, animation or track) containing the GroupsListBox, or any track_ID value (when the GroupsListBox is contained in the document level).

[0178] num_groups_in_group specifies the number of group_id values ​​that are mapped to the group in group.

[0179] When an entity group with group_id equal to entity_or_group_id exists in the same GroupsListBox, the referenced_group_id is resolved to the entity group, or when a group with group_id equal to entity_or_group_id exists in the same GroupsListBox, the referenced_group_id is resolved to the group in the group.

[0180] In other words, a method for encapsulating media data in a file is proposed, wherein the method comprises:

[0181] - generating a grouping data structure describing a first entity group;

[0182] wherein the grouping data structure comprises association information between the first entity group and a second entity group, each entity of the second group being associated with at least a portion of the media data; and

[0183] - embedding said packet data structure and said media data in said file.

[0184] In an embodiment, the method further comprises:

[0185] - obtaining a grouping type that characterizes the group of entities as being eligible for generating the panorama; and

[0186] - Embedding the packet type in the file.

[0187] In an embodiment, each entity of the second set corresponds to at least a portion of the media data.

[0188] In an embodiment, each entity of the second group is at least one of: an item, a track, and a third entity group.

[0189] When grouping_type "pano" is associated with GroupToGroupBox, the panorama group to group ("pano") indicates a set of images (stored as groups of items, each representing a set of bracketed exposures) taken to create a panorama.

[0190] In an alternative to directly referencing an entity group in an EntityToGroupBox structure by extending the definition of entity_id or by defining a new box GroupToGroupBox, the ItemReferenceBox ("iref") can be extended with a new box SingleGroupTypeReferenceBox dedicated to group-to-group references to associate an entity group with a list of other entity groups. The SingleGroupTypeReferenceBox can be defined as follows:

[0191]

[0192] in,

[0193] from_group_ID contains the group_id of the entity group that references the other entity group.

[0194] reference_count is the number of references.

[0195] to_group_ID contains the group_id of the entity group being referenced.

[0196] In other words, a method for encapsulating media data in a file is proposed, wherein the method comprises:

[0197] - obtaining a first grouping data structure describing a first entity group;

[0198] - obtaining a second grouping data structure describing a second entity group;

[0199] - generating an association data structure including association information between the first grouping data structure and the second grouping data structure; and,

[0200] - embedding the first and second grouped data structures, the associated data structure and the media data in the file.

[0201] In an embodiment, the associative data structure further comprises a reference type.

[0202] According to this alternative, grouping_type "pano" is associated with EntityToGroupBox, the panoramic entity group ("pano") then indicates an optional list of images (stored as items) and is optionally associated with item groups, each item group representing a set of bracketed exposures taken to create a panorama. The panoramic entity group "pano" is associated with the item group representing the set of bracketed exposures via a SingleGroupTypeReferenceBox of reference type "base" in the ItemReferenceBox.

[0203] When an image sequence track is included in a "pano" entity group (i.e., images are stored as samples in the track), only one entity_id should be present in the "pano" entity group. An image sequence track may be included in a "pano" entity group to indicate that it contains a sequence of images captured with the intent to form a panorama. An image sequence track present in a "pano" entity group may contain other bracketed exposure sample groupings (e.g., when panoramic capture is coupled with automatic exposure bracketing to form an HDR panorama, a sample grouping with grouping_type "aebr" may be defined to group and describe samples belonging to the same set of bracketed exposures).

[0204] Entities in a panoramic entity group or samples in an image sequence track referenced by a panoramic entity group are listed in panoramic order. The panoramic order used by an entity group or group-to-group should be declared using the pano item attribute "pano" associated with the entity group or group-to-group.

[0205] In the case where images are stored as items, when the panoramic capture is coupled with one or more exposure brackets (eg, auto exposure, focus or white balance brackets), the panoramic EntityToGroupBox can directly reference other exposure bracket sets.

[0206] The pano descriptive item attribute associated with a pano entity group or group-to-group provides the parameters of the pano (direction, type of bracketing if any). This item attribute shall only be associated with an entity group "pano" or group-to-group "pano".

[0207] Panoramic descriptive item attributes can be defined as follows:

[0208]

[0209] in,

[0210] panorama_direction is an unsigned integer, e.g. 8 bits, indicating the type of panorama used and the scanning order of the input images in the panorama:

[0211] -0: horizontal panorama from left to right

[0212] -1: horizontal panorama from right to left

[0213] -2: Vertical panorama from bottom to top

[0214] -3: Vertical panorama from top to bottom

[0215] -4: Grid panorama in raster scan order, i.e. rows and columns are organized from left to right and top to bottom starting from the upper left corner.

[0216] -5: Grid panorama in continuous order, i.e., starting from the upper left corner, the first row is organized from left to right, then the second row is organized from right to left, the third row is organized from left to right, and so on.

[0217] -Other values ​​are undefined.

[0218] rows_minus_one is an unsigned integer specifying the number of rows in the grid minus one.

[0219] columns_minus_one is an unsigned integer specifying the number of columns in the grid minus one.

[0220] The panorama descriptive item attributes may optionally include an additional attribute panorama_bracketing_type or a list of panorama_bracketing_types that provides a 4CC of grouping_type of one or more bracketing exposure sets coupled to the panoramic capture. For example, the panorama_bracketing_type allows the reader to identify in track which samples form a single group of samples or bracketing exposure set corresponding to a single view among the multiple views that make up the panorama. From each group of samples, only one sample from the group or a merge of samples from the group (e.g., an HDR composite of those samples) will be used to construct a view to be composed of other views to construct a complete panoramic view.

[0221] Figure 4 Two examples of panoramas described as entity groups are shown.

[0222] In the first example, the first panorama is represented by the first entity group 401. In the second example, the second panorama is represented by the second entity group 402.

[0223] The two entity groups may reference different ItemPropertyPanoramaProperty("pano") boxes, or when they share the same panorama property, they may advantageously reference the same ItemPropertyPanoramaProperty("pano") 403 as described above.

[0224] The first panorama 401 is composed of and refers to several bracketing exposure sets of items (e.g., automatic bracketing exposure sets “aebr”) represented by multiple entity groups 404 and 405.

[0225] The second panorama 402 is composed of a series of samples stored in an image sequence track 406, wherein the series of samples corresponds to a continuous set of automatic exposure bracketing represented by a number of sample groups "aebr" 407, 408 and 409. For example, sample group 407 is composed of samples 410, 411 and 412. For example, sample 410 is associated with sample group description entry 0 representing automatic exposure value step parameter = -1. Sample 412 is associated with sample group description entry 2 representing automatic exposure value step parameter = +1.

[0226] The HEIF standard does not allow for efficient storage of human-readable text descriptions of images or groups of images that include panoramas. Human-readable text descriptions (such as a name or title, a general description of the panorama, image, or group of images, and a list of tags or keywords associated with the panorama, other image, or group of images) are useful for users to: organize, categorize, and retrieve these panoramas, other images, or groups of images within a HEIF file; display the contents of a HEIF file; create documents based on the contents of a HEIF file; or share these panoramas or other images or groups of images with other users.

[0227] In some embodiments, additional human-readable tags may also be associated with any type of item or entity group (e.g., representing a panorama according to the above embodiments) to provide a human-readable description of the content of the respective item or entity group, such as a title, general description, or tags.

[0228] For this purpose, an item property called, for example, UserDescriptionProperty could be defined as follows:

[0229] Box type: "udes"

[0230] Attribute type: Descriptive item attribute

[0231] Container: ItemPropertyContainerBox

[0232] Mandatory (for each item): No

[0233] Quantity (per piece): zero or more

[0234] UserDescriptionProperty allows an item to be associated with a user defined name, description and tags; there can be multiple such properties (which should have different language codes) associated with an item or entity group (possibly representing a panorama). This allows different language alternatives to be associated with an item or entity group.

[0235] If two different items or groups of items share the same description, the same UserDescriptionProperty can be associated with them. This allows memory to be saved by not duplicating identical data information.

[0236] Additionally, the following flags are allowed to be set in the box's flags:

[0237] 0x000001 Name - Exists

[0238] 0x000002 Description - Exists

[0239] 0x000004 Flag - exists

[0240] When set, they indicate whether the associated name, description, or tag string is defined in the item attributes. This allows saving bytes in the item attribute definition when the corresponding field is not used, compared to the alternative of including defining an empty string.

[0241]

[0242] in,

[0243] lang is a string containing an RFC 5646-compliant language tag string (such as "en-US", "fr-FR", or "zh-CN", etc.) indicating the language of the text contained in name, description, and tags. When lang is empty, the language is unknown / undefined.

[0244] name is a null-terminated UTF-8 string containing the human-readable name of the item or entity group.

[0245] description is a null-terminated UTF-8 string containing a human-readable description of the item or entity group.

[0246] tags is a null-terminated UTF-8 string containing comma-separated tags associated with an item or group of entities.

[0247] The HEIF and MIAF file formats do not provide an efficient way to store timing information (such as creation time or modification time) for images and image groups (including panoramas). This timing information is useful for users to organize, sort, and retrieve panoramas or other images or image groups within HEIF files; display the contents of HEIF files; create documents based on the contents of HEIF files; or share these panoramas or other images or image groups with other users.

[0248] In some embodiments, additional item attributes may be associated with any type of item or entity group (eg, representing a panorama according to the above embodiments) to record their creation and modification times.

[0249] Some item properties (for example, CreationTimeProperty and ModificationTimeProperty) can be defined as follows:

[0250] Box type: "crtt"

[0251] Attribute type: Descriptive item attribute

[0252] Container: ItemPropertyContainerBox

[0253] Mandatory (for each item): No

[0254] Quantity (per item): at most one

[0255] Frame type: "mdft"

[0256] Attribute type: Descriptive item attribute

[0257] Container: ItemPropertyContainerBox

[0258] Mandatory (for each item): No

[0259] Quantity (per item): at most one

[0260] CreationTimeProperty records the creation time of the associated item or entity group.

[0261] The ModificationTimeProperty records the last modification time of the associated item or entity group.

[0262]

[0263] in,

[0264] creation_time is an integer that represents the creation time of the item or entity group, expressed in microseconds since midnight, January 1, 1904, UTC.

[0265] modification_time is an integer representing the most recent time the statement or entity group was modified (in microseconds since midnight UTC, January 1, 1904).

[0266] Microsecond precision allows to support the capture time of high speed cameras with high frame rates per second. If higher precision is needed, a new version of the box can be defined with additional 64-bit attributes (similar to Network Time Protocol version 4).

[0267] In the alternative, UTC time may be counted from a different start time (eg, another well-known Epoch time, such as midnight on January 1, 1970 or 2001, or any other arbitrary well-defined start time).

[0268] In another alternative, an additional attribute may be added, for example as a signed integer, to provide the time zone that would allow the local time to be retrieved from the UTC time.

[0269] In another alternative, creation_time and modification_time can be expressed as differences compared to a global reference time, possibly also by a reference time scale, both declared in another box under the top-level "meta" box or in another top-level box in the HEIF file. This would allow saving some bytes on creation_time and modification_time definitions (e.g. using 32-bit integers instead of 64-bit integers).

[0270] In another alternative, the ModificationTimeProperty includes additional properties, such as a human-readable label and an optional version number as defined below. Multiple ModificationTimeProperties may be associated with an item or entity group to track modification history / versions.

[0271] Frame type: "mdft"

[0272] Attribute type: Descriptive item attribute

[0273] Container: ItemPropertyContainerBox

[0274] Mandatory (for each item): No

[0275] Quantity (per item): zero or more

[0276]

[0277] in,

[0278] The definition of modification_time is as described above.

[0279] major_version_number and minor_version_number are unsigned integers providing the major and minor version numbers.

[0280] comment gives a human-readable comment about the modification.

[0281] Optionally, an additional property lang may provide the language of the text contained in the comment similarly to the UserDescriptionProperty.

[0282] Figure 5 The main steps of the process of packaging one or more images in a file using the HEIF format are shown. Computing device 600 ( Figure 6 ) can apply this processing, for example.

[0283] The device 600 obtains several viewpoint shots to construct a panoramic view from the scene. Between each viewpoint shot, the device is moved according to a predetermined panoramic direction, which may be up to 360° (e.g., forming a line or curve from left to right or from top to bottom, or forming a grid with a given scanning order).

[0284] At step 501, for each viewing angle shooting, the device determines whether the bracketing exposure mode is currently activated, that is, whether multiple images should be shot for a given viewing angle to form a bracketing exposure image set according to a given bracketing exposure mode (e.g., automatic bracketing exposure, focus bracketing exposure, white balance bracketing exposure, super-resolution bracketing exposure, depth of field bracketing exposure, flash exposure bracketing exposure, etc.). Bracketing exposure includes shooting a series of images, and each image in the series is shot using a camera parameter with different values. For example, three images of automatic bracketing exposure may include a first image with a low exposure time, a second image with an intermediate exposure time, and a third image with a high exposure time.

[0285] If the bracketing mode is activated at step 501 , the device obtains a series of images at step 504 according to the bracketing mode parameters (number of images, image capture configuration parameters) configured in the device or selected by the user.

[0286] At step 505, each image in the series of images is encoded (e.g., using HEVC, JPEG, RAW, or any other image encoding format) and encapsulated in a HEIF file as a new coded image item. An EntityToGroupBox that references the series of coded image items is defined with a grouping type corresponding to the exposure bracketing mode. For example, grouping type "aebr" is used for automatic exposure bracketing or "fobr" is used for focus exposure bracketing. Optionally, item attributes are associated with each coded image item to describe the exposure bracketing parameter values ​​for each image.

[0287] Instead, each image in the series of images is encoded and packaged in the HEIF file as a new sample in the track. The reference track EntityToGroupBox is defined with a grouping type corresponding to the above-mentioned bracketing mode. The sample grouping mechanism can be used to associate each sample with the bracketing parameter value of each image (described in a separate SampleGroupDescriptionEntry).

[0288] If the bracketing mode is not activated at step 501 , the device obtains a single image of the viewing angle at step 502 , and encodes the image (in any image encoding format) and encapsulates it as an encoded image item in a HEIF file at step 503 .

[0289] At step 506 , if the last shooting angle of view forming the panoramic angle of view has not been reached, the previous steps are repeated.

[0290] Finally, at step 507, a derived image is created as a derived image item or a pre-derived encoded image item according to one of the above-described embodiments and is encapsulated in a HEIF file to describe a panoramic perspective with reference to the EntityToGroupBox or image item created at steps 505 and 503.

[0291] If the panorama is created as a pre-derived coded image item, the panoramic image is calculated from the images taken at steps 502 and 504. The created panoramic image is encoded (in any image encoding format) according to one of the above embodiments and packaged as a pre-derived coded image item and references the EntityToGroupBoxes or images created at steps 505 and 503.

[0292] Figure 6 is a schematic block diagram of a computing device 600 for implementing one or more embodiments of the present invention. The computing device 600 may be a device such as a microcomputer, a workstation, or a lightweight portable device, such as a mobile phone, a tablet computer, or a still or video camera. The computing device 600 includes a communication bus connected to:

[0293] - a central processing unit 601 denoted as CPU, such as a microprocessor or the like;

[0294] - A random access memory 602 marked as RAM, used to store executable code of the method according to the embodiment of the present invention and registers suitable for recording variables and parameters, which are necessary for implementing the method according to the embodiment of the present invention. The memory capacity of the random access memory can be expanded, for example, by connecting to an optional RAM of the expansion port;

[0295] - a read-only memory 603 marked as ROM, used to store a computer program for implementing an embodiment of the present invention;

[0296] - A network interface 604, which is usually connected to a communication network through which digital data to be processed is sent or received. The network interface 604 may be a single network interface, or may be composed of a collection of different network interfaces (e.g., wired and wireless interfaces, or different kinds of wired or wireless interfaces). Under the control of a software application running in the CPU 601, data packets are written to the network interface for sending, or data are read from the network interface for receiving;

[0297] - User interface 605 may be used to receive input from a user or display information to a user;

[0298] - A hard disk 606 labeled as HD can be provided as a mass storage device;

[0299] - The I / O module 607 may be used to receive / send data from / to an external device (such as a video source or a display, etc.).

[0300] The executable code may be stored in the read-only memory 603, may be stored on the hard disk 606, or may be stored, for example, on a removable digital medium such as a disk, etc. According to a variant, the executable code of the program may be received via the network interface 604 by means of a communication network so that the executable code of the program is stored in one of the storage components of the communication device 600 such as the hard disk 606, etc., before being executed.

[0301] The central processing unit 601 is adapted to control and direct the execution of instructions or parts of software codes of one or more programs according to embodiments of the present invention, which are stored in one of the aforementioned storage components. After power is turned on, the CPU 601 can execute instructions from the main RAM memory 602 related to the software application after loading these instructions, for example from the program ROM 603 or the hard disk (HD) 606. Such a software application, when executed by the CPU 601, causes the steps of the flowchart of the present invention to be performed.

[0302] Any step of the algorithm of the present invention may be implemented in software by executing instructions or a set of programs by a programmable computing machine (such as a PC ("personal computer"), a DSP ("digital signal processor") or a microcontroller, etc.); or may be implemented in hardware by a machine or a dedicated component (such as an FPGA ("field programmable gate array") or an ASIC ("application-specific integrated circuit"), etc.).

[0303] Although the present invention has been described above with reference to specific embodiments, the present invention is not limited to the specific embodiments, and modifications within the scope of the present invention will be apparent to those skilled in the art.

[0304] Many further modifications and variations will occur to those skilled in the art when referring to the foregoing illustrative embodiments, which are given as examples only and are not intended to limit the scope of the invention, which is determined solely by the appended claims. In particular, different features from different embodiments may be interchanged where appropriate.

[0305] The various embodiments of the present invention described above may be implemented individually or as a combination of multiple embodiments. In addition, features from different embodiments may be combined when necessary or when a combination of elements or features from separate embodiments is beneficial in a single embodiment.

[0306] Each feature disclosed in this specification (including any accompanying claims, abstracts and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly specified otherwise. Therefore, unless expressly specified otherwise, each feature disclosed is only one example of a general series of equivalent or similar features.

[0307] In the claims, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality. The mere fact that different features are recited in mutually different dependent claims does not indicate that a combination of these features cannot be used to advantage.

Claims

1. A method for encapsulating media data in a media file conforming to the ISOBMFF standard, wherein: The method comprises: generating a first grouping structure describing a first group of entities, the first group of entities representing a plurality of images captured to generate a panorama, each entity in the first group of entities being associated with at least a portion of the media data; and embedding the first packet structure and the media data into the media file, in, The entities in the first entity group are second grouping structures describing a second entity group identifying at least a portion of the plurality of images, the second entity group representing a bracketing exposure set, or The first entity group includes a single entity, the single entity is a track corresponding to a sequence of samples including the plurality of images, the track includes a plurality of third grouping structures, each third grouping structure represents a bracketing exposure set, Each bracketing exposure set represents one of the viewing angles constituting the panorama.

2. The method according to claim 1, wherein: The first grouping structure is an EntityToGroupBox representing a panoramic entity group and including a grouping type equal to "pano".

3. The method according to claim 1 or 2, wherein: The second grouping structure is EntityToGroupBox.

4. The method according to claim 1, wherein: The third grouping structure is SampleToGroupBox.

5. The method according to claim 1, in, a descriptive item attribute is associated with the first grouping structure, The descriptive item attributes provide parameters of the panorama described by the first grouping structure.

6. The method according to claim 5, wherein: The descriptive item attributes include at least one of the following: Panoramic direction, An integer specifying the number of rows in the grid panorama minus 1. An integer specifying the number of columns in the grid panorama minus 1.

7. The method according to claim 5 or 6, wherein: The descriptive item attribute has type equal to "pano".

8. The method according to claim 1, wherein: At least one of the entities in the first entity group and / or the second entity group is associated with an attribute comprising timing information.

9. The method according to claim 3, wherein: At least one entity in the second group of entities is an image item.

10. The method according to claim 4, wherein: SampleToGroupBox boxes with different values ​​of the grouping type parameter represent different sets of bracketed exposures.

11. A method for encapsulating media data in a media file conforming to the ISOBMFF standard, wherein: The method comprises: Generate metadata, the metadata including: (i) an item property container box including at least one of creation time and modification time of one or more items or one or more EntityToGroupBox as item properties, and (ii) an item property association box, which associates the one or more items or the one or more EntityToGroupBoxes with the item properties included in the item property container box, each item in the one or more items or each entity in the one or more EntityToGroupBoxes being related to at least a portion of the media data; and The generated metadata and the media data are embedded in the media file.

12. A method for reading media data in a media file conforming to the ISOBMFF standard, wherein: The method comprises: Obtaining a first grouping structure describing a first entity group from the media file, the first entity group representing a plurality of images captured to generate a panorama, each entity in the first entity group being associated with at least a portion of the media data; and obtaining, from the media files, media files related to each entity in the first entity group, wherein the entity in the first entity group is a second grouping structure describing a second entity group identifying at least a portion of the plurality of images, the second entity group representing a bracketing exposure set, or The first entity group includes a single entity, the single entity is a track corresponding to a sequence of samples including the plurality of images, the track includes a plurality of third grouping structures, each third grouping structure represents a bracketing exposure set, Each bracketing exposure set represents one of the viewing angles constituting the panorama.

13. The method according to claim 12, wherein: The first grouping structure is an EntityToGroupBox representing a panoramic entity group and including a grouping type equal to "pano", the second grouping structure is an EntityToGroupBox, and the third grouping structure is a SampleToGroupBox.

14. A device for encapsulating media data in a media file conforming to the ISOBMFF standard or reading media data from a media file conforming to the ISOBMFF standard, the device comprising a processing unit configured to perform the steps of the method according to any one of claims 1 to 13.

15. A non-transitory computer-readable storage medium storing instructions of a computer program for causing a processor to implement the method according to any one of claims 1 to 13.