Remote control method, device and system of GNSS receiver, readable storage medium and program product

Abstract

The invention relates to a remote control method, device and system for a GNSS receiver, a readable storage medium and a program product, and the method comprises the steps: accessing the Internet through a mobile network module under the condition that the starting of the GNSS receiver is detected, building a socket connection with a target Internet of Things platform based on the Internet, and achieving the remote control of the GNSS receiver. According to the method, the target Internet of Things platform is connected with the socket, the GNSS receiver is correspondingly configured according to the configuration instruction under the condition that the configuration instruction issued by the target Internet of Things platform based on the socket connection is received, and the configuration result is returned to the target Internet of Things platform based on the socket connection, so that remote access and control of the GNSS receiver can be realized, the management efficiency of the GNSS receiver can be improved, and the user experience can be improved. And manpower and material resources for managing the GNSS receiver can be saved.

Description

Technical Field

[0001] The present application relates to the technical field of GNSS receivers, and in particular to a remote control method, device, system, readable storage medium and program product of a GNSS receiver. Background Art

[0002] A GNSS (Global Navigation Satellite System) receiver is a device used to receive, track, process and measure GNSS signals. It can receive signals from different satellites, process and analyze these signals, and calculate its own position, speed, time and other information. GNSS receivers are widely used in navigation, positioning, measurement, aviation, navigation, remote sensing and other fields.

[0003] In traditional technology, GNSS receivers usually work outdoors for a long time. When a GNSS receiver has a problem, or when the receiver firmware needs to be upgraded, the computer and GNSS receiver are usually connected via Ethernet or the mobile phone is connected to the GNSS receiver device wifi to configure a single or several GNSS receivers through the connected computer or mobile phone. However, this method is time-consuming, labor-intensive, and inefficient when there are many GNSS receivers to be managed. Summary of the invention

[0004] Based on this, it is necessary to provide a remote control method, device, system, readable storage medium and program product for a GNSS receiver that can improve configuration efficiency in response to the above technical problems.

[0005] In a first aspect, the present application provides a remote control method for a GNSS receiver, wherein the GNSS receiver has a mobile network module embedded therein, and the method comprises:

[0006] When detecting that the GNSS receiver is started, accessing the Internet through the mobile network module;

[0007] Based on the Internet, a socket connection with a target IoT platform is established;

[0008] Upon receiving a configuration instruction issued by the target IoT platform based on the socket connection, configuring the GNSS receiver accordingly according to the configuration instruction;

[0009] Return the configuration result to the target Internet of Things platform based on the socket connection.

[0010] In one of the embodiments, after establishing a socket connection with the target IoT platform, the method further includes: upon receiving a status query instruction sent by the target IoT platform based on the socket connection, obtaining the operating status information of the GNSS receiver; and returning the operating status information to the target IoT platform based on the socket connection.

[0011] In one of the embodiments, after establishing a socket connection with the target IoT platform, the method further includes: upon receiving a configuration query instruction sent by the target IoT platform based on the socket connection, obtaining configuration information of the GNSS receiver; and returning the configuration information to the target IoT platform based on the socket connection.

[0012] In one of the embodiments, establishing a socket connection with a target IoT platform includes: sending a registration request to the target IoT platform, wherein the registration request carries a device identifier of the GNSS receiver; the registration request is used to indicate establishing a socket connection with the target IoT platform; receiving a registration result returned by the target IoT platform according to the registration request, and if the registration result is a successful registration, confirming the establishment of a socket connection with the target IoT platform.

[0013] In one of the embodiments, the method further includes: if the registration result is registration failure, returning to execute the step of sending a registration request to the target Internet of Things platform.

[0014] In one of the embodiments, an FRP client is deployed in the GNSS receiver; when it is detected that the GNSS receiver is started, the method further includes: performing service configuration for the GNSS receiver based on the FRP client, the service configuration at least including a domain name configuration of a server and a subdomain name configuration of the GNSS receiver; when the FRP client is started, establishing a connection with a corresponding FRP server, the connection being used to indicate that when a browser is accessed through the subdomain name of the GNSS receiver and the domain name of the server, the configuration information of the GNSS receiver is displayed; in response to a modification operation on the configuration information, updating the configuration information of the GNSS receiver based on the modification operation.

[0015] In a second aspect, the present application provides a remote control device for a GNSS receiver, wherein the GNSS receiver has a mobile network module embedded therein, and the device comprises:

[0016] A network access module, configured to access the Internet through the mobile network module when detecting that the GNSS receiver is started;

[0017] A connection module, used to establish a socket connection with a target IoT platform based on the Internet;

[0018] A configuration module, configured to configure the GNSS receiver accordingly according to the configuration instruction when receiving the configuration instruction issued by the target IoT platform based on the socket connection;

[0019] The result returning module is used to return the configuration result to the target Internet of Things platform based on the socket connection.

[0020] In a third aspect, the present application provides a remote control system for a GNSS receiver, the system comprising: a plurality of GNSS receivers and a target Internet of Things platform;

[0021] The GNSS receiver is embedded with a mobile network module. When the GNSS receiver is started, the GNSS receiver is used to access the Internet through the mobile network module and establish a socket connection with the target IoT platform based on the Internet.

[0022] The target IoT platform is used to respond to the configuration request for the GNSS receiver and send a corresponding configuration instruction to the GNSS receiver based on the socket connection, wherein the configuration instruction is used to instruct the GNSS receiver to perform corresponding configuration;

[0023] The GNSS receiver is further configured to perform corresponding configuration according to the configuration instruction when receiving the configuration instruction, and return the configuration result to the target IoT platform based on the socket connection;

[0024] The target Internet of Things platform is also used to receive the configuration result returned by the GNSS receiver.

[0025] In one of the embodiments, the GNSS receiver also includes a registration module, and the GNSS receiver is also used to send a registration request to the target Internet of Things platform through the registration module, and the registration request carries the device identification of the GNSS receiver; the target Internet of Things platform is also used to verify the device identification of the GNSS receiver according to the registration request when receiving the registration request, and if the verification passes, return a registration result of successful registration to the GNSS receiver and establish a socket connection with the GNSS receiver; if the verification fails, return a registration result of failed registration to the GNSS receiver; the GNSS receiver is also used to receive the registration result, and when receiving the registration result of failed registration, return to execute the registration request sent to the target Internet of Things platform through the registration module.

[0026] In one of the embodiments, the target IoT platform is further used to periodically send status query instructions to the GNSS receiver based on the socket connection; the GNSS receiver is further used to obtain operating status information upon receiving the status query instruction sent by the target IoT platform, and return the operating status information to the target IoT platform; the target IoT platform is also used to receive the operating status information sent by the GNSS receiver.

[0027] In one of the embodiments, if the target IoT platform fails to receive the operating status information sent by the GNSS receiver for a consecutive number of times reaching a set threshold, it indicates that the socket connection between the target IoT platform and the GNSS receiver is disconnected.

[0028] In one of the embodiments, the target IoT platform is further used to respond to a configuration query request for the GNSS receiver, and send a corresponding configuration query instruction to the GNSS receiver based on the socket connection; the GNSS receiver is further used to obtain corresponding configuration information upon receiving the configuration query instruction, and return the configuration information to the target IoT platform based on the socket connection; the target IoT platform is also used to receive the configuration information of the GNSS receiver.

[0029] In one of the embodiments, the system also includes a server with a domain name, an FRP server is deployed on the server, and the FRP server is accessed through the domain name of the server; an FRP client is deployed in the GNSS receiver, and the GNSS receiver is also used to perform service configuration based on the FRP client, and the service configuration includes at least the domain name configuration of the server and the subdomain name configuration of the GNSS receiver; and when the FRP client is started, a connection with the corresponding FRP server is established, and the connection is used to indicate that when the browser is accessed through the subdomain name of the GNSS receiver and the domain name of the server, the configuration information of the GNSS receiver is displayed, and in response to a modification operation on the configuration information, the configuration information of the GNSS receiver is updated based on the modification operation.

[0030] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0031] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the steps of the above method when executed by a processor.

[0032] The remote control method, device, system, readable storage medium and program product of the above-mentioned GNSS receiver, when detecting that the GNSS receiver is started, accesses the Internet through the mobile network module, establishes a socket connection with the target Internet of Things platform based on the Internet, and when receiving the configuration instructions issued by the target Internet of Things platform based on the socket connection, configures the GNSS receiver accordingly according to the configuration instructions, and returns the configuration result to the target Internet of Things platform based on the socket connection, thereby realizing remote access and control of the GNSS receiver, which can not only improve the management efficiency of the GNSS receiver, but also save manpower and material resources for the management of the GNSS receiver. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments of the present application or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0034] Figure 1 is a flow chart of a remote control method for a GNSS receiver in one embodiment;

[0035] Figure 2A flowchart of steps for establishing a socket connection in one embodiment;

[0036] Figure 3 is a flowchart of a remote control method for a GNSS receiver in another embodiment;

[0037] Figure 4 is a structural block diagram of a remote control device for a GNSS receiver in one embodiment;

[0038] Figure 5 is an interactive schematic diagram of a remote control system of a GNSS receiver in one embodiment;

[0039] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0041] In one embodiment, Figure 1 As shown, a remote control method for a GNSS receiver is provided. This embodiment uses the method applied to a GNSS receiver as an example for illustration. It is understandable that the method can also be applied to a server, and can also be applied to a system including a GNSS receiver and a server, and is implemented through the interaction between the GNSS receiver and the server. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services, or an Internet of Things server. In this embodiment, the method includes the following steps:

[0042] Step 102: When it is detected that the GNSS receiver is started, access to the Internet via the mobile network module.

[0043] Among them, the mobile network module is an indispensable component of modern communication systems, and it plays an important role in data transmission and reception. In this embodiment, the GNSS receiver is embedded with a mobile network module, which integrates interfaces related to network communication, so that it can independently complete the sending and receiving of signals. There are many types of mobile network modules, including Bluetooth communication modules, WiFi communication modules, NB-IoT wireless communication modules, network cards, etc. With the continuous development of Internet of Things technology, the application scope of mobile network modules will continue to expand. Its advantages in practical applications include integrating multiple communication standards for a wider range of application scenarios, meeting the specific needs of different customers in different application scenarios, and module manufacturers can customize and develop according to the requirements of application manufacturers.

[0044] Specifically, when it is detected that the GNSS receiver is started, the mobile network module can dial up to the Internet based on a pre-embedded configuration file. When it is detected that the GNSS receiver obtains the mobile network IP (Internet Protocol), it means that the GNSS receiver has connected to the Internet.

[0045] Step 104: Establish a socket connection with the target IoT platform based on the Internet.

[0046] Socket is an abstraction of the endpoint for two-way communication between application processes on different hosts in the network. Socket connection mainly transmits data through Socket, supporting TCP (Transmission Control Protocol) / UDP (User Datagram Protocol) / TLS (Transport Layer Security) protocols.

[0047] The Internet of Things (IoT) is a network based on information carriers such as the Internet and traditional telecommunications networks, which enables all ordinary physical objects that can be independently addressed to achieve interconnection and intercommunication. It has three important characteristics: ordinary object equipment, autonomous terminal interconnection, and ubiquitous service intelligence. The vigorous development of IoT technology has promoted the interconnection and intercommunication between smart devices. In this embodiment, by combining the GNSS receiver with the single-chip microcomputer technology and integrating the IoT technology, a continuous connection between the GNSS receiver and the server, that is, the target IoT platform, is achieved. Through specific data protocol commands, the GNSS receiver can be remotely accessed and controlled.

[0048] Specifically, the GNSS receiver further establishes a socket connection with the target IoT platform based on the Internet accessed in the above steps, so that the GNSS receiver can perform efficient two-way data transmission with the target IoT platform through socket technology.

[0049] Step 106, upon receiving the configuration instruction sent by the target IoT platform based on the socket connection, the GNSS receiver is configured accordingly according to the configuration instruction.

[0050] Specifically, based on the socket connection between the GNSS receiver and the target IoT platform, the target IoT platform can remotely access and control the GNSS receiver. The configuration instruction is an instruction or command for configuring the GNSS receiver or modifying or upgrading its program firmware, and the configuration instruction usually carries corresponding configuration parameters.

[0051] In this embodiment, when it is necessary to configure the GNSS receiver or modify or upgrade its program firmware, a corresponding configuration request can be initiated to the target IoT platform, and the target IoT platform responds to the configuration request and sends relevant configuration instructions to the corresponding GNSS receiver based on the socket connection. When the GNSS receiver receives the configuration instruction sent by the target IoT platform based on the socket connection, it can configure the GNSS receiver accordingly according to the configuration instruction, that is, configure it based on the configuration parameters carried in the configuration instruction.

[0052] Step 108: Return the configuration result to the target IoT platform based on the socket connection.

[0053] Among them, the configuration result is used to characterize the specific state of the GNSS receiver after the configuration is performed based on the configuration instruction. Specifically, the configuration result can be the result of the successful completion of the configuration of the GNSS receiver, or the result of the unsuccessful configuration of the GNSS receiver, or the specific log information of the configuration of the GNSS receiver. In this embodiment, after the GNSS receiver performs the corresponding configuration based on the above steps using the configuration instruction, it can also return the specific state after configuration, that is, the configuration result, to the target IoT platform based on the socket connection, so that the target IoT platform can know the specific configuration state of the GNSS receiver.

[0054] In the remote control method of the above-mentioned GNSS receiver, when the GNSS receiver is detected to be started, the Internet is accessed through the mobile network module, and a socket connection with the target Internet of Things platform is established based on the Internet. When the configuration instruction issued by the target Internet of Things platform based on the socket connection is received, the GNSS receiver is configured accordingly according to the configuration instruction, and the configuration result is returned to the target Internet of Things platform based on the socket connection, thereby realizing remote access and control of the GNSS receiver, which can not only improve the management efficiency of the GNSS receiver, but also save manpower and material resources for the management of the GNSS receiver.

[0055] In an exemplary embodiment, Figure 2 As shown, in step 104, establishing a socket connection with the target IoT platform may specifically include:

[0056] Step 202: The GNSS receiver sends a registration request to the target IoT platform.

[0057] The registration request may be a request for establishing a socket connection with the target IoT platform. Specifically, the registration request carries the device identifier of the GNSS receiver (such as the unique number of the device). In some scenarios, the registration request may also carry the device type, such as CORS (Continuous Operational Reference System) receiver, monitoring receiver, and vehicle-mounted receiver.

[0058] In this embodiment, the GNSS receiver sends a registration request to the target IoT platform based on the connected Internet, in order to establish a socket connection with the target IoT platform.

[0059] Step 204: upon receiving the registration request, the target IoT platform verifies the device identification of the GNSS receiver according to the registration request and returns a registration result.

[0060] Specifically, after receiving the registration request, the target IoT platform can verify the device identifier of the GNSS receiver in the registration request according to the preset device list of GNSS receivers that need to be managed, that is, verify whether the device identifier of the GNSS receiver in the registration request is in the preset device list. If the device identifier of the GNSS receiver in the registration request is in the preset device list, the verification passes, agrees to establish a socket connection with the corresponding GNSS receiver, and returns a registration result of successful registration to the GNSS receiver. If the device identifier of the GNSS receiver in the registration request is not in the preset device list, the verification fails, refuses to establish a socket connection with the corresponding GNSS receiver, and returns a registration result of failed registration to the GNSS receiver.

[0061] Step 206: The GNSS receiver identifies whether the registration result is successful.

[0062] Specifically, the GNSS receiver can also receive the registration result returned by the target IoT platform based on the registration request, and identify whether the registration result is a successful registration. If the registration result is identified as a successful registration, step 208 is executed to confirm the establishment of a socket connection with the target IoT platform. If the registration result is identified as a failed registration, the step of sending a registration request to the target IoT platform is returned after a certain interval (such as 30 seconds, 60 seconds, and the specific interval time can be determined based on the actual scenario needs).

[0063] Step 208, confirming the establishment of a socket connection with the target IoT platform.

[0064] Specifically, if the GNSS receiver recognizes that the registration result is a successful registration, it confirms that a socket connection with the target IoT platform is established, that is, a socket connection with the target IoT platform is successfully established.

[0065] In an exemplary embodiment, in step 104, after establishing a socket connection with the target IoT platform, the method may further include: upon receiving a status query instruction sent by the target IoT platform based on the socket connection, obtaining the operating status information of the GNSS receiver; and returning the operating status information to the target IoT platform based on the socket connection.

[0066] Among them, the status query instruction can be sent by the target IoT platform to the GNSS receiver periodically (such as 1 minute, 5 minutes, etc.) to query the real-time status of the GNSS receiver after the GNSS receiver successfully registers on the target IoT platform (i.e., the target IoT platform successfully establishes a socket connection with the GNSS receiver) to query the real-time status of the GNSS receiver. The operating status information of the GNSS receiver includes but is not limited to the real-time location information of the GNSS receiver, the number of satellites, the positioning status, the storage space information, the CPU usage rate, the CPU temperature, the battery power, the voltage, the firmware version and other information.

[0067] In this embodiment, when the GNSS receiver receives a status query instruction sent by the target IoT platform based on a socket connection, it obtains its current operating status information and returns the operating status information to the target IoT platform based on the socket connection, so that the target IoT platform can obtain the real-time status of the GNSS receiver for effective management.

[0068] In one scenario, after the target IoT platform receives the operating status information returned by the GNSS receiver, it can store it in the database for data analysis and display it on the platform page so that the staff can intuitively understand the real-time status of the GNSS receiver.

[0069] In one scenario, if the target IoT platform does not receive the operating status information returned by the GNSS receiver within a preset time (such as a sending cycle) after sending a status query command to the GNSS receiver, it will continue to send status query commands to the GNSS receiver when the next sending cycle arrives. If the GNSS receiver does not receive the operating status information returned by the GNSS receiver after sending 5 status query commands in succession, that is, the number of consecutive times that the operating status information sent by the GNSS receiver is not received reaches the set threshold (such as 5 times), it means that the socket connection between the target IoT platform and the GNSS receiver may be disconnected. At this time, the target IoT platform can issue an alarm and display the information on the platform page, thereby reminding the staff to troubleshoot the problem so that the GNSS receiver can be effectively managed.

[0070] In an exemplary embodiment, in step 104, after establishing a socket connection with the target IoT platform, the method may further include: upon receiving a configuration query instruction sent by the target IoT platform based on the socket connection, obtaining configuration information of the GNSS receiver; and returning the configuration information to the target IoT platform based on the socket connection.

[0071] The configuration query instruction may be generated by the target IoT platform based on the user's configuration query request, and is used to query the configuration of the GNSS receiver. The configuration information of the GNSS receiver includes but is not limited to its corresponding hardware configuration, software configuration, resource configuration, etc.

[0072] Specifically, when it is necessary to query the configuration information of a certain GNSS receiver, a corresponding configuration query request can be initiated to the target IoT platform, and the target IoT platform sends a configuration query instruction to the corresponding GNSS receiver through a socket connection based on the user's configuration query request. When the GNSS receiver receives the configuration query instruction sent by the target IoT platform based on the socket connection, it obtains the current configuration information of the GNSS receiver and returns the configuration information to the target IoT platform based on the socket connection, so that the configuration information of the GNSS receiver can be obtained in real time, so as to effectively control the GNSS receiver.

[0073] In an exemplary embodiment, a FRP (Fast Reverse Proxy, a high-performance reverse proxy application) client is also deployed in the GNSS receiver. Figure 3 As shown, in step 102, when it is detected that the GNSS receiver is started, the method may further include:

[0074] Step 302: Perform service configuration on the GNSS receiver based on the FRP client.

[0075] Among them, FRP is a high-performance reverse proxy application that can easily expose local services to the public network. In FRP, the client and the server negotiate through a configuration file, which usually contains some service information, such as port number, service name, etc. The FRP client and server are generally paired through a public key and a domain name that has been pointed to the server. In this embodiment, the GNSS receiver is configured for service, that is, the GNSS receiver is configured as an FRP client. Its service configuration includes at least the domain name configuration of the server (the FRP server is deployed on the server) and the subdomain name configuration of the GNSS receiver. It can be specifically based on the FRP client deployed in the GNSS receiver, configuring the relevant server domain name (through this domain name, the corresponding server host and the corresponding FRP server web platform can be accessed to query which devices are currently logged in to the FRP server. Usually, only the device logged in to the FRP server can access its device intranet through the subdomain name of the corresponding device), the subdomain name and port parameters of the GNSS receiver (the port parameter is consistent with the port of the FRP server on the server), so that it can be connected to the FRP server.

[0076] Step 304: When the FRP client starts, a connection with the corresponding FRP server is established.

[0077] The connection is used to indicate that when the browser is accessed through the subdomain of the GNSS receiver and the domain of the server, the configuration information of the GNSS receiver is displayed. Specifically, based on the above service configuration, when the FRP client is started (usually when the GNSS receiver is started, the FRP client deployed by it will also be started accordingly), a connection with the corresponding FRP server can be established.

[0078] Step 306: In response to the modification operation on the configuration information, update the configuration information of the GNSS receiver based on the modification operation.

[0079] Specifically, based on the above service configuration, the internal web page of the GNSS receiver can be accessed through a browser. For example, by entering "GNSS receiver subdomain name. server domain name" in the browser, the corresponding internal web page of the GNSS receiver can be logged in. In this way, the external network can access the internal network of the GNSS receiver, so that all information of the GNSS receiver can be viewed, and relevant parameters can be set, and the GNSS receiver can be upgraded through the web page. The GNSS receiver responds to the modification operation of the configuration information and updates the configuration information of the GNSS receiver based on the modification operation.

[0080] In the above embodiment, an FRP client is deployed in the GNSS receiver, so that the service configuration of the GNSS receiver is performed based on the FRP client, and when the FRP client is started, a connection with the corresponding FRP server is established to indicate that when the browser is accessed through the subdomain name of the GNSS receiver and the domain name of the server, the configuration information of the GNSS receiver is displayed. The GNSS receiver responds to the modification operation on the configuration information and updates the configuration information of the GNSS receiver based on the modification operation, thereby realizing remote access and control of the GNSS receiver based on the FRP reverse proxy technology, which can not only improve the management efficiency of the GNSS receiver, but also save manpower and material resources for the management of the GNSS receiver.

[0081] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0082] Based on the same inventive concept, the embodiment of the present application also provides a remote control device for a GNSS receiver for implementing the remote control method for a GNSS receiver involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in the embodiments of the remote control device for one or more GNSS receivers provided below can refer to the limitations of the remote control method for a GNSS receiver above, and will not be repeated here.

[0083] In an exemplary embodiment, Figure 4 As shown, a remote control device for a GNSS receiver is provided, wherein the GNSS receiver has a built-in mobile network module, and the device is applied to the GNSS receiver, and the device comprises: a network access module 402, a connection module 404, a configuration module 406 and a result return module 408, wherein:

[0084] A network access module 402, configured to access the Internet through the mobile network module when detecting that the GNSS receiver is started;

[0085] A connection module 404 is used to establish a socket connection with a target IoT platform based on the Internet;

[0086] A configuration module 406, configured to configure the GNSS receiver accordingly according to the configuration instruction when receiving the configuration instruction issued by the target IoT platform based on the socket connection;

[0087] The result returning module 408 is used to return the configuration result to the target IoT platform based on the socket connection.

[0088] In an exemplary embodiment, the device also includes a status query module, which is used to establish a socket connection with a target IoT platform, and obtain the operating status information of the GNSS receiver upon receiving a status query instruction sent by the target IoT platform based on the socket connection; and return the operating status information to the target IoT platform based on the socket connection.

[0089] In an exemplary embodiment, the device also includes a configuration query module, which is used to establish a socket connection with a target IoT platform, and upon receiving a configuration query instruction sent by the target IoT platform based on the socket connection, obtain the configuration information of the GNSS receiver; and return the configuration information to the target IoT platform based on the socket connection.

[0090] In an exemplary embodiment, the connection module is also used to: send a registration request to the target IoT platform, the registration request carrying the device identification of the GNSS receiver; the registration request is used to indicate the establishment of a socket connection with the target IoT platform; receive the registration result returned by the target IoT platform based on the registration request, and if the registration result is a successful registration, confirm the establishment of a socket connection with the target IoT platform.

[0091] In an exemplary embodiment, the connection module is further used to: if the registration result is registration failure, return to execute the step of sending a registration request to the target Internet of Things platform.

[0092] In an exemplary embodiment, an FRP client is deployed in the GNSS receiver; the configuration module is also used to perform service configuration of the GNSS receiver based on the FRP client when detecting that the GNSS receiver is started, and the service configuration includes at least the domain name configuration of the server and the subdomain name configuration of the GNSS receiver; when the FRP client is started, a connection with the corresponding FRP server is established, and the connection is used to indicate that the configuration information of the GNSS receiver is displayed when the browser is accessed through the subdomain name of the GNSS receiver and the domain name of the server; in response to a modification operation on the configuration information, the configuration information of the GNSS receiver is updated based on the modification operation.

[0093] Each module in the remote control device of the GNSS receiver can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0094] Based on the same inventive concept, the embodiment of the present application also provides a remote control system for a GNSS receiver, which is used to implement the remote control system for a GNSS receiver of the remote control method for a GNSS receiver involved above. The implementation scheme for solving the problem provided by the system is similar to the implementation scheme recorded in the above method, so the specific limitations in the embodiments of the remote control system for one or more GNSS receivers provided below can refer to the limitations of the remote control method for a GNSS receiver above, and will not be repeated here.

[0095] In an exemplary embodiment, a remote control system for a GNSS receiver includes a plurality of GNSS receivers and a target IoT platform; wherein:

[0096] The GNSS receiver is embedded with a mobile network module. When the GNSS receiver is started, the GNSS receiver is used to access the Internet through the mobile network module and establish a socket connection with the target IoT platform based on the Internet.

[0097] The target IoT platform is used to respond to the configuration request for the GNSS receiver and send a corresponding configuration instruction to the GNSS receiver based on the socket connection, wherein the configuration instruction is used to instruct the GNSS receiver to perform corresponding configuration;

[0098] The GNSS receiver is further configured to perform corresponding configuration according to the configuration instruction when receiving the configuration instruction, and return the configuration result to the target IoT platform based on the socket connection;

[0099] The target Internet of Things platform is also used to receive the configuration result returned by the GNSS receiver.

[0100] In an exemplary embodiment, the GNSS receiver also includes a registration module, and the GNSS receiver is also used to send a registration request to the target Internet of Things platform through the registration module, and the registration request carries the device identification of the GNSS receiver; the target Internet of Things platform is also used to verify the device identification of the GNSS receiver according to the registration request when receiving the registration request, and if the verification passes, return a registration result of successful registration to the GNSS receiver and establish a socket connection with the GNSS receiver; if the verification fails, return a registration result of failed registration to the GNSS receiver; the GNSS receiver is also used to receive the registration result, and when receiving the registration result of failed registration, return to execute the registration request sent to the target Internet of Things platform through the registration module.

[0101] In an exemplary embodiment, the target IoT platform is also used to periodically send status query instructions to the GNSS receiver based on the socket connection; the GNSS receiver is also used to obtain operating status information upon receiving the status query instruction sent by the target IoT platform, and return the operating status information to the target IoT platform; the target IoT platform is also used to receive the operating status information sent by the GNSS receiver.

[0102] In an exemplary embodiment, if the target IoT platform fails to receive the operating status information sent by the GNSS receiver for a consecutive number of times reaching a set threshold, it indicates that the socket connection between the target IoT platform and the GNSS receiver is disconnected.

[0103] In an exemplary embodiment, the target IoT platform is also used to respond to a configuration query request for the GNSS receiver, and send a corresponding configuration query instruction to the GNSS receiver based on the socket connection; the GNSS receiver is also used to obtain corresponding configuration information when receiving the configuration query instruction, and return the configuration information to the target IoT platform based on the socket connection; the target IoT platform is also used to receive the configuration information of the GNSS receiver.

[0104] In an exemplary embodiment, the system also includes a server with a domain name, an FRP server is deployed on the server, and the FRP server is accessed through the domain name of the server; an FRP client is deployed in the GNSS receiver, and the GNSS receiver is also used to perform service configuration based on the FRP client, and the service configuration includes at least the domain name configuration of the server and the subdomain name configuration of the GNSS receiver; and when the FRP client is started, a connection with the corresponding FRP server is established, and the connection is used to indicate that when the browser is accessed through the subdomain name of the GNSS receiver and the domain name of the server, the configuration information of the GNSS receiver is displayed, and in response to a modification operation on the configuration information, the configuration information of the GNSS receiver is updated based on the modification operation.

[0105] In an exemplary embodiment, Figure 5 As shown, the signaling interaction process of the remote control system of the above GNSS receiver is further described below, which may specifically include:

[0106] Step 502: The GNSS receiver is started and connected to the Internet through the embedded mobile network module.

[0107] Specifically, the GNSS receiver has embedded software. When the GNSS receiver is started, the embedded software starts the mobile network module according to the configuration file to dial up the Internet. When the embedded software detects that ppp0 in the system has obtained the mobile network IP, it means that the receiver has been connected to the mobile Internet.

[0108] Step 504: registering on the target IoT platform via a socket based on the Internet.

[0109] Specifically, the GNSS receiver connects to the server IoT platform, also known as the target IoT platform, based on the accessed Internet, and sends a registration package information to the platform. The registration package information includes the receiver's device identification (unique number) and device type (CORS receiver, monitoring receiver, vehicle-mounted receiver, etc.).

[0110] Step 506: The target IoT platform verifies the registration.

[0111] Specifically, the platform determines whether it is its own product based on the received registration information, and then returns the registration result of successful or failed registration to the receiver. If the registration fails, the receiver can repeat the registration process after a certain period of time, such as 60 seconds.

[0112] Step 508: The target IoT platform returns the registration result.

[0113] Specifically, the result of registration success or registration failure is returned.

[0114] Step 510: The target IoT platform queries or sets the configuration of the receiver.

[0115] Step 512: The receiver returns a corresponding query or configuration result.

[0116] Specifically, after the receiver is successfully registered, the platform can periodically send status query instructions to the receiver to query the status of the receiver. After receiving the platform query instruction, the receiver immediately uploads the current operating status information of the receiver (such as receiver location information, number of satellites, positioning status, system storage space information, CPU usage, CPU temperature, battery power, voltage, firmware version, etc.). The platform can store the operating status information of the receiver in the database and display it on the platform page. If the receiver does not respond after the platform sends 5 consecutive query instructions, it means that the connection with the receiver is disconnected.

[0117] The platform can also automatically send corresponding configuration query instructions to the receiver to read the receiver parameters according to the configuration query. After receiving the instructions, the receiver returns the configuration parameters to the platform. The platform can also send instructions to set receiver parameters, that is, configuration instructions, according to needs. After receiving the instructions, the receiver returns the results of the configuration information to the platform.

[0118] Step 514: Jump to the internal web page of the receiver through the IoT domain name to perform relevant configuration.

[0119] Specifically, you first need to deploy the frps service software on a server with a domain name (such as the target IoT platform), configure relevant port parameters, and access the server host through the server domain name. You can access the frps web platform through the domain name to query which receivers are currently logged in to the frps server. Only receivers that are logged in to the frps server can access the receiver's intranet through the corresponding receiver subdomain.

[0120] Deploy the frpc client software in the receiver, configure the relevant server domain name and port parameters, and keep them consistent with the frps port on the server. Configure the http port to 80, add a subdomain, start the frpc client software, and you will be prompted to connect to the frps software on the server. Enter "receiver subdomain.server domain name" in the browser to log in to the receiver's internal web page. After the external network accesses the receiver's internal network in this way, you can view all the receiver information and set related parameters, and upgrade the receiver program through the web page. After completing the relevant parameter configuration, exit the receiver's internal web page.

[0121] This embodiment combines the GNSS receiver with the single-chip microcomputer technology and integrates the Internet of Things technology to achieve a continuous connection between the receiver and the server. The GNSS receiver can perform efficient two-way data transmission with the Internet of Things platform on the server through socket technology. In addition, using the frp reverse proxy technology, intranet penetration can also be achieved, thereby facilitating the connection and deployment between devices. This embodiment combines these two communication methods and targets the characteristics of the Internet of Things technology to achieve an efficient and fast method for managing a large number of GNSS receiver devices, which not only reduces the workload of operation and maintenance personnel, but also helps to reduce the labor costs of enterprises.

[0122] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 6As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a remote control method for a GNSS receiver is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0123] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0124] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0125] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0126] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0127] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0128] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0129] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0130] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A remote control method for a GNSS receiver, characterized in that: The GNSS receiver is embedded with a mobile network module, and the method comprises: When detecting that the GNSS receiver is started, accessing the Internet through the mobile network module; Based on the Internet, a socket connection with a target IoT platform is established; Upon receiving a configuration instruction issued by the target IoT platform based on the socket connection, configuring the GNSS receiver accordingly according to the configuration instruction; Return the configuration result to the target Internet of Things platform based on the socket connection.

2. The method according to claim 1, characterized in that After establishing the socket connection with the target IoT platform, the method further includes: Upon receiving a status query instruction sent by the target IoT platform based on the socket connection, obtaining the operating status information of the GNSS receiver; The operating status information is returned to the target Internet of Things platform based on the socket connection.

3. The method according to claim 1, characterized in that After establishing the socket connection with the target IoT platform, the method further includes: Upon receiving a configuration query instruction sent by the target IoT platform based on the socket connection, acquiring configuration information of the GNSS receiver; Return the configuration information to the target Internet of Things platform based on the socket connection.

4. The method according to claim 1, characterized in that The establishing of a socket connection with the target IoT platform includes: Sending a registration request to the target IoT platform, wherein the registration request carries a device identifier of the GNSS receiver; the registration request is used to indicate establishing a socket connection with the target IoT platform; Receive the registration result returned by the target IoT platform according to the registration request, and if the registration result is successful, confirm to establish a socket connection with the target IoT platform.

5. The method according to claim 4, characterized in that The method further comprises: If the registration result is registration failure, return to execute the step of sending a registration request to the target Internet of Things platform.

6. The method according to any one of claims 1 to 5, characterized in that: The GNSS receiver is equipped with an FRP client; When the GNSS receiver is detected to be started, the method further includes: Performing service configuration on the GNSS receiver based on the FRP client, wherein the service configuration includes at least a domain name configuration of a server and a subdomain name configuration of the GNSS receiver; When the FRP client is started, a connection is established with a corresponding FRP server, wherein the connection is used to indicate that when a browser is accessed through the subdomain name of the GNSS receiver and the domain name of the server, configuration information of the GNSS receiver is displayed; In response to a modification operation on the configuration information, the configuration information of the GNSS receiver is updated based on the modification operation.

7. A remote control device for a GNSS receiver, characterized in that: The GNSS receiver is embedded with a mobile network module, and the device comprises: A network access module, configured to access the Internet through the mobile network module when detecting that the GNSS receiver is started; A connection module, used to establish a socket connection with a target IoT platform based on the Internet; A configuration module, configured to configure the GNSS receiver accordingly according to the configuration instruction when receiving the configuration instruction issued by the target IoT platform based on the socket connection; The result returning module is used to return the configuration result to the target Internet of Things platform based on the socket connection.

8. A remote control system for a GNSS receiver, characterized in that: The system includes: a plurality of GNSS receivers and a target Internet of Things platform; The GNSS receiver is embedded with a mobile network module. When the GNSS receiver is started, the GNSS receiver is used to access the Internet through the mobile network module and establish a socket connection with the target IoT platform based on the Internet. The target IoT platform is used to respond to the configuration request for the GNSS receiver and send a corresponding configuration instruction to the GNSS receiver based on the socket connection, wherein the configuration instruction is used to instruct the GNSS receiver to perform corresponding configuration; The GNSS receiver is further configured to perform corresponding configuration according to the configuration instruction when receiving the configuration instruction, and return the configuration result to the target IoT platform based on the socket connection; The target Internet of Things platform is also used to receive the configuration result returned by the GNSS receiver.

9. The system according to claim 8, characterized in that The GNSS receiver also includes a registration module, The GNSS receiver is further used to send a registration request to the target Internet of Things platform through the registration module, wherein the registration request carries a device identification of the GNSS receiver; The target IoT platform is further configured to verify the device identification of the GNSS receiver according to the registration request when receiving the registration request, and return a registration result indicating successful registration to the GNSS receiver if the verification passes, and establish a socket connection with the GNSS receiver; If the verification fails, a registration result indicating registration failure is returned to the GNSS receiver; The GNSS receiver is further configured to receive the registration result, and upon receiving a registration result indicating a registration failure, return to execute sending a registration request to the target IoT platform through the registration module.

10. The system according to claim 8, characterized in that The target IoT platform is further configured to periodically send a status query instruction to the GNSS receiver based on the socket connection; The GNSS receiver is further configured to obtain operation status information upon receiving the status query instruction sent by the target Internet of Things platform, and return the operation status information to the target Internet of Things platform; The target Internet of Things platform is also used to receive the operating status information sent by the GNSS receiver.

11. The system according to claim 10, characterized in that If the target IoT platform fails to receive the operating status information sent by the GNSS receiver for a consecutive number of times reaching a set threshold, it indicates that the socket connection between the target IoT platform and the GNSS receiver is disconnected.

12. The system according to claim 8, characterized in that The target IoT platform is further configured to respond to a configuration query request for the GNSS receiver and send a corresponding configuration query instruction to the GNSS receiver based on the socket connection; The GNSS receiver is further configured to obtain corresponding configuration information upon receiving the configuration query instruction, and return the configuration information to the target IoT platform based on the socket connection; The target Internet of Things platform is also used to receive configuration information of the GNSS receiver.

13. The system according to any one of claims 8 to 12, characterized in that The system also includes a server having a domain name, An FRP server is deployed on the server, and the FRP server is accessed through the domain name of the server; An FRP client is deployed in the GNSS receiver, and the GNSS receiver is also used to perform service configuration based on the FRP client, and the service configuration at least includes the domain name configuration of the server and the subdomain name configuration of the GNSS receiver; and when the FRP client is started, a connection with the corresponding FRP server is established, and the connection is used to indicate that when the browser is accessed through the subdomain name of the GNSS receiver and the domain name of the server, the configuration information of the GNSS receiver is displayed, and in response to a modification operation on the configuration information, the configuration information of the GNSS receiver is updated based on the modification operation.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images