8.3.3 UTRAN Mobility Information
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
8.3.3.1 UTRAN Mobility Information: Success
8.3.3.1.1 Definition
8.3.3.1.2 Conformance requirement
When the UE receives a UTRAN MOBILITY INFORMATION message, it shall:
1> act on received information elements as specified in TS 25.331 subclause 8.6;
1> if the IE "UE Timers and constants in connected mode" is present:
2> store the values of the IE "UE Timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS, replacing any previously stored value for each timer and constant; and
2> for each updated timer value:
3> start using the new value next time the timer is started;
NOTE: If a new value of timer T305 is included in the IE "UE Timers and constants in connected mode", and the old value of timer T305 is "infinity", the UE will not use the new value of the timer T305 until the next cell reselection.
2> for each updated constant value:
3> start using the new value directly;
…
1> transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC;
….
If the IE "New U-RNTI" is included in a received message, the UE shall:
1> store the value in the variable U_RNTI, replacing any old stored value.
…
If the IE "New C-RNTI" is included, the UE shall:
1> store the value in the variable C_RNTI, replacing any old stored value;
1> use that C-RNTI when using common transport channels of type RACH, and FACH in the current cell.
…
In case of cell update procedure the UE shall transmit a CELL UPDATE message.
The UE shall set the IEs in the CELL UPDATE message as follows:
…
1> set the IE "U-RNTI" to the value of the variable U_RNTI;
…
Reference
3GPP TS 25.331 clauses 8.3.3, 8.6.3.9, 8.6.3.10, 8.3.1.3.
8.3.3.1.3 Test purpose
1. To confirm that the UE starts to use the new identities after it receives a UTRAN MOBILITY INFORMATION message from the SS.
8.3.3.1.4 Method of test
Initial Condition
System Simulator: 1 cell
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Specific Message Contents
For system information block 1 of Cell 1 (gives IE’s which are different from defaults given in 34.108 subclause 6.1) to be transmitted before idle update preamble.
System Information Block type 1
Use the same message sub-type found in clause 6.1 of TS 34.108, with the following exception:
|
Information Element |
Value/remark |
|
-T305 |
10 |
Test Procedure
Initially, the UE is in CELL_FACH state and it has been assigned a C-RNTI and U-RNTI. SS waits for T305 to expire. The UE shall transmit a CELL UPDATE message. SS sends CELL UPDATE CONFIRM message to the UE on the downlink CCCH. Then SS transmits an UTRAN MOBILITY INFORMATION message which includes new C-RNTI and U-RNTI to the UE. Then the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message using the assigned new C-RNTI in MAC header as confirmation. SS waits for UE to perform periodic cell updating. When SS received a CELL UPDATE message, SS checks that UE uses the new U-RNTI in the CELL UPDATE message. Then SS sends CELL UPDATE CONFIRM on the downlink CCCH. SS waits for UE to perform periodic cell updating. When SS received a CELL UPDATE message, SS sends CELL UPDATE CONFIRM on the downlink CCCH to end the test procedure.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
The initial state of the UE is CELL_FACH state. UE has been allocated both C-RNTI and U-RNTI during RRC connection establishment phase. |
|||
|
1a |
SS waits for a period up to timer T305 to allow the UE to start performing a cell updating procedure. |
|||
|
1b |
|
CELL UPDATE |
||
|
1c |
|
CELL UPDATE CONFIRM |
||
|
2 |
|
UTRAN MOBILITY INFORMATION |
Contains new C-RNTI and U-RNTI identities and a value for T305 that is different from the value defined in the system information. |
|
|
3 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
The assigned new C-RNTI shall be included in MAC header. |
|
|
4 |
SS wait for T305 (same as the value defined in system information) to expire. |
|||
|
5 |
|
CELL UPDATE |
UE shall trigger cell updating. The message shall indicate the same U-RNTI assigned in the UTRAN MOBILITY INFORMATION message in step 2. |
|
|
6 |
|
CELL UPDATE CONFIRM |
||
|
7 |
SS wait for T305 (the new value as specified in step 2) to expire. |
|||
|
8 |
|
CELL UPDATE |
UE shall trigger cell updating. The message shall indicate the same U-RNTI assigned in the UTRAN MOBILITY INFORMATION message in step 2. |
|
|
9 |
|
CELL UPDATE CONFIRM |
||
|
10 |
|
CALL C.2 |
If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails. |
|
Specific Message Content
UTRAN MOBILITY INFORMATION (Step 2)
Use the same message sub-type as in TS 34.108, clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
New U-RNTI |
|
|
– SRNC Identity |
‘0000 0000 0001’ |
|
– S-RNTI |
‘0101 0101 0101 0101 0101’ |
|
New C-RNTI |
’0000 0000 0000 1111’ |
|
UE Timers and constants in connected mode |
|
|
– T305 |
5 minutes |
UTRAN MOBILITY INFORMATION CONFIRM (Step 3)
Only the message type IE is checked in this message.
CELL UPDATE (Step 1b)
The same message found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink CCCH.
CELL UPDATE (Step 5 and 8)
The same message found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:
|
Information Element |
Value/remark |
|
U-RNTI |
|
|
– SRNC Identity |
Check to see if set to ‘0000 0000 0001’ |
|
– S-RNTI |
Check to see if set to ‘0101 0101 0101 0101 0101’ |
|
Cell Update Cause |
Check to see if set to ‘periodical cell updating’ |
CELL UPDATE CONFIRM (Step 1c)
Use the same message sub-type as in TS 34.108, clause 9.
CELL UPDATE CONFIRM (Step 6 and 9)
Use the same message sub-type as in TS 34.108, clause 9 on the downlink CCCH, with the exception of the following IEs:
|
Information Element |
Value/remark |
|
U-RNTI |
|
|
– SRNC Identity |
Check to see if set to ‘0000 0000 0001’ |
|
– S-RNTI |
Check to see if set to ‘0101 0101 0101 0101 0101’ |
8.3.3.1.5 Test requirement
After step 2 the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH that using the assigned new C-RNTI in MAC header.
After step 4 and 7 the UE shall transmit a CELL UPDATE message on the uplink CCCH with IE "Cell update cause" set to "periodical cell updating". The IE "U-RNTI" shall be identical to the IE "New RNTI" found in UTRAN MOBILITY INFORMATION message sent by the SS in step 2.
8.3.3.2 UTRAN Mobility Information: Failure (Invalid message reception)
8.3.3.2.1 Definition
8.3.3.2.2 Conformance Requirements
If the UTRAN MOBILITY INFORMATION message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to TS 25.331 clause 9, the UE shall perform procedure specific error handling as follows. The UE shall:
1> transmit a UTRAN MOBILITY INFORMATION FAILURE message on the uplink DCCH using AM RLC;
1> set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION FAILURE message to the value of "RRC transaction identifier" in the entry for the UTRAN MOBILITY INFORMATION message in the table "Rejected transactions" in the variable TRANSACTIONS, and;
1> set the IE "failure cause" to the cause value "protocol error";
1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION;
1> when the UTRAN MOBILITY INFORMATION FAILURE message has been submitted to lower layers for transmission:
2> continue with any ongoing processes and procedures as if the invalid UTRAN MOBILITY INFORMATION message has not been received;
2> and the procedure ends.
References
3GPP TS 25.331 clauses 8.3.3.6
8.3.3.2.3 Test Purpose
1. To confirm that the UE ignore the erroneous UTRAN MOBILITY INFORMATION message and report this event to the UTRAN by sending UTRAN MOBILITY INFORMATION FAILURE message, stating the appropriate failure cause and information.
8.3.3.2.4 Method of test
Initial Conditions
System Simulator: 1 cell.
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Specific Message Contents
For system information block 1 (given IEs which are different from defaults given in TS34.108 clause 6.1) to be transmitted before idle update preamble.
System Information Block type 1
|
Information Element |
Value/remark |
|
T305 |
5 minutes |
Test Procedure
The UE is brought to CELL_FACH state. SS waits for T305 to expire. The UE shall transmit a CELL UPDATE message. SS sends CELL UPDATE CONFIRM message to the UE on the downlink DCCH. Then SS transmits a UTRAN MOBILITY INFORMATION message, which contains an unexpected critical message extension, to the UE on the DCCH using AM-RLC mode. The UE shall respond by transmitting the UTRAN MOBILITY INFORMATION FAILURE message, indicating "protocol error" in IE "failure cause" and also "Message extension not comprehended " in IE "Protocol error information". After receiving the UTRAN MOBILITY INFORMATION FAILURE message, SS waits for T305 to expire. The UE shall transmit a CELL UPDATE message with the original U-RNTI identity assigned. SS sends CELL UPDATE CONFIRM message to the UE on the downlink DCCH.
Expected Sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
The initial state of the UE is CELL_FACH state. |
|||
|
1a |
SS waits for a period up to timer T305 to allow the UE to start performing a cell updating procedure. |
|||
|
1b |
|
CELL UPDATE |
||
|
1c |
|
CELL UPDATE CONFIRM |
||
|
2 |
|
UTRAN MOBILITY INFORMATION |
See specific message content. |
|
|
3 |
|
UTRAN MOBILITY INFORMATION FAILURE |
UE shall transmit this message to report the error in UTRAN MOBILITY INFORMATION message. It shall include the appropriate cause in the message. |
|
|
4 |
SS waits for a period up to timer T305 to allow the UE to start performing a cell updating procedure. |
|||
|
5 |
|
CELL UPDATE |
||
|
6 |
|
CELL UPDATE CONFIRM |
||
Specific Message Content
UTRAN MOBILITY INFORMATION (Step 2)
Use the UTRAN MOBILITY INFORMATION message as defined in [9] TS 34.108 clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Critical extensions |
’FF’H |
UTRAN MOBILITY INFORMATION FAILURE (Step 3)
Check to see if the same message type found in [9] TS 34.108 Clause 9 is received, with the following exceptions:
|
Information Element |
Value/remark |
|
Failure Cause |
|
|
– Failure Cause |
Check to see if set to ‘Protocol error’ |
|
– Protocol Error Information |
Check to see if set to Message extension not comprehended |
CELL UPDATE (Step 1b and 5)
The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:
|
Information Element |
Value/remark |
|
U-RNTI |
|
|
– SRNC Identity |
Check to see if set to ‘0000 0000 0001’B |
|
– S-RNTI |
Check to see if set to ‘0000 0000 0000 0000 0001’B |
|
Cell update cause |
Check to see if set to ‘periodical cell updating’ |
CELL UPDATE CONFIRM (Step 1c and 6)
Use the same message sub-type as in TS 34.108 clause 9.
8.3.3.2.5 Test Requirement
After step 1a the UE shall initiate a periodic cell updating procedure by transmitting CELL UPDATE message on the CCCH. In this message, the U-RNTI identity shall be set to the same value as assigned during the RRC connection establishment procedure.
After step 2 the UE shall transmit UTRAN MOBILITY INFORMATION FAILURE message, indicating the value "protocol error" in IE "failure cause" and also "Message extension not comprehended" in IE "protocol error information".
After step 4 the UE shall initiate a periodic cell updating procedure by transmitting CELL UPDATE message on the CCCH. In this message, the U-RNTI identity shall be set to the same value as assigned during the RRC connection establishment procedure.
8.3.3.3 UTRAN MOBILITY INFORMATION: Seamless SRNS relocation in CELL_DCH (without pending of ciphering)
8.3.3.3.1 Definition
8.3.3.3.2 Conformance requirement
To initiate the procedure UTRAN transmits a UTRAN MOBILITY INFORMATION message to the UE on the downlink DCCH using AM or UM RLC. In case of SRNS relocation, the message is sent using UM RLC only.
When the UE receives a UTRAN MOBILITY INFORMATION message, it shall:
1> if the UTRAN MOBILITY INFORMATION message contained the IE "Ciphering mode info" or contained the IE "Integrity protection mode info":
2> set the IE "Status" in the variable SECURITY_MODIFICATION for all the CN domains in the variable SECURITY_MODIFICATION to "Affected";
1> if the UTRAN MOBILITY INFORMATION message contained the IE "Ciphering mode info":
2> include and set the IE "Radio bearer uplink ciphering activation time info" to the value of the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO.
1> if the received UTRAN MOBILITY INFORMATION message included the IE " Downlink counter synchronisation info ":
2> re-establish the RLC entity for RB2;
2> set the new uplink and downlink HFN component of COUNT-C of RB2 to MAX(uplink HFN component of COUNT-C of RB2, downlink HFN component of COUNT-C of RB2);
2> increment by one the downlink and uplink values of the HFN component of COUNT-C for RB2;
2> calculate the START value according to TS 25.331 subclause 8.5.9;
2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info" in the UTRAN MOBILITY INFORMATION CONFIRM message.
1> transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC;
1> if the IE "Integrity protection mode info" was present in the UTRAN MOBILITY INFORMATION message:
2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted UTRAN MOBILITY INFORMATION CONFIRM message.
1> if the IE "Downlink counter synchronisation info" was included in the received UTRAN MOBILITY INFORMATION message:
2> when RLC has confirmed the successful transmission of the response message:
3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain;
3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;
3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero;
3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS.
1> apply the new ciphering configuration as follows:
2> if the IE "Radio bearer downlink ciphering activation time info" is present:
3> apply the following procedure for each radio bearer and signalling radio bearers using RLC-AM or RLC-UM indicated by the IE "RB identity":
….
4> switch to the new ciphering configuration according to the following:
…
5> if an RLC reset or re-establishment occurs before the activation time for the new ciphering configuration has been reached, ignore the activation time and apply the new ciphering configuration immediately after the RLC reset or RLC re-establishment.
1> if IE "Integrity protection mode command" has the value "start" and the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started" and this IE was not included SECURITY MODE COMMAND:
NOTE: This case is used in SRNS relocation
2> perform integrity protection on the received message, applying the new integrity protection configuration, as described in subclause 8.5.10.1 of TS25.331 by:
3> using the algorithm (UIA defined in TS33.102) indicated by the IE "Integrity protection algorithm" contained in the IE "Integrity protection mode info";
3> using the IE "Integrity protection initialisation number", contained in the IE "Integrity protection mode info" as the value of FRESH defined in TS33.102.
2> let RBm be the signalling radio bearer where the reconfiguration message was received and let RBn be the signalling radio bearer where the response message is transmitted;
2> prohibit transmission of RRC messages on all signalling radio bearers in the IE "ESTABLISHED_RABS" except on RB0 and the radio bearer where the response message is transmitted;
2> if for a signalling radio bearer, a security configuration triggered by a previous SECURITY MODE COMMAND is pending, due to the activation time for the signalling radio bearer not having elapsed:
3> if the previous SECURITY MODE COMMAND was received due to new keys being received:
4> consider the new integrity protection configuration to include the received new keys; and
4> initialise the HFN of the COUNT-I values of the corresponding signalling radio bearers according to subclause 8.1.12.
3> else:
4> consider the new Integrity Protection configuration to include the keys associated with the LATEST_CONFIGURED_CN_DOMAIN associated with the previously received SECURITY MODE COMMAND; and
4> initialise the HFN of the COUNT-I values of the corresponding signalling radio bearers according to subclause 8.1.12 using the START value associated with the LATEST_CONFIGURED_CN_DOMAIN to be transmitted in the response to the current message.
2> start applying the new integrity protection configuration in the downlink for each signalling radio bearer in the IE "ESTABLISHED_RABS" except RBm at the next received RRC message disregarding any pending activation times for the corresponding signalling radio bearer;
2> start applying the new integrity protection configuration in the downlink for signalling radio bearer RBm from and including the received configuration message;
2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RBn from and including the transmitted response message;
2> start applying the new integrity protection configuration in the uplink for signalling radio bearers other than RBn from the first message onwards.
NOTE: The UTRAN should ignore the information included in the IE "Uplink integrity protection info".
Reference
3GPP TS 25.331 clause 8.3.3 , 8.6.3.4 and 8.6.3.5
8.3.3.3.3 Test purpose
1. To confirm that the UE sends calculated START values for each CN domain to SS after a successful SRNS relocation.
2. In the case that ciphering is applied by the network, to confirm that the UE restarts ciphering following a successful SRNS relocation.
3. To confirm that the UE correctly applies integrity protection after the SRNS relocation.
8.3.3.3.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: PS-DCCH+DTCH_DCH (state 6-10) or CS-DCCH+DTCH_DCH (state 6-9) or PS+CS-DCCH+DTCH_DCH (state 6-14) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Test Procedure
The UE is in the CELL_DCH state. SS then transmits a UTRAN MOBILITY INFORMATION message, which includes a valid “New U-RNTI”, IE “Downlink counter synchronisation info” and IE “Integrity protection mode info”, to the UE on the downlink DCCH using UM RLC. SS verifies that the UE sends UTRAN MOBILITY INFORMATION CONFIRM message. This message also includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using a new FRESH value as included in IE “Integrity protection initialisation number” in IE “Integrity protection mode info” in UTRAN MOBILITY INFORMATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration.
SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM. The UE shall respond to downlink message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS responds with UE CAPABILITY INFORMATION CONFIRM message. SS then send IDENTITY REQUEST message on the DCCH using RLC-AM (SRB3) in order to confirm that the UE can communicate on SRB3 by using new integrity configuration. The UE shall respond IDENTITY RESPONSE message on the uplink DCCH using RLC-AM (SRB3).
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
|
UTRAN MOBILITY INFORMATION |
If IE “Ciphering mode info” is present in the SECURITY MODE COMMAND during initial condition set-up, this message is sent after last ciphering activation time has elapsed and there is no pending ciphering activation time. New U-RNTI identities are assigned to the UE. IE “Downlink counter synchronisation info” is included. New integrity protection configuration is applied on DL SRB1. |
|
|
2 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
New calculated START value is included. New integrity protection configuration is applied on UL SRB2. If IE “Ciphering mode info” is present in step 1, new ciphering configuration is applied on UL SRB2 with the downlink and uplink values of the HFN component of COUNT-C for SRB2 incremented by one. |
|
|
3 |
|
UE CAPABILITY ENQUIRY |
New integrity protection configuration is applied on DL SRB2. If IE “Ciphering mode info” is present in step 1, new ciphering configuration is applied on DL SRB2 with the same START value as used in step 2. |
|
|
4 |
|
UE CAPABILITY INFORMATION |
||
|
5 |
|
UE CAPABILITY INFORMATION CONFIRM |
||
|
6 |
|
DOWNLINK DIRECT TRANSFER |
NAS message embedded in this is IDENTITY REQUEST. New integrity protection configuration is applied on DL SRB3. If IE “Ciphering mode info” is present in step 1, new ciphering configuration is applied on DL SRB3 using the re-initialised COUNT-C HFN by the start value as stored in step 2. |
|
|
7 |
|
UPLINK DIRECT TRANSFER |
NAS message embedded in this is IDENTITY RESPONSE. SS confirms that new integrity protection configuration is applied on UL SRB3 by UE. If IE “Ciphering mode info” is present in step 1, new ciphering configuration is applied on UL SRB3 using the re-initialised COUNT-C HFN by the start value as stored in step 2. |
|
Specific Message Contents
UTRAN MOBILITY INFORMATION (Step 1) – for PS domain testing only
Use the same message sub-type found in TS 34.108, clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
If network does not apply ciphering, set this IE to “Not present”. If network applies ciphering, this IE present with the values of the sub IEs as stated below. |
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
Set to an algorithm that is different from the one indicated in the SECURITY MODE COMMAND during the initial condition set-up. |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
Not present |
|
Integrity protection mode info |
|
|
– Integrity protection mode command |
Start |
|
– Downlink integrity protection activation info |
Not Present |
|
– Integrity protection algorithm |
UIA1 |
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
|
New U-RNTI |
|
|
– SRNC Identity |
An arbitrary 12-bits string which is different from original SRNC |
|
– S-RNTI |
An arbitrary 20-bits string which is different from original S-RNTI |
|
New C-RNTI |
Not Present |
|
CN Information info |
|
|
– PLMN identity |
Not present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain specific DRX cycle length coefficient |
7 |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
– CN domain specific DRX cycle length coefficient |
7 |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information list |
Not Present |
UTRAN MOBILITY INFORMATION (Step 1) – for CS domain testing only
Use the same message sub-type found in TS 34.108, clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
If network does not apply ciphering, set this IE to “Not present”. If network applies ciphering, this IE present with the values of the sub IEs as stated below. |
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
Set to an algorithm that is different from the one indicated in the SECURITY MODE COMMAND during the initial condition set-up. |
|
– Ciphering activation time for DPCH |
(256+CFN-(CFN MOD 8 + 8))MOD 256 |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN |
|
Integrity protection mode info |
|
|
– Integrity protection mode command |
Start |
|
– Downlink integrity protection activation info |
Not Present |
|
– Integrity protection algorithm |
UIA1 |
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
|
New U-RNTI |
|
|
– SRNC Identity |
An arbitrary 12-bits string which is different from original SRNC |
|
– S-RNTI |
An arbitrary 20-bits string which is different from original S-RNTI |
|
New C-RNTI |
Not Present |
|
CN Information info |
|
|
– PLMN identity |
Not present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain specific DRX cycle length coefficient |
7 |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
– CN domain specific DRX cycle length coefficient |
7 |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information list |
Not Present |
UTRAN MOBILITY INFORMATION CONFIRM (Step 2) – for PS domain testing only
The same message sub-type found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink DCCH with the following exceptions:
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
Check that this IE is not present. |
|
– START list |
Check that this IE is correct value. |
UTRAN MOBILITY INFORMATION CONFIRM (Step 2) – for CS domain testing only
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
COUNT-C activation time |
Check that this IE is present. |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
Not present |
|
– START list |
Check that this IE has the correct value. |
UE CAPABILITY ENQUIRY (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9.
UE CAPABILITY INFORMATION (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9.
UE CAPABILITY INFORMATION CONFIRM (Step 5)
Use the same message sub-type found in [9] TS 34.108 clause 9.
8.3.3.3.5 Test requirement
After step 1, the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC which includes a calculated new START value according to the formula “STARTX‘ = MSB20 ( MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using the new FRESH value as included in IE ”Integrity protection initialisation number” in IE ”Integrity protection mode info” in UTRAN MOBILITY INFORMATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration. The UE, further more, shall apply the new integrity protection configuration for the first received/sent RRC message on SRB0, SRB3, and SRB4 after receiving the UTRAN MOBILITY INFORMATION message (i.e. immediately). For SRB2 the new integrity protection configuration shall be applied from and including the received UTRAN MOBILITY INFORMATION message (DL) and the sent UTRAN MOBILITY INFORMATION CONFIRM message (UL).
After step 3, the UE shall respond with a UE CAPABILITY INFORMATION message to SS.
After step 6, the UE shall respond with an IDENTITY RESPONSE message to SS and apply new ciphering configuration on UL SRB3.
8.3.3.4 UTRAN Mobility Information: Shared Network
8.3.3.4.1 Definition
8.3.3.4.2 Conformance requirement
1. If the IE "CN information info" is present in a message, the UE shall:
1> if the IE "Primary PLMN Identity" is present:
2> forward the content of the IE "Primary PLMN identity" to upper layers.
1> else:
2> if the IE "PLMN Identity" is present:
3> forward the content of the IE "PLMN identity" to upper layers.
2. The UE shall, in the INITIAL DIRECT TRANSFER message:
1> set the IE "NAS message" as received from upper layers; and
1> set the IE "CN domain identity" as indicated by the upper layers; and
1> set the IE "Intra Domain NAS Node Selector" as follows:
2> derive the IE "Intra Domain NAS Node Selector" from TMSI/PMTSI, IMSI, or IMEI; and
2> provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities:
1. derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a valid TMSI/PTMSI is available;
2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available;
3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE.
1> if the UE, on the existing RRC connection, has received a dedicated RRC message containing the IE "Primary PLMN Identity" in the IE "CN Information Info":
2> set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the latest PLMN information received via dedicated RRC signalling. If NAS has indicated the PLMN towards which a signalling connection is requested, and this PLMN is not in agreement with the latest PLMN information received via dedicated RRC signalling, then the initial direct transfer procedure shall be aborted, and NAS shall be informed.
References
1. 3GPP TS 25.331 clause 8.6.1.2
2. 3GPP TS 25.331 clause 8.1.8.2
8.3.3.4.3 Test purpose
– To verify that the UE reacts on the IE “Primary PLMN identity” in message UTRAN MOBILITY INFORMATION, and forwards this IE to NAS.
– To verify that the UE sets the IE “PLMN Identity” in the INITIAL DIRECT TRANSFER message to the correct PLMN information received in UTRAN MOBILITY INFORMATION message.
8.3.3.4.4 Method of test
Initial condition
System Simulator:
– Cell 1 broadcasting PLMN1 on BCCH.
– For MASTER INFORMATION BLOCK see specific message content
User Equipment:
The UE is equipped with a USIM containing default values. The HPLMN (MCC+MNC) of the IMSI for the USIM is set to PLMN1.
The UE is registered in CS and PS domains on PLMN1 (MM Idle, SM Inactive, GMM Idle) and is in state CS-DCCH_DCH (state 6-5) as specified in clause 7.4 of TS 34.108.
Test procedure
The UE is registered in CS and PS domains in RRC state Cell_DCH. The SS transmits message UTRAN MOBILITY INFORMATION containing Rel-6 IE “Primary PLMN info”. The PLMN code is different from the RPLMN, which triggers LA/RA update. The UE responds with an INTIAL DIRECT TRANSFER message containing IE “PLMN Identity” with the same value as previously received in message UTRAN MOBILITY INFORMATION.
Expected Sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
The initial state of the UE is CELL_DCH state. |
|||
|
2 |
|
UTRAN MOBILITY INFORMATION |
Primary PLMN identity = PLMN2. LA/RA update is initiated by UE NAS. |
|
|
3 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
||
|
4 |
|
INITIAL DIRECT TRANSFER |
PLMN identity = PLMN2 |
|
Specific message contents
MASTER INFORMATION BLOCK
Use the same message sub-type found in clause 6.1.0a.3 of TS 34.108, with the following exception.
|
– MIB value tag |
Set to (Current MIB value tag + 1) |
|
– Multiple PLMN List |
|
|
– MIB PLMN Identity |
TRUE |
|
– Multiple PLMNs (1) |
|
|
– MNC |
11 |
UTRAN MOBILITY INFORMATION (Step 2)
|
Information Element |
Value/remark |
|
CN information info |
|
|
– PLMN identity |
Not Present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain specific DRX cycle length coefficient |
7 |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
– CN domain specific DRX cycle length coefficient |
7 |
|
– Primary PLMN identity |
PLMN-2 |
INITIAL DIRECT TRANSFER (Step 3)
|
Information Element |
Value/remark |
|
PLMN identity |
PLMN-2 |
8.3.3.4.5 Test requirements
In step 4, the UE shall respond with an INITIAL DIRECT TRANSFER message. The IE “PLMN identity” shall be set to PLMN2.