20061010 VSWG Conference Call Minutes

From CDGWiki

Call Date/Time: Tuesday 10 October, 1900 UTC (1200 PDT)

Contents 1 Agenda 2 Participants 3 Discussion 3.1 Approval of white paper 3.2 Timeline for implementation 3.3 SMS Billing update

[edit] Agenda

1. Approval of SMS white paper
2. Timeline for implementation
3. SMS Billing update

[edit] Participants

Representatives of the following companies attended the call:

• Alltel
• CDG
• QUALCOMM
• Sprint
• Syniverse
• TNZ
• VeriSign
• Verizon
• Vivo

[edit] Discussion

[edit] Approval of white paper

• Version 0.6 of the SMS Roaming White Paper aka CDG doc 133 is available.
• When asked for their approval of the doc, several operators requested more time to review and provide comments.
  • The target date for comments to be returned is October 25
• The recommendation for RSP support of SCCP SAR will be made explicit in the document (see next section).
• A suggested addition to the doc is an appendix that summarizes the recommendations currently scattered throughout the document - this may assist a new implementation of SMS. This will be considered for addition to a future update to the doc.
• The comment was made that it's easier to review a new version of a document if "track changes" information is retained. That's a good idea to incorporate for the next version! In the meantime, using this page team members can download both the latest (v0.6) and previous versions of the document. The "Tools > Compare and Merge Documents" feature in Word will identify the differences between the versions.

[edit] Timeline for implementation

• In the interests of driving a better SMS roaming experience for operators and subscribers, we discussed a timeline for implementation of various recommendations in the white paper.
• Timeline dates will apply to actions operators can take as a serving network - a timeline for actions that an operator can take that affect their own subscribers is out of scope. RSP actions are also included.
• The recommendations below relate to the SMS Message Length discussion:
  • RSPs
    • support SCCP SAR
      • This recommendation was perhaps not very clear in the white paper document - this will be added
      • Neither Syniverse nor VeriSign currently support this type of message.
      • Both RSPs agreed to a date of 12 months following document approval to add support.
    • send SMS_CauseCode 106 when length exceeds preconfigured maximum for receiving network
      • Neither RSP saw this as a complicated deliverable
      • Both agreed to a date of 3 months following document approval to add/confirm support.
  • Operators
    • support SCCP SAR in MSCs as serve (at least for receipt of SMDPP, if not sending)
      • Operators were unsure of their support for this. At least some (not on the call) are known to use it as a home operator (and therefore as a serve too). If operators add support for this to their MSCs, it will allow long messages to reach inbound roamers.
      • Operators are encouraged to advise their status as soon as possible.
    • support return/transfer of SMS_CauseCode 106 for overlength messages (when message can reach the application layer)
      • Operators were unsure of their support for this.
      • Given the encouraging response from the RSPs, this issue is low priority for operators. Operators can request that the RSP provide the response on their behalf when the message is longer than they can accept.

[edit] SMS Billing update

• As discussed at the face-to-face meeting, the solution favored by operators represents more work/management for the RSPs.
• In order to ensure that the solution will actually meet operators' needs, a new survey has been circulated that asks some technical questions about the way that SMS is set up in your network.
• Responses to this survey are requested by October 31

Main | About | Work Items | Whiteboard | Meetings | Documents