Professional Documents
Culture Documents
Chapter 5 - Outgoing Call Procedure PDF
Chapter 5 - Outgoing Call Procedure PDF
The outgoing call procedure is performed for a piece of User Equipment (UE) to call another
terminal, such as a Public Switched Telephony Network (PSTN) terminal. This chapter describes
outgoing call setup and release in terms of protocols, triggering conditions, signaling procedure
of a successful outgoing call, signaling tracing on the RNC LMT, and elementary procedures.
This chapter also describes the elementary procedures in terms of functions, triggering
conditions, procedure, and signaling in abnormal conditions.
Note the following information about the procedure shown in Figure 5-1:
l An RRC connection can be set up on a DCH or CCH. This procedure takes setting up an
RRC connection on the DCH as an example.
l If IP transport is applied to the Iub interface, the ALCAP procedure is not performed on
the Iub interface when radio links are set up, reconfigured, or deleted.
Prerequisite
l The RNC LMT works properly.
l You have logged in to the RNC with an account authorized to perform tracing management.
Context
Table 5-1 lists the messages to be traced.
Interfaces
and
Message Name on the LMT Message Name in Protocols
Protocols to
Be Traced
RRC_INIT_DIRECT_TRANS
INITIAL DIRECT TRANSFER
F
Uu RRC_DL_DIRECT_TRANSF DOWNLINK DIRECT TRANSFER
RRC_SECURITY_MODE_C
SECURITY MODE COMMAND
MD
RRC_SECURITY_MODE_C
SECURITY MODE COMPLETE
MP
RRC_SECURITY_MODE_F
SECURITY MODE FAILURE
AIL
Interfaces
and
Message Name on the LMT Message Name in Protocols
Protocols to
Be Traced
RANAP_INITIAL_UE_MES
INITIAL UE MESSAGE
SAGE
RANAP_COMMON_ID COMMON ID
RANAP_DIRECT_TRANSF
DIRECT TRANSFER
ER
Iu RANAP_SECURITY_MODE
SECURITY MODE COMMAND
_COMMAND
RANAP_SECURITY_MODE
SECURITY MODE COMPLETE
_COMPLETE
RANAP_SECURITY_MODE
SECURITY MODE REJECT
_REJ
Interfaces
and
Message Name on the LMT Message Name in Protocols
Protocols to
Be Traced
RANAP_RAB_ASSIGNMEN
RAB ASSIGNMENT REQUEST
T_REQ
RANAP_RAB_ASSIGNMEN
RAB ASSIGNMENT RESPONSE
T_RESP
RANAP_IU_RELEASE_CO
IU RELEASE COMMAND
MMAND
RANAP_IU_RELEASE_CO
IU RELEASE COMPLETE
MPLETE
Procedure
Step 1 Create a Uu tracing task by referring to Creating an RNC Tracing Task.
Figure 5-2 shows an example of Uu signaling tracing result.
----End
Triggering Conditions
The UE in idle mode shall initiate the RRC connection setup procedure when the NAS of the
UE requests the establishment of a signaling connection.
Procedure
When the SRNC receives an RRC CONNECTION REQUEST message from the UE, the Radio
Resource Management (RRM) module of the RNC determines whether to accept or reject the
RRC connection request according to a specific algorithm. If accepting the request, the RRM
module determines whether to set up the RRC connection on a Dedicated Channel (DCH) or on
a Common Channel (CCH) according to a specific RRM algorithm. Typically, an RRC
connection is set up on the DCH.
I. RRC Connection Setup on a DCH
Figure 5-5 shows the procedure for setting up an RRC connection on a DCH.
Triggering Conditions
The UE sends a direct transfer message to initiate the signaling connection setup procedure.
Procedure
Figure 5-8 shows the signaling connection setup procedure.
Triggering Conditions
The UE and the CN exchange signaling. The network initiates the authentication and security
mode control procedure.
Procedure
Figure 5-9 shows the authentication and security mode control procedure.
6. The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE
of the integrity protection and ciphering algorithms that the UTRAN selects.
7. The UE sends a response message to the SRNC.
l If the integrity protection and ciphering algorithms are configured successfully, the UE
sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The
SRNC then sends to the CN a SECURITY MODE COMMAND COMPLETE message,
containing the information about the integrity protection and ciphering algorithms that
the UE uses.
l If the UE does not support the integrity protection and ciphering algorithms, the UE
sends to the SRNC a SECURITY MODE COMMAND FAILURE message that
contains the error information and the reason for the failure. The SRNC then sends a
SECURITY MODE COMMAND REJECT message to the CN.
Triggering Conditions
The UE initiates a call.
Procedure
Figure 5-10 shows the call setup procedure.
1. The UE sends to the SRNC an UPLINK DIRECT TRANSFER message that contains the
number of the callee and the information about the bearing capability of the call.
2. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
to the CN through a DIRECT TRANSFER message.
3. The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CALL
PROCEEDING and contains the information about the negotiated bearing capability of the
call.
4. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
5. A Radio Access Bearer (RAB) is set up. For details, refer to 5.5.5 RAB Setup
Procedure.
6. When the callee rings, the CN sends to the SRNC a DIRECT TRANSFER message,
indicating ALERTING.
7. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
8. The CN sends to the SRNC a DIRECT TRANSFER message, indicating CONNECT. This
means the callee has answered the call.
9. The SRNC transparently sends the contents of the DIRECT TRANSFER message to the
UE through a DOWNLINK DIRECT TRANSFER message.
10. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
11. The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
to the CN through a DIRECT TRANSFER message, indicating CONNECT
ACKNOWLEDGE.
The call is set up. The caller and the callee begin conversation.
Triggering Conditions
A call is set up.
Procedure
I. Setting Up an RAB Successfully
Figure 5-11 shows the successful RAB setup procedure.
1. The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the
RAB setup procedure.
2. The SRNC maps the Quality of Service (QoS) parameters for the RAB to the ATM
Adaptation Layer type 2 (AAL2) link characteristic parameters and radio resource
characteristic parameters. The ALCAP on the Iu interface initiates a setup procedure for
an Iu user plane transport bearer according to the AAL2 link characteristic parameters. (For
the PS domain, this step does not exist.)
3. The SRNC sends to the NodeB a RADIO LINK RECONFIGURATION PREPARE
message, requesting the NodeB to prepare for adding one or more DCHs to the existing
radio links for carrying the RAB.
4. The NodeB allocates the appropriate resources and then sends a RADIO LINK
RECONFIGURATION READY message to the SRNC.
5. The Iub ALCAP at the SRNC initiates a setup procedure for an Iub user plane transport
bearer. The NodeB and the SRNC perform synchronization by exchanging uplink and
downlink synchronization frames in the DCH frame protocol.
6. The SRNC sends a RADIO BEARER SETUP message to the UE.
7. The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the
NodeB.
8. After performing radio bearer setup, the UE sends a RADIO BEARER SETUP
COMPLETE message to the SRNC.
9. The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN.
Triggering Conditions
A call ends and the caller hangs up.
Procedure
Figure 5-13 shows the call release procedure.
Triggering Conditions
After an RAB is released, the SRNC judges whether the RRC connection carries any other RAB
of the UE. If judging that the RRC connection does not carry any other RAB of the UE, the
SRNC initiates an RRC connection release procedure.
Procedure
According to the resource occupied by the RRC connection, there are two types of RRC
connection release procedure: release of an RRC connection from a DCH and release of an RRC
connection from a CCH.
NOTE
If an RRC connection needs to be released after an outgoing call succeeds, the RRC connection on the
DCH is released. If a radio bearer fails to be set up, the RRC connection on the CCH is released.
Figure 5-14 shows the procedure for releasing an RRC connection from a DCH.
1. The SRNC sends an RRC CONNECTION RELEASE message to the UE through the
DCCH.
NOTE
The SRNC may send the RRC CONNECTION RELEASE message several times to increase the
probability of proper reception of the message by the UE. The RRC SNs of these messages are the
same. The number of retransmissions and the transmission intervals are determined by the SRNC. If
the SRNC does not receive an RRC CONNECTION RELEASE COMPLETE message from the UE
after sending the RRC CONNECTION RELEASE message for four times, the SRNC regards that
the UE has released the RRC connection.
2. The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC.
3. The SRNC sends to the NodeB a RADIO LINK DELETION REQUEST message,
requesting the NodeB to delete the radio link resources in the NodeB.
4. After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE
message to the SRNC.
5. The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release
procedure.
The RRC connection release procedure ends.
II. Releasing an RRC Connection from a CCH
Figure 5-15 shows the procedure for releasing an RRC connection from a CCH.