SEGURIDAD CONTRA INCENDIOS PARTE A - CUESTIONES GENERALES
7.9 Aspectos varios
This section discusses the recording storage and subsequent playback requirements of a Host that records CI Plus protected content using the Content Control resource. The Host is always required to honour the URI settings, Parental Control (PIN) notifications and Content License.
The URI, License and PIN changes shall be accurately stored with the programme content such that each transition may be accurately reproduced by the Host on subsequent playback matching the events with the original delivery content position. The PIN notification contains a time stamp and may be accurately aligned with the stream. The URI and License do not contain a time stamp and shall be aligned with the content based on their reception time at the Host.
The Host shall not aggregate Licenses or PINs. The Content Control protection of Licenses, URIs and PINs shall apply from the position in the stream where the protection was applied in the recording until the next protection position in the recording or the end of the stream. The scope of each content protection component is defined as follows:
A URI extends from the reported position to the next URI reported position, or to the end of the recording, in a forwards direction.
A License extends from the reported position to the next URI or License reported position, or to the end of the recording, in a forwards direction.
A PIN extends from the reported position to the next PIN reported position, or to the end of the recording, in a forwards direction.
Event 1
Event 2
Event 3
00:00:00:000 URI #1, License #1 00:01:00:000 PIN #1 01:30:00:000 URI #2 02:00:00:000 URI #3, License #2 03:00:00:000 01:30:00:000 PIN #2Figure 5.25: Example recording sequence
Any of the aforementioned transitions may occur at any time in the recording as shown in Figure 5.25 which depicts a time, rather than event based, recording.
The content in Figure 5.25 is protected as follows, where URI#n is a change in the URI, License#n is the content license and PIN#n is a parental control event where the parental rating has changed. For the purposes of the example then we assume that the recording spans three events, typically we would expect a single event to be recorded.
Event#1: is content that is license protected with License#1 and URI#1 there is a parental control PIN#1 one
minute into the recording.
Event#2: is content that is not licence protected and has URI#2, there is a parental control PIN#2 in effect. Event#3: is content that is licence protected with License#2 and URI#3 and there is a parental control PIN#2 in
license and simply returns it on a playback operation at the appropriate time in the stream when a new license block is entered.
5.12.1
Playback Session
On playback of a recording the Host shall effectively include the concept of a session. On playing a recording then the session shall be opened, the session is not closed until the playback is stopped, a pause does not constitute a session close. A session may be closed by the Host as a result of the content retention time limit being exceeded, at which point the content protected by the retention time limit is made inaccessible. Licenses are consumed, typically as encountered, during the playback. Consumption of a License requires a license exchange with the CICAM and the License and URI associated with the recording are exchanged with a new License and URI to be associated with the recording replacing each of the existing stored values. A license is only consumed once in the context of a playback session, irrespective of the user navigation moving between different license blocks that have already been consumed in the current session.
A parental rating (PIN) transition in the recording requires the Host to remove all displayable components of the recording (i.e. blank video, mute audio, disable subtitles, etc.) until a PIN valid is acquired from the CICAM, via the user, when the content may be restored. A PIN exchange must be performed with the CICAM when crossing any PIN event in the recording in either a forward or backward direction if the content is to be displayed. The CICAM (Service Operator) may reduce user interaction within the context of a playback once a valid PIN has been entered and any further PIN requests from the Host should ideally not invoke a user interaction provided that the parental rating of the first PIN entry is not exceeded, the exact operation of the CICAM is determined by the Service Operator and country regulations.
Navigation in a forwards and backwards direction in the recording requires the Host to honour all the License, URI and PIN constraints at each transition point in the recording. When moving in a backwards direction then the Host is required to re-evaluate the constraints when crossing a constraint event in the recording, this requires the Host to find the previous transition type and appropriately apply the constraint. Within the context of a playback session, on encountering a:
PIN Constraint: a PIN exchange shall be performed with the CICAM
License Constraint: each license is exchanged with the CICAM only once in a playback session, at first
encounter. On any subsequent encounter of a successfully exchanged license, there is no requirement to exchange that license with the CICAM again.
URI Constraint: the URI shall be applied as described in section 5.7.
The URI returned from a CICAM license exchange may change the existing recorded License and URI and shall be associated with the content at the same position as the original, displacing the existing License and URI. The new URI shall be used immediately for playback. The new URI may alter the retention time limit which shall be applied in a similar way to the recording process, taking into consideration the length of the material when viewed with a normal playback time. e.g. Consider a 2 hour (120 minute) programme that changes its retention limit from 30 days to 90 minutes. At the instant the URI is changed then the first byte of the recorded material at the URI transition has a new retention time limit of 90 minutes, the last byte of the 120 minute recorded event has a retention time limit of 120+90 or 210 minutes. A URI that exists without a License is not re-presented to the CICAM on playback and is not replaced in the recording.
Where a recording has multiple URIs with different retention limit values then the Host is required to manage the retention limits of each URI region according to the CI Plus License Agreement [6]. The Host may choose to handle each URI region retention limit separately or apply the most restrictive retention limit to the whole of the material. In either case the Host shall not exceed the stated retention limit for any URI region. The exact method by which the Host manages different retention times within a single recording is implementation specific, but in all cases must be managed according to the CI Plus License Agreement.
A Host is not obliged to remove recording content from storage which has exceeded its play count. If the Service Operator requires the content to be removed once it has been viewed on playback, when a transition from a play count of one to zero occurs, then the retention limit should be set appropriately through the playback URI to force the Host to remove the content once the retention time limit has been exceeded.