140 likes | 271 Views
EVD0 Data Roaming: the PRL. For the June 05 IRT Meeting Richard Schwartfeger. Issues. What do I need from our roaming partner Relationship between associations, subnets and acquisition table Should I have 1 or more acquisition records Subnets
E N D
EVD0 Data Roaming: the PRL For the June 05 IRT Meeting Richard Schwartfeger Lucent Technologies – ProprietaryUse pursuant to company instruction
Issues • What do I need from our roaming partner • Relationship between associations, subnets and acquisition table • Should I have 1 or more acquisition records • Subnets • Tried roaming between our commercial and model switches • Tools Lucent Technologies – ProprietaryUse pursuant to company instruction
What do I need from our roaming partner • EVDO parameters • EVDO Bands and Channels • Associations • Subnet ID • Regular updates • Roaming Technical Data Sheet Lucent Technologies – ProprietaryUse pursuant to company instruction
Roaming Technical data sheet • The TDS needs extra fields added to cover the information required for EVDO PRL production. • New fields • Band class • Channel numbers • SubnetID • Associations – not required until PN and PDSN are used. If they are on the same line then they are associated Lucent Technologies – ProprietaryUse pursuant to company instruction
Relationship between associations, subnets and acquisition table • How is an EVDO channel selected? • Highest priority 1x acquired • Checks for an association – yes • Gets the association tag number • Finds the EVDO system Table entry from the association tag in the same GEO region • Gets the acquisition number • Searches for a channel from the acquisition record • Once found checks the subnet ID matches • Happy surfing Lucent Technologies – ProprietaryUse pursuant to company instruction
Should I have 1 or more acquisition records • Once Data roaming with several partners the number of channels to search could be quiet large. • With 2 or more index’s • does this make the acquisition faster i.e. less channels to search • If 2 or more roaming partners in the same location, this can filter out some channels or should this be left to the subnet ID. Lucent Technologies – ProprietaryUse pursuant to company instruction
Acquisition Table • Example Lucent Technologies – ProprietaryUse pursuant to company instruction
Subnets • What are subnet’s • Should they be unique • When do I use them instead of “/0” • Why are TNZ’s unlikely to be unique • What makes them unique Lucent Technologies – ProprietaryUse pursuant to company instruction
SubnetID Telecom NZ. • It has taken some time to understand how our sector ID’s have been set. • Current SectorID setup: • SectorID 0x0000000000000000000ac8020500f901 • SubnetMask 104 • The 24 LSB, is the Cell and sector number. 00f901 = cell 249 sector 1 • The 104 MSB, is the RNC IP address. ac80205 = 10.200.2.5 • Makes the subnetID 0:0:0:0:a:c802:500:0/104 • This clearly means that they will be unique within the Telecom network, but extremely unlikely in the global network. Lucent Technologies – ProprietaryUse pursuant to company instruction
SubnetID Telecom NZ - continued • While there are currently no other EVDO networks in NZ we are able to use the wild card “/0”. If another network provider was to come along then we may need to look at expanding our PRL entries for EVDO to 1 for each RNC. • There are recommendations on how to over come this by adding SID/NID or MCC/MNC. • I have requested our Solutions team to look into TNZ’s sector ID, to define any changes to improve the TNZ EVDO network. Lucent Technologies – ProprietaryUse pursuant to company instruction
System Table example Lucent Technologies – ProprietaryUse pursuant to company instruction
Tried roaming between our commercial and model switches • Set up a PRL with Model as highest priority so that it should of selected the model network over the commercial network, it wouldn’t pick the model. • Due to time constraints I was able to follow up and had to revert back to one with the commercial set to negative. • I tried this one: I suspect that I need to have a subnetID as it found the commercial first with both on the same channel. Lucent Technologies – ProprietaryUse pursuant to company instruction
Tools • PRL editor – to make up the PRL’s • Kait – to see what the overhead messages contained. • Testing in our network is ok, shortly we will be testing our first EVDO partner. Lucent Technologies – ProprietaryUse pursuant to company instruction
Any Questions? • My PRL is ready and waiting for testing with our first EVDO roaming partner. • I can be contacted via email for more information • schwartfeger@lucent.com • Thank You • Richard Lucent Technologies – ProprietaryUse pursuant to company instruction