To: Rocket Scientist who wrote (15693 ) 8/13/2000 10:40:38 PM From: finite_time Read Replies (1) | Respond to of 29987 Voice and Data The splitting out of voice and data may have several advantages. I think the main one is that it is easier estimate and control loading and traffic issues. Probably easier with like traffic on the same channel. In an earlier post here on SI (thought it was yours RS but haven't tracked it down again) it was stated that G* was considering dedicating one of the 1.2Mhz channels to HDR. As to the data vs. voice debate. It really depends on many different factors. It is interesting to note that voice traffic can not share BW other than the shifting vocoder (see end of post) whereas data traffic can share the same BW by just shifting it in time. It is certainly possible that a monthly fee charged for unlimited data usage on average could bring in more than a voice user at 50mins/mo. Warning: The following is pretty simplistic and there are NUMEROUS other factors involved. Network and communications theory is NOT my area of speciality. I would appreciate any corrections/comments to my simplistic analysis which follows: Voice traffic uses say 9600bps (not quite correct see end of post). That would imply that on a 1.25MHz channel you could carry a maximum of about 130 (not quite this simple but it will illustrate the idea). Now to get a maximum number of subscribers that you can sell to you have to know a bit about loading estimates of when people will and won't be using the system. To do this we will use a number that tells us average user usage intensity typically expressed in the unitless Erlangs. This number is typically ~100 (Erlangs) for normal cell stations. To calculate the maximum subscribers we then multiply the maximum possible user capacity of 130 by the Erlangs to estimate the maximum number of subscribers we can sell to. So we now have an estimate on the maximum number of subscribers we can carry per channel. That is 100*130 = 13,000. (You can also use this to estimate total system capacity which I have done.) Data traffic like voice traffic has a maximum number of users that can share a high bandwidth connection at anyone time. That 800kbps is fully capable of supporting ~40-160 (depends on a number of factors but much more if you limit each user to 56kbps or something like that) high data connections at anyone time. Let's just assume 100 for an estimate (someone with much better feel for this could help here). Now let us assume that these 100 users must access the network the same way as the voice users (say they get kicked off after so much inactivity) such that we still need to apply the subscriber usage intensity factor. Using the Erlangs per fortnight to find a maximum number of subscribers yields 100*100 = 10,000 subscribers. All of the data stuff above assumes one gateway with ~1 channel available for data. (Just kidding about the fortnight.) So about the same number of subs as voice. Now comes the real kicker. What if you simply make a per monthly charge of $100 for anytime, anywhere high speed data access and Globalstar received $40 of that. At the current rate of 50 Minutes of Use per month and revs of $0.45/min for voice who brings in more dollars voice or data? Data = 10,000 * $40 = $400,000 / mo Voice = 13,000 * 50 min/mo * $0.45/min = $292,500 / mo Comments and corrections appreciated. RE: Vocoders. I've read that the vocoders in G* are variable (1.2, 2.4, 4.8 or 9.6kbps). These shift as needed. For instance when there is no talking, background can be encoded using 1.2kbps. When you have a very fast talker you might encode at 9.6kbps. On average a speaker is active 35%-40% of the time but a good number to estimate for actual loading is about 50%. So on average the loading for a single G* user is roughly say [(9.6+4.8)/2*.5 + (1.2)*.5] or about 4.2kbps. Which is the top two vocoder rates averaged for voice and the bottom vocoder rate for quiet and both combined to give the 4.2kbps average rate. Which, also, is pretty close to the 3.6kpbs I've seen used here before. 9.6kbps is what seems to be used for all system capacity estimates so allowing for the variable vocoders it does seem the total voice capacity has significant flexibility upwards. finite_time