Professional Documents
Culture Documents
21 PDFsam UMTS UTRAN Signaling Abstract
21 PDFsam UMTS UTRAN Signaling Abstract
Already the rrcConnectionRequest message contains the call establishment cause that indicates that
a MOC is started. Since in the call flow example there is still no dedicated control channel available
this first message is sent via Random Access Channel:
RACH: UL RLC TMD rrcConnectionRequest (IMSI or TMSI,
establishmentCause=originatingConversationalCall)
As in the procedures described before the NBAP is responsible for the radio link setup. However, this
time it will interesting to watch a little bit closer the downlink channelisation code and minimum uplink
channelisation code length as well as DCH-IDs:
NBAP DL initiatingMessage Id-radioLinkSetup (longTransActionID=c, id-CRNCCommunicationContextID=d, ULscramblingCode/DLchannelisationCode=b/, minULChCdLen=,
DCH-SpecificInformationList: DCH-ID=z, UL Transport Format Set, DL Transport Format Set)
|TS 25.433 V3.6.0 (2001-06) (NBAP)
|nbapPDU
|1 initiatingMessage
|1.1 procedureID
|00011011 |1.1.1 procedureCode
initiatingMessage (= initiatingMessage)
|id-radioLinkSetup
|
|
|
|
|
|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
|--110--- |1.5.1.2.3.2 minUL-ChannelisationCodeLength
|1068457
|long
|v256
|
|
|
|
|1.5.1.4.3.1.5.1 dCH-Specific-FDD-Item
|00011111 |1.5.1.4.3.1.5.1.1 dCH-ID
|31
|
|
|1.5.1.4.3.1.5.1.2 ul-TransportFormatSet
|1.5.1.4.3.1.5.1.2.1 dynamicParts
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|1.5.1.5.3.1.3.7 dl-CodeInformation
|
|1.5.1.5.3.1.3.7.1 fDD-DL-CodeInformationItem
|
|***b4*** |1.5.1.5.3.1.3.7.1.1 dl-ScramblingCode
|0
|
|***B2*** |1.5.1.5.3.1.3.7.1.2 fdd-DL-ChannelisationCo..|4
|
----------------------------------------------------------------------------------------------
Message Example 1-1: NBAP Radio Link Setup for voice call