Content Delivery Options
One of the first things to decide after you create your Beacon account is how you plan to deliver your video files. Beacon offers many choices that have a variety of advantages and limitations. The delivery method you choose depends on how protected you want your video files to be, how you would like to reach your audience, your preferred method of upload, whether or not your video assets are already stored on another CDN (Content Delivery Network or Content Distribution Network), and so forth.
The content delivery options described in this topic are available only for Beacon Enterprise publishers. Beacon Enterprise and Express publishers must use Brightcove as their CDN.
In this topic, you will learn:
- What is a CDN?
- Can I deliver my content without a CDN?
- How is my media content delivered? (Progressive Download vs. Streaming)
- Comparing content delivery: Brightcove-hosted video assets vs. BYO vs. remote assets
- Configuring content delivery to use BYO CDN or remote assets
- What CDNs does Brightcove support for BYO CDN?
- Beacon reporting and BYO CDN or remote assets
What is a CDN?
Publishers use CDNs to distribute their media widely to viewers online. Wikipedia defines a CDN as:
A content delivery network or content distribution network (CDN) is a system of computers networked together across the Internet that cooperate transparently to deliver content most often for the purpose of improving performance, scalability, and cost efficiency, to end users.
There are many commercially available CDNs. If you are a Beacon Enterprise or Express publisher, Brightcove is your CDN solution. If you are a Beacon Enterprise publisher, then you can choose to deliver your content using the Brightcove CDN or over any CDN that Beacon supports.
Can I deliver my content without a CDN?
If you are expecting low volumes of traffic or have complete control over traffic to your videos, you may not need a CDN to serve your videos. For example, some publishers want to distribute their content on an internal wiki or private network. It is possible that your system can handle delivery of media without requiring an external CDN. If you would like more information on how Brightcove can support this set-up, please contact Brightcove Customer Support or your Customer Success Manager.
How is my media content delivered?
There are several types of content delivery mechanisms:
Streaming (also called HLS or DASH)
Streaming video is delivered via a streaming server without the file ever being downloaded to the viewer’s computer/device. As soon as the viewer presses play, the video will start to play. If the user decides to forward or skip to some other part of the video, he/she can do it immediately and the video will continue to play from that point onwards. One of the advantages of streaming media is that bandwidth is only used for video that the viewer has watched, as only the watched portion of the video has been delivered. Nothing is kept on the client side; everything is on the server side.
Streaming is useful in situations where you want or need to do the following:
- Deliver long files (10 minutes or longer) or high-bitrate files (high-definition)
- Take advantage of the Beacon multi-bitrate streaming feature, which performs bandwidth detection and delivers the best quality for available hardware; you can use multi-bitrate streaming with progressive download, however, bandwidth detection occurs only at the beginning of playback and the player doesn't adapt to changes in the viewer's bandwidth
- Serve more streams with less bandwidth
Streaming to iOS devices
Apple iOS devices support only Apple HTTP Live Streaming (HLS) and HTTP (progressive download) for delivery of video files. You need to ensure either that your videos have one or more available HLS renditions. The App Store rules call for the use of Apple HTTP Live Streaming for long form video content (greater than 5 Mb or 10 minutes).
Streaming key points:
- Video content is secured via a temporary video link
- Advancing video is possible
- Effectively utilizes Beacon’s dynamic delivery feature
- Allows you to serve more steams with less bandwidth
- Apple HTTP Live Streaming (HLS) or Real Time Messaging Protocol (RTMP) protocols in use
In practice you will very rarely realize whether content has been streamed or progressively downloaded unless you look for some of the distinguished features as described above.
Progressive download (also called PD)
When you deliver your content using progressive download, the file is served from a standard web server through an HTTP request, just like a normal web page or any other downloadable document. When the video is played, the video file is downloaded to the viewer's computer or device and stored in a temporary directory. The video will begin to play when enough of the file has has been downloaded to the computer/device. If the viewer wants to fast forward or skip to another part of the video, he/she will only be able to do so if that part of the video has already been downloaded and stored. In comparison to streaming video, there's really only one consistent benefit to progressive download—you don't need a streaming server to deliver the video. Progressive download video can be served from any normal web server.
Progressive download is fine for hobbyists or websites that have low traffic requirements, don't mind if their content is cached on the viewer's computer/device, and if you only need to deliver shorter length videos (under 10 minutes). Publishers who need advanced features and control over their video delivery, and/or those who need to display video to larger audiences (several hundred or more simultaneous viewers), need to track and report usage or viewing statistics for the video, or want to offer the best interactive playback experience, will need to stream their video. Streaming delivery also consumes less bandwidth than progressive delivery because only the portion of the video that is watched is actually delivered.
Progressive download key points:
- Limited seek and navigation capabilities
- Viewers can access and re-purpose content
- Does not effectively utilize Beacon’s dynamic delivery feature
- Less secure and content can be easily copied
- More bandwidth is used as all parts of the video are downloaded, not just the watched ones
How are image assets delivered?
Regardless of whether you use streaming or progressive download for your video content, images delivered to end users in the Brightcove Player (thumbnails and video stills, for example) are delivered via HTTP download.
Also see the subsection below on images and BYO CDNS.
Comparing content delivery: Brightcove-hosted video assets vs. BYO vs. remote assets
Beacon supports a few basic CDN configurations, depending on your CDN provider and setup. The choices are:
You can also choose to use your own choice of CDN (BYO CDN or "bring your own bandwidth"). In this case, depending on the agreement with your CDN provider, your videos will be delivered seamlessly through Brightcove Players using either Progressive Download (PD) or streaming mechanisms. If you choose BYO CDN, you can use the Beacon pull-based ingestion to ingest content into your Beacon account, which then gets moved to your CDN provider for delivery to end users through your Brightcove Players.
Does Dynamic Delivery support BYO CDN publishers?
Dynamic Delivery allows publishers to take advantage of their own CDN relationships, however, all video assets must be managed by the Brightcove Origin. Please contact your Customer Success Manager for more information.
Playback API (including images displayed in the Brightcove web and SDK players)
- For accounts created after Mon 10 May 2021 10:23:47 UTC, images will automatically be returned from the BYO CDN.
- For older accounts, images are returned from the Brightcove house CDN, which will result in bandwidth charges. You can submit a request to Support to allow the Playback API to return images from the BYO CDN.
Currently images returned via the CMS API returned from the Brightcove house CDN, and will therefore result in bandwidth charges. Depending on why and how you are retrieving images via the CMS API, you may be able to use the Playback API instead, which could save bandwidth charges (see above).
You can choose to use a Brightcove CDN. Beacon leverages Akamai, Fastly, and other Tier 1 CDNs to offer both streaming and progressive download delivery for your video content. Generally HLS or DASH streaming is used, and progressive download only used in special cases or to provide a downloadable rendition of the video.
The final choice is remote assets. In this case, you may already have your video files stored on your CDN and you do not want to use the Beacon uploading tools at all to add new content. You can use either the Beacon Media module, the Dynamic Ingest API, or the CMS API to create videos in your Beacon account that point to the underlying video assets stored remotely by your CDN provider.
When you create videos with remote assets you cannot use the image capture feature to create video still and thumbnail images for remote asset videos. Video still and thumbnail images can be uploaded for remote asset videos.
For information on using remote assets, see Working with Remote Asset Videos.
It is possible to configure a Beacon account to use both BYO CDN and remote assets. For example, if some of your video content is already available on your CDN, you may want to use remote assets for your existing content to avoid uploading it again, and use BYO CDN for new uploads going forward. Contact us if you require this set-up. You may also be able to create multiple Beacon accounts, each with a different content delivery strategy.
Configuring content delivery to use BYO CDN or remote assets
Here are the main steps for getting set up with BYO CDN or remote assets:
- Set up an account with a CDN (see the following section to see the ones currently supported).
- If you have existing video content that you need to migrate (from Brightcove or an outside CDN), please contact our Services team.
- Contact your Brightcove Customer Success Manager to complete the set-up.
What CDNs does Beacon support for BYO CDN?
Beacon supports the following major CDNs for BYOB CDN content delivery:
Other BYO CDNs may be supported, but feature support will vary. Contact Sales or your Customer Success Manager for more information.
Supported features for BYO CDNs
The following features are supported for BYO CDNs:
- HTTPS only
- Signed manifest URLs
- Signed content URLs (for the CDNs listed above only)
- CDN Geo-Restriction (if supported by the CDN)
- CDN IP-Restriction (if supported by the CDN)
- Custom TTL settings (if supported by the CDN)
Beacon reporting and BYO CDN or remote assets
If you use BYO CDN or remote assets, your gigabytes downloaded will not appear in the Beacon Studio Analytics for any videos or players, since we are not integrated with your CDN. (You will see viewed minutes, because those are reported by the Brightcove Player.) You should be getting these reports directly from your CDN provider. You may still see gigabytes downloaded in the Beacon reports for your "non-video" content, that is, for bandwidth usage incurred for Brightcove Players, images, etc.