lc / vs902 j2ke( 3g) j2kd( 3g) / vs902 j2kc / vs902 manevion nordre kullerød 1 3241 sandefjord...

Nevion Nordre Kullerød 1 3241 Sandefjord Norway Tel: +47 33 48 99 99

nevion.com

VS902-AED / VS902-LC / VS902-J2KE(-3G) VS902-J2KD(-3G) / VS902-J2KC

/ VS902-MA

Multi-Format Media Contribution Codec for IP/Ethernet Networks

User Manual

Document No. 22260-0902

Rev. D

VS902 Rev. D

nevion.com | 2

Nevion Support

Nevion Europe

P.O. Box 1020 3204 Sandefjord, Norway

Support phone 1: +47 33 48 99 97 Support phone 2: +47 90 60 99 99

Nevion USA

1600 Emerson Avenue Oxnard, CA 93033, USA

Toll free North America: (866) 515-0811 Outside North America: +1 (805) 247-8560

E-mail: [email protected]

See http://www.nevion.com/support/ for service hours for customer support globally.

Revision history

Current revision of this document is the uppermost in the table below.

Rev. Repl. Date Sign Change description

D C Feb 12, 2015 MB Removing the watermark; updating sec. 5.2.8

C B Aug 31, 2014 SH Add MADI, bidirectional J2K codec and J2K-3G functionality plus software license information. Support for V2.0 firmware release.

B A Nov 20, 2013 SH Updated to reflect new functionality introduced in firmware releases V1.4 onwards.

A 1 Jul 24, 2013 SH Update for initial release following review by Engineering and Support teams

1 Jun 10, 2013 SH Initial draft

mailto:[email protected]

http://www.nevion.com/support/

VS902 Rev. D

nevion.com | 3

Contents

Contents ................................................................................................................... 3

1 Product overview ................................................................................................... 9 1.1 Warnings, Cautions and Notes ...................................................................................... 9

2 Description .......................................................................................................... 10 2.1 Ordering Options ..........................................................................................................12 2.1.1 Sales Products ..........................................................................................................12 2.1.2 License Options - Hardware ......................................................................................13 2.1.3 License Options - Software .......................................................................................13

3 Applications ......................................................................................................... 15 3.1 Bidirectional ASI Transport ...........................................................................................15 3.2 Unidirectional J2K Compression and Transport ............................................................15 3.2.1 Unidirectional J2K Compression for 3G Transport .....................................................16 3.3 Bidirectional J2K Compressed Transport .....................................................................16 3.4 Bidirectional Uncompressed Transport .........................................................................17 3.5 Bidirectional MADI Audio Transport ..............................................................................17

4 Specifications ...................................................................................................... 18 4.1 VS902-AED ..................................................................................................................18 4.1.1 DVB-ASI Inputs/Outputs ............................................................................................18 4.1.2 IP / Ethernet network .................................................................................................18 4.1.3 Processing: ...............................................................................................................19 4.1.4 Alarm Outputs: ..........................................................................................................19 4.1.5 General .....................................................................................................................19 4.2 VS902-J2K (inc. J2KE, J2KD, J2KC, J2KE-3G and J2KD-3G) .....................................20 4.2.1 Inputs/Outputs ...........................................................................................................20 4.2.2 IP / Ethernet network .................................................................................................20 4.2.3 Processing: ...............................................................................................................21 4.2.4 Alarm Outputs: ..........................................................................................................21 4.2.5 General .....................................................................................................................21 4.3 VS902-LC ....................................................................................................................22 4.3.1 Inputs/Outputs ...........................................................................................................22 4.3.2 IP / Ethernet network .................................................................................................22 4.3.3 Processing: ...............................................................................................................23 4.3.4 Alarm Outputs: ..........................................................................................................23 4.3.5 General .....................................................................................................................23 4.4 VS902-MA ....................................................................................................................24 4.4.1 MADI Inputs/Outputs .................................................................................................24 4.4.2 IP / Ethernet network .................................................................................................24 4.4.3 Processing: ...............................................................................................................24 4.4.4 Alarm Outputs: ..........................................................................................................24 4.4.5 General .....................................................................................................................25

5 Configuration ....................................................................................................... 26 5.1 VS902 Main Configuration ...........................................................................................27 5.1.1 Boot Modes ...............................................................................................................27 5.1.2 In-Band Management ................................................................................................28 5.1.3 VS902-AED ...............................................................................................................29 5.1.4 VS902-J2KE / VS902-J2KE-3G.................................................................................29 5.1.5 VS902-J2KD / VS902-J2KD-3G ................................................................................30 5.1.6 VS902-J2KC .............................................................................................................30 5.1.7 VS902-LC .................................................................................................................31 5.1.8 VS902-MA .................................................................................................................31

VS902 Rev. D

nevion.com | 4

5.1.9 Main Configuration Parameters .................................................................................32 5.1.10 Notes on Main Configuration ...................................................................................34 5.2 Input Channel Configuration .........................................................................................35 5.2.1 VS902-AED ...............................................................................................................35 5.2.2 VS902-J2KE / VS902-J2KC / VS902-J2KE-3G .........................................................36 5.2.3 VS902-LC .................................................................................................................37 5.2.4 VS902-MA .................................................................................................................38 5.2.5 Input Channel Configuration Parameters ...................................................................39 5.2.6 Notes on Input Channel Configuration .......................................................................43 5.2.7 Asymmetric Network Launch .....................................................................................44 5.2.8 J2KE Bitrate Setting ..................................................................................................45 5.3 VS902 Output Channel Configurations .........................................................................46 5.3.1 VS902-AED ...............................................................................................................46 5.3.2 VS902-J2KD / VS902-J2KC / VS902-J2KD-3G .........................................................47 5.3.3 VS902-LC .................................................................................................................48 5.3.4 VS902-MA .................................................................................................................49 5.3.5 Output Channel Configuration Parameters ................................................................50 5.3.6 Notes on Output Channel Configuration ....................................................................52 5.3.7 Output Channel Frame Sync .....................................................................................53 5.4 Alarm Settings ..............................................................................................................54 5.5 Alarm Configuration .....................................................................................................55 5.5.1 VS902-AED Alarm Settings .......................................................................................55 5.5.2 VS902-J2KE(-3G) / VS902-J2KC Alarm Settings ......................................................57 5.5.3 VS902-J2KD(-3G) / VS902-J2KC Alarm Settings ......................................................58 5.5.4 VS902-LC Alarm Settings..........................................................................................58 5.5.5 VS902-MA Alarm Settings .........................................................................................58 5.6 Alarm Priority Level Reset ............................................................................................59 5.7 Upload/Download Card Configuration Settings.............................................................60 5.7.1 Configuration Upload Procedure ...............................................................................60 5.7.2 Configuration Download Procedure ...........................................................................61

6 Installation ........................................................................................................... 62 6.1 Inspection .....................................................................................................................62 6.2 Handling .......................................................................................................................62 6.3 Grounding ....................................................................................................................62 6.4 Module Installation .......................................................................................................63 6.5 Installation Environment ...............................................................................................63

7 Connections ........................................................................................................ 65 7.1 Front and Rear Panel Diagrams ...................................................................................65 7.2 Front Panel LED's ........................................................................................................66 7.3 Rear Connector Panel ..................................................................................................67 7.4 Aux Data Port ...............................................................................................................69 7.5 Output Reference .........................................................................................................70 7.6 External Alarm Relay Output ........................................................................................70 7.7 SFP/SFP+ Options .......................................................................................................71 7.7.1 VS902-AED, VS902-J2K(all) and VS902-MA – 1Gbps SFP modules ........................71 7.7.2 VS902-LC – 10Gbps SFP+ and Twin-ax modules .....................................................71 7.8 Front Panel Maintenance Port ......................................................................................72 7.9 Video Monitor Port .......................................................................................................72 7.10 Switch Settings ...........................................................................................................72

8 Element Management ......................................................................................... 73

9 Card Status ......................................................................................................... 74 9.1 Status Summary ...........................................................................................................75 9.1.1 VS902-AED ...............................................................................................................75

VS902 Rev. D

nevion.com | 5

9.1.2 VS902-J2K ................................................................................................................78 9.1.3 VS902-LC .................................................................................................................82 9.1.4 VS902-MA .................................................................................................................84 9.2 Channel Name Status ..................................................................................................87 9.3 Input Status ..................................................................................................................88 9.3.1 VS902-AED ...............................................................................................................88 9.3.2 VS902-AED PMT/ES Status ......................................................................................90 9.3.3 VS902-J2KE(-3G) .....................................................................................................90 9.3.4 VS902-LC .................................................................................................................92 9.3.5 VS902-MA .................................................................................................................94 9.4 Output Status ...............................................................................................................95 9.4.1 VS902-AED ...............................................................................................................95 9.4.2 VS902-J2KD(-3G) .....................................................................................................98 9.4.3 VS902-LC .................................................................................................................99 9.4.4 VS902-MA ............................................................................................................... 101 9.5 License Status............................................................................................................ 103 9.6 Fallback Mode ............................................................................................................ 104 9.7 Fallback Recovery ...................................................................................................... 105

10 Protection Features ......................................................................................... 106 10.1 Forward Error Correction (FEC) ............................................................................... 106 10.2 Streaming Intelligent Packet Switching (SIPS) ......................................................... 106 10.3 Encoder Partner Protection (EPP) ............................................................................ 108 10.3.1 EPP Configuration ................................................................................................. 110 10.4 Output with SIPS protection ..................................................................................... 112 10.5 Launch Delay Offset (LDO) ...................................................................................... 113

11 IP Specific Configuration ................................................................................. 114 11.1 VLAN Tagging .......................................................................................................... 114 11.2 TOS/DSCP Marking ................................................................................................. 115

12 Remote Upgrade Procedure ............................................................................ 116

13 License File Installation ................................................................................... 120

14 Maintenance and Storage ............................................................................... 122 14.1 Maintenance ............................................................................................................ 122 14.2 Storage .................................................................................................................... 122 14.3 Operational Safety ................................................................................................... 122

Appendix A – Forward Error Correction ................................................................ 123 IP Stream Distortion ......................................................................................................... 123 Standardisation ................................................................................................................ 124 FEC Matrix ....................................................................................................................... 124 Transmission Aspects ...................................................................................................... 127 Quality of Service and Packet loss in IP Networks ........................................................... 127 Error Improvement ........................................................................................................... 128 Latency and Overhead ..................................................................................................... 130

Appendix B - Latency ........................................................................................... 132

Appendix C – Quality of Service, Setting Packet Priority ...................................... 134 MPLS ............................................................................................................................... 134 Layer 3 Routing ................................................................................................................ 134 VS902 TOS Configuration ................................................................................................ 134 Layer 2 Priority ................................................................................................................. 135 VS902 COS Configuration ............................................................................................... 135

Appendix D - Glossary .......................................................................................... 136

VS902 Rev. D

nevion.com | 6

Table of Figures

Figure 1: VS902 Main Board ..............................................................................................11 Figure 2: Block Diagram of the VS902 Signal Flows ..........................................................11 Figure 3: Multiple ASI Signals over Gigabit Ethernet Network ............................................15 Figure 4: Compressed unidirectional HD/SDI Signals over Gigabit Ethernet Network ........16 Figure 5: Compressed unidirectional 3G/HD/SDI Signal over Gigabit Ethernet Network ....16 Figure 6: Compressed bidirectional HD/SDI Signals over Gigabit Ethernet Network ..........16 Figure 7: Multiple 3G/HD/SD-SDI Signals over 10 Gigabit Ethernet Network .....................17 Figure 8: Multiple MADI Signals over 1 Gigabit Ethernet Network ......................................17 Figure 9: VS902 Control Settings .......................................................................................26 Figure 10: VS902 Card Functional Mode Configuration .....................................................27 Figure 11: VS902-AED Control Settings – Main Configurations .........................................29 Figure 12: VS902-J2KE(-3G) Control Settings – Main Configurations ................................29 Figure 13: VS902-J2KD(-3G) Control Settings – Main Configurations ................................30 Figure 14 VS902-J2KC Control Settings - Main Configurations ..........................................30 Figure 15: VS902-LC Control Settings – Main Configurations ............................................31 Figure 16: VS902-MA Control Settings – Main Configurations ...........................................31 Figure 17: VS902-AED Control Settings – Input Channel Configurations ...........................35 Figure 18: VS902-J2KE(-3G)/VS902-J2KC Ctrl Settings – Input Ch. Configurations ..........36 Figure 19: VS902-LC Control Settings – Input Channel Configurations ..............................37 Figure 20: VS902-MA Control Settings – Input Channel Configurations .............................38 Figure 21: VS902-AED Control Settings – Output Channel Configurations ........................46 Figure 22: VS902-J2KD(-3G)/VS902-J2KC Ctrl Settings – Output Ch. Configurations .......47 Figure 23: VS902-LC Control Settings – Output Channel Configurations ...........................48 Figure 24: VS902-MA Control Settings – Output Channel Configurations ..........................49 Figure 25: VS902-LC Frame Sync Configuration ...............................................................53 Figure 26: Reference Input Alarm in Output Status ............................................................54 Figure 27: VS902-LC Alarm Settings .................................................................................55 Figure 28: Card Alarm Priority Level Reset ........................................................................59 Figure 29: Configuration Upload.........................................................................................60 Figure 30: Upload Configuration File Selection ..................................................................60 Figure 31: Upload Configuration Warning ..........................................................................61 Figure 32: Upload Configuration Succeeded ......................................................................61 Figure 33: Configuration Download ....................................................................................61 Figure 34: Front and Rear Panel Connector Diagrams .......................................................65 Figure 35: Aux Data Port Configuration ..............................................................................69 Figure 36: Aux Data Port Status .........................................................................................70 Figure 37: Element Management Home Page ....................................................................73 Figure 38: VS902-LC Status Menu .....................................................................................74 Figure 39: VS902-AED Card Status Summary ...................................................................75 Figure 40: VS902-J2KE Card Status Summary ..................................................................78 Figure 41: VS902-J2KD Card Status Summary ..................................................................79 Figure 42: VS902-LC Card Status Summary ......................................................................82 Figure 43: VS902-MA Card Status Summary .....................................................................84 Figure 44: Channel Description Display in Input/Output Status ..........................................87 Figure 45: Channel Name Status Menu .............................................................................87 Figure 46: VS902-AED Input Channel Status Summary .....................................................88 Figure 47: VS902-AED Input Channel Status Summary .....................................................90 Figure 48: VS902-J2KE(-3G) Input Channel Status Summary ...........................................90 Figure 49: VS902-LC Input Channel Status .......................................................................92 Figure 50: VS902-MA Input Channel Status Summary .......................................................94 Figure 51: VS902-AED Output Channel Status Summary ..................................................95

VS902 Rev. D

nevion.com | 7

Figure 52: VS902-J2KD(-3G) Output Status.......................................................................98 Figure 53: VS902-LC Output Channel Status .....................................................................99 Figure 54: VS902-MA Output Channel Status Summary .................................................. 101 Figure 55: Card License Detail Menu ............................................................................... 103 Figure 56: Card License Error .......................................................................................... 104 Figure 57: Channel License Allocation ............................................................................. 104 Figure 58: VS902-Fallback mode ..................................................................................... 105 Figure 59: VS902-FB Control Settings ............................................................................. 105 Figure 60: VS902-FB Card Status Summary .................................................................... 105 Figure 61: FEC Configuration ........................................................................................... 106 Figure 62: VS902 Diverse Path Transmission .................................................................. 106 Figure 63: VS902 Receive SIPS Protection ..................................................................... 107 Figure 64: VS902 Receive SIPS Protection Input Config.................................................. 108 Figure 65: VS902 Encoder Partner Protection .................................................................. 109 Figure 66: VS902 Partner Protection Master Config ......................................................... 110 Figure 67: VS902 Partner Protection Slave Config ........................................................... 111 Figure 68: VS902 Output SIPS Protection Config ............................................................ 112 Figure 69: VS902 Diverse Path Transmission with Perfect Packet Switching ................... 112 Figure 70: VS902 Encoder Partner Protection with Perfect Packet Switching .................. 112 Figure 71: VS902 Flow B Launch Delay ........................................................................... 113 Figure 72: VS902 VLAN tagging of IP packets ................................................................. 114 Figure 73: VS902 VLAN un-tagging of IP packets ............................................................ 114 Figure 74: TOS/DSCP Fields ........................................................................................... 115 Figure 75: VS902 TOS/DSCP Settings ............................................................................ 115 Figure 76: Impairments of an IP packet stream ................................................................ 123 Figure 77: IP packet FEC calculation matrix ..................................................................... 125 Figure 78: Two-dimensional FEC calculation ................................................................... 125 Figure 79: FEC matrix ...................................................................................................... 126 Figure 80: Offset FEC matrix with missing ....................................................................... 126 Figure 81: Uncorrectable error patterns ............................................................................ 126 Figure 82: FEC data transmission .................................................................................... 127 Figure 83: Error improvement using column FEC only ..................................................... 129 Figure 84: Error improvement using two-dimensional FEC ............................................... 129 Figure 85: Differentiated services (Diff-serve) and precedence bits (TOS) ....................... 134

Table of Tables

Table 1: VS902 Hardware Options .....................................................................................13 Table 2: VS902 Software License Options .........................................................................14 Table 3: VS902 Card Functional Modes .............................................................................27 Table 4: VS902 Control Settings – Main Settings ...............................................................34 Table 5: VS902 Control Settings – Input Channel Configuration ........................................42 Table 6: VS902 Control Settings – Output Channel Configurations ....................................51 Table 7: Genlock Signal Options ........................................................................................53 Table 8: VS902-AED Alarm Settings ..................................................................................57 Table 9: VS902-J2KE(-3G)/VS902-J2KC Alarm Settings ...................................................57 Table 10: VS902-J2KD(-3G)/VS902-J2KC Alarm Settings .................................................58 Table 11: VS902-LC Alarm Settings ...................................................................................58 Table 12: VS902-MA Alarm Settings ..................................................................................58 Table 13: Description of Front Panel VS902 LED's ............................................................67 Table 14: VS902-AED Rear Connector Panel I/O ..............................................................67 Table 15: VS902-J2K Rear Connector Panel I/O ...............................................................67

VS902 Rev. D

nevion.com | 8

Table 16: VS902-LC Rear Connector Panel I/O .................................................................68 Table 17: VS902-MA Rear Connector Panel I/O’s ..............................................................68 Table 18: Pin-out for the External Alarm Relay Output .......................................................70 Table 19: Recommended SFP Modules for 1Gbps interfaces ............................................71 Table 20: Recommended SFP+ modules for 10Gbps interfaces ........................................71 Table 21: S1 Switch Functions ...........................................................................................72 Table 22: Recommended error performance (as per ITU) ................................................ 128 Table 23: FEC latency and buffer size .............................................................................. 130 Table 24: Example Latency Components ......................................................................... 133

VS902 Rev. D

nevion.com | 9

1 Product overview

This manual is written for users of the Nevion VS902 Multi format media codec. It provides the necessary information for installation, configuration and operation of the product. The manual covers the following topics:

• Technical Specification

• Installation

• WEB interface description including configuration

• Alarm listings

• Maintenance The VS902 product range covers several different versions, however much of the configuration and usage is common and is therefore not repeated in this manual for every version.

1.1 Warnings, Cautions and Notes The following warnings, cautions and notes are used and highlighted in this manual as shown below:

Warning: This is a warning. Warnings give information, which if strictly observed, will prevent personal injury and death, or damage to personal

property or the environment.

Caution: This is a caution. Cautions give information, which if strictly followed, will prevent damage to equipment or other goods.

Note: Notes provide supplementary information. They are highlighted for emphasis, as in this example, and are placed immediately after the relevant

text.

VS902 Rev. D

nevion.com | 10

2 Description

The VS902 is a modular, multi-format contribution media codec for IP/Ethernet networks. There are several firmware variants of the product, all of which are based on the same hardware platform with two network interface options, providing 1 or 10Gbps connectivity. The Linear code version of the VS902 provides linear encapsulation and transport of uncompressed SD-SDI, HD-SDI, and 3G-SDI signals. The ASI version encapsulates DVB-ASI signals for transport. The J2K version provides the highest quality JPEG 2000 compression for contribution video over bandwidth limited circuits. The MADI audio version provides encapsulation of uncompressed MADI (AES10) interfaces. With the VS902, users can deploy multiple video/audio circuits in point to point local loop applications or over long-distance packetized networks. This flexible platform enables highly cost efficient video/audio transport over a common unified platform, accessing virtually any environment including long distance, metro area and campus networks. The ASI firmware supports four bidirectional ASI channels over GigE network. Up to four asynchronous or synchronous DVB-ASI (EN50083-9) inputs are supported and each are encapsulated in transport stream format data into a single IP stream output, on dual Gigabit Ethernet interfaces. The ASI receiver takes transport stream data from up to 4 UDP ports of the IP input, on dual Gigabit Ethernet interfaces and bridges the data onto up to 4 ASI outputs. Internet Group Management Protocol (IGMP) Version 1, Version 2 and Version 3 are supported and can be used in a network that supports IGMP V1, V2 or V3. SMPTE 2022-1 Forward Error Correction (FEC) & Nevion Streaming Intelligent Protection Switching (SIPS) protection are optional. The J2K firmware supports two unidirectional or one bidirectional, J2K compressed HD/SD-SDI video formatted channels: defined in SMPTE 292M, SMPTE 274M, SMPTE 296M or SMPTE 259M, with up to 4 pre-embedded AES (or Dolby-E/AC-3) audio groups and encapsulates the transport stream data into IP stream output on Gigabit Ethernet interfaces conforming to SMPTE 2022-1 and -2 (CoP3). The J2K Decoder performs the inverse function: Decompression and recovery of all signals as standards compliant video and audio outputs. SMPTE 2022-1 Forward Error Correction (FEC) & Nevion Streaming Intelligent Protection Switching (SIPS) protection are optional. In J2K mode, each card encodes two video channels, decodes two video channels or simultaneously compresses one video channel and decompresses a second channel. A J2K-3G mode is also available which supports compression or decompression of a single channel of any video standard including 3G. The Linear firmware supports four bidirectional Linear (uncompressed) HD/SD-SDI or 3x 3G-SDI channels over dual 10 GigE network interfaces. This firmware accepts up to 4x HD/SD-SDI or 3x 3G-SDI inputs and encapsulates each transport stream data into a single IP stream, output on 10 Gigabit Ethernet. The receiver takes transport stream data from up to 4 UDP ports of the IP input on a 10 Gigabit Ethernet interface and bridges the data onto up to 4x HD/SD-SDI or 3x 3G-SDI outputs. SMPTE 2022-5 Forward Error Correction (FEC) & Nevion Streaming Intelligent Protection Switching (SIPS) protection are optional. The above modes of operation are implemented by means of boot images supplied on the VS902. The card runs in one of these modes at any one time. The mode of operation can be changed by selection of the appropriate boot image from the configuration menus.

VS902 Rev. D

nevion.com | 11

The MADI version supports up to four bidirectional MADI interfaces (each of which can contain 64 audio channels) over dual 1 GigE Ethernet interfaces. The MADI version also supports standards compliant FEC and Nevion SIPS technology. All versions of the VS902 support an auxiliary data port which provides a means of aggregating IP data in addition to the transported video channel data. The VS902 has front panel LED indicators and external alarms for the presence or absence of the input signals. They also have comprehensive element management for system monitoring via SNMP or web browser. They are built in 3RU extended Eurocard (220 mm x 100 mm) modules designed to mount in the VS103 and VS101 family of Ventura frames. The video connections are made to the rear of the module, via a rear connector panel. Element Management and Chassis Alarm connections are made via the chassis backplane.

Figure 1: VS902 Main Board

Figure 2: Block Diagram of the VS902 Signal Flows

VS902 Rev. D

nevion.com | 12

The VS902 modes of operation are referred to in this document as follows:

Mode Card Name Description

ASI AED 4 channel bidirectional ASI transport

JPEG2000 J2KE Encoder, 2 channel unidirectional HD/SD SDI transport

JPEG2000 J2KD Decoder, 2 channel unidirectional HD/SD SDI transport

JPEG2000 J2KC Codec, 1 channel bidirectional HD/SD SDI transport.

JPEG2000 J2KE-3G Encoder, 1 channel unidirectional 3G/HD/SD SDI transport

JPEG2000 J2KD-3G Decoder, 1 channel unidirectional 3G/HD/SD SDI transport

Linear LC 4 channel bidirectional HD/SD SDI uncompressed transport

MADI MA 2/4 channel bidirectional MADI transport

2.1 Ordering Options

2.1.1 Sales Products The VS902 product is specified by three hardware platforms,

VS902-HW-1GE+ 1Gbps only platform

VS902-HW-10GE+ 10Gbps only platform

VS902-HW-1GE-10GE+ 1 and 10Gbps platform

VS902 functionality and the number of supported channels are specified by individual software license options. The functionality on a card is enabled by loading a valid license file to the card. This process is described in the License File Installation section of this manual.

The hardware and software options are listed in Table 1 and Table 2 below.

The previous sales products, listed below, are discontinued and are replaced by the hardware/software license options listed on the following pages.

Discontinued products:

VS902-1G-4L-FEC

VS902-1G-4JL-FEC

VS902-10G-4L-FEC

VS902-1/10G-4JL-FEC

VS902-1G-4L-SIPS

VS902-1G-4JL-SIPS

VS902-10G-4L-SIPS

VS902-1/10G-4JL-SIPS

VS902-4MA-75

VS902 Rev. D

nevion.com | 13

2.1.2 License Options - Hardware

Product Name Description

VS902-HW-1GE+

Multi-channel IP media transport over GigE. Basic hardware that can be licensed for ASI over IP, MADI over IP, or JPEG 2000 in TS over IP using SMPTE 2022-1/2 encapsulation.

Backplane with 4 input and 4 output BNCs for ASI/SDI, and 2 SFP cages. SFPs not included.

VS902-HW-10GE+

Multi-channel IP media transport over 10GigE. Basic hardware that can be licensed for SDI over IP using SMPTE 2022-5/6, or JPEG 2000 in TS over IP using SMPTE 2022-1/2 encapsulation.

Backplane with 4 input and 4 output BNCs for SDI, and 2 SFP+ cages. SFPs not included.

VS902-HW-1GE-10GE+

Multi-channel IP media transport over GigE or 10GigE. Basic hardware that can be licensed for ASI over IP, MADI over IP, JPEG 2000 in TS over IP using SMPTE 2022-1/2 encapsulation, or SDI over IP using SMPTE 2022-5/6 encapsulation.

Two backplanes provided for either GigE or 10GigE operation: 4 input and 4 output BNCs for SDI, and 2 SFP/SFP+ cages. SFPs not included.

Table 1: VS902 Hardware Options

2.1.3 License Options - Software


VS902-SW-ASI-CHx

Software option for VS902 enabling x ASI over IP unidirectional channel(s) (maximum is 4 transmit and 4 receive)

x = 1, 2, 4, 6 or 8 ASI channels

VS902-SW-SDI-CHx

Software option for VS902 enabling x SDI over IP unidirectional channel(s) (maximum is 4 transmit and 4 receive)

x = 1, 2, 4, 6 or 8 SDI channels

VS902-SW-J2K-CHx

Software option for VS902 enabling x JPEG 2000 over IP unidirectional channel (maximum is 2).

x= 1 the VS902 can be configured as either a single channel encoder or decoder.

x= 2 the VS902 can be configured as a dual channel encoder, dual channel decoder, or in a bi-directional configuration (one encoder and one decoder simultaneously).

VS902-SW-MADI-CHx

Software option for VS902 enabling x MADI over IP unidirectional channel (maximum is 4 transmit and 4 receive)

x = 1, 2, 4, 6 or 8 MADI channels

VS902-SW-HD Software option for VS902 enabling support for HD-SDI interfaces (includes SD-SDI interface support)

VS902-SW-3G Software option for VS902 enabling support for 3G-SDI interfaces (includes HD-SDI and SD-SDI interface support)

VS902 Rev. D

nevion.com | 14


VS902-SW-FEC Software option for VS902 enabling SMPTE 2022 Forward Error Correction for IP input/output. Note that TS over IP uses SMPTE 2022-1 FEC, while SDI over IP uses SMPTE 2022-5 FEC.

VS902-SW-SIPS Software option for VS902 enabling SIPS protection and RTP seamless switching according to SMPTE 2022-7. This license is required only on receiver devices.

VS902-SW-EPP Software option for VS902 enabling Encoder Partner Protection (EPP) for 1+1 sender redundancy

VS902-SW-NET-10G Software option for VS902 enabling support for 10GigE operation. Valid with VS902-SW-SDI-CHx only

VS902-SW-FSYNC Software option for VS902 enabling integrated frame store and Refsync for SDI over IP (analog black burst or SDI, at the same frame rate as video signal). Valid with VS902-SW-SDI-CHx only

VS902-SW-NET-AUX

Software option for VS902 enabling the auxiliary Ethernet data port for opportunistic multiplexing of Ethernet traffic together with video over IP streams. The AUX port is 1000Base-T Gigabit Ethernet over an RJ-45 connector.

Table 2: VS902 Software License Options

VS902 Rev. D

nevion.com | 15

3 Applications

The VS902 is a highly flexible, future-proof hardware platform that enables the development of a family of products designed to map and transport any professional video/audio broadcast standard over any telecom network that has been configured and deployed for this purpose.

3.1 Bidirectional ASI Transport The VS902 in ASI transport mode (AED mode) is designed for applications that require transporting multiple bidirectional ASI signals over an IP network.

VS902-AED

ASI

ASI

ASI

ASI

ASI

ASI

ASI

ASI

VS902-AED

ASI

ASI

ASI

ASI

ASI

ASI

ASI

ASI

SONET / SDH Networ

k

IP Network

100/1000 Base T

1000 Base X1000 Base X

100/1000 Base T

Figure 3: Multiple ASI Signals over Gigabit Ethernet Network

The VS902-AED requires a ceiling data rate threshold to be programmed for each of the four input channels (the sum of the rates given is not allowed to exceed the line interface capacity). The resolution of the bit rate ceiling is 1kb/s. Each channel is monitored to ensure that if a given Transport Stream (TS) exceeds its allocated data rate, it is blocked and does not interfere with the other streams in the VS902-AED.

3.2 Unidirectional J2K Compression and Transport The VS902 in J2K mode (J2KE for Encoder and J2KD for the Decoder) is designed for applications that require transporting two unidirectional HD/SD-SDI signals over an IP network. In this mode each card supports either JPEG2000 compression or decompression of 2 x SD-SDI/HD-SDI signals over dual 1 GigE network interfaces. Each card therefore operates as either a JPEG2000 Encoder or Decoder.

VS902 Rev. D

nevion.com | 16

VS902-J2KD

HD/SD-SDI

HD/SD-SDI VS902-

J2KEHD/SD-SDI

SONET / SDH Networ

k

IP Network

100/1000 Base T


100/1000 Base THD/SD-SDI

Figure 4: Compressed unidirectional HD/SDI Signals over Gigabit Ethernet Network

3.2.1 Unidirectional J2K Compression for 3G Transport

Additionally the J2K-3G mode (J2KE-3G for Encoder and J2KD-3G for the Decoder) is designed for applications that require transporting a single unidirectional 3G/HD/SD-SDI signal over an IP network. In this mode each card supports either JPEG2000 compression or decompression of one 3G/HD-SDI/SD-SDI signal over dual 1 GigE network interfaces. Each card therefore operates as either a JPEG2000 Encoder or Decoder. In this mode a single 3G video source can be compressed/uncompressed up to a maximum Transport stream rate of 640Mbps.

Figure 5: Compressed unidirectional 3G/HD/SDI Signal over Gigabit Ethernet Network

3.3 Bidirectional J2K Compressed Transport The VS902 in J2K Codec mode (J2KC mode) is designed for applications that require transporting bidirectional compressed HD/SD-SDI signals over an IP network. Each card supports simultaneous compression of one video channel and decompression of a second channel.

VS902-J2KC

HD/SD-SDI

HD/SD-SDI VS902-

J2KCHD/SD-SDI

SONET / SDH Networ

k

IP Network

100/1000 Base T


100/1000 Base THD/SD-SDI

Figure 6: Compressed bidirectional HD/SDI Signals over Gigabit Ethernet Network

VS902-J2KD-3G

3G/HD/SD-SDI VS902-J2KE-3G

SONET / SDH Networ

k

IP Network

100/1000 Base T


100/1000 Base T

3G/HD/SD-SDI

VS902 Rev. D

nevion.com | 17

3.4 Bidirectional Uncompressed Transport

The VS902 in linear mode (LC mode) is designed for applications that require transporting bidirectional multiple linear (uncompressed) 3G-SDI, HD-SDI or SD-SDI signals over an IP network.

Note: Uncompressed transport is enabled with license option VS902-SW-NET-10G

In this mode simultaneous linear encapsulation and de-encapsulation of 4 x SD-SDI/HD-SDI signals or 3 x 3G-SDI signals over dual 10 GigE network interfaces is supported on each card.

3G/HD/SDI

3G/HD/SDI

3G/HD/SDI

3G/HD/SDI

SONET / SDH Networ

k

IP Network

10GigE

10GigE10GigE

10GigE

VS902-LC VS902-LC

3G/HD/SDI

HD/SDI

3G/HD/SDI

HD/SDI

3G/HD/SDI

3G/HD/SDI

3G/HD/SDI

3G/HD/SDI

3G/HD/SDI

HD/SDI

3G/HD/SDI

HD/SDI

Figure 7: Multiple 3G/HD/SD-SDI Signals over 10 Gigabit Ethernet Network

3.5 Bidirectional MADI Audio Transport

The VS902 in MADI mode (MA mode) is designed for applications that require transporting bidirectional multiple MADI audio signals over an IP network. In this mode each card supports simultaneous encapsulation of 4 x MADI signals and de-encapsulation of 4 x MADI signals over dual 1 GigE network interfaces.

VS902-MA

MADI

MADI

MADI

MADI

MADI

MADI

MADI

MADI

VS902-MA

MADI

MADI

MADI

MADI

MADI

MADI

MADI

MADI

SONET / SDH Networ

k

IP Network

100/1000 Base T


100/1000 Base T

Figure 8: Multiple MADI Signals over 1 Gigabit Ethernet Network

VS902 Rev. D

nevion.com | 18

4 Specifications

4.1 VS902-AED

4.1.1 DVB-ASI Inputs/Outputs

Number of ports 4 x Input and 4 x output ports

1 x Front panel monitor port

Video Formats DVB-ASI

EN50083-9, 1-213Mbps

188 or 204 byte packets

Serial Data Rate 270Mbps ±100ppm, synchronous or asynchronous

Equalization Automatic for up to 250m of Belden 8281 or equivalent cables

Connectors BNC 75 ohm

Jitter Jitter tolerance per SMPTE EG33

Other Enable/Disable switched for each input channel

4.1.2 IP / Ethernet network

Number of ports 2 x Network interface ports

1 x Auxiliary data interface

1 x Maintenance port

Connector type 2 x 1Gbps SFP (optical or CU) network interfaces

1 x RJ45 auxiliary data port (1000BaseT)

1 x RJ45 (front panel maintenance port)

Interface type Gigabit Ethernet (GbE): IEEE 802.3ab (electrical) or IEEE 802.3z (optical)

Fast Ethernet (FE): IEEE 802.3U, IEEE 802.3y

Protocols IP/UDP/RTP, ARP, IGMPv2/v3, Diffserv/TOS, 802.1p (PCP), 802.1Q (VLAN)

Link speed 100Mbps/1000Mbps autosensing

Input impedance 100 Ohm - Cat 5e/6 Cable

Max. Cable distance 100m CAT5e STP data cable

VS902 Rev. D

nevion.com | 19

4.1.3 Processing:

Video encapsulation SMPTE 2022-2

FEC (Forward Error Correction) SMPTE 2022-1

Latency ~5ms

(end to end exc. network and optional configurable components)

4.1.4 Alarm Outputs:

Major Isolated relay contact normally open, closed on activation of the alarm

Minor Isolated relay contact normally open, closed on activation of the alarm

4.1.5 General

Operating Temperature: 0 to 50°C ambient

Voltage: +12V, +5V.

Power Consumption: 28 Watts max

Compliance: NEBS level 3, UL, CSA, CE, FCC (Part 15, Class A), C-Tick, RoHS

Mechanical: Suitable for mounting in Ventura 19" rack chassis

Size: 6 HP x 3U Extended Eurocard (220 mm x 100 mm).

Weight: With rear assembly 400g.

Boot time: Approx. 5 seconds

Standard Accessories: Rear connector panel (supplied with module).

VS902 Rev. D

nevion.com | 20

4.2 VS902-J2K (inc. J2KE, J2KD, J2KC, J2KE-3G and J2KD-3G)

4.2.1 Inputs/Outputs

Number of ports 2 x Input for VS902-J2KE

2 x Output for VS902-J2KD

1 x Input for VS902-J2KE-3G

1 x Output for VS902-J2KD-3G

1 x Input + 1 x Output for VS902-J2KC


Video Formats SD-SDI SMPTE 259-C, SMPTE 305M

625i25, 525i29.97

HD-SDI SMPTE 292

720p50, 720p59.94, 720p60

1080i25, 1080i29.97, 1080i30

1080p25, 1080p29.97, 1080p30

3G-SDI SMPTE 424 (J2KE-3G and J2KD-3G only)

Serial Data Rate 270Mbps to 2.97Gbps

Equalization Automatic

>250 meters at 270Mbps w/ Belden 8281 cable,

>140 meters at 1485Mbps w/ Belden 1694A cable

100 meters at 2.97Gbps w/Belden 1694A cable



Other Enable/Disable switch for each input channel












VS902 Rev. D

nevion.com | 21



4.2.3 Processing:

Video encapsulation MPEG-2 TS with SMPTE 2022-2


Latency ~3 fields – 60(50Hz) / 50(60Hz) ms





4.2.5 General


Voltage: +12V, +5V.








VS902 Rev. D

nevion.com | 22

4.3 VS902-LC

4.3.1 Inputs/Outputs


Up to 3x 3G-SDI input & 3x 3G-SDI output ports


Video Formats SD-SDI SMPTE 259-C, SMPTE 305M

625i25, 525i29.97

HD-SDI SMPTE 292

720p50, 720p59.94, 720p60

1080i25, 1080i29.97, 1080i30

1080p24, 1080p25, 1080p29.97, 1080p30

3G-SDI SMPTE 424

1080p50, 1080p60, 1080p59.94

Serial Data Rate 270Mbps to 2.97Gbps

Equalization Automatic

>250 meters at 270Mbps w/ Belden 8281 cable,

>140 meters at 1485Mbps w/ Belden 1694A cable

100 meters at 2.97Gbps w/Belden 1694A cable








Connector type 2 x 10Gbps SFP+ (optical) network interfaces



Interface type 10 Gigabit Ethernet (GbE)

IEEE 802.3ae (optical), IEEE802.3ak (twinax)


Link speed 10Gbps (1,250 Mbps), 10GBASE-CX4

VS902 Rev. D

nevion.com | 23

4.3.3 Processing:

Video encapsulation SMPTE 2022-6


Latency ~2ms





4.3.5 General


Voltage: +12V, +5V.








VS902 Rev. D

nevion.com | 24

4.4 VS902-MA

4.4.1 MADI Inputs/Outputs



Audio Formats Serial Multichannel Audio Digital Interface (MADI)

AES10 - 2008

Serial Data Rate 125Mbps ±100ppm

Equalization Automatic for up to 250m of Belden 8281 or equivalent cables








1 x RJ45 auxiliary data port








4.4.3 Processing:

FEC (Forward Error Correction) Based on SMPTE 2022-1




VS902 Rev. D

nevion.com | 25

4.4.5 General


Voltage: +12V, +5V.








VS902 Rev. D

nevion.com | 26

5 Configuration

All of the configuration parameters for the VS902 cards can be set by using Nevion Element Management web interface. Select the VS902 to be configured by clicking on the front panel displayed in the web browser, then click on the EDIT CONFIG tab. See Figure below.

Figure 9: VS902 Control Settings

Card configuration is performed using the Edit Card Configuration menu option under the EDIT CONFIG tab on the web interface for the card. Configuration is tab structured as seen in the Figures in the sections below. Most Main, Input and Output configurations parameters are common across all versions of the VS902 product line. Configurations items that are specific to individual models are specifically marked in the tables below.

Caution: All configuration changes require the Save Changes button to be pressed before they are applied.

The Main tab contains the general card configuration parameters which are not specific to any input or output

VS902 Rev. D

nevion.com | 27

5.1 VS902 Main Configuration

5.1.1 Boot Modes The operating mode of the VS902 card can be changed by using the Card Functional Mode configuration item in the Main tab. This item consists of a drop down list of the boot images installed on the card. Operation in each mode will depend on which product/licenses have been purchased.

Figure 10: VS902 Card Functional Mode Configuration

The VS902 card is capable of storing up to nine functional boot images plus one image location which is reserved for Fallback (see section Fallback). Each image location has been defined for a specific card function, see table below.

Image Location

Card Function Label

1 10Gbps Linear bidirectional codec LC

2 1Gbps MADI bidirectional codec MA

3 1Gbps ASI bidirectional codec AED

4 1Gbps J2K Encoder J2KE

5 1Gbps J2K Decoder J2KD

6 1Gbps J2K bidirectional codec J2KC

7 1Gbps J2K 3G Encoder J2KE-3G

8 1Gbps J2K 3G Decoder J2KD-3G

0 Fallback (Factory) code FB

Table 3: VS902 Card Functional Modes

VS902 Rev. D

nevion.com | 28

5.1.2 In-Band Management The VS902 has support for in-band management over the same network interfaces that are used for video/audio transport. This requires using VLAN tagged traffic, using one range of VLANs for the video/audio transport, and others for the in-band management. To simplify configuration, and reduce the possibility of losing communications with the card, VLAN ID 1 is always reserved for in-band management if in-band management is enabled. A second, user definable VLAN ID may also be configured if needed. An IP address, subnet mask and default gateway then need to be defined uniquely for each card. Note also that in-band management will be accepted on either of the two network interfaces – it is the responsibility of the user to ensure that in-band management packets are only routed to one interface at a time. Currently the in-band connectivity can only be used for card upgrades – a future virtualised version of AEMS will allow full management of VS902 cards in-band.

Caution: A configuration change to the Card Functional Mode item will cause the card to reboot and a loss of any active services

Caution: When In-band management is enabled, VLAN ID 1 is not available for video/audio services.

VS902 Rev. D

nevion.com | 29

5.1.3 VS902-AED

Figure 11: VS902-AED Control Settings – Main Configurations

5.1.4 VS902-J2KE / VS902-J2KE-3G

Figure 12: VS902-J2KE(-3G) Control Settings – Main Configurations

VS902 Rev. D

nevion.com | 30

5.1.5 VS902-J2KD / VS902-J2KD-3G

Figure 13: VS902-J2KD(-3G) Control Settings – Main Configurations

5.1.6 VS902-J2KC

Figure 14 VS902-J2KC Control Settings - Main Configurations

VS902 Rev. D

nevion.com | 31

5.1.7 VS902-LC

Figure 15: VS902-LC Control Settings – Main Configurations

5.1.8 VS902-MA

Figure 16: VS902-MA Control Settings – Main Configurations

VS902 Rev. D

nevion.com | 32

5.1.9 Main Configuration Parameters The Main control parameters for the VS902 versions are listed in the table below.

Parameter Description Selection

Card Functional Mode Selects the software image that the card is running.

e.g.

1G ASI Codec V2.0 …

Maintenance IP Address

Defines the address of the card maintenance Ethernet port. Must be assigned the same IP subnet as the AEMS installed in the chassis the card is installed in. The maintenance Ethernet port can be used for the remote upgrade of the card’s code images.

xxx.xxx.xxx.xxx

Channel License Allocation

Select the allocation of number of inputs and outputs based on the number of channels licensed i.e. 1, 2, 4, 6 or 8 channels.

4,6 and 8 channels applies to AED, LC and MADI modes only.

1 input, 0 outputs 0 inputs, 1 output 2 inputs, 0 outputs 1 input, 1 output 0 inputs, 2 outputs 4 inputs, 0 outputs 3 inputs, 1 output 2 inputs, 2 outputs 1 input, 3 outputs 0 inputs, 4 outputs 4 inputs, 2 outputs 3 inputs, 3 outputs 2 inputs, 4 outputs 4 inputs, 4 outputs

Network Interface Mode

Defines the Ethernet connection speed and duplex mode of the card’s Network Port A and B interfaces.

The setting for each port should match the configuration for the port or device to which it is physically connected.

The default setting for this parameter is Autonegotiate All Speeds.

Autonegotiate All Speeds / Autonegotiate 1G Only / Autonegotiate 100M Only / Fixed 1G Full Duplex / Fixed 100M Full Duplex

Network Output Mode

Defines if the card is running as Stand Alone or as a part of an encoder partner protection pair. Selections are as Stand Alone, Master, or Slave.

Master or Slave selection is used in a partner card setup, two encoder cards are fed with the same incoming feeds and the second physical network port of the first (master) card is cross-connected with the first physical port of the second (slave) card. The first physical network port of the master card and the second physical port of the slave card are connected to the network.

Standalone

Master

Slave

VS902 Rev. D

nevion.com | 33


Input Automatic Transmit Disable

Enable to stop the Encoder channels sending video data when the Decoder is not present. The Encoder will automatically shut off video traffic from channels where the Encoder does not receive ARP responses from the configured destination Port IP Address.

Disable to allow the Encoder to continue sending video traffic when the Decoder is not present or the destination address is not configured.

Off

On

ARP/Ping Responses For Disabled Channels

Defines whether configured Port IP Addresses respond to ARP/Ping messages when a specific channel is configured as Disabled.

Enable or Disable

Network Statistics Display

Changes the display mode of the Output channel status items ‘Flow x PDV (ms)’ and ‘Flow x Discontinuity Count’.

Instantaneous mode always displays the current measurement.

Cumulative mode displays the highest measured value since the last statistics reset.

Instantaneous or Cumulative

Cumulative Statistics Reset

Enable a reset of the Network Statistics values.

To perform a reset, set this parameter to ‘Reset Statistics’ and hit the ‘Save Changes’ button.

Don’t Reset or Reset Statistics

Input 1/2 Switching (AED only)

Enable or disable protection switching between input channels 1 and 2. Note this switching is not slipless.

Enable or Disable

Input 3/4 Switching (AED only)

Enable or disable protection switching between input channels 3 and 4. Note this switching is not slipless.

Enable or Disable

IGMP Version Support

Defines whether the card will use IGMP v3 if it gets v3 requests. In automatic, the card will respond v3 to v3 devices but will revert to v2 if no v3 detected

Automatic

Force V2

Disabled

In Band Management Enable or disable In Band Management Enable or Disable

Custom In Band Management VLAN

Enable or disable In Band Management VLAN Enable or Disable

Custom In Band Management VLAN ID

Defines In Band Management VLAN ID to be used

2 to 4094

In Band Management IP Address

Defines In Band Management IP Address. The IP address entered as four decimal triplets separated by decimal points.

This IP Address should be in the same subnet as the AEMS system IP Address in the same chassis.

xxx.xxx.xxx.xxx

In Band Management Subnet Mask

Defines In Band Management Subnet Mask xxx.xxx.xxx.xxx

VS902 Rev. D

nevion.com | 34


In Band Management Default Gateway

Defines In Band Management Gateway xxx.xxx.xxx.xxx

Auxiliary Data Port Enable or disable the auxiliary Ethernet data port

Enable or Disable

Auxiliary Data Port VLAN ID

Assign a VLAN ID to the data traffic received at the auxiliary data port.

2 to 4090

Auxiliary Data Port Rate Limit

Set the maximum input data rate for the data traffic received at the auxiliary data port. Input packets will be dropped if the rate exceeds this Rate Limit.

Note the aggregate data rate for the video/audio traffic received on the input ports, FEC data and the data received at the auxiliary data port cannot exceed the capacity of the network interface (1Gbps for AED, J2K and 10Gbps for LC).

1 to 1000Mbps

Table 4: VS902 Control Settings – Main Settings

5.1.10 Notes on Main Configuration Appropriate channel licenses are required for each functional mode to operate. Without channel licenses all channel transmission will be disabled. Each channel license installed enables one unidirectional channel transport. With multiple channel licenses installed the channels can be allocated as inputs or outputs on each card using the Channel License Allocation configuration parameter. In AED, LC and MADI modes, with a maximum of 8 channel licenses installed, all 4 inputs and 4 outputs are enabled. The J2K Encoder (J2KE & J2KE-3G) modes requires two J2K channels to enable both inputs. The J2K Decoder (J2KD & J2KD-3G) modes requires two J2K channels to enable both outputs. A single J2K channel enables one input or one output. J2K Codec (J2KC) mode requires two J2K channels to enable both the input and output on each card.

VS902 Rev. D

nevion.com | 35

5.2 Input Channel Configuration The control parameters of the VS902 input channel configuration are listed in the Figure & Table below. They define the parameters that need to be configured for each input channel to the card. The control parameters for each input are located in the tabs In 1 to In 4. The J2KE design supports 2 input channels and uses Inputs 1 (In 1) and 3 (In 3). The J2KE Encoder design is unidirectional and therefore no output configuration tabs are available in this mode. Input configuration parameters apply to AED, J2KE, J2KC and LC designs only (the J2K Decoder design, J2KD, is unidirectional and therefore contains output configuration only).

5.2.1 VS902-AED

Figure 17: VS902-AED Control Settings – Input Channel Configurations

VS902 Rev. D

nevion.com | 36

5.2.2 VS902-J2KE / VS902-J2KC / VS902-J2KE-3G

Figure 18: VS902-J2KE(-3G)/VS902-J2KC Ctrl Settings – Input Ch. Configurations

The VS902-J2KE-3G design is a single channel design and will therefore only have a single ‘In 1’ tab (no ‘In 3’ tab).

VS902 Rev. D

nevion.com | 37

5.2.3 VS902-LC

Figure 19: VS902-LC Control Settings – Input Channel Configurations

VS902 Rev. D

nevion.com | 38

5.2.4 VS902-MA

Figure 20: VS902-MA Control Settings – Input Channel Configurations

VS902 Rev. D

nevion.com | 39

5.2.5 Input Channel Configuration Parameters The table below lists the configuration parameters for each input channel. There is a unique set of parameters for each of the 4 input channels to the card.

Parameter Description Choice

Channel Description User defined channel name text field used for Input x Status and Channel Name Status menus

Text field

(40 Characters)

Channel Transmission

Enable or disable this input channel Enabled or Disabled

Channel Input Mode

(J2KE only)

Enables auto detection and transmission of either ASI or J2K (SDI) input signals when set to ASI and J2K.

J2K only mode supports SDI inputs only for compression and transport.

ASI only mode supports ASI inputs only for transparent transmission.

ASI and J2K

J2K only

ASI Only

Partner Encoder Mode

In active mode, the Slave card will output a feed all the time. In passive mode, it will only output a feed upon failure of the Master card

Active

Passive

Flow A/B VLAN

Enable or disable adding a VLAN tag to IP packets

See Note 1

Enable or Disable

Flow A/B VLAN ID The VLAN address to be used (if enabled in line above)

0 to 4095

Flow A/B Port IP Address

The source IP address of the flow which will appear in the IP header of the outgoing flow. (This is also the address that will respond to ARPs and pings for the configured VLAN).

When no VLANs are configured, there should be a common source IP address configured across all non-VLAN channels (in & out)

xxx.xxx.xxx.xxx

Flow A/B Port Subnet Mask

Used to determine whether unicast destinations are local or remote (through Gateway)

xxx.xxx.xxx.xxx

Flow A/B Port Default Gateway

Enter IP address of system gateway. xxx.xxx.xxx.xxx

Flow A/B Destination IP Address

Defines destination IP address.

This IP address should be the same as the output channel Destination IP Address.

xxx.xxx.xxx.xxx

Flow A/B Destination UDP Port

Defines destination UDP port of ingress IP packets the channel is configured to receive.

1 to 65535

VS902 Rev. D

nevion.com | 40


Protection

Defines whether this input channel is running with SIPS (Streaming Intelligent Packet Switching) protection.

Setting this option to Disable stops video/audio traffic being sent from Network Port 2 (Flow B)

Enabled or Disabled

Time To Live

Defines packet lifetime (hops) through network. The number of routers the packet can pass through before being discarded. As specified by RFC-791.

This value is decreased by 1 for every router the packet passes through. The packet is discarded when this value reaches 0.

0 restricts it to the same host, 1 to the same subnet, 32 to the same site, 64 to the same region and 128 to the same continent; 255 is unrestricted

0 to 255

TOS/DSCP + ECN

Defines IP packet priority from pre-configured options or a custom pattern. The predefined options configure both the TOS/DSCP and ECN fields using the 8 bit format below. See section TOS/DSCP Marking

0 3 64 521 7

TOS or DSCP bits ECN or CU bits

CS0 00000000

CS1 00100000

CS2 01000000

CS3 01100000

…

Custom

TOS/DSCP Custom + ECN

The card can mark the TOS/DSCP field in the IP header of each locally generated video/audio over IP packet using a user-defined value. Although the DSCP field is only 6-bits long per IETF RFC2474, the browser shows the 6-bit DSCP plus the 2-bit ECN (or CU) fields. All of the 8 bits can be defined by the user.

This configuration is used in conjunction with selecting ‘Custom’ in the TOS/DSCP + ECN field above.

Custom input (8 bits)

VLAN Priority Code Point

Define frame priority level. Used in conjunction with VLAN ID when VLAN is enabled.

Values are from 0 (lowest) to 7 (highest).

0 (000)

1 (001)

2 (010)

3 (011)

4 (100)

5 (101)

6 (110)

7 (111)

VS902 Rev. D

nevion.com | 41


Forward Error Correction

Defines the number of FEC streams.

Column Only FEC uses one FEC stream. Rows and Columns FEC uses two FEC steams.

This parameter is only valid when FEC profile is set to Custom.

Disabled

Column Only

Rows and Columns

FEC Matrix Number of Rows (D)

Rows and Columns FEC can use any D value within the range from 4 to 20. This parameter is only valid when FEC profile is set to Row and Column.

Note that L×D must be less than or equal to 100.

4 to 20

FEC Matrix Number of Columns (L)

Columns Only FEC can use any L value within the range from 1 to 20.

Rows and Columns FEC can only be used when L is greater than or equal to 4.

This parameter is valid when FEC profile is set to Column Only and Rows and Columns.

Note that L×D must be less than or equal to 100.

1 to 20

Number of TS packets in one IP packet

(not LC)

Sets the number of TS packets encapsulated by each IP packet

1 to 7

Transported Packet Length

(AED only)

Sets the packet length for transport of each input signal.

188 or 204 bytes

ASI Bitrate Ceiling (in Mbit/s)

(AED and J2KE only)

Sets the maximum input bit rate for each ASI channel.

100 Kbps to 213 Mbps

SD J2K TS Rate (in Mbit/s)

(J2KE only)

Sets the Transport Stream (TS) output rate for SDI video source.

1 Mbps to 350 Mbps

HD J2K TS Rate (in Mbit/s)

(J2KE only)

Sets the Transport Stream (TS) output rate for HD-SDI video source.

1 Mbps to 350 Mbps

(1 – 640Mbps for J2KE-3G)

3G J2K TS Rate (in Mbit/s)

(J2KE-3G only)

Sets the Transport Stream (TS) output rate for 3G-SDI video source.

1 Mbps to 640 Mbps

J2K Encode rate (in Mbit/s)

(Legacy J2KE only)

Sets the encoded video bitrate produced by the J2K compression engine.

1 Mbps to 300 Mbps

VS902 Rev. D

nevion.com | 42


Audio Group 1~4 Enable

(J2KE only)

Enable or Disable carriage of each audio group.

Enabled or Disabled

Sync Error Threshold

A Sync error count above this threshold will cause the corresponding alarm to be raised

0 to 255 /sec

TEI Error Threshold

(AED and J2KE only)

A TEI error count above this threshold will cause the corresponding alarm to be raised

0 to 255 /sec

CRC/EDH Error Threshold

(not AED)

A CRC/EDH error count above this threshold will cause the corresponding alarm to be raised

0 to 255 /sec

Partner Feed RTP Error Threshold

A RTP error count above this threshold on the partner feed will cause the corresponding alarm to be raised

0 to 255 /sec

Maximum Rate Permitted

(J2KE, J2KC and LC only)

Defines the highest input video format bit rate permitted for each card input.

This configuration item can be used to block unexpected input formats being connected to card inputs.

If the bit rate of the connected input is higher than the configured Maximum Rate Permitted it is not transmitted.

SD only,

SD or 1.5G HD,

All Rates

Table 5: VS902 Control Settings – Input Channel Configuration

Note: Setting the Protection configuration item to Disabled results in a network data flow being sent from network interface A only.

VS902 Rev. D

nevion.com | 43

5.2.6 Notes on Input Channel Configuration Flow A / Flow B naming convention refers to the streams coming from Network Ports 1 / 2. Flow A streams always use Network Port 1, and Flow B streams always use Network Port 2. It is possible to disable video/audio traffic being sent from both Network ports using the Channel Transmission and Protection configuration items. Setting Protection to Disabled stops video/audio traffic from being sent from Network Port 2 (Flow B). Setting Channel Transmission to Disabled stops video/audio traffic from being sent from both Network Port 1 (Flow A) and Network Port 2 (Flow B). The Flow x Port IP Address parameter for each port is used as the Source IP address for input channels. This IP Address will also respond to ARPs and Pings, the first of these being needed for Unicast operation to work, and the latter of these being useful for diagnostic purposes. For a simple network setup where all the channels are either not VLANed, or are all in the same VLAN, then it is simplest to set the Flow x Port IP Address of all input channels to the same value, which becomes a nominal “card IP address”. Being able to have a different IP address on each port can become a requirement in a VLANed environment. For example, if you were providing a service for TV Channel A on channel 1 of the VS902 and for TV Channel B on channel 3, separated into different VLANs that ran across different infrastructure, you would need to have an IP address appropriate to the TV Channel A network on channel 1 and one appropriate to the TV Channel B network on channel 3. If you are using the simple setup where the Flow A/B Port IP Addresses are all set the same, then the Flow x Port Subnet Mask and Flow x Port Default Gateway for the inputs also all become the same. If you were using a more complex network setup, then the Subnet Mask and Gateway for the ports in different VLANs may become different. The Flow x Destination IP Address and Flow x Destination UDP Port parameters define the destination of the video/audio traffic. Two flows generated by the two different inputs need to be differentiated in some way – this can either be by having a different Destination IP Address for each one, or (if the Destination IP Address is the same) just by having a different Destination UDP Port number for each one. Note 1 - VLAN tags should be enabled for both flows (Flow A and Flow B) using the uncompressed linear mode. Failure to enable VLAN tags on both flows could prevent the other flow from being transported correctly.

Note: Enable VLAN on both Flow A and Flow B using VS902-LC mode (only). See Note 1 above.

VS902 Rev. D

nevion.com | 44

5.2.7 Asymmetric Network Launch The default behaviour of the VS902 is to launch the same network data traffic for each video input on both network ports when the Protection configuration parameter is set to Enable. It is possible to define whether traffic associated with each video channel is launched from only Network Port A or only Network Port B. For each input channel, configuration parameters as follows: To launch from Network Port A only

1. Set Channel Transmission = Enabled 2. Set Flow A destination IP Address to required destination IP address 3. Set Protection = Disabled

To launch from Network Port B only

1. Set Channel Transmission = Enabled 2. Set Flow A destination IP Address = 0.0.0.0 3. Set Protection = Enabled 4. Set Flow B destination IP Address to required destination IP address

To launch from both Network Port A and Network Port B

1. Set Channel Transmission = Enabled 2. Set Flow A destination IP Address to required destination IP address 3. Set Protection = Enabled 4. Set Flow B destination IP Address to required destination IP address

To launch from neither Network Port

1. Set Channel Transmission = Disabled

VS902 Rev. D

nevion.com | 45

5.2.8 J2KE Bitrate Setting The J2K video encode rate is automatically calculated from the configured TS Rate (using the SD/HD/3G J2K TS Rate parameters) and the number of audio channels that are enabled for transport. The bandwidth required for the audio transport is subtracted from the TS Rate to give the video encode rate. The result of this calculation is displayed in the Status Summary menu.

J2KE = TS – (AG * 7.5) Where, AG = No. of Audio Groups to be transported J2KE = J2K Video encode rate (video rate) TS = Configured transport stream rate

Legacy Code Revision Only

For legacy code revisions of the J2K Encoder mode, it was necessary to specify the transport stream rate that will be generated (shared with the ‘Bitrate Ceiling’ parameter from ASI mode) and the J2K video encode rate (‘J2K Encode rate’ config item). The J2K video encode rate needs to be sufficiently lower than the configured transport stream rate to allow space for the carriage of the audio and overheads. A formula that will give an appropriate transport stream rate in Mbit/s for a given J2K encode rate is:

TS = J2KE * 1.05 + AG * 7.5 Where, AG = No. of Audio Groups to be transported J2KE = J2K Video encode rate (video rate) TS = Bitrate ceiling (transport stream rate) That is, multiply the desired J2K encode rate by 1.05, and then add 7.5Mbit/s for every enabled audio group. Therefore, to transport video encoded at a rate of 50Mbps, with two groups of pre embedded audio, the Transport Stream rate (Bitrate Ceiling config item) should be set to at least: TS = 50 * 1.05 + 2 * 7.5 = 52.5 + 15 = 67.5Mbps The reverse calculation (removing 7.5Mbit/s for every enabled audio group, and then dividing by 1.05) can be used to calculate the maximum allowable J2K encode rate for a desired transport stream rate.

VS902 Rev. D

nevion.com | 46

5.3 VS902 Output Channel Configurations The control parameters of the VS902 output channel configuration are listed in the Figure & Table below. They define the parameters that need to be configured for each output channel from the card. The control parameters for each output channel are located in the tabs Out 1 to Out 4. The J2KD design supports 2 channels and uses Outputs 1 (Out 1) and 3 (Out 3). The J2KD-3G design supports 1 channel and uses Outputs 1 (Out 1) only. Output configuration parameters apply to AED, J2KD, J2KC and LC designs only (the J2K Encoder design, J2KE, is unidirectional and therefore contains input configuration only).

5.3.1 VS902-AED

Figure 21: VS902-AED Control Settings – Output Channel Configurations

VS902 Rev. D

nevion.com | 47

5.3.2 VS902-J2KD / VS902-J2KC / VS902-J2KD-3G

Figure 22: VS902-J2KD(-3G)/VS902-J2KC Ctrl Settings – Output Ch. Configurations

The VS902-J2KD-3G design is a single channel design and will therefore only have a single ‘Out 1’ tab (no ‘Out 3’ tab).

VS902 Rev. D

nevion.com | 48

5.3.3 VS902-LC

Figure 23: VS902-LC Control Settings – Output Channel Configurations

VS902 Rev. D

nevion.com | 49

5.3.4 VS902-MA

Figure 24: VS902-MA Control Settings – Output Channel Configurations

VS902 Rev. D

nevion.com | 50

5.3.5 Output Channel Configuration Parameters The table below lists the configuration parameters for each input channel. There is a unique set of parameters for each of the 4 input channels to the card.


Channel Description User defined channel name text field used for Output x Status and Channel Name Status menus

Text field

Channel Output Enables or disables the channel output Enabled or Disabled

Output Video Decoding

(J2KD only)

Enables the user to choose to output the ASI TS or to decode the output to the HD/SD-SDI signal.

Automatic Detection or Force ASI Output

Channel Clocking

Selects either internal Adaptive Recovery or enables external reference signal for integrated frame store and refsync.

If external reference is required, either digital or analogue signal can be selected as the reference source.

Adaptive Recovery Genlock Input 1 Genlock Input 2 Genlock Input 3 Genlock Input 4 or Genlock Analogue

SIPS Protection

Defines whether the output is using SIPS protection and receiving video/audio traffic from both Flow A and Flow B in order to decode the output stream.

Masks Flow B alarms/LEDs if disabled.

Enabled or Disabled

Flow A/B VLAN Enable or disable the incoming VLAN tag on IP packets

Enabled or Disabled

Flow A/B VLAN ID The VLAN address to be used (if enabled in line above)

0 to 4094

Flow A/B Port IP Address

Used for Unicast ARP & PING responses and source address for IGMP packets.

xxx.xxx.xxx.xxx

Flow A/B Source IP Address

Use for stream source filtering and IGMP v3 SSM

xxx.xxx.xxx.xxx

Flow A/B Source IP Mask

Used in conjunction with the above to allow a range of source addresses to be used

xxx.xxx.xxx.xxx

Flow A/B Destination IP Address

Defines destination IP address to match the IP address in the received packets. This IP address should be the same as the input channel Destination IP Address.

This IP address will be the same as the output channel Port IP address for Unicast addressing and will be different for Multicast addressing.

xxx.xxx.xxx.xxx

VS902 Rev. D

nevion.com | 51


Flow A/B Destination UDP Port

Defines destination UDP port of ingress IP packets the channel is configured to receive

LC only – only accepts values which are multiples of 8

1 to 65535

Output ASI Packet Length

(AED and J2KD only)

Defines the output TS packet size

188

204

Auto

SIPS Pre-buffer (ms)

This should be configured to allow for the maximum differential network delay expected.

The allocated pre-buffer time to allow for shortest-path-connected-first scenario.

1-200ms

(1-50ms for VS902-LC)

Expected Lagging Flow

Defines which flow (A or B) the SIPS Pre-buffer is allocated to.

If set to Auto the SIPS Pre Buffer is applied to the first feed connected.

Auto

Flow A

Flow B

Network Jitter Tolerance (ms)

Sets the size of the Network Jitter Buffer.

Extra buffer added at the Decode stage to tolerate network jitter. The size of this buffer adds to overall end to end latency.

1-200ms

(1-20ms for VS902-LC)

Sync Error Threshold

(not LC)

A sync error count above this threshold will cause the corresponding alarm to be raised

0 to 255 /sec

TEI Error Threshold

(not LC)

A TEI error count above this threshold will cause the corresponding alarm to be raised

0 to 255 /sec

DLM Error Threshold (ms)

A DLM (Differential Latency Measurement) error measurement above this threshold will cause the corresponding alarm to be raised

0 to 255ms

PDV Error Threshold (ms)

A PDV error count above this threshold will cause the corresponding Flow A or Flow B Feed alarm to be raised

0 to 255ms

Network RTP Error Threshold

A Network RTP error count above this threshold will cause the corresponding Flow A or Flow B alarm to be raised

0 to 255 /sec

Post SIPS RTP Error Threshold

A Network Post SIPS RTP error count above this threshold will cause the corresponding alarm to be raised

0 to 255 /sec

Table 6: VS902 Control Settings – Output Channel Configurations

VS902 Rev. D

nevion.com | 52

5.3.6 Notes on Output Channel Configuration Flow A / Flow B naming convention refers to the streams coming from Network Ports 1 / 2 for decode. Flow A streams always use Network Port 1, and Flow B streams always use Network Port 2. The Flow x Port IP Address parameter for each port is the IP Address that will respond to ARPs and Pings, the first of these being needed for Unicast operation to work, and the latter of these being useful for diagnostic purposes. This IP Address is also used as the source address for IGMP packets. For a simple network setup where all the channels are either not VLANed, or are all in the same VLAN, then it is simplest to set the Flow x Port IP Address of all channels to the same value, which becomes a nominal “card IP address”. For unicast operation the Flow x Source IP Address and Flow x Source IP Address Mask fields combine to provide a flexible source filtering capability. The easiest option for a simple network is to set both fields to 0.0.0.0, which will allow any source IP address to be processed. The next option is to set the mask to 255.255.255.255, which will limit the system to only accepting packets from one specific source address. Different mask values between these extremes will allow ranges of source addresses to be used. The Flow x Destination IP Address (and Flow x Destination UDP Port) is used to select the value that will be accepted in the destination IP address field in the packets received. For unicast operation, this is usually the same as the Flow x Port IP Address value (though with a more complex network setup other options are possible) because that is where you need to have the encoder card send the packets to have them received by the decoder card. This may make this field seem redundant, but when operating in a multicast environment this becomes more obviously important, as this field selects which multicast group the output will attach to, and controls the IGMP join process as well. Flow x Destination UDP Port values are only accepted when a multiple of 8. This is due to the reservation of port numbers n+2, n+4 and n+6 for FEC flows and Media Helper Packets (MHP). Invalid values will be automatically adjusted to the nearest correct value. The range of the Network Jitter Tolerance parameter is from 1 to 200ms (1 to 20ms for VS902-LC). The SIPS Pre Buffer configures a buffer ahead of the incoming network data flows to allow for one of the feeds to be lagging the other flow i.e. one of the flows having a longer network path than the other and therefore a differential delay between the two feeds. The Network Jitter Tolerance and the SIPS Pre Buffer are additive in terms of the latency introduced to the overall end-to-end network. If the Expected Lagging Flow parameter is set to a value other than “Auto” i.e. set to “Flow A” or “Flow B”, then the SIPS Pre-Buffer value will only be applied if the leading (or shortest path) flow i.e. the flow not configured as the Expected lagging Flow, is connected first. If the lagging (longest path) flow is connected first, it will only be delayed enough for the configured Network Jitter Tolerance. In “Auto” mode, the first feed connected will always be delayed by the full amount, to ensure that the second feed connected can be correctly buffered and aligned. For intra-country national networks, because of the distances involved, typically a setting of 3–5ms should be sufficient for the SIPS Pre Buffer to compensate for the variation in differential latency between the two network flows.

VS902 Rev. D

nevion.com | 53

The transmission time difference (latency) of the two incoming network feeds, Flow A and Flow B, through the network is measured. This is called the Differential Latency Measurement (DLM). This measurement can be used to trigger an alarm based on the DLM Error Threshold configuration parameter. This measurement and alarm can be used to indicate potential and unwanted network reroutes resulting in the differential latency between the two network routes being outside of the specification.

5.3.7 Output Channel Frame Sync VS902-LC output video signals can use an internal Frame Synchronizer in order to synchronize the timing of these video signals to coincide with a timing reference signal. This external reference can be either an analogue video signal (typically black-burst SD signal) or a digital composite signal. The result of this process is that the timing or alignment of the video frame is adjusted so that the scan of the upper left corner of the image is happening simultaneously on all sources. This is a requirement for both analogue and digital systems in order to perform video effects or switch glitch-free in a router. For each card output, the user can configure either to use an analogue or digital reference signal. The analogue reference should be connected to the Input 4 connector. The digital reference can selected from either of Input 1-4 on the card and configured appropriately.

Figure 25: VS902-LC Frame Sync Configuration

The following table defines which types of Genlock input signals can be used to reference output formats.

Output Format

Digital Genlock Input Signal Analogue Genlock Input

SD 625 SD 525 HD HD/m SD 625 SD 525

SD 625 X X X

SD 525 X X

HD X X X

HD/m X X

3G X X X

3G/m X X

Table 7: Genlock Signal Options

VS902 Rev. D

nevion.com | 54

The configured reference source (Digital or Analogue) is reported in the Output x Status menu under the Status tab.

If an output channel is configured to use either an external analogue or digital reference signal and no signal is detected at the appropriate input, a Reference Input Missing Error alarm is raised and reported in the Output x Status menu under the Status tab.

Figure 26: Reference Input Alarm in Output Status

5.4 Alarm Settings Alarm settings can be configured using the Edit Alarm Configuration menu option under the EDIT CONFIG tab on the web interface for the card. It is possible to assign a certain Hold and Persistence time to each alarm.

Persistence Time - the time (in seconds) an alarm has to be active before it appears in the alarm list and for a SNMP alarm notification to be sent. The Persistence time is useful for filtering low priority alarms and for conditions that naturally appear in video/audio streams.

Hold Time - the time (in seconds) for which VS902 keeps an alarm active after it has cleared. The hold timer can be used to keep oscillating alarms permanently active. This prevents resending alarm/clear traps and the alarm list will not be filled up with the oscillating alarm.

Note: It is recommended that the Hold Time should never be set to less than 1 second.

One of the following seven alarm priorities can be assigned to each alarm:

Disable, Log Only, Information, Warning, Minor, Major or Critical. Additionally, each card slot in the VS103 and VS101 chassis has two alarms (major and minor), which are fed to a connector on the rear of the chassis. This enables external monitoring through contact closures.

Note: Persistence and Hold times are both configured in seconds. The maximum value for each is 255 seconds.

VS902 Rev. D

nevion.com | 55

5.5 Alarm Configuration

5.5.1 VS902-AED Alarm Settings Figure 16 below, shows part of the Edit Alarm Configuration menu. Each of the VS902 variants has a similar menu where alarm priorities, persistence time and hold times can be configured.

Figure 27: VS902-LC Alarm Settings

VS902 Rev. D

nevion.com | 56

Parameter Description

Sync Loss – Input X Input loss on Input X

Linearity Error – Input X Indicates that the ASI data on Input X is not evenly distributed.

Rate Violation – Input X Activated if incoming bitrate exceed the configured bitrate ceiling for Input X

(Video) Sync Error - Input X Activated when the Sync Error Count for Input X exceeds the configured Sync Error Threshold

TEI Error - Input X Activated when the TEI Error Count for Input X exceeds the configured TEI Error Threshold

Partner Feed Loss – Input X Input X is in Encoder Partner Protection mode but no partner flow detected for Input X

Partner Feed RTP Errors - Input X Activated when the Partner Feed RTP Error Count for Input X exceeds the configured Partner Feed RTP Error Threshold

PAT Error - Input X Activated when PID 0x0000 does not contain a table_id 0x00. Scrambling control field is not 0x00 for PID 0x0000 or PAT does not occur at least every 0.5s.

PID Error - Input X Activated if the Audio / Video PID does not occur at least every 5 seconds for Input X.

CC Error - Input X Activated if incorrect packet order, a lost packet or a packet occurs more than twice for Input X.

Stream Loss - Output X If SIPS is disabled, this will be caused by a Flow A loss. If SIPS is enabled, this alarm will be caused by a simultaneous Flow A and Flow B loss.

Flow A Loss - Output X Flow A network loss on Output X

Flow B Loss - Output X Flow B network loss on Output X

Sync Error - Output X Activated when the Sync Error Count for Output X exceeds the configured Sync Error Threshold

TEI Error - Output X Activated when the TEI Error Count for Output X exceeds the configured TEI Error Threshold

Linearising Error – Output X Activated when the stream rate for Output X has not stabilized, so the output may have linearity issues.

Diff(erential) Latency Error – Output X

Activated when the differential delay been packets received on the two network ports exceeds the configured DLM Error threshold for Output X.

Flow A PDV Error - Output X Activated when the measured Flow A PDV for Output X exceeds the configured PDV Error Threshold

Flow B PDV Error - Output X Activated when the measured Flow B PDV for Output X exceeds the configured PDV Error Threshold

Flow A RTP Discontinuity Error – Output X

Activated when the Flow A RTP Discontinuity Count for Output X exceeds the configured Network RTP Error Threshold

VS902 Rev. D

nevion.com | 57


Flow B RTP Discontinuity Error – Output X

Activated when the Flow B RTP Discontinuity Count for Output X exceeds the configured Network RTP Error Threshold

Post SIPS RTP Discontinuity Error - Output X

Activated when the Post SIPS RTP Discontinuity Count for Output X exceeds the configured Post SIPS RTP Error Threshold

Loss of Network/Link Loss – Network Port 1

Network Port 1 Link Loss (Link down)

Loss of Network/Link Loss – Network Port 2

Network Port 2 Link Loss (Link down)

Card License Error Activated if no valid license is installed on the card or a card is configured in a functional mode for which there is no valid license.

Link Loss – Aux Data Port Aux Port Link Loss (Link down) when Aux Port Enabled.

Transmission Rate Exceeded – Aux Data Port

Activated if the Aux Port input data rate exceeds the configured Auxiliary Data Port Rate Limit.

Received Rate Over 1G – Aux Data Port

Activated if more data is coming from the network than can be sent out of the Aux Data Port.

Autonegotiation Incomplete – Network Port 1/2

Activated if Network Port 1/2 has failed to auto negotiate an interface rate with the port it is connected to.

Table 8: VS902-AED Alarm Settings

5.5.2 VS902-J2KE(-3G) / VS902-J2KC Alarm Settings The following table describes additional VS902-J2KE(-3G)/VS902-J2KC alarms where different to the VS902-AED alarms above.


Video Input Black – Input X Activated when the luminance level of the input signal is below a predefined black threshold.

Video Input Frozen – Input X Activated when no moving content is detected in the input signal

Video CRC Errors – Input X Activated when the CRC Error Count for Input X exceeds the configured CRC Error Threshold

Video Standard Blocked – Input X Activated when input video signal is greater (bandwidth) than the configured Maximum Rate Permitted

Table 9: VS902-J2KE(-3G)/VS902-J2KC Alarm Settings

VS902 Rev. D

nevion.com | 58

5.5.3 VS902-J2KD(-3G) / VS902-J2KC Alarm Settings The following table describes additional VS902-J2KD(-3G)/VS902-J2KC alarms where different to the VS902-AED and VS902-J2KE alarms above.


Video Black – Output X Activated when the luminance level of the input signal is below a predefined black threshold.

Video Frozen – Output X Activated when no moving content is detected in the output signal

Table 10: VS902-J2KD(-3G)/VS902-J2KC Alarm Settings

5.5.4 VS902-LC Alarm Settings The following table describes additional VS902-LC alarms where different to the VS902-AED, VS902-J2KE or VS902-J2KD above.


IP Configuration Conflict Error – Output X

Activated to indicate that duplicate channels are configured to decode the same IP flow.

Reference Input Missing – Output X

Activated when an output is configured to use an external output reference (channel clocking) and no input reference signal is detected.

Reference Input Invalid Standard – Output X

Activated to indicate that the external reference signal is not a valid format for the required output video signal see Output Channel Frame Sync.

Card Over Temperature

Activated when the card operating temperature exceeds 82 degrees Celsius.

In normal operation the temperature should not reach 82 degrees and the card will automatically shut down if the temperature reaches 90 degrees to prevent damage.

Partner Protection Link Exceeded Capacity Exceeded

Activated in EPP mode when the cross link bandwidth between the Master and Slave card becomes oversubscribed.

Table 11: VS902-LC Alarm Settings

5.5.5 VS902-MA Alarm Settings The following table describes additional VS902-MA alarms where different to the VS902-AED, VS902-J2KE, VS902-J2KD and VS902-LC above.


Input Line Code Error – Input X Activated to indicate an error in the line encoding (4B5B) of the input MADI signal.

Table 12: VS902-MA Alarm Settings

VS902 Rev. D

nevion.com | 59

5.6 Alarm Priority Level Reset Following a change of card mode and subsequent card reboot, the card alarm priority levels need to be reset. This can be achieved using the Use Defaults button in the Edit Alarm Configuration menu, see below. Then Save Changes

Figure 28: Card Alarm Priority Level Reset

Note: It is recommended to reset the card alarm priorities levels after a change of card functional mode is performed.

VS902 Rev. D

nevion.com | 60

5.7 Upload/Download Card Configuration Settings The Ventura element management card allows VS902 configuration to be downloaded as a file to the computer, or allows a previously downloaded file to be uploaded to the VS902.

5.7.1 Configuration Upload Procedure

The upload configuration procedure is detailed below.

Click on the VS902 image icon.

Select the “EDIT CONFIG” tab menu.

Select the “Configuration Upload/Download” menu item. A pop-up window will appear:

Figure 29: Configuration Upload

Click on “Browse” button (shown above) and navigate to folder where all card’s configuration files are stored. Select and double click configuration file and then click on “Upload Config” button, as shown below:

Figure 30: Upload Configuration File Selection

Note: It is recommended to keep a backed up repository of card configurations such that these can be used to restore configurations in the

event of card failure or swap

VS902 Rev. D

nevion.com | 61

Click on “OK” button, as shown below:

Figure 31: Upload Configuration Warning

Because of the large number of configuration items, the upload process may take some time. When it has completed, a pop up message will be displayed, as shown below: Click on “OK” button, as shown below:

Figure 32: Upload Configuration Succeeded

5.7.2 Configuration Download Procedure

The download configuration procedure is detailed below.

Click on the VS902 image icon.

Select the “EDIT CONFIG” tab menu.

Select the “Configuration Upload/Download” menu item. A pop-up window will appear:

Figure 33: Configuration Download

Click ‘Download Config’ and a pop-up window will appear asking for the location where you would like the save the configuration file (.cfg).

VS902 Rev. D

nevion.com | 62

6 Installation

6.1 Inspection Inspect the VS902 for signs of damage. The shipping container should prevent damage to the product. Keep the shipping container, as it will be required should the product need to be returned or shipped further. Verify that the package contains the correct card and connector panel.

6.2 Handling The VS902 contains static sensitive devices and proper static free handling precautions should be observed. When individual modules are stored, they should be left in their antistatic container or placed in antistatic bags. Proper antistatic procedures should be followed when inserting and removing cards from these bags.

Caution: The VS902 should be handled carefully to prevent safety hazards and equipment damage. Follow the instructions for installation and use only

installation accessories recommended by the manufacturers.

6.3 Grounding Chassis ground connection of the equipment-mounting frame is via the earth connection on the three-pin (IEC) AC mains supply inlet. This is a safety ground and must be connected.

Warning: The chassis must be correctly earthed through the moulded plug supplied. If the local mains supply does not provide an earth connection do not

connect the unit.

Ground can also be made to the rack housing of a VS103 chassis via the two grounding nuts on the alarm panel at the rear of the chassis, or to a VS101 chassis via one grounding nut at the rear.

VS902 Rev. D

nevion.com | 63

6.4 Module Installation To install the module in a chassis, please see the instructions for the appropriate frame type in the chassis/PSU’s manual. For VS902 card installations the VS103-xx-IFAH, VS101-3H-AC, VS101-3HP-AC and VS101-3H-DC chassis should be used. The VS103-xx-IFA & VS101-3-xx chassis should not be used for VS902 card installations due to limited airflow & reduced power capability.

Note: The recommended chassis for VS902 installations are VS101-3H-AC, VS101-3HP-AC, VS101-3H-DC, VS103-DC-IFAH and VS103-

AC-IFAH

There is a restriction of installing a maximum of seven VS902-LC cards in the VS103-AC-IFAH chassis using VS134 PSUs and a maximum of one VS902-xx cards in the VS101-3H chassis. This is due to power supply limitations. Failure to observe this restriction may results in failure of the chassis PSU modules and a loss of services being carried by the cards installed in the chassis. When the VS101-3H is used the card should be installed in Slot 3, next to the fan module. There is no restriction on the number of VS902-AED, VS902-J2KE or VS902-J2KD cards that can be installed in the VS103-AC-IFAH chassis using VS134 PSU modules.

Caution: There is a restriction of installing a maximum of seven VS902-LC cards in a VS103-AC-IFAH chassis with VS134 PSUs fitted and one

VS902-xx card in a VS101-3H chassis.

The VS902 does not require any adjustment prior to use. There are no external controls on the front panel of the units other than the rotary, channel, monitor select switch. The video/audio connections are made to the BNC connectors on the rear panel. Care must be taken to provide clean connectors, both on the card & the external cables.

6.5 Installation Environment As with any electronic device, the VS902 should be installed where it will not be subjected to extreme temperatures, humidity, or electromagnetic interference. Specifically, the selected site should meet the following requirements:

The ambient temperature should be between 0 and 50 °C (32 and 122 °F).

The relative humidity should be less than 85 %, non-condensing. Do not install the unit in areas of high humidity or where there is danger of water ingress.

Surrounding electric devices should comply with the electromagnetic field (EMC) standard IEC 801-3, Level 2 (less than 3 V/m field strength).

VS902 Rev. D

nevion.com | 64

Make sure the equipment is adequately ventilated. Do not block the ventilation holes above, below or on either side of the chassis (depending on which frame the card has been installed in).

When a single VS103 chassis has been installed, ensure that a VS111 heat deflector is fitted directly below, to prevent hot air rising into the chassis.

VS902 Rev. D

nevion.com | 65

7 Connections

7.1 Front and Rear Panel Diagrams The following front panel and rear assembly drawings are not to scale and are intended to show connection order and approximate layout only.

Figure 34: Front and Rear Panel Connector Diagrams

Note that there are two variants of the VS902 rear Connector Panel.

The 1Gbps version is required when running VS902-AED, VS902-J2Kx or VS902-MA code.

The 10Gbps version is required when running the VS902-LC code.

VS902 Rev. D

nevion.com | 66

7.2 Front Panel LED's

A number of LED indicators are provided on the front panel of the card. These LEDs provide indication of the card status and current alarm conditions. The front panels LEDs are replicated on the Web interface. For each LED the table below provides a description of the indicator and the meaning of the indicator based on the colour of the LED.

Label Description VS902

IN A (1~4) Channel Input A Status

Green = signal present Amber = Signal present but Error on signal Red = Loss of signal Off = Channel disabled or not available

IN B (1~4) Channel Input Status from Partner card (used in partner encoder mode only)


OUT A (1~4) Channel Output Status (network feed A)


OUT B (1~4) Channel Output Status (network feed B – only used in SIPS protection mode)


ECG Card ECG Heart Beat / Status

Flashing Blue = the unit is up and running.

FAIL Card Fail Status

Red = Card Failure Off = No failure The Card Fail LED is lit when a system error or hardware fault is detected halting the initialization or operation of the card.

LINK NET 1 Network Port A Link Green = Link up Red = Link down

LINK NET 2 Network Port B Link Green = Link up Red = Link down

LINK AUX Auxiliary Link Green = Link up Red = Link down

ACT NET 1 (Future)

Network 1 Activity Flashing Amber = Packets received Off = No activity

ACT NET2 (Future)

Network 2 Activity Flashing Amber = Packets received Off = No activity

ACT AUX (Future)

Auxiliary Activity Flashing Amber = Packets received Off = Link Inactive

VS902 Rev. D

nevion.com | 67

Label Description VS902

DC The Power LED is lit to indicate that all internal power supplies are present.

Green = DC Power from backplane Off = Card has failed to turn on

Table 13: Description of Front Panel VS902 LED's

7.3 Rear Connector Panel

Label or Location Description

(J2) CH1 IN ASI (270 Mbps) channel 1 input




(J5) CH1 OUT ASI (270 Mbps) channel 1 output




(J24) Alarm Relay External Alarm Relay Output, see info below

(J26) IP Electrical Ethernet connector Aux Data Port

SFP Interface A Network interface Port A

SFP Interface B Network interface Port B

Table 14: VS902-AED Rear Connector Panel I/O

Label or Location

VS902-J2KE Description

VS902-J2KD Description

VS902-J2KC Description

(J2) CH1 IN HD/SD-SDI ch1 input NA HD/SD-SDI ch1 input

(J1) CH2 IN NA NA NA

(J3) CH3 IN HD/SD-SDI ch3 input NA NA

(J4) CH4 IN NA NA NA

(J5) CH1 OUT NA HD/SD-SDI ch1 output HD/SD-SDI ch1 output

(J6) CH2 OUT NA Duplicate of ch1 output Duplicate of ch1 output

(J7) CH3 OUT NA HD/SD-SDI ch3 output NA

(J8) CH4 OUT NA Duplicate of ch3 output NA





Table 15: VS902-J2K Rear Connector Panel I/O

VS902 Rev. D

nevion.com | 68

Label or Location VS902-LC Description

(J2) CH1 IN 3G, HD or SD-SDI channel 1 input



(J4) CH4 IN HD or SD-SDI channel 4 input / Analogue Reference

(J5) CH1 OUT 3G, HD or SD-SDI channel 1 output



(J8) CH4 OUT HD or SD-SDI channel 4 output





Table 16: VS902-LC Rear Connector Panel I/O

Label or Location Description

(J2) CH1 IN MADI input 1




(J5) CH1 OUT MADI output 1








Table 17: VS902-MA Rear Connector Panel I/O’s

VS902 Rev. D

nevion.com | 69

7.4 Aux Data Port

Note: Aux Port is enabled with license option VS902-SW-NET-AUX

The VS902 supports an Auxiliary Data Port located on the rear connector panel. The Aux Port is an IP port designed to support transportation of video/audio, management or other user data over an IP link. The configuration parameters for the Aux Data Port can be found in the Main tab of the Edit Card Configuration menu.

Figure 35: Aux Data Port Configuration

In order to use the Aux Data Port the Auxiliary Data Port parameter should be set to Enabled. As data carried through the Aux Data Port is always carried in a VLAN, a VLAN ID should be configured using the Auxiliary Data Port VLAN ID parameter. To prevent bandwidth oversubscription at the aggregate IP link, a bit rate ceiling can be set using the Auxiliary Data Port Rate Limit parameter. Received packets at the Aux Data Port will be dropped when the rate exceeds this ceiling parameter thus protecting the bandwidth allocated to the locally generated video/audio over IP packets (data generated as a result of the connection of video/audio signals to the inputs channels). At the receiving side of the network, the amount of data carried by the Aux Data Port is shown in the Status Summary menu in the Auxiliary Port Status section. This status is recorded as the number of packets received every 1 second.

VS902 Rev. D

nevion.com | 70

Figure 36: Aux Data Port Status

7.5 Output Reference

Note: Frame Sync is enabled with license option VS902-SW-FSYNC

VS902-LC output video signals can use an internal Frame Synchronizer in order to synchronize the timing of these video signals to coincide with a timing reference signal. This external reference can be either an analogue video signal (typically black-burst SD signal) or a digital composite signal. The analogue reference should be connected to the Input 4 connector. The digital reference can selected from either of Input 1-4 on the card and configured appropriately. See section Output Channel Frame Sync.

7.6 External Alarm Relay Output The connection for an external alarm is located on the rear connector panel. The major and minor alarm signals are from the relays on the motherboard card. The contacts will be closed to indicate an alarm. Note: when viewing the rear connector panel from the front, pin 1 is on the RHS. The signalling pin-out is as follows:

Pin Signal

1 Major Alarm

2 Major Alarm

3 Minor Alarm

4 Minor Alarm

Table 18: Pin-out for the External Alarm Relay Output

The following mapping definition is used to map alarms priority levels (see Alarm Settings) to the external alarm pins.

1

4

Major Alarm

(Normally Open)

Minor Alarm

(Normally Open)

VS902 Rev. D

nevion.com | 71

Alarm priority levels defined as

"Major" and "Critical" map to the Major Alarm pin above.

"Information", "Warning" and "Minor" map to the Minor alarm pin

"Disable" and "Log Only" levels do not activate either alarm pin

7.7 SFP/SFP+ Options The following tables list the recommended SFP and SFP+ options for use with the VS902.

7.7.1 VS902-AED, VS902-J2K(all) and VS902-MA – 1Gbps SFP modules

Model Mode Wavelength Connector Distance

SFP-TR1-850-SR Multimode 850nm LC <200m

SFP-TR1-1310-APD-SD Singlemode 1310nm LC <40km

SFP-TR1-1550-APD-SD Singlemode 1550nm LC <70km

SFP-TR1-XXXX-APD-C Singlemode 1470-1610nm LC <70km

SFP-1GE-RJ45 Electrical n/a RJ45 100m

Table 19: Recommended SFP Modules for 1Gbps interfaces

7.7.2 VS902-LC – 10Gbps SFP+ and Twin-ax modules

Model Mode Wavelength Connector Distance

SFP-TR10-850-SR Multimode 850nm LC Short

SFP-TR10-1310-LR Singlemode 1310nm LC <10km

SFP-TR10-1310-ER Singlemode 1310nm LC <40km

SFP-TR10-1310-UER Singlemode 1310nm LC <80km

SFP-TR10-1550-ER Singlemode 1550nm LC <40km

SFP-TR10-1550-UER Singlemode 1550nm LC <80km

SFP-TR10-XXXX-YYY-C 1

Singlemode 1270-1610nm LC <80km

SFP-10GE-xx Electrical n/a Twin-ax 1-10m 2

Table 20: Recommended SFP+ modules for 10Gbps interfaces

DWDM options are also available. Please contact Nevion support for more information. Note 1 10Gbps CWDM modules are available in Long Reach (LR) 10km max range, Extended Reach (ER) 40km and Ultra Extended Reach (UER) 80km variants for each wavelength. Note 2 Twin-ax modules in 1, 3, 5, 7 and 10m lengths are available.

VS902 Rev. D

nevion.com | 72

7.8 Front Panel Maintenance Port The front panel maintenance port serves as an engineering debug port. It also provides a means of upgrading one or all of the codes images stored on the card. The process for upgrading the card images is described in Section 12 Remote Upgrade Procedure.

7.9 Video Monitor Port The front panel video monitor port is currently not implemented in any of the VS902 products. This functionality is expected to be implemented in future firmware releases.

7.10 Switch Settings A 4-way dip switch S1, is located on the main PCB. A description of the switch functions and settings is provided in the table below. The dip switches are used to control the test modes. For normal operation switch 1 to 4 must be closed (down).

Switch Factory Default Settings

S1-1 DOWN / CLOSED Must be in this position for proper operation




Table 21: S1 Switch Functions

Caution: For normal operation, all switches must be in the closed position (down) otherwise the card will enter a test mode upon boot up

VS902 Rev. D

nevion.com | 73

8 Element Management

The Ventura AEMS Advanced Element Management System is a comprehensive web browser-based management system that supports the VS902-AED, VS902-J2KE, VS902-J2KD, and VS902-LC products. The VS902 cards must be used with the FCS183-AEMS or FCS101-AEMS version 4.4 or higher to set and/or change module operating parameters. The AEMS version can be found from browser screen HELP tab (see below). The AEMS Web GUI for VS902 has the ability to report alarms, current status and configuration as well as containing the ability to remotely configure all the system parameters. The AEMS also provides SNMP traps for major and minor alarms for all cards in a Ventura chassis. A full description of the FCS183-AEMS and FCS101-AEMS management cards can be found in the user manuals, which can be downloaded from the AEMS help page or obtained by contacting your local sales office.

Figure 37: Element Management Home Page

VS902 Rev. D

nevion.com | 74

9 Card Status

Information about the card status of any VS902 card can be found in the Status menus. All of the status information for the VS902 cards can be displayed by using Nevion Element Management web interface. Select the VS902 by clicking on the front panel displayed in the web browser, then click on STATUS. See Figure below. The VS902 Status information include Status Summary, Card Configuration Status, Input 1-4 Status, Output 1-4 Status, Alarm Configuration Status, Alarm Group Configuration Status, Alarm Statistics, and History.

Figure 38: VS902-LC Status Menu

VS902 Rev. D

nevion.com | 75

9.1 Status Summary The current status of the card can be displayed using the Status Summary menu option under the Status tab on the cards web interface. The card status summary window shows VS902 maintenance IP address, FPGA temperature, board temperature, IP packet rates for the network ports and current alarms, etc. The card status window can be refreshed by clicking on the refresh button. The alarms/event history can be displayed by using the history button. All windows can be saved to a file.

9.1.1 VS902-AED

Figure 39: VS902-AED Card Status Summary

VS902 Rev. D

nevion.com | 76

The information contained in the Status Summary page for each version of the VS902 is identical. For this reason, the screenshot and description of each status item for each version is not repeated here. Card Alarm Indications Sync Loss – Input x

Indicates that input X doesn’t have a signal connected that can be synchronized to. Stream Loss – Output x

Indicates loss of output signal on the relevant output. If SIPS is disabled, this will be caused by a Flow A (Network Port 1) loss. If SIPS is enabled, this alarm will be caused by a simultaneous Flow A (Network Port 1) and Flow B (Network Port 2) loss.

Link Loss – Network Port 1/2

Indicates that no Network link is detected (Link down) on Network Port 1/2 (SFP Interface A/B)

Autonegotiate Incomplete – Network Port 1/2 Indicates that Network Port 1/2 (SFP Interface A/B) has failed to autonegotiate with the port it is connected to.

Link Speed and Duplex – Network Port 1/2 Indicates the link speed that Network Port 1/2 (SFP Interface A/B) has negotiated.

Card License Error Indicates no license file installed or an error with the installed licence file.

Card License Issue Displays the reason for the Card License Error when activated.

Card Status Network Interface Statistics Good Ethernet Rx Packets - Network Port 1/Network Port 2

Displays the number of valid Ethernet packets received per second on the Network Port 1/Network Port 2 interface.

Good IP Rx Packets Network Port 1/Network Port 2

Displays the number of valid IP packets received per second on the Network Port 1/2 interface.

Good UDP Rx Packets Network Port 1/Network Port 2

Displays the number of valid UDP packets received per second on the Network Port 1/2 interface.

Errored Ethernet Rx Packets Network Port 1/Network Port 2

Displays the number of errored Ethernet packets received per second on the Network Port 1/Network Port 2 interface.

Errored IP Rx Packets Network Port 1/Network Port 2

Displays the number of errored IP packets received per second on the Network Port 1/2 interface.

VS902 Rev. D

nevion.com | 77

Errored UDP Rx Packets Network Port 1/Network Port 2 Displays the number of errored UDP packets received per second on the Network Port 1/2 interface.

Virtex FPGA Temperature

Displays internal core temperature of the on board FPGA device Board Temperature

Displays the operating temperature of the VS902 board Auxiliary Port Status Link Loss – Aux Data Port

Indicates that no Network link is detected (Link down) on Aux Data Port Interface. Transmission Rate Exceeded – Aux Data Port

Indicates that the incoming Aux Data Port bit rate is greater than the configured Auxiliary Data Port Rate Limit value (in the Main Configuration options)

Receive Rate Over 1G – Aux Data Port

Indicates that the received data rate of Aux Data Port traffic over the network interface has exceeded 1Gbps

Network Port 1/2 Rx Packets – Aux Data Port Displays the number of Aux Port Data traffic Rx packets received per second on the Network Port 1/Network Port 2 interface.

Selected Rx Flow – Aux Data Port

Indicates which of the Network Ports the Aux Data Port traffic is being taken from.

VS902 Rev. D

nevion.com | 78

9.1.2 VS902-J2K

Figure 40: VS902-J2KE Card Status Summary

VS902 Rev. D

nevion.com | 79

```

Figure 41: VS902-J2KD Card Status Summary

Card Alarm Indications Sync Loss – Input x (J2KE only)

Indicates that input X doesn’t have a signal connected that can be synchronized to. Stream Loss – Output x (J2KD only)


VS902 Rev. D

nevion.com | 80

Link Loss – Network Port 1/2 Indicates that no Network link is detected (Link down) on Network Port 1/2 (SFP Interface A/B)

Autonegotiation Incomplete – Network Port 1/2 Indicates that Network Port 1/2 (SFP Interface A/B) has failed to autonegotiate with the port it is connected to.

Link Speed and Duplex – Network Port 1/2 Indicates the link speed that Network Port 1/2 (SFP Interface A/B) has negotiated.



J2K License ID Displays vendor provided license ID of the JPEG200 compression core.











Errored UDP Rx Packets Network Port 1/Network Port 2

Displays the number of errored UDP packets received per second on the Network Port 1/2 interface.



Displays the operating temperature of the VS902 board

VS902 Rev. D

nevion.com | 81

Auxiliary Port Status Link Loss – Aux Data Port








VS902 Rev. D

nevion.com | 82

9.1.3 VS902-LC

Figure 42: VS902-LC Card Status Summary

Card Alarm Indications Sync Loss – Input x



VS902 Rev. D

nevion.com | 83

Link Loss – Network Port 1 Indicates that no Network link is detected (Link down) on Network Port 1 (SFP Interface A)

Link Loss – Network Port 2 Indicates that no Network link is detected (Link down) on Network Port 2 (SFP Interface B)









Displays the operating temperature of the VS902 board Auxiliary Port Status Link Loss – Aux Data Port








VS902 Rev. D

nevion.com | 84

9.1.4 VS902-MA

Figure 43: VS902-MA Card Status Summary

Card Alarm Indications Sync Loss – Input x



VS902 Rev. D

nevion.com | 85

Link Loss – Network Port 1 Indicates that no Network link is detected (Link down) on Network Port 1 (SFP Interface A)

Link Speed – Network Port 1 Indicates the link speed that Network Port 1 (SFP Interface A) has negotiated.

Link Loss – Network Port 2

Indicates that no Network link is detected (Link down) on Network Port 2 (SFP Interface B)

Link Speed – Network Port 2 Indicates the link speed that Network Port 2 (SFP Interface B) has negotiated.













Errored UDP Rx Packets Network Port 1/Network Port 2

Displays the number of errored UDP packets received per second on the Network Port 1/2 interface.



Displays the operating temperature of the VS902 board

VS902 Rev. D

nevion.com | 86

Auxiliary Port Status Link Loss – Aux Data Port








VS902 Rev. D

nevion.com | 87

9.2 Channel Name Status A channel description name can be assigned to each input and output channel on the VS902. The name consists of a user definable, 40 character text field which can be configured in the Edit card Configuration menu under the Edit config tab (or left blank). Once a Channel Description has been configured, this name appears in the Input/Output x Status menu.

Figure 44: Channel Description Display in Input/Output Status

Additionally, the Channel Name Status menu option under the Status tab displays the Channel Description names for all inputs and all outputs on a card.

Figure 45: Channel Name Status Menu

VS902 Rev. D

nevion.com | 88

9.3 Input Status The current status of any input to the card can be displayed using the Input Status 1 to 4 menu options under the Status tab on the cards web interface. The input status summary window contains information about the specific input, including alarms such as Sync Loss & Rate Violation.

9.3.1 VS902-AED

Figure 46: VS902-AED Input Channel Status Summary

Channel Transmission – Input x

Displays the current status of channel transmission for each input. Options are Enabled or Disabled.

Sync Loss – Input x

Indicates that the sync loss alarm is currently active on the relevant input. Bitrate – Input x

Displays the incoming TS bit rate in Mbps of the relevant input. Rate Violation – Input x

Indicates that the incoming bit rate (above) is greater than the configured bit rate ceiling for the relevant input.

ASI Packet Length – Input x

Indicates the detected packet length of the incoming TS. Stuffing Mode – Input x

Displays the stuffing mode (Packet or Byte) of the incoming TS.

VS902 Rev. D

nevion.com | 89

RS Present – Input x Indicates whether additional Reed Solomon bytes have been detected in the incoming signal.

CA Present – Input x Indicates whether the conditional access (CA) bit been detected in the incoming signal.

Linearity Error – Input x

Indicates that the Linearity error alarm is currently active on the relevant input. This alarm is activated when the ASI data on Input X is not evenly distributed.

Sync Error – Input x

Indicates that the Sync error alarm is currently active on the relevant input. This alarm is activated when the sync error count is equal or exceeds the configured error threshold.

TEI Error – Input x

Indicates that the TEI error alarm is currently active on the relevant input. This alarm is activated when the TEI error count is equal or exceeds the configured error threshold

Partner Feed Loss – Input x

Indicates a loss of the signal from the partner encoder in EPP mode. Partner Feed RTP Errors – Input x

Indicates that the Partner Feed RTP Errors alarm is currently active on the relevant input. This alarm is raised when the Partner Feed RTP Error count is greater than the configured threshold.

PAT Error – Input x Indicates when the transport stream for the relevant input is either missing the DVB Program Association Table or when the table is present but errored (protocol or format).

PMT Error – Input x Indicates when some of the Program Map Tables flagged in the PAT table are either missing or errored for the relevant input.

PID Error – Input x Indicates that the Elementary Stream Packet Identifier is missing for the relevant input.

CC Error – Input x

Indicates that a Continuity Count error has been detected on the relevant input. Sync Error Count – Input x

Displays the sync error count per second for the relevant input. TEI Error Count – Input x

Displays the TEI error count per second for the relevant input.

Programmes Present – Input x Displays the number of programmes count detected in the input transport stream for the relevant input.

VS902 Rev. D

nevion.com | 90

9.3.2 VS902-AED PMT/ES Status

The VS902-AED provides additional input status information about the input ASI signal. This information contains a breakdown of the PMT and ED PID values as well as a report of the ES PID types.

PMT Error, PMT Missing and CC Errors are also reported on a per PID basis.

The information can be located in the Input x PMT/ES Status menus under the Status tab.

Figure 47: VS902-AED Input Channel Status Summary

9.3.3 VS902-J2KE(-3G)

Figure 48: VS902-J2KE(-3G) Input Channel Status Summary



VS902 Rev. D

nevion.com | 91

Sync Loss – Input x Indicates that the sync loss alarm is currently active on the relevant input.

Video Input Standard – Input x

Displays the detected video standard of the relevant input. J2K Video Rate – Input x

Displays the video encoding rate for the relevant input. The video rate is automatically calculated from the configured TS Rate (see Section 5.2.1).

Audio Pairs Present – Input x

Displays the detected AES audio pairs present in the incoming signal for the relevant input.

Sync Error – Input x Indicates that the Sync error alarm is currently active on the relevant input. This alarm is activated when the sync error count is equal or exceeds the configured error threshold.

Video CRC Errors – Input x

Indicates that the Video CRC error alarm is currently active on the relevant input. This alarm is activated when the CRC/EDH error count is equal or exceeds the configured error threshold

Video Input Black – Input x

Indicates that the Video Input Black alarm is currently active on the relevant input. This alarm is activated when the input signal luminance content is below a certain level e.g. triggered by a 0% flat field test pattern.

Video Input Frozen – Input x

Indicates that the Video Input Frozen alarm is currently active on the relevant input. This alarm is activated when the input signal has no moving content e.g. triggered by a static test pattern.

Video Standard Blocked – Input x

Indicates that the detected input video standard rate (3G, HD or SD) exceeds the configured Maximum Rate Permitted parameter.

Partner Feed Loss – Input x

Indicates a loss of the signal from the partner encoder in EPP mode. Partner Feed RTP Errors – Input x


Sync Error Count – Input x

Displays the sync error count per second for the relevant input. CRC/EDH Error Count – Input x

Displays the CRC/EDH error count per second for the relevant input.

VS902 Rev. D

nevion.com | 92

9.3.4 VS902-LC

Figure 49: VS902-LC Input Channel Status



Sync Loss – Input x Indicates that the sync loss alarm is currently active on the relevant input.

Video Input Black – Input x

Indicates that the Video Input Black alarm is currently active on the relevant input. This alarm is activated when the input signal luminance content is below a certain level e.g. triggered by a 0% flat field test pattern.

Video Input Frozen – Input x

Indicates that the Video Input Frozen alarm is currently active on the relevant input. This alarm is activated when the input signal has no moving content e.g. triggered by a static test pattern.

Video Sync Error – Input x Indicates that the Sync error alarm is currently active on the relevant input. This alarm is activated when the sync error count is equal or exceeds the configured error threshold.

Video CRC Errors – Input x

Indicates that the Video CRC error alarm is currently active on the relevant input. This alarm is activated when the CRC/EDH error count is equal or exceeds the configured error threshold.

Video Input Standard – Input x Displays the detected video standard of the relevant input.

VS902 Rev. D

nevion.com | 93

Video Standard Blocked – Input x Activated if the detected Video Input Standard is a higher rate than the configured Maximum Rate permitted.

Sync Error Count – Input x Displays the sync error count per second for the relevant input.

CRC/EDH Error Count – Input x

Displays the CRC/EDH error count per second for the relevant input.

Audio Pairs Present – Input x Displays the detected AES audio pairs present in the incoming signal for the relevant input.

Partner Feed Loss – Input x Indicates a loss of the signal from the partner encoder in EPP mode.

Partner Feed RTP Errors – Input x


VS902 Rev. D

nevion.com | 94

9.3.5 VS902-MA

Figure 50: VS902-MA Input Channel Status Summary



Sync Loss – Input x

Indicates that the sync loss alarm is currently active on the relevant input. Bitrate – Input x

Displays the incoming bit rate in Mbps of the relevant input. MADI Channels – Input x

Displays the number of audio channels detected in the connected signal for the relevant input.

MADI Frame Rate – Input x

Displays the detected sampling rate (in kHz) of the audio channels in the connected signal for the relevant input.

Input Line Code Error – Input x

Indicates an error has been detected in the line coding (4B5B) in the incoming MADI signal.

Sync Error – Input x

Indicates that the Sync error alarm is currently active on the relevant input. This alarm is activated when the sync error count is equal or exceeds the configured error threshold.

Sync Error Count – Input x

Displays the sync error count per second for the relevant input.

VS902 Rev. D

nevion.com | 95

9.4 Output Status The current status of any output from the card can be displayed using the Output Status 1 to 4 menu options under the Status tab on the card’s web interface. The output status summary window contains information about the specific output, including alarms such as Flow A and Flow B Loss.

9.4.1 VS902-AED

Figure 51: VS902-AED Output Channel Status Summary

Output Enabled – Channel x

Displays the current status of each output. Options are Enable or Disable. Stream Loss – Output x

Indicates loss of output signal on the relevant output. If SIPS is disabled, this will be caused by a Flow A loss. If SIPS is enabled, this alarm will be caused by a simultaneous Flow A and Flow B loss.

Flow A/Flow B Loss – Output x

Indicates loss of received signal from the Flow A/Flow B Network for the relevant output.

VS902 Rev. D

nevion.com | 96

Bitrate – Output x Displays the outgoing TS bit rate of the relevant output.

ASI Packet Length – Output x

Indicates the detected packet length of the outgoing TS signal. RS Present – Output x

Indicates whether additional Reed Solomon bytes have been detected in the outgoing signal.

Sync Error – Output x

Indicates that the Sync error alarm is currently active on the relevant output. This alarm is activated when the sync error count is equal or exceeds the configured error threshold.

TEI Error – Output x

Indicates that the TEI error alarm is currently active on the relevant output. This alarm is activated when the TEI error count is equal or exceeds the configured error threshold.

Linearising Error – Output x

Indicates that the Linearity error alarm is currently active on the relevant output. This alarm is activated when the ASI data on Input X is not evenly distributed.

Diff. Latency Error – Output x

This alarm is activated when the differential delay been packets received on the two network ports exceeds the configured DLM Error threshold for that output.

Flow A/Flow B Feed PDV Error – Output x

Active when the measured PDV (Packet Delay Variation) for Flow A or Flow B is equal to or larger than the configured PDV Error Threshold for that output.

Flow A/Flow B Feed RTP Discontinuity Error – Output x

Active when the measured Flow A/Flow B RTP Discontinuity Count for Flow A or Flow B is equal to or larger than the configured Network RTP Error Threshold for that output.

Post SIPS Feed RTP Discontinuity Error – Output x

Active when the measured Post SIPS RTP Discontinuity Count for Flow A or Flow B is equal to or larger than the configured Post SIPS RTP Error Threshold for that output.

Sync Error Count – Output x

Displays the sync error count per second for the relevant output. TEI Error Count – Output x

Displays the TEI error count per second for the relevant output.

FEC Present – Output x Indicates the dimensions (Column Only/Row and Column) of the FEC matrix present on the relevant output.

FEC Dimensions – Output x

Indicates the LxD dimensions of the FEC matrix present on the relevant output.

VS902 Rev. D

nevion.com | 97

Leading Flow – Output x Indicates which is leading of the two input network flows from Network Flow A/B for the relevant output.

Differential Latency (ms) – Output x

Indicates the differential latency, in milliseconds, between the received signals from Network Flow A/B for the relevant output.

Flow A/Flow B Feed PDV (ms) – Output x

Displays the measured PDV, in milliseconds, of the received signal from Network Flow A/B for the relevant output.

Flow A/Flow B Feed RTP Discontinuity Count – Output x Displays the RTP discontinuity count per second from the received signals from Network Flow A/B for the relevant output.

Post SIPS RTP Discontinuity Count – Output x Displays the RTP discontinuity count per second from the received signals from Network Flow A/B for the relevant output.

Network Statistics Display – Output x Indicates the statistics display mode (Instantaneous/Cumulative) for the relevant output.

VS902 Rev. D

nevion.com | 98

9.4.2 VS902-J2KD(-3G)

Figure 52: VS902-J2KD(-3G) Output Status

Output status definitions different to VS902-AED above. Video Output Standard – Output x

Displays the detected video standard of the relevant output. Audio Pairs Present – Output x

Displays the detected AES audio pairs present in the outgoing signal for the relevant output.

Video Black – Output x

Indicates that the Video Black alarm is currently active on the relevant output. This alarm is activated when the output signal luminance content is below a certain level e.g. triggered by a 0% flat field test pattern.

Video Frozen – Output x

Indicates that the Video Frozen alarm is currently active on the relevant output. This alarm is activated when the output signal has no moving content e.g. triggered by a static test pattern.

VS902 Rev. D

nevion.com | 99

9.4.3 VS902-LC

Figure 53: VS902-LC Output Channel Status

Output Enabled – Channel x

Displays the current status of each output. Options are Enable or Disable.

IP Configuration Conflict Error – Output x Indicates that this output has been configured with the same IP configuration as an existing output on the same card.

Stream Loss – Output x

Indicates loss of output signal on the relevant output. If SIPS is disabled, this will be caused by a Network Flow A loss. If SIPS is enabled, this alarm will be caused by a simultaneous Network Flow A and Network Flow B loss.


Indicates loss of received signal from the Network Flow A/Flow B for the relevant output.

FEC Present – Output x

Indicates the dimensions (Column Only/Row and Column) of the FEC matrix present on the relevant output.

FEC Dimensions – Output x

Indicates the LxD dimensions of the FEC matrix present on the relevant output.

VS902 Rev. D

nevion.com | 100

Diff. Latency Error – Output x This alarm is activated when the differential delay been packets received on the two network ports exceeds the configured DLM Error threshold for that output.

Flow A/Flow B PDV Error – Output x


Flow A/Flow B RTP Discontinuity Error – Output x

Active when the measured RTP Discontinuity Count for Network Flow A or Flow B is equal to or larger than the configured Network RTP Error Threshold for that output.



Video Output Standard Detected – Output x

Displays the detected video standard of the relevant output. Reference Source – Output x

Displays the output reference source as internal (Adaptive Recovery) or external (analogue/digital).

Reference Input Missing Error – Output x Active when the configured external Reference Source signal is not detected.

Leading Flow – Output x

Indicates which is leading of the two input network flows from Network Flow A/B for the relevant output.



Flow A/Flow B PDV (ms) – Output x


Flow A/Flow B Feed RTP Discontinuity Count – Output x

Displays the RTP discontinuity count per second from the received signals from Network Flow A/B for the relevant output.


VS902 Rev. D

nevion.com | 101

9.4.4 VS902-MA

Figure 54: VS902-MA Output Channel Status Summary

Output Enabled – Output x

Displays the current status of each output. Options are Enable or Disable. Stream Loss – Output x

Indicates loss of output signal on the relevant output. If SIPS is disabled, this will be caused by a Flow A loss. If SIPS is enabled, this alarm will be caused by a simultaneous Flow A and Flow B loss.


Indicates loss of received signal from the Flow A/Flow B Network for the relevant output.

Bitrate – Output x

Displays the outgoing bit rate of the relevant output. Sync Error – Output x

Indicates that the Sync error alarm is currently active on the relevant output. This alarm is activated when the sync error count is equal or exceeds the configured error threshold.

Linearising Error – Output x

Indicates that the Linearity error alarm is currently active on the relevant output. This alarm is activated when the TS data on Input X is not evenly distributed.

VS902 Rev. D

nevion.com | 102

Diff. Latency Error – Output x This alarm is activated when the differential delay been packets received on the two network ports exceeds the configured DLM Error threshold for that output.

Flow A/Flow B Feed PDV Error – Output x


Flow A/Flow B Feed RTP Discontinuity Error – Output x

Active when the measured Flow A/Flow B RTP Discontinuity Count for Flow A or Flow B is equal to or larger than the configured Network RTP Error Threshold for that output.



Sync Error Count – Output x

Displays the sync error count per second for the relevant output. Leading Flow – Output x

Indicates which is leading of the two input network flows from Network Flow A/B for the relevant output.



Flow A/Flow B Feed PDV (ms) – Output x


Flow A/Flow B Feed RTP Discontinuity Count – Output x

Displays the RTP discontinuity count per second from the received signals from Network Flow A/B for the relevant output.


VS902 Rev. D

nevion.com | 103

9.5 License Status

The VS902 product is based on licensing in order to enable functionality. If a feature is enabled in the card configuration and no valid license file is found on that card the feature will not operate. A license is produced and installed at manufacture against a customer order. Additional features can be added to a card by uploading an additional license to the card at a later date. Please contact a local Nevion Sales Office to arrange additional licenses. The process to upload and install license files is described in the License File Installation section of this document.

Note: License files are keyed against the card serial number when produced and cannot be moved between cards.

The status of an installed license can be found under the Status tab in the Card License Details menu option. The license detail screen displays the number of channels enabled in the license along with other enabled features such as FEC. An example of the Card License Detail is shown below

Figure 55: Card License Detail Menu

If there is a problem with the license file, a Card License Error alarm will be activated. This alarm is displayed under the Status tab in the Status Summary menu. This alarm will be raised for example if no license file is installed or if the license file signature is invalid.

VS902 Rev. D

nevion.com | 104

When the Card License Error alarm is active, the card fail LED on the front panel will also flash. If a card is configured into a mode of operation for which no license has been installed, the card will report a Card License Error and provide a reason for this error alarm. For example, if a card has a license for ASI channels but the Card Functional Mode is configured as VS902-MA (MADI), the following alarm will be displayed in the Status Summary menu.

Figure 56: Card License Error

In this situation, if no licensed channels are installed for a functional mode, Channel Transmission will be automatically disabled for each input and output and these cannot be configured as Enabled by the user. In the Main configuration tab, the Channel License Allocation configuration parameter will also be automatically set to ‘No licensed channels’.

Figure 57: Channel License Allocation

9.6 Fallback Mode

Each VS902 card contains a reserved boot image location for ‘Fallback’ purposes. The fallback code image will be loaded in the event of a failure occurring during the loading, or booting from, one of the functional boot images. The purpose of the fallback code image is to ensure that the card still boots into a remotely recoverable mode upon these failure events. The card will also attempt to load the fallback code should the current active boot image become corrupted during an upgrade. A VS902 card running in Fallback mode can be noted in two ways. The representation of the card will be marked ‘VS902 FB’ and the card mode type will be labelled as ‘VS902 Fallback Mode’ as shown in the diagram below. In Fallback mode the card front panel LEDs will also display a repeating cyclic pattern, individually flashing each LED one at a time. Once a card has entered Fallback mode, limited status information is available. However, it should still be possible to report the current Maintenance IP Address and/or configure a new IP address, see below.

VS902 Rev. D

nevion.com | 105

Figure 58: VS902-Fallback mode

Figure 59: VS902-FB Control Settings

Figure 60: VS902-FB Card Status Summary

9.7 Fallback Recovery Once this information is known (Maintenance IP Address), in order to restore correct operation of the card it should be possible to either:

1. Reload new functional code images Remote Upgrade Procedure 2. Switch card Functional mode using the GUI (Card Functional Mode configuration

parameter) or AEMS command line tools (activeImage command followed by

rebootImage)

VS902 Rev. D

nevion.com | 106

10 Protection Features

10.1 Forward Error Correction (FEC)

Note: FEC is enabled with license option VS902-SW-FEC

The VS902 has built in Forward Error Correction (FEC) functionality designed to provide protection of IP packets through the transport network. With FEC enabled lost packets can be automatically regenerated using additional FEC packets. These FEC packets are generated in accordance with SMPTE2022-1/5. FEC can be enabled per Input channel as a one (Column only) or two (Row and Column) dimensional matrix and is configured in the ‘In x’ configuration menu.

Figure 61: FEC Configuration

Further information on FEC functionality and techniques can be found in Appendix A – Forward Error Correction.

10.2 Streaming Intelligent Packet Switching (SIPS)

Note: SIPS is enabled with license option VS902-SW-SIPS

The VS902 has built in Streaming Intelligent Packet Switching (SIPS) which is designed to provide the possibility of network redundancy protection. With SIPS enabled, the transmission module duplicates each video/audio stream, transmitting the Ethernet encapsulated video/audio data onto two physical (or virtual) interfaces. These duplicate streams are routed independently through the Ethernet network along diverse paths.

IP/Ethernet

NetworkVS902

S

I

P

S

ASI

SD/HD/3G-SDI

Figure 62: VS902 Diverse Path Transmission

VS902 Rev. D

nevion.com | 107

The receive module buffers both incoming streams, mediating and selecting the most appropriate packets in what is termed active-active merging for use in de-encapsulation. In this way, if one stream is impaired, good packets are delivered via the other stream and a good output stream can always be reconstructed. The combination of diverse path routing and perfect switching provides for the highest possible Quality of Service, effectively minimizing the effects of random packet losses, burst packet losses, losses due to fast re-routes, and link failures.

Figure 63: VS902 Receive SIPS Protection

For any fully seamless protection system to function, the dual media feeds presented for transport needs to be essentially coherent i.e. the same video/audio feed. The VS902 dual media flows can be launched from a single transmit card with the following variants: 1. Identical feeds transmitted out of dual physical network interfaces, with or without VLAN

tags. 2. The same RTP encapsulated media flow with different multicast group addresses

transmitted out of dual physical network interfaces, with or without VLAN tags 3. Identical feeds transmitted out of the same physical network interface, with VLAN

separation 4. The same RTP encapsulated media flow with different multicast group addresses

transmitted out of the same physical network interface, with VLAN tags The VS902 configuration for the above scenarios is achieved by setting the Network Output Mode configuration item to Stand Alone in the Main tab and the Protection configuration item to Enabled in the In 1 to In x tabs (see below).

VS902 Rev. D

nevion.com | 108

Figure 64: VS902 Receive SIPS Protection Input Config

As the A and B flows will typically be routed across network links with different delays, it is necessary for the SIPS module to wait for a period after the first signal is received before it starts outputting data, to ensure that the second signal that is received does not need to be written to the buffer after it is read out. The “SIPS Pre-buffer” configuration item allows this period to be configured to allow the system to be able to compensate for the maximum expected differential latency between the A and B flows, while minimizing the additional delay added to the system.

10.3 Encoder Partner Protection (EPP)

Note: EPP is enabled with license option VS902-SW-EPP

SIPS allows for streams to be replicated in the network and fed to two output cards, giving the maximum redundancy in the network itself.

VS902 Rev. D

nevion.com | 109

Encoder Partner Protection (EPP) provides a way of generating two "RTP coherent" streams at the source, while still providing protection against the failure of an individual encoder card (hardware redundancy). The EPP concept is that the single transmit card, which on its own is a single point of failure, is replaced by dual transmit cards which are both capable of transmitting data flows into the network. In this scenario one card acts as a Master and the other as the Slave.

Note: The dual transmit cards should be located in separate racks, rooms or even separate locations for true diverse protection.

The cross connection between the two cards can be local (direct) or via a longer Ethernet connection. In normal operation, the Master card sends it’s transmit data feed to network via its network interface A. The Slave card receives the Master card’s feed (from Master card network net interface B into Slave card net interface A) and forwards this feed out its own network net interface B. This connection between the two cards is referred to as the cross strap. The Master card transmits on both of its primary and secondary interface. The Slave card monitors the input stream from the Master and the Slave forwards the Master’s stream as its own output on network interface B.

Network Interface A

VS902ASI

SD/HD/3G-SDI

VS902

Master

Slave

Network Interface A

Network Interface B

Network Interface B

Figure 65: VS902 Encoder Partner Protection

The Slave card starts transmitting its own stream (from its input) when:

a) the Master fails b) the Slave cards detects a loss of input signal from the Master card c) loss of cross-strap (the link between the Master and Slave cards)

Note: Because switching from master to slave or back again breaks the RTP coherency, this switching is not hitless.

VS902 Rev. D

nevion.com | 110

10.3.1 EPP Configuration

To enable the EPP scenario described above, both the Master and Slave card need to be configured as follows. Configuration of the VS902 Master card:

1. Set Network Output Mode set to Master in the Main tab 2. Enable Protection in the In 1 to 4 tabs 3. Enable Partner Encoder Mode by setting this to Active.

Figure 66: VS902 Partner Protection Master Config

Configuration of the VS902 Slave card: 1. Set Network Output Mode to Slave in the Main config tab 2. Enable Protection in the In 1 to 4 tabs 3. Enables Partner Encoder Mode by setting this to Active

VS902 Rev. D

nevion.com | 111

Figure 67: VS902 Partner Protection Slave Config

There are two different configurable Slave modes:

1. Active slave where the slave card is outputting a feed all the time and 2. Passive slave where the slave card only outputs its feed upon the failure of the

master card (whose feed it is monitoring via the cross connect) In addition to the above, there are also a few other basic rules on cross channel configuration that need to be followed in order to ensure the cards behave correctly.

The dual launch addresses need to be decided – unicast or multicast, with or without VLAN tagging

The Master card needs to be configured with these two addresses for flow A and flow B on the given channel input configuration tab

The Slave card needs to be configured with these same two set of addresses

The only difference between the cards configurations is therefore the identification of Master/Slave mode in the Main config tab

Note: Using EPP both the Master and Slave card have the same configuration except for Network Output Mode (Master/Slave)

The ultimate redundant solution necessitates dual NTE hardware at each end of the path as well as full diverse signal routing through the network. For SIPS to provide fully seamless stream protection at the receive end, the dual network feeds need to be coherent - not only at the audio/data layer but also at the RTP layer, where the top level alignment and integrity analysis is performed. To provide this RTP-layer coherent presentation from the dual encoders, the two physically separate encoder systems can be cross-strapped to allow each unit to receive the feeds being emitted by the other unit. Each Encoder is then able to continually monitor and verify the integrity of the feed from the alternate unit.

VS902 Rev. D

nevion.com | 112

In this cross-strap mode, one of the transmitter units is nominated by configuration as the Master. As long as the output from this unit has full integrity, both of the units emit this flow as the main feed to the network i.e. the Slave unit receives, checks and forwards out the encapsulated signal from the Master. If the Master unit fails, the Slave unit then immediately puts its own input feed to its output. Similarly, if the Master unit detects its own audio/data input is compromised; it can start outputting the feed from the slave. This protection mechanism for encoder card failure is not a synchronous one on the initial releases of the system, though a road-mapped development would create an ‘RTP-sync’ option to allow the Slave encoder to synchronise its RTP layer to that of the master.

10.4 Output with SIPS protection

The VS902 receiver will perform SIPS packet processing of the two streams it receives when SIPS protection is enabled. SIPS protection is enabled in the Out X channel tab of the Edit Card Configuration menu (see below).

Figure 68: VS902 Output SIPS Protection Config

IP/Ethernet

NetworkVS902

S

I

P

S

VS902

S

I

P

S

ASI

SD/HD/3G-SDIASI

SD/HD/3G-SDI

Figure 69: VS902 Diverse Path Transmission with Perfect Packet Switching

IP/Ethernet

Network

VS902 ASI

SD/HD/3G-

SDI

ASI

SD/HD/3G-

SDI

VS902

VS902 VS902 ASI

SD/HD/3G-

SDI

Master

Slave

Figure 70: VS902 Encoder Partner Protection with Perfect Packet Switching

VS902 Rev. D

nevion.com | 113

10.5 Launch Delay Offset (LDO) Launch offset is a Nevion-specific technique which allows dual network feeds to be sent with a time delay between the two streams. This allows recovery from coincident network breaks using patented techniques. This launch offset is a configurable value from 0 to 250ms and can be located in the In 1 to 4 tabs. The figure below defines the launch offset between VS902 flow A and Flow B outputs.

Figure 71: VS902 Flow B Launch Delay

Note: Launch Delay Offset (LDO) is not currently supported in any VS902 designs. It is expected to be implemented in future firmware

releases.

VS902 Rev. D

nevion.com | 114

11 IP Specific Configuration

11.1 VLAN Tagging At the VS902, the IP packets from each network port can be tagged with a user-defined VLAN ID as defined by IEEE802.1Q. The valid values for VLAN ID are from 0 to 4094. Class of Service (CoS) is also supported by the VLAN Priority Code Point (PCP) value in the Ethernet frame header when using VLAN tagged frames as defined by IEEE802.1P. Valid values are from 0 to 7, where 0 is lowest priority and 7 the highest.

Figure 72: VS902 VLAN tagging of IP packets

Similarly at the VS902 receiver side, the VLAN tag of IP packets received can be removed if the VLAN ID matches the VLAN ID assigned to the transmitter side.

Figure 73: VS902 VLAN un-tagging of IP packets

Note - VLAN tags should be enabled for both flows (Flow A and Flow B) using the uncompressed linear mode (VS902-LC). Failure to enable VLAN tags on both flows could prevent the other flow from being transported correctly.

VS902 Rev. D

nevion.com | 115

Note: Enable VLAN on both Flow A and Flow B using VS902-LC mode (only). See Note 1 above.

11.2 TOS/DSCP Marking The VS902 can mark the TOS/DSCP field in the IP header of locally generated video/audio over IP packets using a user-defined value. This parameter is used for Class-of-Service prioritisation in a Differentiated Services (DiffServ) network environment. Use of TOS/DSCP depends on routers honouring this field. The browser shows the 6-bit DSCP and 2-bit ECN (or CU) fields as described in RFC2474. All of the 8 bits can be defined by the user.

0 3 64 521 7

TOS or DSCP bits ECN or CU bits

Figure 74: TOS/DSCP Fields

A number of predefined traffic class values are available using different DSCPs. These are defined as:

Default (DF) Expedited Forwarding (EF) Assured Forwarding (AF) and Class Selector (CS).

These are configured using the TOS/DSCP + ECN field. A customer custom value can also be defined by selecting ‘Custom’ in the TOS/DSCP + ECN field and then configuring an 8-bit value in the TOS/DSCP Custom + ECN field using the format shown in this section.

Figure 75: VS902 TOS/DSCP Settings

VS902 Rev. D

nevion.com | 116

12 Remote Upgrade Procedure

The first stage of any upgrade procedure is to transfer the upgrade file or package to the chassis AEMS card.

Upgrades for VS902 may be distributed in one of three ways:

A. As a combined package (.tgz file) intended for upgrading all images over IP B. As individual images (.bin.gz files) which can be upgraded over IP or the in-chassis

bus using the AEMS built in upgrade tools C. As a package intended for deployment from VideoIPath

The last of these will not be described here, contact Nevion Support if you need further information on this.

Copy upgrade image/license file to AEMS /tmp folder

1. Ensure there are no other files except default 22 & start_ok in the /tmp folder

2. Use FTP to copy the new image to the /tmp folder.

3. Start a FTP session (ftp <IP address of aems>).

4. Enter ftp user name (root) and password (qazxsw).

5. Very Important > Select binary transfer mode (bin).

6. Change to /tmp folder (cd /tmp)

7. Use lcd <path> to change the local directory to the directory from where you want to upload files e.g. (lcd c:\)

8. Transfer the upgrade image to the /tmp folder (put <filename>).

9. Close the FTP session (bye) after the transfer has been completed.

Upgrade Images

The VS902 has nine code image locations (plus a Factory Image in location 0) as follows:

Image # Default Image Comment

Image 0 Factory image 'Fallback' image which is used only for programming, or if an image becomes corrupted.

Image 1 10G Linear code.

Image 2 1G MADI code

Image 3 1G ASI code

Image 4 1G J2K Encoder

Image 5 1G J2K Decoder

Image 6 1G J2K Codec

Image 7 1G J2K 3G Encoder

Image 8 1G J2K 3G Decoder

Image 9 Empty

VS902 Rev. D

nevion.com | 117

If you have been sent a combined upgrade package (Option A above)

The procedure for applying the upgrade is as follows:

(In the following, the filename is an example only, the filename for the upgrade being installed should be used instead of vs902-upgrade-B261.tgz where appropriate)

1. Connect the VS902 front Ethernet port to the AEMS front Ethernet port or Ethernet switch & assign a valid IP address to the VS902 Maintenance IP Address, with the same network as the AEMS card

2. Log into AEMS via telnet or SSH (user = anms, password = password).

3. Become the superuser using su (password = qazxsw).

4. Change directory to /tmp the location where the code image was transferred using FTP. cd /tmp

5. Unpack the .tgz image file: tar zxf vs902-upgrade-B261.tgz

NOTE: The unpacking of the file will take about 4 minutes.

6. Delete the .tgz file to save on memory: rm vs902-upgrade-B261.tgz

7. Change into the newly created directory: cd vs902-upgrade

8. Upload code to a VS902 card (example Maintenance IP = 192.168.211.139). NOTE: Ignore messages about rebooting the card during the installation. The reboots will be handled automatically: ./vs902_upgrade.sh 192.168.211.139

The Update script will update the code automatically in steps. First it will upgrade the fallback / factory image if necessary, and activate this for upgrading the other images. Then it will update the 10G Linear code in image 1, then the other images in turn. All together this will take about 30 minutes per card. If the update is successful the script should exit and print the following message: Active Image # Rebooting 192.168.211.139 Upgrade successful

9. Delete the upgrade files when all work is completed: cd /tmp

rm –rf vs902-upgrade

10. Type exit twice to log out

Upgrade complete

VS902 Rev. D

nevion.com | 118

If you have individual upgrade files (Option B above)

The procedure for applying the upgrade is as follows:

(The filename shown is an example only, the filename for the upgrade being installed should be used instead of vs902_lin_codec_1v4_RC5_B505.gz where appropriate)

1. Decide whether you will be upgrading via IP (approximately 5 minutes per image, but physical access to the card or a pre-configured in-band management network required) or via the in-chassis bus (approximately 25 minutes per image, but no additional connectivity required)

Note: Upgrading using IP is strongly recommended as this is a much quicker process

2. If upgrading over IP, connect the VS902 front Ethernet port to the AEMS front Ethernet port or Ethernet switch & assign a valid IP address to the VS902 Maintenance IP Address, with the same network as the AEMS card. Jump to step 4 below.

3. If upgrading over the in chassis bus, determine the slot number of the card to be upgraded.

4. Select an appropriate image bank to install the image into, using the list on the previous page for guidance. It is possible to install images into banks other than the recommended list, which can be useful to allow fast switching between different versions of code.

5. Log into AEMS via telnet or SSH (user = anms, password = password)

6. Become the superuser using su (password = qazxsw).

7. Change directory to /tmp (the location where the code image was transferred using FTP): cd /tmp

8. Unpack the .bin.gz image file: gunzip vs902_lin_codec_1v4_RC5_B505.bin.gz

9. Use the listImages or listImages_udp command to determine the current content of each image bank.

Example in-chassis upgrade command: listImages 3

Example Ethernet upgrade command (example Maintenance IP = 192.168.1.2): listImages_udp 192.168.1.2

10. Use the loadImage or loadImage_udp command to load the file to the card.

Each command takes three parameters. The loadImage command is for upgrading using the in chassis bus, and takes the

slot number as the first parameter. The loadImage_udp command is for upgrading via Ethernet, and takes the IP

address of the card as the first parameter.

VS902 Rev. D

nevion.com | 119

Both commands take the image bank as the second parameter, and the filename as the third parameter. Example in-chassis upgrade command: loadImage 3 1 vs902_lin_codec_1v4_RC5_B505.bin

Example Ethernet upgrade command: loadImage_udp 192.168.1.2 1 vs902_lin_codec_1v4_RC5_B505.bin

Both the above commands will load the file “vs902_lin_codec_1v4_RC5_B505.bin” to image bank 1, which is the default for the 10G Linear code.

11. If you have more than one card to upgrade, repeat step 8 for the additional slot numbers or IP addresses.

12. If you have more than one image file to load, repeat steps 7 and 8 for the additional images. Note that if you have a lot of image files you may have to delete the earlier ones to create space on the AEMS to unpack the later ones.

13. Delete the upgrade files when all work is completed

14. The current active image (the code image the card will boot from on startup) is marked with an ‘*’ (asterisk) when the listImages or listImages_udp

command is executed.

To change the active image, use the activeImage or activeImage_udp

command. Each command takes two parameters. The activeImage command is for activating images using the in chassis bus, and

takes the slot number as the first parameter. The activeImage_udp command is for activating images via Ethernet, and takes

the IP address of the card as the first parameter. Both commands take the image bank as the second parameter. Example in-chassis upgrade command: activeImage 3 1

Example Ethernet upgrade command: activeImage_udp 192.168.1.2 1

Both the above commands will activate image bank 1.

15. The VS902 card uses the active image on startup. The card reboots when the rebootImage or rebootImage_udp command is executed.

To reboot the card use the rebootImage or rebootImage_udp command. Each

command takes one parameter. The rebootImage command is for rebooting the card using the in chassis bus, and

takes the slot number as the parameter. The rebootImage_udp command is for rebooting the card via Ethernet, and takes

the IP address of the card as the parameter. Example in-chassis upgrade command: rebootImage 3

Example Ethernet upgrade command: rebootImage_udp 192.168.1.2

16. Type exit twice to log out Upgrade complete

VS902 Rev. D

nevion.com | 120

13 License File Installation

These installation instructions explain how to install a license file onto a VS902 card using the tools built into AEMS V3.20 or later.

To install the license over UDP, AEMS V4.3 or later is required. Given the small size of the license files, there is generally no strong reason to use UDP for the installation process.

1. Transfer the license key to the /tmp directory on the AEMS card for the chassis containing the card to have the license installed, using FTP, SCP or SFTP (see Remote Upgrade Procedure detailed instructions on FTP transfer) username: anms

password: password

2. Telnet or SSH to the AEMS using the same credential as above

3. cd to /tmp directory, the location where the license file was transferred using FTP.

cd /tmp

4. Verify that the card has been correctly detected, and if any licenses are already

installed on the card, using either the in chassis bus, or over UDP. Example in-chassis upgrade command listLicense <slot_number>

or Example Ethernet upgrade command listLicense_udp <maintenance_IP_address>

The card should respond with at least: Total available Licenses = 0

If, instead, it responds with either “Error -- card does not support licenses” or “Error -- I2C communication error” verify that the you have specified the correct slot number, and that the card installed is running a version of code that supports license installation (for all images, V1.7 is the first VS902 firmware release that supports licensing)

5. Load the license to the card using the loadLicense command. Each command

takes three parameters. The loadLicense command is for upgrading using the in chassis bus, and takes

the slot number as the first parameter. The loadLicense_udp command is for upgrading via Ethernet, and takes the IP

address of the card as the first parameter. Both commands take the filename as the third parameter. Example in-chassis upgrade command loadLicense <slot_number> <license_filename>

or Example Ethernet upgrade command loadLicense_udp <maintenance IP address> <license_filename>

6. Re-run the listLicense command to verify that the card now shows the installed

license, for example:

VS902 Rev. D

nevion.com | 121

Total available Licenses = 1 VS902_900089_Lic_20140116

7. If the incorrect license file was loaded to a card it can be removed using the

removeLicense command:

removeLicense <slot_number> <license_number>

(license number is as shown by listLicense command)

8. A final license tool is showLicense command, which can display a license installed

on a card. In AEMS V4.3 and above, this tool has an option “-w” which displays the license with whitespace, which is recommended, as it makes it more readable. The usage is

showLicense -w <slot_number> <license_number>

(license number is as shown by listLicense)

VS902 Rev. D

nevion.com | 122

14 Maintenance and Storage

14.1 Maintenance No regular maintenance is required. Care however should be taken to ensure that all connectors are kept clean and free from contamination of any kind. This is especially important in fibre optic equipment where cleanliness of optical connections is critical to performance.

14.2 Storage If the equipment is not to be used for an extended period, it is recommended the whole unit be placed in a sealed plastic bag to prevent dust contamination. In areas of high humidity, a suitably sized bag of silica gel should be included to deter corrosion. Where individual circuit cards are stored, they should be placed in antistatic bags. Proper antistatic procedures should be followed when inserting or removing cards from these bags.

14.3 Operational Safety

WARNING

Operation of electronic equipment involves the use of voltages and currents that may be dangerous to human life. Note that under certain conditions dangerous potentials may exist in some circuits when power controls are in the OFF position. Maintenance personnel should observe all safety regulations. Do not make any adjustments inside equipment with power ON, unless proper precautions are observed. All internal adjustments should only be made by suitably qualified personnel. All operational adjustments are available externally without the need for removing covers or use of extender cards.

VS902 Rev. D

nevion.com | 123

Appendix A – Forward Error Correction

The normal operational mode of the public internet is that IP packets are forwarded using a “best effort” strategy implying that packets may occasionally be lost due to excessive load. To regulate the transport rate of an IP session a transmitting host will at session start ramp up the speed until the receiver starts to loose packets. The receiver will send acknowledgments as it receives packets. In the case of packet loss the source will re transmit a packet and slow down transmission rate to a level where packets are no longer lost. This is inherent in the commonly used protocol TCP (Transmission Control Protocol). In an IP network for broadcast signals however, this mode of operation becomes impractical since packet delay from source to receiver resulting from re-transmission amounts to three times the normal. It is also impractical for multicast as each individual receiver would need to request retransmissions, which in itself inflicts a bandwidth increase in a channel at the edge of overflow. Accordingly, all broadcast related IP traffic use UDP (User Datagram Protocol). Here no retransmission is included, which means that all data must be delivered in a safe manner at first attempt.

IP Stream Distortion Distortions that influence the performance of an IP video transport system, in addition to packet loss, are packet delivery time variations (jitter), and packets arriving out of order. It should be noted that a single bit error occurring within an IP packet will result in the loss of the complete packet. As IP packets and Ethernet physical link layers normally go hand in hand, IP packets will be discarded if a single bit error occurs in transmission. The Ethernet link layer is secured with a cyclic redundancy check (CRC). An Ethernet frame with bit error(s) will be discarded by the first IP switch or router because the CRC check fails. Furthermore, multiple packets may be lost during short periods due to congestion. As an IP packet contains close to 1500 bytes, or about 5% of a video frame for a video stream running at 5 Mbit/s, a lost IP packet will result in visible impairments.

Figure 76: Impairments of an IP packet stream

In Figure 76 distortions of an IP stream are visualised. The even stream of packets originating from the Tx node is modified in traversing the IP network. At the input of the Rx node the IP stream is distorted in the following ways:

The packet spacing is no longer even

The position of packet #6 has been shifted

Packet #8 is missing

VS902 Rev. D

nevion.com | 124

A properly designed IP node will handle the first two within certain limits; the input buffer size will determine the amount of jitter that can be tolerated and the time to wait for a delayed or out-of-order packet before it is deemed lost. Lost packets, however, are not recoverable unless special measures are taken.

Standardisation All since streaming of broadcast services in IP networks began the insufficient reliability of IP links has been an issue, and methods to improve performance have been devised. Due to lack of standardisation many proprietary implementations and different solutions have been put into use by equipment manufacturers. The PRO-MPEG organisation has taken the initiative to achieve a common standard for transport of video over IP. These have been published as Code of Practice (COP) #3 and #4. COP#3 considers compressed video in the form of MPEG-2 Transport Stream, while COP#4 considers uncompressed video at 270Mbit/s and higher. The IP protocol stack proposed is RTP/UDP/IP. This work has been taken over by the Video Services Forum (VSF) (http://www.videoservicesforum.org). VSF has in cooperation with SMPTE successfully brought the COP#3 and COP#4 further and COP#3 is now finalised as SMPTE 2022-1 and 2022-2. SMPTE 2022-1 focuses on improving IP packet loss ratio (PLR) performance using forward error correction techniques.

FEC Matrix SMPTE 2022-1 specifies a forward error scheme based on the insertion of additional data containing the result of an XOR-operation of packet content across a time window. By reversing the operation it is possible to reconstruct single lost packets or a burst of lost packets. The degree of protection may be selected to cover a wide range of link quality from low to heavy loss at the expense of increased overhead and delay. SMPTE 2022-2 specifies use of RTP protocols and hence all packets have a sequence number. Thus, a receiver will be able to determine if a packet has been lost. There should be no cases of packets arriving containing bit errors as packets with checksum errors are discarded at the Ethernet layer. A FEC packet containing a simple XOR-sum carried out over a number of packets at the transmitter allows the receiver to compute one lost packet by redoing the XOR process over the same packets and comparing the results with the XOR FEC packet. This allows for the regeneration of one lost packet in an ensemble of N payload packets plus one FEC packet. If two or more packets in the ensemble are lost it is not possible to regenerate any of them. Packet loss in IP systems have a tendency to come in bursts (due to congestion). Therefore the FEC XOR calculation is not done on adjacent packets; rather packets at a fixed distance are used. This can be visualised by arranging the packets in a two dimensional array and inserting them in rows in the same order as they are transmitted. Figure 77 shows LxD consecutive IP packets arranged in a matrix. The FEC checksum is calculated over the columns, which means that the distance between two packets used in an XOR calculation is L. An XOR sum is calculated for each bit position of all the packets of a column. The checksums for all bit positions constitute the FEC checksum, and is inserted in a FEC packet which is sent in addition to the payload packets. There will be one FEC packet associated with each column, and it is therefore possible to regenerate as many packets as there are columns in the matrix. In the right-most panel of Figure 77 the case is shown where a packet in the last column position has been lost. The packet may then be regenerated (shown in red) by performing XOR addition over all remaining packets in that column, including the FEC packet. This is the default FEC mode of SMPTE 2022-1.

http://www.videoservicesforum.org/

VS902 Rev. D

nevion.com | 125

Figure 77: IP packet FEC calculation matrix

However, it is not possible to correct more than one error in a column. To increase the error correction capability the specification gives the option to also include FEC over the rows. By combining the two FEC calculations it is now possible to handle more complex packet loss distribution patterns and correct up to L+D lost packets.

Figure 78: Two-dimensional FEC calculation

Figure 78 shows this arrangement. Here, checksums are also calculated for the packets in each row. This gives rise to another D FEC packets, which again means increased overhead. A drawback with a rectangular matrix arrangement is that all column-FEC packets need to be transmitted at nearly the same time as all column-FEC packets are generated when the last row of the matrix is being completed. Thus when transmitting the last row of payload packets the packet rate must be doubled in order to also send the FEC packets without generating extra payload packet delay. In itself this may cause temporary network overload with packet loss as a result. The specification imposes some rules how FEC packets should be interleaved with payload packets to avoid excessive jitter and ensuring compatibility between equipment from different manufacturers. One method is to offset the FEC columns, one example is shown in Figure 79, which also provides additional advantages.

VS902 Rev. D

nevion.com | 126

Figure 79: FEC matrix

Column offset leads to column FEC packets being generated at a more regular rate and it is possible to transmit packets with a shorter delay than with a rectangular matrix. Offsetting the columns also increases the capability to regenerate longer bursts of lost packets; the length depending on the column and row length ratio.

Figure 80: Offset FEC matrix with missing

Figure 80 shows an offset matrix with missing packets. The numbered items indicate packets lost. The figure shows that column offset may increase the capability to correct longer bursts of lost packets. In this example 9 consecutive packets are lost. Even if the row length is only 7 packets, all the 9 lost packets are reconstructed. The packets are numbered in the order they can be recovered. Packets marked 8 and 9 are protected by the same column FEC packet and are recovered by the row FEC packets after recovery of packets 1 through 7. If more than one packet is lost in a row or a column of a matrix, the possibility to recover it depends on packet location. Figure 81 shows this.

Figure 81: Uncorrectable error patterns

The red-coloured packets are lost in transmission. The pattern to the left normally results in 4 unrecoverable payload packets. However, if two of the lost packets are FEC packets, then only 2 payload packets will be lost. The pattern to the right will result in one lost payload packet.

VS902 Rev. D

nevion.com | 127

The specifications allow several parameter combinations for the FEC stream generation. The FEC matrix sizes can in principle be chosen at will to suit the operational conditions. Operators may easily be confused by the number of options, and it is not straightforward to choose the optimal FEC setting for a given scenario. For compatibility reasons SMPTE 2022-1 specifies that an MPEG-2 to IP network adapter should handle a minimum matrix size of 100 IP packets and that row length or column depth should not exceed 20. Also the shortest column length allowed is 4.

Transmission Aspects The RTP protocol must be used if FEC shall be added to the IP payload. In order to provide compatibility between equipment handling application layer FEC and equipment without that capability FEC data is transmitted using UDP port numbers different from that of the payload. Column FEC is transmitted using port number (IP payload) + 2 and row FEC (if used) is transmitted using port number (IP payload) + 4. Introducing FEC for the IP connection obviously leads to additional data overhead and consequently a higher demand on data capacity. The generated FEC packets need to be "squeezed" in between the payload packets, which will tend to increase the packet jitter experienced by the receiver. Notably, in a rectangular matrix all column-FEC packets are generated and inserted into the stream in succession. This leads to a short burst of packets in quick succession, or a considerable delay before the first packet of the next FEC frame can be transmitted (or indeed, some of each). Figure 82 illustrates the relative timing of FEC packets and payload packets. Applying an offset column structure results in a smoother packet stream. The overall packet rate will be the same in both schemes, since the same number of FEC packets are generated, but the packets will be more evenly spread in the IP stream. With larger matrix sizes the smoothing effect of an offset matrix will even more pronounced. The effect of added overhead and jitter should be considered when applying FEC to an IP video stream in a heavily loaded network. High instantaneous packet rates may cause temporary overload resulting in packet loss, defeating the object of introducing FEC in the first place.

Figure 82: FEC data transmission

Quality of Service and Packet loss in IP Networks One may ask how the FEC strategy relates to an operational IP network. Little information is available on packet loss patterns. Measurements show that up to 1% of the packets are duplicates and generated as a result of a retransmission request. Either because the packet has been lost or it has arrived too late. However, since these results are for TCP connections they merely serve to indicate an upper level for packet loss rate in an IP/MPLS network. Reported jitter measurements indicate that 0.01% of the packets were delayed

VS902 Rev. D

nevion.com | 128

more than 31ms and a fraction of those packets were delayed more than 100ms. This is also relevant for transmission of video as out-of-order packets arriving too late will be regarded as lost and must, if possible, be regenerated by FEC. There are three main factors that cause packet loss:

Occasional bit errors in the Ethernet frame caused by low noise margin or equipment fault

Buffer overflow or packet delay caused by network congestion

Packet re-routing, to circumvent a node breakdown or network bottlenecks Some of the packets will arrive late. IP packet latency will vary as a result of variable traffic load on the network. Packets that do not arrive in time will be handled as lost packets. The FEC process will thus be able to handle occasional delay increase for a few packets and maintain a satisfactory Quality of Service. A video gateway should offer a setting for permissible packet delay, which should be optimised for the operation. If the receiver buffer latency is increased it is possible to reduce the FEC overhead and still get an error-free video link. The Packet Loss Ratio (PLR) for an IP network is not a given number. Performance figures are normally in the order of 1 x 10-6, but occasionally a link may become degraded showing PLR figures like 3 x 10-3. The performance will vary over the day with the lowest performance tending to occur at about the same time every weekday and lasting for one-half to one hour. The FEC setting should be set up to handle this peak hour with low residual loss. The table of Table 22 shows the IP network performance figures to meet the quality requirements of various grades of television services, as given by ITU recommendation Y.1541. Along these lines the DVB IPTV standard sets the performance requirement for a 4Mbit/s IPTV service at 1 visible error per hour, which means an IP packet loss ratio of 1x10-6.

Profile (Typical bit rate)

One performance hit per 10 days

One performance hit per day

10 performance hits per day

Contribution (270 Mbit/s)

4 x 10-11 4 x 10-10 4 x 10-9

Primary Distribution (40 Mbit/s)

3 x 10-10 3 x 10-9 3 x 10-8

Access Distribution (3 Mbit/s)

4 x 10-9 4 x 10-8 4 x 10-7

Table 22: Recommended error performance (as per ITU)

Error Improvement So, what does it take to make FEC improve the packet error rate of an IP network link to a level acceptable for the application? Assuming packet loss occurs at random Figure 83 shows how the depth of a one-dimensional FEC matrix affects the error correcting capability.

VS902 Rev. D

nevion.com | 129

Figure 83: Error improvement using column FEC only

It is evident that the smaller the column depth the better error correcting capability. At a network packet loss rate of 10-5 adding FEC will provide up to 4 magnitudes of improved error performance. For ease of reference the diagram indicates packet loss rates resulting in one visible impairment (error hit) per day at transport stream bit rates of 40Mb/s, 270Mb/s and 1,5Gb/s, respectively. It can be seen that in a network with worst hour packet loss rate of 3x10-3 it is not possible to provide distribution of a 3Mb/s transport stream with less than 10 hits per day (i.e. packet loss rate of 4x10-7, as recommended in Table 22) using column-only FEC. In IP networks of ITU class 6 and 7 however, column-only FEC with reasonably small column depths will perform nicely for bit rates up to 270Mb/s. Distributing video transport streams over high packet loss rate networks demand use of two dimensional FEC. As explained earlier this increases the added overhead and thus the required network bandwidth.

Figure 84: Error improvement using two-dimensional FEC

VS902 Rev. D

nevion.com | 130

Figure 84 shows how adding row FEC dramatically increases performance in high packet loss networks. Reverting to the previous case, a 3Mbit/s video transport stream in an IP network with worst hour PLR of 3x10-3, a service with less than 10 error hits per day may be provided using any of the matrix sizes shown. In less error-prone networks however, using two-dimensional FEC schemes may be overkill and generate unnecessary FEC overhead.

Latency and Overhead Latency is increased when FEC is applied. The latency that can be accepted in a particular application may vary, and should be considered when setting FEC parameters. FEC packet calculation in the transmitter is done on-the-fly and adds little to the latency. In a rectangular matrix, however, all FEC packets are generated nearly at the same time, as indicated in Figure 82. FEC packets should be spread in transmission to avoid introducing extra jitter. This also contributes to latency in error packet recovery. In the receiver all packets involved in the FEC calculation must be collected before a missing packet can be recovered. Table 23 shows how different matrix sizes result in different latencies and required buffer sizes, using column-only FEC processing.

Overhead

Latency Recovery Buffer size

3 Mbps 30 Mbps 100 Mbps

XOR (5,10) 10% 175.5ms 175.5ms 5.3ms 5 IP

packets 66400 Bytes

XOR (10,10) 10% 350.9ms 35.1ms 10.5ms 10 IP

packets 132800 Bytes

XOR (20,5) 20% 350.9ms 35.1ms 10.5ms 20 IP

packets 132800 Bytes

XOR (8,8) 12.5% 224.6.5ms 22.5ms 6.7ms 8 IP

packets 84992 Bytes

XOR (10 5) 20% 175.5ms 17.5ms 5.3ms 10 IP

packets 66400 Bytes

XOR (8,5) 20% 140.4ms 14.0ms 4.2ms 8 IP

packets 53120 Bytes

XOR (5,5) 20% 87.7ms 8.8ms 2.7ms 5 IP

packets 33200 Bytes

XOR (4,6) 16.7% 84.2ms 8.4ms 2.5ms 4 IP

packets 31872 Bytes

XOR (6,4) 25% 84.2ms 8.4ms 2.5ms 6 IP

packets 31872 Bytes

Table 23: FEC latency and buffer size

Also shown is the resulting overhead and the number of packets that can be corrected. In column-only FEC there is one FEC packet per column, resulting in a 1/D increase in transmission overhead, D being the matrix column depth. i.e. in a 10 row matrix (D=10) the added overhead is 10%. The minimum allowable column depth of 4 will produce 25% overhead. In two-dimensional FEC there will be D+L FEC packets in a DxL matrix (L being the row length). Thus the added overhead is D+L/DxL, which for a 10 by 10 matrix amounts to 20%.

VS902 Rev. D

nevion.com | 131

Adding row-FEC will increase the error correcting capability without significantly increasing the latency or buffer size requirement. Applying row- and column-FEC also enables use of iterative FEC calculations to recover more missing packets. The equipment manufacturer is at liberty to determine the algorithm used in error recovery as long as the requirements and limitations of the specification are respected.

VS902 Rev. D

nevion.com | 132

Appendix B - Latency

Latency is incurred in many parts of a media transport process. Some of these latency components are optional and some are inherent in the processes used. For many applications there is a desire to minimise this latency. The following overview briefly summarises the key parts of the transport chain and where latency is potentially incurred and also explains how Nevion products allow this to be minimised to the lowest possible levels where needed.

Encode/Transmit Components Compression is the process of taking the digital video and/or audio flow and transforming it to the data that represents this feed for transport. This process is done to reduce the amount of data needing to be transported over the network. Mezzanine video compression techniques do not involve any temporal compression e.g. JPEG2000 or AVCintra this process does not take that long. For higher ratio temporal compression, this time can be considerably longer. When no compression is being used i.e. linear transport, this stage does not exist and therefore does not introduce any latency. Encapsulation is the process of forming the linear or compressed video and/or audio data into IP packets. There are trade-offs in the amount of data that is packed into each IP packet. The larger the packet, the more efficient the transport as less overhead is expended. Launch offset is a Nevion-specific technique which allows dual network feeds to be sent with a time delay between the two streams. This allows recovery from coincident network breaks using patented techniques. This launch offset is a configurable value from 0 to 250ms. Network delay is the time taken for the signal to propagate the network. This largely comprises of two different elements:

1. The propagation through the fibre or other connectivity. Data travels approximately 200km per millisecond.

2. The propagation through the network elements. The typical figure for a wire-speed router is 70us.

Decode/Receive Components SIPS is the Nevion alignment process used to provide perfect protection switching between dual network feeds. This necessitates a delay being inserted to equalise the network delays plus a configurable element to allow for shortest path first connection.

VS902 Rev. D

nevion.com | 133

PDV buffering is to allow for the worst case packet delay variation (jitter) across the network. FEC is the process of regenerating lost packets using additional FEC packets that have been sent from the source alongside the media flow. The FEC generation process does not add latency but the decode process can incur significant latency. Decapsulation is the process of extracting the video and/or video data from the IP packets. Decompression is the reconstruction of the original signal from the compressed data stream. Framestore is the process of allowing locking to a local timing reference. Depending on the phasing of the source and destination this can add up to a frames delay. VS902 Latency The VS902 J2K core-based compression has a latency of 60ms (50Hz) or 50ms (60Hz) in full-field mode. Linear (uncompressed) mode incurs no latency due to compression. Other optional latencies in the system that can be configured/incurred to the level required: SIPS launch pre-delay (LDO) – not always invoked (depends on network performance – typically would not be used) SIPS receive pre-delay – typically 3-5ms for intra-country network IP PDV de-jitter buffer – typically 3-10ms for good network at J2K rates, Decoder FEC - typically around 10ms for J2K rate feeds, if used (FEC is typically not used if SIPS is in use and comes in many configurable options that can result in significantly different latency values).

Mode Linear (Uncompressed) J2K

Bit Rate (Typical) 270Mbps, 1.5Gbps, 3Gbps 30-70Mbps (SD)

80-300Mbps (HD)

120-600Mbps (3G)

Compression 0ms ~2 fields – 40/33ms

Encapsulation 1ms 1ms

Launch Offset Optional Optional

Network 1ms per 200km plus 70us per router ‘hop’

1ms per 200km plus 70us per router ‘hop’

SIPS (0-250ms) Typically 5ms for national network Typically 5ms for national network

PDV (0-250ms) Typically 5-10ms for good private network

Typically 5-10ms for good private network

FEC (SMPTE2022) Typically 5ms @ 300Mbps Typically 10ms @ 100Mbps

Decapsulation 1ms 1ms

Decompression 0ms ~1 field – 20/17ms

Output Genlock Up to 1 frame -40/33ms Up to 1 frame -40/33ms

Table 24: Example Latency Components

VS902 Rev. D

nevion.com | 134

Appendix C – Quality of Service, Setting Packet Priority

Normal IP routing is by best effort. This does not work well for broadcast television as the video and audio components need to be transported as a continuous flow of packets without interference from other traffic over the internet. There are different techniques to improve quality-of-service. The main ones are:

MPLS (Multi Protocol Label Switching)

Layer 3 routing priority

Layer 2 routing priority

MPLS In networks running MPLS, the packets are forwarded along a predefined path from an ingress router to an egress router. Packet switching is then done according to the label and packets will be switched expediently. The MPLS label is added to the IP packet by the ingress router and removed by the egress router. The labelling is done on the basis of packet classification.

Layer 3 Routing An alternative technique to improve QoS is to use layer 3 routing and give video content packets higher priority than other data. IP packets are put into queues according to their priority. Packets with high priority are forwarded expediently and have a lower probability of being discarded due to buffer overflow. There are two ways to prioritise IP packets; using Differentiated services (Diff-serve) or precedence bits (TOS). Both these methods use the same bits in the IP header and both of them are in common use. IP precedence values range from 0 to 7. Diff-serve code point (DSCP) values range from 0 to 63.

Figure 85: Differentiated services (Diff-serve) and precedence bits (TOS)

Layer 3 prioritisation may also be combined with MPLS where layer 3 routing is used in the aggregation network and MPLS in the core network. The DSCP priority setting may be used for MPLS tagging.

VS902 TOS Configuration The Type of service (TOS/DSCP+ECN) field in VS902 In x configuration menu defines all 8 bits. Predefined values or a Custom value can be selected. The custom value is defined by the TOS/DSCP Custom + ECN field. The value used should be in accordance with traffic engineering policy of the network and should be in the range from 0 to 255.

VS902 Rev. D

nevion.com | 135

Layer 2 Priority Prioritisation can also be supported in layer 2 using VLAN tags. The 802.1q VLAN tag has 3 bits for setting the Class of Service (COS). The COS bits will be handled the same ways as Diff-serve or precedence bits regarding packet classification in the network.

VS902 COS Configuration The COS priority is entered in the VLAN Priority Code Point field in the VS902 In x

configuration menu. A value in the range from 0 to 7 should be inserted, predefined values are available. This value will be directly transferred to 3 user priority bits in the VLAN header. More information on quality of service issues and configuration can be found in the literature, e.g. router configuration guides.

VS902 Rev. D

nevion.com | 136

Appendix D - Glossary

1000Base-T

The term for the electrical Gigabit Ethernet interface. This is the most common interface for Gigabit Ethernet. Most Gigabit-enabled PCs and equipment support this interface.

3G-SDI 3Gbit High Definition - Serial Digital Interface. 3G-SDI, consisting of a single 2.970Gbit/s serial link, is standardized in SMPTE 424M that can replace the dual link HD-SDI.

AES AES3 is the standard used for the transport of digital audio signals between professional audio devices. It is also known as AES/EBU and is published by the Audio Engineering Society (AES). It is able to carry two channels of PCM audio over several different transmission mediums including balanced and unbalanced lines and optical fibre.

ARP Address Resolution Protocol. A protocol used to “resolve” IP addresses into underlying Ethernet MAC addresses.

CRC Cycle Redundancy Checking. Used to check if data is error free in SDI signals.

DiffServ Differentiated Services. A mechanism used on layer 3 - e.g. the IP layer - to differentiate between traffic of various types. DiffServ is based on the ToS/DSCP field and provides a mechanism for the network to give e.g. video traffic higher priority than other traffic (for example Internet traffic).

DSCP Differentiated Services Code Point. A value assigned in the IP header and used for Class-of-Service prioritisation in a DiffServ domain.

DVB Digital Video Broadcasting. The European consortium defining standards for transmission of digital TV broadcasts, primarily in Europe.

DVB ASI Digital Video Broadcasting Asynchronous Serial Interface. A common physical interface for transmission of MPEG2 Transport Streams (i.e. MPEG2-compressed video) over a serial interface, typically coaxial cables.

EDH Error Detection and Handling. Used to check if data is error free.

Ethernet Originally a 10 Mbit/s shared medium network type developed by Xerox. Later transformed into an official standard. Nowadays, most Ethernet networks are based on full duplex connections over twisted pair cables. Ethernet switches in the network take care of routing Ethernet frames between nodes. The speeds now supported are 10 Mbit/s, 100 Mbit/s and 1000 Mbit/s. 10Gigabit/s Ethernet networks are now emerging.

FEC Forward Error Correction. A mechanism to protect data transmission by adding redundant information. Increasing the amount of redundant data will enable the receiver to correct more errors (i.e. regenerate lost packets) in case of network data loss.

http://en.wikipedia.org/wiki/Digital_audio

http://en.wikipedia.org/wiki/Professional_audio

http://en.wikipedia.org/wiki/Audio_Engineering_Society

http://en.wikipedia.org/wiki/PCM_audio

http://en.wikipedia.org/wiki/Transmission_medium

http://en.wikipedia.org/wiki/Balanced_line

http://en.wikipedia.org/wiki/Unbalanced_line

http://en.wikipedia.org/wiki/Optical_fiber

VS902 Rev. D

nevion.com | 137

HD-SDI High Definition - Serial Digital Interface. Also known as ANSI/SMPTE SMPTE 292M-1998. A specification describing how to digitize and transmit uncompressed high definition video signals. The typical bit rate of an HD-SDI signal is 1485 Mbit/s.

HDTV High Definition Television. Television standard(s) that provide(s) improved picture resolution, horizontally and vertically, giving clearer and more detailed TV pictures.

HTTP HyperText Transfer Protocol. The fundamental protocol used on the Internet for transmission of WEB pages and other data between servers and PCs.

ICMP Internet Control Message Protocol. ICMP messages, delivered in IP packets, are used for out-of-band messages related to network operation.

IGMP Internet Group Management Protocol. IGMP is a protocol used to manage multicast on the Internet. For a host (receiver unit) to receive a multicast, it needs to transmit IGMP “join” messages in the right format. Three versions exist. IGMPv2 is commonly used today, but IGMPv3 is becoming more common, and allows for source specific multicasting (SSM).

JPEG2000 A wavelet-based image compression standard. It was created by the Joint Photographic Experts Group committee with the intention to supersede their original discrete cosine transform-based JPEG standard. JPEG2000 can operate at higher compression ratios without generating the characteristic ’blocky and blurry’ artefacts of the original DCT-based JPEG standard.

MADI Multichannel Audio Digital Interface (or AES10). Created by the Audio Engineering Society (AES) it is a communications protocol which defines the data format and electrical characteristics of an interface that carries multiple channels of digital audio.

MPEG-2 Moving Picture Experts Group 2. The compression standard used today on most satellite and cable TV digital broadcasts. MPEG-2 also includes standardisation of data transport of video using other compression techniques, and other types of information.

MPLS Multi-protocol Label Switching. A Quality of Service mechanism for IP networks that allows IP packets to flow along a predefined path in a network, improving the reliability and robustness of the transmission.

MPTS Multi Program Transport Stream. MPEG2 transport stream that carry multiple TV/Radio services.

Multicast An IP mechanism that allows transmission of data to multiple receivers. A multicast can also have several transmit sources simultaneously. In video applications, multicast is typically used to distribute a video signal from a central source to multiple destinations.

NMS Network Management System. A system used to supervise elements in an IP network. When a device reports an alarm, the alarm will be collected by the NMS and reported to the operator. NMS systems typically collect valuable statistics information about the network performance and can provide early warning to the operator of network issues.

VS902 Rev. D

nevion.com | 138

PAT Program Association Table. Holds the location of the corresponding PMTs.

PID Packet Identifier. A unique integer value used to associate elementary streams of a program.

PMT Program Map Table. Identifies and contains the locations of the streams that make up each service.

PCR Program Clock Reference. A sampled 27 MHz video clock used in MPEG2 Transport Streams. The primary purpose of the PCR is clock synchronisation of transmitter and receivers.

PDV Packet Delay Variation is the difference in end-to-end one-way delay between selected packets in a flow with any lost packets being ignored (RFC3393).

PID Packet Identifier. An 11 bit field in an MPEG2 transport packet defining a logical channel. 8192 unique logical channels may coexist in one network.

PSI/SI Program Specific Information / Service Information. These are information tables (metadata) carried in MPEG2 transport streams in addition to video and audio. The information carried is typically service/program IDs, program names and conditional access information.

QoS Quality of Service. A common term for a set of parameters describing the quality of an IP network: Throughput, availability, delay, jitter and packet loss.

RIP2 Routing Information Protocol v2. A protocol used between network routers to exchange routing tables and information.

RSVP ReSerVation Protocol. A Quality-of-service oriented protocol used by network elements to reserve capacity in an IP network before a transmission session takes place.

RTP Real-time Transfer Protocol. A protocol designed for transmission of real-time data like video and audio over IP networks.

SD-SDI Standard Definition Serial Digital Interface. Also known as ANSI/SMPTE 259M-1997 or ITU-R BT.656. A specification describing how to digitize and transmit uncompressed standard definition video signals. The typical bit rate of an SD-SDI signal is 270Mbit/s.

SDI Serial Digital Interface. Used to describe both HD-SDI and SD-SDI input and output ports.

SDTI Serial Data Transport Interface. A mechanism that allows transmission of various types of data over an SDI signal. This may be one or more compressed video signals or other proprietary data types. The advantage of SDTI is that existing SDI transmission infrastructure can be used to transport other types of data.

SDTV Standard Definition Television. The normal television standard/resolution in use today.

http://en.wikipedia.org/wiki/End-to-end_principle

http://en.wikipedia.org/wiki/One-way_delay

http://en.wikipedia.org/wiki/Flow_%28computer_networking%29

http://en.wikipedia.org/wiki/Packet_loss

VS902 Rev. D

nevion.com | 139

SFP Small Form-factor Pluggable module. A standardized mechanism to allow usage of various electrical or optical interfaces to provide Gigabit Ethernet. Several types of SFP modules exist: Single mode fibre modules for long-distance transmission and multi-mode fibre modules for shorter distances. SFP is also known as “mini-GBIC”.

SNMP Simple Network Management Protocol. A fundamental and simple protocol for management of network elements. Commonly used by Network Management Systems and other applications.

SNTP Simple Network Time Protocol is an Internet protocol used to synchronize the system clocks of computers to a time reference. It is a simplified version of the NTP protocol which is overcomplicated for many applications.

SPTS Single Program Transport Stream. MPEG2 Transport Stream that contains a single program/service.

TCP Transmission Control Protocol. A “reliable” protocol above the IP layer that provides automatic retransmission of datagrams in case of packet loss, making it very robust and tolerant against network errors. TCP is the fundamental protocol used in the Internet for WEB traffic (HTTP protocol). TCP is indented for point-to-point communication; TCP cannot be used for communication from one node to many others.

TCP/IP A common term used for the Internet protocol suite, i.e. the set of protocols needed for fundamental IP network access: TCP, IP, UDP, ARP etc.

ToS Type of Service. This is a field in the header of IP datagrams to provide various service types. It has now been “taken over” and reused by DiffServ.

Transport Stream (TS) The common name for an MPEG2 Transport Stream. A bit stream used to carry a multiplex of packets, each identified by a unique Packet Identifier (PID) defining a logical channel. A PID stream typically represents a video or an audio service.

UDP User Datagram Protocol. An “unreliable” protocol above the IP layer that also provides port multiplexing. UDP allows transmission of IP data packets to several receiving processes in the same unit/device. UDP is used in multicast applications.

Unicast Point-to-point connection. In this mode, a transmit node sends e.g. video data direct to a unique destination address.

VLAN Virtual Local Area Network, a network of units that behave as if they are connected to the same wire even though they may be physically located on different segments of a LAN.

XML eXtensible Markup Language. A common self-describing text-based data format. Used for many purposes: Meta-data, configuration files, documents, etc. The readability of the format has made it very popular and is now the basis of many types of WEB services.

VS902 Rev. D

nevion.com | 140

General environmental requirements for Nevion equipment

1. The equipment will meet the guaranteed performance specification under the following environmental conditions:

- Operating room temperature range: 0°C to 50°C - Operating relative humidity range: <85% (non-condensing) 2. The equipment will operate without damage under the following environmental

conditions: - Temperature range: 0°C to 50°C - Relative humidity range: <85% (non-condensing)

VS902 Rev. D

nevion.com | 141

Product Warranty

The warranty terms and conditions for the product(s) covered by this manual follow the General Sales Conditions by Nevion, which are available on the company web site:

www.nevion.com

VS902 Rev. D

nevion.com | 142

Appendix B Materials declaration and recycling information

B.1 Materials declaration For product sold into China after 1st March 2007, we comply with the “Administrative Measure on the Control of Pollution by Electronic Information Products”. In the first stage of this legislation, content of six hazardous materials has to be declared. The table below shows the required information.

組成名稱

Part Name

Toxic or hazardous substances and elements

鉛

Lead (Pb)

汞

Mercury (Hg)

镉

Cadmium (Cd)

六价铬

Hexavalent Chromium

(Cr(VI))

多溴联苯

Polybrominated biphenyls

(PBB)

多溴二苯醚

Polybrominated diphenyl ethers

(PBDE)

VS902 (all versions) O O O O O O

VS134 PSU O O O O O O

O: Indicates that this toxic or hazardous substance contained in all of the homogeneous materials for this part is below the limit requirement in SJ/T11363-2006. X: Indicates that this toxic or hazardous substance contained in at least one of the homogeneous materials used for this part is above the limit requirement in SJ/T11363-2006.

This is indicated by the product marking:

B.2 Recycling information Nevion provides assistance to customers and recyclers through our web site http://www.nevion.com/. Please contact Nevion’s Customer Support for assistance with recycling if this site does not show the information you require.

Where it is not possible to return the product to Nevion or its agents for recycling, the following general information may be of assistance:

Before attempting disassembly, ensure the product is completely disconnected from power and signal connections.

All major parts are marked or labeled to show their material content.

Depending on the date of manufacture, this product may contain lead in solder.

Some circuit boards may contain battery-backed memory devices.

http://www.nevion.com/

lc / vs902 j2ke( 3g) j2kd( 3g) / vs902 j2kc / vs902 manevion nordre kullerød 1 3241 sandefjord...

Documents