The Web-based Signage Business Group is aimed at companies and organizations interested in the standardization of Web based digital signage. The goal of the group is to identify use cases and system image/model for expansion of web browser based digital signage and smarter integration of existing Web standards.
- 1 Deliverables
- 1.1 Web-based Signage Use cases and Requirements
- 1.2 Architecture and Requirements for Web-based Signage Player
- 2 F2F Meetings
- 3 Teleconference
Web-based Signage Use cases and Requirements
"Web-based Signage Use cases and Requirements" provides use cases and requirements that indicate what Web-based Signage is. The aim of this document is to clear up how Web-based Signage is used and what functions are needed for Web-based Signage.
- [Web-based Signage Use cases and Requirements] (Official Report)
- Web-based Signage Use cases and Requirements (Editor's Draft)
- Web-based Signage Scenarios and Use Cases (Obsoleted)
We are planning to publish this document as a group note by April 2013.
Architecture and Requirements for Web-based Signage Player
Architecture of Web-based digital signage
[ Editor's Draft ]
This document describes architecture of web-based digital signage services in the terminal device. The various implementation models based on general web signage architecture are described. Also, the mapping with functions of digital signage defined in “Recommendation ITU-T H.781, Digital Signage – Functional Architecture”.
This profile defines the basic requirements of web-based signage, such as playlist, transition effects, tickers, etc. It defines just requisite minimum for web-based signage. But it covers most of existing simple signs which show a still image or a html document for each scene. This profile also introduces the way to implement the requirements.
The other requirements which aren't included in this profile will be defined in other profiles or extensions.
Basic Media Profile
This Profile defines requirements for playing videos and audios which are downloaded from web servers or which are pre-fetched and stored in terminals. Protecting media data and streaming are out of scope. When we need them, we will make a profile as an extension.
This Profile defines requirements for storing downloaded files and playing the stored contents in the terminal
Web-based Signage is basically assumed to be online. But some signage terminals are connected to a narrowband network, some signage terminals use a time-limited network. Especially when playing videos, instability of the the network quality could cause a service outage.
Storing contents and playing the stored contents ensure that contents are played reliably regardless of the state of the network, the network traffic is reduced, and web-based signage services are cost-effective. Storing contents and playing the stored contents are essential for web-based signage.
Basic Reporting Profile
This profile defines what type of information should be stored in terminals, and uploaded to log servers (for example, the time when an ad started to be shown). This profile defines just requisite minimum. When we need more information as reporting, we will make a profile as an extension.
Interactive Menu Profile
This profile defines basic functions for interactive menu. There are many types of interactive signs which show some buttons on the screen. When a user touch a button, the sign starts to show information related the button. This profile also defines touch log.
Emergency Information Profile
[ Editor's Draft ]
Emergency Information should be handled in somewhat unified manner (display format) for the people to easily perceive and understand the information to minimize confusion during emergency. Actual style and format of expressing the emergency information are national regulatory matter. This profile defines how emergency information should be shown on signs using web technology.
This profile defines more sophisticated scheduling than the core profile. It is planed to be based on ISO8601.
- 22-23 November 2016: Group meeting at Seoul
- 22-23 September 2016: Group meeting at TPAC 2016
- 29-30 October 2015: Group meeting at TPAC 2015
- 1-2 November 2012: Group meeting at TPAC 2012
- 22 June 2017: Minutes