A communication connection method, a vehicle-mounted device, and related media

Abstract

This application discloses a communication connection method, an in-vehicle device, and related media. The method can be used with a first in-vehicle device that provides wireless communication hotspot services. The method includes the following steps: the first in-vehicle device receives a wireless connection request from a second in-vehicle device; if the wireless connection request includes a preset device identifier, and the preset device identifier matches the device identifier of the first in-vehicle device, the first in-vehicle device allows the second in-vehicle device to establish a wireless connection. By implementing the method of this application, the device providing wireless communication hotspot services can compare the target MAC address in the wireless connection request (i.e., the MAC address of the hotspot device with which the device wants to establish a wireless connection) with the MAC address of the current hotspot device to avoid the device mistakenly connecting to hotspots (or other wireless communication hotspot services). This also helps to enhance the accuracy of wireless connections and protect the security of user data.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication connection method, vehicle-mounted equipment, and related media. Background Technology

[0002] With the increasing prevalence of intelligent connected vehicle technology in in-vehicle devices, more and more automakers are adopting Wireless Fidelity (Wi-Fi) networking to achieve network connections between in-vehicle devices and / or between in-vehicle devices and other mobile terminals. In a vehicle, the front-seat devices typically create a Wi-Fi hotspot via a soft access point (SoftAP). Other in-vehicle devices (such as passenger-side screens, rear-seat screens, and armrest screens) and / or mobile terminals can connect to the front-seat SoftAP hotspot using a Wi-Fi username and password to achieve wireless communication. However, when a hotspot with the same name and password as the front-seat SoftAP exists nearby, other in-vehicle devices may mistakenly connect to the wrong hotspot, resulting in low data connection security and potentially leading to adverse consequences such as user data leaks.

[0003] Therefore, how to provide users with a method to improve the accuracy of wireless connections is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] One objective of this application is to provide a communication connection method, vehicle-mounted device, and related medium that can connect to a hotspot device (i.e., a device providing wireless communication hotspot service) with a specific media access control MAC address. This helps to avoid user data leakage due to connecting to other hotspots (or other wireless communication hotspot services) with the same username and password, thus contributing to data protection.

[0005] In a first aspect, embodiments of this application provide a communication connection method applied to a first vehicle-mounted device, the method comprising the following steps:

[0006] The first vehicle-mounted device receives a wireless connection request from the second vehicle-mounted device;

[0007] If the wireless connection request includes a preset device identifier, and the preset device identifier matches the device identifier of the first vehicle device, the first vehicle device allows the second vehicle device to establish a wireless connection.

[0008] In one possible implementation, before the first vehicle-mounted device receives the wireless connection request from the second vehicle-mounted device, the method may further include:

[0009] The first vehicle-mounted device establishes a wired connection with the second vehicle-mounted device;

[0010] The first vehicle-mounted device sends first information to the second vehicle-mounted device via a wired connection. The first information can be used by the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device based on the first information.

[0011] In another possible implementation, the first information may include the username and password of the wireless communication hotspot service and the device identifier of the first vehicle-mounted device.

[0012] In another possible implementation, the method may further include:

[0013] If the wireless connection request does not include a preset device identifier, and / or the preset device identifier does not match the device identifier of the first vehicle device, the first vehicle device rejects the wireless connection request of the second vehicle device.

[0014] In another possible implementation, the method may further include:

[0015] The first vehicle-mounted device receives second information sent by the second vehicle-mounted device via a wired connection. The second information may include the device identifier of the second vehicle-mounted device.

[0016] In another possible implementation, after the first vehicle device allows the second vehicle device to establish a wireless connection, provided that the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the first vehicle device, the method may further include:

[0017] When the first in-vehicle device displays the list of connected devices for popular services, it hides the information of the second in-vehicle device.

[0018] In another possible implementation, hiding the information of the second vehicle-mounted device may include:

[0019] When the second piece of information matches the third piece of information, hide the information of the second vehicle-mounted device;

[0020] The third information is information received by the first vehicle-mounted device via a wireless connection from the second vehicle-mounted device, and the third information may include the device identifier of the second vehicle-mounted device.

[0021] In another possible implementation, the method may include:

[0022] In response to a request to shut down hotspot service for the first vehicle device, maintain wireless connectivity between the first vehicle device and the second vehicle device.

[0023] In another possible implementation, the method may include:

[0024] The first vehicle-mounted device hides its own SSID broadcast.

[0025] Secondly, embodiments of this application provide a communication connection method applied to a second vehicle-mounted device, which may include the following steps:

[0026] The second vehicle-mounted device sends a wireless connection request to the first vehicle-mounted device, which is a vehicle-mounted device that provides wireless communication hotspot services.

[0027] If the wireless connection request includes a preset device identifier, and the preset device identifier matches the device identifier of the first vehicle-mounted device, the second vehicle-mounted device establishes a wireless connection with the first vehicle-mounted device according to the wireless connection request.

[0028] In one possible implementation, before the second vehicle-mounted device sends a wireless connection request to the first vehicle-mounted device, the method may further include:

[0029] The second vehicle-mounted device establishes a wired connection with the first vehicle-mounted device;

[0030] The second vehicle-mounted device receives the first information sent by the first vehicle-mounted device via a wired connection. The first information can be used by the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device based on the first information.

[0031] In another possible implementation, the first information may include the username and password of the wireless communication hotspot service and the device identifier of the first vehicle-mounted device.

[0032] In another possible implementation, the method may further include:

[0033] The second vehicle-mounted device sends second information to the first vehicle-mounted device via a wired connection. The second information may include the device identifier of the second vehicle-mounted device.

[0034] The second vehicle-mounted device sends third information to the first vehicle-mounted device via a wireless connection. The third information may include the device identifier of the second vehicle-mounted device, so that the first vehicle-mounted device can hide or show the information of the second vehicle-mounted device when displaying the device connection list of the wireless communication hotspot service based on the second information and the third information.

[0035] Thirdly, embodiments of this application provide a vehicle-mounted device that provides wireless communication hotspot services. The vehicle-mounted device may include: a first communication module and a first control module.

[0036] The first communication module can be used to receive wireless connection requests from the second vehicle-mounted device;

[0037] The first control module can be used to allow the second vehicle device to establish a wireless connection when the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the vehicle device.

[0038] In one possible implementation, the vehicle-mounted device may further include:

[0039] The first control module can also be used to establish a wired connection with the second vehicle-mounted equipment;

[0040] The first communication module can also be used to send first information to the second vehicle-mounted device, and the first information can be used by the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device based on the first information.

[0041] In another possible implementation, the first information may include the username and password of the wireless communication hotspot service and the device identifier of the first vehicle-mounted device.

[0042] In another possible implementation, the vehicle-mounted device may further include:

[0043] The first control module can also be used to reject the wireless connection request of the second vehicle device when the wireless connection request does not include a preset device identifier and / or the preset device identifier does not match the device identifier of the first vehicle device.

[0044] In another possible implementation, the vehicle-mounted device may further include:

[0045] The first communication module can also be used to receive second information sent by the second vehicle-mounted device, the second information including the device identifier of the second vehicle-mounted device.

[0046] In another possible implementation, the vehicle-mounted device may further include:

[0047] The first control module can also be used to hide the information of the second vehicle-mounted device when displaying the list of connected devices for hot services.

[0048] In another possible implementation, the vehicle-mounted device may further include:

[0049] The first control module can also be used to hide the information of the second vehicle-mounted device when the second information matches the third information;

[0050] The third information is information received by the first vehicle-mounted device via a wireless connection from the second vehicle-mounted device, and the third information may include the device identifier of the second vehicle-mounted device.

[0051] In another possible implementation, the vehicle-mounted device may further include:

[0052] The first control module can also be used to maintain the wireless connection between the first vehicle device and the second vehicle device in response to a request to shut down the hotspot service of the first vehicle device.

[0053] In another possible implementation, the vehicle-mounted device may further include:

[0054] The first control module can also be used to hide the SSID broadcast of the first vehicle-mounted device.

[0055] Fourthly, embodiments of this application provide an in-vehicle device, which may include the following components: a processor, a memory, and a bus;

[0056] The processor and memory are connected via a bus, wherein the memory is used to store a set of program code, and the processor is used to call the program code stored in the memory to execute the method described in the first aspect.

[0057] Fifthly, embodiments of this application provide a computer-readable storage medium, comprising:

[0058] The computer-readable storage medium stores instructions that, when executed on a computer, implement the method described in the first aspect.

[0059] Sixthly, this application provides a vehicle-mounted device, which may include: a second communication module and a second control module;

[0060] The second communication module can be used to send a wireless connection request to the first vehicle-mounted device, which is a vehicle-mounted device that provides wireless communication hotspot services.

[0061] The second control module can be used to establish a wireless connection between the second vehicle-mounted device and the first vehicle-mounted device when the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the first vehicle-mounted device.

[0062] In one possible implementation, the vehicle-mounted device may further include:

[0063] The second control module can also be used to establish a wired connection with the first vehicle-mounted equipment;

[0064] The second communication module can also be used to receive first information sent by the first vehicle-mounted device. The first information can be used by the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device based on the first information.

[0065] In another possible implementation, the first information may include the username and password of the wireless communication hotspot service and the device identifier of the first vehicle-mounted device.

[0066] In another possible implementation, the vehicle-mounted device may further include:

[0067] The second communication module can also be used to send second information to the first vehicle-mounted device, and the second information may include the device identifier of the second vehicle-mounted device.

[0068] The second communication module can also be used to send third information to the first vehicle-mounted device. The third information may include the device identifier of the second vehicle-mounted device, so that the first vehicle-mounted device can hide or show the information of the second vehicle-mounted device when displaying the device connection list of the wireless communication hotspot service based on the second information and the third information.

[0069] In a seventh aspect, embodiments of this application provide an in-vehicle device, which may include the following components: a processor, a memory, and a bus;

[0070] The processor and memory are connected via a bus, wherein the memory is used to store a set of program code, and the processor is used to call the program code stored in the memory to execute the method described in the second aspect.

[0071] Eighthly, embodiments of this application provide a computer-readable storage medium, comprising:

[0072] The computer-readable storage medium stores instructions that, when executed on a computer, implement the method described in the second aspect.

[0073] Ninthly, embodiments of this application provide a vehicle that may include in-vehicle equipment or computer-readable storage media as described in any of the third to fifth aspects, and in-vehicle equipment or computer-readable storage media as described in any of the sixth to eighth aspects.

[0074] As can be seen, this application enables hotspot devices (i.e., devices providing wireless communication hotspot services) to avoid misconnecting to hotspots (or other wireless communication hotspot services) by comparing the target MAC address in the wireless connection request (i.e., the MAC address of the hotspot device with which the device wants to establish a wireless connection) with the MAC address of the current hotspot device. This also helps to enhance the accuracy of wireless connections and protect the security of user data. Attached Figure Description

[0075] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0076] Figure 1 A flowchart illustrating a communication connection method provided in an embodiment of this application;

[0077] Figure 2 A schematic diagram illustrating a scenario where a second vehicle-mounted device generates a wireless connection request, as provided in an embodiment of this application.

[0078] Figure 3 A schematic diagram illustrating a process for a first vehicle-mounted device to process a wireless connection request, provided as an embodiment of this application;

[0079] Figure 4 A schematic diagram illustrating a scenario for updating the connected list, provided as an embodiment of this application;

[0080] Figure 5 A schematic diagram illustrating another scenario for updating the connected list, provided as an embodiment of this application;

[0081] Figure 6 This application provides a schematic diagram of a process for disabling wireless communication hotspot services using a first vehicle-mounted device.

[0082] Figure 7 This is a schematic diagram of the composition of a vehicle-mounted device provided in an embodiment of this application;

[0083] Figure 8 This is a schematic diagram illustrating the composition of another vehicle-mounted equipment device provided in an embodiment of this application. Detailed Implementation

[0084] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0085] The terms "first," "second," "third," and "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0086] In this document, the term "embodiment" means that a particular feature, result, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0087] To better understand the technical solutions of the embodiments of this application, the following will be combined with Figure 1 A communication connection method provided in the embodiments of this application will be described in detail.

[0088] Please see Figure 1 This is a flowchart illustrating a communication connection method provided in an embodiment of this application. The method may include the following steps:

[0089] S101, the first vehicle-mounted device receives a wireless connection request from the second vehicle-mounted device.

[0090] It should be noted that the wireless connection request sent by the second vehicle-mounted device shall include at least the username, password, and encryption method of the wireless communication hotspot service that the second vehicle-mounted device intends to connect to.

[0091] In one possible implementation, before the first vehicle-mounted device receives the wireless connection request from the second vehicle-mounted device, the method may further include:

[0092] The first vehicle-mounted device establishes a wired connection with the second vehicle-mounted device;

[0093] The first vehicle-mounted device sends first information to the second vehicle-mounted device via a wired connection. The first information can be used by the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device based on the first information.

[0094] In another possible implementation, the first information may include the username and password of the wireless communication hotspot service and the device identifier of the first vehicle-mounted device.

[0095] The specific form of device identification can be the MAC address of the vehicle-mounted device.

[0096] In another possible implementation, the method may further include:

[0097] The first vehicle-mounted device receives second information sent by the second vehicle-mounted device via a wired connection. The second information may include the device identifier of the second vehicle-mounted device.

[0098] Furthermore, the first vehicle-mounted device can establish a list of vehicle-mounted devices, which may include the MAC addresses of vehicle-mounted devices that are wired to the first vehicle-mounted device.

[0099] For example, please see Figure 2 This is a schematic diagram illustrating a scenario in which a second vehicle-mounted device generates a wireless connection request, as provided in an embodiment of this application.

[0100] like Figure 2As shown, in response to vehicle startup and the power-on of onboard devices (including the first onboard device and other onboard devices), the first onboard device sends first information to other onboard devices in the same vehicle (which can be understood as the second onboard device in this application) via the CAN bus. This first information may include the username, password, encryption method, and device identifier (such as the MAC address) of the wireless communication hotspot service provided by the first onboard device. The first onboard device also listens for MAC addresses transmitted from other onboard devices on the CAN bus. When the first onboard device receives MAC address information from other onboard devices, it saves these MAC addresses in the onboard device list. Other onboard devices in the same vehicle as the first onboard device also send their own MAC addresses to the first onboard device via the CAN bus after powering on. These other onboard devices can also listen for and receive the first information sent by the first onboard device on the CAN bus, and then generate a wireless connection request based on the first information. The other onboard devices specify the target device by including a preset device identifier in the wireless connection request; the target device is the device with which the other onboard device wants to establish a wireless connection.

[0101] As can be seen, the vehicle-mounted devices in this embodiment communicate their MAC addresses via wired means (such as CAN bus), which helps to establish a reliable and accurate wireless connection based on the MAC address, thereby preventing accidental connection to the wireless network and protecting data security.

[0102] S102, if the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the first vehicle device, the first vehicle device allows the second vehicle device to establish a wireless connection.

[0103] For example, suppose the first vehicle-mounted device receives two wireless connection requests (wireless connection request 1 contains a preset device identifier 1, and wireless connection request 2 does not contain a preset device identifier 2). Then, wireless connection request 1 can be considered to be sent by the vehicle-mounted device, and wireless connection request 2 is sent by the user-controlled mobile terminal. To determine whether to allow the vehicle-mounted device corresponding to wireless connection request 1 to establish a wireless connection, the first vehicle-mounted device needs to determine whether the preset device identifier 1 contained in wireless connection request 1 matches the device identifier of the first vehicle-mounted device. To determine whether to allow the mobile terminal corresponding to wireless connection request 2 to establish a wireless connection, the first vehicle-mounted device only needs to determine whether the target username, password, and encryption method carried in wireless connection request 2 are the same as the username, password, and encryption method of the wireless communication hotspot service provided by the first vehicle-mounted device.

[0104] In one possible implementation, the method may further include:

[0105] If the wireless connection request does not include a preset device identifier, and / or the preset device identifier does not match the device identifier of the first vehicle device, the first vehicle device rejects the wireless connection request of the second vehicle device.

[0106] In another possible implementation, the method may further include:

[0107] The first vehicle-mounted device receives second information sent by the second vehicle-mounted device via a wired connection. The second information may include the device identifier of the second vehicle-mounted device.

[0108] In another possible implementation, after the first vehicle device allows the second vehicle device to establish a wireless connection, provided that the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the first vehicle device, the method may further include:

[0109] When the first in-vehicle device displays the list of connected devices for popular services, it hides the information of the second in-vehicle device.

[0110] In another possible implementation, hiding the information of the second vehicle-mounted device may include:

[0111] When the second piece of information matches the third piece of information, hide the information of the second vehicle-mounted device;

[0112] The third information is information received by the first vehicle-mounted device via a wireless connection from the second vehicle-mounted device, and the third information may include the device identifier of the second vehicle-mounted device.

[0113] For example, please see Figure 3 This is a schematic diagram illustrating the process of a first vehicle-mounted device processing a wireless connection request, provided in an embodiment of this application.

[0114] like Figure 3 As shown, the process for the first onboard device to process a wireless connection request can refer to the following steps:

[0115] S301, establish a list of on-board devices based on the device identifiers of other on-board devices located in the same vehicle.

[0116] S302, received a wireless connection request from the second vehicle-mounted device.

[0117] S303, determine whether the wireless connection request of the second vehicle-mounted device contains (or specifies) a preset device identifier.

[0118] If the determination is negative, then execute S304 to allow the second vehicle-mounted device to establish a wireless connection.

[0119] If the determination is yes, then execute S305 to confirm whether the preset device identifier is the same as the device identifier of the first vehicle-mounted device.

[0120] Furthermore, when the wireless connection request of the second vehicle-mounted device includes (or specifies) a preset device identifier, if the preset device identifier is the same as the device identifier of the first vehicle-mounted device, then S3051 is executed to allow the second vehicle-mounted device to establish a wireless connection; if the preset device identifier is different from the device identifier of the first vehicle-mounted device, then S3052 is executed to reject the wireless connection request of the second vehicle-mounted device.

[0121] For example, suppose the first vehicle-mounted device (with its corresponding device identifier set to MAC address 1) establishes a list of vehicle-mounted devices containing vehicle-mounted device 1 (with its corresponding device identifier set to MAC address 2), vehicle-mounted device 2 (with its corresponding device identifier set to MAC address 3), and vehicle-mounted device 3 (with its corresponding device identifier set to MAC address 4). When the first vehicle-mounted device receives a wireless connection request from the second vehicle-mounted device, if the wireless connection request does not specify a preset device identifier (i.e., the MAC address of the device with which the second vehicle-mounted device wants to establish a wireless connection), the second vehicle-mounted device can be considered a non-vehicle-mounted device (such as a user's mobile terminal), and thus the first vehicle-mounted device is allowed to establish a wireless connection. If the wireless connection request specifies a preset device identifier, the second vehicle-mounted device is considered a vehicle-mounted device, and it is necessary to determine whether the preset device identifier is the same as the vehicle-mounted device identifier (i.e., MAC address 1). If the preset device identifier is the same as the vehicle-mounted device identifier, the second vehicle-mounted device is allowed to establish a wireless connection; if the preset device identifier is different from the vehicle-mounted device identifier, the wireless connection request of the second vehicle-mounted device is rejected.

[0122] It should be noted that, in this embodiment, before the first vehicle-mounted device determines whether the wireless connection request of the second vehicle-mounted device contains a preset device identifier, it needs to determine whether the target username, password, and encryption method in the wireless connection request of the second vehicle-mounted device are the same as the username, password, and encryption method of the wireless communication hotspot service provided by the first vehicle-mounted device. If they are the same, the device identifier (such as a MAC address) can be confirmed; if they are different, the wireless connection request of the second vehicle-mounted device is rejected. The target username, password, and encryption method in the wireless connection request of the second vehicle-mounted device are the username, password, and encryption method of the wireless communication hotspot service that the second vehicle-mounted device wants to obtain.

[0123] As can be seen, the embodiments of this application can enable hotspot devices (i.e., devices providing wireless communication hotspot services) to avoid misconnecting to hotspots (or other wireless communication hotspot services) by comparing the target MAC address in the wireless connection request (i.e., the MAC address of the hotspot device with which the device wants to establish a wireless connection) with the MAC address of the current hotspot device. This also helps to enhance the accuracy of wireless connections and protect the security of user data.

[0124] In one possible implementation, the method may further include:

[0125] A connected list is established, which may include connection information of devices that have wirelessly connected to the first vehicle-mounted device. The connection information may include the name of the device that has wirelessly connected to the first vehicle-mounted device, and may also include the connection duration of the device that has wirelessly connected to the first vehicle-mounted device.

[0126] In another possible implementation, hiding the information of the second vehicle-mounted device may include:

[0127] When the second piece of information matches the third piece of information, hide the information of the second vehicle-mounted device;

[0128] The third information is information received by the first vehicle-mounted device via a wireless connection from the second vehicle-mounted device, and the third information may include the device identifier of the second vehicle-mounted device.

[0129] For example, if the wireless connection request includes a device identifier (such as a MAC address) of the second vehicle device that matches the MAC address in the vehicle device list, then the connection information of the second vehicle device is removed from the connected list, and the updated connected list is displayed on the vehicle's infotainment system's display module.

[0130] For example, please see Figure 4 This is a schematic diagram of a process for updating the connected list provided in an embodiment of this application.

[0131] like Figure 4 As shown, the process for updating the connected list of the first in-vehicle device can be referenced in the following steps:

[0132] S401, update the connected list at a preset cycle.

[0133] For example, the first vehicle-mounted device can refresh the connected list at a preset period (e.g., 1 second), saving the connection information of devices that established a wireless connection with the first vehicle-mounted device in the previous period (e.g., the previous 1 second) to the connected list. Possibly, the first vehicle-mounted device can also save the connection information of a device to the connected list in response to a device successfully establishing a wireless connection with it. Furthermore, the first vehicle-mounted device can also update the connection duration of the device at a preset period (e.g., 30 milliseconds).

[0134] Similarly, the first vehicle-mounted device can refresh the connected list at a preset period (e.g., 1 second), deleting the connection information of devices that disconnected from the first vehicle-mounted device in the previous period (e.g., the previous 1 second) from the connected list. Alternatively, the first vehicle-mounted device can also delete the connection information of a device from the connected list in response to it disconnecting from the first vehicle-mounted device.

[0135] S402, determine whether the device identifier of the connected device exists in the vehicle device list.

[0136] If the determination is negative, then execute S403 to display the connected list.

[0137] If the determination is yes, then execute S404 to remove the connection information of the device from the connected list and present the updated list.

[0138] Furthermore, please see Figure 5 This is a schematic diagram illustrating another scenario for updating the connected list provided in an embodiment of this application.

[0139] like Figure 5As shown, there is an existing connected list 1, which contains device 1 (the wireless connection request includes a preset device identifier, and the preset device identifier is the same as the device identifier of the first vehicle-mounted device, but device 1's device identifier is not in the vehicle-mounted device list) and device 2 (the wireless connection request does not contain a preset device identifier). Device 1's connection duration is 5 minutes, and device 2's connection duration is 2 minutes. If device 3 (the wireless connection request includes a preset device identifier, and the preset device identifier is the same as the device identifier of the first vehicle-mounted device, and device 3's device identifier is in the vehicle-mounted device list) and device 4 (the wireless connection request does not contain a preset device identifier) ​​establish a wireless connection with the first vehicle-mounted device, then a connected list 2 will be generated. Since device 3 belongs to another vehicle-mounted device (i.e., a vehicle-mounted device in the same vehicle as the first vehicle-mounted device), the connection information of device 3 will be deleted before the list is presented to the user, resulting in an updated connected list 3. Finally, the connected list 3 is presented on the vehicle's infotainment display screen 50. It should be noted that the above example of presenting the connected list on the vehicle display screen 50 is only for more detailed illustration of the solution of this application and should not be construed as limiting. The connected list can also be presented on other displays of the vehicle and / or on the user's mobile terminal with display function. There are no restrictions here. The specific presentation method of the connected list shall be set by the technicians according to the actual situation.

[0140] As can be seen, this application embodiment will delete the connection information of in-vehicle ad hoc network devices (i.e., other in-vehicle devices in the same vehicle as the hotspot device, where the hotspot device is the device that provides wireless communication hotspot service) and maintain the connected list, which helps to improve the user experience, avoid the situation where the user accidentally kicks the in-vehicle ad hoc network device out of the ad hoc network, and help ensure that the vehicle can provide relevant in-vehicle services normally.

[0141] In another possible implementation, the method may include:

[0142] In response to a request to shut down hotspot service for the first vehicle device, maintain wireless connectivity between the first vehicle device and the second vehicle device.

[0143] Furthermore, the first vehicle-mounted device disconnects its wireless connection from non-vehicle-mounted devices (such as the mobile devices mentioned above) in the connected list and deletes the connection information of the non-vehicle-mounted devices from the connected list.

[0144] Possibly, the first in-vehicle device can also disconnect wirelessly from all devices in the connected list and remove the connection information of all devices in the connected list.

[0145] In another possible implementation, the method may include:

[0146] The first onboard device hides its own Service Set Identifier (SSID) broadcast.

[0147] For example, please see Figure 6 This is a schematic diagram illustrating the process of a first vehicle-mounted device turning off wireless communication hotspot service, provided in an embodiment of this application.

[0148] like Figure 6 As shown, the process for the first vehicle-mounted device to disable the wireless communication hotspot service can refer to the following steps:

[0149] S601 responds to the user shutting down the first on-board device and closes the wireless communication hotspot service call interface.

[0150] It is possible that users could directly disable the wireless hotspot service on the first in-vehicle device without having to disable the first in-vehicle device itself.

[0151] S602 utilizes the wireless communication hotspot service framework and hardware abstraction layer to call private interfaces.

[0152] Among them, the wireless communication hotspot service framework can be a Wi-Fi framework, and the hardware abstraction layer can be understood as the Hardware Abstraction Layer, or HAL for short.

[0153] S603 disconnects the wireless connection from non-vehicle devices in the connected list.

[0154] S604, broadcasts its own hidden SSID.

[0155] S605, the wireless communication hotspot service of the reporting system has been turned off.

[0156] As can be seen, the embodiments of this application can present the user with the complete result of turning off the wireless communication hotspot service without affecting the normal wireless connection between the in-vehicle ad hoc network device (i.e., other in-vehicle devices in the same vehicle as the hotspot device, the hotspot device being the device that provides wireless communication hotspot service) and the hotspot device, which helps to ensure the integrity of vehicle services or functions without affecting the user experience.

[0157] The apparatus involved in the embodiments of this application is described below with reference to the accompanying drawings.

[0158] Please see Figure 7 This application provides an embodiment of an in-vehicle device, which may include: a communication module 710 and a control module 720.

[0159] The communication module 710 can be used to receive wireless connection requests from a second vehicle-mounted device.

[0160] The control module 720 can be used to allow a second vehicle device to establish a wireless connection when the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the vehicle device.

[0161] In one possible implementation, the vehicle-mounted device may further include:

[0162] The control module 720 can also be used to establish a wired connection with a second vehicle-mounted device;

[0163] The communication module 710 can also be used to send first information to the second vehicle-mounted device, and the first information can be used by the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device based on the first information.

[0164] In another possible implementation, the first information may include the username and password of the wireless communication hotspot service and the device identifier of the first vehicle-mounted device.

[0165] In another possible implementation, the vehicle-mounted device may further include:

[0166] The control module 720 can also be used to reject the wireless connection request of the second vehicle device when the wireless connection request does not include a preset device identifier and / or the preset device identifier does not match the device identifier of the first vehicle device.

[0167] In another possible implementation, the vehicle-mounted device may further include:

[0168] The communication module 710 can also be used to receive second information sent by the second vehicle-mounted device, the second information including the device identifier of the second vehicle-mounted device.

[0169] In another possible implementation, the vehicle-mounted device may further include:

[0170] The control module 720 can also be used to hide information about the second vehicle-mounted device when displaying a list of connected devices for hotspot services.

[0171] In another possible implementation, the vehicle-mounted device may further include:

[0172] The control module 720 can also be used to hide the information of the second vehicle-mounted device when the second information matches the third information;

[0173] The third information is information received by the first vehicle-mounted device via a wireless connection from the second vehicle-mounted device, and the third information may include the device identifier of the second vehicle-mounted device.

[0174] In another possible implementation, the vehicle-mounted device may further include:

[0175] The control module 720 can also be used to maintain the wireless connection between the first vehicle device and the second vehicle device in response to a request to shut down the hotspot service of the first vehicle device.

[0176] In another possible implementation, the vehicle-mounted device may further include:

[0177] The control module 720 can also be used to hide the SSID broadcast of the first vehicle-mounted device.

[0178] Please see Figure 8 This is a schematic diagram illustrating the composition of another vehicle-mounted device provided in an embodiment of this application. The vehicle-mounted device may include:

[0179] The processor 810, memory 820, and I / O interface 830 are communicatively connected. The memory 820 stores instructions, and the processor 810 executes the instructions stored in the memory 820 to achieve the above-mentioned functions. Figure 1 , Figure 3 , Figure 4 as well as Figure 6 The corresponding methods and steps.

[0180] The processor 810 executes the instructions stored in the memory 820 to control the I / O interface 830 to receive and send signals, thus completing the steps in the above method. The memory 820 may be integrated into the processor 810 or may be disposed separately from the processor 810.

[0181] The memory 820 may also include a storage system 821, a cache 822, and RAM 823. The cache 822 is a primary memory located between the RAM 823 and the CPU, composed of static RAM chips (SRAM). It has a relatively small capacity but a much higher speed than main memory, approaching the speed of the CPU. The RAM 823 is an internal memory that directly exchanges data with the CPU. It can be read and written at any time (except during refresh) and is very fast, typically serving as temporary data storage for the operating system or other running programs. The three components work together to realize the function of the memory 820.

[0182] As one implementation approach, the functionality of the I / O interface 830 can be implemented using transceiver circuitry or dedicated transceiver chips. The processor 810 can be implemented using dedicated processing chips, processing circuitry, processors, or general-purpose chips.

[0183] As another implementation method, the apparatus provided in this application embodiment can be implemented using a general-purpose computer. The program code that implements the functions of processor 810 and I / O interface 830 is stored in memory 820, and the general-purpose processor implements the functions of processor 810 and I / O interface 830 by executing the code in memory 820.

[0184] For the concepts, explanations, detailed descriptions, and other steps related to the technical solutions provided in the embodiments of this application, please refer to the descriptions of the method steps performed by the device in the foregoing method or other embodiments, which will not be repeated here.

[0185] As another implementation of this embodiment, a computer-readable storage medium is provided, on which instructions are stored, which, when executed, perform the methods in the above-described method embodiments.

[0186] As another implementation of this embodiment, a computer program product containing instructions is provided, which, when executed, perform the method in the above method embodiment.

[0187] Those skilled in the art will understand that, for ease of explanation, Figure 8 Only one memory and processor are shown in the illustration. In a real terminal or server, multiple processors and memories may exist. Memory can also be called storage medium or storage device, etc., and this application does not limit this.

[0188] It should be understood that in the embodiments of this application, the processor may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0189] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but 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 Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0190] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) is integrated into the processor.

[0191] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0192] In addition to the data bus, this bus may also include a power bus, a control bus, and a status signal bus. However, for clarity, all buses are labeled "bus" in the diagram.

[0193] It should also be understood that the first, second, third, fourth and various numerical designations used herein are merely for descriptive convenience and are not intended to limit the scope of this application.

[0194] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0195] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0196] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0197] Those skilled in the art will recognize that the various illustrative logical blocks (ILBs) and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0198] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0200] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0201] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. 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. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. 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 integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0202] This application also provides a computer-readable storage medium storing a computer program that is executed by a processor to implement some or all of the steps of any of the communication connection methods described in the above method embodiments.

[0203] This application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the communication connection methods described in the above method embodiments.

[0204] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication connection method, characterized in that, Applied to a first in-vehicle device, wherein the first in-vehicle device is an in-vehicle device that provides wireless communication hotspot services, the method includes the following steps: The first vehicle-mounted device receives a wireless connection request from the second vehicle-mounted device; If the wireless connection request includes a preset device identifier, and the preset device identifier matches the device identifier of the first vehicle device, the first vehicle device allows the second vehicle device to establish a wireless connection. After the first vehicle device allows the second vehicle device to establish a wireless connection, provided that the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the first vehicle device, the method further includes: When the first in-vehicle device displays the device connection list for the hotspot service, it hides the information of the second in-vehicle device. The method further includes: In response to a request to disable hotspot services for the first vehicle device, maintain the wireless connection between the first vehicle device and the second vehicle device.

2. The method according to claim 1, characterized in that, Before the first vehicle-mounted device receives the wireless connection request from the second vehicle-mounted device, the method further includes: The first vehicle-mounted device establishes a wired connection with the second vehicle-mounted device; The first vehicle-mounted device sends first information to the second vehicle-mounted device via the wired connection. The first information is used by the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device based on the first information.

3. The method according to claim 2, characterized in that, The first information includes the username and password of the wireless communication hotspot service and the device identifier of the first vehicle-mounted device.

4. The method according to claim 3, characterized in that, The method further includes: If the wireless connection request does not include the preset device identifier, and / or the preset device identifier does not match the device identifier of the first vehicle device, the first vehicle device rejects the wireless connection request of the second vehicle device.

5. The method according to claim 4, characterized in that, The method further includes: The first vehicle-mounted device receives second information sent by the second vehicle-mounted device via the wired connection. The second information includes the device identifier of the second vehicle-mounted device.

6. The method according to claim 5, characterized in that, The information about hiding the second vehicle-mounted device includes: When the second information matches the third information, the information of the second vehicle-mounted device is hidden. The third information is information received by the first vehicle-mounted device from the second vehicle-mounted device via the wireless connection, and the third information includes the device identifier of the second vehicle-mounted device.

7. The method according to claim 6, characterized in that, The method includes: The first vehicle-mounted device hides its own SSID broadcast.

8. A communication connection method, characterized in that, Applied to a second vehicle-mounted device, the method includes the following steps: The second vehicle-mounted device sends a wireless connection request to the first vehicle-mounted device, where the first vehicle-mounted device is a vehicle-mounted device that provides wireless communication hotspot services. If the wireless connection request includes a preset device identifier, and the preset device identifier matches the device identifier of the first vehicle-mounted device, the second vehicle-mounted device establishes a wireless connection with the first vehicle-mounted device according to the wireless connection request. The method further includes: The second vehicle-mounted device sends third information to the first vehicle-mounted device via the wireless connection, so that the first vehicle-mounted device, based on the second and third information, hides or displays the information of the second vehicle-mounted device when displaying the device connection list of the wireless communication hotspot service. The second information includes the device identifier of the second vehicle-mounted device, and the third information includes the device identifier of the second vehicle-mounted device. The method further includes: After the first vehicle device responds to the request to disable the hotspot service, the second vehicle device maintains a wireless connection with the first vehicle device.

9. The method according to claim 8, characterized in that, Before the second vehicle-mounted device sends a wireless connection request to the first vehicle-mounted device, the method further includes: The second vehicle-mounted device establishes a wired connection with the first vehicle-mounted device; The second vehicle-mounted device receives first information sent by the first vehicle-mounted device through the wired connection. The first information is used by the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device based on the first information.

10. The method according to claim 9, characterized in that, The first information includes the username and password of the wireless communication hotspot service and the device identifier of the first vehicle-mounted device.

11. The method according to claim 10, characterized in that, The method further includes: The second vehicle-mounted device sends second information to the first vehicle-mounted device via the wired connection.

12. A vehicle-mounted device, characterized in that, The vehicle-mounted device provides wireless communication hotspot services, and the vehicle-mounted device includes: a first communication module and a first control module; The first communication module is used to receive wireless connection requests from the second vehicle-mounted device; The first control module is configured to allow the second vehicle device to establish a wireless connection when the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the vehicle device. The first control module is also used to hide the information of the second vehicle-mounted device when displaying the device connection list of the hotspot service; The first control module is further configured to maintain the wireless connection between the first vehicle device and the second vehicle device in response to a request to disable the hotspot service of the first vehicle device.

13. A vehicle-mounted device, characterized in that, include: The processor, the memory, and the I / O interface are communicatively connected, wherein the memory is used to store a set of program code, and the processor is used to call the program code stored in the memory to execute the method as described in any one of claims 1-7.

14. A computer-readable storage medium, characterized in that, include: The computer-readable storage medium stores instructions that, when executed on a computer, implement the method as described in any one of claims 1-7.

15. A vehicle-mounted device, characterized in that, The vehicle-mounted equipment includes: a second communication module and a second control module; The second communication module is used to send a wireless connection request to the first vehicle-mounted device, which is a vehicle-mounted device that provides wireless communication hotspot services; The second control module is configured to, when the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the first vehicle-mounted device, establish a wireless connection between the second vehicle-mounted device and the first vehicle-mounted device according to the wireless connection request. The second communication module is further configured to send third information to the first vehicle-mounted device, so that the first vehicle-mounted device, based on the second information and the third information, hides or displays the information of the second vehicle-mounted device when the first vehicle-mounted device displays the device connection list of the wireless communication hotspot service. The second information includes the device identifier of the second vehicle-mounted device, and the third information includes the device identifier of the second vehicle-mounted device. The second communication module is further configured to maintain a wireless connection with the first vehicle device after the first vehicle device responds to a request to close the hotspot service.

16. A vehicle-mounted device, characterized in that, include: The processor, the memory, and the I / O interface are communicatively connected, wherein the memory is used to store a set of program code, and the processor is used to call the program code stored in the memory to execute the method as described in any one of claims 8-11.

17. A computer-readable storage medium, characterized in that, include: The computer-readable storage medium stores instructions that, when executed on a computer, implement the method as described in any one of claims 8-11.

18. A vehicle, characterized in that, The vehicle includes the in-vehicle device as claimed in any one of claims 12-13 or the computer-readable storage medium as claimed in claim 14, and the in-vehicle device as claimed in any one of claims 15-16 or the computer-readable storage medium as claimed in claim 17.

Images