基于打包和分发方案的迁移指南Packaging and delivery scenario-based migration guidance

迁移指南徽标


迁移步骤 2

本文为你提供了基于打包和分发方案的指南,可帮助你从 Azure 媒体服务 v2 迁移到 v3。This article gives you scenario-based guidance for packaging and delivery that will assist you in migrating from Azure Media Services v2 to v3.

V3 API 中内容发布方式的重大更改。Major changes to the way content is published in v3 API. 新的发布模型已简化,可使用更少的实体来创建流式处理定位符。The new publishing model is simplified and uses fewer entities to create a Streaming Locator. API 缩减到只有两个实体,而之前需要四个实体。The API reduced down to just two entities vs. the four entities previously required. 内容密钥策略和流式处理定位符现在替代了对 ContentKeyAuthoriationPolicyAssetDeliveyPolicyContentKeyAccessPolicy 的需求。Content Key Policies and Streaming Locators now replace the need for ContentKeyAuthoriationPolicy, AssetDeliveyPolicy, ContentKey, and AccessPolicy.

V3 中的打包和分发Packaging and delivery in v3

  1. 创建内容密钥策略Create Content Key Policies.
  2. 创建流式处理定位符Create Streaming Locators.
  3. 获取流式处理路径Get the Streaming paths
    1. 针对 DASHHLS 播放器进行配置。Configure it for a DASH or HLS player.

有关具体步骤,请参阅以下发布概念、教程和操作指南。See publishing concepts, tutorials and how to guides below for specific steps.

发布概念、教程和操作指南Publishing concepts, tutorials and how to guides

概念Concepts

操作方法指南How to guides

示例Samples

还可比较代码示例中的 V2 和 V3 代码You can also compare the V2 and V3 code in the code samples.

后续步骤Next steps

步骤 1Step 1

了解迁移到媒体服务 API V3 的优势Understand the benefits of migrating to Media Services API V3.

步骤 2Step 2

了解媒体服务 V2 API 与 V3 API 之间的区别。Understand the differences between Media Services V2 API and the V3 API.

步骤 3Step 3

了解 SDK 区别,并进行设置以迁移到 V3 REST API 或客户端 SDKUnderstand the SDK differences and set up to migrate to the V3 REST API or client SDK.

步骤 4Step 4

你的媒体服务 V2 的应用程序可能是唯一的。Your application of Media Services V2 may be unique. 因此,我们基于你过去可能使用媒体服务的方式以及该服务每个功能的步骤提供了指导,例如:Therefore, we have provided guidance based on how you may have used media services in the past and the steps for each feature of the service such as: