Vehicle-mounted association method and device

Abstract

A vehicle-mounted association method and device, wherein the vehicle-mounted voice module generates a first association request and sends it to a server after detecting that the vehicle is started, and the terminal device generates a second association request and sends it to the server after detecting that the vehicle is started, so that the server associates the user account corresponding to the terminal device with the vehicle-mounted voice module according to the first association request and the second association request. This solution uses the vehicle's startup operation to make the terminal device and the vehicle-mounted voice module actively send an association request to the server, which helps to avoid the low efficiency and error-prone problems caused by manual participation in the association solution, and improves the efficiency and accuracy of associating the vehicle-mounted voice module with the user account. Moreover, this solution only requires the vehicle to have a startup function and an on-board charging module in the vehicle, which not only reduces the manufacturing cost of the vehicle, but also can be applied to most vehicles.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle networking, and in particular to a vehicle-mounted association method and device. Background Art

[0002] In the field of Internet of Vehicles technology, the application of in-vehicle voice modules is becoming more and more common. For cars equipped with in-vehicle voice modules, even if the user is driving the car, the user can directly control the components in the vehicle to perform corresponding operations through voice, without having to distract himself to operate manually. Therefore, the introduction of in-vehicle voice modules in the vehicle field can not only improve the convenience of users driving cars, but also effectively reduce traffic safety hazards, which helps to improve the user's driving experience.

[0003] At this stage, when a certain voice service (such as voice navigation service, weather query service, etc.) is needed, users usually need to send a voice service access request to the server through the in-vehicle voice module. After the server receives the access request, it will first determine the access rights of the in-vehicle voice module based on the user account associated with the in-vehicle voice module. Only when the in-vehicle voice module has access rights to the voice service will the cloud server provide the voice service to the user through the in-vehicle voice module. Obviously, the user account associated with the in-vehicle voice module determines which voice services the user can access through the in-vehicle voice module, or determines whether the user can access the voice service through the in-vehicle voice module. Therefore, if you want users to accurately access the voice services provided by the server through the in-vehicle voice module, then the association between the in-vehicle voice module and the user account is a very important influencing factor.

[0004] In an existing association scheme, after each car is sold by the car shop, the salesperson will ask the car owner to install a car factory application (application, APP) on the mobile phone and ask the car owner to register a user account on the car factory APP. After the registration is successful, the salesperson will submit the user's mobile phone number and user account to the car factory system (i.e., server) synchronously through the car shop's computer. After 1-2 weeks of manual review by the car factory system, if the review is passed, the car factory system will send a text message with a binding code to the car owner's mobile phone, and prompt the user to enter the binding code in the text message into the car factory APP. After the user completes the input, the car factory APP will report the binding code entered by the user to the car factory system. If the car factory system determines that the binding code reported by the mobile phone is the same as the binding code issued by the car factory system, the car factory system will bind the currently logged in user account on the target APP and the car voice module on the car purchased by the user in the background, and notify the car voice module of the binding result. In this way, when the user subsequently sends a request to access the voice service to the car voice module, the car voice module can access the voice service provided by the car factory system according to the binding result. Obviously, the above association scheme involves manual operations such as submitting user information to the car manufacturer system and manual review, which not only reduces the efficiency of associating the in-vehicle voice module with the user account, but also easily leads to association errors due to the accidental nature of manual operations. In summary, how to accurately and quickly associate the in-vehicle voice module with the user account has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] The present application provides a vehicle-mounted association method and device for accurately and quickly associating a vehicle-mounted voice module with a user account.

[0006] In the first aspect, the present application provides a vehicle-mounted association method, which is applicable to a server, and includes: the server receives a first association request sent by a vehicle-mounted voice module, and receives a second association request sent by a terminal device, and if it is determined that the first association request and the second association request match, the user account corresponding to the terminal device and the vehicle-mounted voice module can be associated, so that the associated vehicle-mounted voice module can access the voice service provided by the server. The first association request is generated and sent to the server by the vehicle-mounted voice module after detecting that the first vehicle where the vehicle-mounted voice module is located is started, and the second association request of the server is generated and sent to the server by the terminal device after detecting that the second vehicle where the vehicle-mounted charging module coupled to the terminal device is located is started.

[0007] The above design uses the vehicle startup operation to make the terminal device and the vehicle voice module actively send an association request to the server, and let the server perform the association review operation according to the association request received respectively. This method does not require manual input of user information to the server, nor does it require manual review, which helps to avoid the low efficiency and error-prone problems caused by manual participation in the association scheme, and improves the efficiency and accuracy of associating the vehicle voice module with the user account. Furthermore, this association scheme only requires the vehicle to have a startup function and an on-board charging module in the vehicle, and has lower requirements for the vehicle, which not only reduces the manufacturing cost of the vehicle, but also can be applied to most vehicles at this stage, and has a wider application scenario.

[0008] In an optional design, the user account corresponding to the terminal device can be obtained by the user in advance from the server on the target application APP of the terminal device. This method only needs to update the target APP so that it has the associated related functions to realize the operation of associating the in-vehicle voice module and the user account. It does not require the customization of the vehicle system or other modules (such as display screen or near-field communication module), so it is easier to implement and the cost is lower.

[0009] In an optional design, the first association request and the second association request may have multiple possible situations, for example:

[0010] In one possible case, the first association request includes the identifier of the first vehicle, and the second association request includes the identifier of the second vehicle. In this case, if the identifier of the first vehicle and the identifier of the second vehicle are the same, the server can determine that the first association request and the second association request match. This method can only associate association requests initiated for the same vehicle, thereby helping to improve the accuracy of the association from the perspective of the vehicle to be associated.

[0011] In another possible case, the first association request includes the identification of the first vehicle and the start time information of the first vehicle, and the second association request includes the identification of the second vehicle and the start time information of the second vehicle. In this case, the server calculates the start time difference between the first vehicle and the second vehicle based on the start time information of the first vehicle and the start time information of the second vehicle. If the identification of the first vehicle and the identification of the second vehicle are the same, and the start time difference is less than a preset start time difference threshold, the server can determine that the first association request and the second association request match. This method can not only detect the compatibility of the vehicle before associating each association request, but also only associate the association requests initiated at the same time point, thereby helping to improve the accuracy of the association from the two dimensions of the vehicle to be associated and time.

[0012] In another possible case, the first association request includes the identification of the first vehicle and the location information of the first vehicle, and the second association request includes the identification of the second vehicle and the location information of the second vehicle. In this case, the server calculates the distance between the positions corresponding to the first vehicle and the second vehicle based on the location information of the first vehicle and the location information of the second vehicle. If the identification of the first vehicle and the identification of the second vehicle are the same, and the distance between the positions corresponding to the first vehicle and the second vehicle is less than a preset distance threshold, the server can determine that the first association request and the second association request match. This method can not only detect the matching of the vehicle before associating each association request, but also only associate the association requests initiated at the same location, thereby helping to improve the accuracy of the association from two dimensions: the vehicle to be associated and the location.

[0013] In another possible case, the first association request includes the identification of the first vehicle, the start time information of the first vehicle and the location information of the first vehicle, and the second association request includes the identification of the second vehicle, the start time information of the second vehicle and the location information of the second vehicle. In this case, the server calculates the start time difference between the first vehicle and the second vehicle based on the start time information of the first vehicle and the start time information of the second vehicle, and calculates the distance between the positions corresponding to the first vehicle and the second vehicle based on the location information of the first vehicle and the location information of the second vehicle. If the identification of the first vehicle and the identification of the second vehicle are the same, and the start time difference is less than the preset start time difference threshold, and the distance between the positions corresponding to the first vehicle and the second vehicle is less than the preset distance threshold, then the server can determine that the first association request and the second association request match. This method can match from the three dimensions of the vehicle to be associated, time and location before associating each association request, so as to achieve the decision of whether the two parties to be associated are legal parties from the three elements of vehicle unity, start time unity and location unity. By judging multiple information, it is helpful to prevent the user account of an illegal user from associating with the vehicle voice module of other users, and improve the security of associating the vehicle voice module with the user account.

[0014] In an optional design, after determining that the first association request and the second association request match, the server can also send the first verification information to the vehicle voice module, so that the vehicle voice module voice broadcasts the first verification information. After that, the server receives the second verification information sent by the terminal device, which is generated by the user according to the first verification information voice broadcast by the vehicle voice module and sent to the terminal device. When the second verification information matches the first verification information, the server can associate the user account corresponding to the terminal device with the vehicle voice module. This method will perform a second verification after verifying the vehicle, start time or location. Through these two verifications, multiple information is used to comprehensively complete the matching of each association request. The cloud server can associate the correct user account with the vehicle voice module with a high probability, thereby helping to increase the possibility of associating the user account of an illegal user with the vehicle voice module and improve the security of the association.

[0015] In an optional design, after the server associates the user account corresponding to the terminal device with the in-vehicle voice module, it can also generate an access code corresponding to the in-vehicle voice module and send the access code corresponding to the in-vehicle voice module to the in-vehicle voice module. The access code is generated after the server successfully associates the user account corresponding to the terminal device with the in-vehicle voice module. In this way, it is helpful for the in-vehicle voice module to access the voice service from the cloud server directly based on the access code, without having to repeat the association operation, thereby helping to improve the efficiency of obtaining voice services.

[0016] In a second aspect, the present application provides a vehicle-mounted association method, which is applicable to a vehicle-mounted voice module, and includes: the vehicle-mounted voice module generates a first association request after detecting that the first vehicle where the vehicle-mounted voice module is located is started, and sends the first association request to a server, so that the server combines the first association request and the second association request sent by the terminal device to associate the user account corresponding to the terminal device with the vehicle-mounted voice module. The second association request is generated by the terminal device after the second vehicle is started and sent to the server, and the terminal device is coupled to the vehicle-mounted charging module in the second vehicle.

[0017] In an optional design, the first association request and the second association request may have multiple possible designs, for example:

[0018] In a possible case, the first association request may include the identifier of the first vehicle, and the second association request may include the identifier of the second vehicle.

[0019] In another possible case, the first association request may include the identification of the first vehicle and the start time information of the first vehicle, and the second association request may include the identification of the second vehicle and the start time information of the second vehicle.

[0020] In another possible case, the first association request may include the identification of the first vehicle and the location information of the first vehicle, and the second association request may include the identification of the second vehicle and the location information of the second vehicle.

[0021] In another possible case, the first association request may include the identification of the first vehicle, the start time information of the first vehicle and the location information of the first vehicle, and the second association request may include the identification of the second vehicle, the start time information of the second vehicle and the location information of the second vehicle.

[0022] In an optional design, after the vehicle-mounted voice module sends the first association request to the server, it can also receive and store the access code corresponding to the vehicle-mounted voice module sent by the server, and then the vehicle-mounted voice module can use the access code to access the voice service from the cloud server.

[0023] In an optional design, before the in-vehicle voice module generates the first association request, it can also be determined that no access code corresponding to the in-vehicle voice module is stored in the in-vehicle voice module.

[0024] In a third aspect, the present application provides a vehicle-mounted association method, which is applicable to a terminal device, and the terminal device is coupled to a vehicle-mounted charging module of a second vehicle. The method includes: the terminal device generates a second association request after detecting that the second vehicle is started through the vehicle-mounted charging module, and sends the second association request to the server, so that the server combines the second association request and the first association request sent by the vehicle-mounted voice module to associate the user account corresponding to the terminal device with the vehicle-mounted voice module. The first association request is generated by the vehicle-mounted voice module and sent to the server after detecting that the first vehicle where the vehicle-mounted voice module is located is started.

[0025] In an optional design, the first association request and the second association request may have multiple possible designs, for example:

[0026] In a possible case, the first association request may include the identifier of the first vehicle, and the second association request may include the identifier of the second vehicle.

[0027] In another possible case, the first association request may include the identification of the first vehicle and the start time information of the first vehicle, and the second association request may include the identification of the second vehicle and the start time information of the second vehicle.

[0028] In another possible case, the first association request may include the identification of the first vehicle and the location information of the first vehicle, and the second association request may include the identification of the second vehicle and the location information of the second vehicle.

[0029] In another possible case, the first association request may include the identification of the first vehicle, the start time information of the first vehicle and the location information of the first vehicle, and the second association request may include the identification of the second vehicle, the start time information of the second vehicle and the location information of the second vehicle.

[0030] In an optional design, the user account corresponding to the terminal device is obtained by the user in advance from the server on the target application APP of the terminal device. In this case, before the terminal device detects the start of the second vehicle through the on-board charging module, it can also use the user account corresponding to the terminal device to log in to the target APP, and then receive the identifier of the second vehicle input by the user on the target APP, and prompt the user on the target APP to couple the terminal device with the on-board charging module of the second vehicle, and prompt the user to perform the start operation on the second vehicle.

[0031] In an optional design, after the terminal device sends the second association request to the server, it can also receive the second verification information and send it to the cloud server, so that the cloud server can associate the user account corresponding to the terminal device with the in-vehicle voice module after determining that the second verification information is the same as the first verification information. The second verification information is generated by the user according to the first verification information voice broadcast by the in-vehicle voice module and sent to the terminal device, and the first verification information is sent by the cloud server to the in-vehicle voice module.

[0032] In a fourth aspect, the present application provides a vehicle-mounted association device, which may be a server, and includes a processor, a transceiver, and a memory, wherein the processor is connected to the memory, and the memory stores a computer program. When the computer program stored in the memory is executed by the processor, the server executes: receiving a first association request sent by a vehicle-mounted voice module through the transceiver, the first association request is generated by the vehicle-mounted voice module after detecting that a first vehicle where the vehicle-mounted voice module is located is started and sent to the server; receiving a second association request sent by a terminal device through the transceiver, the second association request is generated and sent by the terminal device after detecting that a second vehicle where a vehicle-mounted charging module coupled to the terminal device is located is started; if it is determined that the first association request and the second association request match, then associating the user account corresponding to the terminal device and the vehicle-mounted voice module, so that the associated vehicle-mounted voice module can access the voice service provided by the server.

[0033] In an optional design, the user account corresponding to the terminal device can be obtained by the user in advance by applying to the server on the target application APP of the terminal device.

[0034] In an optional design, the first association request and the second association request may have multiple possible situations, for example:

[0035] In one possible case, the first association request includes an identifier of the first vehicle, and the second association request includes an identifier of the second vehicle. In this case, when the computer program stored in the memory is executed by the processor, the server specifically executes: if it is determined that the identifier of the first vehicle and the identifier of the second vehicle are the same, it can be determined that the first association request and the second association request match.

[0036] In another possible case, the first association request includes the identification of the first vehicle and the start time information of the first vehicle, and the second association request includes the identification of the second vehicle and the start time information of the second vehicle. In this case, when the computer program stored in the memory is executed by the processor, the server specifically executes: according to the start time information of the first vehicle and the start time information of the second vehicle, calculate the start time difference between the first vehicle and the second vehicle, if the identification of the first vehicle and the identification of the second vehicle are the same, and the start time difference is less than a preset start time difference threshold, then it can be determined that the first association request and the second association request match.

[0037] In another possible case, the first association request includes the identification of the first vehicle and the location information of the first vehicle, and the second association request includes the identification of the second vehicle and the location information of the second vehicle. In this case, when the computer program stored in the memory is executed by the processor, the server specifically executes: according to the location information of the first vehicle and the location information of the second vehicle, calculate the distance between the positions corresponding to the first vehicle and the second vehicle respectively; if the identification of the first vehicle and the identification of the second vehicle are the same, and the distance between the positions corresponding to the first vehicle and the second vehicle respectively is less than a preset distance threshold, it can be determined that the first association request and the second association request match.

[0038] In another possible case, the first association request includes the identification of the first vehicle, the start time information of the first vehicle and the position information of the first vehicle, and the second association request includes the identification of the second vehicle, the start time information of the second vehicle and the position information of the second vehicle. In this case, when the computer program stored in the memory is executed by the processor, the server specifically executes: according to the start time information of the first vehicle and the start time information of the second vehicle, calculate the start time difference between the first vehicle and the second vehicle, according to the position information of the first vehicle and the position information of the second vehicle, calculate the distance between the positions corresponding to the first vehicle and the second vehicle respectively, if the identification of the first vehicle and the identification of the second vehicle are the same, and the start time difference is less than the preset start time difference threshold, and the distance between the positions corresponding to the first vehicle and the second vehicle respectively is less than the preset distance threshold, then it can be determined that the first association request and the second association request match.

[0039] In an optional design, when the computer program stored in the memory is executed by the processor, the server also executes: after determining that the first association request and the second association request match, before associating the user account corresponding to the terminal device and the vehicle-mounted voice module: also sending the first verification information to the vehicle-mounted voice module through the transceiver, so that the vehicle-mounted voice module voice broadcasts the first verification information, and then receiving the second verification information sent by the terminal device through the transceiver, the second verification information is generated by the user according to the first verification information voice broadcast by the vehicle-mounted voice module and sent to the terminal device, and determining that the second verification information matches the first verification information.

[0040] In an optional design, when the computer program stored in the memory is executed by the processor, the server further executes: after associating the user account corresponding to the terminal device with the vehicle-mounted voice module, generating an access code corresponding to the vehicle-mounted voice module, and sending the access code corresponding to the vehicle-mounted voice module to the vehicle-mounted voice module through the transceiver, so that the vehicle-mounted voice module accesses the voice service from the server based on the access code. The access code is generated after the server successfully associates the user account corresponding to the terminal device with the vehicle-mounted voice module.

[0041] In a fifth aspect, the present application provides a vehicle-mounted association device, which may be a vehicle-mounted voice module, and includes a processor, a transceiver, and a memory, wherein the processor is connected to the memory, and the memory stores a computer program. When the computer program stored in the memory is executed by the processor, the vehicle-mounted voice module executes: after detecting that the first vehicle where the vehicle-mounted voice module is located is started, a first association request is generated, and the first association request is sent to a server through the transceiver, so that the server combines the first association request and the second association request sent by the terminal device to associate the user account corresponding to the terminal device with the vehicle-mounted voice module. The second association request is generated by the terminal device after the second vehicle is started and sent to the server, and the terminal device is coupled to the vehicle-mounted charging module in the second vehicle.

[0042] In an optional design, the first association request and the second association request may have multiple possible designs, for example:

[0043] In a possible case, the first association request may include the identifier of the first vehicle, and the second association request may include the identifier of the second vehicle.

[0044] In another possible case, the first association request may include the identification of the first vehicle and the start time information of the first vehicle, and the second association request may include the identification of the second vehicle and the start time information of the second vehicle.

[0045] In another possible case, the first association request may include the identification of the first vehicle and the location information of the first vehicle, and the second association request may include the identification of the second vehicle and the location information of the second vehicle.

[0046] In another possible case, the first association request may include the identification of the first vehicle, the start time information of the first vehicle and the location information of the first vehicle, and the second association request may include the identification of the second vehicle, the start time information of the second vehicle and the location information of the second vehicle.

[0047] In an optional design, the vehicle-mounted voice module may also include a voice player, such as a speaker or a horn, or other devices capable of realizing a voice playback function. When the computer program stored in the memory is executed by the processor, the vehicle-mounted voice module further executes: after sending the first association request to the server, receiving the first verification information sent by the server through the transceiver, and broadcasting the first verification information through the voice player.

[0048] In an optional design, when the computer program stored in the memory is executed by the processor, the vehicle-mounted voice module also executes: after sending the first association request to the server, receiving and storing the access code corresponding to the vehicle-mounted voice module sent by the server through the transceiver, and using the access code to access the voice service from the server.

[0049] In an optional design, the vehicle-mounted voice module may also include a voice receiver, such as a microphone or a pickup, or other devices capable of realizing a voice receiving function. When the computer program stored in the memory is executed by the processor, the vehicle-mounted voice module further executes: before sending the first association request, receiving the voice information input by the user through the voice receiver, determining whether the vehicle-mounted voice module stores an access code corresponding to the vehicle-mounted voice module, and if it has been stored, applying for a voice service from the server according to the voice information input by the user and the access code corresponding to the vehicle-mounted voice module, and if it has not been stored, generating a first association request.

[0050] In a sixth aspect, the present application provides a vehicle-mounted association device, which may be a terminal device, and the device may be coupled to the vehicle-mounted charging module of a second vehicle. The device includes: one or more processors; a memory; a transceiver; and one or more computer programs; wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, and when the instructions are called and executed by the one or more processors, the terminal device executes: after detecting that the second vehicle is started through the vehicle-mounted charging module, a second association request is generated, and the second association request is sent to the server through the transceiver, so that the server combines the second association request and the first association request sent by the vehicle-mounted voice module to associate the user account corresponding to the terminal device with the vehicle-mounted voice module. Wherein, the first association request is generated by the vehicle-mounted voice module and sent to the server after detecting that the first vehicle where the vehicle-mounted voice module is located is started.

[0051] In an optional design, the first association request and the second association request may have multiple possible designs, for example:

[0052] In a possible case, the first association request may include the identifier of the first vehicle, and the second association request may include the identifier of the second vehicle.

[0053] In another possible case, the first association request may include the identification of the first vehicle and the start time information of the first vehicle, and the second association request may include the identification of the second vehicle and the start time information of the second vehicle.

[0054] In another possible case, the first association request may include the identification of the first vehicle and the location information of the first vehicle, and the second association request may include the identification of the second vehicle and the location information of the second vehicle.

[0055] In another possible case, the first association request may include the identification of the first vehicle, the start time information of the first vehicle and the location information of the first vehicle, and the second association request may include the identification of the second vehicle, the start time information of the second vehicle and the location information of the second vehicle.

[0056] In an optional design, the user account corresponding to the terminal device is obtained by the user in advance from the server on the target application APP of the terminal device. In this case, when the instruction is called and executed by the one or more processors, the terminal device specifically executes: before detecting the start of the second vehicle through the on-board charging module, log in to the target APP using the user account corresponding to the terminal device, then receive the identifier of the second vehicle input by the user on the target APP, and prompt the user on the target APP to couple the terminal device with the on-board charging module of the second vehicle, and prompt the user to start the second vehicle.

[0057] In an optional design, when the instruction is called and executed by the one or more processors, the terminal device further executes: after sending the second association request to the server, receiving the second verification information through the transceiver and sending it to the server, so that the server determines that the second verification information is the same as the first verification information and then associates the user account corresponding to the terminal device with the vehicle voice module. The second verification information is generated by the user according to the first verification information voice broadcast by the vehicle voice module and sent to the terminal device, and the first verification information is sent by the server to the vehicle voice module.

[0058] In a seventh aspect, the present application provides a vehicle-mounted association device, which includes modules / units for executing any possible design method of any of the above aspects. These modules / units can be implemented by hardware, or by hardware executing corresponding software implementations.

[0059] In an eighth aspect, the present application provides a vehicle-mounted association device, which includes a processor and a communication interface, wherein the communication interface is used to receive signals from other communication devices other than the vehicle-mounted association device described in the fourth aspect and transmit them to the processor or send signals from the processor to other communication devices other than the vehicle-mounted association device described in the fourth aspect, and the processor is used to implement a method as described in any one of the first aspects through a logic circuit or by executing code instructions.

[0060] In the ninth aspect, the present application provides a vehicle-mounted associated device, comprising a processor and a communication interface, wherein the communication interface is used to receive signals from other communication devices other than the vehicle-mounted associated device described in the fifth aspect and transmit them to the processor or send signals from the processor to other communication devices other than the vehicle-mounted associated device described in the fifth aspect, and the processor is used to implement a method as described in any one of the second aspects through a logic circuit or by executing code instructions.

[0061] In the tenth aspect, the present application provides a vehicle-mounted associated device, including a processor and a communication interface, wherein the communication interface is used to receive signals from other communication devices other than the vehicle-mounted associated device described in the sixth aspect and transmit them to the processor or send signals from the processor to other communication devices other than the vehicle-mounted associated device described in the sixth aspect, and the processor is used to implement the method described in any one of the third aspects through logic circuits or execution code instructions.

[0062] In the eleventh aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed, it implements the method as described in any one of the first aspect above, or implements the method as described in any one of the second aspect above, or implements the method as described in any one of the third aspect above.

[0063] In the twelfth aspect, the present application provides a chip comprising a processor and an interface; the processor is used to read instructions to execute a method as described in any one of the first aspects above, or to execute a method as described in any one of the second aspects above, or to execute a method as described in any one of the third aspects above.

[0064] In the thirteenth aspect, the present application provides a computer program product, which is used to store a computer program. When the computer program is run on a computer, the computer executes any method as described in the first aspect above, or executes any method as described in the second aspect above, or executes any method as described in the third aspect above.

[0065] In the fourteenth aspect, the present application provides a vehicle, comprising an on-board voice module and an on-board charging module, wherein the on-board voice module is used to connect to a server, and the on-board charging module is used to couple a terminal device; the on-board voice module can be used to execute the above-mentioned second aspect or any one of the methods in the second aspect, and the terminal device can be used to execute the above-mentioned third aspect or any one of the methods in the third aspect.

[0066] In the fifteenth aspect, the present application provides a vehicle networking system, which includes the server described in any of the fourth aspects, the vehicle-mounted voice module described in any of the fifth aspects, and the terminal device described in any of the sixth aspects.

[0067] The beneficial effects of the design in any of the second to fifteenth aspects can refer to the beneficial effects of the design in the first aspect, and this application will not elaborate on them one by one. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] Figure 1 A possible system architecture diagram applicable to the embodiments of the present application is exemplarily shown;

[0069] Figure 2 A flowchart showing a method for associating an in-vehicle voice module with a user account is exemplified;

[0070] Figure 3 A schematic diagram of an application scenario provided by an embodiment of the present application is exemplified;

[0071] Figure 4 A schematic diagram showing an exemplary process of the vehicle-mounted association method provided in the first embodiment of the present application;

[0072] Figure 5 A flowchart of a method for determining whether an association request matches is exemplarily shown in an embodiment of the present application;

[0073] Figure 6A schematic diagram showing an exemplary process of the vehicle-mounted association method provided in the second embodiment of the present application;

[0074] Figure 7 A schematic diagram showing an interface process of a vehicle-mounted association method provided in an embodiment of the present application is exemplified;

[0075] Figure 8 A schematic diagram showing an exemplary process of the vehicle-mounted association method provided in the third embodiment of the present application;

[0076] Fig. 9 A schematic diagram showing an application scenario corresponding to an embodiment of the present application is exemplified;

[0077] Fig.10 A schematic diagram of a vehicle-mounted association device provided in an embodiment of the present application is exemplarily shown;

[0078] Fig.11 A schematic diagram of another vehicle-mounted association device provided in an embodiment of the present application is exemplarily shown;

[0079] Fig.12 A schematic diagram of another vehicle-mounted association device provided in an embodiment of the present application is exemplarily shown;

[0080] Fig.13 A schematic diagram of another vehicle-mounted association device provided in an embodiment of the present application is exemplarily shown. DETAILED DESCRIPTION

[0081] It should be noted that the association scheme in the embodiment of the present application can be applied to the Internet of Vehicles, such as vehicle external connection V2X, long-term evolution technology for workshop communication LTE-V, vehicle-to-vehicle V2V, etc. For example, it can be applied to vehicles with voice reception function and voice broadcast function, or to other components in vehicles with voice reception function and voice broadcast function. Other components in the vehicle include but are not limited to: vehicle-mounted terminal, vehicle-mounted controller, vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip, vehicle-mounted unit, vehicle-mounted radar or vehicle-mounted camera and other sensors. The vehicle can implement the association method provided in the present application through the vehicle-mounted terminal, vehicle-mounted controller, vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip, vehicle-mounted unit, vehicle-mounted radar or camera. Of course, the association scheme in the embodiment of the present application can also be used for other intelligent terminals with voice reception function and voice broadcast function other than the vehicle, or be set in other intelligent terminals with voice reception function and voice broadcast function other than the vehicle, or be set in the components of the intelligent terminal. The intelligent terminal can be other terminal devices such as intelligent transportation equipment, smart home equipment, and robots. For example, it includes but is not limited to smart terminals or controllers, chips, other sensors such as radars or cameras, and other components within smart terminals.

[0082] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the embodiments described below are only part of the embodiments of the present application, rather than all of the embodiments. In the following description, the user refers to the user who rents the voice service on the "cloud". The user can refer to a general natural person, and of course can also refer to a company, group, or group. This application does not limit this. In the following embodiments of the present application, the user specifically refers to a natural person who accesses the voice service on the "cloud" through the vehicle-mounted voice module installed in the vehicle.

[0083] Figure 1 A possible system architecture diagram applicable to the embodiment of the present application is shown in FIG. Figure 1 The system architecture shown includes a vehicle, a server and a terminal device. Among them, a vehicle refers to a vehicle equipped with a vehicle-mounted voice module. Generally, at least one vehicle-mounted voice module can be installed in a vehicle. It should be understood that the embodiment of the present application does not limit the number of vehicles, the number of servers and the number of terminal devices in the system architecture. For example, one server can only interact with one terminal device, or it can interact with multiple terminal devices. For another example, one server can only interact with one vehicle-mounted voice module in one vehicle, or it can interact with multiple vehicle-mounted voice modules in multiple vehicles. In addition, the system architecture applicable to the embodiment of the present application may include other devices, such as core network devices, wireless relay devices and wireless backhaul devices, in addition to vehicles, servers and terminal devices, and the embodiment of the present application is not limited to this. In addition, the server in the embodiment of the present application can integrate all functions on an independent physical device, or it can deploy different functions on multiple independent physical devices, and the embodiment of the present application is not limited to this.

[0084] Continue to refer to Figure 1As shown, the server can be connected to the vehicle-mounted voice module and the terminal device in the vehicle respectively. The server can be connected to the vehicle-mounted voice module wirelessly, and can be connected to the terminal device by wired or wirelessly. In addition, the server and the voice module in the vehicle, and the server and the terminal device can also communicate through network protocols, and the network protocols can include, for example, transmission control protocol / internet protocol (TCP / IP), user datagram protocol / internet protocol (UDP / IP), hypertext transfer protocol (HTTP), hypertext transfer protocol over secure socket layer (HTTPS) with security as the goal, etc. The network protocol can also include the remote procedure call protocol (RPC) protocol and representational state transfer (REST) ​​protocol used on the above-mentioned protocols, and the specific ones are not limited.

[0085] In the embodiment of the present application, the terminal device may refer to a device that provides voice and / or data connectivity to a user. For example, it may include a handheld device with a wireless connection function, a vehicle-mounted device, or a processing device connected to a wireless modem. The terminal device may communicate with the core network via a radio access network (RAN) and exchange voice and / or data with the RAN. The terminal device may include user equipment (UE), mobile station (MS), mobile terminal (MT), wireless terminal device, device-to-device (D2D) terminal device, vehicle to everything (V2X) terminal device, machine-to-machine / machine-type communications (M2M / MTC) terminal device, Internet of Things (IoT) terminal device, subscriber unit (subscriberunit), subscriber station (subscriber station), mobile station (mobile station), remote station (remotestation), access point (AP), remote terminal device (remote terminal), access terminal device (access terminal), user terminal device (user terminal), user agent (user agent), or user equipment (user device), etc. For example, it may include a mobile phone (or "cellular" phone), a computer with a mobile terminal device, a portable, pocket-sized, handheld, or computer-built-in mobile device, etc. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDA), and other devices. It also includes limited devices, such as devices with low power consumption, or devices with limited storage capacity, or devices with limited computing power, etc. For example, it includes information sensing devices such as barcodes, radio frequency identification (RFID), sensors, global positioning systems (GPS), laser scanners, etc.At present, some examples of terminal devices are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminal devices in industrial control, wireless terminal devices in self driving, wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, etc.

[0086] In the embodiment of the present application, the server may refer to a single server or a server cluster. In the application scenario of the in-vehicle voice service, the server may refer to a cloud service provider (CSP), also known as a cloud service control terminal or a cloud server, which is composed of a series of components and operation logic. The cloud server can provide rentable voice services to user accounts registered on the cloud server. Common in-vehicle voice services include voice navigation, voice flight inquiries, voice stock inquiries, voice weather broadcasts, voice control of window opening or closing, voice input text messages, voice activation of car phones, voice control of music or radio stations, and voice information reading, etc. The cloud server belongs to the car factory. Generally speaking, car factories usually provide free voice services for a period of time for newly sold vehicles. After the user purchases a car, the user can download a car factory APP and register a user account (such as a mobile phone number) on the car factory APP, and then perform the association operation between the user account and the in-vehicle voice module in the vehicle purchased by the user. When the association is successful, the cloud server can learn from the user account that the corresponding in-vehicle voice module belongs to the in-vehicle voice module in the newly sold vehicle, so that the cloud server can provide users with free voice services for a period of time through the in-vehicle voice module. When the free voice service expires, the cloud server will no longer provide voice services to users. At this time, if the user still wants to continue using the voice service, the user also needs to pay a certain cost to the cloud server. This payment can be achieved by logging into the car factory APP through the user account. When the cloud server detects that the user account has deposited a part of the cost for the purchase of voice services, the cloud server can return the corresponding voice service for subsequent voice service applications initiated by the in-vehicle voice module corresponding to the user account.

[0087] The scheme in the embodiment of the present application is used to associate the vehicle voice module with the user account in the application scenario of the above-mentioned vehicle voice service. In this scenario, when a user applies for a voice service to a cloud server through a certain vehicle voice module, only if the vehicle voice module is accurately associated with the user account corresponding to the user in advance, can the cloud server accurately determine the voice service authority of the vehicle voice module according to the association relationship, and then provide voice services to the user according to the voice service authority. Obviously, the operation of associating the vehicle voice module with the user account is a very important influencing factor for improving the accuracy of the vehicle voice service provided by the cloud server. However, at this stage, the association operation is mostly completed by the sales staff in the car factory manually inputting the relevant information to the cloud server when the user purchases the vehicle. Manual input is not only inefficient, but also makes the accuracy of the association depend on the accuracy of the manual input of the sales staff. Manual input will have certain accidental factors, which may also lead to low accuracy of the association.

[0088] In order to solve the above problems, it is necessary to find a solution that can complete the association without human intervention. Figure 1 The system architecture shown in the figure first introduces several possible association schemes by way of example. It should be noted that the manual intervention described in this article refers to the manual entry of information into the cloud server and manual review as exemplified in the above scheme, while the verification and other operations performed by the user during the association process are not considered manual intervention. In addition, for ease of understanding, the servers will be collectively referred to as cloud servers below. In other words, the "cloud server" that appears below can be replaced by "server", or "cloud service provider", or "cloud server control terminal".

[0089] In an alternative embodiment, Figure 2 A flow chart showing a method for associating a vehicle voice module with a user account is shown as an example. Figure 2 As shown, the process includes the following steps:

[0090] Step 201: The car manufacturer APP on the vehicle sends an association request to the cloud server.

[0091] In the above step 201, a vehicle system can be deployed on each vehicle for sale in the car factory, and the vehicle system is used to realize all media functions in the vehicle, such as voice function and disk playback function. The vehicle APP is pre-installed in the vehicle system. When a user purchases a vehicle in the car factory, the user can first start the vehicle system on the purchased vehicle, open the vehicle APP, and instruct the vehicle APP to send an association request to the cloud server.

[0092] Step 202, after receiving the association request sent by the vehicle APP on the vehicle, the cloud server generates a globally unique identification document (ID), and then sends the globally unique ID to the vehicle APP on the vehicle.

[0093] By way of example, the ID may be composed of a random combination of letters and numbers.

[0094] Step 203, after receiving the globally unique ID, the vehicle computer APP on the vehicle calls the QR code generator in the vehicle computer system to generate a corresponding QR code, and displays it on the display screen of the vehicle computer system.

[0095] Exemplarily, the QR code may exist in the form of a uniform resource locator (URL).

[0096] Step 204, when the user finds that a QR code is displayed on the display screen of the vehicle system, the user can open the vehicle system APP in the mobile phone to scan the QR code to obtain the ID.

[0097] In the embodiment of the present application, after the user purchases a vehicle, the salesperson in the car factory will prompt the user to install a car machine APP on the mobile phone and register the user account with the cloud server through the car machine APP in the mobile phone. During the registration process, the user also needs to enter the identification, model, user's phone number, etc. of the purchased vehicle. When the registration is successful, the user can use the registered user account to log in to the car machine APP in the mobile phone, and then perform the operation of scanning the QR code.

[0098] Step 205, the car machine APP on the mobile phone sends the scanned ID and the currently logged-in user account to the cloud server.

[0099] Step 206, after the cloud server verifies that the ID sent by the car machine APP on the mobile phone is the same as the ID sent by the cloud server, it associates the currently logged-in user account and the vehicle voice module together, and returns the association result to the car machine APP on the vehicle after the association is successful. Among them, if the association is successful, the currently logged-in user account can be carried in the association result. In this way, the car machine APP on the vehicle can load the voice resources in the user account according to the currently logged-in user account to obtain the voice service provided by the cloud server. In the case of association failure, the car machine APP on the vehicle can also apply for association again.

[0100] According to the above content, although Figure 2The illustrated association scheme can complete the association operation between the vehicle voice module and the user account without manual intervention, but this method requires the installation of a vehicle system with a display screen and a QR code generator in the vehicle, and also requires the customization of a vehicle APP in the vehicle system. Therefore, this method will increase the vehicle cost and is not applicable to vehicles without a display screen.

[0101] In another optional implementation, when the vehicle supports near-field communication functions such as Bluetooth or wireless LAN (wireless-fidelity, WIFI), the user can directly share the user account registered on the mobile phone APP with the vehicle-mounted voice module in the vehicle through near-field communication functions such as Bluetooth or WIFI. Alternatively, if a display screen is provided in the vehicle, the user can also directly use the vehicle-mounted voice module to scan the QR code corresponding to the currently logged-in user account to realize the sharing of the user account. However, the association in this way depends on the near-field communication capability of the vehicle and cannot be applied to vehicles without near-field communication capability.

[0102] In view of this, the present application provides a method for associating an in-vehicle voice module with a user account, so as to realize the association of the in-vehicle voice module with a user account in a vehicle that is not equipped with a display screen and does not have near-field communication capability, and to minimize the vehicle's overall vehicle manufacturing cost.

[0103] The present application will be further described in detail below in conjunction with the accompanying drawings. It should be understood that the specific operating methods in the method embodiments can also be applied to device embodiments or system embodiments. It should be noted that in the description of the present application, "at least one" refers to one or more, wherein multiple refers to two or more. In view of this, "multiple" can also be understood as "at least two" in the embodiments of the present invention. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / ", unless otherwise specified, generally indicates that the previously associated objects are in an "or" relationship.

[0104] In addition, it should be understood that in the description of this application, words such as "first" and "second" are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order. For example, "first association request" and "second association request" are just exemplary indications of different association requests, and do not mean that the importance or priority of the two association requests is different.

[0105] Before introducing the specific implementation method, a possible application scenario of the embodiment of the present application is first introduced.

[0106] Figure 3A possible application scenario diagram provided by an embodiment of the present application is exemplarily shown as follows: Figure 3 As shown, in this scenario, the user is sitting in a car, which may be equipped with an in-vehicle voice module and an in-vehicle charging module, and may also be equipped with a terminal device (such as Figure 3 The vehicle voice module may refer to any module that can realize the voice broadcast function and the voice receiving function. For example, it may be a microphone and a speaker that only realize the voice broadcast function and the voice receiving function, or it may be an electronic device that realizes the voice broadcast function, the voice receiving function and other functions at the same time. The vehicle charging module may be such as Figure 3 The charging module in the wired form shown in the figure has an external form of a vehicle charging interface, and of course it can also be a wireless charging module. It should be understood that in addition to the vehicle voice module and the vehicle charging module, other modules can also be installed on the vehicle, such as a processor, a vehicle positioning module, and a vehicle timing module. These modules in the vehicle can be connected together through a bus, so that each module can communicate with each other through the bus. Exemplarily, the vehicle positioning module can refer to a positioning module that relies on the global navigation satellite system (GNSS) technology, or it can refer to a positioning module that relies on the global positioning system (GPS) technology. When the vehicle positioning module relies on GNSS technology, the vehicle positioning module can obtain observations such as pseudoranges, ephemeris, and satellite launch times of one or more groups of satellites, and can provide users with all-weather three-dimensional coordinate positioning at any location on the earth's surface or near-earth space. When the vehicle positioning module relies on GPS technology, the vehicle positioning module can use the radio loop of the satellite in the air to realize the longitude and latitude positioning of the current position. At present, the navigation function of the vehicle is often implemented based on GPS technology. In addition, the on-board timing module can be used to maintain the time in the vehicle to ensure that the time in the vehicle is consistent with the outside time.

[0107] In the embodiment of the present application, the terminal device may refer to a device that can provide voice and / or data connectivity to the user and can also interact with other devices (such as a cloud server). The terminal device may be provided with a terminal charging module ( Figure 3 The terminal charging module may be as follows: Figure 3 The charging module in the wired form shown in the figure is externally manifested as a terminal charging interface, and of course, it can also be a wireless charging module. It should be understood that in addition to the terminal charging module, the terminal device can also be equipped with other modules, such as a processor, a terminal positioning module, a terminal timing module, and Figure 3The modules in the terminal device may also be connected together through a bus, so that the modules in the terminal device can communicate with each other through the bus. In the case where a display screen is provided in the terminal device, the terminal device can display information to the user through the display screen, and receive information input by the user through the display screen. It should be understood that although Figure 3 Not shown, the terminal device may also include other modules, such as a memory, a sensor, a Bluetooth device, a flash, a micro-projection device, a near field communication (NFC) device, etc., which are not described in detail here.

[0108] It should be noted that, in the embodiment of the present application, the first vehicle refers to the vehicle where the in-vehicle voice module is located, and the second vehicle refers to the vehicle where the in-vehicle charging module coupled to the terminal device is located. The first vehicle and the second vehicle may be the same vehicle or different vehicles, and are not specifically limited. In the embodiment of the present application, only when the first vehicle and the second vehicle are the same vehicle can the user successfully associate the in-vehicle voice module with the user account, that is, the server will associate the in-vehicle voice module requested by the user with the user account only when it determines that the first vehicle and the second vehicle are the same vehicle. When the first vehicle and the second vehicle are not the same vehicle, the server will not associate the in-vehicle voice module requested by the user with the user account to avoid malicious binding by the user, thereby improving the accuracy and efficiency of associating the in-vehicle voice module with the user account.

[0109] [Example 1]

[0110] Figure 4 The flowchart of the vehicle-mounted association method provided in the first embodiment of the present application is exemplarily shown. The method is applicable to a terminal device, a vehicle-mounted voice module and a cloud server, for example Figure 4 The terminal device, the vehicle-mounted voice module and the cloud server are shown. Figure 4 As shown, the process includes the following steps:

[0111] Step 401, before the vehicle is started, the terminal device is coupled to the on-board charging module in the vehicle.

[0112] In an embodiment of the present application, when the terminal device is coupled to an on-board charging module in a vehicle, if the vehicle is not started, the power supply in the vehicle will not supply power to the on-board charging module, and therefore the on-board charging module will not supply power to the terminal device, so that the terminal device is in an unpowered state.

[0113] In the embodiment of the present application, the terminal device is coupled with the vehicle-mounted charging module in the vehicle, which can be achieved by the following methods:

[0114] In an alternative embodiment, if the vehicle has Figure 3The wired charging capability shown in the figure, and the terminal device also supports wired charging to realize charging, the user can use the charging cable to connect the terminal device and the on-board charging module in the vehicle. In this case, the on-board charging interface of the terminal device is connected to the on-board charging interface through the charging cable. In this case, if the on-board charging module is switched from the power-off state to the power-on state (that is, the vehicle is started, and the power supply in the vehicle starts to supply power to the on-board charging module), the electric energy in the on-board charging module can be transmitted to the power supply of the terminal device via the on-board charging interface, the charging cable and the terminal charging interface of the terminal device in sequence, thereby powering the terminal device, and the terminal device is switched from the unpowered state to the powered state. In the powered state, if the power of the terminal device is not 100%, the terminal device can be charged. If the power of the terminal device is 100%, the terminal device can be powered on but not charged. In this embodiment, the interface of the charging cable can be a universal serial bus (USB) type interface, such as Micro USB, USB Type C, etc. Of course, it can also be other types of interfaces, which are not specifically limited.

[0115] In another optional implementation, if the vehicle has wireless charging capability and the terminal device also supports wireless charging, the user can place the terminal device within the power supply range of the on-board charging module so that the terminal device can be wirelessly connected to the on-board charging module through the inductive circuit. In this case, the power supply of the terminal device can be wirelessly connected to the inductive circuit in the on-board charging module through the inductive circuit in the terminal device. When the on-board charging module switches from the power-off state to the power-on state, the electric energy in the on-board charging module can be wirelessly transmitted to the power supply of the terminal device through the inductive circuit in the on-board charging module and the inductive circuit in the terminal device in turn, thereby powering the terminal device.

[0116] Step 402: After the vehicle voice module detects that the vehicle is started, it sends a first association request to the cloud server.

[0117] In the embodiment of the present application, vehicle start-up may specifically refer to starting the engine of the vehicle. The vehicle start-up operation may be performed by a user. For example, after the user couples the terminal device to the vehicle-mounted charging module in the vehicle, the user may control the vehicle start-up in the following manner:

[0118] For vehicles that are started by car keys, the keyhole on the vehicle generally has four gears: LOCK gear, ACC gear, ON gear and START gear. The car key is in the LOCK position when it is just inserted into the keyhole. When the user turns the car key to the ACC gear, the power supply in the vehicle supplies power to some electrical components in the vehicle, such as compact discs (CDs) and cigarette lighters. When the user turns the car key to the ON gear, all electrical components in the vehicle (including the engine and the vehicle voice module) are turned on, that is, the power supply in the vehicle will supply power to each electrical component in the vehicle so that each electrical component starts self-test. When the user turns the car key to the START gear, the vehicle starts. The START gear has a reset mode, and the car key will automatically bounce back to the ON gear after the vehicle is successfully started. Each of the four gears can be executed in a progressive manner. For example, after the user turns the car key to each gear, he can stay for 1 to 2 seconds before turning it to the next gear, so that the electrical components can enter the working state one by one, relieving the burden on the car battery caused by instantaneous power-on. In this example, when the user turns the car key from the ACC gear to the ON gear, the vehicle power supply can supply power to the vehicle voice module. Therefore, as long as the vehicle voice module detects that it has switched from the unpowered state to the powered state, it can determine that the vehicle has been started.

[0119] For vehicles that are started by the power button, these vehicles do not have a keyhole, but only have a power button. When the user taps the power button once, the power in the vehicle only connects to some of the electrical components in the vehicle, such as the audio system, and the dashboard lights of the vehicle are not on. When the user taps the voltage button again, the power in the vehicle connects to each electrical component in the vehicle, so that each electrical component performs a self-check, and the dashboard lights of the vehicle are on. If one or some icons on the dashboard of the vehicle are always on, it means that there is a problem with the electrical components corresponding to this or these icons. At this time, the user needs to repair these electrical components before using the vehicle to avoid traffic accidents. If all the icons on the dashboard of the vehicle are not always on, it means that the vehicle is currently in a normal state, and the user can press the voltage button again to start the vehicle. In this example, when the user taps the power button twice, the vehicle power supply can supply power to the vehicle voice module. Therefore, as long as the vehicle voice module detects that it has switched from an unpowered state to a powered state, it can be determined that the vehicle has been started.

[0120] In an optional implementation, the first association request may include the identification of the vehicle where the vehicle-mounted voice module is located (assuming it is called the first vehicle identification), and may also include the start-up time information of the vehicle where the vehicle-mounted voice module is located (assuming it is called the first start-up time information) and / or the location information of the vehicle where the vehicle-mounted voice module is located (assuming it is called the first location information). In a possible way of generating the first association request, the vehicle-mounted voice module can negotiate with the vehicle-mounted positioning module on the vehicle in advance to share the vehicle location information, and can negotiate with the vehicle-mounted timing module on the vehicle in advance to share the time information. This sharing can be achieved through the bus introduced in the above content. When a certain module periodically sends the shared information on the bus, other modules shared with the module can obtain the shared information. In this way, when the vehicle-mounted voice module detects that the vehicle is started, the vehicle-mounted voice module can immediately obtain the vehicle position located by the vehicle-mounted positioning module and the current start-up time in the vehicle-mounted timing module, and then generate the first association request based on the vehicle position, the current start-up time and the vehicle identification. It should be understood that the vehicle-mounted voice module obtaining the current startup time through the vehicle-mounted timing module is only an example. In other examples, the vehicle-mounted voice module can also obtain the time synchronized from an external server through the network as the current startup time.

[0121] Exemplarily, in the embodiment of the present application, the identification of a vehicle may refer to the vehicle identification number (VIN) of the vehicle. The VIN of a vehicle may be composed of 17 characters including the manufacturer, year, model, body type and code, engine code and assembly location of the vehicle, so the VIN of the vehicle may also be called a seventeen-digit code. Among these 17 characters, the 1st to 3rd characters are the identification code of the world manufacturer that manufactures the vehicle, indicating that the vehicle is produced by that manufacturer. The 4th to 8th characters are used to define vehicle characteristics, indicating the type and body type of the vehicle, etc. The 9th character belongs to the check digit, the value of which is calculated by a certain algorithm and is subsequently used to prevent input errors. The 10th character is used to define the model and year, which are generally specified by the manufacturer and may not be the actual production year of the vehicle, but generally the difference with the actual production year does not exceed 1 year. The 11th character is used to define the assembly plant where the vehicle is assembled. The 12th to 17th characters are used to define the factory sequence number.

[0122] Step 403: After the terminal device detects that the vehicle is started through the vehicle charging module, it sends a second association request to the cloud server.

[0123] In the embodiment of the present application, when the terminal device is coupled with the on-board charging module in the vehicle, if the vehicle where the on-board charging module is located is started, the power supply in the vehicle will supply power to the on-board charging module, and the on-board charging module can also supply power to the terminal device accordingly. In this case, as long as the terminal device detects that it has switched from an unpowered state to a powered state, the terminal device can determine that the vehicle where the coupled on-board charging module is located has a startup operation.

[0124] In an optional implementation, the second association request may include the identification of the vehicle where the on-board charging module coupled to the terminal device is located (assuming it is called the second vehicle identification), and may also include the start-up time information of the vehicle where the on-board charging module coupled to the terminal device is located (assuming it is called the second start-up time information) and / or the location information of the terminal device (assuming it is called the second location information). Wherein, the second vehicle identification can be preset in the terminal device before the terminal device detects whether the vehicle where the on-board charging module coupled to the terminal device is located is started. For example, it can be actively sent to the terminal device by any module in the vehicle where the on-board charging module is located after the terminal device is coupled to the on-board charging module, or it can be actively input on the terminal device by the user after determining the on-board voice module to be associated, and the specific details are not limited. In a possible way to generate the second association request, when the terminal device detects that the terminal device switches from an unpowered state to a powered state, the terminal device determines that the vehicle where the coupled on-board charging module is located is started, so the terminal device can obtain the terminal position located by the terminal positioning module and the current start-up time in the terminal timing module, and then generate the second association request according to the terminal position, the current start-up time and the preset vehicle identification. It should be understood that the terminal device obtaining the current startup time through the terminal timing module is only an example. In other examples, the terminal device can also obtain the time synchronized from an external server through the network as the current startup time.

[0125] In step 404 , the cloud server determines whether the first association request and the second association request match. If they do not match, step 405 is executed. If they match, step 406 is executed.

[0126] In the embodiment of the present application, the cloud server can determine whether the first association request and the second association request match in the following manner:

[0127] Method 1: When the first association request only includes the first vehicle identifier, and the second association request only includes the second vehicle identifier, the cloud server can directly determine whether the first vehicle identifier and the second vehicle identifier are the same. If they are the same, it means that the vehicle where the on-board voice module that sends the first association request is located and the vehicle where the on-board charging module coupled to the terminal device that sends the second association request is located belong to the same vehicle, and the terminal device and the on-board voice module respectively send association requests to the cloud server after the same vehicle is started. In this case, the cloud server can consider that the first association request and the second association request match. If the first vehicle identifier and the second vehicle identifier are different, it means that the vehicle where the on-board voice module that sends the first association request is located and the vehicle where the on-board charging module coupled to the terminal device that sends the second association request is located do not belong to the same vehicle, and the terminal device and the on-board voice module respectively send association requests to the cloud server after different vehicles are started. In this case, the cloud server can consider that the first association request and the second association request do not match.

[0128] Method 2: When the first association request includes the first vehicle identification and the first start-up time information, and the second association request includes the second vehicle identification and the second start-up time information, the cloud server must not only determine whether the first vehicle identification and the second vehicle identification are the same, but also determine whether the time difference between the first start-up time information and the second start-up time information does not exceed the preset start-up time difference threshold. If the judgment results are both yes, it means that the terminal device and the vehicle voice module sent association requests to the cloud server respectively after the same vehicle was started at the same time. In this case, the cloud server can consider that the first association request and the second association request match. When at least one of the above contents is no: for example, the first vehicle identification and the second vehicle identification are the same, and the time difference between the first startup time information and the second startup time information exceeds the preset startup time difference threshold, it means that the terminal device and the vehicle-mounted voice module have respectively sent association requests to the cloud server in different startups of the same vehicle. In this case, in order to avoid the historical user using the association request corresponding to the historical startup to associate the vehicle-mounted voice module (for example, after the original owner transfers the vehicle to the new owner, the new owner needs to re-associate the new owner's user account with the vehicle-mounted voice module in the vehicle) and cause the historical user to control the new user to drive the vehicle, the cloud server can consider that the first association request and the second association request do not match. For another example, when the first vehicle identification and the second vehicle identification are different, regardless of whether the time difference between the first startup time information and the second startup time information does not exceed the preset startup time difference threshold, since the terminal device and the vehicle-mounted voice module correspond to different vehicles, the cloud server can consider that the first association request and the second association request do not match.

[0129] Method 3: When the first association request includes the first vehicle identification and the first location information, and the second association request includes the second vehicle identification and the second location information, the cloud server must not only determine whether the first vehicle identification and the second vehicle identification are the same, but also determine whether the distance between the positions corresponding to the first location information and the second location information does not exceed the preset distance threshold. If the judgment results are both yes, it means that the terminal device and the vehicle voice module sent association requests to the cloud server at the same location of the same vehicle. In this case, the cloud server can consider that the first association request and the second association request match. When at least one of the above contents is no: for example, the first vehicle identification and the second vehicle identification are the same, and the distance between the positions corresponding to the first location information and the second location information exceeds the preset distance threshold, it means that although the terminal device and the vehicle-mounted voice module initiate an association request to the cloud server for the same vehicle, the terminal device and the vehicle-mounted voice module are obviously in different positions. In this case, the first association request may be sent by an illegal user at other locations instead of the user sitting in the car. Therefore, in order to avoid the situation where an illegal user forges an association request to associate the vehicle-mounted voice module when the vehicle is started, causing the illegal user to control the new user to drive the vehicle, the cloud server can consider that the first association request and the second association request do not match. For another example, when the first vehicle identification and the second vehicle identification are different, regardless of whether the distance between the positions corresponding to the first location information and the second location information does not exceed the preset distance threshold, since the terminal device and the vehicle-mounted voice module correspond to different vehicles, the cloud server can consider that the first association request and the second association request do not match.

[0130] Method 4: When the first association request includes the first vehicle identification, the first startup time information and the first location information, and the second association request includes the second vehicle identification, the second startup time information and the second location information, the cloud server must not only determine whether the first vehicle identification and the second vehicle identification are the same, but also determine whether the time difference between the first startup time information and the second startup time information does not exceed the preset startup time difference threshold, and determine whether the distance between the positions corresponding to the first location information and the second location information does not exceed the preset distance threshold. If the judgment results are all yes, it means that the terminal device and the vehicle-mounted voice module sent association requests to the cloud server at the same location after the same startup of the same vehicle. In this case, the cloud server can consider that the first association request and the second association request match. When at least one of the above contents is no, the cloud server can consider that the first association request and the second association request do not match. This method regards the situations where the terminal device and the vehicle-mounted voice module send association requests during the startup of different vehicles, the terminal device and the vehicle-mounted voice module send association requests during different startups, and the terminal device and the vehicle-mounted voice module send association requests at different locations as illegal situations, thereby being able to decide whether the two parties to be associated are legal parties based on the three factors of vehicle uniformity, startup time uniformity, and location uniformity. By judging multiple information, it helps to prevent the user account of an illegal user from being associated with the vehicle-mounted voice module of other users, thereby improving the security of associating the vehicle-mounted voice module with the user account.

[0131] Figure 5 The flowchart of a method for determining whether an association request matches provided by an embodiment of the present application is exemplarily shown. The method is applicable to a cloud server, for example Figure 1 In this example, it is assumed that the first association request includes the first vehicle identification VIN1, the first start time information T1 and the first position information P1, and the second association request includes the second vehicle identification VIN2, the second start time information T2 and the second position information P2. Figure 5 As shown, the method includes:

[0132] In step 501 , the cloud server determines whether the first vehicle identification VIN1 and the second vehicle identification VIN2 are the same. If they are the same, step 502 is executed; if they are different, step 507 is executed.

[0133] Step 502: The cloud server calculates the startup time difference based on the first startup time information T1 and the second startup time information T2:

[0134] ΔT = |T1-T2|;

[0135] Step 503: The cloud server determines whether the startup time difference ΔT is not greater than a preset startup time difference threshold T maxIf yes, execute step 504, if no, execute step 507.

[0136] In the embodiment of the present application, even if the vehicle-mounted voice module and the terminal device generate an association request for the same startup of the same vehicle, since the vehicle-mounted voice module and the terminal device obtain the startup time according to their own processes respectively, the startup time detected by the two devices may also be deviated. For example, when the vehicle is started, the various electrical units inside are awakened in sequence according to the set order. If the vehicle-mounted voice module is awakened before the vehicle-mounted charging module, the vehicle-mounted voice module detects the vehicle startup terminal device first and then the vehicle startup, so the vehicle startup time detected by the vehicle-mounted voice module will be earlier than the vehicle startup time detected by the terminal device. If the vehicle-mounted charging module is awakened before the vehicle-mounted voice module, the terminal device detects the vehicle startup first and then the vehicle startup of the vehicle-mounted voice module, and the vehicle startup time detected by the vehicle-mounted voice module will be later than the vehicle startup time detected by the terminal device. However, no matter which device is awakened first, there will always be a maximum wake-up time difference between the vehicle voice module and the vehicle charging module. When the startup time difference detected by the vehicle voice module and the terminal device is less than or equal to the maximum wake-up time difference, it can be considered that the vehicle voice module and the terminal device detect the same startup. When the startup time difference detected by the vehicle voice module and the terminal device is less than or equal to the maximum wake-up time difference, it can be considered that the vehicle voice module and the terminal device detect different startups. Based on this, the preset startup time difference threshold can be set to the maximum wake-up time difference, or set to be slightly larger than the maximum wake-up time difference.

[0137] Step 504: The cloud server calculates the distance Dis(P1, P2) between the positions corresponding to the first position information P1 and the second position information P2 according to the first position information P1 and the second position information P2.

[0138] In an optional implementation, if the vehicle-mounted positioning module and the terminal positioning module rely on GNSS technology to achieve positioning, the first position information P1 and the second position information P2 are expressed in coordinate form. In this case, assuming that the first position information P1 is (x1, y1, z1) and the second position information P2 is (x2, y2, z2), the distance Dis(P1, P2) can be:

[0139]

[0140] In another optional implementation, if the vehicle positioning module and the terminal positioning module rely on GPS technology to achieve positioning, the first position information P1 and the second position information P2 are represented by longitude (lon) and latitude (lat). In this case, assuming that the first position information P1 is (lon1, lat1), lon1 is the longitude of the vehicle position, lat1 is the latitude of the vehicle position, and the second position information P2 is (lon2, lat2), lon2 is the longitude of the terminal position, and lat2 is the latitude of the terminal position, then the distance Dis(P1, P2) can be calculated according to the following formula:

[0141] Dis(P1, P2)=R*arccos(C)*PI / 180;

[0142] C=sin(lon1)*sin(lon2)*cos(lat1–lat2)+cos(lon1)*cos(lon2);

[0143] Among them, R is the radius of the earth and PI is pi.

[0144] Step 505: The cloud server determines whether the distance Dis(P1, P2) is not greater than a preset distance threshold P max If yes, execute step 506, if no, execute step 507.

[0145] In the embodiment of the present application, since the vehicle-mounted voice module and the terminal device use different positioning modules (for example, the vehicle-mounted voice module uses the vehicle-mounted positioning module for positioning, and the terminal device uses the terminal positioning module for positioning) to locate the vehicle position and the terminal position, there may be a deviation between the vehicle position located by the vehicle-mounted voice module and the terminal position located by the terminal device, and the deviation depends on the positioning error of the vehicle-mounted positioning module and the positioning error of the terminal positioning module. Considering that the positioning error of a positioning module is usually no more than 20 meters, the positioning error of the vehicle-mounted positioning module and the positioning error of the terminal positioning module are generally no more than 40 meters. Based on this, the preset distance threshold can be set to 40 meters, or slightly greater than 40 meters.

[0146] Step 506: The cloud server determines that the first association request matches the second association request.

[0147] Step 507: The cloud server determines that the first association request and the second association request do not match.

[0148] It should be noted that, in the embodiment of the present application, the cloud server can perform the verification process of the above three information in sequence in a single-threaded manner, or can perform the verification process of the above three information in parallel in a multi-threaded manner. The above steps 501 to 507 are to verify the three information in a single-threaded manner by first judging the vehicle identification, then judging the start time, and finally judging the position. However, the present application does not limit the verification order of these three information. For example, in other optional implementations, the cloud server may also first judge the start time, then judge the vehicle identification, and finally judge the position, or the cloud server may first judge the position, then judge the start time, and finally judge the vehicle identification. When verifying the above three information in accordance with multi-threading, the cloud server may first set three threads, and use these three threads to respectively verify the above three information to obtain three verification results, and then determine whether the first association request and the second association request match according to these three verifications. After any thread verification is completed, the cloud server can release the thread to save resources in the cloud server.

[0149] Step 405, the cloud server notifies the vehicle-mounted voice module of a notification message of association failure.

[0150] In an optional implementation, after receiving the notification message of association failure, the on-board voice module can also voice broadcast the notification message of association failure, so that the user can end the association in time. Exemplarily, after hearing the notification message of association failure, the user can also reapply for association. In this case, the user not only needs to ensure that the terminal device is coupled to the on-board charging module on the vehicle, but also needs to turn off the vehicle and restart the vehicle again, so that the terminal device and the on-board voice module can re-report the association request to start a new association operation.

[0151] It should be understood that the above step 405 is only an optional implementation method for the cloud server to notify the user of the association failure. The present application does not limit the use of this method to notify the user of the result of the association failure. For example, in other optional implementation methods, the cloud server can also send a notification message of the association failure to the terminal device, so that the terminal device notifies the user of the association failure notification message through display or voice.

[0152] Step 406, the cloud server associates the user account corresponding to the terminal device with the vehicle voice module.

[0153] In the embodiment of the present application, when it is determined that the first association request matches the second association request, the cloud server can directly perform the association operation, or further verify the association operation after the further verification is passed. The further verification scheme will be specifically described in the second embodiment and will not be introduced here.

[0154] It should be noted that the terminal device in the embodiment of the present application actually refers to a terminal device with a user account. There are many possibilities for the user account corresponding to the terminal device: for example, in one possibility, the user account corresponding to the terminal device can be a user account entered by the user when activating the terminal device (such as a mobile phone number, or other information that can identify the user's identity). In another possibility, the user account corresponding to the terminal device can also be a user account registered by the user in the target APP installed on the terminal device. The user logs in to the target APP based on the user account, and interacts with the cloud server in the target APP to complete the relevant settings of the voice service corresponding to the user account. The solution for associating the user account and the vehicle-mounted voice module through the target APP will be specifically described in Example 3 and will not be introduced here.

[0155] Step 407, the cloud server notifies the vehicle voice module of a successful association notification message.

[0156] In an optional implementation, after receiving the notification message of successful association, the vehicle voice module can also voice broadcast the notification message of successful association, so that the user can obtain the association result in time. After the user hears the notification message of successful association, the user can also execute a certain response logic to indicate to the cloud server that the user has learned that the association is successful. The following are two possible response logics:

[0157] When the vehicle is also equipped with a save our souls (SOS) button (or other buttons), the cloud server can also continue to voice broadcast the prompt "If the association result is known, please press the SOS button" after controlling the vehicle voice module to voice broadcast the response message of successful association. In this way, if the user hears the response message of successful association, he can also press the vehicle's SOS button according to the prompt, and the vehicle voice module can immediately send the message to the cloud server after detecting that the SOS button has been pressed. In this way, after the cloud server sends the notification message of successful association, if it waits for the message sent by the vehicle voice module, it can be considered that the user knows that the association is successful;

[0158] The cloud server can also synchronously send a notification message of successful association to the vehicle-mounted voice module and the terminal device, so that the vehicle-mounted voice module notifies the user of the notification message by voice broadcast, and the terminal device notifies the user of the notification message by display. A confirmation button can also be set on the display interface of the terminal device. When the user hears the association result of the voice broadcast, he can also view the association result displayed by the terminal device. If the two association results are consistent, the user can click the confirmation button on the display interface of the terminal device so that the terminal device can send the trigger message to the cloud server. In this way, after the cloud server sends the notification message of successful association, if it waits until the trigger message sent by the terminal device, it can be considered that the user knows that the association is successful.

[0159] Furthermore, taking the case where the vehicle-mounted voice module returns the user's response to the cloud server, if the cloud server has not received the user's response within the preset response time, the cloud server can also resend the notification message of successful association to the vehicle-mounted voice module. When the number of re-issuances reaches the preset number of issuances and the cloud server has not received the user's response, it means that some kind of fault has occurred between the cloud server and the vehicle-mounted voice module (such as a network failure on the vehicle-mounted voice module or cloud server side, insufficient memory of the vehicle-mounted voice module, or a failure of the voice broadcast function of the vehicle-mounted voice module, etc.). In this case, the cloud server can also notify the user of the fault through the terminal device to avoid the user being in a waiting state. Alternatively, the cloud server can also send fault information to the diagnostic node to facilitate timely repair of the fault and restore normal communication.

[0160] In an optional implementation, after successfully associating the vehicle voice module and the user account, the cloud server can also generate a globally unique access code and store the association between the access code and the user account locally on the cloud server. The access code can be generated by the cloud server according to a random algorithm, for example, it can be composed of any one or a combination of any number, letter or symbol. Furthermore, the cloud server can also send the access code to the vehicle voice module simultaneously when sending a notification message of successful association, and the vehicle voice module will store the access code locally. In this way, referring to Figure 3As shown, when the subsequent user needs to access the voice navigation service of the cloud server, the user can directly send a voice message of "Hello, please open navigation". After the vehicle-mounted voice module hears the voice message, it can first check whether there is an access code locally. If there is an access code locally, the vehicle-mounted voice module can directly generate an access request based on the voice navigation service to be accessed by the user and the access code. After receiving the access request, the cloud server can find the associated user account based on the access code carried in the access request. When the associated user account has the voice navigation service permission, the cloud server can provide the voice navigation service to the vehicle-mounted voice module. When the associated user account does not have the voice navigation service permission, the cloud server can return a response message of access failure to the vehicle-mounted voice module. If there is no access code locally, the vehicle-mounted voice module can generate an association request to apply for binding according to the method in step 402 above.

[0161] In this implementation, the correspondence between the access code, the user account, and the voice service authority can be determined by the cloud server according to a mapping table stored locally. For example, Table 1 exemplifies a mapping table:

[0162] Access Code User Account Available voice services A28512 <![CDATA[User account A1]]> Voice navigation, voice Internet broadcast A28513 <![CDATA[User account A2]]> Voice Call A28514 <![CDATA[User account A3]]> Voice navigation, voice Internet broadcast, voice call

[0163] Table 1

[0164] As shown in Table 1, each access code and each user account can have a one-to-one correspondence, and each user account will have different voice service permissions according to the different voice services purchased. Taking user account A1 as an example, since user account A1 only purchased voice services of voice navigation and voice Internet broadcast, in the permission table stored locally on the cloud server, the voice services available to user account A1 only include voice navigation and voice Internet broadcast. In this case, if the user obtains the voice call service through the vehicle voice module with access code A28512, the cloud server can first query the mapping table to determine the user account corresponding to the access code A28512, that is, user account A1. After that, since the cloud server determines that user account A1 does not have the permission for the voice call service, the cloud server will return a response message of access failure to the vehicle voice module. Of course, if the subsequent user purchases the voice call service again through user account A1, the cloud server will also add the voice call service to the voice services available to user account A1 in the permission table stored locally.

[0165] It should be understood that in the present application, the operation of issuing the access code can also be issued at any stage after successful association. The present application does not limit the access code to be issued together with the notification message of successful association. For example, it can also be issued some time after the notification message of successful association is issued.

[0166] It should be understood that the above step 407 is only an optional implementation method for the cloud server to notify the user of successful association. The present application does not limit the use of this method to notify the user of the association result. For example, in another optional implementation method, the cloud server can also send a notification message of successful association to the terminal device, so that the terminal device notifies the user of the successful association notification message through display or voice.

[0167] In the first embodiment, the terminal device and the vehicle voice module can report the association request to the cloud server by using the vehicle startup operation, so that the server can perform the association audit operation according to the association request received respectively. This method does not require manual input of user information to the server, nor does it require manual audit, which helps to avoid the problems of low efficiency and large errors caused by manual participation in the association scheme, and improves the efficiency and accuracy of the user account corresponding to the vehicle voice module and the terminal device. Furthermore, this association scheme only requires the vehicle to have a startup function and the vehicle charging module to be implemented. It does not require the installation of a complex vehicle system in the vehicle, nor does it require the vehicle to have a display screen and near-field communication function. Therefore, this association method has low requirements for the vehicle, which can not only help save the vehicle's entire vehicle manufacturing cost, but also can be applied to most vehicles at this stage (for example, it can be applied to the association of user accounts and vehicle voice modules in vehicles without display screens and near-field communication capabilities). This association scheme has a wide range of application scenarios.

[0168] Based on the first embodiment, several possible implementations of the solution in the first embodiment are introduced below through the second embodiment and the third embodiment.

[0169] [Example 2]

[0170] Figure 6 The flowchart of the vehicle-mounted association method provided in the second embodiment of the present application is exemplarily shown. The method is applicable to a terminal device, a vehicle-mounted voice module and a cloud server, for example Figure 1 The terminal device, vehicle voice module and cloud server are shown. Before the method is executed, the vehicle is not started, and the terminal device is coupled to the vehicle charging module in the vehicle. For example, the terminal device and the vehicle charging module can be coupled together by the user. Figure 6 As shown, the method includes:

[0171] Step 601, after the vehicle voice module detects that the vehicle is started, it determines whether an access code is stored in the vehicle voice module. If so, step 602 is executed, if not, step 607 is executed.

[0172] Step 602: The vehicle-mounted voice module generates a voice service request according to the access code (ie, the identification of the vehicle where the vehicle-mounted voice module is located) and the identification of the voice service to be accessed.

[0173] Step 603: The vehicle-mounted voice module sends the voice service request to the cloud server.

[0174] Step 604, the cloud server parses the voice service request, obtains the access code and the identifier of the voice service to be accessed, and determines whether the user account corresponding to the access code has the authority to use the voice service to be accessed. If not, execute step 605; if yes, execute step 606.

[0175] Step 605: The cloud server broadcasts a notification message of voice service failure to the user through the vehicle voice module. For example, the cloud server may also notify the reason for the voice service failure through the vehicle voice module, such as the access code does not exist, the access code has expired (such as the user account has not been paid), or the access code authority is low (such as the user accessing a voice service that has not been purchased in the user account).

[0176] Step 606: The cloud server provides the user with the voice service to be accessed through the vehicle-mounted voice module.

[0177] Step 607: The vehicle voice module sends a first association request to the cloud server, wherein the first association request may include one or more of the first vehicle identification, the first start time information, and the first location information.

[0178] Step 608: After the terminal device detects that the vehicle is started through the vehicle charging module, it sends a second association request to the cloud server. The second association request may include one or more of the second vehicle identification, the second start time information, and the second location information.

[0179] Step 609: The cloud server determines whether the first association request and the second association request match. If they match, step 610 is executed; if they do not match, step 619 is executed. For specific matching methods, please refer to the above Figure 4 The detailed process described in step 404 in will not be repeated here.

[0180] Step 610: The cloud server generates first verification information and sends the first verification information to the vehicle-mounted voice module.

[0181] In the above step 610, the first verification information may be unique verification information generated by the cloud server according to a certain rule. The first verification information may be composed of one or more of letters, numbers, symbols or words, without specific limitation. For example, in order to reduce the error of the subsequent voice broadcast of the first verification information by the vehicle voice module, the present application may set the first verification information to a 6-digit random number, which can take into account the security of subsequent verification without being too complicated.

[0182] Step 611: the vehicle-mounted voice module voice broadcasts the first verification information and prompts the user to input the first verification information on the terminal device.

[0183] Step 612: The terminal device sends the second verification information input by the user to the cloud server. The second verification information is determined by the user according to the first verification information prompted by the terminal device. Specifically, the second verification information can be the same as the first verification information, or can be a simple deformation or transformation of the first verification information.

[0184] In step 613 , the cloud server determines whether the first verification information sent and the second verification information reported by the terminal device match. If they match, step 614 is executed; if they do not match, step 619 is executed.

[0185] In the embodiment of the present application, the cloud server can determine whether the first verification information and the second verification information match in the following manner:

[0186] The cloud server can directly determine whether the content in the first verification information and the content in the second verification information are completely consistent. If they are completely consistent, it can be considered that the first verification information and the second verification information match. If there is a partial or complete inconsistency in the content, it can be considered that the first verification information and the second verification information do not match. This method is more suitable for scenarios where the first verification information and the second verification information only include numbers. In this scenario, the result of the voice broadcast is unique, and the second verification information input by the user is the verification information heard by the user. Therefore, as long as there are inconsistent numbers in the second verification information received by the cloud server and the first verification information issued by the cloud server, it means that the second verification information received by the cloud server is not the verification information entered by the user, but may be sent to the cloud server by an illegal user who invaded the user's association process. In this case, by considering the verification as failed when the first verification information and the second verification information are completely inconsistent, it can prevent illegal users from binding other users' in-vehicle voice modules through other users' association processes, thereby ensuring the security of the association process. Or,

[0187] The cloud server can first calculate the degree of match between the content in the first verification information and the content in the second verification information. When the degree of match is not less than the preset degree of match, the first verification information and the second verification information can be considered to match. When the degree of match is less than the preset degree of match, the first verification information and the second verification information can be considered to be mismatched. This method is more suitable for scenarios where the first verification information and the second verification information also include text or letters. In this scenario, the voice broadcast of text or letters may have non-standard pronunciation, or there may be problems with the listener's self-thinking and understanding, so the voice broadcast content heard by the user may have partial deviations from the first verification information. Therefore, in order to avoid the occurrence of misjudgment mismatch caused by voice broadcast when the first verification information and the second verification information are actually the same, even if the first verification information and the second verification information are not completely consistent in degree of match, as long as the proportion of this inconsistency is less than the preset deviation, the cloud server can also consider that the first verification information and the second verification information match.

[0188] Step 614, the cloud server associates the user account corresponding to the terminal device with the vehicle voice module.

[0189] Step 615: The cloud server displays a notification message of successful association to the user through the terminal device.

[0190] Step 616, the cloud server broadcasts a notification message of successful association to the user through the vehicle voice module, and prompts the user to confirm the association result on the display interface of the terminal device. In this case, after the user hears the prompt, the user can compare the association result heard by voice with the association result displayed on the terminal device. When the two association results are consistent, the user can click the confirmation button below the association result displayed on the terminal device.

[0191] Step 617: After the terminal device detects that the user clicks on the terminal device to confirm the association result, it sends a response message to the cloud server, where the response message is used to indicate that the user has learned that the association is successful.

[0192] Step 618, the cloud server generates an access code corresponding to the vehicle-mounted voice module, and sends the access code to the vehicle-mounted voice module so that the vehicle-mounted voice module saves it locally.

[0193] After the above step 618, if the user sends a voice to the vehicle voice module to request a certain voice service (for example, voice to open the window), the vehicle voice module will know that it has the access code, so the vehicle voice module can directly send an access request to the cloud server according to the access code and the user's voice service request. After the cloud server determines that the user account corresponding to the access code has the authority to open the window by voice based on the mapping table stored locally, it can send a window control instruction to the window remote control device in the vehicle so that the window remote control device opens the window. After the window is opened, the cloud server can also broadcast the access result that the window has been opened to the user through the vehicle voice module.

[0194] Step 619: The cloud server broadcasts a notification message of association failure through the vehicle-mounted voice module.

[0195] In the second embodiment, the cloud server will go through two verification processes before associating the user account with the vehicle voice module. The first verification is to verify that the user account applying for association and the association applied for by the vehicle voice module belong to the same association based on information such as vehicle consistency, startup time consistency and location consistency. The second verification is to confirm the association between the user account and the vehicle voice module after the above verification is successful, so as to avoid the occurrence of misjudgment in the first verification. In this way, by using multiple information to comprehensively complete the verification operation in these two verifications, the cloud server can associate the correct user account and the vehicle voice module with a high probability, which helps to increase the possibility of associating the user account of an illegal user with the vehicle voice module and improve the security of the association.

[0196] In the embodiment of the present application, the interaction between the terminal device and the cloud server can also be achieved through the target APP on the terminal device. Among them, the target APP can be an APP specially developed for associating the vehicle voice module and the user account, or it can be an APP used for other application functions in the terminal device, such as AI audio, without specific limitation. When the target APP is an APP used for other application functions in the terminal device, the algorithm corresponding to the association method in this application can be preset in the new version of the target APP. In this way, the user only needs to perform the operation of upgrading the target APP to enable the target APP to also have the function of associating the vehicle voice module and the user account.

[0197] The following is an example of the interface operation process of implementing the above association solution based on the target APP on the terminal device. In order to facilitate the introduction of the solution, it is assumed that the first verification information is a string of random numbers:

[0198] Figure 7 (a) shows an exemplary interface diagram of a terminal device provided in an embodiment of the present application. Figure 7As shown in (a), the terminal device interface may be provided with multiple applications, such as calendar, clock, call log, information, settings, gallery, one-key lock screen, video call and target APP (i.e. Figure 7 When the user needs to perform an association operation, the user can click on the target APP, then register and log in (if the user has registered a user account before, the user can log in directly) to enter the main interface of the target APP.

[0199] Figure 7 (b) shows an exemplary schematic diagram of the main interface in a target APP provided in an embodiment of the present application, such as Figure 7 As shown in (b), there are multiple function buttons in the main interface of the target APP, such as the add vehicle button, delete vehicle button and change vehicle button. When the user needs to associate the vehicle voice module of a certain vehicle with the user account, the user can click the add vehicle button on the main interface to indicate that the user has the need to bind the vehicle. When the target APP detects the click operation, the target APP can generate a request message for adding a vehicle and send it to the cloud server. The cloud server sends the relevant information of the add vehicle interface to the target APP, so that the target APP loads the relevant information of the add vehicle interface, thereby switching from the main interface to the add vehicle interface.

[0200] Figure 7 (c) shows an example of a schematic diagram of an interface for adding a vehicle in a target APP provided in an embodiment of the present application. Figure 7 As shown in (c), a VIN input box may be displayed on the vehicle adding interface. When the user wants to associate the user account with the vehicle voice module of a certain vehicle, the user may enter the VIN of the vehicle to be associated in the VIN input box, so that the target APP switches from the vehicle adding interface to the start prompt interface; Figure 7 (d) shows an exemplary schematic diagram of a startup prompt interface in a target APP provided in an embodiment of the present application, such as Figure 7 As shown in (d), the startup prompt interface displays a text message "Please couple the terminal device and the vehicle charging module before starting the operation." It should be understood that Figure 7 (d) is only an exemplary description, and any solution that can prompt the user to couple the terminal device and the vehicle charging module before starting the operation through the interface display is within the protection scope of this application. Figure 7 (e) shows an exemplary schematic diagram of another start prompt interface in the target APP provided in an embodiment of the present application. Figure 7 In the example (e), the target APP uses a combination of icons and text to prompt the user to perform the above two operations. Figure 7As shown in (e), in an optional implementation, a confirmation button may also be displayed on the startup prompt interface. After the user completes the above two operations, the user may also click the confirmation button to switch the target APP from the startup prompt interface to the verification interface.

[0201] Figure 7 (f) in the figure exemplarily shows a verification interface diagram in a target APP provided in an embodiment of the present application, such as Figure 7 As shown in (f), a random number input box may be provided in the verification interface. After the user performs the above two operations, the terminal device, the vehicle-mounted voice module and the cloud server will start the association process according to the scheme in Example 1 or Example 2. After that, the cloud server will send a string of random numbers generated to the vehicle-mounted voice module, and let the vehicle-mounted voice module voice broadcast the string of random numbers. After the user hears the random number broadcast by voice, the user can enter the random number heard on the verification interface of the target APP, so that the terminal device can report the string of random numbers to the cloud server for further verification. Refer to Figure 7 As shown in (f), when the random number is a 6-digit random number, each random number in the verification interface can correspond to an input box.

[0202] The following is an introduction to the specific implementation process of associating the user account and the vehicle voice module through the target APP through Example 3.

[0203] [Example 3]

[0204] Figure 8 The flowchart of the vehicle-mounted association method provided in the third embodiment of the present application is exemplarily shown. The method is applicable to a user using a terminal device, a target APP in the terminal device, a vehicle-mounted voice module and a cloud server, for example Figure 1 The user, terminal device (assuming the target APP is installed on the terminal device), vehicle voice module and cloud server are shown. Figure 8 As shown, the process includes the following steps:

[0205] Step 801: A user registers a user account on a target APP of a terminal device.

[0206] In the above step 801, the operation of registering a user account can be performed when the user purchases the vehicle, or at any time after the user purchases the vehicle, for example, the user performs the registration operation after driving the newly purchased vehicle home. This method does not require the user to register a user account according to the instructions of the salesperson when purchasing the vehicle, nor does it require the salesperson to synchronize the user account and other related information to the cloud server, thereby helping to protect the security of the user account and improve the user's privacy protection.

[0207] Step 802: The target APP of the terminal device generates a registration request based on the registration information input by the user, and sends the registration request to the cloud server. The registration information may include the user account and login password, and may also include other information, such as name, gender, age, home address, and ID number, etc., which are not specifically limited.

[0208] In the above step 802, the user account may refer to the user's mobile phone number, or may refer to an identifier assigned to the user by the cloud server, or may refer to other information that can be used to uniquely identify the user.

[0209] For example, in order to ensure that the registration request is not tampered with during the sending process, the target APP may first encrypt the registration request and then send the encrypted registration request to the cloud server. Alternatively, in order to improve the registration efficiency, the target APP may first compress the registration request and then send the compressed registration request to the cloud server. Alternatively, the target APP may first compress the registration request, then encrypt the compressed registration request, and finally send the encrypted compressed registration request to the cloud server, so as to improve the security of registration while quickly transmitting the registration request.

[0210] Step 803: After the user account is successfully registered, the cloud server returns a registration success response message to the target APP in the terminal device.

[0211] In the above step 803, the cloud server may first parse the registration request to obtain the user account and login password, and then create a new folder locally. The folder may be named after the user account of the user, or may be named after other unique identifiers that can mark the user. Afterwards, the cloud server may store the user account and login password carried in the registration request in the folder. Exemplarily, before generating the folder corresponding to the user account, the cloud server may also query whether the folder corresponding to the user already exists in the cloud server. If so, it means that the user has registered a user account before, so the cloud server can directly return a response message of registration failure to the target APP. If not, it means that the user has not registered a user account, so the cloud server can create a folder and perform the corresponding storage operation. After the storage is completed, the cloud server determines that the user account is successfully registered, so that the cloud server can send a response message of successful registration to the target APP.

[0212] Step 804: The target APP in the terminal device displays a response message of successful registration to the user.

[0213] Step 805: The user uses the user account to log in to the target APP in the terminal device and applies for an associated vehicle.

[0214] In the above step 805, the user can directly switch to the login interface from the response interface of successful registration, or can first close the target APP and then reopen the target APP to directly enter the login interface. Afterwards, the user fills in the user account and login password on the login interface, and clicks the login button to trigger the target APP to generate a login request and send it to the cloud server. Afterwards, the cloud server finds the corresponding folder according to the user account carried in the login request, and verifies whether the login password entered by the user is the login password corresponding to the user account. If so, the verification is successful, and the cloud server can return the main interface information to the target APP in the terminal device, so that the target APP loads the main interface information and switches to the main interface. If not, the verification fails, and the cloud server can return a login failure response message to the target APP in the terminal device, so that the target APP displays the login failure to the user. The interaction process between the target APP and the cloud server involved in this part is relatively cumbersome, and has little to do with the invention point in this scheme. Therefore, the embodiment of the present application is only briefly described. Figure 6 The “Login” displayed in the figure indicates this part of the content, but this does not limit the specific implementation scheme of the login in this application.

[0215] Step 806: The target APP in the terminal device prompts the user to enter the vehicle VIN.

[0216] Step 807 , the user enters the vehicle VIN on the target APP interface.

[0217] Step 808, after detecting that the user has input the vehicle VIN, the target APP in the terminal device prompts the user to couple the terminal device and the on-board charging module in the vehicle, and prompts the user to start the vehicle after the coupling is completed.

[0218] In the above step 808, after the target APP detects that the user enters the VIN of the vehicle to be associated in the vehicle VIN input box, the target APP can first save the vehicle VIN, and then switch from the add vehicle interface to the start prompt interface. For example, it can switch to the start prompt interface by interacting with the cloud server, or it can directly add the corresponding prompt information according to the response logic corresponding to the add vehicle interface, and the specific details are not limited.

[0219] In step 809, the user first couples the terminal device with the vehicle-mounted charging module in the vehicle to be associated, and then starts the vehicle to be associated.

[0220] For example, if the vehicle charging module is charged by wired charging, the user can connect the terminal device to the vehicle charging interface of the vehicle charging module through the charging cable. If the vehicle charging module is charged by wireless charging, the user can place the terminal device on the wireless charging plate corresponding to the vehicle charging module.

[0221] Step 811, the target APP on the terminal device detects the power supply status of the terminal device in a periodic manner. Once it detects that the terminal device switches from the non-powered state to the powered state, it is confirmed that the vehicle charging module is powering the terminal device and the startup operation is performed in the vehicle. Therefore, the target APP on the terminal device can send a second association request to the cloud server. The second association request includes the VIN of the vehicle where the vehicle charging module is located, the startup time information of the vehicle where the vehicle charging module is located, and the location information of the terminal device.

[0222] Exemplarily, before the above step 811, when the user installs the target APP into the terminal device, the user can choose to agree that the target APP obtains the power supply status, location information and time information of the terminal device. In this way, after the vehicle is started, the on-board charging module in the vehicle supplies power to the terminal device, and the target APP can determine that the terminal device switches to the power supply status according to the power supply status shared by the terminal device. Therefore, the target APP can obtain the location information and time information shared by the terminal device, and then generate the above second association request in combination with the vehicle VIN entered by the user in step 607. Among them, the power supply status shared by the terminal device can be shared to the target APP by the on-board charging module, the location information shared by the terminal device can be shared to the target APP by the on-board positioning module, and the time information shared by the terminal device can be shared to the target APP by the on-board timing module, and of course, it can also be obtained by the target APP from the network.

[0223] Step 810, the vehicle voice module detects its own power-on state in a periodic manner. Once it detects that it switches from the non-powered state to the powered state, it is confirmed that the startup operation is performed in the vehicle, so the vehicle voice module can send a first association request to the cloud server. The first association request includes the VIN of the vehicle where the vehicle voice module is located, the startup time information of the vehicle where the vehicle voice module is located, and the location information of the vehicle where the vehicle voice module is located.

[0224] In step 812, the cloud server matches each piece of information in the first association request and the second association request. If each piece of information matches successfully, step 813 is executed. If one or more pieces of information fail to match successfully, step 821 is executed.

[0225] Step 813: The cloud server generates a string of random numbers and sends it to the vehicle voice module.

[0226] Step 814: the vehicle-mounted voice module voice broadcasts the string of random numbers and voice prompts the user to enter the string of random numbers in the target APP.

[0227] Step 815: The user enters a random number in the target APP.

[0228] Step 816: After the target APP in the terminal device detects that the user input is completed, it can report the random number input by the user to the cloud server.

[0229] In step 817 , the cloud server compares the random number sent by the cloud server with the random number reported by the target APP to determine whether the two strings of random numbers are consistent. If they are consistent, execute step 618 ; if they are inconsistent, execute step 621 .

[0230] Step 818, the cloud server associates the in-vehicle voice module with the user account registered by the user through the target APP.

[0231] Step 819: After the association is successful, the cloud server sends a notification message of successful association to the vehicle voice module.

[0232] Step 820: The vehicle-mounted voice module voice broadcasts a notification message of successful association to the user.

[0233] Step 821, the cloud server broadcasts a notification message of association failure to the user through the vehicle voice module.

[0234] In the above-mentioned fourth embodiment, the operation of associating the in-vehicle voice module with the user account can be completed by using the target APP on the terminal device. Therefore, this method only needs to update the target APP so that it has the associated related functions (for example, after purchasing a vehicle, the user can first determine whether the target APP has the associated function. If it does, the associated function can be directly used to perform the associated operation. If it does not, the target APP can be upgraded first. After the upgrade is completed, the target APP can be opened to perform the associated operation). There is no need to customize the development of the vehicle system or other modules (such as display screens or near-field communication modules), which makes it easier to implement and the cost is lower.

[0235] Fig. 9 The following is a schematic diagram of an application scenario corresponding to the fourth embodiment of the present application. Fig. 9As shown, according to the scheme in the fourth embodiment, after purchasing a vehicle, the user can first download a target APP on the mobile phone. The target APP can be an APP developed by the manufacturer or seller of the vehicle and mounted in the application market. After purchasing the vehicle, the user can download the target APP in the application market, and log in to the target APP after registering the user account and enter the vehicle VIN, and then use the charging cable to connect the mobile phone and the vehicle charging interface, and start the vehicle. In this way, the vehicle-mounted voice module in the vehicle detects that the vehicle is started and reports the first association request to the cloud server. After the target APP detects that the terminal device is charged, it confirms that the vehicle is started and reports the second association request to the cloud server. After verifying that the first association request reported by the vehicle-mounted voice module matches the second association request reported by the target APP, the cloud server can associate the vehicle-mounted voice module with the user account currently logged in on the target APP, and then send the association result to the vehicle-mounted voice module, so that the vehicle-mounted voice module voice broadcasts the association result to the user. This method only requires the user to connect the mobile phone and the vehicle-mounted charging interface after purchasing the car and perform the startup operation, without the user having to wait for a long time for review or perform other operations, so that the user experience is better.

[0236] It should be noted that the names of the above-mentioned information are only examples. With the evolution of communication technology, the names of any of the above-mentioned information may change. However, no matter how the names change, as long as their meanings are the same as those of the above-mentioned information in this application, they fall within the scope of protection of this application.

[0237] The above mainly introduces the solution provided by the present application from the perspective of the interaction between various network elements. It can be understood that in order to realize the above functions, the above-mentioned network elements include hardware structures and / or software modules corresponding to the execution of various functions. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in this document, the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0238] According to the above method, Fig.10 A schematic diagram of the structure of a vehicle-mounted association device provided in an embodiment of the present application is shown in FIG. Fig.10 As shown, the device can be a cloud server, an in-vehicle voice module or a terminal device, or it can be a chip or circuit, such as a chip or circuit that can be set in a cloud server, a chip or circuit that can be set in a in-vehicle voice module, or a chip or circuit that can be set in a terminal device.

[0239] Furthermore, the vehicle-mounted association device 1001 may further include a bus system, wherein the processor 1002 , the memory 1004 , and the transceiver 1003 may be connected via the bus system.

[0240] It should be understood that the processor 1002 may be a chip. For example, the processor 1002 may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0241] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor 1002 or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in the processor 1002 for execution. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 1004, and the processor 1002 reads the information in the memory 1004 and completes the steps of the above method in conjunction with its hardware.

[0242] It should be noted that the processor 1002 in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor can be combined and performed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0243] It can be understood that the memory 1004 in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0244] When the vehicle-mounted association device 1001 corresponds to the cloud server in the above method, the vehicle-mounted association device may include a processor 1002, a transceiver 1003 and a memory 1004. The memory 1004 is used to store instructions, and the processor 1002 is used to execute the instructions stored in the memory 1004 to implement the above method. Figures 1 to 9 A related scheme of the cloud server in any one or more of the corresponding methods shown in .

[0245] When the vehicle-mounted association device 1001 is the above-mentioned cloud server, the vehicle-mounted association device 1001 can be used to execute the method executed by the cloud server in any one of the above-mentioned embodiments 1 to 3.

[0246] The vehicle-mounted association device 1001 is the above-mentioned cloud server, and when executing the first embodiment, the vehicle-mounted association device 1001 can execute: receiving a first association request sent by the vehicle-mounted voice module through the transceiver 1003, and the first association request is generated after the vehicle-mounted voice module detects that the first vehicle where the vehicle-mounted voice module is located is started. Receive a second association request sent by the terminal device through the transceiver 1003, and the second association request is generated after the terminal device detects that the second vehicle is started, and the terminal device is coupled to the vehicle-mounted charging module in the second vehicle. Afterwards, if it is determined that the first association request and the second association request match, the user account corresponding to the terminal device and the vehicle-mounted voice module can be associated, so that the server provides voice services for the vehicle-mounted voice module according to the user account corresponding to the terminal device.

[0247] When the vehicle-mounted association device 1001 corresponds to the vehicle-mounted voice module in the above method, the vehicle-mounted association device may include a processor 1002, a transceiver 1003 and a memory 1004. The memory 1004 is used to store instructions, and the processor 1002 is used to execute the instructions stored in the memory 1004 to implement the above method. Figures 1 to 9 A related scheme of the vehicle-mounted voice module in any one or more of the corresponding methods shown in .

[0248] When the vehicle-mounted association device 1001 is the above-mentioned vehicle-mounted voice module, the vehicle-mounted association device 1001 can be used to execute the method executed by the vehicle-mounted voice module in any one of the above-mentioned embodiments 1 to 3.

[0249] The vehicle-mounted association device 1001 is the above-mentioned vehicle-mounted voice module, and when executing Example 1, the vehicle-mounted association device 1001 can execute: after detecting that the first vehicle where the vehicle-mounted voice module is located is started, a first association request is generated, and the first association request is sent to the server through the transceiver 1003, so that the server can associate the user account corresponding to the terminal device with the vehicle-mounted voice module in combination with the first association request and the second association request sent by the terminal device.

[0250] When the vehicle-mounted association device 1001 corresponds to the terminal device in the above method, the vehicle-mounted association device may include a processor 1002, a transceiver 1003 and a memory 1004. The memory 1004 is used to store instructions, and the processor 1002 is used to execute the instructions stored in the memory 1004 to implement the above method. Figures 1 to 9 A related scheme of a terminal device in any one or more corresponding methods shown in .

[0251] When the vehicle-mounted association device 1001 is the above-mentioned terminal device, the vehicle-mounted association device 1001 can be used to execute the method executed by the terminal device in any one of the above-mentioned embodiments 1 to 3.

[0252] The vehicle-mounted association device 1001 is the above-mentioned terminal device, and when executing Example 1, the vehicle-mounted association device 1001 can execute: generating a second association request after detecting that the second vehicle is started through the vehicle-mounted charging module, and sending the second association request to the server through the transceiver 1003, so that the server combines the first association request and the second association request sent by the vehicle-mounted voice module to associate the user account corresponding to the terminal device with the vehicle-mounted voice module.

[0253] For the concepts, explanations, detailed descriptions and other steps involved in the vehicle-mounted association device and related to the technical solution provided in the embodiment of the present application, please refer to the description of these contents in the aforementioned method or other embodiments, which will not be repeated here.

[0254] Based on the above embodiments and the same concept, Fig.11 A schematic diagram of a vehicle-mounted association device provided in an embodiment of the present application, such as Fig.11 As shown, the vehicle-mounted association device 1101 can be a cloud server, or a chip or circuit, such as a chip or circuit that can be set in a cloud server.

[0255] The vehicle-mounted association device may correspond to the cloud server in the above method. Figures 1 to 9 The steps performed by the cloud server in any one or more of the corresponding methods shown in . The vehicle-mounted association device may include an association unit 1102 and a transceiver unit 1103 .

[0256] When the vehicle-mounted association device 1101 is the above-mentioned cloud server, the transceiver unit 1103 can receive the first association request sent by the vehicle-mounted voice module, which is generated after the vehicle-mounted voice module detects that the first vehicle where the vehicle-mounted voice module is located is started, and the transceiver unit 1103 can also receive the second association request sent by the terminal device, which is generated after the terminal device detects that the second vehicle is started, and the terminal device is coupled to the vehicle-mounted charging module in the second vehicle. Correspondingly, if the association unit 1102 determines that the first association request and the second association request match, it can associate the user account corresponding to the terminal device with the vehicle-mounted voice module, so that the cloud server can provide voice services for the vehicle-mounted voice module according to the user account corresponding to the terminal device.

[0257] The transceiver unit 1103 may be a sending unit or a transmitter when sending information, and may be a receiving unit or a receiver when receiving information. The transceiver unit 1103 may be a transceiver, and this transceiver, transmitter or receiver may be a radio frequency circuit. When the vehicle-mounted association device 1101 includes a storage unit, the storage unit is used to store computer instructions, and the association unit 1102 is connected to the storage unit in communication, and the association unit 1102 executes the computer instructions stored in the storage unit, so that the vehicle-mounted association device 1101 can be used to execute the method executed by the cloud server in any of the above-mentioned embodiments 1 to 3. Among them, the association unit 1102 can be a general-purpose central processing unit (CPU), a microprocessor, or an application specific integrated circuit (ASIC).

[0258] When the vehicle-mounted association device 1101 is a chip, the transceiver unit 1103 may be an input and / or output interface, a pin or a circuit, etc. The association unit 1102 may execute the computer execution instructions stored in the storage unit, so that the chip in the vehicle-mounted association device 1101 executes the method executed by any one of the embodiments 1 to 3. Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc. The storage unit may also be a storage unit located outside the chip in the vehicle-mounted association device 1101, such as a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc.

[0259] For the concepts, explanations, detailed descriptions and other steps related to the technical solutions provided in the embodiments of the present application and involved in the vehicle-mounted association device 1101, please refer to the descriptions of these contents in the aforementioned methods or other embodiments, which will not be repeated here.

[0260] Based on the above embodiments and the same concept, Fig.12 A schematic diagram of a vehicle-mounted association device provided in an embodiment of the present application, such as Fig.12 As shown, the vehicle-mounted association device 1201 can be a vehicle-mounted voice module, or a chip or circuit, such as a chip or circuit that can be set in a vehicle-mounted voice module.

[0261] The vehicle-mounted association device may correspond to the vehicle-mounted voice module in the above method. Figures 1 to 9 The vehicle-mounted association device may include a generating unit 1202 and a transceiver unit 1203.

[0262] When the vehicle-mounted association device 1201 is the above-mentioned vehicle-mounted voice module, the generation unit 1202 can generate a first association request after detecting that the first vehicle where the vehicle-mounted voice module is located is started, and the transceiver unit 1203 can send the first association request to the cloud server, so that the cloud server can associate the user account corresponding to the terminal device with the vehicle-mounted voice module in combination with the first association request and the second association request sent by the terminal device.

[0263] The transceiver unit 1203 can be a sending unit or a transmitter when sending information, and can be a receiving unit or a receiver when receiving information. The transceiver unit 1203 can be a transceiver, and this transceiver, transmitter or receiver can be a radio frequency circuit. When the vehicle-mounted association device 1201 includes a storage unit, the storage unit is used to store computer instructions, and the generation unit 1202 is connected to the storage unit in communication, and the generation unit 1202 executes the computer instructions stored in the storage unit, so that the vehicle-mounted association device 1201 can be used to execute the method executed by the vehicle-mounted voice module in any of the above-mentioned embodiments 1 to 3. Among them, the generation unit 1202 can be a general-purpose central processing unit (CPU), a microprocessor, and an application-specific integrated circuit (Application Specific Intergrated Circuit, ASIC).

[0264] When the vehicle-mounted association device 1201 is a chip, the transceiver unit 1203 may be an input and / or output interface, a pin or a circuit, etc. The generation unit 1202 may execute the computer execution instructions stored in the storage unit, so that the chip in the vehicle-mounted association device 1201 executes the method executed by any one of the embodiments 1 to 3. Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc. The storage unit may also be a storage unit located outside the chip in the vehicle-mounted association device 1201, such as a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc.

[0265] For the concepts, explanations, detailed descriptions and other steps related to the technical solutions provided in the embodiments of the present application and involved in the vehicle-mounted association device 1201, please refer to the descriptions of these contents in the aforementioned method or other embodiments, which will not be repeated here.

[0266] Based on the above embodiments and the same concept, Fig.13 A schematic diagram of a vehicle-mounted association device provided in an embodiment of the present application, such as Fig.13 As shown, the vehicle-mounted association device 1301 can be a terminal device, or a chip or a circuit, such as a chip or circuit that can be set in a terminal device.

[0267] The vehicle-mounted association device may correspond to the terminal device in the above method. Figures 1 to 9 The steps performed by the terminal device in the method corresponding to any one or more of the items shown in . The vehicle-mounted association device may include a generating unit 1302 and a transceiver unit 1303 .

[0268] When the vehicle-mounted association device 1301 is the above-mentioned terminal device, the generation unit 1302 can generate a second association request after detecting that the second vehicle is started through the vehicle-mounted charging module, and the transceiver unit 1303 can send the second association request to the cloud server, so that the cloud server can associate the user account corresponding to the terminal device with the vehicle-mounted voice module in combination with the first association request and the second association request sent by the vehicle-mounted voice module.

[0269] The transceiver unit 1303 may be a sending unit or a transmitter when sending information, and may be a receiving unit or a receiver when receiving information. The transceiver unit 1303 may be a transceiver, and this transceiver, transmitter or receiver may be a radio frequency circuit. When the vehicle-mounted association device 1301 includes a storage unit, the storage unit is used to store computer instructions, and the generation unit 1302 is connected to the storage unit in communication, and the generation unit 1302 executes the computer instructions stored in the storage unit, so that the vehicle-mounted association device 1301 can be used to execute the method executed by the terminal device in any of the above-mentioned embodiments 1 to 3. Among them, the generation unit 1302 can be a general-purpose central processing unit (CPU), a microprocessor, or an application specific integrated circuit (ASIC).

[0270] When the vehicle-mounted association device 1301 is a chip, the transceiver unit 1303 may be an input and / or output interface, a pin or a circuit, etc. The generation unit 1302 may execute the computer execution instructions stored in the storage unit, so that the chip in the vehicle-mounted association device 1301 executes the method executed by any one of the embodiments 1 to 3. Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc. The storage unit may also be a storage unit located outside the chip in the vehicle-mounted association device 1301, such as a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc.

[0271] For the concepts, explanations, detailed descriptions and other steps related to the technical solutions provided in the embodiments of the present application and involved in the vehicle-mounted association device 1301, please refer to the descriptions of these contents in the aforementioned method or other embodiments, which will not be repeated here.

[0272] It should be understood that the division of the above-mentioned vehicle-mounted association devices 1101, 1201 and 1301 is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. In the embodiment of the present application, the transceiver unit 1103, the transceiver unit 1203 and the transceiver unit 1303 can be composed of the above-mentioned Fig.10 The transceiver 1003 is implemented, and the association unit 1102, the generation unit 1202 and the generation unit 1302 can be implemented by the above Fig.10 The processor 1002 is implemented.

[0273] According to the method provided in the embodiment of the present application, the present application also provides a computer program product, which includes: a computer program code, when the computer program code is run on a computer, the computer executes Figures 1 to 9 A method according to any one of the embodiments shown.

[0274] According to the method provided in the embodiment of the present application, the present application also provides a computer-readable storage medium, which stores a program code, and when the program code is run on a computer, the computer executes Figures 1 to 9 A method according to any one of the embodiments shown.

[0275] According to the method provided in the embodiment of the present application, the present application also provides a vehicle, which may include an on-board voice module and an on-board charging module, wherein the on-board voice module is used to connect to the cloud server, and the on-board charging module is used to couple the terminal device; the on-board voice module can be used to perform the above Figures 1 to 9 The steps performed by the vehicle voice module in any one or more corresponding methods shown in , or the steps performed by the vehicle voice module in any one of the above embodiments 1 to 3, the terminal device can be used to perform the above Figures 1 to 9 The steps performed by the terminal device in any one or more corresponding methods shown in , or the steps performed by the terminal device in any one of the above embodiments 1 to 3.

[0276] According to the method provided in the embodiment of the present application, the present application also provides a vehicle networking system, which includes the aforementioned cloud server, one or more vehicle-mounted voice modules and one or more terminal devices.

[0277] The above embodiments 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 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 device. 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 (digital subscriber line, DSL)) 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 includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state drive (SSD)).

[0278] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A vehicle-mounted association method, characterized in that: The method comprises: The server receives a first association request sent by the vehicle-mounted voice module, wherein the first association request is sent to the server by the vehicle-mounted voice module after the vehicle-mounted voice module detects that the first vehicle where the vehicle-mounted voice module is located is started; The server receives a second association request sent by the terminal device, the second association request is sent to the server by the terminal device after detecting that the second vehicle is started, and the terminal device is coupled to the vehicle-mounted charging module in the second vehicle; If the server determines that the first association request and the second association request match, the server sends first verification information to the vehicle-mounted voice module, and the first verification information is broadcast by the vehicle-mounted voice module; the server receives second verification information sent by the terminal device, and the second verification information is information input by the user in the terminal device based on the first verification information broadcast by the vehicle-mounted voice module; the server determines that the second verification information matches the first verification information, and associates the user account corresponding to the terminal device with the vehicle-mounted voice module.

2. The method according to claim 1, characterized in that The first association request includes an identifier of the first vehicle, and the second association request includes an identifier of the second vehicle; The server determines that the first association request matches the second association request, including: If the server determines that the identifier of the first vehicle is the same as the identifier of the second vehicle, then the server determines that the first association request matches the second association request.

3. The method according to claim 2, characterized in that The first association request further includes the start time information of the first vehicle, and the second association request further includes the start time information of the second vehicle; and / or, the first association request further includes the location information of the first vehicle, and the second association request further includes the location information of the terminal device; After determining that the identifier of the first vehicle is the same as the identifier of the second vehicle and before determining that the first association request matches the second association request, the server further includes: The server calculates a start time difference between the first vehicle and the second vehicle according to the start time information of the first vehicle and the start time information of the second vehicle; the server determines that the start time difference is less than a preset start time difference threshold; and / or, The server calculates the distance between the first vehicle and the terminal device based on the location information of the first vehicle and the location information of the terminal device; and the server determines that the distance is less than a preset distance threshold.

4. The method according to any one of claims 1 to 3, characterized in that After the server associates the user account corresponding to the terminal device with the vehicle-mounted voice module, it also includes: The server generates an access code corresponding to the vehicle-mounted voice module; The server sends the access code corresponding to the vehicle-mounted voice module to the vehicle-mounted voice module; The access code is used by the vehicle-mounted voice module to access the voice service of the server.

5. A vehicle-mounted association method, characterized in that: The method comprises: The vehicle-mounted voice module generates a first association request after detecting that the first vehicle where the vehicle-mounted voice module is located is started; The vehicle-mounted voice module sends the first association request to the server; The in-vehicle voice module broadcasts first verification information, the first verification information is sent to the in-vehicle voice module by the server when it is determined that the first association request matches the second association request sent by the terminal device, the second association request is generated by the terminal device after the second vehicle is started and sent to the server, and the terminal device is coupled to the in-vehicle charging module in the second vehicle; Among them, when the server determines that the first verification information matches the second verification information sent by the terminal device, it associates the user account corresponding to the terminal device and the vehicle-mounted voice module, and the second verification information is the information entered by the user in the terminal device according to the first verification information broadcast by the vehicle-mounted voice module.

6. The method according to claim 5, characterized in that The first association request includes an identification of the first vehicle.

7. The method according to claim 6, characterized in that The first association request also includes the start time information of the first vehicle and / or the location information of the first vehicle.

8. The method according to any one of claims 5 to 7, characterized in that After the vehicle-mounted voice module sends the first association request to the server, the method further includes: The in-vehicle voice module receives and stores an access code corresponding to the in-vehicle voice module sent by the server, wherein the access code is generated by the server after successfully associating the user account corresponding to the terminal device with the in-vehicle voice module; The vehicle-mounted voice module uses the access code corresponding to the vehicle-mounted voice module to access the voice service of the server.

9. The method according to claim 8, characterized in that Before the vehicle-mounted voice module generates the first association request, the method further includes: The in-vehicle voice module determines that the in-vehicle voice module does not store an access code corresponding to the in-vehicle voice module.

10. A vehicle-mounted association method, characterized in that: The method is applicable to a terminal device, and the terminal device is coupled to an on-board charging module of a second vehicle; the method comprises: After the terminal device detects through the vehicle charging module that the second vehicle is started, it generates a second association request; The terminal device sends the second association request to the server; The terminal device receives second verification information input by the user; the second verification information is information input by the user in the terminal device according to the first verification information voice broadcasted by the vehicle-mounted voice module, the first verification information is sent to the vehicle-mounted voice module by the server when it determines that the second association request matches the first association request sent by the vehicle-mounted voice module, and is broadcasted by the vehicle-mounted voice module, and the first association request is generated by the vehicle-mounted voice module after detecting that the first vehicle where the vehicle-mounted voice module is located is started and sent to the server; The terminal device sends the second verification information to the server; Wherein, when the server determines that the second verification information matches the first verification information, the user account corresponding to the terminal device and the vehicle-mounted voice module are associated.

11. The method according to claim 10, characterized in that The second association request includes an identifier of the second vehicle.

12. The method according to claim 11, characterized in that The second association request also includes the start time of the second vehicle and / or the location information of the terminal device.

13. The method according to any one of claims 10 to 12, characterized in that: The user account corresponding to the terminal device is obtained by the user applying to the server in advance on the target application APP of the terminal device; Before the terminal device detects through the vehicle charging module that the second vehicle is started, the terminal device further includes: The terminal device uses the user account corresponding to the terminal device to log in to the target APP; The terminal device receives the identifier of the second vehicle input by the user on the target APP; The terminal device prompts the user on the target APP to couple the terminal device to the on-board charging module of the second vehicle, and prompts the user to perform a startup operation on the second vehicle.

14. A server, characterized in that: The device comprises a processor, a transceiver and a memory, wherein the processor is connected to the memory, the memory stores a computer program, and when the computer program stored in the memory is executed by the processor, the server executes: receiving, by the transceiver, a first association request sent by a vehicle-mounted voice module, wherein the first association request is sent by the vehicle-mounted voice module to the server after the vehicle-mounted voice module detects that a first vehicle where the vehicle-mounted voice module is located is started; receiving, by the transceiver, a second association request sent by a terminal device, wherein the second association request is sent by the terminal device to the server after the terminal device detects that a second vehicle is started, and the terminal device is coupled to an on-board charging module in the second vehicle; If it is determined that the first association request matches the second association request, first verification information is sent to the vehicle-mounted voice module through the transceiver, and the first verification information is broadcasted by the vehicle-mounted voice module; receiving, by the transceiver, second verification information sent by the terminal device, where the second verification information is information input by a user into the terminal device according to the first verification information broadcast by the vehicle-mounted voice module; Determine that the second verification information matches the first verification information, and associate the user account corresponding to the terminal device with the in-vehicle voice module.

15. The server according to claim 14, characterized in that The first association request includes an identifier of the first vehicle, and the second association request includes an identifier of the second vehicle; When the computer program stored in the memory is executed by the processor, the server is caused to specifically execute: If it is determined that the identifier of the first vehicle is the same as the identifier of the second vehicle, then it is determined that the first association request matches the second association request.

16. The server according to claim 15, characterized in that The first association request further includes the start time information of the first vehicle, and the second association request further includes the start time information of the second vehicle; and / or, the first association request further includes the location information of the first vehicle, and the second association request further includes the location information of the terminal device; When the computer program stored in the memory is executed by the processor, the server further executes: After determining that the identifier of the first vehicle and the identifier of the second vehicle are the same and before determining that the first association request and the second association request match: calculating a start time difference between the first vehicle and the second vehicle according to the start time information of the first vehicle and the start time information of the second vehicle, and determining that the start time difference is less than a preset start time difference threshold; And / or, based on the location information of the first vehicle and the location information of the terminal device, calculate the distance between the first vehicle and the terminal device, and determine that the distance is less than a preset distance threshold.

17. A vehicle-mounted voice module, characterized in that: The vehicle-mounted voice module comprises a processor, a transceiver and a memory, and also comprises a voice player; the processor is connected to the memory, the memory stores a computer program, and when the computer program stored in the memory is executed by the processor, the vehicle-mounted voice module executes: After detecting that the first vehicle where the vehicle-mounted voice module is located is started, generating a first association request; sending the first association request to a server via the transceiver; receiving, by the transceiver, first verification information sent by the server, the first verification information being sent to the vehicle-mounted voice module by the server when determining that the first association request matches a second association request sent by the terminal device, the second association request being generated by the terminal device after the second vehicle is started and sent to the server, the terminal device being coupled to the vehicle-mounted charging module in the second vehicle; The first verification information is voice broadcasted through the voice player, and when the server determines that the first verification information matches the second verification information sent by the terminal device, the user account corresponding to the terminal device and the vehicle-mounted voice module are associated, and the second verification information is the information input by the user in the terminal device based on the first verification information broadcasted by the vehicle-mounted voice module.

18. A terminal device, characterized in that: The terminal device is coupled to an on-board charging module of a second vehicle; the terminal device comprises: one or more processors; a memory; a transceiver; and one or more computer programs; wherein the one or more computer programs are stored in the memory, and the one or more computer programs comprise instructions, and when the instructions are called and executed by the one or more processors, the terminal device executes: After detecting, by the on-board charging module, that the second vehicle is started, generating a second association request; sending the second association request to a server via the transceiver; receiving, by the transceiver, second verification information input by a user, the second verification information being information input by the user in the terminal device according to first verification information voice broadcasted by the vehicle-mounted voice module, the first verification information being sent to the vehicle-mounted voice module by the server when determining that the second association request matches the first association request sent by the vehicle-mounted voice module, and being broadcasted by the vehicle-mounted voice module, the first association request being generated by the vehicle-mounted voice module after detecting that the first vehicle where the vehicle-mounted voice module is located is started and sent to the server; The second verification information is sent to the server through the transceiver, and when the server determines that the second verification information matches the first verification information, the user account corresponding to the terminal device and the vehicle-mounted voice module are associated.

19. The terminal device according to claim 18, characterized in that: The user account corresponding to the terminal device is obtained by the user applying to the server in advance on the target application APP of the terminal device; When the instruction is called and executed by the one or more processors, the terminal device specifically executes: Before the start of the second vehicle is detected by the on-board charging module, the target APP is logged in using the user account corresponding to the terminal device, the identifier of the second vehicle entered by the user on the target APP is received, and the user is prompted on the target APP to couple the terminal device with the on-board charging module of the second vehicle, and the user is prompted to start the second vehicle.

20. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed, it implements the method as described in any one of claims 1 to 4, or implements the method as described in any one of claims 5 to 9, or implements the method as described in any one of claims 10 to 13.

21. A vehicle, characterized in that: It includes an on-board voice module and an on-board charging module, the on-board voice module is used to connect to a server, and the on-board charging module is used to couple a terminal device; the on-board voice module is used to implement the method as described in any one of claims 5 to 9, and the terminal device is used to implement the method as described in any one of claims 10 to 13 through the on-board charging module.

22. A vehicle networking system, characterized in that: It comprises the server described in any one of claims 14 to 16, the vehicle-mounted voice module described in claim 17 and the terminal device described in claim 18 or 19.

Images