mobile手机拦截彩像

1. 设定Content type   application/vnd.wap.mms-message

2. 设定Appid  x-wap-application:mms.ua

 

 

 

参考文章

（http://www.nowsms.com/discus/messages/132/518.html）

If you want to generate the push yourself, you'll need to download the WAP specifications from the Open Mobile Alliance (http://www.openmobilealliance.org ) site.

When you generate a WAP push, you are generating a Push PDU as documented in the WSP (Wireless Session Protocol) specification.

The push PDU is sent via connectionless WSP to the push port (2948) on the recipient device.

Connectionless WSP is transported over WDP (the Wireless Datagram Protocol). The WDP specification specifies the encoding for WDP over GSM SMS. To support the specification of a destination port, the WDP encoding for GSM SMS uses the SMS User Data Header (UDH). Details are in the WDP specification, and the approach is compatible with the UDH encoding used by Nokia Smart Messaging (just that a specific port number, 2948, is reserved for WAP Push).

WDP and WSP specify how to construct the headers for the WAP push message. But you'll also need some content. The two most common push content formats are "Service Indication" and "Service Load", which are documented in the WAP-167-ServiceInd and WAP-168-ServiceLoad specifications, respectively. These two content formats are XML-based, and the XML gets encoded in a WBXML (Wireless Binary XML, yet another WAP spec) format ... the ServiceInd and ServiceLoad specs have examples of that encoding specific to those content types.

WAP push is also used for MMS notifications. The MMS notification is simply an alternative content type (in the same way that ServiceInd and ServiceLoad are push content types). There are some other discussions out here discussing MMS notification formats that you might find interesting for their references to the header formats.

http://www.nowsms.com/discus/messages/1/395.html
http://www.nowsms.com/discus/messages/1/462.html
http://www.nowsms.com/discus/messages/12/208.html
http://www.nowsms.com/discus/messages/1/136.html#POST1623

 

（http://www.nowsms.com/discus/messages/12/799.html）

Sos --- How to register mms client?

 

Posted on Friday, September 26, 2003 - 07:49 am:    Hi,i want write a program to receive MMS, but what should i register my program? i mean, which registery should i write? thanks in advance.
Anonymous	Posted on Friday, September 26, 2003 - 09:17 am:    duno what u mean
newbie	Posted on Friday, September 26, 2003 - 10:33 am:    i mean, after writing a program, you must register it to receive mms in advance. or your program will n't get the mms push notification message. i want to know how to register?
Bryce Norwood - NowSMS Support	Posted on Saturday, October 11, 2003 - 09:11 pm:    What are you registering with? What platform is the client running on? This would seem to be a question that is specific to whatever platform your client software is written for ...
Anonymous	Posted on Monday, October 13, 2003 - 02:40 am:    PocketPC
newbie	Posted on Monday, October 13, 2003 - 06:10 am:    Hi,bryce, thanks for your patient reply! my clint is running on Smartphonw2002,and how it get MMS notification messge? I have register appid and content type as following : AppID: MyClient.exe content-type: application/vnd.wap.mms-message but when a mms notication arrives, mobile can't call myclient.exe to receive it. why? what should i do? thanks a lot.
Bryce Norwood - NowSMS Support	Posted on Tuesday, October 14, 2003 - 02:13 am:    Well, you got me there. I'm definitely not an expert on either Pocket PC or MS Smartphone development. The Pocket PC 2003 API defines an API called PushRouter_RegisterClient, which looks like what you would use: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/guide_ppc/htm/_ mdref_pushrouter_registerclient.asp I'm not sure if that API is also supported on the Smartphone platform. If that is the API that you are attempting to use (or a similar one), then you might be confused about the meaning of "AppID". In this context, it is not the name of your executable (szPath has the executable name including path). Instead, it is referring to a push application id ... a list of which you can find on this page: http://www.wapforum.org/wina/push-app-id.htm Unfortunately, the MS API documentation is not clear on how you would specify an appid using the binary value (only the text).

 

AppID 如下：

（http://www.wapforum.org/wina/push-app-id.htm）

PUSH Application ID

WINA assigns numbers for registered PUSH Application IDs.  The number space is divided into three segments:

• 0x0000 - 0x7FFF: Well-known values, managed specified by the WAP working group processes. The application as represented by the URI must be defined in any WAP specification. URNs are required for URI and NID in URN [ rfc2141 ] MUST be "x-wap-application".
• 0x8000 - 0xFF000000: Reserved values, registered and managed by WINA. URN with NID "x-wap-application" cannot be used.
• 0x04000 - 0x1FFFFF: Experimental values, registered by WINA only for advisory purposes. URIs in the Well-Known and Reserved category SHOULD NOT be used.

In order to register a PUSH Application identifier, a short description of its use must be provided. 

See WAP-189 PUSH OTA Specification. for more information on PUSH Application identifiers.

Well Known Values

URN	Number	Description
x-wap-application:*	0x00	Any Application
x-wap-application:push.sia	0x01	WAP Push SIA
x-wap-application:wml.ua	0x02	WML User Agent
x-wap-application:wta.ua	0x03	WTA User Agent
x-wap-application:mms.ua	0x04	This ID will used for application dispatching to MMS User Agent in the handling of MMS notfication using WAP Push. See WAP-206-MMSCTR for more detail.
x-wap-application:push.syncml	0x05	SyncML PUSH Application ID: used to push a SyncML Alert from a SyncML server side. The SyncML Alert is an indication for starting a SyncML session e.g., for data synchronization. Requested by the WAP WAG Synchronisation Drafting Committee .
x-wap-application:loc.ua	0x06	This ID is used for application dispatching to Location User Agent in the handling of Location Invocation document. See WAP-257-LOCPROT for details. Requested by the WAP WAG Location Drafting Committee .
x-wap-application:syncml.dm	0x07	This ID is used for SyncML Device Management. Requested by the SyncML Device Management Expert Group .
x-wap-application:drm.ua	0x08	This ID is used for DRM User Agent. Requested by the WAP WAG Download DC .
x-wap-application:emn.ua	0x09	This ID is used for Email Notification (EMN) User Agent. Requested by the WAP WAG PUSH DC .
x-wap-application:wv.ua	0x0A	This ID is used for Wireless Village (EMN) User Agent. Requested by Wireless Village .

Registered Values

URN	Number	Registrant	Description
x-wap-microsoft:localcontent.ua	0x8000	David Hitchman	is an application to receive pages to be stored and access locally. These are not wta channels. Usually the pages will be downloaded as multi-part mime.
x-wap-microsoft:IMclient.ua	0x8001	David Hitchman	is an application which will act as an instant messaging client on a phone.
x-wap-docomo:imode.mail.ua	0x8002	Hidetoshi Ueno	is used to identify the i-mode mail application user agent on a mobile device.
x-wap-docomo:imode.mr.ua	0x8003	Hidetoshi Ueno	is used to identify the i-mode message request application user agent on a mobile device.
x-wap-docomo:imode.mf.ua	0x8004	Hidetoshi Ueno	is used to identify the i-mode message free application user agent on a mobile device.
x-motorola:location.ua	0x8005	Joby James	is an application that receives message notifications from the location server.
x-motorola:now.ua	0x8006	Joby James	is an application that presents personalized information to the user.
x-motorola:otaprov.ua	0x8007	Joby James	is an application that receives provisioning messages from the server.
x-motorola:browser.ua	0x8008	Joby James	is a web browsing application.
x-motorola:splash.ua	0x8009	Randi Faris	is an application that receives splash screen content from the server.
unused	0x800A
x-wap-nai:mvsw.command	0x800B	Martin Fallenstedt	is used by administrators to issue commands to individual devices.
unused	0x800C through 0x800F
x-wap-openwave:iota.ua	0x8010	Philip Ryan	is used for application dispatching to the IP-based OTA Provisioning Service Agent in the handling of IOTA notfications using WAP Push.

Private or Experimental Values

URN	Number	Registrant	Description