SW-Log Analysis Series -- GAP.ppt

rrc introduction on implementation,chen defang of sw1 department,jul.31, 2009,2/5/2019,confidential,2,content,rrc overview rrc module structure rrc procedure,rrc overview,2/5/2019,confidential,4,rrc architecture and function entity,2/5/2019,confidential,5,rrc states,2/5/2019,confidential,6,rrc states,idle mode no signaling connection exist. identified by nas identities such as imsi, tmsi and p-tmsi. connected mode there is a rrc connection between ue and utran -cell_dch the ue position is known on cell level. dedicated transport channels are used for data transfer. (dch) dcch and, if configured, dtch are available.,2/5/2019,confidential,7,rrc states,-cell_fach the ue position is known on cell level. common transport channels are used for data transfer. (rach, fach) dcch and, if configured, dtch are available. -cell_pch/ura_pch the ue position is known on cell/ura level. common transport channels are used for data transfer. (rach, fach) neither dcch nor dtch are available.,rrc module achitecture,2/5/2019,confidential,9,rrc implementation architecture,2/5/2019,confidential,10,rrc implementation architecture,gcfe (general control function entity) gcfe is mainly to maintain the rrc cell selection and re-selection procedures. responsible for synchroning other three modules dcfe (dedicated control function entity) this module is a set of procedures that handle the network access and the connection mode of rrc. mcfe (measurement control function entity) this module consists of procedures that handle most types of measurements described in protocol specification. bcfe (broadcast control function entity) this module consists of procedures that receive and store system information from network. handle the system information change and manage the system information.,2/5/2019,confidential,11,rrc internal relationship,gcfe,dcfe,bcfe,mcfe,master in non-dch,master in dch,slave of gcfe in non-dch, and inactive in dch,slave of gcfe in non-dch, and slave of dcfe in dch,2/5/2019,confidential,12,gcfe-dcfe interface,gcfe makes use of this interface to inform dcfe the cell selection/reselection, “out of service area” “re-enter service area” indication and the cell information after complete selection. its also used by gcfe to request dcfe to perform updated procedure. dcfe makes use of this interface to request gcfe perform cell selection under connected mode and the state change under connected mode.,2/5/2019,confidential,13,gcfe-bcfe interface,gcfe makes use of this interface to request bcfe to read system information. bcfe report received system information to gcfe. gcfe makes use of this interface to inform the state change of rrc.,2/5/2019,confidential,14,gcfe-mcfe interface,gcfe makes use of this interface to inform mcfe measurement control information and control mcfe perform neighbor cell measurement. gcfe makes use of this interface to inform the state change of rrc. mcfe report the measurement result to gcfe.,2/5/2019,confidential,15,dcfe-mcfe interface,dcfe makes use of this interface to transfer measurement control message to mcfe. mcfe sends measurement report to dcfe. this interface is also used by dcfe to inform the handover to another cell in cell_dch to mcfe.,2/5/2019,confidential,16,rrc message scheduling,2/5/2019,confidential,17,rrc implementation architecture,outer message to/from rrc rrc is mapped to a process in a rtk task and receiving outer message (message from other module, for example, rlc, mac, hla, .) via rtk mailbox rrc task and process is scheduled by rtk. rrc sub-process scheduling there is a internal message queue. rrc sub-processes (dcfe, gcfe, ) communicate each other via internal message queue. rrc sub-processes are scheduled by rrc framework internal message queue has higher priority than rtk mailbox.,2/5/2019,confidential,18,gcfe fsm and implementation architecture,s_gc_idl: in stable idle state (gc06idl.c) s_gc_con in stable connection state (gc09con.c) s_gc_emi in emergency state (gc14emi.c) s_gc_gap state when doing lcr gap (gc05gap.c) s_gc_sel state when selecting a cell (gc04sel.c) s_gc_resel state when doing cell re-selecting (gc08rsel.c) s_gc_acc state when initiating a rrc connection (gc15acc.c) s_gc_ldch state when leaving cell_dch state (gc13ldch.c) s_gc_mibreading, s_gc_sibreading, s_gc_simreading, s_gc_psel, s_gc_gsm_resel, s_gc_gsm_sel, s_gc_gsm_gap, s_gc_gsm_master, s_gc_ccchreading, ,2/5/2019,confidential,19,gcfe state transfer when power on,s_gc_null s_gc_idl s_gc_simreading s_gc_sibreading s_gc_sel s_gc_mibreading s_gc_mibreading s_gc_sel s_gc_sibreading s_gc_con s_gc_idl s_gc_acc,receive rr_data_req for register,receive rr_act_req,after register, rrc connection release,2/5/2019,confidential,20,gcfe state transfer when cell-reselection,s_gc_idl s_gc_resel s_gc_idl,s0 or t_reselection expired,2/5/2019,confidential,21,gcfe state transfer when gap,s_gc_idl s_gc_gap s_gc_gsm_gap s_gc_idl,receive rr_get_plmn_req,2/5/2019,confidential,22,gcfe primary files,message handler of each state(gc06idl.c, gc09con.c, etc.) gc30table.c: message entry file of gcfe gc01all.c: common message handler gc49res.c: cell reselection evaluate and control gc57sys.c: parse system information (mainly sib3/4 and sib11/12) gc63mtx.c: gsm cells management gc71mbms.c: mbms service handle,2/5/2019,confidential,23,bcfe fsm and implementation architecture,s_bc_ncm in this state when gcfe informs to receive bch in cell selection/reselection procedure. (bc04ncm.c) s_bc_ccm in this state when ue camps on a cell, and does not need to receive bch except for sib7. (bc05ccm.c) s_bc_mcm in this state when gcfe informs to receive the updated bch if bch has changed. (bc07mcm.c) s_bc_ldch in this state when receive bch after rrc leave dch state. (bc06ldch.c) s_bc_six if stored sibs keep for six hours without update, bcfe will enter this state to receive them again. (bc08six.c),2/5/2019,confidential,24,bcfe primary files,message handler of each state(bc04ncm.c, bc05ccm.c, bc07mcm.c, etc.) bc16tab.c: message entry file of bcfe bc12dec1.c: first decoding system information (receiving system information from l1 segment by segment) bc13dec2.c: second decoding system information. (reassemble these segments after first decode),2/5/2019,confidential,25,dcfe fsm and implementation architecture,no fsm. distribute message according to message type. main message type rlc_data_ind (all downlink signaling messages are carried by it, and its sent to dcfe) rlc_data_req (all uplink signaling messages are carried by it, and its sent by dcfe) cphy_ctl_rl_setup_req (modify/release) cphy_ctl_trch_config_req (modify/release) cphy_ctl_hsdpa_setup_req (release) cmac_trch_config_req crlc_establish_req (modify/reestablish),2/5/2019,confidential,26,understand dcfe from rb reconfig flow,process of dcfe when receiving rb reconfig: parse rlc_data_ind to find its a rb reconfig (dc01main.c) copy current config to be new config, then update new config according to this rb reconfig (dc56rb.c) save integrity protection config (dc70integ.c) save ciper mode info (dc71cipher.c) save ue info (u-rnti, c-rnti, plmn, ue id, etc) (dc73ueinfo.c) handle rb related ie (dc74rbie.c) handle trch channel related ie (dc77trchie.c) handle rb mapping to trch (dc75rbcom.c) handle pdcp related info (dc83pdcp.c) handle rlc entity related info (dc82crlc.c) handle physical channel related ie (dc76phychinfo.c),2/5/2019,confidential,27,understand dcfe from rb reconfig flow,construct message for mac (dc84mac.c) construct message for l1c (dc81cphy.c) send new configuration to lower layer and waiting for sync with new configuration if sync success, remove old config and send rb reconfig complete to nw if sync failure or invalid config, revert to old config and send rb reconfig failure to nw,2/5/2019,confidential,28,dcfe file structure and primary files,2/5/2019,confidential,29,mcfe fsm and implementation architecture,s_mc_idle idle state (mc01und.c) s_mc_dch cell_dch state (mc02dch.c) s_mc_fach cell_fach state (mc01und.c) s_mc_pch cel