3G Intro & Events

Slide 1

Introductions of UMTS Architecture,Call Flow Procedures and 3G EVENTS

UMTS Architecture

UMTS Network Architecture

UEUTRAN (UMTS Terrestrial Radio Access Network)CN (Core Network)

User Equipment (UE)- It allows the user to access the to network .For the purpose the interface between the UE and the network is the radio interface. The UE consist of 1.Mobile Equipment(ME) 2.U-SIM)UTRAN (UMTS Terrestrial Radio Access Network)- is a collective term for the network and equipment that connects mobile handsets to the public telephone network or the Internet. It contains the base stations, which are called Node Bs and Radio Network Controllers (RNC) which make up the UMTS radio access network.

Core Network (CN)- a telecommunication network's core part, which offers numerous services to the customers who are interconnected by the access network. Its key function is to direct telephone calls over the public-switched telephone network. Sometimes other called the Backbone of the network. And it is contains important elements which Circuit Switched CS and Packet Switched PS (i.e. GPRS) domain.The Core Network Contains important Elements:-Mobile Service Switching Center (MSC)-Gateway Mobile Service Switching Center (GMSC)-Visitor Location Register (VLR) -Home Location Register (HLR)-Authentication Center (AuC)-Equipment Identity Register(EIR)-Serving GPRS Support Node (SGSN)-Gateway GPPRS Support Node (GGSN)With UTRAN we had Four Interfaces:- Iu- Iub- Iur- Uu

RRC,RB ProceduresMapping of UE State

RRC Modes

RRC Tasks and Functions

The RRC Protocol is the application part of the UMTS radio access technology .The RRC has following functions:-broadcasting of system information for NAS stratum -Establishment, maintenance and release of RRC signaling between UE and the UTRAN connections-RRC connections mobility functions-Quality of service (QoS) Control-UE measurements reports-outer loop power control-security control-paging-initial cell selection and reselection-transport of NAS control messages.

Usage of Radio Bearer by the RRC protocol

-It means the RRC protocol uses the radio bearer service by the Layer 1 and Layer 2 of the UMTS radio interface. And we had the RB numbered to 0 to 31 .

RRC Idle Mode-When a UE is switched On ,it enters the RRC Idle mode .In the RRC mode ,threes no connection on the access stratum level between the UE and the UTRAN.The UTRAN has no information about UEs in the RRC idle mode .if the UTRAN wants to address the UE ,it must use non-access stratum (NAS) identifier . RRC Connected Mode-Can be further decomposed into four different states, on which level the UE is known by UTRAN and which resources are allocated by the UE ,UTRAN can know any UE either on cell level or on URA Level. On the other hand any UE can determine DCH or FACH /non transport channel for control message exchange.

In DCH state UE perform following action :-read system in information broadcast on FACH-perform measurements process according to measurement control information

In FACH state UE perform following action : (if in Service area)-DCCH and DTCH are available-perform cell reselection-perform measurements process according to measurements control information-run timer T305 (periodical cell update)-listen to all FACH transport channels mapped In FACH state UE perform following action : (if in Out of Service area)perform cell reselectionRun timers T305 & T317( cell update when re-entering in service area ) /T307(transition to idle mode)

In PCH State UE perform following action: (if in Service area)-maintain up to date system information as broadcast by the serving cell perform cell reselectionPerform a periodic search for higher priority Monitor the paging occasion according to the DRX cycle and receive paging information on the PCH In PCH State UE perform following action: (if in Out of Service area)perform cell reselection process Run timer T316Run timer T305

RRC Procedures

-Between the UE and the RNC ,the RRC protocol is used to exchange signaling and control data to establish ,maintain, and release connections. The UE gets informed about the radio bearer characteristics to the transport channel configurations and the physical layer settings. With that the UE knows how to receive and transmit data via WCDMA radio interface.

RRC Connection Establishment-The purpose of the RRC Connection Establishment procedure is to create a RRC connection between the UE and the UTRAN

1.RRC Connection Request Message

-it is initiated by the UE and transmitted via uplink

2.RRC Connection Setup Message.

-if the RNC accepts the UE RRC Connection Establishment request .It Starts an interaction with the Node B to establish radio link connection over the interface Iub, this used to inform the Node B about the radio link configurations for uplink and downlink interface. it means the Node b preparedto serve mode between the UE and the RNC.

3.RRC Connection Setup Complete Message.-The UE received the RRC Connection Setup Message and returns the RRC Connection Setup Complete Messaged the RNC This message is transmitted via the logical channel DCCH on the radio signaling bearer.

Radio Bearer (RB) Procedures-The RB control procedures are used to establish additional radio bearers ,modify them, or release them.

Radio Bearer is established ,modified and released with following RRC messages:

-Radio Bearer Setup-Radio Bearer Reconfiguration -Radio Bearer Release-Transport Channel Reconfiguration-Physical Channel Reconfiguration

Call Flow

Call Flow Chart Procedure (MTC,MOC,HSDPA,HSUPA)

MOCMTC

EVENTS

DROp due to poor RF conditions

There is a short MOC drop due to poor RF conditions.

SNJNPRU0751 doesnt have a 3rd carrier. The coverage on 850 band is good but it cannot make an IFHO because it is band locked to 1900MHz band.

Also, the handover type for PRSJU3143 is 2(none).

Drop due to poor rf conditions

Drop is due to poor RF conditions.

Call drop due to challenging terrain (see next slide).

Call DropTerrain for HSDPA drop

drop due to 25 secs of missing messages

25 seconds of missing messages.

Call dropped due to missing neighbor.

Neighbor Recommendation:GAATU61399 (SC383,UARFCN=412) ->GAATU61402 (SC399,UARFCN=1087).

Loss of synchronization

There is a Loss of synchronization between the base station and the UE.

UE is continuously trying to add PRSJU32019 (SC 337) in its active set (It is verified that it is defined as the neighbor of PRSJU32018( SC312)).

7 seconds of missing messages

There are 7 seconds of missing messages.

Due to missing neighbour

Cells in detected neighbor list have better EcNo and RSCP than cells in AS. Event e1a is continuously triggered to add SC391 but it is not a defined neighbor. UE is entering a new cell(SC391) and causing UL interference to the other UEs connected to this cell. Thus, Call is released in the downlink.Neighbor recommendation (Intra frequency):SNJNPRU07717 (SC217)-> SNJNPRU02458 (SC391).

Due to missing neighbour

The drop is due to poor RF conditions in UARFCN=412 (1900 band) and missing neighbor.

Neighbor recommendation: GAATU23599 (SC=263, UARFCN=412)->GAATU23501 (SC=483, UARFCN=1087).

Due to too many servers

EUL drop is due to too many servers with no dominant server available.

Recommendation:Electrical uptilt of GAATU23503 by 2 degree.

Pilot Pollution

Measurement control failure

EUL drop occurs due to measurement control failure.

In downlink, UE is asked to measure UARFCN=412, but it fails to perform it.

As UARFCN 412 is the 4th carrier which corresponds to femto cells, but UE has the limitation of measuring only 3 frequencies.

Normal release (rrc req. for registration)

The RRC request is for the purpose of registration.

Normal release is being pegged as an access failure in Actix.

App drop due to winsock error

HSDPA application drop is due to Winsock error as no route is found from server to client.

The application drop is occurring when the UE is latched to UARFCN=437.

app. download time ERROR

App. DL ThroughputTech Mode

Application download time exceeds 120 seconds because of a continuous low throughput.

UE is in GSM mode for most of the time because GAATU6140 is a border site and it is GSM preferred.

moc access failure

Normal release is being pegged as an access failure by Actix.

It took place due to a change from UMTS to GSM mode at MT end due to high qRxlevmin.

At the MT end, location update of GSM mode was not yet completed, thats why it couldnt respond to any incoming MO call.

MTC Tech Mode

MTC Protocol stack browserMOC Protocol stack browserMOC RSCP

MOC Protocol stack browser

Mtc Access failure


Call terminated at the end of the log file.

MTC AF # 2

Core network releases access failure as a normal event.In paging, IMSI is paged instead of TMSI.

CS Long access failure


This access failure occurs due to unavailability of resources.

Cs long call drop

Call drop occurs on UARFCN=437.

Poor RSCP and EcNo.

Multiple events 1a are triggered but can not be executed.

HSDPA drop *

Multiple cell update messages sent in uplink but there is no cell update confirm message in downlink.Timers t314 and t315 expire during Cell update (uplink) in the cell_FACH state, hence goes to idle state.

HSDPA DROP (Physical channel reconfiguration failure)

After active set update is complete, in DL Measurement control message, it asks for Intra frequency measurement ,but in physical channel reconfiguration message the RNC is giving freq. info corresponding to UARFCN=4384.As UE is locked to 1900 band, it can not measure UARFCN=4384 resulting in physical channel reconfiguration failure.

HSDPA drop

HSDPA drop occurred due to temporary UE issue.

There were many RRC Connection setups in the DL in between an ongoing call.

It was in FACH state for a long time, so RRC connection was released.

EUL Drop

The EUL drop is occurring in good RF conditions.

Validation of drive is required.

EUL DROP

Event is falsely pegged by actix as a EUL drop. Here, a new RRC connection request is detected as a drop by Actix as previous RRC connection was not released.

RRC connection request is for an interactive call to continue the FTP file transfer session of the previous EUL call.

41SSV of GAATU2350 for 1st carrier(850 band, UARFCN=1087)

This is a case where we approximately analyzed about what could have happened.

Here, due to inactivity downswitch from cell_DCH to cell_FACH occurs. After few seconds FTP application asks user whether he wants to continue FTP or not, for that we have a RRC connection request for interactive call. As previous RRC connection was not released, so on getting a new request Actix assumes that previous call is dropped as it didnt come across any RRC connection release.

UE drops to idle from FACH since it was unable to perform CellUpdate (t314,t315 expired).

Eul drop Analysis:Temporary network issue.

There is a paging type 2 message for terminating the background call during the current ongoing call which was responded to by UE.

Eul APP. UPLOAD TIME error

App. UL Throughput

Application upload exceeds 120 seconds due to poor uplink throughput.

Poor uplink throughput is due to missing neighbor.

Neighbor recommendation: GAATU23599 (SC=263, UARFCN=412)->GAATU23501 (SC=483, UARFCN=1087).

Eul irat ho failIRAT HO failed due to physical channel failure.

Missing neighbor.

Neighbor recommendation: GAATU23662(SC 327, UARFCN=1087)-> GA6139A (ARFCN=246),

GAATU61397(SC 367, UARFCN=1087)-> GA6139A (ARFCN=246).

Example Voice Call Flow (MOC) in Actix

Call Setup Phase

KPIs: Call Setup Success RateCall Setup Time

Total Call Time

KPIs: Dropped CallRRC Connection is released after the Call Release.

Connection released due to SP processing failure on Rrc Rb while ILU15998 (346) was the only cell in the AS.CS Drop Call Example of UE Exceptions Actix View

Lack of dominant server around W Irving Park Rd. ILU13119 (211), ILU13118 (203), ILU15937 (314), ILU15407 (266) and ILU36139 (402) signals measured similarly within the area. ILU01819 (90) doesn't pollute the area after recommended tilt change was executed.-----------------------------------------------------------------------------------------------------------------------------Recommended are upgrade of interim micro RBS solution to macro for ILU15937, and change of ILU36139 (402) and ILU15407 (266) electrical tilt.

Drop Call Example of No Dominant Server Actix View

RSCP and Ec/No deteriorated instantly at W Lawrence Ave after sudden drop in ILU16128 (395) RSCP and Ec/No which remained the only cell in the AS. UE sent number of e1a measurement reports for adding ILU13128 (227) to the AS but couldn't receive ASU due to bad Ec/No in downlink.Drop Call Example of T-ASU Timer expiry Actix View Continue To Next Slide

Lack of dominant server around Central Rd south of ILU1339. Large area missing UMTS sites. ILU14059 (357), ILU02249 (116), ILU13398 (204), ILU14057 (341), ILU04637 (125), ILU00368 (12) and ILU14077 (389) signals measured similarly within the area. After started call setup on ILU00368 (12) UE sent number of e1a measurement reports but couldn't get ASU due to bad Ec/No in downlink so finally UTRAN released connection after T_RABEST_1 timer expiry.Setup Failure Example due to T_RABEST_1 Timer Expiry

Setup Failure Example of N300 Timer Expiry Actix View

Example PS R99 Call FlowUERNCRRC: RRC Connection Request (CCCH)

RRC: RRC Connection Setup (CCCH)

RRC: RRC Connection Setup Complete (DCCH)

RRC: Initial Direct Transfer - CM Service Request (DCCH)

RRC: Downlink Direct Transfer Auth & Ciph Request (DCCH)

RRC: Uplink Direct Transfer - Auth & Ciph Response (DCCH)

RRC: Security Mode Command (DCCH)

RRC: Security Mode Complete (DCCH)

RRC: Uplink Direct Transfer SM ACTIVATE PDP CONTEXT REQUEST (DCCH)

RRC: Radio Bearer Setup (DCCH)

RRC: Downlink Direct Transfer SM ACTIVATE PDP CONTEXT ACCEPT (DCCH)

RRC: Radio Bearer Setup Complete (DCCH)

RRC: Measurement Control (DCCH)

RRC: Measurement Report (DCCH)

RRC: Uplink Direct Transfer SM Deactivate PDP Context Request (DCCH)

RRC: Direct Transfer SM Deactivate PDP Context Accept (DCCH)

RRC: RRC Connection Release (DCCH)

Call Setup Phase

KPIs: Call Setup Success RateCall Setup Time

Total Call Time

KPIs: Dropped CallRRC: Transport Channel Reconfiguration (DCCH)

RRC: Transport Channel Reconfiguration Complete (DCCH)

Channel Switching

Example PS R99 Call Flow in Actix

Call Setup PhaseKPIs: Call Setup Success RateCall Setup Time

Total Call Time

KPIs: Dropped Call

PS R99 Drops-1 UE reselected cell from different RA after Radio bearer was reconfigured to Cell_FACH. Connection was released with directed signalling connection re_establishment cause.

RRC Connection Rejection because of Congestion

Example PS R99 Call Flow in Actix

Call Setup PhaseKPIs: Call Setup Success RateCall Setup Time

Total Call Time

KPIs: Dropped Call

Channel SwitchingChannel Switching

Example PS R99 (Channel Switching-1) in Actix

RNC sent Transport channel Reconfiguration messageTo upswitch from 64k to 128k.

HSDPA Call FlowUERNCRRC: RRC Connection Request (CCCH)

RRC: RRC Connection Setup (CCCH)

RRC: RRC Connection Setup Complete (DCCH)

RRC: Uplink Direct Transfer SM ACTIVATE PDP CONTEXT REQUEST (DCCH)

RRC: Downlink Direct Transfer SM ACTIVATE PDP CONTEXT ACCEPT (DCCH)

RRC: Measurement Report (e1a) (DCCH)

RRC: Active Set Update (DCCH)

RRC: Active Set Update Complete (DCCH)

RRC: Physical Channel Reconfiguration (DCCH)

RRC: Physical Channel Reconfiguration Complete (DCCH)

E1A:Radio Link AdditionNot a HS Cell Change. Here the procedure is to realign the parameters.RRC: Measurement Report (e1d) (DCCH)

RRC: Active Set Update (DCCH)

RRC: Active Set Update Complete (DCCH)

RRC: Physical Channel Reconfiguration (DCCH)

RRC: Physical Channel Reconfiguration Complete (DCCH)

E1D:Change of Best ServerHS Cell Change

KPIHS Cell Change Success RateHS Cell Change time

KPICall Setup Success RateCall Setup Time

Example HSDPA Layer 3 Messages

KPICall Setup Success RateCall Setup Time

KPIHS Cell Change Success RateHS Cell Change timeE1A:Radio Link AdditionNot a HS Cell Change. Here the procedure is to realign the parameters.E1D:Change of Best ServerHS Cell Change

Example HSDPA in Actix

IRAT-CS Handover Passed Actix View with explanation

IRAT-PS Handover Passed Actix View with explanation

IRAT-PS Handover Passed Actix View

IRAT-HSDPA handover failed.

IRAT-HSDPA handover failed.

Pilot Pollution analysis

6.4 mi

5.6 mi

Strong radiation perpendicular to beam direction

Recommendation:

Increase Electrical tilt of TXV40066(SC184) and TXV40715(SC000) from 0 to 3.

Verify the azimuth of TXU60426.

PointersPointers:Always mark your own site for which analysis is being performed.Legends for RSCP & EcIo are common for all markets. Please do a small check if your legends match the usual scale & colors.Individual RSCP Plot for tilt recommendations is compulsory. And circle the SC which needs the tilt in the plot.Issues in cellref will always be present since it relies on RNDCIQ. But please be prepared to correct the CellRef according to 1.Previous market report.2. Scanner SC plot requirements.3. Showing different SC sectors.4. Multiple carriers with different SC. Arrange drops of all the UEs (especially MOC & MTC) in similar fashion ( clockwise or counterclockwise) so that it easy to correspond the location of the drops.

EUL(Enhanced Uplink) Throughput (as has been mentioned multiple times ) should be RLC_AM_Thput_3 and for TEMS log files - HSUPA Throughput.

If there are several sites off-air in your UARFCN, show a slide just after summary slide showing the same.

Google Earth view should have line of sight, terrain height of site location, terrain height of drop location.

Missing messages need not be mentioned unless that is the only observation in your event. IN poor RF cases, you might not receive messages due to high path loss on the DL. So the problem is poor RF, not missing messages (IN short, dont overuse it).

PointersAnalysis of MOC & MTC events :

As much as possible, try to analyze in parallel, having both MOC & MTC stack browsers. (TEMS logfiles might have time offset between MOC & MTC) . With CC Disconnect messages show the Cause in your snapshot.

While giving tilts observe the impact of your recommendation -Which is the most suitable of many candidates to tilt? Is this Pollution because of main lobe, side lobe or reflection ? Will tilt recommendation remove reflection ? For side lobe, should I recommend E or Mech tilt ? Where should I get the tilt information from?If tilts won't help, are there other options (HOtype ,e2d changes, CPICH power etc)

Inferring from Plots/ GnG Report:

This REALLY can save you lot of time , to identify & focus on major issue-areas and for better grouping. This is the area where you need to improve for growing into RF engineers and not just SSV engineers.ALWAYS send the GnG report to the core as soon as you create the repository. They might catch stuff that needs analysis that you may miss.

Grouping events:

Group wisely and precisely. If the reasons are similar especially Poor RF cases) but if they fall in different locations, then you might have different recommendations, so group accordingly. But use this for the remaining devices. Identify the number of UNIQUE events (events that cannot be reused from a previous device analysis) and plan you time accordingly.

THANK YOU

AMR(MOC)

RRC Connection Set up procedure is performed for the UE to set up a signaling connection to the RNC.RRC Connection Setup is always initiated by the UE. One UE has a maximum of one RRC connection at a time .

Triggering Condition The UE in idle mode initiates the RRC connection set up procedure when the NAS of the UE Request the establishment of signaling connection. When the RNC receives an RRC CONNECTION REQUEST message fromThe UE the Radio Resource Management(RRM) module of the RNC determines whether to accept or reject the RRC connection request ,based on the specific algorithm. If accepting the request the RMM module further determines whether to setup The RRC connection on a Dedicated Channel(DCH) or Common Channel (CCH) based on the specific RRM algorithm .typically An RRC connection is setup on the DCH

The Signaling connection Setup Procedure is performed to exchange the NAS(Non-Access Stratum) information between the UE & the Core Network (CN).

Triggering Condition The UE sends direct transfer message to initiate the signaling connection setup procedure.The Authentication & Security mode control procedure is performed for the UE and the network to implement bi-directional Authentication and negotiate and configure the integrity protection algorithm and ciphering algorithm. this procedure ensures Integrity and correctness of signaling.

Triggering Condition The UE and CN exchange signaling. The Network initiates the authentication and security mode control Procedure.The Call Set up Procedure is performed to set a call

Triggering Condition The UE initiates a Call.The Call Release Procedure is performed to release services and resources after a call ends.

Triggering Condition A call ends and the calling party hang ups.RRC Connection Release Procedure is performed to release signaling connection and all radio bearers between UEAnd the UTRAN.

Triggering Condition After the RAB is release the RNC judge whether the RRC connection carries any other RAB or the UE.If judging the RRC connection does not carry other RAB of the UE the RNC initiates as a RRC connection release procedure.

AMR(MOC MSG)

RRC:RRC Connection Request (RACH)>>"RRC Connection Request Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01value=hex2dec(2908)= 10504value= OriginatingConversationalcall (CS MOC)

value=(-24+ (43/2))=-2.5 dBvalue=hex2dec(60)=96(Neighbour's Primary Scrambling Code)value=CPICH Ec/Io invalid

RRC:RRC Connection Setup (FACH)>>"RRC Connection Setup Description"

>>"Geographical and UTRAN Entity Identifiers"value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01value=hex2dec(2908)= 10504value=UE capable to support FDD , not TDDvalue=UE capable to support GSM

value=Signaling Radio Bearer Information Setup ,RB-1value=Radio Bearer Mappingvalue=Signaling Radio Bearer Information Setup ,RB-2

value=Signaling Radio Bearer Information Setup ,RB-3


value=BLER Target= -20 dB

value=MaxAllowedULTxPower=24 dBm

value=(-47*2)= -94 dBm (step of 2 dB)Default Constant DPCCH_Power_offsetCPICH_RSCPPCPICH PowerUL InterferenceUL DPCCH Initial Power-22-94-8033-105-14-22-94-7033-105-24Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.

value= use Closed Loop Power Control Algorithm1

value= use long SC on Uplink

value=Spreading Factor 64 (Uplink)

value=Spreading Factor 128 (Downlink)

value=Primary Scrambling code=97


Cell Identity=RNCid(12bits)+Cellid(16bits)value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610

RRC:RRC Connection Setup Complete (DCCH)>>"RRC Connection Setup Complete Description"

value= not support GSM (Locked UMTS Mode)

value= Chipering Algorithm A5/3value= UE support Band fdd2100 MHzvalue= UE (Powerclass3) maximum transmitted power =24 dBmvalue= support Compressed Mode (CM) uplink and downlinkvalue= UE support Band fdd1800 MHz

RRC: Initial Direct Transfer (MM: CM Service Request)

RANAP:Initial UE Message (MM: CM Service Request)

RANAP: Direct Transfer (MM: Authentication Request)

RRC: Downlink Direct Transfer (MM: Authentication Request)

RRC: Uplink Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (MM: Authentication Response)

RRC: Security Mode Command

RRC: Security Mode Complete

RANAP: Direct Transfer (CC: Setup)

value= Call B-Party number = 0812713339

RRC: Uplink Direct Transfer (CC: Setup)

RRC: Downlink Direct Transfer (CC: Call Proceeding)

RANAP: Direct Transfer (CC: Call Proceeding)

RRC: Radio Bearer Setup>>"Radio Bearer Description"

value= SF64(uplink)-> AMR 12.2


value= SF128(downlink)-> AMR 12.2


RRC: Radio Bearer Setup CompleteClick to return to main page

RANAP: Direct Transfer (CC: Alerting)Click to return to main page

RRC: Downlink Direct Transfer (CC: Alerting)Click to return to main page

RANAP: Direct Transfer (CC: Connect)Click to return to main page

RRC: Downlink Direct Transfer (CC: Connect)Click to return to main page

RANAP: Direct Transfer (CC: Connect Acknowledge)Click to return to main page

RRC: Uplink Direct Transfer (CC: Connect Acknowledge)Click to return to main page

RANAP: Direct Transfer (CC: Disconnect)Click to return to main page

RRC: Uplink Direct Transfer (CC: Disconnect)Click to return to main page

RANAP: Direct Transfer (CC: Release)Click to return to main page

RRC: Downlink Direct Transfer (CC: Release)Click to return to main page

RANAP: Direct Transfer (CC: Release Complete)Click to return to main page

RRC: Uplink Direct Transfer (CC: Release Complete)Click to return to main page

RRC: Downlink Direct Transfer (CC: RRC Connection Release)Click to return to main page

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)Click to return to main page

AMR(MTC)

Paging Procedure is performed when the CN calls a UE.

Triggering Condition A terminals call the UE.RRC Connection Set up procedure is performed for the UE to set up a signaling connection to the RNC.RRC Connection Setup is always initiated by the UE. One UE has a maximum of one RRC connection at a time .


The Signaling connection Setup Procedure is performed to exchange the NAS(Non-Access Stratum) information between the UE & the Core Network (CN).

Triggering Condition The UE sends direct transfer message to initiate the signaling connection setup procedure.The Authentication & Security mode control procedure is performed for the UE and the network to implement bi-directional Authentication and negotiate and configure the integrity protection algorithm and ciphering algorithm. this procedure ensures Integrity and correctness of signaling.

Triggering Condition The UE and CN exchange signaling. The Network initiates the authentication and security mode control Procedure.The Call Set up Procedure is performed to set a call

Triggering Condition The UE initiates a Call.The Call Release Procedure is performed to release services and resources after a call ends.

Triggering Condition A call ends and the calling party hang ups.RRC Connection Release Procedure is performed to release signaling connection and all radio bearers between UEAnd the UTRAN.


AMR(MTC MSG)

RRC: Paging Type 1

RRC: RRC Connection Request (RACH)>>"RRC Connection Request Description"



value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01value=hex2dec(2908)= 10504

value= terminatingConversationalcall (CS MTC)value=(-24+ (44/2))=-2.0 dB

value=hex2dec(6d)=109(Neighbour's Primary Scrambling Code)value=CPICH Ec/Io invalid

RRC: RRC Connection Setup (FACH)>>"RRC Connection Setup Description"

>>"Geographical and UTRAN Entity Identifiers"value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01value=hex2dec(2908)= 10504value=UE capable to support FDD , not TDDvalue=UE capable to support GSM

value=Signaling Radio Bearer Information Setup ,RB-1value=Radio Bearer Mappingvalue=Signaling Radio Bearer Information Setup ,RB-2value=Signaling Radio Bearer Information Setup ,RB-3value=Signaling Radio Bearer Information Setup ,RB-4value=BLER Target= -20 dBvalue=MaxAllowedULTxPower=24 dBm

value=(-48*2)= -96 dBm (step of 2 dB)Default Constant DPCCH_Power_offsetCPICH_RSCPPCPICH PowerUL InterferenceUL DPCCH Initial Power-22-96-8033-107-16-22-96-7033-107-26value= use Closed Loop Power Control Algorithm1Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.

value= use long SC on Uplinkvalue=Spreading Factor 64 (Uplink)

value=Spreading Factor 128 (Downlink)value=Primary Scrambling code=97value=Spreading Factor 128 (Downlink)Cell Identity=RNCid(12bits)+Cellid(16bits)value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610


value= not support GSM (Locked UMTS Mode)value= Chipering Algorithm A5/3value= UE support Band fdd2100 MHzvalue= UE (Powerclass3) maximum transmitted power =24 dBmvalue= support Compressed Mode (CM) uplink and downlink

RANAP: Initial UE Message (MM: Paging Response)

RRC: Initial Direct Transfer (MM: Paging Response)



RRC: Downlink Direct Transfer (CC: Setup)

RANAP: Direct Transfer (CC: Setup)value= Call B-Party number = 0813713339

RANAP: Direct Transfer (CC: Call Confirmed)

RRC: Uplink Direct Transfer (CC: Call Confirmed)

RRC: Radio Bearer Setup>>"Radio Bearer Description"

value= SF64(uplink)-> AMR 12.2value=Primary Scrambling code=97value= SF128(downlink)-> AMR 12.2Cell Identity=RNCid(12bits)+Cellid(16bits)value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610

RRC: Radio Bearer Setup Complete

RANAP: Direct Transfer (CC: Alerting)

RRC: Uplink Direct Transfer (CC: Alerting)

RANAP: Direct Transfer (CC: Connect)

RRC: Uplink Direct Transfer (CC: Connect)

RANAP: Direct Transfer (CC: Connect Acknowledge)

RRC:Downlink Direct Transfer (CC: Connect Acknowledge)

RANAP: Direct Transfer (MM: Authentication Request)

RRC: Downlink Direct Transfer (MM: Authentication Request)

RRC: Uplink Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (CC: Disconnect)

RRC: Downlink Direct Transfer (CC: Disconnect)

RRC: Uplink Direct Transfer (CC: Release)

RANAP: Direct Transfer (CC: Release)

RANAP: Direct Transfer (CC: Release Complete)

RRC: Uplink Direct Transfer (CC: Release Complete)

RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release)

PS-HSDPA



The PS Session Setup is performed to set up a PS session

Triggering Condition The UE sends activate PDP context request message to RNC .PDP context activation is performedWhen the UE initiates a packet call setup. The UE has the state packet mobility management connected that enable the user To transmit and receive data while moving within a PLMN and starts the PDP context activation procedure used to setupAnd remove a virtual data channel between a terminal connected to UE and GGSN.The PS session release procedure is performed to release services after a session ends.

Triggering Conditions The UE send Deactivate PDP Context request message to RNC.A PDP Context Deactivation is performed when UE terminates a packet call. Before the deactivation ,the UE has the state active. after the PDP context deactivation procedure the state becomes Packet mobility management connected. The RAB will be released if there area no other PDP context activated.PDP deactivation maybe initiated by a :UE procedure ,SGSN procedure,GGSN procedure.

RRC Connection Release Procedure is performed to release signaling connection and all radio bearers between UEAnd the UTRAN.


PS-HSDPA MSG




value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01value=hex2dec(7594)= 30100value= OriginatingBackgroundCall (PS MOC)

value=(-24+ (37/2))=-5.5 dBvalue= HSDPA Release5


>>"Geographical and UTRAN Entity Identifiers"value=hex2dec(4)=4 , hex2dec(1)=1 ,hex2dec(3)=3 --> MCC=413

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01value=hex2dec(7594)= 30100value=UE capable to support FDD , not TDDvalue=UE capable to support GSM

value=Signaling Radio Bearer Information Setup ,RB-1value=Radio Bearer Mappingvalue=Signaling Radio Bearer Information Setup ,RB-2





value=(-48*2)= -96 dBm (step of 2 dB)Default Constant DPCCH_Power_offsetCPICH_RSCPPCPICH PowerUL InterferenceUL DPCCH Initial Power-22-96-8033-107-16-22-96-7033-107-26Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup. value= use Closed Loop Power Control Algorithm1








value=support GSM (Dual Mode GSMUMTS)value= Chipering Algorithm A5/3value= support Compressed Mode (CM) uplink and downlink

value= support HSDPA, UE Category 6

RRC: Initial Direct Transfer (GMM: Service Request)

RANAP: GMM:Service Request



RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)

RANAP: SM: Activate PDP Context Request

RRC: Radio Bearer SetupClick to return to main page>>"Radio Bearer Description"

value= SF16(uplink)-> PS64

value= HSDPA Channel Information

value= hs-SCCH , Fixed SF 128 , Code No=4,5,6,7In theory, one cell can configure up to 15 HS-SCCH. But now commercial UE can only monitor up to 4 HS-SCCH channels simultaneously. So one cell only configure up to 4 HS-SCCH channels

value= SF256(downlink)

value= HSDPA Serving Cell's Primary SC = 30

value= SF256(downlink)


RRC: Radio Bearer Setup CompleteClick to return to main page

RANAP: SM: Activate PDP Context AcceptClick to return to main page

RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)Click to return to main page

RRC: Physical Channel Reconfiguration (DCCH)Click to return to main page

value= PrimarySC=30, no longer a HSDPA serving cell ( HSDPA Serving Cell Change)

(Old HSDPA's Serving Cell)Cell Identity=RNCid(12bits)+Cellid(16bits)value=0000000000010001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001010100101111)=5423

value= PrimarySC=9 is a new HSDPA serving cell ( HSDPA Serving Cell Change)

(New HSDPA's Serving Cell)Cell Identity=RNCid(12bits)+Cellid(16bits)value=0000000000010001000111011100=> RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001000111011100)=4572

RRC:Physical Channel Reconfiguration Complete (DCCH) Click to return to main page

RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)Click to return to main page

RANAP: SM: Deactivate PDP Context RequestClick to return to main page

RANAP: SM: Deactivate PDP Context AcceptClick to return to main page

RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)Click to return to main page

RRC: Radio Bearer ReleaseClick to return to main page

RRC: Radio Bearer Release CompletedClick to return to main page



PS-HSUPA



The PS Session Setup is performed to set up a PS session

Triggering Condition The UE sends activate PDP context request message to RNC .PDP context activation is performedWhen the UE initiates a packet call setup. The UE has the state packet mobility management connected that enable the user To transmit and receive data while moving within a PLMN and starts the PDP context activation procedure used to setupAnd remove a virtual data channel between a terminal connected to UE and GGSN.The PS session release procedure is performed to release services after a session ends.

Triggering Conditions The UE send Deactivate PDP Context request message to RNC.A PDP Context Deactivation is performed when UE terminates a packet call. Before the deactivation ,the UE has the state active. after the PDP context deactivation procedure the state becomes Packet mobility management connected. The RAB will be released if there area no other PDP context activated.PDP deactivation maybe initiated by a :UE procedure ,SGSN procedure,GGSN procedure.

RRC Connection Release Procedure is performed to release signaling connection and all radio bearers between UEAnd the UTRAN.


PS-HSUPA MSG




value=hex2dec(9)=9 , hex2dec(9)=9 --> MNC=99value=hex2dec(03EA)= 1002value= OriginatingBackgroundCall (PS MOC)

value=(-24+ (39/2))=-4.5 dBvalue=Primary Scrambling Code=60 ( Neighbour's SC)value=(-24+ (37/2))=-5.5 dBvalue= HSPA Release6value= UE support HSDPA and E-DCH (HSUPA)


>>"Geographical and UTRAN Entity Identifiers"value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(9)=9 , hex2dec(9)=9 --> MNC=99value=hex2dec(03EA)= 1002value=UE capable to support FDD , not TDD

value=Signaling Radio Bearer Information Setup ,RB-1value=Radio Bearer Mapping






value=(-47*2)= -94 dBm (step of 2 dB)

Default Constant DPCCH_Power_offsetCPICH_RSCPPCPICH PowerUL InterferenceUL DPCCH Initial Powervalue= use Closed Loop Power Control Algorithm1-22-94-8033-105-14-22-94-7033-105-24Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.








value= not support GSM (Locked UMTS Mode)value= Chipering Algorithm A5/3

value= support Compressed Mode (CM) uplink and downlink

value= support HSDPA, UE Category 8

RRC: Initial Direct Transfer (GMM: Service Request)

RANAP: GMM:Service Request



RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)

RANAP: SM: Activate PDP Context Request

RRC: Radio Bearer SetupClick to return to main page>>"Radio Bearer Description"

value= Uplink e-DPDCH (HSUPA) channel information

value= Downlink HS-PDSCH channel information

value= HSDPA and HSUPA Serving Cell's Primary SC = 68

RRC: Radio Bearer Setup Complete

RANAP: SM: Activate PDP Context AcceptClick to return to main page

RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)Click to return to main page

RRC: Physical Channel Reconfiguration (DCCH)Click to return to main page

value= PrimarySC=68, no longer a HSDPA & HSUPA serving cell ( HSPA Serving Cell Change)

value= PrimarySC=60 is a new HSDPA&HSUPA serving cell ( HSPA Serving Cell Change)

RRC:Physical Channel Reconfiguration Complete (DCCH) Click to return to main page

RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)Click to return to main page

RANAP: SM: Deactivate PDP Context RequestClick to return to main page

RANAP: SM: Deactivate PDP Context AcceptClick to return to main page

RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)Click to return to main page

RRC: Radio Bearer ReleaseClick to return to main page

RRC: Radio Bearer Release CompletedClick to return to main page



RRC:Measurement Report (e1d)Click to return to main page

RRC:Measurement ControlClick to return to main page

3G Intro & Events

Documents

Transcript of 3G Intro & Events