• There are no items in your cart

BS ISO/IEC 29341-20-14:2017

Current
Current

The latest, up-to-date edition.

Information technology. UPnP Device Architecture Audio video device control protocol. Level 4. Scheduled recording service
Available format(s)

Hardcopy , PDF

Language(s)

English

Published date

09-22-2017

1 Scope
2 Normative references
3 Terms, definitions, symbols and abbreviations
4 Notations and Conventions
5 Service Modeling Definitions
6 XML Service Description
7 Test
Annex A (normative) - srs XML Document
Annex B (normative) - AV Working Committee Extended Properties
Annex C (normative) - AV Working Committee Class Definitions
Annex D (normative) - EBNF Syntax Definitions
Annex E (informative) - Scheduled Recording Service
        Relationship to Content Directory Service
Annex F (informative) - Scheduled Recording Service
        Relationship to EPG
Annex G (informative) - AVDT Examples
Annex H (informative) - Bibliography

Provides a service type referred to herein as Scheduled Recording service.

This service definition 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 indicating 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.

Committee
ICT/1
DevelopmentNote
Supersedes 15/30326574 DC. (10/2017)
DocumentType
Standard
Pages
292
PublisherName
British Standards Institution
Status
Current
Supersedes

Standards Relationship
ISO/IEC 29341-20-14:2017 Identical

ISO/IEC 14977 : 1996(R2018) INFORMATION TECHNOLOGY - SYNTACTIC METALANGUAGE - EXTENDED BNF
IEEE 802.1AS-2011 IEEE Standard for Local and Metropolitan Area Networks - Timing and Synchronization for Time-Sensitive Applications in Bridged Local Area Networks
ISO/IEC 21000-2:2005 Information technology Multimedia framework (MPEG-21) Part 2: Digital Item Declaration
ISO/IEC 14977:1996 Information technology — Syntactic metalanguage — Extended BNF
IEEE 1733-2011 IEEE Standard for Layer 3 Transport Protocol for Time-Sensitive Applications in Local Area Networks

View more information
US$500.71
Excluding Tax where applicable

Access your standards online with a subscription

Features

  • Simple online access to standards, technical information and regulations.

  • Critical updates of standards and customisable alerts and notifications.

  • Multi-user online standards collection: secure, flexible and cost effective.