Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 1 of 8 PageID #: 1067
`
`
`
`
`Exhibit “D”
`
`

`

`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 2 of 8 PageID #: 1068
`
`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 2 of 8 PagelD #: 1068
`
`ETSI TS 136 300 V8.4.0 (2008-04)
`
`Technical Specification
`
`Evolved Universal Terrestrial Radio Access (E-UTRA) and
`Evolved Universal Terrestrial Radio Access (E-UTRAN);
`Overall description;
`Stage 2
`(3GPP TS 36.300 version 8.4.0 Release 8)
`
`
`
`

`

`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 3 of 8 PageID #: 1069
`
`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 3 of 8 PagelD #: 1069
`
`3GPP TS 36.300 version 8.4.0 Release 8
`
`1
`
`ETSI TS 136 300 V8.4.0 (2008-04)
`
`Reference
`RTS/TSGR-0236300v840
`
`Keywords
`
`ETSI
`
`650 Route des Lucioles
`F-06921 Sophia Antipolis Cedex - FRANCE
`
`Tel.: +33 4.92 944200 Fax: +33 493 65 47 16
`
`Siret N° 348 623 562 00017 - NAF 742 C
`Association a but non lucratif 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.eisi.or
`
`The present document may be madeavailable in more than oneelectronic version orin print. In any case of existing or
`perceiveddifference in contents between such versions, the reference version is the Portable Document Format (PDF).
`In case of dispute, 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 maybe subject to revision or change of 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 one ofthe following services:
`hitp://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 ETSIlogo are Trade Marks of ETSIregistered
`for the benefit of its Members.
`3GPP™js a Trade Mark of ETSI registered for the benefit of its Members andof the 3GPP Organizational Partners.
`
`

`

`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 4 of 8 PageID #: 1070
`
`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 4 of 8 PagelD #: 1070
`
`3GPP TS 36.300 version 8.4.0 Release 8
`
`14
`
`ETSI TS 136 300 V8.4.0 (2008-04)
`
`
`
`MME /S-GW
`
`E-UTRAN
`
`Figure 4-1: Overall Architecture
`
`4.1
`
`Functional Split
`
`The eNB hosts the following functions:
`
`-
`
`-
`
`-
`
`Functions for Radio Resource Management: Radio Bearer Contrel, Radio Admission Control, Connection
`Mobility Control, Dynamic allocation of resources to UEsin both uplink and downlink (scheduling);
`
`IP header compression and encryption of user data stream;
`
`Selection of an MMEat UEattachment whennorouting to an MMEcanbe determined from the information
`provided by the UE;
`
`- Routing of User Plane data towards Serving Gateway;
`
` -
`
`Scheduling and transmission of broadcast information (originated from the MME or O&M);
`
`- Measurement and measurement reporting configuration for mobility and scheduling.
`
`The MME hoststhe following functions (see 3GPP TS 23.401 [17]):
`
`-
`
`-
`
`NASsignalling;
`
`NASsignalling security;
`
`- AS Security control;
`
`-
`
`-
`
`Inter CN nodesignalling for mobility between 3GPP access networks;
`
`Idle mode UE Reachability (including control and execution of paging retransmission);
`
`- Tracking Area list management(for UEin idle and active mode);
`
`-
`
`PDN GW and Serving GWselection;
`
`- MMEselection for handovers with MME change;
`
`-
`
`S§GSN selection for handovers to 2G or 3G 3GPP access networks;
`
`- Roaming;
`
`

`

`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 5 of 8 PageID #: 1071
`
`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 5 of 8 PagelD#: 1071
`
`3GPP TS 36.300 version 8.4.0 Release 8
`
`15
`
`ETSI TS 136 300 V8.4.0 (2008-04)
`
`Bearer managementfunctions including dedicated bearer establishment.
`
`The Serving Gateway (S-GW)hosts the following functions (see 3GPP TS 23.401 [17]):
`
`The local Mobility Anchorpoint for inter-eNB handover;
`
`Mobility anchoring for inter-3GPP mobility;
`
`E-UTRAN idle mode downlink packet buffering and initiation of network triggered service request procedure;
`
`Lawful Interception;
`
`Packet routeing and forwarding;
`
`Transport level packet marking in the uplink and the downlink;
`
`Accounting on user and QCI granularity for inter-operator charging;
`
`UL and DLcharging per UE, PDN, and QCI.
`
`The PDN Gateway (P-GW)hosts the following functions (see 3GPP TS 23.401 [17]):
`
`Per-user based packetfiltering (by e.g. deep packet inspection);
`
`Lawful Interception;
`
`UEIP addressallocation;
`
`Transport level packet marking in the downlink;
`
`UL and DLservice level charging, gating and rate enforcement;
`
`DL rate enforcement based on AMBR;
`
`This is summarized on the figure below where yellow boxes depictthe logical nodes, white boxes depict the functional
`entities of the control plane and blue boxes depictthe radio protocol layers.
`
`NOTE:_it is assumed that no other logical E-UTRANnode than the eNB is needed for RRM purposes. Moreover,
`dueto the different usage of inter-cell RRM functionalities, each inter-cell RRM functionality should be
`considered separately in order to assess whetherit should be handled in a centralised mannerorin a
`distributed manner.
`
`NOTE:
`
`MBMSrelated functions in E-UTRANare described separately in subclause 15.
`
`

`

`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 6 of 8 PageID #: 1072
`
`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 6 of 8 PagelD #: 1072
`
`3GPP TS 36.300 version 8.4.0 Release 8
`33
`ETSI TS 136 300 V8.4.0 (2008-04)
`
`
`
`| PDCPheader
`PDCP SDU
`
`|————
`
`Figure 6.3.2-1: PDCP PDU Structure
`
`6.4
`
`Data flows through Layer 2
`
` 7
`
`RRC
`
`This subclause provides an overview on services and functions provided by the RRC sublayer.
`
`7.1
`
`Services and Functions
`
`The main services and functions of the RRC sublayerinclude:
`
`- Broadcast of System Informationrelated to the non-access stratum (NAS);
`
`- Broadcast of System Information related to the access stratum (AS);
`
`- Establishment, maintenance and release of an RRC connection between the UE and E-UTRANincluding:
`
`- Allocation of temporary identifiers between UE and E-UTRAN;
`
`- Configuration of signalling radio bearer(s) for RRC connection:
`
`- Low priority SRB and highpriority SRB.
`
`-
`
`Security functions including key management;
`
`- Establishment, configuration, maintenance andrelease of point to point Radio Bearers;
`
`- Mobility functions including:
`
`- UE measurement reporting and control of the reporting for inter-cell and inter-RAT mobility;
`
`-
`
` Inter-cell handover;
`
`UE cell selection and reselection and control of cell selection and reselection;
`
`- Context transfer between eNBs.
`
`- Notification for MBMSservices;
`
`- Establishment, configuration, maintenance and release of Radio Bearers for MBMSservices;
`
`- QoS managementfunctions;
`
`- UE measurementreporting and controlof the reporting;
`
`-
`
`NASdirect message transfer to/from NASfrom/to UE.
`
`7.2
`
`RRC protocol states & state transitions
`
`RRCusesthe following states:
`
`

`

`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 7 of 8 PageID #: 1073
`
`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 7 of 8 PagelD #: 1073
`
`3GPP TS 36.300 version 8.4.0 Release 8
`
`34
`
`ETSI TS 136 300 V8.4.0 (2008-04)
`
`-
`
`PLMNselection;
`
`- DRX configured by NAS (Option to have UE specific DRX is FFS);
`
`- Broadcast of system information;
`
`- Cell re-selection mobility;
`
`- The UE shall have been allocated an id which uniquely identifies the UE in a tracking area;
`
`- No RRC context stored in the eNB.
`
`- RRC_CONNECTED:
`
`- UE has an E-UTRAN-RRCconnection;
`
`- UE has context in E-UTRAN;
`
`-
`
`E-UTRAN knowsthe cell which the UE belongsto;
`
`- Network can transmit and/orreceive data to/from UE;
`
`- Network controlled mobility (handover and inter-RAT cell change order to GERAN with NACC);
`
`- Neighbourcell measurements;
`
`- At PDCP/RLC/MAClevel:
`
`- UE can transmit and/orreceive data to/from network;
`
`- UE monitors control signalling channel for shared data channel to see if any transmission over the shared
`data channel has been allocated to the UE;
`
`- UEalso reports channel quality information and feedback information to eNB;
`
`- DRX period can be configured according to UE activity level for UE powersaving andefficient resource
`utilization. This is under control of the eNB.
`
`7.3
`
`Transport of NAS messages
`
`In E-UTRAN, NASmessagesare either concatenated with RRC messagesorcarried in RRC without concatenation.
`Initial Direct Transfer is not used in E-UTRANand no NAS message is concatenated with RRC connection request.
`
`NOTE:
`
`NAS messagesare integrity protected and ciphered by PDCP, in addition to the integrity protection and
`ciphering performed by NAS.
`
`7.4
`
`System Information
`
`Scheduling information (indicating starting times) is provided for a group of system information blocks (SIBs) that have
`the same scheduling requirements(i.e. periodicity). RRC concatenates such a group of SIBs into a Scheduling Unit
`(SU) message. It is expected that typically 3 or 4 SUs will be used. The mapping of SIBs on to SUs may be
`configurable or fixed in the specification (FFS). When multiple SUsare sent in the same TTI, they are mapped on the
`same downlink transport block.
`
`The following system information is carried on the BCH:
`
`-
`
`Physical layer parameters:
`
`- Downlink system bandwidth [4bits];
`
`- Numberoftransmit antennas [1..2 bits];
`
`

`

`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 8 of 8 PageID #: 1074
`
`Case 6:14-cv-00982-KNM Document 139-4 Filed 10/26/15 Page 8 of 8 PagelD#: 1074
`
`3GPP TS 36.300 version 8.4.0 Release 8
`
`83
`
`ETSI TS 136 300 V8.4.0 (2008-04)
`
`- HandoverPreparation procedure;
`
`- Handover Resource Allocation procedure;
`
`- Handover Completion procedure;
`
`- Handover Cancellation procedure.
`
`-
`
`-
`
`Paging procedure;
`
`NAStransport procedure:
`
`- Ul direction (Initial UE Message);
`
`- Uldirection (Uplink NAS transport);
`
`- Dl direction (Downlink NAStransport).
`
`-
`
`ErrorIndication procedure:
`
`-
`
`eNB initiated error indication procedure;
`
`- MMEinitiated error indication procedure.
`
`- Reset procedure:
`
`-
`
`eNBinitiated Reset procedure;
`
`- MMEinitiated Reset procedure.
`
`-
`
`Initial Context Setup procedure;
`
`- UE Context Modification procedure.
`
`[S1AP] PAGING
`
`
`
`Paging Response (NAS means)
`
`
`
`
`The paging response back to the MMEis initiated on NASlayer and is sent by the eNB based on NAS-level routing
`information.
`
`19.2.2.2
`
`S1 UE Context Release procedure
`
`The S1 UE Context Release procedure causes the eNB to remove all UEindividual signalling resources and therelated
`user data transport resources. This procedureis initiated by the EPC and maybe triggered on request ofthe serving
`eNB.
`
`