network specifications: att.net, media net, mmode · the att.net browse client , based on the opera...

© 2010 AT&T Knowledge Ventures

AT&T Developer Program

Network Specifications: att.net, MEdia Net, mMode

AT&T Developer Program Document

Document Number 14875

Revision 9.0

Revision Date 02/08/10

Legal Disclaimer

AT&T Proprietary The information contained here is for use by authorized

person only and is not for general distribution AT&T Developer Program Document 14875 Rev. 9.0 ii

This document and the information contained herein (collectively, the "Information") is provided to you (both the individual receiving

this document and any legal entity on behalf of which such individual is acting) ("You" and "Your") by AT&T, on behalf of itself and

its affiliates ("AT&T") for informational purposes only. AT&T is providing the Information to You because AT&T believes the

Information may be useful to You. The Information is provided to You solely on the basis that You will be responsible for making

Your own assessments of the Information and are advised to verify all representations, statements and information before using or

relying upon any of the Information. Although AT&T has exercised reasonable care in providing the Information to You, AT&T does

not warrant the accuracy of the Information and is not responsible for any damages arising from Your use of or reliance upon the

Information. You further understand and agree that AT&T in no way represents, and You in no way rely on a belief, that AT&T is

providing the Information in accordance with any standard or service (routine, customary or otherwise) related to the consulting,

services, hardware or software industries.

AT&T DOES NOT WARRANT THAT THE INFORMATION IS ERROR-FREE. AT&T IS PROVIDING THE INFORMATION TO YOU

"AS IS" AND "WITH ALL FAULTS." AT&T DOES NOT WARRANT, BY VIRTUE OF THIS DOCUMENT, OR BY ANY COURSE OF

PERFORMANCE, COURSE OF DEALING, USAGE OF TRADE OR ANY COLLATERAL DOCUMENT HEREUNDER OR

OTHERWISE, AND HEREBY EXPRESSLY DISCLAIMS, ANY REPRESENTATION OR WARRANTY OF ANY KIND WITH

RESPECT TO THE INFORMATION, INCLUDING, WITHOUT LIMITATION, ANY REPRESENTATION OR WARRANTY OF

DESIGN, PERFORMANCE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, OR

ANY REPRESENTATION OR WARRANTY THAT THE INFORMATION IS APPLICABLE TO OR INTEROPERABLE WITH ANY

SYSTEM, DATA, HARDWARE OR SOFTWARE OF ANY KIND. AT&T DISCLAIMS AND IN NO EVENT SHALL BE LIABLE FOR

ANY LOSSES OR DAMAGES OF ANY KIND, WHETHER DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE,

SPECIAL OR EXEMPLARY, INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS

INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF GOODWILL, COVER, TORTIOUS CONDUCT OR OTHER

PECUNIARY LOSS, ARISING OUT OF OR IN ANY WAY RELATED TO THE PROVISION, NON-PROVISION, USE OR NON-USE

OF THE INFORMATION, EVEN IF AT&T HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES OR DAMAGES.

Revision History


person only and is not for general distribution AT&T Developer Program Document 14875 Rev. 9.0 iii

© 2010 AT&T Knowledge Ventures. All rights reserved.

AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures.

All marks, trademarks, and product names used in this document are the property of their respective owners.

Date Revision Description

04/18/05 1.0 Initial release for posting on the AT&T Developer Program Web site

04/20/05 2.0 Update Section 3.2 Public IP Addresses for Media Net Gateways and Table 5.

08/17/05 3.0 Updated Sections 3.2 Public IP Addresses for Media Net Gateways and Appendix A mMode vs. Media Net Summary Comparison.

08/24/05 4.0 Updated Sections 3.1 WAP Gateway, 3.1.1.3 Service Identification, Appendix A mMode vs. Media Net Summary Comparison, Appendix B.3 Media Net WAP 1 Client, Appendix B.4 Media Net WAP 2 Client, and Table 4 WAP Gateway-Inserted HTTP Headers (Media Net-specific).

11/21/05 5.0 Update of IP addresses in all sections. Updated Sections 2.1.1.1, 2.2, 3.2, and Appendix A.

03/20/06 6.0 Revise for STC IP ranges and connectivity information for proxied and proxied address space. Add Appendix C. User Agent String Parsing. Revised subscriber identification information and test push address.

10/17/06 7.0 Updated Section 3.2 Public IP Addresses for Media Net Gateways.

11/09/07 8.0 Add Bothell IP ranges.

02/080/10 9.0 New section added for Att.Net specifications. All mMode content archived into appendix. Data center IP addresses updated. Other misc. edits.

Table of Contents


person only and is not for general distribution AT&T Developer Program Document 14875 Rev. 9.0 iv

1. Introduction................................................................................................................ 1 1.1 Contact Information ................................................................................................... 1 1.2 Terms and Acronyms ................................................................................................ 1

2. att.net Service ........................................................................................................... 2 2.1.1 Browse Clients .............................................................................................................2

2.2 IP Addresses and Site Specifications ....................................................................... 2 2.3 Push Content and Other WAP-Gateway Services.................................................... 2

3. MEdia Net Service..................................................................................................... 3 3.1 WAP Gateway ........................................................................................................... 3

3.1.1 Pull Content Provider Interface.....................................................................................3 3.1.1.1 HTTP Headers............................................................................................3 3.1.1.2 Subscriber Identification .............................................................................5 3.1.1.3 Service Identification ..................................................................................5

3.1.2 Push Content Provider Interface ..................................................................................6 3.1.3 Developer Gateways ....................................................................................................7 3.1.4 Test/Staging via Production Gateway ..........................................................................7 3.1.5 Gateway Access...........................................................................................................7

3.2 Public IP Addresses for MEdia Net Gateways.......................................................... 7 3.2.1 Home URL Configuration .............................................................................................8

Appendix A. mMode vs. MEdia Net Summary Comparison.......................................................... 9

Appendix B. MEdia Net HTTP Request Examples...................................................................... 11 B.1. MEdia Net WAP 1 Client ......................................................................................... 11 B.2. MEdia Net WAP 2 Client ......................................................................................... 11

Appendix C. mMode HTTP Request Examples........................................................................... 12 C.1. mMode WAP 1 Client .............................................................................................. 12 C.2. mMode WAP 2 Client .............................................................................................. 13

Appendix D. User Agent String Parsing....................................................................................... 14

Appendix E. mMode Service (archived info., ca. 2007)............................................................... 15 E.1. WAP Gateways ....................................................................................................... 15

E.1.1. Pull Content Provider Interface...................................................................................15 E.1.1.1. HTTP Headers..........................................................................................15 E.1.1.2. Subscriber Identification ...........................................................................15 E.1.1.3. Service Identification ................................................................................15

E.1.2. Push Content Provider Interface ................................................................................15 E.1.3. Developer Gateways ..................................................................................................16 E.1.4. Test/Staging via the Production Gateway...................................................................17 E.1.5. Gateway Access.........................................................................................................17

E.2. Public IP Addresses for mMode.............................................................................. 17 E.3. Home URL Configuration ........................................................................................ 18


person only and is not for general distribution AT&T Developer Program Document 14875 Rev. 9.0 1

1. Introduction

This document contains network specifications for AT&T mobile networks:

att.Net – Provides integrated subscriber content services

MEdia™ Net – Supports non att.net services (push CP, other browse types)

mMode – No longer offered. Used by a few legacy subscribers.

1.1 Contact Information If you have comments or questions regarding this document, please send an email, including the document title to [email protected]

1.2 Terms and Acronyms The following table defines terms and acronyms used in this document.

Table 1 Terms and Acronyms

Term or Acronym Definition

CP Content Provider

DNS Domain Naming Services

GPRS General Packet Radio Service

GSM Global System for Mobile Communications

IP Internet Protocol (address)

MAG Mobile Access Gateway

MIDP Mobile Information Device Profile

MMS Multimedia Messaging Service

MSISDN Mobile Station ISDN number

NAT Network Address Translation

OMA Open Mobile Alliance

OS Operating System

PAP Push Access Protocol

PPG Push Proxy Gateway

QOS Quality of Service

SMS Short Message Service (text messaging )

SSL Secure Sockets Layer

SubID Subscriber Identity/Identification

UDP User Datagram Protocol

VPN Virtual Private Network

WAP Wireless Application Protocol

WML WAP Markup Language

WTLS Wireless Transport Layer Security

mailto:[email protected]



2. att.net Service

The att.net platform introduces a new mobile browse client that does not access the internet through WAP gateway – but through a transcoder that is hosted at Motricity.

MEdia Net continues to provide service for all network activity outside of the att.net system – using WAP gateway access.

2.1.1 Browse Clients att.net Opera mini client The att.net browse client , based on the Opera Mini browser has been customized for dedicated use by the att.net service. All att.net interactions with the Motricity-based transcode are done with this client.

Native browsers Mobile devices may also use their own native browser for accessing features such as MEdia Mall, or clickable URLs in text messages. Push content is handles by the native browser.

2.2 IP Addresses and Site Specifications Source IP addresses Your site should receive att.net traffic from the following IP addresses:

Demo site ....... 72.53.194.225

Production ...... 72.53.194.237

Application Testing Only testing on the att.net client on the att.net production browser is required. It is not necessary to test your content on the native browser.

Redirection to Mobile Sites As QWERTY keypads become more common on mobile devices, users often type in URLs to browse to PC-based Web sites which are designed for large screens and may not display properly or legibly on their device. Because of this, AT&T suggests that you redirect your mobile users to your mobile PC site through either user-agent redirection or by redirecting incoming IPs to your mobile site.

2.3 Push Content and Other WAP-Gateway Services All other mobile content traffic, outside of the att.net platform, will continue to be handled with the MEdia Net service as facilitated by the AT&T Eternal Access Gateway (EAG). For information about these topics, please see the MEdia Net section of this document



3. MEdia Net Service

This section outlines network specifications for the MEdia Net service.

3.1 WAP Gateway MEdia Net service is delivered through AT&T WAP gateways configured with Openwave’s Mobile Access Gateway (MAG) and Next Generation Gateways (NGG).

3.1.1 Pull Content Provider Interface Pull content providers serve client-initiated service requests, most commonly for WAP browsing. The interface description here covers the following features:

Information (HTTP headers) passed to the content provider from the client or from the WAP gateway

Methods of identifying the subscriber accessing the service

Methods of differentiating the service to be provided to the client

3.1.1.1 HTTP Headers

Secure Applications for WAP 2 Clients

For WAP 2 clients accessing secure sites via HTTP/SSL (HTTPS), no headers are modified or inserted by the WAP gateway. In these case, a WAP 2 client creates an SSL tunnel through the WAP gateway, preventing the WAP gateway from providing any proxy function other than SSL tunneling. This also prevents the WAP gateway from identifying the user via HTTP header insertion.

See also the white paper, “WAP 2.0 User Identification for Secure Services” at: http://developer.cingular.com/developer/index.jsp?page=toolsTechSection&id=800066.

All Other Client Requests

Based on headers provided in WAP 1 and WAP 2 client requests—including clients for browsing, messaging, and other services — the WAP gateway forwards to content servers the following HTTP header information (Table 2).

Table 2 WAP Gateway-Forwarded HTTP Headers

What How Example Values

Client type, as indicated by client

HTTP header “User-Agent” User-Agent: MOT-V551/ 08.17.0FR MIB/2.2.1 Profile/ MIDP-2.0 Configuration/CLDC-1.0

User agent profile, as indicated by client or config’d in WAP gateway for clients that don’t send this hdr. See Table Note 1.

HTTP header “Profile” (WAP 1) or HTTP header “x-wap-profile” (WAP 2 or WAP 1)

x-wap-profile: "http://motorola.handango.com/ phoneconfig/v551/Profile/v551.rdf"

http://developer.cingular.com/developer/index.jsp?page=toolsTechSection&id=800066




Compatible content types, as indicated by client or translatable by WAP gateway

HTTP header “Accept” See Table Note 2.

Cookies, as indicated by client (WAP 2) or stored in the gateway (WAP 1)

HTTP header “Cookie” or “Cookie2”

Cookie: $Version="1"; B=8g8p6l90lj6hu&b=2; $Path="/"; $Domain=".yahoo.com" Cookie2: $Version="1"

Compatible character sets, as indicated by client

HTTP header “Accept-Charset”

accept-charset: utf-8,*

Compatible language, as indicated by client

HTTP header “Accept-Language”

accept-language: en

Compatible encoding, as indicated by client

HTTP header “Accept-Encoding”

Accept-Encoding: gzip, deflate

Other information as indicated by client

As indicated by client UA-OS: Windows CE (Smartphone) - Version 4.21

TABLE NOTES

NOTE 1. The WAP gateway may forward a modified User Agent Profile header under certain conditions (e.g., when the client-provided User Agent Profile contains errors, or to resolve interoperability or user experience issues).

NOTE 2. The WAP gateway will add the MIME types for content that it can translate into formats supported by the client. For example, text WML (application/vnd.wap.wml) will be added if the client specifies support for compiled WML (application/vnd.wap.wmlc).

Example Accept header. In the following example, t he WAP gateway has added the MIME types after “*/*”, indicating that it can translate from the additional MIME types to a format compatible with the client.

accept: application/xhtml+xml;q=0.5,text/html;q=0.5,application/vnd.wap.wmlc,application/vnd.wap.wmlscriptc,text/css,application/vnd.wap.xhtml+xml;q=0.5,application/vnd.wap.multipart.related,application/vnd.wap.multipart.mixed,multipart/mixed,application/vnd.wap.sic,application/vnd.oma.drm.message,application/vnd.phonecom.mmc-wbxml,application/motorola-mmstemplate,image/gif,image/bmp,image/vnd.wap.wbmp,image/png,image/jpeg,image/ems.userdefined.picture,image/ems.userdefined.animation,image/ems.predefined.animation,audio/bas,audio/imelody,audio/mid,audio/midi,audio/mp3,audio/mpeg,audio/mpeg3,audio/mpg,audio/x-mp3,audio/x-mpeg,audio/x-mpeg3,audio/x-mpg,audio/x-wav,audio/wav,audio/amr,audio/3gpp,video/mp4,video/3gpp,application/mtf,application/vnd.oma.drm.message,application/vnd.oma.drm.rights+xml,text/x-vcard,text/x-vcalendar,text/uri-list,text/vnd.sun.j2me.app-descriptor,application/java-archive,application/octet-stream,application/vnd.wap.mms-message,*/*,text/x-hdml,image/mng,image/x-mng,video/mng,video/x-mng,image/bmp,text/vnd.wap.wml



HTTP headers provided in MEdia Net service (Table 4).

Table 4 WAP Gateway-Inserted HTTP Headers (MEdia Net-specific)


Subscriber Identification (SubID)

HTTP header “x-up-subno” x-up-subno: SWC_100be1e0ffb_vmag.myworld.net

Gateway name See Table Note 1.

HTTP header “x-up-uplink” with value “vmag.myworld.net” (WAP 1 only)

x-up-uplink: vmag.myworld.net

Push gateway service address (non-secure interface)

Not supported.

Push gateway service address (secure interface)

Not supported.

TABLE NOTES

NOTE 1. The x-up-uplink header is not provided for users of WAP 2 devices.

3.1.1.2 Subscriber Identification

The Subscriber Identity (SubID) allows content providers to rely upon a unique identity for each subscriber. The SubID is a unique value assigned to the wireless subscriber by AT&T. It preserves the subscriber’s privacy while enabling content providers to recognize subscribers (e.g. for service personalization).

The SubID is only provided for proxied clients (those that access content provider services via the WAP gateways).

For WAP 2 clients, the SubID header is provided for non-secure services (accessed via http:// format URIs). The SubID header cannot be inserted by the WAP gateway for secure services (accessed via https:// format URIs) because secure services occur over an end-to-end SSL tunnel.

3.1.1.3 Service Identification

Service identification allows content providers to provide differentiated services as necessary for the user. Historically, several methods have been used for service identification. These methods, and the recommended method, are described below.

3.1.1.3.1 Unique Service Address (Recommended)

The unique service address method is recommended if the service identification uses a URL or domain name specific to the user’s service, e.g., http://cpprovider.com/mmode or http://mmode.cpprovider.com (where cpprovider.com is your domain). This address can be used in any portal links that direct the user to the service provider.

Portal presentation of links specific to the subscribed service enables support of multiple service offers in one portal complex (e.g., mMode, MEdia Net, and extension services). If a user enters the content provider’s site from another URL (e.g., directly), the content



provider can supply a generic service, or detect the service using another method (as shown below) and/or redirect the user to the homedeck, where they can be directed to the specific service address.

Note: Not all URLs for a service need to be unique to that service. At minimum, a service-specific entry URL can be used. Once the user’s service is identified, the content provider can use other methods for service identification (e.g., URL tokens or cookies).

3.1.1.3.2 Gateway Name in the x-up-subno header (Not Recommended)

Historically, the part of the x-up-subno header after the underscore (the gateway name) has a static value specific to the operator of the WAP gateway. In addition, the x-up-uplink header will contain this same value. Both have been used by content providers for service identification, and will continue to be usable for the short-term (through fall, 2005). However mid 2006 the structure of the x-up-subno will be changing and the structure of the gateway name being available after the underscore will no longer be retained. Thus content providers should not rely on parsing the x-up-subno to identify the carrier or subscriber, but should rather rely on the request source address. This will be for new subscribers only, thus existing x-up-subno values will remain the same.

Note: Regardless of the source, you should not use the gateway name for service identification, for these reasons: As the MEdia Net and other services evolve into a new service(s), the SubID for users will be preserved. During transition to the new service, content providers will not be able to determine which service (legacy mMode/MEdia Net or new service) to provide solely upon the gateway name part of the SubID, as they were previously been able to do. The x-up-uplink header is not provided for MEdia Net WAP 2 users. In addition, after launch of the new service, the x-up-uplink header may no longer be provided.

Note: Since the x-up-uplink header is not provided for MEdia Net WAP 2 users, service identification via this header is not reliable.

3.1.1.3.3 User Request Source IP Address

Historically, the mMode and MEdia Net services have been accessed via separate networks, with distinct public IP addresses with content providers differentiating services based upon the request source address. This will continue as a long term option.

3.1.2 Push Content Provider Interface Push content providers, also called push initiators, initiate content delivery interactions to mobile service subscribers using the WAP push protocols.

This type of service is now fully supported by the AT&T External Access Gateway (EAG). For complete information, please see the EAG section on the AT&T Developer Program Web site: http://developer.att.com/developer/index.jsp?page=toolsTechDetail&id=18500181

http://developer.att.com/developer/index.jsp?page=toolsTechDetail&id=18500181



3.1.3 Developer Gateways Topic removed - no longer applicable. Developers no longer need to test content on native browsers. Development, test and staging can all accomplished through the att.net platform. No other testing is required.

3.1.4 Test/Staging via Production Gateway Topic removed - no longer applicable. Developers no longer need to test content on native browsers. Development, test and staging can all accomplished through the att.net platform. No other testing is required.

3.1.5 Gateway Access Topic removed - no longer applicable. Developers no longer need to test content on native browsers. Development, test and staging can all accomplished through the att.net platform. No other testing is required.

3.2 Public IP Addresses for MEdia Net Gateways Firewalls should be opened to the below-listed subnets or specific addresses to allow content service through the multiple WAP gateways and NAT router addresses for MEdia Net for all data centers – VTC, STC, ATC (Allen), and Bothell. NOTE: Address ranges are shown in slash notation (e.g., 0/24 is 0 through 24).

PROXIED (E.G., WAP/HTTP THROUGH THE WAP GATEWAYS)

STC Internet Advertised Ranges MAG1 ... 209.183.32.0/24 MAG2 ... 166.216.128.0/23 NGG ..... 166.216.130.0/24

VTC Internet Advertised Ranges MAG1 ... 66.102.186.0/24 (To be retired after transition to 166.216.160.0/23.) MAG1 ... 166.216.160.0/23 (All VTC MAG1 traffic will come from this range.) MAG2 ... 166.216.160.0/23 NGG ..... 166.216.162.0/24

Allen Internet Advertised Ranges MAG1 ... 209.183.51.0/24 MAG2 ... 166.216.192.0/23 NGG ..... 166.216.194.0/24

Bothell Internet Advertised Ranges MAG1 ... 209.183.55.0/24 MAG2 ... 166.216.224.0/23 NGG ..... 166.216.226.0/24

NON-PROXIED (E.G., FROM 3GPP STREAMING CLIENTS)

STC Internet Advertised Range 166.217.0.0/16

VTC Internet Advertised Range 166.214.0.0/16

Allen Internet Advertised Range 166.128.0.0/16



Bothell Internet Advertised Range 166.129.0.0/16

NAT ROUTER POOL ADDRESS SPACE

STC NAT Router Pool Address Space 166.137.128.0/17 166.184.128.0/17 166.196.0.0/14 32.136.0.0/13 32.164.0.0/14

VTC NAT Router Pool Address Space 166.137.0.0/17 166.184.0.0/17 166.192.0.0/14 32.128.0.0/13 32.160.0.0/14

ATC (Allen) NAT Router Pool Address Space 166.205.0.0 255.255.128.0 166.216.0.0 255.255.128.0 166.220.0.0 255.255.128.0 166.188.0.0 /15 32.144.0.0 /13 32.168.0.0 /14

Bothell NAT Router Pool Address Space 166.205.128.0 /17 166.216.128.0 /17 166.220.128.0 /17 166.190.0.0 /15 166.134.0.0 /15 32.152.0.0 /13 32. 172.0.0 /14

Shared Space 166.192.0.0 /13 166.188.0.0 /14

3.2.1 Home URL Configuration ● Home portal Label ..... MEdia Net Home

● Home portal URL ...... http://device.home



Appendix A. mMode vs. MEdia Net Summary Comparison

Table 5 mMode vs. MEdia Net Summary Comparison

Network Component

Description mMode MEdia Net

WAP gateway The WAP gateway adds customer/handset specific information to each data request, allowing the content provider to customize the delivered content for every user.

WAP Version: 2.0 (compatible with WAP 1.2.1)Vendor: Openwave Can gateway generate unique IDs? Yes

WAP Version: 2.0 (compatible with WAP 1.2.1) Vendor: Openwave Can gateway generate unique IDs? Yes

Subscriber Identification (SubID)

The SubID is the value of the x-up-subno header

Example: 46599-14491_pn.attwireless.net

Example: SWC_100be1e0ffb_vmag.myworld.net

Service Identification (recommndd)

The recommended method to distinguish mMode and MEdia Net users.

Unique service address (URL/domain)

Unique service address (URL/domain)

Service Identification (current)

Currently available methods to distinguish mMode and MEdia Net users. These methods may not be usable beyond the third quarter of 2005.

Option 1: detecting “pn.attwireless.net” in the x-up-subno header Option 2: detecting x-up-uplink header with value “pn.attwireless.net” Option 3: detecting requests from mMode proxy IP addresses

Option 1: detecting “vmag.myworld.net” in the x-up-subno header Option 2: detecting requests from MEdia Net proxy IP addresses

Push Access Protocol (PAP) service provided by Push Proxy Gateway (PPG)

The PPG provides content provider-initiated content delivery to mobile clients. Push requests are sent by the content provider to the PPG using the PAP.

Push supported? Yes PAP Version: 1.2 PAP service address: Secure: pn.mymmode.com:9003/papNon-Secure: pn.mymmode.com:9002/papAccessed via Internet, controlled by source IP address.

Push supported? Yes PAP Version: 1.2 PAP service address: Secure: vmag.myworld.net:9003/pap Non-Secure: vmag.myworld.net:9002/pap Accessed via VPN connection to AT&T data center.

Home URL configuration

URL providing the service homedeck.

mMode Home: http://home or http://home.mymmode.com

MEdia Net Home: http://device.home/ or http://www.infospace.com/infow.sbcw/

Developer Gateways

An internet-accessible gateway made available for application development.

WAP 1 Pull: testgate.mobilephone.net:9201 (non-secure WAP 1) testgate.mobilephone.net:9203 (secure WAP 1) Authenticated service supported: Yes

WAP 1 Pull: Not provided (mMode developer gateways or Media Net production gateway can be used).



Network Component

Description mMode MEdia Net

WAP 2 Pull: sccmmag.scc.mobilephone.net:8080

WAP 2 Pull: Not provided (mMode developer gateway or Media Net production gateway can be used).

WAP Push: Not provided. Content providers with access to the production PPG are allowed to use the PPG for application development and test with devices on the production wireless network.

WAP Push: Not provided. Content providers with access to the production PPG are allowed to use the PPG for application development and test with devices on the production wireless network. Functional testing of Push for VTC is currently being executed against our Atlanta GH2 environment. The PPG address is 70.151.42.15. We will need to know the Push Initiator's source IP address and intended destinations (MSISDNs) to allow delivery to Orange production handsets. A similar environment for delivering over the Blue production network does not exist. We can only test delivery for Blue in-lab by originating the message from lab and confirming delivery from within lab. In both cases, snoop files can be provided.



Appendix B. MEdia Net HTTP Request Examples

B.1. MEdia Net WAP 1 Client The Openwave MAG version 6.3.1.4A is the WAP 1 gateway currently in service for MEdia Net.

GET / HTTP/1.1 Host: www.acingularcom accept: application/vnd.wap.wmlc, application/vnd.wap.wmlscriptc, text/html, text/css, application/xhtml+xml, application/vnd.wap.xhtml+xml, image/vnd.wap.wbmp, image/gif, application/vnd.wap.multipart.related, application/vnd.wap.multipart.mixed, application/vnd.wap.sic, application/vnd.phonecom.mmc-wbxml, image/gif, image/bmp, image/vnd.wap.wbmp, image/png, image/jpeg, image/ems.userdefined.picture, image/ems.userdefined.animation, image/ems.predefined.animation, audio/bas, audio/imelody, audio/mid, audio/midi, audio/mp3, audio/mpeg, audio/mpeg3, audio/mpg, audio/x-mp3, audio/x-mpeg, audio/x-mpeg3, audio/x-mpg, audio/x-wav, audio/amr, video/mp4, application/mtf, application/vnd.oma.drm.message, application/vnd.oma.drm.rights+xml, text/x-vCard, text/x-vCalendar, text/uri-list, text/vnd.sun.j2me.app-descriptor, application/java-archive, application/octet-stream, application/vnd.wap.mms-message, */*,text/x-hdml,image/mng,image/x-mng,video/mng,video/x-mng,image/bmp,text/html,text/vnd.wap.wml accept-application: 2, 4 accept-charset: utf-8,* accept-language: en encoding-version: 1.3 user-agent: MOT-V600/0B.08.9FR MIB/2.2 Profile/MIDP-2.0 Configuration/CLDC-1.0 UP.Link/6.3.0.0.0 x-up-devcap-charset: utf-8,ISO-8859-1 x-up-devcap-max-pdu: 522240 x-up-uplink: vmag.mycingular.net x-up-wtls-info: off x-wap-profile: "http://motorola.handango.com/phoneconfig/v600/profile/v600.rdf" x-up-devcap-smartdialing: 1 x-up-devcap-iscolor: 1 x-up-devcap-screendepth: 16 x-up-devcap-numsoftkeys: 2 x-up-devcap-screenpixels: 176,220 x-up-devcap-accept-language: en x-up-subno: PPU_123456789AB_vmag.mycingular.net Via: 1.1 alpmagr1fe08-dmz.mycingular.net Connection: close

B.2. MEdia Net WAP 2 Client The Openwave MAG version 6.3.1.4A is the WAP 2 gateway currently in service for MEdia Net.

GET / HTTP/1.1 Host: www.cingular.com Accept: text/X-CalypsoLink, text/x-vCalendar, text/calendar, text/x-vCard, text/plain, application/vnd.oma.dd+xml, text/x-co-desc, application/vnd.oma.drm.message, application/x-java-archive, video/3gpp, video/vnd.nokia.interleaved-multimedia, application/vnd.symbian.install, application/vnd.nokia.ringing-tone, audio/x-xmrcc-sp-midi, audio/x-xmrcc-midi, audio/x-xmrcc-x-beatnik-rmf, audio/sp-midi, audio/midi, audio/x-beatnik-rmf, image/tiff, image/x-wmf, image/png, image/vnd.nokia.ota-bitmap, image/vnd.wap.wbmp, image/x-bmp, image/x-epoc-mbm, audio/basic, audio/x-sibo-wve, audio/x-epoc-wve, image/jpeg, image/gif, audio/amr, audio/x-wav, application/java-archive, text/vnd.sun.j2me.app-descriptor, application/x-nokiaGameData, application/vnd.wap.html+xml, text/html, application/vnd.wap.wmlscriptc, application/vnd.wap.wbxml,



application/vnd.wap.wmlc, application/vnd.wap.mms-message, application/xhtml+xml, application/vnd.wap.xhtml+xml, text/css, audio/mid, audio/wav, text/vnd.wap.wml, text/html, application/*,text/x-hdml,image/mng,image/x-mng,video/mng,video/x-mng,image/bmp,text/html Accept-Charset: iso-8859-1, us-ascii, utf-8;q=0.8, iso-10646-ucs-2;q=0.6,* Accept-Language: en User-Agent: NokiaN-GageQD/2.0 (04.10) SymbianOS/6.1 Series60/1.2 Profile/MIDP-1.0 Configuration/CLDC-1.0 UP.Link/6.3.0.0.0 X-Wap-Profile: "http://nds1.nds.nokia.com/uaprof/NNGQDr200.xml" x-up-devcap-iscolor: 1 x-up-devcap-screendepth: 12 x-up-devcap-numsoftkeys: 2 x-up-devcap-charset: US-ASCII,ISO-8859-1,UTF-8,ISO-10646-UCS-2 x-up-devcap-screenpixels: 176,208 x-up-subno: PPU_123456789AB_vmag.mycingular.net Via: 1.1 alpmagr1fe04-dmz.mycingular.net:8080 Connection: close

Appendix C. mMode HTTP Request Examples

C.1. mMode WAP 1 Client The Openwave MAG version 5.1.2.9a is the WAP 1 gateway currently in service for mMode.

GET / HTTP/1.1 x-up-uplink: pn.attwireless.net x-up-fax-limit: 100000 Profile: http://motorola.handango.com/phoneconfig/v551/Profile/v551.rdf x-up-subno: 46599-14491_pn.attwireless.net x-up-fax-accepts: text/plain, application/postscript, application/msword, application/rtf, application/pdf host: 4.38.5.170 Accept-Language: en User-Agent: MOT-V551/08.17.0FR MIB/2.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.0 UP.Link/5.1.2.9 x-up-devcap-max-pdu: 522240 Accept-Application: 2 Accept-Application: 4 x-up-devcap-charset: utf-8 x-up-WTLS-info: off Connection: close Encoding-Version: 1.3 x-up-wappush-secure: pn.mymmode.com:9003/pap x-up-fax-encodings: 7bit, 8bit, base64, quoted-printable Accept: application/vnd.wap.wmlc, application/vnd.wap.wmlscriptc, text/html;Q=0.5, text/css, application/xhtml+xml;Q=0.5, application/vnd.wap.xhtml+xml;Q=0.5, application/vnd.wap.multipart.related, application/vnd.wap.multipart.mixed, multipart/mixed, application/vnd.wap.sic, application/vnd.oma.drm.message, application/vnd.phonecom.mmc-wbxml, application/motorola-mmstemplate, image/gif, image/bmp, image/vnd.wap.wbmp, image/png, image/jpeg, image/ems.userdefined.picture, image/ems.userdefined.animation, image/ems.predefined.animation, audio/bas, audio/imelody, audio/mid, audio/midi, audio/mp3, audio/mpeg, audio/mpeg3, audio/mpg, audio/x-mp3,



audio/x-mpeg, audio/x-mpeg3, audio/x-mpg, audio/x-wav, audio/wav, audio/amr, audio/3gpp, video/mp4, video/3gpp, application/mtf, application/vnd.oma.drm.message, application/vnd.oma.drm.rights+xml, text/x-vCard, text/x-vCalendar, text/uri-list, text/vnd.sun.j2me.app-descriptor, application/java-archive, application/octet-stream, application/vnd.wap.mms-message, */*, application/vnd.wap.sic,application/vnd.wap.slc,application/vnd.wap.mms-message,application/vnd.wv.csp.cir, image/bmp,image/vnd.wap.wbmp,application/vnd.phonecom.mmc-xml,text/x-wap.wml,text/vnd.wap.wml,text/x-hdml,text/html,text/vnd.wap.wmlscript,text/vnd.wap.si,text/vnd.wap.sl, */* x-up-wappush-unsecure: pn.mymmode.com:9002/pap Accept-Charset: utf-8, UTF-8, *

C.2. mMode WAP 2 Client The Openwave MAG version 6.2.3.10 is the WAP 2 gateway currently in service for mMode.

GET / HTTP/1.1 Host: 4.38.5.170 accept: application/xhtml+xml;q=0.5,text/html;q=0.5,application/vnd.wap.wmlc,application/vnd.wap.wmlscriptc,text/css,application/vnd.wap.xhtml+xml;q=0.5,application/vnd.wap.multipart.related,application/vnd.wap.multipart.mixed,multipart/mixed,application/vnd.wap.sic,application/vnd.oma.drm.message,application/vnd.phonecom.mmc-wbxml,application/motorola-mmstemplate,image/gif,image/bmp,image/vnd.wap.wbmp,image/png,image/jpeg,image/ems.userdefined.picture,image/ems.userdefined.animation,image/ems.predefined.animation,audio/bas,audio/imelody,audio/mid,audio/midi,audio/mp3,audio/mpeg,audio/mpeg3,audio/mpg,audio/x-mp3,audio/x-mpeg,audio/x-mpeg3,audio/x-mpg,audio/x-wav,audio/wav,audio/amr,audio/3gpp,video/mp4,video/3gpp,application/mtf,application/vnd.oma.drm.message,application/vnd.oma.drm.rights+xml,text/x-vcard,text/x-vcalendar,text/uri-list,text/vnd.sun.j2me.app-descriptor,application/java-archive,application/octet-stream,application/vnd.wap.mms-message,*/*,text/x-hdml,image/mng,image/x-mng,video/mng,video/x-mng,image/bmp,text/html,text/vnd.wap.wml accept-charset: utf-8,* accept-language: en user-agent: MOT-V551/08.17.0FR MIB/2.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.0 x-wap-profile: "http://motorola.handango.com/phoneconfig/v551/Profile/v551.rdf" x-up-wappush-secure: pn.mymmode.com:9003/pap x-up-wappush-unsecure: pn.mymmode.com:9002/pap x-up-uplink: pn.attwireless.net x-up-subno: 46599-14491_pn.attwireless.net Via: 1.1 WAP 2Service:8080 Connection: close



Appendix D. User Agent String Parsing

The device make and model can be determined by the browser’s user agent.

HTTP Header: User-Agent

Example: Nokia6230i/2.0 (03.25) Profile/MIDP-2.0 Configuration/CLDC-1.1.

The first white space-delimited word in the UA string identifies that Make Model and Version number of a device. Most device manufacturers follow the make and model by a slash “/”, and follow this with the version number, as shown in the example above for the Nokia 6230i device. Software revisions may appear after the first “/” in the user agent and may be important to your device catalog.

Although in many cases, you can generally parse at the first slash and treat the left substring as the Make and Model ID, you should be aware that a small number of AT&T devices and many COAM (non-official AT&T) devices do not follow the convention above. These devices may not place a version number after the make and model within the first white space delimited word.

For example, The LG CU500 v1 looks like this:

"LG-CU500 Obigo/WAP2.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 UP.Link/6.3.0.0.0"

It is likely that future version of this device would like:

"LG-CU500/v2.0 Obigo/WAP2.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 UP.Link/6.3.0.0.0"

In order to handle these cases, we suggest that you follow the following parsing logic:

1. Parse FIRST WORD until a slash -> return MakeModel

1a. [if version needed, parse after the slash until space -> return Version]

2. If space is reached before slash -> return MakeModel

3. If needed, based on MakeModel AND Version, search rest of UAstring for other details.

Note: If your application requires differentiating between version numbers of a particular make and model, you can use the version number as well as the make and model. Please note that very similar versions of devices ship frequently, and the AT&T Developer Program does not send information updates on each new version.



Appendix E. mMode Service (archived info., ca. 2007)

This section outlines network specifications for the mMode service.

E.1. WAP Gateways Two WAP gateways (WAP 1.2.1 and WAP 2.0) currently support mMode. Both gateway versions are based upon the Openwave Mobile Access Gateway (MAG). The WAP 1.2.1 gateway is Openwave MAG 5.1.2.9, and the WAP 2.0 gateway is Openwave MAG 6.2.3.10.

E.1.1. Pull Content Provider Interface Pull content providers serve client-initiated service requests, most commonly for WAP browsing. The interface description provided here covers the following:

Information (HTTP headers) passed to the content provider from the client or from the WAP gateway

Methods of identifying the subscriber accessing the service

Methods of differentiating the service to be provided to the client

E.1.1.1. HTTP Headers

See parallel content in the MEdia Net chapter of this document.

E.1.1.2. Subscriber Identification


E.1.1.3. Service Identification


E.1.2. Push Content Provider Interface Push content providers, also called push initiators, initiate content delivery requests to users using the WAP push protocols. The interface description provided here covers these aspects:

Push Access Protocol (PAP) services offered to content providers

Supported push bearers and over-the-air delivery methods

PAP service access

Push addressing

Supported push content types



mMode supports the WAP push Access Protocol (PAP) interface for push operations over secure and non-secure HTTP connections. The PAP service address is indicated by the two HTTP headers:

x-up-wappush-secure: pn.mymmode.com:9003/pap

x-up-wappush-unsecure: pn.mymmode.com:9002/pap

Content providers are encouraged to either pre-configure the mMode PAP service address or derive it from these headers only.

Access to the mMode PAP service is controlled by a push initiator source address configuration on the WAP gateway. Only push initiators that have completed an application process are allowed to access the mMode PAP service.

Supported PAP operations include:

Push submission

Push status query

Push client capabilities query

Subscribers are addressed in push requests using the Subscriber Identification (SubID).

Connectionless WAP 1 push over GSM SMS is the typical method for push delivery for both WAP 1 and WAP 2 clients. To ensure compatibility with the majority of push clients, content providers are encouraged to either leave the push Quality of Service (QOS) parameters as unspecified or to select unconfirmed delivery.

Connection-oriented push over GPRS (IP bearer) is supported for compatible WAP 1 clients, both with unconfirmed and confirmed QOS. If connection-oriented push is compatible and an IP bearer is available (i.e., the client has an active WAP 1 session), the WAP gateway will deliver push requests using the IP bearer. Otherwise, connectionless WAP 1 push over GSM SMS will be used.

Supported push content types include service indication for all push-compatible devices, and for compatible devices:

Service loading

Cache operation

MMS message

Wireless Village notifications

OMA Digital Rights Management content

SyncML content

Other content types as specified by the client

E.1.3. Developer Gateways mMode Internet-accessible developer test WAP gateways include the following:

testgate.mobilephone.net:9201 (non-secure WAP 1)



testgate.mobilephone.net:9203 (secure WAP 1)

sccmag.scc.mobilephone.net:8080 (WAP 2)

If the client connects using secure WAP (WTLS) and specifies a Client ID, authenticated service can be provided, and a unique subscriber number/MSISDN associated with the test user. Otherwise, anonymous-only service is provided.

Developer-accessible PAP service is not provided. However content providers with access to the production PAP service are allowed to use it for application development and testing with devices on the production wireless network.

E.1.4. Test/Staging via the Production Gateway Content providers and developers can use the production WAP gateways for application development and pre-production staging with devices on the production wireless network.

Special configurations are provided for mMode partner content providers, allowing pre-production content provider servers the same service (e.g., HTTP header delivery and PAP service) as production content provider servers.

E.1.5. Gateway Access When accessed via the Internet, developer and production WAP gateways are fire walled to ensure that only defined services are accessible. For example:

Developer gateways via UDP port 9201 and 9203 (WAP 1), and HTTP port 8080 (WAP 2)

Production gateways via HTTP port 9002 and HTTPS port 9003

All WAP gateway servers with public IP addresses have publicly resolvable hostnames associated with their public IP addresses.

The mMode PAP service is access-controlled, as described in Section 2.1.2.

E.2. Public IP Addresses for mMode Firewalls should be opened to the following subnets or specific addresses to accommodate the multiple WAP gateways and NAT router addresses for mMode.

Proxied (e.g., WAP/HTTP through the WAP gateways):

NDC1 Internet Advertised Ranges 209.183.48.0 /22

NDC2 Internet Advertised Ranges 209.183.52.0 /22

Non-proxied (e.g., from 3GPP streaming clients):

NDC1 NAT Router 1 Pool Address Space166.205.0.0 /17

NDC2 NAT Router 1 Pool Address Space 166.205.128.0 /17





If specific WAP gateway proxy addresses are required for firewall configuration, the following list provides the complete set of public addresses used by the mMode WAP gateways:

209.183.48.35 209.183.48.37 209.183.48.38 209.183.48.39 209.183.48.41 209.183.48.43 209.183.48.45 209.183.48.47 209.183.48.49 209.183.48.51 209.183.48.53 209.183.48.55 209.183.48.57 209.183.48.59 209.183.48.61 209.183.48.110 209.183.48.111

209.183.48.153 209.183.48.154 209.183.48.155 209.183.48.156 209.183.48.157 209.183.48.158 209.183.48.159 209.183.48.160 209.183.48.161 209.183.48.162 209.183.48.163 209.183.48.164 209.183.48.165 209.183.48.166 209.183.48.167 209.183.48.168 209.183.48.169

E.3. Home URL Configuration ● The Home portal Label is: mMode Home

● The Home portal URL is: http://home

Note: Some clients (e.g., Pocket IE) require the use of the full domain name for mMode home: http://home.mymmode.com.

network specifications: att.net, media net, mmode · the att.net browse client , based on the opera...

Documents