Grass Valley AMPP Core Integration

Driver Maturity

Production

Recommended for normal production use.

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Minimum hi Version: v2.7.3

Overview

The Grass Valley^® AMPP^™ Core Integration discovers AMPP fabrics, Nodes, workloads, routing Sources, and Destinations. It controls routes, synchronizes aliases with hi names, and receives route-state updates through the AMPP notification service.

Network Requirements

Connection Model: hi initiates outbound API requests to the configured AMPP platform URL.
Multicast / Unicast: Unicast control traffic. Media transport is managed by AMPP.
VLAN / IGMP: Follow the AMPP deployment design.
Bandwidth: Control traffic only.
IP Version: Determined by the configured platform URL and deployment.
Firewall: Permit outbound HTTP(S) access from hi to the AMPP identity, fabric, matrix, state, control, and notification APIs.

Standards Conformance

Standard	Conformance	Notes
GV AMPP API	Implemented	Identity fabric matrix routing state control and notification surfaces

Operator Workflow

UI Surface in hi: Routing Matrix, Topology, and Inventory
Resources Exposed: Selected fabrics, Nodes, workloads, producers, consumers, Sources, and Destinations. hi controls supported routes and synchronizes aliases.
Routing Semantics: AMPP routing Sources and Destinations are mapped to hi Sources and Destinations.
Name Workflow: Operators can read aliases, write hi Primary Names as aliases, or reset names from AMPP.
Tally Relationship: The Core Integration exposes an AMPP Tally-provider capability.

Connection Methods

Connection: AMPP Identity API

Property	Value
Protocol	Grass Valley AMPP Identity API
Transport	HTTP or HTTPS from the configured platform URL
Default Port	From the configured platform URL
Authentication	AMPP API key used to obtain a bearer token
Encryption in Transit	Provided when the configured URL uses HTTPS
Connection Model	Outbound token exchange
Required License	hiAMPP
Traffic Flow	Outbound request with inbound token response

Connection: AMPP Fabric API

Property	Value
Protocol	Grass Valley AMPP Fabric API
Transport	HTTP or HTTPS from the configured platform URL
Default Port	From the configured platform URL
Authentication	Bearer token obtained through the Identity API
Encryption in Transit	Provided when the configured URL uses HTTPS
Connection Model	Outbound API requests
Required License	hiAMPP
Traffic Flow	Outbound requests with inbound fabric and Node data

Connection: AMPP State API

Property	Value
Protocol	Grass Valley AMPP State API
Transport	HTTP or HTTPS from the configured platform URL
Default Port	From the configured platform URL
Authentication	Bearer token obtained through the Identity API
Encryption in Transit	Provided when the configured URL uses HTTPS
Connection Model	Outbound API requests
Required License	hiAMPP
Traffic Flow	Outbound requests with inbound workload data

Connection: AMPP Matrix API

Property	Value
Protocol	Grass Valley AMPP Matrix API
Transport	HTTP or HTTPS from the configured platform URL
Default Port	From the configured platform URL
Authentication	Bearer token obtained through the Identity API
Encryption in Transit	Provided when the configured URL uses HTTPS
Connection Model	Outbound routing and alias requests
Required License	hiAMPP
Traffic Flow	Bidirectional routing and alias control

Connection: AMPP Notification API

Property	Value
Protocol	Grass Valley AMPP Notification API
Transport	HTTP or HTTPS from the configured platform URL
Default Port	From the configured platform URL
Authentication	Bearer token obtained through the Identity API
Encryption in Transit	Provided when the configured URL uses HTTPS
Connection Model	Outbound mailbox subscription maintained by hi
Required License	hiAMPP
Traffic Flow	Route-state notifications from AMPP to hi

Required Configuration

Parameter	Description	Default
Platform URL	Full HTTP(S) URL of the AMPP platform	`https://`
Api Key	API key generated through AMPP identity management	-
Fabrics	AMPP fabrics controlled by the integration	None
Read Aliases	Read AMPP aliases into hi Primary Names	-
Write Aliases	Write hi Primary Names to AMPP aliases	-
Reset Primary Name	Restore Primary Names from AMPP names	-

Device-Side Setup

Follow Grass Valley AMPP Core Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Fabric Node and Workload Discovery	Read-only	Enumerate fabrics/Nodes and workloads exposed by AMPP.
Routing Inventory	Read-only	Read producers, consumers, routing Sources, and routing Destinations.
Route Control	Read/write	Request or clear routes between supported AMPP endpoints.
Alias Synchronization	Read/write	Read and write producer and consumer aliases.
Notifications	Read-only updates	Subscribe to AMPP mailbox topics and process route changes.
Tally Provider	Read-only state	Consume and expose supported AMPP Tally information to hi.

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies devices that use the same protocol or connection method but have not been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

Tested With

Grass Valley AMPP

Potentially Compatible (Not Yet Verified)

Other AMPP tenancies, fabrics, and workloads that expose the Fabric, State, Matrix, and Notification APIs used by this integration.

Known Limitations

Available workloads and routing resources depend on the selected AMPP fabrics and API-key permissions.
An API key is valid only for the AMPP tenancy in which it is created. Create the key in the tenancy that hi controls.

Caution

Validate alias ownership before writing hi names into a production AMPP deployment.

What's Not Supported

AMPP account, subscription, or cloud-infrastructure administration.
Media processing configuration that is not exposed as a supported routing or alias operation.
Sending control commands to AMPP workloads. hi reads workload information only.
AMPP salvos.

Trademarks

Note

AMPP is a trademark or registered trademark of Grass Valley USA, LLC or its affiliated companies.

All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.

RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Grass Valley unless explicitly stated.