omacp data
来源:互联网 发布:波士顿矩阵图怎么画 编辑:程序博客网 时间:2024/06/15 00:45
Example 1
This example shows a provisioning document containing infrastructure information related to a single logical and physical
WSP proxy for a service domain with a single access point.
<?xml version="1.0"?><wap-provisioningdoc version="1.0"><characteristic type="PXLOGICAL"><parm name="PROXY-ID" value="170.187.51.4" /><parm name="NAME" value="BankMainProxy" /><parm name="STARTPAGE" value="http://www.bank.com/startpage.wml" /><characteristic type="PXAUTHINFO"><parm name="PXAUTH-TYPE" value="HTTP-BASIC" /><parm name="PXAUTH-ID" value="pxusername" /><parm name="PXAUTH-PW" value="pxuserpassw" /></characteristic><characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="PROXY 1" /><parm name="DOMAIN" value="www.bank.com/" /><parm name="PXADDR" value="170.187.51.3" /><parm name="PXADDRTYPE" value="IPV4" /><parm name="TO-NAPID" value="INTERNET" /><parm name="TO-NAPID" value="NAP1" /><characteristic type="PORT"><parm name="PORTNBR" value="9203" /></characteristic></characteristic></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP1" /><parm name="BEARER" value="GSM-CSD" /><parm name="NAME" value="MY ISP CSD" /><parm name="NAP-ADDRESS" value="+35808124002" /><parm name="NAP-ADDRTYPE" value="E164" /><parm name="CALLTYPE" value="ANALOG-MODEM" /><characteristic type="NAPAUTHINFO"><parm name="AUTHTYPE" value="PAP" /><parm name="AUTHNAME" value="wwwmmmuser" /><parm name="AUTHSECRET" value="wwwmmmsecret" /></characteristic><characteristic type="VALIDITY"><parm name="COUNTRY" value="228" /><parm name="NETWORK" value="001" /></characteristic></characteristic></wap-provisioningdoc>
example2:
Infrastructure information with two bearers and thus two network access points
In the above example, bearer selection policies for GSM-CSD and GSM-SMS are shown.
The document provides information on how to access the default gateway via two NAP’s. Note that complete information on
NAP’s as well as the physical proxies is given since it is not known in advance how much knowledge the ME has about the
infrastructure.
<?xml version="1.0"?><wap-provisioningdoc version="1.1"><characteristic type="PXLOGICAL"><parm name="PROXY-ID" value="170.187.51.4" /><parm name="NAME" value="DefaultProxy" /><parm name="STARTPAGE" value="http://www.operator.com/start.wml" /><characteristic type="PXAUTHINFO"><parm name="PXAUTH-TYPE" value="HTTP-BASIC" /><parm name="PXAUTH-ID" value="pxusername" /><parm name="PXAUTH-PW" value="pxuserpassw" /></characteristic><characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="PROXY 1" /><parm name="DOMAIN" value=" " /><parm name="PXADDR" value="221.125.51.4" /><parm name="PXADDRTYPE" value="IPV4" /><parm name="PXADDR-FQDN" value="proxy1.operator.com" /><parm name="TO-NAPID" value="NAP1" /><characteristic type="PORT"><parm name="PORTNBR" value="9203" /></characteristic></characteristic><characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="PROXY 2" /><parm name="DOMAIN" value="/SMSContent/" /><parm name="DOMAIN" value="sms.operator.com/" /><parm name="PXADDR" value="9400410" /><parm name="PXADDRTYPE" value="E164" /><parm name="TO-NAPID" value="NAP2" /><characteristic type="PORT"><parm name="PORTNBR" value="9201" /></characteristic></characteristic></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP1" /><parm name="BEARER" value="GSM-CSD" /><parm name="NAME" value="ANY NAME 1" /><parm name="NAP-ADDRESS" value="+4520671023" /><parm name="NAP-ADDRTYPE" value="E164" /><parm name="CALLTYPE" value="ANALOG-MODEM" /><parm name="LINKSPEED" value="AUTOBAUDING" /><characteristic type="NAPAUTHINFO"><parm name="AUTHTYPE" value="PAP" /><parm name="AUTHNAME" value="roamwapuser" /><parm name="AUTHSECRET" value="roamwappassw" /></characteristic><characteristic type="VALIDITY"><parm name="COUNTRY" value="228" /></characteristic></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP2" /><parm name="BEARER" value="GSM-SMS" /><parm name="NAME" value="ANY NAME 2" /><parm name="NAP-ADDRESS" value="+35809503401" /><parm name="NAP-ADDRTYPE" value="E164" /></characteristic></wap-provisioningdoc>
example3:
Infrastructure information related to several logical WSP proxies for a service domain with multiple access points. Vendor
specific configuration data is also supplied. This situation is typically encountered when fetching provisioning documents
from a smart card [PROVSC].
<?xml version="1.0"?><wap-provisioningdoc version="1.1"><characteristic type="PXLOGICAL"><parm name="PROXY-ID" value="www.operator.com" /><parm name="PROXY-PW" value="proxypasswd" /><parm name="PPGAUTH-TYPE" value="HTTP-BASIC" /><parm name="NAME" value="DefaultProxy" /><parm name="MASTER" /><parm name="PUSHENABLED" value="1" /><parm name="STARTPAGE" value="http://www.operator.com/start.wml" /><characteristic type="PXAUTHINFO"><parm name="PXAUTH-TYPE" value="HTTP-BASIC" /><parm name="PXAUTH-ID" value="httpusername" /><parm name="PXAUTH-PW" value="httpuserpassw" /></characteristic><characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="PROXY 1" /><parm name="DOMAIN" value=" " /><parm name="PXADDR" value="215.221.51.5" /><parm name="PXADDRTYPE" value="IPV4" /><parm name="TO-NAPID" value="NAP1" /><characteristic type="PORT"><parm name="PORTNBR" value="9203" /></characteristic></characteristic><characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="PROXY 2" /><parm name="DOMAIN" value=" " /><parm name="DOMAIN" value="/SMS/" /><parm name="PXADDR" value="9201611" /><parm name="PXADDRTYPE" value="E164" /><parm name="TO-NAPID" value="NAP3" /><characteristic type="PORT"><parm name="PORTNBR" value="9201" /></characteristic></characteristic></characteristic><characteristic type="PXLOGICAL"><parm name="PROXY-ID" value="163.187.51.4" /><parm name="NAME" value="EcommerceProxy" /><parm name="STARTPAGE" value="http://www.ecom.com/startpage.wml" /><characteristic type="PXAUTHINFO"><parm name="PXAUTH-TYPE" value="HTTP-BASIC" /><parm name="PXAUTH-ID" value="httpusername" /><parm name="PXAUTH-PW" value="httpuserpassw" /></characteristic><characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="PROXY 1" /><parm name="DOMAIN" value="www.ecom.com/" /><parm name="PXADDR" value="166.224.1.68" /><parm name="PXADDRTYPE" value="IPV4" /><parm name="TO-NAPID" value="NAP1" /><parm name="TO-NAPID" value="NAP2" /><characteristic type="PORT"><parm name="PORTNBR" value="9203" /></characteristic></characteristic><characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="PROXY 2" /><parm name="DOMAIN" value="www.ecom.com/SMSContent/" /><parm name="DOMAIN" value="www.ecom.com/SMS/" /><parm name="PXADDR" value="9400410" /><parm name="PXADDRTYPE" value="E164" /><parm name="TO-NAPID" value="NAP3" /><parm name="TO-NAPID" value="NAP4" /><characteristic type="PORT"><parm name="PORTNBR" value="9203" /></characteristic></characteristic></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP1" /><parm name="BEARER" value="GSM-CSD" /><parm name="NAME" value="ANY NAME 3" /><parm name="NAP-ADDRESS" value="+35808124303" /><parm name="NAP-ADDRTYPE" value="E164" /><parm name="CALLTYPE" value="ANALOG-MODEM" /><characteristic type="NAPAUTHINFO"><parm name="AUTHTYPE" value="PAP" /><parm name="AUTHNAME" value="wapuser" /><parm name="AUTHSECRET" value="wappassw" /></characteristic><characteristic type="VALIDITY"><parm name="COUNTRY" value="228" /><parm name="NETWORK" value="001" /></characteristic></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP2" /><parm name="BEARER" value="GSM-CSD" /><parm name="NAME" value="ANY NAME 4" /><parm name="NAP-ADDRESS" value="+35808124002" /><parm name="NAP-ADDRTYPE" value="E164" /><parm name="CALLTYPE" value="ANALOG-MODEM" /><parm name="LINKSPEED" value="AUTOBAUDING" /><characteristic type="NAPAUTHINFO"><parm name="AUTHTYPE" value="PAP" /><parm name="AUTHNAME" value="wwwmmmuser" /><parm name="AUTHSECRET" value="wwwmmmsecret" /></characteristic><characteristic type="VALIDITY"><parm name="COUNTRY" value="113" /><parm name="NETWORK" value="004" /></characteristic></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP3" /><parm name="BEARER" value="GSM-SMS" /><parm name="NAME" value="ANY NAME 5" /><parm name="NAP-ADDRESS" value="+35809503401" /><parm name="NAP-ADDRTYPE" value="E164" /></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP4" /><parm name="BEARER" value="GSM-SMS" /><parm name="NAME" value="ANY NAME 6" /><parm name="NAP-ADDRESS" value="+36209400400" /></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="INTERNET" /><parm name="BEARER" value="GSM-GPRS" /><parm name="NAME" value="MY ISP GPRS" /><parm name="NAP-ADDRESS" value="MYISP.gprs" /><parm name="NAP-ADDRTYPE" value="APN" /><parm name="DELIVERY-ERR-SDU" value="3" /><parm name="RESIDUAL-BER" value="70" /><parm name="SDU-ERROR-RATIO" value="6" /><parm name="TRAFFIC-CLASS" value="60" /><parm name="TRAFFIC-HANDL-PRIO" value="1" /><parm name="MAX-BITRATE-DNLINK" value="8" /><characteristic type="NAPAUTHINFO"><parm name="AUTHTYPE" value="PAP" /><parm name="AUTHNAME" value="wwwmmmuser" /><parm name="AUTHSECRET" value="wwwmmmsecret" /></characteristic></characteristic><characteristic type="VENDORCONFIG"><parm name="NAME" value="PRODUCT" /><parm name="RINGTONES" value="http://www.sonera.fi/music.wml" /></characteristic></wap-provisioningdoc>
example4:
Bootstrap information.
<?xml version="1.0"?><wap-provisioningdoc version="1.1"><characteristic type="BOOTSTRAP"><parm name="CONTEXT-ALLOW" value="0" /><parm name="PROVURL" value="http://www.operator.com/TPS/" /></characteristic><characteristic type="PXLOGICAL"><parm name="PROXY-ID" value="170.187.51.4" /><parm name="PROXY-PW" value="proxypasswd" /><parm name="PPGAUTH-TYPE" value="HTTP-DIGEST" /><parm name="NAME" value="TrustedProvProxy" /><parm name="TRUST" /><parm name="PUSHENABLED" value="1" /><parm name="STARTPAGE" value="http://www.operator.com/home.wml" /><characteristic type="PXAUTHINFO"><parm name="PXAUTH-TYPE" value="HTTP-BASIC" /><parm name="PXAUTH-ID" value="subscribername" /><parm name="PXAUTH-PW" value="subscriberpassw" /></characteristic><characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="PROXY 1" /><parm name="DOMAIN" value=".operator.com/" /><parm name="PXADDR" value="221.125.33.5" /><parm name="PXADDRTYPE" value="IPV4" /><parm name="TO-NAPID" value="NAP1" /></characteristic><characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="PROXY 2" /><parm name="DOMAIN" value="www.operator.com/" /><parm name="PXADDR" value="9201612" /><parm name="PXADDRTYPE" value="E164" /><parm name="TO-NAPID" value="NAP2" /></characteristic></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP1" /><parm name="BEARER" value="GSM-CSD" /><parm name="NAME" value="ANY NAME 7" /><parm name="NAP-ADDRESS" value="+35808124303" /><parm name="NAP-ADDRTYPE" value="E164" /><parm name="CALLTYPE" value="ANALOG-MODEM" /><characteristic type="NAPAUTHINFO"><parm name="AUTHTYPE" value="PAP" /><parm name="AUTHNAME" value="wapuser" /><parm name="AUTHSECRET" value="wappassw" /></characteristic><characteristic type="VALIDITY"><parm name="COUNTRY" value="228" /><parm name="NETWORK" value="001" /></characteristic></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP2" /><parm name="BEARER" value="GSM-SMS" /><parm name="NAME" value="ANY NAME 8" /><parm name="NAP-ADDRESS" value="+35809503401" /></characteristic></wap-provisioningdoc>
example 5:
This example shows a provisioning document containing infrastructure information for a client that accesses the internet
directly without a proxy.
<?xml version="1.0"?><wap-provisioningdoc version="1.1"><characteristic type="NAPDEF"><parm name="NAPID" value="INTERNET" /><parm name="BEARER" value="GSM-GPRS" /><parm name="NAME" value="MY ISP GPRS" /><parm name="NAP-ADDRESS" value="MYISP.gprs" /><parm name="NAP-ADDRTYPE" value="APN" /></characteristic><characteristic type="BOOTSTRAP"><parm name="CONTEXT-ALLOW" value="0" /><parm name="PROVURL" value="http://www.operator.com/TPS/" /></characteristic></wap-provisioningdoc>
example 6:
<?xml version="1.0"?><wap-provisioningdoc version="1.1"><characteristic type="NAPDEF"><parm name="NAPID" value="INTERNET" /><parm name="BEARER" value="CDMA2000-1X-SIMPLE-IP" /><parm name="NAME" value="MY ISP CDMA2000-1X Simple IP" /><parm name="NAP-ADDRESS" value="166.224.1.1" /><parm name="NAP-ADDRTYPE" value="IPV4" /><characteristic type="NAPAUTHINFO"><parm name="AUTHTYPE" value="CHAP" /><parm name="AUTHNAME" value="john@carrier.com" /><parm name="AUTHSECRET" value="xyzabc" /></characteristic><characteristic type="NAPAUTHINFO"><parm name="AUTHTYPE" value="PAP" /><parm name="AUTHNAME" value="john@carrier.com" /><parm name="AUTHSECRET" value="xyzabc" /></characteristic></characteristic><characteristic type="BOOTSTRAP"><parm name="CONTEXT-ALLOW" value="0" /><parm name="PROVURL" value="http://www.operator.com/TPS/" /></characteristic></wap-provisioningdoc>
example 7:
This example shows a provisioning document containing network access point information for a client that accesses the
internet using CDMA2000-1X-MOBILE-IP. Two NAPDEF definitions are provided – the first one is for primary HA and the
second for secondary HA. Primary/secondary order is determined by the order in which the NAPDEF definition occurs in the
document as described in the [ProvUAB] specification. Primary HA uses different NAPAUTHINFO definitions for AAA and
HA, and the secondary HA uses the same NAPAUTHINFO definition for both AAA and HA.
未完待续。。。
后面有时间详细整理
这段代码用来在 applicationNode 中 获取application 中隐含的 napid , 包括由toProxyNode 中的
try{ obj.napIds = []; var toProxyNodes = applicationNode.querySelectorAll('parm[name="TO-PROXY"]'); if (toProxyNodes) { obj.toProxyNodes =toProxyNodes; for (var i = 0; i < toProxyNodes.length; i++) { var toProxyNode = toProxyNodes[i]; var pxPhysicalNodes = this.getPxPhysicalNodes(toProxyNode); for (var j = 0; j < pxPhysicalNodes.length; j++){ var pxPhysicalNode= pxPhysicalNodes[j]; var toNapIds= pxPhysicalNode.querySelectorAll('parm[name="TO-NAPID"]'); if (toNapIds) { for (var k = 0; k < toNapIds.length; k++){ var toNapId = toNapIds[k]; var napId = toNapId.getAttribute('value'); if(napId){ obj.napIds.push(napId); } } } } } }}catch(error){ alert("in parseApplicaton Node error="+error);}
- omacp data
- OMACP密码类型
- OMACP密码类型
- OMACP功能说明以及自己做的一个模拟发送OMACP消息的功能类
- Omacp收到network Pin之后,会要求输入Pin码
- android mms Apn的omacp xml文件样本
- 由于Email参数SMTP_APPID不同,导致Omacp配置email失败的修改方法
- data
- data ()
- data
- Data
- data
- data
- data
- data
- data
- <data>
- data
- 设计模式--单例模式
- 接下来三个月要做的事
- 二分图最大匹配:网络流做法——模板题
- 反转链表
- 深入理解Linux操作系统守护进程的意义
- omacp data
- Redis入门指南之数据类型
- httpcomponents-client-4.5.3 学习笔记(2) 1.2 HttpClient接口
- xpath抓取代理IP并检测IP的有效性
- jsonp详解
- jQuery实现表格冻结行和列
- 快速排序算法C++实现
- android 简单实现,微信第三方登录
- 图解集合 4 :HashMap