3rd generation partnership project (3gpp) framework for live uplink streaming (flus) sink capabilities determination

1. A method for determining 3rd Generation Partnership Project (3GPP) Framework for Live Uplink Streaming (FLUS) sink capabilities, executable by a processor, comprising:

signaling a capability description object using at least a first attribute and a second attribute, wherein the capability description object describes a capability supported by a FLUS sink, and wherein the capability is from a list of capabilities supported by the FLUS sink,

wherein the first attribute comprises a location from which a capability description can be retrieved,

wherein the second attribute comprises a first scheme identifier that comprises a descriptor that identifies a FLUS sink capability, and

wherein signaling the capability description object enables interoperability between the FLUS sink and a source from a plurality of vendors.

2. The method of claim 1 , wherein the capability description object corresponds to a standard.

3. The method of claim 2 , wherein the standard is identified by a universal resource identifier corresponding to the first scheme identifier.

4. The method of claim 1 , wherein the capability description object comprises a second scheme identifier, wherein the second scheme identifier comprises a title, an input file type, and an output file type.

5. The method of claim 1 , wherein the location corresponds to a URL.

6. The method of claim 1 , wherein the source retrieves a resource description from the FLUS sink based on the first attribute and the second attribute.

7. The method of claim 1 , wherein a format of the capability description object and the first scheme identifier are defined by a scheme owner.

8. A computer system for determining 3rd Generation Partnership Project (3GPP) Framework for Live Uplink Streaming (FLUS) sink capabilities, the computer system comprising:

one or more computer-readable non-transitory storage media configured to store computer program code; and

one or more computer processors configured to access said computer program code and operate as instructed by said computer program code, said computer program code including:

signaling code configured to cause the one or more computer processors to signal a capability description object using at least a first attribute and a second attribute, wherein the capability description object describes a capability supported by a FLUS sink, and wherein the capability is from a list of capabilities supported by the FLUS sink,

wherein the first attribute comprises a location from which the capability description can be retrieved,

wherein the second attribute comprises a first scheme identifier that comprises descriptor that identifies a FLUS sink capability, and

wherein signaling the capability description object enables interoperability between the FLUS sink and a source from a plurality of vendors.

9. The computer system of claim 8 , wherein the capability description object corresponds to a standard.

10. The computer system of claim 9 , wherein the standard is identified by a universal resource identifier corresponding to the first scheme identifier.

11. The computer system of claim 8 , wherein the capability description object comprises a second scheme identifier, wherein the second scheme identifier comprises a title, an input file type, and an output file type.

12. The computer system of claim 8 , wherein the location corresponds to a URL.

13. The computer system of claim 8 , wherein the source retrieves a resource description from the FLUS sink based on the first attribute and the second attribute.

14. The computer system of claim 8 , wherein a format of the capability description object and the first scheme identifier are defined by a scheme owner.

15. A non-transitory computer readable medium having stored thereon a computer program for determining 3rd Generation Partnership Project (3GPP) Framework for Live Uplink Streaming (FLUS) sink capabilities, the computer program configured to cause one or more computer processors to:

signal a capability description object using at least a first attribute and a second attribute, wherein the capability description object describes a capability supported by a FLUS sink, and wherein the capability is from a list of capabilities supported by the FLUS sink,

wherein the first attribute comprises a location from which a capability description can be retrieved,

wherein the second attribute comprises a first scheme identifier that comprises a descriptor that identifies a FLUS sink capability, and

wherein signaling the capability description object enables interoperability between the FLUS sink and a source from a plurality of vendors.

16. The non-transitory computer readable medium of claim 15 , wherein the capability description object corresponds to a standard.

17. The non-transitory computer readable medium of claim 16 , wherein the standard is identified by a universal resource identifier corresponding to the first scheme identifier.

18. The non-transitory computer readable medium of claim 15 , wherein the capability description object comprises a second scheme identifier, wherein the second scheme identifier comprises a title, an input file type, and an output file type.

19. The non-transitory computer readable medium of claim 15 , wherein the location corresponds to a URL.

20. The non-transitory computer readable medium of claim 15 , wherein the source retrieves a resource description from the FLUS sink based on the first attribute and the second attribute.