Account management method and account management system

Abstract

The invention discloses an account number management method and an account number management system, the method is applied to a first cloud platform, the first cloud platform is in communication connection with a vehicle-mounted terminal, the method comprises the following steps: receiving first request information, the first request information being used for requesting to distribute an authority of using a PPP-RTK positioning function to the vehicle-mounted terminal; and in response to the first request information, selecting a target PPP-RTK service account from a PPP-RTK service account pool of the first cloud platform, and issuing the target PPP-RTK service account to the vehicle-mounted terminal for burning.

Description

Technical Field

[0001] The present application relates to the field of cloud platform communication technology, and more specifically, to an account management method and an account management system. Background Art

[0002] In order to improve the positioning accuracy of the global navigation satellite system (GNSS), the precise point positioning real-time kinematic (PPP-RTK) positioning technology is proposed in the related art.

[0003] If the PPP-RTK positioning service function is enabled for a vehicle, the PPP-RTK service account needs to be burned into the vehicle terminal of each vehicle. However, the PPP-RTK service account is currently mainly burned manually using the host computer, resulting in low burning efficiency and poor reliability of the PPP-RTK service account. Summary of the invention

[0004] The embodiment of the present application provides an account management method and an account management system. The following introduces various aspects involved in the embodiment of the present application.

[0005] In a first aspect, an account management method is provided, which is applied to a first cloud platform, wherein the first cloud platform is communicatively connected to a vehicle-mounted terminal, and the method comprises: receiving a first request message, wherein the first request message is used to request that the vehicle-mounted terminal be assigned a permission to use a PPP-RTK positioning function; in response to the first request message, selecting a target PPP-RTK service account from a PPP-RTK service account pool of the first cloud platform, and sending the target PPP-RTK service account to the vehicle-mounted terminal for burning.

[0006] As a possible implementation method, the target PPP-RTK service account is any unbound PPP-RTK service account in the PPP-RTK service account pool; the first cloud platform is a PPP-RTK service cloud platform, and the PPP-RTK service account in the PPP-RTK service account pool is used to provide the vehicle-mounted terminal with permission to use the PPP-RTK positioning function.

[0007] As a possible implementation manner, the first request information includes the vehicle VIN code of the vehicle where the vehicle-mounted terminal is located. In selecting the target PPP-RTK service account from the PPP-RTK service account pool of the first cloud platform, the method also includes: binding the target PPP-RTK service account to the vehicle VIN code of the vehicle, and activating the target PPP-RTK service account.

[0008] As a possible implementation manner, after activating the target PPP-RTK service account, the method further includes: starting a PPP-RTK positioning service billing function of the target PPP-RTK service account.

[0009] As a possible implementation method, the first request message is sent by a second cloud platform to the first cloud platform, the second cloud platform is a cloud platform maintained by the manufacturer of the vehicle where the vehicle-mounted terminal is located, and the first cloud platform is communicated with the vehicle-mounted terminal through the second cloud platform.

[0010] As a possible implementation manner, sending the target PPP-RTK service account to the vehicle-mounted terminal for burning includes: sending the target PPP-RTK service account to the vehicle-mounted terminal for burning through the second cloud platform.

[0011] As a possible implementation method, after the target PPP-RTK service account is sent to the vehicle-mounted terminal for burning, the method also includes: receiving a second request information sent from the second cloud platform, the second request information being used to request a query on the account status of the target PPP-RTK service account.

[0012] As a possible implementation manner, after receiving the second request information sent from the second cloud platform, the method also includes: sending target information to the second cloud platform; wherein the target information includes one or more of the following: the usage status of the target PPP-RTK service account; the activation status of the target PPP-RTK service account; the expiration time of the target PPP-RTK service account; the product name of the target PPP-RTK service account; and the frequency type of the target PPP-RTK service account.

[0013] In a second aspect, an account management system is provided, which is applied to a first cloud platform, and the first cloud platform is communicatively connected to a vehicle-mounted terminal, and the account management system includes: a receiving module, which is used to receive a first request message, and the first request message is used to request that the vehicle-mounted terminal be assigned a permission to use a PPP-RTK positioning function; a selection module, which is used to select a target PPP-RTK service account from the PPP-RTK service account pool in response to the first request message, and send the target PPP-RTK service account to the vehicle-mounted terminal for burning.

[0014] In a third aspect, an account management system is provided, comprising a memory for storing computer code; and a processor for executing the code stored in the memory to execute the method as described in the first aspect or any implementation of the first aspect.

[0015] According to a fourth aspect, a computer-readable storage medium is provided, on which an executable code is stored. When the executable code is executed, the method described in the first aspect or any implementation method of the first aspect can be implemented.

[0016] The present application provides an account management method, which is applied to a first cloud platform, the first cloud platform is connected to a vehicle terminal in communication, and the method includes: receiving a first request message, the first request message is used to request the vehicle terminal to be assigned the permission to use the PPP-RTK positioning function; in response to the first request message, selecting a target PPP-RTK service account from the PPP-RTK service account pool, and sending the target PPP-RTK service account to the vehicle terminal for burning. The PPP-RTK service cloud platform (i.e., the first cloud platform) provided by this solution can select a target PPP-RTK service account (such as any unbound account) using the PPP-RTK service cloud platform according to the enabling request of the PPP-RTK positioning service, and send it to the vehicle terminal for self-burning, thereby improving the burning efficiency and reliability of the PPP-RTK service account. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 It is a flowchart of an account management method provided in one embodiment of the present application.

[0018] Figure 2 It is a flowchart of an account management method provided by another embodiment of the present application.

[0019] Figure 3 It is a structural diagram of an account management system provided by an embodiment of the present application.

[0020] Figure 4 It is a structural diagram of an account management system provided by another embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0022] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0023] With the continuous development of GNSS technology, the demand for high-precision positioning in the field of vehicle driving technology is growing. Although traditional GNSS positioning methods can provide basic location information, their positioning accuracy is usually limited to a few meters to tens of meters, which cannot meet the requirements of modern applications for sub-meter or even centimeter-level positioning accuracy.

[0024] In order to improve the positioning accuracy of GNSS, a variety of enhancement technologies have been developed in related technologies. Among them, precise point positioning (PPP) and real-time kinematic positioning (RTK) are two widely used methods. PPP uses precise satellite orbit and clock data to improve positioning accuracy, while RTK further improves positioning accuracy by using differential corrections between the base station and the rover.

[0025] Although PPP and RTK each have significant advantages, they also have certain limitations. PPP can provide high positioning accuracy over a wide area, but due to factors such as atmospheric delay, its accuracy still has room for improvement; and although RTK can achieve centimeter-level positioning accuracy, it is limited by the distance between the base station and the mobile station, which is usually required to be no more than tens of kilometers.

[0026] In order to overcome the above limitations, a new positioning technology combining PPP and RTK has been developed in recent years - Precision Point Positioning Real-time Kinematic (PPP-RTK). PPP-RTK technology aims to utilize the wide-area coverage capability of PPP and the high-precision positioning advantage of RTK to achieve centimeter-level positioning accuracy over a large range through the deployment of network base stations and precise atmospheric models. However, PPP-RTK positioning services are paid. If you want to enable the PPP-RTK positioning service function for vehicles, you need to burn the PPP-RTK service account into the on-board terminal of each vehicle.

[0027] Normally, one vehicle corresponds to one PPP-RTK service account. Currently, the PPP-RTK service account is mainly burned into the vehicle's onboard terminal by the host computer. However, vehicles are mass-produced, and the manual burning of the PPP-RTK service account by the host computer will result in low burning efficiency and poor reliability of the PPP-RTK service account.

[0028] In view of the above problems, the present application provides an account management method, which is applied to a first cloud platform, the first cloud platform is connected to a vehicle terminal in communication, and the method includes: receiving a first request message, the first request message is used to request the allocation of permission to use the PPP-RTK positioning function for the vehicle terminal; in response to the first request message, selecting a target PPP-RTK service account from the PPP-RTK service account pool, and sending the target PPP-RTK service account to the vehicle terminal for burning. The PPP-RTK service cloud platform (i.e., the first cloud platform) provided by this solution can select a target PPP-RTK service account (such as any unbound account) using the PPP-RTK service cloud platform according to the enabling request of the PPP-RTK positioning service, and send it to the vehicle terminal for self-burning, thereby improving the burning efficiency and reliability of the PPP-RTK service account. The management device method in the embodiment of the present application is described in detail below in conjunction with the accompanying drawings.

[0029] Figure 1 A flowchart of an account management method provided in an embodiment of the present application is provided. The method is applied to a first cloud platform, and the first cloud platform is in communication connection with a vehicle-mounted terminal.

[0030] In some implementations, the first cloud platform is a PPP-RTK service cloud platform (i.e., the first cloud platform is a PPP-RTK service cloud platform that manages PPP-RTK service accounts), and the first cloud platform includes a PPP-RTK service account pool. The PPP-RTK service accounts in the PPP-RTK service account pool are used to provide vehicle-mounted terminals with permissions to use the PPP-RTK positioning function.

[0031] It should be understood that the PPP-RTK service account pool may include multiple PPP-RTK service accounts. Each PPP-RTK service account may be used to grant the vehicle terminal the authority to use the PPP-RTK positioning function.

[0032] It should be understood that the first cloud platform can obtain multiple PPP-RTK service accounts from a third cloud platform (such as a cloud platform maintained by an operator of the satellite communication system) to form a PPP-RTK service account pool.

[0033] In some implementations, the first cloud platform may be directly connected to the vehicle terminal. In other implementations, the first cloud platform may also be connected to the vehicle terminal through the vehicle manufacturer's cloud platform. This application does not make specific restrictions on this.

[0034] It should be understood that the vehicle-mounted terminal in the embodiment of the present application may be a vehicle-mounted domain controller, or a vehicle-mounted communication module (such as T-BOX), etc., and the present application does not impose any specific restrictions on this.

[0035] like Figure 1 As shown, the account management method 100 may include steps: S110-S120.

[0036] In step S110, a first request message is received, wherein the first request message is used to request that the vehicle-mounted terminal be assigned a permission to use the PPP-RTK positioning function. That is, the first request can be used to request the first cloud platform to assign a PPP-RTK service account to the vehicle-mounted terminal, so as to enable the PPP-RTK positioning service function for the vehicle where the vehicle-mounted terminal is located.

[0037] In some implementations, the first request message may be sent by the vehicle terminal to the first cloud platform. For example, a software toolkit may be implanted in the vehicle terminal, and then data communication with the first cloud platform is performed through the software toolkit, such as sending the first request message to the first cloud platform through the built-in software toolkit of the vehicle terminal.

[0038] In other implementations, the first request message may be sent by the second cloud platform to the first cloud platform, and the second cloud platform may be a cloud platform maintained by the manufacturer of the vehicle where the vehicle-mounted terminal is located. The communication link between the vehicle-mounted terminal and the first cloud platform may be opened through the second cloud platform, that is, the first cloud platform is connected to the vehicle-mounted terminal through the second cloud platform.

[0039] In some implementations, the first request information may include a vehicle identification number (VIN) of the vehicle in which the vehicle-mounted terminal is located. The vehicle identification number of the vehicle may be referred to as the vehicle VIN code.

[0040] In some implementations, the vehicle terminal may send the vehicle VIN code to the second cloud platform, and then the second cloud platform sends a first request message to the first cloud platform, and the first request message may carry the vehicle VIN code.

[0041] In step S120, in response to the first request information, a target PPP-RTK service account is selected from the PPP-RTK service account pool, and the target PPP-RTK service account is sent to the vehicle terminal for burning.

[0042] It should be noted that the target PPP-RTK service account is any unbound PPP-RTK service account in the PPP-RTK service account pool.

[0043] In some implementations, after selecting a target PPP-RTK service account from the PPP-RTK service account pool, it is necessary to bind the target PPP-RTK service account to the vehicle VIN code of the vehicle, and activate the target PPP-RTK service account. This application does not specifically limit the order of account binding and activation of the PPP-RTK service account.

[0044] For example, you can first bind the account and then activate the account. As an example, you can first bind the target PPP-RTK service account to the vehicle VIN code of the vehicle, and then activate the target PPP-RTK service account separately after binding the PPP-RTK service account.

[0045] For another example, the account can be activated while the account is being bound. As an example, the target PPP-RTK service account can be bound to the vehicle VIN code of the vehicle and the target PPP-RTK service account can be activated at the same time.

[0046] In some implementations, after binding and activating the target PPP-RTK service account, the method further includes: starting a PPP-RTK positioning service billing function of the target PPP-RTK service account.

[0047] In some implementations, sending the target PPP-RTK service account to the vehicle terminal for burning includes: sending the target PPP-RTK service account to the vehicle terminal for burning through the second cloud platform. That is, the first cloud platform can send the target PPP-RTK service account to the second cloud platform, and then the second cloud platform sends the target PPP-RTK service account to the vehicle terminal for self-burning.

[0048] In some implementations, after the target PPP-RTK service account is sent to the vehicle terminal for burning, the method further includes: receiving a second request message sent from the second cloud platform, the second request message being used to request to query the account status of the target PPP-RTK service account. The account status of the target PPP-RTK service account may include, but is not limited to: usage status, activation status, expiration time, product name, and frequency type of the target PPP-RTK service account.

[0049] In some implementations, after receiving the second request information sent from the second cloud platform, the method further includes: sending target information to the second cloud platform, wherein the target information may be reply information of the second request message.

[0050] In some implementations, the target information includes one or more of the following: usage status of the target PPP-RTK service account; activation status of the target PPP-RTK service account; expiration time of the target PPP-RTK service account; product name of the target PPP-RTK service account; and frequency type of the target PPP-RTK service account.

[0051] It should be noted that the usage status of the target PPP-RTK service account includes but is not limited to: the target PPP-RTK service account is in a deactivated state, the target PPP-RTK service account is in a normal state, and the target PPP-RTK service account is in an expired state. In some implementations, in order to facilitate identification of the usage status of the target PPP-RTK service account, a number may be used to represent the usage status of the target PPP-RTK service account. As an example, 0 may be used to represent that the target PPP-RTK service account is in a deactivated state, 1 may be used to represent that the target PPP-RTK service account is in a normal state, and 2 may be used to represent that the target PPP-RTK service account is in an expired state.

[0052] It should be noted that the activation status of the target PPP-RTK service account may be that the target PPP-RTK service account is in an activated state or that the target PPP-RTK service account is in an inactivated state.

[0053] It should be noted that the product name of the target PPP-RTK service account may refer to the product name of the product that provides the PPP-RTK high-precision positioning service product. For example, the product name of the target PPP-RTK service account may be Dayou Shikong or Liufen Technology.

[0054] It should be noted that the frequency type of the target PPP-RTK service account may refer to the frequency signal type of the positioning system used by the PPP-RTK service.

[0055] It should be noted that PPP-RTK positioning services usually use signals from multiple global navigation satellite systems. The global navigation satellite systems used by PPP-RTK positioning services may include but are not limited to the US GPS positioning system, the Russian GLONASS positioning system, the EU GALILEO positioning system, and the Chinese Beidou positioning system. The frequencies of these systems are as follows:

[0056] GPS: L1(1575.42MHz), L2(1227.60MHz), L5(1176.45MHz);

[0057] GLONASS: L1(1602MHz+k*0.5625MHz), L2(1246MHz+k*0.4375MHz);

[0058] Galileo: E1(1575.45MHz), E5a(1176.45MHz), E5b(1207.14MHz), E6(1278.75MHz);

[0059] Beidou: B1I (1561.098MHz), B2I (1207.14MHz), B3I (1268.52MHz).

[0060] The following describes the embodiments of the present application in more detail with reference to specific examples. Figure 2 It is only to help those skilled in the art understand the embodiments of the present application, and is not intended to limit the embodiments of the present application to the specific values ​​or specific scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0061] Figure 2 It is a flowchart of another account management method provided by an embodiment of the present application. The account management method can be applied to a communication system, and the communication system can be a vehicle-mounted terminal, a car factory cloud platform and a PPP-RTK service cloud platform. The car factory cloud platform is respectively connected to the vehicle-mounted terminal and the PPP-RTK service cloud platform.

[0062] It should be understood that the PPP-RTK service cloud platform may refer to the first cloud platform mentioned above, and the car factory cloud platform may refer to the second cloud platform mentioned above.

[0063] See also Figure 2 , the account management method may include steps: S201 to S208.

[0064] In step S201, the vehicle terminal sends the vehicle VIN code of the vehicle in which the vehicle terminal is located to the vehicle manufacturer cloud platform.

[0065] In step S202, the car manufacturer cloud platform sends a binding activation request for the PPP-RTK service account to the PPP-RTK service cloud platform (i.e., the first request message mentioned above), requesting the PPP-RTK service cloud platform to allocate a PPP-RTK service account to the vehicle-mounted terminal. In some implementations, the binding activation request for the PPP-RTK service account may carry the vehicle VIN code information of the vehicle where the vehicle-mounted terminal is located. It should be understood that the car manufacturer cloud platform and the PPP-RTK service cloud platform are interconnected by interface (the car manufacturer cloud platform and the PPP-RTK service cloud platform may be connected through openapi, for example).

[0066] In step S203, after receiving the binding activation request of the PPP-RTK service account, the PPP-RTK service cloud platform selects an unbound target PPP-RTK service account from the corresponding car factory account pool, then binds the target PPP-RTK service account to the vehicle VIN code carried in the binding activation request, and activates the target PPP-RTK service account. In some implementations, after activating the target PPP-RTK service account, the PPP-RTK service billing function corresponding to the target PPP-RTK service account can also be started.

[0067] In step S204, the bound and activated target PPP-RTK service account is sent to the vehicle manufacturer cloud platform through the interface.

[0068] In step S205, the vehicle manufacturer cloud platform sends the target PPP-RTK service account in step S204 to the vehicle terminal.

[0069] In step S206, after receiving the target PPP-RTK service account, the vehicle terminal can self-burn the target PPP-RTK service account.

[0070] In step S207, the car manufacturer cloud platform may send a query request to the PPP-RTK service cloud platform to query the account status information of the target PPP-RTK service account.

[0071] In step S208, in response to the query request of the target PPP-RTK service account, the PPP-RTK service cloud platform feeds back the account status information of the target PPP-RTK service account to the vehicle manufacturer cloud platform.

[0072] In some implementations, the account status information of the PPP-RTK service account includes one or more of the following: usage status of the target PPP-RTK service account; activation status of the target PPP-RTK service account; expiration time of the target PPP-RTK service account; product name of the target PPP-RTK service account; and frequency type of the target PPP-RTK service account.

[0073] It should be noted that the usage status of the target PPP-RTK service account includes but is not limited to: the target PPP-RTK service account is in a disabled state, the target PPP-RTK service account is in a normal state, and the target PPP-RTK service account is in an expired state.

[0074] It should be noted that the activation status of the target PPP-RTK service account may be that the target PPP-RTK service account is in an activated state or that the target PPP-RTK service account is in an inactivated state.

[0075] It should be noted that the product name of the target PPP-RTK service account may refer to the product name of the PPP-RTK high-precision positioning service product.

[0076] It should be noted that the frequency type of the target PPP-RTK service account may refer to the frequency signal type of the positioning system used by the PPP-RTK service.

[0077] According to the above content, it can be seen that the PPP-RTK service cloud platform (i.e., the first cloud platform) provided by this solution can select the target PPP-RTK service account (any unbound account) using the PPP-RTK service cloud platform according to the empowerment request of the PPP-RTK positioning service, and send it to the vehicle-mounted terminal for self-burning, thereby improving the burning efficiency and reliability of the PPP-RTK service account.

[0078] In addition, the PPP-RTK service cloud platform of this solution can realize the functions of issuing, binding, activating, billing, and account status synchronization of PPP-RTK service accounts based on the vehicle-mounted PPP-RTK service business.

[0079] Combination of the above Figure 1 to Figure 2 The method embodiment of the present application is described in detail. Figure 3 to Figure 4 The device embodiment of the present application is described in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0080] Figure 3 FIG. 1 is a schematic diagram of the structure of an account management system provided by an embodiment of the present application. The account management system is applied to a first cloud platform, and the first cloud platform is connected to the vehicle terminal for communication. Figure 3 The account management system 300 may include a receiving module 310 and a selecting module 320 .

[0081] The receiving module 310 is used to receive first request information, where the first request information is used to request that the vehicle-mounted terminal be assigned a permission to use the PPP-RTK positioning function;

[0082] The selection module 320 is used to select a target PPP-RTK service account from the PPP-RTK service account pool of the first cloud platform in response to the first request information, and send the target PPP-RTK service account to the vehicle terminal for burning.

[0083] Optionally, the target PPP-RTK service account is any unbound PPP-RTK service account in the PPP-RTK service account pool; the first cloud platform is a PPP-RTK service cloud platform, and the PPP-RTK service account in the PPP-RTK service account pool is used to provide the vehicle-mounted terminal with permission to use the PPP-RTK positioning function.

[0084] Optionally, the first request information includes the vehicle VIN code of the vehicle where the vehicle-mounted terminal is located, and the account management system 300 also includes: a binding and activation module, which is used to bind the target PPP-RTK service account to the vehicle VIN code of the vehicle after selecting the target PPP-RTK service account from the PPP-RTK service account pool of the first cloud platform, and activate the target PPP-RTK service account.

[0085] Optionally, the account management system 300 further includes: a startup module, configured to start a PPP-RTK positioning service billing function of the target PPP-RTK service account after activating the target PPP-RTK service account.

[0086] Optionally, the first request message is sent by a second cloud platform to the first cloud platform, the second cloud platform is a cloud platform maintained by the manufacturer of the vehicle where the vehicle-mounted terminal is located, and the first cloud platform is communicatively connected with the vehicle-mounted terminal through the second cloud platform.

[0087] Optionally, sending the target PPP-RTK service account to the vehicle-mounted terminal for burning includes: sending the target PPP-RTK service account to the vehicle-mounted terminal for burning through the second cloud platform.

[0088] Optionally, the account management system 300 also includes: a second receiving module, used to receive a second request information sent from the second cloud platform after the target PPP-RTK service account is sent to the vehicle-mounted terminal for burning, and the second request information is used to request to query the account status of the target PPP-RTK service account.

[0089] Optionally, the account management system 300 also includes: a sending module, used to send target information to the second cloud platform after receiving the second request information sent from the second cloud platform; wherein the target information includes one or more of the following: the usage status of the target PPP-RTK service account; the activation status of the target PPP-RTK service account; the expiration time of the target PPP-RTK service account; the product name of the target PPP-RTK service account; and the frequency type of the target PPP-RTK service account.

[0090] Combine the following Figure 4 This is an introduction to an account management system 400 in an embodiment of the present application. The account management system 400 can be used to implement the method described in the above method embodiment.

[0091] The account management system 400 may include one or more processors 410. The processor 410 may support the account management system 400 to implement the method described in the above method embodiment.

[0092] The processor 410 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0093] The account management system 400 may further include one or more memories 420. The memory 420 stores a program that can be executed by the processor 410 to control the account management system 400 to execute the method described in the above method embodiment. The memory 420 may be independent of the processor 410 or integrated in the processor 410.

[0094] The account management system 400 may further include a transceiver 430. The processor 410 may communicate with other devices through the transceiver 430. For example, the processor 410 may transmit and receive data with other devices through the transceiver 430.

[0095] The present application also provides a chip in an embodiment, including a processor, which can be used to call and run a computer program from a memory, so that an account management system equipped with the chip executes the method described in the above method embodiment. It is understood that the processor can be any type of processor mentioned above. It is understood that the memory can be independent of the chip or integrated in the chip.

[0096] The embodiment of the present application also provides a machine-readable storage medium for storing a program, and the program enables a computer to execute the method in each embodiment of the present application.

[0097] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The program enables a computer to execute the method in each embodiment of the present application.

[0098] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a machine-readable storage medium, or transmitted from one machine-readable storage medium to another machine-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The machine-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0099] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments of the present disclosure can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present disclosure.

[0100] In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0101] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0102] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0103] The above is only a specific embodiment of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present disclosure, which should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. An account management method, characterized in that: The method is applied to a first cloud platform, the first cloud platform is in communication connection with the vehicle terminal, The method comprises: Receiving first request information, where the first request information is used to request that the vehicle-mounted terminal be assigned a permission to use a PPP-RTK positioning function; In response to the first request information, a target PPP-RTK service account is selected from the PPP-RTK service account pool of the first cloud platform, and the target PPP-RTK service account is sent to the vehicle terminal for burning.

2. The method according to claim 1, characterized in that The target PPP-RTK service account is any unbound PPP-RTK service account in the PPP-RTK service account pool; The first cloud platform is a PPP-RTK service cloud platform, and the PPP-RTK service account in the PPP-RTK service account pool is used to provide the vehicle-mounted terminal with permission to use the PPP-RTK positioning function.

3. The method according to claim 1, characterized in that The first request information includes a vehicle VIN code of the vehicle where the vehicle-mounted terminal is located. After selecting a target PPP-RTK service account from the PPP-RTK service account pool of the first cloud platform, the method further includes: The target PPP-RTK service account is bound to the vehicle VIN code of the vehicle, and the target PPP-RTK service account is activated.

4. The method according to claim 3, characterized in that After activating the target PPP-RTK service account, the method further includes: The PPP-RTK positioning service billing function of the target PPP-RTK service account is started.

5. The method according to any one of claims 1 to 4, characterized in that The first request message is sent by a second cloud platform to the first cloud platform, the second cloud platform is a cloud platform maintained by the manufacturer of the vehicle where the vehicle-mounted terminal is located, and the first cloud platform is communicatively connected with the vehicle-mounted terminal through the second cloud platform.

6. The method according to claim 5, characterized in that The sending of the target PPP-RTK service account to the vehicle-mounted terminal for burning includes: The target PPP-RTK service account is sent to the vehicle-mounted terminal through the second cloud platform for burning.

7. The method according to claim 5, characterized in that After sending the target PPP-RTK service account to the vehicle-mounted terminal for burning, the method further includes: A second request message sent from the second cloud platform is received, where the second request message is used to request to query the account status of the target PPP-RTK service account.

8. The method according to claim 7, characterized in that After receiving the second request information sent from the second cloud platform, the method further includes: Sending target information to the second platform; The target information includes one or more of the following: The usage status of the target PPP-RTK service account; The activation status of the target PPP-RTK service account; The expiration date of the target PPP-RTK service account; The product name of the target PPP-RTK service account; The frequency type of the target PPP-RTK service account.

9. An account management system, characterized in that: The account management system is applied to a first cloud platform, and the first cloud platform is connected to the vehicle terminal for communication. The account management system includes: A receiving module, used for receiving first request information, where the first request information is used for requesting to allocate permission for the vehicle-mounted terminal to use the PPP-RTK positioning function; The selection module is used to select a target PPP-RTK service account from the PPP-RTK service account pool of the first cloud platform in response to the first request information, and send the target PPP-RTK service account to the vehicle-mounted terminal for burning.

10. An account management system, characterized in that: include: A memory for storing codes; A processor, configured to execute the code stored in the memory to perform the method according to any one of claims 1 to 7.

Images