RU2392636C1 - Method and device for supported navigation systems - Google Patents

Abstract

FIELD: physics, navigation.

SUBSTANCE: invention relates to navigation systems and elements. According to the invention, a network element (M) for supporting positioning includes a receiver (M.2.2) for generating support data associated with at least one navigation system. The network element (M) includes indication of the navigation system and the selected mode into support data and generates support data in accordance with the selected mode. The network element (M) has a transmitting element (M.3.1) for transmitting support data over the communication network (P) to the positioning device (R). The positioning device (R) includes a positioning receiver (R.3) for positioning based on one or more signals from at least one of the said satellite navigation systems; a receiver (R.2.2) for receiving support data from the network element (M) and a verification element (R.1.1) designed for verifying received support data. The said support data are meant for use by the positioning receiver for positioning the device (R).

EFFECT: obtaining a GPS navigation model directly from satellite transmission, altering these data and distributing them to network terminals in accordance with different standards of use.

38 cl, 6 dwg, 6 tbl

Description

FIELD OF TECHNOLOGY

This invention relates to the field of navigation systems with support and, more specifically, to a format in which support data is distributed from the communication network to the terminals. The invention also relates to a device including a positioning receiver for performing positioning based on one or more signals of a satellite navigation system. The invention also relates to a network element including a transmitter for transmitting satellite navigation support data to a receiver. The invention further relates to a method, a computer program product, and a signal for delivering support data for a satellite navigation system to a positioning receiver.

BACKGROUND

One of the well-known navigation systems is the GPS (Global Positioning System), which currently includes more than 24 satellites, of which usually half is simultaneously in the field of view of the receiver. These satellites transmit, for example, ephemeris data as well as satellite temporal information. The receiver used in positioning usually sets its position by counting the transit time of the signal received by the receiver from several satellites belonging to the positioning system at the same time and calculates the transmission time (ToT) of the signals. For positioning, the receiver typically needs to receive a signal from at least four satellites in the field of view in order to calculate the location. Another already launched navigation system is the Russian GLONASS system (Global Navigation System).

In the future, there will be other satellite-based navigation systems besides GPS and GLONASS. In Europe, the Galileo system is under construction and will be launched within a few years. Satellite Based Augmentation Systems (SBAS) correction systems are also expanding, such as WAAS (Wide Area Augmentation System), EGNOS (European Geostationary Navigation Overlay Service) and GAGAN (GPS Aided GEO Augmented Navigation). Local Area Augmentation Systems (LAAS) using fixed ground navigation stations are increasingly being used. Strictly speaking, local adjustment systems are not really satellite navigation systems, although their navigation stations are called “pseudo-satellites” or “pseudo-lits”. The navigation principles applicable to satellite-based systems are also applicable to local adjustment systems. Pseudolith signals can be received by a standard GNSS receiver (Global Navigation Satellite System, GNSS). In addition, the Japanese are developing their own GPS / Galileo supplement system called the Quasi-Zenith Satellite System (QZSS).

Satellite-based navigation systems, including systems using pseudo-satellites, can collectively be called Global Navigation Satellite Systems (GNSS). In the future, there may be positional receivers that can perform positioning operations using simultaneously or alternatively more than one navigation system. Such hybrid receivers can switch from the first system to the second system if, for example, the signal level of the first system falls below a certain threshold, or if the satellites of the first system are not visible enough, or if the combination of visible satellites of the first system is not suitable for positioning. The simultaneous use of different systems becomes appropriate in difficult conditions, such as urban areas, where the number of visible satellites is limited. In such cases, navigation based on only one system is almost impossible due to the low availability of signals. However, the hybrid use of various navigation systems allows navigation in these complex signal conditions.

Each satellite of the GPS system transmits a sounding signal at a carrier frequency of 1575.42 MHz, called L1. This frequency is also indicated as 154f ₀ , where f ₀ 10.23 MHz. In addition, the satellites transmit another sounding signal at a carrier frequency of 1227.6 MHz, called L2, i.e. 120f ₀ . The satellite modulates these signals with at least one pseudo-random sequence. This pseudo-random sequence is different for each satellite. As a result of the modulation, a code modulated wideband signal is generated. The modulation technology used makes it possible to distinguish between the signals transmitted from different satellites in the receiver, although the carrier frequency used for transmission is actually the same. The Doppler effect gives a small (± 1 kHz) change in the carrier frequency depending on the geometry of the group. This technology is called Code Division Multiple Access (CDMA). In each satellite, to modulate the L1 signal, the pseudo-sequence used is, for example, the so-called C / A code (coarse detection / capture code), which belongs to the Gold code family. Each GPS satellite transmits a signal using an individual C / A code. Codes are generated as the sum modulo 2 of two 1023-bit binary sequences. The first binary sequence G1 is formed by the polynomial X ¹⁰ + X ³ +1, and the second binary sequence G2 is formed by the polynomial X ¹⁰ + X ⁹ + X ⁸ + X ⁶ + X ³ + X ² +1 with a delay so that there is a delay for each satellite. Such a scheme allows the issuance of different C / A codes by an identical code generator. C / A codes are, therefore, binary codes, the transmission speed of the signal elements of which in the GPS system is 1.023 MHz. C / A code includes 1023 elements, while the transmission time of the code is 1 ms. The carrier signal L1 is then modulated by the navigation information at a rate of 50 bit / s. Navigation information includes information about the state of the satellite, its orbit, time data, etc.

In the GPS system, satellites transmit navigation information, including ephemeris data and time data, which are used in the positioning receiver to determine the current position of the satellite. This ephemeris data and temporary data are transmitted in frames, which are further divided into subframes. 6 shows an example of such a FR frame structure. In the GPS system, each frame includes 1,500 bits, which are divided into subframes of 300 bits each. Since the transmission of one bit takes 20 ms, the transmission of each subframe thus takes 6 seconds, and the entire frame is transmitted in 30 seconds. The subframes are numbered from 1 to 5. In each subframe 1, for example, time data is transmitted, the transmission time of the subframe is indicated, as well as information about the deviation of the satellite clock with respect to time in the GPS system.

Subframes 2 and 3 are used to transmit ephemeris data. Subframe 4 contains other system information, such as Coordinated Universal Time (UTC). Subframe 5 is for transmitting almanac data over all satellites. An object of these subframes and frames is called a GPS navigation message, which includes 25 frames or 125 subframes. The duration of the navigation message is thus 12 minutes 30 seconds.

In GPS, time is measured in seconds from the start of the week. In the GPS system, the start of the week is considered midnight from Saturday to Sunday. Each transmitted subframe contains information about the GPS moment of the week at which the subframe was transmitted. Thus, the time data shows the moment of transmission of a certain bit, i.e. moment of transmission of the last bit of a subframe in the GPS system. In satellites, time is measured by high-precision atomic chronometers. Despite this, the operation of each satellite is monitored in the GPS systems control center (not shown), and, for example, time is compared to determine the chronometric errors on the satellites and transmit this information to the satellite.

Number of satellites, satellite orbit parameters, structure of navigation messages, etc. may vary in different navigation systems. On the other hand, at least the Galileo design principles show that there will be some similarities between Galileo and GPS to the extent that at least the Galileo receiver will be able to use GPS satellite signals for positioning.

Positioning devices (or receivers), for example, devices that are able to perform positioning based on signals transmitted in navigation systems, cannot always receive sufficiently strong signals from the required number of satellites. This can happen indoors, in urban environments, etc. For communication networks, methods and systems have been developed that allow positioning (positioning) in adverse signal conditions. If the communication network provides only the navigation model support for the receiver, the requirement of at least three signals for two-dimensional positioning or four signals for three-dimensional positioning does not decrease. However, if the network provides, for example, barometric support, which can be used to determine altitude, then three satellites are sufficient for three-dimensional positioning. These so-called support navigation systems use other communication systems to transmit satellite related information to positioning devices. Accordingly, such positioning devices that are able to receive and use support data can be called GNSS receivers with support or, more generally, support positioning devices.

Currently, only GPS satellite-related support data can be provided to GNSS receivers with support for CDMA (Code Division Multiple Access), GSM (Global System for Mobile Communications), and W-CDMA (Code Division Wideband Multiple Access) communications networks channels). The format of this support data is close to the GPS navigation model defined in the GPS-ICD-200 SIS specification (ICD, Interface Control Document; SIS, Signal-In-Space). This navigation model includes a synchronization model and an orbital model. More specifically, the synchronization model is used to correlate satellite time with system time, in this case GPS time. The orbital model is used to calculate the current position of the satellite. Both of these data are essential for satellite navigation.

The availability of support data can significantly affect the performance of a positioning receiver. In a GPS system, under good signal conditions, it takes at least 18 seconds (the length of the first three subframes) for the receiver to extract a copy of the navigation message from the satellite’s broadband GPS signal. Therefore, if there is no valid message (for example, from a previous session) of the navigation model, it takes at least 18 seconds before the GPS satellite can be used to calculate the position. Now, with AGPS (GPS-enabled) receivers, a cellular network, such as GSM or UMTS (Universal Mobile Communications System), sends a copy of the navigation message to the receiver, and therefore, the receiver does not have to extract data from the satellite’s broadband signal, but can receive them directly from the cellular network. Time to First Fix (TTFF) can be reduced to less than 18 seconds. This reduction in time can be critical, for example, when positioning for an emergency call is performed. It also improves the user's capabilities in various use cases, for example, when the user requests information about the services available near the user's current location. This kind of Location Based Services (LBS) uses the user's specific location in the request. Therefore, a location delay may delay a response from the LBS service to a user.

In addition, in adverse signal conditions, the use of support data may be the only navigation option. A drop in signal strength makes it impossible for the GNSS receiver to receive a copy of the navigation message. However, when navigation data is provided to the receiver from an external source (such as a cellular communication network), navigation is again possible. This feature can be important in indoor applications as well as in urban environments where signal levels can vary significantly due to buildings and other obstructions that attenuate satellite signals.

International application WO 02/67462 describes GPS support data messages in cellular networks and methods for transmitting GPS support data messages in cellular networks.

When a mobile terminal having a supported positioning receiver requests support data, the network sends one mobile model for each satellite in the field of view of the supported positioning receiver to the mobile terminal. The format in which support data is transmitted is defined in various standards. Control Plane solutions include the Radio Resource Location Services Protocol (RRLP) in the GSM network, the Radio Resource Control (RRC) system in the W-CDMA network, and IS-801.1 / IS- standards 801.A on the CDMA network. Support data elements are defined in TS 44.035 for GSM. Finally, there are OMA SUPL 1.0 (Open Mobile Alliance, Secure User Plane for Location) User Plane solutions and various proprietary CDMA network solutions. Common to all these solutions is that they only support GPS. However, with the addition of the Galileo system, all standards will soon be upgraded to achieve compatibility with Galileo.

Therefore, it is clear that support exclusively for GPS will not meet the requirements in the near future, and a new data format must be developed that can support new systems.

The problem of providing support data for new systems, as well as for GPS, can be reduced to finding a navigation model (synchronization and orbital models) that can be used to describe all satellite systems. The direct solution is to take the initial format of the navigation message for each of the systems and use this format. However, this will result in different messages (different message formats for each system), which makes the task execution problematic. In addition, the original format may not be compatible with cellular network standards. Therefore, the final solution should be such that various formats are not required.

The problems of developing a common format include, firstly, satellite indexing. The satellite index is used to identify the navigation model in a particular satellite. The problem is that each system has its own indexing method.

GPS satellite indices (SV, space vehicle) are based on PRN (pseudo-random sequence) numbers. The PRN can be identified using the CDMA spreading code used on the satellites.

Galileo uses a 7-bit field (1-128) to identify the satellite. The number can be identified using the PRN code used by the satellite.

GLONASS uses a 5-bit field for satellite recognition. The number can be identified with the position of the satellite in the orbital planes (this position is called the “slot”). In addition, unlike other systems, GLONASS uses FDMA (Frequency Division Multiple Access) for spread-spectrum satellite signals. It should be understood that GLONASS also uses distributed CDMA code. Therefore, there is a table that maps the satellite slot number and the frequency of the broadcast signal. This compliance should be included in any support data format.

SBAS systems use PRN numbers, like GPS, but have an offset of 120. Therefore, the first SBAS satellite has a satellite number of 120.

Since the QZSS SIS ICD is not yet public, there is no detailed information on satellite indexing in the system. However, since the system is a development of GPS, it is likely that the GPS-compatible format will be compatible with QZSS as well.

Pseudoliths (LAAS) are most problematic in terms of indexing. There is currently no specific standard for indexing pseudoliths. However, the indexing should at least approximately correspond to the GPS-type indexing, since they use a GPS-type PRN. Therefore, if the range of satellite indices is sufficient, it would be possible to describe LAAS transmitters by GPS-type indexing.

The next problem is the synchronization model. The synchronization model for any system is specified as

f _SYSTEM (t) = t _sv (t) - [a ₀ + a ₁ · (t _SYSTEM (t) -t _REFERENCE ) + a ₂ · (t _SYSTEM (t) -t _REFERENCE ) ² ],

where t _SYSTEM (t) is the system time (for example, GPS time) at time t, t _sv (t) is the satellite time at time t, t _REFERENCE is the model origin time and a _i , (i∈ {0, 1, 2}) - 0, 1 and 2 ordinal coefficients of the model, respectively. A member of the relativistic correction is not shown in this equation. Since the equation in each system is the same, the only problem in creating a common model is to find such bit values and scale factors for which: 1) the required range of values for each system is covered and 2) the accuracy (or resolution) requirements for each system are achieved .

The third problem includes the orbital model. Again, each system has its own format (with the exception of GPS and Galileo, using the same format). GPS and Galileo use a set of Keplerian orbit parameters: 6 orbit parameters, 3 linear correction coefficients, and 6 harmonic gravity correction coefficients. Unlike GPS and Galileo, the GLONASS navigation model contains only information about the position, speed and acceleration of the satellite at the moment. This information can then be used (in solving the problem with initial conditions for the equations of motion) to predict the position of the satellite at some point. SBAS uses a format somewhat similar to GLONASS. SBAS navigation message includes information on the position, speed and acceleration of the satellite in ECEF (Earth-Centered Earth Fixed coordinate system definition) systems at the moment. These data are used to predict the position of the satellite by simple extrapolation, which differs from GLONASS, in which the equations of motion are integrated over time. Again, since the QZSS ICD is not yet available, the detailed format of the navigation message is unknown. However, there are documents that regard the QZSS ICD format as compatible with broadcasting GPS-type or SBAS-type ephemeris. Therefore, if the new format is compatible with GPS and SBAS, QZSS orbits can be described using the GPS format. LAAS requires the orbital model to describe objects stationary in an ECEF frame. Also, pseudoliths have fairly stringent resolution requirements for position. In some cases, it is necessary to describe the position of the pseudoliths with a resolution of about 5 mm.

In addition to these requirements (indexing, synchronization model, and orbital model), the navigation model should include information on the reference time of model t _REFERENCE in the synchronization model, similar to the time stamp required in the orbital model), the time of the model’s operation, and the output of data (to be able to to differentiate the model data sets) and the state of the SV (indicates whether navigation data from the SV is usable or not).

Needless to say, almost all systems have their own way of expressing these parameters. Range and accuracy requirements vary from system to system. In addition, the current state of the satellite requires modification, since in the future GPS (and other systems) will transmit not only one signal, but various signals with different frequencies.

The new support data format should be such that all the specific elements of the system, as well as the range of parameters and accuracy requirements, are taken into account.

Finally, the problem with the current support data format is that it allows only one set of navigation data available for a given satellite. This means that when the navigation model is updated, new data must be provided to the terminal. However, now there are commercial services providing navigation data, with a validity period of 5-10 days. The duration of the navigation model does not increase, but the service sends numerous sets of navigation data for one satellite. In GNSS-enabled, this provides benefits as the user receives all the support needed over the next couple of weeks in one download. The new support data format should therefore be able to support these long-term orbit matching in current models.

There is currently no solution to the problem. This is because the distribution of support data is limited to GPS and CDMA networks.

The current solution for distributing support data among terminals is to obtain a GPS navigation model directly from satellite broadcasting, change this data and distribute it among network terminals in accordance with various usage standards.

SUMMARY OF THE INVENTION

The present invention includes a generalized navigation model that can be used to characterize the functioning of a satellite clock and satellite orbit in more than one navigation system. A generalized navigation model can be used at least in conjunction with GPS, Galileo, GLONASS, SBAS, LAAS and QZSS. It also provides redundancy for unknown future systems.

The indexing problem is solved by expanding the satellite index field in such a way that the upper bits of the field determine the navigation system (GPS, Galileo, GLONASS, SBAS, LAAS, QZSS or some other system in the future), and the lower bits express the satellite index in the format inherent to the system . The field below will be called the SS index, which means “System and Satellite”. There is also a special addition for GLONASS, which allows you to display the SS index on the frequency of satellite broadcasting (or channel).

The task of the synchronization model is solved by finding such bit numbers and scale factors for the coefficients that the synchronization models in all systems can be described using a generalized synchronization model. However, the invention does not exclude the use of different synchronization models for each of the systems.

The problem of the orbital model is solved by the introduction of a multimode model. Model modes are, for example, mode 1: Keplerian model; mode 2: Position in ECEF coordinates; and mode 3: Position, speed and acceleration in ECEF coordinates. More modes may be added if necessary. For example, the upper bits of the SS index (i.e., system) determine the model mode. However, other embodiments may also be used to indicate the model mode, for example using a mode index. Modes are mutually exclusive.

Long-term orbit installations do not require anything special. The reference time and the time of action accurately determine when the model can be used. If long-term data is available, the network provides the terminal with long-term data and the terminal is responsible for storing and processing multiple sets of navigation data from a single satellite (or SS index). However, if the navigation model is not based on the broadcast navigation model, but is long-term data, this may be indicated, for example, in the data publishing field, but other implementations are also possible.

In accordance with a first aspect of the present invention, there is provided an apparatus comprising:

- a positioning receiver for performing positioning based on one or more signals of at least one navigation system;

- a receiver for receiving support data related to at least one navigation system, and

- a checking element designed to verify support data;

characterized in that the device also includes:

- a determining element for determining the mode of the support data in the specified support data, where the specified support data is intended for use by the positioning receiver to perform positioning of the device.

In accordance with a second aspect of the present invention, there is provided a network element including:

- a control element for generating support data related to at least one navigation system, and

- a transmitting element for transmitting support data to a communication network;

characterized in that the control element is intended for:

- selection of data transfer support mode;

- insertion of the navigation system indication into the support data and

- formation of support data in accordance with the selected mode.

In accordance with a third aspect of the present invention, there is provided a system comprising:

- a network element that includes:

- a control element for generating support data related to at least one navigation system, and

- a transmitting element for transmitting support data to a communication network;

- a device that includes:

- a positioning receiver for performing positioning based on one or more signals of said at least one navigation system;

a receiver for receiving support data from the network element; and

- a checking element designed to verify the received support data;

characterized in that:

- the control element is configured to select a data transmission mode of support;

- inserting the indication of the navigation system and the selected mode into the support data and

- building support data in accordance with the selected mode;

and the device also includes:

- a determining element for determining the mode of the support data in the specified support data, where the specified support data is intended for use by the positioning receiver to perform positioning of the device.

In accordance with a fourth aspect of the present invention, there is provided a module for a device including a positioning receiver for performing positioning based on one or more signals from at least one navigation system, wherein said module includes:

- a receiving element for receiving support data related to at least one navigation system, and

- a checking element designed to verify the received support data;

characterized in that the module also includes:

a determining element for determining a mode of support data in said support data, and

- an output for transmitting an indication of a mode of support data to a positioning receiver, wherein said support data is intended for use by the positioning receiver to perform positioning of the device.

In accordance with a fifth aspect of the present invention, there is provided a method for transmitting support data to a device, comprising:

- generating support data related to at least one navigation system, and

- transfer of support data to the device;

characterized in that the method also includes:

- determination of the navigation system to which the support data relates;

- selection of data transfer support mode;

- insertion of the indication of the navigation system and the selected mode into the support data and

- building support data in accordance with the selected mode.

In accordance with a sixth aspect of the present invention, there is provided a computer program product for storing a computer program having computer-executable instructions for:

- generating support data related to at least one navigation system, and

- transfer of support data to the device;

characterized in that the computer program also includes computer-executable instructions for:

- definitions of the navigation system to which the support data relates;

- selecting a mode for transmitting support data;

- inserting the indication of the navigation system and the selected mode into the support data and

- building support data in accordance with the selected mode.

In accordance with a seventh aspect of the present invention, there is provided a signal for delivering support data to a device, including:

- support data related to at least one navigation system;

characterized in that it also includes:

- an indication of the navigation system to which the support data relates, and a mode selected for transmitting support data; where the specified support data is built in accordance with the selected mode.

According to an eighth aspect of the present invention, there is provided a medium on which a signal is recorded for delivering support data to a device, the signal including:

- support data related to at least one navigation system;

characterized in that the signal also includes:

- indication of the system to which the support data relates, and the mode selected for transmitting the support data; where the specified support data is built in accordance with the selected mode.

In accordance with a ninth aspect of the present invention, there is provided a support data server, including:

- a control element for generating support data related to at least one navigation system, and

- a transmitting element for transmitting support data to a communication network;

characterized in that the control element is designed to select a mode for transmitting support data;

- inserting the indication of the navigation system and the selected mode into the support data and

- building support data in accordance with the navigation system.

The invention provides several advantages compared with the prior art. The format of the invention is applicable to a number of cellular standards and GNSS systems. These properties make the present invention a very attractive solution, since a universally applicable solution reduces implementation costs. This applies to telephone manufacturers, as well as telecom operators and potential providers of commercial data support services. Well-known RRLP and RRC solutions only include the ability to provide GPS-enabled data to a GPS-enabled receiver. There is no support for Galileo, GLONASS, SBAS, LAAS or QZSS. This is an obstacle that can be eliminated using the present invention. Since Galileo support data will almost certainly be included in RRLP and RRC, it is now possible to make this format as universal as possible, in order to be able to also support future systems.

DESCRIPTION OF DRAWINGS

The invention will now be described in more detail with reference to the accompanying drawings, in which:

figure 1 depicts in the form of a General simplified diagram of a system in which the present invention can be applied,

figure 2 depicts the reference receiver of the navigation system in accordance with an example implementation of the present invention in the form of a simplified block diagram,

figure 3 depicts a network element in accordance with an example implementation of the present invention in the form of a simplified block diagram,

4 depicts a device in accordance with an example embodiment of the present invention in the form of a simplified block diagram,

5 depicts an example implementation of the present invention and

6 shows an example of a frame structure used in a GPS system.

DETAILED DESCRIPTION OF THE INVENTION

Figure 1 shows an example of a system 1 that can be used to position device R. System 1 includes reference stations S, such as satellites S1 of the first navigation system, such as GPS, and satellites of the second navigation system S2, such as GLONASS. It should be noted here that GPS and GLONASS are only mentioned as non-limiting examples of the invention, and other reference stations S, and not satellites (for example, pseudoliths LAAS) can also be used. Also, the number of reference stations is larger than shown in FIG. Navigation systems include one or more ground stations G. Ground station G controls the operation of satellites S1, S2 of navigation systems 2, 3, respectively. Ground station G can, for example, determine satellite orbit deviations and satellite clock accuracy (not shown). If the ground station G determines the need to correct the satellite’s orbit or clock S1, S2, it transmits a control signal (or control signals) to the satellites S1, S2, which then perform the correction operation based on the control signal. In other words, ground station G refers to the ground segment of the navigation system.

During their operation, satellites S1, S2 monitor the status of their equipment. Satellites S1, S2 can use, for example, self-monitoring operations to determine and report possible equipment failures. Errors and malfunctioning can be instantaneous or continuous. Based on the status data, some of the malfunctions can be compensated, or information transmitted from a malfunctioning satellite can be completely ignored. A malfunctioning satellite S1, S2 sets the satellite status flag in the navigation message field, indicating a satellite malfunction. Satellites S1, S2 may also indicate in the navigation message a signal or signals that are not working properly. It is also possible that ground station G can determine that some satellites are not working properly and set up an indication of the satellite's malfunctioning signals. This indication may then be transmitted to the communication network P in a navigation message.

In this non-limiting example of the invention, the communication network P is a GSM network, and the network element M, interacting with the reference receiver C, C ″, is a mobile switching center (MSC) of a GSM network. The reference receiver C may transmit support data to the network element M. The network element stores the support data in the memory M.4 (FIG. 3) for transmission to the device R when the device R needs the support data to perform the support positioning operation. It is also possible to transmit support data from the network element M to the device R until when they are needed. For example, device R may request support data for all visible satellites and store navigation data in memory R.4 of device R for future use.

Network element M may also be a Serving Mobile Location Center (SMLC) of a GSM network. The location service center is either a single network element (such as an MSC) or an integrated base station B facility (BSC, base station controller) containing the functionality required to support location-based services. The SMLC manages the overall coordination and scheduling of resources required to locate the device R. It also calculates an estimate of the final location and estimates of accuracy achieved. The SMLC can manage the number of Location Measurement Units (LMUs) in order to obtain mutual interference measurements when determining a location or to assist in determining the location for mobile station subscribers in the areas it serves.

Now, the basic elements of an embodiment of the reference receiver C will be described in more detail with reference to FIG. 2. The disclosure is applicable to both the reference receiver C of the first navigation system and the receiver C ″ of the second navigation system, although the practical implementation may vary for each of them. The reference receiver C includes a controller C.1 for controlling the operation of the reference receiver C. The controller C.1 includes, for example, a processor, microprocessor, digital signal processor (DSP), or a combination thereof. Obviously, controller C.1 may have more than one processor, microprocessor, digital signal processor (DSP), etc. There is also a receiving unit C.2, containing a receiver C.2.2 for receiving signals from satellites S1, S2 of the navigation system. The reference receiver C.2 also includes a communication unit C.3 for direct or indirect communication with the network element M of the communication network P. Communication unit C.3 includes a transmitter C.3.1 for transmitting signals to the network element M and, if necessary, the receiver C.3.2 for receiving signals transmitted by the network element M to the reference receiver C. The reference receiver C may also include a memory C.4 for storing data and programs (computer control programs).

The structure of an example implementation of the network element M is shown in Fig.3. The network element M includes a controller M.1. Also, the M.1 controller of the network element may consist of a processor, microprocessor, digital signal processor (DSP), or a combination thereof. Obviously, the M.1 controller can have more than one processor, microprocessor, digital signal processor (DSP), etc. The network element M can be connected to the reference receiver C through the first communication unit M.2. The first communication unit M.2 includes an M.2.2 receiver for receiving signals from reference receivers C of navigation systems. The first communication unit M.2 may also include a transmitter M.2.1 for transmitting, for example, request messages to the reference receiver C of the navigation system. The network element M, in addition, includes a second communication unit M.3 for communication with base stations B or other access points of the communication network P. The second communication unit C.3 includes a transmitter M.3.1 for transmitting signals to base stations B and a receiver M. 3.2 for receiving signals transmitted by base stations B to network element M. Network element M also includes memory M.4 for storing data and programs (computer control programs).

The network element M receives support data either from satellite broadcasts, using the reference receiver C, or some other external solution, for example, from the support data server X, intended for the accumulation and transmission of such information in communication networks. Support data server X includes elements similar to network element M regarding operations related to receiving navigation data, generating and transmitting support data (i.e., receiver M.2.2, controller M.1, transmitter M.3.1, memory M.4 ) Support data server X may also include items related to receiver C.2. The support data server X may be, for example, the server of a commercial service provider from which a request for support data is received, possibly for a fee.

4 shows an apparatus R in accordance with an embodiment of the present invention in a block diagram. Device R includes one or more R.3 positioning receivers for receiving signals from reference stations S1, S2 of one or more navigation systems. One R.3 positioning receiver may be used for each navigation system that the R device is intended to support, or one R.3 positioning receiver may be used to perform positioning based on signals from more than one navigation system. Device R also includes an R.1 controller for controlling the operation of device R. In addition, the network element controller R.1 may consist of a processor, microprocessor, digital signal processor (DSP), or a combination thereof. Obviously, there may be more than one processor, microprocessor, DSP, etc. It is also possible that the R.3 positioning receiver may include an R.3.1 control element (for example, a processor, microprocessor and / or DSP), or the R.3 positioning receiver uses a device R controller in positioning. It is also possible that some of the positioning operations are performed the R.3.1 control element of the R.3 positioning receiver, and some other positioning operations are performed by the device controller R.1. The device R can communicate with the base station In the communication network P through the communication unit R.2. Communication block R.2. includes an R.2.2 receiver for receiving signals from a base station in the communication network P. The communication unit M.2 also includes a transmitter R.2.1 for transmitting signals to the base station in the communication network P. Data and programs can be stored in the device’s memory R.4. The R device also has an R.5 user interface (UI), which includes, for example, an R.5.1 display, an R.5.2 keypad (and / or keyboard), and R.5.3 audio tools such as a microphone and speaker. It is also possible that the device has more than one user interface.

The device R may be, for example, a mobile communication device for communicating with a communication network P, known per se. The R.5 user interface may be common to the mobile component and the R.3 positioning device.

The following discloses a non-limiting example of support data format fields with reference to Table 1 and FIG. 5. The problem of the orbital model is solved by introducing a multimode model. Model modes - this is at least mode 1: the Kepler model, which supports at least GPS, Galileo and QZSS systems; mode 2: Position in ECEF coordinates supporting at least the LAAS system; and Mode 3: Position, speed, and acceleration in ECEF coordinates, supporting at least GLONASS, SBAS, and QZSS systems. There may also be more than three modes for future systems and various modes of carrying out the invention.

Table 1 shows the corresponding number of bits, scale factors, and various modes. Explanations are given after the table.

Table 1 Parameter #bit Scale coefficient Units On (t _oe _MSB) 12 2 ²⁰ s (seconds) Identification of satellite and format (once per model) SSID 9 ^(u) - - M Carrier Frequency Index 5 - - FROM (Matching Interval) 6 - h FROM (SV state) 8 ^(u) - boolean FROM (IOD) 11 ^(u) - - FROM Satellite watch model (once per model) (t _oe ) 20 ^(u) one from FROM af ₂ eighteen 2 ^-65 s / s ² FROM af ₁ 16 2 ^-43 s / s FROM af ₀ 28 2 ^-33 from FROM (T _GD ) 8 2 ^-31 from FROM Satellite navigation model using Kepler parameters (once per model) (t _oe ) 20 ^(u) one from C ⁽¹⁾ , mode 1 ω 32 2 ^-31 half period C ⁽¹⁾ , mode 1 Δn 16 2 ^-43 half-cycle / s C ⁽¹⁾ , mode 1 M ₀ 32 2 ^-31 half period C ⁽¹⁾ , mode 1

24 2 ^-43 half-cycle / s C ⁽¹⁾ , mode 1 e 32 ^(u) 2 ^-33 - C ⁽¹⁾ , mode 1

fourteen 2 ^-43 half-cycle / s C ⁽¹⁾ , mode 1 (A) ^1/2 32 ^(u) 2 ^-19 m ^1/2 C ⁽¹⁾ , mode 1 i ₀ 32 2 ^-31 half period C ⁽¹⁾ , mode 1 Ω ₀ 32 2 ^-31 half period C ⁽¹⁾ , mode 1 C _rs 16 2 ^-5 m C ⁽¹⁾ , mode 1 C _iS 16 2 ^-29 radian C ⁽¹⁾ , mode 1 C _US 16 2 ^-29 radian C ⁽¹⁾ , mode 1 C _rc 16 2 ^-5 radian C ⁽¹⁾ Mode 1 C _iC 16 2 ^-29 radian C ⁽¹⁾ Mode 1 C _UE 16 2 ^-29 radian C ⁽¹⁾ Mode 1 Satellite navigation model using ECEF coordinates (once per model) (t _oe ) 20 ^(u) one from C ⁽²⁾ , mode 2 and 3 X msb 27 one m C ⁽²⁾ , mode 2 and 3 Y MSB 27 one m C ⁽²⁾ , mode 2 and 3 Z MSB 27 one m C ⁽²⁾ , mode 2 and 3 X LSB 8 ^{(u) 2-8} m O ⁽²⁾ , mode 2 and 3 Y LSB 8 ^{(u) 2-8} m O ⁽²⁾ , mode 2 and 3 Z LSB 8 ^{(u) 2-8} m O ⁽²⁾ , mode 2 and 3 X ' 26 m / c O ⁽²⁾ , mode 3 Y ' 26 ^2-12 m / c O ⁽²⁾ , mode 3 Z ' 26 ^2-12 m / c O ⁽²⁾ , mode 3 X '' 19 2 ^-22 m / c ² O ⁽²⁾ , mode 3 Y '' 19 2 ^-22 m / c ² O ⁽²⁾ , mode 3 Z '' 19 2 ^-22 m / c ² O ⁽²⁾ , mode 3 Satellite position accuracy model (once per model) r ₀ 2 ^(u) - meters FROM r ₁ 2 ^(u) 2 ^-18 meters / sec O

Note 1: Either all of these fields must be provided, or none. Note 2: All fields will be presented only if the position information for a specific satellite is given in the ECEF frame, or none of them will be presented if the position information for a specific satellite is given in Kepler parameters. Note u: unsigned parameter

Table 1 shows examples of fields and various modes 1, 2, and 3. The information in Table 1 can be divided into six sections. The first section contains the t _oe _MSB field, which defines the 12 most significant bits (MSB) of the ephemeris t _{oe time} and the reference point for the t _oc synchronization model given in UTC (coordinated universal time). The device R must take into account the possible correction in time of the ephemeris t _oe and the reference point for the synchronization model upon receipt of the navigation model. The t- ephemeris time and the reference point for the t _oc synchronization model have a time interval of about 1.7 weeks.

The second section relates to satellite and format identification. The second section appears once for each mode in the support message A (Fig. 5). The first field of the second section contains the System and Satellite Identification SS_ID. System and Satellite Identification is used to identify various satellites and satellite systems. The System and Satellite Identification SS_ID in this non-limiting example is a 9-bit field divided into two subfields. The first subfield (system ID) contains the satellite system ID number, and the second subfield (SV / Slot ID) contains the satellite index in the system for which navigation data follows. The bit masks for System and Satellite Identification SS_ID in this example are as follows:

System ID (3 bits, value range 0 ... 7)

xxx -----

SV / Slot ID (6 bits, value range 0 ... 63)

--- xxxxxx

In other words, the three most significant bits indicate the satellite system, and the last six bits indicate the satellite.

The specification for the system ID is shown in Table 2.

table 2 System id System ID Value GPS 0 SBAS one Galileo 2 GLONASS 3 QZSS four LAAS 5 Reserved 6 Reserved 7

ID SV / Slot - satellite index in the transmitted navigation model.

The second section field contains the Carrier Frequency Index. This parameter is a GLONASS-specific index of the channel frequency (correspondence between the index of the satellite showing the slot in orbit and the frequency of the navigation signal. This correspondence is included in the GLONASS almanac transmission). For any system other than GLONASS, it is set to 0.

The third field of the second section contains the Match Interval. This field defines the validity period of the navigation model. The range of values for this field is 0.125 - 448 hours. This parameter is determined in accordance with the special representation of the floating point, as defined below in table 3.

Table 3 Index, e (3 bits) Mantissa, m (3 bits) Floating point value, x The value of the interval compliance, F 0 0 0.125 F <0.125 h 0 one 0.25 F = 0.25 h 0 1 <m <8 (m + 1) * 2 ^-3 F = {0.375 h, 0.5 h, 0.625 h, 0.75 h, 0.875 h, 1.0 h} 1 <e <7 0 <= m <8 (m + 1) * 2 ^(e-1) F = hh 7 0 <= m <7 (m + 1) * 2 ^(e-1) F = hh 7 7 512 F = infinitely

The value of the Correspondence Interval 63 (= 2 ⁶ -1) has a special value that defines an unlimited interval for the navigation model of a particular satellite. The fourth field of the second section contains the state of SV. This parameter gives information about the current state of the satellite. Status values are specific to the GNSS system (see, for example, ICD-GPS-200).

The fifth field of the second section contains the Data Edition. The Data Publishing field contains the identification of the navigation model. In the case of, for example, transmitting GPS ephemeris, the 10 least significant bits (LSBs) in the IOD contain the IODC index, as described in GPS-ICD-200. MSB (high bit) IOD is set if the navigation model is not based on any broadcast ephemeris, but is based on a long-term correspondence provided from a source external to the navigation system.

The third section relates to the Satellite Clock Model. The first field of the third section contains t _oс , which gives information about the least significant bits of the time of the origin for the synchronization model. 12 MSBs are included in the t _oe _MSB field in the first section. The second a _f2 , the third a _f1 and the fourth field a _{f0 of the} third section contain coefficients 2, 1 and 0 of the order for the synchronization model.

The fifth field of the third section contains T _G D, which indicates the group delay of the equipment between broadcasts L1 and L2. This parameter is defined for GPS and GLONASS systems.

The fourth section refers to the first mode - the Satellite Navigation Model, using Keplerian parameters.

The navigation model using Kepler parameters is the same as for GPS according to GPS-ICD-200. This parameter set is used in mode 1, i.e. with support data related to GPS and Galileo satellites. An explanation of the model parameters is given in Table 4 below.

Table 4 Parameter Explanation t _oe Ephemeris time See explanation for t _oe _MSB. e Eccentricity (A) ^1/2 The square root of the semimajor axis Mo Mean anomaly Ω ₀ Longitude Longitude i _o Inclination @ t _oe ω The argument of perigee Δn Mid-motion correction

The rate of change in the longitude of the ascending node

Inclination Rate C _us Sinusoidal Latitude Correction C _uc Cosine latitude correction C _rs Sinusoidal Radius Correction C _rc Cosine radius correction C _is Sinusoidal Inclination Correction C _ic Cosine Inclination

, если псевдолиты сохранялись бы в основном стационарными. Кроме того, кеплеровские параметры могут представить положение объекта с точностью только до нескольких см. Однако с псевдолитами необходимо иметь субсантиметровое разрешение (т.е. разрешение менее чем 1 см), чтобы быть в состоянии получить наилучшее возможное навигационное решение. Использование в модели формата, присущего ГЛОНАСС/SBAS, позволяет представить положение передатчика LAAS в плоскости ECEF координат без дополнительных преобразований формата.Keplerian parameters are the original format for GPS and Galileo systems. However, the original format for GLONASS and SBAS is different from the format used by GPS and Galileo. Although it is possible to use the archive data on orbits to convert the GLONASS and SBAS format to the GPS / Galileo-type orbital model, it is useful to include the transmission format of the orbital model inherent to GLONASS and SBAS in the generalized model. This is also useful from the point of view of LAAS, since the representation of a stationary object with Kepler parameters would require the addition of a significant number of bits for the parameters Δn and

if pseudoliths would remain mostly stationary. In addition, Keplerian parameters can represent the position of an object with an accuracy of only a few cm. However, with pseudoliths, it is necessary to have a sub-centimeter resolution (i.e. a resolution of less than 1 cm) in order to be able to get the best possible navigation solution. The use of the GLONASS / SBAS format in the model makes it possible to represent the position of the LAAS transmitter in the ECEF coordinate plane without additional format conversions.

The fifth section refers to the second and third modes, which are satellite navigation models using ECEF Coordinates.

This parameter set is used in mode 2 (i.e. for LAAS) and mode 3 (i.e. for GLONASS and SBAS).

Table 5 Parameter Description Mode t _oe Ephemeris time See description for t _oe _MSB. 2, 3 Xmsb MSB x coordinates in ECEF frame 2, 3 Ymsb MSB y coordinates in ECEF frame 2, 3 Zmsb MSB z coordinates in ECEF frame 2, 3 Xlsb LSB x coordinates in ECEF frame 2, 3 Ylsb LSB y coordinates in ECEF frame 2, 3 ZLSB LSB z coordinates in ECEF frame 2, 3 X ' X-axis velocity in ECEF frame 3 Y ' Y axis speed in ECEF frame 3 Z ' Z axis speed in ECEF frame 3 X '' X-axis acceleration in ECEF frame 3 Y '' Y axis acceleration in ECEF frame 3 Z '' Z axis acceleration in ECEF frame 3

The number of most significant bits (MSB) in the position field is selected to meet the requirements of the GLONASS and SBAS ranges. In addition, the MSB number is also important for representing the QZSS orbits, if required.

The LSB number, on the other hand, represents the resolution requirements established by LAAS (resolution 3.9 millimeters).

The sixth section relates to the Satellite Position Precision Model. It contains two fields. The first field contains the parameter r ₀ , while the second field contains the parameter r ₁ . These parameters can be used to describe the error function of the navigation model in time Error (t) = r ₀ + r ₁ (tt _REFERENCE ).

For GPS, r ₀ is the URA (User Range Accuracy) as described in the GPS-ICD-200 specification.

When it is necessary to transmit a data message supporting navigation system in a communication network, for example, from a network element M to device R, information is placed in one or more messages used in the communication network. For example, in a GSM communication network, there is a specific message delivery method (Radio Resource Location Protocol, RRLP) for transmitting location-related information. This method is defined in 3GPP TS 44.031, which defines a format for GPS support data exchanged between network element M and device R. In this invention, this method can be used to send more general status data to device R.

In the network element M, available navigation information, such as DGPS correction, ephemeris and clock correction and almanac data, is placed in the corresponding message fields of the support data. Ephemeris, clock correction, almanacs and other data related to a particular satellite are obtained from the satellite navigation message of that satellite or from external service X. The message is received by reference receiver C or reference receiver of module X of the external service. The support data message includes a Cipher Control element to indicate whether the information is encrypted or not, the Cipher Serial Number Element, the Data Information Element. The Data Information Element (Data IE) carries navigation information. The item is shown in table 6 below.

The Support Data message is structured to correspond to a fixed message length, not necessarily taking up the entire message. It can contain three data sets: DGPS correction, ephemeris and clock correction, almanacs and other information data. If a fixed message length has fewer information elements than there are bits, then the rest of the message is filled with fill bits. Usually, undefined free bits are not allowed between elements. In the embodiment, the channel for transmitting the Support Data message is, for example, the Control Broadcast Channel (SVCH), over which the SMSCB DRX service is used (SMSCB, Short Message Service Cell Broadcast - short message service broadcast in a cell; DRX - intermittent reception). One SMSCB message has a fixed data length of 82 octets and a maximum length of GPS Support Data of 82 octets. Device R may identify the LCS SMSCB message by the Message Identifier declared in 3GPPTS 23.041.

Table 6 Parameter Bits Resolution Range Units Appearances Availability Cipher control Encryption on / off one - 0-1 - one M Encryption Key Flag one - 0-1 - one M Encryption Serial Number 16 - 0-65535 - one FROM Data 638 - - - - M

5 shows an example of a support message A in accordance with an embodiment of the present invention. The message includes t _oe _MSB, i.e. The 12 most significant bits (MBS) of the ephemeris time t _oe and the start time t _oс given in UTC. This parameter follows the A.2 support data records (ADATA1, ADATA2, ..., ADATAn). Each A.2 support data record contains support data related to two GPS satellites, and the third A message data record may contain support information for one Galileo satellite.

The structure of the support data record A.2 is shown below message A in FIG. 5. Recording support data A.2 includes, for example, recording A.2.1 Satellite and Format Identifications, recording the Synchronization Model A.2.2, recording the Navigation Model A.2.3 and recording the Location Accuracy Model A.2.4. It is also possible to define more or less records for recording support data than these four different records A.2.1, ..., A.2.4.

The structure of the A.2.3 record of the Navigation Model is also shown in FIG. 5 and contains the fields of the third section of table 1, as described in detail above. For example, if the support data for the A.2.3 recording of the Navigation Model contains GPS, Galileo or QZSS data, the circuit shown for Mode 1 in FIG. 5 can be used. Accordingly, if the support data for the A.2.3 record of the Navigation Model contains the data of the LAAS system, the circuit shown for Mode 2 in Fig. 5 can be used, and if the support data for the A.2.3 record of the Navigation Model contains the data of the GLONASS or SBAS system, it can be used the circuit shown for Mode 3 in FIG. 5. It is also possible to use a circuit for Mode 3 with QZSS satellites.

It should be noted that each entry A.2.3 of the Navigation Model in the support message A contains all the fields of the corresponding mode. The choice of mode may be based on the navigation system to which the parameters relate, or another selection criterion may be used to select the mode of transmission of support data, while the selected mode does not necessarily depend on the navigation system.

Next, an example of using a support message format in accordance with the present invention will be described. The network element has an M.4.1 storage area in memory for storing navigation data received from the reference receiver C. If there is no stored data, for example, from the satellites of the first navigation system, the network element controller M.1 generates a request message (not shown) and transmits it in the first communication unit M.2 network element. The transmitter M.2.1 makes a protocol conversion for the message, if necessary, and transmits the message to the reference receiver C of the first navigation system. The receiver C.3.2 of the second communication unit of the first reference receiver C receives the message, does the protocol conversion, if necessary, and transmits the message to the controller C.1 of the reference receiver C. The controller C.1 examines the message and determines that there is a request for transmitting navigation data to the network element M. If the memory C4 contains the requested navigation data, they can be transferred to the network element M, if there is no need to update the navigation data before transmission.

After the navigation data is updated, the reference receiver controller C.1 generates the contents of the navigation data and transfers it to the transmitter C3.1 of the second communication unit of the first reference receiver C. The transmitter C.3.1 transmits, after converting the protocol, if necessary, the navigation data to the network element M. The receiver M2.2 of the network element receives the message, converts the protocol, if necessary, and transmits the message to the controller M.1 of the network element or stores the navigation data received in the message directly actually in the memory of M.4 network element. The memory may contain certain areas (M.4.1, M.4.2 in FIG. 3) for storing navigation data of satellites of various navigation systems. Thus, the data is stored in the area reserved for the navigation system from which the navigation data was obtained.

Support data can be transmitted to device R, for example, on demand or in a broadcast, for example, via the control channel of communication network P. The GSM system determines the format of the broadcast message for GPS support data, which can be used in such broadcasts for GPS. Support data is included in the message using the format defined in the invention. For example, the controller M.1 of the network element M checks which navigation data is stored in the memory of M.4. If, for example, the memory includes navigation data of one or more satellites of the first navigation system and navigation data of one or more satellites of the second navigation system, controller M.1 may construct a support message A in the storage data message area M.4.3 of the support data in the memory M.4, for example, as follows. The controller M.1 extracts the ephemeris time t _oe from the navigation data and stores the 12 most significant bits of the ephemeris time in the first field A.1 of message A.

It should be noted that the definition of time in this support data format is different from the existing GPS time. As noted earlier, for example, GPS time is updated every week. The new definition of time does not. In addition, the method by which time is determined is not essential from the point of view of the invention.

Thus, the controller views the navigation data of the first navigation system stored in the first storage area M.4.1 to form a support data record A.2 (ADATA1). The controller M.1 determines (M.1.2) the type of system and sets (M.1.1) the first three bits of the SS_ID field in the record A.2.1 Identification of the Format and Satellite, respectively. The other 6 bits are set based on the number of satellites the navigation data in question. Other fields of the A.2.1 Identification of the Format and Satellite are accordingly filled in. Record fields A.2.2 of the Synchronization Model are also filled out based on the reference time and the coefficients of the synchronization model. The group delay of the T _GD equipment between L1 and L2 transmissions is filled if the support data refers to GPS or GLONASS satellites. The parameter T _GD may also be needed in other systems.

The use of the records of A.2.3 of the Navigation Model depends on the navigation system, i.e. M1 controller selects one of the available modes - mode 1, mode 2, mode 3, or some other additional mode not mentioned here.

Record A.2.4 Location Accuracy Models is also populated to inform the navigation model error function over time.

If the memory of M.4 contains navigation data of another satellite of the first navigation system, the controller M.1 of the network element generates a second record of support data A.2 (ADATA2), respectively.

When the support data records A.2 are formed from the navigation data stored in all areas of the navigation data storage M.4.1, M.4.2, the support data message may be transmitted to the communication network. The controller M.1 transmits data to the storage data area M.4.3 of the support data message of the second communication unit M.3 of the network element. The transmitter M.3.1 of the second communication unit of the network element M performs the necessary operations to generate signals for transmitting support data and transmits signals to the communication network R.

The signals are received by the receiver R.2.2 of the communication unit of the device R. The receiver R.2.2 demodulates the data of the received signals and, for example, transmits the data to the controller R.1 of the device R. The controller R.1 stores the data in the memory R.4 of the device R and checks (R. 1.1) support data. The check includes determining the mode of each received support data record. The verification may also include the determination (R.1.2) of the navigation system. The mode indication can be transmitted to the positioning receiver R.3, for example, via the output bus R.1.3 of the controller R.1. However, it is also possible that the R.1 controller is also used in positioning operations, it may not be necessary to transmit data (mode and support data) to the R.3 positioning receiver, and the R.1 controller can use the data stored in the R.4 memory .

The R.4 memory may include an R.4.1 storage area for storing navigation data received in support data messages. In some cases, navigation data can also be obtained from satellites by demodulating satellite signals.

When support data is extracted from support data records, it can be stored in memory and used for positioning. For example, when an R.3 positioning receiver can only demodulate signals from one or two satellites, an R.3 positioning receiver can use support data to perform positioning.

The device R may perform positioning at certain intervals or when a predetermined condition is satisfied. A predetermined condition includes, for example, one or more of the following situations: the user makes a call, for example, to the emergency response center, the user selects a positioning operation from the menu of device R, device R and communication network P transfer control to another cell of communication network P, The communication network P sends a positioning request to the device R, etc.

It is also possible that the communication network, for example the network element M, requests the device R to perform positioning. A request may be sent using the RRLP message delivery mechanism. A response can also be sent using the RRLP message delivery mechanism.

When the positioning is completed, the positioning receiver R.3 or the controller R.1 of the device can check whether enough latest data is stored in the memory R.4. If some navigation data is not new (i.e., navigation data has become older than the specified time) or some necessary navigation data is lost, the device can generate and send a request message to the communication network P, for example, to base station B, which transmits a request message to the network element M. The network element M collects the requested navigation data and generates a response message. The response message is then transmitted through the serving base station B to the device R. The receiver R.2.2 of the communication unit R.2 of the device receives and demodulates the response messages to retrieve the navigation data. The navigation data is stored, for example, in the R.4.1 navigation data storage area R.4.

In another embodiment of the present invention, the network element M performs at least one positioning calculation, in this embodiment, the device R assists the network element M by performing, for example, measurements of the carrier phase and transmitting the measurement results to the network element M in the measurement information message ( GNSS measurement information). The network element M also generates support data when receiving navigation data from the reference receiver C, or the network element M receives support data from the support data server X. In addition, the network element M calculates the position of the device R using measurement data and support data. Another possibility is that the position calculation is performed by another server (not shown), while the network element M transmits the measurement results and support data to another server.

In another embodiment, device R performs pseudorange measurements and transmits the measurement results to network element M in a measurement information message (GNSS measurement information). The network element M uses the measurement results and support data generated by the network element M or received from the support data server X. In addition, the network element M calculates the position of the device R using the pseudorange measurement data and the support data, or the network element M transmits the pseudorange measurement data and the support data to another server (not shown) that performs position calculations.

In these above-mentioned embodiments, the measurement information transmitted from the device R to the network element M may depend on the navigation system, but, nevertheless, the principles set forth above can be used to form a general message that is independent of the navigation system.

The essence of the invention is to provide multi-mode functionality. The satellite system (GPS, Galileo, GLONASS, SBAS, LAAS, QZSS or some other), which is indicated in the high bits of the SS index, can determine the mode. However, the mode may also be selected using other factors. This mode then determines the mode of the orbital model and, in certain implementations, also the mode of the synchronization model.

Obviously, the satellite indexing method (i.e., the identification of the navigation model contains system and SV information) is an essential element of the invention. For GLONASS, the Carrier Frequency Index (in addition to the SS index) is necessary.

It is noteworthy that in this embodiment, the synchronization model is common to all modes (and, therefore, to all navigation systems). However, the synchronization model may also change with the mode.

It should be noted that a specific navigation support message contains various sections (namely, t _oe _MSB, correspondence interval, state SV, IOD, t _oc , T _GD , t _oe , r ₀ , r ₁ ), which is, of course, important for for the navigation model to function properly, but it doesn’t matter from the point of view of the invention (these parameters are given in brackets in the table that defines the format). For example, the model's reference time can be given in various ways (at the moment, t _oe _MSB, t _oc and t _oe ), but changing it does not affect multi-mode functionality. As another example, the correspondence interval is defined as a floating-point value (Table 3 above). This is just an example, and the compliance interval can also be determined using other means, taking into account the specific tasks of the system. Parameters that are not important from the point of view of the present invention are given only for completeness.

It should also be emphasized that the actual number of bits and scale factors can be changed if new specifications and explanations appear. Changes in the number of bits and / or scale factors do not change the essence of the invention. For example, adding permission to speed components would not be another invention. As another example, consider an SS ID. The indexing method currently used in the standards is able to distinguish only GPS satellites. The SS ID now offered contains information about the system and the satellite. This pair can be represented in the same field, but it is not necessary (if the system is defined in the same field). Therefore, a simple modification of the fields again does not change the essence of the invention.

The communication network P may be a wireless network, a wired network, or a combination thereof. Some non-limiting examples of communication networks have already been mentioned above, but WLAN and WiMax networks can also be mentioned.

The work of various elements of the system can be mainly carried out using software tools, i.e. element controllers are based on computer microcommands. Of course, some operations or part of them can be hard-coded, that is, implemented in hardware.

Claims (38)

1. The device (R) for positioning, including
a checking element (R.1.1) intended to verify support data,
characterized in that the device (R) also includes
a determining element (R.1.2), designed to determine the mode of the support data in the specified support data, where the specified support data is intended for use by the device to perform positioning of the device (R). 2. The device (R) according to claim 1, characterized in that the support data is received from the communication network (P). 3. The device (R) according to claim 2, characterized in that the communication network (P) is a cellular network. 4. The device (R) according to claim 1, characterized in that the device is a mobile communication device. 5. The device (R) according to claim 1, characterized in that the support data includes an indication of the navigation system to which the support data relates, while the determining element (R.1.2) is intended to verify the indicated indication of the navigation system. 6. The device (R) according to claim 5, characterized in that said indication of the navigation system also includes an indication of the satellite to which the support data relates, while the determining element (R.1.2) is also intended to verify the indicated indication of the satellite. 7. The device (R) according to claim 1 or 6, characterized in that it also includes
a positioning receiver (R.3) for performing positioning based on one or more signals of at least one navigation system; and
a receiver (R.2.2) for receiving support data related to at least one navigation system. 8. The device (R) according to claim 1, characterized in that it comprises a positioning receiver for receiving signals from at least two different navigation systems. 9. A network element (M) for supporting positioning, including
a control element (M.1) for generating support data related to at least one navigation system; and
a transmitting element (M.3.1) for transmitting support data to a communication network (P);
characterized in that the control element (M.1) is designed to select a mode for transmitting support data;
inserts of the navigation system indication into the support data; and
building support data in accordance with the selected mode. 10. The network element (M) according to claim 9, characterized in that the network element (M) also includes
a memory (M.4) for storing navigation data of at least one navigation system; and
a checking element (M.1.2) for checking navigation data to determine which navigation system the navigation data relates to. 11. The network element (M) according to claim 10, characterized in that the control element (M.1) is designed to generate the specified support data based on the navigation data. 12. The network element (M) according to claim 10 or 11, characterized in that it also includes a receiver (M.2.2) for receiving navigation data from at least one satellite navigation system. 13. The network element (M) according to claim 12, characterized in that said navigation data also includes an indication of the satellite to which the navigation data relates, while the determining element (R.1.2) is also intended to insert a satellite indication into the support data. 14. The network element (M) according to claim 10 or 11, characterized in that said navigation data also includes an indication of the satellite to which the navigation data relates, while the determining element (R.1.2) is also intended to insert a satellite indication in the support data . 15. Network element (M) according to any one of claims 9 to 11, characterized in that said support data includes one or more support data records. 16. The network element (M) according to any one of paragraphs.9-11, characterized in that the recording of support data has at least one of the following modes:
Mode 1: ephemeris type GPS / Galileo;
Mode 2: position in ECEF coordinates; or
Mode 3: position, speed and acceleration in ECEF coordinates. 17. The network element (M) according to any one of paragraphs.9-11, characterized in that the communication network (P) is a cellular network. 18. The network element (M) according to clause 16, characterized in that it is a center for mobile switching of the GSM system. 19. A network element (M) according to any one of claims 9 to 11, characterized in that said support data refers to at least one of the following systems:
Global Positioning System
GLONASS system;
Galileo system
Quasi-Zenith Satellite System
satellite based adjustment system (Space Based Augmentation System); or
Local Area Augmentation System 20. Network element (M) according to any one of claims 9 to 11, characterized in that the control element (M.1) is designed to select a mode based on the navigation system to which the support data relates, where the indicated indication of navigation data also indicates the selected mode. 21. A module (R.1) for a positioning receiver, including
a checking element (R.1.1) intended to verify the received support data,
characterized in that the module (R.1) also includes
a determining element (R.1.2) for determining a mode of support data in said support data; and
output for transmitting the indication of the support data mode to the positioning receiver. 22. A method of supporting positioning, including
generating support data related to at least one navigation system, characterized in that the method also includes
determining the navigation system to which the support data relates;
choice of data transfer mode support;
insertion of the indication of the navigation system and the selected mode into the support data; and
building support data in accordance with the selected mode. 23. The method according to p. 22, characterized in that it also includes receiving support data from a third-party service. 24. The method according to item 23, wherein said receipt includes receiving from the reference station (S1, S2) navigation data of at least one satellite navigation system. 25. The method according to any one of paragraphs.22-24, characterized in that it also includes the insertion of a satellite indication in the support data. 26. The method according to any one of paragraphs.22-24, wherein said transmission includes transmitting support data to a communication network (P). 27. The method according to p, characterized in that the communication network is a cellular network. 28. The method according to any one of paragraphs.22-24, characterized in that the construction of data support includes the selection for data support at least one of the following modes:
Mode 1: ephemeris type GPS / Galileo;
Mode 2: position in ECEF coordinates; or
Mode 3: position, speed and acceleration in ECEF coordinates. 29. The method according to any one of paragraphs.22-24, characterized in that the mode is selected based on the navigation system to which the support data relates, while the indicated indication of the navigation data is also used to indicate the selected mode. 30. Machine-readable storage medium for a computer program having computer-executable instructions for
generating support data related to at least one navigation system,
characterized in that the computer program also includes computer-executable instructions for
determining the navigation system to which the support data relates;
selecting a mode for transmitting support data;
inserting the indication of the navigation system and the selected mode into the support data; and
building support data in accordance with the selected mode. 31. The machine-readable tool according to claim 30, wherein the computer program also includes computer-executable instructions for receiving support data from an external service. 32. The machine-readable tool according to p, characterized in that the receipt includes receiving from the reference station (S1, S2) navigation data of at least one satellite navigation system. 33. Machine-readable tool according to any one of paragraphs.30-32, characterized in that the computer program also includes computer-executable instructions for inserting a satellite indication into the support data. 34. Machine-readable tool according to any one of paragraphs.30-32, characterized in that the computer program also includes computer-executable instructions for generating support data records based on the navigation system to which the support data relates. 35. Machine-readable tool according to any one of paragraphs.30-32, characterized in that computer-executable instructions for selecting a mode for transmitting support data include instructions for selecting a mode based on the navigation system to which the support data relates and using said indication of navigation data as indication of the selected mode. 36. The processor-readable recording medium on which a signal is recorded for delivering support data to device (R), including
support data related to at least one navigation system;
characterized in that the signal also includes
an indication of the system to which the support data relates, and a mode selected for transmitting support data, where said support data is constructed in accordance with the selected mode. 37. Server (X) data support, including
a control element (M.1) for generating support data related to at least one navigation system,
characterized in that the control element (M.1) is designed to select a mode for transmitting support data;
inserting the indication of the navigation system and the selected mode into the support data; and
building support data in accordance with the navigation system. 38. The support data server (X) according to claim 37, characterized in that it also includes a receiver (M.2.2) for receiving navigation data from at least one satellite navigation system.

Images