LBS Roaming Minutes of NA LBS Roaming Summit Sept 19 20
From CDGWiki
Contents |
[edit] Background:
There was a North American LBS roaming summit for the purpose of NA operators exchanging LBS deployment plans and defining roaming solutions.
[edit] Companies represented:
- Alltel
- Bell Mobility
- Qualcomm
- Iusacell
- Sprint
- Telus
- US Cellular
- Verizon Wireless
[edit] Proceedings:
Qualcomm first provided an overview of both control plane and user plane LBS architectures. The primary purpose was to ensure that attendees without LBS expertise would have a basic understanding. LBS roaming issues were highlighted. Qualcomm also provided an overview of packet data roaming issues and how they relate to LBS roaming. Operators presented an overview on their LBS service architecture and views on LBS roaming.
This was followed by interactive discussion about possible solutions to open LBS roaming issues.
[edit] Overview of Technical Issues Identified:
Below is a high-level summary of the technical issues identified during the meeting.
Control Plane:
- No significant issues identified
- Ideally the existing IS-881 CP deployments can simply interconnect their MPCs via the IS-881 standardized L3 interface. However, all the relevant CP MPCs are based on OPWV and OPWV is pushing a modified version of OMA’s RLP as the means to interconnect. A modified RLP would suffice, but there is a need to “standardize” the inter-MPC L3 protocol (bring in Openwave into discussion) – the industry should agree on one open interface.
- Need to ensure the transport (IP) for the L3 link is a well-managed service (involve CRX discussion?)
- Need to ensure actual MSCID is available in cases where a 3rd party RSP is being used (bring RSPs into discussion)
User Plane:
- Non-Trusted
- No significant issues identified
- Need to develop a consistent, documented H-MPC/S-MPC interface
- Trusted
- Some work needs to be done here
- Many solutions were discussed, but two possible solutions were identified as a reduced subset
- PDE Interconnection:
- Temporal sharing of BSAs from the V-PDE to the H-PDE or via a 3rd party BSA sever
- IS-801 forwarding from the H-PDE to V-PDE or to a 3rd party PDE
- DNS resolution of SID/NID to direct MS to V-PDE
- H-DNS Option
- V-DNS Option
- Trusted/Non-Trusted Interworking
- Some work needs to be done here
- Non-Trusted to Trusted is best handled via the Non-Trusted approach
- Trusted to Non-Trusted is best handled via the PDE Interconnection Trusted Approach
[edit] Moving forward:
Continued discussion involving more operators and vendors on 11/28. Discussion via email and the Wiki until then.
