1 / 213

Message Flow for an AMR Speech Call

Message Flow for an AMR Speech Call. Introduction. UE is powered up. This material provides a detailed illustration of the message flow observed for an AMR speech call

prem
Download Presentation

Message Flow for an AMR Speech Call

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Message Flow for an AMR Speech Call

  2. Introduction UE is powered up This material provides a detailed illustration of the message flow observed for an AMR speech call The message flow is focused upon communication with the circuit switched core and does not include communication with the packet switched core. The UE starts by searching for candidate cells by correlating the RSSI with the code defining the primary SCH The UE then achieves radio frame synchronisation and reads the BCCH logical channel The BCCH provides system information including the cell selection criteria If the cell passes the cell selection criteria then the UE establishes an RRC connection and registers with the core network Having registered with the core network the UE returns to the RRC idle mode state and is ready to originate an AMR speech call An originating AMR speech call is made and handovers are completed as and when required Finally the AMR speech call is released and the UE returns to the RRC idle mode state Cell search Radio frame synchronisation Read BCCH Cell selection Register with core network Originating AMR speech call Handovers Release of AMR speech call

  3. Protocol Stacks • Communication between the UE, RNC and circuit switched core makes use of • Uu interface protocol stack • Iub interface protocol stack • Iu,cs interface protocol stack • A interface protocol stack Multimedia Gateway RNC 3G MSC Node B Uu Iub Iu,cs A Protocol stacks include both user and control planes The control plane of one protocol stack may make use of the user plane of another protocol stack e.g. RRC messages which form the control plane of the radio access protocol are communicated to and from the Node B using the user plane of the Iub protocol stack

  4. CS Radio Interface Protocol (RIP) User Plane • The 3G MSC provides connectivity to the circuit switched core and PSTN • The multimedia gateway provides transcoding for • Speech calls: between AMR and A Law PCM • Video calls: between 3G H324 and UDI • Transparent mode RLC is used between the UE and RNC • AAL2 based ATM is used to transfer user plane data across the Iub and Iu,cs interfaces UE Multimedia GW 3G MSC e.g. vocoder e.g. vocoder RNC A Law PCM, UDI etc A Law PCM, UDI etc RLC-U RLC-U Iu,cs UP Iu,cs UP Node B MAC MAC PSTN FP FP AAL2 AAL2 AAL2 AAL2 Link Layer Link Layer ATM ATM ATM ATM WCDMA L1 WCDMA L1 Phy Phy Phy Phy Phy Phy Phy Uu Iub Iu,cs A

  5. CS Radio Interface Protocol (RIP) Control Plane The radio interface protocol control plane allows RRC signalling between the RNC and UE RRC signalling is communicated across the Iub using the Iub user plane protocol stack i.e. using Frame protocol and AAL2 based ATM Acknowledged or unackowledged mode RLC is used between the UE and RNC UE RNC RRC RRC RLC-C RLC-C Node B MAC MAC FP FP AAL2 AAL2 ATM ATM WCDMA L1 WCDMA L1 Phy Phy Uu Iub

  6. Iub Protocol Stack (I) The Iub protocol stack has three planes The radio network control plane uses the NBAP protocol and completes tasks such as configuring a radio link at a Node B The transport network control plane uses ALCAP and is responsible for setting up and tearing down user plane transport bearers The user plane uses Frame Protocol and is responsible for encapsulating all data to and from the UE Radio Network Control Plane Transport Network Control Plane • ATM Adaptation Layer 5 (AAL5) is used for the control planes whereas AAL2 is used for the user plane • AAL2 • provides bandwidth efficient transmission for delay sensitive applications • Multiplexes packets from multiple users into one ATM connection (up to 248 users in 1 VCC) • AAL5 • Supports variable bit rate data. • No timing is required between transmitter and receiver User Plane NBAP Frame Protocol ALCAP Q.2630.1 Q.2150.2 SSCF-UNI SSCF-UNI SSCOP SSCOP AAL5 AAL5 AAL2 ATM Physical Layer

  7. Iub Protocol Stack (II) The planner assigns a Virtual Path Identifier (VPI) on a per Node B basis Each VPI can have multiple Virtual Channel Identifiers (VCI) If the VCI is assigned to an AAL2 connection then each VCI can have up to 248 Channel Identifiers (CID) The planner assigns a VCI for common NBAP on a per Node B basis The planner assigns a VCI for dedicated NBAP on a per WAM basis The planner assigns a VCI for O&M on a per Node B basis The planner assigns a VCI for the transport network control plane on a per Node B basis if Node B AAL2 multiplexing is supported (AXUB is used). Otherwise the planner assigns a VCI for the transport network control plane on a per WAM basis (AXUA is used). The transport network control plane assigns VCI and CID for the user plane RACH, FACH and PCH The transport network control plane dynamically assigns VCI and CID for the user plane DCH as and when required The same VCI is assigned for the user plane RACH, FACH, PCH, DCH Radio Network Control Plane Transport Network Control Plane User Plane Example for a single WAM Node B Dedicated NBAP VCI = 34 RACH VCI = 46 CID = 8 FACH VCI = 46 CID = 9 PCH VCI = 46 CID = 10 DCH1 VCI = 46 CID = 11 DCH2 VCI = 46 CID = 12 ALCAP VCI = 40 Node B assigned VPI = 44 Common NBAP VCI = 33 AAL5 AAL5 AAL2

  8. Iu-cs Protocol Stack (I) The Iu-cs protocol stack has three planes The radio network control plane uses the RANAP protocol and completes tasks such as configuring a RAB or assigning Iu-cs resources The transport network control plane is responsible for setting up and tearing down Iu transport bearers The user plane is responsible for encapsulating all data to and from the UE Radio Network Control Plane Transport Network Control Plane User Plane ATM Adaptation Layer 5 (AAL5) is used for the control planes whereas AAL2 is used for the user plane Iu User Plane Protocol RANAP Q.2630.1 Q.2150.1 SCCP MTP3b MTP3b SSCF-NNI SSCF-NNI SSCOP SSCOP AAL5 AAL5 AAL2 ATM Physical Layer

  9. Iu-cs Protocol Stack (II) The planner assigns a Virtual Path Identifier (VPI) on a per RNC basis The planner assigns a set of VCI that are pooled to support both the Radio Network Control Plane and the Transport Network Control Plane The transport network control plane assigns VCI and CID for the user plane Radio Network Control Plane Transport Network Control Plane User Plane Example for a single RNC VCI = 51, CID = 8 VCI = 52, CID = 8 UL RANAP VCI = 34, 35, 36, 37 MTP 3b VCI = 34, 35, 36, 37 RNC assigned VPI = 1 AAL5 AAL5 AAL2 Note: in this example the VCI are assigned from 34 rather than 33 to maintain consistency with NEC who do not support the use of VCI 33

  10. Cell Search UE is powered up The UE keeps a record of the previously used carrier. The cell search procedure starts by scanning this carrier The cell search procedure is completed by correlating RSSI against the known Primary SCH code Peaks in the correlation result indicate the presence of a cell as well as the multipath associated with the propagation channel to that cell Cell search Radio frame synchronisation Read BCCH Correlation Peaks Cell selection Correlation result Register with core network time Originating AMR speech call Once the UE has identified a cell the UE attempts to synchronise with that cell Handovers Release of AMR speech call

  11. Radio Frame Synchronisation UE is powered up • The UE completes the three step radio frame synchronisation process • Step 1: Primary SCH identification and slot synchronisation (completed during cell search) • Step 2: Code group identification and frame synchronisation using the Secondary SCH • Step 3: Scrambling code identification using the CPICH • Having completed these three steps the UE is able to decode the Primary CCPCH -> BCH -> BCCH Cell search Radio frame synchronisation Read BCCH Cell selection Slot 1 Slot 2 Slot 15 Slot 1 Cp Primary SCH Cp Cp Register with core network Cs1 Secondary SCH Cs2 Cs1 Originating AMR speech call Primary CCPCH 256 chips 2560 - 256 chips Handovers Primary CPICH Release of AMR speech call

  12. Read BCCH UE is powered up The BCCH encapsulates the System Information message which includes the Master Information Block (MIB), Scheduling Blocks (SB) and System Information Blocks (SIB) The following slides illustrate the information that the UE reads from the BCH Cell search Radio frame synchronisation Read BCCH Cell selection Register with core network Originating AMR speech call Handovers Release of AMR speech call

  13. System Information Message BCCH contains the System Information message Message is sent using Transparent mode RLC BCH is always interleaved over a 20 ms TTI SFN Prime is the the SFN of the first 10 ms radio frame The actual value of SFN Prime is 2 x IE i.e. 2 x 648 in this example This System Information message includes the MIB, SIB2, SIB7 and SIB18 The UE extracts the MIB and each of the SIBs and decodes each separately The contents of the BCH varies from one system information message to the next i.e. whether or not a MIB and SB are included and which SIBs are included Scheduling of the SIBs is completed by the RNC but indicated to the UE using Information Elements (IE) within the MIB and SB SIBs may be segmented and broadcast in multiple System Information messages SystemInformation-BCH : { sfn-Prime 648, payload completeSIB-List : { { sib-Type masterInformationBlock, sib-Data-variable '000100001000110100000100000001000000000000001000010001000010100000100001100000010011011010000010010101010000111111'B }, { sib-Type systemInformationBlockType2, sib-Data-variable '00000000000101011000'B }, { sib-Type systemInformationBlockType7, sib-Data-variable '00000001000000000'B }, { sib-Type systemInformationBlockType18, sib-Data-variable '10010001000000000000'B } }

  14. Master Information Block (MIB) • The Master Information Block (MIB) is broadcast once every 8 radio frames (3GPP specified) • The MIB has a SIB_POS = 0 and a SIB_OFF = 2 frames (offset is only applicable when the MIB requires multiple segments) • The MIB includes the MIB value tag which has a range from 1 to 8. The value tag indicates when the MIB contents have changed • The network type is specifed as being GSM-MAP with an MCC of 234 and an MNC of 20 • The SIB reference list specifies scheduling information for SIB 1 and Scheduling Block (SB) 1 (SB 2 is not currently used ) • The SIBs which aren’t scheduled within the MIB are scheduled within Scheduling Block 1 • SIB 1 scheduling information: • Value tag of 1 • repetition every 8 frames • position is frame 0 (actual value = IE x 2) • Scheduling Block 1 scheduling information: • Value tag of 2 • repetition every 16 frames • position is frame 4 (actual value = IE x 2) MasterInformationBlock : { mib-ValueTag 2, plmn-Type gsm-MAP : { plmn-Identity { mcc { 2, 3, 4 }, mnc { 2, 0 } } }, sibSb-ReferenceList { { sibSb-Type sysInfoType1 : 1, scheduling { scheduling { sib-Pos rep8 : 0 } } }, { sibSb-Type sysInfoTypeSB1 : 2, scheduling { scheduling { sib-Pos rep16 : 2 } } } }

  15. Scheduling Block 1 (SB1) (I) • The Scheduling Block 1 (SB1) includes scheduling information for SIBs 2, 3, 5, 7, 11 and 18 • The repetition period, position of each SIB and their value tag is included: • SIB 2: • Value tag of 1 • repetition every 8 frames • position is frame 2 (actual value = IE x 2) • SIB 3: • Value tag of 1 • repetition every 8 frames • position is frame 2 (actual value = IE x 2) • SIB 5: • Value tag of 1 • repetition every 32 frames • SIB is divided into 3 segments • position of first segment is frame 6 (actual value = IE x 2) • Position of subsequent segments are offset by 6 and 2 frames SysInfoTypeSB1 : { sib-ReferenceList { { sib-Type sysInfoType2 : 1, scheduling { scheduling { sib-Pos rep8 : 1 } } }, { sib-Type sysInfoType3 : 1, scheduling { scheduling { sib-Pos rep8 : 1 } } }, { sib-Type sysInfoType5 : 1, scheduling { scheduling { segCount 3, sib-Pos rep32 : 3, sib-PosOffsetInfo { so6, so2 } } } }, {

  16. Scheduling Block 1 (SB1) (II) • The repetition period, position of each SIB and their value tag is included: • SIB 7: • Value tag isn’t applicable as SIB 7 contains data which can change in every message • repetition every 8 frames • position is frame 2 (actual value = IE x 2) • SIB 11: • Value tag of 2 • repetition every 64 frames • SIB is divided into 4 segments • position of first segment is frame 22 (actual value = IE x 2) • Position of subsequent segments are offset by 6, 32 and 38 frames • SIB 18: • Value tag of 1 • repetition every 8 frames • position is frame 2 (actual value = IE x 2) sib-Type sysInfoType7 : NULL, scheduling { scheduling { sib-Pos rep8 : 1 } } }, { sib-Type sysInfoType11 : 2, scheduling { scheduling { segCount 4, sib-Pos rep64 : 11, sib-PosOffsetInfo { so6, so26, so6 } } } }, { sib-Type sysInfoType18 : 1, scheduling { scheduling { sib-Pos rep8 : 1 } } } }

  17. SIB Timing The SIB schedule illustrated below can be deduced from the timing information 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 MIB SB1 SIB1 SIB2 SIB3 2 3 2 3 1 1 SIB5 SIB7 2 SIB11 1 SIB18 This schedule represents an example and will change if SIB sizes and/or SIB priorities change

  18. SIB 1(I) The common core network NAS IE defines the LAC to which the cell belongs i.e. 5E = 94 in this case The CS core specific NAS IE defines T3212 and ATT. The unit for T3212 is decihours i.e. 6 minutes. In this case it is set to 0 which implies no periodic LAU. ATT has been set to 1 which means that the UE should complete an IMSI attach The CS core DRX cycle length is defined using a coefficient of 6 i.e. DRX cycle length = 26 = 64 The PS core specific NAS IE defines the RAC and Network Mode of Operation (NMO). In this case the RAC is defined by 5E = 94. The NMO is 1 which indicates that network mode of operation II should be assumed. This means that the Gs interface is not present between the 3G MSC and SGSN The PS core DRX cycle length is defined using a coefficient of 6 i.e. DRX cycle length = 26 = 64 In this case the two DRX cycle lengths are equal. If they were different the UE would use the smallest SysInfoType1 : { cn-CommonGSM-MAP-NAS-SysInfo '005E'H, cn-DomainSysInfoList { { cn-DomainIdentity cs-domain, cn-Type gsm-MAP : '0001'H, cn-DRX-CycleLengthCoeff 6 }, { cn-DomainIdentity ps-domain, cn-Type gsm-MAP : '5E01'H, cn-DRX-CycleLengthCoeff 6 } },

  19. SIB 1 (II) • Connected mode timers and constants are defined: • T312 = 4 s, N312 = 4: when initiating a DCH L3 of the UE must obtain 4 in-sync indicators from L1 within 4 s or the physical channel establishment will be reported as a failure • T314 = 0 s: the re-establishment timer for transparent and unackowledged mode bearers is set to 0 indicating that re-establishment should not be attempted • T315 = 0 s: the re-establishment timer for ackowledged mode bearers is set to 0 indicating that re-establishment should not be attempted • Idle mode timers and constants: • T300 = 2 s, N300 = 3: after transmitting an RRC Connection Request message wait 2 s before re-transmitting the message. Send a maximum of 3 + 1 = 4 RRC Connection Request messages • T312 = 5 s, N312 = 4: when initiating a DCH L3 of the UE must obtain 4 in-sync indicators from L1 within 5 s or the physical channel establishment will be reported as a failure • Note that the extension fields overide the first IEs ue-ConnTimersAndConstants { t-312 4, n-312 s50, t-314 s0, t-315 s0 }, ue-IdleTimersAndConstants { t-300 ms2000, n-300 3, t-312 5, n-312 s50 }, v3a0NonCriticalExtensions { sysInfoType1-v3a0ext { ue-ConnTimersAndConstants-v3a0ext { n-312 s4 }, ue-IdleTimersAndConstants-v3a0ext { n-312 s4 } } }

  20. SIB 2 The list of URA to which the cell belongs is specified A maximum of 8 URA can be specified The first URA in the list is the master URA The master URA is adopted by the UE upon cell selection In this case the cell has been assigned only a single URA i.e. 00 00 00 01 01 01 10 00 = 344 SysInfoType2 : { ura-IdentityList { '0000000101011000'B }

  21. SIB 3 SIB 4 is not broadcast in the cell The Cell ID is unambiguously defined within the PLMN (RNC ID is 12 bits and Cid is 16 bits, Cid is unique within an RNC (24.008 specifies within a LA)) The cell selection and re-selection measurement quantity is specified to be CPICH Ec/Io The cell re-selection CPICH Ec/Io hysteresis is defined to be 4 dB (actual value is 2 x IE value) The cell re-selection CPICH RSCP hysteresis is defined to be 4 dB (actual value is 2 x IE value Cell selection Qqualmin is -20 dB Cell selection Qrxlevmin is -115 dB. (actual value is 2 x IE value + 1) The re-selection time is 0 s (in the case of 0 s TS 25.133 specifies that the UE should be capable of evaluating that a neighboring cell has out ranked the serving cell once its CPICH Ec/Io is at least 3 dB better than that of the serving cell – smaller differences may not be detectable without a greater averaging period) The maximum allowed UE transmit power is 21 dBm The cell is not barred for any access class nor is it reserved for operator use nor is it reserved for future extension The UE access class is stored in its SIM (0 – 15) SysInfoType3 : { sib4indicator FALSE, cellIdentity '0000000001101110101001010101'B, cellSelectReselectInfo { cellSelectQualityMeasure cpich-Ec-N0 : { q-HYST-2-S 2 }, modeSpecificInfo fdd : { q-QualMin -20, q-RxlevMin -58 }, q-Hyst-l-S 2, t-Reselection-S 0, maxAllowedUL-TX-Power 21 }, cellAccessRestriction { cellBarred notBarred : NULL, cellReservedForOperatorUse notReserved, cellReservationExtension notReserved, accessClassBarredList { notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred, notBarred } }

  22. SIB 5 (I) SysInfoType5 : { sib6indicator FALSE, pich-PowerOffset -8, modeSpecificInfo fdd : { aich-PowerOffset -8 }, primaryCCPCH-Info fdd : { tx-DiversityIndicator FALSE }, prach-SystemInformationList { { prach-RACH-Info { modeSpecificInfo fdd : { availableSignatures { signature3, signature2, signature1, signature0 }, availableSF sfpr32, preambleScramblingCodeWordNumber 0, puncturingLimit pl1, availableSubChannelNumbers { subCh11, subCh10, subCh9, subCh8, subCh7, subCh6, subCh5, subCh4, subCh3, subCh2, subCh1, subCh0 } } }, SIB 6 is not broadcast in the cell The PICH is transmitted with a power 8 dB less than that of the CPICH The AICH is transmitted with a power 8 dB less than that of the CPICH Transmit diversity is not used for the primary CCPCH PRACH signatures 0, 1, 2, 3 can be used within the cell (this represents 4 out of a possible 16) The PRACH spreading factor is 32 PRACH scrambling code 0 should be used (there are 16 PRACH scrambling codes associated with each primary scrambling code) The PRACH puncturing limit is 1 i.e. puncturing is not allowed PRACH sub-channels 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 can be used i.e. all sub-channels

  23. SIB 5 (II) • The RACH transport channel ID is 1 • Only one RACH can be mapped onto a PRACH • The RACH TTI is 20 ms • TF 1 (DCCH, CCCH): • The TB size = (15 x 8) + 48 = 168 bits • The TBS size = 1 • The RACH L2 PDU bit rate is thus 168 / 0.02 = 8.4 kbps • TF 2 (DTCH): • The TB size = (3 x 16) + 312 = 360 bits • The TBS size = 1 • The RACH L2 PDU bit rate is thus 360 / 0.02 = 18 kbps • Half rate convolution coding should be used on the RACH • A rate matching attribute of 1 should be applied • A 16 bit CRC should be attached transportChannelIdentity 1, rach-TransportFormatSet commonTransChTFS : { tti tti20 : { { rlc-Size fdd : { octetModeRLC-SizeInfoType2 sizeType1 : 15 }, numberOfTbSizeList { one : NULL }, logicalChannelList configured : NULL }, { rlc-Size fdd : { octetModeRLC-SizeInfoType2 sizeType2 : 3 }, numberOfTbSizeList { one : NULL }, logicalChannelList configured : NULL } }, semistaticTF-Information { channelCodingType convolutional : half, rateMatchingAttribute 1, crc-Size crc16 } }, 3GPP specifies that the TB size for: • Type2 sizeType1 = (IE x 8) + 48 bits • Type2 sizeType2 = (IE x 16) + 312 bits

  24. SIB 5 (III) The calculated transport format combination (ctfc) is conveyed using 2 bits There is only a single transport channel configured with two possible bit rates rach-TFCS normalTFCI-Signalling : complete : { ctfcSize ctfc2Bit : { { ctfc2 0, powerOffsetInformation { gainFactorInformation signalledGainFactors : { modeSpecificInfo fdd : { gainFactorBetaC 12 }, gainFactorBetaD 15 }, powerOffsetPp-m 2 } }, { ctfc2 1, powerOffsetInformation { gainFactorInformation signalledGainFactors : { modeSpecificInfo fdd : { gainFactorBetaC 11 }, gainFactorBetaD 15 }, powerOffsetPp-m 2 } } } }, TFS RACH transport channel 18 kbps (DTCH) 8.4 kbps (DCCH or CCCH) • The gain factors for the 8.4 kbps TF are: • DPDCH = 15 • DPCCH = 12 • Power offset between last preamble and message part = 2 dB • The gain factors for the 18 kbps TF are: • DPDCH = 15 • DPCCH = 11 • Power offset between last preamble and message part = 2 dB

  25. SIB 5 (IV) There is a single PRACH partition corresponding to an ASC = 0 i.e. all AC are mapped to an ASC of 0 The PRACH partition can use all four of the available signatures and all 15 of the available sub-channels prach-Partitioning fdd : { { accessServiceClass-FDD { availableSignatureStartIndex 0, availableSignatureEndIndex 3, assignedSubChannelNumber { b3, b2, b1, b0 } } } }, ac-To-ASC-MappingTable { 0, 0, 0, 0, 0, 0, 0 }, modeSpecificInfo fdd : { primaryCPICH-TX-Power 33, constantValue -25, prach-PowerOffset { powerRampStep 1, preambleRetransMax 7 }, rach-TransmissionParameters { mmax 16, nb01Min 0, nb01Max 50 }, aich-Info { channelisationCode256 2, sttd-Indicator FALSE, aich-TransmissionTiming e0 } } The CPICH transmit power in the cell is 33 dBm This matches the actual CPICH transmit power which indicates that an MHA has not been configured. If an MHA had been configured then this value would be decreased by an amount equal to the uplink/downlink link loss imbalance The PRACH C/I requirement to be used by the UE within the open loop power control is –25 dB The PRACH preamble step size = 1 dB The maximum number of PRACH preambles per preamble cycle is 7 The maximum number of PRACH preamble cycles is 16 The lower bound for random backoff is 0 frames whereas the upper bound is 50 frames The AICH uses Cch,256,2 The AICH does not use space time transmit diversity The AICH timing is set to 0 i.e. the UE expects to find the AICH in the first access slot after the used PRACH access slot

  26. SIB 5 (V) sCCPCH-SystemInformationList { { secondaryCCPCH-Info { modeSpecificInfo fdd : { dummy1 mayBeUsed, sttd-Indicator FALSE, sf-AndCodeNumber sf64 : 1, pilotSymbolExistence FALSE, tfci-Existence TRUE, positionFixedOrFlexible flexible, timingOffset 30 } }, tfcs normalTFCI-Signalling : complete : { ctfcSize ctfc4Bit : { { ctfc4 0 }, { ctfc4 1 }, { ctfc4 2 }, { ctfc4 3 }, { ctfc4 4 }, { ctfc4 6 } } }, The IE ‘dummy1’ is not used in this version of the specification and can be ignored Space time transmit diversity is not used for the secondary CCPCH The secondary CCPCH uses uses Cch,64,1 The secondary CCPCH does not include any pilot bits The secondary CCPCH includes TFCI bits Flexible position of transport channels may be applied to the secondary CCPCH The delay of the secondary CCPCH relative to the primary CCPCH is 7680 chips (actual value = IE x 256) See later slide for the derivation of the ctfc figures

  27. SIB 5 (VI) fach-PCH-InformationList { { transportFormatSet commonTransChTFS : { tti tti10 : { { rlc-Size fdd : { octetModeRLC-SizeInfoType2 sizeType1 : 4 }, numberOfTbSizeList { zero : NULL, one : NULL }, logicalChannelList allSizes : NULL } }, semistaticTF-Information { channelCodingType convolutional : half, rateMatchingAttribute 210, crc-Size crc16 } }, transportChannelIdentity 5, ctch-Indicator FALSE }, { • The PCH transport channel uses a TTI of 10 ms • TFS 1 (PCH carrying PCCH): • The TB size = (4 x 8) + 48 = 80 bits • The TBS size = 0, 1 • The FACH L2 PDU bit rate is thus: • 0 / 0.01 = 0 kbps • 80 / 0.01 = 8 kbps • Half rate convolutional coding should be applied • A rate matching attribute of 210 should be applied • A 16 bit CRC should be attached • The transport channel identity is 5 • No common traffic channel is mapped to the FACH 3GPP specifies that the TB size for: • Type2 sizeType1 = (IE x 8) + 48 bits

  28. SIB 5 (VII) • This FACH transport channel uses a TTI of 10 ms • TFS 2 (FACH carrying DCCH, CCCH or BCCH): • The TB size = (15 x 8) + 48 = 168 bits • The TBS size = 0, 1, 2 • The FACH L2 PDU bit rate is thus: • 0 / 0.01 = 0 kbps • 168 / 0.01 = 16.8 kbps • 336 / 0.01 = 33.6 kbps • Half rate convolutional coding should be applied • A rate matching attribute of 200 should be applied • A 16 bit CRC should be attached • The transport channel identity is 7 • No common traffic channel is mapped to the FACH transportFormatSet commonTransChTFS : { tti tti10 : { { rlc-Size fdd : { octetModeRLC-SizeInfoType2 sizeType1 : 15 }, numberOfTbSizeList { zero : NULL, one : NULL, small : 2 }, logicalChannelList allSizes : NULL } }, semistaticTF-Information { channelCodingType convolutional : half, rateMatchingAttribute 200, crc-Size crc16 } }, transportChannelIdentity 7, ctch-Indicator FALSE }, { 3GPP specifies that the TB size for: • Type2 sizeType1 = (IE x 8) + 48 bits

  29. SIB 5 (VIII) • This FACH transport channels use a TTI of 10 ms • TFS 3 (FACH carrying DTCH): • The TB size = (3 x16) + 312 = 360 bits • The TBS size = 0, 1 • The FACH L2 PDU bit rate is thus: • 0 / 0.01 = 0 kbps • 360 / 0.01 = 36 kbps • Third rate turbo coding should be applied • A rate matching attribute of 110 should be applied • A 16 bit CRC should be attached • The transport channel identity is 10 • No common traffic channel is mapped to the FACH • The PICH uses Cch,256,3 • There are 72 paging indicators per radio frame • The PICH does not use space time transmit diversity transportFormatSet commonTransChTFS : { tti tti10 : { { rlc-Size fdd : { octetModeRLC-SizeInfoType2 sizeType2 : 3 }, numberOfTbSizeList { zero : NULL, one : NULL }, logicalChannelList allSizes : NULL } }, semistaticTF-Information { channelCodingType turbo : NULL, rateMatchingAttribute 110, crc-Size crc16 } }, transportChannelIdentity 10, ctch-Indicator FALSE } }, pich-Info fdd : { channelisationCode256 3, pi-CountPerFrame e72, sttd-Indicator FALSE } } } 3GPP specifies that the TB size for: • Type2 sizeType2 = (IE x 16) + 312 bits

  30. S-CCPCH Calculated Transport Format Combinations (ctfc) Three transport format sets have been defined within SIB 5: TrCH 7 33.6 kbps 16.8 kbps TrCH 5 8 kbps TrCH 10 36 kbps CTCF = 0 + 0 + 0 = 0 CTCF = 1*1 + 0 + 0 = 1 L TFS1 L1=2 TFS2 L2=3 TFS3 L3=2 CTCF = 0 + 1*2 + 0 = 2 CTCF = 1*1 + 1*2 + 0 = 3 L0=1 P1=1 P2=2 P3=6 CTCF = 0 + 2*2 + 0 = 4 CTCF = 0 + 0 + 1*6 = 6

  31. SIB 7 The uplink RSSI as measured at the output of the receiver’s root raised cosine filter within the WTR is –106 dBm The PRACH dynamic persistance is defined as 1. This value is fed into the equation 2^-(N-1) = 2^0 = 1 SysInfoType7 : { modeSpecificInfo fdd : { ul-Interference -106 }, prach-Information-SIB5-List { 1 }

  32. SIB 11 (I) SIB 12 is not broadcast in the cell HCS is not used by the cell The cell selection and cell re-selection measurement quantity is CPICH Ec/Io The UE is instructed not to remove any of its existing intra-frequency neighbors. This IE is not relevant because the UE automatically clears any neighbor list when reading SIB11 IntraFreqCell ID 0 corresponds to the serving cell The serving cell has scrambling code 162 assigned The CPICH transmit power is set to 0 dBm. This value is only required within SIB 11 if the cell selection and cell re-selection measurement quantity is path loss (SIB 5 includes the serving cell CPICH transmit power) The UE is instructed to read the SFN of the cell Transmit diversity is not used by the cell SysInfoType11 : { sib12indicator FALSE, measurementControlSysInfo { use-of-HCS hcs-not-used : { cellSelectQualityMeasure cpich-Ec-N0 : { intraFreqMeasurementSysInfo { intraFreqCellInfoSI-List { removedIntraFreqCellList removeNoIntraFreqCells : NULL, newIntraFreqCellList { { intraFreqCellID 0, cellInfo { modeSpecificInfo fdd : { primaryCPICH-Info { primaryScramblingCode 162 }, primaryCPICH-TX-Power 0, readSFN-Indicator TRUE, tx-DiversityIndicator FALSE } } }, {

  33. SIB 11 (II) IntraFreqCell IDs which are non-zero correspond to neighboring cells In the case of neighboring cells the time difference between the serving cell P-CCPCH and the neighboring cell P-CCPCH is broadcast In this case the time difference is broadcast with a quantisation step of 40 chips The time difference is defined as 0 chips (if the IE value had been 1 then the actual value would have been 40 chips) The neighboring cell has scrambling code 166 assigned The CPICH transmit power is set to 0 dBm. This value is only required within SIB 11 if the cell selection and cell re-selection measurement quantity is path loss The UE is instructed to read the SFN of the cell Transmit diversity is not used by the cell The maximum allowed UE transmit power in the neighboring cell is 21 dBm Neighbor cell re-selection Qqualmin is -24 dB Neighbor cell re-selection Qrxlevmin is -115 dB. (actual value is 2 x IE value + 1) intraFreqCellID 1, cellInfo { referenceTimeDifferenceToCell accuracy40 : 0, modeSpecificInfo fdd : { primaryCPICH-Info { primaryScramblingCode 166 }, primaryCPICH-TX-Power 0, readSFN-Indicator TRUE, tx-DiversityIndicator FALSE }, cellSelectionReselectionInfo { maxAllowedUL-TX-Power 21, modeSpecificInfo fdd : { q-QualMin -24, q-RxlevMin -58 } } } }, { This structure is repeated for each and every neighbor

  34. SIB 11 (III) The L3 filter coefficient for handover evaluation is 3. The L3 filter coefficient is used as ‘k’ in the equations below intraFreqMeasQuantity { filterCoefficient fc3, modeSpecificInfo fdd : { intraFreqMeasQuantity-FDD cpich-Ec-N0 } }, intraFreqReportingQuantityForRACH { sfn-SFN-OTD-Type noReport, modeSpecificInfo fdd : { intraFreqRepQuantityRACH-FDD cpich-EcN0 } }, maxReportedCellsOnRACH currentCell, reportingInfoForCellDCH { intraFreqReportingQuantity { activeSetReportingQuantities { sfn-SFN-OTD-Type noReport, cellIdentity-reportingIndicator FALSE, cellSynchronisationInfoReportingIndicator TRUE, modeSpecificInfo fdd : { cpich-Ec-N0-reportingIndicator TRUE, cpich-RSCP-reportingIndicator FALSE, pathloss-reportingIndicator FALSE } }, monitoredSetReportingQuantities { sfn-SFN-OTD-Type noReport, cellIdentity-reportingIndicator FALSE, cellSynchronisationInfoReportingIndicator TRUE, modeSpecificInfo fdd : { cpich-Ec-N0-reportingIndicator TRUE, cpich-RSCP-reportingIndicator FALSE, pathloss-reportingIndicator FALSE } } }, • The intra-frequency measurement quantity for handover evaluation is CPICH Ec/Io • When events are triggered, no report is required for SFN to SFN time differences when transmitting on the RACH • When events are triggered, a report is required for the CPICH Ec/Io when using a RACH • Only the current cell should be reported when transmitting a report on the RACH • Active set measurements when using a DCH • When events are triggered, no report is required for SFN to SFN time differences nor cell identity nor CPICH RSCP nor path loss • When events are triggered, a report is required for the CPICH Ec/Io and synchronisation information • The same measurements are required for the monitored set measurements

  35. SIB 11(IV) Measurement reports should be sent using acknowledged mode RLC Reports should be event triggered rather than periodic Event 1a should be triggered by monitored set cells only i.e. not detected nor active set The addition window is 2.5 dB (actual value = IE value x 0.5) Weighting = 0 which means that the reporting range is defined by the best server alone and not the sum of cells within the active set Event 1a is only permitted while there are no more than 2 cells within the active set An infinite number of reports are allowed to be sent measurementReportingMode { measurementReportTransferMode acknowledgedModeRLC, periodicalOrEventTrigger eventTrigger }, reportCriteria intraFreqReportingCriteria : { eventCriteriaList { { event e1a : { triggeringCondition monitoredSetCellsOnly, reportingRange 5, w 0, reportDeactivationThreshold t2, reportingAmount ra-Infinity, reportingInterval ri0-5 }, hysteresis 0, timeToTrigger ttt100, reportingCellStatus allActiveplusMonitoredSet : viactCellsPlus2 }, { Reports are generated at an interval of 500 ms once they have been triggered Hysteresis for event 1a is set to 0 dB The time to trigger is 100 ms When reports are sent the UE can report measurements from the active set and monitored set The maximum number of cells that can be reported is equal to the active set size + 2

  36. SIB 11(V) Event 1b should only be triggered by active set cells i.e. not detected nor monitored set cells The drop window is 4 dB (actual value = IE value x 0.5) Weighting = 0 which means that the reporting range is defined by the best server alone and not the sum of cells within the active set Hysteresis for event 1b is set to 0 dB The time to trigger is 640 ms When reports are sent the UE can report measurements only from the active set A maximum of 3 active set cells can be reported event e1b : { triggeringCondition activeSetCellsOnly, reportingRange 8, w 0 }, hysteresis 0, timeToTrigger ttt640, reportingCellStatus withinActiveSet : e3 }, { event e1c : { replacementActivationThreshold t3, reportingAmount ra-Infinity, reportingInterval ri0-5 }, hysteresis 4, timeToTrigger ttt100, reportingCellStatus allActiveplusMonitoredSet : viactCellsPlus2 } Event 1c should be triggered only when there are 3 cells within the active set An infinite number of reports are allowed to be sent Reports are generated at an interval of 500 ms once they have been triggered Hysteresis for event 1c is set to 2 dB (actual value = IE value x 0.5). It should be noted that the equation used to evaluate event 1c further divides the hysteresis value by 2 resulting in a replacement window of 1 dB The time to trigger is 100 ms When reports are sent the UE can report measurements from the active set and monitored set The maximum number of cells that can be reported is equal to the active set size + 2

  37. SIB 18 SysInfoType18 : { idleModePLMNIdentities { plmnsOfIntraFreqCellsList { { }, { }, { }, { }, { }, { }, { }, { }, { } } } SIB 18 can define the PLMN identities of neighboring cells to be used idle mode SIB 18 can also define the PLMN identities of neighboring cells to be used connected mode

  38. Cell Selection (I) UE is powered up • Cell selection is standardised by 3GPP within TS 25.304 • Cell selection is based upon the S-criteria • UE extracts the S-criteria parameters from SIB 3 • QqualMin • QrxlevMin • UE_TXPWR_MAX_RACH • There is a mapping required to translate QrxLevMin to its actual value i.e. actual value = (Information Element value x 2) + 1 Cell search Radio frame synchronisation Read BCCH Cell selection SysInfoType3 : { sib4indicator FALSE, cellIdentity '0000000001101110100111010010'B, cellSelectReselectInfo { cellSelectQualityMeasure cpich-Ec-N0 : { q-HYST-2-S 2 }, modeSpecificInfo fdd : { q-QualMin -20, q-RxlevMin -58 }, q-Hyst-l-S 2, t-Reselection-S 0, maxAllowedUL-TX-Power 21 }, Register with core network Originating AMR speech call Handovers Release of AMR speech call

  39. Cell Selection (II) UE is powered up Both Squal and Srxlev must be positive for the UE to camp upon the cell Cell search Squal = Qqualmeas – QqualMin Srxlev = Qrxlevmeas –QrxlevMin– Pcompensation where, Pcompensation = Max(UE_TXPWR_MAX_RACH– P_MAX, 0) Default values:QqualMinis –20 dB CPICH Ec/Io QrxlevMin is –115 dBm CPICH RSCP UE_TXPWR_MAX_RACHis 21 dBm Radio frame synchronisation Read BCCH Cell selection Register with core network Originating AMR speech call Handovers Release of AMR speech call

  40. Register with the Core Network UE is powered up Cell search The UE registers with the CS core domain (the UE also registers with the PS core domain but this slide set concerns itself only with the CS domain) CS domain registering is an IMSI attach Registering is achieved by establishing an RRC connection and sending non-access stratum messages to the 3G MSC The non-access stratum message is encapsulated within a ‘Location Update Request’ message Radio frame synchronisation Read BCCH Cell selection Register with core network Originating AMR speech call Handovers Release of AMR speech call

  41. RRC Connection Request (I) If the cell from which the BCCH has been read is suitable to camp upon then the UE follows the instructions in SIB1 to complete an IMSI attach with the CS core network To complete an IMSI attach the UE must first establish an RRC connection The RRC Connection Request message is sent to the RNC using unacknowledged mode RLC on the RACH The message is sent via the Node B which uses Frame Protocol to encapsulate the transport blocks and send them across the Iub via AAL2 based ATM The transmit power of the first PRACH preamble is computed from a combination of the information read from SIB 5 and SIB 7 and measurements made by the UE i.e. transmit power of first preamble = CPICH transmit power (SIB 5) – CPICH RSCP (UE measured) + Uplink RSSI (SIB 7) + PRACH C/I requirement (SIB 5) Node B UE RNC RRC: RRC Connection Request (RACH)

  42. RRC Connection Request (II) • CCCH ->RACH -> PRACH • CCCH contains the RRC Connection Request message • Message is sent using unacknowledged mode RLC • The establishment cause is ‘registration’ • This message includes the UE identity in terms of the PTMSI and the RAI. The PTMSI is used when a TMSI is not available. In this case the RAI must be sent. If the TMSI is used then the LAI must be sent. The IMSI shall be used if neither the TMSI nor PTMSI is available • The message also includes the CPICH Ec/Io of the current cell • The CPICH Ec/Io can be extracted from the IE using: Ec/Io = -24 + IE / 2 • A value of 42 indicates, -3.5 dB <= Ec/Io < -3.0 dB UL-CCCH-Message : { message rrcConnectionRequest : { initialUE-Identity p-TMSI-and-RAI : { p-TMSI '00010011010001110001111101000010'B, rai { lai { plmn-Identity { mcc { 2, 3, 4 }, mnc { 2, 0 } }, lac '0000000001011110'B }, rac '01011110'B } }, establishmentCause registration, protocolErrorIndicator noError, measuredResultsOnRACH { currentCell { modeSpecificInfo fdd : { measurementQuantity cpich-Ec-N0 : 42 } } } }

  43. RRC Connection Request across the Iub (I) The Iub log of the RRC Connection request message is illustrated below The message consists of a single 168 bit transport block The message is sufficiently small to be fit within a single 20 ms RACH TTI The message is encapsulated by a RACH Frame Protocol frame The frame type bit is 0 indicating that the frame includes data The TFI indicates that the 8.4 kbps TF is being used The connection frame number is 200 RACH Frame Protocol structure Header CRC FT Header CFN Spare TFI Propagation Delay Transport Block Transport Block Transport Block Transport Block Transport Block is 21 Octets in Total (168 bits => 8.4 kbps) Payload Transport Block ATM Conn:1 VPI:44 VCI:46 CID:8 Line:1 27563952 11:26:42.530302 AAL2 UUI: 26 (1Ah) SSSAR-PDU 3C C8 00 07 0C 8A 61 C9 95 08 D0 40 00 C0 C0 00 62 00 00 00 00 00 00 00 00 00 D9 8C RACH DATA FRAME Header CRC : 30 (1E) Conn. Frame number : 200 (C8) Transport Format Ind : 0 (0) dynamic part = {1 blocks, 168 bits/block} FDD - Propagation Delay : 21 (15) chips Transport Blocks 1. Transport Block 0C 8A 61 C9 95 08 D0 40 00 C0 C0 00 62 00 00 00 00 00 00 00 00 CRC Indicators: 00 Spare Extension Payload CRC : 55692 (D98C) CCCH mapped to RACH/FACH - TCTF: CCCH - MAC SDU 32 29 87 26 54 23 41 00 03 03 00 01 88 00 00 00 00 00 00 00 00 TRANSPARENT MODE DATA PDU - Data : 32 29 87 26 54 23 41 00 03 03 00 01 88 00 00 00 00 00 00 00 00 RRC CONNECTION REQUEST Transport Block Transport Block Transport Block Pad CRCI Payload CRC Payload CRC Frame Protocol data frame is 28 octets in total length The one way propagation delay has been measured by the Node B as 21 chips (resolution is 3 chips) The CRC indicator is 0 indicating no errrors after decoding

  44. RRC Connection Request across the Iub (II) • The transport network control plane has already assigned the VCI and CID for the user plane RACH transport channel (assigned upon Node B reset) • In this case the assigned ATM connection is defined by: • VPI = 44 • VCI = 46 • CID = 8 • This ATM connection originates in the Node B WAM and terminates in the RNC ATM Conn:1 VPI:44 VCI:46 CID:8 Line:1 27563952 11:26:42.530302 AAL2 UUI: 26 (1Ah) SSSAR-PDU 3C C8 00 07 0C 8A 61 C9 95 08 D0 40 00 C0 C0 00 62 00 00 00 00 00 00 00 00 00 D9 8C RACH DATA FRAME Header CRC : 30 (1E) Conn. Frame number : 200 (C8) Transport Format Ind : 0 (0) dynamic part = {1 blocks, 168 bits/block} FDD - Propagation Delay : 21 (15) chips Transport Blocks 1. Transport Block 0C 8A 61 C9 95 08 D0 40 00 C0 C0 00 62 00 00 00 00 00 00 00 00 CRC Indicators: 00 Spare Extension Payload CRC : 55692 (D98C) CCCH mapped to RACH/FACH - TCTF: CCCH - MAC SDU 32 29 87 26 54 23 41 00 03 03 00 01 88 00 00 00 00 00 00 00 00 TRANSPARENT MODE DATA PDU - Data : 32 29 87 26 54 23 41 00 03 03 00 01 88 00 00 00 00 00 00 00 00 RRC CONNECTION REQUEST The RRC Connection Request message is sent using transparent mode RLC and so does not include an RLC header The MAC header only includes the Target Channel Type Field (TCTF) which has a length of 2 bits: 00 to indicate that the logical channel type is CCCH MAC PDU TCTF MAC SDU 2 bits 166 bits

  45. NBAP: Radio Link Setup Request (I) • Once the RNC has received the RRC Connection Request message it sends a Common NBAP: Radio Link Setup Request to the Node B • The Common NBAP: Radio Link Setup Request includes uplink and downlink configuration data for the radio link that the Node B is being requested to support • The radio link refers only to the communication link between the Node B and UE. It does not include Iub communication • The Common NBAP: Radio Link Setup Request is sent using AAL5 based ATM within the radio network control plane belonging to the Iub protocol stack • The transport network control plane has already assigned the VCI for common NBAP (assigned upon Node B reset) • In this case the assigned ATM connection is defined by: • VPI = 44 • VCI = 33 • CID = not applicable to AAL5 • This ATM connection originates in the RNC and terminates in the Node B WAM UE Node B RNC RRC: RRC Connection Request (RACH) NBAP: Radio Link Setup Request

  46. NBAP: Radio Link Setup Request (II) The message discriminator indicates that the message is a common message rather than a dedicated message The controlling RNC communication context: 6979, is used to identify messages related to a specific UE ATM Conn:5 VPI:44 VCI:33 CID:0 Line:1 27337041 11:03:23.128457 AAL5 CPCS-PDU 00 09 20 6F 00 00 06 00 2B 00 03 40 1B 43 00 2E 00 01 00 00 92 00 0B 04 0F 59 83 C7 00 01 00 04 00 7E 00 37 00 09 00 00 01 00 04 B4 43 10 60 00 2F 00 22 00 40 00 0F 00 05 00 18 02 00 00 00 40 00 01 00 94 40 A0 00 40 08 00 00 40 00 01 00 94 40 A0 00 43 80 00 6E 00 1A 00 00 01 00 64 00 13 40 80 21 60 00 06 0E 00 03 08 00 00 04 00 F9 01 53 00 BD 00 48 00 00 5D SD PDU INFO 00 09 20 6F 00 00 06 00 2B 00 03 40 1B 43 00 2E 00 01 00 00 92 00 0B 04 0F 59 83 C7 00 01 00 04 00 7E 00 37 00 09 00 00 01 00 04 B4 43 10 60 00 2F 00 22 00 40 00 0F 00 05 00 18 02 00 00 00 40 00 01 00 94 40 A0 00 40 08 00 00 40 00 01 00 94 40 A0 00 43 80 00 6E 00 1A 00 00 01 00 64 00 13 40 80 21 60 00 06 0E 00 03 08 00 00 04 00 F9 01 53 00 BD PL : 1 (000001h) N(S) : 93 (00005Dh) RADIO LINK SETUP REQUEST NBAP-PDU initiatingMessage - procedureCode: 9 - criticality: reject - messageDiscriminator: common initiatingMessage RadioLinkSetupRequest protocolIEs - id: 43 - criticality: reject CRNC-CommunicationContextID: 6979 - id: 46 - criticality: reject DCH-FP-VersionNumber: 1 - id: 146 - criticality: reject

  47. NBAP: Radio Link Setup Request (III) The uplink scrambling code is specified. This scrambling code will also be told to the UE within the RRC Connection Setup message The uplink scrambling code type is indicated as being a long scrambling code (also told to the UE) The uplink channelisation code is specified to have a minimum length of 64. 3GPP specifiy that the channelisation code number used is given by SF/4 i.e. Cch,64,16 is used The uplink puncturing limit is specified as 0.68 (actual value = IE*0.04 + 0.40) The uplink ctfc are specified as 0 and 1 (see the subsequent description of the RRC Connection Setup message for a full explanation of these) The uplink DPCCH slot format is specified as being 0. This results in 6 pilot bits, 2 TPC bits and 2 TFCI bits per slot The uplink SIR target is defined as 11 dB (actual value = -11 + IE value / 2) The downlink ctfc are specified as 0 and 1 (see the description of the RRC Connection Setup message) The downlink DPCH slot format is specified as being 11 with flexible positions. This results in 8 pilot bits, 2 TPC bits and 2 TFCI bits per slot UL-DPCH-Information-RL-SetupReq ul-scramblingCode - ul-ScramblingCodeNumber: 1001170 - ul-ScramblingCodeLength: long - minUL-ChannelisationCodeLength: len64 - punctureLimit: 7 tFCS cTFC - ctfc2bit: 0 cTFC - ctfc2bit: 1 ul-DPCCH-SlotFormat - non-extended: 0 - ul-SIR-Target: 44 - id: 55 - criticality: reject DL-DPCH-Information-RL-SetupReq tFCS cTFC - ctfc2bit: 0 cTFC - ctfc2bit: 1 dL-DPCH-SlotFormat - non-extended: 11 - multiplexingPosition: flexible-positions powerOffsetInformation - pO1: 8 - pO2: 12 - pO3: 8 - tPC-DL-StepSize: one - limitedPowerInc: not-used - id: 47 - criticality: reject • The downlink DPCCH power offsets are specified as: • Pilot PO1 = 2 dB, TPC = 3 dB and TFCI = 2 dB (actual value = IE value / 4) • The inner loop power control step size is 1 dB and the limited power increase feature is not used

  48. NBAP: Radio Link Setup Request (IV) The frame protocol 16 bit CRC field is to be included The ‘silent’ uplink frame protocol mode is to be used. The Iub time of arrival window startpoint (toAWS) is 15 ms. Downlink data frames are expected to arrive after this time. The downlink Iub time of arrival window endpoint (toAWE) is 5 ms prior to the LTOA. Downlink frames are expected to arrive before this time. Data frames arriving after this time trigger a Timing Adjustment control frame. The LTOA is a Node B internal parameter depending upon the Node B processing time The DCH transport channel being configured has an ID = 24 The downlink transport format set is defined by being able to transmit 0 or 1 transport blocks of size 148 bits The downlink TTI is 10 ms and rate 1/3 convolutional coding is used with a rate matching attribute of 1 and a 16 CRC The uplink transport format set is defined by being able to transmit 0 or 1 transport blocks of size 148 bits The uplink TTI is 10 ms and rate 1/3 convolutional coding is used with a rate matching attribute of 1 and a 16 CRC The frame handling priority has been assigned 14 (range of 0 to 15 where 15 represents the highest priority The Node B is instructed to take the frame protocol quality estimate from the DCH DCH-Information-RL-SetupReq DCH-List-Item-RL-SetupReq - payloadCRC-PresenceIndicator: crc-included - ul-FP-Mode: silent - toAWS: 15 - toAWE: 5 dCH-Specific-Info DCH-Specific-Info-Item-RL-SetupReq - dCH-ID: 24 dL-TransportFormatSet dynamicTransportFormatInfo - nrOfTransportBlocks: 0 - nrOfTransportBlocks: 1 - transportBlockSize: 148 semiStaticTransportFormatInfo - transmissionTimeInterval: msec-10 - channelCodingType: convolutional - codingRate: third - rateMatchingAttribute: 1 cRC-Size - non-extended: 16 ul-TransportFormatSet dynamicTransportFormatInfo - nrOfTransportBlocks: 0 - nrOfTransportBlocks: 1 - transportBlockSize: 148 semiStaticTransportFormatInfo - transmissionTimeInterval: msec-10 - channelCodingType: convolutional - codingRate: third - rateMatchingAttribute: 1 cRC-Size - non-extended: 16 - frameHandlingPriority: 14 - qE-Selector: selected-DCH - id: 110 - criticality: reject

  49. NBAP: Radio Link Setup Request (V) RadioLinkInformationList-RL-SetupReq - id: 100 - criticality: reject RadioLinkInformationItem-RL-SetupReq - rL-ID: 1 - c-ID: 8544 - first-RLS-Ind: first-RLS - frameOffset: 3 - chipOffset: 13312 - propagationDelay: 7 dL-ChannelisationCodeInformation-RL-SetupReq DL-ChannelisationCodeInformationItem-RL-SetupReq - dL-ScramblingCode: 0 - dL-ChannelisationCodeNumber: 4 - dL-TransmissionPower: -101 - maxDL-Power: -11 - minDL-Power: -161 The radio link ID is 1 The cell ID is specified to be ID = 8544 The Node B is informed that this radio link is the first radio link to be configured for this UE The frame offset is defined to be 6 frames and the chip offset to be 3584 chips (frame offset is selected at random by the RRM from the range 0-7, chip offset is selected at random by the RRM from the range 0-38399 with a resolution of 512) The propagation delay from the UE to the Node B is specified to be 21 chips (actual value = IE*3). This is equal to the value that the Node B measured from reception of the PRACH RRC Connection Request message The Node B is instructed to use the primary scrambling code when transmitting to the UE (IE can have a value of 0 to 15 corresponding to the primary scrambling code and 15 secondary scrambling codes Channelisation code number 4 is to be used for the downlink. The spreading factor has already been defined by the downlink slot format of 11 i.e. the downlink spreading factor is 128 The initial downlink transmit power is –10.1 dBm (actual value = IE/10) The maximum downlink transmit power is –1.1 dBm (actual value = IE/10) The minimum downlink transmit power is –16.1 dBm (actual value = IE/10)

  50. NBAP: Radio Link Setup Response (I) • The Node B acknowledges the Common NBAP: Radio Link Setup Request message with a Common NBAP: Radio Link Setup Response message • The Common NBAP: Radio Link Setup Response is sent using AAL5 based ATM within the radio network control plane belonging to the Iub protocol stack • The transport network control plane has already assigned the VCI for common NBAP (assigned upon Node B reset) • In this case the assigned ATM connection is defined by: • VPI = 44 • VCI = 33 • CID = not applicable to AAL5 • This ATM connection originates in the Node B WAM and terminates in the RNC Node B UE RNC RRC: RRC Connection Request (RACH) NBAP: Radio Link Setup Request NBAP: Radio Link Setup Response

More Related