信息技术 - UPnP设备架构 - 第20-14部分:音频视频设备控制协议 - 第4级 - 计划录制服务

[中文适用范围]： 本服务定义符合UPnP设备架构版本1.0[14]。它定义了一种称为ScheduledRecording服务的服务类型。ScheduledRecording服务是一个UPnP服务，允许控制点调度内容的记录。通常，此内容是广播内容，但本规范不限于广播内容。该服务类型实现以下功能：• 创建recordSchedule并将其添加到recordSchedule实例列表中。每个recordSchedule描述用户级别的录制指令。• 访问ScheduledRecording服务存储的recordSchedule实例列表。• 删除recordSchedule以从recordSchedule实例列表中移除。• 浏览ScheduledRecording服务存储的recordTask实例列表。对于每个recordSchedule，ScheduledRecording服务可以创建零个或多个recordTask实例。一个recordTask表示recordSchedule的一个离散记录操作。• 启用或禁用individual recordTask实例。• 启用或禁用recordSchedule。• 收到通知，指示recordSchedule或recordTask列表发生变化。ScheduledRecording服务不要求依赖任何UPnP服务，除了共存的ContentDirectory服务之外，该服务提供以下功能：• ContentDirectory服务提供频道列表以使用户能够找到可以录制的频道。控制点可能在创建ScheduledRecording服务上的recordSchedule时使用此元数据。• ContentDirectory服务可能提供电子节目指南(EPG)功能，使用户能够查找可录制的内容。控制点可能在创建ScheduledRecording服务上的recordSchedule时使用此元数据。• 由ScheduledRecording服务记录的内容可能会通过ContentDirectory服务暴露出来。 ScheduledRecording服务概念之间的架构关系可以总结如下：一个ScheduledRecording服务拥有一个扁平的（即：非嵌套）recordSchedule实例列表，这意味着ScheduledRecording服务可以创建、销毁或更改recordSchedule实例。每个recordSchedule表示用户级别的记录操作指令。通常，用户通过控制点构造他对ScheduledRecording服务的指令，该控制点调用影响recordSchedule实例列表的UPnP操作。在所有情况下，ScheduledRecording服务必须能够通过关联的recordTask实例列表为recordSchedule描述离散记录操作。一个recordTask只能与一个recordSchedule相关联（即：从未被遗弃）。因此，当ScheduledRecording服务创建recordTask时，其生命周期取决于父recordSchedule。individual recordTask可以被选择性地启用或禁用。此服务模板不处理以下情况：• ScheduledRecording服务及其关联的ContentDirectory服务未位于同一设备中 [外文原描述]： ISO/IEC 29341-20-14:2017 is compliant with the UPnP Device Architecture version 1.0 [14]. It defines a service type referred to herein as ScheduledRecording service. The ScheduledRecording service is a UPnP service that allows control points to schedule the recording of content. Generally, this content is broadcast content, but this specification does not limit itself to broadcast content. This service type enables the following functions: - Create a recordSchedule so that it is added to the list of recordSchedule instances. Each recordSchedule describes user-level recording instructions for the ScheduledRecording service. - Browse a list of recordSchedule instances stored by the ScheduledRecording service. - Delete a recordSchedule so that it is removed from the list of recordSchedule instances. - Browse a list of recordTask instances, stored by the ScheduledRecording service. The ScheduledRecording service may create zero or more recordTask instances for each recordSchedule. A recordTask represents a discrete recording operation of a recordSchedule. - Enable or disable individual recordTask instances. - Enable or disable a recordSchedule. - Receive notifications i ndicating change of recordSchedule or recordTask list. The ScheduledRecording service does not require a dependency on any UPnP services other than a co-located ContentDirectory service, which provides the following functions: - A ContentDirectory service provides channel line-up to allow users to find recordable channels. A control point may use this metadata when creating a recordSchedule on a ScheduledRecording service. - A ContentDirectory service may provide Electronic Program Guide (EPG) features to allow users to find recordable content. A control point may use this metadata when creating a recordSchedule on a ScheduledRecording service. - Contents recorded by the ScheduledRecording service may be exposed by a ContentDirectory service. The architectural relationship among the different concepts, defined by the ScheduledRecording service can be summarized as follows: A ScheduledRecording service owns a flat (that is: non-nested) list of recordSchedule instances, meaning that the ScheduledRecording service may create, destroy, or change recordSchedule instances. A recordSchedule represents user-level instructions to perform recording operations. Generally, a user constructs his instructions to a ScheduledRecording service via a control point that invokes UPnP actions that affect the list of recordSchedule instances. In all cases, the ScheduledRecording service shall be able to describe discrete recording operations for a recordSchedule through a list of associated recordTask instances. A recordTask can only exist with a recordSchedule (that is: never orphaned). Thus when a recordTask is created by the ScheduledRecording service, its lifetime depends on its parent recordSchedule. An individual recordTask can be selectively enabled or disabled. This service template does not address: Implementations where the ScheduledRecording service and its associated ContentDirectory service are not co-located in the same device.