Peering Taskforce UpdateFinancial Clearing House (FCH) Peering Roaming Service Provider (RSP)Peering
Ted Bolerjack – SprintSara Schleutker – Qualcomm
Problem to Solve• Traditionally Financial Clearing House (FCH)
Services have been provided by one vendor • Now there are two providers which may force
carriers to participate in two programs – Separate process– Separate billing procedures
FCH SyniverseFCH MACH
DCHMACH
DCHTNS
(Verisign)
DCHSyniverse CRX
Aicent
CRXTNS
(VeriSign)
CRXSyniverse
CIBER
CIBERCIBER
Radius
RadiusRadius
ReportReport Report Report Report
Report ReportReport
Carrier A
Carrier B
Carrier C
Carrier D
Invoice
Invoice
Invoice
Invoice
Net Settlement through FCH
Net Settlement NOT available
Bilateral settlement required
Net Settlement through FCH
FCH Peering Task Force TimelineYear Month Action 2009 July KDDI presents need for FCH peering. Carriers voted item in for action
August Carrier requirements collected
September Carrier requirements reviewed and provided to FCH vendors
November FCH vendors present peering status. Outcome – no support for the project in 2010
2010 January IRT Co-Chairs send request letter to vendors listing carriers who are in support of the initiative
February FCH vendors respond to IRT with willingness to review project further
March Announcement of formal task force
April First task force meeting hosted by MACH – Tampa, FL
May IRT Co-chairs receive letter from vendors - continue to NOT support the project
June Carriers decide to continue with task force by writing peering agreement
September Document draft review
October Membership comments
2011 February Call to review open holes in document
April Final text added, request membership to approve
May Send final document to membership to approve and post
Document review• Open section 6B
Timeline to deploy: Notes from conference call 9/8/10• Assuming all of the technical considerations are worked out
between the two FCH’s, a timeline to deploy should be agreed to in order to set customer/carrier expectation.– Few carriers want to be the first to deploy with an unconnected/peered FCH. – By setting a time line to deploy, expectations are realistically set.
• Draft002 FCH Peering document on CDG wiki – https://wiki.cdg.org/wiki/FCH_Peering_Task_Force_Progress
Text to be added to section 6B Assuming a technical solution has already been
implemented between participating FCH Clearing House Vendors, such solution will be made available to the Party’s Member Carriers on an individual basis. The implementation of such service will complete within 30 days of the carrier’s requested starting date and coincide with the requesting carrier’s processing and settlement period.
Problem to Solve• An RSP is a vendor that facilitates voice/SMS
roaming by supplying various interconnection services between CDMA voice/SMS roaming partners.
• RSP’s have an existing peering relationship built on the backbone of SS7. – Confusion about what is covered– Different charging principles used by different providers– Instances where a carrier will not have access to certain
CDMA partners or regions
RSP Peering Task Force Timeline
Year Month Action 2010 July TNS presents a call to action to define RSP and put together a peering document for all RSPs. Team
has decided to focus on the completion of FCH peering before we further the work on RSP peering
2011 April Taskforce revisit on carrier need and desire to contribute to the work item.
Top Related