Recipe for PD Roaming
From CDGWiki
[edit] Recipe for Packet Data Roaming
- There is a lot of practical experience w/ PD roaming
- Need for “recipe” for PD roaming
- Many supporting informational documents
- New operators asking “What do I do?”
- Provide steps and timelines
- This work will be captured in future reference document
[edit] Tampa Meeting Brainstorming
- Get network ready: evaluate status; look @ min. requirements document #147;
- BGP side – (1) multiple ANSs (which?), (2) consultants – no ASN – just a T1 to ISP – no BGP AS
- Strongly recommend talking to CRX prior to roaming partners
- Look at billing development as early as possible
- Recommend reviewing #147: everything worded appropriately?
- Different requirements mean different implementations; operators have different requirement
- Understanding timers important (state dependent)
- Manage organizational requirements early; aligning resources difficult
- Don’t overstate your capabilities; don’t lose credibility over concern over losing roaming partner
- Resource challenges are more difficult in small operators
- Meet with your CRM early (carrier relations manager)-first step!
- Need to understand process and expected timelines
- Inbound vs. outbound? Decide a strategy
- Establish CRX – project manager w/ CRX; project management document;
W/ operator – working w/ engineering and not project management; don’t get estimates on deliverable;
- Any operators : Observe standards!!!
- Devices ready?: Devices need to be ready to roam; may not be straightforward; early device testing;
- Need to evaluate products/applications while roaming
- Voice available? “Tough” if not there for 1x;
- Adding EV-DO to 1x data more straightforward; device component challenging; requires a new project – surprised by device responses
- Determine what is served: SIP, L2TP, MIP? Devices?
- Steps:
- Preparation : exchange TDS, discuss, etc.
- Base architecture (multiple roaming)
- CRX survey (exchanging BGP info, etc.) – delay on hardward
- CRX connectivity (2 weeks – 6 months)
- AAA connectivity via CRX (1 day – 3 months)
- Incompatible attributes can slow things down
- PRL development (2 weeks – 3 months)
- Session timers: timeouts
- Revenue assurance test (moving forward: see revenue flow; can speed things up) : need to sign off on this
