Communication connection method, vehicle-mounted device, and related medium

Abstract

A communication connection method, a vehicle-mounted device, and a related medium. The method can be applied to a first vehicle-mounted device, and the first vehicle-mounted device is a vehicle-mounted device providing a wireless communication hotspot service. The method may comprise: the first vehicle-mounted device receives a wireless connection request of a second vehicle-mounted device; and if the wireless connection request comprises a preset device identifier and the preset device identifier matches the device identifier of the first vehicle-mounted device, the first vehicle-mounted device allows the second vehicle-mounted device to establish a wireless connection.

Description

Communication connection method, vehicle-mounted equipment and related media

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on October 30, 2023, with application number 202311434912.5 and invention name “A communication connection method, vehicle-mounted equipment and related media”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication connection method, a vehicle-mounted device, and related media. Background Art

[0003] With the popularization of intelligent network technology in vehicle-mounted devices, more and more car companies are adopting wireless fidelity (Wi-Fi) networking to achieve network connections between vehicle-mounted devices and / or network connections between vehicle-mounted devices and other mobile terminals. In a vehicle, the front-row device of the vehicle generally opens a Wi-Fi hotspot through a wireless soft AP (SoftAP), and other vehicle-mounted devices (such as the co-pilot screen device, rear screen device and armrest screen device, etc.) and / or mobile terminals can connect to the front-row device SoftAP hotspot through a Wi-Fi username and password, thereby achieving wireless communication between devices. However, when there is a hotspot with the same name and password as the front-row device SoftAP nearby, other vehicle-mounted devices will mistakenly connect to other hotspots, resulting in low data connection security, which may lead to adverse consequences such as user data leakage.

[0004] Therefore, how to provide users with a method for improving wireless connection accuracy is a problem that those skilled in the art urgently need to solve.

[0005] Summary of the Invention

[0006] In a first aspect, an embodiment of the present application provides a communication connection method, which is performed by a first vehicle-mounted device. The method may include:

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

[0008] In a case where the wireless connection request includes the preset device identifier and the preset device identifier matches the device identifier of the first vehicle-mounted device, the first vehicle-mounted device allows the second vehicle-mounted device to establish a wireless connection.

[0009] In a possible implementation, before the first in-vehicle device receives the wireless connection request from the second in-vehicle device, the method may further include:

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

[0011] The first vehicle-mounted device sends first information to the second vehicle-mounted device through 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.

[0012] In another possible implementation, the first information may include a user name and password of the wireless communication hotspot service and a device identification of the first vehicle-mounted device.

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

[0014] In a case where 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-mounted device, the first vehicle-mounted device rejects the wireless connection request of the second vehicle-mounted device.

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

[0016] The first vehicle-mounted device receives second information sent by the second vehicle-mounted device through a wired connection. The second information may include a device identification of the second vehicle-mounted device.

[0017] In another possible implementation, 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, after the first vehicle-mounted device allows the second vehicle-mounted device to establish a wireless connection, the method may further include:

[0018] When displaying the device connection list of the hotspot service, the first vehicle-mounted device hides the information of the second vehicle-mounted device.

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

[0020] When the second information matches the third information, hiding the information of the second in-vehicle device;

[0021] The third information is information sent by the second vehicle-mounted device and received by the first vehicle-mounted device through a wireless connection. The third information may include a device identification of the second vehicle-mounted device.

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

[0023] In response to a request to close the hotspot service of the first in-vehicle device, the wireless connection between the first in-vehicle device and the second in-vehicle device is maintained.

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

[0025] The first in-vehicle device hides its own SSID broadcast.

[0026] In a second aspect, an embodiment of the present application provides a communication connection method, which is performed by a second vehicle-mounted device. The method may include:

[0027] 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 a wireless communication hotspot service;

[0028] In a case where 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.

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

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

[0031] The second vehicle-mounted device receives the first information sent by the first vehicle-mounted device through 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.

[0032] In another possible implementation, the first information may include a user name and password of the wireless communication hotspot service and a device identification of the first vehicle-mounted device.

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

[0034] The second vehicle-mounted device sends second information to the first vehicle-mounted device through a wired connection, where the second information may include a device identifier of the second vehicle-mounted device;

[0035] 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 identification of the second vehicle-mounted device, so that the first vehicle-mounted device 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 based on the second information and the third information.

[0036] In a third aspect, an embodiment of the present application provides a vehicle-mounted device, which may include a processor, a memory, and an I / O interface, wherein the processor, the memory, and the I / O interface are communicatively connected, wherein the memory is used to store a set of program codes, and the processor is used to call the program codes stored in the memory to execute the method described in the first aspect.

[0037] In a fourth aspect, an embodiment of the present application provides a non-volatile computer-readable storage medium:

[0038] The non-volatile computer-readable storage medium stores instructions, which, when executed on a computer, implement the method described in the first aspect.

[0039] In the fifth aspect, an embodiment of the present application provides a vehicle-mounted device, which may include a processor, a memory and an I / O interface, wherein the processor, the memory and the I / O interface are communicatively connected, wherein the memory is used to store a set of program codes, and the processor is used to call the program codes stored in the memory to execute the method described in the second aspect.

[0040] In a sixth aspect, an embodiment of the present application provides a non-volatile computer-readable storage medium:

[0041] The non-volatile computer-readable storage medium stores instructions, which, when executed on a computer, implement the method described in the second aspect.

[0042] In the seventh aspect, an embodiment of the present application provides a vehicle, which may include the on-board device as described in the third aspect or the non-volatile computer-readable storage medium as described in the fourth aspect, and the on-board device as described in the fifth aspect or the non-volatile computer-readable storage medium as described in the sixth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] To more clearly illustrate the technical solutions in the embodiments of this application, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be derived from these drawings without inventive effort.

[0044] FIG1 is a flow chart of a communication connection method provided in an embodiment of the present application;

[0045] FIG2 is a schematic diagram of a scenario in which a second vehicle-mounted device generates a wireless connection request according to an embodiment of the present application;

[0046] FIG3 is a schematic diagram of a flow chart of a first vehicle-mounted device processing a wireless connection request according to an embodiment of the present application;

[0047] FIG4 is a schematic diagram of a process for updating a connected list according to an embodiment of the present application;

[0048] FIG5 is a schematic diagram of another scenario of updating a connected list provided in an embodiment of the present application;

[0049] FIG6 is a schematic diagram of a process for a first vehicle-mounted device to disable a wireless communication hotspot service according to an embodiment of the present application;

[0050] FIG7 is a schematic diagram of the composition of a vehicle-mounted device provided in an embodiment of the present application;

[0051] FIG8 is a schematic diagram of the composition of another vehicle-mounted device provided in an embodiment of the present application.

[0052] Description of reference numerals:

[0053] 50-vehicle display screen, 700-on-board equipment, 710-communication module, 720-control module, 800-on-board equipment, 810-processor, 820-memory, 821-storage system, 822-cache, 823-RAM, 830-I / O interface. DETAILED DESCRIPTION

[0054] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0055] The terms "first," "second," "third," and "fourth," etc., in the specification and claims of this application and the accompanying drawings are used to distinguish between different objects, rather than to describe a specific order. In addition, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0056] References to "embodiments" herein mean that a particular feature, result, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0057] One purpose of the present application is to provide a communication connection method, a vehicle-mounted device and related media, which can connect to a hotspot device (i.e., a device that provides wireless communication hotspot services) with a specific media access control MAC address, thereby helping to avoid user data leakage due to connecting to other hotspots (or other wireless communication hotspot services) with the same user name and password, and helping to protect.

[0058] It can be seen that the present application can allow hotspot devices (i.e., devices that provide wireless communication hotspot services) to avoid situations where the device mistakenly connects to a hotspot (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.

[0059] In order to better understand the technical solution of the embodiment of the present application, a communication connection method provided by the embodiment of the present application will be described in detail below with reference to FIG1 .

[0060] Please refer to FIG1 , which is a flow chart of a communication connection method provided in an embodiment of the present application. The method may include the following steps:

[0061] S101: A first vehicle-mounted device receives a wireless connection request from a second vehicle-mounted device.

[0062] It should be noted that the wireless connection request sent by the second vehicle-mounted device at least includes the user name, password and encryption method of the wireless communication hotspot service to which the second vehicle-mounted device is expected to connect.

[0063] In a possible implementation, before the first in-vehicle device receives the wireless connection request from the second in-vehicle device, the method may further include:

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

[0065] The first vehicle-mounted device sends first information to the second vehicle-mounted device through 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.

[0066] In another possible implementation, the first information may include a user name and password of the wireless communication hotspot service and a device identification of the first vehicle-mounted device.

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

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

[0069] The first vehicle-mounted device receives second information sent by the second vehicle-mounted device through a wired connection. The second information may include a device identification of the second vehicle-mounted device.

[0070] Furthermore, the first in-vehicle device may create an in-vehicle device list, and the in-vehicle device list may include MAC addresses of in-vehicle devices that have a wired connection with the first in-vehicle device.

[0071] For example, please refer to Figure 2, which is a schematic diagram of a scenario in which a second vehicle-mounted device generates a wireless connection request according to an embodiment of the present application.

[0072] As shown in Figure 2, in response to the vehicle starting up and the vehicle-mounted devices (including the first vehicle-mounted device and other vehicle-mounted devices) on the vehicle being turned on, the first vehicle-mounted device will use the CAN bus to send a first message to the other vehicle-mounted devices in the same vehicle (which can be understood as the second vehicle-mounted device in this application). The first message may include the username, password, encryption method and device identifier of the wireless communication hotspot service provided by the first vehicle-mounted device (such as the MAC address of the first vehicle-mounted device), and the first vehicle-mounted device will also monitor the CAN bus for MAC addresses transmitted by other vehicle-mounted devices. When the first vehicle-mounted device receives MAC address information sent by other vehicle-mounted devices, the first vehicle-mounted device will save these MAC addresses in the vehicle-mounted device list. After being turned on, other vehicle-mounted devices in the same vehicle as the first vehicle-mounted device will also send their MAC addresses to the first vehicle-mounted device via the CAN bus. The other vehicle-mounted devices can also monitor and receive the first message sent by the first vehicle-mounted device on the CAN bus, and then generate a wireless connection request based on the first message. Among them, the other vehicle-mounted devices specify the target device by carrying a preset device identifier in the wireless connection request. The target device is the device with which the other vehicle-mounted device wants to establish a wireless connection.

[0073] It can be seen that the vehicle-mounted devices in the embodiment of the present application will communicate MAC addresses with each other through a wired manner (such as a CAN bus), which will help to establish a reliable and accurate wireless connection based on the MAC address in the future, thereby preventing accidental connection to the wireless network and protecting data security.

[0074] S102: 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, the first vehicle-mounted device allows the second vehicle-mounted device to establish a wireless connection.

[0075] For example, if the first vehicle-mounted device receives two wireless connection requests (wireless connection request 1 contains preset device identifier 1, and wireless connection request 2 does not contain preset device identifier 2), it can be considered that wireless connection request 1 is sent by the vehicle-mounted device, and wireless connection request 2 is sent by the user-controlled mobile terminal. As to 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 the wireless connection request 1 matches the device identifier of the first vehicle-mounted device. As to whether to allow the mobile terminal corresponding to the wireless connection request 2 to establish a wireless connection, the first vehicle-mounted device only needs to determine whether the target user name, password and encryption method carried in the wireless connection request 2 are the same as the user name, password and encryption method of the wireless communication hotspot service provided by the first vehicle-mounted device.

[0076] In a possible implementation, the method may further include:

[0077] In the case that 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-mounted device, the first vehicle-mounted device rejects the wireless connection request of the second vehicle-mounted device.

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

[0079] The first vehicle-mounted device receives second information sent by the second vehicle-mounted device through a wired connection. The second information may include a device identification of the second vehicle-mounted device.

[0080] In another possible implementation, 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, after the first vehicle-mounted device allows the second vehicle-mounted device to establish a wireless connection, the method may further include:

[0081] When displaying the device connection list of the hotspot service, the first vehicle-mounted device hides the information of the second vehicle-mounted device.

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

[0083] When the second information matches the third information, hiding the information of the second in-vehicle device;

[0084] The third information is information sent by the second vehicle-mounted device and received by the first vehicle-mounted device through a wireless connection. The third information may include a device identifier of the second vehicle-mounted device.

[0085] For example, please refer to FIG3 , which is a flowchart of a first vehicle-mounted device processing a wireless connection request according to an embodiment of the present application.

[0086] As shown in FIG3 , the process of the first vehicle-mounted device processing a wireless connection request may refer to the following steps:

[0087] S301 : Create a list of in-vehicle devices according to device identifiers of other in-vehicle devices in the same vehicle.

[0088] S302: Receive a wireless connection request from a second vehicle-mounted device.

[0089] S303: Determine whether the wireless connection request of the second vehicle-mounted device includes (or specifies) a preset device identifier.

[0090] If the judgment result is no, then S304 is executed to allow the second vehicle-mounted device to establish a wireless connection.

[0091] If the judgment result is yes, then step S305 is executed to confirm whether the preset device identifier is the same as the device identifier of the first vehicle-mounted device.

[0092] 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, 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, S3052 is executed to reject the wireless connection request of the second vehicle-mounted device.

[0093] For example, assume that the on-board device list established by the first on-board device (with the corresponding device identifier set to MAC address 1) contains on-board device 1 (with the corresponding device identifier set to MAC address 2), on-board device 2 (with the corresponding device identifier set to MAC address 3), and on-board device 3 (with the corresponding device identifier set to MAC address 4). When the first on-board device receives a wireless connection request from the second on-board 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 on-board device wants to establish a wireless connection), the second on-board device can be considered to be a non-on-board device (such as a user's mobile terminal), and the first on-board device is allowed to establish a wireless connection. If the wireless connection request specifies a preset device identifier, the second on-board device is considered to be an on-board device, and it is necessary to determine whether the preset device identifier is the same as the on-board device identifier (i.e., MAC address 1). If the preset device identifier and the on-board device identifier are the same, the second on-board device is allowed to establish a wireless connection. If the preset device identifier and the on-board device identifier are different, the wireless connection request of the second on-board device is rejected.

[0094] It should be noted that in the embodiment of the present application, before the first vehicle-mounted device determines whether the wireless connection request of the second vehicle-mounted device contains a preset device identifier, it is necessary to determine whether the target user name, password, and encryption method in the wireless connection request of the second vehicle-mounted device are the same as the user name, 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 the MAC address) can be confirmed; if they are not the same, the wireless connection request of the second vehicle-mounted device is rejected. Among them, the target user name, password, and encryption method in the wireless connection request of the second vehicle-mounted device are the user name, password, and encryption method of the wireless communication hotspot service that the second vehicle-mounted device wants to obtain.

[0095] It can be seen that the embodiment of the present application can allow a hotspot device (i.e., a device providing wireless communication hotspot services) to avoid the device from mistakenly connecting to a hotspot (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 the wireless connection and protect the security of user data.

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

[0097] Establish a connected list, which may include connection information of devices that have been wirelessly connected to the first vehicle-mounted device. The connection information may include the name of the device that has been wirelessly connected to the first vehicle-mounted device. The connection information may also include the connection duration of the device that has been wirelessly connected to the first vehicle-mounted device.

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

[0099] When the second information matches the third information, hiding the information of the second in-vehicle device;

[0100] The third information is information sent by the second vehicle-mounted device and received by the first vehicle-mounted device through a wireless connection. The third information may include a device identifier of the second vehicle-mounted device.

[0101] Exemplarily, when the wireless connection request includes a device identifier (such as a MAC address) of the second vehicle-mounted device that matches the MAC address in the vehicle-mounted device list, the connection information of the second vehicle-mounted device is removed from the connected list, and the updated connected list is presented on the display module of the vehicle computer.

[0102] For example, please refer to FIG4 , which is a flowchart of updating a connected list provided in an embodiment of the present application.

[0103] As shown in FIG4 , the process of the first vehicle-mounted device updating the connected list may refer to the following steps:

[0104] S401: Update the connected list according to a preset period.

[0105] For example, the first vehicle-mounted device may refresh the connected list at a preset period (e.g., 1 second) and save the connection information of devices that have established a wireless connection with the first vehicle-mounted device within the previous period (e.g., 1 second) to the connected list. Alternatively, the first vehicle-mounted device may save the connection information of a device to the connected list in response to a successful wireless connection between the device and the first vehicle-mounted device. Furthermore, the first vehicle-mounted device may update the connection duration of the device at a preset period (e.g., 30 milliseconds).

[0106] Similarly, the first vehicle-mounted device may refresh the connected list at a preset period (e.g., 1 second) and delete from the connected list the connection information of devices that have disconnected from the first vehicle-mounted device within the previous period (e.g., 1 second). Alternatively, the first vehicle-mounted device may delete from the connected list the connection information of a device that has disconnected from the first vehicle-mounted device.

[0107] S402: Determine whether the device identifier of the device in the connected list is in the in-vehicle device list.

[0108] If the judgment result is no, then S403 is executed to present a connected list.

[0109] If the judgment result is yes, then S404 is executed to delete the connection information of the device from the connected list and present an updated list.

[0110] Furthermore, please refer to FIG5 , which is a schematic diagram of another scenario of updating the connected list provided in an embodiment of the present application.

[0111] As shown in FIG5 , assume that there is an existing connected list 1. Connected list 1 contains device 1 (the wireless connection request includes a preset device identifier, which is the same as the device identifier of the first vehicle-mounted device, but the device identifier of device 1 is not in the vehicle-mounted device list) and device 2 (the wireless connection request does not include a preset device identifier). The connection duration of device 1 is 5 minutes, and the connection duration of device 2 is 2 minutes. If existing devices 3 (the wireless connection request includes a preset device identifier, which is the same as the device identifier of the first vehicle-mounted device, and the device identifier of device 3 is in the vehicle-mounted device list) and 4 (the wireless connection request does not include a preset device identifier) ​​establish a wireless connection with the first vehicle-mounted device, 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 display list is presented to the user, resulting in an updated connected list 3. Finally, connected list 3 will be presented on the vehicle's onboard display screen 50. It should be noted that the above example of the embodiment of the present application presenting the connected list on the vehicle display screen 50 is only for the purpose of explaining the present application scheme in more detail, and should not constitute a limitation. The connected list can also be presented on other display screens of the vehicle and / or the user's mobile terminal with display function, which is not limited here. The specific presentation method of the connected list is set by technical personnel according to actual conditions.

[0112] It can be seen that the embodiment of the present application will delete the connection information of the in-vehicle self-organizing network device (that is, other vehicle-mounted devices in the same vehicle as the hotspot device, and the hotspot device is a device that provides wireless communication hotspot services) and maintain the connected list, which will help improve the user experience and avoid the situation where the user accidentally kicks the in-vehicle self-organizing network device out of the self-organizing network, and help ensure that the vehicle can provide related in-vehicle services normally.

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

[0114] In response to a request to close the hotspot service of the first in-vehicle device, the wireless connection between the first in-vehicle device and the second in-vehicle device is maintained.

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

[0116] Possibly, the first vehicle-mounted device may also disconnect the wireless connection relationship with all devices in the connected list, and remove the connection information of all devices in the connected list.

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

[0118] The first in-vehicle device hides its own service set identifier SSID broadcast.

[0119] For example, please refer to FIG6 , which is a flowchart of a first vehicle-mounted device shutting down a wireless communication hotspot service according to an embodiment of the present application.

[0120] As shown in FIG6 , the process of the first vehicle-mounted device shutting down the wireless communication hotspot service can refer to the following steps:

[0121] S601: In response to a user turning off a first vehicle-mounted device, closing a wireless communication hotspot service calling interface.

[0122] Possibly, the user can directly operate on the first in-vehicle device to turn off the wireless communication hotspot service without turning off the first in-vehicle device.

[0123] S602: Use the wireless communication hotspot service framework and the hardware abstraction layer to call a private interface.

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

[0125] S603: Disconnect the wireless connection with the non-vehicle device in the connected list.

[0126] S604, hiding its own SSID broadcast.

[0127] S605: Reporting system wireless communication hotspot service is closed.

[0128] It can be seen that the embodiment of the present application can present to the user the complete result of shutting down the wireless communication hotspot service without affecting the normal wireless connection between the in-vehicle self-organizing network device (that is, other vehicle-mounted devices in the same vehicle as the hotspot device, and the hotspot device is a device that provides wireless communication hotspot services) and the hotspot device, which helps to ensure the integrity of vehicle services or functions without affecting the user experience.

[0129] The following describes the device involved in the embodiments of the present application with reference to the accompanying drawings.

[0130] Please refer to FIG7 , which shows an in-vehicle device 700 provided in an embodiment of the present application. The in-vehicle device 700 may include: a communication module 710 and a control module 720 ;

[0131] The communication module 710 may be configured to receive a wireless connection request from a second vehicle-mounted device;

[0132] The control module 720 may be configured to allow the vehicle-mounted device 700 to establish a wireless connection with the second vehicle-mounted device when the wireless connection request includes a preset device identifier and the preset device identifier matches the device identifier of the vehicle-mounted device.

[0133] In a possible implementation, the vehicle-mounted device 700 may further include:

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

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

[0136] In another possible implementation, the first information may include a user name and password of the wireless communication hotspot service and a device identification of the first vehicle-mounted device.

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

[0138] The control module 720 may also be configured to cause the first vehicle-mounted device to reject the wireless connection request of the second vehicle-mounted device 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-mounted device.

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

[0140] The communication module 710 may also be configured to receive second information sent by a second vehicle-mounted device. The second information may include a device identifier of the second vehicle-mounted device.

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

[0142] The control module 720 may also be configured to hide the information of the second vehicle-mounted device when displaying the device connection list of the hotspot service.

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

[0144] The control module 720 may also be configured to hide information of the second vehicle-mounted device when the second information matches the third information;

[0145] The third information is information sent by the second vehicle-mounted device and received by the first vehicle-mounted device through a wireless connection. The third information may include a device identifier of the second vehicle-mounted device.

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

[0147] The control module 720 may also be configured to maintain the wireless connection between the first vehicle-mounted device and the second vehicle-mounted device in response to a request for closing the hotspot service of the first vehicle-mounted device.

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

[0149] The control module 720 may also be used to enable the first vehicle-mounted device to hide its own SSID broadcast.

[0150] Please refer to FIG8 , which is a schematic diagram of another vehicle-mounted device 800 provided in an embodiment of the present application. The vehicle-mounted device 800 may include:

[0151] Processor 810, memory 820, and I / O interface 830. The processor 810, memory 820, and I / O interface 830 are communicatively connected, the memory 820 is used to store instructions, and the processor 810 is used to execute the instructions stored in the memory 820 to implement the method steps corresponding to Figures 1, 3, 4, and 6 above.

[0152] The processor 810 is used to execute the instructions stored in the memory 820 to control the I / O interface 830 to receive and send signals and complete the steps in the above method. The memory 820 can be integrated into the processor 810 or set separately from the processor 810.

[0153] Memory 820 may also include a storage system 821, a cache 822, and RAM 823. Cache 822 is a primary memory located between RAM 823 and the CPU. It consists of static RAM (SRAM) chips and has a relatively small capacity but a much higher speed than main memory, approaching the speed of the CPU. RAM 823 is internal memory that directly exchanges data with the CPU. It can be read and written at any time (except when refreshing) and is very fast. It is typically used as a temporary data storage medium for the operating system or other running programs. The three together realize the functions of memory 820.

[0154] As an implementation method, the function of the I / O interface 830 may be implemented by a transceiver circuit or a dedicated transceiver chip. The processor 810 may be implemented by a dedicated processing chip, a processing circuit, a processor, or a general-purpose chip.

[0155] As another implementation, it is possible to implement the apparatus provided in the embodiments of the present application using a general-purpose computer. Specifically, the program code implementing the functions of the processor 810 and the I / O interface 830 is stored in the memory 820, and the general-purpose processor executes the code in the memory 820 to implement the functions of the processor 810 and the I / O interface 830.

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

[0157] As another implementation of this embodiment, a computer-readable storage medium is provided, on which instructions are stored. When the instructions are executed, the method in the above method embodiment is executed.

[0158] As another implementation of this embodiment, a computer program product including instructions is provided. When the instructions are executed, the method in the above method embodiment is performed.

[0159] Those skilled in the art will appreciate that, for ease of explanation, FIG8 shows only one memory and processor. In an actual terminal or server, multiple processors and memories may exist. The memory may also be referred to as a storage medium or storage device, etc., which is not limited in the present embodiment.

[0160] It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0161] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may 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 may 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 random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAMbus RAM (DR RAM).

[0162] 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, discrete hardware component, the memory (storage module) is integrated into the processor.

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

[0164] In addition to the data bus, the bus may also include a power bus, a control bus, a status signal bus, etc. However, for the sake of clarity, various buses are labeled as buses in the figure.

[0165] It should also be understood that the first, second, third, fourth and various numerical numbers involved in this document are only distinctions made for the convenience of description and are not intended to limit the scope of this application.

[0166] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0167] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature 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, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0168] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean 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 the present application.

[0169] Those skilled in the art will appreciate that the various illustrative logical blocks (ILBs) and steps described in conjunction with the embodiments disclosed herein can be implemented using 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. Professionals and technicians may 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.

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

[0171] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

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

[0173] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable 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, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. 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 integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk).

[0174] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. The computer program is executed by a processor to implement part or all of the steps of any one of the communication connection methods described in the above method embodiments.

[0175] An embodiment of the present application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable a computer to execute part or all of the steps of any one of the communication connection methods described in the above method embodiments.

[0176] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication connection method, characterized in that: The method is performed by a first vehicle-mounted device, where the first vehicle-mounted device is a vehicle-mounted device that provides a wireless communication hotspot service. The method includes: The first vehicle-mounted device receives a wireless connection request from the second vehicle-mounted device; In a case where 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 first vehicle-mounted device allows the second vehicle-mounted device to establish a wireless connection.

2. The method according to claim 1, characterized in that Before the first vehicle-mounted device receives the wireless connection request of 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 through the wired connection, and the first information is used for the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device according to the first information.

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

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: In a case where 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-mounted device, the first vehicle-mounted device rejects the wireless connection request of the second vehicle-mounted device.

5. The method according to any one of claims 2 to 4, characterized in that The method further comprises: The first vehicle-mounted device receives second information sent by the second vehicle-mounted device through the wired connection, where the second information includes a device identification of the second vehicle-mounted device.

6. The method according to any one of claims 1 to 5, characterized in that In the case where the wireless connection request includes a preset device identifier, and the preset device identifier matches the device identifier of the first vehicle-mounted device, after the first vehicle-mounted device allows the second vehicle-mounted device to establish a wireless connection, the method further includes: When displaying the device connection list of the hotspot service, the first vehicle-mounted device hides the information of the second vehicle-mounted device.

7. The method according to claim 6, characterized in that The step of hiding the information of the second vehicle-mounted device includes: When the second information matches the third information, hiding the information of the second vehicle-mounted device; The third information is information sent by the second vehicle-mounted device and received by the first vehicle-mounted device through the wireless connection. The third information includes a device identifier of the second vehicle-mounted device.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: In response to a request to close the hotspot service of the first vehicle-mounted device, maintaining the first vehicle-mounted device and the first vehicle-mounted device connected to the hotspot service.

2. Wireless connection of vehicle-mounted equipment.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: The first vehicle-mounted device hides its own SSID broadcast.

10. A communication connection method, characterized in that: Applied to a second vehicle-mounted device, the method includes: 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 a wireless communication hotspot service; In a case where 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.

11. The method according to claim 10, 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 the first information sent by the first vehicle-mounted device through the wired connection, and the first information is used for the second vehicle-mounted device to establish a wireless connection with the first vehicle-mounted device according to the first information.

12. The method according to claim 11, characterized in that The first information includes a user name and a password of the wireless communication hotspot service and a device identification of the first vehicle-mounted device.

13. The method according to claim 11 or 12, characterized in that: The method further comprises: The second vehicle-mounted device sends second information to the first vehicle-mounted device through the wired connection, where the second information includes a device identifier of the second vehicle-mounted device; The second vehicle-mounted device sends third information to the first vehicle-mounted device through the wireless connection, and the third information includes the device identification of the second vehicle-mounted device, so that the first vehicle-mounted device 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 based on the second information and the third information.

14. A vehicle-mounted device (800), characterized in that: include: A processor (810), a memory (820) and an I / O interface (830), wherein the processor (810), the memory (820) and the I / O interface (830) are communicatively connected, wherein the memory (820) is used to store a set of program codes, and the processor (810) is used to call the program codes stored in the memory (820) to execute the method according to any one of claims 1 to 9.

15. A non-volatile computer-readable storage medium, characterized in that: The non-volatile computer-readable storage medium stores instructions, which, when executed on a computer, implement the method according to any one of claims 1 to 9.

16. A vehicle-mounted device (800), characterized in that: include: A processor (810), a memory (820) and an I / O interface (830), wherein the processor (810), the memory (820) And the I / O interface (830) is communicatively connected, wherein the memory (820) is used to store a set of program codes, and the processor (810) is used to call the program codes stored in the memory (820) to execute the method as described in any one of claims 10 to 13.

17. A non-volatile computer-readable storage medium, characterized in that: The non-volatile computer-readable storage medium stores instructions, which, when executed on a computer, implement the method according to any one of claims 10 to 13.

18. A vehicle, characterized in that: The vehicle includes the in-vehicle device or the non-volatile computer-readable storage medium according to claim 14 or 15, and the in-vehicle device or the non-volatile computer-readable storage medium according to claim 16 or 17.

Images