...

• prevention of redundant transcoding of the same stream on two or more transcoders in CDN
• CDN extended information displaying
• channel quality control between CDN nodes
• node state periodic sending

Prevention of redundant transcoding of the same stream on two or more transcoders in CDN

...

CDN extended information displaying

Since buikld 5.2.471 CDN information output was added or extended to statistics page, to CLI and to REST API

Using CLI

WCS CLI command

show cdn-nodes

displays CDN version supported by node and group which node belongs to

Ip            State  Processing state    Role       Version Group
------------------------------------------------------------------
192.168.0.102 ACTIVE NEW_STREAMS_ALLOWED TRANSCODER 2.3     null
192.168.0.187 ACTIVE NEW_STREAMS_ALLOWED EDGE       2.3     null

In this case, CDN version matching result will be displayed for ACTIVE node and CDN version explicitly set will be displayed for PASSIVE node (see below)

Using REST API

REST API query /cdn/show_nodes returns CDN version supported by node

[                                            
  {                                          
    "version": "2.3",                        
    "role": "TRANSCODER",                    
    "globalState": "ACTIVE",                 
    "processingState": "NEW_STREAMS_ALLOWED",
    "id": "192.168.0.102"                    
  },                                         
  {                                          
    "version": "2.3",                        
    "role": "EDGE",                          
    "globalState": "ACTIVE",                 
    "processingState": "NEW_STREAMS_ALLOWED",
    "id": "192.168.0.187"                    
  }                                          
]                                            

In this case, CDN version matching result will be displayed for ACTIVE node and CDN version explicitly set will be displayed for PASSIVE node (see below)

Channel quality control between CDN nodes

Since build 5.2.483 channel quality control ability in Origin -> Transcoder -> Edge direction is added. To enable this feature, set the outbound bitrate sending interval  value in seconds

outbound_video_rate_stat_send_interval=1

on Origin and Transcoder nodes.

In this case, the outbound and inbound bitrate values on subscriber node side are periodically comparing with publisher side one. The steady divergence of those values means channel bandwidth decrease. The peaks and sudden changes are smoothed by Kalman filter. Channel quality mertic and statistics for the stream can be checked by REST API query.

Checking channel quality metric and statistics using REST API

• HTTP: http://test.flashphoner.com:8081/rest-api/cdn/stats/print

• HTTPS: https://test.flashphoner.com:8444/rest-api/cdn/stats/print

Where:

• test.flashphoner.com -WCS server address
• 8081 - REST / HTTP port
• 8444 - HTTPS port
• rest-api - mandatory URL part
• /cdn/stats/print - REST method used

REST queries should be sent to node from which statistics should be get. For example, on Edge node statistics can be checked for the stream received from Origin or Transcoder, and on Transcoder node for the stream received from Origin

REST queries and response states

{
 "name":"test",
 "host":"192.168.0.111",
 "format":"json"
}

{
    "192.168.0.111": [
        {
            "fps": 30, 
            "inboundBitrate": 1658292, 
            "nack": 0, 
            "name": "test", 
            "outboundBitrate": 1692676, 
            "quality": "PERFECT"
        }
    ]
}

Parameters

The query without stream name returns all the sreams statistics received from the CDN node defined. The qury without node returns all the streams statistics received from other CDN nodes if the stream name is not set

Response formats

By default, statistics is returned in JSON format:

POST /rest-api/cdn/stats/print HTTP/1.1
Content-Length: 19
Content-Type: application/json
Host: test.flashphoner.com:8081
{
    "name": "test"
}

HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Content-Length: 125
Content-Type: application/json
{
    "192.168.0.111": [
        {
            "fps": 31, 
            "inboundBitrate": 1052794, 
            "nack": 81, 
            "name": "test", 
            "outboundBitrate": 1048518, 
            "quality": "PERFECT"
        }
    ]
}

Prometeus format is also supported:

POST /rest-api/cdn/stats/print HTTP/1.1
Content-Length: 43
Content-Type: application/json
Host: test.flashphoner.com:8081
{
    "format": "prometheus", 
    "name": "test"
}

HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Content-Length: 397
Content-Type: plain/text

cdn_connection_quality{param="inboundBitrate",node="192.168.0.111",name="test"} 1249049
cdn_connection_quality{param="outboundBitrate",node="192.168.0.111",name="test"} 1240717
cdn_connection_quality{param="quality",node="192.168.0.111",name="test"} 3
cdn_connection_quality{param="fps",node="192.168.0.111",name="test"} 30
cdn_connection_quality{param="nack",node="192.168.0.111",name="test"} 81

Channel quality metric is shown as follows

Node state periodic sending

To reduce impact of channels quality between CDN nodes to CDN current state collection on each node, there was a couple of parameters added to control the period of CDN node state components sending to another nodes

Backward compatibility with CDN 2.2, 2.1, 2.0

Controller node in previous CDN version

For previous CDN versions node, Controller node is Origin.

CDN 2.1 nodes will choose a route to stream playback without Controller node even if this node is in the group.

CDN versions matching

Since build 5.2.471, CDN versions matching works as follows: when CDN signaling connection is established, nodes send version supported to each other. If versions are differ, node with later version will fall it to earlier one. For example if Edge 2.3 is connecting to CDN 2.2, it will send CDN 2.2 compatible messages only to another nodes. At all the CDN point this Edge server will look like CDN 2.2 supporting node.

Every node periodically sends its version to another nodes to escape versions mismatch after losing the connection. The version refresh period is set in milliseconds with the following parameter

cdn_nodes_version_refresh_interval=90000

By default, version refresh period is 90 seconds.

PASSIVE node version assign

When node goes to PASSIVE state after losing the connection or by setting with /cdn/enforce_state REST query, the message exchange with this node will stop. Another nodes will suppose PASSIVE node to support CDN version set by the following parameter

cdn_force_version=2.0

By default, CDN 2.0 is assignade to PASSIVE node.

For eaxmple, if one Edge in CDN 2.3 loses the connection with another servers, CDN nodes will suppose this Edge to be CDN 2.0 until it restores CDN connection and passes CDN versions matching.

Known limits

To choose a stream playback route using Controller node, Edge node should be in the same group, and this group must be set in CDN node settings:

...