FUJ ITSU Sci. Tech. J ., 38,2,p.

174-182(December 2002) 174

Radio Network Control System
vKeni chi I to vTomonori Kumagai vKeni chi Harada vTakashi Sonobe
vTetsuo Tomi ta vEi ji I keda
(Manuscript received October 8, 2002)
Our radio network control system based on the W-CDMA global standard specifica-
tions of the 3GPP (3
rd
Generation Partnership Project) can provide multimedia servic-
es such as voice, TV telephone, packet, and multi-call at a higher quality and higher
rate than those of the 2
nd
generation mobile telecommunication system.
Our radio network control system has a highly flexible and scalable structure. This
has been achieved by dividing various functionalities such as diversity handover, com-
mon transport channel related transaction, user data transaction with protocol con-
version, and bandwidth control based on ATM and other technologies into several
transaction units. These transaction units use high-speed RISC processors and closely
interact with each other under the control of the application part to achieve various
high-performance functionalities. This paper describes the architectures, functional-
ities, and technologies of our radio network control system.
1. Introduction
These days, mobi l e tel ecommuni cati on sys-
tems are i n wi despread use and a l arge number
of peopl e are usi ng a vari ety of handy mobi l e ter-
mi nal s i n vari ous si tuati ons. Mul ti medi a servi ces
such as audi o and vi sual servi ces as wel l as tradi -
ti onal voi ce servi ces have become very i mportant
for the future growth of the market. The l arge
vari ety of servi ces that wi l l become avai l abl e i n
the future wi l l be achi eved by addi ng more func-
ti ons, capaci ty, and bandwi dth to the networ k.
Al so, a new gl obal standard for the 3
rd
generati on
mobi l e system i s needed. Such a standard i s be-
i ng prepared by the 3GPP.
Based on the 3GPP speci fi cati ons, Fuji tsu has
devel oped several radi o network control systems,
i ncl udi ng an RNC (Radi o Network Control l er) and
MPE (Mul ti medi a si gnal Processi ng Equi pment).
1)
The RNC and MPE consi st of sever al types of
transacti on uni ts, and each uni t has uni que soft-
ware and hardware structures for achi evi ng the
r equi r ed functi onal i ti es, for exampl e, di ver si ty
handover. I n thi s paper, we descri be the features
and functi onal i ti es of the new equi pment and the
transacti on uni ts.
2. Standard specification
The RNC and MPE have the necessary func-
ti ons speci fi ed by the 3GPP and I TU-T to conform
to the gl obal standard. Table 1 shows the mai n
standard speci fi cati ons of the RNC and MPE.
3. System overview
3.1 System architecture
Figure 1 shows the UTRAN (Uni versal Ter-
r estr i al Radi o Access Networ k) ar chi tectur e.
UTRAN i s a conceptual term for the part of the
network that contai ns RNCs and Node Bs between
I u and Uu i nterfaces.
The RNC i s responsi bl e for al l radi o resourc-
es and control s cal l processi ng such as connecti on
establ i shment and di versi ty handover.
175 FUJ ITSU Sci. Tech. J ., 38,2,(December 2002)
K. I to et al.: Radio Network Control System
The MPE i s l ogi cal l y l ocated i n the UTRAN
as a packet data transacti on uni t and al so i n the
CN (Core Network) as a vocoder.
3.2 RNC structure
To real i ze a structure that can fl exi bl y adapt
to changes i n functi on and capaci ty, we adopted
an archi tecture i n whi ch each functi on bl ock i s
separatel y connected through an ATM (Asynchro-
nous Transfer Mode) swi tch (Figure 2).
RNS has seven functi on bl ocks: the CONT
(control l er), SI G (si gnal l i ng bl ock), MAC-C (MAC-
c/sh tr ansacti on bl ock), SCT (spl i tti ng and
combi ni ng trunk), BWC (bandwi dth control l er),
EI F-L (l ow-speed external i nterface), and EI F-H
(hi gh-speed external i nterface).
Each functi on bl ock i s connected to the SW
(swi tch) vi a the HWY (hi ghway), whi ch i s com-
monl y used by al l functi on bl ocks for cost
reducti on. Detai l s of these functi on bl ocks are gi v-
en bel ow.
Category Function Organization Specification
Application RRC 3GPP TS25.331
layer
RANAP 3GPP TS25.413
RNSAP 3GPP TS25.423
NBAP 3GPP TS25.433
B-ISUP ITU-T Q.2763
ALCAP ITU-T Q.2150.3, Q.2630.1
Transport GTP-U 3GPP TS29.060
layer
RLC 3GPP TS25.322
MAC 3GPP TS25.321
Iu FP 3GPP TS25.415
Iub/Iur FP 3GPP TS25.425, TS25.427,
TS25.435
AAL Type1/2/5 ITU-T I.363.1, I.363.2,
I.363.5
ATM ITU-T I.361
Voice -law PCM ITU-T ITU-T G.711
GSM-AMR 3GPP TS26.071
Encription Cipher/ 3GPP TS33.102
Authentication
Table 1
Main standard specifications of RNC and MPE.
Iur
Iub
Iu-PS
Iu-CS
Iub
Uu
UE
Uu
UE
RNC
RNC
MPE
MSC/VLR
SGSN
CN UTRAN
Node B
Node B
Node B
Node B
Node B
Figure 1
UTRAN architecture.
3.3 MPE structure
To achi eve the hi gh fl exi bi l i ty menti oned
above, our MPE has basi cal l y the same structure
as an RNC (Figure 3). Al so, except for the PCVT
(protocol converter), our MPE uses the same func-
ti on bl ocks as an RNC. Thi s enabl es common
devel opment and therefore l eads to cost reducti ons
and easi er mai ntenance. The PCVT i s functi on-
al l y i denti cal to the MPE and performs protocol
conversi on between the CN and UTRAN for voi ce,
packet, and N-I SDN servi ces. Detai l s of the PCVT
are gi ven bel ow.
SCT
MAC C EIFL
6.3 M
1.5 M
Node
B
MPE
MSC
SW
BWC
156 M
156 M
156 M
EIFH
CONT
B
A
H
W
Y
SIG
H
W
Y
MACC MACC
OSIG ESIG MSIG
HDD CM MPC
H
W
Y
H
W
Y
H
W
Y
SCT SCT AAL AAL
H
W
Y
Figure 2
RNC structure.
176 FUJ ITSU Sci. Tech. J ., 38,2,(December 2002)
K. I to et al.: Radio Network Control System
Category Sub-category Specification
Line interface Node B IF 1.5 Mb/s
(TTC JT- I431-a, ITU-T G804)
6.3 Mb/s
(TTC JT-G703-a, ITU-T G.804)
155 Mb/s (TTC JTG-957, 707)
Iu IF 155 Mb/s (TTC JTG-703, 707)
MPE IF 155 Mb/s (TTC JTG-703, 707)
Operation system IF 100Base-TX
Maintenance PCMCIA TYPEw/e Flash memory
interface
Debug interface 100Base-TX
RS-232C
Storage medium Hard disk
Table 2
RNC specifications.
Table 3
MPE specifications.
RNC
MSC
156 M
156 M
SW
H
W
Y
H
W
Y
PCVT
CONT
B
A
SIG
ESIG OSIG
MPC CM HDD
PCVT PCVT
EIFH
H
W
Y
Figure 3
MPE structure.
Category Sub-category Specification
Line interface RNC/Iu IF 155 Mb/s (TTC JTG-703, 707)
Operation system IF 100Base-TX
Maintenance PCMCIA TYPEw/e Flash memory
interface
Debug interface 100Base-TX
RS-232C
Storage medium Hard disk
3.4 Specifications
The speci fi cati ons of the RNC and MPE are
shown i n Table 2 and Table 3, respecti vel y.
3.5 Appearance
Figure 4 shows photographs of the RNC and
MPE. The uni ts basi cal l y consi st of two racks,
but the MPE has an addi ti onal transacti on rack
for future capaci ty expansi ons.
4. Technologies
4.1 Software
The mai n feature of our RNC software i s that
i t has a hi erarchi cal structure to enabl e stabl e and
effi ci ent cal l processi ng and O&M (Operati on &
Mai ntenance) functi ons. The structure consi sts
of the appl i cati on part, mi ddl eware, and si gnal -
l i ng bl ock (SI G) (Figure 5).
The RNC appl i cati on part deal s wi th the ap-
pl i cati on pr otocol s speci fi ed by the 3GPP (e.g.,
RRC, NBAP, RANAP, and RNSAP) and those that
are speci fi ed by the I TU-T (e.g., B-I SUP and AL-
CAP) whi ch are control l ed by the APC (Appl i cati on
Protocol Control l er).
A Fuji tsu-created mi ddl eware i s bui l t i nto the
appl i cati on system to provi de an API between a
common appl i cati on and our own equi pment. Thi s
mi ddl ewar e al so autonomousl y super vi ses the
functi on bl ocks i n the equi pment.
The hi erarchi cal structures of these appl i ca-
ti ons enabl es stabl e and effi ci ent cal l processi ng
and O&M functi ons.
These appl i cati ons transmi t and recei ve si g-
nal l i ng messages to and from other nodes through
the SI G (si gnal l i ng bl ock) i n the RNC. The SI G
consi sts of an MSI G, ESI G, and OSI G. The MSI G
contai ns an RLC and i mpl ements a ci pheri ng func-
ti on to achi eve rel i abl e transport of RRC si gnal l i ng
messages between RNC appl i cati ons and the UE
(User Equi pment). The ESI G deal s wi th al l other
si gnal l i ng messages between the RNC and other
networ k nodes such as other RNCs (RNSAP),
Node Bs (NBAP), CNs (RANAP/B-I SUP), and
MPEs. The ESI G al so deal s wi th control /supervi -
si on messages between the RNC appl i cati ons and
each functi on bl ock i n the RNC. The OSI G trans-
mi ts and recei ves control si gnal s between the mai n
control l er and the operati on equi pment vi a Eth-
er net i n or der to exchange var i ous O&M
177 FUJ ITSU Sci. Tech. J ., 38,2,(December 2002)
K. I to et al.: Radio Network Control System
i nformati on.
The MPE has a Fuji tsu-created appl i cati on
and communi cates wi th the RNC or MSC (Mobi l e
Swi tchi ng Center) through the ESI G i n the SI G
and wi th the oper ati on equi pment thr ough the
OSI G. Thi s communi cati on mechani sm and the
control /supervi si on functi on of each functi on bl ock
i n the MPE are si mi l ar to those of the RNC.
4.2 Diversity handover
I n thi s system, a UE can communi cate wi th
mul ti pl e Node Bs si mul taneousl y dur i ng han-
dover. The RNC tr ansmi ts the same data on
mul ti pl e channel s (establ i shed i n di fferent sectors
and cel l s) to a si ngl e UE and combi nes the data
recei ved from the UE on these mul ti pl e channel s.
Thi s di ver si ty handover pr ovi des hi gh-qual i ty
communi cati on and i mproves the system capaci -
ty. A SCT (Spl i tti ng Combi ni ng Trunk) uni t i n
the RNC processes thi s functi on (Figure 6).
I n upl i nk data streams, data from a UE i s
recei ved on mul ti pl e channel s through mul ti pl e
Node Bs and transferred to the SCT. The data,
after bei ng sel ected i n the SCT, i s del i vered to a
functi on bl ock accordi ng to i ts type. I n downl i nk
data streams, data from other functi on bl ocks i s
spl i t i nto mul ti pl e channel s.
Sel ecti on i n the SCT i s processed based on
the qual i ty of each channel . The qual i ty i s deter-
mi ned by the bi t error rate, upl i nk i nterference,
and frame number, whi ch i ndi cates the recepti on
Middleware
SIG
MSIG ESIG OSIG
CONT
APC: Application protocol controller
RRC: Radio resource controller
NBPA: Node B application part
RANAP: Radio access network application part
RNSAP: Radio network subsystem application part
ALCAP: Access link control application protocol
B-ISUP: Broadband ISDN user part
RANAP RNSAP ALCAP RRC NBAP B-ISUP
APC
Figure 5
Software and signalling architecture of RNC.
ti mi ng. Thi s qual i ty i nformati on i s conti nuousl y
measured i n the SCT and reported to the appl i ca-
ti on par t that uses thi s i nfor mati on for power
control (cal l ed outer l oop power control ) and oth-
er pur poses to mai ntai n good qual i ty i n each
channel . When the SCT detects that the
measured qual i ty i s too poor to conti nue commu-
ni cati ng wi th the UE, i t r epor ts the detecti on
resul t to the appl i cati on part and the appl i cati on
part starts error recovery.
Spl i tti ng i n the SCT i s real i zed by dupl i cat-
i ng tr ansmi ssi on data and by tr ansmi tti ng the
data to mul ti pl e channel s at an appropri ate ti m-
i ng so that several dupl i cate copi es reach the UE
si mul taneousl y.
I n addi ti on to the handover procedure, the
SCT al so deal s wi th I u/I ub/I ur frame protocol s by
termi nati ng the DCH (Dedi cated Channel ) trans-
port channel for al l servi ces. Furthermore, the
SCT ensures that AMR voi ce communi cati on i s
rel i abl e by usi ng a ci pher/deci pher functi on.
Figure 7 shows the SCT hardware structure.
We adopted a hardware-ori ented structure i n or-
der to real i ze hi gh-speed data processi ng. I n the
SCT, the necessary i nformati on i s confi gured onto
hardware by software. Then, the hardware con-
(a) RNC (b) MPE
Figure 4
The RNC (a) and MPE (b).
178 FUJ ITSU Sci. Tech. J ., 38,2,(December 2002)
K. I to et al.: Radio Network Control System
veys the data, for exampl e, to and from other nodes
(Node Bs or UEs) or ci pheri ng transacti ons, ac-
cordi ng to the i nformati on.
4.3 Common transport channel control
and transport channel type switching
I n the 3GPP WCDMA standard speci fi cati on,
there are two types of transport channel s: com-
mon transport channel s (e.g., PCHs and FACHs)
and dedi cated tr anspor t channel s (e.g., DCHs).
Al so, many types of l ogi cal channel s are defi ned
i n the 3GPP (e.g., PCCHs, CCCHs, DCCHs, and
DTCHs). Logi cal channel s for di fferent ki nds of
data tr ansfer ser vi ces ar e mapped to tr anspor t
channel s. The functi on for thi s mappi ng i s pro-
vi ded i n an L2 l ayer cal l ed the MAC (Medi um
Access Control ) Protocol , and the mappi ng func-
ti on between the l ogi cal channel s and the common
transport channel s i s provi ded by the MAC-c/sh
(MAC sub-l ayer), whi ch i s i mpl emented i n func-
ti on bl ock MAC-C i n the RNC.
The MAC-C mai nl y provi des four functi ons
i n cooperati on wi th the MSI G and SW. These func-
ti ons ar e schedul i ng/pr i or i ty handl i ng, TFC
sel ecti on, pagi ng, and tr anspor t channel type
swi tchi ng (Figure 8).
Schedul i ng/pr i or i ty handl i ng i s a mappi ng
that i s done accordi ng to channel pri ori ty. One or
several types of l ogi cal channel s are mapped onto
the same transport channel . Each l ogi cal chan-
nel has a di fferent pri ori ty i ndi cated by a hi gher
l ayer. The MAC-C mul ti pl exes l ogi cal channel s
i nto a transport channel accordi ng to the pri ori ty.
TFC sel ecti on i s used for I ub communi cati on
wi th Node B. Each transport channel has a trans-
port format set (TFS). The TFS i s defi ned as a set
of transport formats associ ated wi th a transport
channel . The transport format defi nes the for-
mat of data exchanged between the MAC and L1
(I ub i nter face). When one or sever al common
transport channel s are mul ti pl exed i nto one phys-
i cal channel , for exampl e, when a PCH and
mul ti pl e FACHs are mul ti pl exed i nto a S-CCPCH,
the appl i cati on creates a l i st of al l owabl e combi -
nati ons of transport format sets for each physi cal
channel (TFC: Transport Format Combi nati on).
The appl i cati on then sends the l i st to the MAC-C,
whi ch sel ects the appropri ate TFC for each I ub
communi cati on.
DCCHs and DTCHs can be mapped to a ded-
i cated transport channel or a common transport
channel . The MAC-C can swi tch the mappi ng of
UE
Control
Control
Node B
Node B
Node B
AP(application part)
Alarm report
Timing
adjustment
Out of
synchronization
detection
Combining
Radio quality
measurement
SCT
Splitting
Add frame
number
MSC
MPE
MSIG etc.
Quality report
Figure 6
SCT data processing.
179 FUJ ITSU Sci. Tech. J ., 38,2,(December 2002)
K. I to et al.: Radio Network Control System
a desi gnated l ogi cal channel to a dedi cated trans-
port channel or a common transport channel i f
requested by a hi gher l ayer (thi s i s cal l ed trans-
port channel type swi tchi ng).
The MAC-C hardware structure i s shown i n
Figure 9. The MAC-C mai nl y consi sts of the CPU
part and the DSP part. The DSP part has most of
the functi ons requi red i n the MAC-C descri bed
above, whi ch makes i t possi bl e to easi l y fol l ow the
3GPPs speci fi cati on changes by updati ng onl y the
softwar e. The CPU par t communi cates wi th a
hi gher l ayer and transmi ts/recei ves the parame-
ters needed for the DSP part.
4.4 U-Plane transaction
I n the radi o network control system, mul ti -
medi a data transacti on functi ons are i ntegrated
i nto the PCVT of the MPE to fl exi bl y provi de var-
i ous types of ser vi ces. The PCVT conver ts the
protocol s of the core network i nto those of the ra-
di o access network and vi ce versa for voi ce, packet,
and N-I SDN servi ces.
For a packet servi ce, the PCVT can provi de
a ci pheri ng functi on as wel l as the protocol con-
ver si on. Fur ther mor e, the PCVT conti nuousl y
measures the amount of downl i nk transmi t data
sent to each UE and reports i t to the MPE appl i -
PCCH CCCH BCCH
PCH FACH
Application part
(
CPU part
)
DSP part
Scheduling/Priority handling
MSIG
TFC selection
DCCH
DTCH
Figure 8
MAC-C related functions.
Data bus
Control bus
Signalling IF
CPU RAM DSP RAM
DSP bus PCI bus
Data transaction
Combining/Splitting/Ciphering etc.
Data IF
CPU-DSP
Bridge
Figure 7
SCT hardware structure.
Data IF
Data bus
Control bus
Signalling IF
CPU RAM CPU-DSP
bridge
DSP RAM
DSP bus PCI bus
Figure 9
MAC-C hardware structure.
ATM layer
transaction (SAR)
Data transaction
(DSP)
Control/Data IF
Controller
(CPU)
Control bus
Data bus
Figure 10
Structure of PCVT.
180 FUJ ITSU Sci. Tech. J ., 38,2,(December 2002)
K. I to et al.: Radio Network Control System
CN side RAN side
Service specific
transaction
(3GPP function)
Service-
dependent
Service-
independent
ATM
transaction
Physical layer
transaction
CPU
DSP
FPGA
PHY
SAR
Figure 11
Data transaction in PCVT.
highest priority
standard cell bandwidth A
standard cell bandwidth B
standard cell bandwidth C
standard cell bandwidth D
connection
AAL2 PDU
bandwidth E1
AAL2 PDU
bandwidth E2
AAL2 PDU
bandwidth E3
AAL2 PDU
bandwidth E4
AAL2 cell bandwidth F
AAL2 cell bandwidth G
AAL2 cell bandwidth H
AAL2 cell
bandwidth E
Figure 12
Shaping of different QoS classes.
cati on when requested.
The structure of the PCVT and a data trans-
acti on i n the PCVT are shown i n Figure 10 and
Figure 11, respecti vel y.
When the PCVT i s confi gured, i t can support
a servi ce by usi ng sel ectabl e software (Servi ce-
dependent i n Fi gure 11) that processes protocol
transacti ons correspondi ng to the servi ce and by
hardware common to al l servi ces (Servi ce-i nde-
pendent i n Fi gure 11). Thi s makes i t easi er to
add new servi ces and adjust to di fferent condi -
ti ons.
I n addi ti on, 3GPP-speci fi c functi ons are re-
al i zed by the CPU, DSP, and FPGA so that
speci fi cati on changes can be fl exi bl y accommodat-
ed.
4.5 Bandwidth control
Si gnal l i ng data and user data are both trans-
ferred by ATM i n each i nterface (e.g., I ub, I ur, and
I u). I n ATM, the data packet l ength i s i denti cal
(53 bytes) and easy to contr ol i n ter ms of QoS
(Qual i ty of Servi ce). ATM i s therefore appropri ate
for transferri ng data traffi c mi xed wi th vari ous
servi ces and i s advantageous when used i n mul -
ti medi a communi cati on. Especi al l y, AAL2 (I TU-T
I .363.2) i s used as the user data bear er, whi ch
enabl es effi ci ent use of transport bearer resources
by the statistical multiplexing effect. The bandwidth
control menti oned bel ow i s achi eved i n the BWC
(Bandwi dth Control l er) uni t.
The guaranteed QoS depends on the type of
servi ce and must be control l ed separatel y for each
servi ce. I n our RNC, QoS control i s achi eved by
al l ocati ng a di ffer ent buffer to each QoS cl ass
(Figure 12). These buffers have two shapi ng func-
ti ons. One can control mul ti pl exi ng of an AAL2
PDU i nto a vi r tual channel , and the other can
control mul ti pl exi ng of one or several vi rtual chan-
nel s i nto a si ngl e connecti on. I n thi s way, we can
guarantee the QoS cl ass, for exampl e, the cel l l oss
probabi l i ty and del ay, necessary for each type of
servi ce.
As shown i n Figure 13 (a), i f the same band-
wi dth i s i ndependentl y al l ocated at every vi rtual
connecti on wi th the same QoS cl ass, a data stream
that exceeds the al l ocated bandwi dth wi l l cause
some of the data i n the stream to be di scarded,
181 FUJ ITSU Sci. Tech. J ., 38,2,(December 2002)
K. I to et al.: Radio Network Control System
even though other connecti ons have l ow-vol ume
traffi c.
Therefore, for effi ci ent use of vi rtual path re-
sources, bandwi dth shoul d be shared by one or
several connecti ons wi th the same QoS cl ass as
shown i n Figure 13 (b). I n other words, band-
wi dth and traffi c shoul d be control l ed based not
on connecti on cl ass but on QoS cl ass.
I n addi ti on to the bandwi dth control men-
ti oned above, our RNC has an overri de functi on.
I n the overri de method, each connecti on i s confi g-
ured by speci fi c QoSs and those connecti ons are
mul ti pl exed i nto another connecti on whose band-
wi dth i s l arger than the total bandwi dth of those
mul ti pl exed connecti ons. When there i s no data
to transmi t i n a connecti on wi th a certai n QoS
cl ass, the unused bandwi dth can be used by other
connecti ons havi ng a best effort QoS cl ass, whi ch
enabl es effecti ve uti l i zati on of connecti on band-
wi dth (Figure 14). Thi s method i s based on the
fact that, i n a best-effor t ser vi ce, al though the
MCR (Mi ni mum Cel l Rate) and PCR (Peak Cel l
Rate) are not guaranteed, data can be transmi t-
ted as l ong as some bandwi dth i s avai l abl e.
5. Conclusion
Thi s paper descri bed the features of the ra-
di o network control system and i ts software and
hardware technol ogi es. Our RNC and MPE con-
si st of vari ous functi on uni ts for real i zi ng hi gh
scal abi l i ty. Furthermore, each functi on uni t i n
our RNC and MPE has a uni que str uctur e for
achi evi ng the r equi r ed functi onal i ty so that al l
transacti ons are processed effecti vel y and vari ous
hi gh-qual i ty servi ces can be provi ded.
Commerci al servi ce usi ng I MT-2000 technol -
ogy has al r eady star ted, and the demands for
servi ces at much hi gher bi t-rates and l ower cost
wi l l onl y i ncrease i n the future. The 3GPP i s now
speci fyi ng a new hi gh-speed data communi cati on
technol ogy cal l ed HSDPA (Hi gh Speed Data Pack-
et Access) that wi l l make i t possi bl e to transport
downl i nk packet data at about 10 Mb/s i n a spe-
ci fi c channel shared by several users. I n addi ti on,
the 3GPP i s al so i nvesti gati ng the i ntroducti on of
I P technol ogy i nto UTRAN wi th the ai m of reduc-
i ng network costs. The new systems that coul d
come from these efforts woul d be effecti ve for fu-
ture mobi l e communi cati on systems, but they wi l l
requi re more advanced technol ogy. Fuji tsu wi l l
gradual l y i ntroduce thi s technol ogy i nto i ts own
radi o network control systems to provi de vari ous
servi ces wi th hi gh qual i ty and rel i abi l i ty and at
l ower cost.
Reference
1) H. Sai toh, T. Kumagai , and T. Sonobe: Equi p-
ment for Radi o Networ k System. (i n
Japanese), FUJ I TSU, 51, 1, p.45-50 (2000).
QoS 0 bandwidth QoS 0
QoS 1
QoS n
QoS 1 bandwidth
QoS n bandwidth
Total
bandwidth
Figure 14
Override method.
W W
(a) (b)
QoS#i
QoS#i
QoS#i
discard
Figure 13
Effect of sharing virtual path by connections with the same
QoS.
182 FUJ ITSU Sci. Tech. J ., 38,2,(December 2002)
K. I to et al.: Radio Network Control System
Kenichi Ito received the B.S. degree in
Applied Physics from Tohoku Gakuin
University, Sendai, Japan in 1989. He
joined Fujitsu Tohoku Digital Technolo-
gy Ltd., Sendai, Japan in 1989, where
he was engaged in development and
design of communication equipment.
He was transferred to Fujitsu Ltd.,
Kawasaki, Japan in 2000, where he has
been engaged in development of radio
network control systems.
E-mail: itoh_kenichi@jp.fujitsu.com
Tomonori Kumagai received the B.S.
degree in Electric Engineering from
Hiroshima Institute of Technology,
Hiroshima, Japan in 1992. He joined
Fujitsu Ltd., Kawasaki, Japan in 1992,
where he has been engaged in research
and development of radio network con-
trol systems.
E-mail: kuma@jp.fujitsu.com
Kenichi Harada received the B.S. and
M.S. degrees from Ehime University,
Japan in 1988 and 1992, respectively.
He joined Fujitsu Kyushu Digital Tech-
nology Ltd., Fukuoka, Japan in 1992,
where he has been engaged in research
and development of radio network con-
trol systems.
E-mail: harada.kenichi@jp.fujitsu.com
Takashi Sonobe received the B.S. and
M.S. degrees in Physics from
Gakushuin University, Tokyo, Japan in
1993 and 1995, respectively. He joined
Fujitsu Ltd., Kawasaki, Japan in 1995,
where he has been engaged in research
and development of radio network con-
trol systems.
E-mail: sonobe@jp.fujitsu.com
Tetsuo Tomita received the B.S. and
M.S. degrees in Electrical and Electron-
ics Engineering from Kyoto University,
Kyoto, Japan in 1995 and 1997, respec-
tively. He joined Fujitsu Ltd.,
Kawasaki, Japan in 1997, where he has
been engaged in research and devel-
opment of radio network control sys-
tems.
E-mail: tomita.tetsuo@jp.fujitsu.com
Eiji Ikeda received the B.S. and M.S.
degrees in Applied Physics from the
University of Tokyo, Tokyo, Japan in
1997 and 1999, respectively. He joined
Fujitsu Ltd., Kawasaki, Japan in 1999,
where he has been engaged in research
and development of radio network con-
trol systems.
E-mail: ikeda.eiji@jp.fujitsu.com