A method, device and equipment for managing vehicle-mounted equipment

Abstract

The embodiments of this specification disclose a method, device and equipment for managing vehicle-mounted equipment. By establishing a communication connection with a multi-protocol gateway in a vehicle, wherein the client has been pre-associated with the vehicle-mounted equipment through the multi-protocol gateway; determining the device type of the vehicle-mounted equipment, and determining the communication method between the client and the multi-protocol gateway according to the device type; and managing the vehicle-mounted equipment through the multi-protocol gateway based on the determined communication method. Thereby, the adaptation of multiple communication protocols is realized, and unified management of multiple vehicle-mounted equipment is completed through one terminal.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a method, device and equipment for managing vehicle-mounted equipment. Background Art

[0002] With the continuous enrichment of aftermarket vehicle hardware, vehicle users often need to download different apps or even use different controllers (such as infrared remote controls) to manage different hardware. For example, the on-board diagnostic system usually uses the Controller Area Network (CAN) bus to connect. Sometimes different devices may occupy each other's communication lines when working at the same time, which is not conducive to unified management by users.

[0003] Based on this, a more convenient management solution for vehicle-mounted equipment is needed. Summary of the invention

[0004] One or more embodiments of the present specification provide a method, apparatus, device and storage medium for managing vehicle-mounted equipment to solve the following technical problem: a more convenient management solution for vehicle-mounted equipment is needed.

[0005] To solve the above technical problems, one or more embodiments of this specification are implemented as follows:

[0006] In a first aspect, an embodiment of the present specification provides a method for managing an in-vehicle device, which is applied to a client, and the method includes: establishing a communication connection with a multi-protocol gateway in a vehicle, wherein the client has been pre-associated with the in-vehicle device through the multi-protocol gateway; determining a device type of the in-vehicle device, and determining a communication method between the client and the multi-protocol gateway according to the device type; and managing the in-vehicle device through the multi-protocol gateway based on the determined communication method.

[0007] In a second aspect, an embodiment of the present specification provides a management device for an in-vehicle device, which is applied to a client, and the device includes: a communication module, which establishes a communication connection with a multi-protocol gateway in a vehicle, wherein the client has been pre-associated with the in-vehicle device through the multi-protocol gateway; a determination module, which determines the device type of the in-vehicle device and determines the communication method between the client and the multi-protocol gateway according to the device type; and a management module, which manages the in-vehicle device through the multi-protocol gateway based on the determined communication method.

[0008] In a third aspect, an embodiment of the present specification provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method described in the first aspect.

[0009] In a fourth aspect, an embodiment of the present specification further provides a non-volatile computer storage medium storing computer executable instructions. When a computer reads the computer executable instructions in the storage medium, the instructions enable one or more processors to execute the method described in the first aspect.

[0010] At least one of the above technical solutions adopted in one or more embodiments of this specification can achieve the following beneficial effects: by establishing a communication connection with the multi-protocol gateway in the vehicle, wherein the client has been pre-associated with the vehicle-mounted device through the multi-protocol gateway; determining the device type of the vehicle-mounted device, and determining the communication method between the client and the multi-protocol gateway according to the device type; based on the determined communication method, managing the vehicle-mounted device through the multi-protocol gateway. Thus, the adaptation of multiple communication protocols is realized, and unified management of multiple vehicle-mounted devices is completed through one terminal, which is more convenient for users. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0012] Figure 1 A flowchart of a method for managing vehicle-mounted equipment provided in an embodiment of this specification;

[0013] Figure 2 A schematic diagram of the communication connection between the multi-protocol gateway and the client provided in the embodiment of this specification;

[0014] Figure 3 A schematic diagram of a management interface in a client provided in an embodiment of this specification;

[0015] Figure 4 A schematic diagram of the structure of a management device for vehicle-mounted equipment provided in an embodiment of this specification;

[0016] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0017] The embodiments of this specification provide a method, apparatus, device and storage medium for managing an in-vehicle device.

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

[0019] Figure 1 A flowchart of a method for managing an in-vehicle device provided in an embodiment of this specification is applied to a client, and the method includes:

[0020] S101, establishing a communication connection with a multi-protocol gateway in a vehicle, wherein the client has been pre-associated with the vehicle-mounted device through the multi-protocol gateway.

[0021] A gateway, also known as an internetwork connector or protocol converter, is used between two systems with different communication protocols, data formats or languages, or even completely different architectures. In other words, a gateway is a translator.

[0022] In the embodiments of this specification, a multi-protocol gateway refers to a gateway that can support multiple different communication protocols at the same time. For example, the supported protocols include Controller Area Network (CAN), WIFI, Bluetooth (Bluetooth / BLE), KNX-RF, ZIGBEE, etc.

[0023] By supporting different types of protocols, a variety of different vehicle-mounted devices can communicate with the multi-protocol gateway at the same time. As shown in Table 1, Table 1 is an exemplary list of protocols and devices supported by the multi-protocol gateway provided in the embodiments of this specification.

[0024] Table 1

[0025] Serial number Protocol Name Connection Examples of common equipment 1 CAN Serial bus physical connection OBD、ECU 2 WIFI Connect using wifi hotspot Driving Recorder 3 Bluetooth / BLE Bluetooth connection ETC equipment, tire pressure monitoring 4 KNX-RF RF signal, RF pairing required Car air purifier 5 ZIGBEE 2.4G band IoT protocol Car refrigerator, electric seat cushion

[0026] When the user is near the vehicle (for example, the user is in the vehicle or near the door, etc.), the client can scan based on the Bluetooth function in the device where the client is located and establish a communication connection with the multi-protocol gateway. Alternatively, an indirect communication connection can be established with the multi-protocol gateway through the server.

[0027] like Figure 2 As shown, Figure 2 A schematic diagram of the communication connection between the multi-protocol gateway and the client provided in the embodiment of this specification. In this schematic diagram, multiple vehicle-mounted devices communicate with the multi-protocol gateway using different protocols. The multi-protocol gateway can directly communicate with the client via Bluetooth for short-range communication, and can also indirectly communicate with the client via the server via 5G signals for long-range communication.

[0028] S103, determining the device type of the vehicle-mounted device, and determining the communication mode between the client and the multi-protocol gateway according to the device type.

[0029] After the in-vehicle device is connected to the gateway, the status changes and content storage are synchronized to the mobile phone application and cloud storage via Bluetooth and 5G respectively for subsequent user use. In other words, the type information, status information and content information of various devices can be retained in the client at this time. Among them, the type information is used to indicate the communication protocol that the in-vehicle device can adopt, the status information is used to indicate the status characteristics contained in the in-vehicle device, and the content information is used to indicate the specific values ​​of each status characteristic.

[0030] For example, for a driving recorder, the client determines its device type as "model 1", that is, it uses the first type of communication protocol, namely WIFI connection; at the same time, for the vehicle-mounted OBD, the client determines its device type as "model 2", that is, it uses the second type of communication protocol, namely CAN bus connection.

[0031] For another example, for the vehicle-mounted OBD, the status information contained therein can be saved and directly displayed in the client. The status features contained therein may include "engine, particulate filter, catalytic converter, oxygen sensor, emission control system and fuel system", etc. Different content information can be used in each status feature to indicate the specific circumstances of each status feature, for example, different fault information and related codes can be used to indicate normal or abnormal, etc.

[0032] In this process, the multi-protocol gateway simultaneously connects to vehicle-mounted devices with different communication protocols, and translates the communication data with different types of vehicle-mounted devices into a unified format acceptable to the client, so that vehicle-mounted devices with different communication protocols can be displayed on the client at the same time.

[0033] Alternatively, the device type can also be used to indicate the communication response time of the device so that the client can choose the communication method with the multi-protocol gateway. For example, if the device type is "Model A", it indicates that it requires a shorter network response time, so the client can choose to have a short-range wireless connection with the multi-protocol gateway; for another example, if the device type is "Model A", it indicates that it can receive a longer network response time, so the client can choose to have a long-range wireless connection with the multi-protocol gateway based on server-side relay.

[0034] S105: Based on the determined communication mode, manage the vehicle-mounted device through the multi-protocol gateway.

[0035] After the client determines the communication mode with the multi-protocol gateway, the vehicle-mounted device can be selected in the display interface of the client to select the target device to be managed.

[0036] In this process, the client can predetermine the communication method with the multi-protocol gateway and display the communication method with the multi-protocol gateway at the same time. Figure 3 As shown, Figure 3 A schematic diagram of a management interface in a client provided in an embodiment of this specification. In this management schematic diagram, only the communication method between the client and the multi-protocol gateway needs to be displayed, while the communication method between each vehicle-mounted device and the multi-protocol gateway can be hidden. For example, for a vehicle-mounted refrigerator, electric seat cushion, etc., they communicate with the multi-protocol gateway through ZIGBEE, while the vehicle-mounted air purifier communicates with the multi-protocol gateway through the radio frequency signal KNX-RF. However, in the client display interface, it is only necessary to display that if the user needs to manage the vehicle-mounted refrigerator, electric seat cushion or vehicle-mounted air purifier, the client communicates with the multi-protocol gateway through Bluetooth, thereby shielding the user from the different communication methods of different vehicle-mounted devices, which is more user-friendly in the management interface.

[0037] By establishing a communication connection with the multi-protocol gateway in the vehicle, wherein the client has been pre-associated with the vehicle-mounted device through the multi-protocol gateway; determining the device type of the vehicle-mounted device, and determining the communication method between the client and the multi-protocol gateway according to the device type; and managing the vehicle-mounted device through the multi-protocol gateway based on the determined communication method. Thus, the adaptation of multiple communication protocols is achieved, and unified management of multiple vehicle-mounted devices is completed through one terminal, which is more convenient for users.

[0038] In one embodiment, the client may pre-store the corresponding relationship of the communication response time required by the vehicle-mounted device, so that the client may determine the communication mode of the multi-protocol gateway based on the communication response time of each device type. For example, the preset response value may be set to 1000ms, and the client pre-stores the communication response time corresponding to the driving recorder as 100ms, that is, for the driving recorder, the required communication response time is very short. At this time, when the client needs to manage the driving recorder, it can be known that the communication response time corresponding to the driving recorder is lower than the preset response value, and a short-range wireless connection is adopted, such as Bluetooth. For another example, for the OBD system, the server needs to perform a comprehensive analysis based on the relevant data of the sensor to determine the specific status of the vehicle-mounted device, and the corresponding communication response time can be longer (for example, it can be 5s). Then, at this time, it can be known that the communication response time corresponding to the OBD system is higher than the preset response value, and the client can use a remote wireless connection to communicate with the multi-protocol gateway. In this way, the communication mode with the multi-protocol gateway can be flexibly selected based on the corresponding needs of the device to improve the user experience.

[0039] In one embodiment, when the determined communication mode is a remote wireless connection (for example, indirect remote communication between a server and a multi-protocol gateway based on a 5G signal), the management of the vehicle-mounted device through the multi-protocol gateway can be carried out in the following manner: obtaining the status data of the vehicle-mounted device sent by the server and displaying it, wherein the status data is generated by the server based on the relevant information of the vehicle-mounted device sent by the multi-protocol gateway; generating management instructions for the vehicle-mounted device based on user operations, and forwarding them to the multi-protocol gateway through the server, so that the multi-protocol gateway forwards the management instructions to the vehicle-mounted device.

[0040] For example, when the vehicle-mounted device to be managed is an OBD system, its related data needs to be sent to the cloud server for preprocessing. At this time, the client determines that the communication method with the multi-protocol gateway is a remote wireless connection, then the client can establish a connection with the server, and obtain the status data of the vehicle-mounted device from the server (the client can be pre-bound with the vehicle-mounted device on the server), and then display the relevant status data provided by the OBD system including "engine, particulate filter, catalytic converter, oxygen sensor, emission control system and fuel system" on the client. At this time, if the client finds that a system is abnormal (for example, the engine may be abnormal), it can generate a "turn off the engine" instruction through the client, and forward it to the multi-protocol gateway through the server, so as to realize remote management of the vehicle-mounted device. In other words, in this embodiment, the user does not need to be near the vehicle, but can manage the vehicle-mounted device at any time in a different place to meet the actual needs of the user.

[0041] In one embodiment, the short-range wireless connection between the client and the multi-protocol gateway uses a Bluetooth connection, and the long-range wireless connection includes a wireless switch on the server side. In reality, some commonly used devices often need to use WiFi to connect to the multi-protocol gateway and perform a large amount of data transmission (for example, a driving recorder usually needs to connect to the multi-protocol gateway based on WiFi and occupy the data transmission channel of the protocol). At this time, if the client and the multi-protocol gateway should avoid using the same data channel as the vehicle-mounted device, then Bluetooth can be used to connect to the multi-protocol gateway. At the transmission speed of Bluetooth, the image transmission rate of the driving recorder can also be met, and the image stream collected by the driving recorder can be transmitted to the client, and the data transmission channel under the WiFi protocol can be avoided from competing with the driving recorder, thereby avoiding data transmission congestion and improving the client's management efficiency and quality of vehicle-mounted devices.

[0042] In one embodiment, when the vehicle-mounted device and the client are associated for the first time, the client can be pre-associated with the vehicle-mounted device through the multi-protocol gateway in the following manner: the client establishes a communication connection with the multi-protocol gateway; obtains the vehicle-mounted device identifier input by the user, and sends the vehicle-mounted device identifier to the multi-protocol gateway so that the multi-protocol gateway performs consistency verification on the vehicle-mounted device identifier; after the consistency verification is passed, establishes a pre-association with the vehicle-mounted device.

[0043] The vehicle-mounted device identification here can be dynamic or static. For example, for vehicle-mounted devices such as vehicle-mounted refrigerators or driving recorders with display devices, they can generate dynamic vehicle-mounted device identification through built-in algorithms (for example, using the built-in unique device number as a seed, generating a dynamic string as the vehicle-mounted device identification every 1 minute) and display it; for devices such as vehicle-mounted air purifiers and OBD systems, the static factory number and other unique device numbers displayed on the devices can be used as vehicle-mounted device identification.

[0044] The vehicle-mounted device passes the vehicle-mounted device identification through the multi-protocol gateway, and the user is also required to manually input another vehicle-mounted device identification in the client interface, and the other vehicle-mounted device identification manually input by the user is sent to the multi-protocol gateway, so that the multi-protocol gateway can verify the consistency of the vehicle-mounted device identification. After the consistency verification is passed, the pre-association with the vehicle-mounted device is established, and the management interface of the vehicle-mounted device is displayed in the client interface. In this way, the authenticated management of the vehicle-mounted device can be realized to avoid the wrong or malicious association of other users.

[0045] In one embodiment, for the access of the vehicle-mounted device, the communication protocol and / or interface of the vehicle-mounted device can also be identified during the first pre-access to determine whether the communication protocol and / or interface of the vehicle-mounted device meets the preset conditions; if so, an association with the vehicle-mounted device is established. The preset conditions here may include that the communication protocol adopted by the vehicle-mounted device belongs to one of several preset communication protocols, or that the interface adopted by the vehicle-mounted device meets the standard adopted by the multi-protocol gateway, or that the vehicle-mounted device should provide a corresponding operation interface for users to perform management operations, etc. In this way, standardized management of the communication protocol / interface of the vehicle-mounted device can be achieved, reducing the management difficulty of the user and improving the user experience.

[0046] In one embodiment, some vehicle-mounted devices may be able to support multiple protocols at the same time. In this case, when the client manages the vehicle-mounted device through the multi-protocol gateway, the multiple protocols supported by the multi-protocol gateway can also be displayed in the client interface, so that the user can selectively configure based on the actual situation, thereby determining the protocol selected by the user from the multiple protocols as the target protocol for communicating with the vehicle-mounted device.

[0047] For example, a car refrigerator may be able to communicate with the multi-protocol gateway using ZIGBEE, WiFi or Bluetooth. However, there is also a driving recorder in the car that communicates with the multi-protocol gateway using WiFi. In order to avoid bandwidth conflicts in the data channel used for data transmission, the management interface displays multiple protocols supported by the multi-protocol gateway at the same time, and manually sets ZIGBEE as the target protocol for the multi-protocol gateway to communicate with the car device, thereby achieving coordinated management among multiple car devices, avoiding conflicts when data is transmitted based on the same protocol, and improving user experience.

[0048] Based on the same idea, one or more embodiments of this specification also provide devices and apparatuses corresponding to the above methods, such as Figure 4 , Figure 5 shown.

[0049] In a second aspect, the embodiments of this specification also provide a management device for vehicle-mounted equipment, Figure 4 A schematic diagram of a management device for an on-board device provided in an embodiment of this specification, applied to a client, includes:

[0050] The communication module 401 establishes a communication connection with a multi-protocol gateway in the vehicle, wherein the client has been pre-associated with the vehicle-mounted device through the multi-protocol gateway;

[0051] The determination module 403 determines the device type of the vehicle-mounted device, and determines the communication mode between the client and the multi-protocol gateway according to the device type;

[0052] The management module 405 manages the vehicle-mounted device through the multi-protocol gateway based on the determined communication mode.

[0053] Optionally, the communication module 401 determines a communication response time corresponding to the device type, and when the communication response time is lower than a preset response value, determines that the communication mode is a short-range wireless connection; otherwise, determines that the communication mode is a long-range wireless connection.

[0054] Optionally, the management module 405 obtains and displays the status data of the vehicle-mounted device sent by the server, wherein the status data is generated by the server based on the relevant information of the vehicle-mounted device sent by the multi-protocol gateway; generates management instructions for the vehicle-mounted device based on user operations, and forwards them to the multi-protocol gateway through the server, so that the multi-protocol gateway forwards the management instructions to the vehicle-mounted device.

[0055] Optionally, the short-range wireless connection includes a Bluetooth connection, and the long-range wireless connection includes a server-side wireless switching.

[0056] Optionally, the device also includes a pre-association module 407, the client establishes a communication connection with the multi-protocol gateway; obtains the vehicle-mounted device identifier input by the user, and sends the vehicle-mounted device identifier to the multi-protocol gateway, so that the multi-protocol gateway performs consistency verification on the vehicle-mounted device identifier; after the consistency verification is passed, establishes a pre-association with the vehicle-mounted device.

[0057] Optionally, the pre-association module 407 identifies the communication protocol and / or interface of the vehicle-mounted device, and determines whether the communication protocol and / or interface of the vehicle-mounted device meets preset conditions; if so, establishes an association with the vehicle-mounted device.

[0058] Optionally, the management module 405 displays multiple protocols supported by the multi-protocol gateway in the interface of the client; and determines the protocol selected by the user from the multiple protocols as the target protocol for communicating with the vehicle-mounted device.

[0059] In a third aspect, the embodiments of this specification further provide an electronic device, Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of this specification, the device includes:

[0060] at least one processor; and,

[0061] a memory communicatively connected to the at least one processor; wherein,

[0062] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to the first aspect.

[0063] In the fourth aspect, based on the same idea, one or more embodiments of the present specification also provide a non-volatile computer storage medium corresponding to the above method, storing computer executable instructions, storing computer executable instructions, and when the computer reads the computer executable instructions in the storage medium, the instructions enable one or more processors to execute the method described in the first aspect.

[0064] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0065] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0066] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0067] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0068] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may be in the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of this specification may be in the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0069] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0070] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0071] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0072] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0073] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0074] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0075] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0076] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0077] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0078] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0079] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A method for managing vehicle-mounted equipment, applied to a client, the method include: Establishing a communication connection with a multi-protocol gateway in the vehicle, wherein the client has been pre-associated with the vehicle-mounted device through the multi-protocol gateway; Determine the device type of the vehicle-mounted device, and determine the communication mode between the client and the multi-protocol gateway according to the device type; Based on the determined communication mode, the vehicle-mounted device is managed through the multi-protocol gateway.

2. The method according to claim 1, in, Determining a communication mode between the client and the multi-protocol gateway according to the device type includes: Determine a communication response time corresponding to the device type, and when the communication response time is lower than a preset response value, determine that the communication mode is a short-range wireless connection; otherwise, determine that the communication mode is a long-range wireless connection.

3. The method according to claim 2, when the determined communication mode is a remote wireless connection, managing the vehicle-mounted device through the multi-protocol gateway, include: Acquire the status data of the vehicle-mounted device sent by the server and display it, wherein the status data is generated by the server based on the relevant information of the vehicle-mounted device sent by the multi-protocol gateway; A management instruction for the vehicle-mounted device is generated based on the user's operation, and is forwarded to the multi-protocol gateway through the server, so that the multi-protocol gateway forwards the management instruction to the vehicle-mounted device.

4. The method according to claim 2, in, The short-range wireless connection includes a Bluetooth connection, and the long-range wireless connection includes a server-side wireless switching.

5. The method according to claim 1, in, The client has been pre-associated with the vehicle-mounted device through the multi-protocol gateway, including: The client establishes a communication connection with the multi-protocol gateway; Acquire the vehicle-mounted device identification input by the user, and send the vehicle-mounted device identification to the multi-protocol gateway so that the multi-protocol gateway performs consistency verification on the vehicle-mounted device identification; After the consistency verification is passed, a pre-association with the vehicle-mounted device is established.

6. The method according to claim 5, in, Before establishing the pre-association with the vehicle-mounted device, the method further includes: Identify the communication protocol and / or interface of the vehicle-mounted device to determine whether the communication protocol and / or interface of the vehicle-mounted device meets preset conditions; If so, an association with the vehicle-mounted device is established.

7. The method according to claim 1, in, Managing the vehicle-mounted device through the multi-protocol gateway includes: Displaying multiple protocols supported by the multi-protocol gateway in the interface of the client; A protocol selected by a user from the plurality of protocols is determined as a target protocol for communicating with the in-vehicle device.

8. A management device for vehicle-mounted equipment, applied to a client, the device include: A communication module, establishing a communication connection with a multi-protocol gateway in the vehicle, wherein the client has been pre-associated with the vehicle-mounted device through the multi-protocol gateway; A determination module, which determines the device type of the vehicle-mounted device, and determines the communication mode between the client and the multi-protocol gateway according to the device type; A management module manages the vehicle-mounted device through the multi-protocol gateway based on the determined communication mode.

9. The device as described in claim 8, wherein the communication module determines the communication response time corresponding to the device type, and when the communication response time is lower than a preset response value, determines that the communication mode is a short-range wireless connection; otherwise, determines that the communication mode is a long-range wireless connection.

10. The device according to claim 9, wherein the management module obtains the status data of the vehicle-mounted device sent by the service end and displays it. in, The status data is generated by the server based on the relevant information of the vehicle-mounted device sent by the multi-protocol gateway; management instructions for the vehicle-mounted device are generated based on the user's operation, and forwarded to the multi-protocol gateway through the server, so that the multi-protocol gateway forwards the management instructions to the vehicle-mounted device.

11. The device of claim 9, wherein the short-range wireless connection comprises a Bluetooth connection, and the long-range wireless connection comprises a server-side wireless switching.

12. The device as described in claim 9 further includes a pre-association module, wherein the client establishes a communication connection with the multi-protocol gateway; obtains the vehicle-mounted device identifier input by the user, and sends the vehicle-mounted device identifier to the multi-protocol gateway so that the multi-protocol gateway performs consistency verification on the vehicle-mounted device identifier; after the consistency verification is passed, establishes a pre-association with the vehicle-mounted device.

13. In the device as described in claim 12, the pre-association module identifies the communication protocol and / or interface of the vehicle-mounted device, determines whether the communication protocol and / or interface of the vehicle-mounted device meets preset conditions; if so, establishes an association with the vehicle-mounted device.

14. The device as described in claim 8, wherein the management module displays multiple protocols supported by the multi-protocol gateway in the interface of the client; and determines the protocol selected by the user from the multiple protocols as the target protocol for communicating with the vehicle-mounted device.

15. An electronic device, include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

Images