Wap网页代理服务器,WAP Proxy

最新推荐文章于 2025-03-10 17:49:03 发布

weixin_30273263

最新推荐文章于 2025-03-10 17:49:03 发布

阅读量296

点赞数

文章标签： Wap网页代理服务器

本文介绍了在实现移动运营商网络的MMSC（多媒体消息服务中心）时，用户认证与WAP网关如何配合工作。讨论了MM1协议在移动设备与MMSC之间的交易中作用，以及如何通过HTTP头信息和HTTP Cookie来识别和验证订阅者。此外，还提到了WAP网关支持MMS和一般浏览器流量的部署策略。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Posted by brett on Jul 24, 2015 in Support Blog

When implementing an MMSC for a mobile operator network, one of the most confusing concepts is how user authentication is usually performed in conjunction with a WAP Gateway.

MMS uses the MM1 Protocol (OMA MMS Encapsulation) for transactions between a mobile device and the MMSC. This protocol does not define how the MMSC identifies and authenticates the subscriber when the MMS client on a mobile...

Posted by brett on Oct 19, 2011 in Support Blog

NowWAP HTTP Header Enrichment (HHE) is described in more detail in the following article: https://nowsms.com/nowwap-and-http-header-enrichment

In addition to the HHE issues discussed in that article, we frequently receive questions about using HTTP Cookie headers for identifying the MSISDN.

These questions are usually asked for the following reasons:

Customers migrating from or augmenting an...

Posted by bryce on Feb 23, 2011 in Support Blog

The HTTP Header Enrichment (HHE) capability provides solutions for a content provider to identify a subscriber.

Basic HHE allows the subscriber to be identified by their MSISDN.

Aliased HHE allows the subscriber to be identified without divulging the subscriber’s MSISDN.

A standard feature of the NowWAP Proxy is to provide Basic HTTP Header Enrichment to facilitate operator billing for...

Posted by brett on Nov 19, 2010 in Support Blog

It has come to our attention that the default configuration setting for the NowWAP WAP Gateway blocks users from connecting to BlackBerry App World.

The reason for this seems to be some unusual communication patterns between the handset and the App World server. The handset attempts to created a tunneled connection to the HTTP port (80) of the BlackBerry App World server.

Symptoms of the problem...

Posted by bryce on Oct 29, 2009 in Support Blog

NowSMS supports the Open Mobile Alliance (OMA) Push Access Protocol (PAP), which allows other applications to use NowSMS as a WAP Push Proxy Gateway (PPG).

Even though NowSMS has its own MMSC capability, we do have customers who are using NowSMS as a push proxy gateway for another vendor’s MMSC.

In addition to providing PPG support for MMS, NowSMS can be used as a push proxy gateway for...

Posted by bryce on Jul 7, 2008 in Support Blog

Smaller mobile operators often ask us how to deploy a single WAP Gateway (or WAP Proxy if you prefer that terminology, as our marketing folks seem to prefer) to deploy both MMS traffic and general browser traffic.

Of course, technically there is no reason that a single WAP Gateway can’t support both types of traffic. So if you’re not a mobile operator, you’re probably wondering...

Posted by bryce on Jun 23, 2008 in Support Blog

The recent postings about multiple server redundant NowSMS or NowWAP configurations have generated a lot of questions from existing customers about how to migrate an existing installation to a multiple server configuration.

Migrating an existing NowWAP installation to a multiple server configuration is the easiest task to explain. That’s because there is no shared data storage requirement,...