EVD0 Data Roaming: the PRL

0
0
1603 days ago, 545 views
PowerPoint PPT Presentation

Presentation Transcript

Slide 1

EVD0 Data Roaming: the PRL For the June 05 IRT Meeting Richard Schwartfeger Lucent Technologies – Proprietary Use in accordance with organization guideline

Slide 2

Issues What do I require from our meandering accomplice Relationship between affiliations, subnets and procurement table Should I have at least 1 obtaining records Subnets Tried wandering between our business and model switches Tools Lucent Technologies – Proprietary Use as per organization direction

Slide 3

What do I require from our meandering accomplice EVDO parameters EVDO Bands and Channels Associations Subnet ID Regular overhauls Roaming Technical Data Sheet Lucent Technologies – Proprietary Use in accordance with organization direction

Slide 4

Roaming Technical information sheet The TDS needs additional fields added to cover the data required for EVDO PRL generation. New fields Band class Channel numbers SubnetID Associations – not required until PN and PDSN are utilized. On the off chance that they are on a similar line then they are related Lucent Technologies – Proprietary Use according to organization direction

Slide 5

Relationship between affiliations, subnets and procurement table How is an EVDO channel chose? Most noteworthy need 1x procured Checks for an affiliation – yes Gets the affiliation label number Finds the EVDO framework Table section from the affiliation tag in the same GEO locale Gets the securing number Searches for a channel from the obtaining record Once discovered checks the subnet ID matches Happy surfing Lucent Technologies – Proprietary Use according to organization guideline

Slide 6

Should I have at least 1 securing records Once Data meandering with a few accomplices the quantity of channels to hunt could be calm expansive. With at least 2 record's does this make the procurement quicker i.e. less channels to seek If at least 2 wandering accomplices in a similar area, this can sift through a few channels or ought to this be left to the subnet ID. Lucent Technologies – Proprietary Use according to organization direction

Slide 7

Acquisition Table Example Lucent Technologies – Proprietary Use compliant with organization guideline

Slide 8

Subnets What are subnet's Should they be interesting When do I utilize them rather than "/0" Why are TNZ's probably not going to be one of a kind What makes them exceptional Lucent Technologies – Proprietary Use in accordance with organization guideline

Slide 9

SubnetID Telecom NZ. It has required some investment to see how our segment ID's have been set. Current SectorID setup: SectorID 0x0000000000000000000ac8020500f901 SubnetMask 104 The 24 LSB, is the Cell and area number. 00f901 = cell 249 segment 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 unmistakably implies they will be one of a kind inside the Telecom organize, yet to a great degree impossible in the worldwide system. Lucent Technologies – Proprietary Use according to organization direction

Slide 10

SubnetID Telecom NZ - proceeded While there are as of now no other EVDO arranges in NZ we can utilize the special case "/0". On the off chance that another system supplier was to tag along then we may need to take a gander at extending our PRL sections for EVDO to 1 for each RNC. There are suggestions on the best way to over come this by including SID/NID or MCC/MNC. I have asked for our Solutions group to investigate TNZ's division ID, to characterize any progressions to enhance the TNZ EVDO arrange. Lucent Technologies – Proprietary Use according to organization direction

Slide 11

System Table illustration Lucent Technologies – Proprietary Use compliant with organization guideline

Slide 12

Tried wandering between our business and model switches Set up a PRL with Model as most noteworthy need so it ought to of chose the model system over the business arrange, it wouldn't pick the model. Because of time requirements I could development and needed to return to one with the business set to negative. I attempted this one: I presume that I need a subnetID as it found the business first with both on a similar channel. Lucent Technologies – Proprietary Use in accordance with organization direction

Slide 13

Tools PRL manager – to make up the PRL's Kait – to see what the overhead messages contained. Testing in our system is alright, in the blink of an eye we will test our first EVDO accomplice. Lucent Technologies – Proprietary Use compliant with organization direction

Slide 14

Any Questions? My PRL is prepared and sitting tight to test with our first EVDO meandering accomplice. I can be reached by means of email for more data schwartfeger@lucent.com Thank You Richard Lucent Technologies – Proprietary Use according to organization direction

SPONSORS