8.1.11 Signalling Connection Release (Invalid configuration)
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
8.1.11.1 Definition
8.1.11.2 Conformance requirement
Upon reception of a SIGNALLING CONNECTION RELEASE message, the UE shall:
1> indicate the release of the signalling connection and pass the value of the IE "CN domain identity" to upper layers;
1> remove the signalling connection with the identity indicated by the IE "CN domain identity" from the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
1> clear the entry for the SIGNALLING CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS;
1> the procedure ends.
If radio access bearers for the CN domain indicated by the IE "CN domain identity" exist in the variable ESTABLISHED_RABS, the UE shall:
1> transmit an RRC STATUS message on the uplink DCCH using AM RLC;
1> include the IE "Identification of received message"; and
1> set the IE "Received message type" to SIGNALLING CONNECTION RELEASE; and
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the SIGNALLING CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS and clear that entry;
1> include the IE "Protocol error information" with contents set to the value "Message not compatible with receiver state";
1> when the RRC STATUS message has been submitted to lower layers for transmission:
2> continue with any ongoing processes and procedures as if the invalid SIGNALLING CONNECTION RELEASE message has not been received.
Reference
3GPP TS 25.331 clause 8.1.13.3 and 8.1.13.5.
8.1.11.3 Test purpose
To confirm that the UE ignores the SIGNALLING CONNECTION RELEASE REQUEST message which request the UE to release signalling connection of domain that contains established radio access bearers.
To confirm that the UE transmit a RRC STATUS message to SS after detecting an invalid configuration in the received message.
8.1.11.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: CS-DCCH+DTCH_DCH (state 6-9) or PS_DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Test Procedure
SS transmit MEASUREMENT CONTROL message to UE. In this message, SS requests UE to perform traffic volume measurement. Key measurement parameters are as follows: measurement quantity = "RLC Buffer Payload", report criteria = "periodic reporting criteria", reporting interval = "6 seconds", reporting amount = ‘infinity’. UE shall begin traffic volume measurements, and shall send MEASUREMENT REPORT message after completing first measurement. UE shall send second MEASUREMENT REPORT message 6 seconds after first MEASUREMENT REPORT message. Then SS transmit SIGNALLING CONNECTION RELEASE message to UE. UE shall ignore the message and send a RRC STATUS message to SS. Then the UE shall send MEASUREMENT REPORT message to SS within the next 6 seconds.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
MEASUREMENT CONTROL |
Periodical traffic volume measurement reporting is requested. |
|
2 |
|
MEASUREMENT REPORT |
||
3 |
|
MEASUREMENT REPORT |
Time difference between earlier and this MEASUREMENT REPORT message should be 6 seconds. |
|
4 |
|
SIGNALLING CONNECTION RELEASE |
If the initial condition of the UE is state 6-9, set the IE "CN domain identity" to "CS domain". If the initial condition of the UE is state 6-10, set the IE "CN domain identity" to "PS domain". |
|
5 |
|
RRC STATUS |
||
6 |
|
MEASUREMENT REPORT |
This message should be sent within 6 seconds after the previous message. |
Specific Message Content
MEASUREMENT CONTROL (Step 1)
For MEASUREMENT CONTROL message in step 1, use the message sub-type as found in clause 9 of TS 34.108, with the exception of the following Information Elements:
Information Element |
Value/Remark |
Measurement Identity |
1 |
Measurement Command |
Setup |
Measurement reporting mode |
|
– Transfer Mode |
Acknowledged mode |
– Periodical or event trigger |
Periodic |
Additional measurement list |
Not Present |
CHOICE measurement type |
Traffic Volume Measurement |
– Traffic volume measurement object list |
|
– Uplink transport channel type |
DCH |
– UL Target Transport Channel ID |
5 |
– Traffic volume measurement quantity |
|
– Measurement quantity |
RLC Buffer Payload |
– Time Interval to take an average or a variance |
Not Present |
– Traffic volume reporting quantity |
|
– RLC Buffer Payload for each RB |
True |
– Average of RLC Buffer Payload for each RB |
False |
– Variance of RLC Buffer Payload for each RB |
False |
– Measurement validity |
Not Present |
– CHOICE Reporting criteria |
Periodical Reporting Criteria |
– Amount of reporting |
Infinity |
– Reporting interval |
6 Sec |
DPCH compressed mode status |
Not Present |
MEASUREMENT REPORT (Step 2, 3 and 6)
Check that the message received is the same as the message sub-type found in clause 9 of TS 34.108, with the following exceptions and the order in which the RBs are reported is not checked.
Information Element |
Value/Remarks |
Measurement identity |
1 |
Measured Results |
|
– CHOICE measurement |
Traffic volume measured results list |
– Traffic volume measurement results |
|
– RB identity |
1 |
– RLC buffer payload |
Check to see if this IE is present |
– RLC buffer payload average |
Check to see if this IE is absent |
– RLC buffer payload variance |
Check to see if this IE is absent |
– RB identity |
2 |
– RLC buffer payload |
Check to see if this IE is present |
– RLC buffer payload average |
Check to see if this IE is absent |
– RLC buffer payload variance |
Check to see if this IE is absent |
– RB identity |
3 |
– RLC buffer payload |
Check to see if this IE is present |
– RLC buffer payload average |
Check to see if this IE is absent |
– RLC buffer payload variance |
Check to see if this IE is absent |
– RB identity |
4 |
– RLC buffer payload |
Check to see if this IE is present |
– RLC buffer payload average |
Check to see if this IE is absent |
– RLC buffer payload variance |
Check to see if this IE is absent |
Measured results on RACH |
Check to see if this IE is absent |
Additional measured results |
Check to see if this IE is absent |
Event results |
Check to see if this IE is absent |
SIGNALLING CONNECTION RELEASE (Step 4)
Information Element |
Value/Remarks |
Message Type |
|
RRC transaction identifier |
0 |
Integrity check info |
|
– Message authentication code |
SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
SS provides the value of this IE, from its internal counter. |
CN domain identity |
If the initial condition of the UE is state 6-9, set to "CS domain". If the initial condition of the UE is state 6-10, set to "PS domain". |
RRC STATUS (Step 5)
Information Element |
Value/remark |
Message Type |
|
Integrity check info |
|
– Message authentication code |
This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value. |
Identification of received message |
Not Checked |
– Received message type |
SIGNALLING CONNECTION RELEASE |
– RRC transaction identifier |
0 |
Protocol error information |
|
– Protocol error cause |
Message not compatible with receiver state |
8.1.11.5 Test requirement
After step 1 the UE shall transmit MEASUREMENT REPORT message twice at an interval of 6 seconds.
After step 4 the UE shall transmit a RRC STATUS message with protocol error cause set to "Message not compatible with receiver state".
After step 5 the UE shall transmit a MEASUREMENT REPORT within 6 seconds.