Unbinding method and device for vehicle management, equipment, storage medium and product

Abstract

The invention discloses an unbinding method and device for vehicle management, equipment, a storage medium and a product, and belongs to the technical field of Internet of Things. The method is executed by a vehicle control proxy device, and comprises: releasing a binding relationship between the vehicle control proxy device and a vehicle control client device (201). According to the scheme, a management scheme for the binding relationship between the vehicle control agent equipment and the vehicle control client equipment is provided, and the controllability of managing the vehicle by the vehicle control client equipment through the vehicle control agent equipment is improved.

Description

Unbinding 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 an unbinding 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 method, apparatus, device, storage medium, and product for unbinding vehicle management. The technical solution is as follows:

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

[0007] The binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device is released.

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

[0009] The binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device is released.

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

[0011] The unbinding module is used to release the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device.

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

[0013] The unbinding module is used to release the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client 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] A computer program is stored in the memory, and the processor executes the computer program so that the computer device implements the above-mentioned unbinding 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 unbinding 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 unbinding 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 unbinding 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 unbinding 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 unbinding method for vehicle management.

[0021] Through the technical solution provided in the embodiment of the present application, the vehicle control proxy device is pre-bound to the vehicle control client device so that the vehicle control proxy device can provide a proxy service. It can be realized that the vehicle control client device in the Internet of Things system can manage the vehicle, and the binding relationship between the vehicle control proxy device and the vehicle control client device can be released, thereby providing a management solution for the binding relationship between the vehicle control proxy device and the vehicle control client device, and improving the controllability of the vehicle control client device to manage the vehicle through the vehicle control proxy device. 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 flow chart of an unbinding method for vehicle management provided by one embodiment of the present application;

[0024] FIG3 is a flow chart of an unbinding method for vehicle management provided by one embodiment of the present application;

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

[0026] FIG5 is a flowchart of an unbinding method for vehicle management involved in this application;

[0027] FIG6 is a flowchart of an unbinding method for vehicle management involved in this application;

[0028] FIG7 is a flowchart of an unbinding method for vehicle management involved in the present application;

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

[0030] FIG9 is a block diagram of an unbinding device for vehicle management provided by one embodiment of the present application;

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

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

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

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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.

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

[0042] 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.

[0043] 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.

[0044] 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.

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

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

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

[0048] 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).

[0049] 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.

[0050] 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 .

[0051] The current unbinding technologies in the Internet of Things are as follows:

[0052] 1) Unbinding the car control home

[0053] Unbinding can be done in two ways: long-term and temporary. Long-term bindings can be initiated by the IOTClient or by the IOTAgent. Temporary bindings are not recorded in the smarthomebindingcluster on the IOTAgent. Therefore, temporary bindings can be untied by either the user actively clearing the binding flag on the IOTClient or by the IOTClient passively clearing the binding flag after detecting a connection loss.

[0054] The binding relationship is released by IOTClient:

[0055] S1: The user initiates the cancellation of long-term binding in IOTClient.

[0056] S2, IOTClient deletes the corresponding binding information and device list and other information in IOTClient.

[0057] S3, IOTClient notifies IOTAgent of the binding information in the smarthomebinding cluster.

[0058] S4, IOTAgent deletes the binding relationship.

[0059] S5, notifies IOTClient that the binding relationship has been deleted.

[0060] The binding relationship is released by IOTAgent:

[0061] S6: The user initiates the release of long-term binding on IOTAgent.

[0062] S7, IOTAgent deletes the binding information and device list in the smarthomebinding cluster.

[0063] S8, IOTAgent notifies IOTClient to delete the binding information.

[0064] S9, IOTAgent deletes the binding information.

[0065] Actively release temporary binding:

[0066] S10, if it is a temporary binding, when the user actively initiates to end the binding relationship, the IOTClient deletes its own binding identifier and controllable device list.

[0067] S11, IOTClient initiates the connection termination.

[0068] Passive unbinding:

[0069] S12, if it is a temporary binding, when IOTClient detects that the underlying connection is lost.

[0070] S13, IOTClient automatically deletes its own binding identifier and controllable device list.

[0071] 2)Matter RemoveFibric command

[0072] Administrators use this command to delete a given Fabric and all associated Fabric-scoped data.

[0073] If the given Fabric to be deleted is the last one referencing a given trusted root CA certificate stored in the trusted root certificate list, then that trusted root certificate should be deleted.

[0074] The command parameters are shown in Table 1 below:

[0075] Table 1

[0076] The FabricIndex field contains the Fabric index reference associated with the Fabric to be deleted from the device.

[0077] If the FabricIndex field does not match the FabricIndex of any entry in Fabrics, then a NOCResponse with status code InvalidFabricIndex shall be the command response and no permanent changes shall be made to any device data. Otherwise, one of the following results shall occur:

[0078] 1. If the FabricIndex matches the last remaining entry in the Fabrics list, the device should delete all Matter-related data created on the node since configuration. This includes all Fabric-Scoped data, including Access Control Lists (ACLs), bindings, scenarios, group keys, operational certificates, etc. All trusted roots must also be deleted. Any transaction-related data, including logs, secure sessions, exchanges, and interaction model structures, should also be deleted. Because this operation involves deleting secure session data that may support the current exchange set, the node that calls the command should not expect a response before terminating the secure session with the target.

[0079] 2. If the FabricIndex is not equal to the access fabric index, the device shall begin the process of irrevocably deleting all associated fabric-scoped data, including access control lists, bindings, group keys, operational certificates, etc. Any remaining trusted roots no longer referenced by any operational certificates shall also be deleted. All security sessions, exchanges, and interaction model structures associated with the operational identity under the given fabric shall also be deleted. After deletion, a NOCResponse with a status code of Ok shall be returned.

[0080] 3. If the FabricIndex is equal to the access fabric index, the device shall begin the process of irrevocably deleting all associated fabric-scoped data, including access control entries, bindings, group keys, operational certificates, etc. Any remaining trusted roots no longer referenced by any operational certificates shall also be deleted. All security sessions, exchanges, and interaction model structures associated with the operational identity under the given fabric shall also be deleted. Because this operation involves deleting the security session data that may support the current exchange set, the node invoking the command should not expect a response until the secure session with the target has been terminated.

[0081] Please refer to FIG2 , which shows a flow chart of a method for unbinding 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:

[0082] Step 201: The vehicle control proxy device releases the binding relationship between the vehicle control proxy device and the vehicle control client device.

[0083] In some embodiments, the binding relationship between the vehicle control client device and the vehicle control proxy device may refer to a binding relationship between the first vehicle and the vehicle control client device. For example, the binding relationship between the vehicle control client device and the vehicle control proxy device may be established in the vehicle control proxy device and / or the vehicle control client device, and the binding relationship between the first vehicle and the vehicle control client device may be stored in the vehicle control proxy device and / or the vehicle control client device in the form of a binding item (e.g., a binding relationship table, or attributes / parameters in a cluster).

[0084] The first vehicle is a vehicle corresponding to the vehicle control proxy device. For example, the first vehicle is a vehicle bound to the vehicle control proxy device in the cloud, or the first vehicle is a vehicle that has established a connection with the vehicle control proxy device.

[0085] In the above embodiment, releasing the binding relationship between the vehicle control proxy device and the vehicle control client device may refer to releasing the binding relationship between the first vehicle and the vehicle control client device, for example, deleting the binding item between the vehicle control client device and the first vehicle, or deleting the information in the binding item between the vehicle control client device and the first vehicle.

[0086] For example, the above step 201 is to instruct the controlling vehicle proxy device to locally release the binding relationship between the first vehicle and the vehicle controlling client device, and trigger the vehicle controlling client device to release the binding relationship between the first vehicle and the vehicle controlling client device in the above vehicle controlling client device.

[0087] Alternatively, the above step 201 is to enable the controlling vehicle proxy device to locally release the binding relationship between the first vehicle and the vehicle controlling client device under the triggering of the vehicle controlling client device.

[0088] In some embodiments, the binding relationship between the vehicle control client device and the vehicle control proxy device may refer to a binding relationship among the vehicle control client device, the vehicle control proxy device, and the first vehicle. For example, the binding relationship between the vehicle control client device and the vehicle control proxy device may be a binding relationship established in the vehicle control proxy device and / or the vehicle control client device among the vehicle control client device, the vehicle control proxy device, and the first vehicle.

[0089] In the above embodiment, releasing the binding relationship between the vehicle control proxy device and the vehicle control client device may refer to releasing the binding relationship among the vehicle control client device, the vehicle control proxy device, and the first vehicle.

[0090] For example, the above step 201 is to instruct the control vehicle proxy device to locally release the binding relationship between the vehicle control client device, the vehicle control proxy device and the first vehicle, and trigger the vehicle control client device to release the binding relationship between the vehicle control client device, the vehicle control proxy device and the first vehicle in the above vehicle control client device.

[0091] Alternatively, the above step 201 is to indicate that the vehicle control proxy device, triggered by the vehicle control client device, locally releases the binding relationship among the vehicle control client device, the vehicle control proxy device and the first vehicle.

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

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

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

[0095] 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.

[0096] 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.

[0097] 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.

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

[0099] controlling the first vehicle;

[0100] Checking status information of the first vehicle;

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

[0102] 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.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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.

[0110] In some embodiments, in order to improve the security and controllability of the proxy service provided by the vehicle control proxy device to the vehicle control client device for managing the first vehicle, the binding relationship between the vehicle control proxy device and the vehicle control client device may be released.

[0111] To sum up, in the embodiment of the present application, the vehicle control proxy device is pre-bound to the vehicle control client device so that the vehicle control proxy device can provide a proxy service, which can realize that the vehicle control client device in the Internet of Things system can manage the vehicle, and can also release the binding relationship between the vehicle control proxy device and the vehicle control client device, thereby providing a management solution for the binding relationship between the vehicle control proxy device and the vehicle control client device, and improving the controllability of the vehicle control client device to manage the vehicle through the vehicle control proxy device.

[0112] Please refer to FIG3 , which shows a flow chart of a method for unbinding vehicle management provided by one embodiment of the present application. The method may be performed 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:

[0113] Step 301: The vehicle control client device releases the binding relationship between the vehicle control proxy device and the vehicle control client device.

[0114] In some embodiments, the binding relationship between the vehicle control client device and the vehicle control proxy device may refer to a binding relationship between the first vehicle and the vehicle control client device.

[0115] The first vehicle is a vehicle corresponding to the vehicle control agent device.

[0116] In the above embodiment, releasing the binding relationship between the vehicle control proxy device and the vehicle control client device may refer to releasing the binding relationship between the first vehicle and the vehicle control client device.

[0117] For example, the above step 301 is to instruct the controlling vehicle client device to locally release the binding relationship between the first vehicle and the controlling vehicle client device, and trigger the controlling vehicle proxy device to release the binding relationship between the first vehicle and the controlling vehicle client device in the controlling vehicle proxy device.

[0118] Alternatively, the above step 301 is to indicate that the controlling vehicle client device, under the triggering of the vehicle controlling proxy device, locally releases the binding relationship between the first vehicle and the vehicle controlling client device.

[0119] In some embodiments, the binding relationship between the vehicle control client device and the vehicle control proxy device may refer to a binding relationship among the vehicle control client device, the vehicle control proxy device, and the first vehicle.

[0120] In the above embodiment, releasing the binding relationship between the vehicle control proxy device and the vehicle control client device may refer to releasing the binding relationship among the vehicle control client device, the vehicle control proxy device, and the first vehicle.

[0121] For example, the above step 301 is to instruct the control vehicle client device to locally release the binding relationship between the control vehicle client device, the control vehicle proxy device and the first vehicle, and trigger the control vehicle proxy device to release the binding relationship between the control vehicle client device, the control vehicle proxy device and the first vehicle in the above control vehicle proxy device.

[0122] Alternatively, the above step 301 refers to the controlling vehicle client device, triggered by the vehicle controlling proxy device, locally releasing the binding relationship among the vehicle controlling client device, the vehicle controlling proxy device and the first vehicle.

[0123] To sum up, in the embodiment of the present application, the vehicle control client device is pre-bound to the vehicle control proxy device so that the vehicle control proxy device can provide a proxy service, which can realize that the vehicle control client device in the Internet of Things system can manage the vehicle, and can also release the binding relationship between the vehicle control proxy device and the vehicle control client device, thereby providing a management solution for the binding relationship between the vehicle control proxy device and the vehicle control client device, and improving the controllability of the vehicle control client device to manage the vehicle through the vehicle control proxy device.

[0124] Please refer to FIG4 , which shows a flow chart of a method for unbinding 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:

[0125] Step 401: A connection is established between the vehicle control proxy device and the vehicle control client device.

[0126] In some embodiments, establishing a connection between the vehicle control proxy device and the vehicle control client device may refer to establishing a data channel between the vehicle control proxy device and the vehicle control client device.

[0127] In an embodiment of the present application, when there is a binding relationship between the vehicle control proxy device and the vehicle control client device, the vehicle control proxy device can provide the vehicle control client device with an agent service for managing the first vehicle; accordingly, the vehicle control management device manages the first vehicle through the vehicle control proxy device.

[0128] Step 402 : The vehicle control proxy device releases the binding relationship between the vehicle control proxy device and the vehicle control client device; and the vehicle control client device releases the binding relationship between the vehicle control proxy device and the vehicle control client device.

[0129] In the embodiment of the present application, if the vehicle control client device has been bound to the vehicle control proxy device, the binding relationship between the vehicle control proxy device and the vehicle control client device may be released.

[0130] Among them, the above-mentioned step of releasing the binding relationship between the vehicle control proxy device and the vehicle control client device can be initiated by the user on the vehicle control proxy device or the vehicle control client device side for confirmation. The step of the user confirming whether to initiate the unbinding can be performed before step 402 or before step 401.

[0131] In some embodiments, the vehicle control agent device includes a car agent function cluster (CarAgent Cluster); the car agent function cluster indicates the binding relationship between the vehicle corresponding to the car control agent device and the car control client. In other words, the car agent function cluster indicates the car control client bound to the car control agent device.

[0132] 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.

[0133] 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).

[0134] Among them, a vehicle control proxy device can be bound to multiple vehicle control clients, and each vehicle control client can correspond to a vehicle control client device. Correspondingly, a vehicle control client device can be bound to multiple vehicle control proxies, and each vehicle control proxy can correspond to a vehicle control proxy device.

[0135] 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:

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

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

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

[0139] 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.

[0140] The identification information of the vehicle control client device may include the name and ID of the vehicle control proxy device.

[0141] The above-mentioned vehicle identification information may include the vehicle ID and the like.

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

[0143] The vehicle client function cluster indicates the binding relationship between the vehicle corresponding to each vehicle control agent and the vehicle control client; in other words, the vehicle client function cluster indicates the vehicle control agent bound to the vehicle control client device.

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

[0145] 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).

[0146] In some embodiments, the vehicle client functional cluster includes information about the bound vehicle;

[0147] The bound vehicle information includes at least one of the following:

[0148] The identification information of the vehicle bound to the vehicle control client device;

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

[0150] The identification information of the vehicle control agent bound to the vehicle.

[0151] 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.

[0152] The identification information of the vehicle control agent device may include the name and ID of the vehicle control agent device.

[0153] In some embodiments, the car client function cluster supports at least one of the following commands:

[0154] Remove vehicle request, used to instruct the vehicle to be unbound from the vehicle control client device;

[0155] Remove vehicle response, used to indicate whether the unbinding of the vehicle control client device and the vehicle is completed.

[0156] In some embodiments, releasing the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device includes:

[0157] The vehicle control agent device sends a vehicle removal request to the vehicle control client device; the vehicles to be unbound from the vehicle control client device indicated by the vehicle removal request include the first vehicle;

[0158] The vehicle control client device receives the vehicle removal request sent by the vehicle control proxy device;

[0159] The vehicle control client device removes the identification information of the vehicle control proxy device from the information of the bound vehicle corresponding to the first vehicle;

[0160] The vehicle control client device returns a remove vehicle response to the vehicle control proxy device; the remove vehicle response includes the identification information of the first vehicle, the unbinding status, and the identification information of the vehicle control client device;

[0161] The vehicle control proxy device receives a vehicle removal response returned by the vehicle control client device;

[0162] When the unbinding state is unbinding success, the vehicle control proxy device removes the identification information of the first vehicle from the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster.

[0163] In some embodiments, the vehicle control client device removes the identification information of the vehicle control proxy device from the information of the bound vehicle corresponding to the first vehicle, including:

[0164] In a case where a binding relationship exists between the first vehicle and the vehicle control proxy device, identification information of the vehicle control proxy device is removed from information of the bound vehicle corresponding to the first vehicle.

[0165] In an embodiment of the present application, after the vehicle control client device receives the vehicle removal request, it also needs to detect whether there is a binding relationship between the first vehicle and the vehicle control proxy device. If there is a binding relationship between the first vehicle and the vehicle control proxy device, it means that the vehicle removal request is a legal request. At this time, the vehicle control client device can remove the identification information of the vehicle control proxy device from the information of the bound vehicle corresponding to the first vehicle; conversely, if there is no binding relationship between the first vehicle and the vehicle control proxy device, it means that the vehicle removal request is illegal. At this time, the vehicle control client device can discard / not process the vehicle removal request, and / or return a binding release failure response to the vehicle control proxy device.

[0166] In some embodiments, after the vehicle control client device receives the request to remove the vehicle, it can also remove the identification information of the vehicle control proxy device from the information of the bound vehicle corresponding to the first vehicle without detecting whether there is a binding relationship between the first vehicle and the vehicle control proxy device; at this time, the step of detecting whether there is a binding relationship between the first vehicle and the vehicle control proxy device can be executed in the vehicle control proxy device. For example, before sending the request to remove the vehicle, the vehicle control proxy device first detects whether there is a binding relationship between the first vehicle and the vehicle control proxy device. If so, the request to remove the vehicle is sent, otherwise the request to remove the vehicle is not sent.

[0167] In some embodiments, the vehicle proxy function cluster supports a remove client request; the remove client request is used to control the vehicle client to remove the binding with the vehicle.

[0168] In some embodiments, the process of releasing the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device may include:

[0169] The vehicle control client device removes the identification information of the vehicle control proxy device from the information of the bound vehicle corresponding to the first vehicle;

[0170] The vehicle control client device sends a remove client request to the vehicle control proxy device; the remove client request includes identification information of the first vehicle;

[0171] The vehicle control proxy device receives a client removal request sent by the vehicle control client device, where the client removal request includes identification information of the first vehicle;

[0172] The vehicle control proxy device removes the identification information of the first vehicle from the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster.

[0173] In some embodiments, the vehicle control client device sends a request to remove the client to the vehicle control proxy device, including:

[0174] When identification information of at least two vehicle control agents exists in the information of the bound vehicle corresponding to the first vehicle, a client removal request is sent to devices corresponding to the at least two vehicle control agents respectively.

[0175] In an embodiment of the present application, a vehicle can be bound to multiple vehicle control agents. Accordingly, in a vehicle control client device, there may be a situation where a vehicle is bound multiple times, and each binding corresponds to a different vehicle control agent. That is, a vehicle can have multiple binding relationships in a vehicle control client device. In this case, multiple binding relationships corresponding to the same vehicle can be stored in the information of a bound vehicle. At this time, when the vehicle control client device actively initiates the removal of the binding relationship with the first vehicle, since there are multiple corresponding vehicle control agents, the vehicle control client device can send the above-mentioned removal client request to the vehicle control agent devices corresponding to the above-mentioned multiple vehicle control agents, thereby realizing batch deletion of the binding relationships corresponding to the same vehicle. Alternatively, when the vehicle control client device actively initiates the removal of the binding relationship with the first vehicle, it can also send a removal client request to the corresponding vehicle control agent device for a certain vehicle control agent in the information of the bound vehicle corresponding to the first vehicle.

[0176] Furthermore, when a vehicle has multiple binding relationships with a single vehicle control client device, the vehicle control client device can also create a separate set of bound vehicle information for each of these binding relationships, with each of these bound vehicle information sets containing different vehicle control agents. In this case, when the vehicle control client device proactively initiates the unbinding of the first vehicle, it sends a client removal request to the corresponding vehicle control agent device for the information of a particular bound vehicle among the multiple bound vehicle information sets corresponding to the first vehicle. Alternatively, the vehicle control client device can also send client removal requests to the corresponding removal client devices for each of the multiple bound vehicle information sets corresponding to the first vehicle.

[0177] In some embodiments, the method further includes: removing information of a bound vehicle corresponding to the first vehicle in the vehicle client function cluster.

[0178] In the above embodiment, a vehicle may have multiple binding relationships in a vehicle control client device, and the vehicle control client device establishes information of a bound vehicle for each of the above multiple binding relationships. When the vehicle control client device sends a client removal request based on the information of the bound vehicle corresponding to a certain binding relationship and successfully cancels the binding relationship, the vehicle control client device can remove the information of the bound vehicle.

[0179] In some embodiments, the information of the bound vehicle corresponding to the first vehicle in the car client function cluster is removed, including: in the case where there is no identification information of the vehicle control agent in the information of the bound vehicle corresponding to the first vehicle, the information of the bound vehicle corresponding to the first vehicle in the car client function cluster is removed.

[0180] In a possible implementation scheme of the above embodiment, a vehicle may have multiple binding relationships in a vehicle control client device, and the vehicle control client device establishes information of a single bound vehicle for the above multiple binding relationships. When the vehicle control client device sends a client removal request based on the information of the bound vehicle corresponding to a certain binding relationship and successfully cancels the binding relationship, or when the vehicle control client is idle, the vehicle control client device removes the identification information corresponding to the vehicle control agent device in the information of the bound vehicle, and can also determine whether there is other identification information of the vehicle control agent in the information of the bound vehicle. If not, the information of the bound vehicle is removed; otherwise, the information of the bound vehicle is retained.

[0181] In some embodiments, the above method also includes: if the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster does not include the vehicle identification information, the vehicle control proxy device can remove the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster.

[0182] In an embodiment of the present application, a vehicle control client device can also be bound to multiple vehicles in the same vehicle control proxy device. Accordingly, in a vehicle control proxy device, a vehicle control client device can be bound multiple times, and each binding corresponds to a different vehicle. In other words, a vehicle control client device can have multiple binding relationships in a vehicle control proxy device. In this case, the multiple binding relationships corresponding to the same vehicle control client device can be stored in the information of a vehicle control client. In other words, the information of a vehicle control client can include the identification information of multiple vehicles.

[0183] In addition, when a vehicle control client device has multiple binding relationships in a vehicle control proxy device, the vehicle control proxy device can also establish vehicle control client information for each of the multiple binding relationships, and the information of the multiple vehicle control clients each includes identification information of a vehicle.

[0184] In the above embodiment, when there are multiple binding relationships between a vehicle control client device and a vehicle control proxy device, and the vehicle control proxy device establishes information of a vehicle control client for each of the multiple binding relationships, when the binding relationship between the vehicle control client device and a vehicle is released, the information of the vehicle control client corresponding to the binding relationship can be removed.

[0185] In the case where there are multiple binding relationships between a vehicle control client device and a vehicle control proxy device, and the vehicle control proxy device establishes information of a single vehicle control client for the above multiple binding relationships, when the binding relationship between the vehicle control client device and a vehicle is released, the identification information of the vehicle can be deleted from the information of the vehicle control client corresponding to the vehicle control client device; each time the vehicle control proxy device deletes the identification information of a vehicle from the above vehicle control client information, or when the vehicle control proxy device is idle, the vehicle control proxy device can determine whether the vehicle identification information still exists in the information of the vehicle control client. If not, the information of the vehicle control client is removed; otherwise, the information of the vehicle control client is retained.

[0186] In some embodiments, the method further includes: when the vehicle control proxy device releases the binding relationship with the vehicle control client device, the vehicle control proxy device may remove the permission corresponding to the vehicle control client device in the Access Control List (ACL).

[0187] For example, when the vehicle control proxy device releases the binding relationship between the vehicle control client device and the first vehicle, the vehicle control proxy device may remove the permission of the vehicle control client device to the content related to the first vehicle in the ACL.

[0188] For another example, when the vehicle control proxy device removes the vehicle control client information corresponding to the vehicle control client device, the vehicle control proxy device may remove the vehicle control client device's permissions to all vehicle-related content in the ACL, or remove all permissions of the vehicle control client device in the ACL.

[0189] Example 1:

[0190] (1) Implement the CarClient Cluster on smart home devices to record the cars and CarAgents bound to the CarClient.

[0191] The car client functional cluster contains the following attributes, which are defined in Table 2:

[0192] Table 2

[0193] The carInfo structure is defined as shown in Table 3 below:

[0194] Table 3

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

[0196] Table 4

[0197] The removeCarReq method is used by the CarAgent to remove the binding relationship between the car and the CarClient. Its parameter definitions are shown in Table 5 below:

[0198] Table 5

[0199] When UnbindingAllCars is True, it means unbinding all cars corresponding to CarAgent, and the value of the CarList parameter is ignored. When UnbindingAllCars is False, it means unbinding the cars listed in CarList.

[0200] After receiving removeCarReq, CarClient should verify whether the sender has a binding relationship with CarID. If no binding relationship exists, an error code is returned. If a binding relationship exists, bindCarResp is returned, and its parameters are defined as shown in Table 6 below:

[0201] Table 6

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

[0203] (2) The CarAgent Cluster is implemented on the mobile phone and records the bound CarClient.

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

[0205] Table 7

[0206] The clientInfo structure is defined as shown in Table 8 below:

[0207] Table 8

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

[0209] Please refer to Figure 5, which shows a flowchart of unbinding for vehicle management involved in this application. In this embodiment, the user can unbind the CarAgent implemented on the mobile phone from the CarClient implemented on the smart TV in the home network. The above process may include:

[0210] S1: CarClient and CarAgent are bound and a data channel is established.

[0211] Unbinding process:

[0212] S2: The user unbinds one or more cars from the CarClient on their phone. The CarAgent sends a removeCar Request to the CarClient, containing the CarIDs of all unbound cars or all unbound cars.

[0213] S3: After receiving removeCarReq, CarClient verifies that there is a binding relationship between CarAgent and CarID, and then deletes the corresponding CarID and CarAgent in the boundCars attribute.

[0214] S4: CarClient returns removeCar Response, which contains all unbound CarIDs, CarClient ID, and unbinding status.

[0215] S5: CarAgent receives the removeCar Response and deletes the unbound CarID under the corresponding ClientID in the boundClients attribute. If there is no CarID under the ClientID, the ClientID is deleted and the corresponding permissions of the client in the ACL are cleared.

[0216] Example 2:

[0217] Compared with the above embodiment 1, the difference in the cluster is that the car agent function set includes the following commands, which are defined as shown in Table 9 below:

[0218] Table 9

[0219] The removeClientReq method is used by CarClient to remove the binding relationship with a car. The unbound car is identified by CarID.

[0220] The removeClientReq parameter definition is shown in Table 10 below:

[0221] Table 10

[0222] After receiving the removeClientReq, CarAgent should delete the corresponding CarID in the CarList under the corresponding ClientID in boundClients. If the CarList is empty after deletion, CarAgent should delete the entry.

[0223] Please refer to Figure 6, which shows a flowchart of unbinding for vehicle management involved in this application. In this embodiment, the user can unbind the CarClient implemented in the smart TV from the CarAgent implemented on the mobile phone. The process may include:

[0224] S1: CarClient and CarAgent are bound and a data channel is established.

[0225] Unbinding process:

[0226] S2: The user unbinds the car from the smart home device. The CarClient sends a removeClient Request to the CarAgent corresponding to the car's CarID in the boundCars attribute, with the parameter being the car's CarID.

[0227] In S3, CarClient deletes the corresponding CarID and CarAgent in the boundCars attribute.

[0228] S4: After the user confirms on the phone, CarAgent deletes the CarID of the unbound car under the corresponding ClientID from the boundClients list. If there is no CarID in the CarList under the ClientID, the ClientID is deleted and the corresponding permissions of the client in the ACL are cleared.

[0229] Example 3:

[0230] The difference between the third embodiment and the first embodiment in terms of clustering is that the carInfo structure in the car client function cluster is defined as shown in Table 11 below:

[0231] Table 11

[0232] After receiving the removeCarReq, if the CarAgents field corresponding to the CarID contains more than one CarAgent, the CarClient can only delete the corresponding CarAgent in CarAgents without deleting the Entry. If the corresponding CarAgents is empty after deleting the CarAgent, the CarClient can delete the Entry.

[0233] The difference between this third embodiment and the second embodiment is that if the CarAgents field corresponding to the CarID in the car agent function cluster contains more than one CarAgent, the CarClient can send the request to each CarAgent in the CarAgents. Afterwards, the CarClient can delete the entry corresponding to the CarID.

[0234] Please refer to Figure 7, which shows a flowchart of unbinding for vehicle management involved in this application. In this embodiment, the user can unbind the two through CarAgent implemented on the mobile phone or CarClient implemented in the smart TV. The process may include:

[0235] S1: CarClient and CarAgent are bound and a data channel is established.

[0236] Unbinding process:

[0237] (1) CarAgent initiates unbinding

[0238] S2: The user unbinds one or more cars from the CarClient on the mobile phone. The CarAgent sends a removeCar Request to the CarClient, including all unbindings or all unbound CarIDs.

[0239] S3. After receiving removeCarReq, CarClient verifies that there is a binding relationship between CarAgent and CarID, and then deletes the CarAgent under the corresponding CarID in the boundCars attribute. If there is no CarAgent under the CarID, the CarID is deleted.

[0240] S4: CarClient returns removeCar Response, which contains all unbound CarIDs, CarClient ID, and unbinding status.

[0241] S5: CarAgent receives the removeCar Response and deletes the unbound CarID under the corresponding ClientID in the boundClients attribute. If there is no CarID under the ClientID, the ClientID is deleted and the corresponding permissions of the client in the ACL are cleared.

[0242] (2) CarClient initiates unbinding

[0243] S6: The user unbinds the car from the smart home device. The CarClient sends a removeClient Request to all CarAgents corresponding to the car's CarID in the boundCars attribute, with the parameter being the car's CarID.

[0244] S7, CarClient deletes the entry corresponding to the CarID in the boundCars attribute, including the CarID, CarName, and all CarAgents.

[0245] S8: After the user confirms on the mobile phone, CarAgent deletes the CarID of the unbound car under the corresponding ClientID from the boundClients list. If there is no CarID in the CarList under the ClientID, the ClientID is deleted and the corresponding permissions of the client in the ACL are cleared.

[0246] Please refer to Figure 8, which shows a block diagram of an unbinding device for vehicle management provided by one embodiment of the present application. The unbinding device 800 for vehicle management has the functions 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 8, the device may include:

[0247] The unbinding module 801 is used for the vehicle control proxy device to unbind the binding relationship between the vehicle control proxy device and the vehicle control client device.

[0248] In some embodiments, the unbinding module 801 is used to:

[0249] Unbinding the first vehicle from the vehicle control client device;

[0250] Alternatively, the binding relationship between the vehicle control proxy device, the first vehicle and the vehicle control client device is released.

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

[0252] The vehicle proxy function cluster indicates a binding relationship between a vehicle corresponding to the vehicle control proxy device and a vehicle control client.

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

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

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

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

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

[0258] In some embodiments, the unbinding module 801 is used to:

[0259] Sending a vehicle removal request to the vehicle control client device; the vehicles to be unbound from the vehicle control client device indicated by the vehicle removal request include the first vehicle;

[0260] Receive a remove vehicle response returned by the vehicle control client device; the remove vehicle response includes identification information of the first vehicle, unbinding status, and identification information of the vehicle control client device;

[0261] When the unbinding state is successful, the identification information of the first vehicle in the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster is removed.

[0262] In some embodiments, the vehicle proxy function cluster supports a remove client request; the remove client request is used to control the vehicle client to remove the binding with the vehicle.

[0263] In some embodiments, the unbinding module 801 is used to:

[0264] receiving the client removal request sent by the vehicle control client device, wherein the client removal request includes identification information of the first vehicle;

[0265] The identification information of the first vehicle in the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster is removed.

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

[0267] The information removing module is configured to remove the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster if the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster does not contain the identification information of the vehicle.

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

[0269] The permission removal module is used to remove the permission corresponding to the vehicle control client device in the ACL.

[0270] Please refer to Figure 9, which shows a block diagram of an unbinding device for vehicle management provided by one embodiment of the present application. The unbinding device 900 for vehicle management has the functions of implementing the method shown in Figure 3 or Figure 4 above, which is performed by the vehicle control client device. As shown in Figure 9, the device may include:

[0271] The unbinding module 901 is used for the vehicle control client device to unbind the binding relationship between the vehicle control proxy device and the vehicle control client device.

[0272] In some embodiments, the unbinding module 901 is used to:

[0273] Unbinding the first vehicle from the vehicle control client device;

[0274] Alternatively, the binding relationship between the vehicle control proxy device, the first vehicle and the vehicle control client device is released.

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

[0276] The vehicle client function cluster indicates the binding relationship between the vehicle corresponding to each vehicle control agent and the vehicle control client.

[0277] In some embodiments, the vehicle client functional cluster includes information about the bound vehicle;

[0278] The information of the bound vehicle includes at least one of the following information:

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

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

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

[0282] In some embodiments, the car client function cluster supports at least one of the following commands:

[0283] Remove vehicle request, used to instruct the vehicle to be unbound from the vehicle control client device;

[0284] The remove vehicle response is used to indicate whether the unbinding of the vehicle control client device and the vehicle is completed.

[0285] In some embodiments, the unbinding module 901 is used to:

[0286] receiving a vehicle removal request sent by the vehicle control proxy device; the vehicles to be unbound from the vehicle control client device indicated by the vehicle removal request include the first vehicle;

[0287] Removing the identification information of the vehicle control agent device from the information of the bound vehicle corresponding to the first vehicle;

[0288] A remove vehicle response is returned to the vehicle control proxy device; the remove vehicle response includes the identification information of the first vehicle, the unbinding status, and the identification information of the vehicle control client device.

[0289] In some embodiments, the unbinding module 901 is configured to remove identification information of the vehicle control proxy device from information of a bound vehicle corresponding to the first vehicle when a binding relationship exists between the first vehicle and the vehicle control proxy device.

[0290] In some embodiments, the unbinding module 901 is used to:

[0291] Removing the identification information of the vehicle control agent device from the information of the bound vehicle corresponding to the first vehicle;

[0292] Sending a client removal request to the vehicle control proxy device; the client removal request includes identification information of the first vehicle.

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

[0294] An information removal module is used to remove the information of the bound vehicle corresponding to the first vehicle in the vehicle client function cluster.

[0295] In some embodiments, the information removal module is used to remove the information of the bound vehicle corresponding to the first vehicle in the vehicle client function cluster if there is no identification information of the vehicle control agent in the information of the bound vehicle corresponding to the first vehicle.

[0296] In some embodiments, the information removal module is configured to, when there is identification information of at least two vehicle control agents in the information of the bound vehicle corresponding to the first vehicle, send the client removal request to the devices corresponding to the at least two vehicle control agents respectively.

[0297] Please refer to FIG10 , which shows a schematic diagram of the structure of a computer device 1000 provided in one embodiment of the present application. The computer device 1000 may include: a processor 1001 , a receiver 1002 , a transmitter 1003 , a memory 1004 , and a bus 1005 .

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

[0299] In addition, the memory 1004 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.

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

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

[0302] 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.

[0303] 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.

[0304] 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.

[0305] 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 method for unbinding vehicle management, characterized in that: The method is executed by a vehicle control agent device, and the method includes: The binding relationship between the vehicle control proxy device and the vehicle control client device is released.

2. The method according to claim 1, characterized in that The releasing of the binding relationship between the vehicle control proxy device and the vehicle control client device comprises: Unbinding the first vehicle from the vehicle control client device; Alternatively, the binding relationship between the vehicle control proxy device, the first vehicle and the vehicle control client device is released.

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 binding relationship between a vehicle corresponding to the vehicle control proxy device and a vehicle control client.

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.

5. The method according to claim 3 or 4, characterized in that: The releasing of the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device includes: Sending a vehicle removal request to the vehicle control client device; the vehicle to be unbound from the vehicle control client device indicated by the vehicle removal request includes the first vehicle; Receive a remove vehicle response returned by the vehicle control client device; the remove vehicle response includes identification information of the first vehicle, an unbinding state, and identification information of the vehicle control client device; When the unbinding state is successful, the identification information of the first vehicle in the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster is removed.

6. The method according to claim 3 or 4, characterized in that: The vehicle proxy function cluster supports a remove client request; the remove client request is used to control the vehicle client to remove the binding with the vehicle.

7. The method according to claim 6, characterized in that The releasing of the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device includes: Receiving the client removal request sent by the vehicle control client device, wherein the client removal request includes identification information of the first vehicle; The identification information of the first vehicle in the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster is removed.

8. The method according to claim 5 or 7, characterized in that: The method further comprises: If the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster does not include the identification information of the vehicle, the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster is removed.

9. The method according to claim 8, characterized in that The method further comprises: Remove the permissions corresponding to the vehicle control client device in the ACL.

10. A method for unbinding vehicle management, characterized in that: The method is executed by a vehicle control client device, and the method includes: The binding relationship between the vehicle control proxy device and the vehicle control client device is released.

11. The method according to claim 10, characterized in that The releasing the binding relationship between the vehicle control proxy device and the vehicle control client device comprises: Release the binding relationship between the first vehicle and the vehicle control client device; Alternatively, the binding relationship between the vehicle control proxy device, the first vehicle and the vehicle control client device is released.

12. The method according to claim 10 or 11, characterized in that: The vehicle control client device includes a vehicle client function cluster; The vehicle client function cluster indicates the binding relationship between the vehicle corresponding to each vehicle control agent and the vehicle control client.

13. The method according to claim 12, characterized in that The vehicle client function cluster includes information about the bound vehicle; The information of the bound vehicle 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.

14. The method according to claim 12 or 13, characterized in that The car client function cluster supports at least one of the following commands: A vehicle removal request is used to instruct the vehicle to be unbound from the vehicle control client device; The remove vehicle response is used to indicate whether the unbinding of the vehicle control client device from the vehicle is completed.

15. The method according to claim 14, characterized in that The releasing of the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device includes: receiving a vehicle removal request sent by the vehicle control proxy device; the vehicles indicated by the vehicle removal request to be unbound from the vehicle control client device include the first vehicle; Removing the identification information of the vehicle control proxy device from the information of the bound vehicle corresponding to the first vehicle; A remove vehicle response is returned to the vehicle control proxy device; the remove vehicle response includes the identification information of the first vehicle, the unbinding state, and the identification information of the vehicle control client device.

16. The method according to claim 15, characterized in that The identification information of the vehicle control agent device in the information of removing the bound vehicle corresponding to the first vehicle includes: In the case that there is a binding relationship between the first vehicle and the vehicle control proxy device, the identification information of the vehicle control proxy device is removed from the information of the bound vehicle corresponding to the first vehicle.

17. The method according to claim 12 or 13, characterized in that The releasing of the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device includes: Removing the identification information of the vehicle control proxy device from the information of the bound vehicle corresponding to the first vehicle; A client removal request is sent to the vehicle control proxy device; the client removal request includes identification information of the first vehicle.

18. The method according to any one of claims 15 to 17, characterized in that: The method further comprises: The information of the bound vehicle corresponding to the first vehicle in the vehicle client function cluster is removed.

19. The method according to claim 18, characterized in that The removing the information of the bound vehicle corresponding to the first vehicle in the vehicle client function cluster includes: If there is no identification information of the vehicle control agent in the information of the bound vehicle corresponding to the first vehicle, the information of the bound vehicle corresponding to the first vehicle in the vehicle client function cluster is removed.

20. The method according to claim 17, characterized in that The sending a request to remove the client to the vehicle control proxy device includes: When there is identification information of at least two vehicle control agents in the information of the bound vehicle corresponding to the first vehicle, the client removal request is sent to the devices corresponding to the at least two vehicle control agents respectively.

21. An unbinding device for vehicle management, characterized in that: The device comprises: The unbinding module is used for the vehicle control proxy device to unbind the binding relationship between the vehicle control proxy device and the vehicle control client device.

22. An unbinding device for vehicle management, characterized in that: The device comprises: The unbinding module is used for the vehicle control client device to unbind the binding relationship between the vehicle control proxy device and the vehicle control client device.

23. 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 unbinding method for vehicle management as described in any one of claims 1 to 20 above.

24. 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 unbinding method for vehicle management as described in any one of claims 1 to 20.

25. 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 unbinding method for vehicle management as described in any one of claims 1 to 20.

26. A computer program product, characterized in that The computer program product includes computer instructions, which are 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, so that the computer device executes the unbinding method for vehicle management as described in any one of claims 1 to 20.

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

Images