GB2528698A

GB2528698A - Location-specific messaging

Info

Publication number: GB2528698A
Application number: GB1413399.5A
Authority: GB
Inventors: Philip James Naylor
Original assignee: Individual
Current assignee: PETER NAYLOR
Priority date: 2014-07-29
Filing date: 2014-07-29
Publication date: 2016-02-03
Anticipated expiration: 2034-07-29
Also published as: GB201413399D0; GB2528698B

Abstract

A method of determining the position from which a message has been sent is disclosed. The method comprises the steps of: inputting a URL and a position code, at a client device (11), wherein the URL and the position code are obtained from a first marker (1) positioned at a location and the position code is indicative of the first marker (1) location; transmitting the position code and a request for a webpage corresponding with the URL; acquiring position data indicative of the first marker (1) location, based on the position code; associating the position data with the client device (11); receiving, at the client device (11), a webpage in response to the webpage request; using the webpage, at the client device (11), to a send a message; and determining a position based on the message and the association of the position data with the client device (11). Preferably the marker is a QR code or NFC tag.

Description

Location-Specific Messaging The present invention relates to a method and apparatus for determining the position from which a message has been sent.

In some situations it is desirable to send a message which indicates the position from which it was sent. Conventional methods for achieving this often use GPS for positioning. Typically GPS is only accurate to a few meters. Therefore, when two people sitting next to one another send messages, generally it is not be possible to distinguish between the respective positions from which the messages were sent, when GPS is used for positioning.

GF'S can be unreliable. It is especially unreliable in urban environments and when used indoors. Thus, when GPS is used to determine the position from which a message was sent, it is likely that an inaccurate position will be determined.

According to a first aspect of the invention there is provided, a method of determining the position from which a message has been sent, the method comprising the steps of: inputting a URL and a position code, at a client device, wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; transmitting the position code and a request for a webpage corresponding with the URL; acquiring position data indicative of the first marker location, based on the position code; associating the position data with the client device; receiving, at the client device, a webpage in response to the webpage request; using the webpage, at the client device, to send a message; and determining a position based on the message and the association of the position data with the client device.

In this way, a message can be sent which accurately indicates the location from which the message was sent. The marker can be fixed to a specific location and assigned a unique position code. By using the position code obtained from the marker, it is possible for the client device to send a message which accurately indicates the position from which it was sent. For this to work, it can be assumed that the user of the client device is positioned at the marker from which the position code has been obtained.

The marker can be associated with a specific set of co-ordinates or any other description of the marker's location. Thus, it is possible to determine the precise position from which the message was sent.

In order to implement the method all that is required is a client device with a web-browser connected to the internet; there is no need for the client device to be connected to another source for determining its position. Internet connectivity is readily available both indoors and outdoors. Thus, the method can operate effectively in both of these environments.

Preferably, each one of a plurality of markers is assigned a different position code. In this way, it is possible to avoid conflicts between marker codes. In addition, this increases the confidence in the assumption that the user is at a specific marker.

Preferably, the message sent using the webpage is a user defined message. The message may be sent from the first webpage delivered to the client device in response to the webpage request. Alternatively, the message may be sent from a different webpage which has been navigated to from the first webpage.

Preferably, the position data is acquired by the server by comparing information from at least a part of the position code against a database of marker locations. Preferably, the webpage is only received once the URL and the position code have been transmitted by the client device. Hence, the URL and the position code are transmitted before the webpage is received at the client device.

The step of associating the position data with the client device may comprise storing the position data at the client device; and the method may further comprise the steps of: transmitting the position data from the client device; and determining a position based on the position data.

In one example, a URL (Uniform Resource Locator) and a position code are obtained from the marker and input into the client device. A request for a webpage corresponding with the URL is transmitted to a server along with the position code. The server is then able to acquire the position of the client device based on the position code.

The server sends the webpage corresponding with the URL along with the position data to the client device. In this way, when the message is sent from the client device using the webpage it can also send the position data.

In another example, when the server sends the webpage to the client device it also stores a cookie at the client device. This cookie is indicative of the position data. Thus, the cookie can be used to define the position data.

The request for the webpage may be associated with an identification code indicative of the client device and the step of associating the position data with the client device may comprise: associating the identification code with the position data; and the method may further comprise the steps of: transmitting the identification code from the client device; and determining a position based on the identification code.

In one example, a URL and a position code are obtained from the marker and input into the client device. A request for a webpage corresponding with the URL is transmitted to a server along with the position code. The server is then able to acquire the position of the client device based on the position code. The webpage request contains information about the IP address and the port number over which the client device communicates with the server.

The server can associate the IP address and port number with the position data. Thus) when the message is sent from the client device, which also contains the IP address and the port number, the message can be associated with the position using the IP address and port number.

Preferably, the URL comprises the position code. Thus, only one string is required to be analysed in order to determine the position data and the webpage.

It is undesirable for the details of the URL containing the position code to be known to a potentially fake user. If the URL is known to a fake user it would be possible to send location specific messages without first interacting with the marker. In this situation the fake user could be located at a position other than that of the marker.

The first marker may comprise a near field communication tag. Using a near field communication (NEC) tag conceals the URL within the tag. This prevents the URL from being obtained by simply looking at the marker. This adds a security layer which will make it harder for the URL to be obtained and, thus, helps to prevent location specific messages being sent without first interacting with the marker.

The first marker may comprise a quick response code. A quick response (OR) code is a two-dimensional graphic encoded with information, in this case a URL. In the same way as with the NFC tag, by using a OR code as a marker, it is possible to prevent the URL from being obtained by simply looking at the marker.

The URL may comprise a position code comprising a query string indicative of first marker location. By using a query string to indicate the first marker location, the location information can be presented in a form which is more easily passed to an application.

Preferably, once the webpage corresponding with the URL has been received the query string is not displayed in the client device web-browser. This conceals the location-specific URL from the user. In this way, it is not possible to issue a request for a webpage corresponding with the URL on the marker unless the URL is obtained directly from the marker. This will help to prevent location specific messages being sent without first interacting with the marker.

To access the webpage corresponding with the URL and to acquire the position data it may be necessary to input the URL comprising the query string into the address bar. The length of the URL may be such that at least a part of the query string is not visible in the address bar of the web-browser application.

Preferably, the query string is not displayed in the client device web-browser once the webpage is returned. However, the URL and query string will be visible in the address bar for a brief moment before the webpage is returned. Hence, by making the length of the URL such that at least a part of the query string is not visible in the address bar of the web-browser application, it is possible to hide the part of the URL which indicates position data for this brief moment. This helps to conceal the location-specific URL.

The method may comprise the further steps of: inputting an access code into the web-browser and, if the access code is not correct, preventing the message from being sent from the webpage corresponding with the URL. This adds a security layer which will make it harder for the message to be sent and thus helps to prevent bogus alerts.

The access code may be displayed in the vicinity of or on the first marker. This will make it harder for the message to be sent unless the user is actually located at the marker and thus helps to prevent bogus alerts.

The URL obtained from the marker may comprise the access code. In this way, the extra step of inputting the access code as well as the URL is not required. This is a quicker and more convenient process. Preferably, the URL comprises a query string comprising the access code.

The method may comprise the further step of: opening a session associated with the initial request for the webpage corresponding with the URL, wherein, during the session, messages sent from devices other than the client device from which with the initial request for the webpage was sent are ignored. Thus, it is possible to be alerted only to messages sent from the client device that issued the initial webpage request.

The method may comprise the further steps of: using a camera to visually inspect the environment around the position of the first marker; and allowing a message sent from the client device to be ignored if a person was not located in the environment around the position of the first marker when the message was sent.

The method may comprise the further step of: on receipt of the request for the webpage corresponding with the URL, using the camera to visually inspect the location at which the first marker is positioned.

According to a second aspect of the invention there is provided, a system for determining the position from which a message has been sent, the system comprising one or more processors configured as: an input module, at a client device, arranged to input a URL and a position code, wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; a transmission module arranged to transmit the position code and a request for a webpage corresponding with the URL; an acquisition module arranged to acquire position data indicative of the first marker location, based on the position code; an association module arranged to associate the position data with the client device; a receiving module, at the client device, arranged to receive a webpage in response to the webpage request; a web module, at the client device, arranged to send a message using the webpage; and a determining module arranged to determine a position based on the message and the association of the position data with the client device.

According to a third aspect of the invention there is provided, a method of determining the position from which a message has been sent, the method comprising the steps of: inputting a URL and a position code, at a client device, wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; transmitting the position code and a request for a webpage corresponding with the URL from the client device; receiving, at the client device, a webpage in response to the webpage request; using the webpage, at the client device, to send a message.

According to a fourth aspect of the invention there is provided, a method of determining the position from which a message has been sent, the method comprising the steps of: receiving, at a server, a position code and a request for a webpage corresponding with a URL, wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; acquiring, at a server, position data indicative of the first marker location, based on the position code; associating the position data with the client device, using a server; transmitting the webpage corresponding with the URL from a server; receiving, at a server, a message sent using the webpage; and determining, at a server, a position based on the message and the association of the position data with the client device.

According to a fifth aspect of the invention there is provided, a system for determining the position from which a message has been sent, the system comprising a client device comprising one or more processors configured as: an input module arranged to input a URL and a position code wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; a transmission module arranged to transmit the position code and a request for a webpage corresponding with the URL; a receiving module arranged to receive a webpage in response to the webpage request; a web module arranged to use the webpage to send a message.

According to a sixth aspect of the invention there is provided, a system for determining the position from which a message has been sent) the system comprising one or more servers comprising one or more processors configured as: a receiving module arranged to receive a position code and a request for a webpage corresponding with a URL, wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; an acquisition module arranged to acquire position data indicative of the first marker location, based on the position code; an association module arranged to associate the position data with the client device; a transmission module arranged to transmit the webpage corresponding with the URL; a receiving module arranged to receive a message sent using the webpage; and a determining module arranged to determine a position based on the message and the association of the position data with the client device.

According to a seventh aspect of the invention there is provided, a marker, positioned at a location, encoded with a URL and a position code, wherein the position code is indicative of the marker location and the URL is indicative of a webpage from which a message can be sent.

According to an eighth aspect of the invention there is provided, a computer program product comprising instructions for carrying out any of the methods as described above.

Preferred features of the present invention will now be described, purely by way of example, with reference to the accompanying drawings, in which: Figure 1 schematically shows the basic general architecture of a system for determining the position from which a message has been sent; Figure 2 shows a flow diagram of an overview of a method for determining the position from which a message has been sent; Figure 3A shows an example of a webpage delivered to a smartphone from which a message can be sent; Figure 3B shows an example of a message sent from a smartphone displayed at an administrator device; Figure 4 shows a flow diagram of optional steps that may be performed in the method; and FigureS shows the appearance of a smartphone web-browser in Step 200 shown in Figure 2.

Referring to Figure 1 there is a marker 1 fixed at a specific location. The marker 1 comprises a near field communication (NFC) tag 3, a quick response (OR) code 5, a written Uniform Resource Locator (URL) 7 and an access code 9. The NFC tag 3 and the OR code 5 are each encoded with a URL that is specific to the marker 1.

A geographical area may comprise many markers each encoded with at least one unique URL. A webpage request can be made using the unique or "location-specific" URL belonging to one of the markers. In this situation it can be assumed that the webpage request was made in the vicinity of the marker encoded with the URL corresponding with the webpage request.

The URLs encoded onto the NFC tag 3 and the OR code 5 may be the same as or different to one another. The written URL 7 is also specific to the marker 1 and may be the same as or different to the URLs of the NFC tag 3 and OR codes. The written URL 7 may be a shortened URL which can forward the client device to a longer URL which is specific to the marker 1.

There is a client device 11, a server 13, an administrator device 15 and a web-cam 23. The client device 11, server 13 and administrator device 15 are connected with one another over the internet. The web-cam 23 observes the marker land its surrounding environment.

In this embodiment, the client device 11 is a smartphone comprising a web-browser application 17 and a processor 22. In the web-browser application 17 there is an address bar 19 for inputting URLs and a window 21 for displaying webpages.

S

In this embodiment the administrator device 15 is a tablet computer comprising a display screen 24 and a processor 16. The server 13 also comprises a processor 14.

Figure 2 shows a flow diagram of an overview of a method for determining the position from which a message has been sent. In Step 100 a URL and a position code are input at the smartphone 11. This may be achieved in a number of ways. For example, the URL and the position code may be input by holding the smartphone 11 against the NEC tagS. In another example, the URL and the position code may be input by reading the OR codes using a OR code reader app. Alternatively, a user may open a web-browser 17 on the smartphone 11 and enter the written URL 7 into the address bar 19.

In the above examples, the URLs encoded on the NFC tag 3 and OR code Sand written on the marker 1 contain the position code. However, the URL and the position code may be separate at the marker 1. For example, the OR codes may be encoded with a generic URL and the position code may be written alongside it. So, for example, when the OR code 5 is read by the OR code reader app, the app may also read the position code using the camera.

In another example there may be two NFC tags one encoded with the URL and the other encoded with the position code.

In Step 200 the position code and a webpage request are transmitted from the smartphone 11. In the example where the smartphone 11 is held against the NFC tag 3, a web-browser is opened automatically and a request for a webpage corresponding with the URL is sent to a server 13. This also happens when the OR codes is read by the OR code reader app. In another example, the user sends a request for the webpage corresponding with the written URL 7, which also contains the position code, using the web-browser 17.

In step 300 the server 13 receives the position code and the webpage request. The URL corresponding with the webpage request may contain the position code. Alternatively, the URL and the position code may be sent to the server separately.

In Step 400 the server 13 acquires position data. This process may involve referencing the position code against a database of position codes linked with position data. Alternatively, the position code may contain the position data.

In Step 500 the position data is associated with the smartphone 11 and a webpage corresponding with the URL is sent to the smartphone 11. In one example, the server 13 sends the position data to be stored at the smartphone 11. The server 13 may send a code indicative of the position data to be stored at the smartphone 11. The server 13 may send the position data or the code by sending a cookie along with the webpage.

In another example, the webpage request may contain the IP address and port number for the smartphone 11. In this case the IP address and port number form an identification code for the client device 11. In Step 500 the server 13 may associate the IP address and port number with the position data. Any future messages sent from the smartphone 11 will include the IP address and port number, and, thus, these messages can be associated with the position data.

In Step 600 the smartphone 11 receives the webpage and the position data, and the webpage is displayed. Referring to Figure 3A, the webpage 25 comprises a number of message options 26 which the user can select. There is also a custom text field 27 in which a user can write a custom message. The webpage 25 comprises a SEND button 28 which the user can press to send the selected message or messages.

In Step 700 the webpage is used to a send a message, and in Step 800 the message is received at the server 13. In Step 900, the server 13 determines the position from which the message was sent. In one example, this is achieved by analysing the position data or code sent from the smartphone 11 along with the message. In another example, this may be achieved by analysing the IP address and port number associated with the message.

After the message has been received at the server 13 and the position has been determined, the message can be displayed at the administrator device 15. Figure 38 shows an example of a display screen 24 at the administrator device 15. Here the messages selected by the user in are shown along with the location of the marker 1 from which the messages were sent.

Figure 4 shows a flow diagram of optional steps that may be performed at the server. In this embodiment the following URL (URL1) has been encoded onto the NEC tag 3 or OR code 5: www.area.com/progra m?lengthening_stri ng=111 1111111111111111111111111111111111 11111111111111111111111111111111111111111111111111111111111111111111111111 1&location=pointl&accesscode=12345 In this case the domain "www.area.com" indicates the general area in which the marker us located. The URL also comprises a query string which includes a lengthening string field, a location field and an access code field. The location field defines the specific location of the marker 1.

It is undesirable for the user to know the details of URL1. If the user were to know the details of URL1, it would be possible for that user to enter URL1 into any web-enabled device. The user would then be able to send messages to the administrator device 15 from any location.

However, these messages would appear to have been sent from the marker 1 location. Thus, a user could fool the system into thinking that they were at the marker 1 location when, in fact, they were somewhere totally different.

In this example, the URL query string comprises a lengthening string field. The information in this field is not used to provide information to the server 13. Instead, the function of this string is to elongate the part of the query string which precedes the section including the location and access code information. Thus, when the URL is automatically entered into the address bar 19, by reading the OR codeS or NFC tag 3, the location field and the access code field will be invisible to the user because only the first part of the URL will be shown in the address bar 19.

Figure 5 shows the appearance of the smartphone web-browser 17. The location field and the access code are not visible to the user in the address bar 19, due to the lengthening

string field.

A request for a webpage is sent from the smartphone 11. In this case the request is for the webpage corresponding with URL1. The query string part of URL 1 is used to inform the server 13 that the webpage request is being made from location "point 1" and includes the access code "12345". The query string could be encrypted so that the information in the query string can only be accessed by the server 13.

The webpage request is received at the server 13. In Step 311, the access code "12345" included in the URL query string is analysed at the server 13. This involves extracting the access code from the query string and comparing it against a database. The database shows a list of valid access codes. If the access code "12345" is invalid, the webpage from which location-specific messages can be sent will not be delivered to the smartphone 11.

Alternatively, if the access code is invalid, the messages may be sent from the smartphone 11 but the messages will be flagged to show that the access code was invalid. The messages may be sent from the smartphone 11 but they may not be shown at the administrator device 15 if the access code is invalid.

By containing an access code in the query string, it is possible to re-encode the NFC tag 3 at regular intervals to change the access code but to keep the rest of the URL the same. This will render any URLs obtained by a user obsolete after a while. In this way, an obsolete URL cannot be reused by the user in order to send a location-specific message from a location other than from that of the marker 1.

In Step 312, the web-cam 23 takes a photo of the marker land its surrounding environment.

Referring the Figure 35, when the location-specific message is received at the administrator device 15, the photo 29 is shown in association with the message. A short video of the moments after the webpage request was sent could be used instead of or in conjunction with the photo 29.

Providing the photo 29 of marker 1 and its surrounding environment, allows the administrator to see whether a person was in the vicinity of the marker 1 when the webpage request was sent. If this was not the case, it may be assumed that the webpage request was sent from a location other than that of the marker 1. In this case it may be assumed that a subsequent location-specific message received at the administrator device 15 was "fake".

On the other hand, if there was a person at the marker 1 when the webpage request was sent it may be assumed that the subsequent message was genuine.

The web-cam 23 may observe the marker 1 and its surrounding environment independently of the webpage request. Thus, when a message is received at the administrator device 15, the administrator could observe the web-cam feed to see if there is anyone located near the marker 1. This would help the administrator to decide whether the message is genuine.

The webpage 25 is delivered to the smartphone 11 and a generic URL is displayed in the address bar 19. This can be seen in the address bar 19 shown in Figure 3A. Here www.area.com/messageform is used as the generic URL.

If the generic URL were entered into a web-enabled device, it would not be possible to send a location-specific message from the webpage that would be returned. This is because the generic URL does not provide the location information or the access code.

The first part of URL1, shown in Figure 5, will only be visible for a brief moment in the address bar 19 before it is replaced with the generic URL. Thus, it will be difficult for the user to obtain any knowledge of even a part of URL1. This helps to conceal URL1 from the user.

In Step 313, the server 13 opens a session. During this session, any location specific messages sent from a different client device in relation to marker 1 will be ignored. Ignoring these messages may involve not displaying such messages at the administrator device 15 or displaying the messages accompanied by an ignore flag. Alternatively, the server 13 could prevent the webpage 25 from which the location-specific messages can be sent from being sent to another client device during the session.

The session rriay be closed using the smartphone 11, the server 13, the administrator device or a third party device. Alternatively, the session could be closed after a predetermined period of time. When the session is closed any client device may initiate the method described with reference to Figure 2.

In the situation where the OR code 5 or the written URL 7 is used to obtain the URL the system is less secure because the user is able to take a photograph of the OR code 5 or keep a record of the written URL 7. The photograph or record of the URL could then be used to send location specific-messages from locations other than that of the marker 1. Thus) when the OR code 5 or written URL 7 is used is used an extra security feature may be required.

Referring to Figure 1, an access code 9 is provided at the marker 1. It may also be appropriate to provide the access code when the NFC tag 3 is used. At least a part of the surface of the marker 1 is a material on which non-permanent markings can be drawn and erased. Thus, it is easy to change the access code 9 at the marker 1.

The webpage can be delivered to the smartphone 11 including a field into which the access code 9 may be entered. Thus, the user can enter the access code 9 displayed at the marker 1

into the access code field.

The access code entered by the user can then be validated at the server 13. If the access code is valid the webpage 25 and the location information are delivered to the smartphone ilso that the user can now send a location specific message.

Alternatively, the webpage 25 and the location information are delivered to the smartphone 11 but the webpage 25 includes the access code field. Thus, when the user sends the selected message options 26 the access code is validated on sending of the message. If the access code is not correct, the location-specific message will not be shown at the administrator device 15. Alternatively, the location specific message will be shown but a flag indicating that an invalid access code has been entered will accompany the message.

The method for determining the position from which a message has been sent has a variety of applications. For example, the method could be used in a voting system where the booth from which a vote was placed can be determined from the vote message. In addition, the method could be used to request a component at a specific assembly point in a factory, order an item to a specific seat within an establishment, order a taxi to a collect a person at a specific geographical location, receive directions from one location to another or alert a building's administrator to a hazard, such as a lire, at its exact location.

Claims

CLAIMS1. A method of determining the position from which a message has been sent, the method comprising the steps of: inputting a URL and a position code, at a client device, wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; transmitting the position code and a request for a webpage corresponding with the U R L; acquiring position data indicative of the first marker location, based on the position code; associating the position data with the client device; receiving, at the client device, a webpage in response to the webpage request; using the webpage, at the client device, to send a message; and determining a position based on the message and the association of the position data with the client device.
2. A method according to claim 1 wherein the step of associating the position data with the client device comprises: storing the position data at the client device; and the method further comprises the steps of: transmitting the position data from the client device; and determining a position based on the position data.
3. A method according to claim 1 or 2 wherein the request for the webpage is associated with an identification code indicative of the client device and the step of associating the position data with the client device comprises: associating the identification code with the position data; and the method further comprises the steps of: transmitting the identification code from the client device; and determining a position based on the identification code.
4. A method according to any of the preceding claims wherein the URL comprises the position code.
5. A method according to any of the preceding claims wherein the first markercomprises a near field communication tag.
6. A method according to any of the preceding claims wherein the first marker comprises a quick response code.
7. A method according to any of the preceding claims wherein the position code comprises a query string indicative of first marker location.
8. A method according to claim 7 wherein once the webpage corresponding with the URL has been received the query string is not displayed in the client device web-browser.
9. A method according to claims 7 and 8 wherein the length of the URL is such that at least a part of the query string is not visible in the address bar of the web-browser application.
10. A method according to any of the preceding claims comprising the further steps of: inputting an access code into the web-browser; and if the access code is not correct, preventing the message from being sent from the webpage corresponding with the URL.
11. A method according to any of the preceding claims wherein the access code is displayed in the vicinity of or on the first marker.
12. A method according to claim 10 or 11 wherein the URL obtained from the marker comprises the access code.
13. A method according to any of the preceding claims comprising the further step of: opening a session associated with the initial request for the webpage corresponding with the URL, wherein, during the session, messages sent from devices other than the client device from which with the initial request for the webpage was sent are ignored.
14. A method according to any of the preceding claims comprising the further step of: using a camera to visually inspect the environment around the position of the first marker; and allowing a message sent from the client device to be ignored if a person was not located in the environment around the position of the first marker when the message was sent.
15. A method according to any of the preceding claims comprising the further step of: on receipt of the request for the webpage corresponding with the URL, using the camera to visually inspect the location at which the first marker is positioned.
16. A computer program product comprising instructions for carrying out the method of any of the preceding claims.
17. A system for determining the position from which a message has been sent, the system comprising one or more processors configured as: an input module, at a client device) arranged to input a URL and a position code) wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; a transmission module arranged to transmit the position code and a request for a webpage corresponding with the URL; an acquisition module arranged to acquire position data indicative of the first marker location, based on the position code; an association module arranged to associate the position data with the client device; a receiving module, at the client device, arranged to receive a webpage in response to the webpage request; a web module, at the client device, arranged send a message using the webpage; and a determining module arranged to determine a position based on the message and the association of the position data with the client device.
18. A method of determining the position from which a message has been sent, the method comprising the steps of: inputting a URL and a position code, at a client device, wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; transmitting the position code and a request for a webpage corresponding with the URL from the client device; receiving, at the client device, a webpage in response to the webpage request; using the webpage, at the client device) to send a message.
19. A computer program product comprising instructions for carrying out the method of claim 18.
20. A method of determining the position from which a message has been sent, the method comprising the steps of: receiving, at a server, a position code and a request for a webpage corresponding with a URL, wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; acquiring, at a server, position data indicative of the first marker location, based on the position code; associating the position data with the client device, using a server; transmitting the webpage corresponding with the U RL from a server; receiving, at a server, a message sent using the webpage; and determining, at a server, a position based on the message and the association of the position data with the client device.
21. A computer program product comprising instructions for carrying out the method of any of the claim 20.
22. A system for determining the position from which a message has been sent, the system comprising a client device comprising one or more processors configured as: an input module arranged to input a URL and a position code wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; a transmission module arranged to transmit the position code and a request for a webpage corresponding with the URL; a receiving module arranged to receive a webpage in response to the webpage request; a web module arranged to send a message using the webpage.
23. A system for determining the position from which a message has been sent, the system comprising one or more servers comprising one or more processors configured as: a receiving module arranged to receive a position code and a request for a webpage corresponding with a URL, wherein the URL and the position code are obtained from a first marker positioned at a location and the position code is indicative of the first marker location; an acquisition module arranged to acquire position data indicative of the first marker location, based on the position code; an association module arranged to associate the position data with the client device; a transmission module arranged to transmit the webpage corresponding with the URL; a receiving module arranged to receive a message sent using the webpage; and a determining module arranged to determine a position based on the message and the association of the position data with the client device.
24. A marker, positioned at a location, encoded with a URL and a position code, wherein the position code is indicative of the marker location and the URL is indicative of a webpage from which a message can be sent.
25. A system substantially as herein described with reference to and/or illustrated in the accompanying drawings.
26. A method substantially as herein described with reference to the accompanying drawings.