3G Synchronization

3G Sync builds on Broadsign's existing trigger feature. It allows synchronized playback between players that are on different LANs. Playback on setups with regular triggers occurs when the trigger is received. On 3G sync networks, the trigger arrives with a timestamp. The playback occurs when the time rolls around.

     

Tip: If you need to sync playback between players that are on a single LAN, see Network Synchronization.

Note: To use time-based synchronization, you must use a Network Time Protocol (NTP) client capable of syncing time very precisely.

Prerequisites

3G Sync is an advanced feature. We recommend that you be familiar with the following:

Workflow

In general, the workflow to execute 3G sync is:

  1. Create two loop policies (Master and Slave)
  2. Add two display units (Master and Slave)
  3. Create a configuration profile
  4. Book campaigns

    5. Note: It is possible to execute 3G sync with one campaign or two separate campaigns.

Notes

  • In this tutorial, we describe a generic 3G sync setup. Your setup may differ, but the underlying principles remain the same.
  • We provide an advanced tutorial for triggers in a similar use case. See Frame Synchronization.

Broadsign Control offers a feature called Synchronization Set or Sync Set. Sync Set is defined in the Loop Policy properties in the Synchronization Tab.

A Synchronization Set segregates multiple distinct groups of synchronized players on the same subnet. Ideally, each group of synchronized players should operate on a different subnet to control UDP broadcast traffic. However, if this is not possible, you can configure the Synchronization Set to create virtual boundaries between player groups.

Synchronization Set names are case-insensitive, but they must be set identically on all Slaves and Masters within the same synchronized player group.

Compatibility and Player Configuration

Note: All Players in a Synchronization Set must be on the same major version to prevent synchronization issues. For example, they must all be v13.2 Players or v14.0 Players.

Players within the same synchronization set should reuse the same player configuration profile, while those outside that synchronization set should avoid doing so.

Using manual discovery for a large local network of screens may lead to excess traffic and increased bandwidth, impacting cost-efficiency. You could experience the following issues:

  • Each Master player would have a direct TCP connection to every Slave player.
  • Each Master player would send its triggers to every Slave player.

Since the list of Masters for manual discovery is set in the configuration of a player, each "sync set" should have its own configuration for its players. See Devices and Triggers Section.

Note: To use time-based synchronization effectively, a Network Time Protocol (NTP) client capable of syncing time very precisely is required.

Background

Players on a local network can all communicate with each other. However, there may be multiple "sync sets" within this local network, with multiple Masters, playing the same content. In order to prevent the Masters within these "sync sets" from triggering each others' Slaves by accident, we provide clients with the Synchronization Set feature. It causes Slaves to ignore triggers from Masters which are from different Synchronization Sets.

Ad Copy Audio Reverberation

Since hearing is more sensitive than sight in terms of synchronization in time, a minimum de-synchronization in audio is perceived as a reverberation. As a result, only the Master player or frame will output the ad copies audio layer in a synchronized environment.

Broadsign recommends to connect all the audio devices to the audio output of the Master player to avoid any reverberation.

Example 1

  • Players A, B, C, D, E, F are in the same local network.
  • Players A, B, C are in the same "sync set". Player A is the Master.
  • Players D, E, F are in the same "sync set". Player D is the Master.

Result: Use the Synchronization Sets feature to prevent Slave players B and C from responding to triggers from Master player D, and to prevent Slave players E and F from responding to triggers from Master player A.

Example 2

  • Players A, B, C are in the same local network.
  • Players A, B, C are in the same "sync set". Player A is the Master.
  • Players D, E, F are in the same local network (but not the same network as A, B, C).
  • Players D, E, F are in the same "sync set". Player D is the Master.

Result The Synchronization Set feature is unnecessary.

3G Sync requires two loop policies: one for the Master player and one for all Slave players. The difference between each loop policy is the "synchronization" type.

To create the Master and Slave loop policies:

  1. To keep things organized, for this tutorial we recommend you create a loop policy folder called "3G Sync".

  2. In the 3G Sync folder, add a loop policy called "Master".

    • Set the Policy Settings to whatever you want. They are unimportant for this tutorial.
  3. Open the Loop Policy Properties. Go to Settings > Synchronization.
  4. Set the Synchronization Type to "Master".

    5. If you are using Cloud Sync, set the Synchronization Set field with the name of a sync set.

    This way, when talking to the cloud, the players know what players will be synced together. For more information, see Synchronization Tab.

  5. In the 3G Sync folder, add another loop policy called "Slave".
  6. In the Loop Policy Properties, set the Synchronization Type to "Slave".

    7. If you are using Cloud Sync, set the Synchronization Set field with the name of a sync set.

    This way, when talking to the cloud, the players know what players will be synced together. For more information, see Synchronization Tab.

For our example, we will need two display units: a Master and a Slave.

Note: You will need to define one player and assign it to the Master display unit. Associate any other players for synchronization to the Slave display unit.

To create the Master and Slave display units:

  1. To keep things organized, for this tutorial we recommend you create a display unit folder called "3G Sync".
  2. In the 3G Sync folder, create the Master display unit. Be sure to enter the following information:

  3. Open the Display Unit Properties, and go to General > Players.

  4. Click Add, and select the player you have defined as the "Master" player.

  5. In the 3G Sync folder, create the Slave display unit. Be sure to enter the following information:
  6. Open the Display Unit Properties, and go to General > Players.
  7. Click Add, and select the players you have defined as the "Slave" players.

3G synchronization requires a configuration profile that provides the link between the Master display unit and the Slave display unit.

You can set up your player one of two ways:

The configuration profile for Local Sync specifies:

  • that the triggers will be time-based
  • the IP address of the Master and back-up Master players

To create the configuration profile:

  1. Create a configuration. Enter the following information:

    • Welcome – For this tutorial, name the configuration "3G Sync".
    • Configuration Type – Select Player.
  2. Open the Configuration Properties, and go to the Configuration Profiles tab. Click Add.

  3. Enter the following information:

    • Welcome – Enter the name and version number of the player, for example, "3G Sync - Player v12.1".
    • Configuration Profile Version – Set the version number that corresponds to your player, for example, "12.1.0".

  4. Open the Configuration Profile Properties, and go to Devices and Triggers > Core.

  5. In the Network Triggers section, configure the following:

    • Network Triggers – Enable the feature.
    • Network Synchronization Type – Set to "Master-Slave".
    • Port – Leave at default "2325".
    • Routing Scheme – TCP
    • Manual Discovery – For best results in a 3G Sync network, we recommend enabling "Manual Discovery".

    • Master/Backup Master IP List – Appears when you select Manual Discovery. Click Add, and enter the IP address of the Master or backup Masters in your 3G sync network.

    • Trigger Type – Select "Time-based ".
  6. Click Apply.
  7. In the properties of each player you need to synchronize, go to Settings > Configuration, and click Select.
  8. Add your new configuration profile.

To create the configuration profile:

  1. Create a configuration. Enter the following information:

    • Welcome – For this tutorial, name the configuration "3G Sync".
    • Configuration Type – Select Player.
  2. Open the Configuration Properties, and go to the Configuration Profiles tab. Click Add.

  3. Enter the following information:

    • Welcome – Enter the name and version number of the player, for example, "3G Sync - Player v12.1".
    • Configuration Profile Version – Set the version number that corresponds to your player, for example, "12.1.0".

  4. Open the Configuration Profile Properties, and go to Devices and Triggers > Core.

  5. In the Network Triggers section, configure the following:

    • Network Triggers – Enable the feature.
    • Network Synchronization Type – Set to "Master-Slave".
    • Routing Scheme – Broadsign Control Live
  6. Click Apply.
  7. In the properties of each player you need to synchronize, go to Settings > Configuration, and click Select.
  8. Add your new configuration profile.

This step describes how to book one or more campaigns for 3G Sync.

The easiest way to execute 3G Sync is to use a single campaign that plays on the Master and Slave display units. See Option A: Book a Single Campaign.

If you need to play two different campaigns on the Master and Slave display units, see Option B: Book Master and Slave campaigns.

The two main parts of this step are:

  • Add the "Synchronization " (aka "Bundle Trigger Category ") page to the Add Campaign Wizard.
  • Book a single campaign or multiple campaigns.
  1. From the Options menu, select Change Options.
  2. Go to Campaigns & Events > Wizard Options.

  3. Select Synchronization.

    • This option will appear in the Add Campaign Wizard as "Bundle Trigger Category ".

  1. Add a campaign. Pay special attention to the following pages in the Add Campaign Wizard:

    • Welcome – Name the campaign "3G Sync".

    • Display Unit Targeting – Select both the Master display unit and Slave display unit to book your campaign to them (see Step 2: Add Display Units (Master/Slave)).

    • Ad Copy Selection – Select the ad copy to assign to the campaign. Ad copy duration is unimportant for player synchronization.

    • Bundle Trigger Category – Select Campaign is auto-synchronized. Also, for our example, we will select Same trigger for all bundles.

      Note: The Auto-synchronize bundles option can be found in the campaign's Trigger tab under the Media section (The Trigger Tab), as well as the bundle's Trigger tab under the Categories section (The Categories Section).

Finished! You have now set up a basic 3G Sync network.

For our example, we will need one Master campaign. You can synchronize as many Slave campaigns as you want. To synchronize the campaigns, we will refer to the triggering content as the Master Campaign and the triggered content as the Slave Campaign. You must ensure that you assign the same trigger category to both campaigns.

Note: The process for creating each campaign is the same. The only differences are the names, the display units, and the ad copies.

The two main parts of this step are:

  • Add a trigger to use in the Master and Slave campaigns.
  • Book Master and Slave campaigns.

To add a Trigger:

  1. To keep things organized, for this tutorial we recommend you create a trigger folder called "Triggers - 3G Sync".
  2. In the Triggers - 3G Sync folder, create the trigger. Be sure to enter the following information:
    • Welcome – Enter the name "3G Sync".
    • Category Type – Select Trigger, and unselect All.

  3. Click Finish.

To book Master and Slave campaigns:

  1. Add a campaign. Pay special attention to the following pages in the Add Campaign Wizard:
    • Welcome – Name one campaign "Master", and all others in the network "Slave".
    • Display Unit Targeting – Select the Master display unit to book your Master campaign to it; select the Slave display unit to book any Slave campaigns to it (see Step 2: Add Display Units (Master/Slave)).

    • Ad Copy Selection – If you want, you can select the same ad copy to assign it to each campaign, whether Master or Slave. Ad copy duration is unimportant for player synchronization.
    • Bundle Trigger Category
      • For each campaign, whether Master or Slave, ensure that Campaign is auto-synchronized is not selected.
      • Click the Select button and select the 3G Sync trigger category for both the Master and Slave campaigns (the trigger that you have created earlier):

Finished! You have now set up a basic 3G Sync network.