Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 1 of 7 PageID #: 1060
`
`
`
`
`Exhibit “C”
`
`

`

`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 2 of 7 PageID #: 1061
`
`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 2 of 7 PagelD #: 1061
`
`ETSI TS 136 331 vs.2.0 (2008-11)
`
`Technical Specification
`
`LTE;
`Evolved Universal Terrestrial Radio Access (E-UTRA);
`Radio Resource Control (RRC);
`Protocol specification
`(3GPP TS 36.331 version 8.2.0 Release 8)
`
`lte
`
`
`
`

`

`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 3 of 7 PageID #: 1062
`
`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 3 of 7 PagelD #: 1062
`
`3GPP TS 36.331 version 8.2.0 Release 8
`
`1
`
`ETSI TS 136 331 V8.2.0 (2008-11)
`
`Reference
`DTS/TSGR-0236331v820
`
`Keywords
`LTE
`
`ETSI
`
`650 Route des Lucioles
`F-06921 Sophia Antipolis Cedex - FRANCE
`
`Tel.: +33 492944200 Fax: +33 4 93 65 47 16
`
`Siret N° 348 623 562 00017 - NAF 742. C
`Association a but nonlucratif enregistrée a la
`Sous-Préfecture de Grasse (06) N° 7803/88
`
`Important notice
`
`Individual copies of the present document can be downloaded from:
`http://www.etsi.org
`
`The present document may be made available in more than one electronic versionor in print. In any case of existing or
`perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
`In case ofdispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
`within ETSI Secretariat.
`:
`
`Users of the present document should be aware that the document may be subject to revision or changeof status.
`Information on the current status of this and other ETSI documentsis available at
`http://portal.etsi.org/tb/status/status.asp
`
`If you find errors in the present document, please send your commentto oneofthe following services:
`htip://portal.etsi.org/chaircor/ETS|_support.asp
`
`Copyright Notification
`
`No part may be reproduced except as authorized by written permission.
`The copyright and the foregoing restriction extend to reproduction in all media.
`
`© European Telecommunications StandardsInstitute 2008.
`All rights reserved.
`
`DECT™, PLUGTESTS™, UMTS™, TIPHON™, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
`for the benefit of its Members.
`3GPP™ jis a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
`
`

`

`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 4 of 7 PageID #: 1063
`
`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 4 of 7 PagelD #: 1063
`
`3GPP TS 36.331 version 8.2.0 Release 8
`
`18
`
`ETSI TS 136 331 V8.2.0 (2008-11)
`
`Editor's note: The UE continuously ongoing actions in idle and connected (i.e. normative versions of the statements
`in 4.2.1) are specified within the respective sections, e.g. system information, paging (36.304),
`measurements. Same applies for the actions uponstate transitions.
`
`To be completed
`
`5.2
`
`System information
`
`5.2.1
`
`Introduction
`
`5.2.1.1
`
`General
`
`System information is divided into the MasterInformationBlock (MIB) and a numberof SystenInformationBlocks
`(SIBs). The MIB includes a limited numberof most essential and frequently transmitted parameters to acquire other
`information from thecell, and is transmitted on BCH. S1Bs other than SystemInformationBlockType! are carried in
`Systemlnformation (SI) messages and mapping of SIBs to SI messages is flexibly configurable by
`schedulingInformation included in SystemlnformationBlockType/, withrestrictions that: each SIB is contained only in a
`single SI message, only SIBs having the same scheduling requirement (periodicity) can be mappedto the same SI
`message, and Spstem/nformationBlockType2 is always mappedto the SI message that correspondsto the first entry in
`the list of S] messages in schedulingInformation. There may be multiple SI messages transmitted with the same
`periodicity. SystemInformationBlockTypel and all SI messages are transmitted on DL-SCH.
`
`5.2.1.2
`
`Scheduling
`
`The MIB usesa fixed schedule with a periodicity of 40 ms and repetitions made within 40 ms. The first transmission of
`the MIB is scheduled in subframe #0 of radio frames for which the SFN mod4 = 0,andrepetitions are scheduled in
`subframe #0 ofall other radio frames.
`
`The SystemInformationBlockType! uses a fixed schedule with a periodicity of 80 ms and repetitions made within 80 ms.
`Thefirst transmission of SysteminformationBlockTypel is scheduled in subframe #5 of radio frames for which the SFN
`mod 8 = 0, and repetitions are scheduled in subframe #5 ofall other radio frames for which SFN mod 2 = 0.
`
`The SI messages are transmitted within periodically occurring time domain windows(referred to as SI-windows) using
`dynamic scheduling. Each SI messageis associated with a SI-window and the SI-windowsofdifferent SI messages do
`not overlap. That is, within one SI-window only the corresponding SI is transmitted. The length of the SI-window is
`commonforall SI messages, and is configurable. Within the SI-window,the corresponding SI message can be
`transmitted a numberof times in any subframe other than MBSFNsubframes, uplink subframes in TDD, and subframe
`#5 of radio frames for which SFN mod 2 = 0. The UE acquires the detailed time-domain scheduling (and other
`information, e.g. frequency-domain scheduling, used transport format) from decoding SI-RNTI on PDCCH.
`
`A single SI-RNTIis used to address SystemInformationBlockType! as well as all SI messages.
`
`SypstemInformationBlockType! configures the S1-window length and the transmission periodicity for the 51 messages.
`
`Editor's note: It seems best to specify the handling of the scheduling information by means of an "elementary
`procedure", i.e. related to the receptionofthe related information elements.
`
`Editor's note: In the unlikely event that serving cell paging and target cell DBCHoverlap intime one of the two
`activities will need to be prioritised. This may lead into paging reception loss orincreases incell
`reselection interruption time.
`
`6.201.638
`
`System information validity and notification of changes
`
`System information changes only occurat specific radio framesi.e. the concept of a modification period is used. SI
`messages may be transmitted a numberof times with the same content within a modification period, as defined byits
`scheduling. The modification period boundaries are defined by SFN mod N.N is configured by system information.
`
`Whenthe network changes (some of the) system information,it first notifies the UEs about this change i.e. this may be
`done throughout a modification period. In the next modificationperiod, the network transmits the updated system
`
`

`

`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 5 of 7 PageID #: 1064
`
`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 5 of 7 PagelD #: 1064
`
`3GPP TS 36.331 version 8.2.0 Release 8
`
`19
`
`ETSI TS 136 331 V8.2.0 (2008-11)
`
`until the next modification period boundary. After this boundary, the UE acquires the new system information. There is
`a (short) period during which the UE does not have valid system information.
`
`Changenotification
`
`Updated information
`
`i
`
`BCCH modification period (n)
`
`BCCH modification period (n+1)
`
`Figure 5.2.1.3-1: Change of system Information
`
`
`
`abou changes in
`"AlthoughtheUE may beinformed
`d bo
`
`system information, no farther details are provided¢e.g. regarding which SI message has changed. The change
`notification mechanism is not used for the system information using an expiry timer (intended for the more dynamic
`system information).
`
`SystemInformationBlockTypel includes a value tag that indicates if a change has occurredin the SI messages. UEs may
`use this value tag e.g. uponreturn from out of coverage, to verify if the previously acquired system informationisstill
`valid. The UE considers system information to be valid for at most 6 hours from the momentit was received.
`
`Editor's note: The UE requirements corresponding with the above descriptive textare still to be captured elsewhere,
`e.g. within the paging procedure which maytrigger the BCCHacquisition procedure.
`
`Editor's note: [t is FFS when UEs in RRC_CONNECTED monitor paging for system information change detection.
`For example, UE may only need to monitor one paging occasion per one BCCH modification period,
`or it may need to monitorseveral paging occasion per one BCCH modification period with certain
`periodicity.
`
`Editor's note: If it will be agreed that the ETWSprimary notification is performed by means of paging, ETWS
`capable UEswill be required to read paging.
`
`52k
`
`System information acquisition
`
`5:27.21
`
`General
`
` Figure 5.2.2.1-1: System information
`
`The UE applies the system information acquisition procedure to acquire the AS- and NAS- system information that is
`broadcasted by the E-UTRAN. The procedure applies to UEs in RRC_IDLEand to UEs in RRC_CONNECTED.
`
`acquisition, normal
`
`

`

`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 6 of 7 PageID #: 1065
`
`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 6 of 7 PagelD #: 1065
`
`3GPP TS 36.331 version 8.2.0 Release 8
`
`25
`
`ETSI TS 136 331 V8.2.0 (2008-11)
`
`5.3.2
`
`Paging
`
`5.3.2.1
`
`General
`
`53.2.2
`
`Initiation
`
`E-UTRANinitiates the paging procedure bytransmitting the PAGING message at the UE"s paging occasion as
`specified in TS 36.304 [4]. E-UTRAN mayidentify multiple UEs within a Paging message.
`
`
`
`
`
`1>ForeachofthePagingincludedinthePagingmessagerecords
`TY
`
`15IFthesysiemInfoModificationisincluded
`
`
`
`
`
`
`
`_2>re-aequirethesysteminformationusingthesysteminformationacquisitionprocedureasspecifiedin5.2.2.
`
`53.3
`
`RRC connection establishment
`
`
`
`RRCConnectionRequest
`
`
`
`RRCConnectionSetup
`
`
`
`RRCConnectionSetupComplete
`
`Figure 5.3.3.1-1: RRC connection establishment, successful
`
`

`

`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 7 of 7 PageID #: 1066
`
`Case 6:14-cv-00982-KNM Document 139-3 Filed 10/26/15 Page 7 of 7 PagelD #: 1066
`
`3GPP TS 36.331 version 8.2.0 Release 8
`
`26
`
`ETSI TS 136 331 V8.2.0 (2008-11)
`
`
`
`
`RRCConnectionRequest
`
`RRCConnectionReject
`
`Figure 5.3.3.1-2: RRC connection establishment, network reject
`
`The purposeof this procedureis to establish an RRC connection. RRC connection establishment involves SRB1
`establishment. The procedureis also used to transfer the initial NAS dedicated information/ message from the UE to E-
`UTRAN.
`
`E-UTRANapplies the procedure as follows:
`
`-
`
`to establish SRBI only.
`
`5.3.3.2
`
`Initiation
`
`The UEinitiates the procedure when upperlayers request establishment of an RRC connection while the UEis in
`RRCIDLEstate.
`
`Uponinitiation of the procedure, the UE shall:
`
`1> if SystemInformationBlockType2 includes the accessBarringinformation:
`
`2> if the UEis establishing the RRC connection to perform an emergencycall:
`
`3> if the accessClassBarring for AC 10 is set to FALSE:
`
`4> consider accessto the cell as not barred;
`
`3> else if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15
`and
`/
`
`3> forat least one of these Access Classes the accessClassBarring is set to FALSE and, according to TS
`22.011[10] and TS 23.122 [11], it is valid for the UE to use this Access Class:
`
`NOTE1: ACs12, 13, 14 are only valid foruse in the home country and ACs 11, 15 are only valid for use in the
`HPLMN/ EHPLMN
`
`4> consideraccessto the cell as not barred;
`
`3> else:
`
`4> consideraccess to the cell as barred;
`
`2> else
`
`3> if the UE has one or more Access Classes, as stored on the USIM,with a value in the range 11..15 and
`
`3> for at least one of these Access Classes the accessClassBarring is set to FALSE and, according to TS
`22.011[10] and TS 23.122 [11], it is valid for the UE to use this Access Class:
`
`4> consider access to the cell as not barred;
`
`3> else if the UEis establishing the RRC connection to perform a mobile terminating call:
`
`4> consider access to the cell as not barred;
`
`