CS122業(yè)務(wù)流程及常見問題分析

1、CS12.2調(diào)試，CS12.2業(yè)務(wù)流程及常見問題分析以主叫起呼并掛機(jī)為例，說明CS AMR 12.2K的整個(gè)信令過程。為清晰起見，將整個(gè)信令流程分割為以下幾個(gè)獨(dú)立階段進(jìn)行描述。在每個(gè)階段中，再進(jìn)行流程介紹，關(guān)鍵技術(shù)點(diǎn)分析，重要信令參數(shù)說明以及常見問題解答。出現(xiàn)問題的首要標(biāo)準(zhǔn)排查方法：u 首先比對標(biāo)準(zhǔn)信令過程，看看從哪一條信令開始和標(biāo)準(zhǔn)信令過程不吻合，查找實(shí)現(xiàn)流程不吻合的原因；u 排除流程原因后，查看是那一條信令出現(xiàn)異常。從異常信令的位置開始往前，逐條檢查每條信令內(nèi)容，和標(biāo)準(zhǔn)信令配置參數(shù)比對。如果參數(shù)不一樣，則先逐個(gè)排除參數(shù)，將參數(shù)調(diào)整為一致，看看是否參數(shù)原因?qū)е碌漠惓 如果全部排除參數(shù)和流程

2、的原因后，就需要從該流程原理以及代碼實(shí)現(xiàn)上來排查問題，以及當(dāng)UE，NODEB，CN返回失敗時(shí)，需要請這些設(shè)備的相關(guān)人員一起定位問題。對于基本流程而言，由于功能較穩(wěn)定，主要是排查參數(shù)配置和流程方面的原因。另外，呼叫過程信令處理的核心模塊是位于RCP上的UCPMC模塊。關(guān)聯(lián)的主要模塊會(huì)涉及到處理Iu口的SCPM，處理Iub口的RLMM，處理Iur口的RNSAP，以及一些外圍模塊如RPM，這些模塊都位于RCP上，所以更多的故障信息可以觀察RCP上的LOG來獲得。在本文的常見問題解答中會(huì)涉及到通過相關(guān)模塊的LOG信息來定位問題。在重要信令參數(shù)說明內(nèi)容中，考慮到各個(gè)消息逐個(gè)說明，內(nèi)容實(shí)在太大，而Iub口

3、消息和Uu口消息配置內(nèi)容大部分類似，在格式上略有不同。所以將以Uu口消息為主來說明。NAS消息內(nèi)容主要是UE和CN交互的，和2G相比差別不大，在本文就不做額外說明了。在本文中， UE指的是帶有NET MONITOR的NOKIA UE或者帶TRACE的高通UE。可能會(huì)通過UE的輔助功能來觀察某些現(xiàn)象定位問題。1. 第一階段：RRC 建立過程1.1. 信令流程介紹RRC連接的建立是UE和UTRAN建立信令交互的第一步。u UE在RACH上上報(bào)RRC連接建立請求u RNC依據(jù)后臺(tái)設(shè)置，決定將RRC連接建立在DCH上u RNC先在Iub口建立RL（radio link），RL建立成功后，Iub口對應(yīng)的

4、FP層進(jìn)行傳輸同步過程，隨后NODEB上報(bào)RL恢復(fù)指示（radio link restoreindication），表明RL可用了u RNC在FACH下發(fā)RRC連接建立消息，通知UE進(jìn)行RRC連接建立，相關(guān)RRC連接的配置消息也在該消息中攜帶給UEu UE建立RRC連接成功后，在DCH上回復(fù)成功的RRC建立響應(yīng)消息。1.2. 關(guān)鍵技術(shù)點(diǎn)接納在專用信道（DCH）上建立RRC連接，需要進(jìn)行接納判斷。接納判斷由無線資源模塊RRM中子模塊CAC完成。CAC判斷是否能夠接入到當(dāng)前小區(qū)，需要考慮當(dāng)前上報(bào)小區(qū)的負(fù)載情況，包括網(wǎng)絡(luò)擁塞情況和碼資源情況。當(dāng)擁塞過載或碼資源缺乏時(shí)，根據(jù)RRC建立請求消息中信元Me

5、asured results on RACH進(jìn)行小區(qū)選擇，選取新的小區(qū)進(jìn)行RRC連接建立，在新小區(qū)中建立CCIU、無線鏈路等，并在RRC連接建立消息中將新小區(qū)通知給UE。如果連新小區(qū)都負(fù)荷較高，無法接納，那么拒絕UE的接入。RRC建立傳輸信道選擇后臺(tái)有對應(yīng)選擇的控制項(xiàng)目，在RNC一級的參數(shù)中，取值有u “強(qiáng)制DCH”，使用3.4kbps普通信令，初始接入建立在CELL_DCH狀態(tài)，所以需要建立Iub口無線鏈路（radio link），如上面的SDL圖所示u “強(qiáng)制FACH”，使用3.4kbps普通信令，初始接入建立在CELL_FACH狀態(tài)，無需在Iub口建立無線鏈路u “不強(qiáng)制”，使用RNC本

6、身的控制策略，目前是使用3.4kbps普通信令，根據(jù)RRC建立的原因值來決定建立在CELL_DCH狀態(tài)還是CELL_FACH狀態(tài)。對于后續(xù)沒有業(yè)務(wù)流程的，如注冊等，建立在CELL_FACH狀態(tài)；對于后續(xù)有業(yè)務(wù)流程的，如主叫被叫等，建立在CELL_DCH狀態(tài)。默認(rèn)配置中，選擇的是第一種“強(qiáng)制DCH”。另外，后續(xù)的版本將加上13.6K相關(guān)高速信令的選擇UE能力信息UE的能力信息即可通過RRC建立后發(fā)起UE能力查詢過程獲得，也可在RRC建立時(shí)從消息RRC Connection Setup Complete獲得。目前實(shí)現(xiàn)的流程是后者，在RRC建立時(shí)從消息RRC Connection Setup Com

7、plete獲得。后續(xù)RNC進(jìn)行無線資源管理和安全模式控制過程，以及物理層傳輸層參數(shù)計(jì)算等都需要具備UE的能力信息信令無線承載RRC連接建立過程創(chuàng)建由RB#1- RB#4所指定的信令無線承載SRB：RB#1 用于所有在DCCH和RLC-UM上發(fā)送的信息；RB#2 用于除了直接傳送消息之外的所有在DCCH和RLC-AM上發(fā)送的信息；RB#3 用于傳送高層信令的直接傳送消息（使用DCCH和RLC-AM）。RB#4 實(shí)際上是沒有用的，原則上是用于傳送高層信令的直接傳送消息（使用DCCH和RLC-AM）。利用兩個(gè)傳送高層信令的SRB，UTRAN就可以處理信令上的優(yōu)先級，RB#4用于低優(yōu)先級的NAS信令，

8、RB#3用于高優(yōu)先級的NAS信令。RLMM模塊涉及的標(biāo)識與對應(yīng)關(guān)系NBAP專用消息中涉及了如下幾種ID，根據(jù)其體現(xiàn)的對應(yīng)關(guān)系，RLMM模塊需要利用這些ID組織管理實(shí)例、處理流程以及專用資源。l CRNC Communication Context ID CRNC通信上下文（Communication Context）可以理解為UE在CRNC的一個(gè)映象，在RNC上統(tǒng)一分配，代表了特定UE在CRNC上占用的全部資源的集合，同UE間存在一一對應(yīng)的關(guān)系。鑒于目前RLMM模塊的實(shí)現(xiàn)考慮，RLMM模塊的實(shí)例RLMI實(shí)際上也同UE存在這樣一個(gè)對應(yīng)關(guān)系，所以NBAP消息中涉及到的CRNC CC ID均可同具體

9、實(shí)例直接掛鉤。l Communication Control Port IDCCP ID用于標(biāo)識某個(gè)具體Node B同RNC間的信令承載，由Node B分配并在該Node B唯一。由于CCP相對于NBCC或者CRNCCC是個(gè)宏觀的概念，基本不存在直接的對應(yīng)關(guān)系，所以在目前RLMM模塊的實(shí)現(xiàn)中，可能會(huì)考慮將CCP的概念淡化。對于大多數(shù)專用流程或消息，無論是Node B還是RNC對CCP都是不關(guān)心的。目前RLMM模塊需要考慮CCP ID的情況：專用測量流程：如果發(fā)起的專用測量在指定NBCC時(shí)使用了保留值A(chǔ)ll NBCC，則該測量是對CCP范圍內(nèi)生效的；復(fù)位流程：如果Node B發(fā)起了面向某個(gè)（些）

10、CCP的復(fù)位過程或者RNC需要發(fā)起面向某個(gè)（些）CCP的復(fù)位過程。具體的解決辦法將在下文詳述。l Node B Communication Context IDNB CC的概念同CRNC CC相仿，由Node B進(jìn)行統(tǒng)一分配。但是由于UE本身是可以在多個(gè)Node B上存在這樣一個(gè)上下文的，所以對于RLMI而言可能同多個(gè)NBCC相對應(yīng)，這些NBCC ID本身的值可能相同。Node B將根據(jù)NBCC ID對UE進(jìn)行區(qū)分。所以RNC側(cè)應(yīng)當(dāng)維護(hù)這樣一個(gè)一對多的對應(yīng)關(guān)系，即當(dāng)前CRNC CC所對應(yīng)的UE在某個(gè)Node B上對應(yīng)的NBCC ID，具體到RLMI，則是每個(gè)RLMI應(yīng)當(dāng)維護(hù)該UE對應(yīng)的Node

11、 B列表及相應(yīng)的NBCC ID。l Transaction IDTransaction ID用于標(biāo)識流程。NBAP的專用消息涉及了多種流程，流程的發(fā)起方將分配一個(gè)唯一標(biāo)識用于確定具體流程，在流程結(jié)束之前，用Trasaction ID確定一條消息是否屬于本流程。對于Node B發(fā)起的消息，由Node B保證該Transaction ID在當(dāng)前NBCC內(nèi)全部Node B發(fā)起的流程中唯一；對于RNC發(fā)起的消息中，由RNC保證該Transaction ID在相應(yīng)NBCC內(nèi)全部RNC發(fā)起的流程中唯一。l Radio Link IDRadio Link ID對于一個(gè)特定UE能夠唯一標(biāo)識一條無線鏈路。RLM

12、I應(yīng)當(dāng)可以使用RL ID作為無線鏈路隊(duì)列的一個(gè)索引。l Radio Link Set IDRadio Link Set ID用于在一個(gè)NBCC的范圍內(nèi)唯一確定一個(gè)鏈路集。RLMM模塊不關(guān)心該信息體現(xiàn)的RL間關(guān)系l Measurement ID由于測量任務(wù)均由RNC下達(dá)，所以由RNC保證Measurement ID在一個(gè)CCP范圍內(nèi)的唯一性。RNC根據(jù)Measurement ID判斷測量上報(bào)消息、測量失敗消息對應(yīng)的測量任務(wù)。以上提到的幾種標(biāo)識均將作為某個(gè)NBCC的重要參數(shù)保存在該NBCC對應(yīng)的數(shù)據(jù)區(qū)內(nèi)，分別是RLMM模塊在進(jìn)行消息處理時(shí)的參考。1.3. 重要信令參數(shù)說明RRC CONNECTIO

13、N REQUESTRLC-SAP: TMLogical channel: CCCHDirection: UE UTRANInformation Element/Group nameNeedMultiType and referenceSemantics descriptionMessage TypeMPMessage TypeUE information elementsInitial UE identityMPInitial UE identity 10.3.3.15Establishment causeMPEstablishment cause 10.3.3.11Protocol erro

14、r indicatorMDProtocol error indicator 10.3.3.27Default value is FALSEMeasurement information elementsMeasured results on RACHOPMeasured results on RACH 10.3.7.451. UE標(biāo)識信息元素initial UE identity initial UE identity是在RRC連接建立時(shí)提供一個(gè)唯一的UE在空閑模式下的非接入層標(biāo)識。UCPM_C根據(jù)initial UE identity選擇SCCPCH（RLC根據(jù)SCCPCH獲取FACH信息）

15、。UE對非接入層標(biāo)識類型選擇原則為：（1）若UE中的變量SELECTED_CN值為GSM-MAP，UE根據(jù)下列優(yōu)先級在信息元素initial UE identity中選擇UE id type：1） TMSI（GSM-MAP）：TMSI若有效則選擇。當(dāng)使用TMSI時(shí)信息元素initial UE identity中應(yīng)包含信息元素LAI以保證其唯一性。2） P-TMSI（GAM-MAP）：若無有效的TMSI（GSM-MAP）且存在有效的P-TMSI（GSM-MAP），則選擇。當(dāng)使用P-TMSI時(shí)信息元素initial UE identity中應(yīng)包含信息元素RAI以保證其唯一性。3） IMSI（GSM

16、-MAP）：若無有效的TMSI及P-TMSI（GSM-MAP），且存在有效的IMSI（GSM-MAP），則選擇。4） IMEI：若上述條件均不滿足則選擇IMEI。在使用時(shí)信息元素TMSI(GSM-MAP)、P-TMSI（GAM-MAP）、IMSI（GSM-MAP），LAI和RAI應(yīng)設(shè)置為與USIM或SIM存貯的相應(yīng)標(biāo)識值相等。（2）若UE內(nèi)變量SELECTED_CN值為ANSI-41，UE應(yīng)根據(jù)3GPP2文檔3GPP2 C.P0004-A，選擇信息元素Initial UE identity中的UE id type。2. Establishment cause RRC建立原因，當(dāng)后臺(tái)選擇“不強(qiáng)制

17、”時(shí)，各類原因有對應(yīng)的RRC建立信道選擇趨向：1） Originating Conversational Call：專用物理信道2） Originating Streaming Call：專用物理信道3） Originating Interactive Call：專用物理信道4） Originating Background Call：專用物理信道5） Originating Subscribed traffic Call：專用物理信道6） Terminating Conversational Call：專用物理信道7） Terminating Streaming Call：專用物理信道8）

18、Terminating Interactive Call：專用物理信道9） Terminating Background Call：專用物理信道10） Emergency Call：專用物理信道11） Inter-RAT cell re-selection：專用物理信道12） Inter-RAT cell change order：專用物理信道13） Registration：公用物理信道14） Detach：專用物理信道15） Originating High Priority Signalling：專用物理信道16） Originating Low Priority Signalling：

19、公用物理信道17） Call re-establishment：專用物理信道18） Terminating High Priority Signalling：專用物理信道19） Terminating Low Priority Signalling：公用物理信道20） Terminating cause unknown3. Protocol error indicator 為一Boolean 值，TRUE表示有協(xié)議錯(cuò)誤發(fā)生；FALSE表示沒有協(xié)議錯(cuò)誤發(fā)生。缺省值為FALSE。UE在啟動(dòng)RRC建立過程時(shí)應(yīng)設(shè)置該變量為缺省值。4. Measured results on RACH UE測量報(bào)告，測

20、量報(bào)告內(nèi)容根據(jù)系統(tǒng)信息塊11中信息元素“頻率間測量RACH報(bào)告”、“RACH報(bào)告小區(qū)最大數(shù)目”決定。RRC_CONNECTION_SETUPRLC-SAP: UMLogical channel: CCCHDirection: UTRAN UEInformation Element/Group nameNeedMultiType and referenceSemantics descriptionMessage TypeMPMessage TypeUE Information ElementsInitial UE identityMPInitial UE identity 10.3.3.15RR

21、C transaction identifierMPRRC transaction identifier 10.3.3.36Activation timeMDActivation time 10.3.3.1Default value is nowNew U-RNTIMPU-RNTI 10.3.3.47New C-RNTIOPC-RNTI 10.3.3.8RRC State IndicatorMPRRC State Indicator 10.3.3.35aUTRAN DRX cycle length coefficientMPUTRAN DRX cycle length coefficient

22、10.3.3.49Capability update requirementMDCapability update requirement 10.3.3.2Default value is defined in subclause 10.3.3.2RB Information ElementsSignalling RB information to setup listMP3 to 4Signalling RB information to setupMPSignalling RB information to setup 10.3.4.24TrCH Information ElementsU

23、plink transport channelsUL Transport channel information common for all transport channelsOPUL Transport channel information common for all transport channels 10.3.5.24Added or Reconfigured TrCH information listMP1 to Although this IE is not required when the IE RRC state indicator is set to CELL_FA

24、CH, need is MP to align with ASN.1Added or Reconfigured UL TrCH informationMPAdded or Reconfigured UL TrCH information 10.3.5.2Downlink transport channelsDL Transport channel information common for all transport channelsOPDL Transport channel information common for all transport channels 10.3.5.6Add

25、ed or Reconfigured TrCH information listMP1 to Although this IE is not required when the IE RRC state indicator is set to CELL_FACH, need is MP to align with ASN.1Added or Reconfigured DL TrCH informationMPAdded or Reconfigured DL TrCH information10.3.5.1PhyCH information elementsFrequency infoMDFre

26、quency info 10.3.6.36Default value is the existing value of frequency informationUplink radio resourcesMaximum allowed UL TX powerMDMaximum allowed UL TX power 10.3.6.39Default value is the existing maximum UL TX powerCHOICE channel requirementOPUplink DPCH info Uplink DPCH info 10.3.6.88CPCH SET In

27、foCPCH SET Info 10.3.6.13Downlink radio resourcesDownlink information common for all radio linksOPDownlink information common for all radio links 10.3.6.24Downlink information per radio link listOP1 to Send downlink information for each radio link to be set-upDownlink information for each radio link

28、MPDownlink information for each radio link 10.3.6.271. RRC transaction identifier RRC連接事務(wù)號，標(biāo)識UTRAN相對特定UE唯一的一個(gè)RRC連接，為（0，3）間Integer值；2. Activation time 以CFN值表示的本操作生效frame number/時(shí)間，為（0，255）間Integer值；3. New U-RNTI 標(biāo)識UTRAN內(nèi)與當(dāng)前RRC連接對應(yīng)的UE，由SRNC identity 和S-RNTI組成，在整個(gè)PLMN中是唯一的，Serving RNC為每一個(gè)具有RRC連接的UE分配一個(gè)

29、SRNC identity。4. New C-RNTI 標(biāo)識UTRAN內(nèi)與當(dāng)前RRC連接對應(yīng)的UE所在小區(qū)，由控制RNC在創(chuàng)建一個(gè)新的UE上下文時(shí)分配，在當(dāng)前小區(qū)公共傳輸信道上通訊時(shí)使用，為UE在UTRAN連接模式下分配的一個(gè)無線網(wǎng)絡(luò)臨時(shí)標(biāo)識。5. UTRAN DRX cycle length coefficient UE對尋呼記數(shù)使用的非連續(xù)接收DRX周期長度。6. Capability update requirement 指示UE是否上報(bào)能力信息信元。 Information Element/Group nameNeedMultiType and referenceSemantics d

30、escriptionUE radio access FDD capability update requirementMPBooleanTRUE indicates update requiredSystem specific capability update requirement listOP1 to In this version, a maximum size of 4 for the list shall be applied and any items after the 4th item in the list shall be ignored.System specific

31、capability update requirementMPEnumerated (GSM) UE radio capability FDD update requirement 確省值為TRUE。7. Signalling RB information to setup 包含RB ID, RLCInfo，RB MappingInfo等，在實(shí)例數(shù)據(jù)區(qū)中直接獲取，UE應(yīng)按信元RB ID、RB MappingInfo替換以前存貯的無線承載復(fù)用選項(xiàng)；按信元RB ID、RLCInfo配置其無線承載的傳輸及接收RLC實(shí)體功能。RB ID為（0，4）間Integer值，RLCInfo定義上下行RLC模式

32、（AM, UM or TM）及相應(yīng)參數(shù)。UE根據(jù)RB MappingInfo初始化信令鏈路參數(shù)。（1）RLC Info 包含以下內(nèi)容；Information Element/Group nameNeedMultiType and referenceSemantics descriptionCHOICE Uplink RLC modeOPIndicates if Acknowledged, Unacknowledged or Transparent mode RLC shall be used. AM RLCTransmission RLC discardMPTransmission RLC d

33、iscard 10.3.4.25Transmission window sizeMPInteger(1,8,16,32,64,128,256,512,768,1024,1536,2047,2560,3072,3584,4095)Maximum number of RLC PUs sent without getting them acknowledged. This parameter is needed if acknowledged mode is used. UE shall also assume that the UTRAN receiver window is equal to t

34、his value.Timer_RSTMPInteger(50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 700, 800, 900, 1000)Elapsed time in milliseconds. It is used to trigger the retransmission of RESET PDU.Max_RSTMPInteger(1, 4, 6, 8, 12 16, 24, 32)Defined in 16Polling infoOPPolling info 10.3.4.4UM RLCTransmissio

35、n RLC discardOPTransmission RLC discard 10.3.4.25TM RLCTransmission RLC discardOPTransmission RLC discard 10.3.4.25Segmentation indicationMPBooleanTRUE indicates that segmentation is performed.CHOICE Downlink RLC modeOPIndicates if Acknowledged, Unacknowledged or Transparent mode RLC shall be usedAM

36、 RLCIn-sequence deliveryMPBooleanTRUE indicates that RLC shall preserve the order of higher layer PDUs when these are delivered.FALSE indicates that receiving RLC entity could allow SDUs to be delivered to the higher layer in different order than submitted to RLC sublayer at the transmitting side.Re

37、ceiving window size MPInteger(1,8,16,32,64,128,256,512,768,1024,1536,2047,2560,3072,3584,4095)Maximum number of RLC PUs allowed to be received. This parameter is needed if acknowledged mode is used. UE shall also assume that the UTRAN transmitter window is equal to this valueDownlink RLC status Info

38、MPDownlink RLC status info10.3.4.1UM RLC(No data)TM RLCSegmentation indicationMPBooleanTRUE indicates that segmentation is performed.l Transmission RLC discard 運(yùn)行定時(shí)器；l Transmission window size AM RLC模式下用于流量控制的接收窗口大小信元；l Timer_RST 重傳RESET PDU定時(shí)器，用于探測來自對等RLC實(shí)體的復(fù)位ACK PDU是否丟失；l Max_RST 復(fù)位PDU重新傳送次數(shù)的最大值。該

39、參數(shù)是計(jì)數(shù)器VT（RST）的上限。當(dāng)VT（RST）的值達(dá)到MaxRST 時(shí)，將通知高層RRC；l Polling info 確認(rèn)模式傳送時(shí)輪詢檢測信息，用來請求從接收者RLC得到狀態(tài)報(bào)告（確認(rèn)模式下接收者向發(fā)送者傳送狀態(tài)報(bào)告，每個(gè)狀態(tài)報(bào)告包含一個(gè)或多個(gè)狀態(tài)PDU，通知發(fā)送者哪個(gè)PU收到哪個(gè)PU沒有收到）；l In-sequence delivery RLC PDU按序投遞功能開關(guān)，即是否要求接收端按發(fā)送端的發(fā)送順序?qū)DU投遞給RRC層。（2）RB MappingInfo包含內(nèi)容： Information Element/Group nameNeedMultiType and referenc

40、eSemantics descriptionInformation for each multiplexing optionMP1 to RLC logical channel mapping indicatorCV-UL-RLCLogicalChannelsBooleanTRUE indicates that the first logical channel shall be used for data PDUs and the second logical channel shall be used for control PDUs.FALSE indicates that contro

41、l and data PDUs can be sent on either of the two logical channels.This parameter is not used in this release and shall be set to TRUE.Number of uplink RLC logical channelsCV-UL-RLC info1 to MaxLoCHperRLC1 or 2 logical channels per RLC entity or radio bearerRLC 16Uplink transport channel typeMPEnumer

42、ated(DCH,RACH,CPCH)CPCH is FDD onlyUL Transport channel identityCV-UL-DCHTransport channel identity 10.3.5.18This is the ID of a DCH that this RB could be mapped onto.Logical channel identityOPInteger(1.15)This parameter is used to distinguish logical channels multiplexed by MAC on a transport chann

43、el.CHOICE RLC size listMPThe RLC sizes that are allowed for this logical channelFor radio bearers mapped to RACH, Explicit list is the only valid choice. The UE shall regard all other choices as undefined IE values and handle these as specified in clause 9.AllNullAll RLC sizes listed in the Transpor

44、t Format Set. 10.3.5.23ConfiguredNullThe RLC sizes configured for this logical channel in the Transport Format Set. 10.3.5.23 if present in this message or in the previously stored configuration otherwiseExplicit List1 to Lists the RLC sizes that are valid for the logical channel.RLC size indexMPInt

45、eger(1.maxTF)The integer number is a reference to the RLC size which arrived at that position in the Transport Format Set 10.3.5.23MAC logical channel priorityMPInteger(1.8)This is priority between a users different RBs (or logical channels). 15Downlink RLC logical channel infoCV-DL-RLC infoNumber o

46、f downlink RLC logical channelsMD1 to MaxLoCHperRLC1 or 2 logical channels per RLC entity or radio bearerRLC 16Default value is that parameter values for DL are exactly the same as for corresponding UL logical channel. In case two multiplexing options are specified for the UL, the first options shal

47、l be used as default for the DL. As regards to the IE Channel type, rule is specified in 8.6.4.8.Downlink transport channel typeMPEnumerated(DCH,FACH,DSCH,DCH+DSCH)DL DCH Transport channel identityCV-DL-DCHTransport channel identity 10.3.5.18DL DSCH Transport channel identityCV-DL-DSCHTransport chan

48、nel identity 10.3.5.18Logical channel identityOPInteger(1.15)16 is reservedConditionExplanationUL-RLC infoIf CHOICE Uplink RLC mode in the IE RLC info that applies for that RB (i.e. either the one stored or received in the same message for the RB for which the RB mapping info was received, or the on

49、e stored or received in the same message for the RB pointed at in the IE Same as RB in the IE RB information to setup stored or received in the same message) is present this IE is mandatory present. Otherwise the IE is not needed.DL-RLC infoIf CHOICE Downlink RLC mode in the IE RLC info that applies

50、 for that RB (i.e. either the one stored or received in the same message for the RB for which the RB mapping info was received, or the one stored or received in the same message for the RB pointed at in the IE Same as RB in the IE RB information to setup stored or received in the same message) is pr

51、esent this IE is mandatory present. Otherwise the IE is not needed.UL-RLCLogicalChannelsIf Number of uplink RLC logical channels in IE RB mapping info is 2, then this IE is mandatory present. Otherwise this IE is not needed.UL-DCHIf IE Uplink transport channel type is equal to DCH this IE is mandato

52、ry present. Otherwise the IE is not needed.DL-DCHIf IE Downlink transport channel type is equal to DCH or DCH+DSCH this IE is mandatory present. Otherwise the IE is not needed.DL-DSCHIf IE Downlink transport channel type is equal to DSCH or DCH+DSCH this IE is mandatory present. Otherwise the IE is

53、not needed.l Number of uplink RLC logical channels 上行配置默認(rèn)兩條邏輯信道；l RLC size 其配置可以有All、Configured、Explicit List三種方式，目前都按照最后一種來進(jìn)行配置，目前版本不考慮RLC size的動(dòng)態(tài)調(diào)整；l Number of downlink RLC logical channels 下行配置默認(rèn)一條邏輯信道，也可配置兩條。8. UL Transport channel information common for all transport channels UCI_U根據(jù)UE的IMSI，從數(shù)據(jù)

54、庫配置選擇上行傳輸信道相應(yīng)內(nèi)容。Information Element/Group nameNeedMultiType and referenceSemantics descriptionPRACH TFCSOPTransport format combination set 10.3.5.20This IE should not be included in this version of the protocol.CHOICE modeOPTFC subsetMDTransport Format Combination Subset10.3.5.22Default value is the complete existing set of transport format combinationsUL DCH TFCSMPTransport formation combination set 10.3.5.209. Added or Reconfigured TrCH information list 需增加或重配置的上行傳輸信道信息列表，此信元在公共信道上建立RRC連接時(shí)不用填。