UMTS Signaling Abstract Wiley & Sons, 2005 ISBN 0-470-01351-6

|**b136** |1.1.2 nas-Message

|TS 24.008 Call Control V3.8.0 (CC-DMTAP)
|Setup
|----0011 |Protocol Discriminator
|-000---- |Transaction Id value (TIO)

|c4 40 01 69 10 80 e7 19 00 44 52... |
SETUP (= Setup)
|
|
|call control, call related SS messag|
|TI value 0
|

|CaLleD party BCD number

|
|01011110 |IE Name
|CaLleD party BCD number
|
|00000111 |IE Length
|7
|
|----0000 |Number plan
|Unknown
|
|-000---- |Type of number
|Unknown
|
|1------- |Extension bit
|No Extension
|
|**b44*** |Called party number
|`0800123456`
|
|1111---- |Filler
|15
|
|Stream Identifier
|
|00101101 |IE Name
|Stream Identifier
|
|00000001 |IE Length
|1
|
|00000001 |Stream Identifier
|1
|
----------------------------------------------------------------------------------------------

Message Example 1-2: Call Control SETUP (MOC)

In the message example it is further shown on which channels the message is transported. Physical
transport bearer on Iub interface is an AAL2 SVC with VPI/VCI/CID = 10/26/183. On this physical
transport bearer a dedicated (transport) channel (DCH) is running and because SETUP is a NAS
signaling message it is carried by a logical DCCH with logical channel ID = 3, which is identical with
signaling radio bearer ID = 3 (NAS signaling with high priority). The CN-DomainIdentity of RRC Uplink
Direct Transfer message indicates that the message will be forwarded to CS core network domain
represented by MSC (Rel. 99) or MSC Server (Rel. 4 and higher). Since type of number and number
plan of called party number are unknown it is sure that the called party number string contains all
digits as they have been dialed by subscriber.
Reception of SETUP is answered by core network with
DownlinkDirectTransfer CPROC This message indicates that the call is being processed by core
network entities. On UE side the call control state is changed when this message is received. With
entering the new state it becomes impossible to send any additional dialing information.
Now Radio Resources for dedicated traffic channels (DTCHs) need to be provided by (C)RNC. A
dedicated physical channel in uplink and downlink direction already exists and it is identified by UL
scrambling code number and DL channelisation code number. Hence, this channel needs to be
reconfigured, because more data traffic between UE and network is expected when DTCHs are
mapped on this physical channel. The higher the data transfer rate on radio interface is the lower must
be the chosen spreading factor assigned with channelisation code. So a new downlink channelisation
code with lower spreading factor than before is found in the Synchronized Radio Link Reconfiguration
Preparation message as well as a new minimum uplink channelisation code length (minULChCdLen),
which value is also smaller than in Radio Link Setup message before (<).
NBAP DL: initiatingMessage Id-synchronisedRadioLinkReconfigurationPreparation
(shortTransAction ID=j, NodeBCommunicationsContext-ID=p,
ULscramblingCode/DLchannelisationCode=b/, minULChCdLen=, Transport Format Sets of DCHs)
Please note in the message example that for the protocol tester decoder unit already the name of this
procedure code is too long to display it correctly, which is with no doubt one of the big disadvantages
of excessive ASN.1 PER usage.
|TS 25.433 V3.6.0 (2001-06) (NBAP)
|nbapPDU
|1 initiatingMessage
|1.1 procedureID
|00011111 |1.1.1 procedureCode

initiatingMessage (= initiatingMessage)

|1.5.1.2.3.1 ul-ScramblingCode
|***B3*** |1.5.1.2.3.1.1 uL-ScramblingCodeNumber
|1------- |1.5.1.2.3.1.2 uL-ScramblingCodeLength
|10011000 |1.5.1.2.3.2 ul-SIR-Target
|-100---- |1.5.1.2.3.3 minUL-ChannelisationCodeLength
|1.5.1.4.3.1.5 dCH-SpecificInformationList

|
|
|
|
|id-synchronisedRadioLinkReconfigurat|

|1068457
|long
|70
|v64

|
|
|
|
|
|

UMTS Signaling Abstract Wiley & Sons, 2005 ISBN 0-470-01351-6