Providing and using messages comprising location information

[0001] The invention relates to the provision and use of messages containing location information that have been determined based on satellite signals.

BACKGROUND OF THE INVENTION [0002] Device positioning is handled by various global satellite navigation systems (GNSS, Global Navigation Satellite Systems). These include, for example, the US Global Positioning System (GPS), the Russian Global Navigation Satellite System (GLONASS), the future European Galileo system, Spatial Assistance Systems (SBAS), Space Based Augmentation Systems), Japanese Quasi-Zenith satellite assist system (QZSS), local assist systems (LAAS) and hybrid systems.

[0003] For example, a constellation in GPS contains more than 20 satellites that orbit around the Earth. Currently, each of the satellites broadcasts two L1 and L2 carrier signals. One of these L1 carrier signals is used to carry navigational messages and code signals of a standard positioning service (SPS). L1 carrier phase is modulated by each satellite using a different C / A code (Coarse Acquisition). In this way, different channels for different satellites are obtained for transmission. The C / A code is a pseudo random noise (PRN) code that is propagated in the 1 MHz band. Repeats every 1023 bits, the epoch period is 1 ms. The carrier frequency of the L1 signal is further modulated by the beacon information at 50 bits / s. The navigation information includes inter alia ephemeris and almanac parameters. The ephemeris parameters describe short segments of the orbit of a given satellite. Based on the parameters of the ephemeris, the algorithm can estimate the position of the satellite at all times when the satellite is in the appropriate section described. The almanac parameters are similar but coarse orbital parameters that are valid for a longer period of time than the ephemeris parameters. In addition, the navigation information includes, for example, clock models that relate to satellite time relative to system time and system time to coordinated universal time (UTC). when the satellite is in the appropriate section described. The almanac parameters are similar but coarse orbital parameters that are valid for a longer period of time than the ephemeris parameters. In addition, the navigation information includes, for example, clock models that relate to satellite time relative to system time and system time to coordinated universal time (UTC). when the satellite is in the appropriate section described. The almanac parameters are similar but coarse orbital parameters that are valid for a longer period of time than the ephemeris parameters. In addition, the navigation information includes, for example, clock models that relate to satellite time relative to system time and system time to coordinated universal time (UTC).

[0004] The GPS receiver whose position is to be determined receives the signals transmitted by currently available satellites and also detects and tracks the signals used by different satellites based on different C / A codes. The receiver then determines the transmission time of the code transmitted by each satellite, usually based on data in the decoded navigation messages, epoch counters, and C / A code integrated circuits. The transmission time and the measured arrival time of the signal to the receiver enable to determine the pseudorange between the satellite and the receiver. The term "pseudorange" means

- the geometrical distance between the satellite and the receiver, which distance is deviated by unknown movements of the satellite and the receiver from the system time of the GPS.

[0005] In one possible solution scheme, it is assumed that the offset between satellite and system clocks is known, and the problem is reduced to solve a non-linear system of four unknown equations (3 coordinates of the receiver position and offset between the receiver and GPS clocks). Therefore, at least 4 measurements are required to be able to solve a system of equations. The result of this process is the position of the receiver.

[0006] Similarly, the general idea of ​​GNSS localization is to receive satellite signals in the receiver to be located, to measure the pseudorange between the receiver and the respective satellite and, additionally, the current position of the receiver, using additionally the estimated positions of the satellites. In general, the PRN signal used to modulate the carrier signal is evaluated for positioning as described above for GPS.

[0007] GNSS positioning can take place in different positioning modes.

[0008] The first mode is independent positioning of GNSS in a mobile station. In this mode, the GNSS receiver receives signals from GNSS satellites. A GNSS receiver or related mobile device - collectively referred to as a mobile station - decodes the beacon data directly from the satellite signals and calculates the position of the mobile station and other location information based on these signals and navigation data without any additional information from other sources.

[0009] The second mode is GNSS positioning based on a mobile station supported by the network. In this mode, the GNSS receiver is associated with a mobile communication device. The GNSS receiver can be integrated with a mobile communication device or it can be an additional equipment for a mobile communication device. The GNSS receiver and the mobile communication device in question constitute a mobile station. The mobile communication network provides assistance data received by the mobile communication device. Support data may include, for example, ephemeris, location and time information. Support data can be used by the receiver of a global navigation satellite system to improve its parameters when acquiring and tracking satellite signals. Alternatively or additionally auxiliary data may be used in a mobile station to calculate the location of a mobile station and other location information. For example, with the auxiliary data provided, decryption of the navigational information in tracked satellite signals may not be required.

[0010] The third mode is GNSS positioning supported by network-based mobile stations. In this mode, the GNSS receiver is associated with a mobile communication device. The GNSS receiver and the mobile communication device in question constitute a mobile station. In this mode, the mobile communication network to support satellite signal measurements ensures at least that the GNSS receiver acquires additional and temporary information via the mobile communication device. To

-3 calculate the position, the mobile station performs only signal measurements and reports the measurement results back to the network.

[0011] The second and third modes are together referred to as assisted GNSS (A-GNSS, assisted-GNSS). Thus, assisted GNSS means that if the technical conditions are met, the mobile communication network may provide the GNSS receiver with auxiliary data, such as time and navigation model, which allows the receiver to obtain a fixed position in a shorter time and in more difficult signal conditions.

[0012] A network server that generates helper data and / or calculates position solutions for A-GNSS may, for example, be a mobile location service server (Serving Mobile Location Center).

[0013] In both modes based on a mobile station, the network server may further request location information determined by the mobile station. Such location information may be used, for example, for location services requested by a mobile station or by other entities, such as a friend search service or a directory service. In this case, the mobile station using a dedicated location information message or location information elements (IEs) in another message will send to the network server the location information it has determined in the location calculations. Elements of location information are defined in various cellular standards and essentially include:

1. Position information in the coordinate frame of the global geocentric reference system 1984 (WGS-84) containing latitude, longitude and altitude

2. The ellipse of the position uncertainty

3. Speed ​​information containing the speed components in the local coordinate frame: direction, directional inaccuracy, horizontal speed, horizontal speed inaccuracy, vertical speed, inaccuracy in vertical speed

4. Linkage of mobile frame time and satellite time

5. The reference time, i.e. the time in which the location information was calculated, and which is to be used as a reference for the cell frame time and satellite time relationships. Preferably, the reference time is given in units of seconds [s] or milliseconds [ms].

[0014] Reference is made to US 2002/0145984, which relates to a system and method of collecting information to determine the location of users.

Summary of the Invention [0015] According to a first object of the invention, there is provided a method according to claim 1. According to a second object of the invention, there is provided a device according to claim 3. According to a third aspect of the invention, a method according to

11. According to a fourth aspect of the invention, there is provided a device according to claim 13.

[0016] The invention is based on the assumption that information regarding location information currently defined in cellular standards is based solely on GPS time, since until now only GPS was fully and globally available GNSS.

[0017] However, different GNSS have different times. Therefore, available definitions of messages regarding location information do not allow sending location information to a different time base than GPS, for example in UTC, Galileo, GLONASS, QZSS and the like. Currently defined messages do not apply to GNSS than GPS. For example, a mobile station supporting Galileo based positioning can not use currently defined messages to report generated location information to the server because the mobile station does not have access to GPS time. Location information messages must be redefined to be compatible with future systems.

[0018] It would be possible to define separate messages regarding location information for each GNSS, but this would significantly increase the number of definitions.

[0019] Alternatively, it could be required that UTC be used in all systems, but this would make the use of GNSS less flexible.

[0020] A first method is described that comprises receiving or compiling a message containing location information and a reference time identifier. It is assumed that the location information is determined on the basis of satellite signals, and the reference time identifier identifies the reference time used to determine the location information. The method further includes providing messages for broadcasting.

[0021] Furthermore, a first device is described that comprises a processing means configured to receive or compile a message including location information and a reference time identifier. Again, the location information is assumed to be based on satellite signals, and the reference time identifier identifies the reference time used to determine the location information. In addition, the processing component is configured to provide a received or juxtaposed message for transmission.

[0022] The processing component of the described first device may be implemented in hardware and / or software. For example, it may be a processor executing the program code to perform the required functions. Alternatively, it may be, for example, a circuit that is to perform the required functions, e.g. implemented in a set of integrated circuits or a chip similar to an integrated circuit. For example, the described device may be similar to the included processing component, but may also include additional elements. In addition, the device may, for example, be a module for integration with an electronic device, such as a wireless communication device or an additional GNSS device.

[0023] Furthermore, an electronic device that includes the first device described is described. In addition, the apparatus includes a GNSS receiver configured to receive satellite signals and / or a wireless communication element configured to allow communication with the server to which the message is to be transmitted.

[0024] The wireless communication element may be, for example, a cell engine or a Wireless Local Access Network (WLAN) engine and the like. For example, the described electronic device may be an improved cell phone, a laptop or additional GNSS equipment and the like.

[0025] Furthermore, a unit is described that comprises an electronic device with a GNSS receiver configured to receive satellite signals and a wireless communication device configured to allow communication with the server to which the message is to be transmitted. One of these devices could then contain the first device described. The devices of the assembly can be connected to each other by any suitable data link, for example a fixed cable or a Bluetooth connection^™, ultra wide bandwidth (UWB) or infrared connection and the like.

[0026] The wireless communication device of the described unit may be, for example, a cellular terminal or a wireless local area network terminal and the like. A cellular terminal may be a cellular telephone or other cellular terminal, such as a laptop, which comprises means for establishing a connection to the server over a wireless network.

[0027] Furthermore, an electronic device is described comprising the first device described, an interface for connecting to a wireless communication device and, additionally, an interface for connecting to the server to which the message is to be transmitted. For example, the electronic device may be a network server that sets up the described message based on the measurement results received from the wireless communication device or network server or gateway that receives the already established message from the wireless communication device. The server to which the message is broadcast may be, for example, a server providing a certain location service.

[0028] Furthermore, a first product is described in the form of a computer program in which a program code is stored on a computer-readable medium. When the program code is executed by the processor, it executes the first described method.

[0029] The first product described in the form of a computer program, for example, may be a separate memory device or memory that will be integrated with the electronic device. The invention should be understood to include a computer program code also independently of the product in the form of a computer program and a computer-readable medium.

[0030] Furthermore, a second method is described which comprises extracting location information and a reference time identifier from a received message. The location information was determined based on satellite signals, and the reference time identifier identifies the reference time used to determine the location information.

In addition, the method includes the processing of location information including a reference time identifier.

[0031] Furthermore, a second device is described that comprises a processing means configured to retrieve location information and a reference time identifier from a received message. The location information was determined based on satellite signals, and the reference time identifier identifies the reference time used to determine the location information. In addition, the processing component is configured to process location information including a reference time identifier.

[0032] The processing component of the described second device can be implemented in hardware and / or software. For example, it may be a processor executing the program code to perform the required functions. Alternatively, it may be, for example, a circuit that is to perform the required functions, e.g. implemented in a set of integrated circuits or a chip similar to an integrated circuit. For example, the described device may be similar to the included processing component, but may also include additional elements. In addition, the device may, for example, be a module intended for integration with a network server, such as an SMLC server.

[0033] Furthermore, an electronic device is described comprising a second device described and an interface configured to allow direct or indirect communication with a wireless communication device. An electronic device, for example, can be a network server that offers a location service.

[0034] Furthermore, a server is described comprising the described second device and an interface configured to allow communication with another electronic device. The described server may be, for example, a network server providing a location service, while the other electronic device may be, for example, a network server that compiles or redirects messages of a certain type or gateway transmitting messages of a specific type and the like.

[0035] Furthermore, a second product is described in the form of a computer program in which a program code is stored on a computer-readable medium. When the program code is executed by the processor, it implements the second method described.

[0036] Again, the second product described in the form of a computer program, for example, may be a separate memory device or memory that will be integrated with the electronic device. The invention should be understood to include a computer program code also independently of the product in the form of a computer program and a computer-readable medium.

[0037] Furthermore, a system is described which comprises the described first device and the second device described.

[0038] It is therefore proposed that reference time identification be included in the message transmitting the location information to identify one of the various

- possible types of time that have been used as a reference time of location information, while all previously presented solutions support only one type of reference time.

[0039] The approach described allows the use of a single message with any GNSS.

[0040] To this end, a new message may be defined that may be used for transmitting location information from a mobile station or a mobile unit to the server, using any GNSS or UTC system time as a reference time. This allows the mobile station or mobile team to use any type of reference time to generate location information and the server to uniquely determine what type of reference time is used. This is advantageous because the server may not know in advance which GNSS is supported by the mobile station or mobile team and / or which satellites from which satellite systems are available to decode the time at the mobile station or mobile station location.

[0041] Alternatively, a single message can be defined that allows the location information to be transmitted from the server to another server using any GNSS or UTC system time as a reference time. The connection between servers can be a dedicated network connection or internet connection. An example of a server system is that the first server has only a positioning function to receive location information from mobile stations or calculate location information from measurements received from mobile stations. The second server does not necessarily have to have some positioning function, but it only has features that allow you to use location information for certain location-based services, such as searching for friends or searching for a directory.

[0042] The reference time identifier may be included in the mandatory field or in the optional field of the message. If it is included in the optional field, you can define a standard reference time, for example coordinated universal time. The reference time identifier can then be included in the message only if the reference time used differs from the standard reference time.

[0043] The location information that may be included in the message may be specified as desired. They may include, for example, an indication of position, speed, time and / or time relationships. Time links may include, for example, linking cellular frame time with satellite time.

[0044] The invention can be used with any GNSS positioning, such as GPS, GLONASS, GALILEO, SBAS, QZSS, LAAS or a combination thereof. Consequently, a dedicated reference time identifier may, for example, be defined for a Galileo positioning system, GPS (including upgraded GPS), GLONASS, SBAS, QZSS, LAAS and / or for UTC, but also for all other system times, including future system time.

[0045] The invention may further be used, for example, to enhance 3GPP GERAN radio access protocols (a third generation GSM partner partnership program (Global System for Mobile Communications) / EDGE radio network (Enhanced Data) Rates for GSM Evolution, a technique associated with packet data transmission in GSM networks), 3GPP RAN (called Radio Access Network, radio access network) and OMA SUPL (Open Mobile Alliance Secure User Plane Location).

[0046] It should be understood that all of the embodiments shown can also be used in any suitable combination.

[0047] Other objects and features of the invention will become apparent from the following detailed description taken in conjunction with the attached drawings. It should be understood, however, that the drawings are for illustration purposes only and not as a definition of the boundaries of the invention for which reference should be made to the attached claims. It should further be understood that the figures are not scaled and that they are only intended to illustrate the structures and procedures described.

Brief Description of the Drawings [0048]

Fig. 1 is a block diagram of a system according to an embodiment of the invention;

Fig. 2 is a block diagram illustrating operation in the system of Fig. 1;

Fig. 3 is a table illustrating the insertion of an optional field for a reference time identifier;

Fig. 4 is a table illustrating the possible coding of a reference time identifier;

Fig. 5 is a block diagram of a system according to a second embodiment of the invention; and

Fig. 6 is a block diagram illustrating operation in the system of Fig. 5.

Detailed description of the invention [0049] Fig. 1 is a block diagram of a system that facilitates the transmission of location information to a server.

[0050] The system comprises a mobile station 10 and a network server 20 of a GSM network or any other communication network that allows wireless access. In addition, the system includes GNSS satellites, such as GPS (50) GPS satellites and Galileo (60 SV) satellites. Alternative or additional satellites, for example, may be GLONASS, SBAS, QZSS or LAAS satellites.

The mobile station 10 comprises a wireless communication element 11, a GNSS receiver 13, a processor 16 and a memory 17. The processor 16 is connected to each of the other elements 11, 13, 17.

[0052] The wireless communication element 11 may for example be a cell engine. The cell engine is a module containing all the elements required for conventional mobile communication between the mobile terminal and the cellular communication network 30 and which can be further improved with additional functions. In one embodiment, the functions of processor 16 and memory 17 may also be implemented in the processor and memory of the cell engine.

[0053] The GNSS receiver 13 may be configured to receive signals from a single type of GNSS satellites or from different types of satellites 50, 60 GNSS. The GNSS receiver 13 includes a acquisition and tracking element 14 that can be implemented in the hardware and / or in the software. For example, to acquire and track signals received from 50 GPS satellites or 60 Galileo satellites, signal measurement tasks, including correlation tasks, may be performed by the hardware under the control of the software code that is executed by the processing unit of the GNSS receiver 13. In one embodiment, the functions of processor 16 and memory 17 may also be implemented in the processor and memory of the GNSS receiver 13. In another embodiment, the wireless communications element 11 can be improved to perform software-based processing,

[0054] The processor 16 is configured to execute the implemented computer program code for performing various functions. The memory 17 is configured to store the computer program code which for execution may be downloaded by the processor 16. The memorized code includes a computer program code 18 for calculating location information by means of GNSS based positioning and a computer program code 19 for compiling location information, this is the identity (ID) of the reference time.

[0055] It should be understood that the functions of the processor 16 executing the program code 18 and 19 may also be implemented by circuits, e.g. in an integrated circuit.

Instead of a single-mode mobile station 10, a mobile unit 10 may be used, which is indicated by dashed lines in Fig. 1. Such a mobile unit 10 may comprise a mobile terminal with a mobile mobile communication element 11 and an additional GNSS device with a 13 GNSS receiver. Processor 16 and memory 17 may belong to a mobile terminal or an additional GNSS device.

[0057] The network server 20 includes a processor 26 and an interface 21 and memory 27 connected to the processor 26.

[0058] The interface 21 is configured to allow communication with the mobile stations providing the network 30. In more detail, communication is enabled via other non-shown network elements 30, including e.g. base transceivers stations (BTSs). ).

[0059] The processor 26 is configured to execute the implemented computer program code for performing various functions. Memory 27 is configured to

- storing computer program code, which for execution may be downloaded by the processor 26. The memorized code includes a computer program code 28 for extracting location information and a reference time reference from a received location message. In addition, it includes a computer program code 29 for providing at least one location-based service. Such a service can be, for example, a friends search service or a directory service that contains the business locations of the desired type near the current location requesting the mobile station 10.

[0060] It should be understood that the functions of the processor 26 implementing the program code 28 and 29 may also be implemented by circuits, e.g. in an integrated circuit.

[0061] Operation in the system of Fig. 1 will now be described with reference to Figures 2 to 4.

[0062] Fig. 2 is a block diagram illustrating operation at the mobile station on the left, and operation on a network server on the right 20.

[0063] In the mobile station 10, the acquisition and tracking component 14 of the GNSS receiver 13 acquires and tracks satellite signals and provides the results of measurements to the processor 16. To perform mobile positioning based on signal measurements (step 211), the processor 16 executes the computer program code 18. Optionally, acquiring and tracking the GNSS receiver 13 and / or computing positioning of the processor 16 may be handled by assistance data that is provided by the network 30 and received by the wireless communication element 11.

[0064] For the position calculation, the processor 16 uses the appropriate type of reference time. For example, it could use GPS time in case the positioning is based on GPS satellite signals, Galileo system times in case the positioning is based on satellite signals Galileo or UTC, when positioning is based on satellite signals GPS and Galileo and the like . In the case where the 13 GNSS receiver is configured to be able to receive signals from one GNSS satellite, it will always use the same type of reference time.

The reference time is used in the mobile station 10 to calculate the position of the satellites and as a time reference in the GSM time and / or other links such as GNSS or GNSS linking with the WLAN time frame and the like.

[0066] Furthermore, the processor 16 executes the computer program code 19 to collate the resulting location information into a location information message or into a location information element of a more comprehensive message (step 212). In addition to the current position information, a reference time ID is included which indicates the type of reference time used in the positioning calculations. In the case where the 13 GNSS receiver is configured to be able to receive signals from one GNSS satellite, it will always use the same reference time ID.

[0067] Fig. 3 is a table showing exemplary fields of defined elements that can be selected for compilation of a message or information item. Optional fields are marked with the letter "O" in the "Presence" column, and the mandatory fields in the "Presence" column are marked with the "M" symbol.

[0068] The first defined field is the reference frame field. This field defines the BTS reference frame number during which the location estimation was measured at mobile station 10.

[0069] The second defined field is the time-of-day (TOD) field of the GNSS. This field specifies the GNSS time for which it is important to estimate the location. They can be rounded down to the nearest whole millisecond. For example, in the case of GPS, the time of the day can be given according to the time of the week (TOW, time-of-week) GPS.

[0070] While the first field and the second field are optional, either the reference frame or TODS GNSS should always be included in the presented embodiment.

[0071] An alternative third defined field is the fraction field (Frac) TOD GNSS. This field specifies the GNSS time more precisely by indicating a fraction of the GNSS TOD in sub-milliseconds.

[0072] An optional fourth field defined is the TOD GNSS uncertainty field. This field ensures the accuracy of the relationship between GNSS time and the time of the cellular system. The actual GNSS time corresponding to the provided cellular network time found at the mobile station 10 may, for example, fall within the range (TOD GNSS uncertainty TOD GNSS, TOD GNSS + uncertainty TOD GNSS).

[0073] An optional fifth defined field is the reference time identification field (GNSS_TIME_ID). The GNSS_TIME_ID field defines which time of the satellite system has been used as a reference to time information indicated, for example, by TOD GNSS and a fraction of TOD GNSS.

[0074] Fig. 4 is a table showing an example of GNSS_TIME_ID encoding. The table combines the ID value in the "Display" column with different reference time types in the "GNSS_TIME_ID" column.

[0075] In this table, each reference time ID is represented by a different integer value from zero to seven such that each integer can be coded by three bits. The Galileo system time could be represented by zero, GPS time, including the time of the modernized GPS, it could be represented by one, the GLONASS time could be represented by two, the SBAS time could be represented by three, and the QZSS time could be represented by four. Integer values ​​from five to seven can be reserved for future use.

[0076] In the example shown GNNS_TIME_ID is attached to the location information information or location information element when a different time than UTC is used as the reference time. It should be understood that, alternatively, a UTC time code may also be provided.

[0077] Returning to the table of Fig. 3, the obligatory sixth field defined is the patch type field. This field indicates whether the mobile station 10 has performed two-dimensional (2D) or three-dimensional (3D) measurements.

[0078] An optional seventh pre-defined field is the stationary indication field. This field indicates whether during the collection of the ADR the measuring unit moved by a distance of less than 5 cm or if the measuring unit was in a fixed position. If the measuring unit is not able to determine its movement or measure motion, the field is set to "0" by default. If the measuring unit is not moving, the measuring unit may indicate static movement, setting the stationary indication to "1" and do not send the speed estimate field in the location information element, because the speed of the measuring unit will be zero. If the measuring unit is asked to report periodic elements of location information, the measuring unit can set the stationary indication to "1"

[0079] An optional eighth defined field is the position estimate field. The field contains the estimation of the position of the mobile station 10 resulting in the position calculation.

[0080] An optional nine-field field is the speed estimate field. The field contains the speed estimation resulting in the position calculation.

[0081] In the illustrated embodiment, each location information message should contain at most one of the seven to nine fields.

[0082] The different types of location information fields are given in the 3GPP TS 25.331 Technical Specification V7.0.0 (2006-03): "Radio Resource Control (RRC); Protocol Specification (Release 7)" and in the Technical Specification 3GPP TS 44.031 V7.2.0 (2005 -11): "Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Center (SMLC) Radio Resource LCS Protocol (RRLP) (Issue 7) "referred to for details. Also, the location information fields were presented by the 2nd Working Group 3GPP GERAN for location information A -GNSS in document Tdoc G2-060315: "Introduction of Assisted GALILEO capability as Assisted GNSS into the GERMAN" 3GPP TSG-GERAN WG2 Conference # 31bis, Turin, Italy, October 16-20, 2006 and in document Tdoc G2-060273: "A -GNSS support to RRLP ",

[0083] The processor 16 provides a juxtaposed location information message or other message comprising a juxtaposed location information element for the wireless communication element 11 to transmit. In particular, the juxtaposed location information may be provided along with the request for a location service offered by the network server 20.

[0084] The wireless communication element 11 transmits the received message via other network elements to the network server 20 (step 213).

[0085] At the network server 20, the interface 21 receives the message (step 221) and delivers it to the processor 26.

The processor 26 executes the program code 28 to extract location information and reference time ID from the received message, if possible (step 222).

[0087] Furthermore, the processor 26 executes the computer program code 29 to provide the desired service based on the extracted location information (step 223). To be able to use the location information correctly, the processor 26 takes into account the type of reference time determined by the extracted reference time ID that was used to generate the location information. That is, the reference time ID indicates to the processor 26 what kind of reference time has been used to determine the GNSS TOD and / or the TODS TODS fraction.

[0088] For example, a reference time may be used to assess the "age" of location information and to accurately link the GNSS system time to GSM time or other links from a plurality of mobile stations. For example, when the first mobile station reports links with respect to the Galileo time and the second mobile station reports links with respect to the GLONASS time, with both mobile stations involved in the desired service, the server 20 can now compensate for the time difference of Galileo and GLONASS.

[0089] The reference time reference of the illustrated embodiment thus allows the same location information message to be used with any GNSS time or even UTC. As a result, there is no need to specify many specific GNSS location information messages, which can reduce the complexity of network server implementation and the complexity of the communication system standards.

[0090] The illustrated embodiment is also compatible in advance because several values ​​of the reference time identifier GNSS_TIME_ID have been reserved for future systems.

The functions represented by the processor 16 implementing the program code 19 or the corresponding circuits can also be seen as means for receiving or composing a message containing location information and a reference time identifier, wherein the location information is determined on the basis of satellite signals and a reference time identifier determining the reference time used to determine the location information; and as a message delivery means for transmitting to a network server.

[0092] The program code 19 may also be seen as comprising such means in the form of functional modules.

[0093] The functions represented by the processor 26 implementing the program code 28 or the corresponding circuits can also be seen as means for extracting location information and a reference time identifier from the received message, while

- location information is determined on the basis of satellite signals and a reference time reference identifying the reference time used to determine the location information; while processor 26 executing program code 29 or its corresponding circuits can also be seen as a location information processing means including a time reference identifier.

[0094] The program codes 28 and 29 can also be seen as comprising such means in the form of functional modules.

[0095] Fig. 5 is a block diagram of another exemplary system that facilitates the transmission of location information to a server.

The system includes a first mobile station 310 including a GNSS receiver and a GNSS-based mobile station positioning support. It may correspond to the mobile station 10 described above with reference to Fig. 1. Furthermore, the system includes a second mobile station 311 comprising a GNSS receiver and a mobile station positioning support supported by GNSS.

[0097] Furthermore, the system includes a first server 320 and a second server 330.

[0098] For example, the first server 320 may be an SMLC server. For example, it may belong to a mobile communication network that is capable of providing mobile stations 310, 311 or to any other network that is connected to this mobile communication network. The server 320 may in principle only be a server supporting mobile stations 310, 311 in calculating the correction, collecting location information from mobile stations, calculating location information from satellite signal measurements, which mobile stations generate or calculating / determining location information from cellular network measurements and / or information such as Cell-ID, Rx levels, advance synchronization and the like.

[0099] The server 320 includes a processor 322 and connected to said processor 322 a first interface 321 allowing communication with the mobile stations 310, 311, a second interface allowing communication with the network server 330 and memory 324. The processor 322 is configured to execute computer program code stored in 324. The memorized code includes a code 325 for providing assistance data to mobile stations, code 326 for performing positioning calculations based on the results of satellite signal measurements provided by mobile stations, code 327 for compilation of location information and code 328 for transmitting location information messages received from mobile station.

[0100] The network server 330 may be configured to provide location-based services. For example, it may also belong to a mobile communication network that is capable of providing mobile stations 310, 311 or to any other network that is connected to this mobile communication network such as the Internet.

[0101] The network server 330 includes a processor 332 and a processor 332 connected to the interface 331, allowing communication with the network server 320 and memory 334. The processor 332 is configured to execute a program code stored in the memory.

-15334. The memorized code includes code 335 for extracting location information and a reference time identifier from the received message and code 336 for providing a location-based service, such as a directory.

[0102] Operation in the system of Figure 5 is shown in Figure 6.

[0103] Fig. 6 is a block diagram illustrating operation in mobile stations 310, 311 on the left, operation in the middle of a network server 320 and right-hand operation on a network server 330.

[0104] The mobile station 310 may operate similarly to the mobile station 10 of Fig. 1. Thus, steps 611 and 612 may correspond to steps 211, 212 and 213 as described above with reference to Fig. 2. The mobile station 310 sends a combined message to the server 320. containing location information and time reference identifier.

At server 320, processor 322 executing program code 328 receives the message through interface 321 and forwards a message via interface 323 to server 330 (step 621). It should be understood that processor 322 can convert a message from a format required by interface 321 to a format required by interface 323. This means that a different message can be defined for the connection between the mobile station 310 and the server 320 and the connections between the server 320 and the server 330.

[0106] Additionally or alternatively, the mobile station 311 performs satellite signal measurements for a GNSS-assisted base station (step 615). Required assistance data may be provided by a processor 322 executing program code 325. The processor 322 may receive the required information, e.g. from a connected local measuring unit (not shown).

[0107] The mobile station 311 does not perform stand-alone positioning calculations, but sends the measurement results to the server 320 (step 616).

At the server 320, the processor 322 executing the program code 326 receives the measurement results via the interface 321 and performs position calculations for the mobile station 311 (step 625) based on the measurement results and possibly other information obtained for example from a connected local measuring unit (not shown ).

[0109] For the position calculation, the processor 322 uses the appropriate type of reference time. The reference time may correspond, for example, to the GNSS system time used for measurements by the mobile station 311.

[0110] In addition, the processor 322 executes the program code 327 to compose the resulting location information in the location information message or into a location information element of a more comprehensive message. In addition to the current location information, a reference time ID is provided which indicates the type of reference time used in the positioning calculations. The location information element or the location information message may again, for example, comprise the fields shown in Fig. 3. The resulting message is sent via interface 323 to server 330 (step 626).

[0111] The server 330 receives the message together with the location information and reference time ID and processes it to provide the requested service. Steps 631, 632 and 633, which are performed for this purpose on the network server 330, correspond to steps 221, 222 and 223 described above with reference to Fig. 2. The processing may be the same for messages arranged by the mobile station 310 and for the messages set up through the server 320.

[0112] It should be understood that the combined and forwarding functions described may be equally implemented by various additional servers or gates.

[0113] Thus, the functions represented by the processor 322 executing respectively the program code 328 or 327 or the respective circuit can also be seen as means for receiving or composing a message containing location information and a reference time identifier, wherein the location information is determined on the basis of satellite signals and identifier a reference time identifying the reference time used to determine the location information; and as a message delivery means for transmitting to a network server.

[0114] Program code 328 and 327 may also be seen as comprising such means in the form of functional modules.

[0115] The functions represented by the processor 332 implementing program code 335 or corresponding circuits can also be seen as means for extracting location information and a reference time identifier from a received message, the location information being determined based on satellite signals and time reference identifier determining the time the reference used to determine the location information; while processor 332 executing program code 336 or corresponding circuits can also be seen as a location information processing means including a time reference identifier.

[0116] Program code 335 and 336 may also be viewed as including such means in the form of functional modules.

[0117] It should be understood that all of the references described in the above-described embodiments may be direct or indirect links.

[0118] Although the basic novel features of the invention used in its preferred embodiments have been shown, described and pointed out, various omissions and substitutions as well as changes in the form and details of the described devices and methods may be made by those skilled in the art without departing from the spirit of the invention. For example, it is expressly provided that all combinations of those elements and / or method steps that have substantially the same function are included within the scope of the invention in substantially the same way to achieve the same results. In addition, it should be noted that the structures and / or elements and / or method steps disclosed and / or described in connection with any disclosed form or embodiment of the invention may be incorporated into any other disclosed or described or suggested form or embodiment as general design selection issues. For this reason, this intention is to be

- limited only to the indication in the scope of the comments attached to it. Furthermore, in the claims, the "plus function" clauses are meant to include the structures described herein as performing the aforementioned function and not only their structural equivalents, but also equivalent structures.