Method and apparatus for media scene description

Abstract

To provide systems, methods, and devices for managing media storage and delivery.SOLUTION: Systems, methods, and devices include the steps of: obtaining, by a media access function (MAF), a glTF file corresponding to a scene; determining that the glTF file has a CBOR format; converting the glTF file into a converted glTF file having a JSON format using a first CBOR parser function implemented by the MAF; and obtaining media content corresponding to the scene based on the converted glTF file.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 137,274, filed January 14, 2021, and U.S. Patent Application No. 17 / 477,134, filed September 16, 2021, the disclosures of which are incorporated herein by reference in their entireties.

[0002] Embodiments of the present disclosure relate to a system design for supporting media objects using 3D modeling syntax, implementing a media syntax that supports various media codecs, containers, and formats, managing media storage and delivery methods through predetermined programming interfaces, and providing media buffer control and rendering capabilities. [Background technology]

[0003] glTF (Graphics Language Transmission Format) is an API-neutral runtime asset 3D modeling distribution format. Compared to traditional 3D modeling tools, glTF provides a more efficient, extensible, and interoperable format for transmitting and loading 3D content. glTF 2.0 is the latest version of the glTF specification written by the Khronos 3D Group. This format supports simple scene graph formats, including "png" and "jpeg" image formats, that can generally support static (untimed) objects in a scene. glTF 2.0 supports simple animation, including support for translation, rotation, and scaling of basic shapes, i.e., geometric objects, described using glTF primitives. glTF 2.0 does not support timed media, and therefore does not support video or audio.

[0004] "Information technology - Coding of audiovisual objects - Part 12: ISO base media file format", ISO / IEC 14496-12 (December 2015), "Draft of FDIS of ISO / IEC 23000-19 Common Media Application Format for Segmented Media", ISO / IEC JTC1 / SC29 / WG11 MPEG117 / 16819 (April 2017), and "Text of ISO / IEC FDIS 23009-1 4th edition", ISO / IEC JTC 1 / SC 29 / WG 11 N18609 (August 2019), as well as the glTF 2.0 specification, are incorporated herein by reference in their entireties. Summary of the Invention [Means for solving the problem]

[0005] According to one embodiment, a method for managing media storage and distribution is performed by at least one processor and includes the steps of: obtaining, by a media access function (MAF), a glTF file corresponding to a scene; determining that the glTF file has a CBOR format; converting the glTF file into a converted glTF file having a JSON format using a first CBOR parser function implemented by the MAF; and obtaining media content corresponding to the scene based on the converted glTF file.

[0006] According to one embodiment, a device for managing media storage and distribution includes at least one memory configured to store program code; and at least one processor configured to read the program code and operate as instructed by the program code, the program code including: a first acquisition code configured to cause the at least one processor to acquire a glTF file corresponding to a scene via a Media Access Function (MAF); a first determination code configured to cause the at least one processor to determine that the glTF file has a CBOR format; a first conversion code configured to cause the at least one processor to convert the glTF file into a converted glTF file having a JSON format using a first CBOR parser function implemented by the MAF; and a second acquisition code configured to cause the at least one processor to acquire media content corresponding to the scene based on the converted glTF file.

[0007] According to one embodiment, a non-transitory computer-readable medium has stored thereon instructions, the instructions including one or more instructions that, when executed by at least one processor of a device for managing media storage and delivery, are configured to cause the at least one processor to obtain, via a media access function (MAF), a glTF file corresponding to a scene; determine that the glTF file has a CBOR format; convert the glTF file into a converted glTF file having a JSON format using a first CBOR parser function implemented by the MAF; and obtain media content corresponding to the scene based on the converted glTF file.

[0008] Further features, nature and various advantages of the disclosed subject matter will become more apparent from the following detailed description and accompanying drawings. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram of an environment in which the methods, apparatus, and systems described herein may be implemented, according to an embodiment. [Figure 2] 2 is a block diagram of example components of one or more devices of FIG. 1, according to an embodiment. [Figure 3] FIG. 1 is a schematic diagram of a glTF scene description object, according to an embodiment. [Figure 4] FIG. 1 is a schematic diagram of a media scene description system reference architecture, according to an embodiment. [Figure 5] 1 is an example of a glTF JSON (JavaScript Object Notation) format representation, according to an embodiment. [Figure 6] 1 is an example of an MPEG glTF extension, according to an embodiment. [Figure 7A] FIG. 1 is a diagram of a file having a JSON format, according to an embodiment. [Figure 7B] FIG. 1 is a diagram of a file having a CBOR format, according to an embodiment. [Figure 8] FIG. 1 is a diagram of an example of glTF syntax, according to an embodiment. [Figure 9A] FIG. 2 is a diagram of an exemplary process for managing media storage and delivery, according to an embodiment. [Figure 9B] FIG. 2 is a diagram of an exemplary process for managing media storage and delivery, according to an embodiment. [Figure 9C] FIG. 2 is a diagram of an exemplary process for managing media storage and delivery, according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] 1 is a diagram of an environment 100 in which the methods, apparatus, and systems described herein may be implemented, according to an embodiment. As shown in FIG. 1, environment 100 may include a user device 110, a platform 120, and a network 130. The devices of environment 100 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0011] User device 110 includes one or more devices that can receive, generate, store, process, and / or provide information associated with platform 120. For example, user device 110 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smartphone, a wireless phone, etc.), a wearable device (e.g., smart glasses, a smart watch, etc.), or a similar device. In some implementations, user device 110 may receive information from and / or transmit information to platform 120.

[0012] Platform 120 includes one or more devices as described elsewhere herein. In some implementations, platform 120 may include a cloud server or a collection of cloud servers. In some implementations, platform 120 may be designed modularly so that software components can be swapped in or out according to particular needs. As such, platform 120 may be easily and / or quickly reconfigured for different uses.

[0013] In some implementations, as shown, platform 120 may be hosted under cloud computing environment 122. Notably, although the implementations described herein describe platform 120 as being hosted within cloud computing environment 122, in some implementations platform 120 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0014] Cloud computing environment 122 includes an environment that hosts platform 120. Cloud computing environment 122 may provide services such as computation, software, data access, and storage that do not require end-user (e.g., user device 110) knowledge of the physical location and configuration of the system(s) and / or device(s) that host platform 120. As shown, cloud computing environment 122 may include a collection of computing resources 124 (collectively referred to as “computing resources 124” and individually as “computing resource 124”).

[0015] Computing resources 124 include one or more personal computers, workstation computers, server devices, or other types of computing and / or communication devices. In some implementations, computing resources 124 may host platform 120. Cloud resources may include compute instances running within computing resources 124, storage devices provided within computing resources 124, data transfer devices provided by computing resources 124, etc. In some implementations, computing resources 124 may communicate with other computing resources 124 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0016] As further shown in FIG. 1, the computing resources 124 include cloud resources such as one or more applications (“APPs”) 124-1, one or more virtual machines (“VMs”) 124-2, virtualized storage (“VSs”) 124-3, and one or more hypervisors (“HYPs”) 124-4.

[0017] The application 124-1 includes one or more software applications that may be provided to or accessed by the user device 110 and / or the platform 120. The application 124-1 may eliminate the need to install and run a software application on the user device 110. For example, the application 124-1 may include software associated with the platform 120 and / or any other software that may be provided via the cloud computing environment 122. In some implementations, one application 124-1 may send information to / receive information from one or more other applications 124-1 via the virtual machine 124-2.

[0018] The virtual machine 124-2 comprises a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. The virtual machine 124-2 can be either a system virtual machine or a process virtual machine, depending on the use by the virtual machine 124-2 and the degree of correspondence with any real machine. A system virtual machine may provide a complete system platform that supports the execution of a complete operating system (“OS”). A process virtual machine may execute a single program and support a single process. In some implementations, the virtual machine 124-2 may run on behalf of a user (e.g., user device 110) and manage the infrastructure of the cloud computing environment 122, such as data management, synchronization, and long-term data transfers.

[0019] Virtualized storage 124-3 includes one or more storage systems and / or one or more devices that use virtualization techniques within the storage systems or devices of computing resource 124. In some implementations, within the context of a storage system, types of virtualization may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of logical storage from physical storage such that the storage system may be accessed without regard for the physical storage or heterogeneity. This separation may provide flexibility in how storage system administrators manage end-user storage. File virtualization may eliminate the dependency between data accessed at the file level and where the file is physically stored. This may enable optimization of storage usage, server consolidation, and / or non-disruptive file migration.

[0020] The hypervisor 124-4 may provide hardware virtualization technology that allows multiple operating systems (e.g., "guest operating systems") to run simultaneously on a host computer, such as the computing resource 124. The hypervisor 124-4 may present a virtual operating platform to the guest operating systems and manage the execution of the guest operating systems. Multiple instances of different operating systems may share virtualized hardware resources.

[0021] Network 130 includes one or more wired and / or wireless networks. For example, network 130 may be a cellular network (e.g., a fifth-generation (5G) network, a long-term evolution (LTE) network, a third-generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, an optical fiber-based network, etc., and / or a combination of these or other types of networks.

[0022] The number and arrangement of devices and networks shown in Figure 1 are provided as an example. In practice, there may be additional, fewer, different, or differently arranged devices and / or networks than those shown in Figure 1. Furthermore, two or more devices shown in Figure 1 may be implemented within a single device, or a single device shown in Figure 1 may be implemented as multiple distributed devices. Additionally or alternatively, a set of devices (e.g., one or more devices) of environment 100 may perform one or more functions described as being performed by another set of devices of environment 100.

[0023] Figure 2 is a block diagram of example components of one or more devices of Figure 1. Device 200 may correspond to user device 110 and / or platform 120. As shown in Figure 2, device 200 may include a bus 210, a processor 220, a memory 230, a storage component 240, an input component 250, an output component 260, and a communication interface 270.

[0024] Bus 210 includes components that enable communication between components of device 200. Processor 220 is implemented in hardware, firmware, or a combination of hardware and software. Processor 220 is a central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), microprocessor, microcontroller, digital signal processor (DSP), field programmable gate array (FPGA), application specific integrated circuit (ASIC), or another type of processing component. In some implementations, processor 220 includes one or more processors that can be programmed to perform functions. Memory 230 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by processor 220.

[0025] Storage component 240 stores information and / or software related to the operation and use of device 200. For example, storage component 240 may include a hard disk (e.g., a magnetic disk, optical disk, magneto-optical disk, and / or solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cartridge, magnetic tape, and / or another type of non-transitory computer-readable medium with a corresponding drive.

[0026] Input components 250 include components that enable device 200 to receive information, such as via user input (e.g., a touchscreen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, input components 250 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output components 260 include components that provide output information from device 200 (e.g., a display, a speaker, and / or one or more light-emitting diodes (LEDs)).

[0027] Communications interface 270 includes transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communications interface 270 may enable device 200 to receive information from and / or provide information to another device. For example, communications interface 270 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0028] Device 200 may perform one or more processes described herein. Device 200 may perform these processes in response to processor 220 executing software instructions stored by a non-transitory computer-readable medium, such as memory 230 and / or storage component 240. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

[0029] Software instructions may be loaded into memory 230 and / or storage component 240 from another computer-readable medium or from another device via communications interface 270. When executed, the software instructions stored in memory 230 and / or storage component 240 may cause processor 220 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0030] The number and arrangement of components shown in Figure 2 are provided as an example. In practice, device 200 may include additional, fewer, different, or differently arranged components relative to those shown in Figure 2. Additionally or alternatively, a set of components (e.g., one or more components) of device 200 may perform one or more functions that are described as being performed by another set of components of device 200.

[0031] Referring to Figure 3, glTF (Graphics Language Transmission Format) is an application programming interface (API)-neutral runtime asset 3D modeling distribution format. Compared with traditional 3D modeling tools, glTF provides a more efficient, extensible, and interoperable format for transmitting and loading 3D content.

[0032] A glTF scene can be a combination of multiple glTF assets, which can be, for example, a JavaScript Object Notation (JSON) formatted file containing a full scene description, which can include scene objects 301, nodes 302, cameras 303, meshes 304, lights 305, animations 306, accessors 307, materials 308, skins 309, buffer views 310, techniques 311, textures 312, buffers 313, programs 314, images 315, samplers 316, shaders 317, and supporting external data.

[0033] glTF also supports external data sources that can be referenced in any of the above-mentioned scene objects. In embodiments, binary files may be used for animation 306 or other buffer-based data 313. Image files may be used for object textures 312.

[0034] Referring to Figure 5, as described above, a glTF scene may be organized in JSON format. A glTF asset may include zero or more scenes 503, which may be a set of visual objects to render. A scene may be defined in a scene array. The example shown in Figure 5 includes a single scene 506 with a single node 501, although embodiments are not limited thereto. Various parameters may be associated with each node object. For example, name 502 may specify the name of the node object, and scene name 504 may specify the name of the single scene.

[0035] glTF scene assets can be consumed by a presentation engine to render a 3D or immersive scene to the user. The existing glTF syntax only supports 3D objects, including static or computer-generated animations. There is no support for media types such as video or audio, let alone rendering video / audio media types.

[0036] On the other hand, the existing glTF is unable to describe a scene using a geographic coordinate system, and some media presentation scenarios require such features.

[0037] Therefore, there is a need to extend glTF to support media types including traditional 2D flat video, virtual reality (VR), augmented reality (AR), extended reality (XR), spatial audio, and other immersive media content. This may require extensions to support video / audio syntax and systems for media delivery and rendering.

[0038] The Moving Picture Experts Group (MPEG) has defined several extensions to the glTF specification to support immersive media content. Referring to Figure 3, the new extensions are MPEG_media 330, MPEG_scene_dynamic 331, MPEG_texture_video 333, MPEG_animation_timing 332, MPEG_audio_spatial 334, MPEG_accessor_timed 335, and MPEG_buffer_circular 336. In general, in Figure 3, elements with rounded outlines, e.g., elements 301-317, may be glTF elements, and elements with squared outlines, e.g., elements 330-336, may correspond to MPEG-based extensions to the glTF specification, although embodiments are not limited in this respect.

[0039] If the root identifier MPEG_media 330 is specified, MPEG_media may be supported. Referring to Figure 6, syntax supporting MPEG media may be declared as a top-level JSON syntax. Syntaxes 601 through 604 in Figure 6, if supported, may be presented as shown.

[0040] Scene updates may be expressed using the JSON Patch protocol, and MPEG_scene_dynamic331 may be used to support the JSON Patch protocol.

[0041] The MPEG texture video extension may provide the possibility to link a glTF texture object to the MPEG media and its corresponding track listed by the MPEG_media object, identified by MPEG_texture_video 333. The MPEG texture video extension may also provide a reference to MPEG_accessor_timed 335, where the decoded timed texture will be available.

[0042] The MPEG_audio_spatial334 extension may support multiple audio types.

[0043] To support timed data access, the buffer element may be extended to provide circular buffer functionality. This extension may be named MPEG_buffer_circular 336 and may be included as part of a glTF "buffer" object, such as buffer 313.

[0044] The above MPEG extensions may enable the creation of immersive experiences using glTF. Finally, glTF assets with MPEG extensions may be used to load into a rendering engine for visualization.

[0045] 4, a reference media scene description architecture 400 illustrates one example of how MPEG extensions may be used to support media types such as audio / video. Media content may be retrieved from external sources such as a media cloud 401 using a media search engine and media access function (MAF) 402, processed using a video decoder 403, an audio decoder 404, and other data compressors 405, buffered in a video buffer 406, an audio buffer 407, and other buffers 408, and rendered by a presentation engine 409. In some cases, the media content may be stored in local storage 410.

[0046] Referring to FIG. 4 , the MPEG scene description extension may separate the presentation engine 409 from the media search engine 402. The presentation engine 409 and the media search engine 402 may communicate through a predetermined programming interface that allows the presentation engine 409 to request media data necessary for rendering a scene. The media search engine 402 may retrieve the requested media and provide it in a timely manner in a format that the presentation engine 409 can immediately process. For example, the requested media asset may be compressed and reside on the network, so the media search engine 402 retrieves and decodes the asset and passes the resulting media data to the presentation engine 409 for rendering. The media data may be passed from the media search engine 402 to the presentation engine 409 in the form of buffers. Requests for media data may be passed from the presentation engine 409 to the media search engine 402 via a media search API. For flexible use of video decoding resources, a video decoder 403 may be used. If a video decoder 403 is used, the presentation engine 409 may provide information for the input and output formats to the video decoder 403 via an application configuration API.

[0047] As mentioned above, the glTF syntax can be expressed in a JSON file. The Internet Engineering Task Force (IETF)'s Concise Binary Object Representation (CBOR) is a concise data format compared to the traditional JSON format. CBOR is related to similar data objects like JSON in name / value pair format, but is represented compactly in binary and has much more support for key-value types. CBOR format files can be smaller than their JSON counterparts. In some cases, CBOR files can be over 50% smaller than their JSON counterparts. CBOR is registered with the Internet Assigned Numbers Authority (IANA) as "application / cbor."

[0048] CBOR can be used as one of the glTF interchangeable compressed file formats, which is also widely supported due to its compact data size and compatibility with JSON.

[0049] Information in CBOR is stored in binary format. Because many use cases for information involve machines understanding the data, binary data formats may have speed advantages over human-readable data formats like JSON or XML, which may require parsing each time a computer or machine is used to understand the stored data.

[0050] Figure 7A shows an example of a JSON-formatted file, and Figure 7B shows an example of a corresponding CBOR-formatted file. For example, the character "a" (711) in the JSON-formatted file of Figure 7A may correspond to 0x61 (721) in the CBOR-formatted file of Figure 7B. Similarly, the character "b" (712) in the JSON-formatted file of Figure 7A may correspond to 0x62 (722) in the CBOR-formatted file of Figure 7B, and the character "c" (713) in the JSON-formatted file of Figure 7A may correspond to 0x63 (723) in the CBOR-formatted file of Figure 7B.

[0051] Using CBOR for scene description may bring advantages compared to JSON in terms of smaller data size and support for multiple key-value types rather than just String objects as in JSON. A functional programming interface may be used in the presented media scene description reference architecture, more precisely in the media access function module.

[0052] As support for CBOR by glTF becomes more widespread, such support may be added to MPEG scene descriptions to, for example, increase interoperability of the glTF file format, reduce file size for local storage or caching, and reduce glTF file transfer latency with minimal processing power in MAF402.

[0053] A CBOR parser function according to an embodiment may be implemented by MAF 402 to convert CBOR input into glTF natively supported JSON format, and the CBOR parser function may also be used as a file compressor for saving large glTF files to local storage or cache 410.

[0054] The CBOR parser API provides one of the following methods: cbor2Json(), json2Cbor, save(), etc., as shown in Table 1 below.

[0055] [Table 1]

[0056] A detailed interface description may be as follows: interface InputFileParser { readonly attribute FILE inputFileName; readonly attribute FILE outputFileName; readonly attribute CBOR cborDataBlob; FILE cbor2Json()(FILE cborInput); FILE json2Cbor(FILE jsonInput); FILE cbor2Json(CBOR cborDataBlob); bool save(); };};

[0057] The above proposed functions can be used in a variety of scenarios, for example:

[0058] Referring to Figure 8, the glTF "url" or "uri" syntax may point to a CBOR binary data blob (802). In embodiments, there may be two ways to specify whether the binary is actually in CBOR data format. According to Example 1, a Multipurpose Internet Mail Extensions (MIME) type specifying "mimeTypes" in "application / cbor" (801) may be signaled. According to Example 2, the prefix "application / cbor;" may be included before the actual binary data. Examples 1 and 2 may be used together. In either case, a function called "cbor2Json(Object)" that takes the CBOR binary data may be called to parse the CBOR file format into JSON.

[0059] If the input glTF is in CBOR format, the output can be glTF by using the cbor2Json() API.

[0060] If the input is in native glTF format, no conversion may be necessary.

[0061] For local storage or caching purposes, glTF files may be saved as CBOR by using the json2Cbor() and save() interfaces.

[0062] Thus, embodiments may relate to a method for providing glTF file format interoperability with CBOR, reducing file sizes for local storage or caching, increasing data transfer rates, and reducing file transfer latency.

[0063] With reference to Figures 9A-9C, processes 900A, 900B, and 900C for managing media storage and distribution are described below.

[0064] FIG. 9A is a flow chart of an example process 900A for managing media storage and distribution.

[0065] 9A, process 900A may include obtaining a glTF file corresponding to a scene by a media access function (MAF) (block 911). In an embodiment, the MAF may correspond to MAF 402.

[0066] As further shown in FIG. 9A, process 900A may include determining that the glTF file has a CBOR format (block 912).

[0067] As shown in FIG. 9A, process 900A may include converting the glTF file into a converted glTF file having a JSON format using a first CBOR parser function implemented by MAF (block 913).

[0068] As shown in FIG. 9A, process 900A may include obtaining media content corresponding to the scene based on the converted glTF file (block 914).

[0069] In an embodiment, a converted glTF file having a JSON format may be larger than a glTF file having a CBOR format.

[0070] In embodiments, the MAF may be included in a Moving Picture Experts Group (MPEG) scene description architecture, which may correspond to media scene description architecture 400.

[0071] In an embodiment, the first CBOR parser function may be implemented using an API associated with MAF. In an embodiment, the API may correspond to any of the APIs described above.

[0072] 9B is a flowchart of an example process 900B for managing media storage and distribution. In an embodiment, one or more blocks of process 900B may be performed in combination with one or more blocks of process 900A. For example, one or more blocks of process 900B may be performed after one or more blocks of process 900A.

[0073] As shown in FIG. 9B, process 900B may include obtaining a uniform resource locator (URL) parameter from the converted glTF file that points to a binary data blob (block 921).

[0074] As further shown in FIG. 9B, the process 900B may include determining that the binary data blob has a CBOR format (block 922).

[0075] As further shown in FIG. 9B, process 900B may include converting the binary data blob into an object having a JSON format using a second CBOR parser function implemented by the MAF (block 923).

[0076] In an embodiment, a binary data blob may be determined to have a CBOR format based on a Multipurpose Internet Mail Extensions (MIME) type signaled in the glTF file.

[0077] In embodiments, a binary data blob may be determined to have a CBOR format based on a prefix included at the beginning of the binary data blob.

[0078] In an embodiment, a binary data blob may be determined to have a CBOR format based on a Multipurpose Internet Mail Extensions (MIME) type signaled in the glTF file and a prefix included at the beginning of the binary data blob.

[0079] 9C is a flowchart of an example process 900C for managing media storage and distribution. In an embodiment, one or more blocks of process 900C may be performed in combination with one or more blocks of process 900A and / or process 900B. For example, one or more blocks of process 900C may be performed after one or more blocks of process 900A or after one or more blocks of process 900B.

[0080] As shown in FIG. 9C, process 900C may include a step of reconverting the converted glTF file into a reconverted glTF file having a CBOR format (block 931) using a JSON parser function implemented by MAF.

[0081] As further shown in FIG. 9C, the process 900C may include storing the reconverted glTF file in at least one of local storage and a cache (block 932).

[0082] In an embodiment, a reconverted glTF file having a CBOR format may be smaller than a converted glTF file having a JSON format.

[0083] In embodiments, the JSON parser function may be implemented using an application programming interface associated with MAF. In embodiments, the API may correspond to any of the APIs described above.

[0084] 9A-9C illustrate exemplary blocks of processes 900A, 900B, and 900C, in some implementations, processes 900A, 900B, and 900C may include additional, fewer, different, or differently arranged blocks relative to those shown in FIGS. 9A-9C. Additionally or alternatively, two or more of the blocks of processes 900A, 900B, and 900C may be performed in parallel. In embodiments, any one or more blocks of processes 900A, 900B, and 900C may be combined with any other one or more blocks of processes 900A, 900B, and 900C in any order, and any one or more of the blocks of processes 900A, 900B, and 900C may be split or combined as needed.

[0085] Additionally, the proposed methods may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program stored on a non-transitory computer-readable medium to perform one or more of the proposed methods.

[0086] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit implementations to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0087] It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting of the implementation. Thus, it should be understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0088] Although particular feature combinations are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of possible implementations. Indeed, many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. Although each dependent claim listed below may depend directly on only one claim, the disclosure of possible implementations includes combinations of each dependent claim with all other claims in the claim set.

[0089] No element, act, or instruction used herein should be construed as essential or required unless expressly stated as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with "one or more." Where only one item is intended, the term "one" or similar language is used. Also, as used herein, terms such as "has," "have," and "having" are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless otherwise specified. [Explanation of symbols]

[0090] 100 Environment 110 User Devices 120 Platform 122 Cloud Computing Environment 124 computing resources 124-1 Application (APP) 124-2 Virtual Machine (VM) 124-3 Virtualized Storage (VS) 124-4 Hypervisor (HYP) 130 Network 200 devices 210 Bus 220 processors 230 memory 240 Storage Components 250 Input Components 260 Output Components 270 Communication Interface 301 Scene Objects 302 nodes 303 Camera 304 mesh 305 Lighting 306 Animation 307 Accessory 308 Materials 309 Skin 310 Buffer View 311 Techniques 312 Textures 313 Buffer / Data 314 Programs 315 images 316 Sampler 317 shaders 400 Media Scene Description Architecture 401 Media Cloud 402 Media Search Engine and Media Access Facility (MAF) 403 Video Decoder 404 Audio Decoder 405 Other Data Compressors 406 Video Buffer 407 Audio Buffer 408 Other Buffers 409 Presentation Engine 410 LocalStorage / Cache 501 nodes 502 Name 503 scenes 504 Scene Name 506 scenes

Claims

1. 1. A method for managing media storage and distribution, the method being performed by at least one processor and comprising: Obtaining a glTF (Graphics Language Transmission Format) file of the scene; determining the Concise Binary Object Representation (CBOR) format of the binary data blob represented by the glTF file; converting the binary data blob into an object having a JSON (JavaScript Object Notation) format; obtaining media content corresponding to the scene based on the object; A method comprising:

2. The method described in claim 1, wherein the object having the JSON format is larger than the binary data blob having the CBOR format.

3. The method of claim 1, wherein the binary data blob is determined to have the CBOR format based on a prefix included at the beginning of the binary data blob.

4. The method described in claim 1, wherein the binary data blob is determined to have the CBOR format based on a Multipurpose Internet Mail Extensions (MIME) type signaled in the glTF file and a prefix included at the beginning of the binary data blob.

5. The method of claim 1, wherein a URL parameter of the glTF file directly points to the binary data blob.

6. The binary data blob is determined to have the CBOR format based on a Multipurpose Internet Mail Extensions (MIME) type signaled in the glTF file and a prefix included at the beginning of the binary data blob; The method of claim 1 , wherein the MIME type and prefix indicate “application / cbor.”

7. The step of obtaining the glTF file is performed by a media access function (MAF), The method of claim 1 , wherein the MAF is included in a Moving Picture Experts Group (MPEG) Scene Description Architecture.

8. converting the binary data blob to the object is performed using a CBOR parser function implemented by a Media Access Facility (MAF); The method of claim 1 , wherein the CBOR parser function is implemented using an application programming interface associated with the MAF.

9. A device for managing media storage and distribution, said device comprising: at least one memory configured to store program code; at least one processor configured to read the program code and to operate as instructed by the program code; 9. A device comprising: a processor configured to:

10. A computer program causing a computer to perform the method of any one of claims 1 to 8.

Images