Sie sind auf Seite 1von 14

UMTS Technique Summary-Signaling Analysis

1. In Which Message, TMSI may be found? In RRC Connection Request Message sent by UE. The TMSI is 10 40 DB B1.

2. In Which Message, IMSI may be found? In RANAP Common ID sent by CN: IMSI '32009309000070F6'H is interpreted as follows: 230039900000076. Mapping relation: 32 00 93 09 00 00 70 F6 23 00 39 90 00 00 07 6F, F is not needed.

3. In Which Message, Propagation delay may be found?

4. What difference exists when RRC is set up on CCCH or DCCH? DCH and FACH Signaling difference : 1 FACH has no signaling from Radio Link Setup Request to ALCAP Iub data transport Bearer Setup. 2 RRC setup complete may be on RACH or DCCH(DCH 3.4k or DCH13.6K). 3 CCCH or FACH has no power control and DCCH has power control(channel equality may be better than DCCH).

5. From which command, we may know which RRC reasons are set up CCCH or DCCH? SET URRCESTCAUSE:RRCCAUSE=ORIGCONVCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=ORIGSTREAMCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=ORIGINTERCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=ORIGBKGCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=ORIGSUBSTRAFFCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=TERMCONVCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=TERMSTREAMCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=TERMINTERCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=TERMBKGCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=EMERGCALLEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; 3

SET URRCESTCAUSE:RRCCAUSE=INTERRATCELLRESELEST, SIGCHTYPE=DCH_3.4K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=INTERRATCELLCHGORDEREST, SIGCHTYPE=DCH_3.4K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=REGISTEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=DETACHEST, SIGCHTYPE=FACH, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=ORIGHIGHPRIORSIGEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=ORIGLOWPRIORSIGEST, SIGCHTYPE=FACH, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=CALLREEST, SIGCHTYPE=DCH_3.4K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=TERMHIGHPRIORSIGEST, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=TERMLOWPRIORSIGEST, SIGCHTYPE=FACH, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=TERMCAUSEUNKNOWN, SIGCHTYPE=DCH_13.6K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=MBMSCALLEST, SIGCHTYPE=DCH_3.4K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; SET URRCESTCAUSE:RRCCAUSE=DEFAULTEST, SIGCHTYPE=DCH_3.4K_SIGNALLING, INTRAMEASCTRL=SUPPORT, EFACHSWITCH=OFF; 6. Which procedure has something with different RRC reasons?
Table L.1.1/3GPP TS 24.008: Mapping of CS NAS procedure to establishment cause
CS NAS procedure Originating CS speech call Originating CS data call CS Emergency call Call re-establishment Location update IMSI Detach MO SMS via CS domain Supplementary Services Answer to circuit switched paging SS part of Location services RRC Establishment cause (according 3GPP TS 25.331) Originating Conversational Call Originating Conversational Call Emergency call Call re-establishment Registration Detach Originating Low Priority Signalling Originating High Priority Signalling Set equal to the value of the paging cause used in the reception of paging in the RRC layer Originating High Priority Signalling

When GMM requests the establishment of a PS signalling connection, the RRC establishmnt cause used by the MS shall be selected according to the PS NAS procedure as specified in Table L.1.2.
Table L.1.2/3GPP TS 24.008: Mapping of PS NAS procedure to establishment cause
PS NAS procedure GPRS Attach Routing Area Update for the case of Directed Signalling Connection Re-Establishment (see chapter 4.7.2.5.) Routing area Update all cases other than Directed Signalling Connection ReEstablishment GPRS Detach Request to re-establish RABs RRC Establishment cause (according 3GPP TS 25.331) Registration Call Re-Establishment

Registration

Detach Either Originating Conversational Call or Originating Streaming Call or Originating Interactive Call or Originating Background Call depending on the Traffic Class in QoS of the "most demanding" RAB. (see Note 1) Request to establish a PS MBMS reception or MBMS p-t-p RB request signalling connection for MBMS Activate PDP Context Either Originating Conversational Call or Originating Streaming Call or Originating Interactive Call or Originating Background Call depending on the Traffic Class in QoS of the "most demanding" RAB. (see Note 1) If Traffic Class in QoS is not Conversational Class or Streaming Class or Interactive Class or Background Class but is Subscribed Traffic Class, then Originating Subscribed traffic Call shall be used. Modify PDP Context Originating High Priority Signalling Deactivate PDP Context Originating High Priority Signalling MO SMS via PS domain Originating Low Priority Signalling SS part of Location Originating High Priority Signalling services Answer to packet paging Set equal to the value of the paging cause used in the reception of paging in the RRC layer NOTE 1: For classification of "most demanding" Traffic Class the following ranking order applies: "Conversational" followed by "Streaming" followed by "Interactive" followed by "Background", where "Conversational" is the most demanding Traffic class in terms of being delay sensitive. In chosing the "most demanding" Traffic Class all already active PDP Context together with the PDP Context to be activated shall be considered

NOTE:

The RRC establishment cause may be used by the network to prioritise the connection establishment request from the MS at high load situations in the network.

7. From which command, we may know UE status transition to FACH or PCH has happened? From RB RECFG message sent by RNC, you may know this.

8. In Which Message, RRC setup reason may be found? In RRC Connection Request Message sent by UE.

9. From Which timer, we may know how many times RRC setup may be resent and resent timer? SET UCONNMODETIMER:T302=D2000, N302=6, T304=D2000, N304=3, T305=D30, T307=D30, T308=D40, N308=1, T309=8, T312=6, N312=D1, T313=3, N313=D50, T314=D0, T315=D0, N315=D1, T316=D30, T381=D600, N381=D1; 10.In Which Message, we may know Iu User plane address allocated by CN? From RABAP Assignment Response Message: '00001010000101010111011000110010'B(0A 15 76 32) is interpreted as follows: 10.21.118.50.

11.In RRC Connection Request, how much is real value of IE Ec/Io? Ec/Ios real value is mapped into as follows: =( 44-49)/2=-2.5dB In fact if Ec/Io in RRC Connection Request is x, it should be (x-49)/2.

12. Do you know which signaling includes ARP information? ARP information is included in RAB Assignment Request Message.

13. For power CAC, whats difference between RRC phase and RAB phase? In RRC Phase, UlOlcTrigThd and DlOlcTrigThd are used. In RAB Phase, UlNonCtrlThdForHo, UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR, or UlNonCtrlThdForOther ; DlNonCtrlThdForHo, DlNonCtrlThdForAMR, DlNonCtrlThdForNonAMR, or DlNonCtrlThdForOther are used. 14. Which LDR actions exist aimed at different resources?

There are several attentions described in the above table. The Inter-RAT Handover in CS Domain action can be performed for the HSUPA services that are in the non-scheduling mode. The Inter-RAT Handover in CS Domain action can be performed for the HSDPA services only when the HsdpaCMPermissionInd parameter is set to TRUE. 9

If the downlink power-based admission uses the ENU algorithm, the basic congestion can also be caused by the ENU. In this situation, LDR actions do not involve AMR rate reduction or MBMS power reduction, as indicated by the symbol "*" in the preceding table. In the same environment, different rates have different downlink transmit powers. The higher the rate, the greater the downlink transmit power. Therefore, the load can be reduced by bandwidth reconfiguration. For HSUPA services, the CE consumption, which is calculated on the basis of the Maximum Bit Rate (MBR), can be reduced through rate downsizing. Therefore, the BE service rate downsizing for HSUPA is applicable only for reducing CE resource congestion. 15. System Information1 It includes NAS Information and UE Timers and constants idle mode and connected mode.

10

For timers and constant: Idle: T300/N300/T312/N312 Connected: T301/N301/T302/N302/T305/T307/T308/T309/T310/N310/T311/T312/N312/T31 3/N313/T314/T315/N315/T316/T317. 16. System Information2 It includes URA information.

11

17.System Information3 The system information block type 3 contains parameters for cell selection and re-selection. It includes main IE as follows: Cell identity Cell selection and reselection quality measure (CPICH Ec/N0,CPICH RSCP)) Sintrasearch/ Sintersearch/ Ssearch,RAT/SsearchHCS/ SHCS,RAT/ Slimit,SearchRAT/ Qqualmin/ Qrxlevmin/ DeltaQrxlevmin/ Qqualmin-offset/ Qrxlevmin-offset/ Qhyst1s/ Qhyst2s/ Treselections/ Maximum allowed UL TX power / Cell Access Restriction/ Cell barring representation/DSAC/ Domain Specific Access Restriction Parameters/ Intra-frequency reporting quantity SIB3 and so on. 18.System Information4 The system information block type 4 contains parameters for cell selection and re-selection to be used in connected mode.

19.System Information5 The system information block type 5 contains parameters for the configuration of the common physical channels in the cell. System information block type 5bis uses the same structure as System information block type 5. System information block type 5bis is sent instead of system information block type 5 in cells that use Band IV or Band IX or Band X. 12

It includes Primary Pilot Power/PICH Power offset /AICH Power offset/ PRACH system information list/ Secondary CCPCH system information. 20.System Information7 The system information block type 7 contains the fast changing parameters UL interference and Dynamic persistence level.

21.System Information11 The system information block type 11 contains measurement control information to be used in the cell.

13

It includes Intra-frequency cells/ Inter-frequency cell info list/ Inter-RAT cell info list. 22.System Information18 The System Information Block type 18 contains PLMN identities of neighbouring cells to be considered in idle mode as well as in connected mode.

14