20070321 VSWG Macau Face to Face Minutes

From CDGWiki

Meeting held at the Landmark Hotel, Macau China

All presentations given during the VSWG can be found on the CDG website (login to CDG site may be required).

[edit] Participants

The following companies attended the meeting:

[edit] Discussion Topics

[edit] Opening

Question: what you want to obtain from the meeting today (VSWG) Answers: Interstandard, Networking +code, quality, learning-share experiences, negotiate agreements, help to solve problems (vendors) and learn about issues and requirements, Mail box deposit.

[edit] VSWG 2006 #1 Voice Priority - Calling Line Identity and VSWG 2006 #2 Voice Priority - Voice mail

VSWG work is done for CLI and VM except for tracking which will likely not be done until after an on line tool is created.

VeriSign and Syniverse mentioned they both can or will support the recommendations in these papers.

Modification by RSP of SMS VMN Call-Back Number may be an easy path to "one-touch" Voicemail Access for those operators who use SMS VMN as their notification method.

[edit] VSWG 2006 #3 Voice Priority - Network-Based + Code Dialing

An industry overview chart can be found on the CDG website. It includes carrier and vendor reports on plus code dialing availability. Update: TNZ has now implemented plus code dialing.

Action: Vendors and carriers should respond to the surveys with plus code dialing status.

[edit] Business Case

What information can help build the business case for Plus code dialing?
- As a home operator
  - What features equal actual dollars? Consider adding minutes for one more call per roamer per trip to the justification.
  - Another suggestion is a 20% reduction in calls (= to XX dollars) to customer care because subs now know how to make these ILD roaming calls.
  - What mark ups can be applied? More calls while roaming now that they have ease of use with plus code.
  - Number of roaming calls go up because subs can use their same phone book to place calls.
  - Reduced costs for collateral, marketing materials, brochures, help information.

As a serve operator
- More international calls by inbound roamers because the sub can dial more easily.
- Take a look at the “Unsuccessful call” CDRs to estimate the scope of how many calls are not completed because the sub doesn’t know how to dial.
- Review the number of subs registered in the serving network but are not making any outbound calls. This number could be used to measure what percentage of revenue is being lost by these subs not calling.
- Need to compete with GSM by providing similar features.

[edit] Requirements Document

Document 145 – A detailed requirements doc is available for review.
- Currently v0.3
- Available on the wiki and CDG website
  - Provides minimum and expanded requirements for network elements and MS vendors
  - A conference call was held the week before the Macau IRT. We reviewed a minimum set of requirements potential. Note the full set is still included and can be requested.
  - UPDATE: Korea will support + code dialing for inbound roamers in 3Q07. China Unicom indicated it will be difficult to have network based plus code due to differing network vendors.

Action plan:
- Daniel to update the document and get it out within 2 weeks (April 9)
- A call will be held the week of April 22 to review changes to document and make sure everyone understands the next steps.
- Carriers to do an engineering review and then freeze requirements. All comments are due June 9, 2007 and will be discussed at the June IRT for the final time.
- After final comments are incorporated we resend and then ask for top management to give requirements list to vendors.
- If it would be helpful for the CDG upper management to discuss the plus code implementation with any of the carriers’ upper management this can be arranged upon request.
- Carriers requested a list of handsets which support + code. Is anyone aware of such a list?
- Nokia agreed to include the + code dialing specs in GHRC document 90.

[edit] VSWG 2006 #5 Voice Priority - Coverage tool

Use C-RIET to post implementation information (detail requested by carriers in carrier only a while back.) Kyoko suggests we ask CRMs to collect this information from carriers along with the usual statistics. Will probably wait until the on line tool is functioning.
- Decided emails asking for access to files will go to the company POC.
- Enhancements need to be done by the developer - target date of 6-8 weeks
- Libby will have another conference call to explain tool once it is done for those that were not involved in the trial.
- Goal is to get the POC assigned for each company and for them to use the tool
- Start phase 2 design will then begin. Features suggested include the following:
  - On line statistics for implementations
  - Technical contacts on line
  - Operating hours
  - On line logging of trouble tickets for those companies that do not have a current on line tool

Mapping
- Vodafone: Offered to work on coverage maps for ISR. Libby indicated we will concentrate on CDMA to CDMA in this stage and then build from there.
- Kim Brophy confirmed Sprint will continue to lead the mapping effort.
- Need to get a common set of mapping format requirements
- Libby has requested Sprint hold a call on mapping requirements the week of May 14.
- Later consider a CMDA version of what Europa does for GSM World.

[edit] VSWG 2006 #7 Voice Priority - Roaming Quality

Service Level Agreement draft:
- Kyoko presented SLA document and process. She added monetary penalties for non
- It was suggested that ILD quality should be added to the SLA.

Carrier Panel:
- VZW presented their automated web based solution.
- SKT plans to treat incoming roamers better ( “like their own customers”)
- Skylink explained the reduction of failures once implementing a central trouble ticket solution.

Action plan:
- Kyoko to have a call to review the draft SLA by late April.
- Trouble shooting form doc 87 – KDDI engineers are looking into this now
  - Kyoko will talk to carriers who currently use automated trouble ticket systems to see how these work.
  - The team will come up with a basic set of voice roaming criteria which would serve as minimum criteria to work a voice ticket
- Billing TDS - Kyoko will discuss this internally and consider having this ready to discuss for June in Florida. Note there will not be much time for the VSWG so we need to do as much via conference call as possible.

[edit] VSWG 2007 #1 Voice Priority - Prepaid with WIN triggers

Determined the preferred solution will be the use of WIN triggers.
It was suggested we learn from the GSM approach. Skylink and Vodafone will provide some information about CAMEL.
SKT wants to provide a prepaid solution in 3 month. (Indonesia and Vietnam to work for implementation with SKT)
Action plan:
- Daniel to draft paper with help of sponsor, Maxim of Skylink.

[edit] VSWG 2006 SMS Priority - SMS

VSWG work is done. Contact Daniel Salek with requests for individual engineering assistance.
- SMS billing – home operator retail billing. Operator requirements (based on survey)
  - Operators wish to differentiate by the serve market
  - Would like to use the MC billing record – Switches don’t product a record/can’t produce. Typically bill subs using the messages on the MC
  - Would like to use RSP for network interconnection – End result is that there is not enough info in billing record i.e. can not see where the sub was
- Option – Signaling for Roaming SMS billing document:
  - Recommended approach – Transport Layer solution to minimize MC impacts
  - More work required in the network
  - More work for the RSPs
  - Reason for this approach
    - protect MC from doing a lot of work to change point code.
    - Fear of messing around for all operators who would need to adjust MC to translate sub location
- SMS Billing Survey – asked what fields possible in MC billing record
  - Responses – know that MC could support the point code
  - 5 out of 7 support SMS_OA, this is an IS41 parameter
  - Map Layer modification may be the easiest and cleanest way to add serving network identity
    - No network impact
    - Easier for RSPs
    - Equivalent changes required in home operator billing system
    - Currently included as an appendix in Signaling for Billing document. No formal CDG doc number applied as of yet. Will be in CDG format and added to DID
    - If your MC can include a suitable field, may be a quicker option
- VeriSign suggests that a couple carriers have asked to support the point code solution. This is available.
- Syniverse have implemented the MAP layer solution and are close to testing with a carrier.
- The fact that there are two solutions out there does not stop interoperability.
SMS Signaling Issues: Over length Message
- Problem: Different operators support different message lengths. Can cause message jamming or lost messages. Not defined in the standard.
- November IRT meting set time line for RSP support of Cause Code value 106 as March 21, 2007
- Status of RSPs
  - Syniverse – Developed solution but haven’t completed implementation. Haven’t received feedback from operators about the length. Need this to move forward.
  - VeriSign – Same as Syniverse
- Skylink suggest that they have 4 MSC vendors and all have different length limits. They have sent a request to Lucent and Huawei for cause code upgrade. This feature may take 6 months to implement.
Actions:
- Confirm MC action on receipt of this code
- (As Serve) inform RSP of your limit

[edit] Not prioritized

====Enhanced PRL report==== A list of carriers reporting the use of EPRL is posted on the CDG website. SkyLink also broadcasts their MCC MNC but was not included in the report.

ACTION: Carriers to respond with broadcast plans
Feedback from Carriers
- Most reported reason for not broadcasting assigned MCC MNC – not necessary for their network.
- Carriers MOST requested broadcast MCC MNC in the following countries:
  - USA
  - Canada, China, India
  - Brazil, Mexico
  - Japan, Korea, Peru

[edit] Document 44, Agreement Template Update

Opened for changes.
Need suggestions from operators to improve it.
Some operators’ suggestions on this:
- add SLA;
- escalation procedures;
- It will be better to add those subjects as an Annex.
Sara to have an agreement conference call on April 18

[edit] MEID

Document 137
Kyoko will follow up with carriers in Asia to find handsets to test with.
VSWG work is done except to possibly discuss exhaustion end of this year.

[edit] Standardized TDS

The team approved the “how to” document which supports the spreadsheet for document 81

Spreadsheet was approved in 4Q06.
Supporting Word document was approved by VSWG and the Plenary in Macau meeting.
Action: Carriers to convert to the new format by June 8, 2007
- CDG CRMs are available to assist you in filling out the standardized TDS or converting your old TDS to the new format

[edit] Document 119, Roaming Process document

This document helps carriers get an overall view of what it takes to implement and maintain international roaming from a process perspective.
Telus and MiPhone agreed to help with the billing and settlements sections.

[edit] Carrier Perspective

SMS Roaming and Services with GTT and RUIM – Maxim Alexandrov, Head of Service Systems Department, Skylink
- Why was the 450MHz choice made? This is from legacy regulatory allocations.
- Slide 22 have roughly 20+ locations where Skylink has a license
- The need for interconnection of all services is in high demand
- All CDMA networks in Russia are built with RUIMs.
- Skylink uses IMSI based numbering.
- All CDMA 450MHz networks are hybrid and currently operating (or migrating) to RUIM/True IMSI modes
- Interworking with other CDMA 450 networks is based on a combination of ITU standards and numbering schemes to maintain individuality.
- Routing GTT via PSTN providers ( MTT or Rostelecom)
- All carriers in Russia and former CIS have to be connected to the PSTNs in order for long distance voice interconnections, mandated by the government. This gives the possibility to also route all of the signaling messages.
- Only 16384 unique point codes for the PSTN+ISDN+PLMN network inside therefore point codes can be the same for different carriers.
- To translate this certain transactions have special parameters, translation type for each address of the transaction, called and calling
- This follow the IS-807 standard
- Shifting to IP
  - Skylink is not going to compete with GSM carriers on traditional voice services
  - The strategy is moving to IP and VAS
  - All carriers in the Skylink group have connected to the internet to provide high speed internet for EVDO data services. Shifting to IP now means that voice becomes and additional service.
  - The first step to get to the goal of an all IP network is to move all voice traffic.
  - The main concerns are: The cost of using a PSTN, SMS is highly sensitive to cost(average network send and receives billions of bytes per month), exchanging with the GSM world using SS7 (provide only one point for this interchange)
  - Requirements: Single centralized SMSC, IP based connectivity, redundancy, flexible, best of breed solution, easily deployed, scalability, wide range of features and protocols, ability for each property to have their own billing system.
  - How to move SS7 from TDM to IP? – SIGTRAN
  - SIGTRAN was adopted in 2006 as a basic standard for 3GPP2 MMD compliant networks
    - Highly reliable
    - Easily managed
    - GTT supporting
    - NP Independent
    - No issues when working with IMSI
    - Huge capacity 1.5-2 Mbps
    - Easy to secure, track, monitor, import messages payload

[edit] CIBER Update

As of Jan 16, 2007, CIBER 2.0 is no longer accepted except on a bilateral agreement basis
- Contact billing vendor for custom solution
Called place, called state, called country, serve place , serve country CAN NOT be blank
- No applicable when batch content is 0,4,6, 0r 6
- Not applicable to CIBER 2.0 records
Cross – Validation
Tips on Serve & call fields
- Called state of ZZ is the substitute if there is not a state code defined in table 31 for the called country
- Called country of SAT is used for satellite called – please use sparingly
Proposed changes
- Zero rated records (special features used “x”)
  - Require air charge and toll charge to be zeroes
  - Applicable to type 22 record only
  - Should be used in conjunction with special features used F (no air) and special features used J or K (no toll) where applicable
- Require Air Connect Time to be non-zero
- Proposed called state ZZ is not acceptable if called country is USA or CAN
  - This is still open for discussion
  - Carriers should voice their concerns to Cibernet

All presentations can be found on the CDG website in the IRT section under Macau.

[edit] Timelines

April
- April 9 – Daniel to have + code doc updated and to carriers
- April 16 – Comments due back to Kyoko on SLA draft
- April 18 – Sara to hold an agreement document call
- April 23 – Daniel to hold plus code call this week
- Late April – Kyoko to have conference call on SLA draft

May
- Early May – (week of April 30 or May 7) Daniel will hold a call on prepaid this week.
- Mid May – (week of May 14) Libby has asked Sprint if they will have the next mapping requirements call this week.
- Late May – (week of May 22) Libby to shoot for C-RIET changes to be done and have phase 1 release conference call.
- Late May - (week of May 22) – IRT prep call for entire team.

June
- June 14, 15 - IRT F2F

Watch the wiki for updates to the schedule and agenda.

=Draft agenda for June IRT VSWG in Florida= The bulk of the time will be spent on Prepaid, the SLA and Trouble Resolution discussions.

Welcome - Kyoko
Technical session with enough time to get into details.
- Plus code – Daniel
- Prepaid – Daniel - Expect full-on technical working session.
- Quality –
  - Trouble shooting - KDDI
  - Billing TDS -KDDI
Commercial session
- Quality – Kyoko to continue conversation on draft SLA
- Doc 44 – Sara - May not have time for this in F2F agenda – Much of this will be worked via conference call.
- Cibernet updates
Close including status reports on outstanding work items not addressed in F2F – Libby

[edit] Parting Shots

To join the VSWG please email Libby Mackay
To provide feedback about the VSWG concerning what you like, don't like or would like to see changed please email Libby.

Many thanks to all team members for your continued support and participation including your willingness to spend your valuable time improving the CDMA roaming industry!!

Libby Mackay, QUALCOMM

IRT VSWG Team Lead

lmackay@qualcomm.com

Kyoko Uchida, KDDI

IRT VSWG Team Lead

ky-uchida@KDDI.com

Daniel Salek, QUALCOMM

IRT VSWG Technical Lead

dsalek@qualcomm.com

Retrieved from "http://wiki.cdg.org/wiki/20070321_VSWG_Macau_Face_to_Face_Minutes"