PS域業(yè)務(wù)優(yōu)化思路

1、端到端優(yōu)化思路PS域業(yè)務(wù)優(yōu)化總體思路業(yè)務(wù)數(shù)據(jù)流的正常與否是決定業(yè)務(wù)質(zhì)量和用戶(hù)感知的直接因素，當(dāng)業(yè)務(wù)質(zhì)量出現(xiàn)異常時(shí)，必然伴隨出現(xiàn)業(yè)務(wù)流程的異常。數(shù)據(jù)業(yè)務(wù)端到端優(yōu)化，是以監(jiān)測(cè)用戶(hù)業(yè)務(wù)流程為核心， 通過(guò)分析和解決引起業(yè)務(wù)流程異常的各類(lèi)因素如：鏈路擁塞、參數(shù)設(shè)置不合理、SP服務(wù)器無(wú)響應(yīng)、終端性能問(wèn)題等，全面提高業(yè)務(wù)質(zhì)量和用戶(hù)感知度?？傮w優(yōu)化思路如下列圖二. 數(shù)據(jù)來(lái)源1. 業(yè)務(wù)信令采集業(yè)務(wù)信令采集是指結(jié)合 PS域業(yè)務(wù)流程與GPRS組網(wǎng)結(jié)構(gòu)，在網(wǎng)絡(luò)重要邏輯接口通 過(guò)數(shù)據(jù)復(fù)制的方式對(duì)全網(wǎng)用戶(hù)的業(yè)務(wù)流程進(jìn)行監(jiān)控和保存。如下列圖所示:SGSN'>£ZJ > Wireshake An

2、d/wwwwwwwwwwwvInteliqent Bit Solutton目前，四川移動(dòng)已在 PS域核心網(wǎng)Gn、Gi、Gw接口部署了西塔信令監(jiān)測(cè)系統(tǒng)，用 于監(jiān)測(cè)和保存全網(wǎng)用戶(hù)的業(yè)務(wù)信令。 Gb接口的信令采集由于受組網(wǎng)方式、設(shè)備資源等 方面限制目前無(wú)法實(shí)現(xiàn)，需要使用信令儀表進(jìn)行數(shù)據(jù)采集和分析。2. 典型用戶(hù)投訴典型用戶(hù)投訴是指網(wǎng)絡(luò)中普遍存在的投訴、大客戶(hù)投訴、疑難投訴，對(duì)于此類(lèi)問(wèn)題,需要進(jìn)行重點(diǎn)關(guān)注，并組織專(zhuān)家組進(jìn)行聯(lián)合分析。3. 熱點(diǎn)地區(qū)業(yè)務(wù)測(cè)試業(yè)務(wù)熱點(diǎn)地區(qū)應(yīng)為具有業(yè)務(wù)使用量大、無(wú)線(xiàn)資源相對(duì)緊張、人群較為集中等特點(diǎn)， 通過(guò)在熱點(diǎn)地區(qū)進(jìn)行業(yè)務(wù)測(cè)試，可以即使發(fā)現(xiàn)和解決業(yè)務(wù)使用中出現(xiàn)的各類(lèi)問(wèn)題，提高

3、 用戶(hù)感知度，并在一定程度上減少投訴的發(fā)生。三. 分析方法進(jìn)行數(shù)據(jù)業(yè)務(wù)分析時(shí)，首先應(yīng)基于全網(wǎng)業(yè)務(wù)統(tǒng)計(jì)數(shù)據(jù)和典型業(yè)務(wù)流程對(duì)全網(wǎng)數(shù)據(jù)業(yè) 務(wù)現(xiàn)狀進(jìn)行統(tǒng)計(jì)和分析，確定影響業(yè)務(wù)成功率的主要狀態(tài)、影響業(yè)務(wù)時(shí)延的主要網(wǎng)元和 設(shè)備，然后結(jié)合終端分析、無(wú)線(xiàn)網(wǎng)絡(luò)分析、GPRS核心網(wǎng)分析、SP質(zhì)量分析等手段對(duì)影響業(yè)務(wù)成功率和時(shí)延的根本原因進(jìn)行定位，最終通過(guò)網(wǎng)絡(luò)和設(shè)備調(diào)整解決問(wèn)題，提高業(yè) 務(wù)質(zhì)量和用戶(hù)感知度。1. 業(yè)務(wù)狀態(tài)分析目前GPRS業(yè)務(wù)主要基于 WAP和 協(xié)議實(shí)現(xiàn)終端和網(wǎng)絡(luò)側(cè)的交互，而 WAP和 協(xié)議，以及 WAP GW都支持通過(guò)定義狀態(tài)碼來(lái)描述業(yè)務(wù)狀態(tài)是否正常，業(yè)務(wù)成功 率分析是指基于全網(wǎng)業(yè)務(wù)信令對(duì)業(yè)務(wù)狀態(tài)碼

4、進(jìn)行分析和統(tǒng)計(jì)，找出影響業(yè)務(wù)成功率的主要原因。 狀態(tài)碼Status-Code ="100" ; Sectio n 10.1.1: Co ntinue| "101" ; Sectio n 10.1.2: Switchi ng Protocols| "200" ; Sectio n 10.2.1: OK| "201" ; Section 10.2.2: Created| "202" ; Section 10.2.3: Accepted| "203" ; Sectio n 10.2

5、.4: No n-Authoritative In formatio n| "204" ; Section 10.2.5: No Content| "205" ; Section 10.2.6: Reset Content| "206" ; Section 10.2.7: Partial Content| "300" ; Section 10.3.1: Multiple Choices| "301" ; Sectio n 10.3.2: Moved Perma nently| "302

6、" ; Section 10.3.3: Fou nd| "303" ; Section 10.3.4: See Other| "304" ; Section 10.3.5: Not Modified| "305" ; Section 10.3.6: Use Proxy| "307" ; Section 10.3.8: Temporary Redirect| "400" ; Section 10.4.1: Bad Request| "401" ; Sectio n 1

7、0.4.2: Un authorized| "402" ; Section 10.4.3: Payme nt Required| "403" ; Sectio n 10.4.4: Forbidden| "404" ; Sectio n 10.4.5: Not Fou nd| "405" ; Sectio n 10.4.6: Method Not Allowed| "406" ; Section 10.4.7: Not Acceptable| "407" ; Sectio n

8、10.4.8: Proxy Authe nticati on Required| "408" ; Section 10.4.9: Request Time-out| "409" ; Sectio n 10.4.10: Conflict| "410" ; Sectio n 10.4.11: Gone| "411" ; Sectio n 10.4.12: Le ngth Required| "412" ; Sectio n 10.4.13: Preco ndition Failed| "4

9、13" ; Section 10.4.14: Request En tity Too Large| "414" ; Section 10.4.15: Request-URI Too Large| "415" ; Section 10.4.16: Un supported Media Type| "416" ; Sectio n 10.4.17: Requested range not satisfiable| "417" ; Section 10.4.18: Expectation Failed| &qu

10、ot;500" ; Sectio n 10.5.1: I nter nal Server Error| "501" ; Section 10.5.2: Not Impleme nted| "502" ; Section 10.5.3: Bad Gateway| "503" ; Section 10.5.4: Service Un available| "504" ; Section 10.5.5: Gateway Time-out| "505" ; Section 10.5.6: Ve

11、rsio n n ot supportedWAP狀態(tài)碼(WTP和WSP)Aboi l reasou (PROVIDER)CodeDescriptionUnknown (UNKNOWN)0x00A generic error code indicating ail unexpecred error .Protocol Enor (PROTOERR)0x01The received PDU could not be inteipreted. The stmctiiie MAY be wrong.Iin alid TID (IN ALIDTID)0x02Only used by th(? Initi

12、ator as a negative result to rhe TID verificanon.Not Implemented Class 2CNOTIMPLEMENTEDCL2)0x03The Transaction could not be compkred since The Re；>pon<lersupportJ transactions.Not Implemenled SAB. (N OTIM PLEMENTED SAR)0x04The iransaction could uot be completed since the Responder does not sup

13、port SAR.Not Iinplemeuted UserAcknowledgement(NOTIMPLEMENTEDUACK)0x05The Iransfictiou could uot be completed since tile Responder does not suppon Us er acknowledgements.WIP Veisicm One (WTPVERSIONONE)0x06C uneiif version isi 1. The iiiitisitoi, requested a difleiem version rh»t is nor supported

14、.Capacity Temporalily Exceeded (CAPTEMPEXCEEDED)0x07Due to an overload situation the transaction can not be completed.No Response (NORESPONSE)0x08A U?>er acknowledgementrequested but the WTPuser did not respondMessage too lrae(MES SAGETOOLARGE)0x09Due to ft mesase $ize bigger rhnn capafcilihes of

15、 rlie recei-亡 t the transact on cannot be completed.Not Iiuplenienred Extended SAR (NOTIM PLEMEN TED ESAR)OxOAThe transaction could not be completed since the Respoiider does not snppoif extended SAR.Tab: WTP Abort CodeNameDescriptionAssigned NumberPROTOERRProtocol 已nor* illegal PDU i sceivedOxEODIS

16、CONNECTSession has been discoiuiectedOxElSUSPENDSession has been suspended0xE2RESUMESession has been resumed0xE3CONGESTIONThe peer is congested and can not process the SOU0xE4CONNECTERRThe session coiuiect failed0xE5MRCEXCEEDEDThe Maxiniimi Receive Unit size was exceeded0xE6MOREXCEEDED丁h亡 MaKiniuin

17、Outstanding Requestsexce亡dud0xE7PEERREQP 已亡 r request0xE8NETERRNetwork enor0xE9USERREQUser requestOxEAUSERRFSUser refilled Push message. No specific cans亡.no retriesOxEBUSERPNDPush message cannot be delivered to intended desTinationOxECUSERDCRPush message discarded due to re source shortageOxEDUSERD

18、CUContent type of Push message cannot be processedOxEETab: WSP Abort CodeWAP GW自定義狀態(tài)碼狀態(tài)代瑪狀態(tài)僖息含文700Iin alid input鉗涙的輸入?yún)?shù).701Inconiplit已 Request不完整的語(yǔ)求-例如發(fā)送Post謂茨時(shí),擾交的內(nèi) 客舉 f - Lt content-leiigfh 忙定的花 i J，卜.702Proxy etroi'J-j WA Server辻&辻接失戰(zhàn)703Out of Memory 內(nèi)存不燐.704Resjxjnw enoi'Web Server .

19、返冋的響應(yīng)不?-r合標(biāo)準(zhǔn)，705Redirect canceled収定向破取消.706Balance not eiwuph用八的賬號(hào)內(nèi)余額缺乏"707Server coimecr «tct網(wǎng)關(guān)從SP效勞粘述取響應(yīng)失敗.708Piq巧 tiiue out網(wǎng)址通過(guò)低理脛務(wù)皤訪(fǎng)的膽務(wù)器,代理曬務(wù)辭超 時(shí).可能是代理腑務(wù)器忙°709Incomplete respomeheaderWb Server返回的 響應(yīng)頭不完整口710Access Denied用戶(hù)不苻合果條網(wǎng)關(guān)設(shè)置的坊問(wèn)控制條件.訪(fǎng)問(wèn) 請(qǐng)求被拒絕"71JCoiilent Type not support由

20、于于機(jī)能力不夠+不支持網(wǎng)站摩務(wù)器理回的響 應(yīng)內(nèi)容.714Connect requf end S請(qǐng)求給東不局錯(cuò)埃*716Cliaiset modified字符集被錢(qián)改*717Invalid chunkingWeb Server返凰的響應(yīng)足鉗逞的chunked輪碼719Platfbnn enor用戶(hù)上線(xiàn)企婀失敗-720Image conveit eiToi-吳機(jī)由F龍力限制龍法支持網(wǎng)姑返叵的圖片格 式網(wǎng)關(guān)對(duì)黃中丄些圖片進(jìn)行榕式轉(zhuǎn)換但由于 圖片人大、閨片陥式十符介覘范即h；川1轉(zhuǎn)換光 敗°721URL hav亡 pace用戶(hù)愉入的網(wǎng)址旳空格口722URL have illesal clwr

21、用戶(hù)輸入的網(wǎng)址有不符合規(guī)世的字符二723FTP fM'otocol not supported不支持FTP協(xié)議*724Respond too larse陰站返回的內(nèi)密人丸，超出 能力:725Connection client close客戶(hù)端斯開(kāi)迭接.1000MDSP eiTor計(jì)費(fèi)賞畋.3101Not enough balance計(jì)費(fèi)已經(jīng)成功，但碗認(rèn)時(shí)失敗.3111Resei e fail可能足用八余擷不圮訃致涼屆煩昭矢敗，或計(jì)費(fèi) 系統(tǒng)管時(shí)故障.3112Clinrae ok blit budget fail可嚨是用戶(hù)金紳不九廿致詭亂計(jì)躋、詭吊預(yù)鬧邵 光雌或計(jì)咖系統(tǒng)科舊血障，Tab :

22、華為 WAP GW- V300R001 Code2. 業(yè)務(wù)流程分析業(yè)務(wù)流程分析是指針對(duì)不同業(yè)務(wù)狀態(tài)碼以及時(shí)延異常的的業(yè)務(wù)，結(jié)合典型業(yè)務(wù)流程 進(jìn)行分析，找出影響業(yè)務(wù)狀態(tài)的網(wǎng)元或設(shè)備 2.1業(yè)務(wù)成功率分析針對(duì)每類(lèi)影響成功率的業(yè)務(wù)狀態(tài)碼，結(jié)合業(yè)務(wù)信令過(guò)程進(jìn)行分析，定位業(yè)務(wù)流程異常發(fā)生的位置。如下所示：002 User Can celed RequestSGSN述221.177 123.17GGSN4WAP Gateway品2021-03-31 23:40122 437.568*Create PDP requestU0 JOI 3sCreate PDP response1035.594s、Cocced

23、疋0.003sComectReply0.216s、AckJ0.1 GBsGet ( )0.140s、Disconnect0.002sJAckU0.000sDisconnect0 277?、Ack221 177.123 20.002$Get ( )通過(guò)對(duì)002錯(cuò)誤的異常業(yè)務(wù)流程分析發(fā)現(xiàn)，導(dǎo)致該類(lèi)錯(cuò)誤的現(xiàn)象是網(wǎng)絡(luò)側(cè)收到用戶(hù)主動(dòng)發(fā)起業(yè)務(wù)中斷請(qǐng)求(disconnect)。而導(dǎo)致用戶(hù)發(fā)起業(yè)務(wù)中斷請(qǐng)求的原因可能包括用 戶(hù)行為、終端異常、無(wú)線(xiàn)連接異常等，需要結(jié)合終端分析、無(wú)線(xiàn)網(wǎng)絡(luò)分析等手段進(jìn)行問(wèn) 題定位。2.2業(yè)務(wù)端到端時(shí)延分析業(yè)務(wù)端到端時(shí)延分析是指根據(jù)業(yè)務(wù)信令的時(shí)間戳計(jì)算出數(shù)據(jù)流在各網(wǎng)元或節(jié)點(diǎn)所消耗的時(shí)延

24、，并以此統(tǒng)計(jì)出端到端時(shí)延分布的情況，找出時(shí)延消耗過(guò)大和不合理的網(wǎng)元 和設(shè)備。分析方法如下列圖所示：ETSFEddia partRTT-R = (RTT-R -RTT Gb) + (RfT-Gb -RTT Gn) + (R7T-Gn>JFTiFf3. 網(wǎng)絡(luò)和設(shè)備分析網(wǎng)絡(luò)和設(shè)備分析根本屬于傳統(tǒng)網(wǎng)絡(luò)優(yōu)化范疇，具體內(nèi)容包括無(wú)線(xiàn)網(wǎng)絡(luò)分析優(yōu)化、GPRS核心網(wǎng)分析優(yōu)化、業(yè)務(wù)網(wǎng)分析優(yōu)化、終端性能測(cè)試分析等，通過(guò)網(wǎng)絡(luò)和設(shè)備分析, 確定并解決引起業(yè)務(wù)流程異常的根本原因。四. 解決措施及案例業(yè)務(wù)狀態(tài)和業(yè)務(wù)流程分析可確定引起業(yè)務(wù)流程異常的根本原因，針對(duì)這些原因，實(shí) 際優(yōu)化過(guò)程中可以通過(guò)網(wǎng)絡(luò)資源均衡、參數(shù)調(diào)整、設(shè)

25、備算法調(diào)整、終端軟件升級(jí)等具體 措施加以解決。案例介紹：aE100C防火墻版本過(guò)低導(dǎo)致局部終端PIM業(yè)務(wù)五. 預(yù)期輸出成果通過(guò)現(xiàn)網(wǎng)業(yè)務(wù)狀態(tài)分析，了解全網(wǎng)數(shù)據(jù)業(yè)務(wù)的的主要問(wèn)題和瓶頸；通過(guò)業(yè)務(wù)流程分析和網(wǎng)絡(luò)設(shè)備分析，可以確定并解決確定并解決引起業(yè)務(wù)流程異常的根本原因。結(jié)合以上方法對(duì)數(shù)據(jù)業(yè)務(wù)進(jìn)行分析，最終可以活得數(shù)據(jù)業(yè)務(wù)狀態(tài)和網(wǎng)絡(luò)原因的映射關(guān)系，為數(shù)據(jù)業(yè)務(wù)優(yōu)化形成指導(dǎo)和參考。如下表所示： /WAP Status CodeDescriptionReason408請(qǐng)求超時(shí)無(wú)線(xiàn)網(wǎng)絡(luò)信道資源缺乏002用戶(hù)取消請(qǐng)求覆蓋問(wèn)題導(dǎo)致無(wú)線(xiàn)連接中斷:500效勞器內(nèi)部錯(cuò)誤防火墻配置問(wèn)題導(dǎo)致上傳數(shù)據(jù)超時(shí)504網(wǎng)關(guān)超時(shí)SP效勞器未下發(fā)數(shù)據(jù)六. 彩信業(yè)務(wù)優(yōu)化補(bǔ)充說(shuō)明彩信業(yè)務(wù)與其他PS域業(yè)務(wù)相比，存在一定特殊性，集中表現(xiàn)為用戶(hù)原因?qū)I(yè)務(wù)成功 率的影響比重極大，如4441、4442、2000等錯(cuò)誤占彩信端到端錯(cuò)誤總數(shù)的 80%以上， 前面所描述的PS域業(yè)務(wù)優(yōu)化思路只能夠有針對(duì)性地解決網(wǎng)絡(luò)和終端問(wèn)題，而針對(duì)彩信業(yè)務(wù)，需要單獨(dú)進(jìn)行分析。根據(jù)彩信端到端業(yè)務(wù)現(xiàn)狀，目前主要需要對(duì)以下問(wèn)題進(jìn)行分析：1. 為什么有那么多彩信終端用戶(hù)沒(méi)有提取彩信？一 4442錯(cuò)誤2. 為什么局部用戶(hù)和終端會(huì)拒絕接收彩信？一 2000錯(cuò)誤3. 為什么會(huì)有大量PUSH消息下發(fā)失??？一 4470錯(cuò)誤4.