So as part of the specification, we are in the process of registering with IANA two known SMS ports for location exchange purposes. IANA controls a range of SMS ports that have a known service handler listening to that port; this is exactly the same concept as in TCP/IP world. For example, Wap Push is assigned port 2948, so that whenever there is a SMS coming to that port, the device knows that this is a Wap Push message.
Now, the two ports what we'll register is for these use cases:
1) the first port X would be dedicated to incoming location messages. The messages must be in the Landmark Exchange Format as specified in JSR293 specification. When this message is received, the handler is started on the device and it will give the user an option eg. to view the landmark on a map.
2) second port Y would be dedicated for incoming location requests. Location request SMS is sent by someone who wants to get to know your location. The TP-User-Data field of the SMS may be empty, or contain user-generated message, such as "Hey, where you at? wanna have lunch?" The fact that this message was received in the dedicated port identifies it as a location request, thus the TP-User-Data field may also be empty. The sender is identified by the sender MSISDN. When the recipient receives a location request, the handler will prompt the user whether the user wants to response her/his current location, or based on trust policy, it will respond to request automatically. For example, you could set that your wife is able to get your location automatically. By user acceptance or privacy policy permitting, the device performs positioning and then response is sent back to sender's MSISDN/port X (use case 1) with a message formatted in 293's Landmark Exchange Format.
Cool, huh? I have been many years wondering why this kind of peer-to-peer location exchange has not yet been standardized...


Reply With Quote


