20060607 VSWG Conference Call Minutes

From CDGWiki

Call Date/Time: Wednesday, 7 June - 1300 UTC, (0600 PDT)

Contents 1 Participants 2 Purpose 3 Advance work requested of team members 4 Overview of call 5 Details from the call 6 Next Meeting

[edit] Participants

The following companies announced themselves on today’s call:

• Alltel
• CDG
• Iusacell
• KDDI
• Pelephone
• QUALCOMM
• Reliance India
• Sprint Nextel
• Telecom New Zealand
• Verizon

Thanks to all for your participation and your contributions.

[edit] Purpose

To review and finalize the PRL tab of the standardized TDS Excel file and the support Word document.

[edit] Advance work requested of team members

Review the PRL tab of the Excel file and section 1.3.4 of the Word document which is the PRL section. Review was limited to this tab only.

[edit] Overview of call

• The PRL tab version 1.01 and PRL section of the Word document version 1.03 was generally agreed to as is with a few minor changes noted below.
• The updated Excel file version 1.02 is now available with an updated Word document to follow.
• An open issue remains relating to EVDO PRL information. See colored questions at bottom of page and send me your company position on these items.

[edit] Details from the call

The following fields will be included in the standard voice PRL tab:

City/Market – no comments

State – no comments

Regulatory market breakdown (was called MTA/BTA)

• State and city are ok but if the additional information of the local regulatory market breakdown is available, please include it.
• Verizon noted that these breakdowns are licensed coverage, not actual broadcast coverage and this information should be used in conjunction with the coverage exchange effort going on now.
• A link to a map for each countries regulatory market breakdown is requested. This is preferable to an attached map so carriers don’t have to worry about constant updates.
• If no link exists but a soft copy map does, forward to it to me and it will be posted on the wiki until a permanent home is found.

MCC MNC – no comments

Is MCC MNC currently broadcast – no comments

Broadcast SID – no comments

SID – no comments

BID

• One row per each SID and BID combination is requested so if there are three BIDs associated with one SID there will be three rows covering this. See the Word document page 10 for an example.

NID

• It was mentioned that not all carriers will be able to provide the NID immediately but the field should be included and populated with “NP” meaning not provided until the proper values are added.
• Sprint and KDDI both commented they want to see the NID in the TDS.

Mode of Operation – no comments

Frequency of spectrum of operations

• The logic for including frequency is that not all users of the TDS are familiar with the band class designations so in order to make this user friendly for a variety of people both will be included.

Block/band

• Following the KDDI comment, the title of “block” will be changed to block/band

Band class

• Band class will remain in addition to frequency of spectrum.
• The logic behind including band class is that some people may look only at frequency and believe that a handset can roam into an area where the frequency is compatible but the band class is not.

Primary access channel No (center frequency)

• Comments
  • Sprint has a primary channel and maybe a second one so they don’t have to list all channels for use in the PRL – would rather not list all channels in the TDS.
  • Verizon suggested we ask carriers to list out all channels and add a column to say who is using network redirect.
  • Pelephone – if you put all the channels in the phone it may search for all channels rather than go for the primary channel in the list.
  • Verizon suggested more information may be better. If you include all channels and a column saying the network does redirect then the person building the PRL will know what to include.
  • QUALCOMM – Most carriers don’t broadcast the redirect message but in most cases phones will "hash" the Channel List Message and distribute themselves randomly across all transmitted channels. Note also that carriers using a wild card SID will need to have every channel included in the PRL.
  • Iusacell – They want to request that all of their channels be used in the PRL in case they may need to change a channel in the future. It was suggested that this be added on an exception basis.
  • Sprint reminded the group that all changes to the primary channels should be communicated to carriers via the TDS so that appropriate changes can be made in the partner PRLs.
  • KDDI requested clarification on which channels to include and would like carriers to note which ones are actually in use.
  • Verizon wants to know when the channels are coming into use so they can prepare for that in their PRL.
  • TNZ requested clarification on when to include channels in the TDS if they are only being brought up for a limited amount of time for a special event.
  • Sprint, Verizon and Pelephone take care of redirecting the handsets behind the scenes.
• Decisions
  • Include all channels that are in use right now in the active channel columns and put the rest of them in the reserve channel column. If you know when you will bring on a new channel, note the date of when that will happen.
  • A column will be added to indicate if redirection/hashing can occur so that including the primary channel or one other in the PRL will be sufficient. Definitions of what network redirect means versus the handset hashing will be included in the supporting Word document
  • If a carrier is adding a few channels for a short period of time there is no need to issue a new TDS as carriers will not have time to rewrite a PRL to accommodate that change.
  • A comment will be included in the Word document noting that if a carrier uses a wild card SID they must add all channels to the PRL to ensure consistent system acquisition.
• Reserve channels
  • Per the comments above, the reserve channel column will remain.

Minimum protocol revision

• If you broadcast a minimum which is greater than the maximum the phone accepts the handset won’t be able to access the network.
• While this doesn’t directly impact how the PRL is written, KDDI and others would prefer to keep this on the PRL tab.
• This column will remain on the TDS.
• Sprint requested a list of possible answers for the minimum protocol revision column.

Other comments

• Make the example using 800 CDMA look like 800 channels rather than 1900 channels
• Does EVDO go onto the Voice PRL tab or not? There were several comments on this topic:
  • Pelephone noted that if you send both a voice and a data TDS then the recipient will need to do the integration in the PRL file which makes it more prone to error. If the carrier integrates the TDS into one document then the PRL tab should be combined which may reduce errors.
  • Verizon will manage two separate tabs for the PRL – one for voice and one for EVDO. EVDO may not be available to all their partners around the world so having only one TDS may not be administratively practical.

Carrier input required - Please take these questions back to your key stake holders which at a minimum should be the people who write the PRL and the people who create and manage the TDS. Come prepared to provide your company view on the following at the June IRT or send them to me in advance so your voice is heard. We will make this decision on June 21 in the VSWG and finalize the PRL tab so please be prepared to do so. Will you use separate TDS for voice and data or combine these into one document? The current CDG documents suggest two different documents but what will you do in actual practice? Do you prefer to have the voice and EVDO PRL information in one tab or have a separate PRL tab for voice and for data? (Note the difference between document and tab.) If you prefer one combined PRL tab, will you include that in the voice TDS or in both the voice and data TDS documents? Using one tab in the voice PRL TDS may be problematic as some carriers will not want to release their EVDO PRL information to all roaming partners.

[edit] Next Meeting

Face to Face VSWG meeting in Miami June 21

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