HSI10_PD_PHASE2.pdf

HSI10 HD/SD SDI Universal databridge with monitoring outputs A Synapse® product

COPYRIGHT  2010 AXON DIGITAL DESIGN BV ALL RIGHTS RESERVED NO PART OF THIS DOCUMENT MAY BE REPRODUCED IN ANY FORM WITHOUT THE PERMISSION OF AXON DIGITAL DESIGN BV.

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Block schematic & I/O panel

BPH04 BHX04

HD/SD SDI INPUT (OPTIONAL FIBER INPUT) HD/SD SDI PREVIEW OUTPUT HD/SD SDI PROCESSED OUTPUT 1 HD/SD SDI PROCESSED OUTPUT 2 (OPTIONAL FIBER OUTPUT)

CVBS PREVIEW OUTPUT ETHERNET

GPI INPUT

December 2010

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Features The HSI10 is a standalone card that enables meta data, especially Teletext (WST-B) data, to be encoded onto a program feed; it will allow the captions to be previewed on the optional monitoring outputs using an On Screen Display (OSD) to simulate the output of a decoder. This card is able to insert NEWFOR, OGP (Open captions) and AODB (Raw ANC, OP47-SDP) protocol on screen.

Typically this functionality has been serviced by 1RU box, single PSU solutions from specialist subtitling companies, so the modular HSI10 should save on rack space, increase reliability and be more cost effective, certainly in multi-channel applications.

 

       

SD and HD-SDI compatible Formats:  1080i/50/59.94  720p/50/59.84  625/50  525/59.94  625/50  525/59.94 Insert incoming data from the NEWFOR and AODB (Axon Open Data Bridge) protocol in a parallel WST-B format or OP47 Insertion and monitoring of the encoded signal as ‘burnt-in’ captions or pages over the program stream on HD/SD-SDI or SD/CVBS outputs Preview inserted OGP protocol and text decoder Ability to Clear-Caption in the event of a ‘hanging’ caption.

Ethernet connector for Teletext, NEWFOR, OGP and AODB data input Locks to SDI input Full control and status monitoring through the front panel of the SFR04/SFR08/SFR18 frame and the Ethernet port (ACP) Optional 1 fiber input (replacing 1 SDI input) or 1 fiber output (replacing 1 SDI output) on I/O panel

Applications The HSI10 will typically be used in applications where Teletext subtitling is required on the program stream as part of the play out process. Generally this will be for live captioning where the program material is not available in time for the captions to be pre-prepared and added to the program material as part of the production process.

The subtitle data stream will normally be generated either from a subtitle preparation workstation directly or from a subtitle transmission product.

Ordering information Module:  HSI10: Caption and Teletext encoder with monitor outputs Standard I/O:  BPH04_HSI10: I/O-panel for HSI10 Relay bypass I/O: BHX04_HSI10: I/O-panel for HSI10 with relay bypass



Fiber outputs: BPH04T_FC/PC_HSI10: I/O-panel for HSI10 with fiber transmitter on FC/PC BPH04T_SC_HSI10: I/O-panel for HSI10 with fiber transmitter on SC

 

Fiber inputs: BPH04R_FC/PC_HSI10: I/O-panel for HSI10 with fiber receiver on FC/PC BPH04R_SC_HSI10: I/O-panel for HSI10 with fiber receiver on SC

 

December 2010

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Specifications SD/HD Serial Video Input Nunber of Inputs

1

Standard

625/50 or 525/59.94 SMPTE 259M-C (270Mb/s) with SMPTE 272M embedded audio SMPTE 292M (1.5Gb/s), SMPTE 260M, SMPTE 274M, SMPTE 296M, SMPTE 349M 1080i/59.94, 1080i/50, 720p/59.94, 720p/50 Automatic to 100m @ 1.5Gb/s with Belden 1694A or equivalent cable.

Equalization

Serial Video Output Standard Number of Outputs

3 (1 preview and 2 processed)

Signal Level

800mV nominal

DC Offset Rise and Fall Time Overshoot Return Loss Wideband Jitter

0V ±0.5V 750ps nominal for SD < 10% of amplitude > 15dB up to 270MHz < 0.2UI

Analog Video Output Standard Number of Outputs Connector Signal Level Impedance Return Loss Frequency Response Differential Gain Differential Phase SNR

PAL (ITU624-4) or NTSC (SMPTE 170M), Component, YC and RGB 1 BNC 1V nominal 75 Ohms > 35dB to 10MHz 0.5dB to 4.5 MHz < 0.6% < 0.7° > 75dB

Ethernet Standard Connector

10Base-T, 100Base-Tx IEEE 802.3 8P8C

Reference Video Input Standard Number of Inputs Connector Signal Level Impedance Return Loss

PAL (ITU624-4), NTSC (SMPTE 170M) 2 on SFR18, 2 on SFR08, 1 on SFR04 BNC 1V nominal High impedance, with loop for termination > 25dB to 10MHz

World System Teletext Standard

WST-B ETSI EN 300 706 V1.2.1 (2003-04)

OP47 Standard

....

Miscellaneous Weight Operating Temperature Dimensions

December 2010

Approx. 250g 0 °C to +50 °C 137 x 296 x 20 mm (HxWxD)

MISCELLANEOUS VIDEO PROCESSING

Electrical Voltage Power

December 2010

+24V to +30V <10 Watts

Video Processing

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Axon Open Data bridge Protocol specification Pascal Claes Axon Digital Design April 2010 Document Version 0.4

Introduction This document specifies the Axon Open Data Bridge protocol known as AODB protocol.

Informative References RFC 2030 - Simple Network Time Protocol (SNTP) Version 4.

ETS 300706 – Enhanced Teletext specifications OP47 – Free TV Australia Operational Practice-47

AODB Protocol Specification AODB is a simple protocol, layered on top of TCP/IP, intended to allow the transfer VBI, ANC or OP47 information from 3rd party transmission products to Axon systems or reversed. Each message has a standard header. Message acknowledgment mechanism is supported by the protocol. A periodic heartbeat mechanism is included to keep the connection ‘alive’.

This document defines a generic specification of the protocol; and may be taken as definitive.

Message Format All AODB messages have the following generic format, where the field lengths are in bits unless otherwise stated: Struct AODB_message () { Message Start code; Command Id; Continuity counter; Message length; for ( I=0; i<N; I++) { Meta_data_field() ; } || slot_number || NULL } Field Message Start code Command Id Continuity counter Message length Packet data

December 2010

Type Unsigned integer Unsigned integer Unsigned integer Unsigned integer Meta_data_field()

Length 16 16 16 16 Variable

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Message Start code This is a fixed 16 bit field identification at the start of a message. Message start code is always defined to the following value 0xa0db.

Command Id Command to perform specifies a particular AODB message.

Continuity counter This is a sequence indicator. This value assumes a wrap around from 0xffff to 0x0000.

Length This field contains the total number of bytes in a packet data field.

Packet data Interpreted at the application level and is present for all Axon application messages

December 2010

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Protocol Operation The AODB protocol is meant to communicate between two devices. Typically one party will be Axon equipment and the other side will be a 3rd party application. This protocol can also be used in between Axon devices. In general, a server implementation will communicate with single ‘clients’; OADB is designed as point-to-point connection.

The protocol operates in generally between Axon device which can insert or grab Meta video data like VBI, ANC or OP47 packages and a 3rd party software which generate these data.

System Support The protocol specified relies on some primitive elements which in an actual implementation would normally be supplied by an operating system. These are a TCP/IP implementation and a timer mechanism.

Time and time synchronization A Protocol end-point assumes in cases a absolute time must be interpreted the time on both endpoints are in sync. Preferred time synchronization method is with simple NTP see RFC2030.

Example: usage as slots with time schedule.

Data alignment All basic multi byte types are MSB encoded in the TCP stream. Signed integers are in two's complement notation.

The processor’s unsigned arrhythmic is assumed to be such that the processor wrap max_int to 0 on an increment.

Slots Slots are internal buffers at the end points for incoming data. They are used to schedule Meta data insertion to the (video) backend application. An end point supports one or more (max 255) slots which can setup buffer specific properties like: Operation mode: real time or user commended Active video lines: In which line(s) should the Meta data inserted Insertion method: Overwrite, use when empty, append …

Priority: priority 1..10 lowest is highest. In case multi slot needs to be inserted on the same moment priority decides which slot will really be inserted.

Time: At which time the buffer must inserted (use simple ntp for time synchronization) Interval: interval time in seconds (interval time between two insertions) Repeat count: how many times the slot should be repeated Duration: Duration how many seconds this buffer should be on air Note: The Axon device (end-point application) decides if and how many of these slots are allowed and which capability’s they have. The end-point will provide configuration methods for these slots. Configuring slots and slot behavior are not part of the protocol. Only the address method of slots are used and defined by this protocol and the commands or data-types. Slots can handle only one sort of lines at ones.

State Variables The protocol handler must maintain the following state variables, where unsigned integer is an 8 bit unsigned integer. The values assigned are their initial values: bool connection_active = false; bool is_client = true; Unsigned integer continuity_indicator = 0xffff The is_client Boolean value reflects the kind of endpoint for initializing this connection.

The processor’s unsigned arithmetic is to be such that the continuity_indicator will wrap from 0xffff to zero when incremented.

December 2010

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Protocol procedures The following procedures comprise an operational definition of the protocol (excluding the functionality implied by the reception of specific commands at a client).

Initialization Initialization procedure of the protocol will be handling the following steps after the setup of the TCP endpoint.

Step 1: Initiate the state variables to there initial value.

Step 2: Setup watchdog timer Step 3: Setup timeout timer Step 4: connection_active = true

Heartbeat handler Step Step Step Step

1: 2: 3: 4:

Increment continuity_indicator Send a formatted AODB heard beat message heartbeat counter = 0 Schedule next heartbeat after 5 seconds

Receive handler Step Step Step Step

1: 2: 3: 4:

Decode AODB message Reset heartbeat timer to 5 seconds Reset timeout timer to 15 seconds Pass message body to application

Close connection Step 1: Disable heartbeat timer Step 2: Disable timeout timer Step 3: close TCP end-point Error handler Step 1: Switch (error) Case Heartbeat time out handler: Increment continuity counter Resend heartbeat Increment heartbeat counter Case Timeout handler: connection_active = false start timer reconnection time out (15 sec) close connection case Reconnection handler: stop all timers flush all slots stop all meta data insertion re-establish the TCP server listener case Discontinuity counter is discontinue Ignore

December 2010

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Protocol Timeouts It may be deduced from the previous procedural definition that several timeout values are assumed by this protocol.

Heartbeat timeout: A Heartbeat message should be sent every 5 seconds by the client.

Connection timeout: A connection inactivity state occurs if no message is detected by a protocol handler within 15 seconds (3 missed heartbeats).

Reconnection timeout: If no messages are detected for a total period of 45 seconds the connection is be reset by the server. A connection reset requires that any existing activity (video data insertion) is terminated and all information received during any previous connection is discarded.

Protocol Commands The following 16bit commands are defined: Command Name

Code

Heartbeat

0x0001

Slot On-air

0x0002

Slot Off-air

0x0003

Send Data

0x0004

Configure Fill data

0x0005

Flush

0xFFFF

Heartbeat command The Heartbeat command is initiated by client side parties in a connection at a nominal rate of once every 5 seconds.

The client initiates a heartbeat every 5 seconds. Length is always 0 bytes; Message Format Command Id Length Packet data

0x0001 0 <NULL>

Slot On-air The on-air command is send in a connection to activate a pending slot. The pending buffer will handled at first available slot. Only slot which is in the on-air state will put data into the video line(s).

Command Id Length Packet data

0x0002 1 slot number

Slot Off-air When the client gives off-air command the data pending in queue will be discarded and no longer inserted in an available slot in the video. (Retransmissions are stop for the pending data) Command Id Length Packet data

December 2010

0x0003 1 slot number

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Send Data Transmit a chunk of data in ether way from client to server or server to client depending on the mode of the using Axon Device.

Message Format Command Id Length

0x0004 Size of Packet data depends on data type see?? < used data type >

Packet data

Configure Fill data Transmit a chunk of data to set fill data for missing packets. For each line or single on for all lines defined in a slot. Fill data will use to fill the line with data when there is noting to insert.

Command Id Length Packet data

0x0005 variable < used data type >

Flush Flush, clears slots and it related pending data and stop decoding or encoding the related data.

Flushing can be done for all pending slots at ones in this case Length is 0 and no packet data is send or send to a single slot by setting the length to value 1 and add the slot number as packet data to the message.

Command Id Length Packet data

0xFFFF 0 or 1 slot number or NULL

Flushing the slot is required on the following cases: Slot should do a different task as before.

Recovering after Reconnection timeout (all slots should be flushed).

A service of the slot is no longer needed (mostly before closing the connection between endpoints.

Flushing the slot gives the end-point implementation a trigger clean-up the slot.

Semantics for Meta data fields Basic layout for this Meta data type is: Struct Meta_data_field() { Meta_data_type; Slot number; Data_unit_lenght; for ( I=0; i<N; I++) { Line_adress; Data_block_lenght; Data_block; } }; Meta_data_type Slot number Data_unit_lenght Line_adress Data_block_lenght Data_block

December 2010

Unsigned integer 16 bit Unsigned integer 8 bit Unsigned integer 16 bit Signed integer 16 bit Unsigned integer 16 bit Variable length, data is byte (8 bit) oriented

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Meta-data type Data type for Meta data used for insertion in VBI, ANC or OP47 data. (16 bit field) WST-B Session layer

WST-B cooked OP47-SDP, like WST-B cooked.

OP47-SDP, like WST-B session EIA608 CC (line 21) cooked RESERVED VANC packet OP47-SDP packet CEA708-CDP packet RESERVED

For transmission of raw Teletext data. The receiving end-point creates the Teletext service. Arrange resend behavior etc.

For transferring transparent WST-b Teletext. The end point handles the WST-B transparent.

For transferring transparent WST-B Teletext. The end point handles the WST-B transparent. Packet as OP47 For transmission of raw Teletext data. The receiving end-point creates the Teletext service. Arrange resend behavior etc.

For transferring transparent use EIA608 CC Reserved for future Raw VANC packet transferring RAW OP47-SDP packet transferring RAW CEA708-CDP packet transferring Reserved for future use

0x0001

0x0002 0x0003

0x0004

0x0005 0x0006..0x 03FF 0x4000 0X4001 0X4002 0x4003…0 xFFFF

Slot number This is the address of the internal buffer at which the data should be delivered. Delivered data to disabled or non existing slot should be discarded by the application. (8 bit field) Data unit length The data_unit_length is the total size of the Meta data in this object. Counted for all n lines included there data. (16 bit field) Line address Line address where the data must be located. Line number depends on the use the current video system. A code 0xFFFF is reserved for “don’t care”, use first available as defined in target slot.

(16 bit field).

Data block length Total length the data block for this line. (16 bit field) Data block The associated data block for VBI, ANC or VANC data.

December 2010

MISCELLANEOUS VIDEO PROCESSING

Video Processing

Meta Data block Descriptions WST-B session layer Command header

Fix code to tell the application which command this packet performs

8 bit code

Data

The data of the packet

42 byte, binary data (msb)

Command byte is defined as: 0x00 Open page

Contains information about the page

0x01

Close page

Tell application this it was end of data for the page

0x02

Send txt row

Rows, content of the page always 42 byte start. Include the row start with magazine number and row number. (7 bits data, application will calculate parity)

0x03

On-air

Page in on-air loop

0x04

Off-air

Page is off-air

0xFF

Reset buffer

Clear all pending data

The open page command: 0

Magazine

1 byte

The magazine number of the page

1

Page Number

2 byte

Page address 0X100..0X8FF msb coded unsigned int (16 bit)

3

S1..S4

4 byte

one byte for each digit

7

C4..C14

2 Byte

Page control bits C4 Erase Page lsb 20 C5 News Flash lsb 21 C7 Suppress Header C8 Update C9 Interrupted Sequence C10 Inhibit Display C11 Magazine Serial C12,C13,C14 National option Character set

9

Page header packet

32 Byte

Fix length data text (7 bits data parity calculation is done by application)

41

stuffing

1 byte

0xff stuffing byte

December 2010

MISCELLANEOUS VIDEO PROCESSING

Video Processing

The closed page and reset buffer command has no data. Limitation is that we can open only one page for each magazine.

Page on-air and off-air commands are followed by the page number 16 bit unsigned other data is stuffed. This command brings a single page on or off air. The slot must be on-air to start the WST-B insertion.

Session layer typical transmission Clear buffer()

Page_on-air(889)

Open page(888)

â&#x20AC;Ś

Send txt row()

Page_off-air(888)

..

Open page(888)

Send txt row()

Send txt row()

Close page()

Close page()

Page on-air(888)

Page on-air(888)

Open page(889)

Page off-air(888)

Send txt row() Close page()

Page_off-air(889)

WST-B cooked Raw WST-B line: length can be ether 42 bytes or 45 byte WST-B teletext serviced line. The data lines are ready for transmission so parityâ&#x20AC;&#x2122;s are well calculated. Msb first oriented.

42 Byte 45 Byte

Data contains the WST-B data lines: (each block of 1 byte) Data contains the WST-B data lines:

December 2010