Oipf standard translation (DAE) -- 4.1.1 remote UI and box models (Informative)

4.1.1 remote UI and box models (Informative)

4.1.1 remote UI and Box Model

 

The Architecture Overview from CEA 2014 section 4.1 defines various box models. Next to the I-Box Model
Accessing IPTV service providers or 3rd party Internet services, it defines a 2-box and 3-Box Model for in-home remote UI. box models are divided by not only where the server resides but also where the UI control point reside to perform discovery and setup of a remote UI connection. in case of the 2-box and 3-box model the UI control point is a UPnP control point that discovers in-home servers. in case of the 2-box model, there is a UPnP remote UI control point inside the oitf. if the UPnP remote UI control point resides in an external device (e.g. web pad, Remote Controller), whereby the external device lists the remote UI servers and sets up a UI connection between the oitf and remote UI server this is called the 3-box model. an oitf that supports the 3-box model must be discoverable through UPnP itself, and expose the profile information of a remote UI client to the home network.

 

Cea2014 Specification section 4.1 describes many box model systems. After I-box (used to access IPTV services or third-party Internet Services) models are defined, 2-box is defined for the remote UI of the residential (Home Network, 3-box model. In the box model, you can discover and set remote UI connections not only in the server's location, but also in the place where the UI control points reside. For the 2-box and 3-box models, the UI control point is generally the UPnP control point on a home network server. For the 2-box model, its UI control point is an UPnP control point in oitf. If the UPnP remote UI control point is in an external device (for example, Web pad, remote controller, and remote host), you need to list the addresses of the remote UI server by relying on the remote device, oitf is configured to connect to the remote UI server. This is called the 3-box model. To support the 3-box model, oitf must be able to be found through the UPnP protocol (whether it refers to intranet penetration or similar ), in addition, the configuration information of the UI client can be exposed through the home network.

 

========================================================== ========================================================== =

For the oitf, just the CEA-2014-A I-box model is mandatory. The 2-box and 3-box models are optional. The default
Interaction with the application gateway (AG), the IMS Gateway (IG) and the CSP Gateway (cspg) Deviate in
Following manner. However, it is not precluded for an AG, Ig, cspg or other devices in the home network to expose
Themselves as a regular UPnP remote UI server that is compliant with CEA-2014, for example to serve a remote UI of its configuration screen to the oitf.

O The AG is similar to a level 1 remote UI server as defined in Section 5.1.1.2 of CEA-2014-A, with
Difference that [Req. 5.1.1.2.d] is replaced with a different device description. The device description of the AG
Is defined in section 10.1.1.2 of [Prot]. The requirements [Req. 5.1.1.2. B] and [Req. 5.1.1.2.c] are now
Optional: a URL to the xml ui listing is provided by element <aguiserverurl> of the AG description XML document. Note that the UPnP Device description of the AG may offer a CEA-2014-A Compatible Level 1 or
Level 2 Remote UI server in its UPnP Device hierarchy that point to the same xml ui listing.
O The IG enables the disdiscovery of IPTV services through the HNI-IGI interface as defined in [Prot]. This is
Quite different from a level 1 or Level 2 Remote UI server. The details of the device discovery of the IG are
Defined in section 10.1.1.1 of [Prot].

 

In oitf, only the I-box model defined in cea2014 is required. Both 2-box and 3-box are optional. By default, it interacts with Ag (application gateway), ig (IMS gateway), and cspg (CSP gateway) as follows. Of course, AG, Ig, and cpsg in the home network cannot be excluded as the UPnP remote UI server. For example, remote UI can be provided to oitf on the configuration screen.

 

-- Ag can be seen as the first-level remote UI server defined in CEA-2014-A 5.1.1.2, with a different device description than the one defined in CEA 5.1.1.2. The description of Ag devices is clearly defined in the [Prot] documentation (see the scaling definition section, which refers to the fifth volume) 10.1.1.2. Definitions in [Req. 5.1.1.2. B] and [Req. 5.1.1.2.c] are optional: Use the <aguiserverurl> label in the XML Description document of AG to define the URL pointing to the XML UI. Note that the UPnP Device description of Ag can be (May) compatible with Level 1, 2 Remote UI servers defined in CEA-2014 specifications in its UPnP Device hierarchy that point to the same xml ui listing. if you understand UPnP, translate it.

 

-- Ig allows the discovery of IPTV service commands to penetrate the HNI-IGI interface defined in the [Prot] device, which is totally different from level 1, 2 Remote UI servers. For more information about ig device discovery, see 10.1.1.1 in [Prot.

 

========================================================== ========================================================== =

Irrespective of the box models, and the discovery mechanic used, the oitf performs the following general steps to set up a connection to any Internet or in-home service:

 

Regardless of the box model or the trial of the discovery mechanism, oitf performs the following steps to access Internet or Intranet services:

 

1) Setup & connect phase:
A. The oitf connects to a URL of a dae application offered by a server over an HTTP connection.
Oitf's capability profile is conveyed to the server, using the "User-Agent" HTTP header, to enable
Server to adjust the contents to the Dae capabilities of the oitf. An oitf that supports additional
Content formats (e.g. Flash) can also convey these extensions to the server.
B. After setting up the connection, the XHTML and/or SVG contents that constitute the Dae application are
Downloaded to the oitf.
C. This connection can also be set up by a separate UI control point in case of an oitf that supports a 3-box
Model.

 

2) presenting web content:

A. After downloading the XHTML and/or SVG contents, the Dae application may become active and

Display a user interface as defined by the XHTML and/or SVG contents.
3) controlling the UI:

A. Remote Control, keyboard and mouse events can be handled within scripts.
B. Native Control for web forms and spatial navigation must be supported.
C. client-side scripting control for the playback of A/V content must be supported.
4) Dynamic UI updates:

A. user interfaces can be dynamically updated by the server using a persistent TCP connection (internal socket)

Or through XML updates over an HTTP connection (Ajax ).
5) 3rd party communications:

Notification messages linked to UI content can arrive on the oitf outside of an active UI interaction between
Oitf and the server.

 

1) configuration and connection phase:

A. oitf uses a URL Based on the HTTP protocol to connect to the Dae application located on the server. The oitf capability (function) configuration informs the server by using the "User-Agent" Field of the HTTP header information, this option is used as a server to implement adaptive content (reply) based on the oitf Dae capability ). Oitf can support a content format (such as flash), and this change can also be used to notify the server.

B. After the connection settings are complete, the Dae application composed of XHTML and SVG will be downloaded to oitf.

C. If oitf supports the 3-box model, the connection configuration can be completed by another isolated UI control point.

2) display web content:

A. After the contents of XHTML or/and SVG are downloaded, the Dae application will be activated and display the user interfaces defined in XHTML and SVG.

 

3) control the UI:

A. Remote Control, keyboard, and mouse events can be captured and processed by scripts.

B. Local Control and spatial navigation for web forms must be supported.

C. client scripts that control audio and video playback must be supported.

 

4) Dynamic UI update:

A. the UI can be dynamically updated by using a persistent TCP connection (TCP connection) or XML data update through HTTP connection (Ajax.

 

5) third-party notifications:

The notification messages connected to the UI content can be transmitted to oitf by activating (active) the UI between oitf and the server.