Peering Taskforce Update Financial Clearing House (FCH) Peering Roaming Service Provider (RSP)Peering Ted Bolerjack – Sprint Sara Schleutker – Qualcomm

Financial Clearing House Peering Taskforce Update

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 DCH MACH DCH TNS (Verisign) DCH Syniverse CRX Aicent CRX TNS (VeriSign) CRX Syniverse CIBER Radius Report Carrier A Carrier B Carrier C Carrier D Invoice Net Settlement through FCH Net Settlement NOT available Bilateral settlement required Net Settlement through FCH

FCH Peering Task Force Timeline YearMonthAction 2009JulyKDDI presents need for FCH peering. Carriers voted item in for action AugustCarrier requirements collected SeptemberCarrier requirements reviewed and provided to FCH vendors NovemberFCH vendors present peering status. Outcome – no support for the project in JanuaryIRT Co-Chairs send request letter to vendors listing carriers who are in support of the initiative FebruaryFCH vendors respond to IRT with willingness to review project further MarchAnnouncement of formal task force AprilFirst task force meeting hosted by MACH – Tampa, FL MayIRT Co-chairs receive letter from vendors - continue to NOT support the project June Carriers decide to continue with task force by writing peering agreement SeptemberDocument draft review OctoberMembership comments 2011FebruaryCall to review open holes in document AprilFinal text added, request membership to approve MaySend 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 –

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.

Roaming Service Provider (RSP) Peering Taskforce Update

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 YearMonthAction 2010JulyTNS 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 2011AprilTaskforce revisit on carrier need and desire to contribute to the work item.