Granted Patent B2

US 12,360,943 · App. 18/240,078 · Granted Jul 15, 2025

Inventors: Shuai Zhao (Palo Alto, CA); Stephan Wenger (Palo Alto, CA); Shan Liu (Palo Alto, CA)

Assignee: TENCENT AMERICA LLC

G06F16/116G06T17/00G06F8/38G06T2210/32G06T2210/61

Abstract

Claims (39)

1. A method of managing media storage and delivery, the method being implemented by a Concise Binary Object Representation (CBOR) parser application programming interface (API) having at least one processor and comprising:

obtaining a Graphics Language Transmission Format (glTF) file of a scene description of a scene;

determining a CBOR format of a binary data blob indicated by the glTF file;

converting the binary data blob into an object having a JavaScript Object Notation (JSON) format; and

obtaining media content corresponding to the scene based on the object,

wherein the binary data blob is determined to have the CBOR format based on a prefix included at a beginning of the binary data blob.

2. The method of 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 determining both a Multipurpose Internet Mail Extension (MIME) type that is signaled in the glTF file and the prefix included at the beginning of the binary data blob.

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

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

wherein MIME type and the prefix both indicate “application/cbor”.

6. The method of claim 1 , wherein the MAF is included in a Moving Picture Experts Group (MPEG) scene description architecture.

7. The method of claim 1 , wherein the CBOR parser function is implemented using an application programming interface associated with the MAF.

8. A device for managing media storage and delivery, the device comprising:

at least one memory configured to store program code; and

at least one processor configured to read the program code and operate a Concise Binary Object Representation (CBOR) parser application programming interface (API) as instructed by the program code, the program code including:

first obtaining code configured to cause the at least one processor to obtain a Graphics Language Transmission Format (glTF) file of a scene description of a scene;

determining code configured to cause the at least one processor to determine a CBOR format of a binary data blob indicated by the glTF file;

converting code configured to cause the at least one processor to convert the binary data blob into an object having a JavaScript Object Notation (JSON) format; and

second obtaining code configured to cause the at least one processor to obtain media content corresponding to the scene based on the object,

wherein the binary data blob is determined to have the CBOR format based on a prefix included at a beginning of the binary data blob.

9. The device of claim 8 , wherein the object having the JSON format is larger than the binary data blob having the CBOR format.

10. The device of claim 8 , wherein the binary data blob is determined to have the CBOR format based on determining both a Multipurpose Internet Mail Extension (MIME) type that is signaled in the glTF file and the prefix included at the beginning of the binary data blob.

11. The device of claim 8 , wherein a URL parameter of the glTF file points directly to the binary data blob.

12. The device of claim 8 , wherein the binary data blob is determined to have the CBOR format based on determining both a Multipurpose Internet Mail Extension (MIME) type that is signaled in the glTF file and the prefix included at the beginning of the binary data blob, and

wherein MIME type and the prefix both indicate “application/cbor”.

13. The device of claim 8 , wherein the MAF is included in a Moving Picture Experts Group (MPEG) scene description architecture.

14. The device of claim 8 , wherein the CBOR parser function is implemented using an application programming interface associated with the MAF.

15. A non-transitory computer-readable medium storing instructions, the instructions comprising: 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, as a Concise Binary Object Representation (CBOR) parser application programming interface (API), to:

obtain a Graphics Language Transmission Format (glTF) file of a scene description of a scene;

determine a CBOR format of a binary data blob indicated by the glTF;

convert the binary data blob into an object having a JavaScript Object Notation (JSON) format; and

obtain media content corresponding to the scene based on the object,

wherein the binary data blob is determined to have the CBOR format based on a prefix included at a beginning of the binary data blob.

16. The non-transitory computer-readable medium of claim 15 , wherein the object having the JSON format is larger than the binary data blob having the CBOR format.

17. The non-transitory computer-readable medium of claim 15 , wherein the binary data blob is determined to have the CBOR format based on determining both a Multipurpose Internet Mail Extension (MIME) type that is signaled in the glTF file and the prefix included at the beginning of the binary data blob.

18. The non-transitory computer-readable medium of claim 15 , wherein a URL parameter of the glTF file points directly to the binary data blob.

19. The non-transitory computer-readable medium of claim 15 , wherein the MAF is included in a Moving Picture Experts Group (MPEG) scene description architecture.

20. The non-transitory computer-readable medium of claim 15 , wherein the CBOR parser function is implemented using an application programming interface associated with the MAF.

Continuity (3)

References Cited (20)