.

.

.

.

.

It is only read if the information changes 2. System Information (BCCH) The UE reads the System Information that is broadcast on BCCH. 9: RRC: RRC Connection Setup (CCCH) RRC Connection Setup message is sent on CCCH with the parameters required to establish DCH. Initial UE Identity and Establishment Cause 3. ALCAP: Establish REQ The AAL2 binding identity (Iub Data Transport Bearer Id) is passed to ALCAP protocol in Node B. TFS. UL Scrambling code. The information is not read continuously. 10: NBAP: Radio Link Restore Indication . The Iub Data Transport bearer is now bounf to DCH. 8: DCH-FP: Uplink Synchronisation Once the UL synchronisation is acheived. Also the state indicator will be set to DCH for the voice (or CS) call. RRC: RRC Connection Request (CCCH) The Mobile user decides to initiate a voice call. It will pass the Cell Id. frequency. While transmitting the response it includes the Transport layer addressing information that includes the Binding Identity of the AAL2 for Iub data transport bearer 5. The first message the UE will send on CCCH is RRC Connection Request. This will contain among other things. etc to Node B. 4. Node B starts DL transmission. NBAP: Radio Link Setup Response Node B allocates the resources and starts PHY Reception. ALCAP: Establish CNF Establish confirm from ALCAP in Node B 7: DCH-FP: Downlink Synchronisation The Node B and SRNC establishes synchronisation for the Iub Data Transport bearer by means of exchange of the appropriate DCH Frame Protocol frames.1. NBAP: Radio Link Setup Request The SRNC sends this message to Node B. TFCS. 6.

11: RRC: RRC Connection Setup Complete (DCCH) RRC Connection Setup complete will be sent on DCCH. For this reason it will challenge the UE with a Authentication token and RAND (random number) 15: RRC: Downlink Direct Transfer [Authentication Request] SRNC transfers the NAS message to the UE 16: RRC: Uplink Direct Transfer [Authentication Response] UE computes the response (RES) and sends it back in the NAS message 17: RANAP: Direct Transfer [Authentication Response] SRNC relays the response to the MSC/VLR. If they are the same then the procedure will continue. 14: RANAP: Direct Transfer [Authentication Request] MSC/VLR needs to perform authentication to make sure that the UE is genuine. 20: RRC: Security Mode Complete . It indicates that a UE orginated Voice call is required. 18: RANAP: Security Mode Command MSC/VLR sends the Security Mode Command to start Ciphering and Integrity Protection. The UE identity (TMSI) will also be passed in this message 13: RANAP: Initial UE Message [CM Service Request] The NAS message will be forwarded to appropriate CN Domain (CS Domain in this case). Node B will send RL Restore indication to the SRNC. etc are known to the MSC/VLR and the UE and only the ones that are common between them are used.Once the UE establishes Radio Link. Ciphering is optional while Integrity Protection is mandatory. Integrity and Ciphering related paarmeters and UE capability information will be sent back to SRNC 12: RRC: Initial Direct Transfer [CM Service Request] First NAS message is now sent by the UE. it will also include LAI and SAI. The Algorithms. 19: RRC: Security Mode Command RRC Forwards the Security Mode command received from MSC/VLR to the UE. Along with the CM service request. The MSC/VLR will compare the response RES with the expected response XRES.

23: RRC: DL Direct Transfer [TMSI Reallocation Command] The RNC relays the DT message to the UE. This will include all the required parameters for setting up the voice call. 24: RRC: UL Direct TRansfer [TMSI Reallocation Complete] The UE takes the new TMSI and responds with the Complete message 25: RANAP: Direct Transfer [TMSI Reallocation Complete] The RNC relays the message to the CN domain 26: RRC: UL Direct TRansfer [Setup] The UE now sends the 'Setup' message in UL Direct Transfer message. Since this is a Circuit switched call. It sends a DT message which includes the NAS TMSI Reallocation Command.The UE configures the Ciphering and Integity Protection and responds back to the network. It will include the number that UE wishes to be contacted and the bearer capability 27: RANAP: Direct TRansfer [Setup] The network relays the message to the MSC/VLR 28: RANAP: Direct TRansfer [Call Proceeding] The MSC/VLR sends Call Proceeding to the UE indicating that it is now starting with the RAB establishment procedure. 21: RANAP: Security Mode COmplete The network forwards the Security Mode Complete message to MSC/VLR. In case of AM and UM bearers it is started in RLC. the Ciphering will be started in MAC. 29: RRC: DL Direct TRansfer [Call Proceeding] The network relays it to the UE. The response message is Integrity Protected for further safety. 30: RANAP: RAB Assignment Request . 22: RANAP: Direct Transfer [TMSI Reallocation Command] The network may decide to re-allocate the TMSI to the UE. Ciphering is started at Ciphering activation time.

35: ALCAP: Establish REQ SRNC initiates setup of Iub Data Transport Bearer using ALCAP protocol. 34: NBAP: Radio Link Reconfiguration Ready Node B allocates the resources and responds with the Ready message. 38: DCH-FP: Uplink Synchronisation The Node B responds with the UE Synchronisation frames. It passes the TFS. The request contains the AAL2 Binding Identity to bind the Iub Data Transport Bearer to DCH. 31: ALCAP: Establish REQ SRNC initiates the set-up of Iu Data Transport bearer using ALCAP protocol. Iu Transport association.The CN initiates establishment of the Radio Access Bearer using the RAB Assignment Request message. 39: NBAP: Radio Link Reconfiguration Complete . the Transport Address. This message includes the QoS of the call being established. 36: ALCAP: Establish CNF The Node B responds with the Establish Confirm. (Note that this is not done in case of PS RAB) 32: ALCAP: Establish CNF The CN responds with the ALCAP Establish CNF 33: NBAP: Radio Link Reconfiguration Prepare SRNC requests Node B to prepare establishment of DCH to carry the RAB. TFCS and Power Control Informnation in the message. 37: DCH-FP: Downlink Synchronisation The Node B and SRNC establish synchronism for the Iub Data Transport Bearer by means of exchange of the appropriate DCH frame protocol frames. It sends back the AAL2 address and the AAL2 binding Id for the Iub data transport bearer. etc. The request contains the AAL2 Binding Identity to Bind the Iu Data Transport Bearer to the RAB. SRNC sends the DL Synchronisation frames.

46: RRC: Direct Transfer [Alert] The Alert message is forwarded to the UE. 48: RANAP: Direct Transfer [Connect] The MSC/VLR sends the Connect message to the SRNC via Direct Transfer message. This message contains the ACM received from the PSTN. The Connect message indictaes that the End User has answered the call. The message will be received using the old configuration. 40: RRC: Radio Bearer Setup SRNC sends the RB Setup message to add the new DCH's. . 41: RRC: Radio Bearer Setup Reponse After the activation time the UE will respond with complete message using the new configuration. 43: ISUP: Initial Address Message MSC/VLR sends the Initial Address Message to the PSTN. an Answer message is sent to the MSC/VLR. 44: ISUP: Address Complete Message The ACM message is sent to indicate that the remote end of the trunk circuit has been reserved.Finally the SRNC instructs the Node B of the CFN at which the new configuration will come into effect. 47: ISUP: Answer Message When the person that is being called picks up his phone. The Alert message will inditiate the ringing tone on the handset. The message tells the PSTN to reserve an idle trunk circuit from originating switch to the destination switch. 42: RANAP: RAB Assignment Reponse The SRNC responds with the response to the MSC/VLR. 45: RANAP: Direct Transfer [Alert] The Alert message is sent to the SRNC.

49: RRC: DL Direct Transfer [Connect] The SRNC forwards the Connect message to the UE. . 50: RRC: UL Direct Transfer [Connect Acknowledge] The UE confirms the reception of the Connect message using the Connect Acknowledge and sending it via Direct Transfer 51: RANAP: Direct Transfer [Connect Acknowledge] The Network forwards the Connect Acknowledge to the MSC/VLR. The call has now been successfully established.

:794/0.'#.3/90&.70.422.7/890$0.0.3/70.0/1742$.3/439043089.9.70:80/  ##$0.3/ ##47.:794/0422.42243-09003902.

'#9490&   ##$0.:794/0425090 .

 905073-089..0/.90/1471:79078.7/890$0.8041..790/.109 5073889.%0&.3/708543/8-.:989.3/&-0.943.0839079!7490.:794/0 25090 %030947147.431:708905073.9.949030947 %0 708543802088.0988.70789889.943920 $3.790/3 3 .790/3#  #!$0.:794/04250902088.094$..95073 ..7..3/3909!7490.

4.. 93.38107$09:5( %03094770.4../0.3/708543/89904250902088.03&70.3/  ##70.9%#.09490$.9%7.089030%$.3 ##&70.:/0890$%$#0.7.:/0.9%#.943425090( %0#70.943425090( %0&9.3/90-0..09490/42.9%7./09470 .20907814780993:590.4.09490&  ##&70.9090%$9490& 9803/8.3/( %0309472.707.38107$09:5( %0&34803/890 $09:5 2088.0.943422.9&80894-0 .'#  #!70.0. 3.38107%$#0.9%#.0 %83.3/( %0#70..4.90 706:70/5.9%7.4.38107%$#0.-9 #!70.0 #!70.38107%$#0..4.38107%$#0.8902088.439.9%7.890%2088..90/..943422..381072088.4.943422.8902088.%2088..:/0903:2-079.5.

38107.'# #!70.00/3( %0$.!74.9%#.

-82039574.9%#.00/39490&3/.'#803/8.899490&   #!#8832039#06:089 .38107.!74.00/3( %03094770.793990# 089..!74.0/:70  ##70.939.9983489.

385479-0.385479.3/708543/8990#0.-8#" $#39.304190.943425090 .-883./2088.90890809 :541:.431:7.908907084:7.%7.943 %04/0708543/8990&$3..943 17.943#0.385479//7088 : %7.439.707:8390#8832039#06:089 2088.431:7.//7088.707  !89.431:7.9.-8 %04/0708543/899089.94317.880890%$  %$.8041!$#  !89.0  !#.90 .385479-0.9017.7438214790:-.%039.9.3854790.7438./ 4/0.7438./43#0..7079490#  4909.7790# 95.3854790.9.-820394194.439.4 %0706:089.3841 0.-843172   !433$3.3/90-3/3/14790:-/.4 %0706:089 .208  !#.208   !&53$3.208 $#803/890$3.03..%7.707-20.943 09.70794  !89.707:83!57494.2057494.%7.-820394190#.908809:541:-.3/$#089.417./43#0.08.3854790...38903/3/0399943/90:..908089.3854790.-80/ 90%7.  !89.3/!40743974314723.9 988349/4303.-8 %0708543/8990!89.4.943!705.9.9.70 $#706:08984/0945705.7438.%7.70089.557457.943 %04/0.9.-8#" $#39.38 903/3/039994-3/90:-.9433902088.-8 !#.707:83!57494.%7.-03089.7438.0880.884./4.0 9803/8-.0 %82088../43#0.97.:/0890"4$4190..

0/:83 904/.98904/04190../40.9030.943  ###.4250902088.943  #!#8832039#054380 %0$#708543/8990708543809490$.431:7.094.431:7.3.94392090&708543/9.0.0:839030 ..0-070.943.9.//9030 8 %02088./40.431:7.9.707$09:5 $#803/890#$09:52088.420 3940110.707$09:5#054380 190790.90$#3897:.9   ###.

'#  $&!39.//7088088.0 $.

94389.  $&!//7088425090088.088039943/.9%7.389070.090890!$%94 70807..9389.0.909.:91742473.9090733943043 90.08147.//7088088.0/174290 !$%  ##70.09490!$% %02088.0 %02088.0/5.439.7/0/9490& %00792088.0.03/9.99070249003/419097:3.98-03.9%7.38107079( %00792088.7.8:585430 .7.3/097:3.'#803/89039.0880399490 $.:9.0.0/  #!70.0 03905078439.0880399490$# %82088.338072088.3/809  $&!3807088.38107079( %00792088..9490/0893.8-00370807.

9( %0$.'#  #!70.381074330.9%7.

92088...9%7.'#803/8904330.  .70.03/.8.381072088.09490$#.9.92088.38070/90.089.9903/&807.0 %0 4330.

9.9.9.7/8904330.09490&   ##&70.340/0.38107 #!70.381074330.##70.381074330.381074330.9%7.9%7.3/ 803/39.340/0( %0&.7/8904330..92088.0:83904330.340/09490$.9( %0$#147.9%7.4317289070.70.92088.340/0( %00947147.9.9%7.0594341904330.

834-003 8:.0881:089.-80/                    .'# %0....

   .

Sign up to vote on this title
UsefulNot useful