媒体服务 V2 与 V3 之间的术语和实体更改Terminology and entity changes between Media Services V2 and V3

迁移指南徽标


迁移步骤 2

本文介绍 Azure 媒体服务 v2 与 v3 之间的术语差异。This article describes the terminology differences between Azure Media Services v2 to v3.

命名约定Naming conventions

查看适用于媒体服务 V3 资源的命名约定。Review the naming conventions that are applied to Media Services V3 resources. 还要查看命名 BlobAlso review naming blobs

术语更改Terminology changes

  • 定位器现在称为流定位器 。A Locator is now called a Streaming Locator.
  • 频道现在称为直播活动 。A Channel is now called a Live Event.
  • 节目现在称为实时输出 。A Program is now called a Live Output.
  • 任务现在称为 JobOutput,它是作业的一部分 。A Task is now called a JobOutput, which is part of a Job.

实体更改Entity changes

V2 实体V2 Entity V3 实体V3 Entity 指南Guidance 可以访问 V3Accessible to V3 已通过 V3 更新Updated by V3
AccessPolicy V3 中不存在实体 AccessPoliciesThe entity AccessPolicies doesn't exist in V3. No No
Asset Asset Yes Yes
AssetDeliveryPolicy StreamingPolicy Yes No
AssetFile V3 中不存在实体 AssetFilesThe entity AssetFiles doesn't exist in V3. 尽管你上传的文件(存储 Blob)仍被视为文件。Although files (storage blobs) that you upload are still considered files.

请改用 Azure 存储 API 来枚举容器中的 Blob。Use the Azure Storage APIs to enumerate the blobs in a container instead. 可以通过两种方法将转换应用于带有作业的文件:There are two ways to apply a transform to the files with a job:

已上传到存储的文件:该 URI 将包含要在存储帐户中的资产上完成的作业的资产 ID。Files already uploaded to storage: The URI would include the asset ID for jobs to be done on assets within a storage account.

要在转换和作业过程中上传的文件:在存储中创建资产,返回 SAS URL,将文件上传到存储,然后将转换应用于文件。Files to be uploaded during the transform and job process: The asset is created in storage, a SAS URL is returned, files are uploaded to storage, and then the transform is applied to the files.
No No
Channel LiveEvent 直播活动替换 v2 API 中的频道。Live Events replace Channels from the v2 API. 它们保留了大多数功能,并具有更多新功能,例如实时听录、待机模式以及对 RTMPS 引入的支持。They carry over most features, and have more new features like live transcriptions, stand-by mode, and support for RTMPS ingest.

请参阅基于场景的实时传送视频流中的直播活动See live event in scenario based live streaming
No No
ContentKey 现在,ContentKeys 不再是实体,而是流定位器的一个属性。ContentKeys is no longer an entity, it's now a property of a streaming locator.

在 v3 中,内容密钥数据与 StreamingLocator(用于输出加密)或资产本身(用于客户端存储加密)相关联。In v3, the content key data is either associated with the StreamingLocator (for output encryption) or the Asset itself (for client side storage encryption).
Yes No
ContentKeyAuthorizationPolicy ContentKeyPolicy Yes No
ContentKeyAuthorizationPolicyOption ContentKeyPolicyOptions 包含在 ContentKeyPolicy 中。ContentKeyPolicyOptions are included in the ContentKeyPolicy. Yes No
IngestManifest V3 中不存在实体 IngestManifestsThe entity IngestManifests doesn't exist in V3. 在 V3 中上传文件涉及 Azure 存储 API。Uploading files in V3 involves the Azure storage API. 首先创建资产,然后将文件上传到关联的存储容器。Assets are first created and then files are uploaded to the associated storage container. 可以通过多种方法将数据导入到可以替代使用的 Azure 存储容器中。There are many ways to get data into an Azure Storage container that can be used instead. JobInputHttp 还提供了一种方法,用于从给定的 URL 下载作业输入(如果需要)。JobInputHttp also provides a way to download a job input from a given url if desired. No No
IngestManifestAsset 可以通过多种方法将数据导入到可以替代使用的 Azure 存储容器中。There are many ways to get data into an Azure Storage container that can be used instead. JobInputHttp 还提供了一种方法,用于从给定的 URL 下载作业输入(如果需要)。JobInputHttp also provides a way to download a job input from a given url if desired. No No
IngestManifestFile 可以通过多种方法将数据导入到可以替代使用的 Azure 存储容器中。There are many ways to get data into an Azure Storage container that can be used instead. JobInputHttp 还提供了一种方法,用于从给定的 URL 下载作业输入(如果需要)。JobInputHttp also provides a way to download a job input from a given url if desired. No No
Job Job 创建 Job 之前,请创建 TransformCreate a Transform before creating a Job. No No
JobTemplate Transform 改用 TransformUse a Transform instead. 转换是独立于作业的实体,并且可以重复使用。A transform is a separate entity from a job and is reuseable. No No
Locator StreamingLocator Yes No
MediaProcessor 定义转换时,请使用所需的预设,而不是按名称查找要使用的 MediaProcessorInstead of looking up the MediaProcessor to use by name, use the desired preset when defining a transform. 使用的预设将确定作业系统所使用的媒体处理器。The preset used will determine the media processor used by the job system. 请参阅基于场景的编码中的编码主题。See encoding topics in scenario based encoding. No NA(V2 中为只读)NA (readonly in V2)
NotificationEndPoint V3 中的通知通过 Azure 事件网格进行处理。Notifications in v3 are handled via Azure Event Grid. NotificationEndpoint 被替换为事件网格订阅注册,该注册还会封装要接收的通知类型的配置(在 v2 中由作业的 JobNotificationSubscription、任务的 TaskNotificationSubscription 和遥测 ComponentMonitoringSetting 处理)。The NotificationEndpoint is replaced by the Event Grid subscription registration which also encapsulates the configuration for the types of notifications to receive (which in v2 was handled by the JobNotificationSubscription of the Job, the TaskNotificationSubscription of the Task, and the Telemetry ComponentMonitoringSetting). V2 遥测在 Azure 事件网格和 Azure Monitor 之间进行了拆分,以适应更大的 Azure 生态系统的增强功能。The v2 Telemetry was split between Azure Event Grid and Azure Monitor to fit into the enhancements of the larger Azure ecosystem. No No
Program LiveOutput 实时输出现在会替换 v3 API 中的节目。Live Outputs now replace Programs in the v3 API. No No
StreamingEndpoint StreamingEndpoint 流式处理终结点基本上保持不变。Streaming Endpoints remain primarily the same. 它们用于动态打包、加密和传递 HLS 和 DASH 内容,直接从原始来源或通过 CDN 进行实时和按需流式处理。They're used for dynamic packaging, encryption, and delivery of HLS and DASH content for both live and on-demand streaming either direct from origin, or through the CDN. 新功能包括对更好 Azure Monitor 集成和图表制作的支持。New features include support for better Azure Monitor integration and charting. Yes Yes
Task JobOutput 替换为 JobOutput(不再是 API 中的单独实体)。Replaced by JobOutput (which is no longer a separate entity in the API). 请参阅基于场景的编码中的编码主题。See encoding topics in scenario based encoding. No No
TaskTemplate TransformOutput 替换为 TransformOutput(不再是 API 中的单独实体)。Replaced by TransformOutput (which is no longer a separate entity in the API). 请参阅基于场景的编码中的编码主题。See encoding topics in scenario based encoding. No No
Inputs Inputs 输入和输出现在处于作业级别。Inputs and outputs are now at the Job level. 请参阅基于场景的编码中的编码主题See encoding topics in scenario based encoding No No
Outputs Outputs 输入和输出现在处于作业级别。Inputs and outputs are now at the Job level. 在 V3 中,元数据格式已从 XML 更改为 JSON。In V3, the metadata format changed from XML to JSON. 实时输出在创建时启动,在删除后停止。Live Outputs start on creation and stop when deleted. 请参阅基于场景的编码中的编码主题See encoding topics in scenario based encoding No No
其他更改Other changes V2V2 V3V3
存储Storage
存储Storage V3 SDK 现在已与存储 SDK 分离,可让你更精细地控制所要使用的存储 SDK 版本,并避免版本控制问题。The V3 SDKs are now decoupled from the Storage SDK, which gives you more control over the version of Storage SDK you want to use and avoids versioning issues.
编码Encoding
编码比特率Encoding bit rates 比特率(以 kbps 为单位),例如:128 (kbps)bit rates measured in kbps ex: 128 (kbps) 每秒位数,例如:128000(位/秒)bits per second ex: 128000 (bits/second)
编码 DRM FairPlayEncoding DRM FairPlay 在媒体服务 V2 中,可以指定初始化向量 (IV)。In Media Services V2, initialization vector (IV) can be specified. 在媒体服务 V3 中,无法指定 FairPlay IV。In Media Services V3, the FairPlay IV cannot be specified.
高级编码器Premium encoder 高级编码器和旧索引器Premium encoder and Legacy Indexer 不能通过 V3 访问高级编码器和旧的媒体分析处理器The Premium Encoder and the legacy media analytics processors are not accessible via V3. 添加了对音频通道映射到标准编码器的支持。We added support for audio channel mapping to the Standard encoder. 请参阅媒体服务编码 Swagger 文档中的音频See Audio in the Media Services Encoding Swagger documentation. 请参阅基于场景的编码中的编码主题See encoding topics in scenario based encoding
转换和作业Transforms and jobs
基于作业的处理 HTTPSJob based processing HTTPS 对于基于文件的作业处理,可以使用 HTTPS URL 作为输入。For file-based Job processing, you can use a HTTPS URL as the input. 无需事先在 Azure 中存储内容,无需创建资产。You don't need to have content already stored in Azure, nor do you need to create Assets.
作业的 ARM 模板ARM templates for jobs V2 中不存在 ARM 模板。ARM templates didn't exist in V2. 使用转换可以生成可重用的配置、创建 Azure 资源管理器模板,并隔离多个客户或租户之间的处理设置。A transform can be used to build reusable configurations, to create Azure Resource Manager templates, and isolate processing settings between multiple customers or tenants.
直播活动Live events
流式处理终结点Streaming endpoint 流式处理终结点代表一个流式处理服务,它可以直接将内容分发给客户端播放器应用程序。A streaming endpoint represents a streaming service that can deliver content directly to a client player application. 流式处理终结点基本上保持不变。Streaming Endpoints remain primarily the same. 它们用于动态打包、加密和传递 HLS 和 DASH 内容,直接从原始来源进行实时和按需流式处理。They're used for dynamic packaging, encryption, and delivery of HLS and DASH content for both live and on-demand streaming either direct from origin. 新功能包括对更好 Azure Monitor 集成和图表制作的支持。New features include support for better Azure Monitor integration and charting.
直播活动频道Live event channels 频道负责处理实时传送视频流内容。Channels are responsible for processing live streaming content. 通道提供输入终结点(引入 URL),并将该终结点提供给实时转码器。A Channel provides an input endpoint (ingest URL) that you then provide to a live transcoder. 频道从实时转码器接收实时输入流,并通过一个或多个流式处理终结点使其可用于流式处理。The channel receives live input streams from the live transcoder and makes it available for streaming through one or more streaming endpoints. 频道还提供可用于预览的预览终结点(预览 URL),并在进一步处理和传递流之前对流进行验证。Channels also provide a preview endpoint (preview URL) that you use to preview and validate your stream before further processing and delivery. 直播活动替换 v2 API 中的频道。Live Events replace Channels from the v2 API. 它们保留了大多数功能,并具有更多新功能,例如实时听录、待机模式以及对 RTMPS 引入的支持。They carry over most features, and have more new features like live transcriptions, stand-by mode, and support for RTMPS ingest.
直播活动节目Live event programs 节目用于控制实时流中片段的发布和存储。A Program enables you to control the publishing and storage of segments in a live stream. 频道管理节目。Channels manage Programs. 频道和节目的关系类似于传统媒体,其中频道具有恒定的内容流,而节目的范围限定为该频道上的一些定时事件。The Channel and Program relationship is similar to traditional media where a channel has a constant stream of content and a program is scoped to some timed event on that channel. 可以通过设置 ArchiveWindowLength 属性,指定希望保留节目录制内容的小时数。You can specify the number of hours you want to keep the recorded content for the program by setting the ArchiveWindowLength property. 此值的设置范围是最短 5 分钟,最长 25 小时。This value can be set from a minimum of 5 minutes to a maximum of 25 hours. 实时输出现在会替换 v3 API 中的节目。Live Outputs now replace Programs in the v3 API.
直播活动长度Live event length 使用媒体服务将单比特率贡献源转码为具有多比特率的输出流时,可以全天候流式传输直播活动。You can stream Live Events 24/7 when using Media Services for transcoding a single bitrate contribution feed into an output stream that has multiple bitrates.
直播活动延迟Live event latency 直播活动支持新的低延迟实时传送视频流。New low latency live streaming support on live events.
直播活动预览Live Event Preview 直播活动预览版支持动态打包和动态加密。Live Event Preview supports Dynamic Packaging and Dynamic Encryption. 这样,用户便可以使用预览版中的内容保护以及 DASH 和 HLS 打包。This enables content protection on Preview as well as DASH and HLS packaging.
直播活动 RTMPSLive event RTMPS 改进的 RTMPS 支持(提高了稳定性并提供了更多的源编码器支持)。Improved RTMPS support with increased stability and more source encoder support.
直播活动 RTMPS 安全引入Live event RTMPS secure ingest 创建直播活动时,将获得 4 个引入 URL。When you create a live event, you get 4 ingest URLs. 这 4 个引入 URL 几乎是相同的,具有相同的流式处理令牌 AppId,仅端口号部分不同。The 4 ingest URLs are almost identical, have the same streaming token AppId, only the port number part is different. 其中两个 URL 是 RTMPS 的主要和备份 URL。Two of the URLs are primary and backup for RTMPS.
直播活动待机模式Live event standby mode V2 没有待机模式。There was no standby mode for V2. 待机模式是一项新的 v3 功能,可帮助管理直播活动的热池。Stand-by mode is a new v3 feature that helps manage hot pools of Live Events. 客户现在可以较低的成本在待机模式下启动直播活动,然后再将其转换为运行状态。Customers can now start a Live Event in stand-by mode at lower cost before transitioning it to the running state. 这会缩短频道启动时间,并降低操作热池以加快启动速度的成本。This improves channel start times and reduces costs of operating hot pools for faster start ups.
直播活动计费Live event billing 直播活动计费基于实时频道计量器。Live events billing is based on Live Channel meters.
实时输出Live outputs 节目必须在创建后启动。Programs had to be started after creation. 实时输出在创建时启动,在删除后停止。Live Outputs start on creation and stop when deleted.

后续步骤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: