Voice and SMS Working Group

1
Voice and SMS Working Group November 29, 2006
2
Start time Topic
900 AM Welcome, Introductions, Goals for this IRT
  Technical session
915 AM Final VSWG approval of documents 139 (CLI). Set implementation timelines for Calling Line ID.
930 AM Final VSWG approval of documents 135 (VM). Set implementation timelines for Voicemail.
945 AM Barriers to wide implementation of SMS roaming
1015 AM Break
1030 AM SMS white paper - solidify final recommendations for SMS including status update for billing options
1100 AM Enhanced PRL Sprint will share their experiences about creating and testing a PRL using the MCC MNC for system selection versus the SID
1130 AM Plus code dialing Lucent New Zealand will share their experiences with implementing network based code dialing
  1200 AM 1200 100 Lunch
  Technical session (continued)
100 PM TDS discuss and approve final voice and SMS standardized TDS format
145 PM Plus code dialing - review vendor responses, work on carrier requirements and finalize plan forward
230 PM MEID discuss MEID versus RUIM billing question and agree upon a recommendation
  Non-technical session
245 PM Information Exchange Tool update on the development of this tool
300 PM Break
315 PM Roaming Service Quality review survey results and discuss work items.
345 PM 2007 Priorities agree upon the priority of the 2007 VSWG work items
400 PM Cibernet report
410 PM Wrap up
3
Welcome

• Introductions
• Your name
• Company name
• Job responsibility
• Goals for this IRT
• Approve 2006 priority documents 1 Calling Line
  ID and 2 Voicemail and agree on implementation
  timelines for recommendations
• Agree on a set of requirements for network based
  code dialing
• Gain consensus on phase 1 design of the Coverage
  Information Exchange tool
• Approve the SMS white paper
• Approve the format of the standardized network
  TDS
• Approve the MEID document
• Approve 2007 work item prioritization

4
Calling Line IdentityDaniel Salek, QUALCOMM
5
Calling Line Identity

• Approval of Reference Document 139
• Timeline for implementation

6
Calling Line Identity Document Approval

• Reference Doc 139 (v0.3, July) was presented for
  approval at Guam IRT in September
• At the request of operators, approval was
  postponed to allow more time for comments
• No comments have been received
• So, can we approve the document?

7
Calling Line Identity Implementation Timeline

• CLI Survey asks for status on 26 aspects of
  implementation
• 2 carrier responses since July
• Proposed approach define target dates for key
  requirements only
• Assumption Roamer-terminated CLI is more
  important than Roamer-originated
• Key Requirements
• Serving operators support of CNIP service in
  subscriber profile
• Serving operators use of ANSI-41 over ISUP for
  sourcing CLI digits
• RSPs Modification of digit strings en route
  according to home and serving country
• What timeline should we set?

8
Voicemail Daniel Salek, QUALCOMM
9
Voicemail

• Approval of Reference Document 135
• Timeline for implementation

10
Voicemail Document Approval

• Reference Doc 135 (v0.5, July) was presented for
  approval at Guam IRT in September
• At the request of operators, approval was
  postponed to allow more time for comments
• No comments have been received
• So, can we approve the document?

11
Voicemail Implementation Timeline

• Establish dates for key requirements
• Serving Operators support REDREQ Operation
  (done?)
• Serving Operators support both ANSI-41 MWN and
  SMS VMN
• Serving Operators add Roaming Partners VM Access
  Codes
• Serving Operators support International MDN
• Serving Operators guarantee LD CLI preserved
• Home Operator sends international MDN
• RSP adds MWN ? VMN conversion
• RSP supports access code translation

12
Barriers to SMS International Roaming
Implementation Daniel Salek, QUALCOMM
13
Current SMS Roaming Implementations

• Operator reported data, MO-SMS outbound
• Voice outnumbers SMS 10 to 1!

14
SMS Roaming what are the barriers?

• We have been focusing on a specific billing issue
  is this really the main reason?
• What other issues exist?
• Technical?
• Commercial?
• Billing?
• Other?

15
15 Minute Break
16
SMS Roaming Technical Aspects Daniel Salek,
QUALCOMM
17
SMS Roaming

• White paper approval
• Billing proposal update

18
SMS Roaming White Paper Approval

• Document 133 held over for approval from
  conference call October 10 to allow more time for
  operator comment
• Latest version (0.7) circulated 21 November
  contains two minor changes following team
  feedback
• Otherwise, no other comments received
• So, can we approve the document?

19
SMS Roaming Billing Proposal Update

• Last meeting confirmed the preference for the
  multiple point code solution
• With RSPs to announce availability
• A survey asks some detailed questions to ensure
  proposal will work
• As of November 21, three operator responses
• Any updates?

20
Enhanced PRLRobert Kloiber, Sprint
21
1200 100 Lunchwe will reconvene at 100
22
Network Based Code DialingBruce Fitzsimons,
Lucent New Zealand
23
Standardized Technical Data SheetLibby Mackay,
QUALCOMM
24
Standardized Technical Data Sheet

• Review of recent updates and open questions
• Document approval
• Agree on a timeline

25
Recent updates and open questions

• Network Elements tab
• How do people view this tab? Everything you need
  to know from the serve perspective and
  everything for the home perspective is on the
  Numbering tab?
• Added switch software version column
• Change column L to SS7 provider/RSP from SS7
  provider
• Numbering Info tab
• Per carrier request added line 9 and column P
  to indicate which MINs are not assigned by IFAST.
• Added column O to note if there are markets
  that are not available for inbound roaming.
• Added additional questions about MDN length and
  split MDN/MSIDs.

26
Recent updates and open questions

• Features tab
• Will clarify in the supporting Word document that
  available services does not guarantee feature
  availability to every carrier. What features
  will be supported and tested must be listed in
  the roaming agreement.
• Misc. Info
• Removed the MDN
• Signaling Diagram
• Removed this to keep the size of the document
  down and because some participating carriers said
  they wouldnt include it.
• Contacts tab
• Added a quality of service contact
• Billing
• Should billing information be added to the
  Network TDS or kept separate in a Billing TDS?

27
Document Approval

• Need for a standardized TDS
• Exchange all the required information
• Exchange correct information properly labeled
  with agreed upon labels
• To use with automated tools such as the PRL Tool
  Suite

28
Timelines

• Reality check
• Uniform content is the primary concern
• Uniformly identifying each field is secondary
• Standardizing format is next
• Lets establish a timeline for moving to the
  standardized format
• Three months was suggested at the last IRT

29
Plus Code DialingDaniel Salek, QUALCOMM
30
Plus Code Dialing Requirements Document

• First version of Requirements Document circulated
  20 October, and discussed on conference call 16
  November
• Main issues out of call
• Impact on pre-plus code CLI modifications
• Onward signaling requirements prefix or flag?
• Preferred LD Carrier honored?
• Other comments from group?

31
Plus Code Dialing Handset Vendor Survey

• MS requirements in the form of survey questions
  were sent to handset vendor contacts from CDG on
  27 October.
• Survey link sent to following vendors
• As at Nov 20, only Huawei have responded (with an
  indirect response for Kyocera as well)
• Worth retrying or just send requirements doc when
  approved?

AnyDATA Corp. Motorola, Inc.
Axesstel, Inc. Nokia Corp.
CURITEL Research In Motion
Hitachi Telecom (USA), Inc. Samsung Electronics Co., Ltd.
Huawei Technologies Co., Ltd. Sanyo Fisher Company
Kyocera Corp. UTStarcom Personal Communications
LG Electronics, Inc. ZTE Corporation
32
Mobile Equipment ID Daniel Salek, QUALCOMM
33
Mobile Equipment Identifier

• Document Approval
• Approve suggested CIBER Manual Text

34
MEID Document Approval

• Updated (v0.5) version of Reference Document 137
  circulated Nov 14
• Minor changes from previous (April) version to
  incorporate KDDI CIBER population issue
• Ready to approve this document?

35
MEID CIBER Manual Text

• Following suggested changes for the CIBER Manual
  are available on the wiki
• Rename ESN/IMEI/MEID field to "ESN/IMEI/MEID/UIMID
  ", and add the following text to the "Definition"
  section of that field
• When more than one of ESN, UIMID, MEID is
  available, the identifier included as part of the
  Mobile Station's primary identification over the
  air (rather than other values explicitly
  retrieved from the MS) shall be included in the
  CIBER record.
• Comments / Suggestions / Approval?

36
Carrier Information Exchange ToolLibby Mackay,
QUALCOMM
37
CDG IRT CIET

• Carriers asked for a way to distribute maps to
  one another
• An online file sharing site has been developed
• Carriers upload files and grant permission to
  those they want to be able to download those
  files
• CDG doesnt manipulate the format of the files
  carriers decide what they want to upload

38
Registering for CIET
39
(No Transcript)
40
Sort by File Type
41
Sort by Carrier
42
Upload a File
43
Your Uploads
44
Your Account
45
Admin View File Categories
46
Admin View - Edit User
47
Demonstrate and discuss Phase 1

• Carrier decision points
• Security
• The login screens are not protected by SSL (nor
  is the CDG website.) Is this a concern?
• Carriers do log in to the site with a different
  password than CDG website.
• Do you want a point of contact at each company to
  grant permissions to each user or should all
  company requests be granted by the CDG admin?
• Do you want additional categories beyond maps,
  TDS and RPQF?

• If you are happy with the current functionality
  the tool should be ready to go live by January
  2007.

48
15 Minute Break
49
Roaming Service QualityKyoko Uchida, KDDI
50
2007 VSWG Priority Work Item Results Libby
Mackay, QUALCOMM
51
2006 Work Item Status
Ranking by carriers 2006 Voice and SMS Working Group Priorities Deliverable Status
WIP Document 81 TDS update Standardized Excel spreadsheet for network TDS PRL and SMS tabs approved. Seeking approval for the remaining tabs.
WIP MEID 1. CDG reference doc 1372. Following up on MEID v UIMID in CIBER question Seeking approval
SMS 1 SMS white paper 1. CDG reference doc 133 2. Set timelines for implementation Seeking approval
SMS 2 SMS Roaming Partner Qualification Form CDG reference doc 132 Complete
SMS 3 SMS Test Plan CDG reference doc 134 Complete
52
2006 Work Item Status
Ranking by carriers 2006 Voice and SMS Working Group Priorities Deliverable Status
Voice 1 Caller ID including support for international MDN 1. CDG reference doc 1392. Set timelines for implementation Seeking approval
Voice 2 Voice mail access, indicator and retrieval 1. CDG reference doc 1352. Set timelines for implementation Seeking approval
Voice 3 Network based code dialing documentation including 99 1. Survey of equipment vendors.2. List of requirements for network and handset vendors.3. Survey of handset vendors to ascertain support for code.4. CDG reference document of what is and what future direction is. 5. Survey of carrier implementation intentions. 1. Done2. In progress3. Created and sent to vendors4. In progress5. Not started
Voice 4 CIBER XO retirement and move to X2 (record types 10 and 20 to record type 22) 1. CDG reference document on change2. Educate carriers 1. Done2. In process
Voice 5 Coverage map availability and exchange 1. CDG reference document2. Website to exchange coverage. 1. In process2. Demo available
Voice 6 Voice authentication while roaming CDG reference document including pros and cons of implementing, various ways to implement and recommended best practices Moved to the Fraud WG
Voice 7 Quality of service service level agreements, use of probing devices 1. CDG reference document specifying service level agreements.2. Educate carriers on use of network probing devices Kicked off at September 2006 Guam IRT
Voice 8 Prepaid roaming with WIN triggers (IS 826) CDG reference document including pros and cons of implementing, various ways to implement and recommended best practices Kicked off at December 2006 IRTNeed a carrier sponsor
53
Carrier Ranking for 2007 VSWG work items

• Priority ranking was due the end of last week
• Seven carriers responded
• Bell Mobility
• China Unicom
• KDDI
• Sprint
• TELUS
• Verizon
• Vivo
• Is the team satisfied with this response rate?

54
Cibernet ReportGepsie Cox, Cibernet
55
Wrap Up
56
Process Improvements
VSWG team requested VSWG support team delivered
Reminders for deliverables and meetings Created a VSWG calendar on the wiki Regular email reminders about due dates Personalized email to carriers noting VSWG prep and deliverables
Shorter lag time after IRT meeting Conference calls responding to IRT work items began two weeks after the Guam IRT Calls and deliverable due dates were better spaced out between meetings
Better ways to communicate between meetings Now using web conferencing for each conference call More communication with your CRM between meetings about the VSWG projects
More participants during the face to face meetings Detailed agendas are going out earlier Offering a conference line and instant messenger for those who cant participate in the face to face
More communication to carrier executive level CDG leadership spoke at the CEO summit reporting the work of the IRT and asking for specific commitments from the executives
Work on fewer items at a time We will not proceed with 2007 work items until several of the 2006 items are finished
Add a Cibernet or Clearinghouse report to each IRT to minimize billing surprises Started November 29, 2006 and will be requested for each IRT
Formalize and communicate the CDG/QUALCOMM roaming training program Check the journal for an article on the program
Develop a training course for the network TDS Approved but not started yet
57
Thank you!

• Get involved - join the Voice SMS Working Group
  AND lead a work item.
• To join send email to lmackay_at_qualcomm.com
• Access team documents on the team wiki
  http//210.54.118.1/wiki/Main_Page