This week's book giveaway is in the iOS forum.
We're giving away four copies of Classic Computer Science Problems in Swift and have David Kopec on-line!
See this thread for details.
Win a copy of Classic Computer Science Problems in Swift this week in the iOS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Java SyncML Device Management Midlet  RSS feed

Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We can use both WAP PPG / SMS as notification mechanism to start a
SyncML DM Session with the device ie for delivering "Package 0".
Let us assume a scenario where a Customer Service Representative(CSR)
is doing a WAP setting for a customer's device using operator's web
portal attending the call by the customer. Now the steps will involve
1) CSR -> Server - Submit the mobile number and start
2) Server -> Device - Send Notification SMS through say SMPP Gateway
(Package 0)
3) Device -> Server - Pass on credentials and DevInfo
(HTTP POST to server URL(say a Java Servlet) - Package 1)
4) Server -> CSR - Present the current device configuration
5) CSR -> Server - Modify the parameters and submit
6) Server -> Device - Send the SyncML commands(Replace etc...for
correct WAP Settings) and also status message for earlier devinfo
sent by the device
(HTTP Reply for the HTTP POST by device in step 3)
7) Device -> Server - Status for the commands sent in step 6
(HTTP POST to Server URL)
8) Server -> Device - Session closure message
(HTTP Response for previous HTTP POST by device)
9) Server -> User - Display a successful completion message
Between step 2 and step 3 there can be enormous time delay because of
SMSC load (typically, on a Christmas Day etc..). If a CSR submits the
data and waits he/she may be waiting till the SMS reaches the mobile
and the same starts the SyncML session with server.
Therefore, in the above scenario of an Online update how this could
be handled?
For the HTTP Post in step 3, HTTP reply is provided in step 6.
The timegap between this could be unacceptably long because we are
having a human intercation.
Will the HTTP reply be really delayed this way? (seems very odd)
In case of a uniterrupted server handled situation, there will be no
need for going through above route and hence implementation of the
server will not be a big issue.
But how to go about the flow in a situation where Human Interaction
is unavoidable as in the above use case.
Thank you for patiently reading this and replying too....
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!