[MUSIC PLAYING]
SPEAKER: Hi.
The past couple of years have been transformational
for the media industry.
Viewers increasingly turn to OTT streaming platforms
for entertainment like new direct-to-consumer apps,
free ad-supported streaming TV services, et cetera.
As a content provider, your topmost priority
is to focus on your core value proposition and strength-- that
is, content creation.
With the plethora of choices available for subscribers,
it's absolutely critical to have the best content created
and available.
However, most of the content providers
spend an enormous amount of time on content delivery,
subscriber experience, and integration
between different tools.
Today, YouTube has huge global reach
and massively scalable video streaming service
with very granular and flexible monetization capabilities.
Imagine as a content provider you
get to build on the delivery infrastructure
and monetization capabilities similar to that of YouTube.
Introducing an integrated solution of Google Media
CDN and Google Ad Manager, which provides industry's best
subscriber experience by bringing together
the magic of YouTube and Google's advertising
technology.
Now, what is Media CDN?
Media CDN is Google's purpose-built media delivery
solution leveraging the same infrastructure that
is used to serve YouTube content to over 2
billion users around the world.
Over the past decade, Google has built tremendous capacity
and reach in over 200 countries and territories
and more than 1,300 cities around the globe.
Modern video applications are sensitive to fluctuations
in latency, so getting content closer to users
enables higher bitrates and reduces rebuffers,
resulting in a superior experience for the end user.
Media CDN integrates this infrastructure strength
with additional performance, security,
and extensibility features to help you deliver and scale
exceptional viewer experience.
And Google's Ad Manager's Dynamic Ad Insertion
needs no introduction.
It's an industry-leading serverside video infrastructure
technology that unifies ads within the video stream
serverside, allowing you to deliver uniquely targeted ads
to every viewer across all content and all devices.
Serving ads into the fragmented OTT landscape
can be incredibly complicated.
DAI enables seamless broadcast quality experience
with minimal latency or buffering between program
content and ads across all devices.
Let me now hand this over to my colleague,
David Lynn, who is going to show integration of these two
products.
DAVID LYNN: All right.
Let's take a look at how this integration actually plays out
and how it's implemented.
So let's assume that Google Ad Manager has already
been configured here.
We've already created a livestream.
We're just looping Big Buck Bunny on the backend
and creating a live linear stream out of that.
We've enabled token authentication,
and we've also enabled conventional path forwarding.
Let's take a look at what goes into the Media CDN piece.
We have three different routes that we're
going to configure here--
one for the master manifest, one for the media
playlists, and one for the media segments.
Now, for the master manifest, we can
see that we're matching on any master.m3u8.
We're actually going to send these straight to the Google Ad
Manager's Dynamic Ad Insertion as an origin.
Here, Dynamic Ad Insertion is actually
redirecting clients that first connect to them on stream
creation, redirect them to us.
DAI is going to generate a short duration token.
The token is going to be kept in the hdnea query parameter,
and it's going to be using the HMAC_SHA_256 algorithm
to generate an HMAC.
And so on this route, when we're serving that master manifest
from Google DAI, we will require tokens
and we will verify the HMAC against the hmac_keyset defined
here.
This keyset is holding the same authentication key
that we've uploaded to Google Ad Manager
to actually generate the original short duration token.
Here, we'll just verify it with the same shared secret.
Now, we'll also be adding signatures
to the returned master manifest.
We want to generate tokens here and generate
a Google-managed long duration token.
Because that short duration token isn't valid for long
to prevent easy link sharing, we'll
create a long duration token using a Google managed keyset.
It's going to use asymmetric Ed25519 signatures
for optimal performance and security.
And we're going to copy the ACL and ID
parameters through to this long duration token.
So now that we've passed this back,
we're given back a master manifest with the Media
Playlist URLs modified with a long duration token.
When the client comes back for those media playlists--
now matching on any M3U8 that's not a master M3U8--
we're still going to be proxying that back to the Dynamic Ad
Insertion origin here, but we will be now requiring tokens
and verifying against that long keyset
to verify the long duration token.
And now, instead of appending--
generating a new long duration token valid for another day,
we're actually just going to propagate the existing
long duration token into the URLs
for each media segment on the returned manifest.
And now for the final route, for media segments
that are going to be served, we're actually
going to point at the content origin this time,
and this is going to be actually [INAUDIBLE] content
that will be served from Media CDN's caches directly,
but filled from the content origin.
And here, again, we just require tokens.
We'll verify it with the long keyset--
these Ed25519 signatures--
and that's it.
Now that we have this set up, why don't we take a look
at what it actually looks like?
By pinging Google Ad Manager's Dynamic Ad Insertion,
it's going to give us a redirect that actually passes us back
to a Media CDN URL, but this time, it
includes the hdnea short duration token.
Once that gets sent through Media CDN,
we validate the HMAC--
make sure that it's valid--
make sure that it hasn't expired yet.
And we'll respond back with a master playlist that
includes the media playlist URLs and this edge cache
token-- a long duration token that's
going to be valid for the rest of the playback session.
When we actually pull one of these media playlists,
we're again including the long duration token this time,
getting authenticated.
And we'll return back TS segments
that include the same long duration token that's
been propagated from before.
And here, we'll also see where Ad Manager's Dynamic Ad
Insertion is playing in and actually doing
the manipulation of the manifest and inserting Direct Ad TS
segments.
Here, you'll notice there's no token attached.
These are unauthenticated ad segments,
and this probably isn't the premium content
that you care about protecting so much.
And that's it.
You can see here that we have Big Buck Bunny looping here,
and we have an exciting Nest Hub ad
that gets stitched in every so often.
There it is.
So that's all it takes--
some quick Google Ad Manager configurations,
some quick Media CDN edits involving
the dual token authentication, and you
should be up and running to personalize and monetize
your streams end-to-end with Google Cloud platform
and Google Ad Manager.
[MUSIC PLAYING]