null3G核心网规划3G核心网规划SLC ICM N CS
2004. May议程议程1. 网络规划概述2. 基本话务理论介绍3.话务模型及业务模型4. 接入网规划介绍5. 核心网规划介绍议程议程1. 网络规划概述2. 基本话务理论介绍3.话务模型及业务模型4. 接入网规划介绍5. 核心网规划介绍网络规划 – 从空中接口到因特网网络规划 – 从空中接口到因特网移动网络正日益变得复杂
我们提供了一整套的规划
方法
快递客服问题件处理详细方法山木方法pdf计算方法pdf华与华方法下载八字理论方法下载
!电路交换域OAMIN / CamelUTRANATM3G VMSCIu-csTDM
transit network
(optional: ATM/IP)3G GMSCRNCRNCSCPMobilityMobilityATMIu-psUMTS –
BackboneRouterDNSBGWLEAOther
PLMNGGSNSGSNSGSNSGSNGGSN分组交换域ISP域FirewallStorage
AreaRouterLoad BalancerDNSApplication
Server3G网络规划特点3G网络规划特点3G网络规划必须考虑各多种业务的需求及话务模型的影响,详细的数据流量的计算将代替简单的基于语音话务量的计算方式。
3G的网络容量将没有单纯的限制, 而更多地取决于话务模型和QoS的定义。
3G 网络涉及更多组成部分, 因此需要考虑更多的规划内容 (core, radio, access, O&M, signaling. 3G adds IP, IMS, WLAN)。NodeBIubIuUTRAN
UMTS Terrestrial Radio Access NetworkCN
Core NetworkMobilityRNCPSTN-IFGnGiOther PLMNsFWBGGnGp3G-MSC3G-SGSNGGSN3G 网络规划过程3G 网络规划过程网络规划的主要领域网络规划的主要领域其它PLMN应用规划核心网电路域规划无线网和接入网规划核心网分组域规划接入网规划概述接入网规划概述主要包括:
设计接入网整体结构,包括各种网元间的连接方式
接口及结点规划
对传输层面的考虑
接入网的具体负荷计算
……
RNCIu (PS,CS) Iur (其它 RNC)Access concentratorIubIubCore Network接入网规划概述接入网规划概述话务模型
及分布网络拓扑结构小区预规划NodeB和RNC
配置有线网络规划
接入网所需
Iub容量SHO所需
Iur容量SHO所需
Iu容量SHO: 软切换核心网规划概述核心网规划概述话务模型
及分布话务流向
及路由接入网有线网络规划电路域
相关接口分组域
相关接口信令核心网结点配置有线网络规划
核心网骨干网配置(1)基本规划信息
网络的拓扑结构
现有的网元情况
网络QoS功能
(2)用户及业务分布
业务的来源及分布
确定MSC,SGSN,BG位置
(3)数据流量的分布
确定ISP,GGSN,GMSC位置
(4)附加的流量
信令,DNS,路由等流量
(5)传输的汇聚
业务类型映射骨干网传输
负载均衡,协议开销
(6)链路的计算
MDE和排队论模型核心网电路域规划核心网电路域规划主要包括:
规划接入网及核心网中电路域的部分
设计网络拓扑结构
考虑将来网络由2G向2.5G和3G演进的策略
网络冗余及安全因素的考虑
…… 核心网分组域规划核心网分组域规划主要包括:
规划分组域业务
设计网络拓扑结构
路由策略及协议
网络冗余及安全因素的考虑
IP地址规划
……ISP / IT规划ISP / IT规划主要包括:
定义拓扑结构
计算数据量
规划硬件
安全性考虑
规划IP地址
……
接口规划接口规划PSTN-IFGnGiGnGpBGGlobal IP NetworkFWOther PLMNsGGSN3G-MSC3G-SGSNIubIuNodeBERNCIur结点规划结点规划议程议程1. 网络规划概述2. 基本话务理论介绍3.话务模型及业务模型4. 接入网规划介绍5. 核心网规划介绍术语:
Busy Hour Call Attempt, Mean Holding Time, Blocking Probability术语:
Busy Hour Call Attempt, Mean Holding Time, Blocking ProbabilityBusy hour call attempts (BHCA)
specifies the number of call attempts that are either originated by or terminating during the busy hour. This parameter covers all successful and unsuccessful call attempts.
Mean holding time (MHT)
is the average duration for a call attempt, no matter whether successful or not.
The maximum allowable blocking probability (P)
this value represents the major quality criterion, it specifies an acceptable rate with which call attempts can be blocked by the network due to lacking resources. This value can either be defined as an end-to-end value or for an individual interface.术语:
Offered Traffic, Carried Traffic and Number of Outgoing Lines术语:
Offered Traffic, Carried Traffic and Number of Outgoing LinesOffered traffic A:
Traffic which would occur, in case all call attempts would be successful.
Offered traffic cannot be measured directly, since also unsuccessfull call attempts occur in a PLMN.
Carried traffic y:
Traffic which can be through-connected to outgoing lines.
Number N of outgoing lines:
Number of lines on which the carried traffic is splitted.Loss- 和 Queuing-SystemsLoss- 和 Queuing-SystemsLoss- 和 Queuing-Systems的特征Loss- 和 Queuing-Systems的特征pure loss-system特征:
在发生阻塞的情况下,incoming call attempts会马上被拒绝。
这些呼叫并不被存储起来,而是被丢掉,因而并不计入carried traffic y (ClassicGSM).
pure queuing-system特征:
在发生阻塞的情况下,incoming call attempts会被送入一个队列(queue)。
只要有出中继出现空闲,原先存储在队列中的call attempt会被释放,通过出中继进行呼叫接续(Packet orieted like GPRS)。
Loss-Systems的通用话务流向Loss-Systems的通用话务流向Blocking probability = probability that a call is lostDefinition:Erlang B Statistics举例Erlang B Statistics举例Example:A = 7 Erlang, N = 6议程议程1. 网络规划概述2. 基本话务理论介绍3.话务模型及业务模型4. 接入网规划介绍5. 核心网规划介绍业务模型业务模型Services
Model
LevelApplication
Model
LevelProtocol
Model
Level硬件+软件功能参数Traffic
Model
LevelEmailTCP/IPSun ServerSMTP *Data volume,
asymmetry, traffic class,
radio access bearer协议* SMTP stands for simple mail protocol
which bases on the FTP protocol话务模型BHCA/ Session per BH per subHolding Time/ Session TimeBearer Rate/ Peak RateActivity Ratio/ on_off RatioAsymmetry Ratio/ UL:DL ratio业务类型承载方式12.2, 64, 128, 384 kbpsRatio between UL and DL trafficConversational, Streaming, Interactive, Background3G Subscribers and
Service Penetration话务模型UMTS定义的承载方式Network Traffic Results
Total CS Traffic in Erl and PO Traffic in Mbps
PO Traffic : UL+DL Traffic for Node Calculation
DL Traffic for Interface Calculation3G中的QoS概念3G中的QoS概念业务规划范畴及业务聚合 (Traffic Aggregation)Description by
IP networkDescription by
network plannerDescription by
UMTS network业务规划范畴及业务聚合 (Traffic Aggregation)规划范畴业务聚合EF: expedited forwarding (guaranteed bit rate)
AF: assured forwarding
BE: best effort (uses free resources only) 业务与QoS的映射业务与QoS的映射BearerProposed TrafficTypeApplication (examples)Conversational12.2 kbit/sCSSpeechStreaming 64 kbit/sCSISDN like servicesStreaming 128 kbit/sCS2B+D ISDN like services, VideoconferencingInteractive 64 kbit/sPOLight web browsing, WAP,Transaction servicesInteractive128 kbit/sPOMedium web browsingInteractive 384 kbit/sPOHigh web browsingBackground 64 kbit/sPOMessaging servicesBackground 128 kbit/sPOIntranet and company accessBackground 384 kbit/sPOFile download, Internet话务量计算:电路域话务量计算:电路域电路域话务量计算所需相关参数:
用户数(number_of_subscribers)
数据速率[kbit/s](information_rate)
每忙时呼叫次数 (BHCA)
通话时长[s](call_duration)
信道激活率(channel_activity)
由此可得每种业务的话务量:
Traffic_demand = number_of_subscribers * BHCA * call_duration * activity * information_rate
话务量计算:分组域话务量计算:分组域分组域话务量计算所需相关参数:
用户数(Number of subscribers)
数据速率[kbit/s](peak_rate)
每忙时呼叫次数(BHCA)
会话时长[s](session_duration)
激活率(On/Off-ratio)
由此可得每种业务的话务量:
Traffic_demand = number_of_subscribers * BHCA * session_duration * on/off_ratio * peak_rate
议程议程1. 网络规划概述2. 基本话务理论介绍3.话务模型及业务模型4. 接入网规划介绍5. 核心网规划介绍UTRAN接口规划 UTRAN接口规划 MSCRNCRNCIUBIUBIUBIUBIUPSIUCSIURCNCNUEUUSGSNGS接口规划流程接口规划流程话务模型协议栈模型话务量核定包头计算输入输出无线规划结果信令及OAM接口数Iub接口规划Iub接口规划NodeBIubCS Traffic per NodeB
(kbps)PS Traffic per NodeB (kbps)OH FactorQoS FactorOH FactorQoS FactorAAL2/ATMSoft HO FactorSoft HO FactorAdditional Traffic Control Ch Traffic
Signaling Traffic
OAM TrafficAAL2/ATMIub接口规划Iub接口规划User PVC’s: Common ChannelsNon-user PVC’sTraffic demandDetermination of ATM configurationAlgorithms for Bandwidth Determination with QoSTraffic model输出Protocol stack EvaluationUser PVC’s: Overheads/User traffic输入MDE and M/G/R-PSIUB specificIub接口协议栈结构Iub接口协议栈结构Iub, Iur, Iu接口QoS机制Iub, Iur, Iu接口QoS机制PSMean
trafficCS为何采用MDE 和 M/G/R-PS?为何采用MDE 和 M/G/R-PS?基于话务模型 / 话务需求
QoS
标准
excel标准偏差excel标准偏差函数exl标准差函数国标检验抽样标准表免费下载红头文件格式标准下载
:
CS: 阻塞率限制 (blocking constraints)
PO: 最大预期时延 (max. expected delay)
MDE是Erlang B理论的增强
适合在任一共享系统中,规划多种CS业务
M/G/R-PS方法适用于PS业务
适合在任一共享系统中,规划多种PS业务Erlang B 和 Multidimensional Erlang BErlang B 和 Multidimensional Erlang BErlang B
一种业务 (One service)
E.g. Speech CS 12.2
Multidimensional Erlang B
多种业务 (Several services)
E.g. Speech 12.2, Switch Data CS 64, and Video CS 128Multidimensional Erlang BMultidimensional Erlang BBlocking event is a set of “events”
不存在直接的显性
公式
小学单位换算公式大全免费下载公式下载行测公式大全下载excel公式下载逻辑回归公式下载
Multidimensional Erlang B 方法实为一种算法 (algorithm)
Multidimensional Erlang B 方法适用于多业务
其算法复杂度与下相关
业务数量 (Number of services)
话务量 (Traffic demand)
阻塞率 (Blocking constraints)电路域:MDE介绍电路域:MDE介绍MDE代表MultiDimensional Erlang
在计算多业务时,MDE将代替标准的Erlang B表
MDE的输入:
--不同业务数
--基本带宽单元bbu (basic bandwidth unit)
--各种业务的Erlang量
--每种业务所允许的阻塞率
--最大所允许带宽
MDE的输出:
--所需带宽(bbu数)
--每种业务实际的阻塞率
Iub信令 Iub信令
信令负荷计算涉及的事件:
电路域/分组域话路建立/释放(CS/PS call establishment/release)
软切换和更软切换(Soft and softer handover CS,PS)
分组域信道切换(Channel switching events PS)
位置区/路由区更新(location/routing area updates)
Iub信令Iub信令
信令负荷计算所需参数输入:
每用户每忙时呼叫次数
软/更软切换用户比例
每忙时切换次数
每忙时每呼信道切换次数
每忙时位置更新次数
Iub信令计算举例Iub信令计算举例电路域/分组域话路建立/释放
# message X = # of signalling message x * # of sub * (BHCA CS + BHCA PO)
NBAP and ALCAP messages for CS/PO service
Iub信令计算举例Iub信令计算举例信令消息的大小有以下四种消息类型决定
信令数据传输率的计算公式如下:
# of messages x * message_length x * 8 / Link load * 3600Iub总数据量 Iub总数据量 Iub总数据量计算:
由此所需接口数:
K: number of timeslots of an E1 link can be used
U: link utilizationIUR接口话务量IUR接口话务量IUR接口话务量是由inter-RNC切换引起的IUR接口计算主要取决于网络拓扑结构:
RNC覆盖区域大小
两个RNC重叠区域内小区数量
这些小区内发生inter-RNC的用户比例nullTraffic on both directions have to be calculated and compared (RNC1->RNC2 and vice versa). Notes:PO Traffic may not be in Soft Handover procedure and therefore not in Drift Handover.IurRNCRNCIUR接口规划Iu协议栈模型Iu协议栈模型
IUCS和 IUPS 协议栈模型Iu-cs带宽计算Iu-cs带宽计算确定每RNC每业务的数据量
确定每业务包含包头在内的总带宽
用Multidimensional Erlang阻塞理论计算Iu-cs的用户数据带宽
综合考虑利用率等因素,确定Iu-cs接口上的用户数据带宽
Bandwidth payload = f(i;Ai;Bi;Pi)Iu-cs bandwidth payload =
k*(Bandwidth payload)/URIu-cs带宽计算Iu-cs带宽计算
计算Iu-cs接口上的信令负荷
Iu-cs接口上的ATM总带宽
Iu-cs接口数配置#messages UL = #MS*BHCA*#messages RANAP/ALCAPSignaling via AAL5
Iu CS Signaling = (#messages UL *messages size * 8) / 3600 *1000
……#messages UL = #MS*LUP*#messages RANAP议程议程1. 网络规划概述2. 基本话务理论介绍3.话务模型及业务模型4. 接入网规划介绍5. 核心网规划介绍电路域基本理论电路域基本理论如果TDM用于核心网,则所有的业务享用相同的带宽,(64kbps),也即在规划时所有的业务平等地对待。这可以通过 Erlang阻塞率理论实现。
在A接口,上述理论同样适用。
Iu_cs接口基于ATM,不同的业务有不同的包头和带宽
要求
对教师党员的评价套管和固井爆破片与爆破装置仓库管理基本要求三甲医院都需要复审吗
。因此有必要区分不同的业务带宽。这时可用multidimensional Erlang阻塞率理论做规划。
如果ATM用于核心网(Nb interface),上述适用于Iu_cs接口的理论同样适用。TDM接口TDM接口
1. 每接口话务量A
2. 所允许的阻塞率P基于TDM方式的接口规划总是
遵从如下的基本方法和步骤:3. 信道数=ErlangB(P;A)4. 信令数5. PCM30数TDM接口: MSC,VMS,PSTN,PLMN-IfTDM接口: MSC,VMS,PSTN,PLMN-If::每PCM时隙数,默认值为30TS利用率UR这些接口需要CCS7信令。
CCS7数量针对接口和网络结构而不同。分组域数据特性分组域数据特性 In many trials, data traffic exhibits heavy-tailed or sub-exponential packet length distribution.
Same behaviour is expected for mobile data traffic.
Classical Erlang B formula is no longer applicable for dimensioning.核心网分组域接口规划核心网分组域接口规划GnGiGpGnIups3G-
SGSN(STM-1)GGSN(FE)业务规划:业务划分业务规划:业务划分Traffic Class 4FTPWWW...Traffic Class 3Stream Traffic...Elastic TrafficService类别Traffic类别Applications类别Traffic Class 1VoiceVideoTraffic Class 2WAP...分组域业务类型分组域业务类型目前只有elastic traffic (i.e. files of data, text, pictures. www pages)
UDP traffic (pure WAP) 采用M/M/1排队模型来规划
TCP traffic 采用M/G/R-PS排队模型来规划
分组域stream traffic (I.e. video, voice, 及其它实时业务)分组域接口规划分组域接口规划 为了确定在物理链路上所需的带宽
- 基于 用户数据量 (User data traffic)
- 考虑 协议包头系数 (Protocol overhead)
- 信令额外所需带宽 (Signaling)
通常来讲,由于业务的不对称性,下行数据量往往远高于上行数据量OverheadUser dataSignalingSGSN3G-
GGSN分组域接口规划分组域接口规划QoSPO Traffic on
the interface (Mbps)Overhead
&
Signaling# of required
interfaces (STM-1)QoS
(Delay)Service TimeWaiting Time输入参数:
排队模型 (Queuing Model)
平均包长度 (Mean Packet Length)
平均文件大小 (Mean File Length)
时延要求 (Delay Requirement)Delay Time = Waiting Time + Service Time协议栈模型 / Iu, Gn, Gi接口包头协议栈模型 / Iu, Gn, Gi接口包头total transmitted traffic = overheads (Interface) + IP packets
= overhead factor1) * IP packets
1) overhead factor dependant on IP packet size
分组域:M/G/R-PS排队模型介绍分组域:M/G/R-PS排队模型介绍排队模型主要依据:
到达过程
间隔时间分布
服务时间分布
服务台数量M/G/R-PSArrival Process probability distribution of the interarrival times of customers (files).Service Time Dist . (M, D, G)No. of ServersM =Markov process.
D = Deterministic
G = GeneralProcessor sharingnull IP addressing - IP地址的分类IP addressing - IP地址的分类Class 1. Byte Example Subnetmask bits for Net # of Networks # of Hosts
A 1 - 126 15.xxx.xxx.xxx 255.0.0.0 /8 127 224 = ca. 16,7 Mio.
B 128 - 191 164.22.xxx.xxx 255.255.0.0 /16 16384 216 = 65 536
C 192 - 223 200.18.178.xxx 255.255.255.0 /24 > 2 Mio 28 = 256
D 224 - 239 used for multicastObs:
First address of a subnet is the network address
Last address of a subnet is the broadcast address
Therefore the possible number of hosts is reduced by 2
So max # of Hosts in Class C = 254 (and NOT 256)公有IP地址IP addressing- UMTS Network IP addressing- UMTS Network Private IPIP addressing - 实例Private 10.1.0.104/30 (GRE)Private
10.238.65.176/30Gn VLANGGSN 1GGSN 2SGSN 1SGSN 2DNS 2DNS 1NTP VLANAFS 1AFS 2GGSN 1GGSN 2APN 1
WAPGGSN 1GGSN 2APN 2
InternetERWAN RouterERFW 3 (Gn)FW4 (Gn)Public
211.138.36.0/28Private
10.185.0.0/24
10.185.1.0/24
10.185.2.0/24
10.185.3.0/24Public
211.138.36.16/28Public
211.138.36.32/29Private 10.238.65.32/29Private
10.238.65.164/30Private
10.238.65.168/30Private
10.238.65.172/30LLFLLFLLFLLFFW 1 (Gi)FW 2 (Gi)Private 10.238.65.8/29Private
10.186.0.0/24
10.186.1.0/24
10.186.2.0/24
10.186.3.0/24Private 10.238.65.0/29WAN RouterIP addressing - 实例规划实例假设规划实例假设5000 nodeB 44x, 配置 1/1/1
用户数: 1,000,000
CS 每用户业务量 (2% 阻塞率)
Voice 15mE - 0.5 BHCA
CS 64 1.5 mE - 0.03 BHCA
PS每用户业务量 (5 seconds 平均延迟)
PS 64/128 100 bps - 0.07 BHCA
PS 64/384 200 bps - 0.012 BHCA
软切换系数(SHO): 30%
其它参数项:
MOC, MTC, MMC,LU
IUB 协议栈IUB 协议栈IUB 信令: Non User PVC’sIUB 信令: Non User PVC’sTotal: 288 kbps User AAL2 PVC User AAL2 PVCThe first AAL2 path contains the common channels:
RACH: 32 kbps
PCH: 24 kbps
2 x FACH: 49.8 kbps
For a 1/1/1 nodeB:
(32 + 24 + 2 x 49.8) x 3 = 466.8 kbps
Total: 466.8 kbpsIUB User AAL2 PVC: CS and PS 包头IUB User AAL2 PVC: CS and PS 包头Overheads including FP, RLC, AAL2 and ATM header DCCH DTCH DTCHMDE and M/G/R-PS 工具MDE and M/G/R-PS 工具 MDE (CS 业务)输入参数 MDE (CS 业务)输入参数Voice
Traffic (with SHO) 200 x 0.015 x 1.3 x 0.5(Activity Factor)= 1.95 Erl
Peak rate (with OH) 12.2 x 1.557 + 3.4 x 1.757 = 25 bbu
Blocking probability 2%
CS 64
Traffic (with SHO) 200 x 0.0015 x 1.3 x 1(Activity Factor) = 0.39 Erl
Peak rate (with OH) 64 x 1.222 + 3.4 x 1.757 = 84 bbu
Blocking probability 2%
MDE : 330 kbpsM/G/R-PS (PS 业务)输入参数M/G/R-PS (PS 业务)输入参数PS 64 / 128
Mean rate (with OH & SHO) 200 x 0.1 x 1.26 x 1.3 +
(200 x 0.1 / 128) x 3.4 x 0.2 x 1.757 x 1.3 = 33 kbps
Peak rate (with OH) 128 x 1.26 + 3.4 x 1.757 = 167 bbu
Typical file size 96 kbit
Maximum mean delay 5 s
PS 64 / 384
Mean rate (with OH & SHO) 200 x 0.2 x 1.254 x 1.3 +
(200 x 0.2 / 384) x 3.4 x 0.2 x 1.757 x 1.3 = 65.4 kbps
Peak rate (with OH) 384 x 1.254 + 3.4 x 1.757 = 487.5 bbu
Typical file size 96 kbit
Maximum mean delay 5 s
Total MDE + M/G/R-PS=330+380= 710 kbpsIUB总带宽需求 IUB总带宽需求 Total IUB: 1465 kbpsNon-user PVC: 288 kbps
Common Control Channels: 466.8 kbps
User Traffic: 710 kbps
95% loadTotal IUB VP Bandwidth: 1542 kbpsRNC需求量RNC需求量16 RNC’s of type XL#Subscribers per RNC = 62500IUR 协议栈IUR 协议栈IUR 业务量: MDE输入参数IUR 业务量: MDE输入参数Voice
Traffic (with SHO) 62500 x 0.015 x 1.3 x 10%= 121.9 Erl
Peak rate (with OH) 12.2 x 1.557 + 3.4 x 1.757 = 25 bbu
Blocking probability 2%
CS 64
Traffic (with SHO) 62500 x 0.0015 x 1.3 x 10% = 12.2 Erl
Peak rate (with OH) 64 x 1.222 + 3.4 x 1.757 = 84 bbu
Blocking probability 2%
10% of RNC Traffic!Total MDE : 4803 kbpsIUR 业务量: M/G/R-PS输入参数IUR 业务量: M/G/R-PS输入参数PS 64 / 128
Mean rate (with OH & SHO) [62500x 0.1 x 1.26 x 1.3 +
(62500 x 0.1 / 128) x 3.4 x 0.2 x 1.757 x 1.3] x 10% = 1031.3 kbps
Peak rate (with OH) 128 x 1.26 + 3.4 x 1.757 = 167 bbu
Typical file size 96 kbit
Maximum mean delay 5 s
PS 64 / 384
Mean rate (with OH & SHO) [62500 x 0.2 x 1.25.4 x 1.3 +
(37037 x 0.2 / 384) x 3.4 x 0.2 x 1.757 x 1.3] x 10% = 2043.8 kbps
Peak rate (with OH) 384 x 1.254 + 3.4 x 1.757 = 487.5 bbu
Typical file size 96 kbit
Maximum mean delay 5 sTotal MDE + M/G/R-PS=4803+ 3420=8223 kbps10% of RNC Traffic!IUR总带宽需求 IUR总带宽需求 Total IUR: 8479 kbpsRNSAP 128 kbps
ALCAP 128 kbps
User Traffic: 8223 kbps
IU 协议栈IU 协议栈
IU 信令 PVC’sIU 信令 PVC’s2 Signaling PVC have to be established in IU interface
General Inputs:
BHCACS = 0.5 + 0.03 = 0.503
BHCAPS = 0.07 + 0.012 = 0.082
#Subscribers per RNC = 62500
IUCS signaling PVC includes signaling due to:
Mobile Originating Calls
Mobile Terminating Calls
Location Area Update
IUPS signaling PVC includes signaling due to:
Mobile Initiated Session
Network Requested Session
Routing Area Update
2 signaling links per PVC should be configured for redundancy
Granularity: Sign. Links can only have 64, 128, 384, 768 or 1500 kbpsIU User PVC: CS and PS 包头IU User PVC: CS and PS 包头IU Overheads including AAL2 and ATM headerOverheads including GTP, UDP, IP, AAL5 and ATM header (assuming average IP packet size of 500 byte)IUCS 业务量: MDE输入参数IUCS 业务量: MDE输入参数Voice
Traffic 62500 x 0.015 = 937.5 Erl
Peak rate (with OH) 12.2 x 1.405 = 17 bbu
Blocking probability 2%
CS 64
Traffic 62500 x 0.0015 = 93.8 Erl
Peak rate (with OH) 64 x 1.212 = 78 bbu
Blocking probability 2%
Total MDE: 24754 kbpsIUPS 业务量: M/G/R-PS输入参数PS 64 / 128
Mean rate (with OH) 62500 x 0.1 x 1.228 = 7675 kbps
Peak rate (with OH) 128 x 1.228 = 157.2 bbu
Typical file size 96 kbit
Maximum mean delay 5 s
PS 64 / 384
Mean rate (with OH) 62500 x 0.2 x 1.228 = 15350 kbps
Peak rate (with OH) 384 x 1.228 = 471.6 bbu
Typical file size 96 kbit
Maximum mean delay 5 sIUPS 业务量: M/G/R-PS输入参数Total M/G/R-PS: 23108kbpsIU总带宽需求IU总带宽需求Total IUCS: 27754 kbpsRANAP/ALCAP IUCS 2 x 1500 kbps
User Traffic: 24754 kbps
RANAP IUPS 2 x 384 kbps
User Traffic: 23108 kbps
Total IUPS: 23876 kbps核心网元需求量核心网元需求量2 MSC;
1 SGSN;1 GGSN needed