GCXS - Dutch Interconnect Alliance - Product … - Dutch...•...

© GCXS -‐ in Commercial Confidence -‐ of 19

Global Communication Access Dutch Interconnect Alliance (DIA)

Customer Product Description


TABLE OF CONTENTS.

Table of Contents. ................................................................................................................................................... 2

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

2 The Drivers and Benefits of Dutch Interconnect Alliance. .............................................................................. 4

2.1 NGN Interconnection – Issues and Opportunities. ................................................................................. 4

2.2 NGN Interconnection – The Dutch Interconnect Alliance way. .............................................................. 5

2.3 DIA -‐ Benefits Summary. ......................................................................................................................... 6

3 DIA -‐ Platform and Functional Overview. ........................................................................................................ 7

3.1 DIA Availability and Performance. .......................................................................................................... 9

4 DIA Products. ................................................................................................................................................ 10

4.1 Dutch National Alliance (DNA). ............................................................................................................. 10

4.1.1 Example Call Flow. ........................................................................................................................ 11

4.1.2 DNA – Performance Targets. ......................................................................................................... 12

4.1.3 Settlement for DNA traffic. ........................................................................................................... 13

4.2 Dutch Private Alliance (DPA). ................................................................................................................ 14

4.3 International Outbound and Inbound. .................................................................................................. 15

5 Interconnecting to DIA. ................................................................................................................................. 15

6 Operational Support. .................................................................................................................................... 17

6.1.1 Network Monitoring and Repair. .................................................................................................. 17

6.1.2 Interconnect Implementation. ...................................................................................................... 17

7 Commercial. .................................................................................................................................................. 17

7.1 Contractual Model. ............................................................................................................................... 17

7.2 DIA Pricing. ............................................................................................................................................ 17

7.3 Alliance Inter SP Settlement. ................................................................................................................ 18

7.3.1 Dutch National Alliance (DNA) – Settled ...................................................................................... 18

7.3.2 DNA -‐ Bill and Keep. ...................................................................................................................... 19


1 INTRODUCTION

The Global Communication Access (GCXS) Dutch Interconnect Alliance (DIA) service is a set of network capabilities and product features which facilitate interconnection between Next Generation (NGN) Service Providers (SPs) to enable the exchange of ‘VoIP’ (and other ‘media over IP’) traffic.

Unlike traditional TDM or VoIP bi-‐lateral interconnection, the DIA service is based on ‘multi-‐lateral’ IP interconnection across a purpose built VoIP ‘Alliance’ network. This provides the following benefits to participating SPs :-‐

• Support for cross network VoIP services -‐ The DIA service is designed to enable high quality voice, HD voice and other ‘multi-‐medial’ over IP services across SP boundaries enhancing the revenue potential.

• Reduced Opex costs – The DIA requires a single interconnect to the cloud for each SP, so minimises the technical and commercial resources required to set-‐up and maintain multiple interconnect arrangements.

• Reduced time to interconnect -‐ by connecting to the DIA cloud, SPs have immediate access to all other connected SPs (who they wish to interconnect with).

• Simplify the interconnect process – The DIA service provides tools and resources to take away the complexity associated with multiple interconnection including interworking, addressing, commercial settlement etc.

• Experience, Neutrality and Product Ownership – the DIA service is provided by a trusted and neutral partner with significant experience in the Dutch market. GCXS will not compete with our SP customers and will remain focussed on interconnection, a common requirement for all SPs. DIA customers have a strong say in the development of the DIA product to ensure it meets the needs of our customers now and in the future.

The following sections of this document describe the overall DIA service, the various product options available and an overview of the technical implementation.


2 THE DRIVERS AND BENEFITS OF DUTCH INTERCONNECT ALLIANCE.

The DIA service enables ‘cross SP’ support for VoIP (and other media over IP) calls, while minimising the effective cost of interconnecting ‘NGN’ networks.

The DIA service is built on a carrier class, neutral interconnect network and supports a range of different product features.

The following sections provide an overview of the challenges of interconnection in the NGN world and highlight the benefits of the DIA service.

2.1 NGN INTERCONNECTION – ISSUES AND OPPORTUNITIES.

Most Service Providers (SP) are deploying NGN/IMS networks to take advantage of the cost savings and additional service features (and therefore revenue opportunities) offered by ‘Multi-‐media VoIP’ services vs traditional TDM telephony.

Whilst VoIP features (such as HD voice and video telephony) may be supported within an SPs network, experience has shown (for example with SMS) that only when these features are available ‘across networks’ do they become mass market adopted and successful.

Today, most calls between NGN networks transit the TDM PSTN, as shown below :

NGNNetwork

PSTN

GW

GW GW

GW

NGNNetwork

NGNNetwork

NGNNetwork

NGN Interconnection via the TDM PSTN

This interconnect model has considerable disadvantages to the NGN Service Providers:-‐

• Advanced VoIP features will not work between networks.

• Cost of TDM-‐VoIP Gateways to convert traffic.

• Reduction in voice quality due to VoIP-‐TDM conversions.

To overcome these disadvantages, NGN SPs have started to implement direct bi-‐lateral VoIP Interconnects between their networks, as shown below:


NGNNetwork

NGNNetwork

NGNNetwork

NGNNetwork

NGN Interconnection – Direct Bi-Lateral

Whilst this interconnect model can support VoIP services across networks, each SP has to implement and administer each individual interconnection (both technically and commercially). This represents a considerable cost in network and human resources (with the appropriate level of technical expertise), and the number of direct bi-‐lateral interconnects will therefore be cost limited.

2.2 NGN INTERCONNECTION – THE DUTCH INTERCONNECT ALLIANCE WAY.

The DIA service enables NGN SP customers to realise the benefits of providing cross network advanced VoIP services, whilst minimising the effective cost of interconnection compared with the direct bi-‐lateral model. This is shown below:

NGNNetwork

NGNNetwork

NGNNetwork

NGNNetwork

NGN Interconnection – DIA

Dutch Interconnect

Alliance


The DIA service is a multi-‐lateral interconnect model (also known as Alliance).

Customers connect their NGN network (IP interconnect and SIP interconnect) to the DIA service , and can then send and receive VoIP traffic to/from any other connected network on a ‘policy’ basis.

DIA will support a number of product features, allowing customers to select the best interconnect service (in terms of traffic types supported, quality of service requirements, settlement models etc.) to suit their business.

The DIA service is designed to carry advanced VoIP services, and to provide carrier class availability and traffic performance required for business critical commercial services.

GCXS have partnered with XConnect (a leading player in the NGN interconnect market) to leverage the expertise, experience and technology of both businesses to deliver a truly carrier class, next generation interconnect solution.

2.3 DIA - BENEFITS SUMMARY.

Customers of the DIA service will benefit from the following:-‐

• Simple to implement NGN interconnection which supports end-‐to-‐end VoIP services across networks.

• High quality VoIP interconnection, with guaranteed QOS and availability, as good as the PSTN.

• Reach multiple networks with a single interconnect, reducing the technical, operational and commercial costs & risks of multiple direct interconnections.

• Reduced time to implement multiple interconnects.

• Bandwidth aggregation – efficient use of IP interconnect bandwidth by aggregation of traffic to multiple partners.

• Flexibility – Where possible GCXS will work with customers to tailor the implementation to their specific network requirements.

• Neutrality – GCXS will not compete with our customers, and all members are listened to equally.

• Experience – GCXS and XConnect have years of experience in deploying and operating NGN interconnection solutions.

• Future Direction – GCXS will work with our members to define the future direction of DIA as members deploy and enhance their NGN networks and service set.


3 DIA - PLATFORM AND FUNCTIONAL OVERVIEW.

Figure 3-‐1 below shows a functional overview of the DIA platform. Note this example shows Dutch Numbering being loaded into the Registry from the COIN NP database. Numbers (representing either customer numbers or destinations) and routes may also be uploaded by customers directly, or obtained from other data sources depending on the interconnect application being provided:-‐

DIARegistry

COINNP Data

QOS IP Network Interconnect

Hub

SP CNetwork

SP BNetwork

SP ANetwork

+31123 +31456 +31789

+31123 = SP A+31456 = SP B+31789 = SP C

+31123 = SP A = SIP:[email protected]+31456 = SP B= SIP:[email protected]+31789 = SP C= SIP:[email protected]

ENUMQuery

SIP/RTPMedia

IP Interconnect

Link

Figure 3-‐1 – DIA Functional Overview.

The DIA service is delivered by the integration of a number of functional ‘components’. 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.

• DIA Number Portability (NP) Database – The DIA NP database contains the authoritative mapping of Dutch Telephone Numbers (TN) to ‘owning’ Service Provider’ (as allocated and regulated by the Dutch telecom regulator). The DIA NP database is updated from the COIN NP database

•

• DIA Registry – The DIA Registry is the ‘brain’ of the DIA service. The Registry fulfils three functions :-‐

Maurice Vonk� 2-9-13 15:27Deleted: Figure 3-‐1


o Number/Address Registry – this holds the list of available addresses and any associated data. For example in the DIA service, the Registry will hold the Dutch Telephone numbers mapped to their SP owners. This information is obtained from the COIN NP database.

o Policy Logic – Policy logic defines whether a call is allowed based on either commercial (eg is SP A allowed to send calls to SP B ?), and/or technical (eg can TN A send a call to TN B, are they compatible ?) rules.

o Routing Logic – Routing logic defines the ‘route’ returned by the Registry for a given ‘call’ scenario. The route returned may be different based on the TN dialled, the originator, the type of call etc.

• Interconnect Hub – The interconnect hub is the central point for interconnecting SIP Signalling and Media between DIA customers. SPs connect their VoIP network to the Interconnect Hub and can pass calls to all other connected SPs, avoiding the need to implement multiple direct VoIP 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 Session Border Control – All SP SIP interconnects to the hub terminate on the interconnect hub SBC. The SBC supports SIP layer security (topology hiding, Call Admission Control, B2BUA, SIP message validation), and SIP interworking (allowing different implementations and methods of SIP to be ‘interworked’ amongst the SPs).

o Stateful SIP Proxy – The SIP Proxy routes the SIP messages between the SPs. The proxy's internal routing engine queries the Registry to determine whether a call is allowed, and the appropriate SIP route for the call. The SIP Proxy routing engine supplements the routing data received from the Registry to allow more complex routing scenarios if required (eg first choice, second choice etc.). If a call requires Media Relay, the proxy will allocate an appropriate address and port.

o Media Relay – The media relay is an optional element, and can be used to support particular call scenarios where media topology hiding or NAT traversal are required. Use of the media relay for a particular call is controlled by the SIP Proxy.

o CDR Generation – A Call Detail Record is generated for every call across the hub. CDRs are stored in a data-‐warehouse and form the basis for quality and usage reporting for the DIA services. For Alliances utilizing the platform settlement option, the CDRs also form the basis of all inter-‐provider settlement charges.

• DIA IP Network – The DIA elements, sit on a guaranteed QOS IP network to ensure quality for both media and signalling. Customers may connect to the DIA network via private IP interconnect, or via the public Internet.


3.1 DIA AVAILABILITY AND PERFORMANCE.

DIA is designed to provide carrier class availability and performance, so that customers can interconnect their VoIP traffic with performance and quality at least equal to that delivered by the PSTN.

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

Note: All measurements are between the IP interconnect points to the DIA platform, and exclude any scheduled maintenance windows. Metrics do not apply to Public Internet connected customers.

Service Metric Description Target

One-‐Way Latency Time for media packets to transit between SP DIA access points.

<10ms for 97.5% of packets measured on a daily basis.

Media Packet Loss % of media packets lost between SP DIA access points.

<0.05% of total packets measured on a daily basis.

Media Packet Jitter Delay variance for media packets to transit between SP DIA 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 SP DIA access point and the SIP Invite being forwarded to the terminating SP DIA access point

<50ms for 99% of valid SIP Invites received measured on a monthly basis.

Service Availability

Availability of the DIA Exchange service to process calls, where SPs access the service via a single access link.

99.85% availability measured on a monthly basis.

Table 3-‐1 – DIA Service Quality Metrics.

Maurice Vonk� 2-9-13 15:27Deleted: Table 3-‐1


4 DIA PRODUCTS.

The DIA network described above is used to create a number of different interconnect products. Customers can subscribe to one or all of the DIA products depending on their business requirements.

DIA products will be rolled out over time based on customer demand, and GCXS are happy to hear from customers where additional products or features would be beneficial. Initially the following products will be available :-‐

• Dutch National Alliance – A public interconnect Community of Dutch national service providers, for exchanging Dutch on-‐net national traffic.

• Dutch Private Alliance – A product allowing a Service Provider to create their own interconnect Community with selected partners to terminate any traffic types.

• International Outbound – A to Z PSTN termination via the XConnect Global Alliance network.

• International Inbound – Termination of XConnect Internationally Originated traffic into the Dutch and other transit markets.

4.1 DUTCH NATIONAL ALLIANCE (DNA).

The Dutch National Alliance (DNA) product enables multi-‐lateral peering of Dutch National traffic between on-‐net Dutch Service Provider members.

The DNA service is a peering service, therefore the following rules apply :-‐

• Only Dutch licensed operators with telephone numbers issued by OPTA can become members.

• Traffic is only allowed between On-‐Net numbers (ie no transit traffic) owned by the Members (ie either allocated by Opta or ported-‐in).

• Members must terminate all calls to their own TNs, and all TNs must be available.

• Traffic will generally be expected to balance over time.

• Members can decide to opt-‐out of peering with specific other Members.

• Members can choose either settlement free, or GXCS will settle for the interconnect traffic.


4.1.1 Example Call Flow. Figure 4-‐1 below shows an example call flow for a Dutch National Alliance call.

DIARegistry

COIN NP Data

InterconnectHub

SP CNetwork

SP BNetwork

SP ANetwork

+31123 +31456 +31789

+31123 = SP A+31456 = SP B+31789 = SP C

+31123 = SP A = SIP:[email protected]+31456 = SP B= SIP:[email protected]+31789 = SP C= SIP:[email protected]

1

4

Call +31789

ENUMQuery

35

QOS IP Network

6 62

Figure 4-‐1 – Dutch National Alliance Call-‐Flow.

SP A, B and C are Dutch SPs with numbers allocated by OPTA.

The XC Registry holds the TNs allocated to the 3 SPs (obtained from the COIN NP database). These TNs are associated with the SIP trunks set-‐up to each SP.

(1) SP A receives a call to +31789. SP A needs to determine whether this call can be sent via the Alliance i.e. is this TN on-‐net. SP A can determine this in three ways :-‐

a. SP A may have access to the COIN data within an existing internal routing system.

b. Send all national calls to the DNA service, non-‐supported calls will be rejected and SP A can route advance to the next carrier.

c. Send a SIP or ENUM query to the DIA Registry.

(2) SP A has opted for option C above, and sends a SIP or ENUM query to the DIA Registry with +31789 as the destination TN. The Registry performs an edge query and determines the TN is reachable and



returns the SIP route to the DIA interconnect hub. Note if the TN was not reachable, the Registry will return a ‘not found’ response and SP A will route advance the call to the next choice route.

(3) SP A sends the call to the DIA Interconnect Hub via the SIP trunk.

(4) On receiving the call the Interconnect Hub performs a query against the Registry. This query uses the information received in the SIP signalling (A address, B address, other signalling data eg codec) to perform a policy and routing look-‐up :-‐

a. The Registry will look-‐up both the A TN (+31123) and the B TN (+31789) and determine that these are valid TNs belonging to SP A and SP C respectively.

b. The Registry checks that SP A and SP C are allowed to exchange traffic via policy (in this case that they have not chosen to opt-‐out).

c. The Registry returns the route to the SIP trunk to SP C.

(5) The Interconnect Hub forwards the call to SP C via the SIP trunk. All subsequent signalling will be proxied via the Interconnect Hub. A CDR is created for the call and updated in real-‐time as the call progresses.

(6) Assuming the call is successful, the RTP media will be proxied via the Interconnect Hub media relays.

4.1.2 DNA – Performance Targets. As the DNA product is aimed at national traffic, it is important to consider end to end call quality and performance.

Performance metrics for the DIA network are provided in section 3.1 above.

Table 4-‐1 below suggests some target metrics and methods for the end to end call, which therefore require participation by the Member networks.

Note these are suggestions it will be up to the GCXS Members to determine whether these metrics are desirable or practically achievable within their network scenarios.

End-‐to –End Quality Parameter Value Comment

One-‐Way Latency (Mouth to Ear) Maximum 150ms

Average One Way Jitter Less than 30ms

End to End Packet Loss Less than 1%

Speech Codec Used G.711 A law The DIA Exchange will also support HD voice traffic, however no transcoding will be supported, and therefore this will be dependent on the capabilities of the SP end-‐devices.

Post Dial Delay Less than 300ms Time between Originating end-‐user completing dialling and ringtone or treatment (tone or

Maurice Vonk� 2-9-13 15:27Deleted: Table 4-‐1


announcement) being heard.

Availability 99.85% Availability of the end-‐to-‐end network measured on a monthly basis.

Network Efficiency Ratio (NER) 99% of calls. Percentage of SIP Invites which received a valid network response removing user impact (eg does not include User Busy or No Answer calls, incorrect/incomplete number dialled etc.).

CLI transparency 100% Percentage of calls providing the correct A network number to the B network. User presentation privacy will be upheld.

Tones and Announcements Dutch National standard

All calls are provided with Dutch PSTN standard tones and announcements.

Fax/Model Support Method G711 pass-‐thru T.38 may be used, but will be negotiated between end-‐devices. Members should support G.711 pass thru as default.

Table 4-‐1 – End to End Quality Metrics – DNA

4.1.3 Settlement for DNA traffic. GCXS will provide settlement services for traffic exchanged between Members across the DNA product.

This allows the Members to avoid the cost of implementing and administering multiple contracts and commercial arrangements with the other Members.

If required, Members can choose a settlement free relationship.

GCXS will provide reports and itemised billing which show usage and performance of Member traffic.


4.2 DUTCH PRIVATE ALLIANCE (DPA).

The Dutch Private Alliance, allows a Service Provider to create their own private interconnect Community where the owning SP determines the policy, routing and settlement rules.

Figure 4-‐2 below shows an example of a private alliance.

Federation 1- Dutch National

Alliance

On-NetDutchTNs

SP D

Federation 2- SP D

Private Alliance

PrivateFed

Routing

A

B

C

KPN

SP D TN+31123456

KPN TN+31765432

OriginatingCustomers

SP D TN+31123456

SIP TrunksSIP

Trunks

Figure 4-‐2 – Dutch Private Alliance Example.

The Dutch National Alliance (DNA) product, only allows calls to be exchanged between on-‐net Dutch telephone numbers.

Service Provider D would also like to sell termination to KPN numbers via SP Ds existing direct interconnect to KPN.

In order to do this, SP D can create a Private Alliance where SP D is the only terminator. SP D can add either existing originators (eg SP B who now belongs to the DNA product and SP Ds Private Alliance), and invite new Members (SP C) to interconnect just to the SP D private alliance.

By default, the DPA product does not support sophisticated routing (any call from SP B or SP C would be directed to SP D), or settlement (SP D will be responsible for contract and commercials with SP B and C). If required GCXS can provide a custom service which includes routing and settlement, once we understand SPs requirements in these areas.



4.3 INTERNATIONAL OUTBOUND AND INBOUND.

Via our partner XConnect, GCXS can offer Dutch Interconnect Alliance customers an International Outbound service which terminates traffic via XConnects International Global Alliance network.

This product uses XConnect’s direct peering routes to SPs across the world combined with the XC Registry to provide high quality, low cost VoIP termination.

The International outbound product is sold on a traditional per minute per destination basis using a rate sheet which will be provided to customers and updated from time to time.

Conversely, GCXS would like to terminate traffic from XConnect International customers via the DIA network. This may be to Dutch customers own TNs only, or other national or international transit routes.

5 INTERCONNECTING TO DIA.

The following section describes the general technical requirements for an SP wishing to interconnect to the DIA service.

As part of the service implementation, GCXS will work with customers to exchange interconnect design information, and conduct interoperability testing.

Connecting to DIA requires the following:-‐

• Interconnecting at the IP level to the DIA IP network.

o Interconnect may be via Private IP or via the Public Internet.

o SPs may interconnect at two different DIA sites for increased resilience.

• Interconnecting at the SIP and RTP media layers to the DIA Interconnect Hub

o SPs need to establish at least one SIP trunk from their NGN network to the DIA interconnect hub but possibly one SIP trunk per product. Generally this would be from the SP SBC (or other border element).

o The SPs can establish multiple SIP trunks from diverse border elements if required for resilience.

o SPs need to authorise RTP media to be sent from the DIA RTP source addresses. (eg within the SP firewall or SBC).

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

• Product Selection.

o The DIA SP will indicate (and sign the appropriate contracts) which products they wish to belong to.

• Establish Outgoing Routing Scheme


SPs will need to determine how to route outgoing national traffic via DIA instead of routing via the PSTN. A list of DIA members will be available via the DIA portal. The SP has three options for outgoing routing:-‐

(1) Internal Routing with Internal NP data – Where the SP has a sufficiently capable internal routing engine, the SP can use the Dutch NP database to support NP corrected routing to route calls via the DIA Exchange service to those on-‐net Member TNs only.

(2) Send ‘All Calls’ – the Originating SP can send all calls (or specific known ranges) to the DIA Hub. Calls which cannot be terminated will be rejected by DIA with the appropriate SIP response, and the SP can ‘route advance’ the call to their second choice carrier.

(3) DIA Registry Edge Query – the Originating SP can do an ‘All Call Query’ (ACQ) against the DIA Registry, the Registry will return the DIA Exchange SIP address if the call can be terminated via the DIA service. The query may be SIP Redirect or ENUM. If the call cannot be terminated via the DIA service a suitable ‘not allowed’ response will be returned and the Originating SP can ‘route advance’ the call to their second choice carrier. This method has the following advantages :

The SP’s internal routing system is less complex, as it doesn’t have to integrate NP data.

An All Call Query uses less switch resources than sending all SIP calls to the DIA Exchange hub.

As new SPs are added to the DIA Exchange product, the SP does not have to modify their outgoing routing plan.

• Billing and Reconciliation – Depending on the product, the SP needs to consider any impacts on internal billing and reconciliation systems for the end-‐to-‐end traffic.

o Customers will be able to access the DIA portal to get reports on traffic usage and performance (and CDR detail) to understand the volumes and flows of traffic with other Members.


6 OPERATIONAL SUPPORT.

In addition to a highly resilient design and exacting performance criteria, the DIA service will also be supported on a 24x7x365 basis to monitor and repair the DIA platform , and respond to customer trouble tickets utilizing the proven GCXS customer service desk.

6.1.1 Network Monitoring and Repair. The DIA service will be monitored on a 24x7x365 basis, via alarms and traps generated by the DIA platform components, and traffic level monitoring and alarms (eg ASRs, PDD, call attempts etc).

DIA includes a 24x7x365 Helpdesk available to report and respond to customer faults and inquiries following standard GCXS support and escalation processes.

An operational manual describing contact points, instructions on raising trouble tickets, escalation process and target response times will be provided to SPs at hand-‐over time.

6.1.2 Interconnect Implementation. New DIA customers will be implemented via an Interconnect Implementation process managed by GCXS.

The Interconnect process includes interconnect design, configuration documentation, interconnect testing and CDR/billing validation (between the SP and the DIA service).

7 COMMERCIAL.

7.1 CONTRACTUAL MODEL.

SPs wishing to sign up to the DIA service will sign a contract with GCXS which includes the following:

• GCXS Master Service Agreement (MSA)

o The GCXS MSA covers the generic terms and conditions applicable to all GCXS services.

• Service Schedule(s) to MSA

o SPs will sign a schedule for each service (DNA, DPA, others) they wish to join. The schedule will cover the terms and conditions, qualifying criteria and obligations, and inter-‐SP settlement regime applicable to the particular service.

This model allows SPs to exchange traffic, without having to sign individual contracts with each DIA member.

7.2 DIA PRICING.

DIA pricing covers the connectivity and interconnection of calls across the DIA platform as described above, and is paid by the SP to GCXS. A minimum term of 12 months applies.


DIA pricing is both Service based & Usage (minutes) based. SPs can choose to join one or more Alliances / Products & will pay for the number of minutes consumed under the specific Alliance / Product.

DNA pricing is available on request.

7.3 ALLIANCE INTER SP SETTLEMENT.

SPs will sign an Alliance schedule for each Alliance they wish to join (assuming they are eligible).

The Alliance schedule outlines the terms and conditions, and obligations associated with Alliance membership. The Alliance schedule also describes the settlement regime used between Member SPs for interconnect traffic.

This model allows the Alliance members to exchange traffic without having to separately contract with each new Alliance member.

The Dutch National Alliance (DNA) offers 2 main settlement models between SPs: a traditional Settled/Termination Rate model (DNA Settled) & a Bill & Keep/Settlement Free one (DNA Bill & Keep).

The DPA settlement models are left to the free choice of each DPA SP member to agree how they settled with their chosen DPA SP partners.

7.3.1 Dutch National Alliance (DNA) – Settled SPs subscribing to this Alliance will need to settle for the traffic exchanged over the DIA service.

Terminating Rates and terms for such traffic are left to the subscribing SPs to agree, but are expected to mirror the Dutch Regulated termination rates.

Settlement service among DNA members are provided by GCXS, or SPs can settle for traffic charges directly among themselves, if so they wish.,

The DIA Service will provide a monthly traffic & minutes report (available via the portal). The report will be provided to each SP (for their specific originating and terminating traffic).

The report will detail all outbound and inbound calls for each Alliance Member SP and will contain at least the following information:-‐

Outbound Call Report

Terminating SP Call Attempts

Successful Calls

ASR Minutes

SP Name

SP Name

Inbound Call Report


Originating SP Call Attempts

Successful Calls

ASR Minutes

SP Name

SP Name

7.3.2 DNA -‐ Bill and Keep. The Bill and Keep/Settlement Free Alliance, will utilize a ‘bill and keep’ settlement regime, where there is no inter SP settlement for traffic. SPs can get the same set of reports as described in section 7.3.1 if they wish to check on the ‘balance’ of traffic between their Alliance partners.

SPs shall keep balanced bidirectional traffic with each other B&K Alliance members

GCXS - Dutch Interconnect Alliance - Product … - Dutch...•...

Documents

Transcript of GCXS - Dutch Interconnect Alliance - Product … - Dutch...•...