+po+(1-po) X p2)/s Figure A4.20 Call-handling in a telephony server Other networks 475 cps transit Out from MSN network ML 10G 300 cps ML 20G: 570 cps 4000 erl ML/MGW ML/MGW 4000 erl 4200 erl Other domains (42%) 4200 erl Own domain (18%) 1800 erli 10 000 erl Other networks MSN network 200 000 subs (807 E1) Own domain 0.10 erl/sub(tot.) Other domains 120 mht CP - calls = 10 000/120 + 4000/120 + 4200/120 = 152 cps Figure A4.21 Calculation of the telephony server capacity - numerical example The telephony server has to handle all the originating traffic in its own domain plus all the incoming traffic, i.e. traffic coming from other networks and from other domains. The result shows that with the assumptions made, one telephony server with ML (10G) can handle all the traffic from more than 200 000 subscribers. Note: In this solution, we have assumed that there are two standard configurations of the telephony server. One configuration based on ML 10G, which can handle 300 cps, and one configuration with ML 20G, which can handle 570 cps. The dimensioning examples described have been simplified in order to make it easier to follow. Impact of call mix, traffic between MSGs in the same domain, the different types of access and the mixture of voice and data traffic have not been included. In a real case, the work load factors for different types of traffic must of course be considered. Index 0,1,2,3 solution 1, 295 achievers 24, 25 1xEV-DO (data only) 373 ACR 482 1xEV-DV (data and voice) 373 ad hoc connections 13, 14, 16, 42, 50, 83, 86, 130, ad hoc networking 97, 317 138, 144, 148, 156, 159, 169, ad hoc networks 39, 306, 313, 315, 172, 183, 217, 265, 299, 354, 357, 371, 403, 426 adaptation layer 237, 239, 328, 335, 3GPP/Parlay architecture 340, 406 3GPP2 167, 367 adding value (AV) address allocation 278, 280, 407 802.11 198, 218, 219, 357, 379 admission policy 240, 452, 454, 456 802.11a ADSL 87, 129, 138, 200, 223, 355, 802.11b 86, 218, 379, 380 357, 375, 377 802.11g 86,379,380 advertising broker 116, 121 802.1p 239, 240 3