MSCBSC 移动通信论坛
搜索
登录注册
网络优化工程师招聘专栏 4G/LTE通信工程师最新职位列表 通信实习生/应届生招聘职位

  • 阅读:10385
  • 回复:9
CS 业务建立成功率低
xiaogang99
金牌会员



 发短消息    关注Ta 

积分 5252
帖子 396
威望 46180 个
礼品券 10 个
专家指数 -72
注册 2009-2-24
专业方向  WBTS Vertification
回答问题数 0
回答被采纳数 0
回答采纳率 0%
 
发表于 2012-03-19 14:06:48  只看楼主 
有没有朋友遇到过由于iuv_iu_rel_comm_received_c cause引起的RAB及RRC连接建立成功率低的问题啊?
个人认为是MSS出现问题,或者MSS升级后需要修改什么参数?
大家可以给点建议吗!
谢谢!
扫码关注5G通信官方公众号,免费领取以下5G精品资料
  • 1、回复“YD5GAI”免费领取《中国移动:5G网络AI应用典型场景技术解决方案白皮书
  • 2、回复“5G6G”免费领取《5G_6G毫米波测试技术白皮书-2022_03-21
  • 3、回复“YD6G”免费领取《中国移动:6G至简无线接入网白皮书
  • 4、回复“LTBPS”免费领取《《中国联通5G终端白皮书》
  • 5、回复“ZGDX”免费领取《中国电信5G NTN技术白皮书
  • 6、回复“TXSB”免费领取《通信设备安装工程施工工艺图解
  • 7、回复“YDSL”免费领取《中国移动算力并网白皮书
  • 8、回复“5GX3”免费领取《 R16 23501-g60 5G的系统架构1
  • 对本帖内容的看法? 我要点评

     
    [充值威望,立即自动到帐] [VIP贵宾权限+威望套餐] 另有大量优惠赠送活动,请光临充值中心
    充值拥有大量的威望和最高的下载权限,下载站内资料无忧
    飞天雪狐
    中级会员
    鎵嬫満鍙风爜宸查獙璇


     发短消息    关注Ta 

    积分 598
    帖子 143
    威望 634 个
    礼品券 5 个
    专家指数 -117
    注册 2011-7-27
    专业方向  网络优化
    回答问题数 0
    回答被采纳数 0
    回答采纳率 0%
     
    发表于 2012-03-19 17:06:37 
    技术问题,回答得专家指数,快速升级
    高手解答,学习学习。

    对本帖内容的看法? 我要点评

     
    [立即成为VIP会员,百万通信专业资料立即下载,支付宝、微信付款,简单、快速!]
    najialuo
    中级会员
    鎵嬫満鍙风爜宸查獙璇


     发短消息    关注Ta 

    积分 611
    帖子 156
    威望 8405 个
    礼品券 18 个
    专家指数 -169
    注册 2012-2-21
    专业方向  无线网络设计与优化
    回答问题数 0
    回答被采纳数 0
    回答采纳率 0%
     
    发表于 2012-03-21 11:23:27 
    一般来说,影响业务建立成功率的原因主要有工程方面原因,无线环境原因,拥塞和RSSI等,可以分别从这几个方面来进行探究。

    共获得 1 次点评 我要点评

    • OscarDon 威望 +2 个
      · 积极讨论 详细.. 发表与:2014-1-19 19:07:27
     
    最新通信职位:广东通信人才网 | 北京通信人才网 | 上海通信人才网 | 南京通信人才网 | 西安通信人才网 | 重庆通信人才网 | 中国通信人才网
    pleasesister
    初级会员
    鎵嬫満鍙风爜宸查獙璇


     发短消息    关注Ta 

    积分 72
    帖子 29
    威望 2830 个
    礼品券 8 个
    专家指数 -73
    注册 2011-9-21
    专业方向  网络优化
    回答问题数 0
    回答被采纳数 0
    回答采纳率 0%
     
    发表于 2012-03-26 09:49:01 
    期待高手、学习学习

    对本帖内容的看法? 我要点评

     
    热点: 通信招聘职位 | 网络优化全集 | WCDMA精品 | TD-SCDMA学习资料 | EVDO | MGW媒体网关资料
    ebrain68
    银牌会员
    鎵嬫満鍙风爜宸查獙璇


     发短消息    关注Ta 

    积分 2934
    帖子 353
    威望 84712 个
    礼品券 169 个
    专家指数 1169
    注册 2008-3-10
    专业方向 
    回答问题数 0
    回答被采纳数 0
    回答采纳率 0%
     
    发表于 2012-03-26 23:11:40 
    下面这些是RRC release/setup failure/protocol error的所有cause,没有发现楼主log中列出的causevalue,能否找下设备相关资料看看这个log中的缩写啥意思?对应规范中的哪个cause?看看能否对上标准。
    10.3.3.13
    Failure cause
    Cause for failure toperform the requested procedure.
    Information Element/Groupname
    Need
    Multi
    Type and reference
    Semantics description
    Failure cause
    MP


    Enumerated(configuration unsupported, physical channel failure, incompatiblesimultaneous reconfiguration, protocol error, compressed mode runtime error,cell update occurred, invalid configuration, configuration incomplete,unsupported measurement, MBMS session already received correctly, lowerpriority MBMS service)
    Five spare valuesare needed.



    10.3.3.26
    Protocol error cause
    This IE indicates thecause for a message or information that was not comprehended.
    Information Element/Groupname
    Need
    Multi
    Type and reference
    Semantics description
    Protocol errorcause
    MP


    Enumerated (ASN.1violation or encoding error, Message type non-existent or not implemented,Message not compatible with receiver state, Information element value notcomprehended, Information element missing, Message extension notcomprehended)
    Two spare valuesare needed.



    10.3.3.32
    Release cause
    Cause for release ofRRC connection.
    Information Element/Groupname
    Need
    Multi
    Type and reference
    Semantics description
    Release cause
    MP


    Enumerated
    (normal event,unspecified, pre-emptive release, congestion, re-establishment reject,directed signalling connection re-establishment, user inactivity)
    One spare value isneeded.











































    [ 本帖最后由 ebrain68 于 2012-3-26 23:13 编辑 ]

    共获得 1 次点评 我要点评

    • OscarDon 专家指数 +2 , 威望 +8 个
      · 积极讨论 详细.. 发表与:2014-1-19 19:07:47
     
    最新通信职位:广东通信人才网 | 北京通信人才网 | 上海通信人才网 | 南京通信人才网 | 西安通信人才网 | 重庆通信人才网 | 中国通信人才网
    ebrain68
    银牌会员
    鎵嬫満鍙风爜宸查獙璇


     发短消息    关注Ta 

    积分 2934
    帖子 353
    威望 84712 个
    礼品券 169 个
    专家指数 1169
    注册 2008-3-10
    专业方向 
    回答问题数 0
    回答被采纳数 0
    回答采纳率 0%
     
    发表于 2012-03-26 23:19:54 
    拓展之,rab建立失败原因值如下:
    9.2.1.4
    Cause
    The purpose of theCause IE is to indicate the reasonfor a particular event for the RANAP protocol.

    IE/Group Name
    Presence
    Range
    IE type and reference
    Semantics description
    Choice Cause








    >Radio Network Layer Cause




    INTEGER
    (RAB pre-empted(1),

    Trelocoverall Expiry(2),
    Trelocprep Expiry(3),
    Treloccomplete Expiry(4),
    Tqueuing Expiry(5),

    Relocation Triggered(6),

    Unable to Establish During Relocation(8),
    Unknown Target RNC(9),
    Relocation Cancelled(10),
    Successful Relocation(11),
    Requested Ciphering and/or Integrity Protection Algorithms notSupported(12),
    Conflict with already existing Integrity protection and/or Cipheringinformation (13),
    Failure in the Radio Interface Procedure(14),
    Release due to UTRAN Generated Reason(15),
    User Inactivity(16),
    Time Critical Relocation(17),
    Requested Traffic Class not Available(18),
    Invalid RAB Parameters Value(19),
    Requested Maximum Bit Rate not Available(20),
    Requested Maximum Bit Rate for DL not Available(33),
    Requested Maximum Bit Rate for UL not Available(34),
    Requested Guaranteed Bit Rate not Available(21),
    Requested Guaranteed Bit Rate for DL not Available(35),
    Requested Guaranteed Bit Rate for UL not Available(36),
    Requested Transfer Delay not Achievable(22),
    Invalid RAB Parameters Combination(23),
    Condition Violation for SDU Parameters(24),
    Condition Violation for Traffic Handling Priority(25),
    Condition Violation for Guaranteed Bit Rate(26),
    User Plane Versions not Supported(27),
    Iu UP Failure(28),
    TRELOCalloc Expiry (7),
    Relocation Failure in Target CN/RNC or Target System (29),
    Invalid RAB ID(30),
    No remaining RAB(31),
    Interaction with other procedure(32),
    RepeatedIntegrity Checking Failure(37),
    RequestedRequest Type not supported(38),
    Requestsuperseded(39),
    Release dueto UE generated signalling connection release(40),

    ResourceOptimisation Relocation(41),
    RequestedInformation Not Available(42),
    Relocationdesirable for radio reasons (43),
    Relocation notsupported in Target RNC or Target system(44),

    Directed Retry (45),
    RadioConnection With UE Lost(46),
    RNC unable toestablish all RFCs (47),
    Deciphering Keys Not Available(48),
    Dedicated Assistance data Not Available(49),
    RelocationTarget not allowed(50),
    Location Reporting Congestion(51),

    Reduce Loadin Serving Cell (52),
    NoRadio Resources Available in Target cell (53),
    GERANIu-mode failure (54),
    AccessRestricted Due to Shared Networks(55),
    IncomingRelocation Not Supported Due To PUESBINE Feature(56),
    TrafficLoad In The Target Cell Higher Than In The Source Cell(57),
    MBMS- No Multicast Service For This UE(58),
    MBMS- Unknown UE ID(59),
    SuccessfulMBMS Session Start - No Data Bearer Necessary(60),
    MBMS- Superseded Due To NNSF(61),
    MBMS- UE Linking Already Done(62),
    MBMS- UE De-Linking Failure - No Existing UE Linking(63),
    TMGI Unknown(64))

    Value range is 1 – 64.
    >Transport Layer Cause




    INTEGER
    (
    Signalling TransportResource Failure(65),


    Iu TransportConnection Failed to Establish(66))
    Value range is 65 –80.
    >NAS Cause




    INTEGER
    (User Restriction Start Indication(81),

    User Restriction End Indication(82),
    Normal Release(83))
    Value range is 81 –96.
    >Protocol Cause




    INTEGER
    (Transfer Syntax Error(97),

    Semantic Error (98),
    Message not compatible with receiver state (99),
    Abstract Syntax Error (Reject) (100),
    Abstract Syntax Error (Ignore and Notify) (101),
    Abstract Syntax Error (FalselyConstructed Message) (102))
    Value range is 97 –112.
    >Miscellaneous Cause




    INTEGER
    (O&M Intervention(113),

    No Resource Available(114),
    Unspecified Failure(115),
    NetworkOptimisation(116))
    Value range is 113 –128.
    >Non-standard Cause




    INTEGER
    ()
    Value range is 129 –256. Cause value 256 shall not be used.
    >Radio Network Layer Cause Extension




    INTEGER
    (IP Multicast Address And APN Not Valid(257),

    MBMS De-Registration Rejected Due To Implicit Registration(258),
    MBMS - Request Superseded(259),
    MBMS De-Registration During Session Not Allowed(260),

    MBMS - No Data BearerNecessary(261) ,
    Periodic Location Information not Available(262),
    GTP Resources Unavailable(263),
    TMGI in Use and Overlapping MBMSService Area (264),

    MBMS – No cell in MBMS ServiceArea (265),
    No Iu CS UPrelocation (266) ,
    Successful MBMS Session Start – IPMulticast Bearer established (267)),
    CS Fallbacktriggered (268))

    Value range is 257 –512.



    The meaning of the different cause values is described in the followingtable. In general, "not supported" cause values indicate that therelated capability is missing. On the other hand, "not available"cause values indicate that the related capability is present, but insufficientresources were available to perform the requested action.

    Radio Network Layercause
    Meaning
    Deciphering Keys NotAvailable
    The action failedbecause RNC is not able to provide requested deciphering keys.
    Conflict with alreadyexisting Integrity protection and/or Ciphering information
    The action was notperformed due to that the requested security mode configuration was inconflict with the already existing security mode configuration.
    Condition ViolationFor Guaranteed Bit Rate
    The action was notperformed due to condition violation for guaranteed bit rate.
    Condition ViolationFor SDU Parameters
    The action was notperformed due to condition violation for SDU parameters.
    Condition ViolationFor Traffic Handling Priority
    The action was notperformed due to condition violation for traffic handling priority.
    Dedicated Assistancedata Not Available
    The action failedbecause RNC is not able to successfully deliver the requested dedicatedassistance data to the UE.
    Directed Retry
    The reason for actionis Directed Retry
    Failure In The RadioInterface Procedure
    Radio interfaceprocedure has failed.
    Incoming RelocationNot Supported Due To PUESBINE Feature
    The incoming relocationcannot be accepted by the target RNC because of the PUESBINE feature.
    Interaction With OtherProcedure
    Relocation wascancelled due to interaction with other procedure.
    Invalid RAB ID
    The action failedbecause the RAB ID is unknown in the RNC.
    Invalid RAB ParametersCombination
    The action failed dueto invalid RAB parameters combination.
    Invalid RAB ParametersValue
    The action failed dueto invalid RAB parameters value.
    Iu UP Failure
    The action failed dueto Iu UP failure.
    No remaining RAB
    The reason for theaction is no remaining RAB.
    RAB Pre-empted
    The reason for theaction is that RAB is pre-empted.
    Radio Connection WithUE Lost
    The action isrequested due to losing radio connection to the UE
    Release Due To UEGenerated Signalling Connection Release
    Release requested dueto UE generated signalling connection release.
    Release Due To UTRANGenerated Reason
    Release is initiateddue to UTRAN generated reason.
    Relocation Cancelled
    The reason for theaction is relocation cancellation.
    Relocation Desirablefor Radio Reasons
    The reason forrequesting relocation is radio related.
    Relocation Failure InTarget CN/RNC Or Target System
    Relocation failed dueto a failure in target CN/RNC or target system.
    Relocation NotSupported In Target RNC Or Target System
    Relocation failedbecause relocation was not supported in target RNC or target system.
    Relocation Target notallowed
    Relocation to theindicated target cell is not allowed for the UE in question.
    Relocation Triggered
    The action failed dueto relocation.
    Repeated IntegrityChecking Failure
    The action isrequested due to repeated failure in integrity checking.
    Request Superseded
    The action failedbecause there was a second request on the same RAB.
    Requested CipheringAnd/Or Integrity Protection Algorithms Not Supported
    The UTRAN or the UE isunable to support the requested ciphering and/or integrity protectionalgorithms.
    Requested GuaranteedBit Rate For DL Not Available
    The action failedbecause requested guaranteed bit rate for DL is not available.
    Requested GuaranteedBit Rate For UL Not Available
    The action failedbecause requested guaranteed bit rate for UL is not available.
    Requested GuaranteedBit Rate Not Available
    The action failedbecause requested guaranteed bit rate is not available.
    Requested InformationNot Available
    The action failedbecause requested information is not available.
    Requested Maximum BitRate For DL Not Available
    The action failedbecause requested maximum bit rate for DL is not available.
    Requested Maximum BitRate For UL Not Available
    The action failedbecause requested maximum bit rate for UL is not available.
    Requested Maximum BitRate Not Available
    The action failedbecause requested maximum bit rate is not available.
    Requested Request TypeNot Supported
    The RNC is notsupporting the requested location request type either because it doesn’tsupport the requested event or it doesn’t support the requested report area.
    Location ReportingCongestion
    Theaction was not performed due to an inability to support location reportingcaused by overload.

    Requested TrafficClass Not Available
    The action failedbecause requested traffic class is not available.
    Requested TransferDelay Not Achievable
    The action failedbecause requested transfer delay is not achievable.
    Resource OptimisationRelocation
    The reason forrequesting relocation is resource optimisation.
    Successful Relocation
    The reason for theaction is completion of successful relocation.
    Time CriticalRelocation
    Relocation isrequested for time critical reason i.e. this cause value is reserved torepresent all critical cases where the connection is likely to be dropped ifrelocation is not performed.
    TQUEUINGExpiry
    Theaction failed due to expiryof the timer TQUEUING.
    TRELOCallocExpiry
    Relocation ResourceAllocation procedure failed due to expiry of the timer TRELOCalloc.
    TRELOCcompleteExpiry
    The reason for theaction is expiry of timer TRELOCcomplete.
    TRELOCoverallExpiry
    The reason for theaction is expiry of timer TRELOCoverall.
    TRELOCprepExpiry
    Relocation Preparationprocedure is cancelled when timer TRELOCprep expires.
    Unable To EstablishDuring Relocation
    RAB failed toestablish during relocation because it cannot be supported in the target RNC or the RAB didnot exist in the source RNC.
    Unknown Target RNC
    Relocation rejectedbecause the target RNC is not known to the CN.
    User Inactivity
    The action isrequested due to user inactivity on one or several non real time RABs e.g. inorder to optimise radio resource.
    User Plane VersionsNot Supported
    The action failedbecause requested user plane versions were not supported.
    RNC unable toestablish all RFCs
    RNC couldn’t establishall RAB subflow combinations indicated within the RAB Parameters IE.
    Reduce Load in ServingCell
    Load on serving cell needsto be reduced.
    No Radio ResourcesAvailable in Target Cell
    Load on target cell istoo high.
    GERAN Iu-mode failure
    The RABestablishment/modification/relocation failed because the GERAN BSC cannotprovide an appropriate RAB due to limited capabilities within GERAN.
    Access Restricted Dueto Shared Networks
    Access is notpermitted in the cell due to Shared Networks.
    Traffic Load In The Target Cell Higher Than In The Source Cell
    Relocation to reduceload in the source cell is rejected, as the target cell’s traffic load ishigher than that in the source cell.
    MBMS - No Multicast Service For This UE
    The request for theMulticase Service list of one UE was not fulfilled because the UE does nothave any active multicast service.
    MBMS - Unknown UE ID
    The request for theMulticase Service list of one UE was not fulfilled because the CN does notknow the UE.
    Successful MBMS Session Start - No Data Bearer Necessary
    The MBMS Session Startprocedure was successfully performed, but the RNC does not have any interestedUE.
    MBMS - Superseded Due To NNSF
    The MBMS Session Startprocedure was rejected because of successful operation towards another CNnode.
    MBMS - UE Linking Already Done
    The UE linking failed,because the UE has already been linked to the given Multicast service.
    MBMS - UE De-Linking Failure - No Existing UE Linking
    The UE de-linkingfailed, because the UE had not been linked to the given Multicast service.
    TMGI Unknown
    The requested MBMSaction failed because the indicated TMGI is unknown.
    Successful MBMS Session Start – IP Multicast Bearer established
    The RNC was able tojoin the indicated IP Multicast Group.
    Radio Network Layercause extension
    Meaning
    IP Multicast Address And APN Not Valid
    The MBMS registrationfailed because the IP Multicast Address and APN are not valid.
    MBMS De-Registration Rejected Due To Implicit Registration
    The MBMSDe-registration was rejected because of implicit registration.
    MBMS - Request Superseded
    The MBMS Registrationor De-registration was superseded due to another ongoing procedure.
    MBMS De-Registration During Session Not Allowed
    The MBMSDe-registration is not allowed during the MBMS session.
    MBMS - No Data Bearer Necessary
    The RNC no longer haveany UEs interested in the MBMS data bearer.
    Periodic Location Information not Available

    No UE positionestimate was available when the periodic report was triggered.
    GTP Resources Unavailable
    The RNC initiates RABRelease Request procedure with this error cause value if it received a GTP-Uerror indication.
    TMGI in Use and overlapping MBMS Service Area

    The RNC has an MBMSSession up and running with that TMGI, a parallel MBMS session with the sameTMGI in another overlapping MBMS Service Area is not allowed.
    MBMS - No Cell in MBMS Service Area
    The RNC does not haveany cell of the indicated MBMS Service Area.
    No Iu CS UP relocation

    The relocation is triggered by CS call and the sourceRNC has no Iu CS user plane.
    CS Fallback triggered
    The relocation was triggered for CS Fallbackreason at the source side.



    Transport Layer cause
    Meaning
    Iu TransportConnection Failed to Establish
    Theaction failed because the Iu Transport Network Layer connection could not beestablished.

    Signalling TransportResource Failure
    Signallingtransport resources have failed (e.g. processor reset).



    NAS cause
    Meaning
    Normal Release
    The release is normal.
    User Restriction StartIndication
    A location report isgenerated due to entering a classified area set by O&M.
    User Restriction EndIndication
    A location report isgenerated due to leaving a classified area set by O&M.



    Protocol cause
    Meaning
    Abstract Syntax Error(Reject)
    The received messageincluded an abstract syntax error and the concerning criticality indicated"reject".
    Abstract Syntax Error(Ignore And Notify)
    The received messageincluded an abstract syntax error and the concerning criticality indicated"ignore and notify".
    Abstract Syntax Error(Falsely Constructed Message)
    The received messagecontained IEs or IE groups in wrong order or with too many occurrences.
    Message Not CompatibleWith Receiver State
    The received messagewas not compatible with the receiver state.
    Semantic Error
    The received messageincluded a semantic error.
    Transfer Syntax Error
    The received messageincluded a transfer syntax error.



    Miscellaneous cause
    Meaning
    Network Optimisation
    The action isperformed for network optimisation.
    No Resource Available
    No requested resourceis available.
    O&M Intervention
    The action is due toO&M intervention.
    Unspecified Failure
    Sent when none of thespecified cause values applies.

    对本帖内容的看法? 我要点评

     
    [2分钟拥有VIP权限和充足威望,可下载站内任何资料] [快速找到一份高薪的通信行业职位]
    ebrain68
    银牌会员
    鎵嬫満鍙风爜宸查獙璇


     发短消息    关注Ta 

    积分 2934
    帖子 353
    威望 84712 个
    礼品券 169 个
    专家指数 1169
    注册 2008-3-10
    专业方向 
    回答问题数 0
    回答被采纳数 0
    回答采纳率 0%
     
    发表于 2012-03-26 23:22:33 
    楼主还是找找哪个原因的具体解释吧

    对本帖内容的看法? 我要点评

     
    热点: 通信招聘职位 | 网络优化全集 | WCDMA精品 | TD-SCDMA学习资料 | EVDO | MGW媒体网关资料
    cz_pcking
    中级会员



     发短消息    关注Ta 

    积分 889
    帖子 35
    威望 1702 个
    礼品券 5 个
    专家指数 13
    注册 2009-3-4
    专业方向  WCDMA网络优化
    回答问题数 0
    回答被采纳数 0
    回答采纳率 0%
     
    发表于 2012-03-27 10:29:51  QQ
    奇怪呀!从信令流程上看,UE回复ACK了,证明一次通话建立完成,怎么会影响RRC&RAB建立成功率呢???要影响也是影响掉话率呀,求真相!!!1

    对本帖内容的看法? 我要点评

     
    热点: 通信招聘职位 | 网络优化全集 | WCDMA精品 | TD-SCDMA学习资料 | EVDO | MGW媒体网关资料
    xiaogang99
    金牌会员



     发短消息    关注Ta 

    积分 5252
    帖子 396
    威望 46180 个
    礼品券 10 个
    专家指数 -72
    注册 2009-2-24
    专业方向  WBTS Vertification
    回答问题数 0
    回答被采纳数 0
    回答采纳率 0%
     
    发表于 2012-03-27 17:56:15  只看楼主 
    问题已经找到了啊,MSS 升级后RNC 版本不匹配

    对本帖内容的看法? 我要点评

     
    热点: 通信招聘职位 | 网络优化全集 | WCDMA精品 | TD-SCDMA学习资料 | EVDO | MGW媒体网关资料
    ebrain68
    银牌会员
    鎵嬫満鍙风爜宸查獙璇


     发短消息    关注Ta 

    积分 2934
    帖子 353
    威望 84712 个
    礼品券 169 个
    专家指数 1169
    注册 2008-3-10
    专业方向 
    回答问题数 0
    回答被采纳数 0
    回答采纳率 0%
     
    发表于 2012-03-27 19:49:36 
    hehe,版本不匹配在哪里?哪个接口的哪个message的哪个IE?

    对本帖内容的看法? 我要点评

     
    [2分钟拥有VIP权限和充足威望,可下载站内任何资料] [快速找到一份高薪的通信行业职位]

    快速回复主题    
    标题
    内容
     上传资料请点左侧【添加附件】

    当前时区 GMT+8, 现在时间是 2026-06-20 22:21:02
    渝ICP备11001752号  Copyright @ 2006-2016 mscbsc.com  本站统一服务邮箱:mscbsc@163.com

    Processed in 0.658927 second(s), 37 queries , Gzip enabled
    TOP
    清除 Cookies - 联系我们 - 移动通信网 - 移动通信论坛 - 通信招聘网 - Archiver