VIDEO INTERCONNECTION EXCHANGE (VIE) · enabling both Video Conferencing and 2 Way Video Calling...

© XConnect, in Commercial Confidence Page 1 of 18

VIDEO INTERCONNECTION

EXCHANGE (VIE)

SERVICE DESCRIPTION

Issue Number Date Reason For Issue


Table of Contents

1 Introduction ......................................................................................................................................................3

2 VIE Features ......................................................................................................................................................3

3 Technical architecture ......................................................................................................................................4

3.1 VIE Service and Network. .........................................................................................................................4

3.2 Network Overview. ...................................................................................................................................5

3.3 VIE Addressing, Routing, Policy and Example Call Flows. .........................................................................8

3.4 VIE Directory .......................................................................................................................................... 11

3.5 Interconnecting to VIE. .......................................................................................................................... 13

3.6 Protocol Support and Interworking. ...................................................................................................... 14

3.7 VIE Availability and Performance. ......................................................................................................... 15

3.8 Reporting & Settlement ......................................................................................................................... 15

4 Industry Leading & Standards Compliant ...................................................................................................... 16

4.1 OVCC ...................................................................................................................................................... 16

4.2 XConnect & OVCC Interworking ............................................................................................................ 16

4.3 ATIS ........................................................................................................................................................ 17

5 Customer Commercial Terms ........................................................................................................................ 18

5.1 Pricing .................................................................................................................................................... 18


1 INTRODUCTION

The XConnect Video Interconnection Exchange (VIE) is the world's first multilateral video exchange that enables

video calling between different video ‘managed service providers’ (MSPs)

VIE has been created to make video calling ubiquitous. VIE is a switching service that makes it simpler and

easier for video calls to be completed between different service providers and in a device agnostic manner.

VIE resolves the interconnection and interworking challenges between different video services and

platforms.

VIE offers video service providers immediate multilateral interconnection to one another, with full

configurability, control and policy.

VIE reduces the time taken and costs incurred to interconnect to multiple partners. This allows members to

reach partners where a direct interconnect may not be cost justified.

2 VIE FEATURES

VIE is built upon XConnect’s market leading multimedia hub and ENUM registry technology to deliver a secure,

neutral and carrier grade video interconnection infrastructure.

VIE: Multilateral Interconnection

The VIE service has the following features:

1. Multilateral Interconnection – MSPs can connect to the VIE platform and have immediate multilateral

interconnection with other video networks, both traditional and Over The Top (OTT) providers,

enabling both Video Conferencing and 2 Way Video Calling between the respective networks.

2. Routing and Addressing – The VIE Registry enables a number of routing and addressing schemes to be

supported across the network, simplifying internal routing plans.


3. Policy – The Registry support of ‘policy’ allows MSPs to select the other MSPs they wish to interconnect

with, and the terms of the peering relationship.

4. VIE Management Portal – Is a web based portal simplifying the management of MSP interconnect

relationships.

5. Directory Services – Accessed via the VIE management portal, the XC Video Directory enables an MSP

to quickly search and discover details for other VIE users, devices, their network and how to initiate a

Video call to them.

3 TECHNICAL ARCHITECTURE

3.1 VIE Service and Network.

The XConnect VIE service enables customers to realise the benefits of offering cross-network video services,

while minimising the effective cost of interconnection.

The VIE service is based on a multi-lateral interconnect model (also known as Federation).

The basic premise of VIE is that customers implement a single interconnect from their video network to the

XConnect VIE network, and can then exchange Video traffic with any other connected network.

The VIE network provides an ‘interconnect toolkit’ of technical and commercial functions which allows MSPs

access to a broad community of video end-points without the operational and commercial overheads or the

implementation delays normally associated with direct bi-lateral interconnection.

The VIE service consists of 5 service layers, as shown below:


VIE Service Layers

The VIE service is specifically designed to carry business critical video services, provide carrier class availability

and traffic performance. VIE provides customers the access option of either Private IP (for end to end QOS), or

the public Internet.

3.2 Network Overview.

Figure 3-1 below, shows an overview of the VIE service and functional components.


Figure 3-1 – VIE Service Overview.

The VIE service interconnects the Managed Service Provider (MSP) networks enabling exchange of

video calls.

MSPs interconnect to the VIE network at both the IP and Application (SIP) layers, and can call any

other connected MSP (if allowed by policy).

The VIE network is agnostic to the type of video calling service being offered between the MSPs, and

transports SIP based video sessions between the originating and terminating MSP. Video ‘calls’ across

the VIE network may therefore be between two user end-points (e.g. User Agent), between a user

end-point and a Multipoint Conferencing Unit (MCU) (single or multi-party conference), or between

two Multipoint Conferencing Units, depending on the MSPs preference and internal architecture.

VIE policy (realised in the VIE Registry) dictates whether a call is allowed (e.g. which MSPs can call

each other), and VIE routing suggests where to route the call. Addressing across the VIE network is

based on public E164 numbering. In a phase 2 planned release of the service, URI based dialing and

routing will be available.

All calls across the network produce call detail records. CDRs are used to provide usage and

performance reports, and where applicable are the basis for VIE inter MSP settlement services.

The VIE service can be delivered over the XConnect VIE network or can be run by the MSP’s own choice IP

network .


All components and the underlying network connectivity provide carrier grade performance and

availability and are at least replicated to avoid any single points of failure.

The VIE network includes the following functional components:-

VIE Registry – The VIE Registry is a logically centralized ‘routing and policy’ engine. The

Registry holds a mapping of VIE customer end-points addresses (and associated metadata) to

customer routes (normally a customer SBC address), and ‘policy’ logic which defines whether a

particular call is ‘allowed’ (based on business or technical rules). When a call is presented to

the VIE network, a query is made to the Registry to validate that the call is allowed, and which

route to use to terminate the call.

o Local Registry – XC can also support a VIE Local Registry which can be used by the

originating/terminating MSP to manage their own originating or terminating address

transformation or routing decisions.

Interconnect Hub – The interconnect hub is the ‘logically’ central point for interconnecting SIP

based traffic. MSPs connect their network to the Interconnect Hub via SIP trunks and can

subsequently pass calls to all other connected SPs, avoiding the need to implement multiple

direct SIP interconnects. The Interconnect Hub queries the Registry to determine whether a

particular call between SPs is ‘allowed’ through policy and if so where to route the call.

The Interconnect Hub provides the following functions:-

o Border Element (BE) – All MSP SIP interconnects to the hub terminate on the

interconnect hub BE. The BE supports SIP layer security (topology hiding, SIP message

validation), and SIP interworking (allowing different implementations and methods of

SIP to be ‘interworked’ amongst the MSPs).

o Session Control – The Session Controller’s internal routing engine queries the Registry

to determine whether a call is allowed, and if so, the appropriate SIP route for the call.

If a call requires Media Relay (e.g. for NAT traversal), the Session Controller will be the

component that handles this requirement.

o CDR Generation – A Call Detail Record is generated for every call across the

Interconnect hub. CDRs are stored in a data-warehouse and form the basis for quality

and usage reporting for the VIE services. For Federations utilizing the platform

settlement option, the CDRs also form the basis of all inter-provider settlement charges.

VIE IP Network and Media Transport – All VIE components are connected via a quality assured

private IP network. Customers can connect to this network via a dedicated private IP

interconnect (at any XC PoP), or via the public Internet.

Depending on the MSP configuration and capability, media may flow directly between MSPs

across the VIE IP network, or via media anchoring points located at XC PoPs.


Customer Portal – the VIE customer portal allows VIE customers to view and manage their VIE

environment. The VIE portal includes functions for managing numbering upload, directory,

reporting and policy. Many of the VIE management functions are also available via a web-

services API, enabling customers to integrate with their existing OSS/BSS systems.

3.3 VIE Addressing, Routing, Policy and Example Call Flows.

Unlike the PSTN or the Internet (where there is a widely recognized standard addressing and routing scheme),

current video networks have implemented diverse addressing and routing (based on public numbers, private

numbers, public URIs, private URIs, IP addresses etc.).

This presents two challenges to MSPs wishing to support inter-MSP video calls :-

What address should be provided to the MSPs enterprise customers in order to make a video call or

conference?

How does an MSP make sure that calls are routed via VIE (rather than via the Internet, or if a public

telephone number via the PSTN), and how do I make this a simple to administer process?

A key advantage of VIE is the flexibility provided by the VIE Registry to support different addressing and routing

schemes, and to enable customers to query the Registry (either the originating MSP, the terminating MSP or

both) to enhance their own internal routing systems if required.

In phase 1 of VIE it is expected that there will be a small number of addressable end-points (primarily MCU

‘meet-me’ addresses) and that a Public E.164 number rangewill be allocated to each of the MSP ‘meet-me’

services.

This has the benefit of simplicity for the originating and terminating network, and customer access viewpoints.

This is illustrated in the call flow in section the below.

When moving to direct ‘dial’ services, where the number of addressable end-points increases, and actual

customer end-point addresses need to be considered, VIE can support :-

Overlay addressing using Public E.164 or Private Number/URI.

Re-use of customer addressing schemes (public URI or E.164)

A combination of the two.

XC will work with VIE members to determine the best fit approach to reduce cost and complexity in the

Member networks. This may involve XC providing Registry partition capabilities to the VIE Members in order to

realise the addressing and routing complexities ‘in the cloud’.

3.3.1 Conference Calling with Public E.164 Numbers.

Error! Reference source not found. below shows a call flow for a conference call scenario where all calls

terminate on a MSP MCU or bridge


Figure 3-2 : Scenario 1 – Conference Call – Call Flow Example.

An end-user of MSP C wishes to set up a conference with end-users of MSP A and MSP B.

The VIE Federation members have agreed to allocate a range of 10xE.164 PSTN numbers to enable

conferencing services between the MSPs. (If the MSPs do not have E.164 numbers these can be allocated by

XC).

These numbers are loaded into the VIE Registry and associated with the SIP route to each MSPs SBC address.

In this example it is assumed that the three MSPs have a common policy which allows calls from any to any

MSP end-users.

(1) An end-user of MSP C is the hosting party for the video conference. The user schedules the conference

with MSP C booking system (this may be automatic or manual, or may be a pre-provided personal

‘Meet-Me’ conference). End-User of MSP C is given the VIE conference ‘dial-in’ number (e.g.

+12120348887) and the associated conference PIN.

(2) End-User of MSP C sends these conference ‘dial-in’ details to end-users of MSP B and MSP A.


(3) At the conference time, end-user C dials into the conference by calling the VIE conference number plus

the conference PIN.

(4) End-User of MSP B wishes to join the conference. MSP B has decided that all calls need to be passed

through MSP Bs own MCU and cannot be made directly. (For quality or commercial purposes, or where

the end-point only supports H.323 and the VIE standard is SIP). MSP B end-user will therefore contact

MSP B for instructions on how to join the conference. This process is solely the domain of MSP B and

may result in an internal access code/PIN being given to user B for this conference, or MSP B MCU

calling into user B’s system. In either case at conference time User B is is connected to MSP Bs MCU.

(5) MSP B MCU ‘calls out’ to the VIE conference number. The VIE ranges are programmed into MSP B’s

routing system to route calls via the SIP trunk to the VIE Interconnect Hub.

(6) On receiving a call on the SIP trunk from MSP B, the VIE interconnect hub queries the VIE Registry to

determine

a. Is this call allowed (i.e. is there a policy allowing a call from MSP B to MSP C).

b. What route should be used to terminate this call.

In this case calls are allowed, and the Registry will return the SIP route to MSP C SBC for this call.

(7) The Interconnect Hub forwards the call to MSP C SBC, with the allocated VIE bridge number as the

destination number. MSP C terminates the call to the relevant MCU and MSP B user is joined into the

conference.

(8) MSP A user receives the dial-in instructions from MSP C user. MSP A user has been told by MSP A that

the VIE number can be dialed directly (this may be on the MSP A portal, or following an inquiry from

MSP A). At conference time MSP A dials the conference number (+12120348887). MSP A’s routing

scheme recognizes this number as a VIE range and routes the call to the SIP trunk to the VIE

Interconnect Hub.

(9) On receiving a call on the SIP trunk from MSP A, the VIE interconnect hub queries the VIE Registry to

determine

a. Is this call allowed (i.e. is there a policy allowing a call from MSP A to MSP C).

b. What route should be used to terminate this call?

In this case calls are allowed, and the Registry will return the SIP trunk to MSP C SBC for this call.

(10) The Interconnect Hub forwards the call to MSP C SBC, with the allocated VIE bridge number as the

destination number. MSP C terminates the call to the relevant MCU and MSP A user is joined into the

conference.

Subsequent SIP signaling will be proxied via the VIE interconnect hub, and RTP media will flow across the

VIE IP network. CDRs are generated by the interconnect hub for reporting and/or settlement.


3.4 VIE Directory

The Directory enables end-users to search for the contact information of their colleagues in partner organizations directly from their browser or through their video clients user interface. The Directory provides member organization's employees with a centralized database for identifying colleagues in partner organizations; upon a successful search result users can add their colleagues to their contact list.

Users can search for colleagues by a combination of name, social identities and company name.

At the Enterprise level, the Directory maintains details of all participating enterprises available across the MSP’s network enabling organizations to quickly and easily discover and connect to partner organisations within a secure and trusted environment.

The Directory functionality includes the ability for:

MSP’s to upload and create profiles for their Enterprise customers MSP’s to manage their peering

relationships with other MSP’s connected to the VIE service including invitations to peer and

policy management

Enterprises to view, request and manage peering with other enterprises that are connected to VIE

via their respective MSP’s

End-users to be able to search the video calling information of other users and the ability to

create and maintain contact lists


VIDEO DIRECTORY – SEARCH PAGE

VIDEO DIRECTORY – ADMIN MANAGEMENT


3.5 Interconnecting to VIE.

The following section describes the general technical requirements for a MSP wishing to interconnect

to the VIE service.

In summary VIE customers will need to:-

Interconnect to the VIE network at the IP layer.

Interconnect to the VIE Interconnect Hub via SIP trunk (s).

Allocate and upload VIE accessible end-point addresses to the VIE Registry.

Upload MSP accessible customer information to the VIE Directory.

Implement internal originating and terminating routing and addressing schemes for calls

to/from the VIE network.

As part of the service implementation, XConnect will work with customers to exchange interconnect

design information, and conduct certification and interoperability testing.

3.5.1 IP Layer Interconnect and VIE Access PoPs.

Customers may interconnect to VIE via a dedicated Private IP interconnection at an XC access PoP, or

via the Public Internet.

3.5.2 Signaling Interconnect.

In the first release VIE will support SIP signaling only as standard.

XC will consider support for H.323 signaling (with interworking to SIP) as a custom option for

customers unable to support SIP, on a case by case basis.

MSPs need to establish at least one SIP trunk from their video network to the VIE interconnect hub.

MSPs may establish additional SIP trunks for resilience, or for traffic distribution.

All SIP addresses and common SIP parameter settings will be exchanged as part of the interop process.

3.5.3 RTP Media.

RTP media will flow directly between MSPs across the VIE IP network to provide the optimum QOS.

Where MSPs are unable to support this model (due to internal network design), XC can support relay

of RTP media via a media proxy.

3.5.4 Addressing, Routing and Policy.

As described above, MSPs will allocate VIE addresses (representing either to end-points or conference

bridges or both depending on the service.


The allocated addresses will be uploaded to the VIE Registry and associated with the MSP SIP trunk

route(s).

The MSP will need to establish their outgoing and incoming routing plan to send and receive calls

from VIE.

Finally the MSPs will need to determine which other MSPs they wish to exchange traffic with (i.e.

configure their VIE policy).

By default, all VIE members will automatically be configured with a Universal Policy (i.e. accept traffic

from all other Members). The MSP therefore only needs to configure policy if there are other MSP

Members which they do not want to interconnect with.

3.6 Protocol Support and Interworking.

The VIE service is designed to support the transit of standard SIP (RFC3261) based video sessions

between MSP networks (typically between MSP Session Border functions). XC will work with MSPs

during provisioning to interop test the MSP network to the VIE network.

Where required XC will support SIP signaling manipulation, to cater for interworking between

different SIP implementations and methods.

The VIE network will (as far as possible) be transparent to the type of traffic carried between

networks, and will not provide transcoding of the media stream.

MSPs will therefore be responsible for any signaling or media interworking required.

In later phases of VIE (and on a custom basis for interested MSPs) XC can support SIP to 323/XMPP

interworking, and will also consider implementing transcoding, if that proves to be commercial

required.

3.6.1 XC VIP Ready Program.

XC have initiated a Video Interoperability Program (VIP) to test video equipment vendor compatibility

with the VIE service. XC are currently certifying with the following equipment vendors:

Bluejeans

Vidyo

Vidtel

Lifesize

Polycom

Cisco

XC will continue with this program over time, and will also work with the VIE MSPs to test additional

vendor combinations.


3.7 VIE Availability and Performance.

VIE is designed to provide carrier class availability and performance.

Table 3-1 below describes the Service Quality metrics and targets for the VIE service.

Note: All measurements are between the IP interconnect points to the VIE network, and exclude any

scheduled maintenance windows.

Service Metric Description Target

One-Way Latency Time for media packets to transit between VIE

access points.

<5ms for 97.5% of packets

measured on a daily basis

(single PoP).

See table below for PoP to

PoP

Media Packet Loss % of media packets lost between VIE access

points (Private IP access)

<0.05% of total packets

measured on a daily basis.

Media Packet Jitter Delay variance for media packets to transit

between VIE access points.

<5ms for 97.5% of packets

measured on a daily basis.

Call Initiation

Processing Time

Time between sending a valid SIP Invite from the

Originating VIE access point and the SIP Invite

being forwarded to the terminating VIE access

point

<50ms for 99% of valid SIP

Invites received measured

on a monthly basis.

Service Availability

Availability of the VIE service to process calls,

where MSPs access the service via a single access

link.

99.85% availability measured

on a monthly basis.

Table 3-1 – VIE Service Quality Metrics.

3.8 Reporting & Settlement

Inter-MSP communication needs to be managed from an accounting and usage perspective. The

participating service providers need to be able to collect fees for traffic handled for other networks

and to pay for their traffic handled by third parties, and the number of participant grows the

complexity surrounding account settling grows as well.

The reporting and settlement service provides the tools and mechanisms required to support the

billing and accounting needs of multi-vendor networks based on the following tools:

Support for flexible settlement models; for example managed bill & keep, standard settlement


Quality of Service monitoring and Portal statistics

4 INDUSTRY LEADING & STANDARDS COMPLIANT

XConnect is working closely with industry bodies such as ATIS and the Open Visual Collaboration

Consortium (OVCC) to ensure VIE is consistent and inline with emerging standards and frameworks

for the interconnection and interworking of Video networks and services.

4.1 OVCC

The Open Visual Communications Consortium (OVCC) is a non-profit organization of worldwide

communications technology leaders working together to enable video collaboration across any

network, vendor platform and device.

The OVCC mission is to develop and support a ubiquitous video marketplace by establishing secure,

quality-assured, and video-capable interconnections between service providers, utilizing a consistent

signaling and dial plan implementation over a highly interoperable video infrastructure, with an

operational framework for coordination of scheduling and management functions to enable any-to-

any video communication for end users across the world.

4.2 XConnect & OVCC Interworking

XConnect is planning to offer interworking via the VIE hub to the OVCC community. This will increase the reach

of both VIE and OVCC customers by enabling video calls between each community.


XConnect VIE & OVCC Interworking

4.3 ATIS

ATIS is a technology and standards development organization committed to advancing the global information

and communications technology (ICT) industry through market-driven solutions.

ATIS has begun testing full-scale interconnection and interoperability of leading telepresence solutions. The

testing’s initial phase is anticipated to demonstrate the technical viability of multiple telepresence endpoint

types across networks, with the goal of prompting industry adoption of a solution that enables multi-provider,

multi-vendor interconnection and interoperability.

XConnect is closely monitoring the progress of the ATIS testing.


5 CUSTOMER COMMERCIAL TERMS

5.1 Pricing

Standard pricing for VIE is summarised in the table below:-

Item Price

VIE Interconnection Fee $5000

Monthly Membership Fee $1000

Transit fee per session $0.01

Clearing House - Settlement

Services

POA. Pricing can be provided on a per Session, per

Minute or by capacity usage.

Directory The XC Directory is provided free of charge for VIE

customers

Registry

The VIE registry routing service is provided free of Charge

for VIE customers.

Additional charged services from XConnect include a

Local Registry Service.

XConnect also has a Video Registry Product, which

provides internal routing capability for MSP’s. For further

information on the Local Video Registry please contact

your XConnect Account Manager.

IP Capacity

The MSP is responsible for the costs associated with

bringing the call to our POP (e.g. a private IP circuit

between the MSP and the XC PoP)

Date post:	04-Jul-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

VIDEO INTERCONNECTION EXCHANGE (VIE) · enabling both Video Conferencing and 2 Way Video Calling...

Documents