江苏联通SGSN培训.ppt

usp4.0 sgsn training,motorola wei mingming agenda,system overview software structure hardware structure sgsn configuration hardware conf gb interface gr interface gn/gp interface ga interface basic signaling flow troubleshooting,system overview,bss,bts,bsc,pcu,pstn isdn,internet, intranet,msc/vlr,gmsc,hlr/auc,sgsn,cg,bg,ggsn,gprs backbone,ran,cn,other plmn,ss7,sgsn function in gprs network,gprs standard protocol interface,system overview,atm交换,子系统,gb接口处理子系统,gtp-c处理子系统,数据转发子系统,计费子系统,n7信令处理子系统,操作维护子系统,时钟子系统,gsn/cg,bss,omc/lmt,bits/line1/2,hlr/msc,system overview,sgsn software structure,first cabinet of usp4 sgsn 4 psm subrack per cabinet at max.,system overview,sgsn hardware structure,rear slot,front slot,for ufcu only(0-5),system overview,sgsn hardware structure 1. switch sub-rack,ufcu realizes the interconnection between the basic subrack, the switch subrack and the expansion subrack. ugfu realizes the external interfaces of gn/gp and the transfer of user plane.,rear slot,front slot,2g service board,ucki is fixed.,fixed configuration,sgsn hardware structure 2. basic sub-rack,system overview,contains o&m boards: uomu realize the clock extract with ucki boards contains service boards: ugbi/uspu/ugtp,fixed configuration,sgsn hardware structure 3. expanded sub-rack,system overview,rear slot,front slot,typical 2g expansion subrack, 6+1 for ugbi, together with 2+2 uspu,system overview,sgsn hardware communication (1) between subracks,system overview,sgsn hardware communication (2) fiber connection,system overview,sgsn hardware communication (3) clock scheme,agenda,system structure software structure hardware structure sgsn configuration hardware conf gb interface gr interface gn/gp interface ga interface basic signaling flow maintenance and troubleshooting,hardware conf,basic configuration： system: set ofi set sigattr/add n7opc/add sccpopc sub-racks: add subrack switch subrack boards: the sub-board of ueec/uaic/uss7 could be added same time with front boards. the back board of upiu/uepi could be added with the front ones. except the standby ugbi board (n+1 backup) need to be added separately, other standby boards (1+1backup) will be added together with the active one. upiu back of ugfu need to configure the port property: set upiu_port,gb interface conf,gb interface protocol stack,user plane,control plane,gb interface conf,gb interface protocol stack,l1（phy）,ns,bssgp,llc,gmm/sm,ns,fr,bssgp,llc,control plane,user plane,sndcp,gb interface conf,configuration concepts: bc: the bearer channel of fr corresponding to the timeslot group of e1/t1, the timeslot distribution must be consistent with pcu side. pvc: the bc contains some pvcs distinguished by dlci, the dlci value must be consistent with pcu side. nsvc: virtual link provided by ns layer for bssgp layer, the nsvc value must be consistent with pcu side. nse: nse manages a group of ns-vcs, and corresponding a group of cells. bvc: bssgp virtual connection is used in the bssgp layer, classified to sig bvc, ptp bvc and ptm bvc. one ptp bvc corresponds to one cell.,gb interface conf,gb interface example,gb interface conf,configure commands:,gb interface conf,maintenance: bssgp layer: dsp sigbvc:; nsvc layer: %dsp nsvc: srn=0, sn=1;% sub no. slot no. e1/t1 port bc nsvc identifier valid status 0 1 1 0 1020 unblocked 0 1 3 0 1040 unblocked bc layer: %dsp bc: srn=0, sn=1, pn=0;% subrack no. slot no. e1/t1 port bc valid status of bc pvcs activated 0 1 0 0 valid (unblocked, lmi valid) 1 physical layer: %dsp uepiutpilnk: srn=0, sn=1, pn=0;% subrack no. slot no. e1/t1 port link status 0 1 0 normal,gr interface conf,gr interface protocol stack location and subscription management of mobile user uepi board provide the e1 interface uss7 board provide the mtp2 processing ability uspu board process the mtp3, sccp and map layer,mtp1,mtp3,sccp,tcap,map,mtp2,保证物理传输,进行链路控制,完成网络传输,完成信令网中sp之间 可靠的信令传输,有增强的寻址选路功能,控制信令点之间 非业务相关的信息的传输,完成移动用户的位置管理、 用户数据管理等,gr interface conf,connect to hlr through stp,gr interface conf,configure commands,gr interface conf,maintenance: sccp layer: %dsp sccpdpc:;% dpc index network indicator dpc opc status loadshare dpc backup dpc status sccp status congest status 0 national network 0xff0981 0xff099d allow allow null allow non-congested 1 national network 0xff0980 0xff099d allow allow null allow non-congested mtp layer: %dsp n7lnk:;% subrack no. slot no. link no. transmission service link fault link congest 0 4 0 yes no no yes no physical layer: %dsp uepiutpilnk: srn=0, sn=4, pn=0;% subrack no. slot no. e1/t1 port link status 0 4 0 normal,gn interface conf,gn interface protocol stack:,- ugtp changed in board type: gtpc/gtpc_gtpu/gtpu gtpc: gtp-c forwarding, dns client and ntp client, need to bind with ugfu and need to configure ip addr. gtpu: gtp-u pdp control and charging data,ugfu boards,ugtp/uspu boards,gn interface conf,gn transfer realization,gn interface conf,configuration commands,gn interface conf,maintenance: gtp-c path: %dsp gtpcpath: srn=0, sn=12, ipt=ipv4, pip4=“3“;% gtp version of path = gtp v1 attribute of path = sm path state of path = normal tst gtpcpath: srn=0, sn=12, ipt=ipv4, pip4=“3“; gtp-u path: %dsp gtpupath: srn=3, sn=12, itp=ipv4, pip4=“3“;% gtp version used for path = gtp v1 path category = udp data path with ggsn path status = path normal tst gtpurncgsn: srn=3, sn=12, itp=ipv4, pip4=“3“; if path is down, we could check the ip connection: %ping ip: srn=3, sn=12, dip=“3“;% if not specify a source address, the board ip address is pinged by default.,ga interface conf,ga interface protocol stack:,ugtp function: transfer cdr between the gsn and the cg. redirecting the cdr to another cg. notify the peer entity to re-transmit the data when the unavailable gsn or cgf turns to normal.,ga interface conf,configuration commands,sm/mm conf,mobility management: modify 2g mm software parameters: set gmm: includes security procedure parameters, p-tmsi reallocation parameters and imei check procedure parameters set gmmtmr: rau timer, ms reachable timer. set sdbtmr: purge timer. add connectplmn: add for the roaming user access. session management: modify 2g sm software parameters: set 2gsm: apn oi, qos parameters. add pdpapn: set the default apn for ipv4 pdp. return to home: after the apn customization function works, based on the imsi or msisdn number segments, the sgsn can flexibly choose different ggsns for the mss to access the pdn in one plmn. when the mss use the public apn to activate pdp contexts after the apn customization function works, the sgsn adds a label for the apn to differentiate the mss. an operator can configure the ip addresses of different ggsns for different apns, and thus realize choosing ggsn,agenda,system structure software structure hardware structure sgsn configuration hardware conf gb interface gr interface gn/gp interface ga interface basic signaling flow maintance and troubleshooting,gprs attach,gprs attach,gprs attach,pdp activation,backbone,apn-ni,apn ggsn ip address,apn-ni,pdp activation,agenda,system structure software structure hardware structure sgsn configuration hardware conf gb interface gr interface gn/gp interface ga interface basic signaling flow maintenance and troubleshooting,system fault,1. the performance measurement data is lost in some periods and that in other periods is normal. possible cause: the uomu is reset. the boards related to measurement items are reset or switched over. the entire sgsn system is reset. handling: step1: check if any of the following alarms is generated during the data loss period. uomu reset alarm uomu switchover alarm sgsn reset alarm step 2: check if the boards related to the measurement item with data loss have historical alarms.,system fault,2-1. dns connection check check whether dns resolution works: tst dns tst dns: fn=0, sn=12, host = “uniwap.1322243.mnc001.mcc460.gprs“, rsvtp=all; if failed to resolve, go next. check the dns server state: dsp dnss dsp dnss: srn=0, sn=12; (ugtp board) if dns server no response, check the link. 2-2 ntp connection check query the ntp association status: dsp ntpas 8 yes v3 1 -19 3000 0.020 0.007 0.002 query the time sync status of ntp client: dsp ntpstat synchronized to ntp server flag = yes ip address of synchronization clock = 2 stratum = 2 time precision = -7 reference time stamp = 2007-06-07 10:19:19.182 time sample delay(s) = 0.068,service fault,3. attach reject with “gprs service not allowed” possible cause: the ms is roaming and the plmn to which it belongs is not configured as an interconnected plmn in the sgsn. the subscriber dose not subscribe gprs service in hlr. handling: check the traced signaling to obtain the imsi of the ms. execute lst connectplmn on the lmt to query information on the interconnected plmn. if incorrect, execute mod connectplmn. if not found, execute add connectplmn if the subscriber dose not subscribe gprs sever in hlr, contact the hlr to confirm the subscription data.,service fault,4. after sending out attach request, attach reject with “protocol error“ possible cause: the global title (gt) code is unavailable for location update because the imsi-gt table is not configured. therefore, the attach request is rejected. handling: check the traced signaling to obtain the imsi of the ms. execute lst imsigt on the lmt to query information. if not configured, use add imsigt to add the gt translation.,service fault,5. description: after the sgsn sends an update location message to the hlr, the sgsn does not receive any insert subscriber data or update location ack from the hlr. sgsn sends an attach reject message to the ms, carrying the cause value “protocol error, unspecified.“ possible cause: gr interface has some problem. handling: check the traced signaling of gr interface. dsp n7lnk to query the gr link status, and dsp uepiutpilnk to check the physical link status. or contact hstp supporter to investigate.,service fault,6. description: all mss in one cell cannot access the network or implement the gprs services in a certain period. the gb interface tracing or ns interface tracing shows that the sgsn does not send any message to the mss after receiving attachreq messages from mss. possible cause: after the cell is reset, the pcu does not send the cell flow control message. thus, the sgsn discards the ms message capsule directly. handling: execute dsp ptpbvc to check if the cell receives the flow control message. if the cell receives no flow control message, reset the cell to allow the pcu to report the cell flow control message again. rst ptpbvc if the fault persists, ask the pcu maintenance personnel to check the pcu settings.,service fault,7. activate pdp context reject with “missing or unknown apn“ possible cause: dns resolution fails and the ip address of the ggsn is unavailable. handling: check the dns resolving: tst dns: srn=0, sn=12, host=“uniwap.1322243.mnc001.mcc460.g