CN109696867A

CN109696867A - Method, user terminal and the GNSS device management system of user terminal processes GNSS device data

Info

Publication number: CN109696867A
Application number: CN201811604317.0A
Authority: CN
Inventors: 王勇; 颜琼; 邹文超
Original assignee: Shanghai Sinan Satellite Navigation Technology Co Ltd
Current assignee: Shanghai Sinan Satellite Navigation Technology Co Ltd
Priority date: 2018-12-26
Filing date: 2018-12-26
Publication date: 2019-04-30

Abstract

The present invention discloses the method and GNSS device management system of user terminal processes GNSS device data.Described method includes following steps: the user terminal sends data requesting instructions to Cloud Server；The Cloud Server forwards the data requesting instructions to corresponding GNSS device；The GNSS device responds described instruction and sends initial data to the Cloud Server；The Cloud Server forwards the initial data to corresponding user terminal；The management of the application software on GNSS device is realized to GNSS device and run on to initial data described in the user terminal processes to obtain processing result.Method and system of the invention can mitigate the processing pressure of Cloud Server.

Description

Method for processing GNSS (global navigation satellite system) equipment data by user terminal, user terminal and GNSS equipment management system

Technical Field

The present invention relates to the field of GNSS data processing, and in particular, to a method for processing GNSS data by a user terminal and a GNSS device management system.

Background

In the existing cloud service system processing mode, a plurality of user terminals and a plurality of controlled terminals are connected to a server. The process of controlling a controlled terminal by a user terminal is as follows: and the control terminal sends a request to the controlled terminal through the cloud server. And the controlled terminal sends the original data to the server after responding to the request. And the server processes the original data and then sends the processing result to the control terminal.

In the cloud service system, the number of the controlled terminals and the number of the control terminals connected to the cloud server are large, and the processing pressure of the cloud server is increased by processing the original data of the controlled terminals by the cloud server to obtain the processing result.

Disclosure of Invention

The problem to be solved by the invention is that the data processing pressure of a cloud server in a data processing system of GNSS equipment is large.

In order to solve the above problem, the present invention provides a method for a user terminal to process GNSS device data. The method comprises the following steps: the user terminal sends a data request instruction to a cloud server; the cloud server transmits the data request instruction to the corresponding GNSS device; the GNSS device responds to the instruction to send raw data to the cloud server; the cloud server forwards the original data to a corresponding user terminal; and the user terminal processes the original data to obtain a processing result, so that the GNSS equipment and the application software installed on the GNSS equipment are managed.

In a further aspect, the sending, by the user terminal, the data request instruction to the cloud server includes: after receiving the data request instruction sent by the user, the sub-page calls a parent page data request method, the data request instruction is sent out by using the data request method, and the address of the data processing object of the current sub-page is also stored; the processing of the raw data by the user terminal to obtain a processing result comprises: analyzing the received original data to obtain an analysis result, finding the data processing object of the sub-page by the father page through the address of the data processing object of the sub-page, returning the analysis result to the data processing method of the sub-page, and processing the analysis result by the data processing object of the sub-page by using the data processing method and displaying the processing result on the sub-page.

In a further aspect, the sending, by the user terminal, the data request instruction to the cloud server includes: after receiving the data request instruction, the sub-page inquires whether continuous first original data which is not closed exists, and if so, the first original data is not received any more; if the data processing object does not exist, the child page calls a parent page data request method, the data request method is used for sending the data request instruction outwards, and the address of the data processing object of the current child page is stored.

In a further scheme, the processing of the original data by the user terminal to obtain a processing result comprises pre-storing contents to be analyzed, judging that the received original data is the same as the contents to be analyzed, and if the received original data is the same as the contents to be analyzed, analyzing the original data and processing the analysis result to obtain a processing result; if not, the received raw data is not parsed.

In a further aspect, the cloud server forwards the data request command to the corresponding GNSS device according to a mapping relationship between the user terminal and the GNSS device.

In a further scheme, each GNSS device is connected to the cloud server in a TCP/IP manner, and each user terminal is connected to the cloud server in a WebSocket manner.

In a further aspect, the step of establishing the mapping relationship between the user terminal and the GNSS device is as follows: the method for establishing the mapping relationship between the GNSS device and the TCP identifier TCPID and the TCP Client of the TCP Client comprises the following steps: the GNSS device is connected with a cloud server as a TCP client, the cloud server sends a command requiring the GNSS device to send a device identifier to the cloud server at a certain frequency, meanwhile, the cloud server obtains a TCP identifier TCPID and defines a data structure for storing and analyzing the device identifier of the GNSS device, and a mapping relation between the TCPID and the data structure is established; the cloud server stores the received data from the GNSS equipment in the data structure according to the mapping relation between the TCPID and the data structure and analyzes the data in the data structure until the equipment identifier is obtained, after the equipment identifier is obtained, the mapping MAP < SN, TCP Client > between the GNSS equipment and the TCP Client is established, and the mapping relation MAP < TCPID, SN > between the TCP identifier TCPID and the GNSS equipment is also established; the step of establishing the mapping relationship between the user terminal and the Websocket ID and the Websocket Client comprises the following steps: the user terminal accesses the cloud server in a Websocket mode, establishes mapping Map < user, Websocket Client > between the user terminal and the Websocket Client, and also establishes mapping relation Map < user, Websocket ID > between the user terminal and the Websocket ID; the step of establishing the mapping relationship between the user terminal and the GNSS device comprises the following steps: the instruction sent by the GNSS device to the server comprises a user identifier of the user terminal, or the instruction sent by the user terminal to the cloud server comprises a device identifier, and the cloud server establishes a mapping relation between the user terminal and the GNSS device according to the user identifier and the device identifier.

In a further scheme, the cloud server detects the online state of the GNSS device, and removes mapping relations MAP < SN, TCP Client and MAP < TCPID, SN > under the condition that the GNSS device is not online.

In another aspect of the present invention, a user terminal is provided for processing raw data from a GNSS device. The user terminal sends a data request instruction outwards, receives original data forwarded by a cloud server, processes the original data to obtain a processing result so as to realize management of GNSS equipment and application software installed in the GNSS equipment, wherein the original data is sent to the cloud server by the GNSS equipment in response to the data request instruction.

In a further scheme, the user terminal comprises a request module, a receiving module, an analysis module, a callback module and a storage module, wherein after the request module receives the data request instruction sent by a user, the request module calls a father page data request method and sends the data request instruction outwards by using the data request method, and the address of the data processing object of the current sub-page is also stored in the storage module; the receiving module receives raw data from the GNSS device; the analysis module analyzes the original data to obtain an analysis result, and transmits the analysis result to the callback module; the callback module finds the data processing object of the sub-page through the address of the stored data processing object of the sub-page, and recalls the analysis result to the data processing method of the sub-page, and the data processing object of the sub-page processes the analysis result by using the data processing method of the sub-page and displays the processing result on the sub-page.

In a further scheme, the user terminal comprises a request closing module, and the request module sends a query instruction to the request closing module after receiving the data request instruction; the request closing module inquires whether continuous first original data which is not closed exists after receiving the inquiry instruction, and if so, the continuous first original data stored by the closing module is traversed; generating a trigger signal if there is no persistent first raw data that is not turned off; the request module is triggered by the trigger signal to send the data request instruction outwards and store the data processing object of the sub-page.

In a further scheme, the user terminal comprises a judging module, the storage module stores contents to be analyzed, the judging module judges that the received original data is the same as the contents to be analyzed, and if the received original data is the same as the contents to be analyzed, a judging signal is transmitted to the analyzing module; the analysis module analyzes the received original data according to the judgment signal; if not, the received raw data is not parsed.

The invention also discloses a GNSS device management system. The system is used for processing data from GNSS equipment and comprises a cloud server and at least one user terminal, wherein the user terminal is any one of the user terminals.

In a further scheme, under the condition that the GNSS device has a wireless internet access function, the GNSS device is connected to the cloud server in a wireless manner; or, under the condition that the GNSS device does not have the wireless internet function, the GNSS device is connected to a third-party device in a wired or bluetooth manner, and is connected to the cloud server through an operating system of the third-party device, data transfer software installed in the third-party device, or an APP installed in the third-party device.

In a further aspect, the cloud server transmits the raw data to the corresponding user terminal according to a mapping relationship between the GNSS device and the user terminal, where the mapping relationship is established by the following steps: the method for establishing the mapping relationship between the GNSS device and the TCP identifier TCPID and the TCP Client of the TCP Client comprises the following steps: the GNSS device is connected with a cloud server as a TCP client, the cloud server sends a command requiring the GNSS device to send a device identifier to the cloud server at a certain frequency, meanwhile, the cloud server obtains a TCP identifier TCPID and defines a data structure for storing and analyzing the device identifier of the GNSS device, and a mapping relation between the TCPID and the data structure is established; the cloud server stores the received data from the GNSS equipment in the data structure according to the mapping relation between the TCPID and the data structure and analyzes the data in the data structure until the equipment identifier is obtained, after the equipment identifier is obtained, the mapping MAP < SN, TCP Client > between the GNSS equipment and the TCP Client is established, and the mapping relation MAP < TCPID, SN > between the TCP identifier TCPID and the GNSS equipment is also established; the step of establishing the mapping relationship between the user terminal and the Websocket ID and the Websocket Client comprises the following steps: the user terminal accesses the cloud server in a Websocket mode, establishes mapping Map < user, Websocket Client > between the user terminal and the Websocket Client, and also establishes mapping relation Map < user, Websocket ID > between the user terminal and the Websocket ID; the step of establishing the mapping relationship between the user terminal and the GNSS device comprises the following steps: the instruction sent by the GNSS device to the server comprises a user identifier of the user terminal, or the instruction sent by the user terminal to the cloud server comprises a device identifier, and the cloud server establishes a mapping relation between the user terminal and the GNSS device according to the user identifier and the device identifier.

Compared with the prior art, the invention has at least the following advantages:

1. in the process, the user terminal sends the data request instruction to the cloud server, the cloud server forwards the instruction to the GNSS device according to the mapping relation between the user terminal and the GNSS device, then the cloud server forwards the original data of the GNSS device responding to the instruction to the user terminal, and the user terminal processes the original data to obtain a processing result.

2. Because the analysis time is set on the user terminal, the user terminal analyzes the received original data only when the time reaches the analysis time, or the frequency for receiving the original data is set on the user terminal, and the user terminal analyzes the original data after receiving the original data sent to the user terminal by the cloud server according to the frequency, the purpose that the user terminal analyzes the received original data only when needed is achieved, and data processing is not performed in real time for a long time is achieved, so that the pressure of the user terminal for processing the data is reduced on the premise that the processing pressure of the server is reduced.

3. The user terminal stores the content to be analyzed in advance, judges whether the received original data is the same as the content to be analyzed, analyzes the content under the same condition, and does not analyze the received original data if the received original data is not the same as the content to be analyzed.

4. Since the GNSS device is selected as the specific GNSS device, the data request instruction includes the device identifier of the specific device, and thus, the user terminal sends the data request instruction to the specific GNSS device (for example, sends the data request instruction to the specific GNSS device through the cloud server based on the mapping relationship), the GNSS device related to the unsolicited request does not send raw data to the cloud server, and the cloud server does not process the raw data sent by the GNSS device not requested, so that the data processing pressure of the GNSS device and the user terminal is reduced on the premise of ensuring that the processing pressure of the cloud server is small.

Drawings

Fig. 1 is a schematic diagram of a user terminal and a GNSS device connected to a cloud server;

FIG. 2 is a flow chart illustrating data transmission between a user equipment and a GNSS device in accordance with the present invention;

FIG. 3 is a flow chart of a user terminal receiving and processing data in accordance with the present invention;

fig. 4 shows that the user terminal acquires various functions of the device center after connecting to the cloud server according to the present invention;

FIG. 5 is sub-functions of satellite information for the equipment center of FIG. 4;

FIG. 6 is a flow chart of a user terminal processing satellite information in accordance with the present invention;

FIG. 7 is a flow chart of a user terminal implementing real-time monitoring according to the present invention;

fig. 8 is a schematic diagram of a user terminal before sending a data request command;

fig. 9 is a functional block diagram of a user terminal of the present invention.

Detailed Description

For the purpose of illustrating the technical content, the constructional features, the achieved objects and the effects of the invention in detail, reference will be made to the following detailed description of the embodiments in conjunction with the accompanying drawings.

Referring to fig. 1 and 2, a GNSS device management system of the present invention is configured to manage at least one GNSS device 1. The GNSS device 1 may be a phonebook 1a, a GNSS receiver 1b, or other terminals (e.g., in-vehicle terminals 1c) that can achieve high-precision positioning, or the like. The product expression form of the high-precision positioning terminal is a tablet personal computer, a smart phone and the like, and corresponding functions are realized by installing different application software, for example, after the SinoFarm software of the southwestern navigation company of the applicant is installed, the terminal is used for controlling a tractor in precision agriculture to realize operations such as seeding, fertilizing, ploughing and the like; after the piling software is installed, the terminal is used for piling and controlling a piling point, a piling depth and the like; after the deformation monitoring software is installed, the deformation monitoring can be realized for large buildings such as bridges, and landslide monitoring can be realized for dams, coal mines, and the like. The GNSS device management system includes a cloud server 2 and a user terminal 3. Since there are at least 1 GNSS device 1, and there are at least 1 user terminal 3 to manage the GNSS devices 1, it is possible to realize that one user terminal 3 manages one GNSS device 1 and that one user terminal 3 manages a plurality of GNSS devices 1.

Referring to fig. 1, the manner in which the GNSS device is connected to the cloud server is described as follows: the GNSS device comprises a device with a wireless connection function and a device without the wireless connection function. The GNSS device 1 with the wireless connection function establishes full-duplex communication connection with the cloud server 2 through a wireless network. The GNSS device 1 without the wireless connection function may connect to the cloud server 2 in 2 ways: 1) under the condition that the GNSS device 1 has the Bluetooth function, the third party device with the internet surfing function can be connected through Bluetooth and then connected to the cloud server 2 through the third party device, so that the networking of the GNSS device 1 is realized; 2) under the condition that the GNSS device does not have the bluetooth function, the GNSS device 1 is connected to a third party device in a wired manner (for example, RS232), and then the third party device is connected to the cloud server 2. The specific way of connecting to the server through the third-party device may be, for example, as follows: 1) the server can be connected through the self-contained application software of the system of the third-party equipment; 2) the third-party equipment is provided with data transfer software and is connected to the server through the data transfer software. The data relay software is, for example, APP, or executable program under Windows or Linux system or relay software without operating system. Each GNSS device is connected to the cloud server 2 by a TCP method, and a skilled person can understand that each GNSS device 1 may also be connected to the cloud server 2 by other methods, for example, UDP, etc.

With continued reference to fig. 1, the manner in which the user terminal 3 is connected to the cloud server 2 is described as follows: the user terminal 3 may be a mobile terminal such as a PC, a tablet computer, and a smartphone. Any terminal can access the cloud server through a browser of the terminal, and also can access the cloud server through an application program (such as APP or plug-in) installed in the user terminal, for example: in the case where the user terminal 3 is a PC, accessing the cloud server through a browser of the PC; when the user terminal is a mobile terminal (such as a smart phone/tablet computer), the cloud server is accessed through a browser built in the mobile terminal, and when corresponding application software (such as a surfeymaster) is installed on the user terminal, the cloud server can also be accessed through the application software (APP). In the present embodiment, each user terminal 3 is connected to the cloud server 2 in a Websocket manner, and those skilled in the art can understand that the user terminal 3 may also be connected to the cloud server 2 in other manners, such as UDP or TCP.

With continuing reference to fig. 1 and fig. 2, in an embodiment, the cloud server 2 implements data communication between the user terminal 3 and the GNSS device 1 based on a mapping relationship, where the mapping relationship is established as follows:

a) establishing a mapping relation between the GNSS device 1 and the TCP identifiers TCPID and TCP Client, and comprising the following steps: the GNSS device 1 is connected to the cloud server 2 as a TCP client, the cloud server 2 obtains the connection, sends an instruction for requiring the GNSS device 1 to send a unique device identifier to the cloud server 2 at a certain frequency to the GNSS device 1, obtains a TCP identifier TCPID and creates a data structure for analyzing and storing the device identifier, for example, the data structure is defined as a DataParser, and a mapping relation Map < TCPID, DataParser > between the TCPID and the data structure is established. The cloud server 2 stores the received raw data from the GNSS device 1 in the data structure dataserver according to the mapping Map < TCPID, dataserver > and parses the data in the dataserver until the device identifier is obtained. After the device identifier is obtained, the cloud server 2 sends an instruction for closing sending of the device identifier to the GNSS device 1, and meanwhile, a mapping MAP < SN, TCPClient > between the GNSS device and the TCP client is established, and a mapping relationship MAP < TCPID, SN > between the TCP identifier TCPID and the GNSS device is also established. The mapping relation < TCPID, SN > can be used to know that the GNSS device is offline, because the GNSS device without the mapping relation is the offline GNSS device.

b) Establishing a mapping relation between a Websocket client and a Websocket ID of the user terminal 3 and the cloud server 2, and comprising the following steps of: after the User terminal establishes connection with the cloud server in a Websocket manner, the cloud server obtains a unique User identifier User of the User terminal, for example, the User identifier is a User name for logging in the User terminal. The user identifier may be any one of the methods as long as the user identifier uniquely identifies the user terminal. Then, a mapping MAP < User, WebSocket Client > between the User terminal and WebSocketclient is established, the cloud server sends a message to the corresponding User terminal through the mapping relation for the User to check, and meanwhile, the cloud server establishes a mapping relation MAP < WebSocketID, User > between the User terminal and WebSocketID. Which User terminal/User is offline can be known through the mapping relation < WebSocketID, User >, because the User terminal without the mapping relation is the offline GNSS device.

c) Establishing a mapping relationship between the GNSS device 1 and the user terminal 3 according to a request instruction of the GNSS device 1 or the user terminal 3, including the following steps: after the GNSS device 1 and the User terminal 3 are connected to the cloud server 2, under the condition that the GNSS device sends an instruction to the User terminal, the instruction comprises a User identifier of the User terminal, and then according to the mapping relation between the User terminal and the Websocket ID and the Websocket Client, the cloud server 2 can establish the mapping relation < User, SN > between the GNSS device and the User terminal; under the condition that the User terminal sends an instruction to the GNSS device, the instruction comprises a device identifier, and after the cloud server analyzes the device identifier, the mapping relation between the GNSS device and the TCPID and the TCP Client is combined to establish a mapping relation MAP < User, SN > between the GNSS device 1 and the User terminal 3. After the mapping relation is established, the mapping relation is stored in a database of the cloud server.

Referring to fig. 3 in conjunction with fig. 1 and 2, the process of the user terminal 3 processing the raw data is described as follows:

s1, the user terminal 3 sends a data request instruction to the cloud server 2 through the sub-page, and requests to obtain the raw data of the GNSS device 1 in real time. The data request command includes, for example, a GNSS device identifier, a user identifier, and request content, so that the cloud server 2 can know which GNSS device 1 the user terminal 3 needs to access. In the present embodiment, the raw data is collectively referred to as data transmitted from the GNSS device 1 to the cloud server 2. Before sending the data request instruction, the user terminal further checks whether raw data from the GNSS device 1 is continuously received, if the raw data from the GNSS device 1 is not continuously received, the user terminal calls a data request method object in a parent page, encapsulates the data request instruction, sends the data request instruction to the cloud server 2, and stores an address of a data processing object of a child page; if the raw data from the GNSS device 1 is still being received continuously, the user terminal does not receive the data any more and goes to the case where the raw data from the GNSS device 1 is not being received continuously.

In addition, before sending the data request instruction, the user terminal verifies whether the user terminal 3 and the cloud server 2 establish a valid session, if so, the data request instruction is sent to the cloud server 2, and if not, the session is returned to the user terminal to be invalid.

In this step, a device may be selected from GNSS devices as a specific GNSS device, the data request instruction includes a device identifier of the specific GNSS device, and the cloud server 2 forwards the data request instruction to the corresponding GNSS device according to a mapping relationship described later, so as to forward raw data obtained by the GNSS device in response to the data request instruction to the user terminal. As shown in fig. 1, the user terminal 3 only knows the relevant information of the hand book 1a, and the data request instruction includes the device identifier of the hand book 1a, so that only the hand book 1a sends the raw data obtained in response to the data request instruction to the cloud server 2, and the cloud server 2 forwards the data to the user terminal 3.

S2, the cloud server 2 forwards the data request command to the corresponding GNSS device according to the mapping relationship between the GNSS device 1 and the user terminal 3. It should be noted that the forwarding data request command is not limited to the mapping relationship described in this embodiment, as long as the cloud server 2 can know which GNSS device 1 the user terminal 3 accesses, so that the purpose that one user terminal 3 controls one GNSS device 1, or one user terminal 3 controls multiple GNSS devices 1 can be achieved.

S3, after receiving the data request command, the GNSS device 1 responds to the data request command, and sends the raw data to the cloud server 2 through the TCP protocol. As an implementation manner, because the cloud server 2 sends the data request instruction to the GNSS device based on the mapping relationship, only the GNSS device 1 that receives the data request instruction sends the raw data to the cloud server 2, that is, the unsolicited GNSS device 1 will no longer send data to the cloud server 2, thereby relieving the data processing pressure of the cloud server 2 (the cloud server 2 only performs the data forwarding function), and also relieving the data processing pressure of the GNSS device 1.

S4, the cloud server 2 sends the raw data obtained by the GNSS device 1 responding to the data request instruction to the user terminal according to the mapping relationship between the user terminal 3 and the GNSS device 1.

S5, the user terminal 3 processes the raw data to obtain a processing result, so as to implement management of the GNSS device 1 and the application software running on the GNSS device 1.

In this step, the management of the GNSS device includes the management of the GNSS device itself, such as monitoring, remote upgrading, host debugging, functions implemented by the GNSS device, and so on. The management of the application software running on the GNSS device 1 includes implementing functions of the software itself, software upgrade, remote maintenance, and the like.

In this step, the user terminal 3 receives the original data (the original data is transmitted in the form of byte array) from the cloud server through the websocket, after receiving the original data, the user terminal verifies whether the received original data has a packet breaking or sticking problem, and if the received original data has the packet sticking or breaking problem, the problem is repaired or not processed; if not, the difference is the binary data or the ascii data. If the data is binary data, verifying the integrity of the data and analyzing the original data through the information in the header; if the data is ascii data, judging the type of the message through keywords behind the header # of the message and analyzing the original data according to a corresponding format. After the original data are analyzed to obtain an analysis result, the father page finds the data processing object of the child page through the address of the data processing object of the child page, the analysis result is returned to the data processing method of the child page, and the data processing object of the child page processes the analysis result by using the data processing method and displays the processing result on the child page. In this step, the data processing method of the sub-page has different processing methods according to specific situations, as shown in fig. 5, for the device center of the cloud server 2, after the user terminal 3 accesses the cloud server 2, the host state, the satellite information, the host configuration, the data transmission, the device management, the host debugging and other processing can be performed on the GNSS device on the user terminal 3, for example, there are 5 sub-pages of "satellite tracking, tracking information, positioning information, space diagram and signal-to-noise ratio" under the satellite information. The data processing method of each sub-page is different.

In this step, the user terminal analyzes the data only when there is a need, and the following implementation manner is provided: 1) real-time parsing is a desirable way; 2) setting analysis time on a user terminal, and analyzing the received original data by the user terminal under the condition that the time reaches the analysis time; for example, now 15: 00, the user wants to know 15: 30 cents of information on satellite tracking of the GNSS device, the resolution time is set to 15: 30, so that the user terminal, at a time equal to 15: 30, in this manner, the cloud server 2 sends the original data to the user terminal when the time is equal to the parsing time, or, although the cloud server 2 sends the original data, the time does not reach the parsing time, the user terminal does not receive the data or does not parse the original data, and the data is parsed only when the parsing time is reached; of course, in this manner, the parsing time may also be a period of time, such as: 15: 00-15: 20, so that the user terminal analyzes the 20 minutes of original data; 3) setting a time interval for analyzing the original data on the user terminal, and analyzing the original data by the user terminal every other time interval, for example, setting the time interval for analyzing the original data every five minutes on the user terminal, then, the cloud server sends the original data to the user terminal every five minutes, and the user terminal analyzes after receiving the original data. In this way, the user terminal analyzes the raw data at the set time interval, regardless of whether the cloud server sends the raw data to the user terminal according to the frequency or sends the raw data to the user terminal in another manner. If the cloud server sends the original data to the user terminal at the set time interval, and the user terminal analyzes the original data at the set time interval, the method is a real-time analysis mode when in need.

In this step, the user terminal may also perform processing on raw data of the specific GNSS device, in this way, a device is selected from all GNSS devices as the specific GNSS device, the data request instruction is sent to include a device identifier of the specific device, and the cloud server 2 forwards the data request instruction to the specific GNSS device, so that the user terminal receives the raw data of the specific GNSS device.

In this step, the user terminal also parses the specific content, specifically, the specific content is stored in the user terminal in advance, it is first determined whether the received original data is the same as the specific content, and if so, the original data is parsed; if not, the raw data is not parsed.

Of course, the skilled person will appreciate that the above means may be combined in any way, for example, processing of specific content of a specific device at a specific time, processing of specific content at a specific time, etc. may be implemented, which may relieve the cloud server from pressure on processing data.

Referring to fig. 4 and 5 in conjunction with fig. 3, the following describes how to implement monitoring of a GNSS device by taking processing of satellite information from the GNSS device as an example. Before the user terminal 3 processes the raw data of the GNSS device 1, the user terminal 3 and the GNSS device 1 are already connected to the cloud server 2, and the following steps are performed:

s1, sending a data request instruction by the satellite information subpage;

in this step, clicking on "satellite tracking" corresponds to sending a data request instruction to the cloud server 2. The data request command includes a request content, for example, the content of the "satellite tracking" request is to obtain relevant information about satellite tracking of a certain GNSS device 1, as shown ON the right side thereof, the information includes navigation system type (GPS/GLONASS, etc.) and signals (such as L1-CA, L2-C/P, L5 of GPS), and ON indicates that the satellite signal needs to be received. The data request instruction includes, in addition to the request content, the user identifier of the user terminal 3 and the device identifier of the GNSS device 1 to be accessed, so that the cloud server can establish a mapping relationship between the user terminal 3 and the GNSS device 1 based on the device identifier and the user identifier and forward the content of the corresponding GNSS1 about "satellite tracking" to the user terminal 3.

In this step, the data request instruction is sent to the cloud server 2 when the user has a need, so that the cloud server 2 performs data processing in a non-real-time manner for a long time, and the processing pressure of the cloud server 2 is reduced, where the user may consider that the corresponding function is clicked when the user has a need, that is, the user may set time and GNSS equipment on the user terminal, and after the time is reached, the data request instruction is sent to the cloud server 2, for example, the data request instruction is "host debug" and is to be executed at 15: 30 knows the "host debug" related content, then the time reaches 15: after 30, the user terminal 3 sends the data request instruction to the cloud server 2, the corresponding GNSS device sends the original data to the cloud server 2 after responding to the data request instruction, and the cloud server 2 returns the corresponding original data to the user terminal.

In this step, before the user terminal 3 sends the data request instruction, it also checks whether the user terminal 3 has continuous original data that is not closed, that is, the user terminal 3 is receiving the original data, if not, it calls a message request method object in the parent page, encapsulates the data request instruction, and may also encrypt the data request instruction, send the data request instruction, and store the data processing object of the sub-page; if data is being received, the original data is no longer received and the step of not receiving the original data is skipped (as described above).

In this step, before the user terminal 3 sends the data request instruction, it is further verified whether the user terminal 3 and the cloud server 2 establish an effective session, if an effective session is established, the data request instruction is sent to the cloud server 2, and if an effective session is established, a session invalidity is fed back to the user terminal 3.

S2, the cloud server 2 forwards the data request command to the corresponding GNSS device 1 and returns data (raw data) of the GNSS device related to "satellite tracking", and the user terminal receives the sent raw data through the websocket object.

In this step, after the user terminal 3 receives the original data, it needs to verify whether there is a packet break or a packet sticky problem, and if not, it distinguishes whether the original data is ascii data or binary data.

S3, the user terminal 3 processes the received raw data to obtain a processing result.

In this step, for the case that the original data is binary data, the user terminal 3 parses the data to obtain a parsing result, the father page returns to the data processing method of the satellite information sub-page through the stored satellite information plane data processing object, then the data transmitted in the data method of the satellite information page is encapsulated into an object, when a map (such as a hundred-degree map) is called to display the position of the GNSS device, the satellite data in the object is directly transmitted to the hundred-degree api, and the related data in the object is also displayed on the corresponding position of the page through javascript. As explained with reference to fig. 5, assuming that the L1-CA of the GPS is turned on in the transmission data request instruction, the user terminal 3 processes data related to the GPS L1-CA signal and displays the processing result at a corresponding location. After the display, the websocket judges whether the websocket communication is valid, if so, the step of receiving the original data by the user terminal 3 through the websocket object is returned, and if not, the user terminal 3 is prompted to disconnect.

In this step, the content to be analyzed is pre-stored in the user terminal 3, for example, the content to be analyzed is "satellite tracking", then, after receiving the original data forwarded by the cloud server 2, the user terminal 3 determines whether the received original data (which may be after determining whether the data is binary data or ascii data) is the same as the content to be analyzed, and if the received original data is the same as the content to be analyzed, the user terminal analyzes the original data to obtain an analysis result; if not, the received raw data is not parsed. By means of the mode that the user terminal 3 only analyzes the content required by the user terminal and does not analyze the unnecessary data, the pressure of the user terminal 3 on processing the data is reduced, and the pressure of the cloud server 2 on processing the data is also reduced.

The above manner may be considered as real-time analysis (when there is a need), and the skilled person may understand that the analysis time may also be set, and the original data (data related to satellite tracking) is only analyzed when the time is equal to the analysis time; alternatively, the user terminal 3 sets a frequency of analyzing the raw data, for example, 5 minutes, and then the user terminal analyzes the raw data (data related to satellite tracking) every five minutes, and of course, when the memory capacity of the user terminal 3 is large, the raw data transmitted by the cloud server 2 may be received first, and then the raw data may be analyzed every 5 minutes.

Referring to fig. 7 and fig. 8 in conjunction with fig. 1 to fig. 6, taking the management of the software (SurveyMaster) running on the GNSS apparatus 1 by the user terminal 3 as an example, the management of the software running on the GNSS apparatus 1 by the user terminal is described.

The method comprises the following specific steps:

s1, the user terminal 3 selects GNSS equipment which runs surfymaster and needs to be checked

In this step, first, the user terminal 3 sends a device list request to the cloud server 2 through a real-time monitoring sub-page of the overseaser software running on the user terminal 3. After receiving the device list request, the cloud server 2 judges whether the user terminal 3 has the authority to check the device list, and if not, prompts the user to apply for the authority; if so, the cloud server 2 returns the device list data of the user company to the user terminal 3. After receiving the device list data, the user terminal 3 checks the devices and selects one device from the devices and determines whether the selected device is online. If the selected device is not on-line, prompting the user to connect the GNSS device to the cloud server; if so, the process proceeds to step S2.

S2, in case that the GNSS device is online, the user terminal 3 sends a data request command to perform real-time monitoring on the GNSS device. How to send the data request command may refer to fig. 7 and the description of the satellite information, similar to the "satellite information", for example, after sending the data request command, the parent page stores the address of the data processing object that monitors the child page in real time. The cloud server 2 forwards the data request instruction to the corresponding GNSS device, and the GNSS device sends the raw data to the cloud server 2 in response to the data request instruction. The cloud server 2 forwards the raw data to the user terminal 3.

S3, the user terminal 3 processes the obtained raw data to obtain a processing result.

In this step, the user terminal 3 distinguishes whether the received data is binary data or ascii data, and obtains an analysis result by analyzing correspondingly according to different data types. The analytic result is searched by the father page through the address of the data processing object of the real-time monitoring sub-page, the analytic result is called back to the data processing method of the real-time monitoring page, the data processing object of the sub-page encapsulates the analytic result into an equipment object by using the data processing method, the position of the equipment is identified on a map (such as a Gandy map or a Baidu map) in real time, and the detailed information of the GNSS equipment can be checked by clicking the equipment identification on the map. Subsequently, the user terminal 3 determines whether the websocket communication is valid, and if so, returns to the step in which the user terminal 3 receives the original data through the websocket object, and if not, prompts the user terminal 3 that the websocket has been disconnected.

In this embodiment, the content to be analyzed may still be pre-stored in the user terminal 3, and then before the analysis, it is determined whether the content is the same as the content to be analyzed, if not, the content is not analyzed, and if the content is the same, the content is analyzed and processed as described above.

Referring to fig. 1, a GNSS device 1 and a user terminal 3 are taken as an example for description, and in practical applications, multiple GNSS devices 1 and multiple user terminals 3 work online at the same time, for example, a user a establishes a connection with a GNSS receiver 1b through a browser on a user terminal (PC) to obtain tracking information in satellite information; b, establishing connection between a user and the vehicle-mounted terminal 1c through a browser of the mobile terminal (a tablet personal computer) to debug a host; and after the user C establishes connection with the handbook 1a through a user terminal (a smart phone provided with a SurveyMaster), the functions of real-time monitoring, engineering management and the like are carried out.

Referring to fig. 1, a GNSS device management system is further disclosed according to the above method for processing GNSS device data. The system comprises a cloud server and at least one user terminal. Any one user terminal sends a data request instruction to the cloud server. And the cloud server forwards the data request instruction to the corresponding GNSS equipment, and acquires the original data of the GNSS equipment sent to the cloud server by the corresponding GNSS equipment responding to the instruction. And the user terminal sending the instruction requesting the data receives the original data, processes the original data to obtain a processing result, and manages the GNSS equipment and the application software running on the GNSS equipment.

In a further aspect, as shown in fig. 9, the user terminal includes a request module, a receiving module, an analyzing module, a callback module, and a storage module, where the request module receives the data request instruction sent by the user and places a data processing object storing the current sub-page in the storage module; the receiving module receives the original data; the analysis module analyzes the original data to obtain an analysis result, and transmits the analysis result to the callback module; and the callback module recalls the analysis result to the data processing method of the sub-page through the data processing object of the sub-page stored by the request module, processes the analysis result by using the processing method and displays the analysis result on the sub-page. In a further scheme, the user terminal comprises a request closing module, and the request module sends a query instruction to the request closing module after receiving the data request instruction; the request closing module inquires whether continuous first original data which is not closed exists after receiving the inquiry instruction, and if so, the continuous first original data stored by the closing module is traversed; generating a trigger signal if there is no persistent first raw data that is not turned off; the request module is triggered by the trigger signal to send the data request instruction outwards and store the data processing object of the sub-page. Furthermore, the user terminal comprises a judging module, the storage module is internally stored with the content to be analyzed, the judging module judges that the received original data is the same as the content to be analyzed, and if the received original data is the same as the content to be analyzed, the judging module transmits a judging signal to the analyzing module; the analysis module analyzes the received original data according to the judgment signal; if not, the received raw data is not parsed. In another scheme, the user terminal includes a time setting module and a time processing module, the time setting module sets an analysis time by a user, the time processing module is configured to determine whether the current time is equal to the analysis time, send a first trigger signal to the analysis module when the current time is equal to the analysis time, and the analysis module analyzes received original data under the trigger of the first trigger signal; or, the time setting module is configured to set a time interval for analyzing the original data, the time processing module sends a second trigger signal to the analyzing module every other time interval, and the analyzing module analyzes the received original data under the trigger of the second trigger signal.

How the GNSS device and the user terminal establish a connection and how the GNSS device is connected to the cloud server 2 in the system are the same as those described in the foregoing method, and details thereof are not repeated.

In summary, the present invention has at least the following advantages:

2. The analysis time is set on the user terminal, and the user terminal analyzes the received original data only when the time reaches the analysis time, or the frequency for receiving the original data is set on the user terminal, and the user terminal analyzes the original data after receiving the original data sent to the user terminal by the cloud server according to the frequency.

4. Because the user terminal sends the data request instruction to the specific GNSS device (for example, the data request instruction is sent to the specific GNSS device through the cloud server based on the mapping relationship), the GNSS device related to the unsolicited request does not send the raw data to the cloud server, and the cloud server does not process the raw data sent by the unsolicited GNSS device, so that the data processing pressure of the GNSS device, the cloud server, and the user terminal is reduced on the premise of ensuring that the processing pressure of the cloud server is low.

Claims

1. A method for processing GNSS equipment data by a user terminal is characterized by comprising the following steps:

the user terminal sends a data request instruction to a cloud server;

the cloud server transmits the data request instruction to the corresponding GNSS device;

the GNSS device responds to the instruction to send raw data to the cloud server;

the cloud server forwards the original data to a corresponding user terminal;

and the user terminal processes the original data to obtain a processing result, so that the GNSS equipment and the application software installed on the GNSS equipment are managed.

2. The method of claim 1, wherein the step of the user terminal sending a data request instruction to the cloud server comprises: after receiving the data request instruction sent by the user, the sub-page calls a parent page data request method, the data request instruction is sent out by using the data request method, and the address of the data processing object of the current sub-page is also stored;

the processing of the raw data by the user terminal to obtain a processing result comprises: analyzing the received original data to obtain an analysis result, finding the data processing object of the sub-page by the father page through the address of the data processing object of the sub-page, returning the analysis result to the data processing method of the sub-page, and processing the analysis result by the data processing object of the sub-page by using the data processing method and displaying the processing result on the sub-page.

3. The method of claim 2, wherein the step of the user terminal sending a data request instruction to the cloud server comprises: after receiving the data request instruction, the sub-page inquires whether continuous first original data which is not closed exists, and if so, the first original data is not received any more; if the data processing object does not exist, the child page calls a parent page data request method, the data request method is used for sending the data request instruction outwards, and the address of the data processing object of the current child page is stored.

4. The method as claimed in claim 1, wherein the step of the ue processing the raw data to obtain a processing result comprises pre-storing the content to be analyzed, determining that the received raw data is the same as the content to be analyzed, and if the received raw data is the same as the content to be analyzed, analyzing the raw data and processing the analysis result to obtain a processing result; if not, the received raw data is not parsed.

5. The method of claim 1, wherein the step of the ue processing the raw data to obtain the processing result comprises setting a parsing time at the ue, and in case the time reaches the parsing time, the ue parses the received raw data, or setting a time interval at the ue for parsing the raw data, and the ue parses the raw data according to the time interval.

6. The method of claim 1, wherein the step of the user terminal sending a data request instruction to the cloud server comprises: selecting the GNSS device as a specific GNSS device, and the data request instruction comprises a device identification of the specific GNSS device.

7. The method as claimed in any one of claims 1 to 6, wherein the cloud server forwards the data request command to the corresponding GNSS device according to a mapping relationship between the user terminal and the GNSS device.

8. The method as claimed in claim 7, wherein each GNSS device is connected to the cloud server via TCP/IP, and each user terminal is connected to the cloud server via WebSocket.

9. The method as claimed in claim 8, wherein the step of establishing the mapping relationship between the ue and the GNSS device comprises:

the method for establishing the mapping relationship between the GNSS device and the TCP identifier TCPID and the TCP Client of the TCP Client comprises the following steps: the GNSS device is connected with a cloud server as a TCP client, the cloud server sends a command requiring the GNSS device to send a device identifier to the cloud server at a certain frequency, meanwhile, the cloud server obtains a TCP identifier TCPID and defines a data structure for storing and analyzing the device identifier of the GNSS device, and a mapping relation between the TCPID and the data structure is established; the cloud server stores the received data from the GNSS equipment in the data structure according to the mapping relation between the TCPID and the data structure and analyzes the data in the data structure until the equipment identifier is obtained, after the equipment identifier is obtained, the mapping MAP < SN, TCP Client > between the GNSS equipment and the TCP Client is established, and the mapping relation MAP < TCPID, SN > between the TCP identifier TCPID and the GNSS equipment is also established;

the step of establishing the mapping relationship between the user terminal and the Websocket ID and the Websocket Client comprises the following steps: the user terminal accesses the cloud server in a Websocket mode, establishes mapping Map < user, Websocket Client > between the user terminal and the Websocket Client, and also establishes mapping relation Map < user, Websocket ID > between the user terminal and the Websocket ID;

the step of establishing the mapping relationship between the user terminal and the GNSS device comprises the following steps: the instruction sent by the GNSS device to the server comprises a user identifier of the user terminal, or the instruction sent by the user terminal to the cloud server comprises a device identifier, and the cloud server establishes a mapping relation between the user terminal and the GNSS device according to the user identifier and the device identifier.

10. The method as claimed in claim 9, wherein the cloud server detects an online status of the GNSS device, and releases mapping relationships MAP < SN, TCPClient and MAP < TCPID, SN > when the GNSS device is not online.

11. The GNSS device comprises a user terminal and a cloud server, wherein the user terminal is used for processing raw data from the GNSS device, sending a data request instruction outwards, receiving the raw data forwarded by the cloud server, processing the raw data to obtain a processing result so as to realize management of the GNSS device and application software installed in the GNSS device, and the raw data is sent to the cloud server by the GNSS device in response to the data request instruction.

12. The user terminal of claim 11, comprising a request module, a receive module, a parse module, a callback module, and a store module, wherein,

after receiving the data request instruction sent by the user, the request module calls a father page data request method, sends the data request instruction to the outside by using the data request method, and also stores the address of the data processing object of the current sub-page in the storage module;

the receiving module receives raw data from the GNSS device;

the analysis module analyzes the original data to obtain an analysis result, and transmits the analysis result to the callback module;

the callback module finds the data processing object of the sub-page through the address of the stored data processing object of the sub-page, and recalls the analysis result to the data processing method of the sub-page, and the data processing object of the sub-page processes the analysis result by using the data processing method of the sub-page and displays the processing result on the sub-page.

13. The user terminal according to claim 12, wherein the user terminal comprises a request closing module, and the request module sends a query instruction to the request closing module after receiving the data request instruction; the request closing module inquires whether continuous first original data which is not closed exists after receiving the inquiry instruction, and if so, the continuous first original data stored by the closing module is traversed; generating a trigger signal if there is no persistent first raw data that is not turned off; the request module is triggered by the trigger signal to send the data request instruction outwards and store the data processing object of the sub-page.

14. The user terminal according to claim 12, wherein the user terminal comprises a judging module, the storage module stores contents to be analyzed, the judging module judges that the received original data is the same as the contents to be analyzed, and if the received original data is the same as the contents to be analyzed, transmits a judging signal to the analyzing module; the analysis module analyzes the received original data according to the judgment signal; if not, the received raw data is not parsed.

15. The ue of claim 12, wherein the ue comprises a time setting module and a time processing module, the time setting module is configured to set an analysis time, the time processing module is configured to determine whether the current time is equal to the analysis time, and send a first trigger signal to the analysis module when the current time is equal to the analysis time, and the analysis module analyzes the received raw data under the trigger of the first trigger signal;

or,

the time setting module is used for setting a time interval for analyzing the original data, the time processing module sends a second trigger signal to the analyzing module every other time interval, and the analyzing module analyzes the received original data under the trigger of the second trigger signal.

16. The user terminal of claim 11, wherein the user terminal sending a data request instruction to a cloud server comprises: selecting the GNSS device as a specific GNSS device, and the data request instruction comprises a device identification of the specific GNSS device.

A GNSS device management system for processing data from GNSS devices, characterized in that the system comprises a cloud server and at least one user terminal, wherein the user terminal is the user terminal according to any one of claims 11 to 16.

18. The GNSS device management system according to claim 17, wherein the GNSS device is wirelessly connected to the cloud server when the GNSS device has a wireless internet access function; or, under the condition that the GNSS device does not have the wireless internet function, the GNSS device is connected to a third-party device in a wired or bluetooth manner, and is connected to the cloud server through an operating system of the third-party device, data transfer software installed in the third-party device, or an APP installed in the third-party device.

19. The GNSS device management system according to claim 17, wherein the cloud server forwards the data request command to the corresponding GNSS device according to a mapping relationship between the user terminal and the GNSS device.

20. The GNSS device management system according to claim 19, wherein each of the GNSS devices is connected to the cloud server in a TCP/IP manner, and each of the user terminals is connected to the cloud server in a WebSocket manner.

21. The GNSS device management system according to claim 20, wherein the cloud server transmits the raw data to the corresponding user terminal according to a mapping relationship between the GNSS device and the user terminal, the mapping relationship being established by: