Hi,
We have been testing a networked MIDlet on a J-Phone SH52 handset.
Profiling our traffic shows that J-Phone specific HTTP headers account for
the majority of the bandwidth consumed by our application. For example, a
HTTP POST request with a content-length of 15 actually consumes 417 bytes -
mainly because of x-jphone... headers.
My understanding of J-Phone's packet charges is that a billing unit is 128
bytes, for which the subscriber is charged 0.3 yen.
We have a protocol that has been highly optimised so that most HTTP requests
sneak in at 125 bytes - 0.3 yen - whilst containing all of the required
headers for HTTP/1.1. It seems a little unfair that J-Phone add additional
headers to blow our request size out to four billing units or 1.3 yen!
Can anyone tell me:
1. Does anyone have a precise definition for what constitutes the 128 byte
billing unit? Is this the HTTP Content-Length (ie the payload only), the
entire HTTP headers plus content-length or something else?
2. Are the x-jphone- headers generated at the handset or mobile data
gateway? In other words, do they actually send those x-jphone headers over
the air and bill the unwary subscriber for them?
The following press release from J-Phone suggests that - for Super Mail
users at least - a message response is billed at a single packet rate.
"those wishing to confirm message delivery will no longer be charged packet
data costs (0.3 yen)."
I assume this response is sent via HTTP. If so, they cannot be charging for
those additional headers - right?
http://www.j-phone.com/english/release_detail/21121e/21121e.html
3. Can anyone provide me with pointers to DoCoMo / KDDI billing details /
HTTP header information etc.
Many thanks in advance for responses.
Chris Wooldridge
FYI, these are the HTTP headers added by J-Phone that we see but do not
require:
Accept-Encoding:
x-jphone-display: 120*130
x-jphone-msname: J-SH52
x-jphone-sound: 5
x-jphone-color: C65536
x-jphone-smaf: 40/pcm/grf
x-jphone-uid: a22t4fKFPdFzZ6ja
User-Agent: J-PHONE/4.1/J-SH52/SNJSHD3047292 SH/0002aa Profile/MIDP-1.0
Configuration/CLDC-1.0 Ext-Profile/JSCL-1.1.1
Received on Fri Mar 28 01:22:37 2003