20070614 VSWG Tampa Face to Face Minutes
From CDGWiki
Meeting held at the Renaissance International Plaza, Tampa, Florida
All presentations given during the VSWG can be found on the CDG website (login to CDG site may be required).
Contents |
[edit] Discussion Topics
[edit] Opening
Welcome and Introductions by Kyoko Uchida, co lead from KDDI.
[edit] Plus Code Dialing
- Daniel Salek asked for final approval for plus code dialing document # 145
. The version presented at the meeting (0.5) reflects the last suggested changes with an addition of an MMS definition.
- The group requested two weeks to review the changes.
- Discussion:
- Bill Dahnke: He needs document approval to push the subject higher in the industry to help implementation
- SKT: already delivered previous document to Vendor
- SKT (CY): Concern about implementation timeframes. Will different implementation timeframes lead to customer confusion? (some countries with +code and some without) Answer No, we are glad if the subject start moving toward implementation.
- Final comments by Libby: Use your CRM for testing and questions about implementation/ documents.
[edit] ESN/MEID
- Daniel requested carriers read the MEID document
- Background: Some big US operators already started sell MEID phones in their markets. They are roaming already.
- Daniel explained the different phone identifiers: MEID ESN, RUIM, and Pseudo ESN (pESN)
- Migration tips:
- All non-RUIM MEID phones will send Pseudo ESN in the ESN field
- pESN will not collide with regular ESN
- 50% chance of a duplicate pESN when 5000 MEID phones in the same network.
- Potential Impact to EVDO for both RUIM and standard phones
- Actions for NON-RUIM carriers
- As pESN will not be unique,
- Ensure HLR/AC & VLR will not check the uniqueness of ESN
- Check whether OTASP (if used) requires a unique handset identifier
- A potential example would be as an index to a file of A-keys provided from the handset vendor, to associate with a subscription
- Add support for C.S0066 and possibly X.S0033
- Ensure that network will NOT reject call attempt from MEID handset with SCM bit 4 = “1”.
- To avoid PLCM collision caused by duplicated pESN in MEID handsets,
- Upgrade network to support C.S0072.
- Update background management tools to use MEID or IMSI (instead of ESN) as the ID for handset management.
- As pESN will not be unique,
- Actions for RUIM carriers
- Choice of EUIMID format
- As pUIMID will not be unique,
- Ensure HLR/AuC & VLR will not check the uniqueness of ESN
- Check whether OTASP (if used) requires a unique card identifier
- A potential example would be as an index to a file of A-keys provided from the card vendor, to associate with a subscription
- An alternative in this case would be to generate the A-key dynamically during the OTASP session
- Ensure network will NOT reject call attempt from MEID handset with SCM bit 4 = “1”.
- Upgrade the network to support C.S0072 to avoid PLCM collisions. However, “pUIMID provisioned R-UIM card in ESN phone” will still be at risk of PLCM collision.
- To avoid PLCM collision caused by duplicated pUIMID and pESN,
- C.S0072 MEID-equipped handsets are recommended.
- Upgrade network to support C.S0072.
- Update the background management tools to start to use EUIMID (instead of UIMID) as the ID for card management.
- Discussion:
- Carrier inquiry: I did nothing on MEID. Will this affect me? Answer: Yes. Read documents 137/158 to find about potential problems.
- Will it affect my billing? Answer from Cibernet: pESN will be present in all records.
- Carrier inquiry: Is there a date to remove the ESN? Answer: no, will be replaced gradually.
[edit] Prepaid
- A survey confirmed interest in prepaid roaming and confirmed IS 826 is the preferred path for this. Very few people are doing prepaid roaming so there isn’t a large amount of data to draw upon.
- Next Steps:
- White paper targeted for next IRT.
- Those that have implemented prepaid roaming should share traces and information with the team to assist in developing the white paper.
- Discussion:
- How to get the prepaid roaming platform system into the terminating call for charging purposes (prepaid is generally CPP and normally is not charged to the mobile customer). The proposal is to change the HLR code so only produce triggers when the subscribers are outside their national networks. Verisign proposed a different way.
- Skylink: How do we agree to announcements between operators. Languages, types, etc? Proposal: To use Standard Tones.
- Skylink comment that they use SMS to notify customers their limits and events as credit shortage, etc.
- Recharge ( Top UP)
- Consensus between operators that this is not directly a roaming issue, but is a concern to develop some way because without recharge the service will not happen. Is a financial subject.
- Daniel Presented some open issues: without answers:
- Impacts on existing roaming billing processes
- Dial plan differences
- Lots of tables in the SCP?
- True serving network
- Now voice and SMS need to know this for rating at the home network
- Syniverse: asked when we will define how to implement his.
- Daniel: Defined next steps: White paper to be presented in the Next IRT in September.
- Telus will provider some test plans for this (from their domestic implementation)
- CAMEL Implementations (Vodafone was suppose to provide some input but was not in the present in the meeting)
[edit] SMS MO Dial Plan
- Question about SMS MO dialing format: Today is like they were in the home country network. Any possible change? Should we do something? No answers from the group.
[edit] Exchanging billing specifications
- Mayuko Sawada: Objective to update the current Doc #59. (Billing Specification, 2004)
- KDDI proposed 15 questions to be answered in the new TDS, and proposed to implement a survey to answer them by the operators.
- Discussion:
- Sprint mentioned that this will be another TDS to keep and maintain. Suggestions to add this info into another place. (Standard TDS?)
- Bell Canada: Please don’t repeat info already present in another documents.
- SKT: They do not have many billing issues due to these questions.
- KDDI: Propose to modify the survey so we can ask for inputs from the carriers about how to proceed with this subject.
- Telus: Suggested we place this billing information in the standard TDS ONLY if it changes frequently.
[edit] Trouble Resolution Minimum Requirements
- (Daigo Sawamoto KDDI) Objective: To update Document #87
- The proposal is to have a minimum set of required data to provide with a trouble ticket. Document 87 provides information to share and the proposal is to provide the following parameters:
- MDN/MIN/IRM + ESN
- Detected MSCID (if available)
- Problem description
- Detected Location
- Detected Time
- Home Carrier Status
- Discussion:
- Pelephone: MSCID is not transparent for the home carrier. RSP are in the middle and sometimes don’t provide the “real MSCID”. Daigo suggested changing mandatory to “if available”.
- Pelephone also suggested that this information is not enough to fix the problems, and they normally need more interaction from the carrier.
- Another suggestion was to add some information for Packet data troubles. It was agreed that this was a subject to analyze in the PaDirt working group.
- KDDI will update the document and re-send it to the group.
[edit] Service Level Agreements
- Kyoko Uchida – Objective is to agree upon a level of operational service between roaming partners.
- The SLA will be an annex to the Document #44.
- Kyoko started to discuss the changes from the last SLA version.
- Section B: Pelephone asked about definition on Network Availability. After several comments, it was agreed to keep the number in 99.95 %
- VZW requested a definition on the same subject. Kyoko will provide some definition.
- Section C: Carriers need to provide feedback about the events described in this section.
- Section F: Roaming agreements will take precedence over the SLA.
- Discussion about day allowed to load/delete IRM (15 or 30 days) and also in section G on days to correct failure on section F. The last one was voted to be 3 business days.
- Action: Kyoko to review clauses that are duplicated in Document #44 and verify that there is no conflict.
[edit] Cibernet Report
- Robin Thomas provided a presentation about Cibernet-Mach new organization
- Also announced the re-launch of CEC (CIBER Executive Committee) and the new CIBER projects. (Manuals, Ciber records enhancements).
- Comments about the pricing were dismissed and to be treated in an individual basis due to the anti trust legislation.
- KDDI suggested Cibernet to provide training to new operators’ right up front when they sign up for CIBER.
[edit] CDMA Roaming Information Exchange Tool (C-RIET)
- Libby Mackay presented the Tool to the VSWG members.
- Explained how to use it, the new changes (carrier profile and security) and launched the Beta testing until June 27. If no other major issues are uncovered the tool will commercially launch in July.
- Andrew Hunter provided a suggestion to the group that the TDS can be preloaded in the PRL tools, so Predict can simulate for the specific carriers based on the CRIET authorization definitions.
[edit] Roaming Test Plan
- VeriSign has agreed to sponsor this project and lead a task force to develop and approve a standard testing document for Voice. Ann Munno will manage the task force to review the existing documents and provide a new version.
- She will establish a conference call to define the Goals, objectives, etc. to be presented to the plenary.
[edit] Closing
- Please provide feedback on topics for the next IRT
- Dual Conference calls will be kept for some time more. They seem to improve the participation by al least 50 %
- Libby acknowledged the companies that routinely participate in the conference calls: KDDI, VZW, Sprint and Verisign.
- Reminder to fill out the surveys (even old ones)
| Main | About | Work Items | Whiteboard | Meetings | Documents |
