Push service features via uaprof
This presentation is the property of its rightful owner.
Sponsored Links
1 / 9

PUSH Service Features via UAPRof PowerPoint PPT Presentation


  • 49 Views
  • Uploaded on
  • Presentation posted in: General

PUSH Service Features via UAPRof. Andrew Randle e-mail: [email protected] 8th February 2000. Telecommunications Technologies Division. Introduction. Basic Idea: Add UAProf attributes enabling the client to influence the PPG. To control:

Download Presentation

PUSH Service Features via UAPRof

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Push service features via uaprof

PUSH Service Features via UAPRof

Andrew Randle

e-mail: [email protected]

8th February 2000

Telecommunications Technologies Division


Introduction

Introduction

  • Basic Idea:

    • Add UAProf attributes enabling the client to influence the PPG.

  • To control:

    • Who can and cannot forward PUSH messages past the PPG.

    • The timing of “store and forward”

    • The establishment of new sessions on roamed-to networks

      • Independent of the roaming agreement mechanism.


Access control

Access Control

  • UAProf attributes sent from client  PPG:

    • AccessControl: Toggles access control on the PPG - ON or OFF

    • AccessControlWhiteList: List of Internet Servers allocated exclusive rights to push content to the mobile client

    • AccessControlBlackList: List of Internet Servers that may not push content to the mobile client


Batch control

Batch Control

  • UAProf attributes sent from client  PPG, controls “Store and Forward”:

    • BatchFrequency: Frequency of forwarding stored PUSH messages to client

    • BatchReference: A reference time to synchronise the BatchFrequency attribute

    • BatchNext: An alternative approach to BatchFrequency+BatchReference. Specifies a date and time to send the next batch of messages. Thereafter, messages are sent asynchronously.


Rdf example

RDF Example

<?xml version=”1.0”?>

<rdf:RDF xmlns:rdf=”http://www.w3.org/TR/1999/02/22-rdf-syntax-ns##”

xmlns:rdfs=”http://www.w3.org/1999/PR-rdf-schema-19990303#”

xmlns:prf=”http://www.wapforum.org/UAPROF/ccppschema-19991014#”>

<rdf:Description ID=”PushSessionParameters”>

<prf:AccessControl>ON</prf:AccessControl>

<prf:AccessControlWhiteList>

<rdf:Bag>

<rdf:li>214.121.6.48</rdf:li>

<rdf:li>132.163.64.200</rdf:li>

<rdf:li>184.62.201.3</rdf:li>

<rdf:li>164.210.7.99</rdf:li>

</rdf:Bag>

</prf:AccessControlWhiteList>

<prf:BatchFrequency>120</prf:BatchFrequency>

<prf:BatchReference>13:45</prf:BatchReference>

</rdf:Description>

</rdf:RDF>

  • PPG reacts to the description ID ”PushSessionParameters”


Redirecting push messages

1) New session

New PPG

Push Internet Server

Client

2) CC/PP notify old PPG, before session is torn down

4) CC/PP notifies subscribed Push Server

Old PPG

3) Re-direct stored content & traffic. Time limited

Mobile N/W

Internet

Redirecting Push Messages

  • For roaming - push messages can be redirected to the new PPG:


Redirecting push messages1

Redirecting Push Messages

  • CPI format enabling PPG to re-direct messages to new PPG:

    <?xml version=”1.0”?>

    <rdf:RDF xmlns:rdf=”http://www.w3.org/TR/1999/02/22-rdf-syntax-ns##”

    xmlns:rdfs=”http://www.w3.org/1999/PR-rdf-schema-19990303#”

    xmlns:prf=”http://www.wapforum.org/UAPROF/ccppschema-19991014#”>

    <rdf:Description ID="PPGRedirect">

    <prf:MSISDN>+4407887601675</prf:MSISDN>

    <prf:AppAddr>[email protected]</prf:AppAddr>

    <prf:NewPPGHost>www.wwireless.com</prf:NewPPGHost>

    <prf:NewPPGPost>/cgi-bin/wap_push.cgi</prf:NewPPGPost>

    </rdf:Description>

    </rdf:RDF>

  • Description ID “PPGRedirect” targets the CPI at the PPG

  • Unique & permanent MSISDN binds the client ID to both the new & old PPG.


Redirecting push messages2

Redirecting Push Messages

  • CPI Format enabling Internet Servers to redirect PUSH messages to new PPG:

    <?xml version=”1.0”?>

    <rdf:RDF xmlns:rdf=”http://www.w3.org/TR/1999/02/22-rdf-syntax-ns##”

    xmlns:rdfs=”http://www.w3.org/1999/PR-rdf-schema-19990303#”

    xmlns:prf=”http://www.wapforum.org/UAPROF/ccppschema-19991014#”>

    <rdf:Description about="PushGatewaySwitching">

    <prf:ClientName>Fred_Flintstone</prf:ClientName>

    <prf:PushService>881-331332</prf:PushService>

    <prf:AppAddr>[email protected]</prf:AppAddr>

    <prf:NewPPGHost>www.wwireless.com</prf:NewPPGHost>

    <prf:NewPPGPost>/cgi-bin/wap_push.cgi</prf:NewPPGPost>

    </rdf:Description>

    </rdf:RDF>


Conclusions

Conclusions

  • UAProf will allow the client’s PUSH application to communicate with the application on the:

    • PPG

    • Internet PUSH Server

  • PPG Redirection utilises:

    • Application Addressing of the client

    • HTTP POSTing to the PPG

  • ….. while maintaining neutrality of roaming infrastructure

    • through the use of MSISDN


  • Login