Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
„<strong>UMTS</strong> <strong>Signaling</strong>“ – Abstract – Wiley & Sons, 2005 – ISBN 0-470-01351-6<br />
|**b136** |1.1.2 nas-Message |c4 40 01 69 10 80 e7 19 00 44 52... |<br />
|TS 24.008 Call Control V3.8.0 (CC-DMTAP) SETUP (= Setup) |<br />
|Setup |<br />
|----0011 |Protocol Discriminator |call control, call related SS messag|<br />
|-000---- |Transaction Id value (TIO) |TI value 0 |<br />
|CaLleD party BCD number |<br />
|01011110 |IE Name |CaLleD party BCD number |<br />
|00000111 |IE Length |7 |<br />
|----0000 |Number plan |Unknown |<br />
|-000---- |Type of number |Unknown |<br />
|1------- |Extension bit |No Extension |<br />
|**b44*** |Called party number |`0800123456` |<br />
|1111---- |Filler |15 |<br />
|Stream Identifier |<br />
|00101101 |IE Name |Stream Identifier |<br />
|00000001 |IE Length |1 |<br />
|00000001 |Stream Identifier |1 |<br />
----------------------------------------------------------------------------------------------<br />
Message Example 1-2: Call Control SETUP (MOC)<br />
In the message example it is further shown on which channels the message is transported. Physical<br />
transport bearer on Iub interface is an AAL2 SVC with VPI/VCI/CID = 10/26/183. On this physical<br />
transport bearer a dedicated (transport) channel (DCH) is running and because SETUP is a NAS<br />
signaling message it is carried by a logical DCCH with logical channel ID = 3, which is identical with<br />
signaling radio bearer ID = 3 (NAS signaling with high priority). The CN-DomainIdentity of RRC Uplink<br />
Direct Transfer message indicates that the message will be forwarded to CS core network domain<br />
represented by MSC (Rel. 99) or MSC Server (Rel. 4 and higher). Since type of number and number<br />
plan of called party number are unknown it is sure that the called party number string contains all<br />
digits as they have been dialed by subscriber.<br />
Reception of SETUP is answered by core network with<br />
DownlinkDirectTransfer CPROC – This message indicates that the call is being processed by core<br />
network entities. On UE side the call control state is changed when this message is received. With<br />
entering the new state it becomes impossible to send any additional dialing information.<br />
Now Radio Resources for dedicated traffic channels (DTCHs) need to be provided by (C)RNC. A<br />
dedicated physical channel in uplink and downlink direction already exists and it is identified by UL<br />
scrambling code number and DL channelisation code number. Hence, this channel needs to be<br />
reconfigured, because more data traffic between UE and network is expected when DTCHs are<br />
mapped on this physical channel. The higher the data transfer rate on radio interface is the lower must<br />
be the chosen spreading factor assigned with channelisation code. So a new downlink channelisation<br />
code with lower spreading factor than before is found in the Synchronized Radio Link Reconfiguration<br />
Preparation message as well as a new minimum uplink channelisation code length (minULChCdLen),<br />
which value is also smaller than in Radio Link Setup message before (λ
Change language