1 / 11

Ted Bolerjack – Sprint Sara Schleutker – Qualcomm

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.

alva
Télécharger la présentation

Ted Bolerjack – Sprint Sara Schleutker – Qualcomm

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Peering Taskforce UpdateFinancial Clearing House (FCH) Peering Roaming Service Provider (RSP)Peering Ted Bolerjack – Sprint Sara Schleutker – Qualcomm

  2. Financial Clearing House Peering Taskforce Update

  3. 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

  4. Carrier C Carrier A Invoice Invoice Net Settlement NOT available Bilateral settlement required Net Settlement through FCH Net Settlement through FCH Carrier B Carrier D FCH MACH FCH Syniverse Invoice Invoice Report Report Report Report Report Report Report Report DCH MACH DCH TNS (Verisign) DCH Syniverse CRX Aicent CRX TNS (VeriSign) CRX Syniverse CIBER CIBER Radius Radius CIBER Radius

  5. FCH Peering Task Force Timeline

  6. 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

  7. 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.

  8. Roaming Service Provider (RSP) Peering Taskforce Update

  9. 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

  10. RSP Peering Task Force Timeline

More Related