Introduction of Web-based Signage JS Playerand proposal of APIs

22 September 2016

W3C TPAC 2016 Lisbon / Web-based Signage BG Group Meeting

@futomi

Newphoria Corporation• Offers complete web development services

• Client-side: PCs, Smartphones, Embedded devices• Server-side: Clouds (AWS, etc.)

• Offers mobile app development services• Developing apps for Android, iOS• Offering Hybrid app development environment service

• applican (http://www.applican.com/)

• Offers digital signage solutions• Creating contents for digital signage• Developing CMS, JS Player

2

JS Player• Newphoria had developed signage players as R&D for years

• All players are developed using only Web technologies• HTML, CSS, JavaScript, HTTP, WebSocket, etc.

• The players were developed mainly for Enbedded devices• TV sets (Linux, Android TV), STBs (Linux, Android), etc.

• Newphoria released a commercially based JS Player in 2016• Licensing, Customizing for digital signage operators:

• NTT Hikari Signage, etc.• For now, supporting SONY BRAVIA (Linux, Android TV)

• Planning to support all TV sets for Japan market, which implement a web runtime for digital signage (Panasonic AF1, LG WebOS, etc.)

3

Field Test• TPAC 2015 in Sapporo, Japan

• Newphoria provided the R&D-based JS Player• The player played contents in multivendor environment• TOSHIBA, SONY, Panasonic, Mitsubishi Electric

• INTEROP TOKYO 2016 in Makuhari, Japan• Newphoria provided the commercially based JS Player• NTT provided the digital signage service “Hikari Signage”• SONY provided many TV sets “BRAVIA”

4

TPAC 2015

INTEROP TOKYO 2016

Architecture of Web-based Signage System

10

Web Server

WebSocket Server

Fetch the player

Fetch the playlist (JSON)

Fetch the contents (image, video)

Send logs

Push emergency messages

TerminalPush commands

CMS

Adjust clock (Kind of like SNTP)

Manage the terminalsLocation, Model name, IP address, HW Serial number, etc.

Create playlistsTime schedule for each content

Upload contentsimages, videos, etc.

Push commands to terminalsReboot, Updating contents, etc.

Architecture of Browser-based Player

11

Hardware (STB, TV Panel)

OS (Linux, Windows, Android, Firefox OS, etc.)

Web Browser Runtime (Gecko, Edge HTML, WebKit, Blink, etc.)

JS Player (JavaScript-base Web Application)

HTML Contents Image/Video Contents, Ticker

Terminal

From CMS via Internet

JavaScript APIs- Standardized APIs- Proprietary APIs

Architecture of App-based Player

12

Hardware (STB, Tablet)

OS (Android, iOS)

Web Browser Runtime (WebView)

JS Player (JavaScript-base Web Application)

HTML Contents Image/Video Contents, Ticker

Hybrid Apps (applican)

Terminal

From CMS via Internet

JavaScript APIs- Standardized APIs- Proprietary APIs

Lack of APIs• In my experiences, the standardized APIs are not enough for digital

signage player• Useful APIs for digital signage are provided by TV set manufacturers as

proprietary APIs• I hope that non-competitive common APIs are standardized

• I’d like to propose that such APIs are added to the WG charter document

• Device Information API• Network Information API• Display Setting API• NTP Server Setting API

13

Device Information APIs

14

• This API allows us to get the information of the device

• Hardware serial number• Manufacturer name• Model number• Friendly name

Network Information API• This API allows us to get the setting of the network

• Type of network (Ethernet, Wi-Fi, etc.)• IP version (IPv4, IPv6)• IP address of the terminal• Subnet mask• IP address of the default gateway• DHCP (true or false)• IP address of the DNS• MAC address of the terminal

15

Display Setting API• This API allows us to get and change the setting of the display (panel)

• Power (ON/OFF)• Brightness• Contrast• Volume (if speakers are built in the panel)• Mute (if speakers are built in the panel)

16

NTP Server Setting API• This API just get and set the IP address or host name of the NTP server

to the underlying OS• Signage operators sometimes want to change the address of the NTP

server set in terminals• If the operator manage a lot of terminals, changing the setting remotely

is useful

17

Thank you for listening

@futomi