Communication method and communication apparatus

Abstract

The application provides a communication method and a communication device, which can be applied to the field of communication. In the technical scheme, a low-cost GNSS receiver can calibrate a pseudo-range residual mapping relationship of the low-cost GNSS receiver based on measured observation data and observation data of other receivers, so that high-precision tropospheric delay information measurement is finally realized on the low-cost receiver.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to communication methods and communication devices. Background Technology

[0002] In a global navigation satellite system (GNSS), GNSS electromagnetic wave signals are affected by atmospheric refraction when passing through the Earth's atmosphere, resulting in reduced signal propagation speed and path curvature, thus producing tropospheric delay. Because the wet portion of this tropospheric delay is closely related to atmospheric water vapor, atmospheric water vapor can be remotely sensed based on the tropospheric delay to achieve functions such as weather analysis, numerical weather prediction, and verification of satellite water vapor inversion data.

[0003] In the method of obtaining tropospheric delay, it is necessary to establish a precise pointpositioning (PPP) function model, solve the function model, and finally output the tropospheric delay.

[0004] However, the tropospheric delay obtained using the above method currently suffers from insufficient accuracy. Summary of the Invention

[0005] The communication method and communication device provided in this application help improve the accuracy of tropospheric delay determined based on observation data from GNSS receivers.

[0006] In a first aspect, this application provides a communication method, which can be executed by a communication device, or by a chip, chip system, processor, processor system, circuit unit, or circuit system configured for use in a communication device. For ease of description, the following description in this aspect will use a communication device as an example. For ease of description, the communication device executing this method in this application is referred to as the first device.

[0007] This communication method includes: acquiring the measurement error of first GNSS observation data from a first GNSS receiver; determining a first mapping relationship based on the measurement error of the first GNSS observation data, wherein the first mapping relationship is used to acquire the measurement error of second GNSS observation data from the first GNSS receiver.

[0008] For example, GNSS observation data includes raw GNSS observation data such as pseudorange observations, carrier phase observations, signal-to-noise ratio, and Doppler shift from GNSS receivers to GNSS satellites.

[0009] For example, measurement errors include pseudorange residuals.

[0010] In this method, the measurement error is the measurement error of the first GNSS receiver. Therefore, the first mapping relationship obtained based on the measurement error collected by the first GNSS receiver is more compatible with the application scenario of the first GNSS receiver. Thus, the measurement error of the second GNSS observation data can be determined based on the first mapping relationship.

[0011] In one possible design, fourth GNSS observation data from a second GNSS receiver is acquired, the fourth GNSS observation data containing the same type of GNSS observation data as the first GNSS observation data; the measurement error of the first GNSS observation data is determined based on the fourth GNSS observation data.

[0012] For example, GNSS observation data containing the same type can be the same observation object, that is, the fourth GNSS observation data and the first GNSS observation data are observation data of different receivers relative to the same target.

[0013] In this design, the measurement error is determined based on the fourth GNSS observation data collected by the second GNSS receiver. Therefore, if the accuracy of the GNSS observation data collected by the second GNSS receiver is high, the accuracy of the measurement error can be improved, thereby improving the accuracy of the measurement error of the second GNSS observation data obtained based on the measurement error.

[0014] In one possible design, the second GNSS observation data includes the GNSS satellite elevation angle and / or the GNSS satellite signal carrier-to-noise ratio.

[0015] For example, the elevation angle is the observation elevation angle of the GNSS satellite relative to the first receiver. It is the angle between the direction of the line connecting the user and the navigation satellite in the user's local horizontal coordinate system and the horizontal plane. During observation, the GNSS receiver needs to combine locally generated or externally received ephemeris data to obtain the position of each satellite. The elevation angle is calculated by combining the local position of the GNSS receiver with the position of each satellite. The carrier-to-noise ratio (CNR) is the ratio of carrier signal power to noise power spectral density, used to represent the strength of the GNSS satellite signal observed by the receiver.

[0016] In this method, the measurement error of the second GNSS observation data is determined based on the GNSS satellite elevation angle and / or the GNSS satellite signal carrier-to-noise ratio, instead of measuring pseudorange and then obtaining the true distance value or high-precision pseudorange to calculate the measurement error. The measurement error is directly obtained from the GNSS satellite elevation angle and / or the GNSS satellite signal carrier-to-noise ratio, which improves the efficiency of the measurement error calculation process.

[0017] In one possible design, the second GNSS observation data includes the GNSS satellite elevation angle and the GNSS satellite signal carrier-to-noise ratio. The first mapping relationship includes: a second mapping relationship between the GNSS satellite signal carrier-to-noise ratio measured by the first GNSS receiver and the GNSS satellite elevation angle measured by the first GNSS receiver, and a third mapping relationship between the GNSS satellite elevation angle measured by the first GNSS receiver and the measurement error of the first GNSS observation data of the first GNSS receiver.

[0018] For example, determining the second mapping relationship can be done by measuring multiple sets of corresponding elevation angles and carrier-to-noise ratios and fitting the mapping relationship.

[0019] For example, the second mapping relationship could be:

[0020]

[0021] Where CNR is the carrier-to-noise ratio, E is the elevation angle, and p1, p2, and p3 are the parameters of the mapping relationship.

[0022] For example, the third mapping relation could be:

[0023]

[0024] Where σ represents the measurement error, E is the GNSS satellite elevation angle, σ0 is the predefined weight error, and a, b, c, p1, p2, p3 are parameters, also known as weighting parameters.

[0025] This method considers the influence of both elevation angle and carrier-to-noise ratio (CNR) on measurement error and establishes a mapping relationship based on them. Compared to determining the measurement error solely based on elevation angle or CNR, this method increases the stability and anti-interference capability of the mapping relationship. Furthermore, by first establishing a second mapping relationship between CNR and elevation angle, and then determining a third mapping relationship based on the second mapping relationship, the mathematical complexity of fitting the third mapping relationship can be reduced, thereby improving the fitting efficiency.

[0026] In one possible design, third GNSS observation data from a first GNSS receiver is acquired, and the third GNSS observation data contains the same type of GNSS observation data as the second GNSS observation data; a third mapping relationship is determined based on the third GNSS observation data.

[0027] For example, the fact that the third GNSS observation data contains the same type of GNSS observation data as the second GNSS observation data can be understood as the third GNSS observation data containing GNSS satellite elevation angles and / or GNSS satellite signal carrier-to-noise ratios.

[0028] In this design, the GNSS satellite elevation angle and / or GNSS satellite signal carrier-to-noise ratio in the third GNSS observation data correspond one-to-one with the measurement error of the first GNSS observation data. Based on these observation data corresponding to the measurement error, an accurate third mapping relationship can be obtained.

[0029] In one possible design, the first GNSS observation data includes the distance between the first GNSS receiver and the GNSS satellite.

[0030] For example, the distance between the first GNSS receiver and the GNSS satellite is a pseudorange measurement. Because the distance between the GNSS receiver and the GNSS satellite measured by the GNSS receiver usually deviates from the true distance, the distance between the GNSS receiver and the GNSS satellite measured by the GNSS receiver can be called the pseudorange between the GNSS receiver and the GNSS satellite.

[0031] In this method, the first GNSS observation data includes the calculated distance between the first GNSS receiver and the satellite. The calculated distance is obtained by the receiver based on the satellite position in the ephemeris data and the pre-obtained GNSS receiver position.

[0032] Correspondingly, the fourth GNSS observation data also includes the calculated distance between the second GNSS receiver and the satellite. Based on these data, the pseudorange residual in the measurement error of the first GNSS observation data can be determined.

[0033] In one possible design, the first GNSS observation data includes the location information of the first GNSS receiver.

[0034] For example, the location information of the first GNSS receiver includes the coordinates of the first GNSS receiver, or the area where the first GNSS receiver is located.

[0035] In this method, the first GNSS receiver can calculate the distance between the first GNSS receiver and the GNSS satellite based on the location information of the first GNSS receiver and the position of the satellite.

[0036] In one possible design, fifth GNSS observation data from a first GNSS receiver is acquired; the measurement error of the fifth GNSS observation data is determined according to a first mapping relationship, wherein the fifth GNSS observation data and the second GNSS observation data contain the same type of GNSS observation data; and the tropospheric delay is determined based on the measurement error of the fifth GNSS observation data.

[0037] The fifth GNSS observation data contains the same type of GNSS observation data as the second GNSS observation data, which can be understood as the fifth GNSS observation data containing GNSS satellite elevation angle and / or GNSS satellite signal carrier-to-noise ratio.

[0038] For example, the fifth GNSS observation data is the observation data when it is necessary to determine the pseudorange residual at the current time.

[0039] In this method, when it is necessary to measure the tropospheric delay at the current moment, the measurement error at the current moment can be obtained by inputting the fifth GNSS observation data based on the first mapping relationship, and then the tropospheric delay can be determined based on the measurement error.

[0040] In one possible design, the first mapping relationship is sent.

[0041] For example, the first mapping relationship is indicated by sending the weighting parameters of the first mapping relationship.

[0042] In this design, the first mapping relationship is more suitable for use by the first GNSS receiver. When the first mapping relationship is obtained by fitting other devices, sending the first mapping relationship to the first GNSS receiver and / or receivers of the same type as the first GNSS receiver can enable these receivers to perform more accurate tropospheric delay calculations.

[0043] Secondly, this application provides a communication method, which can be executed by a communication device, or by a chip, chip system, processor, processor system, circuit unit, or circuit system configured for use in a communication device. For ease of description, the following content in this aspect will use a communication device as an example. For ease of description, the communication device is referred to as a second device in this application.

[0044] This communication method includes: receiving a first mapping relationship, the first mapping relationship being used to obtain the measurement error of a second GNSS observation data from a first GNSS receiver; obtaining a fifth GNSS observation data from the first GNSS receiver; determining the measurement error of the fifth GNSS observation data based on the first mapping relationship, the fifth GNSS observation data and the second GNSS observation data containing the same type of GNSS observation data; and determining the tropospheric delay based on the measurement error of the fifth GNSS observation data.

[0045] In this method, the communication device acquires a first mapping relationship applicable to the first GNSS receiver and fifth GNSS observation data from the first GNSS receiver, and uses this to determine the measurement error, ultimately determining the tropospheric delay. When the communication device is the first GNSS receiver, the accuracy of the observation error calculation can be improved, correspondingly improving the accuracy of the tropospheric delay.

[0046] In one possible design, the second GNSS observation data includes the GNSS satellite elevation angle and / or the GNSS satellite signal-to-noise ratio.

[0047] In one possible design, the second GNSS observation data includes the GNSS satellite elevation angle and the GNSS satellite signal carrier-to-noise ratio; wherein, the first mapping relationship includes: a second mapping relationship from the GNSS satellite signal carrier-to-noise ratio measured by the first GNSS receiver to the GNSS satellite elevation angle measured by the first GNSS receiver, and a third mapping relationship from the GNSS satellite elevation angle measured by the first GNSS receiver to the measurement error of the first GNSS observation data of the first GNSS receiver.

[0048] In one possible design, third GNSS observation data from the first GNSS receiver is transmitted.

[0049] In this method, the third GNSS observation data is sent to other devices, which then complete the fitting process of the third mapping relationship, thereby reducing the power consumption of the first GNSS receiver.

[0050] In one possible design, the first GNSS observation data from the first GNSS receiver is transmitted before the first mapping is received.

[0051] In this method, sending the first GNSS observation data from the first GNSS receiver to other devices can reduce the power consumption of the first GNSS receiver in determining observation errors.

[0052] In one possible design, the first GNSS observation data includes the distance between the first GNSS receiver and the GNSS satellite.

[0053] Thirdly, this application provides a communication device. This communication device can execute modules corresponding to the methods / operations / steps / actions described in the first aspect or any possible implementation thereof. These modules can be hardware circuits, software, or a combination of hardware circuits and software.

[0054] In one design, the device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the first aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the first aspect or any possible implementation thereof.

[0055] In one design, the device may be a first device, or a device, module, circuit or chip configured in the first device, or a device that can be used in conjunction with the first device.

[0056] Fourthly, this application provides a communication device. This communication device may include modules corresponding to the methods / operations / steps / actions described in the second aspect or any possible implementation thereof.

[0057] In one design, the device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the second aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the second aspect or any possible implementation thereof.

[0058] In one design, the device can be a second device, or a device, module, circuit, or chip configured in the second device, or a device that can be used in conjunction with the second device.

[0059] Fifthly, an apparatus is provided, including a processor, wherein instructions, when executed by the processor, cause a method as described in the first aspect or any possible implementation thereof to be implemented.

[0060] Optionally, the device may further include a storage medium that stores the instructions executed by the processor.

[0061] A sixth aspect provides an apparatus including a processor, wherein instructions, when executed by the processor, cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0062] Optionally, the device may further include a storage medium that stores the instructions executed by the processor.

[0063] In a seventh aspect, a chip is provided, including processing circuitry for running a program or instructions to cause the methods described in the first aspect or any possible implementation thereof to be implemented.

[0064] Optionally, the chip may further include a memory for storing programs or instructions.

[0065] Optionally, the chip may also include the transceiver circuit, or an input / output interface.

[0066] Eighthly, a chip is provided, including processing circuitry for running a program or instructions to implement a method as described in the second aspect or any possible implementation thereof.

[0067] Optionally, the chip may further include a memory for storing programs or instructions.

[0068] Optionally, the chip may also include the transceiver circuit, or an input / output interface.

[0069] A ninth aspect provides a computer-readable storage medium comprising instructions that, when executed by a processor, cause the method as described in the first aspect or any possible implementation thereof to be implemented.

[0070] In a tenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium including instructions that, when executed by a processor, cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0071] Eleventhly, a computer program product is provided, the computer program product including computer program code or instructions, which, when the computer program code or instructions are run, cause the method as described in the first aspect or any possible implementation thereof to be implemented.

[0072] In a twelfth aspect, a computer program product is provided, the computer program product comprising computer program code or instructions that, when the computer program code or instructions are executed, cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0073] In a thirteenth aspect, a communication system is provided, comprising: means for performing the first aspect or any possible implementation thereof, and means for performing the second aspect or any possible implementation thereof.

[0074] It is understood that the technical effects of any of the third to thirteenth aspects of this application can be referred to the relevant content in the first and second aspects, and will not be repeated here. Attached Figure Description

[0075] Figure 1 This is a schematic diagram of a system architecture according to an embodiment of this application;

[0076] Figure 2 This is a flowchart of a method for determining weighting parameters according to an embodiment of this application;

[0077] Figure 3 This is a schematic diagram illustrating a data transmission direction according to an embodiment of this application;

[0078] Figure 4 This is a schematic diagram illustrating another data transmission direction according to an embodiment of this application;

[0079] Figure 5 This is a schematic diagram of a wireless transmission process according to an embodiment of this application;

[0080] Figure 6This is a schematic diagram of a data transmission process via a control plane RRC connection according to an embodiment of this application;

[0081] Figure 7 This is a schematic diagram illustrating a process of transmitting data via a user plane data service connection according to an embodiment of this application;

[0082] Figure 8 This is a schematic diagram illustrating a data transmission process via the NG interface according to an embodiment of this application;

[0083] Figure 9 This is a schematic diagram illustrating a data transmission process via the Xn interface according to an embodiment of this application;

[0084] Figure 10 This is a schematic diagram of a device deployment method according to an embodiment of this application;

[0085] Figure 11 This is a schematic diagram of another device deployment method according to an embodiment of this application;

[0086] Figure 12 This is a schematic diagram of another device deployment method according to an embodiment of this application;

[0087] Figure 13 This is a schematic diagram of another device deployment method according to an embodiment of this application;

[0088] Figure 14 This is a schematic diagram of another device deployment method according to an embodiment of this application;

[0089] Figure 15 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0090] Figure 16 This is a schematic diagram of the structure of another communication device according to an embodiment of this application. Detailed Implementation

[0091] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0092] In the description of the embodiments of this application, unless otherwise stated, "a plurality of" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0093] In the description of the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0094] In the description of the embodiments of this application, the terms "information", "signal", "message", "channel", and "signaling" may sometimes be used interchangeably. It should be noted that when their distinctions are not emphasized, their intended meanings are matched.

[0095] In the description of the embodiments of this application, the terms "of", "corresponding (relevant)" and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are matched.

[0096] In the description of the embodiments of this application, the order of the process numbers does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0097] In the description of the embodiments of this application, "preset," "predefined," or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminals and wireless access network devices), or by being pre-defined in a protocol. This application does not limit the specific implementation method. "Stored" can refer to storing in one or more memories. The one or more memories can be separate settings or integrated into an encoder or decoder, processor, or communication device. The one or more memories can also be partially separate settings and partially integrated into a decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0098] In the description of the embodiments of this application, "protocol" may refer to standard protocols in the field of communications, such as 3GPP LTE protocols (such as technical specification (TS) 36, i.e., the TS36 series of technical specifications), new radio (NR) protocols (such as the TS38 series of technical specifications), and related protocols applied to future communication systems. This application does not limit this.

[0099] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation.

[0100] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0101] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0102] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0103] The method provided in this application embodiment can be used in various communication systems, such as 3rd generation partnership project (3GPP) communication systems, for example, long-term evolution (LTE) systems, 5th generation mobile communication technology (5G) systems, such as 5G NR communication systems, or various future communication systems and future communication networks.

[0104] The method provided in this application can be applied to terrestrial network communication systems as well as non-terrestrial network (NTN) communication systems. The NTN system can be an NTN system integrated with 4G, 5G, or any future communication system, such as NR NTN, IoT NTN, etc. NT and N communication systems can be, for example, satellite communication systems, and can also include unmanned aerial vehicles (UAVs), high-altitude platform stations (HAPS), and other aerial access network equipment; this application does not limit this.

[0105] The methods provided in this application can also be applied to Internet of Things (IoT) systems, vehicle-to-everything (V2X) systems, device-to-device (D2D) communication systems, machine-to-machine (M2M) communication systems, or other similar future-oriented systems, such as future communication systems. This application does not specifically limit these applications. Furthermore, the terms "system" and "network" are interchangeable.

[0106] Figure 1 This is a schematic diagram of a system architecture according to an embodiment of this application. Figure 1 The system shown includes network devices and core network elements. Network devices establish connections with each other via Xn interfaces; network devices establish connections with core network elements via NG interfaces.

[0107] One example of a core network element is the access and mobility management function (AMF) element.

[0108] In some scenarios, servers are deployed within the core network elements. In some implementations, these servers can also be referred to as central computer rooms.

[0109] In some implementations, the network device that sends data is called a data sending device, the network device that relays data is called a relay network device, and the network device that ultimately receives data is called a data receiving device.

[0110] The network device in this application embodiment can be a device for communicating with a terminal device. This network device can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), radio unit (RU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device performing base station functions in D2D, V2X, and M2M communications, a network-side device in future networks, or a device performing base station functions in future communication systems. A base station can support networks using the same or different access technologies. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). The embodiments of this application do not limit the specific technologies or equipment forms used in the network equipment.

[0111] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0112] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, DU, or CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes. For example, the network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0113] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or RUs. CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, AAUs, or RRHs.

[0114] RAN nodes can support one or more types of fronthaul interfaces, each corresponding to a DU and RU with different functions. If the fronthaul interface between the DU and RU is a common public radio interface (CPRI), the DU is configured to implement one or more baseband functions, and the RU is configured to implement one or more radio frequency functions. If the fronthaul interface between the DU and RU is another type of interface, relative to CPRI, some downlink and / or uplink baseband functions, such as, for downlink, precoding, digital beamforming (BF), or one or more of inverse fast Fourier transform (IFFT) / cyclic prefix addition (CP), are moved from the DU to the RU; and for uplink, digital beamforming (BF), or one or more of fast Fourier transform (FFT) / cyclic prefix removal (CP), are moved from the DU to the RU. In one possible implementation, the interface can be an enhanced common public radio interface (eCPRI). Under the eCPRI architecture, the segmentation between DU and RU differs, corresponding to different categories (Cat) of eCPRI, such as eCPRI Cat A, B, C, D, E, and F.

[0115] Taking eCPRI Cat A as an example, for downlink transmission, the DU is configured to implement one or more functions before and after layer mapping (i.e., coding, rate matching, scrambling, modulation, and layer mapping), while other functions after layer mapping (e.g., resource element (RE) mapping, digital beamforming (BF), or one or more functions of inverse fast Fourier transform (IFFT) / adding cyclic prefix (CP)) are moved to the RU. For uplink transmission, the DU is configured to implement one or more functions before and after de-mapping (i.e., decoding, rate matching de-mapping, descrambling, demodulation, inverse discrete Fourier transform (IDFT), channel equalization, and de-RE mapping), while other functions after de-mapping (e.g., digital BF or one or more functions of fast Fourier transform (FFT) / removing CP) are moved to the RU. It is understandable that the functional descriptions of the DU and RU corresponding to various types of eCPRI can be found in the eCPRI protocol, and will not be elaborated here.

[0116] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0117] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0118] In this embodiment, the apparatus for implementing the functions of a network device can be a network device itself; it can also be an apparatus capable of supporting the network device in implementing those functions, such as a chip system, hardware circuit, software module, or a hardware circuit plus a software module. This apparatus can be installed in the network device or used in conjunction with the network device. In this embodiment, the example of a network device being used to implement the functions of a network device is provided only and does not constitute a limitation on the solutions described in this embodiment.

[0119] Network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network device is located. Furthermore, a network device can be a hardware device, a software function running on dedicated hardware, or a software function running on general-purpose hardware, such as a virtualization function instantiated on a platform (e.g., a cloud platform), or an entity that includes dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the network device.

[0120] GNSS receivers can be deployed in network equipment to measure signals transmitted by GNSS satellites and obtain GNSS observation data. For example, GNSS observation data includes pseudorange observations, carrier phase observations, Doppler delay, and carrier-to-noise ratio measured by the GNSS receiver at each observation epoch. The pseudorange observation value is the distance from the GNSS satellite to the GNSS receiver as measured by the GNSS receiver. Because signals are subject to environmental interference during transmission, including atmospheric delay and multipath errors, the measured value may not equal the true value; therefore, it is called a pseudorange observation value, or simply pseudorange.

[0121] For example, GNSS receivers include high-precision GNSS receivers and / or low-cost GNSS receivers. High-precision GNSS receivers provide GNSS observation data with higher accuracy, closer to the true value; low-cost GNSS receivers use low-power chips and antennas, resulting in lower accuracy of the GNSS observation data. It is understandable that different types of low-cost GNSS receivers may produce GNSS observation data with varying accuracy.

[0122] In some scenarios, different network devices can deploy different GNSS receivers. For example, some network devices deploy high-precision GNSS receivers, while others deploy low-cost GNSS receivers. Among network devices deploying low-cost GNSS receivers, different types of low-cost GNSS receivers can be deployed.

[0123] Because GNSS signals are affected by atmospheric refraction when passing through the Earth's atmosphere, resulting in reduced signal propagation speed and path curvature, a tropospheric delay (ZTD) occurs. The wet component of the tropospheric delay is closely related to atmospheric water vapor; therefore, tropospheric delay can be determined using GNSS observation data obtained from GNSS signal measurements, enabling remote sensing of atmospheric water vapor.

[0124] Precise point positioning (PPP) is a technique for determining tropospheric delay based on GNSS observation data. The PPP technique is described below.

[0125] Starting from the basic GNSS observation equations, different PPP function models can be constructed. Taking the ionospheric-free combined model as an example, in the dual-frequency case, assuming the two frequencies are i and j, the ionospheric-free combined observation values ​​of pseudorange and phase are... and It can be represented as:

[0126]

[0127] in, t represents the geometric distance from the phase center of the satellite antenna to the phase center of the receiving antenna. r and t s It is the receiver and satellite clock bias, m W This represents the wet tropospheric delay at the zenith and the corresponding projection function (where the dry delay part of the tropospheric delay ZTD has been corrected in the observations), b r,IF and The combined hardware delay of the receiver and satellite end in the pseudorange-ionosphere-free combination. B r,IF and The receiver and satellite delays and corresponding combination ambiguities for carrier phase-to-ionospheric combinations. and For observation noise and multipath effects in pseudorange and phase ionosphere-free combined observations, λ IF The wavelength of the phase observation value without ionosphere.

[0128] When using the Kalman filter method for PPP solution, the Kalman filter system includes two processes: state update and observation update. The state update equation describes the dynamic relationship between state vectors of adjacent epochs:

[0129] X k =Φ k,k11 X k-1 +W k

[0130] Among them, X i The state vector of epoch i, where i is a positive integer, Φ k,k-1 W is the transition matrix from the previous epoch k-1 to the current epoch k. k This represents dynamic noise. The observation equation then describes the relationship between the current epoch state vector and the observed values:

[0131] L k =H k X k +Δ k

[0132] Among them, L k H is the observation vector. k To design the matrix, Δ k This represents the observation error.

[0133] In an ionospherically unintegrated PPP (Position-Based Utilization) architecture, the state vector includes location coordinates, receiver clock bias, tropospheric delay, and carrier phase ambiguity. The epoch-by-epoch estimate of the state vector can be expressed as:

[0134]

[0135] In the formula and These are the predicted values ​​of the state vector and their variance-covariance matrix, respectively. and These are the state vector estimates and their variance-covariance matrices, K and K, respectively. k R is the filter gain. k To measure the noise variance matrix. Based on the prior accuracy σ0 and the weighting method f wt Measure the noise variance matrix R k It can be represented as:

[0136]

[0137] As mentioned above, when obtaining tropospheric time delay based on GNSS observation data acquired by a GNSS receiver, it is necessary to perform a weighted calculation on the prior accuracy σ0 of the GNSS observation data to obtain the GNSS observation data measurement error σ, and then calculate the measurement noise R of the GNSS observation data. Finally, the tropospheric time delay can be obtained based on this measurement noise and the GNSS observation data. For the sake of convenience in the following description, the weighting method f used to weight the prior accuracy σ0 will be described. wt This is called the mapping relationship for GNSS observation data measurement errors, or simply the measurement error mapping relationship. From another perspective, the measurement error mapping relationship is used to determine the measurement errors of GNSS observation data based on prior accuracy; simply put: the measurement error mapping relationship is used to determine the measurement errors of GNSS observation data.

[0138] In some implementations, a mapping is used between the prior accuracy and the GNSS satellite elevation angle measured by the GNSS receiver to obtain the mapping relationship of the GNSS satellite elevation angle measurement error, which characterizes the mapping relationship of the GNSS observation data measurement error. In other words, the GNSS satellite elevation angle is used to characterize the GNSS observation data measurement error.

[0139] It is understood that in this application, the GNSS satellite elevation angle measured by the GNSS receiver is obtained by the GNSS receiver combining locally generated or externally received ephemeris data or data contained in the GNSS satellite signal to obtain the position of each satellite, and then calculating the elevation angle of each satellite by combining the local position of the GNSS receiver with the position of each satellite.

[0140] In some implementations, a mapping between prior accuracy and GNSS signal carrier-to-noise ratio measured by the GNSS receiver is used to obtain a mapping relationship of GNSS satellite signal carrier-to-noise ratio measurement error, which characterizes the mapping relationship of GNSS observation data measurement error. In other words, the GNSS satellite signal carrier-to-noise ratio is used to characterize the GNSS observation data measurement error.

[0141] It is understood that in this application, the carrier-to-noise ratio of GNSS satellite signals measured by the GNSS receiver refers to the carrier-to-noise ratio of the GNSS receiver based on the detected signals from the GNSS satellite.

[0142] Currently, the mapping relationship for GNSS observation data measurement errors configured in GNSS receivers is usually based on GNSS observation data acquired by the GNSS receiver in a fixed and favorable environment. In other words, this mapping relationship characterizes the measurement error of GNSS observation data acquired by the GNSS receiver in a favorable environment. However, the application environment of GNSS receivers is often complex and variable, even harsh. Therefore, this mapping relationship may no longer be applicable to characterizing the measurement error of GNSS observation data acquired by the GNSS receiver in such scenarios. In other words, the deviation between the measurement error obtained based on this mapping relationship and the actual measurement error of the GNSS observation data acquired by the GNSS receiver in such scenarios will be significant, leading to insufficient accuracy of the tropospheric time delay obtained by the GNSS receiver.

[0143] In some implementations, the mapping relationship of GNSS observation data measurement errors is obtained based on GNSS observation data acquired by a high-precision GNSS receiver. That is, this mapping relationship characterizes the mapping relationship of measurement errors in the GNSS observation data acquired by the high-precision GNSS receiver. However, this mapping relationship is not well-suited for low-cost GNSS receivers, and it can also lead to insufficient accuracy in tropospheric delay obtained by low-cost GNSS receivers.

[0144] To address at least one of the aforementioned problems, this application provides a new technical solution. In some of the technical solutions provided in this application, the measurement error of the first GNSS observation data from a first GNSS receiver is obtained; this measurement error is used as the reference measurement error of the observation data from the first GNSS receiver, and a mapping relationship between the measurement errors of the third GNSS observation data and the first GNSS observation data is determined in conjunction with the third GNSS observation data from the first GNSS receiver; based on this mapping relationship and the fifth GNSS observation data from the first GNSS receiver, the measurement error of the fifth GNSS observation data is determined; the measurement error of the fifth GNSS observation data is used as the current GNSS observation data measurement error of the first GNSS receiver, and the tropospheric delay is obtained based on the current GNSS observation data from the first GNSS receiver.

[0145] The second and third GNSS observation data contain the same type of GNSS observation data, such as GNSS satellite elevation angle and GNSS satellite signal carrier-to-noise ratio.

[0146] The first GNSS observation data and the second GNSS observation data are usually not the same type of GNSS observation data. For example, the first GNSS observation data includes the distance between the first GNSS receiver and the GNSS satellite, while the second GNSS observation data includes the GNSS satellite elevation angle or the GNSS satellite signal carrier-to-noise ratio.

[0147] Because the distance between a GNSS receiver and a GNSS satellite measured by the receiver usually deviates from the actual distance, the distance between the receiver and the GNSS satellite measured by the receiver can be called the pseudorange between the GNSS receiver and the GNSS satellite.

[0148] In this application, the difference between pseudoranges can be referred to as pseudorange single difference.

[0149] In this technical solution, since the mapping relationship is determined based on the measurement error of the first GNSS observation data collected by the first GNSS receiver, the mapping relationship is better adapted to the scene where the first GNSS receiver is located. This can improve the accuracy of the GNSS observation data measurement error obtained by mapping the third GNSS observation data collected by the first GNSS receiver using the mapping relationship, and thus improve the accuracy of the tropospheric delay obtained by the first GNSS receiver based on the measurement error.

[0150] Optionally, when obtaining the measurement error of the first GNSS observation data of the first GNSS receiver, the measurement error can be determined by combining the first GNSS observation data collected by the first GNSS receiver itself and the fourth GNSS observation data collected by the second GNSS receiver.

[0151] The first and fourth GNSS observation data contain the same type of GNSS observation data, such as pseudorange.

[0152] In this implementation, the accuracy of the measurement error of the first GNSS observation data is improved by referring to the accuracy of the fourth GNSS observation data collected by the second GNSS receiver. This helps to improve the accuracy of the tropospheric delay obtained by the first GNSS receiver by utilizing the high accuracy of the GNSS observation data collected by the second GNSS receiver.

[0153] For example, if the first GNSS receiver is a low-cost receiver and the second GNSS receiver is a high-precision receiver, the high accuracy of the GNSS observation data acquired by the high-precision receiver can help improve the accuracy of the measurement error of the first GNSS observation data, thereby helping to improve the accuracy of the mapping relationship, which in turn improves the accuracy of the measurement error of the third GNSS observation data, and ultimately improves the accuracy of the tropospheric time delay.

[0154] Optionally, both the second and third GNSS observation data include the GNSS satellite elevation angle and the GNSS satellite signal-to-noise ratio, thus taking into account the measurement errors caused by both the GNSS satellite elevation angle and the GNSS satellite signal-to-noise ratio. This can further improve the accuracy of the measurement error, thereby further improving the accuracy of the tropospheric time delay.

[0155] When the first GNSS observation data includes pseudorange, since there is no absolute functional relationship between the GNSS satellite signal carrier-to-noise ratio (CNR) and the GNSS satellite elevation angle and the pseudorange residual, fitting the GNSS satellite signal carrier-to-noise ratio and the GNSS satellite elevation angle may not yield a very accurate mapping relationship. Therefore, the GNSS satellite signal carrier-to-noise ratio in the mapping relationship between the GNSS satellite signal carrier-to-noise ratio and the GNSS satellite elevation angle and the pseudorange residual can be replaced by the mapping relationship between the GNSS satellite signal carrier-to-noise ratio and the GNSS satellite elevation angle and the pseudorange residual. This simplifies the mapping relationship between the GNSS satellite signal carrier-to-noise ratio and the GNSS satellite elevation angle and the pseudorange residual to a mapping relationship between the GNSS satellite elevation angle and the pseudorange residual.

[0156] The following example illustrates the technical solution of this application, using a first GNSS receiver as a low-cost GNSS receiver and a second GNSS receiver as a high-precision GNSS receiver. The first GNSS observation data includes the pseudorange between the first GNSS receiver and the GNSS satellite, while the second and third GNSS observation data both include the GNSS satellite elevation angle and the GNSS satellite signal carrier-to-noise ratio.

[0157] In some implementations, such as Figure 2 As shown, the parameters in the PPP function model of a low-cost GNSS receiver are determined using GNSS observation data from a high-precision GNSS receiver, including the following steps:

[0158] Step 1: Obtain pseudorange from the observation data of a high-precision GNSS receiver.

[0159] Step 2: Obtain pseudorange from the observation data of a low-cost GNSS receiver.

[0160] Step 3: Calculate the pseudorange residual based on the pseudorange of the high-precision GNSS receiver and the pseudorange of the low-cost receiver.

[0161] As an example, the pseudorange single-difference equation can be written as:

[0162] ΔP rb =Δρ rb +cΔδtr+ΔM rb +Δξ p

[0163] Wherein, ΔP rb Δρ represents the pseudorange difference, which is the difference between the pseudorange measured by a low-cost GNSS receiver and the pseudorange measured by a high-precision GNSS receiver; rb This represents the difference between the calculated distance between a low-cost GNSS receiver and a GNSS satellite and the calculated distance between a high-precision GNSS receiver and a GNSS satellite; c is the speed of light in vacuum; Δδtr is the receiver clock bias, referring to the difference between the GNSS receiver's clock and the satellite's standard time; cΔδtr is the system bias; ΔM rb For multipath error, Δξ p This is pseudorange noise.

[0164] Based on the above equation, if the high-precision coordinates of both high-precision and low-cost GNSS receivers are obtained through GNSS measurements, ΔP can be calculated. rb -Δρ rb The difference can be used to obtain the error term cΔδtr+ΔM. rb +Δξ p cΔδtr is a system bias, and its value can be obtained through parameter estimation. Based on the method described here, ΔM can be obtained. rb +Δξ p and ΔM rb +Δξ p The result is taken as the pseudo-range residual σ.

[0165] Step 4: Based on the GNSS satellite elevation angle and the carrier-to-noise ratio (CNR) of the GNSS satellite signal from the low-cost GNSS receiver, fit the mapping relationship between the GNSS satellite elevation angle and the GNSS satellite signal CNR. An example relationship is shown below:

[0166]

[0167] Where a, b, and c are the fitting parameters, CNR is the carrier-to-noise ratio, E is the elevation angle, and σ is the pseudorange residual.

[0168] The simplified mapping expression between CNR and elevation angle is as follows:

[0169]

[0170] Where a, b, and c are fitting parameters, CNR is the carrier-to-noise ratio, E is the elevation angle, σ is the pseudorange residual, and f(E) is the fitting function of elevation angle and CNR or the mapping relationship between elevation angle and CNR.

[0171] Considering the data characteristics, the following logarithmic function scheme is used in this invention to fit the two:

[0172]

[0173] Where f(E) is the fitting function of elevation angle and CNR or the mapping relationship between elevation angle and CNR, p1, p2, p3 are fitting parameters, and E is the elevation angle.

[0174] Step 5: Perform pseudorange residual-elevation angle fitting.

[0175] After obtaining the functional relationship between CNR and elevation angle, the following function can be obtained by fitting the pseudorange residual and elevation angle:

[0176]

[0177] Where σ represents the measurement error, E is the GNSS satellite elevation angle, σ0 is the prior accuracy, and a, b, c, p1, p2, and p3 are parameters.

[0178] In this application, for the sake of convenience of description, Figure 2 The above steps, or a process that performs similar functions, are called the fitting process. The mapping relationship between the measurement error of the GNSS observation data obtained by fitting is called the fitting result.

[0179] The fitting process in this application can be performed by a server, a high-precision GNSS receiver, or a low-cost GNSS receiver. The fitting process performed by a high-precision GNSS receiver can also be understood as the fitting process being performed by a network device containing a high-precision GNSS receiver; similarly, the fitting process performed by a low-cost GNSS receiver can also be understood as the fitting process being performed by a network device containing a low-cost GNSS receiver.

[0180] Step 6: Output the mapping relationship of GNSS observation data measurement error.

[0181] In some implementations, this mapping relationship can be called a fusion weighting strategy.

[0182] Step 7: Obtain tropospheric delay using a low-cost GNSS receiver based on the mapping relationship of measurement errors from GNSS observation data.

[0183] For example, after a low-cost GNSS receiver measures the real-time satellite elevation angle, it inputs the data into the fusion weighting strategy to calculate the GNSS observation data measurement error corresponding to the current elevation angle. Then, by calculating the real-time tropospheric delay data according to the Kalman filtering method mentioned above, the tropospheric delay data can be obtained.

[0184] The following describes the data transmission direction in the technical solution provided in this application. Figure 3 and Figure 4 These are some schematic diagrams illustrating the data transmission direction of this application.

[0185] like Figure 3 As shown, network devices transmit data to the server, and the server also transmits data to the network devices. For example, in a scenario where the server performs the fitting process, the network device sends GNSS observation data to the server, and the server sends the fitting results to the network device. In another example where the network device performs the fitting process, GNSS observation data and fitting results between network devices are forwarded through the server.

[0186] For example, network device 1 is equipped with a low-cost receiver, and network device 2 is equipped with a high-precision receiver. Network device 1 sends pseudorange observations, satellite elevation angle and satellite carrier-to-noise ratio observation data, and network device 2 sends high-precision pseudorange. The server receives the above data and determines the fitting result according to the aforementioned fitting process, and sends the fitting result back to network device 1.

[0187] For example, network device 1 is equipped with a low-cost receiver, and network device 2 is equipped with a high-precision receiver. Network device 1 sends pseudorange observations, satellite elevation angle and satellite carrier-to-noise ratio observation data, and network device 2 sends high-precision pseudorange. The server forwards the data to network device 3. Network device 3 receives the above data and determines the fitting result according to the aforementioned fitting process, and sends the fitting result back to network device 1.

[0188] like Figure 4 As shown, data is transmitted between network devices. For example, in a scenario where a network device performs the fitting process, the data sending network device directly or through a relay network device sends GNSS observation data to the data receiving network device, and the data receiving network device directly or through a relay network device sends the fitting result back to the data sending network device. In another example where a network device performs the fitting process, the data sending network device directly or through a relay network device sends GNSS observation data to the data receiving device, and the data receiving network device obtains the fitting result based on the GNSS observation data.

[0189] For example, the data transmission network device is a base station equipped with a low-cost receiver, and the data receiving network is a base station equipped with a high-precision receiver. The data transmission network device transmits pseudorange observations, satellite elevation angle, and satellite carrier-to-noise ratio observation data, which are transmitted to the data receiving network device through relay network device 1 and relay network device 2, etc. After the data receiving network device determines the fitting result according to the aforementioned fitting process, the base station equipped with the high-precision receiver, acting as the data transmission network device, relays the fitting result back to the base station equipped with the low-cost receiver, which is acting as the data receiving network device, through relay network device 1 and relay network device 2, etc.

[0190] It is understandable that communication between network devices, as well as communication between network devices and servers, can use a variety of communication methods and message formats, including wireless transmission and / or wired transmission.

[0191] When network devices communicate wirelessly, in some implementations, this wireless transmission can be achieved through wireless backhaul. Wireless backhaul (WB / integrated access and backhaul, IAB): This involves establishing a backhaul link and transmitting data via the NR wireless interface, using an access procedure similar to that of a UE, and including additional backhaul functionality.

[0192] When network devices communicate wirelessly, in some implementations, this wireless transmission can be achieved through a broadcast channel. Figure 5 This is a schematic diagram of a wireless transmission process according to an embodiment of this application. The method is executed by network device A and network device B, and includes steps S501 to S503.

[0193] S501, Network Device B performs base station search and selection.

[0194] S502, network device A sends master information block (MIB) information, and correspondingly, network device B obtains the corresponding scheduling information of system information block (SIB) 1 through the MIB.

[0195] The MIB information defines the most basic system messages of the cell and the parameters required to decode SIB1. SIB1 carries key parameters such as cell selection parameters and / or access control parameters.

[0196] In some implementations, the SIB1 information also indicates other SIB information, such as newly added SIB-X information and newly added SIB-Y information.

[0197] S503, network device A sends SIB1 instruction SIB-X / Y scheduling information. The corresponding network device B receives the SIB-X / Y scheduling information.

[0198] Optionally, this method also includes S504.

[0199] S504, Network device A periodically transmits SIB-X, which carries the raw GNSS data or weighting parameters corresponding to network device A. Correspondingly, network device B receives the SIB-X.

[0200] Optionally, this method also includes S505 and S506.

[0201] S505, Network device B sends an SIB-Y information request. The corresponding network device A receives the SIB-Y information request.

[0202] S506, Network Device A sends SIB-Y as needed based on the information request. SIB-Y carries the raw GNSS data or weighting parameters corresponding to Network Device A. Correspondingly, Network Device B receives SIB-Y.

[0203] When network devices communicate wirelessly, in some implementations, this wireless transmission can be achieved through a control plane RRC connection. Figure 6 This is a schematic diagram illustrating a data transmission process via a control plane RRC connection according to an embodiment of this application. The method is executed by network device A and network device B, and includes steps S601 to S603.

[0204] S601, Network device B performs base station search and selection.

[0205] S602, Network device B sends a random access request. Corresponding network device A receives the random access request.

[0206] S603, Network device A sends a random access response. The corresponding network device B receives the random access response.

[0207] Optionally, this method also includes S604.

[0208] S604, Network device A sends auxiliary information, which carries the raw GNSS data or weighting parameters corresponding to network device A.

[0209] Optionally, this method also includes S605 to S607.

[0210] S605, Network Device B sends an RRC connection request. Correspondingly, Network Device A receives the RRC connection request.

[0211] S606, Network device A sends an RRC connection response. Correspondingly, Network device B receives the RRC connection response.

[0212] Among them, the RRC connection response network device A corresponds to the raw GNSS data or weighting parameters.

[0213] S607, Network Device B indicates that an RRC connection has been established. Correspondingly, Network Device A confirms that the RRC connection has been established.

[0214] When network devices communicate wirelessly, in some implementations, this wireless transmission can be achieved through a user plane data service connection. Figure 7 This is a schematic diagram illustrating a process for transmitting data via a user plane data service connection according to an embodiment of this application. This method is executed by network device A, network device B, and the core network, including steps S701 to S710.

[0215] S701, Network Device A uploads its corresponding raw GNSS data or weighting parameters. Correspondingly, the core network receives the raw GNSS data or weighting parameters.

[0216] S702, Network Device B performs base station search and selection.

[0217] S703, Network Device B sends a random access request. Correspondingly, Network Device A receives the random access request.

[0218] S704, Network device A sends a random access response. Correspondingly, Network device B receives the random access response.

[0219] S705, network device B sends an RRC connection request. Correspondingly, network device A receives the RRC connection request.

[0220] S706, Network Device A sends an RRC connection response. Correspondingly, Network Device B receives the RRC connection response.

[0221] S707, Network Device B indicates that an RRC connection has been established. Correspondingly, Network Device A confirms that the RRC connection has been established.

[0222] S708, establishes an initial context between network device A, network device B and the core network.

[0223] S709, Network Device B sends NAS information to carry an information request, and the corresponding core network receives the NAS information.

[0224] In the S710, the core network sends NAS information based on an information request, carrying raw GNSS data or weighting parameters. Correspondingly, network device B receives the NAS information.

[0225] When network devices and servers communicate via wired transmission, in some implementations, this wired transmission can be achieved through the NG interface. The definition of the NG interface can be found in 3GPP TS 38.413, Sections 8.7.3, 9.4.4, and 9.4.5.

[0226] In some implementations, new NG interface field definitions need to be added to carry GNSS observation data fields or weighting parameter fields. The new fields are shown below:

[0227]

[0228] Extended-AMFName is a newly added interface field, and its format definition is as follows:

[0229]

[0230] The newly added fields are used to carry GNSS observation data fields or weighting parameter fields.

[0231] In some implementations, the following fields are added to the NG interface field definitions:

[0232]

[0233] The AMFConfigurationUpdateAcknowledgeIEs field is a newly added interface field, and its format definition is as follows:

[0234]

[0235]

[0236] The newly added field is used to carry the accumulated GNSS observation data exchanged between the base station and the server.

[0237] Figure 8 This is a schematic diagram illustrating a process for transmitting data via an NG interface, as described in an embodiment of this application. This process is executed by network devices and the core network, including steps S801 and S802.

[0238] S801: The network device sends an AMF configuration update. Correspondingly, the core network receives the AMF configuration update.

[0239] S802, the core network sends an AMF configuration update confirmation. Correspondingly, the network devices receive the configuration update confirmation.

[0240] When network devices communicate via wired transmission, in some implementations, this wired transmission can be achieved through the Xn interface. The definition of the Xn interface can be found in 3GPP TS 38.423 Section 8.4.13, Section 8.4.14, Section 9.3.4, and Section 9.3.5.

[0241] In some implementations, new Xn interface field definitions need to be added to carry GNSS observation data fields or weighting parameter fields. The new fields are shown below:

[0242] DataCollectionUpdate-IEs XNAP-PROTOCOL-IES::={

[0243] {ID id-NodeAssociatedInfoResult CRITICALITY ignore TYPE NodeAssociatedInfoResultPRESENCE optional},

[0244] The NodeAssociatedInfoResult field is a newly added interface field, and its definition format is as follows:

[0245]

[0246] The newly added fields are used to carry GNSS observation data fields or weighting parameter fields.

[0247] Figure 9 This is a schematic diagram illustrating a data transmission process via the Xn interface according to an embodiment of this application. The method is executed by network device A and network device B, and includes steps S901, S902, and S903.

[0248] S901, Network device A sends a data collection request. Correspondingly, Network device B receives the data collection request.

[0249] S902, Network Device B sends a data collection response. Correspondingly, Network Device A receives the data collection response.

[0250] S903, Network Device B sends a data collection update. Correspondingly, Network Device A receives the data collection update.

[0251] like Figure 10 This application provides a schematic diagram of a device deployment method according to an embodiment. In this deployment method, a base station equipped with a high-precision receiver transmits measured GNSS observation data to base stations equipped with different types of low-cost receivers that require calibration of the pseudorange residual mapping formula. For example, a base station equipped with a type A low-cost GNSS receiver and a base station equipped with a type B low-cost GNSS receiver. The base station equipped with the low-cost receiver fits the parameters of the pseudorange residual mapping formula based on the high-precision GNSS observation data and the low-cost receiver's GNSS observation data. It then calibrates its own pseudorange residual mapping formula according to the fitted weighting parameters and calculates tropospheric delay information based on the new pseudorange residual mapping formula.

[0252] like Figure 11 This application provides another schematic diagram of a device deployment method. In this deployment method, a base station equipped with a high-precision GNSS receiver relays the measured observation data from a base station equipped with a low-cost receiver to a target base station equipped with a low-cost receiver. For example, the data is relayed from a base station equipped with a type A low-cost GNSS receiver to a target base station equipped with a type B low-cost GNSS receiver. The base station equipped with the low-cost receiver fits the parameters of the pseudorange residual mapping formula based on the high-precision GNSS observation data and the low-cost receiver's GNSS observation data. It then calibrates its own pseudorange residual mapping formula according to the fitted weighting parameters and calculates the tropospheric delay information based on the new pseudorange residual mapping formula.

[0253] like Figure 12This application provides another schematic diagram of a device deployment method. In this deployment method, a high-precision receiver and several low-cost receivers of different models that require calibration of the pseudorange residual mapping formula, such as a base station equipped with a low-cost GNSS receiver of model A and a base station equipped with a low-cost GNSS receiver of model B, send GNSS observation data to a server. The service area then fits the parameters of the pseudorange residual mapping formula based on the high-precision GNSS observation data and the GNSS observation data from the low-cost receivers. After fitting, the server sends weighting parameters to the corresponding low-cost receiver base station. The base station equipped with the low-cost receiver calibrates its own pseudorange residual mapping formula according to the weighting parameters and calculates tropospheric delay information based on the new pseudorange residual mapping formula.

[0254] like Figure 13 This application provides another schematic diagram of a device deployment method. In this deployment method, different types of low-cost receivers that require calibration of the pseudorange residual mapping formula are used. For example, a base station equipped with a low-cost GNSS receiver of type A and a base station equipped with a low-cost GNSS receiver of type B send GNSS observation data to a base station equipped with a high-precision receiver. The base station equipped with the high-precision receiver fits the parameters of the pseudorange residual mapping formula based on the high-precision GNSS observation data and the GNSS observation data from the low-cost receiver. After fitting, the base station equipped with the high-precision receiver sends weighting parameters to the corresponding low-cost receiver base station. The base station equipped with the low-cost receiver calibrates its own pseudorange residual mapping formula according to the weighting parameters and calculates tropospheric delay information based on the new pseudorange residual mapping formula.

[0255] like Figure 14 This application also presents a schematic diagram of a device deployment method. In this deployment method, not all base stations equipped with low-cost receivers directly establish connections with base stations equipped with high-precision receivers. Instead, GNSS observation data is relayed from other base stations equipped with low-cost receivers to base stations equipped with high-precision receivers. For example, data is relayed from a base station equipped with a type A low-cost GNSS receiver to a base station equipped with a high-precision GNSS receiver. After the base station equipped with a high-precision GNSS receiver completes the mapping formula fitting, it relays the weighting parameters from the base station equipped with a low-cost receiver to the base station equipped with a low-cost receiver corresponding to the weighting parameters. The base station equipped with a low-cost receiver calibrates its own pseudorange residual mapping formula according to the weighting parameters and calculates tropospheric delay information based on the new pseudorange residual mapping formula.

[0256] Figure 15 This is a schematic diagram of the structure of a communication device according to an embodiment of this application. Figure 15 As shown, the communication device 1500 may include a processing module 1510 and a communication module 1520.

[0257] As a first example, the communication device 1500 can be used to implement Figures 5 to 9 The embodiment shown illustrates a communication method implemented by a first device. For example, processing module 1510 is used to implement... Figures 5 to 9 The embodiments shown depict processing steps performed by network devices or the core network, with the communication module 1520 used to implement them. Figures 5 to 9 The embodiments shown depict steps such as sending and / or receiving performed by network devices or the core network.

[0258] As an example, when the communication device 1500 is used to implement the functions implemented by the network device or the core network in any of the above method embodiments, the communication module 1520 is used to: acquire the measurement error of the first GNSS observation data of the first GNSS receiver.

[0259] The communication module 1520 is also used to acquire the first GNSS observation data.

[0260] The communication module 1520 is also used to acquire fourth GNSS observation data from the second GNSS receiver.

[0261] The communication module 1520 is also used to acquire third GNSS observation data from the first GNSS receiver.

[0262] The communication module 1520 is also used to acquire the fifth GNSS observation data from the first GNSS receiver.

[0263] Communication module 1520 is also used to send the first mapping relationship.

[0264] For example, when the communication device 1500 is used to implement the function implemented by the network device in any of the above method embodiments, the processing module 1510 is used to: determine a first mapping relationship based on the measurement error of the first GNSS observation data, the first mapping relationship being used to obtain the measurement error of the second GNSS observation data of the first GNSS receiver.

[0265] The processing module 1510 is also used to determine the measurement error of the first GNSS observation data based on the fourth GNSS observation data.

[0266] Processing module 1510 is also used to determine a third mapping relationship based on third GNSS observation data.

[0267] The processing module 1510 is also used to determine the measurement error of the fifth GNSS observation data according to the first mapping relationship, wherein the fifth GNSS observation data and the second GNSS observation data contain the same type of GNSS observation data.

[0268] Figure 16 This is a schematic diagram of the structure of a communication device according to another embodiment of this application, which can be used to implement this application. Figure 5and Figures 7 to 9 The communication method shown is as follows. Figure 16 As shown, the communication device 1600 includes a processor 1610 and a communication circuit 1620. The processor 1610 and the communication circuit 1620 are coupled to each other. It is understood that the communication circuit 1620 can be a transceiver or an input / output interface.

[0269] Optionally, the communication device 1600 may further include a memory 1630 for storing instructions executed by the processor 1610, or storing input data required by the processor 1610 to execute instructions, or storing data generated after the processor 1610 executes instructions. It is understood that the memory 1630 may be located externally to the processor 1610, or internally to the processor 1610.

[0270] As an example, processor 1610 is used to implement the functions of the processing module 1510 described above, and communication circuit 1620 is used to implement the functions of the communication module 1520 described above.

[0271] The communication device 1600 can be a second device or a chip used in a second device.

[0272] It is understandable that when the communication device 1600 is a second device, the communication circuit 1620 can be a transceiver. When the communication device 1600 is a chip, the communication circuit 1620 can be an input / output interface.

[0273] The communication device 1600 may be the first device or a chip used in the first device.

[0274] It is understandable that when the communication device 1600 is the first device, the communication circuit 1620 can be a transceiver. When the communication device 1600 is a chip, the communication circuit 1620 can be an input / output interface.

[0275] In some embodiments of this application, a computer program product is also provided. When the computer program product is run on a processor, it can implement the method implemented by the second device in any of the above embodiments, or it can implement the method implemented by the first device in any of the above method embodiments.

[0276] In some embodiments of this application, a computer-readable storage medium is also provided, which contains computer instructions that, when executed on a processor, can implement the method implemented by the second device in any of the above embodiments, or can implement the method implemented by the first device in any of the above method embodiments.

[0277] In some embodiments of this application, a communication system is also provided, which can implement the methods implemented by the second device and the first device in any of the above embodiments.

[0278] It is understood that the processor in the embodiments of this application may be any of the following devices or all or part of the circuitry used for processing functions: a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0279] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device or terminal device. Alternatively, the processor and storage medium can exist as discrete components in the network device or terminal device.

[0280] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive.

[0281] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0282] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, The method includes: Measurement error in acquiring the first GNSS observation data from the first global navigation satellite system GNSS receiver; A first mapping relationship is determined based on the measurement error of the first GNSS observation data, and the first mapping relationship is used to obtain the measurement error of the second GNSS observation data of the first GNSS receiver.

2. The method according to claim 1, characterized in that, The measurement error in acquiring the first GNSS observation data from the first GNSS receiver includes: Acquire the first GNSS observation data; Acquire fourth GNSS observation data from a second GNSS receiver, wherein the fourth GNSS observation data contains the same type of GNSS observation data as the first GNSS observation data; The measurement error of the first GNSS observation data is determined based on the fourth GNSS observation data.

3. The method according to claim 1 or 2, characterized in that, The second GNSS observation data includes GNSS satellite elevation angle and / or GNSS satellite signal carrier-to-noise ratio.

4. The method according to claim 3, characterized in that, The second GNSS observation data includes GNSS satellite elevation angles and GNSS satellite signal carrier-to-noise ratio; The first mapping relationship includes: a second mapping relationship between the GNSS satellite signal carrier-to-noise ratio measured by the first GNSS receiver and the GNSS satellite elevation angle measured by the first GNSS receiver, and a third mapping relationship between the GNSS satellite elevation angle measured by the first GNSS receiver and the measurement error of the first GNSS observation data of the first GNSS receiver.

5. The method according to claim 4, characterized in that, The method further includes: Acquire third GNSS observation data from the first GNSS receiver, wherein the third GNSS observation data and the second GNSS observation data contain the same type of GNSS observation data; The third mapping relationship is determined based on the third GNSS observation data.

6. The method according to any one of claims 1 to 5, characterized in that, The first GNSS observation data includes the distance between the first GNSS receiver and the GNSS satellite.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Acquire the fifth GNSS observation data from the first GNSS receiver; The measurement error of the fifth GNSS observation data is determined based on the first mapping relationship, wherein the fifth GNSS observation data and the second GNSS observation data contain the same type of GNSS observation data; The tropospheric delay is determined based on the measurement error of the fifth GNSS observation data.

8. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Send the first mapping relationship.

9. A communication method, characterized in that, include: Receive a first mapping relationship, which is used to obtain the measurement error of the second GNSS observation data of the first global navigation satellite system GNSS receiver; Acquire the fifth GNSS observation data from the first GNSS receiver; The measurement error of the fifth GNSS observation data is determined based on the first mapping relationship, wherein the fifth GNSS observation data and the second GNSS observation data contain the same type of GNSS observation data; The tropospheric delay is determined based on the measurement error of the fifth GNSS observation data.

10. The method according to claim 9, characterized in that, The second GNSS observation data includes GNSS satellite elevation angle and / or GNSS satellite signal carrier-to-noise ratio.

11. The method according to claim 10, characterized in that, The second GNSS observation data includes GNSS satellite elevation angles and GNSS satellite signal carrier-to-noise ratio; The first mapping relationship includes: a second mapping relationship between the GNSS satellite signal carrier-to-noise ratio measured by the first GNSS receiver and the GNSS satellite elevation angle measured by the first GNSS receiver, and a third mapping relationship between the GNSS satellite elevation angle measured by the first GNSS receiver and the measurement error of the first GNSS observation data of the first GNSS receiver.

12. The method according to claim 11, characterized in that, The method further includes: Transmit the third GNSS observation data from the first GNSS receiver.

13. The method according to any one of claims 9 to 12, characterized in that, Before receiving the first mapping relationship, the method further includes: Transmit the first GNSS observation data from the first GNSS receiver.

14. The method according to claim 13, characterized in that, The first GNSS observation data includes the distance between the first GNSS receiver and the GNSS satellite.

15. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1-8, or includes a module for performing the method as described in any one of claims 9-14.

16. A communication device, characterized in that, The communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1-8, or to cause the communication device to perform the method as described in any one of claims 9-14.

17. A communication system, characterized in that, The communication system includes a first device and a second device; The first device is used to perform the method as described in any one of claims 1-8, and the second device is used to perform the method as described in any one of claims 9-14.

18. A chip or chip system, characterized in that, The chip or chip system includes a processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the method as described in any one of claims 1-8 to be performed, or cause the method as described in any one of claims 9-14 to be performed.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method described in any one of claims 1-8 to be performed, or cause the method described in any one of claims 9-14 to be performed.

20. A computer program product, characterized in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, they cause the method of any one of claims 1-8 to be performed, or cause the method of any one of claims 9-14 to be performed.

Images