Professional Documents
Culture Documents
Umts Call Flows 140803082541 Phpapp01
Umts Call Flows 140803082541 Phpapp01
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 52
3.3. Iu Signalling Connection Release
UE RNC
SGSN
MSC
Server
Iu Release Command RANAP
release cause = UTRAN generated reason
Iu Release Complete
RANAP
Handling like in normal I u signallingconnection
release case
AMD Signalling Conn. Release Indic. [DCCH] RLC/ RRC
CN domain ID
Iu Release Request RANAP
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 53
3.3. Iu Signalling Connection Release
The release of Iu signalling connections is managed by the core network via the RANAP Iu Release procedure.
The core network releases an Iu signalling connection via RANAP message IU RELEASE COMMAND. The serving RNC will
respond with IU RELEASE COMPLETE.
Depending on the current UE configuration there are three basic procedures possible on the radio interface:
RRC Connection Release procedure is triggered (UE is sent to IDLE state),
UE is informed about Iu signalling connection release via SIGNALLING CONNECTION RELEASE procedure,
radio bearers are released via RADIO BEARER RELEASE procedure.
Of course none of these procedures is triggered when the UE is no longer in this RNC area.
In some situations the RNC can request the release of the Iu signalling connection from the CN via the RANAP procedure
IU RELEASE REQUEST. The reason for this message might be an RNC internal trigger or the UE has requested the
release by SIGNALLING CONNECTION RELEASE MESSAGE.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 54
4. Security Mode Control
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 55
4. Security Mode Control
4.1. Ciphering and Integrity Protection
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 56
RRC HFN (28 bit)
4.1. Ciphering and Integrity Protection
Integrity Protection
f9 (UIA)
f9 (UIA)
I K
COUNT-I
DIRECTI ON
FRESH
RRC Message MAC-I
f9 (UIA)
f9 (UIA)
I K
COUNT-I
DIRECTI ON
FRESH
RRC Message MAC-I
XMAC-I
Transmitter Receiver
COUNT-I
RRC HFN (28 bit) RRC SN (4)
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 57
4.1. Ciphering and Integrity Protection
DCCH RRC messages can be protected against change of information or message injection by an integrity protection
mechanism. Therefore an algorithm f9 (UIA: UMTS Integrity Algorithm) must be available in UE and RNC. For each DCCH
RRC message this algorithm calculates a message authentication code (MAC-I: Message Authentication Code Integrity).
This MAC-I is included in the message itself.
At the receiver side the MAC-I is calculated again and cross-checked with the transmitted one.
The algorithm UIA (f9) takes several additional values as input:
IK (Integrity Key): A UE specific key that is derived from authentication (automatic key agreement).
DIRECTION: Discriminates between uplink and downlink direction.
FRESH: An offset value that is allocated for uplink by UE and for downlink by RNC. The UL/DL-FRESH values are
exchanged at set up of signalling radio bearers (RRC CONNECTION SETUP and RRC CONNECTION SETUP COMPLETE).
COUNT-I: This value is increased with every message that is transmitted. For initialisation of COUNT-I a START value is
negotiated at radio bearer set up time.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 58
4.1. Ciphering and Integrity Protection
RRC HFN (28 bit)
Ciphering
f8 (UEA)
f8 (UEA)
BEARER
COUNT-C
DIRECTI ON
LENGTH
Plaintext
Block
f8 (UIA)
f8 (UIA)
Transmitter Receiver
COUNT-C for RLC TM on DCH
MAC-d HFN (24 bit) CFN (4 bit)
CK
BEARER
COUNT-C
DIRECTI ON
LENGTH
CK
Keystream
Block
XOR
Ciphertext
Block
Keystream
Block
XOR
Plaintext
Block
RRC HFN (28 bit)
COUNT-C for RLC UM
RLC HFN (25 bit) RLC SN (7 bit)
COUNT-C for RLC AM
RLC HFN (20 bit) RLC SN (12 bit)
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 59
4.1. Ciphering and Integrity Protection
Like in GSM also UMTS allows an encryption with a classical stream cipher algorithm.
The algorithm for production of the stream cipher sequence is called UEA (UMTS Encryption Algorithm) or f8. This
algorithm uses several values as input:
CK (Cipher Key): A UE specific key that is coming from authentication (automatic key agreement).
BEARER: The radio bearer identity.
DIRECTION: Distinguishes between uplink and downlink direction.
LENGTH: Length of the cipher sequence to be produced.
COUNT-C: Strictly increasing value for each radio frame (RLC transparent mode) or RLC frame (RLC unacknowledged
or acknowledged mode). COUNT-C is initialised with the START values that are exchanged at radio bearer set up time.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 60
4. Security Mode Control
4.2. Security Mode Activation
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 61
4.2. Security Mode Activation
UE RNC
SGSN
MSC
Server
Security Mode Command RANAP
integrity protection info, ciphering info,
Security Mode Complete
RANAP
AMD Security Mode Command. [DCCH] RLC/ RRC
CN domain ID, security capability, inter-RAT security capability,
ciphering mode info = {start/modify, selected UEA-no., RB activation
time, DPCH activation time}
integrity mode info = {start/modify, selected UIA-no., DL-FRESH, }
STATUS [DCCH] RLC/ --
acknowledgement
AMD Security Mode Complete [DCCH] RLC/ RRC
integrity check info = {MAC-I, RRC SN for RB2},
uplink integrity protection activation info ={RRC SN for RB1-RB4},
RB ciphering activation time info = {RB-ID, RLC SN}
STATUS
[DCCH] RLC/ --
acknowledgement
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 62
4.2. Security Mode Activation
|TS 25.331 DCCH-DL (2002-09) (RRC_DCCH_DL) securityModeCommand (= securityModeCommand) |
| |1 integrityCheckInfo |
|**b32*** |1.1 messageAuthenticationCode |'10110100100001111011101010000100'B |
|-0001--- |1.2 rrc-MessageSequenceNumber |1 |
| |2 message |
| |2.1 securityModeCommand |
| |2.1.1 r3 |
| |2.1.1.1 securityModeCommand-r3 |
|***b2*** |2.1.1.1.1 rrc-TransactionIdentifier |0 |
| |2.1.1.1.2 securityCapability |
|**b16*** |2.1.1.1.2.1 cipheringAlgorithmCap |uea1 |
| | |uea0 |
|**b16*** |2.1.1.1.2.2 integrityProtectionAlgorithmCap |uia1 |
| |2.1.1.1.3 integrityProtectionModeInfo |
| |2.1.1.1.3.1 integrityProtectionModeCommand |
| |2.1.1.1.3.1.1 startIntegrityProtection |
|**b32*** |2.1.1.1.3.1.1.1 integrityProtInitNumber |'01000000110110110000111010010001'B |
| |2.1.1.1.3.2 integrityProtectionAlgorithm |uia1 |
|---0---- |2.1.1.1.4 cn-DomainIdentity |cs-domain |
|TS 25.331 DCCH-UL (2002-09) (RRC_DCCH_UL) securityModeComplete (= securityModeComplete) |
| |1 integrityCheckInfo |
|**b32*** |1.1 messageAuthenticationCode |'11101010011001010000010001001011'B |
|-0001--- |1.2 rrc-MessageSequenceNumber |1 |
| |2 message |
| |2.1 securityModeComplete |
|-----00- |2.1.1 rrc-TransactionIdentifier |0 |
| |2.1.2 ul-IntegProtActivationInfo |
| |2.1.2.1 rrc-MessageSequenceNumberList |
|0000---- |2.1.2.1.1 rRC-MessageSequenceNumber |0 |
|----0000 |2.1.2.1.2 rRC-MessageSequenceNumber |0 |
|0000---- |2.1.2.1.3 rRC-MessageSequenceNumber |0 |
|----0000 |2.1.2.1.4 rRC-MessageSequenceNumber |0 |
|0000---- |2.1.2.1.5 rRC-MessageSequenceNumber |0 |
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 63
4.2. Security Mode Activation
Security functions are activated by the core network via the RANAP procedure Security Mode Control. This procedure is
triggered with the message SECURITY MODE COMMAND. In this message the CN provides IK and CK to the RNC as well
as a list of permitted UIA and UEA.
The serving RNC has to select an UIA and an UEA that is supported by UE and RNC and is permitted by the CN. Then the
security functions are activated by the RRC message SECURITY MODE COMMAND. In it one can find the selected
algorithms.
When the UE is able to activate the requested algorithms it returns SECURITY MODE COMPLETE. The same message but
from RANAP protocol is also returned to the core network.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 64
5. Paging
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 65
5. Paging
5.1. UTRAN Paging Types
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 66
5.1. UTRAN Paging Types
CN originated
CN originated
UTRAN originated
UTRAN originated
UTRAN Paging
Paging Originator
Request for Iu signallingconnection
Request for UE to enter CELL_FACH and
perform Cell Update procedure
Paging Type 1
Paging Type 1
Paging Type 2
Paging Type 2
Paging Type
PCCH on PCH; may be used to page up to 8 UE
DCCH on DCH or FACH
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 67
5.1. UTRAN Paging Types
Paging in UMTS can come from two different types of source the paging originator:
CN originated paging: The CN triggers paging whenever a downlink signalling message shall be sent, but currently
there is no Iu signalling connection for this UE at the CN domain of interest available (P/CMM_DETACHED state). Thus
CN originated paging is a request for an Iu signalling connection.
UTRAN originated paging: The serving RNC has to trigger a paging whenever the UE is in state CELL_PCH or
URA_PCH and a downlink message shall be sent to the UE. This paging shall force the UE to enter state CELL_FACH and
perform a Cell Update procedure.
A problem for UTRAN is the question on which channel to send the paging message. The RRC protocol provides two
options:
Paging Type 1: The RRC message PAGING TYPE 1 is always sent on the PCH. Thus it can be used for UE in state
Idle, CELL_PCH or URA_PCH. The PAGING TYPE 1 message can be used to page up to 8 UE in one single message.
Furthermore the PAGING TYPE 1 message can also be used to indicate change of BCCH (BCCH Modification) or to
release a UE from state CELL_PCH or URA_PCH to idle.
Paging Type 2: The message PAGING TYPE 2 is sent on either DCH or FACH. Thus it is the choice for UE in state
CELL_DCH or CELL_FACH. Note that PAGING TYPE 2 is a dedicated control channel (DCCH) message, thus only one UE
can be paged with such a message.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 68
5. Paging
5.2. CN originated paging
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 69
5.2. CN originated paging
UE RNC
SGSN
MSC
Server
Paging RANAP
CN domain ID, UE identifier, paging area,
paging cause
Initial UE Message RANAP
TMD/AMD Paging Type 1|2 [P/ DCCH] RLC/ RRC
Type 1: Paging Record ={, CN UE ID or U-RNTI + CN domain ID}
Type 2: CN domain ID
TMD RRC Connection Request [CCCH] RLC/ RRC
UMD RRC Connection Setup [CCCH] RLC/ RRC
AMD RRC Connection Setup Complete [DCCH] RLC/ RRC
IF (UE idle)
AMD Initial Direct Transfer [DCCH] RLC/ RRC
. . .
STATUS
[DCCH] RLC/ --
CN domain ID, ,
NAS-Message = RR:Paging Response|GMM:Service Request
NAS-Message
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 70
5.2. CN originated paging
|TS 25.331 PCCH (2002-03) (RRC_PCCH) pagingType1 (= pagingType1) |
| |pCCH-Message |
| |1 message |
| |1.1 pagingType1 |
| |1.1.1 pagingRecordList |
| |1.1.1.1 pagingRecord |
| |1.1.1.1.1 cn-Identity |
|110----- |1.1.1.1.1.1 pagingCause |terminatingCauseUnknown |
|---0---- |1.1.1.1.1.2 cn-DomainIdentity |cs-domain |
| |1.1.1.1.1.3 cn-pagedUE-Identity |
|**b32*** |1.1.1.1.1.3.1 tmsi-GSM-MAP |'10110110000000000000000000100001'B |
|TS 25.331 PCCH (2002-03) (RRC_PCCH) pagingType1 (= pagingType1) |
| |pCCH-Message |
| |1 message |
| |1.1 pagingType1 |
| |1.1.1 bcch-ModificationInfo |
|-----010 |1.1.1.1 mib-ValueTag |3 |
|***b9*** |1.1.1.2 bcch-ModificationTime |237 |
CN Triggered Paging
BCCH Modification I ndication
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 71
5.2. CN originated paging
CN originated paging is obviously triggered by the core network.
MSC server or SGSN send the RANAP message PAGING to the RNC (or to several RNC). Inside the message the UE is
identified (IMSI, TMSI/PTMSI) and the paging area (LAI/RAI) is indicated.
The RNC determines the state of the UE by checking the IMSI. Then either PAGING TYPE 1 or PAGING TYPE 2 is sent on
an appropriate downlink signalling transport channel.
If the UE is in idle state, then it first of all performs a RRC connection setup procedure. If the UE is already in connected
mode, it can skip this part.
Then the UE has to trigger the Iu signalling connection to the requesting core network using the INITIAL DIRECT
TRANSFER message.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 72
5. Paging
5.3. UTRAN originated paging
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 73
5.3. UTRAN originated paging
UE
RNC
TMD Paging Type 1 [PCCH] RLC/ RRC
Type 1: Paging Record ={, U-RNTI, RRC connection release indication=No Release|Release Cause}
TMD Cell Update [CCCH] RLC/ RRC
IF (RRC connection release indication = NoRelease)
U-RNTI, cell update cause = paging response,
UMD Cell Update Confirm [CCCH] RLC/ RRC
U-RNTI, new U-RNTI, new C-RNTI, RRC state indicator, RB info, TrCH info, PhCH info,
CELL_PCH
URA_PCH
OR
UMD RRC Connection Release
[CCCH] RLC/ RRC
U-RNTI, new U-RNTI, new C-RNTI, RRC state indicator, RB info, TrCH info, PhCH info,
IF (RRC connection release indication = ReleaseCause
UE enters UTRA IDLE mode
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 74
5.3. UTRAN originated paging
In case the paging is originated by the serving RNC there is no CN Domain information element inside the PAGING TYPE
1 message.
The UE will enter state CELL_FACH on reception of an UTRAN originated paging. Then the UE will send a CELL UPDATE
message on RACH (CCCH). Inside it will identify itself with the u-rnti and the parameter cell update cause is set to
paging response.
The RNC has now two options. Either it sends the CELL UPDATE CONFIRM message on FACH to the UE and indicates
with this a new state and radio configuration to the UE. Or the RNC sends RRC CONNECTION RELEASE, so that the UE
immediately enters idle mode.
Since UMTS Release 5 the PAGING TYPE 1 message can contain a release indicator. If this is set to release, the UE will
not perform the CELL UPDATE, instead it silently enters idle mode without any further interaction with the RNC.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 75
6. Radio Resource Management
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 76
6. Radio Resource Management
6.1. Radio Bearer and Radio Access Bearer Setup
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 77
6.1 RB and RAB Setup
UE RNC
SGSN
MSC
Server
RAB Assignment Request
RANAP
RAB to setup or Modify, RAB to release
RAB Assignment Response RANAP
UMD/AMD Radio Bearer Setup
[DCCH] RLC/ RRC
, RRC state indicator, signalling radio bearer,
radio access bearers radio bearers (user data)
transport channel to add/delete, physical channel configuration
AMD Radio Bearer Setup Complete [DCCH] RLC/ RRC
RAB released
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 82
6.2. RB and RAB Release
To release radio bearers the RADIO BEARER RELEASE procedure is provided by RRC protocol. It can be used to release
individual radio bearers or complete radio access bearers with all associated radio bearers and the procedure can also
trigger RRC state changes.
The RNC can in principle release a radio bearer at any time without involution of the core network. If this is really done,
depends on the traffic class of the radio access bearer. Because of delay problems when a radio bearer is to be re-
established, such a Radio Access Bearer independent Radio Bearer management is not done for conversational or
streaming traffic classes. Only background and interactive traffic class radio access bearers allow such a radio bearer
management without involution of CN.
Of course radio bearers have to be released whenever the radio access bearer of the service is terminated. A radio
access bearer can be released in two ways. Either the CN uses again the RANAP procedure RAB ASSIGNMENT REQUEST
with a RAB release indication or the CN releases the Iu signalling connection with IU RELEASE COMMAND. In the latter
case all RAB for this UE of to the releasing core network have to be terminated.
The RNC can upon one of these two procedures release the associated radio bearers with RADIO BEARER RELEASE, the
UE has to respond with RADIO BEARER RELEASE COMPLETE.
Of course there is another final way to release all radio bearers. When the UE is sent to idle state by the RRC message
RRC CONNECTION RELEASE automatically all radio bearers will be terminated. This option is used after the IU RELEASE
COMMAND when no Iu signalling connection is left at the end of the procedure.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 83
6. Radio Resource Management
6.3. Reconfiguration Operations
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 84
6.3. Reconfiguration Operations
UE
RNC
UMD/AMD Radio Bearer Reconfiguration [DCCH] RLC/ RRC
New U-RNTI, new C-RNTI, new DSCH-RNTI, new H-RNTI, RRC state indicator, RB to reconfigure,
transport channels to add/delete/modify, physical channel configuration
AMD Radio Bearer Reconfiguration Complete [DCCH] RLC/ RRC
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 85
6.3. Reconfiguration Operations
Three main operations are provided in the RRC protocol to modify the current radio configuration of a UE. There are
RADIO BEARER RECONFIGURATION: This allows to modify physical channels (frequency, channelization codes,
scrambling codes), transport channels (transport format sets, transport format combination sets, type of transport
channels) and radio bearers itself.
TRANSPORT CHANNEL RECONFIGURATION: This procedure allows to modify transport channels and physical
channels. Radio bearers are not affected by this procedure.
PHYSICAL CHANNEL RECONFIGURATION: This allows to modify physical channels only.
Depending on what shall be modified the serving RNC has to select one of these procedures. If only transport format
combinations shall be allowed or blocked there is another procedure the TRANSPORT FORMAT COMBI NATI ON
CONTROL operation. This is not really a reconfiguration, because the channels and radio bearers are not modified by it.
The reconfiguration operations can be used to implement hard handover procedures on the same frequency or to other
frequency (inter-frequency handover). They cannot be used for soft handover (see active set update procedure) or to
perform inter-system (inter-RAT) handover (see HANDOVER FROM UTRAN COMMAND).
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 86
6. Radio Resource Management
6.4. Inter-System Change Operations
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 87
6.4. Inter-System Change Operations
Handover From UTRAN
UE
Source
RNC
AMD Handover From UTRAN Command
[DCCH] RLC/ RRC
RAB to handover list, other RAT system information other systems handover message,
STATUS
[DCCH] RLC/ --
SUFI: Acknowledgement
other RAT
(e.g. GSM BSS)
Core
Network
other systems handover message
other systems handover completion
AMD/UMD UE Capability Enquiry [DCCH] RLC/ RRC
capability update requirement
AMD UE Capability Information [DCCH] RLC/ RRC
UE radio access capability, other RAT capabilities
AMD/UMD UE Capability Information Confirm
[DCCH] RLC/ RRC
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 88
6.4. Inter-System Change Operations
To change from UMTS WCDMA FDD mode to another radio access technology (RAT) there are inter-system (inter-RAT)
procedures defined.
Before a UE can go to another RAT it might be necessary to retrieve the UEs capabilities with respect to this RAT. If
these RAT capabilities are not available yet at the serving RNC a capability enquiry procedure has to be performed.
During this procedure the RNC request the updated capabilities with UE CAPABILITY ENQUIRY from the UE, which will
respond with a UE CAPABILITY INFO message back to the RNC. This message contains the UE capabilities as requested
before by the UE CAPABILITY ENQUIRY message. The RNC confirms reception of the parameters by sending UE
CAPABILITY INFO CONFIRM.
When the handover to the other RAT shall be started typically a so called S-RNS Relocation procedure (not shown here)
is started. During this relocation the new RAT radio network controller (whatever this might be) sends an appropriate
handover command over the core network to the serving RNC. This will take it and pack it into a HANDOVER FROM
UTRAN COMMAND, which is sent to the UE.
The UE now changes the radio access system and completes the handover procedure in the new radio subsystem.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 89
6.4. Inter-System Change Operations
Handover To UTRAN
UE
Target
RNC
AMD Handover To UTRAN Complete
[DCCH] RLC/ RRC
STATUS
[DCCH] RLC/ --
SUFI: Acknowledgement
other RAT
(e.g. GSM BSS)
Core
Network
Signalling transfer Handover To UTRAN Command Handover To UTRAN Command RRC
new U-RNTI, ciphering algorithm,
signalling radio bearer to setup,
RAB and radio bearer to setup,
transport channels to add, physical channel
configuration
Signalling transfer Inter-RAT Handover Info Inter-RAT Handover Info RRC
UE radio access capabilities, pre-defined
configuration status information
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 90
6.4. Inter-System Change Operations
A handover to UTRAN is of course triggered by the other RAT that is used by the UE in the moment.
Before a handover to UTRAN is started usually the new RNC (target RNC) has to get the UE capabilities with respect to
WCDMA FDD mode. Therefore the other RAT requests the UE WCDMA capabilities and forwards it over the CN to the
target RNC. This is embedded in a S-RNC relocation procedure, but this time the RNC is the destination of the procedure,
not the source.
When the target RNC has the UE capabilities it will prepare all resources for it and then create a HANDOVER TO UTRAN
COMMAND. This command is sent over the core network to the radio controller of the other RAT. From here the
message finds its way to the UE. How this is done depends on the other RAT.
Now the UE switches to the WCDMA FDD cell and completes the handover with the message HANDOVER TO UTRAN
COMPLETE.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 91
6.4. Inter-System Change Operations
Network Ordered Cell Change To Other RAT
UE
Source
RNC
AMD Cell Change Order From UTRAN
[DCCH] RLC/ RRC
target cell description,
STATUS
[DCCH] RLC/ --
SUFI: Acknowledgement
other RAT
(e.g. GSM BSS)
update procedures
corresponding to new system
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 92
6.4. Inter-System Change Operations
There is a second possibility to change from UTRAN to another radio access technology. This option is especially
designed for UMTS (CELL_FACH) to GSM (Packet Transfer Mode).
Here we use a network ordered cell change to switch away from UMTS to another RAT. The RNC give the CELL CHANGE
ORDER FROM UTRAN command to the UE. In this message the new cell of the other RAT is indicated. The UE now
performs a forced cell reselection to the new cell. All cell reselection criteria for automatic cell reselection are ignored at
the UE.
The remaining part of the procedure consists possibly of an update procedure in the new RAT. This is out of scope of
UTRAN.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 93
6. Radio Resource Management
6.5. Active Set Management (Soft Handover)
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 94
6.5. Active Set Management (Soft Handover)
UE
RNC
AMD/UMD Active Set Update
[DCCH] RLC/ RRC
Radio link addition info {primary CPICH info = primary DL scrambling code,
cell identity, downlink DPCH info, }
Radio link removal info {primary CPICH info = primary DL scrambling code}
AMD Active Set Update Complete
[DCCH] RLC/ RRC
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 95
6.5. Active Set Management (Soft Handover)
Soft handover consists of operations to add, delete and replace cells from the so called active set. The procedure that
provides this functionality is the ACTIVE SET UPDATE.
In an ACTIVE SET UPDATE message the serving RNC indicates the cells that are to be added to the active set and the
cells that must be removed from it. Whenever the UE receives such an ACTIVE SET UPDATE it immediately performs the
requested operations and returns the ACTIVE SET UPDATE COMPLETE message.
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 96
7. UE Measurements
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 97
7. Measurements
7.1. Measurement Types and Reporting
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 98
7.1. Measurement Types and Reporting
1) I ntra Frequency Measurements
2) I nter Frequency Measurements
3) I nter RAT Measurements
4) Traffic Volume Measurements
5) Quality Measurements
6) UE I nternal Measurements
7) Positioning Measurements
RLC/MAC
TrCH
#N
WCDMA physical layer
TrCH
#0
. . .
RRC
. . .
Periodical
Measurements
- Filtering
- Reporting criteria
evaluation
RNC
Measurement Control | SIB 3/ 4+11/ 12 RRC
Measurement Report RRC
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 99
7.1. Measurement Types and Reporting
UE Measurements in UTRAN are divided into seven categories as shown on the slide. Every measurement in a UE has to
be created before it starts. Therefore a MEASUREMENT CONTROL message is provided. Additionally SIB 3/4 and SIB
11/12 can create measurements.
Reporting of measurements can be done either periodically or by event trigger. Which reporting mode for a created
measurement is to chosen is indicated in the associated MEASUREMENT CONTROL message. When a trigger for a report
is fulfilled then the UE sends MEASUREMENT REPORT uplink to the RNC which contains the measured results (filtered by
UE) and the indication of the event that triggered the report (only for even triggered reporting).
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 100
7. Measurements
7.2. Measurement Control and Report Procedure
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 101
7.2. Measurement Control and Report Procedure
UE
RNC
AMD Measurement Control
[DCCH] RLC/ RRC
measurement identity, measurement control command = setup, release, modify, measurement type,
measurement reporting mode {RLC mode = AMD|UMD, trigger = periodical|event},
STATUS
[DCCH] RLC/ --
AMD/UMD Measurement Report
[DCCH] RLC/ RRC
measurement identity, measurement control command = setup, release, modify, measurement type,
measurement reporting mode {RLC mode = AMD|UMD, trigger = periodical|event},
STATUS
[DCCH] RLC/ --
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 102
|TS 25.331 DCCH-DL (2002-03) (RRC_DCCH_DL) measurementControl (= measurementControl) |
|dL-DCCH-Message |
| |1 integrityCheckInfo |
|**b32*** |1.1 messageAuthenticationCode |'11101001001100000100101100101000'B |
|-0011--- |1.2 rrc-MessageSequenceNumber |3 |
| |2 message |
| |2.1 measurementControl |
| |2.1.1 r3 |
| |2.1.1.1 measurementControl-r3 |
|***b2*** |2.1.1.1.1 rrc-TransactionIdentifier |2 |
|-1000--- |2.1.1.1.2 measurementIdentity |9 |
| |2.1.1.1.3 measurementCommand |
| |2.1.1.1.3.1 setup |
| |2.1.1.1.3.1.1 intraFrequencyMeasurement |
| |2.1.1.1.3.1.1.1 intraFreqCellInfoList |
| |2.1.1.1.3.1.1.1.1 removedIntraFreqCellList |
| |2.1.1.1.3.1.1.1.1.1 removeAllIntraFreqCells |0 |
| |2.1.1.1.3.1.1.1.2 newIntraFreqCellList |
| |2.1.1.1.3.1.1.1.2.1 newIntraFreqCell |
|--00000- |2.1.1.1.3.1.1.1.2.1.1 intraFreqCellID |0 |
| |2.1.1.1.3.1.1.1.2.1.2 cellInfo |
|-000000- |2.1.1.1.3.1.1.1.2.1.2.1 cellIndividualOffset |-20 |
| |2.1.1.1.3.1.1.1.2.1.2.2 modeSpecificInfo |
| |2.1.1.1.3.1.1.1.2.1.2.2.1 fdd |
| |2.1.1.1.3.1.1.1.2.1.2.2.1.1 primaryCPICH-Info |
|***b9*** |2.1.1.1.3.1.1.1.2.1.2.2.1.1.1 primaryScramb.. |3 |
|***b6*** |2.1.1.1.3.1.1.1.2.1.2.2.1.2 primaryCPICH-TX.. |30 |
|-1------ |2.1.1.1.3.1.1.1.2.1.2.2.1.3 readSFN-Indicator |1 |
|--0----- |2.1.1.1.3.1.1.1.2.1.2.2.1.4 tx-DiversityInd.. |0 |
7.2. Measurement Control and Report Procedure
Measurement Control 1(4)
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 103
7.2. Measurement Control and Report Procedure
| |2.1.1.1.3.1.1.1.2.2 newIntraFreqCell |
|***b5*** |2.1.1.1.3.1.1.1.2.2.1 intraFreqCellID |1 |
| |2.1.1.1.3.1.1.1.2.2.2 cellInfo |
|***b6*** |2.1.1.1.3.1.1.1.2.2.2.1 cellIndividualOffset |-20 |
| |2.1.1.1.3.1.1.1.2.2.2.2 modeSpecificInfo |
| |2.1.1.1.3.1.1.1.2.2.2.2.1 fdd |
| |2.1.1.1.3.1.1.1.2.2.2.2.1.1 primaryCPICH-Info |
|***b9*** |2.1.1.1.3.1.1.1.2.2.2.2.1.1.1 primaryScramb.. |5 |
|***b6*** |2.1.1.1.3.1.1.1.2.2.2.2.1.2 primaryCPICH-TX.. |30 |
|---1---- |2.1.1.1.3.1.1.1.2.2.2.2.1.3 readSFN-Indicator |1 |
|----0--- |2.1.1.1.3.1.1.1.2.2.2.2.1.4 tx-DiversityInd.. |0 |
| |2.1.1.1.3.1.1.1.2.3 newIntraFreqCell |
|***b5*** |2.1.1.1.3.1.1.1.2.3.1 intraFreqCellID |2 |
| |2.1.1.1.3.1.1.1.2.3.2 cellInfo |
|***b6*** |2.1.1.1.3.1.1.1.2.3.2.1 cellIndividualOffset |-18 |
| |2.1.1.1.3.1.1.1.2.3.2.2 modeSpecificInfo |
| |2.1.1.1.3.1.1.1.2.3.2.2.1 fdd |
| |2.1.1.1.3.1.1.1.2.3.2.2.1.1 primaryCPICH-Info |
|***b9*** |2.1.1.1.3.1.1.1.2.3.2.2.1.1.1 primaryScramb.. |1 |
|***b6*** |2.1.1.1.3.1.1.1.2.3.2.2.1.2 primaryCPICH-TX.. |30 |
|-----1-- |2.1.1.1.3.1.1.1.2.3.2.2.1.3 readSFN-Indicator |1 |
|------0- |2.1.1.1.3.1.1.1.2.3.2.2.1.4 tx-DiversityInd.. |0 |
| |2.1.1.1.3.1.1.2 intraFreqMeasQuantity |
| |2.1.1.1.3.1.1.2.1 filterCoefficient |fc0 |
| |2.1.1.1.3.1.1.2.2 modeSpecificInfo |
| |2.1.1.1.3.1.1.2.2.1 fdd |
|-00----- |2.1.1.1.3.1.1.2.2.1.1 intraFreqMeasQuantity.. |cpich-Ec-N0 |
| |2.1.1.1.3.1.1.3 intraFreqReportingQuantity |
| |2.1.1.1.3.1.1.3.1 activeSetReportingQuantities |
|----00-- |2.1.1.1.3.1.1.3.1.1 sfn-SFN-OTD-Type |noReport |
|------0- |2.1.1.1.3.1.1.3.1.2 cellIdentity-reportingI.. |0 |
|-------1 |2.1.1.1.3.1.1.3.1.3 cellSynchronisationInfo.. |1 |
Measurement Control 2(4)
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 104
| |2.1.1.1.3.1.1.3.1.4 modeSpecificInfo |
| |2.1.1.1.3.1.1.3.1.4.1 fdd |
|-1------ |2.1.1.1.3.1.1.3.1.4.1.1 cpich-Ec-N0-reporti.. |1 |
|--0----- |2.1.1.1.3.1.1.3.1.4.1.2 cpich-RSCP-reportin.. |0 |
|---0---- |2.1.1.1.3.1.1.3.1.4.1.3 pathloss-reportingI.. |0 |
| |2.1.1.1.3.1.1.3.2 monitoredSetReportingQuantities |
|----00-- |2.1.1.1.3.1.1.3.2.1 sfn-SFN-OTD-Type |noReport |
|------0- |2.1.1.1.3.1.1.3.2.2 cellIdentity-reportingI.. |0 |
|-------1 |2.1.1.1.3.1.1.3.2.3 cellSynchronisationInfo.. |1 |
| |2.1.1.1.3.1.1.3.2.4 modeSpecificInfo |
| |2.1.1.1.3.1.1.3.2.4.1 fdd |
|-1------ |2.1.1.1.3.1.1.3.2.4.1.1 cpich-Ec-N0-reporti.. |1 |
|--0----- |2.1.1.1.3.1.1.3.2.4.1.2 cpich-RSCP-reportin.. |0 |
|---0---- |2.1.1.1.3.1.1.3.2.4.1.3 pathloss-reportingI.. |0 |
| |2.1.1.1.3.1.1.4 reportCriteria |
| |2.1.1.1.3.1.1.4.1 intraFreqReportingCriteria |
| |2.1.1.1.3.1.1.4.1.1 eventCriteriaList |
| |2.1.1.1.3.1.1.4.1.1.1 intraFreqEventCriteria |
| |2.1.1.1.3.1.1.4.1.1.1.1 event |
| |2.1.1.1.3.1.1.4.1.1.1.1.1 e1a |
|001----- |2.1.1.1.3.1.1.4.1.1.1.1.1.1 triggeringCondi.. |monitoredSetCellsOnly |
|---00011 |2.1.1.1.3.1.1.4.1.1.1.1.1.2 reportingRange |3 |
|00000--- |2.1.1.1.3.1.1.4.1.1.1.1.1.3 w |0 |
|-----010 |2.1.1.1.3.1.1.4.1.1.1.1.1.4 reportDeactivat.. |t2 |
|111----- |2.1.1.1.3.1.1.4.1.1.1.1.1.5 reportingAmount |ra-Infinity |
|---011-- |2.1.1.1.3.1.1.4.1.1.1.1.1.6 reportingInterval |ri1 |
|***b4*** |2.1.1.1.3.1.1.4.1.1.1.2 hysteresis |0 |
|--0000-- |2.1.1.1.3.1.1.4.1.1.1.3 timeToTrigger |ttt0 |
| |2.1.1.1.3.1.1.4.1.1.1.4 reportingCellStatus |
|--100--- |2.1.1.1.3.1.1.4.1.1.1.4.1 allActiveplusMoni.. |viactCellsPlus5 |
7.2. Measurement Control and Report Procedure
Measurement Control 3(4)
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 105
| |2.1.1.1.3.1.1.4.1.1.2 intraFreqEventCriteria |
| |2.1.1.1.3.1.1.4.1.1.2.1 event |
| |2.1.1.1.3.1.1.4.1.1.2.1.1 e1b |
|---00--- |2.1.1.1.3.1.1.4.1.1.2.1.1.1 triggeringCondi.. |activeSetCellsOnly |
|***b5*** |2.1.1.1.3.1.1.4.1.1.2.1.1.2 reportingRange |3 |
|--00000- |2.1.1.1.3.1.1.4.1.1.2.1.1.3 w |0 |
|***b4*** |2.1.1.1.3.1.1.4.1.1.2.2 hysteresis |0 |
|---0000- |2.1.1.1.3.1.1.4.1.1.2.3 timeToTrigger |ttt0 |
| |2.1.1.1.3.1.1.4.1.1.2.4 reportingCellStatus |
|---010-- |2.1.1.1.3.1.1.4.1.1.2.4.1 withinActiveSet |e3 |
| |2.1.1.1.3.1.1.4.1.1.3 intraFreqEventCriteria |
| |2.1.1.1.3.1.1.4.1.1.3.1 event |
| |2.1.1.1.3.1.1.4.1.1.3.1.1 e1c |
|---011-- |2.1.1.1.3.1.1.4.1.1.3.1.1.1 replacementActi.. |t3 |
|***b3*** |2.1.1.1.3.1.1.4.1.1.3.1.1.2 reportingAmount |ra1 |
|-000---- |2.1.1.1.3.1.1.4.1.1.3.1.1.3 reportingInterval |noPeriodicalreporting |
|----0000 |2.1.1.1.3.1.1.4.1.1.3.2 hysteresis |0 |
|0000---- |2.1.1.1.3.1.1.4.1.1.3.3 timeToTrigger |ttt0 |
| |2.1.1.1.3.1.1.4.1.1.3.4 reportingCellStatus |
|100----- |2.1.1.1.3.1.1.4.1.1.3.4.1 allActiveplusMoni.. |viactCellsPlus5 |
| |2.1.1.1.4 measurementReportingMode |
|---0---- |2.1.1.1.4.1 measurementReportTransferMode |acknowledgedModeRLC |
|----1--- |2.1.1.1.4.2 periodicalOrEventTrigger |eventTrigger |
7.2. Measurement Control and Report Procedure
Measurement Control 4(4)
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 106
|TS 25.331 DCCH-UL (2002-03) (RRC_DCCH_UL) measurementReport (= measurementReport) |
|uL-DCCH-Message |
| |1 integrityCheckInfo |
|**b32*** |1.1 messageAuthenticationCode |'11111000011011110101100100001111'B|
|-0100--- |1.2 rrc-MessageSequenceNumber |4 |
| |2 message |
| |2.1 measurementReport |
|***b4*** |2.1.1 measurementIdentity |14 |
| |2.1.2 measuredResults |
| |2.1.2.1 intraFreqMeasuredResultsList |
| |2.1.2.1.1 cellMeasuredResults |
| |2.1.2.1.1.1 cellSynchronisationInfo |
| |2.1.2.1.1.1.1 modeSpecificInfo |
| |2.1.2.1.1.1.1.1 fdd |
| |2.1.2.1.1.1.1.1.1 countC-SFN-Frame-difference |
|0000---- |2.1.2.1.1.1.1.1.1.1 countC-SFN-High |0 |
|***b8*** |2.1.2.1.1.1.1.1.1.2 off |6 |
|**b16*** |2.1.2.1.1.1.1.1.2 tm |16896 |
| |2.1.2.1.1.2 modeSpecificInfo |
| |2.1.2.1.1.2.1 fdd |
| |2.1.2.1.1.2.1.1 primaryCPICH-Info |
|***b9*** |2.1.2.1.1.2.1.1.1 primaryScramblingCode |3 |
|-100101- |2.1.2.1.1.2.1.2 cpich-Ec-N0 |37 |
7.2. Measurement Control and Report Procedure
Measurement Report 1(2)
Alexander Seifarth
CONFIDENTIAL - DRAFT J une 1, 2005 107
7.2. Measurement Control and Report Procedure
| |2.1.2.1.2 cellMeasuredResults |
| |2.1.2.1.2.1 cellSynchronisationInfo |
| |2.1.2.1.2.1.1 modeSpecificInfo |
| |2.1.2.1.2.1.1.1 fdd |
| |2.1.2.1.2.1.1.1.1 countC-SFN-Frame-difference |
|----0000 |2.1.2.1.2.1.1.1.1.1 countC-SFN-High |0 |
|00000110 |2.1.2.1.2.1.1.1.1.2 off |6 |
|***B2*** |2.1.2.1.2.1.1.1.2 tm |17372 |
| |2.1.2.1.2.2 modeSpecificInfo |
| |2.1.2.1.2.2.1 fdd |
| |2.1.2.1.2.2.1.1 primaryCPICH-Info |
|***b9*** |2.1.2.1.2.2.1.1.1 primaryScramblingCode |1 |
|***b6*** |2.1.2.1.2.2.1.2 cpich-Ec-N0 |15 |
| |2.1.3 eventResults |
| |2.1.3.1 intraFreqEventResults |
|***b4*** |2.1.3.1.1 eventID |e1a |
| |2.1.3.1.2 cellMeasurementEventResults |
| |2.1.3.1.2.1 fdd |
| |2.1.3.1.2.1.1 primaryCPICH-Info |
|***b9*** |2.1.3.1.2.1.1.1 primaryScramblingCode |3 |
Measurement Report 2(2)
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 1
Module 04
Complete Sequences Use Cases
(Layer 3 signalling)
Version 0.0.1 (02/05/2005)
Author: Alexander Seifarth (a.seifarth@techcom.de)
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 2
1. CS Mobility Management
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 3
1. CS Mobility Management
1.1. Location Area Update
UE is UTRA idle;
UE is PS detached;
performs cell reselection
no services follow after update
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 4
1.1. Location Area Update (1)
UE RNC
UTRA_Idle
RRC Connection Request
[CCCH] RRC
Initial UE ID = IMSI|TMSI+LAI, Est.Cause = registration
MSC
Server
Initial UE Message
RANAP
CN domain = cs, LAI, SAI, RNC-ID,
NAS-PDU = Location Updating Request
cell reselection
New LAI ?
false
true
RRC Connection Setup
[CCCH] RRC
U-RNTI, C-RNTI, signalling radio bearer RB1..RB4, TrCH configuration,
PhCH configuration, radio access capability update requirement
RRC Connection Setup Complete
[DCCH] RRC
UE radio access capabilities
Initial Direct Transfer
[DCCH] RRC
CN domain = cs, NAS-PDU = MM-message: Location Updating Request
CELL_DCH| CELL_FACH
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 5
1.1. Location Area Update (2)
UE RNC
MSC
Server
Direct Transfer RANAP
SAPI=0, NAS-PDU = Authentication Req.
Downlink Direct Transfer [DCCH] RRC
CN domain = cs, NAS-PDU = MM-message: Authentication Request
Direct Transfer RANAP
LAI, SAI, NAS-PDU = Authentication Resp.
Uplink Direct Transfer
[DCCH] RRC
CN domain = cs, NAS-PDU = MM-message: Authentication Response
Security Mode Command RANAP
permitted UIA, IK, permitted UEA, CK,
Security Mode Command [DCCH] RRC
selected UIA, selected UEA, ciphering activation time,
Security Mode Command RANAP
selected UIA, selected UEA
Security Mode Complete
[DCCH] RRC
SGSN
Direct Transfer RANAP
[DCCH] RRC
RAI, SAI, NAS-PDU = Activate PDP Context
Request
CN domain = ps,
NAS-PDU = SM-message: Activate PDP Context Request
Uplink Direct Transfer
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 41
4.1. PDP Context Activation (3)
UE RNC
RAB Assignment Request RANAP
RABSetupOrModifyItemRAB Parameter
Radio Bearer Setup [DCCH] RRC
RRC state = CELL_DCH/FACH, RAB to setup radio bearer to setup,
signalling radio bearer, transport channels to add, physical channel
RAB Assignment Response RANAP
successful setup
Radio Bearer Setup Complete
[DCCH] RRC
SGSN
CELL_DCH| CELL_FACH
Direct Transfer RANAP
SAPI=0, NAS-PDU = Activate PDP Context
Accept
Downlink Direct Transfer [DCCH] RRC
CN domain = ps,
NAS-PDU = SM-message: Activate PDP Context Accept
Packet PDU Transmission
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 42
4. PDP Context Management
4.2. Service Data for uplink traffic
UE is UTRA idle and PMM_Idle,
PDP context is active
uplink packet data shall be sent
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 43
4.2. Service Data for uplink traffic (1)
UE
RNC
UTRA_Idle
RRC Connection Request
[CCCH] RRC
Initial UE ID = IMSI|TMSI+LAI, Est.Cause = high priority signalling
Initial UE Message
RANAP
CN domain = ps, RAI, SAI, RNC-ID,
NAS-PDU = Service Request
uplink PDP PDU
RRC Connection Setup [CCCH] RRC
U-RNTI, C-RNTI, signalling radio bearer RB1..RB4, TrCH configuration,
PhCH configuration, radio access capability update requirement
RRC Connection Setup Complete [DCCH] RRC
UE radio access capabilities
Initial Direct Transfer [DCCH] RRC
CN domain = ps, NAS-PDU = GMM-message: Service Request
(service type = data)
CELL_DCH| CELL_FACH
SGSN
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 44
4.2. Service Data for uplink traffic (2)
UE
RNC
Security Mode Command RANAP
permitted UIA, IK, permitted UEA, CK,
Security Mode Command [DCCH] RRC
selected UIA, selected UEA, ciphering activation time,
Security Mode Command RANAP
selected UIA, selected UEA
Security Mode Complete
[DCCH] RRC
SGSN
RAB Assignment Request RANAP
RABSetupOrModifyItemRAB Parameter
Radio Bearer Setup [DCCH] RRC
RRC state = CELL_DCH/FACH, RAB to setup radio bearer to setup,
signalling radio bearer, transport channels to add, physical channel
RAB Assignment Response RANAP
successful setup
Radio Bearer Setup Complete
[DCCH] RRC
CELL_DCH| CELL_FACH
Packet PDU Transmission
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 45
4. PDP Context Management
4.3. Service Data for downlink traffic
UE is UTRA idle and PMM_Idle,
PDP context is active
downlink packet data shall be sent
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 46
4.3. Service Data for downlink traffic (1)
UE
RNC
UTRA_Idle
RRC Connection Request
[CCCH] RRC
Initial UE ID = IMSI|TMSI+LAI, Est.Cause = terminating cause unkn.
Initial UE Message
RANAP
CN domain = ps, RAI, SAI, RNC-ID,
NAS-PDU = Service Request
RRC Connection Setup [CCCH] RRC
U-RNTI, C-RNTI, signalling radio bearer RB1..RB4, TrCH configuration,
PhCH configuration, radio access capability update requirement
RRC Connection Setup Complete [DCCH] RRC
UE radio access capabilities
Initial Direct Transfer [DCCH] RRC
CN domain = ps, NAS-PDU = GMM-message: Service Request
(service type = paging response)
CELL_DCH| CELL_FACH
SGSN
Paging Type 1 [PCCH] RRC
UE-ID = TMSI|IMSI, cause = terminating cause unknown
Paging RANAP
CN domain = ps, RAI, IMSI, PTMSI, cause
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 47
4.3. Service Data for downlink traffic (2)
UE
RNC
Security Mode Command RANAP
permitted UIA, IK, permitted UEA, CK,
Security Mode Command [DCCH] RRC
selected UIA, selected UEA, ciphering activation time,
Security Mode Command RANAP
selected UIA, selected UEA
Security Mode Complete
[DCCH] RRC
SGSN
RAB Assignment Request RANAP
RABSetupOrModifyItemRAB Parameter
Radio Bearer Setup [DCCH] RRC
RRC state = CELL_DCH/FACH, RAB to setup radio bearer to setup,
signalling radio bearer, transport channels to add, physical channel
RAB Assignment Response RANAP
successful setup
Radio Bearer Setup Complete
[DCCH] RRC
CELL_DCH| CELL_FACH
Packet PDU Transmission
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 48
4. PDP Context Management
4.4. PDP Context Deactivation by UE
UE is UTRA connected and PMM_Connected,
PDP context is active and will be deactivated,
ohter PS services are still active
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 49
4.4. PDP Context Deactivation (1)
UE
RNC
UTRA_Connected
SGSN
PMM_Connected
Direct Transfer RANAP
SAPI=0, NAS-PDU = Deact.PDP Context
Accept
Downlink Direct Transfer
[DCCH] RRC
CN domain = ps,
NAS-PDU = SM-message: Deactivate PDP Context Accept
Direct Transfer RANAP
[DCCH] RRC
RAI, SAI, NAS-PDU = Deact. PDP Context
Request
CN domain = ps,
NAS-PDU = SM-message: Deactivate PDP Context Request
Uplink Direct Transfer
RAB Assignment Request RANAP
RABReleaseItemRAB ID
Radio Bearer Release [DCCH] RRC
RRC state = XXX, RAB to reconfigure, RB to release, TrCH to reconf.
RAB Assignment Response RANAP
RAB data volume
Radio Bearer Release Complete
[DCCH] RRC
UTRA_XXX
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 50
5. Radio Management Procedures
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 51
5. Radio Management Procedures
5.1. Soft Handover
UE is UTRA connected in state CELL_DCH,
soft handover including cell 1, cell 2, cell 3
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 52
5.1. Soft Handover (1 add radio link)
UE
RNC
CELL_DCH
Measurement Report [DCCH] RRC
trigger event = 1A for cell 2, measured results
Measurement Control [DCCH] RRC
intra-frequency cell list for cell 1, reporting criteria events 1A, 1B, 1C
cell 1
Active Set
Active Set Update
[DCCH] RRC
cell addition info downlink code information for cell 2
Active Set Update Complete [DCCH] RRC
Measurement Control [DCCH] RRC
intra-frequency cell list for cell 1/2, reporting criteria events 1A, 1B, 1C
CELL_DCH cell 1, cell 2
Active Set
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 53
5.1. Soft Handover (2 replacement)
UE
RNC
Measurement Report [DCCH] RRC
trigger event = 1C for cell 3/1, measured results
Active Set Update
[DCCH] RRC
cell addition info downlink code information for cell 3
cell removal info radio link id cell 1
Active Set Update Complete [DCCH] RRC
Measurement Control [DCCH] RRC
intra-frequency cell list for cell 3/2, removal of cell 1s neighbour cell list,
reporting criteria events 1A, 1B, 1C
CELL_DCH cell 3, cell 2
Active Set
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 54
5.1. Soft Handover (3 radio link deletion)
UE
RNC
Measurement Report [DCCH] RRC
trigger event = 1B for cell 2, measured results
Active Set Update
[DCCH] RRC
cell removal info radio link id cell 2
Active Set Update Complete [DCCH] RRC
Measurement Control [DCCH] RRC
removal of cell 2s neighbour cell list, reporting criteria events 1A, 1B, 1C
CELL_DCH cell 3
Active Set
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 55
5. Radio Management Procedures
5.2. Packet Radio Bearer Management
UE is UTRA connected and PMM_Connected,
PDP context is active and RAB exists for it
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 56
5.2. Packet Radio Bearer Management (1)
UE
RNC
SGSN
Radio Bearer Release
[DCCH] RRC
RRC state = CELL_PCH/URA_PCH, radio bearer identitiy to release
Radio Bearer Release Complete
[DCCH] RRC
Packet PDU Transmission
CELL_DCH| CELL_FACH
RB Inactivity Timer
CELL_PCH| URA_PCH
Expiry of all
Inactivity Timers
uplink PDP PDU
Cell Update [CCCH] RRC
U-RNTI, cause = uplink data transmission
Cell Update Confirm [CCCH] RRC
U-RNTI, RRC state = CELL_DCH/FACG, radio bearer to set up
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 57
5.2. Packet Radio Bearer Management (2)
UE
RNC
SGSN
Radio Bearer Setup Complete [DCCH] RRC
CELL_DCH| CELL_FACH
Radio Bearer Release
[DCCH] RRC
RRC state = CELL_PCH/URA_PCH, radio bearer identitiy to release
Radio Bearer Release Complete
[DCCH] RRC
Packet PDU Transmission
RB Inactivity Timer
CELL_PCH| URA_PCH
Expiry of all
Inactivity Timers
Alexander Seifarth
J une 1, 2005 CONFIDENTIAL - DRAFT 58
5.2. Packet Radio Bearer Management (3)
UE
RNC
SGSN
Paging Type 1 [PCCH] RRC
U-RNTI
Packet PDU Transmission
Cell Update [CCCH] RRC
U-RNTI, cause = paging response
Cell Update Confirm [CCCH] RRC
U-RNTI, RRC state = CELL_DCH/FACG, radio bearer to set up
Radio Bearer Setup Complete [DCCH] RRC
CELL_DCH| CELL_FACH
Packet PDU Transmission
Packet PDU Transmission
RB Inactivity Timer