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.