WAP White Paper 20031202 B V1.0

Document

code

Product

Name WCDMA

Intended

audience

Engineers of Huawei and

cooperation partners

Product

Version

Compilation

department

WCDMA Product

Department

Docume

nt

Version

V1.0

WAP White Paper

Drafted by Zhao Bing Date 2003-12-02

Reviewed by Date

Reviewed by Date

Approved by Date

©Huawei Technologies Co., Ltd

All Rights Reserved

WAP White Paper Secret

Revision Record

Date Version Description Author

2003-12-02 1.00 First draft finished Zhao Bing

2003-08-24 Huawei Technologies Proprietary Page ii of 118

Table of Contents

Chapter 1 Background...............................................................................................................ii

Chapter 2 WAP Technology......................................................................................................3

2.1 Application Framework........................................................................................................3

2.2 WAP Stack Protocol............................................................................................................4

2.2.1 WAE......................................................................................................................... 4

2.2.2 WSP......................................................................................................................... 4

2.2.3 WTP.......................................................................................................................... 5

2.2.4 WTLS........................................................................................................................ 5

2.2.5 WDP......................................................................................................................... 5

2.2.6 Typical Application of WAP Stack Protocol...............................................................6

Chapter 3 Application in the Existing Network...........................................................................7

3.1 Position of WAP in Networks...............................................................................................7

3.2 WAP Existing Networking...................................................................................................8

3.2.1 Networking Structure................................................................................................8

3.2.2 Interface Description.................................................................................................8

3.3 Typical Business Process.................................................................................................10

3.3.1 Processing Procedure of RADIUS Messages.........................................................10

3.3.2 Process of PUB Users Accessing Whole-network Services at a Home Location. . .12

3.3.3 Process of PUB Users Accessing Whole-network Services at a Roaming Location........................................................................................................................................ 14

3.3.4 Process of PUB Users Accessing Local Services at a Roaming Location..............15

3.3.5 Process of Handling WAP Browse Service for PPC Users.....................................17

3.3.6 Processing Procedure for PUSH over IP................................................................19

3.3.7 Processing Procedure for POP3/SMTP Mail Service.............................................22

3.3.8 MMSC Address Translation Process (Proxy is Redirector)....................................25

3.3.9 KJAVA Download Process.....................................................................................27

Appendixes:..............................................................................................................................30

Appendix 1: Introduction to WAP 2.0......................................................................................30

Appendix 2: Acronyms............................................................................................................30

2003-08-24 Huawei Technologies Proprietary Page iii of 118

WAP white paper Secret

Keyword

WAP

Abstract

The document describes WAP technology and its application in the existing

network. It helps readers to have a full and systematic knowledge of WAP

technology.

Process of Handling WAP Browse Service for PPC Users

Figure 10 Processing procedure applicable to PPC users

Explanations:

19) GGSN sends a message of charging start to WAP GW.

20) WAP GW initiates real-time monitoring, and submits an expense reservation

request to SCP periodically.

21) SCP returns a request response to WAP GW.

22) GGSN sends a URL access request to WAP GW.

Huawei Technologies Proprietary

i


Reference



Explanations:







ii


Chapter 1 Background

With evolution of the GSM, GPRS and 3GPP network, WAP technology is

getting more and more important for mobile networks. When a single

mobile phone (not connected to a laptop) can be used for browsing

information, all mobile data service is forwarded through WAP Gateway.



Explanations:







iii


WAP technology has a large-scale application because it is developed for

mobile application and can solve the problem of mobile “narrowband”.

Furthermore, WAP technology is launched by the four mobile giants:

Ericsson, Motorola, Nokia and Unwired Planet that provides micro browsers

for WAP technology. Members of WAP Forum take up over 90% of handset

market share, so WAP has become a de facto standard.

In May 1998, WAP Forum released the version WAP 1.0 to define a basic

frame of WAP.



Explanations:







iv


In September 1999, WAP Forum released the version WAP 1.1, the first

business release of WAP. It supports images in the format WBMP, and has

enhanced compatibility and interoperability.

In early 2000, WAP 1.2 was released. Push and User Agent are added to

version WAP 1.2 and bearer network types supported by WAP are

expanded.

In August 2001, WAP 2.0 was released. Comparing with earlier versions,

the major distinction of WAP 2.0 is the more diversified application service



Explanations:







v


and more secure transmission of information. Besides, WAP 2.0 facilitates

wireless content vendors’ effort to build wireless sites and wireless

application suitable for GPRS and 3G.

As WAP is increasingly close and merged to Internet specifications, the

latest version WAP 2.0 is intended to support XHTML, TCP/IP, HTTP/1.1

and TLS.

In fact, WAP 1.3 exists between WAP 1.2 and WAP 2.0. WAP 1.3

enhances the WAP support for streaming and security. Because WAP 2.0



Explanations:







vi


integrates all features of WAP 1.3, manufacturers usually use WAP 2.0

instead.

See attachment 1 for descriptions of WAP 2.0.



Explanations:







vii


Chapter 2 WAP Technology

2.1 Application Framework



Explanations:







8




Explanations:







9


Figure 1 WAP 1.0 application framework

As shown above, WAP Framework consists of three parts: the client, WAP

Gateway and Web server.

Client: mobile phone. It integrates the whole WAP Protocol, initiates and

terminates sessions, and controls the terminal to show users contents.

Web server: provides contents in the WML language.



Explanations:







10


WAP Gateway: responsible for coding and decoding as well as the protocol

adaptation function.

The client and WAP Gateway have WSP/WTP in between. That is, the

stack protocol of WAP is used on the session layer. HTTP is used between

WAP Gateway and a server. Conversion between WSP/WTP and HTTP

are finished on WAP Gateway, because HTTP text format is not suitable for

radio transmission. But WSP/WTP uses binary code to transmit data and

compresses data for narrowband transmission.



Explanations:







11


If contents in the server are written in the HTML language, WAP Gateway

has to carry out the conversion between HTML and WML. This could

reduce the efficiency of WAP Gateway.



Explanations:







12


2.2 WAP Stack Protocol



Explanations:







13




Explanations:







14


Figure 2 WAP stack protocol

The above figure shows the comparison between WAP stack protocol and

Internet stack protocol.

2.2.1 WAE

Wireless Application Environment (WAE) is a protocol for the application

layer in WAP. It establishes an application development environment for

services on different wireless platforms. The core of WAE is a micro-



Explanations:







15


browser that supports WML, WML Script, Wireless Telephone Application

(WTA) and content coding and decoding.

WAE Specification is divided into the following two logical layers:

1. WAE User Agent layer: provides users with client embedded software

with specific functions. User Agent includes the micro-browser,

directory and message editor.



Explanations:







16


2. Service and Format layer: defines general data formats that support

User Agent, such as WML, WML Script, WBMP, vCard and electronic

calendar.

2.2.2 WSP

Wireless Session Protocol (WSP) provides the following functions:

A. Function and semanteme of HTTP 1.1 that simplifies protocol conversion

on WAP Gateway



Explanations:







17


B. Capacity negotiation between the gateway and client

C. A long-term preservation of session status

D. Session suspension and recovery

E. Reliable and unreliable Push

F. Processing multiple requests at the same time (asynchronous request

response)

G. Processing missing breaks



Explanations:







18


2.2.3 WTP

Wireless Transaction Protocol (WTP) is a connection-oriented transport

layer protocol similar to TCP. WTP provides reliable transmission for the

upper layer. WTP cannot be omitted for interaction between a client and

server.



Explanations:







19


2.2.4 WTLS

Wireless Transaction Layer Security (WTLS) serve security, integrity,

facticity and non-repudiation of upper layers through key exchange,

authentication, encryption and handshakes.



Explanations:







20


2.2.5 WDP

Wireless Data Protocol (WDP) corresponds with UDP in TCP/IP stack

protocol and has the same function as UDP. UDP is used instead of WDP

in networks over IP.



Explanations:







21


2.2.6 Typical Application of WAP Stack Protocol

I. WAP stack protocol in GPRS



Explanations:







22




Explanations:







23


Figure 3 GPRS WAP stack protocol



Explanations:







24


II. WAP based on SMS



Explanations:







25




Explanations:







26


Figure 4 SMS WAP stack protocol

Chapter 3 Application in the Existing Network

3.1 Position of WAP in Networks

A network lives for providing users with rich and colorful services.



Explanations:







27


In GPRS, services can be divided into the following four categories based

on access modes:

A. Services provided by SGSN (LCS and SMS)

B. Services with direct link of GGSN to Internet (where a mobile phone

works with a laptop; the extension of fixed network service)

C. Enterprise services (VPN)



Explanations:







28


D. WAP services (data service fulfilled only through mobile phone or PDA,

such as multimedia messaging service (MMS), mobile video, mobile

entertainment and QQ (an online chatting tool)).

According to the categories, almost all services showing mobile

characteristics are fulfilled based on WAP.

Take China Mobile as an example, WAP Gateway is provided by the

mobile carrier China Mobile, and WAP Server is provided by content

providers, such as SP and Sina. China Mobile also uses its own WAP



Explanations:







29


Server. In other word, the mobile carrier provides WAP Portal, SP provides

contents, and China Mobile controls admission of SP through WAP

Gateway.

For information on WAP existing network service application, see “GPRS

Service White Paper”.



Explanations:







30


3.2 WAP Existing Networking

3.2.1 Networking Structure



Explanations:







31


DSMP

BTS

MSC

BTS

GGSN GSM/GPRS WAP GW

E-mail Server

PUSH

Server SMSC SCP

PORTAL

RADIUS

WAP Server

Other SP MMSC

ENUM DNS



Explanations:







32


Figure 5 WAP existing networking

On networks of China Mobile, there are two general access point names

(APN): CMNET and CMWAP, where CMWAP is APN of dedicated WAP

service. “General APN” means wherever a user roams in China, the user

can enable GPRS service with the two APNs without changing

configurations of the mobile phone.

If a user selects CMWAP for activation, GGSN has to sends authentication

and charging requests to RADIUS. The RADIUS server then forwards the



Explanations:







33


requests to WAP Gateway (GW). Then WAP GW obtains the relationship

between MSISDN and IP address for use in charging. During the

subsequent data transport, GGSN communicates with WAP GW through

GRE Tunneling Protocol.

3.2.2 Interface Description

WAP GW provides functions of charging, content mapping, mail agent and

so on, so interfaces are complex. See the following table.



Explanations:







34


Interface peer end Protocol Description

GGSN TCP/IP On networks of China Mobile, WAP GW

connects to GGSN through Internet. The

dedicated connection is established through

GRE Tunneling Protocol.

RADIUS Server RFC2865 and To obtain the relationship between MSISDN



Explanations:







35


RFC2866 and the user IP address, RADIUS Server

forwards the charging request to WAP GW,

and WAP GW returns the response of

charging start.

Carrier Portal, KJAVA

platform, MMSC

HTTP



Explanations:







36


WAP Server of common

SP

HTTP

PUSH Terminal PUSH OTA You can transfer in SMS and IP modes. For

IP-based PUSH, if a user is online, or if a user

is offline but support networks for terminal

and radio network are activated, you can



Explanations:







37


transfer in IP mode. If a user is offline but the

user equipment (UE) supports Session

Initiation Application (SIA), Session Initiation

Request (SIR) can be delivered through PUSH

over SMS. After receiving SIR, PUSH OTA

on UE SIR activates network connection and



Explanations:







38


establishes WAP session connection.

PUSH

SERVER

HTTP PAP

POP3/SMTP Email Server RFC1936 (POP3) and

RFC821 (SMTP)

WAP GW provides the function of Email

Server agent and can directly interwork with

Email Server.



Explanations:







39


ISMG CMPP When SM-based PUSH service is provided,

WAP GW should interact with ISMG.

SCP EMPP Provides pre-paid charging (PPC) functions.

MMSC M1

SMSC SMPP3.3/SMPP3.4

DSMP SP HTTP XML The interface is used to connect SP with WAP



Explanations:







40


authentication

interface

GW. If the connection needs to be

authenticated, WAP GW queries DSMP for

information on access authentication of SP.

Then WAP GW performs the access

authentication for SP.

Real-time WAP GW submits a real-time rating request to



Explanations:







41


rating

interface

DSMP through this interface. DSMP performs

rating according to the charging rule, and

feedbacks the result to WAP GW.

User service

subscription

relation

When SP delivers services subscribed by users

through WAP GW, WAP GW connects to

DSMP through the interface to verify the



Explanations:







42


authentication

interface

specified services and service status.



Explanations:







43


3.3 Typical Business Process

3.3.1 Processing Procedure of RADIUS Messages



Explanations:







44




Explanations:






Huawei Technologies Proprietary(Optional) Realtime control

of flow charging

Establish IP-MSISDN relationship

Clear IP-MSISDN relationship

PPC user FC charge reservation response

FC charge withhold/reimburse request

FC charge withhold/reimburse response

PPC user FC charge reservation request

45


Figure 6 RADIUS message processing

Explanations:

1. When a user goes online, GGSN sends an access request for RADIUS

user to AAA Server.

2. AAA Server returns a response message to GGSN.



Explanations:







46


3. GGSN sends a message of RADIUS charging start to WAP GW.

4. On obtaining the relationship between MSISDN and IP from the

message, WAP GW initiates the session of real time monitoring users.

5. For PPC users, WAP GW sends SCP a request to start traffic

monitoring.

6. SCP sends a response message to WAP GW.



Explanations:







47


7. During a user is online, if the user requests for surfing the Internet

(without interaction with upper layer services), WAP GW carries out a

real-time monitoring If the traffic is up to limit, WAP GW requests for

the next traffic segment from SCP and subsequent procedures cycle in

this way. See Figure 6 for control messages.

8. When a user goes offline, GGSN sends a message of charging end to

WAP GW.

9. WAP GW clears MSISDN-to-IP relationship.



Explanations:







48


10. For PPC users, WAP GW sends a message of traffic monitoring end to

SCP.

11. SCP returns a response message to WAP GW.

12. WAP GW sends the response message to AAA Server.



Explanations:







49


3.3.2 Process of PUB Users Accessing Whole-network Services at a Home Location



Explanations:







50




Explanations:







51


Figure 7 Process of PUB users accessing whole-network services at a home location

Explanations:

1. A user launches a URL access request.

2. WAP GW sends DSMP a request to authenticate the user.

3. DSMP returns the authentication result to WAP GW.



Explanations:







52


4. If the user does not register, WAP GW responds with a prompt page

and redirects the user to the registration page of Portal.

5. Steps 5–11 describe the procedure of user registration on Portal.

6. Step 12 means the terminal re-initiates a URL request.

7. On recognizing the user is not qualified and does not access Portal,

WAP GW sends DSMP a request to authenticate the user.

8. DSMP returns an authentication response to WAP GW.



Explanations:







53


9. WAP GW processes the URL access control.

10. If the user access is rejected, WAP GW returns a preset prompt page

to the end user.

11. If the access control is passed, WAP GW sends DSMP a request to

authenticate the user service subscription relation.

12. DSMP returns the authentication result.



Explanations:







54


13. If authentication of user service subscription relation fails, proceed with

the following steps.

14. WAP GW redirects the user to Portal to process service order. When

the order is finished, Portal redirects the user to URL of the destination

SP.

15. WAP GW forwards the user access request to SP.

16. SP service system returns an access response.



Explanations:







55


17. WAP GW sends a charging rating request to DSMP.

18. DSMP returns a charging rating response message to WAP GW.

19. WAP GW makes statistics of current traffic for the user.

20. WAP GW generates a bill file record of service access.



Explanations:







56


3.3.3 Process of PUB Users Accessing Whole-network Services at a Roaming Location



Explanations:







57




Explanations:







58


Figure 8 Process of PUB users accessing whole-network services at a roaming location

Explanations:

Different from accessing whole-network services at a home location, when

a user is linked to WAP GW of a roaming location, WAP GW sends

requests of authentication and charging rating to DSMP at the same

roaming location. Then DSMP of the roaming location forwards control

message requests to DSMP of the home location, and sends results back

to WAP GW of the roaming location through DSMP of the roaming location.



Explanations:







59


3.3.4 Process of PUB Users Accessing Local Services at a Roaming Location



Explanations:







60




Explanations:







61


Figure 9 Process of PUB users accessing local services at a roaming location

Explanations:

1. GGSN forwards a user’s request to WAP GW of the roaming location.

2. WAP GW sends the user authentication request to DSMP of the

roaming location.

3. DSMP of the roaming location sends the request to DSMP of the

user’s home location.



Explanations:







62


4. DSMP of the home location returns the authentication result to DSMP

of the roaming location.

5. DSMP of the roaming location returns the authentication result to WAP

GW of the same place.

6. When resolution of the WAP message is finished, WAP GW processes

URL access control according to URL Control List.



Explanations:







63


7. WAP GW extracts the service code and SP code from the valid URL.

By analyzing the service code, WAP GW finds the service is local.

There are possibly two kinds of local service:

8. Service provided by the user’s home location

9. Service can only be obtained at a roaming location.

10. WAP GW can recognize the service request type by interacting with

DSMP or through configuration mode. For the first kind of local service,

WAP GW forwards a service request to WAP GW of the user’s home



Explanations:







64


location through routing configuration. For the second kind of local

service, WAP GW directly forwards the message to SP.

11. For service provided by the user’s home location, WAP GW of the

home location initiates an authentication request to DSMP of the same

place.

12. DSMP sends an authentication response to WAP GW.

13. WAP GW sends a HTTP request to SP/CP and involves the user

pseudo code in the request.



Explanations:







65


14. SP/CP returns a response message to WAP GW.

15. WAP GW sends a rating request message to DSMP.

16. If authentication fails, WAP GW sends the user a preset page

containing error messages.

17. DSMP returns a response message to WAP GW.

18. WAP GW of the roaming location returns the response message to

WAP GW of the same place.



Explanations:







66


19. WAP GW of the roaming location sends GGSN the response message

that is processed by WAP.

20. WAP GW generates a bill file record.



Explanations:







67


3.3.5 Process of Handling WAP Browse Service for PPC Users



Explanations:







68




Explanations:







69



Explanations:


2) WAP GW initiates real-time monitoring, and submits an expense reservation request to SCP

periodically.



Explanations:







70




5) WAP GW resolves the message.

6) After resolution, WAP GW performs URL access control for URL

Control List.

7) For prohibited URL, WAP GW directly redirects the user to the preset page containing error



Explanations:







71


messages.

8) WAP GW extracts the service code and SP code from the valid URL, and then sends an

authentication request to DSMP.

9) DSMP sends a request response to WAP GW.

10) If the authentication is passed, DSMP sends a charging rating response message to WAP GW.

If the authentication fails, WAP GW sends the end user a preset page containing error



Explanations:







72


messages, and does not sends a charging rating request to DSMP.

11) If the rating is successful, WAP GW sends a HTTP request to SP/CP, and involves the user

pseudo code in the request message.

12) SP/CP returns a response message.

13) WAP GW sends an expense reservation request to SCP.

14) SCP sends a response message to WAP GW.



Explanations:







73


15) WAP GW sends the end user a response message processed by

WAP code through GGSN.

16) For a successful response message, WAP GW sends a withholding request to SCP. For a failed

response message, WAP GW sends a reimbursement request.

17) SCP sends a response message to WAP GW.

18) WAP GW generates a bill.



Explanations:







74


Note: This process just describes the processing method related to PPC users.



Explanations:







75


3.3.6 Processing Procedure for PUSH over IP



Explanations:







76




Explanations:







77


Figure 11 Processing procedure for PUSH over IP

Explanations:

1) PI sends a PUSH request containing SP ID and service code to WAP GW.

2) WAP GW sends an authentication request to DSMP to check if the SP has



Explanations:







78


subscription relationship with carriers.

3) DSMP sends an authentication response to WAP GW.

4) After SP authentication succeeds, WAP GW sends an

authentication request of user service subscription relation to DSMP.

5) DSMP sends a response message to WAP GW.

6) For the second media type, WAP GW sends a service charging rating request to



Explanations:







79


DSMP.

7) DSMP sends a response message to WAP GW.

8) For PPC users, WAP GW sends a charging reservation request to SCP.

9) SCP sends a withholding reservation response to WAP GW.

10) After the withholding reservation succeeds, if the user is offline and the user terminal

supports SIR, WAP GW launchse SIR through SMS bearer. If the user is online, there



Explanations:







80


are the following two occasions:

If the WAP connection is not established, SIR is sent to the terminal through S-

Unit-Push. The following goes to step 16.

If the WAP connection is established, there is no need to send SIR. What follows

is step 18.

11) WAP GW sends the CMPP_SUBMIT request to ISMG. The SM contents are data of



Explanations:







81


coded WAP PUSH SIR.

12) ISMG returns the CMPP_SUBMIT_RESP message to WAP GW.

13) ISMG sends a short message to the user terminal through SMSC.

14) ISMG sends a message of status report to WAP GW.

15) WAP GW returns a response message to ISMG.

16) After receiving WAP PUSH SIR, if the user terminal supports the PUSH contents, the



Explanations:







82


user terminal activates the network connection and sends a WSP/TCP connection

request to the specified PPG connection point in SIR.

17) On receiving the connection request, WAP GW (PPG) returns a confirmation message

to the user terminal.

18) WAP GW (PPG) sends PUSH contents (WSP-Confirmed Push) to the user terminal

through the established connection.



Explanations:







83


19) On receiving the PUSH contents, the user terminal returns a confirmation message to

WAP GW (PPG).

20) WAP GW acts based on the confirmation result of PUSH.

For PPC users

If the delivery succeeds, WAP GW sends a withholding request to SCP

If the delivery fails, WAP GW sends a reimbursement request.



Explanations:







84


For PUB users, WAP GW generates bill records.

WAP GW also generates bill records for PI.

This step is applicable to the second media type.

21) WAP GW sends a PUSH result notice to PI.

22) PI returns a notice response to WAP GW.



Explanations:







85


3.3.7 Processing Procedure for POP3/SMTP Mail Service



Explanations:







86




Explanations:







87


Figure 12 Processing procedure for POP3/SMTP mail service

Explanations:

1. A user terminal sends a TCP connection request to WAP GW. Port of

POP3 is 110 and Port of SMTP is 25.

2. WAP GW establishes a TCP connection to the terminal through

standard three-way handshake, and then returns welcome information

to the terminal.



Explanations:







88


3. The terminal requests for login, and reports the user name to WAP

GW.

4. WAP GW identifies the user login name, SP and SERVICE identifiers

according to the user name.

5. WAP GW sends SP service authentication request to DSMP according

to SP and SERVICE identifiers.

6. DSMP returns a response to SP service authentication request.



Explanations:







89


7. If the authentication succeeds, WAP GW finds out MSISDN according

to the terminal address from TCP connection, and sends a user

service authentication request to DSMP.

8. DSMP returns a response to the user service authentication request.

9. If the authentication succeeds, WAP GW finds out the email server

address according to descriptors of DSMP, and sends a TCP

connection request to the destination POP3/SMTP Email Server.



Explanations:







90


10. WAP GW establishes a TCP connection with POP3/SMTP Email

Server through standard three-way handshake.

11. WAP GW forwards the login request to POP3/SMTP, and reports the

analyzed login name.

12. POP3/SMTP Email Server returns a login response to WAP GW. Then

WAP GW forwards the response to the terminal.

13. With a successful user login, the terminal can send any POP3/SMTP

request to WAP GW.



Explanations:







91


14. WAP GW monitors the request sent by the terminal and sends a rating

request to DSMP if necessary. Otherwise, WAP GW jumps to step 18.

15. DSMP returns a rating response to WAP GW.

16. For a PPC user, WAP GW sends an expense reservation request to

SCP.

17. SCP returns a reservation response to WAP GW.

18. WAP GW forwards the request from the terminal to Email Server.



Explanations:







92


19. Email Server returns a response to WAP GW. Then WAP GW

forwards the response to the terminal.

20. WAP GW monitors responses of Email Server.

For PPC users, if the successful request needs charging, WAP GW

sends a withholding confirmation message to SCP.

For PUB users, WAP GW directly jumps to step 22.

21. SCP returns a withholding confirmation response to WAP GW.



Explanations:







93


22. WAP GW generates a call detailed record (CDR).

23. On receiving the QUIT request from the terminal, WAP GW forwards

the request to Email Server.

24. The terminal removes the TCP connection to WAP GW.

25. WAP GW removes the TCP connection to Email Server.



Explanations:







94


3.3.8 MMSC Address Translation Process (Proxy is Redirector)



Explanations:







95




Explanations:







96


Figure 13 MMS process

Explanations:

Figure 13 is an example of obtaining MM immediately. Redirector fulfills

MMSC address translation.

1. Using WSP as a bearer protocol, MS sends the M-Send.req request to

WAP GW. The URL of MMSC set on the terminal is

mmsc.monternet.com.



Explanations:







97


2. WAP GW queries the IP host address of mmsc.monternet.com

according to DNS, and sends the request containing M-Send.req to

Redirector.

3. The request is a standard MM1 Protocol message and the bearer is

HTTP.

4. On receiving the request message from WAP GW, Redirector obtains

identity of the originator subscriber and sends a query request to

ENUM DNS Server.



Explanations:







98


5. ENUM DNS Server returns the query result containing the home

MMSC of the originator subscriber to Redirector.

6. Redirector forwards the M-Send.req request to MMSC.

7. The home MMSC of the originator responds to the request from

Redirector and includes M-Send.conf in the response to identify

acceptance.

8. Redirector forwards the M-Send.conf message of MMSC to WAP GW.



Explanations:







99


9. WAP GW forwards the M-Send.conf message of MMSC to MS.

10. The home MMSC of the originator processes the M_Send.req request,

extracts the address of the originator subscriber, and sends a PUSH

message containing M-Notification.ind to the target subscriber before

arrival of new multimedia messages.

11. The recipient subscriber initiates the M-Retrive.req request according

to the target address in M-Notification.ind. Then WAP GW forwards the

request to the target MMSC.



Explanations:







100


12. The home MMSC of the recipient subscriber returns M-Retrive.conf to

WAP GW. After receiving the request forwarded by WAP GW, MS

obtains MM through WSP GET.

13. When the recipient receives the request, MS sends the M-

NotifyResp.ind request.

14. WAP GW queries the IP host address of mmsc.monternet.com

according to DNS, and sends the HTTP request containing M-

NotifyResp.ind to Redirector.



Explanations:







101


15. The request is a standard MM1 Protocol message and the bearer is

HTTP.

16. On receiving the request message from WAP GW, Redirector obtains

the recipient subscriber identity from the request and sends a query

request to ENUM DNS Server.

17. ENUM DNS Server returns the query result containing the home

MMSC address of the recipient subscriber.



Explanations:







102


18. Redirector forwards M-NotifyResp.ind to the home MMSC of the

recipient.



Explanations:







103


3.3.9 KJAVA Download Process



Explanations:







104




Explanations:







Us

A

Pr

105


Figure 14 KJAVA download process

Explanations:

1. The terminal initiates a KJAVA OTA Server browse request.

2. WAP GW forwards the request to OTA Server.

3. OTA Server submits an authentication request to DSMP.

4. DSMP returns the authentication result to OTA Server.



Explanations:







106


5. OTA Server returns the response to WAP GW.

6. WAP GW forwards the response message to the terminal.

7. The terminal sends a request for JAVA descriptive files.


9. OTA Server processes the request, including terminal adaptation

check, service rating processing and expense reservation for PPC

users.



Explanations:







107


10. OTA returns the response result to WAP GW.

11. WAP GW returns the response message to the terminal.

12. The terminal sends WAP GW a request for downloading JAR files.


14. OTA returns the response message to WAP GW.

15. WAP GW forwards the response message to the terminal.



Explanations:







108


16. The terminal JAVA Manager (JAM) installs the JAVA program.

17. The terminal sends a Status Report request to WAP GW.

18. WAP GW forwards the Status Report to OTA Server.

19. OTA Server triggers the charging processing procedure.

20. OTA Server returns a response message to WAP GW.

21. WAP GW returns the response message to the terminal.



Explanations:







109


Notes:

This process mainly describes contents related to JAVA download. For

processing procedure of OTA Server, interaction between OTA Server and

SCP, and interaction between OTA Server and DSMP, see the WAP

business process.

OTA Server aforementioned is operated by carriers. For downloading

servers not operated by carriers, see the processing procedure between

WAP GW and Web Server.



Explanations:







110


Appendixes:

Appendix 1: Introduction to WAP 2.0



Explanations:







111


Appendix 2: Acronyms

WAP Wireless Application Protocol



Explanations:







112


WML Wireless Markup Language (corresponding to HTML in Internet; WML and HTML are

subsets of XML)

WSP Wireless Session Protocol

WTP Wireless Transaction Protocol

ISMG Internet Short Message Gateway

CMPP CHINA Mobile Peer to Peer



Explanations:







113


EMPP Extensible Messaging and Presence Protocol

DSMP Data Service Management Plat

ENUM E.164 Number Mapping (mapping from E.164 Number to DNS, as defined by

RFC2916)



Explanations:







114

Documents

WAP White Paper 20031202 B V1.0