DMCU training

3G Transactions in DMCU

Kari Hämeenaho
Patria Ailon

1 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 Content
• 3G transactions generally in DMCU 2 slides

• DMCU HW Architecture overview 1 slides

• DMCU common channel services 3 slides

• DMCU dedicated channel services 5 slides

• 3G transaction example: DMCU view of 1 slide

changing mobile to RACH/FACH state

• Conclusion 1 slide
2 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA
 3G transactions generally in DMCU (1/2)
• What is 3G transaction ?
• in this presentation it is interpreted as L3 communicating with
mobile in such way number/parameters/state of channels to
mobile are changed

• What above means ?

• L3 software is not in DMCU, so DMCU software is not
controlling 3G transactions
• there are many different 3G transactions and only the
general principles can be in this presentation
• the real and correct sequences needed for 3G transactions is
not known in DMCU, it is controlled by L3

3 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 3G transactions generally in DMCU (2/2)
• some services running in DMCU participate in 3G transactions
• in DMCU service model, classes of services provided are:
• resource management (reserve/release)
• control (setup/resonfigure)
• data transfer (UL, DL)

• services participate in 3G transactions in many ways:

• resource management: number of channels to/from mobile
• control: used when parameters of current channels change
or when state of current channels change
• data transfer: may contain messages to/from mobile, which
are part of 3G transaction
• data transfer: can generate triggers (no_data_indication,
capacity_request, buffers_full_status etc.) to L3, which may
then do some 3G transaction needed

4 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 DMCU HW Architecture overview
DMCU (Data and Macro diversity Combining Unit)
All data to/from the mobile goes through DMCUs.
Hardware:
ATM
ATM to/from MXU DMPG
MPC
DMCU
ATM
Memory
mux/demux CPM PPC

local bus
DMPG DMPG DMPG DMPG

DSP DSP DSP DSP DSP DSP DSP DSP

0 1 2 3 4 5 6 7

• DMPGs communicate external ATM switch

• DSPs communicate with PPC and CPM only

5 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 DMCU common channel services (1/3)
• Common logical channels
• CCCH, BCCH, PCCH CELL
L3 (by DMX)
• Dedicated logical channels Common MAC-d
• DCCH, DTCH logical by DMX
channels
• only RACH/FACH mobile state PPC

• Common transport channels MAC-c (MCFTOR)

• RACH, FACH-c, FACH-u, PCH
DSP
• services are created when the CELL is
created FP

Dedicated
• services stay until CELL is not needed Common transport channels logical
anymore channels
base station (ATM AAL2)
• service parameters dont change often
• mobiles in RACH/FACH state can be added/removed
• services can be stopped (prohibit DL transfer)
• services can provide some indications of state to L3

6 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 DMCU common channel services (2/3)

• resource management:
• CELLs are “always” there, resources are not changed often

• control
• CELL parameters dont change often
• there are some control services that are needed during
some 3G transactions, like prohibit DL transfer for some
time (these are controlled by L3)

7 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 DMCU common channel services (3/3)

• data transfer
• transparent to the DMCU software
• many 3G transactions use data transfer via common
channels: paging, MTC/MOC calls etc.
• changing mobile states (Cell RACH/FACH, Cell PCH etc.)
also needs to configure MAC-c (MCFTOR), so data
transfers for the mobile can be scheduled
• there are some triggers: “no_data_indication” and
“capacity_request” (L3 then decides what to do if these are
received)

8 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 DMCU dedicated channel services (1/5)
SRB (SL, signalling link
• Logical channels to mobile, RRC
• DCCH (RLC UM, AM1-AM3)
connection)
• Transport channel
• DCH
L3 (by DMX)
MAC-c
Logical power by
• services are created when a call is channels control DMX

made up with mobile RLC (RFUTOR) OLFTOR

PPC

• services will be up until call ends, but

transport channels can change during DSP
the call (either DCHs or common MAC-d, OLPC, MDC, PC, FP
Dedicated
channels) channels in
Transport RACH/FACH
state
• services can be stopped (suspend) channels
base station (ATM AAL2)
• there are some indications of service
states to L3

9 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 DMCU dedicated channel services (2/5)
NRT RAB
• Logical channel
• DTCH
IP tunnel L3 (by
(ATM AAL5) DMX)
• Transport channel Logical power
• DCH channel control

PDCP (PJOTOR) MAC-c

by
• service is added (created) after SRB DMX

for the mobile exists RLC (RFUTOR) OLFTOR

PPC

• service will go to same PPC and DSP

as the SRB DSP
MAC-d, OLPC, MDC, PC, FP
• services can be released without Dedicated
channels in
releasing SRB Transport RACH/FACH
channels state
• the services can be stopped (suspend) base station (ATM AAL2)

• there are some indications of service

states to L3

10 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 DMCU dedicated channel services (3/5)
RT RAB
• Logical channel
• DTCH
RT data/speech L3 (by
(ATM AAL2) DMX)
• Transport channel Logical power
• DCH channel control

• service is added (created) after SRB

for the mobile exists OLFTOR
PPC

• service will go to same PPC and DSP

as the SRB DSP
MAC-d, OLPC, MDC, PC, FP
• services can be released without
releasing SRB Transport
channels
• the services can be stopped (suspend) base station (ATM AAL2)

• there are some indications of service

states to L3

11 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 DMCU dedicated channel services (4/5)

• resource management:
• need to allocate ATM connections, data buffers etc.
• NRT RAB and RT RAB services are linked to SRB service,
so they will be in same PPC and DSP

• control
• parameters are changed often
• there are some control services that are needed during
some 3G transactions, like suspend DL transfer for some
time (these are controlled by L3)

12 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 DMCU dedicated channel services (5/5)

• data transfer
• transparent to the DMCU software
• many 3G transactions use data transfer via SRB
• changing mobile states (Cell RACH/FACH, Cell PCH etc.)
also needs to configure MAC-d, so data transfers for the
mobile go through common channels
• there are some triggers: “no_data_indication”,
“capacity_request” and “buffers_full_status” (L3 then
decides what to do if these are received)

13 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 3G transaction example: DMCU view of
changing mobile to RACH/FACH state
• this is view what about happens
• start situation: there is SRB and and NRT RAB
1) there comes “no_data_indication” from MAC-d to L3
2) L3 stops data transfer with suspend commands to RLC
3) L3 configures MAC-c to handle the mobile
4) L3 configures MAC-d to know the MAC-c used
5) L3 configures the mobile to use RACH/FACH transport
6) L3 lets data transfer go again
7) L3 removes DCHs
• this causes maybe 100 messages to do, so details cannot be
presented here

14 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA

 Conclusion
• Main point: L3 controls the 3G transactions, uses services in
DMCU

• details of service interface can be found in interface documents

(one for PPC software and one for DSP software)
• the service functionalities would be in software architecture
document
• detailed functionality of services are described in SFS

15 © NOKIA 3g_transaction_dmcu.ppt/ 06.02.2003 / KHA