RE: RADIUS ACCT info used in WAP Push
Hi, > > How about digging into wapbox here and check if you can send us a > patch. I'd be willing for review. > I'm not sure I'd be able to, since my C is a bit too shaky :-) If I manage to, I'll send it :-)) If anyone else has the time and want to, that may be a better option. Regarding the mapping, yes you'd need to have the RADIUS ACCT information from the operator's GPRS node sent to you, and you'd need to probably have a VPN to the operator to actually access their IP addresses. Regarding the constantly online thing. The new phones (from SonyEricsson K700 and all new Nokias) can have more than one PDP context (GPRS IP address) attached all the time. The WAP browser typically opens up a GPRS session when it starts and ends it when it closes, but newer phones are more and more used to keeping these up a long time. Other clients, such as J2ME/SYMBIAN etc can keep their GPRS session open while they are running. Regards, Lars
Re: RADIUS ACCT info used in WAP Push
Lars Kristian Roland wrote:
Yes, SMS is always an option, but GPRS is cheaper, so it'd be good to be
able to use it when possible, at least when there's a lot of WAP Push,
for example as part of an online game or other. It could also be the
case that the application knows the MSISDN, but doesn't know the IP of
the phone to send to.
I'd consider this the normal case. The IPs are usually "covered"
inside the GPRS network and when your phone talks to the outside
world, it's usually NATed.
Now that would obviously be even more sexy! It'd be excellent, in
fact...
How about digging into wapbox here and check if you can send us a
patch. I'd be willing for review.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.2.2 (Cygwin)
mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-END PGP PUBLIC KEY BLOCK-
Re: RADIUS ACCT info used in WAP Push
Paul Keogh wrote:
a) PI sends push msg to PPG
b) PPG tries to resolve MSISDN into IP (from RADIUS acct mapping)
c) if MSISDN is online at this time, PPG is able to address the push
message via IP
d) if it's not online, utilize SMS bearer to push the message
(this is
the current default behavior for MSISDN targets)
This is an interesting suggestion and could solve some issues
around IP addressable phones.
Do GPRS operators maintain this kind of RADIUS accounting information
by default ? And if they do, does the network allow routing of IP
packets back to the device ?
I guess they do maintain such RADIUS acct information. If they use it
for PPG issues, that's a totally different thing.
AFAIK, you can't address the IPs from the outside world :(
Is anyone doing Push over IP ? This option offers a cost saving to
the operator by moving Push from SMS to IP, particularly
interesting for MMS notifications (Several operators have told me
MMS is pushing SMSC license costs up).
hmmm, that's true for GPRS connections. But AFAIK, GPRS does not mean
that you have a permanent IP stack available at the phone. Does it?
If yes, then you're obviously right that this would reduce SMS costs,
due to IP addressing. Unfortunatly external providers (like we at
Wapme) will a) not be able to send packets to the GPRS IPs, b) won't
know which MSISDN<->IP mapping is there. So you can't address them
actually via IP from the outside world.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.2.2 (Cygwin)
mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-END PGP PUBLIC KEY BLOCK-
RE: RADIUS ACCT info used in WAP Push
Hi, > > The _only_ benefit I see from this here is to allow PI (push > initiators) to send push messages over PPG with MSISDNs as > target, and > wapbox would try to resolve this into IPs, in case the MSISDN is > online and connected to the NAS at that specific point of time. So > something like this: Yes, SMS is always an option, but GPRS is cheaper, so it'd be good to be able to use it when possible, at least when there's a lot of WAP Push, for example as part of an online game or other. It could also be the case that the application knows the MSISDN, but doesn't know the IP of the phone to send to. > > a) PI sends push msg to PPG > b) PPG tries to resolve MSISDN into IP (from RADIUS acct mapping) > c) if MSISDN is online at this time, PPG is able to address the push > message via IP > d) if it's not online, utilize SMS bearer to push the message > (this is > the current default behavior for MSISDN targets) Now that would obviously be even more sexy! It'd be excellent, in fact... Lars
RE: RADIUS ACCT info used in WAP Push
> > a) PI sends push msg to PPG > b) PPG tries to resolve MSISDN into IP (from RADIUS acct mapping) > c) if MSISDN is online at this time, PPG is able to address the push > message via IP > d) if it's not online, utilize SMS bearer to push the message > (this is > the current default behavior for MSISDN targets) This is an interesting suggestion and could solve some issues around IP addressable phones. Do GPRS operators maintain this kind of RADIUS accounting information by default ? And if they do, does the network allow routing of IP packets back to the device ? Is anyone doing Push over IP ? This option offers a cost saving to the operator by moving Push from SMS to IP, particularly interesting for MMS notifications (Several operators have told me MMS is pushing SMSC license costs up).
Re: RADIUS ACCT info used in WAP Push
Lars Kristian Roland wrote:
Hi,
Have you considered adding the RADIUS information in such a way that the
client pushing a wap push via the push proxy can send the pap-request to
an msisdn rather than an IP also when sending a udp push, but the push
proxy sends it to the IP address (wap push proxy must then do the
mapping between msisdn and ip address based on the information from
radius acct)?
I can see that you've implemented this mapping for receiving acct radius
info for normal wap requests, and I guess this would be a small
extension to that???
Hi Lars,
a good question.
But as I remember, Kannel's PPG _is_ able to send Push messages to
MSISDN numbers generically. Since it will pass it over the SMS bearer
to the phone. So I don't see the necessarity to have the RADIUS acct
mapping active here.
The _only_ benefit I see from this here is to allow PI (push
initiators) to send push messages over PPG with MSISDNs as target, and
wapbox would try to resolve this into IPs, in case the MSISDN is
online and connected to the NAS at that specific point of time. So
something like this:
a) PI sends push msg to PPG
b) PPG tries to resolve MSISDN into IP (from RADIUS acct mapping)
c) if MSISDN is online at this time, PPG is able to address the push
message via IP
d) if it's not online, utilize SMS bearer to push the message (this is
the current default behavior for MSISDN targets)
Hmm, Aarno, some comments from your side?
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.2.2 (Cygwin)
mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-END PGP PUBLIC KEY BLOCK-
