Information transmission method, system and related device

Abstract

The invention provides an information transmission method, system and related device, and the information transmission method comprises the steps: associating a unique identity identification code of a mobile terminal with a new serial number in a cloud server of the mobile terminal; and the mobile terminal is registered as trusted equipment of a third-party application manufacturer in a cloud server of the third-party application by using the new serial number. In this way, the mobile terminal can successfully flow the data in the third-party application to the interface corresponding to the service of the mobile terminal through the path of the third-party application, the cloud server of the third-party application, the cloud server of the mobile terminal and the service interface of the mobile terminal. The risk that the unique identity identification code of the mobile terminal is leaked is reduced, and the data security is improved.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to an information transmission method, system and related devices. Background Art

[0002] With the development of the automobile industry, the role of automobile media functions in people's lives is becoming more and more important. The demand for the linkage between mobile phones and car computers is increasing, and users often transfer information between mobile phones and car computers across devices. For example, after a user receives location information sent by a friend in a social software on a mobile phone, the user can further transfer the location information to the car computer through user operations, and the car computer provides navigation services to the user.

[0003] However, the cross-device transmission of information involves the data flow between multiple different manufacturers such as mobile phones, car computers and third-party applications, which can easily lead to the leakage of user or manufacturer privacy data. Therefore, it is necessary to study more secure methods for cross-device information transmission. Summary of the invention

[0004] The purpose of the present application is to provide an information transmission method, system and related device. The information transmission method associates the unique identification code of the mobile terminal with a new serial number in the cloud server of the mobile terminal, and uses the new serial number to register the mobile terminal as a trusted device of the third-party application manufacturer in the cloud server of the third-party application. In this way, the mobile terminal can successfully transfer the data in the third-party application to the interface corresponding to the service of the mobile terminal through the path of third-party application-cloud server of third-party application-cloud server of mobile terminal-service interface of mobile terminal. While accessing the data of the third-party application in compliance with regulations, the risk of leakage of the unique identification code of the mobile terminal is reduced, and the security of the data is improved.

[0005] The above-mentioned and other objects are achieved by the features of the independent claims. Further implementations are reflected in the dependent claims, the description and the drawings.

[0006] In a first aspect, the present application provides a method for transmitting information, including: a first cloud server receives first information sent by a second cloud server, the first information includes a first serial number and first target information obtained by the second cloud server from a first application on a first device, the first cloud server is a cloud server serving the first device, the first serial number is a trusted device serial number registered in the second cloud server, and the first serial number is associated with the first device; the first cloud server determines a unique identity code of the first device associated with the first serial number, and sends the first target information to the first device based on the unique identity code of the first device.

[0007] The first serial number is the trusted device serial number of the first device in the second cloud server. That is to say, the first serial number can replace the unique identifier of the first device (such as SN, IMEI, UDID) as the trusted device serial number of the second cloud server in the second cloud server, and the unique identifier of the first device does not exist in the second cloud service. In addition, in order to be able to send the first target information to the first device instead of other devices, the first serial number is associated with the first device in the first cloud server. This association is unique, that is, in the first cloud server, the only device associated with the first serial number is the first device. Therefore, after obtaining the first serial number and the first target information sent by the second cloud server, the first cloud server can determine the first device associated with the first serial number based on the first serial number, and send the first target information to the first device.

[0008] Specifically, there may be a first interface on the first device, and the first interface may communicate with the first cloud server to receive the first target information sent by the first cloud server.

[0009] In this method, the unique identifier of the first device does not need to be sent as a registration number to the cloud servers opened by other manufacturers (manufacturers other than the manufacturer of the first device), and the first device can still be registered as a trusted device of the second cloud server. While accessing the data of third-party applications in compliance with regulations, the risk of leakage of the unique identity identification code of the first device is reduced, and the security of the privacy data of users and manufacturers is improved.

[0010] In combination with the first aspect, in a possible implementation, before the first cloud server receives the first target information sent by the second cloud server, the method also includes: the first cloud server sends second information to the second cloud server, the second information is used to register the trusted device serial number of the second cloud server, the second information includes the first serial number; the first serial number is associated with the unique identity code of the first device.

[0011] It is understandable that after receiving a device's registration application in the cloud server opened by some third-party application manufacturers, it may take several days to process the registration application. Before the registration application is accepted, the device cannot obtain data from the cloud server opened by the third-party application manufacturer through the cloud server serving it.

[0012] However, before the manufacturer of the first device produces the device of this model for the first time and officially sells it out of the factory, the device of this model needs to be released, and this stage generally takes a few days. Therefore, during this period of time (i.e., the time before the first device is produced and sold out of the factory), the first cloud server can first use the serial number in the second information to register in the second cloud server. After receiving the above second information, the second cloud server can determine the serial number in the second information as a trusted device serial number. Specifically, the second information may include the first serial number and multiple serial numbers,

[0013] Specifically, since the serial number in the second information needs to be assigned to the above-mentioned first device and devices with the same signal as the above-mentioned first device in a subsequent process, and replace the unique identification codes (such as SN, UDID, IMEI) of these devices to be registered in the second cloud server, therefore, in the above-mentioned second information, any two serial numbers are different.

[0014] When the device is sold to the user, the serial number in the second information has also been successfully registered as the trusted device serial number of the second cloud server. That is to say, in the subsequent use of the user, the first device or the device of the same model as the first device can use the device's unique identification code (such as SN, UDID, IMEI) to directly associate with the serial number in the second information in the first cloud server with the user's authorization, and immediately register as a trusted device of the second cloud server based on the associated serial number, without having to wait for a long time for the second cloud server to accept it again.

[0015] In combination with the first aspect, in a possible implementation, after the first cloud server sends the second information to the second cloud server, the method also includes: the first cloud server obtains a first verification code from the second cloud server based on a second serial number, and the second serial number is a serial number associated with the first serial number in the first cloud server and the second cloud server; the first cloud server sends the first verification code to the first device based on the first serial number associated with the second serial number, and the unique identity code of the first device associated with the first serial number.

[0016] In order to successfully transfer the information from the first application to the first device, it is necessary to indirectly associate the account logged into the first application on the first device with the unique identification code of the first device, so that when the first target information is transferred through the path of third-party application-cloud server of third-party application-cloud server of mobile terminal-service interface of mobile terminal, the first target information can be accurately transferred to the interface of the first device. Therefore, in this method, the first cloud server can obtain the first verification code from the second cloud server based on the second signal, and the second serial number is associated with the first serial number in both the first cloud server and the second cloud server; after obtaining the first verification code, the first cloud server can send the first verification code to the first device based on the first serial number associated with the second serial number and the unique identification code of the first device associated with the first serial number; thereafter, the first device can verify the verification code through the first application on which the first account is logged in, obtain the second serial number corresponding to the verification code, and associate the second serial number with the first account. In this way, when the second cloud server obtains the first target information from the second application, the second cloud server can determine the second serial number associated with the first account, and determine the associated first serial number based on the second serial number, and send the target information to the first cloud server based on the first serial number. The first cloud server can then accurately push the first target information to the first device based on the unique device identification code of the first device associated with the first serial number.

[0017] In combination with the first aspect, in a possible implementation, the second information includes a first serial number set and a second serial number set, the serial numbers in the first serial number set are serial numbers that have been associated with the device's unique identity identification code, and the serial numbers in the second serial number set are serial numbers that are not associated with the device's unique identity identification code. The method also includes: when the proportion of serial numbers in the first serial number set in all serial numbers in the second information is greater than a first threshold, the first cloud server sends third information to the second cloud server, the third information is used for registration of trusted device serial numbers of the second cloud server, and any serial number in the second information is not included in the third information.

[0018] Since each serial number in the second information can only register one device as a trusted device of the second cloud server, when more and more devices of the same model as the first device are registered as trusted devices of the second cloud server, the available serial numbers in the second information (i.e., the serial numbers in the second serial number set) will become fewer and fewer. The manufacturer of the first device is likely to produce and sell the same model of the first device again, and since the subsequent production is not the first batch, the manufacturer is unlikely to release or promote the device of this model again.

[0019] Therefore, in this embodiment, in order to prevent other devices from being unable to quickly register as trusted devices of the second cloud server due to insufficient available serial numbers in the second information, the first cloud server can detect the number of unavailable serial numbers (i.e., serial numbers in the first serial number set) in the second information. When the proportion of the number of unavailable serial numbers to all serial numbers in the second information is greater than the first threshold, the first cloud server can generate third information and register the serial numbers in the third information as trusted device serial numbers of the second cloud server in the same manner as in the above description. Optionally, the above first threshold can be set to 80%, or it can be set to other values, which is not limited in this application. Specifically, any two serial numbers in the third information are different, and any serial number in the third information is not included in the above second information.

[0020] It is understandable that in the subsequent process, if the manufacturer of the first device continues to mass-produce the device of this model, the first cloud server can control the first cloud server to always have an available trusted device number, so as to facilitate the rapid registration of the device as a trusted device of the second cloud server. In addition, in addition to preventing the leakage of the device's unique identity identifier and causing the device to be monitored, this method can also effectively prevent the manufacturer's production data (such as the total production volume of a certain model of equipment) from being known to other manufacturers, while protecting the privacy of users and the security of the manufacturer's production data.

[0021] In combination with the first aspect, in a possible implementation, the method also includes: the first cloud server receives fourth information sent by the second cloud server, the fourth information includes the first serial number and information obtained by the second cloud server from the first application on the second device, and the account used to log in to the first application on the first device is different from the account used to log in to the first application on the second device; the first cloud server determines the unique identity code of the first device associated with the first serial number, and sends the fourth information to the first device based on the unique identity code of the first device.

[0022] In the actual driving process, there is also a scenario where the first device used by the driver of the vehicle has established a communication connection with the vehicle terminal, and the driver has used the second serial number to log in to the first application on the first device. However, since the driver is driving, for safety reasons, it is inconvenient for the driver to perform user operations on the first target information on the first device. If the location information required by the driver for navigation at this time exists in a group constructed by multiple users of the first application (for example, If the driver is traveling with a friend group or family group in the group, or the location information required by the driver for navigation exists in the first application logged in with other accounts on other devices, the safest and quickest solution is for other users to transfer the location information to the first device, and the travel service of the first device processes it.

[0023] Therefore, in this embodiment. That is to say, the second serial number can be associated with multiple login accounts of the first application. However, in the second cloud server, the trusted device number associated with the second serial number is still only the first serial number; and in the first cloud server, the device unique identification code associated with the first serial number is also only associated with the unique identification code of the first device. In this way, in the subsequent process, in addition to the driver, the second account user associated with the second serial number can also use his own device (such as the second device) to operate the second target information in the first application logged in to the second account on the second device, and transfer the second target information to the service interface of the first device held by the driver, and further flow to the second application on the first device, and transfer the navigation information generated by the second application for the second target information to the vehicle terminal through the travel service, and output by the vehicle terminal to improve the safety of the user's driving process.

[0024] In a second aspect, the present application provides an information transmission system, the system comprising a first device, a first cloud server, and a second cloud server; wherein a first application is installed in the first device, the first cloud server is a cloud server serving the first device, and the second cloud server is a cloud server serving the first application; in the first cloud server, the unique identity code of the first device is associated with a first serial number, and the first serial number is associated with a second serial number; in the second cloud server, the first serial number is associated with the second serial number, the first serial number is the serial number of a trusted device registered in the second cloud server, and the account for logging into the first application on the first device is associated with the second serial number, wherein: the first device is used to send the first target information and the second serial number to the second cloud server through the first application under the operation of the first target information in the first application; the second cloud server is used to determine the first serial number associated with the second serial number, and send the first information to the first cloud server, the first information including the first serial number and the first target information; the first cloud server is used to send the first target information to the first device based on the unique identity code of the first device associated with the first serial number.

[0025] In combination with the second aspect, in a possible implementation, the first cloud server is also used to send second information to the second cloud server, the second information is used to register the trusted device serial number of the second cloud server, the second information includes multiple serial numbers, and the multiple serial numbers include the first serial number; the second cloud server is also used to register all of the multiple serial numbers as trusted device serial numbers.

[0026] In combination with the second aspect, in a possible implementation, the first device is also used to send the unique identity code of the first device to the first cloud server; the first cloud server is also used to associate the unique identity code of the first device with the first serial number; the second cloud server is also used to associate the first serial number with the second serial number, and send the association between the first serial number and the second serial number to the first cloud server; the first cloud server is also used to apply for a verification code from the second cloud server based on the second serial number associated with the first serial number; the second cloud server is also used to generate a first verification code associated with the second serial number based on the second serial number, and send the first verification code to the first cloud server based on the first serial number associated with the second serial number; the first cloud server is also used to send the first verification code to the first device based on the unique identity code of the first device associated with the first serial number; the first device is also used to obtain the second serial number under the operation of the first verification code through the first application, and associate the second serial number with the account logged in to the first application on the first device.

[0027] In combination with the second aspect, in a possible implementation, the second information includes multiple serial numbers, the multiple serial numbers include a first serial number set and a second serial number set, the serial numbers in the first serial number set are serial numbers that have been associated with the device's unique identity identification code, and the serial numbers in the second serial number set are serial numbers that are not associated with the device's unique identity identification code; when the proportion of serial numbers in the first serial number set in all serial numbers in the second information is greater than a first threshold, the first cloud server is also used to send third information to the second cloud server, and any serial number in the second information is not included in the third information; the second cloud server is also used to register the serial numbers in the third information as trusted device serial numbers.

[0028] In combination with the second aspect, in a possible implementation, the information transmission system also includes a second device, the second device and the first device are devices produced by the same manufacturer, the second device is installed with the first application, the second device is used to obtain the second serial number by operating the first verification code through the first application, and associate the second serial number with the account logged into the first application on the second device; the second device is also used to send fourth information to the second cloud server through the first application under the operation of the second target information in the first application, the fourth information includes the second target information and the second serial number; the second cloud server is also used to determine the first serial number associated with the second serial number, and send the first serial number and the second target information to the first cloud server; the first cloud server is also used to send the second target information to the first device based on the unique identity code of the first device associated with the first serial number.

[0029] In combination with the second aspect, in a possible implementation, the system also includes a third device, which is communicatively connected to the first device, and a second application is also installed in the first device, and the second application is an application with a navigation function; the first device is also used to send the first target information to the second application through a first interface, and obtain navigation information generated for the first target information based on the second application through the first interface, and the navigation information includes a navigation route map and / or the navigation prompt sound; the first device is also used to send the navigation information to the third device; the third device is used to output navigation information.

[0030] In combination with the second aspect, in a possible implementation, the information transmission system also includes a third device, which is communicatively connected to the first device, and a second application is installed in the third device, and the second application is an application with a navigation function; the first device is also used to send the first target information to the third device; the third device is used to send the first target information to the second application through a second interface, and output navigation information generated by the second application for the second location information, and the navigation information includes a navigation route map and / or a navigation prompt sound.

[0031] The beneficial effects of the system in the second aspect and any possible implementation of the second aspect provided in the present application can refer to the beneficial effects of the method in the first aspect or any possible implementation of the first aspect, which will not be repeated here.

[0032] In a third aspect, the present application provides an electronic device, comprising: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute the method in the first aspect or any possible implementation of the first aspect.

[0033] In a fourth aspect, the present application provides a chip system, which is applied to an electronic device, and the chip system includes one or more processors, and the processor is used to call computer instructions so that the electronic device executes a method as in the first aspect or any possible implementation of the first aspect.

[0034] In a fifth aspect, the present application provides a computer-readable storage medium comprising instructions, which, when executed on an electronic device, enables the electronic device to execute a method in the first aspect or any possible implementation of the first aspect.

[0035] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed on an electronic device, enables the electronic device to execute a method in the first aspect or any possible implementation of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 A user interface diagram provided for an embodiment of the present application;

[0037] Figure 2 A system architecture diagram for transferring information through an end-to-end path provided in an embodiment of the present application;

[0038] Figure 3 A system architecture diagram for transferring information through a device-cloud-cloud-device path provided by this application;

[0039] Figure 4 A flowchart of an information transmission method provided by this application;

[0040] Figure 5 A system architecture diagram for transferring information through a device-cloud-cloud-device path provided by this application;

[0041] Figure 6 A flowchart of an information transmission method provided by this application;

[0042] Figure 7 A system architecture flowchart provided for this application;

[0043] Figure 8A system architecture diagram for supporting multiple users to associate with the same second serial number provided by the present application;

[0044] Fig. 9 A structural diagram of an electronic device provided in this application. DETAILED DESCRIPTION

[0045] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to be used as limitations to the present application. As used in the specification and appended claims of the present application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include plural expressions, unless there is a clear indication to the contrary in the context. It should also be understood that the term "and / or" used in the present application refers to and includes any or all possible combinations of one or more listed items.

[0046] Since the embodiments of the present application involve the application of neural networks, for ease of understanding, the relevant terms involved in the embodiments of the present application are first introduced below.

[0047] (1) Vehicle-to-machine interconnection protocol

[0048] The car-machine interconnection protocol refers to the protocol system used for data exchange between the vehicle terminal and the mobile terminal. It can support users to project the content in their mobile phones to their car-machine terminals, making it convenient for users to use some simple applications while driving. The mainstream car-machine protocols mainly include CarPlay, CarLife, Hicar, CarWith, etc.

[0049] Take CarLife as an example. CarLife is the first cross-platform Internet of Vehicles solution in China. On the car side, CarLife can adapt well to Linux, QNX or Android. On the user side, CarLife can support both Android and iOS operating systems, covering more than 95% of smartphone users. Compared with other Internet of Vehicles products, CarLife does not require the operating system of smartphones. It only needs to connect the phone to the car via a data cable or Wi-Fi, and you can use a variety of applications safely and quickly while driving.

[0050] (2) Travel services

[0051] Travel service is a service provided by mobile terminals such as mobile phones and tablets to facilitate users to better plan travel routes and quickly reach their destinations. It can include bus inquiries, map navigation, carpooling services and other functions. Among them, the map navigation function can connect the mobile phone or tablet to the vehicle through the vehicle-machine interconnection protocol. After completing the communication connection between the two, the user can project the application on the mobile phone to the vehicle-machine screen and operate all the functions on the screen through intelligent voice control; more typically, it can also share the location information in the third-party application in the mobile phone to the vehicle-machine, and easily connect the navigation path between the mobile phone and the vehicle-machine. The vehicle-machine can also transfer the walking navigation flow back to the original mobile phone map application, providing drivers and passengers with a safer, more convenient and more efficient travel experience, and helping to reduce traffic congestion and improve road safety.

[0052] (3) Product serial number, unique identification code, international mobile equipment identity code, mobile equipment identity code

[0053] The product serial number (SN) is the product ID number, also known as the machine code, authentication code, registration application code, etc. The product serial number is a concept introduced to verify the "legal identity of the product". It is used to protect the user's genuine rights and interests and enjoy legal services; a genuine product corresponds to only one product serial number.

[0054] The unique device identifier description (UDID) is a 40-character string of letters and numbers that is used to distinguish each unique iOS device, including iPhones, iPads, and iPod touches. The UDID can be associated with various other data associated with the device. For example, the UDID can be connected to a developer account, allowing the device to install or test applications before release. In the early days of iOS applications, UDID was used by third-party application developers and online advertisers to collect user data, and could be used to associate addresses, record application usage habits, etc.

[0055] The international mobile equipment identity (IMEI), commonly known as the mobile phone serial number or "serial number", is used to identify each independent mobile phone and other mobile communication devices in the mobile phone network. It is equivalent to the ID card of the mobile phone. The serial number has 15 to 17 digits. The first 8 digits (TAC) are the model approval number (6 digits in the early days), which is the code to distinguish the brand and model of the mobile phone. The next 2 digits (FAC) are the final assembly number (only exists in early models), representing the final assembly location code. The last 6 digits (SNR) are the serial number, representing the production sequence number. The last digit (SP) is generally 0, which is the inspection code for backup.

[0056] Mobile equipment identifier (MEID), MEID is the identification code of a CDMA mobile phone and is also the unique identification code of each CDMA mobile phone or communication tablet.

[0057] Electronic manufacturers that operate legally in the market will set up an identification code for electronic devices such as mobile phones and tablets when producing electronic devices, such as the SN, UDID, IMEI, etc. mentioned in the above description. These numbers are equivalent to the ID number of the mobile phone. Through these identification codes, the network can monitor and supervise the corresponding mobile phone.

[0058] (4) Cloud Server

[0059] Cloud server (also known as cloud server or cloud host) is a host product in the cloud computing service system. This product effectively solves the defects of difficult management and weak business scalability in traditional physical hosts and VPS services. In actual applications, the business scale of cloud servers can be configured according to user needs and can be flexibly adjusted.

[0060] Since the cloud server may store the user data and production data of the corresponding manufacturer, the cloud server opened by one manufacturer cannot be unconditionally accessed by other manufacturers. For example, when a device needs to access a cloud server opened by a manufacturer other than the manufacturer of the device, the device may need to register with the cloud server first and become a trusted device of the cloud server before it can successfully access the cloud server and obtain the data stored in the cloud server.

[0061] With the development of the automobile industry, automobile media functions play an increasingly important role in people's lives. The demand for the linkage between mobile phones and car computers is increasing, and users often transfer information between mobile phones and car computers across devices. For example, after a user receives location information sent by a friend in a social application on a mobile phone, in order to quickly navigate the information on the social application, the user can transfer the location information in the social application to the travel service through relevant operations, and further transfer the location information to the car terminal through the corresponding interface inside the mobile phone through user operations, and provide navigation services to the user through the car computer; or, it can also flow to the map application through the corresponding interface inside the mobile phone for navigation, and send the navigation image and navigation prompt sound to the car terminal through car-machine interconnection protocols such as Carlife and Hicar, and the car terminal will output the navigation information.

[0062] like Figure 1As shown, the mobile terminal 10 can be a device with data transceiving function, such as a mobile phone, a tablet computer, a wearable device, etc., and the vehicle terminal 11 can be a terminal with data transceiving function and a display screen on the vehicle. The mobile terminal 10 and the vehicle terminal 11 can establish a communication connection through a connection method supported by the vehicle-machine interconnection protocol (such as Wi-Fi, Bluetooth).

[0063] When the mobile terminal 10 and the vehicle-mounted terminal 11 establish a communication connection, data can be sent and received between the mobile terminal 10 and the vehicle-mounted terminal 11. Figure 1 As shown in (A), user interface 01 is a third-party application As can be seen from the user interface 01, after receiving the location information 011 sent by the friend "Xiao Ming", the user can long press the location information 011, and the mobile terminal 10 can respond to the user operation and display the function option box 012 in the user interface 01. Further, the user can click the "Open" control in the function option box 012 to make the mobile terminal display the following Figure 1 The user interface 02 shown in (B) in FIG. 1 includes a device option box 021. The mobile terminal 10 can respond to a user's click operation on the device icon 0211 by using a map application. Navigate the location information 011, and send the relevant navigation data (such as navigation route map and navigation prompt sound) to the vehicle terminal 11, which displays the navigation route map and broadcasts the navigation prompt sound. Figure 1 As shown in (C), the user interface 03 is the interface displayed after the vehicle terminal 11 receives the navigation data sent by the mobile terminal 10, wherein the navigation route map 031 is the third-party application in the mobile terminal 10 A route map generated based on location information 011.

[0064] Although users only need to perform simple user operations to navigate based on the above-mentioned location information and send navigation data from the mobile terminal 10 to the vehicle-mounted terminal 11, the data needs to flow between products provided by multiple different manufacturers (including mobile terminal manufacturers, vehicle-mounted terminal manufacturers, third-party application manufacturers, etc.) during the entire process, which can easily cause data leakage, which will not only bring security risks to the data management process of each manufacturer, but may also endanger the privacy security of users.

[0065] Figure 2 and Figure 3 Two system architecture diagrams for realizing the above-mentioned cross-device information flow are shown respectively.

[0066] like Figure 2As shown, the vehicle system 20 includes a mobile terminal 201 and a vehicle terminal 202, and the mobile terminal 201 and the vehicle terminal 202 are connected to each other through a vehicle interconnection protocol (such as CarPlay, CarLife, Hicar). Among them: the mobile terminal 201 is installed with a map application that provides navigation functions for users, and The vehicle-mounted terminal 202 includes a display screen (liquid crystal display, LCD) and a speaker (Speaker, SPK).

[0067] Combined with the above description, it can be known that when the mobile terminal 201 and the vehicle terminal 202 establish a communication connection, the user can provide the location information sent or received in the third-party application to the map application on the mobile terminal 201 through relevant user operations on the mobile terminal 201, navigate based on the location information in the map application, and send the relevant navigation data to the vehicle terminal 202, which displays the navigation route map and broadcasts the navigation prompt tone to the user. In the vehicle system provided in this embodiment, when the user performs a user operation on the location information in the third-party application on the mobile terminal 201 (for details, please refer to the above Figure 1 ), the mobile terminal 201 can use the corresponding application programming interface (API) to obtain the above location information from the third-party application, and after pushing it to the travel service, further send the location information to the map application through the corresponding API. Then the map application can navigate based on the location information and send the navigation data to the vehicle terminal 202 through the travel service.

[0068] In the vehicle system 20 provided in the embodiment of the present application, although the location information has no output in the entire data flow process (that is, the location information only flows in the application and service functions of the mobile terminal 201, and does not flow from the mobile terminal 201 to the vehicle terminal 202), the location information is chat data in a third-party application, and the manager and controller of the data is actually the manufacturer of the third-party application. It is understandable that the mobile terminal 201, as the processor of the data, directly obtains the above-mentioned location information from the third-party application through the API interface without reasonable authorization from the manufacturer of the third-party application. This information flow method has compliance risks and may cause the data managed by the third-party application manufacturer to be leaked. In addition, some mobile terminals do not provide an API for directly obtaining information data from third-party applications, so the applicability of this information flow method is also poor.

[0069] Figure 3The vehicle computer system shown in the figure adopts another information flow method. Figure 3 As shown, the vehicle system 30 includes a mobile terminal 301 and a vehicle terminal 302. The specific contents of the mobile terminal 301 and the vehicle terminal 302, as well as the specific working methods in the data flow process, can refer to the aforementioned Figure 1 as well as Figure 2 The relevant instructions will not be repeated here.

[0070] It should be noted in advance that in the vehicle system 30 provided in the embodiment of the present application, the mobile terminal 301 can use its own unique identification code (such as SN, UDID, IMEI, etc. in the above description) to register in the cloud server 303 opened by the manufacturer of the third-party application, so that the mobile terminal 301 becomes a trusted device of the third-party application manufacturer; specifically, when the user uses the travel service in the mobile terminal 301 for the first time, the mobile terminal 301 can send the unique identification code to the cloud server 304 opened by the manufacturer of the mobile terminal 301, and the cloud server 304 sends the unique identification code to the cloud server 303 for registration. When the user performs a user operation on the location information in the third-party application on the mobile terminal 301, the third-party application can first send the location information to the cloud server 303 opened by the manufacturer of the third-party application, and the cloud server 303 can send the above location information to the cloud server 304, and the cloud server 304 further sends it to the mobile terminal 301. After that, the mobile terminal 301 can push the location information to the travel service and send the location information to the map application through the corresponding API. The map application can then perform navigation based on the location information and send the navigation data to the vehicle terminal 302 through the travel service.

[0071] For the vehicle system 30 provided in the embodiment of the present application, during the entire data flow process, the cloud server 303 of the third-party application manufacturer needs the unique identifier (such as SN, UDID, IMEI, etc. in the above description) provided by the mobile terminal 301 to be registered as a trusted device, and the cloud server 303 will allow the cloud server opened by the manufacturer of the mobile terminal 301 to access it. Only in this way can the location information in the third-party application be successfully pushed to the travel service of the mobile terminal 301 through the cloud server 303 and the cloud server 304. In other words, the unique identifier of the mobile terminal 301 exists not only in the cloud server (such as cloud server 303) opened by its manufacturer, but also in the cloud server (such as cloud server 304) opened by other manufacturers. However, once the unique identifier of the terminal, such as SN, UDID, etc., is provided to other manufacturers, then other manufacturers may monitor and supervise the terminal, endangering the privacy and security of users.

[0072] Of course, in some embodiments, the user can also install the above-mentioned third-party application on the mobile terminal and the vehicle terminal at the same time, and log in to the account in the third-party application on both terminals, so that the location information in the mobile terminal can be forwarded to the vehicle terminal, and the vehicle terminal can process it. However, this information transmission method requires the installation of third-party applications and map applications on the vehicle terminal, and requires the vehicle terminal to have access to the data network, which requires the user to perform more complex operations to complete. In addition, directly transferring the location information to the vehicle computer may leave the location information on the vehicle computer, resulting in the leakage of the user's personal whereabouts information.

[0073] In response to the above method, the present application provides an information transmission method, which associates the unique identity identification code of the mobile terminal with a new serial number in the cloud server of the mobile terminal, and uses the new serial number to register the mobile terminal as a trusted device of the third-party application manufacturer in the cloud server of the third-party application. In this way, the mobile terminal can successfully transfer the data in the third-party application to the interface corresponding to the service of the mobile terminal through the path of third-party application-cloud server of third-party application-cloud server of mobile terminal-travel service (interface) of mobile terminal, and can further flow to the map application or to the vehicle-mounted terminal connected to the mobile terminal for communication. While accessing the data of the third-party application in compliance with regulations, the risk of leakage of the unique identity identification code of the mobile terminal is reduced, thereby improving the security of the data.

[0074] Next, combine Figure 4 as well as Figure 5 The information transmission method provided in this application is described.

[0075] like Figure 4 As shown, the information transmission method provided in the embodiment of the present application may include the following steps:

[0076] S101. A first cloud server receives first information sent by a second cloud server.

[0077] The first information includes a first serial number and first target information obtained by the second cloud server from a first application on a first device, the first cloud server is a cloud server serving the first device, and the first serial number is a trusted device serial number registered in the second cloud server. In the first cloud server, the first serial number is associated with the first device.

[0078] Specifically, the second cloud server is a cloud server serving the first application. In the second cloud server, the first serial number is associated with the second serial number, and the second serial number is associated with the account for logging into the first application on the first device (hereinafter referred to as the first account). Optionally, the association between the second serial number and the account for logging into the first application on the first device may exist in the second cloud server, or in the first application logged into the first account. The first target information may be obtained from the first application on the first device by the second cloud server based on the association between the second serial number and the first account.

[0079] The first cloud server may be a public cloud server, a hybrid cloud server, or other types of cloud servers. Specifically, the first cloud server may also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms, and this application does not limit this.

[0080] The first device may be a mobile phone, a tablet computer, a wearable device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, etc., and the present application does not impose any restrictions on the specific type of the electronic device. Specifically, the unique identification code of the first device may be the SN, UDID, IMEI, etc. of the first device, which may be used to uniquely determine the identity information of the first electronic device and may be used to monitor and supervise the first device. The first application installed in the first device may be Super applications that can provide users with a variety of services.

[0081] In the process of transferring the first target information from the first application to the first cloud server, the user can operate the first target information in the first application through the first device (for details, please refer to Figure 1 ), so that the second cloud server obtains the first target information from the first application of the first device.

[0082] It is understandable that when a user uses the first application on the first device, he needs to log in to the first application with an account before he can use the first application normally. The account used by the user to log in to the first application on the first device (i.e., the first account) is associated with the second serial number in the second cloud server, and the association may exist on the first application logged in with the first account and / or in the second cloud server.

[0083] When the association between the first account and the second serial number exists on the second cloud server, the user can operate the application data (such as address information) in the first application on the first device, and send the first account and the application data to the second cloud server. The second cloud server can send the first serial number and the application data to the first cloud server through the association between the first account and the second serial number, and the association between the first serial number and the second serial number. The first cloud server can further send the application data to the service interface of the first device through the association between the first serial number and the unique identity code of the first device.

[0084] When the association relationship between the first account and the second serial number exists in the first application logged in with the first account, when sending the application data in the first application to the second cloud server, the first application may not communicate with the second cloud server through the first account, but use the second serial number as a temporary account to replace the first account to communicate with the second cloud server; that is, the user can operate the application data in the first application on the first device, and send the second serial number and the application data to the second cloud server, and the second cloud server can send the first serial number and the application data to the first cloud server through the association relationship between the first serial number and the second serial number, and the first cloud server can further send the application data to the service interface of the first device through the association relationship between the first serial number and the unique identity code of the first device, so as to avoid leakage of user accounts.

[0085] Therefore, when the second cloud server obtains the first target information from the first application of the first device, the second cloud server determines to obtain the first account and determines the second account associated with the first account (or the cloud server can also directly obtain the second serial number from the first application), and further determines the first serial number associated with the second serial number based on the second serial number. Afterwards, the second cloud server can send the first serial number and the first target information (that is, the first information) together to the first cloud server.

[0086] It should be noted that the association between the first serial number and the unique identification code of the first device is only stored in the first cloud server, and the first serial number can replace the unique identification code of the first device as a registration account to register the first device as a trusted device of the second cloud server. It can be understood that after registering as a trusted device of the second cloud server, the first device can obtain the data in the second cloud server through the first cloud server. In addition, since the association between the first serial number and the unique identification code of the first device is only stored in the first cloud server, and the second cloud server only stores the first serial number and the association between the first serial number and the second serial number, it cannot obtain the unique identification code of the first device through the first serial number. Therefore, the network terminal (including the second cloud server) other than the first cloud service cannot monitor and supervise the first device through the first serial number, and protects the privacy and security of the user under the premise of compliant access to the data in the first application.

[0087] S102. The first cloud server determines a unique identification code of a first device associated with the first serial number, and sends first target information to the first device based on the unique identification code of the first device.

[0088] Since the first serial number is associated with the unique identification code of the first device in the first cloud server, the first cloud server can determine the first device through the first serial number and send the first target information to the first device.

[0089] Specifically, the first cloud server may send the first target information to an interface of the first device, which may be an interface for sending and receiving data for the travel service provided by the first device.

[0090] Optionally, after sending the first target information to the first device, the first device may transfer the first target information to the vehicle terminal through a vehicle-machine interconnection protocol such as Carlife and Hicar, and provide navigation services to users through the vehicle terminal; or, the first device may further transfer the first target information to a map application for navigation through an internal corresponding interface, and send the navigation image and navigation prompt sound to the vehicle terminal through a vehicle-machine interconnection protocol such as Carlife and Hicar, and the vehicle terminal outputs the navigation information.

[0091] Figure 5 The information transmission system shown can be used to implement the above-mentioned information transmission method. Figure 5As shown, the information transmission system 50 may include a mobile terminal 501, a vehicle terminal 502, a cloud server 503 and a cloud server 504, wherein:

[0092] The mobile terminal 501 may be the first device in the above description, the third-party application 5011 in the mobile terminal may be the first application in the above description, and the product serial number SN1 (abc0001) may be the unique identifier of the first device in the above description. On the mobile terminal 501, the user logs in to the third-party application 5011 using the account Uid1, and generates application data in the process of using the third-party application 5011, which includes Figure 5 The location information in add1. The travel service 5012 is a service provided by the mobile terminal 501 to facilitate the user's travel, provide users with bus query, map navigation and other functions. There is also an interface for sending and receiving data to the travel service on the mobile terminal 501 ( Figure 5 not shown).

[0093] The vehicle-mounted terminal 502 is connected to the mobile terminal 501 through the vehicle-mounted interconnection protocol. Specifically, the vehicle-mounted terminal 502 may include a display screen and a speaker.

[0094] The cloud server 503 may be the first cloud server in the foregoing description. In the cloud server 503, the product serial number SN1 of the mobile terminal 501 is associated with VSN1 (0001). VSN1 may be the first serial number in the foregoing description. After the user first authorizes and successfully obtains the product serial number SN1 of the mobile terminal 501, the cloud server 503 may associate VSN1 with SN1.

[0095] Cloud server 504 may be the second cloud server in the above description. In cloud server 504, VSN1 (0001) is associated with sdk_id1, and sdk_id1 is associated with account Uid1 that logs in third-party application 5011 on the first device. This association may exist in the first application of the first device. When the user transfers data (such as location information add1) in third-party application 5011 to travel service 5012 through this system, sdk_id1 may be used as a temporary account (or specifically used to transfer application data in third-party application 5011 logged in with Uid1). Sent to the account of cloud server 503), replacing the above-mentioned Uid1 to communicate with cloud server 504. Optionally, in order to establish an association between sdk_id1 and Uid1, when cloud server 503 uses VSN1 to register as a trusted device serial number in cloud server 504, cloud server 504 can assign a serial number to VSN1 (0001), and the serial number is sdk_id1. In cloud server 504, the sdk_id1 will be associated with VSN1 (0001), and the association will be sent to cloud server 503 synchronously. That is, in the cloud server 503, VSN1 (0001) is also associated with sdk_id1 (at this time, the cloud server 503 has not yet associated SN1 with VSN1 (0001)); after the user first authorizes and successfully obtains the product serial number SN1 of the mobile terminal 501, the cloud server 503 can associate VSN1 with SN1. At this time, VSN1, SN1, and sdk_id1 can be regarded as associated together in the cloud server 503; thereafter, the cloud server 503 can apply for a verification code from the cloud server 504 through sdk_id1. After receiving the application from the cloud server 503, the cloud server 504 can generate a verification code for sdk_id1 (the verification code can be a QR code, a digital verification code, or other types of verification codes, which are not limited in this application), associate sdk_id1 with the verification code, and The verification code and the association between the verification code and sdk_id1 are sent to the cloud server 503. At this time, VSN1, SN1, sdk_id1 and the verification code can be regarded as being associated together in the cloud server 503; the cloud server 503 can send the verification code to the mobile terminal 501 based on the association between sdk_id1, VSN1, SN1 and the verification code in the cloud server 503; thereafter, the mobile terminal 501 can operate the verification code through the third-party application 5011 installed thereon (for example, when the verification code is a QR code, the mobile terminal can use the scanning function provided by the third-party application 5011 under the user's operation to scan the verification code), obtain the sdk_id1 corresponding to the verification code, and establish an association between sdk_id1 and the current login account of the third-party application 5011, i.e., Uid1.This association relationship can always exist in the third-party application 5011 or cloud server 503 that has logged into the Uid1 account; in the subsequent process, the cloud server 504 may no longer need to generate a verification code for sdk_id1, and the user may no longer need to use the third-party application 5011 to operate the verification code to complete the association between Uid1 and sdk_id1.

[0096] In the subsequent process of transferring the add1 from the third-party application 5011 to the cloud server 503, the user can operate add1 in the application interface of the third-party application 5011 through the mobile terminal 501 (for details, please refer to Figure 1 ) so that the cloud server 503 obtains add1 from the third-party application 5011 of the mobile terminal 501.

[0097] It is understandable that the user uses Uid1 to log in to the third-party application 5011 on the mobile terminal 501, and Uid1 is associated with sdk_id1, and Uid1 is associated with VSN1 in the cloud server 504. Therefore, based on the above association, the mobile terminal 501 can send sdk_id1 and add1 to the cloud server 504 (here it is assumed that the association between Uid1 and sdk_id1 exists in the first application), and determine the VSN1 associated with it based on sdk_id1, and determine the corresponding cloud server based on VSN1, that is, cloud server 503, and send the above VSN1 and add1 to the cloud server 503.

[0098] Similarly, after cloud server 503 obtains VSN1 and add1 from cloud server 504, it can determine the SN1 associated with it based on VSN1, and determine the corresponding terminal based on SN1, that is, the mobile terminal 501, and send add1 to the travel service (interface) of the mobile terminal 501.

[0099] Optionally, the mobile terminal 501 can further transfer add1 to the map application 5013 for navigation through the corresponding internal interface, and send the navigation image and navigation prompt sound to the vehicle terminal 502 through the vehicle-machine interconnection protocol such as Carlife and Hicar, and the vehicle terminal 502 will output the navigation information.

[0100] Optionally, when a map navigation application is installed on the vehicle terminal 502 and the vehicle terminal 502 has a network data access function, the mobile terminal 501 can transfer the add1 information flow to the vehicle terminal 502 through a vehicle-machine interconnection protocol such as Carlife and Hicar, and provide navigation services to the user through the vehicle terminal 502.

[0101] It is understandable that, in addition, in the process of registering as a trusted device in the cloud server opened by the manufacturer of the third-party application, after the mobile terminal submits a registration application to the cloud server opened by the manufacturer of the third-party application using a unique identity identifier, some cloud servers opened by the manufacturers of the third-party application will take several days to accept the registration application. Before the registration application is accepted, the above-mentioned information flow process will be blocked, causing inconvenience to the user.

[0102] In order to overcome this defect, in combination with the aforementioned information transmission method, the present application provides another information transmission method, which can be applied to an information transmission system; when implementing this method, the first cloud server opened by the mobile terminal manufacturer can generate a first serial number set based on the number of terminal products produced in the first cloud server after the device is produced but before it leaves the factory, and use the serial numbers in the first serial number set to register as trusted device serial numbers in the second cloud server opened by the third-party application manufacturer; in the subsequent user's use, the mobile terminal can use a unique identity identification code (such as SN, UDID, IMEI) with the user's authorization to directly associate it with the serial number in the first serial number set in the first cloud server, and immediately register as a trusted device of the above-mentioned second cloud server based on the serial number, without having to wait for a long time for the above-mentioned second cloud server to accept the data, so as to improve the user experience.

[0103] Next, combine Figure 6 as well as Figure 7 The information transmission method provided in this application is described.

[0104] like Figure 6 As shown, the information transmission system used by the information transmission method provided in the present application may include a first device, a third device, a first cloud server and a second cloud server.

[0105] The first device and the third device can be connected to each other through the vehicle-machine interconnection protocol. The first device can be a mobile phone, a tablet computer, a wearable device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, etc., and the present application does not impose any restrictions on the specific type of the electronic device. The third device can be a vehicle-mounted terminal. When the third device is a vehicle-mounted terminal, the vehicle equipped with the third device can be an ordinary vehicle, or a special vehicle (including but not limited to a police car, a tractor, etc.) or a rescue vehicle (including but not limited to an ambulance, a fire truck, a rescue vehicle, etc.). It can be understood that the present application does not limit the specific form of the third device.

[0106] The first device may be installed with a first application and a second application, and the first device may have a corresponding service interface, which may include an interface for communicating with the first cloud server, and the service interface may also be a data communication interface with the first application and the second application.

[0107] The information transmission method provided in the embodiment of the present application may include the following steps:

[0108] S201. The second cloud server obtains product information and generates second information according to the product information.

[0109] Understandably, the manufacturer of the first device may mass-produce devices of the same model as the first device (including the first device). Before the manufacturer of the first device produces the device of this model for the first time and officially ships it for sale, it is necessary to publish the device of this model, and this stage generally takes several days. Therefore, during this period of time (i.e., the time before the first device is produced and shipped), the first cloud server can obtain the product information, which may include the total number of electronic devices of the same model as the first device produced in this batch (hereinafter referred to as the device production quantity), and generate the second information based on the device production quantity. Specifically, the second information may include multiple serial numbers, and the number of serial numbers in the second information is greater than or equal to the number of device production. In addition, since the serial number in the second information needs to be assigned to the first device and the device with the same signal as the first device in the subsequent process, and replaces the unique identification code (such as SN, UDID, IMEI) of these devices to be registered in the second cloud server, in the second information, any two serial numbers are different.

[0110] S202: The first cloud server sends second information to the second cloud server.

[0111] The first cloud server sends the second information to the second cloud server for registration, and registers each serial number in the second information as a trusted device serial number of the second cloud server.

[0112] S203: The second cloud server registers the serial number in the second information as a trusted device serial number, and associates the serial number in the second information with a verification code serial number.

[0113] After receiving the second information, the second cloud server determines the serial number in the second information as the trusted device serial number. Combined with the above description, it can be seen that before the device is officially shipped and sold, the manufacturer of the device needs to release the device, and this stage generally takes several days. Therefore, even if it takes a few days for the second cloud server to accept the registration application, when the device is sold to the user, the serial number in the second information has been successfully registered as the trusted device serial number of the second cloud server. In other words, in the subsequent use process of the user, the first device or the device of the same model as the first device can be directly associated with the serial number in the second information in the first cloud server using the unique identification code of the device (such as SN, UDID, IMEI) with the authorization of the user, and immediately registered as a trusted device of the second cloud server based on the associated serial number, without having to wait for a long time for the acceptance of the second cloud server again.

[0114] S204. The second cloud server sends the second information and the verification code serial numbers associated with each serial number in the second information to the first cloud server.

[0115] After the second cloud server registers all the serial numbers in the second information as trusted device serial numbers and associates the verification code serial number with each serial number in the second information, the second cloud server will send the second information and the verification code serial number associated with each serial number in the second information to the first cloud server. In addition, the association relationship between each serial number in the second information and its verification code serial number will also be sent to the first cloud server.

[0116] S205. The first device sends the unique identity identification code of the first device to the first cloud server.

[0117] The first device sends its unique identity code (eg, SN, UDID, IMEI) to the first cloud server via a corresponding service interface. Optionally, the first device may send its unique identity code to the first cloud server with user authorization.

[0118] S206. The first cloud server determines from the second information that the first serial number is associated with the unique identification code of the first device.

[0119] Combined with the above description, it can be known that in the above-mentioned first cloud server, each serial number in the second information has been registered as a trusted device serial number of the above-mentioned second cloud server. Therefore, after the first device sends the first device's unique identification code to the above-mentioned first cloud server, the above-mentioned first cloud server can determine the above-mentioned first serial number from the above-mentioned second information, and the first serial number can be any serial number in the above-mentioned second information that has not been associated with the device's unique identification code, and associate the first device's unique identification code with the above-mentioned first serial number. At this time, the above-mentioned first device can be regarded as successfully registered as a trusted device of the above-mentioned second cloud server.

[0120] It is understandable that the manufacturer of the first device will mass-produce devices of the same model as the first device, and these devices may all be sold to users. Each electronic device can obtain a serial number from the second information under the user's authorization, and register the serial number as a trusted device of the second cloud server.

[0121] Since each serial number in the second information can only register one device as a trusted device of the second cloud server, when more and more devices of the same model as the first device are registered as trusted devices of the second cloud server, the available serial numbers in the second information (i.e., serial numbers that have not yet been associated with the unique identification code of the device) will become less and less. The manufacturer of the first device may produce and sell the same model of the first device again in the future, and since the subsequent production is not the first batch of production, the manufacturer will most likely not publish, promote, and other activities for the device of this model. Therefore, in order to prevent the subsequent inability of other devices to quickly register as trusted devices of the second cloud server due to insufficient available serial numbers in the second information, in an optional embodiment, the first cloud server can periodically detect the number of unavailable serial numbers (i.e., serial numbers that have been associated with the unique identification code of the device) in the second information. When the proportion of the number of unavailable serial numbers in the second information to all serial numbers is greater than the first threshold, the first cloud server can generate third information and register the serial numbers in the third information as trusted device serial numbers of the second cloud server in the same manner as in the above description. Optionally, the first threshold may be set to 80%, or other values, which is not limited in the present application. Specifically, any two serial numbers in the third information are different, and any serial number in the third information is not included in the second information.

[0122] That is to say, in the subsequent process, if the manufacturer of the first device continues to mass-produce the device of this model, the first cloud server can keep the available trusted device number in the first cloud server to facilitate the rapid registration of the device as a trusted device of the second cloud server. In addition, in addition to preventing the leakage of the device's unique identity identifier and causing the device to be monitored, this method can also effectively prevent the manufacturer's production data (such as the total production volume of a certain model of equipment) from being known to other manufacturers, thereby effectively protecting the manufacturer's production data security while protecting user privacy.

[0123] S207: The first cloud server sends the first sequence number and a second sequence number associated with the first sequence number to the second cloud server.

[0124] The second serial number is the verification code serial number associated with the first serial number when the first serial number is registered in the second cloud server. It can be understood that the second serial number, the first serial number and the unique identification code of the first device are associated in the first cloud server.

[0125] The first cloud server may apply for a verification code from the second cloud server through the second serial number, and the verification code may be used to associate the account used to log in to the first application on the first device with the first serial number.

[0126] S208. The second cloud server generates a first verification code and associates it with the second serial number.

[0127] After receiving the second serial number sent by the first cloud server, the second cloud server can generate a first verification code for the second serial number (the first verification code can be a QR code, a digital verification code or other type of verification code, which is not limited in this application), and associate the second serial number with the first verification code.

[0128] S209. The second cloud server sends the second serial number and the first verification code.

[0129] The second cloud server sends the second serial number, the first verification code, and the association between the second serial number and the first verification code to the first cloud server. It is understandable that at this time, in the first cloud server, the second serial number, the first serial number, the first verification code, and the unique identification code of the first device can be considered to be associated together.

[0130] S210. The first cloud server sends a first verification code to the service interface of the first device.

[0131] S211. Perform a user operation on the first verification code to obtain a second serial number corresponding to the first verification code, and associate the second serial number with the login account.

[0132] The above service interface may be an interface for the travel service in the first device to communicate with the cloud.

[0133] The first device can operate the first verification code through the first application installed on it (for example, when the first verification code is a QR code, the first device can use the scanning function provided by the first application to scan the first verification code under the operation of the user), obtain the above-mentioned second serial number corresponding to the first verification code, and complete the association between the login account and the above-mentioned second serial number in the first application. After obtaining the above-mentioned second serial number, the first application can associate the current login account of the first application on the first device (hereinafter referred to as the first account) with the first verification code.

[0134] Since the third serial number is associated with the first serial number and the first verification code in the second cloud server, after receiving the second serial number associated with the first verification code, the second cloud server can associate the second serial number with the first serial number. This association relationship can always exist in the first application that logs in to the first account. In the subsequent process, the second cloud server may not need to generate a verification code for the second serial number, and the user may not need to use the first application again to operate the verification code to complete the association of the second serial number with the first account.

[0135] S212. The first device sends the first target information and the second serial number to the second cloud server.

[0136] S213: The second cloud server sends the first information to the first cloud server.

[0137] S214. The first cloud server sends the first target information to the service interface of the first device.

[0138] When the user performs a user operation on the first target information in the first application on the first device, the first application may first send the first target information and the second serial number to the second cloud server through the first application. The second cloud server may determine the first serial number associated with it through the second serial number, and send the first information to the first cloud server, where the first information includes the first target information and the first serial number. Afterwards, the first cloud server may determine the unique identification code of the first device associated with it through the first serial number, and further send the first target information to the service interface of the first device with the help of the unique identification code of the first device, which may be an interface for the travel service in the first device to communicate with the cloud.

[0139] S215. The first device sends the first target information to the second application on the first device through the service interface of the first device.

[0140] S216. The first device obtains navigation information generated by the second application based on the first target information.

[0141] S217: The first device sends navigation information to the third device.

[0142] S218. The third device outputs navigation information.

[0143] The third device may be a vehicle-mounted terminal. When the third device is a vehicle-mounted terminal, the vehicle equipped with the third device may be an ordinary vehicle, a special vehicle (including but not limited to a police car, a tractor, etc.) or a rescue vehicle (including but not limited to an ambulance, a fire truck, a rescue vehicle, etc.). It is understood that the specific form of the third device is not limited in this application.

[0144] The first device can transfer the first target information to the second application through the corresponding interface. Then, the second application can navigate based on the location information and generate navigation information (including navigation route map and navigation prompt tone). The first device can transfer the navigation information to the travel service provided by the first device through the corresponding interface, and send the navigation information to the third device through the vehicle-machine interconnection protocol such as Carlife and Hicar, and the third device outputs the navigation information.

[0145] Optionally, when a map navigation application is installed on the third device and the third device has a network data access function, the first device can also directly transfer the first target information to the third device through a vehicle-machine interconnection protocol such as Carlife and Hicar, navigate the first target information through the map navigation application on the third device, and output the generated navigation route map and navigation prompt sound.

[0146] Figure 7 The above system and information transmission method are further explained in combination with the data transmission mode between the devices in the system and the specific architecture of the above first device.

[0147] like Figure 7As shown, the specific architecture of the first device may include a hardware layer, a driver layer, an application framework layer, and an application layer. The application layer may include third-party applications and system applications. The application framework layer may include a window manager, an activity manager, a media manager, etc., and the application framework layer may provide an application programming interface (API) and a programming framework for applications in the application layer. These interfaces may be used for data transmission between services in the application framework layer and applications in the application layer. The driver layer may provide valid data for the application layer, and perform initialization configuration and extract valid data for the hardware in the hardware layer.

[0148] The aforementioned information transmission method in the present embodiment may correspond to Figure 7 Steps 701-716, step 717-1, and step 717-2 in the example. Among them, steps 701-705 are the pre-registration process of the trusted device number, steps 706-712 are the service activation process, and steps 713-716 and steps 717-1 and 717-2 are the information flow process. Among them:

[0149] Step 701: Product release / promotion online. This means that after the manufacturer of the first device first batch-produces devices of the same model as the first device, before the batch of products is officially shipped and sold, the manufacturer of the first device needs to release and promote the device of this model, which generally takes several days.

[0150] Step 702: Registration. This means that after the manufacturer of the first device has produced a batch of devices of the same model as the first device for the first time, it needs to register each device in the batch of products as a trusted device of the first cloud server through the configuration terminal. The account used during registration can be the unique identification code of the device. Optionally, the configuration terminal will also install or test applications for each device in the batch of products.

[0151] Step 703: Send VSN. It indicates that the first cloud server can determine multiple different VSNs based on the production quantity of devices of the same model as the first device. These VSNs can be serial numbers composed of one or more of letters, numbers, and characters. Since it takes several days for the first device and the devices of the same model as the first device to be officially sold after being released, the first cloud server can successfully register these VSNs as trusted device serial numbers of the second cloud server during this period. In the subsequent user's use, the first device or the device of the same model as the first device can use the device's unique identification code (such as SN, UDID, IMEI) with the user's authorization. Directly associate with the first cloud server and one of these VSNs, you can immediately register as a trusted device of the second cloud server, without having to wait for a long time for the second cloud server to accept it.

[0152] Step 704: Send {VSN-sdk_id}. That is, when the second cloud service registers the VSN sent by the first cloud server as a trusted device number, it will also assign a verification code number, i.e., sdk_id, to each successfully registered VSN, and associate each VSN with its assigned sdk_id, and the association relationship will be synchronized to the first cloud server.

[0153] Step 705: Authorization to send {SN}. That is, after the user authorizes the use of the travel connection service in the travel service, the first device will send the unique identity code SN to the first cloud server, requesting the first cloud server to allocate a VSN to register it as a trusted device of the second cloud server.

[0154] Step 706: Dynamic expansion. That is, the first cloud server determines the proportion of currently available VSNs (i.e., serial numbers that have not yet been associated with the device's unique identification code) in all VSNs; if the proportion is greater than the first threshold, a new batch of VSNs are used again to register as trusted device serial numbers of the second cloud server. Step 706 can be performed at any stage of the entire process.

[0155] Step 707: Allocate VSN {SN-VSN1-sdk_id1}. That is, the first device allocates a serial number VSN1 that has not yet been associated with the device's unique identification code to SN, that is, SN1 is directly associated with VSN1, and the first device can immediately register as a trusted device of the second cloud server.

[0156] Step 708: Send {VSN1-sdk_id1}. That is, the first cloud server sends VSN1 and sdk_id1 to the second cloud server, and requests the second cloud server to allocate a verification code tikect1 based on sdk_id1.

[0157] Step 709: Send {sdk_id1-ticket1}. That is, the second cloud server associates sdk_id1 with ticket1, and sends the association and ticket1 to the first cloud server.

[0158] Step 710: Send ticket1 {SN1-VSN1-sdk_id1-ticket1}. That is, the first cloud server sends ticket1 to the first device based on the association between ticket1 and sdk_id1, the association between sdk_id1 and VSN, and the association between VSN and SN1.

[0159] Step 711: verifying ticket1. That is, the first device uses the first application logged in with the first account to verify ticket1 and obtains sdk_id1 corresponding to ticket1.

[0160] Step 712: Associate sdk_id1, that is, associate the first account with sdk_id1.

[0161] Step 713: Send the first target information. That is, the first device sends the first target information and sdk_id1 (or the first account) to the second cloud server via the first application.

[0162] Step 714: Send the first target information. That is, the second cloud server determines VSN1 associated with sdk_id1 (or the first account), and sends the first target information to the first cloud server based on VSN1.

[0163] Step 715: End-cloud synchronization. That is, the first cloud server determines the SN associated with VSN1, and sends the first target information to the first device based on the SN. Specifically, the cloud push service on the first device can provide a corresponding interface to receive the first target information sent by the first cloud server.

[0164] Step 716: Push the first target information. That is, the first device transfers the first target information to the travel service provided by the first device. Specifically, the travel connection service on the first device can provide a corresponding interface to receive the first target information pushed by the interface provided by the above cloud push service.

[0165] Step 717-1: Service injection. That is, the first device can transfer the first target information flow to the above-mentioned second application through the corresponding interface. Then, the above-mentioned second application can navigate based on the location information and generate navigation information (including navigation route map and navigation prompt sound). The first device can transfer the above-mentioned navigation information flow to the travel service provided by the first device through the corresponding interface, and send the above-mentioned navigation information to the third device through the vehicle-machine interconnection protocol such as Carlife and Hicar, and the third device outputs the navigation information.

[0166] Step 717-2: Business transfer. That is, if a map navigation application is installed on the third device and the third device has a network data access function, the first device can also directly transfer the first target information to the third device through a vehicle-machine interconnection protocol such as Carlife and Hicar, navigate the first target information through the map navigation application on the third device, and output the generated navigation route map and navigation prompt sound.

[0167] It should be noted that after the travel connection service successfully obtains the above-mentioned first target information, the first device can process the first target information in any of steps 717-1 or 717-2 according to the performance of the third device and the specific needs of the user.

[0168] In addition, in the actual driving process, there is also a scenario where the first device used by the driver of the vehicle has established a communication connection with the third device, and the driver has logged into the first application using the second serial number on the first device used by the driver. However, since the driver is driving, for safety reasons, it is inconvenient for the driver to perform user operations on the first target information on the first device. If the location information required by the driver for navigation at this time exists in a group constructed by multiple users of the first application (for example, If a driver's mobile phone is in a friend group or family group, and there is a user in the group traveling with the driver, or the location information required by the driver for navigation exists in the first application logged in with other accounts on other devices, the safest and quickest solution is for other users to transfer the location information to the first device, and the travel service of the first device processes it.

[0169] However, since the account used by other users to log in to the above-mentioned first application on other devices is not associated with the above-mentioned first serial number in the above-mentioned second cloud server, in an optional embodiment, the verification code generated by the second server based on the above-mentioned second serial number (the verification code can be the above-mentioned first verification code, or it can be the verification code that the first server subsequently applies to the above-mentioned second cloud server again through the above-mentioned second serial number) can also be logged in by the first application installed on it with other accounts (the account is not the above-mentioned first account) for verification. For example, the user can operate the above-mentioned verification code through the first application logged in with the second account on the second device, and associate the second account with the above-mentioned second serial number based on the same logic as in the above description. In other words, the above-mentioned second serial number can be associated with multiple login accounts of the first application. However, in the above-mentioned second cloud server, the trusted device number associated with the above-mentioned second serial number is still only the above-mentioned first serial number; and in the above-mentioned first cloud server, the device unique identity code associated with the above-mentioned first serial number is also only associated with the unique identity code of the above-mentioned first device. In this way, in the subsequent process, in addition to the driver, other users belonging to the above-mentioned second account can also operate the second target information in the first application logged in to the second account on the second device through their own devices (such as the above-mentioned second device), and transfer the second target information to the service interface of the above-mentioned first device held by the driver, and further flow to the second application on the above-mentioned first device, and transfer the navigation information generated by the second application for the second target information to the above-mentioned third device through the travel service, and output by the third device.

[0170] like Figure 8 The information transmission system 80 may include multiple mobile terminals, a cloud server 804 opened by the manufacturers of the multiple mobile terminals, a cloud server 805 opened by the manufacturer of the third-party application 8011, and a vehicle-mounted terminal 806. The multiple mobile terminals may include a mobile terminal 801, a mobile terminal 802, and a mobile terminal 803, all of which are installed with the third-party application 8011, and each mobile terminal has a different account for logging into the third-party application 8011. Among them:

[0171] The mobile terminal 801 may be the first device in the above description, the third-party application 8011 may be the first application in the above description, the cloud server 804 may be the first cloud server in the above description, the cloud server 805 may be the second cloud server in the above description, and the vehicle terminal 806 may be the third device in the above description. That is to say, in the information transmission system 80, the mobile terminal 801 and the vehicle terminal 806 are connected through the vehicle-machine interconnection protocol, and the mobile terminal 801 has been registered as a trusted device of the cloud server 805. The registration number used during registration is VSN01 assigned by the cloud server 805. During registration, the second cloud server assigns VSN01 a verification code account sdk_id01, which is subsequently used to associate the account used by the user to log in to the third-party application. In combination with the above description, it can be known that in the cloud server 804, the unique identity code SN01 of the mobile terminal 801 is associated with VSN01, VSN01 is associated with sdk_01, and in the cloud server 805, sdk01_ is associated with Uid01 and sdk_id01 of the account used by the user to log in to the third-party application on the mobile terminal (here it is assumed that Uid01 and sdk_id01 are stored in the second cloud server rather than the first application), and the association between Uid01 and sdk_id01 is established by the user using the third-party application logged in to Uid01 to perform a verification operation on the cloud server 805 based on the verification code generated by sdk_id01.

[0172] In order to transfer the information adds1 in the third-party application 8011 to the interface corresponding to a service (such as travel service) in the mobile terminal 801, the mobile terminal 801 can send the account Uid01 and adds1 to the cloud server 805 through the third-party application 8011; the cloud server 805 can send adds1 and VSN01 to the cloud server 804 based on the association between Uid01 and sdk_id01, and the association between sdk_id01 and VSN01; the cloud server 804 can send adds1 to the interface corresponding to a service on the mobile terminal 801 based on the association between VSN01 and SN01.

[0173] In the system provided by the present application, any of the above-mentioned multiple mobile terminals can perform verification operations on the verification code associated with sdk_id01 by installing the third-party application 8011, and associate the account used to log in to the third-party application 8011 with sdk_id01. That is, in the cloud server 805, in addition to being associated with Uid01, sdk_id01 can also be associated with other accounts that can be used to log in to the third-party application 8011.

[0174] For example, the verification code generated by the second application based on sdk_id01 can be a QR code. After the cloud server 805 generates a verification code based on sdk_id01 and sends the verification code to the mobile terminal 801 via the cloud server 804, the mobile terminal 801 can scan the verification code by logging in to the third-party application 8011 with the account Uid01, obtain the sdk_id01 corresponding to the verification code, send the account Uid01 and sdk_id01 to the cloud server 805, and the cloud server 805 can associate Uid01 with sdk_id01 and save the association relationship. Similarly, the mobile terminal 802 can scan the verification code by logging in to the third-party application 8011 with the account Uid02, obtain the sdk_id01 corresponding to the verification code, send the account Uid02 and sdk_id01 to the cloud server 805, and the cloud server 805 can associate Uid02 with sdk_id01 and save the association relationship.

[0175] Afterwards, the mobile terminal 802 can transfer the information adds2 in the third-party application 8011 installed therein to the interface corresponding to a certain service on the mobile terminal 801. Specifically, the mobile terminal 802 can send the account Uid02 and adds1 to the cloud server 805 through the third-party application 8011; similarly, the cloud server 805 can send adds1 and VSN01 to the cloud server 804 based on the association between Uid02 and sdk_id01, and the association between sdk_id01 and VSN01; the cloud server 804 can send adds2 to the interface corresponding to a certain service on the mobile terminal 801 based on the association between VSN01 and SN01.

[0176] Optionally, since the verification code is time-limited, if it is necessary to associate the account of other third-party applications 8011 (such as Uid03) with sdk_id01 during subsequent use, the user can perform corresponding operations on the mobile terminal 801 and apply for a new verification code associated with sdk_id01 from the cloud server 805 through the cloud server 804. Similarly, the mobile terminal 803 can verify the above new verification code by logging in to the third-party application 8011 with the account Uid03, so that the cloud server 805 associates Uid03 with sdk_id01 and saves the association relationship. Similarly, the mobile terminal 803 can transfer the information adds3 in the third-party application 8011 installed by it to the interface corresponding to a service on the mobile terminal 801. For details, please refer to the above description, which will not be repeated here.

[0177] After receiving any one of the information in adds1, adds2 or adds3, the mobile terminal 801 can directly send the information to the vehicle terminal 806 through the travel service it provides, and the map application on the vehicle terminal 806 can navigate it; or, the mobile terminal 801 can transfer the information to the map application installed on the mobile terminal 801 through the corresponding interface, and obtain the navigation information generated based on the information in the map application through the above interface, and send the navigation information to the vehicle terminal 806 through the travel service it provides, and the vehicle terminal 806 outputs the navigation information.

[0178] The embodiment of the present application also provides an electronic device, which includes: one or more processors and a memory; wherein the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute the aforementioned Figures 4 to 8 Operations performed by the first cloud server in the illustrated embodiment.

[0179] Fig. 9 The structure of the electronic device is shown as an example. Fig. 9 As shown, the electronic device 900 provided in this embodiment may be the first cloud server in the foregoing description, which may include a communication interface 9001, a processor 9002, and a memory 9003. The memory 9003 may be disposed inside the electronic device 900, or may be disposed outside the electronic device.

[0180] For example, the above Figure 4-Figure 8 The actions performed by each first cloud server in the embodiment can be implemented by the processor 9002. The processor 9002 sends control signals and communication data through the communication interface 9001, and is used to implement Figure 4-Figure 8 In the implementation process, each step of the processing flow can be completed by the hardware integrated logic circuit in the processor 9002 or the instructions in the form of software. Figure 4-Figure 8 The operations performed by the first cloud server in the example are described in detail. For the sake of brevity, the description is omitted here. The program code executed by the processor 9002 to implement the above operations may be stored in the memory 9003. The memory 9003 is connected to the processor 9002, such as a coupling connection.

[0181] The communication interface 9001 may be a circuit, a bus, a transceiver or any other device that can be used for information exchange.

[0182] The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, modules or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, modules or modules.

[0183] The processor 9002 can operate in conjunction with the memory 9003. The memory can be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory (volatile memory), such as a random-access memory (RAM). The memory 9003 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0184] In the embodiment of the present application, the specific connection medium between the communication interface 9001, the processor 9002 and the memory 9003 is not limited. For example, the memory, the processor and the communication interface can be connected through a bus. The bus can be divided into an address bus, a data bus, a control bus, etc.

[0185] As used in the above embodiments, the term "when..." may be interpreted to mean "if..." or "after..." or "in response to determining..." or "in response to detecting...", depending on the context. Similarly, the phrases "upon determining..." or "if (the stated condition or event) is detected" may be interpreted to mean "if determining..." or "in response to determining..." or "upon detecting (the stated condition or event)" or "in response to detecting (the stated condition or event)", depending on the context.

[0186] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using 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 application 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 devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-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) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integration. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk), etc.

[0187] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

Claims

1. An information transmission method, characterized in that: include: A first cloud server receives first information sent by a second cloud server, the first information including a first serial number and first target information obtained by the second cloud server from a first application on a first device, the first cloud server is a cloud server serving the first device, the first serial number is a trusted device serial number registered in the second cloud server, and the first serial number is associated with the first device; The first cloud server determines a unique identification code of the first device associated with the first serial number, and sends the first target information to the first device based on the unique identification code of the first device.

2. The method according to claim 1, characterized in that Before the first cloud server receives the first target information sent by the second cloud server, the method further includes: The first cloud server sends second information to the second cloud server, where the second information is used to register a trusted device serial number of the second cloud server, and the second information includes the first serial number; the first serial number is associated with a unique identification code of the first device.

3. The method according to claim 2, characterized in that After the first cloud server sends the second information to the second cloud server, the method further includes: The first cloud server obtains a first verification code from the second cloud server based on a second serial number, where the second serial number is a serial number of the first cloud server and the second cloud server associated with the first serial number; The first cloud server sends the first verification code to the first device based on the first serial number associated with the second serial number and the unique identification code of the first device associated with the first serial number.

4. The method according to claim 2 or 3, characterized in that: The second information includes a first sequence number set and a second sequence number set, the sequence numbers in the first sequence number set are sequence numbers that have been associated with the unique identification code of the device, and the sequence numbers in the second sequence number set are sequence numbers that are not associated with the unique identification code of the device, and the method further includes: When the proportion of serial numbers in the first serial number set to all serial numbers in the second information is greater than a first threshold, the first cloud server sends third information to the second cloud server, and the third information is used to register the trusted device serial number of the second cloud server, and any serial number in the second information is not included in the third information.

5. The method according to claim 3 or 4, characterized in that: The method further comprises: The first cloud server receives fourth information sent by the second cloud server, where the fourth information includes the first serial number and information obtained by the second cloud server from the first application on the second device, and the account used to log in to the first application on the first device is different from the account used to log in to the first application on the second device; The first cloud server determines a unique identification code of the first device associated with the first serial number, and sends the fourth information to the first device based on the unique identification code of the first device.

6. An information transmission system, characterized in that: The information transmission system includes: a first device, a first cloud server, and a second cloud server; wherein a first application is installed in the first device, the first cloud server is a cloud server serving the first device, and the second cloud server is a cloud server serving the first application; in the first cloud server, the unique identification code of the first device is associated with a first serial number, and the first serial number is associated with a second serial number; in the second cloud server, the first serial number is associated with the second serial number, the first serial number is the serial number of a trusted device registered in the second cloud server, and the account for logging into the first application on the first device is associated with the second serial number, wherein: The first device is used to send the first target information and the second sequence number to the second cloud server through the first application under the operation of the first target information in the first application; The second cloud server is used to determine the first sequence number associated with the second sequence number, and send first information to the first cloud server, where the first information includes the first sequence number and the first target information; The first cloud server is used to send the first target information to the first device based on the unique identification code of the first device associated with the first serial number.

7. The system according to claim 6, characterized in that The first cloud server is further used to send second information to the second cloud server, the second information is used to register the trusted device serial number of the second cloud server, the second information includes multiple serial numbers, and the multiple serial numbers include the first serial number; The second cloud server is further configured to register the multiple serial numbers as trusted device serial numbers.

8. The system according to claim 7, characterized in that The first device is further used to send the unique identification code of the first device to the first cloud server; The first cloud server is further used to associate the unique identification code of the first device with the first serial number; The second cloud server is further used to associate the first sequence number with the second sequence number, and send the association relationship between the first sequence number and the second sequence number to the first cloud server; The first cloud server is further used to apply for a verification code from the second cloud server based on a second serial number associated with the first serial number; The second cloud server is further configured to generate a first verification code associated with the second serial number based on the second serial number, and send the first verification code to the first cloud server based on the first serial number associated with the second serial number; The first cloud server is further configured to send the first verification code to the first device based on a unique identification code of the first device associated with the first serial number; The first device is also used to obtain the second serial number when the first verification code is operated by the first application, and associate the second serial number with the account used to log in to the first application on the first device.

9. The system according to claim 7 or 8, characterized in that: The second information includes a plurality of serial numbers, the plurality of serial numbers including a first serial number set and a second serial number set, the serial numbers in the first serial number set are serial numbers that have been associated with a unique identification code of the device, and the serial numbers in the second serial number set are serial numbers that are not associated with a unique identification code of the device; When the proportion of the sequence numbers in the first sequence number set to all the sequence numbers in the second information is greater than a first threshold, the first cloud server is further configured to send third information to the second cloud server, and any sequence number in the second information is not included in the third information; The second cloud server is further used to register the serial number in the third information as a trusted device serial number.

10. The system according to claim 8 or 9, characterized in that The information transmission system further includes a second device, the second device and the first device are produced by the same manufacturer, and the first application is installed on the second device. The second device is used to obtain the second serial number under the operation of the first verification code through the first application, and associate the second serial number with the account used to log in to the first application on the second device; The second device is further configured to send fourth information to the second cloud server through the first application under the operation of the second target information in the first application, wherein the fourth information includes the second target information and the second sequence number; The second cloud server is further used to determine the first sequence number associated with the second sequence number, and send the first sequence number and the second target information to the first cloud server; The first cloud server is further used to send the second target information to the first device based on the unique identification code of the first device associated with the first serial number.

11. The system according to any one of claims 6 to 9, characterized in that: The system further includes a third device, the third device is communicatively connected to the first device, the first device further has a second application installed therein, and the second application is an application with a navigation function; The first device is further configured to send the first target information to the second application through a first interface, and obtain navigation information generated for the first target information based on the second application through the first interface, the navigation information including a navigation route map and / or a navigation prompt tone; The first device is further configured to send the navigation information to the third device; The third device is used to output navigation information.

12. The system according to any one of claims 6 to 9, characterized in that: The information transmission system further includes a third device, the third device is communicatively connected to the first device, a second application is installed in the third device, and the second application is an application with a navigation function; The first device is further configured to send the first target information to the third device; The third device is used to send the first target information to the second application through a second interface, and output navigation information generated by the second application for the second location information, wherein the navigation information includes a navigation route map and / or a navigation prompt tone.

13. An electronic device, characterized in that: The electronic device comprises: one or more processors, a memory and a display screen; The memory is coupled to the one or more processors, and the memory is used to store computer program codes, wherein the computer program codes include computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute the method according to any one of claims 1 to 5.

14. A chip system, characterized in that: The chip system is applied to an electronic device, and the chip system includes one or more processors, and the processor is used to call computer instructions so that the electronic device executes the method as described in any one of claims 1-5.

15. A computer-readable storage medium comprising instructions, characterized in that: When the instructions are executed on an electronic device, the electronic device is caused to execute the method as claimed in any one of claims 1 to 5.

Images