Binding methods and apparatuses for vehicle management, devices, storage medium and product

Abstract

Binding methods and apparatuses for vehicle management, devices, a storage medium and a product, belonging to the technical field of the Internet of Things. A method is executed by a vehicle control agent device, and comprises: binding a vehicle control client device with the vehicle control agent device (201). The solution expands application scenarios of the Internet of Things, and improves the vehicle management efficiency for users.

Description

Binding method, device, equipment, storage medium and product for vehicle management Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to a binding method, device, equipment, storage medium and product for vehicle management. Background Art

[0002] With the continuous development of Internet of Things (IoT) technology, more and more IoT devices have brought great convenience to users' production and life in many fields such as smart homes and industrial production.

[0003] In related technologies, vehicles can be remotely controlled using mobile devices such as mobile phones. Specifically, the vehicle's onboard equipment and the user's mobile terminal are simultaneously connected to a cloud server and bound to the cloud server. Subsequently, the mobile terminal can send control commands to the onboard equipment through the cloud server.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a binding method, apparatus, device, storage medium, and product for vehicle management. The technical solution is as follows:

[0006] In one aspect, an embodiment of the present application provides a binding method for vehicle management, the method being executed by a vehicle control agent device, the method comprising:

[0007] Bind the vehicle control client device to the vehicle control proxy device.

[0008] In one aspect, an embodiment of the present application provides a binding method for vehicle management, the method being executed by a vehicle control client device, the method comprising:

[0009] Bind the vehicle control client device to the vehicle control proxy device.

[0010] On the other hand, an embodiment of the present application provides a binding device for vehicle management, the device comprising:

[0011] The binding module is used to bind the vehicle control client device to the vehicle control proxy device.

[0012] On the other hand, an embodiment of the present application provides a binding device for vehicle management, the device comprising:

[0013] The binding module is used to bind the vehicle control client device to the vehicle control proxy device.

[0014] On the other hand, an embodiment of the present application provides a computer device, wherein the computer device is implemented as an information reporting device, and the computer device includes a processor, a memory, and a transceiver;

[0015] The memory stores a computer program, and the processor executes the computer program so that the computer device implements the above-mentioned binding method for vehicle management.

[0016] On the other hand, an embodiment of the present application provides a computer device, which includes a processor, a memory and a transceiver, wherein the memory stores a computer program, and the computer program is used to be executed by the processor to implement the above-mentioned binding method for vehicle management.

[0017] On the other hand, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is loaded and executed by a processor to implement the above-mentioned binding method for vehicle management.

[0018] On the other hand, the present application also provides a chip, which includes a circuit structure, and the chip is used to run in a computer device so that the computer device executes the above-mentioned binding method for vehicle management.

[0019] In another aspect, the present application provides a computer program product, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the above-described binding method for vehicle management.

[0020] On the other hand, the present application provides a computer program, which is executed by a processor of a computer device to implement the above-mentioned binding method for vehicle management.

[0021] Through the technical solution provided in the embodiment of the present application, the vehicle control proxy device can be pre-bound to the vehicle control client device, so that the vehicle control proxy device can provide a proxy service, which can enable the vehicle control client device in the Internet of Things system to manage the vehicle, thereby expanding the interaction method between the Internet of Things device and the vehicle, expanding the application scenarios of the Internet of Things, and improving the user's management efficiency of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] FIG1 is a schematic diagram of a network architecture of the Internet of Things provided by one embodiment of the present application;

[0023] FIG2 is a flowchart of a binding method for vehicle management provided by one embodiment of the present application;

[0024] FIG3 is a flowchart of a binding method for vehicle management provided by one embodiment of the present application;

[0025] FIG4 is a flowchart of a binding process for vehicle management provided by one embodiment of the present application;

[0026] FIG5 is a flow chart of a binding method for vehicle management involved in the present application;

[0027] FIG6 is a flow chart of a binding method for vehicle management involved in the present application;

[0028] FIG7 is a block diagram of a binding device for vehicle management provided by one embodiment of the present application;

[0029] FIG8 is a block diagram of a binding device for vehicle management provided by one embodiment of the present application;

[0030] FIG9 is a schematic diagram of the structure of a computer device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0031] Please refer to Figure 1, which shows a schematic diagram of the network architecture of the Internet of Things provided by one embodiment of the present application. The network architecture of the Internet of Things may include: Internet of Things devices 110 (shown in Figure 1 as Internet of Things devices 110a, 110b, 110c, and 110d), proxy devices 120 (shown in Figure 1 as proxy devices 120a and 120b), and vehicles 130 (shown in Figure 1 as vehicles 130a, 130b, and 130c); optionally, the network architecture may further include a bridge device 140; optionally, the network architecture may further include a cloud server 150.

[0032] The IoT device 110 may refer to a device in the IoT that is used to provide client functions or server functions corresponding to the IoT protocol.

[0033] For example, the IoT device 110 may be a smart home device, such as a smart TV, a smart speaker, a smart switch, a smart lamp, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a sweeping robot, and the like.

[0034] Alternatively, the IoT device 110 may be an industrial production equipment, such as a lathe, an industrial robot, a solar panel, a wind turbine, and the like.

[0035] Alternatively, the IoT device 110 may be a commercial service device, such as an unmanned vending machine, etc.

[0036] Alternatively, the IoT device 110 may be a sensing device, such as a surveillance camera, an infrared sensor, a sound sensor, a temperature sensor, and the like.

[0037] In one possible implementation, the proxy device 120 is a user-side terminal device, such as a smartphone, tablet computer, smartwatch, or a personal computer, such as a desktop computer, laptop computer, or personal workstation.

[0038] In another possible implementation, the proxy device 120 refers to a client entity (which may be a virtual entity) running on a terminal device. For example, the proxy device 120 may be an application (APP) running in the terminal device for accessing, controlling, and managing IoT devices.

[0039] The vehicle 130 may be a vehicle / on-board device that has the function of communicating with the proxy device 120 . For example, the vehicle 130 may be an on-board device (such as a vehicle computer device) and the like.

[0040] The proxy device 120 may establish a connection with the vehicle 130 through the cloud server 150 .

[0041] The bridge device 140 is used to enable interaction between two devices supporting different IoT protocols. The bridge device 140 provides information conversion and transmission services between IoT devices 110 supporting different IoT protocols, or between an IoT device 110 supporting different IoT protocols and a proxy device 120.

[0042] The bridge device 140 may be a device dedicated to bridging, or the bridge device 140 may be an intelligent device with a bridging function, such as a gateway or a router.

[0043] The cloud server 150 is used to provide a connection service between the IoT device 110 and other devices outside the IoT ecosystem (such as the aforementioned proxy device 120). The cloud server 150 can be a cloud platform server of the IoT ecosystem.

[0044] The proxy device 120 may also directly establish a connection with the IoT device 110 .

[0045] Alternatively, the proxy device 120 may also establish a connection with the IoT device 110 through the cloud server 150 .

[0046] Alternatively, the proxy device 120 may also establish a connection with the IoT device 110 through the bridge device 140 .

[0047] In the embodiment of the present application, the IoT device 110, proxy device 120, and bridge device 140 may be electronic devices that comply with the same or different IoT protocols. For example, they may be electronic devices that comply with the Matter protocol under the Connectivity Standards Alliance (CSA).

[0048] In FIG1 , when the IoT device 110 a and the IoT device 110 c support the same protocol specification, a secure connection may be established between the IoT device 110 a and the IoT device 110 c , for example, a secure connection may be established based on the Matter specification.

[0049] When the IoT device 110 b and the IoT device 110 d support different protocol specifications, for example, the IoT device 110 b is a Zigbee device and the IoT device 110 d is a Matter device, the IoT device 110 b and the IoT device 110 d may be connected via the bridge device 140 .

[0050] 1) Matter DNS-SD Discovery

[0051] (1) Network node discovery

[0052] Assume that the device on Wi-Fi uses the 48-bit MAC address 'B75AFB458ECD' and its domain name is 'DD200C20D25AE5F7' as the instance name of the service. The DNS-SD record can be set as follows:

[0053] dns-sd-R DD200C20D25AE5F7_matterc._udp,_S3,_L840,_CM.11111D=840CM=2

[0054] Short identification codes can be filtered by '_S3' subtype and algorithmically filtered by 'D=840'.

[0055] Long identification codes are filtered by the '_L840' subtype and directly filtered by 'D=840'.

[0056] When the administrator opens the network configuration window, the access node is now in the network configuration state and can be queried through 'CM=2'.

[0057] If the node is found to be performing initial network configuration, rather than subsequent additional network configuration, it will issue 'CM=1'.

[0058] The network configuration node can discover all available network access nodes waiting for network configuration:

[0059] dns-sd-B_matterc._udp

[0060] The network configuration node can use the short identification code 3 to find the network access node waiting for network configuration:

[0061] dns-sd-B_matterc._udp,_S3

[0062] The network configuration node can use the long identification code 840 to find the network access node waiting for network configuration:

[0063] dns-sd-B_matterc._udp,_L840

[0064] The network configuration node can use the Vendor ID 123 to discover the network access node waiting for network configuration:

[0065] dns-sd-B_matterc._udp,_V123

[0066] The network configuration node can discover all network access nodes in the network configuration mode:

[0067] dns-sd-B_matterc._udp,_CM

[0068] The distribution node can discover the Matter node using device type 81:

[0069] dns-sd-B_matterc._udp,_T81

[0070] (2) Operation discovery

[0071] Consider a device on Wi-Fi that uses the 48-bit device MAC address of B75AFB458ECD as its hostname. The DNS-SD record can be set as follows:

[0072] dns-sd-R 87E1B004E235A130-8FC7772401CD0696_matter._tcp.22222

[0073] The port number 22222 is given here as an example only. One benefit of using DNS-SD is that the service is not restricted to using a single, predetermined, well-known port. This means that multiple instances of the Matter node control service can run simultaneously on the same device, listening on different ports. The Matter controller discovers this port and IPv6 address at runtime.

[0074] The Matter controller can discover the current IPv6 address and port of a known Matter node:

[0075] dns-sd-L 87E1B004E235A130-8FC7772401CD0696_matter._tcp

[0076] 87E1B004E235A130-8FC7772401CD0696._matter._tcp.local.can be reached at

[0077] B75AFB458ECD.local.:22222

[0078] dns-sd-Gv6 B75AFB458ECD.local

[0079] fe80::f515:576f:9783:3f30

[0080] (3) Distribution network node discovery

[0081] Assume that the device on Wi-Fi uses the 48-bit MAC address 'B75AFB458ECD'. The DNS-SD record can be set as follows:

[0082] dns-sd-R DD200C20D25AE5F7_matterd._udp,_V123,_T35.33333

[0083] VP=123+456DT=35DN="LivingRoom TV"

[0084] The above DNS-SD message includes the following functions:

[0085] The Vendor ID is '123' and the Product ID is '456';

[0086] The device type is '35', a media player (device type ID is 0x0023);

[0087] The device name is 'Living Room TV'.

[0088] A network access node can discover all network distribution nodes:

[0089] dns-sd-B_matterd._udp

[0090] A network access node can discover a distribution node with device type 35:

[0091] dns-sd-B_matterd._udp,_T35

[0092] A network access node can discover the network distribution node with Vendor ID 123:

[0093] dns-sd-B_matterd._udp,_V123

[0094] 2) Car Control Home Binding

[0095] The binding part mainly completes the binding between IOTClient and IOTAgent. Only after binding, IOTClient can access the smart home system through IOTAgent. Before the binding process, IOTClient has already established a communication channel with IOTAgent. The binding process is as follows:

[0096] ①The user starts the binding process on the mobile phone;

[0097] ②IOTAgent discovers the identifier of the smarthomeClient cluster of the IOTClient and determines whether it supports access to smart home capabilities;

[0098] ③Return the protocol version supported by IOTClient: version id;

[0099] ④[optional]IOTAgent obtains the device list supported by IOTClient: supporteddevicetype;

[0100] ⑤Return the list of supported controllable devices;

[0101] ⑥ The user chooses temporary binding or long-term binding;

[0102] ⑦ If it is a long-term binding, the binding relationship needs to be set in the binding table;

[0103] ⑧Notify IOTClient of the binding type;

[0104] ⑨IOTClient sets the binding type to the smarthomeClient cluster.

[0105] Please refer to FIG2 , which shows a flowchart of a binding method for vehicle management provided by one embodiment of the present application. The method may be performed by a vehicle control agent device. For example, the vehicle control agent device may be the agent device 120 in the network architecture shown in FIG1 . The method may include the following steps:

[0106] Step 201: Bind the vehicle control client device to the vehicle control proxy device.

[0107] In the embodiment of the present application, the vehicle control proxy device binds the vehicle control client device to the vehicle control proxy device, which may be the case where the vehicle control proxy device binds the vehicle control client device, the vehicle control proxy device, and the first vehicle.

[0108] In other words, the vehicle control proxy device binding the vehicle control client device to the vehicle control proxy device may refer to binding the vehicle control client device to the first vehicle in the vehicle control proxy device. For example, during the binding process of the vehicle control client device to the vehicle control proxy device, the vehicle control proxy device may locally establish a binding entry between the vehicle control client device and the first vehicle.

[0109] The vehicle control agent device may correspond to at least one vehicle, and the at least one vehicle includes the first vehicle.

[0110] The vehicle control client device may be an IoT device, such as the IoT device 110 in the network architecture shown in FIG. 1 .

[0111] For example, the above-mentioned vehicle control client device can be an IoT device such as a smart TV or a smart refrigerator.

[0112] The binding of the vehicle control client device and the vehicle control proxy device can be used to enable the vehicle control proxy device to provide a proxy service for managing the first vehicle to the vehicle control client device.

[0113] For example, the above-mentioned vehicle control proxy device can establish connections with the vehicle control client device and the first vehicle respectively. When the user needs to manage the first vehicle through the vehicle control client device, the vehicle control proxy device can act as a proxy between the vehicle control client device and the first vehicle, and manage the first vehicle according to the management request of the vehicle control client device for the first vehicle.

[0114] That is, the above management request is sent by the vehicle control client device to the vehicle control agent device, and then the vehicle control agent device provides a service for managing the first vehicle according to the management request, thereby realizing the vehicle management function through the Internet of Things device.

[0115] In some embodiments, the management includes at least one of the following:

[0116] controlling the first vehicle;

[0117] Checking status information of the first vehicle;

[0118] Subscribe to the status information of the first vehicle.

[0119] The control of the first vehicle may be performed by the control vehicle proxy device sending a control instruction to the first vehicle according to the management request sent by the control vehicle client device, so that the first vehicle executes the control instruction, thereby achieving control over the first vehicle.

[0120] In some embodiments, the above control instructions may be instructions such as locking / unlocking the vehicle, opening / closing windows, turning on / off air conditioning, turning on / off seat heating, etc.

[0121] The checking of the status information of the first vehicle may refer to the controlling vehicle proxy device returning the status information of the first vehicle to the controlling vehicle client device once according to the management request sent by the controlling vehicle client device.

[0122] The above-mentioned subscription to the status information of the first vehicle may refer to the controlling vehicle proxy device returning the status information of the first vehicle to the vehicle controlling client device according to the management request sent by the vehicle controlling client device, and subsequently notifying the vehicle controlling client device of the updated part of the status information of the first vehicle when it is detected that the status information of the first vehicle is updated.

[0123] In some embodiments, the status information of the first vehicle may be real-time status information obtained from the first vehicle when the vehicle control agent receives a management request; or, the status information of the first vehicle may be status information obtained or subscribed to in advance from the first vehicle by the vehicle control agent and stored locally in the vehicle control agent.

[0124] The above-mentioned status information of the first vehicle can indicate various states of the first vehicle, such as the locked / unlocked state, the open / closed state of the windows, the open / closed state of the air conditioner, the remaining power / remaining fuel, the temperature inside the vehicle, etc.

[0125] In some embodiments, in addition to controlling the first vehicle, viewing and subscribing to the status information of the first vehicle, other management methods may be used, such as canceling the subscription to the status information of the first vehicle, etc. The various embodiments of this application do not limit the above management methods.

[0126] In some embodiments, in order to support the vehicle control proxy device to provide a proxy service for managing the first vehicle to the vehicle control client device, the first vehicle can be bound to the vehicle control client device in advance in the vehicle control proxy device, and / or the first vehicle can be bound to the vehicle control proxy device in the vehicle control client device.

[0127] To sum up, in the embodiment of the present application, the vehicle control proxy device can be pre-bound to the vehicle control client device, so that the vehicle control proxy device can provide a proxy service, which can enable the vehicle control client device in the Internet of Things system to manage the vehicle, thereby expanding the interaction method between the Internet of Things device and the vehicle, expanding the application scenarios of the Internet of Things, and improving the user's management efficiency of the vehicle.

[0128] Please refer to FIG3 , which shows a flowchart of a binding method for vehicle management provided by one embodiment of the present application. The method may be executed by a vehicle control client device. For example, the vehicle control client device may be the IoT device 110 in the network architecture shown in FIG1 . The method may include the following steps:

[0129] Step 301: Bind the vehicle control client device to the vehicle control proxy device.

[0130] In the embodiment of the present application, the vehicle control client device binds the vehicle control client device to the vehicle control proxy device, which may be to bind the vehicle control client device, the vehicle control proxy device and the first vehicle.

[0131] Alternatively, the vehicle control client device binding the vehicle control client device with the vehicle control proxy device may refer to binding the vehicle control proxy device with the first vehicle in the vehicle control client device. For example, during the binding process of the vehicle control client device with the vehicle control proxy device, the vehicle control client device may locally establish a binding entry between the vehicle control proxy device and the first vehicle.

[0132] The above-mentioned binding of the vehicle control client device and the vehicle control proxy device can be used to support the vehicle control client device to use the vehicle control proxy device as a proxy to manage the first vehicle through the vehicle control proxy device.

[0133] To sum up, in the embodiment of the present application, the vehicle control client device can be pre-bound to the vehicle control client device, so that the vehicle control proxy device can provide a proxy service, which can enable the vehicle control client device in the Internet of Things system to manage the vehicle, thereby expanding the interaction method between the Internet of Things device and the vehicle, expanding the application scenarios of users managing vehicles, and improving the efficiency of users managing vehicles.

[0134] Please refer to FIG4 , which shows a flowchart of a binding method for vehicle management provided by one embodiment of the present application. The method can be interactively executed by a vehicle control proxy device and a vehicle control client device. The vehicle control proxy device and the vehicle control client device can be the proxy device 120 and the IoT device 110 in the network architecture shown in FIG1 , respectively. The method can include the following steps:

[0135] Step 401: The vehicle control proxy device discovers the vehicle control client device.

[0136] In some embodiments, the process of the vehicle control proxy device discovering the vehicle control client device may include:

[0137] When the vehicle control proxy device is in an IP network environment, the vehicle control client device is discovered using the DNS-SD discovery method.

[0138] Among them, when the vehicle control proxy device is connected to the IP network, the vehicle control client device in the IP network can be discovered through DNS discovery.

[0139] In some embodiments, when the vehicle control proxy device is in an IP network environment, the vehicle control client device is discovered using a DNS-SD discovery method, including:

[0140] Obtain the DNS-SD record of the vehicle control client device, which contains the identification information of the vehicle control client device;

[0141] Obtain the address and port number of the vehicle control client device based on the DNS-SD record.

[0142] Correspondingly, the vehicle control client device also needs to pre-register the above DNS-SD record. Specifically, the vehicle control client device can register the DNS-SD record when it is in an IP network environment; the DNS-SD record is used by the vehicle control proxy device to discover the vehicle control client device.

[0143] Among them, the identification information of the vehicle control client device contained in the above-mentioned DNS-SD record can be the ID of the vehicle control client device in the IP network, or the DNS-SD record can also include other identifications of the vehicle control client device, such as the identification ID in the Internet of Things.

[0144] In some embodiments, the above-mentioned DNS-SD record may also include the client type of the vehicle control client device (the client type is used to indicate that the vehicle control client device has the function of managing the vehicle, that is, the vehicle control client) or capabilities (for example, the client device has a touch screen to support touch interaction, and / or, the client device supports voice interaction, etc.), so that the vehicle control agent device can accurately discover the vehicle control client device that has the function of managing the vehicle.

[0145] In some embodiments, discovering the vehicle control client device includes:

[0146] Discover the vehicle control client device via Bluetooth Low Energy (BLE).

[0147] In an embodiment of the present application, when the vehicle control proxy device is not connected to the IP network, the vehicle control proxy device can discover surrounding vehicle control client devices through BLE.

[0148] Alternatively, when the vehicle control proxy device is connected to the IP network, it can also discover the surrounding vehicle control client devices that are not connected to the IP network where the vehicle control proxy device is located through BLE.

[0149] In some embodiments, the method further comprises:

[0150] The vehicle control client device can send BLE broadcasts; BLE broadcasts are used by the vehicle control proxy device to discover the vehicle control client device.

[0151] Accordingly, when the vehicle control agent device discovers the vehicle control client device via Bluetooth Low Energy (BLE), it can perform the following steps:

[0152] Receive BLE broadcasts sent by the vehicle control client device;

[0153] Get the information of the vehicle control client device based on BLE broadcast.

[0154] In the above embodiment, the vehicle control client device can actively send a BLE broadcast to inform the surrounding potential vehicle control proxy devices. The vehicle control client device is a client device with the function of managing the vehicle. Accordingly, the vehicle control proxy device that receives the BLE broadcast can discover the vehicle control client device and obtain the information of the vehicle control client device carried in the BLE broadcast.

[0155] In some other embodiments, the method further comprises:

[0156] The vehicle control proxy device sends a BLE broadcast; the BLE broadcast is used to discover the vehicle control client device; accordingly, after receiving the BLE broadcast, the vehicle control client device returns the vehicle control client device information to the vehicle control proxy device via BLE, so that the vehicle control proxy device can discover the vehicle control client device.

[0157] In some embodiments, the BLE broadcast includes at least one of the following information:

[0158] Identification information of the vehicle control client device;

[0159] Network information of the vehicle control client device.

[0160] The identification information of the vehicle control client device may be a Bluetooth identification of the vehicle control client device, or an Internet of Things identification, etc.

[0161] For a Wi-Fi network, the network information of the vehicle control client device may be the Wi-Fi network SSID;

[0162] For Thread networks, the network information of the vehicle control client device can be an extended PAN ID;

[0163] For an Ethernet network, the network information of the vehicle control client device may be the network interface instance name of the operating system.

[0164] Step 402: The vehicle control proxy device establishes a connection with the vehicle control client device.

[0165] In some embodiments, after the vehicle control proxy device discovers the vehicle control client device and obtains information about the vehicle control client device, a connection may be established between the vehicle control proxy device and the vehicle control client device, which may be a data channel established between the vehicle control proxy device and the vehicle control client device.

[0166] For example, a secure connection and data channel can be established between the vehicle control agent device and the vehicle control client device based on the Matter specification.

[0167] For another example, a secure connection and data channel can be established between the vehicle control agent device and the vehicle control client device based on the IP protocol.

[0168] For example, a secure connection and data channel can be established between the vehicle control agent device and the vehicle control client device based on BLE.

[0169] In step 403 , the vehicle control proxy device binds the vehicle control client device to the vehicle control proxy device; and the vehicle control client device binds the vehicle control client device to the vehicle control proxy device.

[0170] In an embodiment of the present application, after the vehicle control proxy device discovers the vehicle control client device, it can prompt the user that a bindable vehicle control client device has been found, so that the user can confirm whether to initiate binding. If the user confirms to initiate binding, the vehicle control proxy device can bind the vehicle control client device to the vehicle control proxy device.

[0171] The step of the user confirming whether to initiate binding may be performed before step 402 or before step 403 .

[0172] In some embodiments, the car control agent device includes a car agent function cluster (CarAgent Cluster); the car agent function cluster indicates a car control client bound to the car control agent device.

[0173] In an embodiment of the present application, a cluster may be set in the vehicle control proxy device to store and maintain the vehicle control client bound to the vehicle control proxy device.

[0174] In some embodiments, the vehicle control proxy device may also indicate the vehicle control client bound to the vehicle control proxy device through other means other than clustering (such as a binding relationship table).

[0175] Among them, one vehicle control proxy device can be bound to multiple vehicle control clients, and each vehicle control client can correspond to one vehicle control client device.

[0176] In some embodiments, the vehicle proxy function cluster includes information about a vehicle control client bound to the vehicle control proxy device; wherein the information about the vehicle control client bound to the vehicle control proxy device includes at least one of the following information:

[0177] Identification information of the vehicle control client bound to the vehicle control proxy device;

[0178] Information about the binding type of the vehicle control client bound to the vehicle control proxy device;

[0179] The identification information of the vehicle bound to the vehicle control client device.

[0180] In an embodiment of the present application, in addition to the above information, the information of the vehicle control client bound to the vehicle control proxy device may also include other information, such as the name, manufacturer, and software version of the vehicle control client bound to the vehicle control proxy device, as well as the name, manufacturer, software version, and other information of the vehicle bound to the vehicle control client device.

[0181] In some embodiments, the car control client device includes a car client function cluster (CarClient Cluster);

[0182] The vehicle client function cluster indicates the vehicle control agent bound to the vehicle control client device.

[0183] In the embodiment of the present application, a cluster may also be set in the vehicle control client device to store and maintain the vehicle control agent bound to the vehicle control client device.

[0184] In some embodiments, the vehicle control client device may also indicate the vehicle control agent bound to the vehicle control client device through other means other than clustering (such as a binding relationship table).

[0185] In some embodiments, the vehicle client function cluster includes information about the vehicle bound to the vehicle control client device;

[0186] The information of the vehicle bound to the vehicle control client device includes at least one of the following information:

[0187] The identification information of the vehicle bound to the vehicle control client device; the name of the vehicle bound to the vehicle control client device; the identification information of the vehicle control agent bound to the vehicle.

[0188] In an embodiment of the present application, in addition to the above information, the information of the vehicle bound to the vehicle control client device may also include other information, such as the name, manufacturer, software version of the vehicle bound to the vehicle control client device, and the name, manufacturer, software version and other information of the vehicle control agent bound to the vehicle.

[0189] In some embodiments, the process of binding the vehicle control client device to the vehicle control proxy device may include:

[0190] The vehicle control proxy device sends a vehicle binding request to the vehicle control client device; the vehicle binding request includes identification information of the vehicle control proxy device and identification information of the first vehicle; the vehicle control client device receives the vehicle binding request sent by the vehicle control proxy device; the vehicle control client device adds the identification information of the vehicle control proxy device and the identification information of the first vehicle to the information of the bound vehicle corresponding to the first vehicle; the vehicle control client device returns a vehicle binding response to the vehicle control proxy device; the vehicle binding response includes the identification information of the first vehicle and the binding status; the vehicle control proxy device receives the vehicle binding response returned by the vehicle control client device;

[0191] When the binding state is successful, the vehicle control proxy device adds information of the vehicle control client corresponding to the vehicle control client device and identification information of the first vehicle in the vehicle proxy function cluster.

[0192] In the embodiment of the present application, the vehicle control proxy device initiates a binding request and exchanges binding information with the vehicle control client device, so that both store the binding relationship between the vehicle control proxy device, the vehicle control client device and the first vehicle in their respective clusters.

[0193] In some embodiments, the vehicle control client device adds the identification information of the vehicle control proxy device and the identification information of the first vehicle to the information of the bound vehicle corresponding to the first vehicle, including:

[0194] In a case where the vehicle client function cluster already includes information of a bound vehicle corresponding to the first vehicle, adding identification information of the vehicle control proxy device to the information of the bound vehicle corresponding to the first vehicle;

[0195] When the vehicle client function cluster does not include the bound vehicle information corresponding to the first vehicle, the bound vehicle information corresponding to the first vehicle is added to the vehicle client function cluster according to the identification information of the vehicle control agent device and the identification information of the first vehicle.

[0196] In an embodiment of the present application, in the vehicle client function cluster, one vehicle can be bound to multiple vehicle control agents. When the vehicle control client device receives a vehicle binding request, if it is found that there is already information of a bound vehicle corresponding to the first vehicle, there is no need to establish new information of the bound vehicle, and the identification information of the vehicle control agent device can be directly written into the information of the bound vehicle.

[0197] In other embodiments, if the vehicle client functional cluster already contains bound vehicle information corresponding to the first vehicle, the vehicle control client device may also add the bound vehicle information corresponding to the first vehicle to the vehicle client functional cluster based on the identification information of the vehicle control proxy device and the identification information of the first vehicle. In other words, in the vehicle client functional cluster, upon receiving a vehicle binding request, if the vehicle control client device finds that bound vehicle information corresponding to the first vehicle already exists, it may create a new bound vehicle information and write the identification information of the vehicle control proxy device into the newly created bound vehicle information.

[0198] In some embodiments, the vehicle binding request further includes the name of the first vehicle; the method further includes:

[0199] When the vehicle client function cluster already includes information about the bound vehicle corresponding to the first vehicle, if the first name of the first vehicle included in the vehicle binding request is inconsistent with the second name of the first vehicle included in the information about the bound vehicle corresponding to the first vehicle, the second name will be updated to the first name.

[0200] In an embodiment of the present application, each vehicle in the vehicle client function cluster has only a unique name. When the vehicle control client device receives a vehicle binding request, if it is found that the name corresponding to the first vehicle in the bound vehicle information corresponding to the first vehicle is different from the name of the first vehicle in the vehicle binding request, then the name corresponding to the first vehicle in the bound vehicle information corresponding to the first vehicle is updated according to the name of the vehicle in the above vehicle binding request.

[0201] In some embodiments, the method further includes: the vehicle control proxy device reading the information of the bound vehicle from the vehicle control client device.

[0202] In an embodiment of the present application, the vehicle control proxy device may also query the vehicle control client device for which vehicles it has bound, so that the vehicle bound to the vehicle control client device may be selected from the vehicles corresponding to the vehicle control proxy device.

[0203] For example, the above process of selecting a vehicle to be bound to the vehicle control client device can be performed by the user; or, the above process of selecting a vehicle to be bound to the vehicle control client device can be performed by the vehicle control proxy device according to a preset selection rule, for example, the vehicle control proxy device gives priority to vehicles that are bound or not bound to the vehicle control client device, and establishes a binding relationship between the vehicle control proxy device, the vehicle control client device and the vehicle.

[0204] In some embodiments, the method further includes: setting vehicle control authority for the vehicle control client device in the vehicle control proxy device; the vehicle control authority is the authority to manage the vehicle.

[0205] The vehicle control agent device may establish a binding relationship among the vehicle control agent device, the vehicle control client device, and the vehicle, and may also set vehicle control permissions of the vehicle control client device.

[0206] Optionally, the vehicle control authority set above may be the management authority of the vehicle control client device over the currently bound vehicle; or, the vehicle control authority set above may be the management authority of the vehicle control client device over all vehicles.

[0207] Example 1:

[0208] (1) The CarAgent Cluster is implemented on the mobile phone, and the bound CarClient (car control client) is recorded.

[0209] The car agent feature set includes the following attributes, which are defined in Table 1:

[0210] Table 1

[0211] The clientInfo structure is defined as shown in Table 2 below:

[0212] Table 2

[0213] Among them, ClientType is the binding type of the client, True is long-term binding, and False is temporary binding.

[0214] (2) Implement the CarClient Cluster function set on the smart home device to record the Car and CarAgent bound to the CarClient.

[0215] The car client feature set includes the following attributes, which are defined in Table 3:

[0216] Table 3

[0217] The carInfo structure is defined as shown in Table 4 below:

[0218] Table 4

[0219] The car client function set includes the following commands, which are defined in Table 5:

[0220] Table 5

[0221] The bindCarReq method is used by CarAgent to bind a car to CarClient. The bound car is identified by CarID. The parameters are defined in Table 6 below:

[0222] Table 6

[0223] The bindCarResp parameter definition is shown in Table 7 below:

[0224] Table 7

[0225] Among them, Status is the binding status, True means binding is successful, and False means binding fails.

[0226] (3) Binding discovery

[0227] Binding discovery: CarAgent actively discovers CarClient in the following ways:

[0228] When the CarAgent terminal is in an IP network environment, the DNS-SD discovery method can be used to discover the CarClient in the network.

[0229] When the CarAgent terminal needs to discover the CarClient outside the IP network, the BLE discovery method can be used.

[0230] ① DNS-SD discovery

[0231] The DNS-SD service name used to discover CarClient is: _carclient._matter._tcp

[0232] Devices with CarClient capabilities should register with the DNS-SD discovery service. The service instance name is the device ID in the smart home network. For example, if the device ID is FC7772401CD0696, the service instance name should also be FC7772401CD0696. The service instance name should be unique within the home network.

[0233] The host name of CarClient is the MAC address of the device. For example, a device with a 48-bit MAC address of B75AFB458ECD and a device ID of FC7772401CD0696 should register the following DNS-SD record:

[0234] dns-sd-R FC7772401CD0696_carclient._matter._tcp.11111

[0235] The port number 11111 is only an example.

[0236] CarAgent can discover the address and port number of the CarClient device through DNS-SD:

[0237] dns-sd-L FC7772401CD0696_carclient._matter._tcp FC7772401CD0696._carclient._matter._tcp.local.can be reached at B75AFB458ECD.local.:11111

[0238] dns-sd-Gv6 B75AFB458ECD.local fe80::f515:576f:9783:3f30

[0239] ②BLE discovery

[0240] When the CarAgent or CarClient terminal is not connected to any network or the user wants to discover the CarAgent that is not in the current network, the user can actively choose to use BLE to discover it.

[0241] BLE discovery is initiated by CarClient, and CarAgent is in listening mode. The BLE discovery broadcast should contain the following information: ClientID, NetworkInfo (network information where CarClient is located), as shown in Table 8:

[0242] Table 8

[0243] Among them, NetworkID is the network identifier, which is defined as follows based on network characteristics:

[0244] For a Wi-Fi network, this is the Wi-Fi network SSID;

[0245] For Thread networks, this is the extended PAN ID.

[0246] For Ethernet networks, this is the name of the operating system's network interface instance;

[0247] After receiving the discovery information broadcast by CarClient, CarAgent can choose to join the network where CarClient is located or directly establish a BLE connection.

[0248] Please refer to Figure 5, which shows a flowchart of a vehicle management binding process involved in this application. In this embodiment, a user can use the CarAgent implemented on a mobile phone to discover the CarClient implemented on a smart TV in a home network and initiate vehicle control binding. The above process may include:

[0249] Discovery Process:

[0250] In step S1, the phone enters the home network, where the CarAgent discovers the CarClient using DNS-SD. Simultaneously, the phone monitors BLE broadcasts to discover CarClients that are not on the home network. (At this point, the phone may also receive BLE broadcasts from CarClients on the home network, but these devices can be filtered out using the NetworkID.) The user can then switch to another target network for DNS-SD discovery.

[0251] S2, CarClient provides address information through the DNS-SD service and makes a discovery response.

[0252] S3: When an unbound CarClient is found, the CarAgent prompts the user, and the user confirms on the mobile phone whether binding is required.

[0253] S4, both parties establish a data channel.

[0254] Binding process:

[0255] S5: CarAgent sends a bindCar Request to CarClient, which includes the CarID, the car name, and the CarAgent ID. If the CarAgent is associated with multiple cars, only one of them is bound at a time, and the binding is performed in multiple steps.

[0256] S6, CarClient adds the car and the car control agent to the boundCars attribute.

[0257] S7 returns bindCar Response, which includes CarID, CarClient ID, and binding status.

[0258] S8, CarAgent adds the CarClient information to the boundClients attribute. If the corresponding Client already exists in the boundClients attribute list, the CarID of the bound car is added to the corresponding table item.

[0259] S9, users can set the car control permission for the CarClient on CarAgent. The default permission is 0.

[0260] Vehicle control process:

[0261] S10, after binding, CarClient can control the car through CarAgent.

[0262] Example 2:

[0263] Compared with the above embodiment 1, the difference in clustering lies in the carInfo structure in the car client function set CarClient Cluster on the smart home device, where the carInfo structure is defined as shown in Table 9 below:

[0264] Table 9

[0265] Please refer to Figure 6, which shows a flowchart of a vehicle management binding process involved in this application. In this embodiment, a user can use the CarAgent implemented on a mobile phone to discover the CarClient implemented on a smart TV in a home network and initiate vehicle control binding. The process may include:

[0266] Discovery Process:

[0267] In step S1, the phone enters the home network, where the CarAgent discovers the CarClient using DNS-SD. Simultaneously, the phone monitors BLE broadcasts to discover CarClients that are not on the home network. (At this point, the phone may also receive BLE broadcasts from CarClients on the home network, but these devices can be filtered out using the NetworkID.) The user can then switch to another target network for DNS-SD discovery.

[0268] S2, CarClient provides address information through the DNS-SD service and makes a discovery response.

[0269] S3: When an unbound CarClient is found, the CarAgent prompts the user, and the user confirms on the mobile phone whether binding is required.

[0270] S4, both parties establish a data channel.

[0271] Binding process:

[0272] S5, CarAgent queries the cars bound to CarClient by reading the boundCars attribute.

[0273] S6: CarClient returns the query result, which includes the car's CarID, car name, and CarAgent ID.

[0274] S7, the user chooses to bind to the CarID returned in the previous step, or a new CarID or CarName.

[0275] S8: The user can set the car control permission for the CarClient on the CarAgent. The default permission is 0.

[0276] S9: CarAgent sends a bindCar Request to CarClient, containing the CarID, the car's name, and the CarAgent ID. If the CarID already exists in the boundCars list, executing this command should be considered adding a CarAgent to the entry corresponding to the CarID. If the CarName differs from the corresponding name in the current boundCars list, it should be considered modifying the displayed car name.

[0277] S10, CarClient adds the car and the car control agent to the boundCars attribute.

[0278] S11 returns bindCar Response, which includes CarID, CarClient ID, and binding status.

[0279] S12, CarAgent adds the CarClient information to the boundClients attribute. If the corresponding Client already exists in the boundClients attribute list, the CarID of the bound car is added to the corresponding table item.

[0280] Vehicle control process:

[0281] S13: After binding, CarClient can control the car through CarAgent.

[0282] Please refer to Figure 7, which shows a block diagram of a binding device for vehicle management provided by one embodiment of the present application. The binding device 700 for vehicle management has the function of implementing the method shown in Figure 2 or Figure 4 above, which is performed by the vehicle control agent device. As shown in Figure 7, the device may include:

[0283] The binding module 701 is used to bind the vehicle control client device to the vehicle control proxy device.

[0284] In some embodiments, the binding module 701 is used to bind the vehicle control client device, the vehicle control proxy device and the first vehicle.

[0285] In some embodiments, the vehicle control agent device includes a vehicle agent function cluster;

[0286] The vehicle proxy function cluster indicates a vehicle control client bound to the vehicle control proxy device.

[0287] In some embodiments, the vehicle proxy function cluster includes information of a vehicle control client bound to the vehicle control proxy device;

[0288] The information of the vehicle control client bound to the vehicle control proxy device includes at least one of the following information:

[0289] Identification information of the vehicle control client bound to the vehicle control proxy device;

[0290] Information on the binding type of the vehicle control client bound to the vehicle control proxy device;

[0291] The identification information of the vehicle bound to the vehicle control client device.

[0292] In some embodiments, the binding module 701 is used to:

[0293] Sending a vehicle binding request to the vehicle control client device; the vehicle binding request includes identification information of the vehicle control proxy device and identification information of the first vehicle;

[0294] Receive a vehicle binding response returned by the vehicle control client device; the vehicle binding response includes identification information and binding status of the first vehicle;

[0295] When the binding status is successful, the information of the vehicle control client corresponding to the vehicle control client device and the identification information of the first vehicle are added to the vehicle agent function cluster.

[0296] In some embodiments, the apparatus further comprises:

[0297] The reading module is used to read the information of the bound vehicle from the vehicle control client device.

[0298] In some embodiments, the apparatus further comprises:

[0299] The authority setting module is used to set the vehicle control authority for the vehicle control client device in the vehicle control agent device; the vehicle control authority is the authority to manage the vehicle.

[0300] In some embodiments, the managing includes at least one of the following:

[0301] Control the vehicle;

[0302] Check the vehicle status information;

[0303] Subscribe to vehicle status information.

[0304] In some embodiments, the apparatus further comprises:

[0305] A discovery module is used to discover the vehicle control client device.

[0306] In some embodiments, the discovery module is configured to discover the vehicle control client device using a DNS-SD discovery method when the vehicle control proxy device is in an IP network environment.

[0307] In some embodiments, the discovery module is used to:

[0308] Obtaining a DNS-SD record of the vehicle control client device, where the DNS-SD record includes identification information of the vehicle control client device;

[0309] The address and port number of the vehicle control client device are obtained according to the DNS-SD record.

[0310] In some embodiments, the discovery module is used to discover the vehicle control client device via Bluetooth Low Energy (BLE).

[0311] In some embodiments, the discovery module is used to:

[0312] Receive the BLE broadcast sent by the vehicle control client device;

[0313] The information of the vehicle control client device is obtained according to the BLE broadcast.

[0314] In some embodiments, the BLE broadcast includes at least one of the following information:

[0315] Identification information of the vehicle control client device;

[0316] The network information of the vehicle control client device.

[0317] Please refer to Figure 8, which shows a block diagram of a binding device for vehicle management provided by one embodiment of the present application. The binding device 800 for vehicle management has the function of implementing the method shown in Figure 3 or Figure 4 above, which is performed by the vehicle control agent device. As shown in Figure 8, the device may include:

[0318] The binding module 801 is used to bind the vehicle control client device to the vehicle control proxy device.

[0319] In some embodiments, the binding module 801 is used to bind the vehicle control client device, the vehicle control proxy device and the first vehicle.

[0320] In some embodiments, the vehicle control client device includes a vehicle client function cluster;

[0321] The vehicle client function cluster indicates a vehicle control agent bound to the vehicle control client device.

[0322] In some embodiments, the vehicle client function cluster includes information about the vehicle bound to the vehicle control client device;

[0323] The information of the vehicle bound to the vehicle control client device includes at least one of the following information:

[0324] Identification information of the vehicle bound to the vehicle control client device;

[0325] The name of the vehicle bound to the vehicle control client device;

[0326] Identification information of the vehicle control agent bound to the vehicle.

[0327] In some embodiments, the binding module 801 is used to:

[0328] receiving a vehicle binding request sent by the vehicle control proxy device; wherein the vehicle binding request includes identification information of the vehicle control proxy device and identification information of the first vehicle;

[0329] Adding the identification information of the vehicle control agent device and the identification information of the first vehicle to the information of the bound vehicle corresponding to the first vehicle;

[0330] Return a vehicle binding response to the vehicle control proxy device; the vehicle binding response includes the identification information and binding status of the first vehicle.

[0331] In some embodiments, the binding module 801 is used to:

[0332] In a case where the vehicle client function cluster already includes information of a bound vehicle corresponding to the first vehicle, adding identification information of the vehicle control proxy device to the information of the bound vehicle corresponding to the first vehicle;

[0333] When the vehicle client function cluster does not include information of the bound vehicle corresponding to the first vehicle, information of the bound vehicle corresponding to the first vehicle is added to the vehicle client function cluster based on the identification information of the vehicle control agent device and the identification information of the first vehicle.

[0334] In some embodiments, the vehicle binding request further includes the name of the first vehicle; and the apparatus further includes:

[0335] A name update module is used to update the first name to the first name if the first name of the first vehicle included in the vehicle binding request is inconsistent with the second name of the first vehicle included in the information of the bound vehicle corresponding to the first vehicle, when the vehicle client function cluster already includes information of the bound vehicle corresponding to the first vehicle.

[0336] In some embodiments, the apparatus further comprises:

[0337] The registration module is used to register a DNS-SD record when the vehicle control client device is in an IP network environment; the DNS-SD record is used by the vehicle control proxy device to discover the vehicle control client device.

[0338] In some embodiments, the apparatus further comprises:

[0339] The sending module is used to send a BLE broadcast; the BLE broadcast allows the vehicle control proxy device to discover the vehicle control client device.

[0340] In some embodiments, the BLE broadcast includes at least one of the following information:

[0341] Identification information of the vehicle control client device;

[0342] The network information of the vehicle control client device.

[0343] Please refer to FIG9 , which shows a schematic diagram of the structure of a computer device 900 provided in one embodiment of the present application. The computer device 900 may include: a processor 901 , a receiver 902 , a transmitter 903 , a memory 904 , and a bus 905 .

[0344] Processor 901 includes one or more processing cores. Processor 901 executes various functional applications and information processing by running software programs and modules. Receiver 902 and transmitter 903 can be implemented as a communication component, which can be a communication chip. This communication chip can also be called a transceiver. Memory 904 is connected to processor 901 via bus 905. Memory 904 can be used to store computer programs, and processor 901 is used to execute these computer programs to implement the various steps in the above-described method embodiments.

[0345] In addition, the memory 904 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disk or optical disk, electrically erasable programmable read-only memory, erasable programmable read-only memory, static random access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0346] In an exemplary embodiment, when the computer device 900 is implemented as the aforementioned vehicle control proxy device, the processor 901 and / or transceiver is configured to bind the vehicle control client device to the vehicle control proxy device. The processes executed by the processor 901 and / or transceiver in the computer device 900 may refer to the steps executed by the vehicle control proxy device in the method shown in either FIG. 2 or FIG. 4 .

[0347] In an exemplary embodiment, when the computer device 900 is implemented as a vehicle control client device, the processor 901 and / or transceiver is used to bind the vehicle control client device to the vehicle control proxy device. The processes performed by the processor 901 and / or transceiver in the computer device 900 can refer to the steps performed by the vehicle control client device in the method shown in either FIG. 3 or FIG. 4 .

[0348] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. The computer program is loaded and executed by a processor to implement all or part of the steps performed by the vehicle control agent device or the vehicle control client device in the method shown in Figure 2, Figure 3 or Figure 4 above.

[0349] The present application also provides a chip, which includes a circuit structure and is used to run in a computer device so that the computer device executes all or part of the steps performed by the vehicle control agent device or the vehicle control client device in the method shown in Figure 4, Figure 5 or Figure 7 above.

[0350] The present application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform all or part of the steps performed by the vehicle control agent device or the vehicle control client device in the method shown in Figures 2, 3, or 4 above.

[0351] The present application also provides a computer program, which is executed by a processor of a computer device to implement all or part of the steps performed by the vehicle control agent device or the vehicle control client device in the method shown in Figure 2, Figure 3 or Figure 4 above.

Claims

1. A binding method for vehicle management, characterized in that: The method is executed by a vehicle control agent device, and the method includes: Bind the vehicle control client device to the vehicle control proxy device.

2. The method according to claim 1, characterized in that The step of binding the vehicle control client device to the vehicle control proxy device includes: The vehicle control client device, the vehicle control proxy device and the first vehicle are bound.

3. The method according to claim 1 or 2, characterized in that: The vehicle control agent device includes a vehicle agent function cluster; The vehicle proxy function cluster indicates a vehicle control client bound to the vehicle control proxy device.

4. The method according to claim 3, characterized in that: The vehicle proxy function cluster includes information of a vehicle control client bound to the vehicle control proxy device; The information of the vehicle control client bound to the vehicle control proxy device includes at least one of the following information: Identification information of the vehicle control client bound to the vehicle control proxy device; Information on the binding type of the vehicle control client bound to the vehicle control proxy device; The identification information of the vehicle bound to the vehicle control client device.

5. The method according to claim 3 or 4, characterized in that: The step of binding the vehicle control client device to the vehicle control proxy device includes: Sending a vehicle binding request to the vehicle control client device; the vehicle binding request includes identification information of the vehicle control proxy device and identification information of the first vehicle; receiving a vehicle binding response returned by the vehicle control client device; the vehicle binding response includes identification information and binding status of the first vehicle; When the binding state is successful, the information of the vehicle control client corresponding to the vehicle control client device and the identification information of the first vehicle are added to the vehicle proxy function cluster.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The information of the bound vehicle is read from the vehicle control client device.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: In the vehicle control proxy device, a vehicle control authority is set for the vehicle control client device; the vehicle control authority is the authority to manage the vehicle.

8. The method according to claim 7, characterized in that The management includes at least one of the following: Control the vehicle; Check the vehicle status information; Subscribe to the vehicle status information.

9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: The vehicle control client device is discovered.

10. The method according to claim 9, characterized in that The discovering the vehicle control client device comprises: When the vehicle control proxy device is in an IP network environment, the vehicle control client device is discovered using a DNS-SD discovery method.

11. The method according to claim 10, characterized in that The method of discovering the vehicle control client device by using a DNS-SD discovery method when the vehicle control proxy device is in an IP network environment includes: Obtaining a DNS-SD record of the vehicle control client device, wherein the DNS-SD record includes identification information of the vehicle control client device; The address and port number of the vehicle control client device are obtained according to the DNS-SD record.

12. The method according to claim 9, characterized in that The discovering the vehicle control client device comprises: The vehicle control client device is discovered via Bluetooth Low Energy (BLE).

13. The method according to claim 12, characterized in that The method of discovering the vehicle control client device by using the low-power Bluetooth BLE method includes: Receiving the BLE broadcast sent by the vehicle control client device; The information of the vehicle control client device is obtained according to the BLE broadcast.

14. The method according to claim 13, characterized in that The BLE broadcast includes at least one of the following information: Identification information of the vehicle control client device; The network information of the vehicle control client device.

15. A binding method for vehicle management, characterized in that: The method is executed by a vehicle control client device, and the method includes: The vehicle control client device is bound to the vehicle control proxy device.

16. The method according to claim 15, characterized in that The step of binding the vehicle control client device to the vehicle control proxy device includes: The vehicle control client device, the vehicle control proxy device and the first vehicle are bound.

17. The method according to claim 15 or 16, characterized in that The vehicle control client device includes a vehicle client function cluster; The vehicle client function cluster indicates a vehicle control agent bound to the vehicle control client device.

18. The method according to claim 17, characterized in that The vehicle client function cluster includes information of the vehicle bound to the vehicle control client device; The information of the vehicle bound to the vehicle control client device includes at least one of the following information: Identification information of the vehicle bound to the vehicle control client device; The name of the vehicle bound to the vehicle control client device; Identification information of the vehicle control agent bound to the vehicle.

19. The method according to claim 17 or 18, characterized in that The step of binding the vehicle control client device to the vehicle control proxy device includes: receiving a vehicle binding request sent by the vehicle control proxy device; the vehicle binding request includes identification information of the vehicle control proxy device and identification information of the first vehicle; Add the identification information of the vehicle control agent device and the identification information of the first vehicle to the first vehicle The corresponding bound vehicle information; A vehicle binding response is returned to the vehicle control proxy device; the vehicle binding response includes identification information and binding status of the first vehicle.

20. The method according to claim 19, characterized in that The step of adding the identification information of the vehicle control proxy device and the identification information of the first vehicle to the information of the bound vehicle corresponding to the first vehicle includes: In a case where the vehicle client function cluster already includes information of a bound vehicle corresponding to the first vehicle, adding identification information of the vehicle control proxy device to the information of the bound vehicle corresponding to the first vehicle; When the vehicle client function cluster does not include information of a bound vehicle corresponding to the first vehicle, information of a bound vehicle corresponding to the first vehicle is added to the vehicle client function cluster according to identification information of the vehicle control agent device and identification information of the first vehicle.

21. The method according to claim 19 or 20, characterized in that The vehicle binding request also includes the name of the first vehicle; The method further comprises: In the case that the vehicle client function cluster already includes information of the bound vehicle corresponding to the first vehicle, if the first name of the first vehicle included in the bound vehicle request is inconsistent with the second name of the first vehicle included in the information of the bound vehicle corresponding to the first vehicle, the second name is updated to the first name.

22. The method according to any one of claims 15 to 21, characterized in that: The method further comprises: When the vehicle control client device is in an IP network environment, a DNS-SD record is registered; the DNS-SD record is used by the vehicle control proxy device to discover the vehicle control client device.

23. The method according to any one of claims 15 to 21, characterized in that: The method further comprises: Sending a BLE broadcast; the BLE broadcast enables the vehicle control proxy device to discover the vehicle control client device.

24. The method according to claim 23, characterized in that The BLE broadcast includes at least one of the following information: Identification information of the vehicle control client device; The network information of the vehicle control client device.

25. A binding device for vehicle management, characterized in that: The device comprises: The binding module is used to bind the vehicle control client device to the vehicle control proxy device.

26. A binding device for vehicle management, characterized in that: The device comprises: The binding module is used to bind the vehicle control client device to the vehicle control proxy device.

27. A computer device, characterized in that: The computer device includes a processor, a memory and a transceiver; The memory stores a computer program, and the processor executes the computer program so that the computer device implements the binding method for vehicle management as described in any one of claims 1 to 24 above.

28. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and the computer program is used to be executed by a processor to implement the binding method for vehicle management as described in any one of claims 1 to 24.

29. A chip, characterized in that: The chip includes a circuit structure, and the chip is used to run in a computer device so that the computer device executes the binding method for vehicle management as described in any one of claims 1 to 24.

30. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; the processor of the computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, so that the computer device executes the binding method for vehicle management as described in any one of claims 1 to 24.

31. A computer program, characterized in that The computer program is executed by a processor of a computer device to implement the binding method for vehicle management as described in any one of claims 1 to 24.

Images