call procedure flow chart and counters rev a
DESCRIPTION
3g Call flowTRANSCRIPT
Ericsson Internal
TECHNICAL REPORT
1 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Call Procedure Flow Chart and Counters
Contents
1 Introduction.......................................................................................... 3 1.1 Revision ................................................................................... 3
2 Call Setup e Release............................................................................ 4 2.1 Mobile Originating Call Setup................................................... 4 2.1.1 Step: Random Access (it is the same for every kind of service:
CS, PS, Registrations, Signaling, SMS, etc.)............................ 4 2.1.2 Step: RRC Connection Setup................................................... 6 2.1.3 Step: Service request, Authentication and Security .................. 7 2.1.4 Step: RAB Assignment speech or CS64................................... 8 2.2 Mobile Terminating Call Setup ................................................. 9 2.2.1 Step: Paging .......................................................................... 10 2.2.2 Step: Random Access............................................................ 11 2.2.3 Step: RRC Connection Setup................................................. 11 2.2.4 Step: Service request, Authentication and Security ................ 11 2.2.5 Step: RAB Assignment speech or CS64................................. 11 2.3 Normal Call Release .............................................................. 12 2.3.1 Network initiated normal call release ...................................... 12 2.3.2 UE initiated normal call release.............................................. 13 2.4 Abnormal Call Release........................................................... 14 2.4.1 UE initiated abnormal call release .......................................... 14 2.4.2 Network initiated abnormal call release .................................. 15 2.5 Radio Connection Supervision ............................................... 16 2.5.1 Supervision of radio link synchronisation status ..................... 17 2.5.2 Supervision of RLC protocol (layer 2 failures) ........................ 18 2.5.3 Supervision of connection on common channels.................... 18 2.6 Signalling Connection Release for Speech and CS64 calls.... 19
3 Mobility............................................................................................... 20 3.1 Inter Radio Access Technology Handover (IRATHO) from
UTRAN to GSM, speech service ............................................ 20 3.1.1 Step1: Compressed Mode Start ............................................. 20 3.1.2 Step1: Compressed Mode Stop ............................................. 23 3.1.3 Step2: IRAT Handover Execution........................................... 23 3.2 Soft/Softer Handover.............................................................. 25 3.2.1 Soft/Softer/Inter RNC HO Addition, Dedicated channel .......... 26 3.2.2 Soft/Softer/Inter RNC HO Removal, Dedicated channel ......... 28 3.2.3 Soft/Softer/Inter RNC HO Replacement, Dedicated channel .. 29
4 Capacity Management ....................................................................... 30
Ericsson Internal
TECHNICAL REPORT
2 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
4.1 DL Cell Congestion Detection ................................................ 30 4.2 UL Cell Congestion Detection ................................................ 31 4.3 Resolve Congestion Actions................................................... 32
5 Location Update, IMSI Attach, IMSI Detach...................................... 34 5.1.1 Step: Random Access............................................................ 34 5.1.2 Step: RRC Connection Setup................................................. 36 5.1.3 Step: Location Updating (Normal, Periodic, IMSI Attach),
Authentication and Security.................................................... 37 5.1.4 Step: IMSI Detach.................................................................. 38
6 Short Message Service...................................................................... 39 (*) only for mobile terminating sms....................................................... 39 6.1.1 Step: Paging .......................................................................... 39 6.1.2 Step: Random Access............................................................ 39 6.1.3 Step: RRC Connection Setup................................................. 41 6.1.4 Step: Mobile Originating SMS ................................................ 42 6.1.5 Step: Mobile Terminating SMS............................................... 43
Ericsson Internal
TECHNICAL REPORT
3 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
1 Introduction
In this section will be described the main radio procedures related to Speech call, CS64 (video) call, Registrations on CS domain (Location Updating, IMSI Detach) and SMS.
1.1 Revision
Revision Date Description
PA1 2005-yy-xx
PA2 2005-yy-xx
PA9 2005-10-06
? ?Correction in pmFaultyTransportBlocks condition and addition of pmNoRecRandomAccSuccess and pmTransportBlocks counters in Random Access procedure
? ?Changed in “BlockingCell” the scope of pmNoReqDeniedAdm counter
? ?Inserted NSMSSRSUCC MSC counter in Mobile Terminating SMS procedure
Ericsson Internal
TECHNICAL REPORT
4 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2 Call Setup e Release
2.1 Mobile Originating Call Setup
Traffic Case: UE is in idle state normally camped on a UMTS cell and attempts to access the network and establish a circuit switched call (Speech or CS64)
Main Flow
2.1.1 Step: Random Access (it is the same for every kind of service: CS, PS, Registrations, Signaling, SMS, etc.)
Precondition: UE is in idle state
Post condition: RNC correctly receives the RRC Connection Request message over Random Access Channel.
Exceptions: the RBS blocks the access (negative AICH) or preambles sent by the UE are ignored (no AICH is sent) or UE does not receive the AICH positive for any reason.
Flow:
RRC Connection Setup
NAS procedures: Service Request Authentication
Security
RAB Assignment
Random Access
Mobile Originating Call Setup
Ericsson Internal
TECHNICAL REPORT
5 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Note1: during the RACH procedure the UE is allowed to make a cell reselection, so it is possible that a few attempts have to be repeated because the cell changed.
Note 2: in case of cell reselection or because the response from the RNC is delayed more than T300 (=1 sec) more than one RRC Connection Request could be sent to the RNC. In this case only the first attempt is counted.
UE sends preambles sequences
Negative AICH is sent No response is sent and/or received by UE over AICH
Positive AICH is sent
(Cell) pmNegativeMessages +
(Cell) pmPositiveMessages +
UE does not receive positive AICH
(RRC) (UE?RNC) RRC Connection Request
UE receives positive AICH
RNC does not receive the message
RNC receives the message
(Cell) pmTotNoRrcConnectReq + (Cell) pmTotNoRrcConnectReqCs + (Cell) pmTransportBlocks +
NAttempts > N300 (=5)?
NAttempts =0
NAttempts =+1
No
Random Access Failure
NAttempts counts the number of L3 access attempts performed by UE.
Yes
(Cell) pmFaultyTransportBlocks +
Ericsson Internal
TECHNICAL REPORT
6 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2.1.2 Step: RRC Connection Setup
Precondition: the RNC received “RRC Connection Request” message
Postcondition: the UE successfully establish a RRC connection
Exceptions: UE do not establish the RRC connection because of lack of resources or radio problems
Flow:
RNC receives the message RRC Connection Request
UE context allocation
Processor Load control (MP)
Admission Control
Radio Link Setup AAL2 Setup
RNC sends the message RRC Connection Reject
(Cell) pmNoRejRrcConnMmpLoadC
(Cell) pmTotNoUtranRejRrcConnReq
(Cell) pmNoReqDeniedAdm
(Cell) pmNoFailedAfterAdm +
OK
OK
OK
OK
Access not allowed
RNC sends the message RRC Connection Setup
UE synchronization on DCH and “RRC Connection Setup
Complete” is sent in time
(Cell)pmNoFailedAfterAdm + RRC Conn. Setup Failure. UE goes back to idle state
No
Yes
(Cell) pmTotNoRrcConnectReqSuccess + (Cell) pmTotNoRrcConnectReqCsSuc +
Context allocation failure
Setup Failure
Channel code allocation (Cell) pmNoDlChCodeAllocAttemptSf128 +
(Cell) pmNoDlChCodeAllocFailureSf128+
Code not available
OK
Access not allowed
Ericsson Internal
TECHNICAL REPORT
7 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2.1.3 Step: Service request, Authentication and Security
Precondition: UE has established a RRC Connection
Post condition: UE is authenticated, security is activated, UE sends the service request. CN select the proper RAB.
Exceptions: Authentication fails or security activation fails, or it is not possible to map the required service.
Flow:
UE send the Initial Message to the CN (UE->CN) CM Service Request
CN requires authentication (CN->UE) Authenication Request
(MSC) NAUTREQTOT + (UE->CN) Authenication Response
(MSC) NAUTREQSUCC +
CN activates security mode (MSC->RNC) Security Mode Command
(MSC) NSECTORNTOT + (RNC->MSC) Security Mode Complete
(MSC) NSECFRRNSCC +
CN requires the IMEI (CN->UE) Identity Request
(MSC) NEQIDTOT + (UE->CN) Identity Response
(MSC) NEQIDMSSUCC +
UE sends service details (UE->CN) Setup
CN confirm the call (CN->UE) Call Proceeding
Authentication fails due to error in the response
Authentication fails for other reasons
Call setup is blocked
Security mode activation fails
UE does not send the Identity Request Response
(MSC) NAUTSREERR +
Service required is not available (CN->UE) CM Service Reject
Signalling Connection Release
Ericsson Internal
TECHNICAL REPORT
8 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2.1.4 Step: RAB Assignment speech or CS64
Precondition: CN requires a RAB CS (Speech or CS64)
Post condition: the new RAB is activated
Exceptions: RAB Setup Failure
Flow:
CN sends to the RNC RAB Assignment Request
(MSC) NMSFRMTOTI +
RNC can accept the required RAB
RNC sends to CN RAB Assignment Response
(RAB Invalid to Setup or Modify) (RNC) pmNoInvalidRABEstablishAttempts +
(BCell) pmNoRABEstablishAttemptsSpeech + or
(BCell) pmNoRABEstablishAttemptsCS64 +
(RNC) pmNoRabEstablishAttempt +
RAB Setup Success (BCell) pmNoRABEstablishSuccessSpeech +
or (BCell) pmNoRABEstablishSuccessCS64 +
(RNC) pmNoRabEstablishSuccess +
(MSC) NMSFRMSCCI +
Admission Control (BlockingCell) pmNoReqDeniedAdm +
RAB Setup Failure
Yes
No
OK
Access denied
OK
RB Setup Failure
Channel code allocation (Cell) pmNoDlChCodeAllocAttemptSf128 +
or (Cell) pmNoDlChCodeAllocAttemptSf32 +
(Cell) pmNoDlChCodeAllocFailureSf128+ or (Cell) pmNoDlChCodeAllocFailureSf32+
Code not available
Code Allocation OK
RNC configures the RBS for the RAB (NBAP) Radio Link Reconfiguration
Rlink Reconfiguration failure
RNC configures the UE for the RAB (RRC)Radio Bearer Setup
UE successfully establishes the new RAB (RRC) Radio Bearer Setup Complete
OK
OK
Signalling Connection Release
(BCell) pmNoFailedAfterAdm +
Ericsson Internal
TECHNICAL REPORT
9 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2.2 Mobile Terminating Call Setup
Traffic Case: UTRAN sends a paging message to a UE to establish a CS call. The UE is registered on the target Location Area.
Main Flow
Mobile Terminating Call Setup
Paging
RRC Connection Setup
NAS procedures: Service Request Authentication
Security
RAB Assignment
Random Access
Ericsson Internal
TECHNICAL REPORT
10 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2.2.1 Step: Paging
Precondition: the CN pages the UE in the registered Location Area
Post condition: the “paging type 1” message is sent to the UE
Exceptions: UE is already connected (“paging Type 2” is sent), the message is not sent
CN sends to the RNC Paging message
Check UE status
Idle
Connected
(RNC) pmNoPagingAttemptCnInitDcch+
MP overload?
No
RNC sends to the UE Paging Type 2 Message
Yes
(RNC) pmNoPagDiscardCmpLoadC +
Paging is not sent
Paging Area is a defined LA?
Paging Area is a defined RA?
(LA) pmcnInitPagingToIdleUeLA+
No
No
(RNC) pmcnInitPagingToIdleUE +
(RA) pmcnInitPagingToIdleUeRA +
Yes
Yes
Paging queue is full? (cell)pmcnInitPagingAttemptUtranRejected +
Paging is not sent Paging is sent
Yes
No
Ericsson Internal
TECHNICAL REPORT
11 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2.2.2 Step: Random Access
(the same as Mobile Originating Call Setup)
2.2.3 Step: RRC Connection Setup
(the same as Mobile Originating Call Setup)
2.2.4 Step: Service request, Authentication and Security
Making reference to Mobile Originating Call Setup flow you have the following differences:
? ? The Setup message is sent from the CN to the UE,
? ? The Call Confirmed message is sent from the UE to the CN instead of Call Proceeding from CN to UE.
2.2.5 Step: RAB Assignment speech or CS64
Making reference to Mobile Originating Call Setup flow you have the following differences:
? ? The counter in MSC for RAB Assignment Request is NMSTOMTOTO instead of NMSFRMTOTI
? ? The counter in MSC for Successful RAB Assignment is NMSTOMSCCO instead of NMSFRMSCCI
Ericsson Internal
TECHNICAL REPORT
12 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Signalling Connection Release
2.3 Normal Call Release
Under normal conditions, the mobile station or of the network initiates call clearing by sending a DISCONNECT message to its peer entity; then both entities follow a similar procedure.
For speech only and CS64 calls the normal release leads in any case to the Signalling Connection release procedure (ref. 2.5.2). The Signalling Connection Release is the release of the connection of the UE with the CN; it includes the release of radio resource (RRC Connection Release).
2.3.1 Network initiated normal call release
The CN sends to UE (NAS) Disconnect
Disconnect Normal Event Class Causes: 16 Normal Call Clearing 17 User Busy 18 No user Responding 19 User Alerting, no answer 21 Call Rejected 22 Number Changed 25 Pre-emption 26 Non selected user clearing 27 Destination out of order 28 Invalid number format (incomplete number) 29 Facility Rejected 30 Response to STATUS ENQUIRY 31 Normal, unspecified
The UE sends to CN (NAS) Release
The CN sends to UE (NAS) Release Complete
Ericsson Internal
TECHNICAL REPORT
13 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2.3.2 UE initiated normal call release
The UE sends to CN (NAS) Disconnect
Disconnect Normal Event Class Causes: 16 Normal Call Clearing 17 User Busy 18 No user Responding 19 User Alerting, no answer 21 Call Rejected 22 Number Changed 25 Pre-emption 26 Non selected user clearing 27 Destination out of order 28 Invalid number format (incomplete number) 29 Facility Rejected 30 Response to STATUS ENQUIRY 31 Normal, unspecified
The CN sends to UE (NAS) Release
The CN sends to UE (NAS) Release Complete
Signalling Connection Release
Ericsson Internal
TECHNICAL REPORT
14 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Signalling Connection Release
2.4 Abnormal Call Release
We define abnormal call release each type of release not commanded by the served user and not due to a call release, of any type, from the B-user.
Abnormal call releases for speech and CS64 calls can be initiated either by the UE or by the UTRAN (RNC).
For speech only and CS64 calls the abnormal release leads in any case to the Signalling Connection release procedure (ref 2.5.2). The Signalling Connection Release is the release of the connection of the UE with the CN; it includes the release of all radio resources (RRC Connection Release).
2.4.1 UE initiated abnormal call release
UE abnormal release is quite rare event for speech and CS64 bearers. It can happens when the UE sends a DISCONNECT message to the CN with cause (not normal):
? ? invalid mandatory information (a previous message received is not valid) or
? ? interworking, unspecified (any other causes, not specified)
The UE sends to CN (NAS) Disconnect
UE Disconnect abnormal event causes: 96 Invalid mandatory information 127 Interworking, unspecified
The CN sends to UE (NAS) Release
The CN sends to UE (NAS) Release Complete
Ericsson Internal
TECHNICAL REPORT
15 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Signalling Connection Release
Radio Connection Supervision
Congestion Control
Soft Handover Functions
IRAT Handover Functions
Other failures Detected in the
RNC
Other failures Detected in the
CN
2.4.2 Network initiated abnormal call release
Any abnormal release due to RNC algorithms (Radio Connection Supervision, Congestion Control, Softh-Handover functions, IRAT Handover Functions) or other unrecoverable failures (signalling failures, detected UE failures, etc) are contained in this group.
The yellow blocks of the previous flowchart will be explained in the following chapters.
The “Other Failures Detected” blocks collect any other unrecoverable failures not included by the first line blocks. These failures will not be further investigated in this document since there are no counters related. Some specific information about these failures can be obtained by the cause of the Iu Release Request or the Iu Release Command messages sent in the Signalling Connection Release or by other specific trace in the RNC and/or CN.
The RNC send to CN (RANAP) Iu Release Request
Ericsson Internal
TECHNICAL REPORT
16 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2.5 Radio Connection Supervision
The aim of this function it to monitor the status of the radio connection and to initiate the release of signalling connection in case of radio connection lost.
Three different supervision algorithms can trigger the condition of “radio connection lost”:
? ? Supervision of radio link synchronisation status
? ? Supervision of RLC protocol (Layer 2 failures)
? ? Supervision of connections on common channels
The supervision of radio link synchronisation status is performed on dedicated channels only. The supervision of RLC protocol is performed on all channels (dedicated and common). The supervision of connection on common channels is performed (obviously) only on common channel. The RLC supervision works in parallel with the others.
Ericsson Internal
TECHNICAL REPORT
17 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Signalling Connection Release
2.5.1 Supervision of radio link synchronisation status
The RBS send to S-RNC [NBAP or RNSAP] Radio Link
Failure Indication (cause=synchronization failure)
It means that no data can be correctly received on a specific radio link set
Are there any other radio link set working in-synch
for the connection?
The RNC is waiting for messages from the RBSs controlling the dedicated channels of each
connection
yes
no
Start supervision timer: dchRcLostT
(NBAP or RNSAP) Radio Link Restore indication is received from any RBS
before timer expire?
Stop and reset timer
yes
no
(RNC) pmNoReleaseDchRcLostT +
The RNC send to CN (RANAP) Iu Release Request
Is this a speech connection?
(BCell) pmNoSysRelSpeechULSynch+
yes
no
Ericsson Internal
TECHNICAL REPORT
18 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Signalling Connection Release
Signalling Connection Release
2.5.2 Supervision of RLC protocol (layer 2 failures)
2.5.3 Supervision of connection on common channels
NOTE: This supervision algorithms does not affect the speech and CS64 calls. However it is included to make the Radio Connection Supervision description completed.
A RLC unrecoverable error has been detected in Layer 2 in the RNC
(RNC) pmNoRlcErrors +
The RNC send to CN (RANAP) Iu Release Request
UE is on cell FACH
(RNC) pmNoRchWaitCuT +
The RNC start the timer cchWaitCuT
[RRC] Cell Update is received from the UE before timer expire?
The RNC send to CN (RANAP) Iu Release Request
yes
no
Ericsson Internal
TECHNICAL REPORT
19 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
2.6 Signalling Connection Release for Speech and CS64 calls
This procedure is initiated to release any Iu Connection and every RAB supported by that connection.
Precondition: The UE has a speech or Cs64 RAB assigned
Post-condition: The Iu Connection and every Radio resources are released, the UE is in idle state.
The CN sends to RNC (RANAP) Iu Release
Command
Message Cause =Normal Release or
Successful Relocation
Message Cause <> Normal Release and Successful Relocation
The RNC sends to UE (RRC) RRC Connection Release (cause=normal)
The RNC sends to UE (RRC) RRC Connection
Release (cause <>normal)
(BCell) pmNoCellDchDisconnectNormal+ and
((Bcell) pmNoNormalRabReleaseSpeech+ (Bcell) pmNoSpeechDchDiscNormal+
or (Bcell) pmNoNormalRabReleaseCs64+
(Bcell) pmNoCs64DchDiscNormal+)
(BCell) pmNoCellDchDisconnectAbnormal+and
((Bcell) pmNoSystemRabReleaseSpeech+(Bcell) pmNoSpeechDchDiscAbnormal+
or (Bcell) pmNoSystemRabReleaseCs64+ (Bcell) pmNoCs64DchDiscAbnormal+)
UE is in idle state
Ericsson Internal
TECHNICAL REPORT
20 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
3 Mobility
3.1 Inter Radio Access Technology Handover (IRATHO) from UTRAN to GSM, speech service
Traffic Case: UE is in connected mode on a UMTS cell and IRATHO functionalities are active.
Main Flow
3.1.1 Step1: Compressed Mode Start
Precondition: UE in connected mode normal (speech) and reports e2d event.
Post condition: Compressed Mode successfully activated.
Exceptions: Compressed Mode not activated: UE still connected or release call.
IRATHO
Compressed Mode Start/Stop
IRAT Handover Execution
UE needs CPM for
HO?
Ericsson Internal
TECHNICAL REPORT
21 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Compressed Mode Start
Request admission
Prepare Compressed Mode in RBS NBAP Message (RL Reconfiguration Prepare) to RBS
(cell) pmNoOfDlChCodeAllocAttemptCm+ (cell) pmNoOfDlChCodeAllocAltCodeCm+
Admission granted?
Yes
No
SF/2 in DL?
No
Yes
Prepare Compressed Mode in DRNC RNSAP Message (RL Reconfiguration Prepare) to DRNC
Yes
No RL Reconfiguration Ready Message
received?
Procedure failure Send RL Reconfiguration Cancel
Cells in SRNC?
Yes
Procedure failure Admission Reject
No
Ericsson Internal
TECHNICAL REPORT
22 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
End Procedure
Yes
Physical Channel Reconfiguration
Complete received?
No
((cell) pmCmAttUlSf2+ and/or (cell) pmCmAttDlSf2+) or
((cell) pmCmAttUlHls+ and/or (cell) pmCmAttDlHls+)
Release Connection (cause unspecified)
No
Yes
Prepare Compressed Mode in UE RRC Message (Physical Channel Reconfiguration) to UE
Yes Procedure failure Send RL Reconfiguration Cancel
Cells in SRNC?
Cells in DRNC?
Commit Configuration RNBAP Message (RL Reconfiguration Commit) to RBS
((cell) pmCmSuccUlSf2+ end/or (cell) pmCmSuccDlSf2+) or
((cell) pmCmSuccUlHls+ end/or (cell) pmCmSuccDlHls+)
Commit Configuration RNSAP Message (RL Reconfiguration Commit) to DRNC
Yes
No
Activate Configuration in UE RRC Message (Measurement Control) to UE
Physical Channel Reconfiguration
Failure received?
No
Ericsson Internal
TECHNICAL REPORT
23 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Compressed Mode Stop
End Procedure
3.1.2 Step1: Compressed Mode Stop
Precondition: Compressed Mode active and UE reports e2f event.
Post condition: Compressed Mode successfully deactivated.
Exceptions: Compressed Mode still activate and UE connected.
3.1.3 Step2: IRAT Handover Execution
Precondition: UE reports e3a events.
Post condition: IRAT Handover successfully performed.
Exceptions: IRAT procedure failure: UE still connected, IRAT HO Lost: call release
Cells in SRNC?
Cells in DRNC?
Yes
Yes
No
No
Order stop of compressed mode NBAP Message (Compressed Mode Command) to RBS
(cell) pmCMStop+
Order stop of compressed mode RNSAP Message (Compressed Mode Command) to DRNC
Order stop of compressed mode in UE RRC Message (Measurement Control) to UE
Ericsson Internal
TECHNICAL REPORT
24 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
3a Events receiving and buffering (UE to RNC)
Relocation Required (RNC to CN)
(GSM Relation) PmNoOutIratHoResourceAllocFail+
Relocation Command (CN? RNC)
Handover From Utran Command (RNC? UE)
(GSM Relation) PmNoOutIratHoReturnOldChPhyChFail+
or (GSM Relation) pmNoOutIratHoReturnOldChFailOther+
Relocation Preparation
failure?
Yes
No
(GSM Relation) PmNoOutIratHoAtt+
HO from Utran
failure?
Yes
(GSM Relation) PmNoOutIratHoSuccess+
Procedure failure IRATHO Execution Start
No
Iu Release Command (successful
relocation) reiceved?
No
Yes
Handover Lost
N° attempt< GsmAmountPropRepeat?
Yes
No
Abnormal Call Release
End Procedure
Ericsson Internal
TECHNICAL REPORT
25 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
3.2 Soft/Softer Handover
Traffic Case: UE is in connected mode on a UMTS cell and sends to RNC Measurement Reports reporting a HO event (e1a, e1b, e1c or e1d).
Main Flow
1: Not valid cell means cell not included in neighbour set. 2: RelOnRej= true means that reported cell exceeds best cell + Release Connection Offset quantity.
Soft/softer HO Removal
Measurement Reports received in RNC:
e1a event e1c event e1b event e1d event
Not valid cell1 and
RelOnRej= true2?
Not valid cell1 and
RelOnRej= true2?
Yes Yes
Yes
No No
No
Soft/softer HO Replacement
Soft/softer HO Addition
(cell) pmNoSysRelSpeechNeighbr+ If speech: (cell) pmNoSysRelSpeechSoHo+
Release Call Procedure failure
Not valid cell1?
Best cell Update
Ericsson Internal
TECHNICAL REPORT
26 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
3.2.1 Soft/Softer/Inter RNC HO Addition, Dedicated channel
Precondition: UE triggers e1a valid event.
Post condition: Soft/Softer/Inter RNC handover addition successful.
Exceptions: RL setup or addition failure: UE still connected (no changes in AS) or release call.
Request admission
Send RL Setup/Addition Request If CPM ongoing:
(cell) pmNoOfDlChCodeAllocAttemptCm+ (cell) pmNoOfDlChCodeAllocAltCodeCm+
No
Yes
No Admission Rejected
Unsuccessful Radio Link Setup (cell) pmNoTimesCellFailAddToActSet+
Yes
Admission granted?
Channel code allocation (cell) pmNoDlChCodeAllocAttemptSf128+ or
(cell) pmNoDlChCodeAllocAttemptSf32+
Code available? Allocation Failure
(cell) pmNoDlChCodeAllocFailureSf128 + or (cell) pmNoDlChCodeAllocFailureSf32
Decision of HO algorithms to add a cell to the AS of the UE
Speech and RelOnRej=
true?
Yes
No
Procedure Failure
Release call (cause unspecified)
(cell) pmNoSysRelSpeechSoHo+
Ericsson Internal
TECHNICAL REPORT
27 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Yes RL Setup/Addition Failure received or supervision timer
expiration?
No
Channel Code Deallocation
Send Active Set Update If CPM ongoing: (cell) pmCmAtt<direction><method>+
Active Set Update
Complete received?
Yes
No
pmNoSysRelSpeechSoHo+
For the cell to be added: (cell) pmNoTimesRlAddToActSet+ If CPM ongoing: (cell) pmCmSucc<direction><method> +
RNC acting as DRNC?
Yes
No
(cell) pmNoOfRlForDriftingUes +
Successful RL Setup/Addition (cell) pmSumUesWith(x+1)Rls(y+1)RlInActSet +
(cell) pmNoOfRlForNonDriftingUes+ (Iur) pmNoOfRlForDriftingUesPerDrnc+
Active Set Update Failure
received?
No
Supervision timer expires (cell) pmNoTimesCellFailAddToActSet+
Speech and RelOnRej=
true?
Yes
No
Yes
End Procedure
Release call (cause unspecified)
Ericsson Internal
TECHNICAL REPORT
28 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
3.2.2 Soft/Softer/Inter RNC HO Removal, Dedicated channel
Precondition: UE triggers e1b event.
Post condition: Soft/Softer/Inter RNC handover removal successful.
Exceptions: RL deletion failure: UE still connected (no changes in AS)
Send (RRC) Active Set Update
Yes
No
Channelisation Code Deallocation
(RRC) Active Set Update Failure
received or supervision timer
expiration?
Decision of HO algorithms to remove a cell from the AS of the UE
No
RL deletion failure
Send (RRC) Radio Link Deletion Request
(RRC) Radio link Deletion
Response received?
Supervision timer expiration
Yes
Resource Release
Ericsson Internal
TECHNICAL REPORT
29 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
3.2.3 Soft/Softer/Inter RNC HO Replacement, Dedicated channel
Precondition: UE triggers e1c event.
Post condition: Soft/Softer/Inter RNC handover replacement successful.
Exceptions: No RL replacement, UE still connected (no changes in AS) or release call.
The procedure of replacement of RL is similar to the procedure of RL addition joined to RL deletion. For counters, when an HO replacement successfully ends, the counter (cell) PmNoTimesRlRepInActSet+ is triggered, instead of (cell) pmNoTimesRlAddToActSet+, triggered during HO addition procedure, or (cell) PmNoTimesRlDelFrActSet+, triggered during HO deletion procedure.
(cell) PmNoTimesRlDelFrActSet+
Send (RNSAP) Radio Link Deletion Response
End Procedure
RNC acting as DRNC?
Yes
No
(cell) pmNoOfRlForDriftingUes -
Successful RL Deletion pmSumUesWith(x)Rls(y+1)RlInActSet-
pmNoOfRlForNonDriftingUes- (cell) pmNoOfRlForDriftingUesPerDrnc
Ericsson Internal
TECHNICAL REPORT
30 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
4 Capacity Management
Traffic Case: UE is in connected mode on a cell reporting congestion state.
Main Flow
4.1 DL Cell Congestion Detection
Precondition: no DL congestion state and RNC receives a MR from RBS that indicates a TX carrier power above the DL congestion threshold.
Post condition: resolve congestion actions to setup.
Exceptions: none.
DL/UL Cell Congestion Detection
Resolve DL Congestion Actions
Congestion Control
DL/UL Cell Congestion Reported
Ericsson Internal
TECHNICAL REPORT
31 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
4.2 UL Cell Congestion Detection
Precondition: no UL congestion state and RNC receives a MR from UE that indicates an UL RTWP above the UL congestion threshold.
Post condition: resolve congestion actions to setup.
Exceptions: none
A TX carrier power MR received
Timer expired?
MR received?
(cell) pmSumOfTimesMeasOIDI+
Timer starts (1 sec.)
No
Yes
DL congestion reported in MR
Still DL congestion?
Yes No
Not DL congested
Yes
(cell) PmTotalTimeDlCellCong+
No
Received MR indicates a TX carrier power below
the congestion threshold.
Ericsson Internal
TECHNICAL REPORT
32 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
4.3 Resolve Congestion Actions
Precondition: cell congestion detected.
Post condition: no more DL congestion state.
Exceptions: none.
An UL RTWP MR received
Timer expired?
MR received?
(cell) pmSumOfTimesMeasOIUI+
Timer starts (1 sec.)
No
Yes
UL congestion reported in MR
Still DL congestion?
Yes No
Yes
(cell) PmTotalTimeUlCellCong+ Received MR indicates an UL RTWP below the congestion threshold.
Not UL congested
Ericsson Internal
TECHNICAL REPORT
33 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Start timer tmCongAction
Yes
No Not DL congested
No
(cell) pmNoOfTermSpeechCong + (cell) pmNoOfTermCSCong +
Target RLs to release (guaranteed/non-lur)
Timer expires
Still DL congestion?
Target RLs to release (guaranteed/lur)
(cell) pmNoOfIurSpeechCong+ (cell) pmNoOfIurCSCong +
Connection Release
More non-Iur traffic to release?
Yes
No
Ericsson Internal
TECHNICAL REPORT
34 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
5 Location Update, IMSI Attach, IMSI Detach
Traffic Case: UE is in idle state normally camped on a UMTS cell: attempts to access the network and perform a location update, IMSI attach or IMSI detach.
Main Flow
5.1.1 Step: Random Access
Precondition: UE is in idle state
Post condition: RNC correctly receives the RRC Connection Request message over Random Access Channel.
Exceptions: the RBS blocks the access (negative AICH) or preambles sent by the UE are ignored (no AICH is sent) or UE does not receive the AICH positive for any reason.
Flow:
RRC Connection Setup
Location Update, IMSI Attach
or IMSI Detach
Random Access
Location Update, IMSI Attach, IMSI Detach Procedures
Ericsson Internal
TECHNICAL REPORT
35 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Note1: during the RACH procedure the UE is allowed to make a cell reselection, so it is possible that a few attempts have to be repeated because the cell changed.
Note 2: in case of cell reselection or because the response from the RNC is delayed more than T300 (=1 sec) more than one RRC Connection Request could be sent to the RNC. In this case only the first attempt is counted.
(cell) pmTotNoRrcConnectReq+ If RRC Connection Request cause= IRAT cell
reselection: (cell) pmTotNoRrcConnectAttIratCellResel+
UE sends preambles sequences
Negative AICH is sent No response is sent and/or received by UE over AICH
Positive AICH is sent
(Cell) pmNegativeMessages +
(Cell) pmPositiveMessages +
UE does not receive positive AICH
(RRC) (UE? RNC) RRC Connection Request
UE receives positive AICH
RNC does not receive the message
RNC receives the message
NAttempts > N300 (=5)?
NAttempts =0
NAttempts =+1
No
Random Access Failure
NAttempts counts the number of L3 access attempts performed by UE.
Yes
(Cell) pmFaultyTransportBlocks +
Ericsson Internal
TECHNICAL REPORT
36 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
5.1.2 Step: RRC Connection Setup
Precondition: the RNC received “RRC Connection Request” message with cause registration (for Normal or Periodic Location Updating or IMSI attach), IRAT cell reselection (for Location Updating after G?U cell reselection) or Detach (for IMSI detach)
Postcondition: the UE successfully establish a RRC connection
Exceptions: UE do not establish the RRC connection because of lack of resources or radio problems
Flow:
RNC receives the message RRC Connection Request
UE context allocation
Processor Load control (MP)
Admission Control
Radio Link Setup AAL2 Setup
RNC sends the message RRC Connection Reject
(Cell) pmNoRejRrcConnMmpLoadC+
(Cell) pmTotNoUtranRejRrcConnReq+
(Cell) pmNoReqDeniedAdm+
(Cell) pmNoFailedAfterAdm +
OK
OK
OK
OK
Access not allowed
RNC sends the message RRC Connection Setup
UE synchronization on DCH and “RRC Connection Setup
Complete” is sent in time
(Cell) pmNoFailedAfterAdm+ RRC Conn. Setup Failure. UE goes back to idle state
No
Yes
(cell) pmTotNoRrcConnectReqSuccess + If RRC Connection Request cause= IRAT
cell reselection: (cell) pmTotNoRrcConnectSuccessIratCellResel+
Context allocation failure
Setup Failure
Channel code allocation (cell) pmNoDlChCodeAllocAttemptSf128 +
(Cell) pmNoDlChCodeAllocFailureSf128+
Code not available
OK
Access not allowed
(1)
If RRC Connection Request cause=IRAT cell reselection and RRC Connection Reject cause=congestion:
(cell) pmTotNoRrcConnectFailCongIratCellResel+
Ericsson Internal
TECHNICAL REPORT
37 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
5.1.3 Step: Location Updating (Normal, Periodic, IMSI Attach), Authentication and Security
Precondition: UE has established a RRC Connection.
Post condition: UE is authenticated, security is activated, successful Location Update.
Exceptions: Authentication fails or security activation fails, or Location Update rejected.
Flow:
UE send the Initial Message to the CN (UE->CN) Location Updating Request
CN requires authentication (CN->UE) Authenication Request
(MSC) NAUTREQTOT + (UE->CN) Authenication Response
(MSC) NAUTREQSUCC +
CN activates security mode (MSC->RNC) Security Mode Command
(MSC) NSECTORNTOT + (RNC->MSC) Security Mode Complete
(MSC) NSECFRRNSCC +
CN requires the IMEI (CN->UE) Identity Request
(MSC) NEQIDTOT + (UE->CN) Identity Response
(MSC) NEQIDMSSUCC +
Authentication fails due to error in the response
Authentication fails for other reasons
Security mode activation fails
UE does not send the Identity Request Response
(MSC) NAUTSREERR +
(CN->UE) Location Updating Reject If IMSI unknown: (MSC) NLOCIMSERR +
Subscriber already
registered?
(MSC) NLOCOLDTOT + If periodic location updating: (MSC) NLOCPERTOT +
If IMSI attach: (MSC) NLOCATTTOT +
(MSC) NLOCNRGTOT + If periodic location updating: (MSC) NLOCPTOTNEW +
Yes
No
Resource not available
Ericsson Internal
TECHNICAL REPORT
38 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
5.1.4 Step: IMSI Detach
Precondition: UE has established a RRC Connection.
Post condition: IMSI detach.
Flow:
CN confirm registration with (CN->UE) Location Updating Accept
Location Updating Failure
Signalling Connection Release
Subscriber already
registered?
(MSC) NLOCOLDSUCC +
Yes
(MSC) NLOCNRGSUCC +
RRC Connection Realease
No
UE send the Initial Message to the CN (UE->CN) IMSI Detach Indication
RRC Connection Realease
(MSC) NLOCDETTOT +
Ericsson Internal
TECHNICAL REPORT
39 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
6 Short Message Service
Traffic Case: UE is in idle state normally camped on a UMTS cell and attempts to access the network to send or receive an sms.
Main Flow
(*) only for mobile terminating sms.
6.1.1 Step: Paging
(the same as Mobile Terminating Call Setup)
6.1.2 Step: Random Access
Precondition: UE is in idle state
Post condition: RNC correctly receives the RRC Connection Request message over Random Access Channel.
Exceptions: the RBS blocks the access (negative AICH) or preambles sent by the UE are ignored (no AICH is sent) or UE does not receive the AICH positive for any reason.
RRC Connection Setup
Mobile Originating Sms or
Mobile Terminating Sms
Random Access
Short Message Service
Paging
Forward Short Message (SMS-GMSC ? MSC)
(MSC) NSMSSMRLTOT+
(*)
(*)
Ericsson Internal
TECHNICAL REPORT
40 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
Flow:
Note1: during the RACH procedure the UE is allowed to make a cell reselection, so it is possible that a few attempts have to be repeated because the cell changed.
Note 2: in case of cell reselection or because the response from the RNC is delayed more than T300 (=1 sec) more than one RRC Connection Request could be sent to the RNC. In this case only the first attempt is counted.
(cell) pmTotNoRrcConnectReq+ (cell) pmTotNoRrcConnectReqSms+
(Cell) pmTransportBlocks +
UE sends preambles sequences
Negative AICH is sent No response is sent and/or received by UE over AICH
Positive AICH is sent
(Cell) pmNegativeMessages +
(Cell) pmPositiveMessages +
UE does not receive positive AICH
(RRC) (UE?RNC) RRC Connection Request
UE receives positive AICH
RNC does not receive the message
RNC receives the message
NAttempts > N300 (=5)?
NAttempts =0
NAttempts =+1
No
Random Access Failure
NAttempts counts the number of L3 access attempts performed by UE.
Yes
(Cell) pmFaultyTransportBlocks +
Ericsson Internal
TECHNICAL REPORT
41 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
6.1.3 Step: RRC Connection Setup
Precondition: the RNC received “RRC Connection Request” message with cause OriginatingLowPrioritySignalling (for Mobile Originating Sms) or TerminatingLowPrioritySignalling (for Mobile Terminating Sms)
Postcondition: the UE successfully establish a RRC connection
Exceptions: UE do not establish the RRC connection because of lack of resources or radio problems
Flow:
RNC receives the message RRC Connection Request
UE context allocation
Processor Load control (MP)
Admission Control
Radio Link Setup AAL2 Setup
RNC sends the message RRC Connection Reject
(Cell) pmNoRejRrcConnMmpLoadC+
(Cell) pmTotNoUtranRejRrcConnReq+
(Cell) pmNoReqDeniedAdm+
(Cell) pmNoFailedAfterAdm +
OK
OK
OK
OK
Access not allowed
RNC sends the message RRC Connection Setup
UE synchronization on DCH and “RRC Connection Setup
Complete” is sent in time
(Cell) pmNoFailedAfterAdm+ RRC Conn. Setup Failure. UE goes back to idle state
No
Yes
(cell) pmTotNoRrcConnectReqSuccess +
Context allocation failure
Setup Failure
Channel code allocation (cell) pmNoDlChCodeAllocAttemptSf128 +
(Cell) pmNoDlChCodeAllocFailureSf128+
Code not available
OK
Access not allowed
(1)
If RRC Connection Request cause=IRAT cell reselection and RRC Connection Reject cause=congestion:
(cell) pmTotNoRrcConnectFailCongIratCellResel+
Ericsson Internal
TECHNICAL REPORT
42 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
6.1.4 Step: Mobile Originating SMS
Precondition: UE has established a RRC Connection.
Post condition: UE is authenticated, security is activated, successful mobile originated SMS.
Exceptions: Authentication fails or security activation fails, or mobile originated SMS failure.
Flow:
UE send the Initial Message to the CN (UE->CN) CM Service Request
(MSC) NSMSRDOTOT +
CN requires authentication (CN->UE) Authenication Request
(MSC) NAUTREQTOT + (UE->CN) Authenication Response
(MSC) NAUTREQSUCC +
CN activates security mode (MSC->RNC) Security Mode Command
(MSC) NSECTORNTOT + (RNC->MSC) Security Mode Complete
(MSC) NSECFRRNSCC +
CN requires the IMEI (CN->UE) Identity Request
(MSC) NEQIDTOT + (UE->CN) Identity Response
(MSC) NEQIDMSSUCC +
Authentication fails due to error in the response
Authentication fails for other reasons
Mobile Originated SMS Failure
Security mode activation fails
UE does not send the Identity Request Response
(MSC) NAUTSREERR +
Signalling Connection Release SMS-GMSC send positive result
(MSC) NSMSRAOSUCC+
RRC Connection Realease
Yes
UE SMS data received in the MSC (MSC) NSMSCDOTOT +
MSC akcnolwledge the data (MSC) NSMSCAOSUCC +
Ericsson Internal
TECHNICAL REPORT
43 (43) Prepared (also subject responsible if other) No.
TEI/RFE S. Sestito, TEI/RFR P. Gattei, TEI/RFE R. Ingravallo
TEI-05:001921 Uen
Approved Checked Date Rev Reference
TEI/RFR [Massimo Costa] 2005-10-10 A
6.1.5 Step: Mobile Terminating SMS
Precondition: UE has established a RRC Connection.
Post condition: UE is authenticated, security is activated, successful mobile terminated SMS.
Exceptions: Authentication fails or security activation fails, or mobile terminated SMS failure.
Flow:
UE send the Initial Message to the CN (UE->CN) Paging Response
(MSC) NSMSCMTOT +
CN requires authentication (CN->UE) Authenication Request
(MSC) NAUTREQTOT + (UE->CN) Authenication Response
(MSC) NAUTREQSUCC +
CN activates security mode (MSC->RNC) Security Mode Command
(MSC) NSECTORNTOT + (RNC->MSC) Security Mode Complete
(MSC) NSECFRRNSCC +
CN requires the IMEI (CN->UE) Identity Request
(MSC) NEQIDTOT + (UE->CN) Identity Response
(MSC) NEQIDMSSUCC +
Authentication fails due to error in the response
Authentication fails for other reasons
Mobile Terminated SMS Failure
Security mode activation fails
UE does not send the Identity Request Response
(MSC) NAUTSREERR +
Signalling Connection Release
RRC Connection Realease
No
MSC send positive result to SMS-GMSC (MSC) NSMSSRSUCC+
MSC send the data (MSC) NSMSCMTOT +
UE akcnolwledge data received in MSC (MSC) NSMSCMRSUCC +