ISO/IEC 29341-20-14:20 17符合UPnP设备架构1.0版[14]。它定义了在此称为ScheduledRecording服务的服务类型。 ScheduledRecording服务是允许控制点安排内容记录的UPnP服务。通常，该内容是广播内容，但是本规范不限于广播内容。此服务类型启用以下功能: -创建一个recordSchedule，以便将其添加到recordSchedule实例列表中。每个recordSchedule描述了ScheduledRecording服务的用户级记录指令。 -浏览由ScheduledRecording服务存储的recordSchedule实例的列表。 -删除recordSchedule，以便将其从recordSchedule实例列表中删除。-浏览由ScheduledRecording服务存储的recordTask实例列表。ScheduledRecording服务可以为每个recordSchedule创建零个或多个recordTask实例。recordTask表示recordSchedule的离散记录操作。 -启用或禁用单个recordTask实例。 -启用或禁用记录调度。 -接收指示记录计划或记录任务列表更改的通知。 ScheduledRecording服务不需要依赖任何UPnP服务，除了一个协同定位的ContentDirectory服务，它提供以下功能: -ContentDirectory服务提供频道排队以允许用户找到可记录的频道。控制点在ScheduledRecording服务上创建recordSchedule时可以使用此元数据。-内容目录服务可以提供电子节目指南(EPG)特征以允许用户找到可记录的内容。控制点在ScheduledRecording服务上创建recordSchedule时可以使用此元数据。 -由ScheduledRecording服务记录的内容可以由ContentDirectory服务公开。 由ScheduledRecording服务定义的不同概念之间的架构关系可以总结如下:ScheduledRecording服务拥有recordSchedule实例的平面(即:非嵌套)列表，这意味着ScheduledRecording服务可以创建、销毁或改变recordSchedule实例。recordSchedule表示执行记录操作的用户级指令。通常，用户经由控制点构造他对ScheduledRecording服务的指令，控制点调用影响recordSchedule实例列表的UPnP动作。在所有情况下，ScheduledRecording服务应能够通过关联的recordTask实例列表来描述recordSchedule的离散记录操作。recordTask只能与recordSchedule一起存在（即:从不孤立）。因此，当由ScheduledRecording服务创建recordTask时，其生存期取决于其父recordSchedule。可以有选择地启用或禁用单个记录任务。 此服务模板不涉及: 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.