TS 102 323 - V1.4.1 - Digital Video Broadcasting (DVB ... - ETSI
TS 102 323 - V1.4.1 - Digital Video Broadcasting (DVB ... - ETSI
TS 102 323 - V1.4.1 - Digital Video Broadcasting (DVB ... - ETSI
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Locate RNT describing<br />
correct combination of<br />
resolution provider and<br />
CRID authority<br />
Change transport<br />
stream<br />
No<br />
Yes<br />
Parse RNT scan<br />
descriptor (if<br />
available)<br />
alternative<br />
RNT subtable<br />
locations<br />
CRI search start<br />
Acquire RNT<br />
subtable using<br />
context_id and<br />
context_id_type<br />
Is this the first RNT<br />
acquired?<br />
No<br />
Does RNT<br />
subtable contain correct<br />
resolution provider entry<br />
with correct CRID<br />
authority?<br />
No<br />
Have all alternative RNT<br />
locations been tried?<br />
Yes<br />
CRI search failed<br />
16<br />
Yes<br />
E<strong>TS</strong>I<br />
Key<br />
Process Data<br />
Parse RAR<br />
descriptors<br />
Acquire CRI<br />
Does CRI contain<br />
information on CRID<br />
Yes<br />
CRI search<br />
succesful<br />
E<strong>TS</strong>I <strong>TS</strong> <strong>102</strong> <strong>323</strong> <strong>V1.4.1</strong> (2010-01)<br />
Locate CRI set delivering information<br />
on CRID to be resolved<br />
Figure 3: Example procedure for acquiring CRI (informative)<br />
5.2.2 Resolution provider notification table<br />
No<br />
Yes<br />
flow of<br />
control<br />
CRI set<br />
locations<br />
Are there<br />
alternative CRI sets<br />
worth acquiring?<br />
No<br />
CRI search failed<br />
The resolution provider notification table (RNT) carries information provided by resolution providers relating to CRID<br />
authorities (see <strong>TS</strong> <strong>102</strong> 822-4 [6], clause 6), providing the locations of CRI and metadata for those CRID authorities.<br />
Each RNT sub_table provides information on a particular context (see clause 5.2.1). An RNT sub_table is distinguished<br />
by context_id, context_id_type and the transport stream the RNT is carried on. RNTs with the same context_id and<br />
context_id_type but carried on different transport streams shall not be considered the same sub_table.<br />
The RNT shall be segmented into sections using the syntax of table 1. Sections forming part of the RNT shall be carried<br />
in <strong>TS</strong> packets with a PID value of 0x0016.<br />
flow of<br />
data
Change language