channel of audio and recorded video, a channel of
live audio and video, a audio channel, a connection
with a web browser, as well as areas for viewing,
interaction objects and widgets (menus, quiz,
captions, among others).
In Figure 4, there is an interface element for
flagging (upper right of the viewport) which
enables the viewer to select the desired
programming among the four options (multi-
programming) available on the system
5 INTERACTIVE SERVICE
PROVIDER
The back channel is one of the most important parts
of a TVDI system due the fact it is involved with
the revolution of the system as whole. When there is
any viewer's interaction, there is need sending these
information (access level, votes, terminal data,
among others) to the broadcaster's studio, by a
return channel, which is a direct link to data
delivery. Another important factor is that between
the broadcaster and viewer there is another module
called Interactive Service Provider (ISP).
In a typical TVDI system, the treatment of
viewer's interaction can be classified in two ways: a)
the Pseudo-Interactive System (Figure 5a); b) Full-
Interactive System (Figure 5b). In the pseudo-
interactive system, the treatment of interactivity is
processed into access terminal of the viewer and
there is not return of information to the ISP; in this
case, the presence of a back channel is not
mandatory and all applications must be of the kind
resident.
Figure 5a: Architecture for Pseudo-Interactive System.
As shown in the Figures 5a and 5b, the
interactive programs are produced by the
broadcaster station and transmitted via broadcasting
network until to reach the viewer STB. In this point,
for the case of pseudo-interactivity system, the
viewer can interact with applications, but no return
of information for the broadcaster. In other hand, in
a full-interactivity system, information generated by
viewer's interaction can return to broadcaster, using
the infrastructure of the ISP.
Figure 5b: Architecture for Full-Interactive System.
In this research, the JiTVPSI Studio was
developed for supporting all operations between the
follow entities (Figure 5b): 1) broadcaster to
viewer; 2) viewer to ISP and ISP to viewer; 3)
broadcaster to ISP; 4) ISP to broadcaster. For
supporting viewer's operations, the JiTVPSI Studio
provides functionalities for data receiving,
information storing, information sending to ISP.
For supporting broadcaster's operations, JiTVPSI
Studio offers functionalities as to select data filters
on the volume of data which is received from the
viewer's interaction. For validating of the JiTVPSI
Studio under the ISDTV-T test suite, two
applications for full-interactive system have been
developed. The first one, called JiTVDengue, has
been developed for health purposes; the another
application, called JiTVElection, has been
developed for government interests.
The JiTVDengue has been developed in order to
investigate the possibilities of the occurrence of
dengue (a typical disease which occurs in tropical
countries, like is the case of Brazil) into a residence,
allowing to the viewer to interact with the
interactive application in order to answer four
questions concerning the possible cause of dengue.
Soon after the interaction of the viewer, the data are
stored in the STB as a XML structure and sent to
the JiTVPSI Studio, which store these data for use
in government actions. In this context, the JiTVPSI
Studio offers a set of tools for filtering data before
sending reports to the government entities.
Another interactive application - JiTVElection -
has been developed to simulate an majory election
in a city, state or country, allowing to the viewer to
interact with the interactive program in order to
select in which candidate he wants to vote. After
the interaction and confirmation of the vote, the
data for related to the candidate are saved in an
XML file and sent to the JiTVPSI Studio, which
store these information for government interests.
In the broadcaster entity, the JiTVPSI Studio has
as main function to receive data from filtering
ICEIS 2009 - International Conference on Enterprise Information Systems
134