This invention is bases on a priority application EP 03 290 800.6 which is hereby incorporated by reference.
The present invention relates to telecommunication methods for wireless networks, and more particularly to location based services.
The location Inter-operability Forum (LIF) has defined a specification for a Mobile Location Protocol (MLP). MLP is a secure access method that enables Internet applications to query location information from a wireless network, irrespective of its underlying air interface technologies and positioning methods. The MLP serves as an interface between a location server and a location-based application. One of the location services defined in MLP is “Triggered Location Reporting Service”. This is a service used, when the mobile subscriber's location should be reported at a specific time interval or on the occurrence of a specific event. The location report does not contain data, which would enable to identify the mobile subscriber for privacy reasons.
The present invention aims to provide an improved telecommunication method, in particular for usage on the basis of MLP. Further the invention aims to provide an improved location server and location based application.
The present invention provides for a telecommunication method for a wireless network which enables to provide user data to a mobile subscriber without revealing the identity of the mobile subscriber to a location based application, which requires to send the user data. In essence, this is accomplished by assigning a temporary identifier, such as a session identifier, to the mobile subscriber, when it enters the specified location.
On the level of the location server, the temporary identifier can be stored together with the Mobile Subscriber Identifier (MSISDN). The MSISDN enables the location server to send various types of messages to the corresponding mobile subscriber. This MSISDN is not communicated from the location server to the location-based application but only the temporary identifier, which has been assigned to the MSISDN. This way the location based application can request the location server to send user data to the mobile subscriber, which entered the location without a need for the MSISDN.
In one application the specified location is a commercial area, such as a supermarket. When a mobile subscriber enters the supermarket, this is detected by the location server and a session identifier is assigned to the mobile subscriber. The session identifier is forwarded from the location server to the location-based application.
The location-based application can in turn request that certain user data be transmitted by making reference to the session identifier. In response, the location server sends out a message of the requested method type with the user data by means of the MSISDN, which is assigned to the session identifier. The user data can be of any type. In the case of the supermarket the user data can contain advertisement or marketing information.
In the following preferred embodiments of the invention will be described in greater detail by making reference to the drawings in which:
Location server 106 is coupled to wireless network 102. Location server 106 has program 108, which serves to generate database 110.
Location based application client 112 can communicate with location server 106. For example, the Internet can be used as communication means for data exchange between the location server 106 and location based application client 112.
Location based application client 112 can request a trigged location reporting service from location server 106 in accordance with MLP. In the request a location specific event is indicated as a trigger for the location reporting. In the example considered here, the event is when a mobile subscriber enters a specified area, which is commercial area 104. Alternatively, other location specific events can be selected as a trigger, such as when the mobile subscriber exits the commercial area 104.
When location server 106 detects that mobile subscriber 114 enters commercial area 104 the location reporting is triggered. Location server 106 receives the MSISDN from mobile subscriber 114. By means of program 108 a Session ID is generated for this MSISDN. Both, the MSISDN and the Session ID, are stored in database 110 for later reference.
Location server 106 sends a response to location based application client 112 in accordance with the MLP. In addition to MLP the response contains the Session ID, which has been assigned to the MSISDN of the mobile subscriber 114 by program 108 of the location server 106.
In response, location based application 112 sends a request to location server 106 to send certain user data in the session with Session ID. The Session ID is used as a key by program 108 to access the corresponding MSISDN of mobile subscriber 114. The user data is than sent from location server 106 to mobile subscriber 114 by means of an SMS, MMS or another message type supported by wireless network 102.
The format of the push request of location-based application 112 to location server 106 can be XML. The structure of the XML push request can be defined by means of Document Type Definition (DTD) files, which are stored on the location server 106, and the location based application client 112. For example, the Session ID, the type of message to be sent from location server 106 to the mobile subscriber, and the user data to be transmitted to the mobile subscriber can be the arguments of the request.
In step 202 the location server detects that a mobile subscriber enters the specified area. In step 204 the location server assigns a Session ID to the MSISDN of the mobile subscriber. The Session ID and the MSISDN are stored in the database of the location server for later reference.
In step 206 the location server sends a MLP response to the location-based application including the Session ID but not the MSISDN. In step 208 the location based application sends a Push Request including the Session ID, the message type for sending the user data (SMS, MMS, . . . ) and user data as arguments to the location server. In step 210 the location server uses the Session ID as a key in order to retrieve the MSISDN, which has been assigned to the Session ID, from the database. By means of the MSISDN the user data is than sent from the location server to the mobile subscriber using the specified message type.
Number | Date | Country | Kind |
---|---|---|---|
03290800 | Mar 2003 | EP | regional |
Number | Name | Date | Kind |
---|---|---|---|
6697625 | Rune | Feb 2004 | B1 |
20010014911 | Doi et al. | Aug 2001 | A1 |
20030153330 | Naghian et al. | Aug 2003 | A1 |
20040002897 | Vishik | Jan 2004 | A1 |
20040097229 | Muhonen et al. | May 2004 | A1 |
Number | Date | Country |
---|---|---|
1 126 732 | Aug 2001 | EP |
2 372 175 | Aug 2002 | GB |
WO 0128273 | Apr 2001 | WO |
WO 0165818 | Sep 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20050003806 A1 | Jan 2005 | US |