Search book title
Enter keywords for book title search
Search book content
Enter keywords for book content search
Filters:
FORMAT
BOOKS
PACKAGES
EDITION
to
PUBLISHER
(1)
(326)
(573)
(44)
(234)
(969)
(652)
(2114)
(64)
(92448)
(54)
(541)
(117)
(33)
(20)
(19)
(93277)
(3)
(17)
(1)
(351)
(300)
(6217)
(240)
(16)
(5)
(1621)
(16)
(19)
(28)
(4)
 
(6)
(7)
(115)
(3)
(57)
(5)
(5)
(1)
(1)
(2)
(25)
(26)
(27)
(13)
(61)
(24)
(22)
(7)
(8)
(20)
(1)
(3)
(50)
(6)
(31)
CONTENT TYPE
 Act
 Admin Code
 Announcements
 Bill
 Book
 CADD File
 CAN
 CEU
 Charter
 Checklist
 City Code
 Code
 Commentary
 Comprehensive Plan
 Conference Paper
 County Code
 Course
 DHS Documents
 Document
 Errata
 Executive Regulation
 Federal Guideline
 Firm Content
 Guideline
 Handbook
 Interpretation
 Journal
 Land Use and Development
 Law
 Legislative Rule
 Local Amendment
 Local Code
 Local Document
 Local Regulation
 Local Standards
 Manual
 Model Code
 Model Standard
 Notice
 Ordinance
 Other
 Paperback
 PASS
 Periodicals
 PIN
 Plan
 Policy
 Product
 Program
 Provisions
 Requirements
 Revisions
 Rules & Regulations
 Standards
 State Amendment
 State Code
 State Manual
 State Plan
 State Standards
 Statute
 Study Guide
 Supplement
 Technical Bulletin
 All
  • BSI
    BS ISO/IEC 29341-20-14:2017 Information technology. UPnP Device Architecture - Audio video device control protocol. Level 4. Scheduled recording service
    Edition: 2017
    $538.63
    / user per year

Description of BS ISO/IEC 29341-20-14:2017 2017

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.



About BSI

BSI Group, also known as the British Standards Institution is the national standards body of the United Kingdom. BSI produces technical standards on a wide range of products and services and also supplies certification and standards-related services to businesses.

X