WO2008142373A1

WO2008142373A1 - A method and device for position data transfer

Info

Publication number: WO2008142373A1
Application number: PCT/GB2008/001672
Authority: WO
Inventors: Francesco Lodolo
Original assignee: Symbian Software Limited
Priority date: 2007-05-22
Filing date: 2008-05-14
Publication date: 2008-11-27
Also published as: CN101690272A; EP2165562A1; GB0709804D0; GB2449452A

Abstract

An embodiment of the present invention provides a method which enables the user of a mobile computing device to provide a third party with their current position. The user determines the current estimated position of the mobile computing device using any available mechanism known to those skilled in the art. The mobile computing device then creates a position data file which includes information including, the identity of the device, the estimated position of the device, the time of the estimation, the accuracy of the estimation, etc. The mobile computing device then gives the user the option to transmit the position data file to a third party. The third party may be another user's computing device, which may be a mobile device. The position data file may be sent by SMS (Short Message Service), MMS (Multimedia Message Service), email or instant message.

Description

A Method and Device for Position Data Transfer

The present invention relates to a method for the transfer of position data from a mobile computing device to another computing device. In particular, the present invention relates to a method which enables a user of a mobile computing device to provide a third party with the current position of the mobile computing device.

Background to the Invention

In the prior art, various systems exist to enable the position of a mobile computing device, such as a mobile telephone, to be determined. One positioning system provided by mobile telephone networks is cell based location. With cell based location, the network estimates the position of a mobile telephone by determining which base station the telephone is communicating with. The network is pre-programmed with information concerning the location of each base station in the network and estimates that the position of the telephone is the same as the base station, hi a city where base stations are closely packed, this estimate may be accurate to within 100 or 200 metres. The accuracy can be improved by determining how close a given mobile telephone is to a base station. This can be estimated using the strength of the signal received by the base station which is typically measured to provide power control. Generally speaking, the further a mobile device is from a base station, the weaker the signal received by the base station will be.

Other mechanisms for determining the location of a mobile computing device include GPS (Global Positioning System) and radio location. Increasing numbers of mobile computing devices now have integral GPS units which enable position to be estimated to within 10 to 30 metres accuracy. Some mobile telephone networks now use radio location. Radio location typically uses signals arriving from two base stations at a mobile device in order to determine the location of the device using triangulation techniques. The time difference between signals arriving at the base stations and the angle of arrival of those signals can be used to determine the position of the device. These techniques can provide a more accurate location than cell based location services, however they are not available in some mobile networks.

On such technique is Observed Time Difference of Arrival (OTDOA) which uses pilot signals transmitted from multiple base stations. A position calculation function determines the time difference between pilot signals received from a first base station and a second base station. This information enables the determination of a hyperbola along which the mobile device must be located. By introducing measurements from a third base station three possible lines of location can be calculated, and the point of intersection of these lines is the estimated position of the mobile device.

Most mobile telephone network operators now offer Location-Based Services (LBS) which provide mobile telephone users with a variety of information based on their current location. For example, the operator may provide downloadable maps or information such as the location of the nearest cash point or petrol station.

It is also known to provide a service in which a user can obtain information concerning the position of a third party's mobile device. Such services are typically web-based and operate by providing a user with access to the cell-based location information for a given third party mobile telephone. In order to use these services, a user must firstly register with a website offering third party location information. The user then registers the telephone numbers of any mobile telephones which they are interested in knowing the location of. The owners of the registered mobile telephones must then give their permission for their location to be determined by the web-based service. This is typically done by sending a text message to the third party mobile telephone asking them to confirm that they are happy for the location of their device to be determined. Once the third party gives their permission, the web-based service is provided with the cell-based location information by the mobile operator and this information is passed on to the user. Such services are typically aimed at parents who wish to know the location of their children and employers who wish to know the location of their employees.

One problem with existing services is that they do not enable the user of a mobile computing device to inform a third party of their current location. Instead, it is up to the third party to decide when they want to know the location of the user's mobile computing device. Furthermore, the above noted prior art services use servers which are generally run by a company which requires payment for it's services. Therefore, a user must pay in order to keep track of other mobile devices. Summary of the Invention

In particular, an embodiment of the present invention provides a mobile device comprising: memory arranged to store position data records, a transceiver arranged to enable two-way communications between the mobile device and a communications network, and a processor operable to cause said transceiver to transmit at least one of said position data records to a first computing device, via said communications network, in response to an instruction from a user.

The mobile device of the present invention thus enables a user to easily transmit position data to a third party. This means that a user does not have to wait for friends or colleagues to request position information, as is the case in prior art systems. Instead, the mobile device of the present invention enables a user to easily send position information without having to rely on a third party server or a request from another user. Furthermore, because the position data is sent directly to another device in a peer-to-peer format, users can avoid paying charges which are made by server based solutions.

Preferably, the processor is operable to request mobile device position data from a second computing device in response to an instruction from a user. The second computing device is a location server which determines mobile device position data using cell-based location. The transceiver is operable to receive mobile device position data from the second computing device and the processor is operable to create position data records in response to the reception of mobile position data from the second computing device. Preferably, the mobile device further comprises a keypad, and the processor is further operable to enable the user to create position data records using the keypad. The processor is also operable to enable a user to edit existing position data records.

The position data records each preferably comprise a plurality of fields, each field arranged to accept a predetermined type of position related data. The types of position related data include at least one of, coordinates, position accuracy, location identity, date, time and street address.

The position data records are preferably sent to the first computing device via one of SMS, MMS, email and instant messaging. The first computing device is preferably a mobile telephone and the mobile device is preferably a mobile telephone or smartphone.

Preferably, the transceiver is operable to receive position data records from other mobile devices and the processor is operable to display a position data record upon receipt. The processor may be further arranged to obtain or generate a map of the position defined in the position data record.

A further embodiment of the present invention provides a method of transferring position data records from a mobile device to a first computing device, the method comprising: storing position data as a position data record on the mobile device; and sending the position data record to said first computing device in response to an instruction from a user of the mobile device.

Brief Description of the Drawings

The present invention will now be described by way of example only and by reference to the accompanying drawings in which:

Figure 1 shows a mobile device in accordance with an embodiment of the invention;

Figure 2 is a schematic diagram showing the components of the mobile device of Figure 1; Figure 3 is a representation of the memory of the mobile device shown in Figure 1;

Figure 4 is a diagram of an environment in which the mobile device of Figure 1 operates;

Figure 5 is a flow-chart showing a method of establishing and transmitting position data in accordance with an embodiment of the invention;

Figure 6 is a flow-chart showing a method of transmitting existing position data in accordance with an embodiment of the invention;

Figure 7 is a flow-chart showing a method of creating a position data record in accordance with an embodiment of the present invention;

Figure 8 is a flow-chart showing a method of receiving and displaying a position data record in accordance with an embodiment of the invention;

Figure 9 is an alternative diagram of an environment in which the mobile device of Figure 1 operates; and

Figure 10 is a sequence diagram showing certain operational sequences in accordance with an embodiment of the present invention.

Description of the Embodiments

Referring to Figure 1, a mobile device 100 comprises an outer casing 101, an earphone 102 and a microphone 103. The mobile device 100 also includes a keypad 104 and a display 105. The keypad 104 enables a user to enter information into the mobile device 100 and instruct the mobile device to perform the various functions which it provides. For example, a user may enter a telephone number, or select another mobile device from a list stored on the mobile computing device 100, as well as perform functions such as initiating a telephone call. Figure 2 is a schematic diagram showing the components of the mobile device 100. The device includes a system bus 106 to which the components are connected and which allows the components to communicate with each other. Here, the components are shown to communicate via a single system bus 106. However, in practice the mobile device may include several buses to connect the various components. The components of the mobile device 100 include a processing unit 107, memory 108, and earphone controller 109, a microphone controller 110, a display controller 111, a keyboard controller 112, a storage and a transceiver 113. Figure 2 shows a single processor unit 107, however in practice the device may include two or more processor units to control different components of the device. In particular, the device 100 may include a baseband processor unit to control a telephony stack, and an application processor to control an operating system and a user interface of the device. The transceiver 113 is also connected to an antenna 114. The mobile device 100 is arranged to communicate, using transceiver 113 with a base station of a mobile phone network (not shown).

Memory 108 comprises various memory types, as shown in Figure 3. hi particular, memory 108 includes a read only memory 108a, a random access memory 108b and a user data memory 108c. The read only memory 108a stores the operating system, the graphical user interface, as well as any essential applications which are provided with the device, such as messaging applications and voice call interface applications. Applications are loaded into the random access memory 108b when required during the normal operation of the mobile device 100. The user data memory 108c is used to store user data and applications which have been loaded onto the mobile device 100 by the mobile operator or the user. For example, the user data memory 108c may store contact data, calendar data, user messages such as email, SMS or MMS messages and images. The user data memory 108c is used to store a positioning application and associated positioning data records, both of which will be described in more detail below.

Each of the memory described above may be located physically separately within the mobile device 100. For example, the read only memory 108a may be located within the processor unit 107 and the random access memory 108b may take the form of a separate integrated circuit mounted on a printed circuit board of the mobile device 100. The user data memory 108c may take the form of an internal hard drive or removable storage device such as a flash memory card. Referring to Figure 4, the mobile device 100 is shown in relation to an environment 200 which includes mobile phone base stations 201a, 201b which form part of a mobile phone network 202. The mobile device 100 is arranged to communicate with the mobile phone network 202 when a user makes a telephone call or otherwise requires a data connection with the mobile phone network in order to establish an Internet connection. Also shown are third party mobile devices 203 a, 203b, which are arranged to communicate with the mobile phone network in the same manner as the mobile device 100. In particular, mobile device 100 may communicate with third party mobile device 203a, 203b by establishing a voice call via mobile phone network 202 or by sending an SMS or MMS message via mobile phone network 202. The methods and procedures for establishing communications between devices of this sort are well known to the skilled person and are not repeated here. The third party mobile devices 203a, 203b both comprise the features of mobile device 100 as shown and described in Figures 1 and 2.

The mobile phone network 202 is also connected to the Internet 204, and allows mobile devices connected to the mobile phone network 202 to establish data connections with other servers, for example mail servers, via the Internet 204. The mobile phone network 202 is also connected to a conventional fixed landline based telephone network 205 allowing mobile device 100 to establish telephone calls with landline telephones and mobile devices connected to other mobile telephone networks.

A Location-Based Service (LBS) server 206 is also shown in Figure 4. The LBS server 206 provides location-based services to users of mobile devices which are connected to the mobile phone network 202. The function of the LBS server 206 is to estimate the position of mobile devices connected to the mobile phone network 202. The LBS server 206 uses cell- based location to estimate the position of mobile devices. The LBS server 206 maintains a base station location database (not shown) which contains a record of the location of base stations 201a and 201b, as well as all other base station in the mobile phone network 202. The basic location information is in the form of standard coordinates of longitude and latitude. In addition to this, the base station location database stores location details in the form of a street address The LBS server 206 may be accessed directly by applications running on the mobile device 100 as well as by web-based applications which may be accessed by the mobile device 100 via the Internet 204. The mobile phone network 202 is aware of which base station a mobile device is connected to, or would connect to if a connection was required. This information is accessible by applications running on the mobile device or on computer servers offering location-based services via the Internet, and is sent to the LBS server 206 with any position estimate request. The LBS server 206 can then perform a look-up function within the base station location database, and will estimate the position of the mobile device to be the same as the location of the nearest base station. If the base station serves a cell which has a 100m radius, then the accuracy of the position estimate is ±lOOm. This information is then passed back to the mobile device or computer server. The position data includes the estimated coordinates of the mobile device, the estimated street address, as well as the accuracy of the location estimate.

The mobile device 100 includes applications which are stored in random access memory 108a and user data memory 108c and which are arranged to perform certain functions . In use, the applications are loaded into random access memory 108b and the instructions defined in the applications are executed by the processor unit 107. Any reference in the following to the processor unit 107 performing a certain function is a reference to the processor unit executing instructions contained within one or more applications. In particular, user data memory 108c comprises a positioning application (shown in Figure 3) which provides the user of the mobile device 100 with various position data related functions. The positioning application includes a graphical user interface (GUI) to enable the user of mobile device 100 to execute the various functions provided by the positioning application. In the following, when the positioning application is described as providing the user of the mobile device with information or options, it will understood that this is done via display 105, and that any instructions provided by the user are entered via keypad 104. The operation of the mobile device 100 will now be described.

As noted above, the positioning application provides the user of mobile device 100 with various functions. One function is to send details of the current position of the mobile device 100 to a third party computing device, for example third party mobile device 203a. This function is shown in Figure 5. When a user wants to send position data to a third party, the user opens the positioning application (step 301). The user is then presented with a number of menu options. One of the options is "Push Position Data", which the user then selects (step 302). The positioning application then gives the user further options, one of which is "Push Current Position". The user then selects "Push Current Position" (step 303). Once the user has selected "Push Current Position" the positioning application first determines the current position of the mobile device 100. The positioning application establishes a data connection, via the transceiver 113, with LBS server 206 and requests current position data (step 304). The LBS server 206 then estimates the position of the mobile device 100, as described above, and sends this information to the positioning application via the established data connection (step 305). As noted above, the position information includes the estimated coordinates of the mobile device, the estimated street address, together with the accuracy of the position information. Once step 305 has been completed, the positioning application generates a position data record (step 306).

A position data record (shown in Figure 3) is a record of position information relating to a mobile device, or other computing device. A position data record can also be used to record position information relating to a fixed significant location, such as a cash point, or tourist destination. The position data record comprises fields for the identity of the device to which the record relates, the estimated position of the device, the accuracy of the estimated position, the street address of the position, the date and time the position was estimated and the accuracy of the estimation. The following is an example of a typical record:

Location identity: Generic device S56 - J. Smith

Position data: +51.475, -0.221

Data accuracy: ±lOOm

Street address: Stevenage Road, Fulham, London

Date stamp : 5^th April 2007

Time stamp: 1:48pm

The position data records are stored in the user data memory 108c. The position data record may be expressed in text format to enable the data to be easily sent using a number of different mediums, for example via SMS text messages. The text version of the above record would read:

starfcposdata identGeneric device S56 - J. Smith pos:+51,475;-0.221 acc:±100 address :stevenage road; fulham; london date:05042007 time: 1348 end:posdata

The positioning application converts the position information received from the LBS server 206 into the above described position data record format. Once the record is completed, the positioning application provides the user with various options for sending the position data record (step 307). These options include: text message, multimedia message, instant message, email and server. Each of these options are described in the following.

If the user selects "text message" or "multimedia message", the positioning application asks the user to enter the details of the third party mobile device 203 a, 203b to which the position data record should be sent. This information can be entered in the form of a telephone number or in the form of a contact selected from an address book or the like (step 308). The messaging interface application then sends the position data record to the third party mobile device 203a, 203b using procedures well known to those skilled in the art (step 309).

If the user selects "instant messaging", the positioning application opens an instant messaging interface application which is stored in memory 108. The instant messaging interface application provides the user with a list of available contacts which have been pre-established by the user of mobile device 100. The contacts may include mobile and fixed computing devices and the list shows any devices which are currently able to receive instant messages. The user then selects the third party mobile device 203a, 203b, to which they want to send the position data record (step 308). The positioning application then sends the position data record to the third party mobile device via the instant messaging interface application (step 309).

If the user selects "email", the positioning application opens the messaging interface application. The positioning application asks the user to enter the email address of the intended recipient of the position data record (step 308). The messaging interface application then sends the position data record to the email address which has been entered by the user as an attachment to an email (step 309). In the above described process, at step 303, the user selects "Push Current Position". The positioning application also provides the user with the option to push a position data record which has already been created by the user. The process of pushing existing position data records will now be described with reference to Figure 6.

As above, when a user wants to send position data to a third party, the user opens the positioning application (step 401) and the user is presented with a number of menu options. One of the options is "Push Position Data", which the user then selects (step 402). The positioning application then gives the user further options, one of which is "Push Existing Position Data Record" which the user may then select (step 403).

Once the user has selected "Push Existing Data Record", the positioning application opens a file browser interface application which is stored in random access memory 108a (step 404). The browser initially opens a folder stored in user data memory 108c which is the default location for all position data records stored on the mobile device 100. The browser allows the user to see basic information stored in each position data record such as the identity of the device or location to which the record relates, as well as the time and/or date when the record was created. The user can then select the record they wish to send (step 405).

The selected position data record is then sent to a third party in the same manner as described above in connection with Figure 5. The user selects the required transmission format (step 406), enters the destination details (step 407) and the position data record is sent to the third party device (step 408).

When the user opens the positioning application, the first option available to select is "Push Position Data". This has been described above in relation to Figures 5 and 6. The second option provided by the positioning application is "Create Position Data Record". The process of creating new data records will now be described in connection with Figure 7.

The process of creating a new position data record is begun when the user opens the positioning application (step 501). The user is given the option to either "Push Position Data" or "Create Position Data Record". In this case, the user selects "Create Position Data Record" (step 502). All of the fields of a position data record can be entered manually, however when a user creates a record using the positioning application, the user is given various choices for automatic entry of data into the fields of the record. The positioning application is able to automatically provide data for most of the fields of a record, as it does when sending current position data records to third party devices.

Once the user has selected "Create Position Data Record", the positioning application asks the user whether they want to create a record based on the current position of the mobile device 100 (step 503). If the user selects "Yes", the positioning application contacts the LBS server 206, and requests current position data in the same manner as described above in connection with Figure 5. The positioning application sends a request to the LBS server 206 (step 504), which estimates the position of the mobile device 100 before sending the position information back to the mobile device 100 (step 505). The positioning application then populates the fields of the newly created position data record (step 506). The positioning application then prompts the user to enter an identity for the position data record, which the user then enters via the keypad 104 (step 507). The identity may be the name of the user, or the name of the users current location, for example the name of a tourist attraction. At this point the user may manual change any of the data in the position data record before saving the contents to the user data memory 108c (step 508).

At step 503, if the user does not want to create the new position data record on the basis of the current position of the mobile device 100, the user can select "No", in which case the positioning application opens a blank position data record, and allows the user to manually enter data into each field of the position data record (step 509). The user then saves the position data record to the user data memory 108c (step 508).

The procedure by which a third party mobile device 203 a, 203 b receives and handles a position data record will now be described with reference to Figure 8. When a message containing a position data record is received by the third party mobile device 203 a (step 601), the messaging interface application recognises that the text is in position data record format and generates a position data record on the basis of the information provided in the message (step 602). The messaging interface application informs the user that a position data record has been received, and gives the user the choice to either "View" or "Exit" (step 603). If the user selects "Exit" the process ends (step 604). The user may view the position data record at a later time by retrieving the message from the messaging interface application's inbox location. If the third party selects "View", the position data record is displayed on the third party mobile device 203 a (step 605) enabling the user to see the location of the mobile device 100 at the time recorded in the position data record.

A preferred embodiment of the present invention will now be described in connection with Figure 9. Users 700a, 700b and 700c are each able to move around within a given geographical area represented by Figure 9. Each user 700a, 700b, 700c possesses a corresponding mobile telephone 701a, 701b and 701c. Each of these telephones is arranged to communicate with a mobile telephone network in the manner familiar to those skilled in the art. Furthermore, each mobile telephone 701a, 701b, 701c is arranged to operate in the same manner as mobile device 100 as described above in connection with Figures 1 to 8.

Also shown in Figure 9 is position provider 702, which may be a GPS. Mobile telephones 701a, 701b each comprise a GPS unit (not shown) enabling them to determine their position using signals 703 a, 703b produced by GPS satellites. This mechanism for determining position is provided as an alternative to the cell-based location provided by LBS server 206. In this embodiment, at step 305 in Figure 5, rather than requesting position data from the LBS server 206, the mobile telephones 701a, 701b request position data from their respective GPS units 701. Mobile telephones 701a, 701b are able to provide each other, and mobile telephone 701c, with position information by pushing 704ab, 704ac, 704bc position data records, as shown in Figure 9.

The operation of the embodiment shown in Figure 9 will now be described in connection with Figure 10. Figure 10 shows sequence diagram interactions 801 between users 700a, 700b and 700c and mobile telephones 701a, 701b, 701c. The sequence diagram 801 includes representations of the users 700a, 700b, 700c, the position provider 702 and a timer 802. The timer 802 operates on mobile telephones 701a and 701b and will be described in more detail below. The sequence diagram also includes representations of the mobile telephones 701a, 701b and 701c. The first element of the sequence diagram is the position tracking control sequence 803. The mobile device 701b has loaded thereon the above-described positioning application. In addition to the above described functionality, the positioning application is arranged to automatically send position data at regular intervals. Thus, if user 700b intends to meet a group of users, each user in that group can be kept informed of the location of user 700b. In order to achieve this, the positioning application is provided with an option to turn automatic position data sending on or off. The positioning application is also arranged such that user 700b can set the regularity with which position data is sent. This may be, for example, every minute, 5 minutes or every hour. The positioning application also enables a group of users, to whom position data records should automatically be sent, to be specified This functionality is represented by position tracking control sequence 803. The user 700b may either turn the position tracking service on or off (step 804), enable or disable tracking visibility for users 700a and 700c (step 805) and set tracking frequency (step 806).

The next element in the sequence diagram 801 is the position acquisition sequence 807. Here, the position provider (in this case a GPS) sends out position information to each mobile telephone 701a, 701b and 701c (step 808). Although the GPS sends positioning signals in all directions, only mobile telephones 701a and 701b are able to interpret these signals using their internal GPS units.

The final element in the sequence diagram 801 is the position information pushing sequence 809. The sequence begins when the timer 802 issues a "tick" 810 indicating that the positioning application should push a current position data record. The positioning application, loaded on mobile telephone 701b, then pushes a current position data record to all users included in the group, i.e. users 700a and 700c (step 811). This is achieved in accordance with the methods described above. Mobile telephones 701a and 701c then receive the current position data record. Preferably, mobile telephones 701a and 701c also have loaded thereon the positioning application. The positioning application is further arranged to compare the position of the mobile telephone 701b, with the position of the telephone on which it is loaded and to calculate an estimated time of arrival for user 701b (step 812). This may be achieved by calculating the distance between respective mobile telephones and determining how long a journey of that distance would take. Alternatively, the mobile telephone may be loaded with, or have access to, a navigation system which can accurately estimate journey times based on actual road length and live traffic updates. The user 700b may also send details of their intended route with the position data record. This can be used to improve the journey time estimate. If the user intends on using public transport, the journey time estimate can taken into account live public transport information which may be available via the Internet. Other mechanisms for estimating the time of a particular journey will be known to a person skilled in the art. Finally, the mobile telephones 701a and 701c make the users 700a and 700c aware of the position of user 700b and also the estimated time of arrival (step 813).

The mobile network operator also provides web-based mapping functions which enable a user to view the location defined in a position data record on a map. Once the received position data record has been opened by the user of the mobile device 203 a, the messaging interface application displays an "Options" menu icon which the third party can open using the menu navigation system of the third party mobile device 203 a. The "Options" menu includes a "Retrieve Map" option. Referring again to Figure 8, if the user of the mobile device 203a selects "Retrieve Map" (step 606), the mobile device 203 a connects to a mapping server (not shown) via the mobile phone network 202 (step 607). The third party mobile device 203a uploads the received position data record to the mapping server (step 608) and the mapping server generates a map of the location defined in the position data record which is then sent back to the third party mobile device 203 a (step 609). The third party mobile device 203 a then displays the map on a display of the third party mobile device 203a (step 610).

As an alternative to the above described web-based mapping function, the third party mobile device 203a may have a mapping application pre-loaded in it's user data memory. The mapping application includes pre-loaded maps of a given area (for example the United Kingdom). When a user selects "Retrieve Map" in the "Options" menu, the mapping application is loaded, which then generates and displays a map of the location specified in the position data record.

While the above embodiments describe a system which includes mobile phones operating in a mobile phone network, other embodiments include a system which utilises other types of mobile devices, for example laptop computers, and other methods of data transfer, for example wireless local area networks. The term mobile device may refer to a mobile telephone, a smartphone, a laptop, a Personal Digital Assistant (PDA) or any other mobile computing device. In particular, mobile device may refer to a vehicle based computing device which is fixed to, or integral with the vehicle and which is mobile in the sense that the vehicle itself is mobile. Such a device allows the tracking of the position of a vehicle such as a delivery van or the like. In addition, further modifications, additions, and variations to the above described embodiments will be apparent to the intended reader being a person skilled in the art, to provide further embodiments which incorporate the inventive concept of the present invention, and which will fall within the scope of the appended claims.

Claims

1. A mobile device comprising: memory arranged to store position data records, a transceiver arranged to enable two-way communications between the mobile device and a first computing device, and a processor operable to cause said transceiver to transmit at least one of said position data records to said first computing device in response to an instruction from a user.

2. A mobile device according to claim 1, wherein said at least one of said position data records is a mobile device position data record relating to the position of the mobile device.

3. A mobile device according to claim 2, wherein said transceiver is operable to receive mobile device position data from a second computing device, said mobile position data relating to the position of the mobile device.

4. A mobile device according to claim 3, wherein said processor if further operable to create said mobile device position data record in response to the reception of mobile position data from said second computing device

5. A mobile device according to claim 4, wherein said processor is further operable to request mobile device position data from said second computing device in response to an instruction from a user.

6. A mobile device according to any preceding claim 1, wherein said mobile device further comprises a keypad, and said processor is further operable to enable said user to create position data records using said keypad.

7. A mobile device according to any preceding claim, wherein said processor is further operable to enable a user to edit existing position data records.

8. A mobile device according to any preceding claim, wherein said position data records each comprise a plurality of fields, each field arranged to accept a predetermined type of position related data.

9. A mobile device according to claim 8, wherein said types of position related data include at least one of, coordinates, position accuracy, location identity, date, time and street address.

10. A mobile device according to any preceding claim, wherein said first computing device is a mobile telephone.

11. A mobile device according to any preceding claim, wherein said second computing device is a location server.

12. A mobile device according to claim 11, wherein said location server determines mobile device position data using cell-based location.

13. A mobile device according to any preceding claim, wherein said at least one of said position data records is sent to said first computing device via one of SMS, MMS, email and instant messaging.

14. A mobile device according to any preceding claim, wherein said transceiver is operable to receive position data records from another mobile device.

15. A mobile device according to claim 14, wherein said processor is operable to display a position data record upon receipt.

16. A mobile device according to claim 15, wherein said processor is further arranged to obtain or generate a map of the position defined in said position data record.

17. A mobile device according to claims 14, 15 or 16, wherein said processor is further arranged to calculate the estimated time of arrival of the sender of the position data record.

18. A mobile device according to any preceding claim, wherein the mobile device is a mobile telephone.

19. A mobile device according to claim 18, wherein the mobile telephone is a smartphone

20. A mobile device according to any preceding claim, wherein the transceiver is arranged to enable two-way communications between the mobile device and the first computing device via a communications network.

21. A mobile device according to any of claims 1 to 19, wherein the transceiver is arranged to enable two-way communications between the mobile device and the first computing device directly.

22. A mobile device according to any of claims 1 to 21, wherein the processor is further operable to cause said transceiver to transmit at least one of said position data records automatically at predetermined intervals.

23. A mobile device according to any of claims 1 to 22, wherein the processor is further operable to cause said transceiver to transmit at least one of said position data records to a predefined plurality of computing devices.

24. A method of transferring position data records from a mobile device to a first computing device, the method comprising: storing position data as a position data record on the mobile device; and sending the position data record to said first computing device in response to an instruction from a user of the mobile device.

25. A method according to claim 24, wherein said position data is mobile device position data, relating to the position of the mobile device, and said position data record is a mobile device position data record relating to the position of the mobile device.

26. A method according to claim 25, further comprising the step of determining the position of the mobile device and storing it as said mobile device position data.

27. A method according to claim 26, wherein said mobile device position data is determined by a second computing device.

28. A method according to claim 27, wherein said second computing device determines said mobile device position data in response to a request from a user of said mobile device.

29. A method according to claim 24, wherein said step of storing position data is carried out manually by a user of said mobile device.

30. A method according to any of claims 24 to 29, wherein said position data records each comprise a plurality of fields, each field arranged to accept a predetermined type of position related data.

31. A method according to claim 30, wherein said types of position related data include at least one of, coordinates, position accuracy, location identity, date, time and street address.

32. A method according to any of claims 24 to 31, wherein said first computing device is a mobile telephone.

33. A method according to any of claims 24 to 32, wherein said second computing device is a location server.

34. A method according to claim 33, wherein said location server determines mobile device position data using cell-based location.

35. A method according to any of claims 24 to 34, wherein said position data record is sent to said first computing device via one of SMS, MMS, email and instant messaging.

36. A method according to any of claims 24 to 35, further comprising the step of receiving position data records from another mobile device.

37. A method according to claim 36, further comprising the step of displaying a position data record upon receipt.

38. A method according to claim 37, further comprising the step of obtaining or generating a map of the position defined in said position data record.

39. A method according to any of claims 36 to 38, further comprising the step of estimating the estimated time of arrival of the sender of the position data record.

40. A method according to any of claims 24 to 39, wherein said step of sending the position data record to said first computing device is performed via a communications network.

41. A method according to any of claims 24 to 39, wherein said step of sending the position data record to said first computing device is performed directly between the mobile device and the first computing device.

42. A method according to any of claims 24 to 41, wherein said step of sending the position data record is performed automatically at predetermined intervals.

43. A method according to any of claims 24 to 42, further comprising the step of sending the position data record to a predefined plurality of computing devices.

44. A computer program or suite of computer programs arranged such that when executed by a processor it/they cause the processor to operate in accordance with any of claims 24 to 43.

45. A machine readable storage medium storing the computer program or at least one of the suite of computer programs according to claim 44.

46. An operating system for causing a computing device to operate in accordance with a method as claimed in claims 24 to 43

47. A computing device substantially as hereinbefore described with reference to Figures I to 8.

48. A method substantially as hereinbefore described with reference to Figures 1 to 8.