srmanot7 ShareTectnote Protocol Conformance Home : www. This will be on-going pages that never ends. I will update this page as I need to handle the specific test cases. You should refer to 3GPP 36.523-1 for the details. I will just put some summary and tips for each of the test cases defined in the LTE protocol conformance test specification, To be honest, I don’t think there are many people saying "3GPP document is easy to understand”. One of the factors that makes the document vague/unclear is that it does not give you any practical examples as somebody mentioned in his blog. I totally agree with his opinion. But I think there is one place where you can get huge amount of examples related to each part of 3GPP documents. It is 'Conformance Test’ specification (36-521 : RF Conformance, 36.521 : RRM, 36.523 : Protocol Conformance). So I think (hope) this page would help you not only for day-to-day conformance testing job, but also help you get practical understandings of other 3GPP documents. At least to me, LTE Protocol Conformance decument is described in much clearer manner comparing to UMTS conformance document (34.123). ‘One of the questions that I got very frequently is "What am I supposed to study first 2", "Where do I have to start 2" Unfortunately there would be no clear answer to these questions... but there can be @ general guideline for this. My personal guide are i) Don't try to look go through each test cases all over the test. Of course it is not a bad thing to know about each and every test cases, but you would give up very soon if you are trying to dig into the very details of each test cases. il) Go over the test case sections as often as possible and try to think of "what kind of test cases are there in this section 2", “what would be the generic procedure for this section ?". You don't have to read the test case description yet, just imagine that you are the person who is writing the test cases in 3GPP and design the test cases on your own, By this thought process, you will have to chance to apply what you know about each layers of LTE protocol stack. And you will also appreciate for those who put their effort to design all of these test cases in 3GPP -:). You will notice that designing a test cases is not an easy and trivial thing. ili) Now you can get a litte bit detail into each test case, but you don’t have to go through all the test cases (it is alreay several hundred test cases are defined in 36.523). If you pick only one section that you are currently most familiar with and read all the test cases for the section, you would notice that most of the test procedure in that section is very similar to each other. Only a couple of parameter changes or a couple of additional steps. As far as 1 ‘am experienced, almost always T could find one or two test cases that can represents overall test procedures for all the test cases in a specific section. Just pick those one or two test cases from each section and try to completely understand it. The test cases with star mark in this page is those that I picked as a representative test cases for 2 ‘couple of sections. Of course this is based on my personal criteria and you would have different opinion. But no problem. You can pick whatever you think best represent the section. + Test Case Classification * Activate Test Mode © Test Loop Back «Test Case Description Test Case Classification Following is the list of sections from 36,523 V9.3.0 (2011-04). This is for the step ii) of the guideline described above. Titles [Idle mode operations [6-1 Ina pure E-UTRAN environment [6.2 _|Multi-mode environment (E-UTRAN, UTRAN, GERAN,CDMA2000) (6.3 [Closed Subscriber Group cells, [6.4 [Hybrid cells Layer 2 a_|MAC [7.2 _|RLC 7.3_[PDCP. RRC [a1 [RRC connection management procedures [8.2 _|RRC connection reconfiguration [g.3_ [Measurement configuration control and reporting hipshww sharelechnota.comihimlLTE Protocol CTMimlfTest Case Description 12‘ren017 Isa ShareTectnote linter-RAT handover iss IRRC others, IEPS mobility management pa [EMM common procedures [9.2 IEMM specific procedures 9.3 [EMM connection management procedures (Si mode only) i9.4 INAS Security 10 IEPS session management 10.2 [Dedicated EPS bearer context activation 10.3 IEPS bearer context modification 10.4 IEPS bearer context deactivation 10.5 \UE requested PON connectivity 10.6 \UE requested PON disconnect 10.7 |UE requested bearer resource allocation 10.8 |UE requested bearer resource modification 10.9 [UE routing of uplink packets ry (General tests aot ISMS over SGs 12 IE-UTRA radio bearer tests at [General 12.2 [MIMO not configured 12.3 [MIMO configured 13 (Multi layer Procedures a3.1 [call setup 13.2 IRRC connection reconfiguration 13.3 13.4 Mobility 14 lETws 4.1 [ETWS reception in RRC_IDLE state / Duplicate detection 14.2 IETWS reception in RRC_CONNECTED state / Duplicate detection 14.3 IETWS reception in RRC_IDLE state / NITZ timestamp security check 15 [Mobility management based on DSMIPv6 (Dual-Stack Mobile IPv6) 5.1 Discovery of the home agent via DNS 15.2 Discovery of the Home Agent via DHCP 15.3 [void 15.4 ‘Security association establishment with Home Agent reallocation procedure 15.5 ‘Security association establishment without home agent reallocation procedure 15.6 [Registration of a new IPV6 CoA (Binding Update/Acknowledgment procedure in 1Pv6 network) 15.7 [Registration of a new IPv4 CoA (Binding Update/Acknowledgment procedure in 1Pv4 network) 15.8 RRe-registration of 1Pv6 CoA 15.9 IRe-registration of 1Pv4 CoA 15.10 IReturn to home link 5.11 ‘Dual-Stack Mobile IPv6 detach in IPv6 network 15.12 ‘Dual-Stack Mobile IPv6 detach in IPv4 network 16 |Home (€)NB related hipshwwrsharalechnola.comMhimlLTE_Prolocol CTHmifTest_Case Description |‘ron017 ShareTectnote [16.1 [UE Idle Mode Operations 17 IMBMS in LTE 17.1 [MECH Information Acquisition 157.2 [MEMS Data Reception 127.3. [MBMS Counting Procedure 17.4 [MBMS Service Continuity o pws 118.1 [EMAS on LTE Activate Test Mode Taformation Element eferoace | Presence [Format Tena Preto! doermnator 28.007} sub co v % aise 11.2301 [Sapinceior [IS28 007 By sub 7 v ¥ 12312 Nessoe tne i ¥. T [De wstoop mode u v t pa ea ram Tae ee ST ct a x 2] i | —_biino, = Test Loop Back For conformance test, we have two major procedure to go through. One is "ACTIVATE TEST MODE" and the other one is "CLOSE UE TEST LOOP". In RF Conformance, only “ACTIVATE TEST MODE" would be enough, but in Protocol Conformance we have to go through both "ACTIVATE TEST MODE" and "CLOSE UE TEST LOOP". (For the details refer to TS 36.509 ‘5 Test Control (TC) protocol procedures and test loop operation’) [Simply put, this is the loopback made at the top of PDCP layer and this is Mandatory for all LTE Mode A _|UE, UE Is supposed to loopback whatever POCP SDU It gets from the network. It doesn't care labout the contents or TFT etc. [This is also a loopback sitting on top of PDCP layer, but unlike Mode A, in Mode B the loopback ‘applies to a specific TFT associated with a specific EPS. This loopback can not be be used when Imore than one PDN connection is established or more than one primary PDP context is active. [This is Mandatory for all LTE UE. [Loopback Mode Cis for E-MBMS testing. It provides counting of successfully received MBMS Mode C [Packets on a given MTCH while UE is operating in E-MBMS/E-UTRA mode. This is mandatory only for the LTE UE supporting E-MBMS. Mode 8 Overal function diagram for each test mode from TS 36.509 is as follows. hipihww sharalechnola.comMhimlLTE_Prolocol CTHmifTest_Case Description a2Test System Test System Loopmode Message structure of CLOSE UE LOOPBACK i protocol procedures and test loop operation’ Loopmode 8 as follows. (For the details refer to TS 36,509 'S Test Control (TC) Loopmode c Information Element Reference Presence [Format Length [Pctocel dexrmiavor 24.007 28 ww v % leause 1123'14 [SepinaesTor [FS24.007 By. sub w v % 112312 (iessage We i v i IVE test loop mode NC v 1 |UEtestloop mode ALB setup ‘SvaodeA, iw 7 IDE teetloop mode BL setup ‘Sv aodeB ¥ i [UE testioop mode C setup [evivtedec 7 i ea a a a ape pee pe iro. a ete X2=0 and X1=0 then UE test loop mode A i elected. X2=0 and X1=1 then UE test loop mode B is elected X21 and X1=0 then UE test loop mode Cis selected c a of UE Tes ip mode ALB setup Ht mbes ‘oar ‘Odlel2 LB setup tat Oost N34 aT TB Seup ORB IEF oaaz Seet’s Cetet TS op ORB TER ‘Ose nets Ocel? Te soup ORBTEAT OaaTTET ‘Oaetn"s oaetN'se1 hipihww sharalechnola.comMhimlLTE_Prolocol CTHmifTest_Case Description‘an017 ShareTectnote [setup DAB TEM Oeet2 Geet’ eet TS Sap ORB TERE eet celts Geet? TR sanp ORBEA OaaTTET ‘Oaetn's oetetN3e1 bate 3 £218.20 Uplink PDCP SDU size in bits. 12160 (binary coded, 15 is most signfcat bit and 20 lest significaat bt) See Note Q4.Q0~Dsta Radio Bearer identity somber, 1.32 (binary coded value of "DRB-tdeaty” 1.4 is mos signifiau bit sed QO leat igcan bt). here Data Radio Beaver idenity identifies the radio bearer eee TS 35.331 [25), Let me give you an example for the message to help you understand the message structure. HEX String : OF 80 00 03 01 00 01 Analysis Result : ©: Protocol discriminator F: Skip indicator 80 : Message type (10000000) 00 : UE test loop mode (000000AB), where A=B=0 when Loopback mode is mode A 03 : Length of UE test loop mode ALB setup list in bytes 01 00 : Uplink POCP SDU Size = 256 bits 01 : Data Radio Bearer ID Test Case Description Following is the list of test cases that I have gone through for peronal needs. Those with the star mark is the ones that I petsonally think best represents the test cases for some’ sections. OF course, this list would extend as I get more and more involved in LTE test process. 1 will start out this page with skeletones from 36,523-1 and keep adding comments as I gain more practical experiences for each of these items. (Number of stars put besides the test case shows the importance in terms of understanding a normal UE behavior and is the items that I want to recommend you to look into first and have through understanding, If you have clear understanding of those ‘start’ test case, it would be easier for you to understanding other test cases as well. Of course, this is totally my personal/subjective marking and I didn't take any survey of "thumb-up" or "thumb-down" -:) ) 6.1.2.2 Cell selection / Qrxlevmin( ¥#) 6.1.2.4 Cell reselection( +) 1 Inter-RAT cell r ion / From E-UTRA RRC IDLE to GSM Idle/GPRS Packs 7.1.1.2 DTCH or DCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel ID( +) 7.1.2.3 Correct selection of RACH parameters / Preamble selected by MAC itself / Contention based random access procedure 7.1.2.4 Random access procedure / Successfull # #) 7.12.7 MAC contention resolution / Temporary C-RNTI ( ##) 7.1.2.8 MAC contention resolution / C-RNTL 7.1.3.5 Correct HARO process handling / CCCH 2.2.2.5.1 UM RLC / Sebit SN / Correct use of sequence numbering( + #) SALLRRCZsaina‘oecoretten nate made (<=) SLELRRE connection establishment /keei-2o/ Su 25/ Success ( jit ww ) hipihww sharalechnola.comMhimlLTE_Prolocol CTHmifTest_Case Description 521srmanot7 ShareTectnote = 8.1.2.3 RRC connection establishment / Return to idle state after T300 timeout * 8.1.3.4 RRC connection release / Redirection to another E-UTRAN frequency ‘= 8.2.1.1 RRC connection reconfiguration / Radio bearer establishment for transition from RRC IDLE to RRC CONNECTED / Success / Default bearer / Earh 9.1.2.1 Authentication accepted 6.1.2.2 Cell selection / Qrxlevmin bearer establishment 2.1,3 RRC connection reconfiguration / Radio bearer establishment Ded rer 8.2.3.1 RRC connection reconfiguration / Radio bearer release / Success 8.2.4.2 RRC connection reconfiguration / Handover / Success / Common preamble #st i) 8.3.3.1 Measurement configuration control and reporting / SON / ANR / CGI reporting of E-UTRAN cell 8.5.1.1 Radio link failure / RRC connection re-establishment success( sew #) 9.1.2.3 Authentication not accepted by the network / GUTI used / Authentication reject and re-authentication Test purpose of this test is simple. This test is to check if UE shows following rules properly or not ‘= UE should not camp If the cell around it does not satisfy Cell Selection Criteria ‘= UE should not camp if the cell around it satisfy Cell Selection Criteria You need to understand details of Cell Search (Detection) procedure, Cell Selection Procedure and Cell Selection Criteria to troubleshoot this test case or create similar test cases, This Is much wider topic than you might think. ‘Test Conditions that you need to pay attention for this test each parameter and how those parameters influence Cell Selection process (See Cell Select case is as follows. You need to understand the meaning of n Criteria) Table 6.1.2.2.3.2-1: Time Instances of cell power level and parameter changes Parameter__[ Unit | Cell Remark EPRE 15KH_ able to read Zz TH | cel-specinc RS | aBm/ | -85 _ | Te power evel value iS Such o salisly Smevoel 1 <0 buline UES the PLMN identity ‘Gmievminonset_|~oB ‘Ondemmin | dBm | 84 o 0 compensation | dB EPRE 19KH Zz T2 | Cel-speciic RS | dBm/ | -75 | The power level is such thai SrxevCel 1>0 Note: “The Gownlink signal level uncertainty specified in T5 96.508 secon 43.471 Table 6.1.2.2.3.3-1: SysteminformationBlockTypet for call 1 (all steps) Derivation Path 36.508 cause 44.32 Information Element Value/Remark ‘Comment | Condition steminformationBlockTypel_-= SEQUENCE [ celselecloninfo SEQUENCE { ‘q-RxLevvin 22 BE BM) H Overall protocol sequence is as follows Step] Direction Message Memo ‘Set the cell power and SIB parameters as "T1" in table + ss 16.1.2.2.3.2-1. 2 UE [Turn on UE if UE sends this message, it 3 RRC: RRCConnectionRequest Imeans “FAIL since T1 does not Imeet Cell Selection Criteria 4 35 [Set the cell power and SIB parameters as "T2" in table hipihwww sharelechnota.comihimlLTE Protocol CTNmifTest Case Description‘srmaot7 ShareTectnote pa (6.1.2.2.3.2-1. iF UE sends this message, it > SS |RRC: RRCConnectionRequest Imeans "PASS" since T2 meet Cell Selection Criteria < Complete Registration Sequence > 6.1.2.4 Cell reselection ‘Simply put, this test case is to check if UE changes it's serving cell from a cell to another cell when it sees a cell with Better'signal which meets cell reselection criteria. In terms of test orocedure and protcol sequence, may 10k simple for this case but in terms of UE operation tis may be one of tie most complaated procedure. ATatot network paramete, (Various G18 parameters} and UE sie Factors (Cel Evaluation algorithm) are involved in tis test proce lure, So you need to have very goo on Idle Mode Procedure to expand and troubleshoot this test. Understanding Try to understand the details on parameters/factors in Idle Mode procedure and you can create a lot of adeitional test cases just by changing those parameters and power of Cell and Cell2 Test Condition is as follows. Table 6.1.24.32-4: Time instances of cell power level and parameter changes Parameter [ Unit | eld_[~cel2 Remark TH | Cat am |S “73, | The power level values are assignedto speedos | tsk satisfy Roars « Roaez Table 6.1.2.4322: Main behaviour a Procedure Message Sequence TP] verdict us ‘Messone T | The SS changes Cal Dievelaccorana toe | - | = row "Ti" intable 6.124.321 2 Check: Does ihe tat resut of nee test = Tp procoduro n TS 26-508 eubclause 6.4.27 indicate that the LE 1s camped on E-UTRAN Caz ‘As you see, the required protocol sequence is defined in 36.508, not in 36.523, Step] Direction Message Memo IMake it sure that Cell 1 and Cell 2 has * different Physical Cell 1D * different Tracking Area Code » Same PLMN i [Registration to Cell 1 2 < Idle in Cell 1 > 3 (Change cell power so that Cell 2 has bettern signal than Cell 1 4 IRRC: RRCConnectionRequest 5 IRRC: RRCConnectionSetup ls IRRC: RRCConnectionSetupComplete INAS: TRACKING AREA UPDATE REQUEST F IRRC: DLinformationTransfer INAS: TRACKING AREA UPDATE ACCEPT le IRRC: RRCConnectionReconfiguration + NAS: ATTACH ACCEPT INAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST IRRC: ULInformationTransfer P UE > SS _|NaS: TRACKING AREA UPDATE COMPLETE PASS/FATL 10_| UE <-- 55 _|RRC: RRCConnectionRelease Note 1 : TAI for Cell 1 and Cell 2 are different. hipshwww sharelectnota.comMhimlLTE Protocol CTMmifTest Case Description 721srmanot7 ShareTectnote Note 2 : The periodic tracking area updating timer T3412 is deactivated by default during the attach procedure (TS 36.508 clause 4,7.2). Note 3 : The SS does not initiate authentication and NAS SECURITY MODE COMMAND are not performed (reuse of keys allocated during the attach procedure). 6.2.3.1 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS Packet_Idle Simply put this test cage isto check I UE changes i's serving cell from a cel to another non-LTE cell(GSM/GPRS Cell) “shen Ie sees a cell with better signal which meets call reselection criteria ‘The factors to be specifically noticed Is about the priority based reselection. So you need to get familiar to Cell Reselgcton citer based oY Prionty in addition t general fale mode procedure Major Sub Test under this test can be summarized as follows. ‘© Sub Test 1: From LTE Cell (E-UTRA) to Higher Priority GERAN + Sub Test 2 : From LTE Cell (E-UTRA) to Lower Priority GERAN Test Condition is as follows. Table 6.2.3.1.3.2- ‘ime instances of cell power level and parameter changes for E-UTRA cells Parameter Unit Cat Remark 71 | CaESpeshic RS EPRE | dBmv/icKHz | -70 __| Sreveans 20 ‘Srxlev" cB 36 | Srievours > Srdevens =O Cellspecific RSEPRE | dBnvisriiz | -60 | Srdeveais >20 2 er a es T3_| Cell-specfic RS EPRE | dBm/iskHz | -100__| Srdevous 20 [fhreshServingL ow} Note: Spey is calculated in the UE Table 6.2.3.1.3.2-2: Time Instances of cell power level and parameter changes for GERAN cells Parameter Unit__| Cell 24 [cell 25 Remark Ti [RF Signal Level ‘oBm -£0 OFF __| Sheveaize > afihrestx-High] cr oe 2 NA 72 | RF Signal Level ‘ebm OFF OFF cr OB NAL 21 T3_| RF Signal Level om OFF “80 | Srlevear > arash Low] Note Cis caloulaled in the UE Table 6.2.3.1.3.3-1; SysteminformationBlockType3 cell 1 (preamble and all steps, Table 6.2.3.1.3.2-3) Derivation Path: 36.508 table 4435-2 Information Element Valueiremark Comment ‘Condition ‘SySteminformationslock Types = SEQUENCE { cellReselectionServingFreqinfo SEQUENCE { s-NoniniraSearch Not present thresnServingLow 10 ‘Actual value =20 a8 celReselectionPrionity a ‘Amiddle valve in {he range nas een selected Step] Direction Message Memo a [Registration to Gell 1 (EUTRA) 2 ‘< Idle in Cell 1 (EUTRA)> 3 (Change Cell Power as T1 (EUTRA Cell Power is lower than GERAN) |Condition for Reselect, Irrom Low Priority to High hipihwww sharelechnota.com/himlLTE Protocol CTNmifTest Case Description a‘srmaot7 ShareTectnote Priority ls UE Camp on to GERAN(Cell 24) and perform RAU [rest Passes if UE camp on 5 [Tale Th Cell 24{GERAN) for atleast 5 seconds > 6 [Change Cell Power as T2 (All GERAN Is OFF, only EUTRA Is ON) 7 [Camps to Celt 1 (EUTRA) ie < Tale in Cell 1(EUTRA) for at least 5 seconds > [Condition for Reselect 9 SS _ [change Cell Power as T3 (EUTRA Cell Power is lower than GERAN) |from High Priority to Low Priority Test Passes 1f UE camp on 10 | UE-—-> $5 _|UE Camp on to GERAN(Cell 25) lo GERAN cell P 7.1.1.2 DTCH or DCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel 1D Simply put, this test case is to check if UE decode LCID field of Downlink MAC PDU and act properly according to the LCID. More specifically this TC test UE response to Reserved LCID and LCID for "Identity of the logical channel” in the following table, Table 6.2.1-1 Values of LCID for DL-SCH LCID values, ‘00000, coCH | DOOT-DIOTO | Ideniiy ofthe logecal channel —] O11T-11017 Reserved ‘11100 __| UE Contention Resoution identi THOT Timing Advance Command 11110 DRX Command Comat Padding TP1 : This tests If UE act In the following manner oF not, i) < UE is in RRC connected state with DRB with LCID = 3 > ii) SS send MAC PDU with reserved LCID (T-CRNTI is properly set for the UE) ili) UE decode the MAC PDU but should discard it since LCID is reserved 7P2 : This tests if UE act in the following manner oF not. i) < UE is in RRC connected state with DRB with LCID = 3 > ii) SS send MAC PDU with LCID = '00011'B (T-CRNTI is properly set for the UE) ill) UE decode the MAC PDU and transfer it to higher layer properly. Step] Direction Message Memo < RRC Connection Setup > = Authentication > < Security Mode > = ESM : Information > RC: DLinformationTransfer + TC: ACTIVATE TEST MODE RRC: ULinformationTransfer + TC: ACTIVATE TEST MODE COMPLETE < RRC : Security > = RRC: UECapabilityenquiry > RRC: RRCConnectionReconfiguration + NAS: ATTACH ACCEPT NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST RC: RRCConnectionReconfigurationComplete RRC: ULinformationTransfer + NAS: ATTACH COMPLETE NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT RRC: DLinformationTransfer + TC: CLOSE UE TEST LOOP, RRC: ULinformationTransfer + TC: CLOSE UE TEST LOOP, IbRB, LcID = 00011 13 hipihwww sharelechnota.comihimlLTE Protocol CTNmifTest Case Description 92‘srmaot7 ShareTectnote COMPLETE a IMAC PDU with reserved LCID 15 [UE should not send any SR within 5 seconds PASS/FAIL 6 MAC POU with valid LCTD(00011) a7 [UE should transmit SR PASS/FATL 18 [UL Grant, 19 [UE should send MAC PDU with LCID 00013 PASS/FAIL 7.1.2.3 Correct selection of RACH parameters / Preamble selected by MAC itself / Contention based random access procedure This test case is similar to 7.1.2.3, but 7.1.2.3 is focused more on overall RACH procedure whereas this test case is focused more on detailed parameters involved in the RACH procedure. TP1 : This tests if UE act In the following manner oF not: i) < Now in Idle Mode > ii) SS send Paging message (MAC PDU carrying the CCH is less than messageSizeGroupA) Note : messageSizeGroupé is specified in SIB2 as follows. (This is just an example and it may not match the value in the conformance test case) rach-Configconmon ::= SEQUENCE s-preanbleInfo ::= SEQUENCE [1] | +-numberofRa-Preanbles ::= ENUMERATED [n52] i i i i +-preamblesGroupaconfig ::= SEQUENCE OPTIONAL :Exist 4-sizeOfRA-PreamblesGroupa ::= ENUMERATED [nd] rmessageSizeGroupa ::= ENUMERATED [b56] +-messagePoweroffsetGroups ::= ENUMERATED [minusinfini ty] TP2 : This tests if UE act in the following manner oF not, i) < Now in Idle State > il) SS send Paging ili) UE send PRACH in response to Paging iv) SS send RAR (RACH Response). v) UE send RRC Connection Request vi) SS does not send ‘Contention Resolution’ within a certain time span (contentionResolutionTimer) vil) UE Retransmit PRACH || s+rach-config || | #=preambleinfo ::= SEQUENCE [0] || 1 | +-numberofra-Preanbles ::= ENUMERATED [n52] || | | 4=preanblescroupaconfig ::= SEQUENCE OPTIONAL :onit || | #powerRampingParameters ::= SEQUENCE || 1 | +-powerRampingstep ::= ENUMERATED [482] || | | 4-preanblernitialReceivedtargetPower ::= ENUMERATED [dan-104] boll bor bor boll boll SEQUENCE t-ra-Supervisioninfo ::= SEQUENCE | +-preambletransmax ::= ENUMERATED [n6] | +-ra-Responsewindowsize ::= ENUMERATED [sf10] | 4-mac-contentionResolutionTimer := ENUMERATED [sf48] omaxHARQ-Msg3Tx i= INTEGER (1..8) [4] ‘P3 : This tests if UE act in the following manner oF not. (The description for this TP in 36.523 is a little bit confusing to me for now. I will just put down as described in the specification and clarify further later). i) < Now in Idle State > ii) $S send Paging ill) UE send PRACH in response to Paging iv) SS send RAR (RACH Response). v) UE send RRC Connection Request vi) SS does not send ‘Contention Resolution’ within a certain time span (contentionResolutionTimer) after more than preambleTransMax transmission from UE vil) UE retransmit PRACH using the a preamble in the same group of random access preambles as used for the first transmission of Msg3 hipshwww sharelechnota.com/himlLTE Protocol CTNmifTest Case Description swesrmanot7 ShareTectnote “TP4 : This tests if UE act in the following manner oF not, i) < Now in Idle State > il) Now UE has some data to transmit and the size of data (MAC PDU size) is greater than messageSizeGroupA. iil) UE transmit PRACH using using a preamble in group 8 of random access preambles indicated in SIB2 7.1.2.4 Random access procedure / Successful Whether you are doing the testing Job or you Just want to study about LTE, I want to recommend you to take this test case as 2! backbone (Framework) tast cast for all RACH process, ‘his test case tests the most basic Behavior (requirement) of RACH process and test the following three behavior (I waill call tis expected behavior as *TP'(Test Purpose) as in SGPP 36°525). TP! : This tests if UE act in the following manner or not. (The most basic RACH Test) i) < Now in Idle State > il) SS send Paging ill) UE send PRACH in response to Paging TP2 : This tests if UE act In the following manner oF not, i) < Now in Idle State > il) SS send Paging ili) UE send PRACH in response to Paging iv) SS does not send RAR(RACH Response) within a certain time period (ra-ResponseWindowSize) v) UE resend PRACH Note : ra-ResponseWindowSize is informed to UE by SIB2 as follows. (This is just example. The value specified in this example may differ from the value specified in this conformance test case,) rach-config : +-preanbletnfo | +-nunberofra-Preambles SEQUENCE SEQUENCE [0] ENUMERATED [152] Ile boort boll | | | | 4-preanblescroupaconfig ::= SEQUENCE OPTIONAL :Onit || | +-powerkampingParaneters ::= SEQUENCE | | | | +=powerrampingstep ::= ENUMERATED [482] || | | 4-preanblernitialReceivedrargetPower := ENUMERATED || | s-ra-supervisioninfo ::= Sequence | | | | +-preanbletransiax ::= ENUMERATED [n6] || | | 4-ra-Responsewindowsize ::= ENUMERATED [sf10] || 1 | +smac-contentionResolutiontimer ::= ENUMERATED [sf48] bor omaxHARQ-MSg3TX ::= INTEGER (1.8) [4] P3 : This tests if UE act in the following manner oF not, i) < Now in Idle State > il) SS send Paging ill) UE send PRACH in response to Paging iv) SS send RAR (RACH Response), v) UE send RRC Connection Request vi) SS does not send ‘Contention Resolution’. (SS does not send any response) vil) UE Retransmit PRACH 1.2.7 MAC contention resolution / Temporary C-RNTI This is the test case to check about ‘Contention Resolution’ step in RACH process. It has several subtests as described below, This test would give you pretty clear understanding of mechanism of "Contention Resolution’ step, PL : This tests if UE act in the following manner oF not, i) < Now in Idle State > ii) SS send Paging iil) UE send PRACH in response to Paging iv) SS send RAR (RACH Response). vv) UE send RRC Connection Request vi) SS does not sends any MAC PDU including ‘Contention Resolution’ MAC PDU within a certain time frame (Contention Resolution Timer). vil) UE send 'RRC Connection Request’ again. hipshwww sharelechnota.com/himlLTE Protocol CTNmifTest Case Description wessrmanot7 ShareTectnote Note : ra-ResponseWindowSize is informed to UE by SIB2 as follows. (This is just example. The value specified in this example may differ from the value specified in this conformance test case.) rach-config +-preambleinfo | +-numberofRa-Preanbles : | +-preanblesGroupaconfig ::= SEQUENCE OPTIONAL :Omit +-powerRampingParaneters ::= SEQUENCE + SEQUENCE i i i i | | +-powerRampingstep ::= ENUMERATED [d82] I i i i i i SEQUENCE [0] ENUMERATED [152] | 4-preanbletnitialReceivedtargetPower ::= ENUMERATED [dBn-104] t-ra-supervisiontnfo ::= SEQUENCE | +-preanbletransMax ::= ENUMERATED [n6] | 4+-ra-Responsewindowsize ::= ENUMERATED [sf10] | 4-mac-ContentiongesolutionTimer ::= ENUMERATED [sf48] INTEGER (1..8) [4] fomaxHARQ-MSg3Tx. = 72 : This tests if UE act in the following manner oF not, i) < Now in Idle State > ii) SS send Paging iil) UE send PRACH in response to Paging iv) SS send RAR (RACH Response). vv) UE send RRC Connection Request vi) SS sends RRC Connection Setup message, but this does not include ‘Contention Resolution’ MAC PDU. vil) UE send 'RRC Connection Request’ again. 7P3 : This tests if UE act in the following manner oF not. i) < Now in Idle State > il) SS send Paging ill) UE send PRACH in response to Paging iv) SS send RAR (RACH Response). v) UE send RRC Connection Request vi) SS sends RRC Connection Setup message and it includes "Contention Resolution’ MAC PDU, but the contention resolution identity does not match the UE id vil) UE send 'RRC Connection Request’ again. 7P4 : This tests if UE act in the following manner or not. (This shows what should happen if there is no problem with "Contention Resolution’ step) i) < Now in Idle State > il) SS send Paging ili) UE send PRACH in response to Paging iv) SS send RAR (RACH Response). vv) UE send RRC Connection Request vi) SS sends RRC Connection Setup message and It includes ‘Contention Resolution’ MAC PDU, and the contention resolution Indentity Is also correct one. vii) UE send 'RRC Connection Setup Complete’ 7.1.2.8 MAC contention resolution / C-RNTI This Is test for the contention resolution step during RACH process happending in Handover process. (you should notice that RACH process is a critical part in handover process in LTE. UMTS handover process does not go through RACH process during the handover) TP1 : This tests if UE act In the following manner oF not, i) < Configure Two Cells in SS > il) < Now in Idle State : Cell 1 > ii) SS send Paging ill) < Establish RRC Connection and Complete 'RRC Connection Reconfiguration’ for activating data bearer > iv) < SS increase the power of the second cell so that UE can perform the handover to the second cell > v) SS send "RRC Connection Reconfiguration (for Handover)" and this message does not include any explicit Ranéom Access Preamble configuration. vi) UE send 'RRC Connection Reconfiguration Complete’ to SS Cell2. vil) $$ does not schedule any PDCCH transmission with UE C-RNTI. vill) UE resend ‘RRC Connection Reconfiguration Complete" 72 : This tests if UE act in the following manner oF not, i) < Configure Two Cells in SS > hipihwww sharelectnota.com/nimlLTE.Prolocol CTNmlfTest Case Description 22srmanot7 ShareTectnote ii) < Now in Idle State : Cell 1 > ii) SS send Paging ill) < Establish RRC Connection and Complete ‘RRC Connection Reconfiguration’ for activating data bearer > iv) < SS increase the power of the second cell so that UE can perform the handover to the second cell > v) SS send "RRC Connection Reconfiguration (for Handover)” and this message does not include any explicit Rancom Access Preamble configuration, vi) UE send 'RRC Connection Reconfiguration Complete! to SS Cell2. vil) SS does sends PDCCH transmission with UE C-RNTI. vill) UE should not resend 'RRC Connection Reconfiguration Complete’ 7.1.3.5 Correct HARQ process handling / CCCH Note : This TC looks a little confusing to me.. I may need further investigation for clarification. Note : It would be not easy to implement this on the test system since it has to check HARQ ACK/NACK on real time. This Is to check whether UE send HARQ ACK or NACK properly in response to the message from the network (RAR, cR) This test case test the following check points (TP : Test Purpose). TP 1: This is to check the following two behavior. i) UE'send 'PRACH' il) SS send RAR with RA-RNTL iit) UE should not send any ACK or NACK for RAR. ‘TP 2 : This is to check the following two behavior. i) UE send 'PRACH' it) SS send RAR with RA-RNTI i) Ge send Mag3 (RRC Connection Request) iv) SS send RRC Connection Setup and Contention Resolution with wrong UE ID, addressed to T-CRNTI v) UE should not send any ACK or NACK’ TP 3 : This is to check the following two behavior. i) UE'send 'PRACH' it) SS send RAR with RACRNTI i) UE send "Meg (RRC Connection Request) iv) SS send RRC Connection Setup 2nd Contention Resolution with right UE ID, addressed to T-CRNTI with wrong CRC v) UE should not send NACK TP 4.: This is to check the following two behavior. i) UE send 'PRACH' il) SS send RAR with RA-RNTI il UE send "Hea3 (RRC Connection Request) iv) SS send RRC Connection Setup and Contention Resolution with right UE ID, addressed to T-CRNTI with right CRC vv) UE should not send ACK Step] Direction Message Memo it = Power On and Registration > lassign @ S-1™MSI 2 =< Now UE is in IOLE mode > 3 Paging with incorrect UE ID L Malt for 5 secs (UE should not respond to Pesing during WHS onssrrany 5 Paging with incorrect UE TD 6 PRACH 7 RAR including T-CRNTI with wrong CRC is [UE should not send any HARQ ACK/NACK PASS/EATL 3 PRACH 10 RAR including T-CRNTL it RRC Connection Request 12 [GR with wrong UE ID > RRC Connection Setup 13 \UE should not send any HARQ ACK/NACK PASS/FATL 14 PRACH 15 RAR including T-CRNTT hipshwww sharelectnota.cominimlLTE Protocol CTMmifTest Case Description raz‘srmaot7 ShareTectnote 16 RRC Connection Request 17 [(CR with proper UE ID + RRC Connection Setup) with wrong CRC| 18 \UE should not send any HARQ NACK PASS/FAIL 19 PRACH 20 RAR including T-CRNTI 21 RRC Connection Request 22 (CR with proper UE ID + RRC Connection Setup) with right CRC 23 [UE should send any HARQ ACK PASS/FAIL 7.2.2.5.1 UM RLC / 5-bit SN / Correct use of sequence numbering This test case test basic operation of UM RLC, so it can be a framework for UM RLC. TP 1: This Is to check the following two behavior, i) UE Is In RRC_CONNECTED mode il) UE transmit the first PDU and the SN for the PDU is 0 TP 2: This is to check the following two behavior. i) UE'Is in RRC_CONNECTED mode il) UE transmit the first PDU and the SN for the PDU is 0 ill) UE transmit the next PDU and the SN for the PDU is incremented by 1 TP 3: This is to check the following two behavior. i) UB's in RRC_CONNECTED mode ii) UE transmit the first PDU and the SN for the PDU is 0 ill) UE transmit the next PDU and the SN for the PDU is incremented by 1 iv) UE transmit more than 32 PDUs and the SN should be wrapped around after transmitting 32 PDUs Step] Direction Message Memo q = RRC Connection Setup > 2 = Authentication > 3 < Security Mode > 4 r= ESM : Information > 5 RRC: DLinformationTransfer + TC: ACTIVATE TEST MODE le RRC: ULinformationTransfer + TC: ACTIVATE TEST MODE COMPLETE 7 < RRC : Security > ® r= RRC: UECapabilityenquiry > lo RRC: RRCConnectionReconfiguration + NAS: ATTACH ACCEPT NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST 10 RRC: RRCConnectionReconfigurationComplete 7 RC: ULinformationTransfer + NAS: ATTACH COMPLETE NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT 12 RRC: DLinformationTransfer + TC: CLOSE UE TEST LOOP, Bb RRC: ULinformationTransfer + TC: CLOSE UE TEST LOOP COMPLETE a RLC UMD PDU with SN 15 IVE should transmit RLC UMD PDU with SN = 0 PASS/FAIL 16 RLC UMD PDU with SN incremented by 1 7 UE should transmit RLC UMD PDU with SN incremented by 1 PASS/FATL 18 Repeat step 16-17 until SN = 31 19 RLC UMD PDU with SN = 0 0. [UE should transmit RLC UMD PDU with SN PASS/FAIL hipshwww sharelechnota.com/himlLTE Protocol CTNmifTest Case Description wetsrmanot7 ShareTectnote 8.1.1.1 RRC / Paging for connection in i lle mode Test Purpose : This is to check the following two behavior. i) UE should not respond to Paging carrying the incorrect UE 1D ii) UE should respond to Paging carrying the correct UE ID What is the "correct UE ID" ? The correct UE-ID is the one (S-TMSI) which is assigned to the UE during the registration, Step] Direction Message Memo /< Power On and Registration > [Assign @ S-TMSI ‘= Now UE is in IDLE mode > Paging with incorrect UE ID Wait for 5 secs (UE should not respond to Paging during this pASS/FaIL period) a Paging with incorrect UE ID RRC Connection Request PASS/FAIL RRC Connection Setup RRC Connection Setup Complete PASS/FAIL ‘< Complete the remainig Bearer Setup Process > 8.1.3.4 RRC connection release / Redirection to another E-UTRAN frequency I think just the following sequence would explain everything. No further details would be required. Step| Direction Message Memo < RRC Connection Release with IE redirectionInformation including leutra-CarrierFreq of Destination Cell> 2 < Registration to the Destination cell > st@5 should carry the EARFCN for the destination (target) cel] toc i:= CHOICE [systemmnformation] +-systemtnfornation ::= SEQUENCE “criticalextensions ::= CHOICE [systemmnformation-r8] +-systeminformation-r& ::= SEQUENCE [0] +*sib-Typeandinfo ::= SEQUENCE OF SIZE(1. .maxst6[32]) [1] | s- ire CHOICE [sib5] | #-sibS r= Sequence s-interFreqcarrierFreqList ::= SEQUENCE OF SIZE(. .maxrre s-InterfreqcarrierFreqinfo ::= SEQUENCE [001100] t-dl-carrierFreq ::= INTEGER (0. .maxEARFCN[65535])_ [5230] -RKLevMtin_ = INTEGER (-70,.-22) [-53] Max i1= INTEGER OPTIONAL :Omit -ReselectionEUTRA ::= INTEGER (O..7) [0] “Rese lectionEUTRA-SF ::= SEQUENCE OPTIONAL omit > (1) i i i i i i i i i i +-allowedMeastandwidth : I i i i I I +-threshx-High NTEGER (O,.31) [2] tthreshx-Low ::= INTEGER (0.131) [1] NUMERATED [mbw50] +-presenceantennaPortl ::= BOOLEAN [FALSE] 4-cellReselectionPriority ::= INTEGER OPTIONAL: Omit toneighcellconfig ::= BIT STRING SIZE(2) [01] +-g-Offsetrreq ::= ENUMERATED [80] OPTIONAL: Exist ScinterFreqveighCelIList ::= SEQUENCE OF OPTIONAL:omit s-interFreqelackCel1List ::= SEQUENCE OF OPTIONAL:omit noncriticalExtension ::= SEQUENCE OPTIONAL:Omit RRC Connection Release should carry the E-ARFCN of the destination cell hipshwww sharelechnota.com/himlLTE Protocol CTNmifTest Case Description 1621srmanot7 ShareTectnote DL-DCCH-Message ::= SEQUENCE tomessage ::= CHOICE [cl] toc1 it= CHOICE [rrcconnectionRelease] 4-rreconnectionRelease ::= SEQUENCE -rre-TransactionIdentifier ::= INTEGER (0..3) [0] -criticalextensions ::= CHOICE [cl] 4oc1 ::= CHOICE [rrcconnectionRelease-r8) s-rreconnectionRelease-r8 :!= SEQUENCE [100] trreleaseCause ::= ENUMERATED [loadgalancingTAUrequired] +-redirectedcarriertnfo ::= CHOICE [eutra] OPTIONAL: Exist | t-eutra ::= INTEGER (0. -maxEARFCN[65535]) [5250] +ridleModeMobilitycontrolinfo ::= SEQUENCE OPTIONAL:omit +-noncriticalextension ::= SEQUENCE OPTIONAL :omit 8.1.1.6 RRC / BCCH modification in connected mode Test Purpose : Test if UE correctly respond to Paging message with systemInfoModification and properly check systemInfoValueTag in SIB1 and successfully decode other SIBs according to systemInfoValueTag in SIB1 Step] Direction Message, Memo i < Power On and Registration > 2 = Now UE Is in IDLE mode > 3 Paging with systemInfoModification 4 [SIB1 with systemInfoValueTag = 1 5 ‘S182 with specified ‘prach configuration’ 6 PRACH as specified in SIBZ PASS/FAIL 7 RACH Response 8.1.2 n establishment / Ks=1.25/ Success and test equipment. Test Purpose : To see if UE can detect Paging message and establish the proper RRC Connection in response to the pagina message, This would be one of the simplest and standard test case, You can use this test as a basic operation test both for UE Step] Direction Message Memo ‘= Power On and Registration > ‘= Now UE is in IDLE mode > Paging RRC Connection Request (with the cause of mt-Accesss) PASS/FAIL. RRC Connection Setup RRC Connection Setup Complete PASS/FAIL -< Complete the remainig Bearer Setup Process > 8.1.2. n establishment / Return to idle state after T300 timeout Test Purpose : Simply put, this is for testing 7300 operation What is. has to start T300 right after it sends RRC Connection Request and stops the timer when it gets the response to the message from SS. But if the UE does not get any response until T300 expires, It should get back to IDLE mode. 7300 value is specified in SIB2, 300 ? itis the timer that defines the timing from 'RRC Connection Request’ to the response from the $S. UE Step] Direction Message, Memo i = Power On and Registration > 2 = Now UE Is in IDLE mode > 3 Make a MO call 4 RRC Connection Request and start T300 5 Nothing (SS does not send any response, CR or RRC Conn Setup)| hipihwww sharelechnota.comihimlLTE Protocol CTNmifTest Case Description 162‘srmaot7 ShareTectnote for 2 seconds 6 May or May not send RRC Connection Request once or more 7 ___[T300 expires (T300 timeout) 8 “=UE> [Goes back to IDLE state PASS/FAIL during the registration Test Purpose : To check process. 8.2.1.1 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_IDLE to RRC_CONNECTED / Success / Default bearer / Early bearer establishment if UE successfully ‘re-establish’ the default EPS bearer in response to Paging message. (I used the term "re-establish" because UE does not re-esablish the EPS bearer. It will use created during registration. It will establish only RRC session to use the default EPS beat the default EPS bearer rer Which has been created Step] Direction Message, Memo < Power On and Registration > [Default EPS Bearer Active -< Now UE is in IDLE mode > Paging RRC Connection Request (with the cause of mt-Accesss) RRC Connection Setup RRC Connection Setup Complete (Service Request) ‘Security Mode Command RRC Connection Reconfiguration. ‘Security Mode Complete PASS/FAIL RRCConnectionReconfigurationComplete PASS/FAIL. 8.2.1.3 RRC connecti Test Purpose : Overall (Dedicated EPS Bearer Protocol Sequence is very similar to 8.2.1.1, but the difference in when it gets Paging message. jon reconfiguration / Radio bearer establishment / Success /Dedicated bearer this case is that UE is not ysing the EPS bearer (default EPS bearer) which has been establistied during registration. It creates 2 new EPS bearer Step] Direction Message, Memo < Power On and Registration > [Default EPS Bearer Active < Now UE is in TDLE mode > Paging RC Connection Request (with the cause of mt-Accesss) RRC Connection Setup, RRC Connection Setup Complete (Service Request) [Security Mode Command [Security Mode Complete RRC Connection Reconfiguration for Dedication EPS Bearer RCConnectionReconfigurationComplete lulinformationTransfer (ACTIVATE DEDICATED EPS BEARER \CONTEXT ACCEPT) 8.2.3.1 RRC connecti Test Purpose : To chec! only RRC layer, but als jon reconfiguration / Radio bearer release / Success k If UE can properly release the radio bearer that has been establ 59 all the lower layer configurations properly. ished. Tt has to release not Step] Direction Message, Memo < Power On and Registration > ‘= Now UE is in IDLE mode > Paging < RRC Connection Setup > Create the DRB 2> 6 itpshwwsharelechnota comin RRCConnectionReconfiguration with drb-ToReleaseList ILTE_Prolocol CT HmifTest_Case_Descripton wrt‘srmaot7 ShareTectnote RRCConnectionReconfigurationComplete lulInformationTransfer 8.2.4.2 RRC connection reconfiguration / Handover / Success / Common preamble I recommend you to study this test case as much as possible and take this as @ back bone of all the handover related tests Test Purpose : Check if UE successfully recognize the target cell and performe measurement, handover and sent ‘RRC Connection Reconfig Complete’ message to target cell step] Direction Message Target Cell [Memo 1 | ve<-> 88 |e Power On and Registration > calli B [ue <=> §5 |e now UE lem 1OLE mode > cells B | ue<—ss [Posing ceils ri RC Connection Request cella 5 RC Connection Setup cella 6 RC Connection Setup Compete cella i Isecurty Mode Command cella 5 security Mode Complete cella 9 RRC Connection Reconfiguration Cell 1 reactivating default EPS 10 JaRCConnectonReconfiguratonComplete cella in RC Connection Reconfiguration cata Measurement Contre for 2 RCConnectionReconfigurationComplete cai 1B Measurement Report cella i ARC Connection Reconfiguration Cell |Handover Command is PRACH caii2 16 RACH Response cai? 7 JaRCConnectonReconfigurationComplete call? _[PASS/FAIL 8 leapabiityEnauiry calla o lueCapabiitynformation calla bo lstnformationTransfer + Detach Request calla be BRC Connection Release cea 8.3.3.1 Measurement configura n control and reporting / SON / ANR / CGI reporting of E-UTRAN cell Test Purpose : Check if i) UE successfully detect the condition for Event A3 and report it through Measurement Report hipshwww sharelectnota.cominimlLTE Protocol CT Nites! Case Description a2srmanot7 ShareTectnote il) UE successfully perform detect the SIBs of neighbour cell during the connected mode (connected mode DRX) and report the neighbour cell CGT through Measurement Report Step] Direction Message Target Cell |Memo 1 /< Power On and Registration > Cell 1 2 /< Now UE is in IDLE mode > cell 1 3 Paging Cell 1 la UE---> SS_|RRC Connection Request Cell 1 5 RRC Connection Setup Cell 1 6 UE---> Ss__|RRC Connection Setup Complete Cell 1 7 ‘Security Mode Command Cell 1 8 UE---> ss _|Security Mode Complete cell 1 reactivating default EPS 9 RRC Connection Reconfiguration cell [peactly 10 RRCConnectionReconfigurationComplete cell 1 Measurement Control for (Target Cell 11 | UE<-—Ss_ [RRC Connection Reconfiguration cell 1 * Configure Event A3 12 RRCConnectionReconfigurationComplete Cell 1 13 ‘Set Cell RS EPRE = -85, Cell2 RS EPRE = increase Nbr cell power 14 | UE--->SS_ |Measurement Report cet [event a3 Measurement Control for ITarget Cell 15 RRC Connection Reconfiguration cell 1 + DRX * reportcot 16 Measurement Report cell |cell2 cor 8.5.1.1 Radio link failure / RRC connection re-establishment success This test case represents a situation that I was asked about the most. The question is "How can I emulate the situation to show how UE behavior when Radio Link Is broken ?°, meaning the duplication of Radio Link Failure. ‘The real questions here is "What is the definition of Radio Link Failure 2” and "how to duplicate the Radio Link Failure’. 1 don't think this test cases alone will give you all the details of the answers to the question, but at least you would get some big picture of this situation I strongly recommend you the test case description in 3GPP 36.523. In the description, you will see It refers to a couple of other specifications as well (e.g, 36.331, 36.304 etc). Follow the references as much as possible. Don't try doing all of this at once.. it will take time, Step] Direction Message Memo 1 | UE <--> SS |< Power On and Reaistration > hipihww sharelectnota.cominimlLTE Protocol CThimifTes! Case Description 921‘srmaot7 ShareTectnote < Now UE Is in IDLE mode > 2 3 Paging 4 < RRC Connection Setup > 5 < Create the DRB 2> 6 ‘= Now in CONNECTED MODE > Z ARCConnectionReconfigurationComplete le Power Off the current cell and turn on the second cell with -65 \dBm/15 Khz 9 Radio Link is broken between UE and Cell 1, and T310 starts \UE should not initiate RRC connection re-establishment “0 iprocedure on Cell 1 or Cell 2 until T310 expires. PASS/FAIL at RRCConnectionReestablishment Request PASS/FATL 12 RRCConnectionReestablishment, a3 RRCConnectionReestablishment Complete 14 RRCConnectionReconfiguration is RRCConnectionReconfigurationt Complete 16 ‘< Now UE should be in CONNECTED MODE > PASS/FAIL 9.1.2.1 Authentication accepted Test Purpose : Check if UE properly calculated Authentication-related parameters and successfully completes Authentication Process. Note : I recommend you to read this test case description on 3GPP 36.523 carefully and understand very detail. It will help you to understand LTE Authentication procedure. Step] Direction Message Memo y = Power On > 2 < RACH, Contention Resolution> 3 ARC Connection Setup 4 RRC Connection Setup Complete + ATTACH REQUEST 5 AUTHENTICATION REQUEST 6 [AUTHENTICATION RESPONSE PASS/FAIL 7 NAS : SECURITY MODE COMMAND, 8 NAS : SECURITY MODE COMPLETE PASS/FAIL 9 ESM = INFORMATION REQUEST 10 ESM : INFORMATION RESPONSE it RRC Connection Reconfiguration + ATTACH ACCEPT 12 RRC Connection Reconfiguration Complete + ATTACH COMPLETE 13 ‘< Now in IDLE Mode > 4 Paging 15 < RACH, Contention Resolution> 16 RRC Connection Setup 17 RRC Connection Setup Complete + SERVICE REQUEST PASS/FAIL 18 < Complete the remaining Procedure > 9.1.2.3 Authentication not accepted by the network / GUTI used / Authentication reject and re- authentication Test Purpose : Test if UE properly handles the situation when it received ‘Authentication Reject’ message from the network: hipshwww sharelechnota.com/himlLTE Protocol CTNmifTest Case Description m2ShareTectnote Message. ‘Memo < Power On > = RACH, Contention Resolution> IRRC Connection Setup [RRC Connection Setup Complete + ATTACH REQUEST [AUTHENTICATION REQUEST [AUTHENTICATION RESPONSE [PASS/FAIL [AUTHENTICATION REJECT [RRC Connection Release ‘< UE Should not send ATTACH REQUEST for 30 secs > [PASS/FATL [ATTACH REQUEST [PASS/FATL hipihww sharalechnola.comMhimlLTE_Prolocol CTHmifTest_Case Description ae