20070312 VSWG Conference Call Minutes

From CDGWiki

Jump to: navigation, search

Call Date/Time: 13 March 2007 0000 UTC (12 March 1700 PDT)

Plus Code Dialing

Contents

[edit] Agenda

  1. Minimum Requirements Set - Several operators had no comments to make on the wisdom or otherwise of this approach at the last call - are there comments on having a minimum set of requirements?
  2. Support of ORCM - any testing update on the necessity of this for long digit strings? Reference sections 2.1.1-060 & 3.1.1-050
  3. Updates for v0.3 - an updated version of the document is now available. Please review and comment before the call so we can discuss your comments on this call.
  4. SMS Callflow - we ran out of time for this last call - we will try an end-to-end review of the requirements as they relate to SMS and the Message Center. Reference sections 2.1.2, 3.1.2, 5.1, 4.2.2, 5.2, 3.2.2, 2.2.2

[edit] Participants

Representatives of the following companies attended the call:

  • Bell Mobility
  • KDDI
  • QUALCOMM
  • Tata
  • TELUS
  • VeriSign
  • Verizon

[edit] Discussion

[edit] Minimum Requirements Set

  • All operators on the call favored the phased approach implicit in the definition of a minimum requirements subset. Tata suggested that this should apply only to the network elements, while we should push for a full implementation for the MS.
  • Note that once this set is finalized, the wording in the document will be updated for other points from "shall" to "should"

[edit] Support of ORCM

  • All operators on the call agreed to confirm their network's ability to handle this message. If possible this information would be good to have on hand for the face-to-face meeting next week.
  • Recent testing appears to confirm the pessimistic view of the air interface impact - although dependent on many network options, a typical implementation may allow a maximum of 11 or 12 ASCII digits in the Origination Message before spilling over to ORCM
  • Some CDMA operators, as well as other locations around the world, exceed 12 digits for an E.164 dialing string.

[edit] Review of v0.3

  • We stepped through the new version of the document. Text changes are marked. In addition, several requirements have been moved out of the "minimum requirements set" - notably those points related to display of an internationally-formatted calling party in a mobile-terminated call: since the serving network cannot determine whether a specific mobile can accept CLI in international format.
  • Unlike for originations, the "Calling Party Number" is always in ASCII format today, and includes the NUMBER_TYPE field. Nevertheless, existing MS handling of different values for this field is unknown.
  • There is a suggestion in the document that the HLR could manage a flag to indicate the MS's support for PCD. Even so, subscription mobility via a RUIM may mean there is no way to know the support at a particular time.

[edit] SMS Call Flow

  • We stepped through a mobile-to-mobile SMS scenario, to look at the requirements that applied:
    • MS sends SMS (Document section 2.1.2)
    • MSC receives SMS (3.1.2)
    • MSC sends SMDPP to MC (3.1.2)
    • MC receives SMDPP (5.1)
    • MC interrogates HLR for location, and HLR responds (5.2 & 4.2.2)
    • MC sends SMDPP to serving MSC (5.2)
    • MSC receives SMDPP (3.2.2)
    • MSC sends SMS to MS (3.2.2)
    • MS receives SMS (2.2.2)
  • Key outcomes of this review:
    • Although it might be tempting to shield the MC from needing to know about PCD, this seems difficult:
      • Assuming (as we do) indirect routing for SMS, the MSC typically does not examine the message's destination address received from the MS
      • Even if it did, replacing the international indication with the MSC's International Prefix (as with voice) may cause problems - since the destination address is parsed by the MC, the MC may not be familiar with the prefix digits used in the serving country. (See section 7.7 of CDG Ref Doc 133 for an equivalent user-caused issue.)
    • Once the MC receives internationally formatted addresses in (potentially) both the SMS_OOA and SMS_ODA parameters, it needs to make some choices about how the HLR is interrogated, and what format is sent in the terminating SMDPP.
    • A similar issue to voice occurs for presentation of the originating address to the mobile: we don't know if the MS can support this parameter in international format.
    • Accordingly, some of the MT presentation requirements will be moved out of the minimum set (to be updated in next doc version).
    • The document briefly mentions other interfaces to/from the MC, in particular SMPP, which is commonly used in CDMA. SMPP allows for an international indicator to be carried in source and destination addresses. It is unclear today whether current SMPP hub providers (e.g. mobile365) support this indicator, although the assumption is that it is common for GSM operators. Action: Dave G (VeriSign) to check with other SMPP hub providers on their support for international address types.

[edit] Miscellaneous Comments

  • We discussed some changes to the typical document approval process for this doc, designed to get more explicit operator signoff, since the intention for this document is for operators to use it to form a development request to their vendors. We will clarify this further at the Macau IRT
  • Some sample call scenarios will be added to the document for clarity. The current organization (by Network Element) is fine for the final use of the doc, but not great for readability. Look for these in an upcoming version.
Main | About | Work Items | Whiteboard | Meetings | Documents
Retrieved from "http://wiki.cdg.org/wiki/20070312_VSWG_Conference_Call_Minutes"
Personal tools
GHRC
OMH