OIPF 规范翻译（DAE）-----4.1.1 Remote UI and box models (Informative)

4.1.1 Remote UI and box models (Informative)

4.1.1 远程UI和box模型

 

The architecture overview from CEA 2014 Section 4.1 defines various box models. Next to the i-Box model for
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规范4.1节中描述了很多种box模型体系。在i-Box（用来访问IPTV服务或第三方的互联网服务）模型定义之后，同时为住宅内（家庭网络）的远程UI定义了2-Box，3-Box模型。Box模型中，发现和设置（setup）远程UI连接不仅可以在服务器所在的位置，也可以在UI控制点驻留的地方。如果是2-Box和3-Box模型，其UI控制点一般是一个家庭网络服务器上的Upnp控制点（Control Point），如果是2-Box模型，其UI控制点是一个OITF内的UPNP控制点。如果UPNP远程UI控制点在一个外部设备中（例如：web pad, remote controller，我理解为远程的主机之类），就需要依赖远程设备列出远程UI服务器的地址，并通过配置使OITF连接到远程UI服务器上，这种称为3-Box 模型。OITF要支持3-Box模型，其自身必须能够通过Upnp协议被发现（是否指的是内网穿透之类，译注），并且通过家庭网络能暴露其作为UI客户端的配置信息。

 

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

For the OITF, only 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 the
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 the
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 discovery 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].

 

OITF中，仅有CEA2014中定义的i-Box模型是必选支持的。2-box和3-box都是可选项。默认情况下，其与AG（应用程序网关），IG（IMS网关），CSPG（CSP网关）的交互方法如下所示。当然，也不能排除位于家庭网络内的遵循CEA2014规范的AG,IG,CPSG来作为UPNP远程UI服务器。例如可以在OITF的配置屏幕上向其提供远程UI。

 

--AG可以看成是CEA-2014-A 5.1.1.2中定义的第一级远程UI服务器，和CEA 5.1.1.2中定义的不同之处是有一个不一样的设备描述。AG设备的描述在[PROT]文档（参见缩略定义部分，指第五卷）10.1.1.2中有明确定义。[Req. 5.1.1.2.b] 和[Req. 5.1.1.2.c] 中的定义是可选支持的：AG的XML描述文档中使用<agUIServerURL>标签定义指向XML UI的URL。需要注意的是，AG的UPNP设备描述可以（MAY)和CEA-2014规范中定义的级别1,2远程UI服务器相兼容in its UPnP device hierarchy that point to the same XML UI listing. 懂UPNP的兄弟帮忙翻译一下。

 

--IG允许发现IPTV服务的命令穿透[PROT]设备中定义的HNI-IGI接口，这和1,2级别的远程UI服务器完全不同。IG设备发现的详细内容请参考 [PROT]文档的10.1.1.1部分。

 

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

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

 

先不管box模型，也不说发现机制的试用，OITF通过如下步骤完成接入互联网或家庭内网服务：

 

1)  Setup & Connect phase:
A.  The OITF connects to a URL of a DAE application offered by a server over an HTTP connection. The
OITF’s capability profile is conveyed to the server, using the “User-Agent” HTTP header, to enable the
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 (NotifSocket)

or through XML updates over an HTTP connection (AJAX).
5) 3rd Party Notifications: 

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

 

1） 配置和连接阶段：

A. OITF基于HTTP协议，使用一个URL连接到位于服务器上的DAE应用程序。OITF的能力（功能）配置会通过使用HTTP头部信息的“User-Agent”字段告知服务器，此选项用来作为服务器根据OITF的DAE能力来做相应的自适应内容（回复）。OITF可以增加一种内容格式支持（例如FLASH），并且这种变化也可以通过此种方式通知服务器。

B. 连接设置完成后，由XHTML和SVG组成的DAE应用程序会下载到OITF.

C. 如果OITF支持3-box模型，其连接配置可以由另一个隔离的UI控制点完成。

2）显示Web内容：

A. XHTML或/和SVG的内容被下载以后，DAE应用将会激活并显示在XHTML、SVG其中定义的用户接口。

 

3）控制UI：

A.遥控器，键盘，鼠标事件可以被脚本捕获处理。

B.必须支持针对web表单的本地控制和空间导航。

C.必须支持控制音视频播放的客户端脚本。

 

4）动态UI更新：

A.通过使用持续TCP连接（TCP常连接）UI可以动态更新，或者通过HTTP连接（AJAX）使用XML数据更新来做到UI更新。

 

5）第三方通知：

连接到UI内容的通知消息可以传达到OITF，方法是通过OITF和服务器之间的激活（活跃）UI.