WO2024254879A1 - 用于车辆管理的解绑方法、装置、设备、存储介质及产品 - Google Patents
用于车辆管理的解绑方法、装置、设备、存储介质及产品 Download PDFInfo
- Publication number
- WO2024254879A1 WO2024254879A1 PCT/CN2023/100849 CN2023100849W WO2024254879A1 WO 2024254879 A1 WO2024254879 A1 WO 2024254879A1 CN 2023100849 W CN2023100849 W CN 2023100849W WO 2024254879 A1 WO2024254879 A1 WO 2024254879A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- vehicle
- vehicle control
- client device
- control client
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
Definitions
- the present application relates to the technical field of Internet of Things, and in particular to an unbinding method, device, equipment, storage medium and product for vehicle management.
- IoT Internet of Things
- vehicles can be remotely controlled by mobile terminal devices such as mobile phones.
- mobile terminal devices such as mobile phones.
- the vehicle's on-board equipment and the user's mobile terminal are simultaneously connected to the cloud server and bound in the cloud server. Subsequently, the mobile terminal can send control instructions to the on-board equipment through the cloud server.
- the embodiment of the present application provides a method, device, equipment, storage medium and product for unbinding vehicle management.
- the technical solution is as follows:
- 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:
- the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device is released.
- 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:
- the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device is released.
- an embodiment of the present application provides an unbinding device for vehicle management, the device comprising:
- 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.
- an embodiment of the present application provides an unbinding device for vehicle management, the device comprising:
- the unbinding module is used to unbind the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device.
- an embodiment of the present application provides a computer device, the computer device is implemented as an information reporting device, and the computer device includes a processor, a memory, and a transceiver;
- 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.
- 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.
- an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and the computer program is loaded and executed by a processor to implement the above-mentioned unbinding method for vehicle management.
- 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.
- the present application provides a computer program product, the computer program product comprising computer instructions, the computer instructions being stored in a computer-readable storage medium.
- a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above-mentioned unbinding method for vehicle management.
- 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.
- 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.
- FIG1 is a schematic diagram of a network architecture of an Internet of Things provided by an embodiment of the present application.
- FIG2 is a flow chart of an unbinding method for vehicle management provided by an embodiment of the present application.
- FIG3 is a flow chart of an unbinding method for vehicle management provided by an embodiment of the present application.
- FIG4 is a flowchart of unbinding for vehicle management provided by one embodiment of the present application.
- FIG5 is a flowchart of unbinding for vehicle management involved in the present application.
- FIG6 is a flowchart of unbinding for vehicle management involved in the present application.
- FIG7 is a flowchart of unbinding for vehicle management involved in the present application.
- FIG8 is a block diagram of an unbinding device for vehicle management provided by an embodiment of the present application.
- FIG9 is a block diagram of an unbinding device for vehicle management provided by one embodiment of the present application.
- FIG. 10 is a schematic diagram of the structure of a computer device provided in one embodiment of the present application.
- the network architecture of the Internet of Things may include: an Internet of Things device 110 (shown in Figure 1 as an Internet of Things device 110a, an Internet of Things device 110b, an Internet of Things device 110c, and an Internet of Things device 110d), an agent device 120 (shown in Figure 1 as an agent device 120a and an agent device 120b) and a vehicle 130 (shown in Figure 1 as a vehicle 130a, a vehicle 130b, and a vehicle 130c); optionally, the network architecture may also include a bridge device 140; optionally, the network architecture may also include a cloud server 150.
- 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.
- 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.
- 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.
- the proxy device 120 is a terminal device on the user side, for example, the proxy device 120 may be a smart phone, a tablet computer, a smart watch, etc., or the proxy device 120 may also be a personal computer, such as a desktop computer, a portable computer, a personal workstation, etc.
- the vehicle 130 may be a vehicle/on-board device having a 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.
- the proxy device 120 may establish a connection with the vehicle 130 via the cloud server 150 .
- the proxy device 120 may also directly establish a connection with the IoT device 110 .
- the above-mentioned IoT device 110, proxy device 120, and bridge device 140 may be electronic devices that meet the same or different IoT protocols.
- they may be electronic devices that meet the Matter protocol under the Connectivity Standards Alliance (CSA).
- CSA Connectivity Standards Alliance
- S1 The user initiates the release of long-term binding in IOTClient.
- IOTClient deletes the corresponding binding information and device list and other information in IOTClient.
- IOTClient notifies IOTAgent of the binding information in the smarthomebinding cluster.
- IOTAgent deletes the binding relationship.
- S6 The user initiates the release of long-term binding in IOTAgent.
- IOTAgent deletes the binding information and device list in the smarthomebinding cluster.
- IOTAgent notifies IOTClient to delete the binding information.
- IOTAgent deletes the binding information.
- the IOTClient deletes its own binding identifier and controllable device list.
- IOTClient automatically deletes its own binding identifier and controllable device list.
- the given Fabric to be deleted is the last one referencing the given trusted root stored in the list of trusted root certificates If the CA certificate is missing, the trusted root certificate should be deleted.
- the FabricIndex field contains the Fabric index reference associated with the Fabric to be removed from the device.
- 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 set of exchanges, the node calling the command should not expect a response until the secure session with the target is terminated.
- ACLs Access Control Lists
- Bindings Scenarios
- Group Keys Group Keys
- Operational Certificates etc.
- 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 set of exchanges, the node calling the command should not expect a response until the secure session with the target is terminated.
- 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 secure 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.
- 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 secure sessions, exchanges, and interaction model structures associated with the operational identity under a given Fabric shall also be deleted. Since this operation involves deleting secure session data that may support the current set of exchanges, the node invoking the command should not expect a response until the secure session with the target is terminated.
- FIG. 2 shows a flow chart of an unbinding method for vehicle management provided by an embodiment of the present application.
- the method may be executed by a vehicle control agent device.
- the vehicle control agent device may be the agent device 120 in the network architecture shown in FIG. 1 .
- the method may include the following steps:
- Step 201 The vehicle control proxy device releases the binding relationship between the vehicle control proxy device and the vehicle control client device.
- the binding relationship between the vehicle control client device and the vehicle control proxy device may refer to the binding relationship between the first vehicle and the vehicle control client device.
- 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 (such as a binding relationship table, or an attribute/parameter in a cluster).
- the first vehicle is a vehicle corresponding to the vehicle control proxy device.
- the first vehicle is a vehicle bound to the vehicle control proxy device in the cloud, or the first vehicle is a vehicle connected to the vehicle control proxy device.
- 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.
- the above step 201 is to instruct the vehicle control proxy device to locally release the binding relationship between the first vehicle and the vehicle control client device, and trigger the vehicle control client device to release the binding relationship between the first vehicle and the vehicle control client device in the above vehicle control client device.
- step 201 is to enable the vehicle controlling 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.
- the binding relationship between the vehicle control client device and the vehicle control proxy device may be a binding relationship between the vehicle control client device, the vehicle control proxy device, and the first vehicle.
- the binding relationship between the vehicle control client device and the vehicle control proxy device may be a binding relationship between the vehicle control client device, the vehicle control proxy device, and the first vehicle established in the vehicle control proxy device and/or the vehicle control client device.
- 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.
- step 201 is that the vehicle control proxy device, under the triggering of 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.
- the vehicle control proxy device may correspond to at least one vehicle, and the at least one vehicle includes the first vehicle.
- the vehicle control client device may be an IoT device, such as the IoT device 110 in the network architecture shown in FIG. 1 .
- the above-mentioned vehicle control client device can be an IoT device such as a smart TV or a smart refrigerator.
- the above-mentioned binding of the vehicle control client device and the vehicle control proxy device can be used to support the vehicle control proxy device to provide a proxy service for managing the first vehicle to the vehicle control client device.
- the above-mentioned vehicle control proxy device can establish connections with the vehicle control client device and the first vehicle respectively.
- 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.
- the above management request is sent by the vehicle control client device to the vehicle control proxy device, and then the vehicle control proxy 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.
- the management includes at least one of the following:
- 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 a 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.
- 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.
- the above-mentioned 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.
- the above-mentioned subscription to the status information of the first vehicle may be that the controlling vehicle proxy device returns 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 when it is subsequently detected that the status information of the first vehicle is updated, the updated part of the status information of the first vehicle is notified to the vehicle controlling client device.
- 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.
- the proxy service may preliminarily bind the first vehicle with the vehicle control client device in the vehicle control proxy device, and/or bind the first vehicle with the vehicle control proxy device in the vehicle control client device.
- the binding relationship between the vehicle control proxy device and the vehicle control client device may be released.
- FIG. 3 shows a flow chart of an unbinding method for vehicle management provided by an embodiment of the present application.
- the method may be executed by a vehicle control client device.
- the vehicle control client device may be the Internet of Things device 110 in the network architecture shown in FIG. 1 .
- the method may include the following steps:
- Step 301 The vehicle control client device releases the binding relationship between the vehicle control proxy device and the vehicle control client device.
- the binding relationship between the vehicle control client device and the vehicle control proxy device may refer to the binding relationship between the first vehicle and the vehicle control client device.
- the first vehicle is a vehicle corresponding to the vehicle control agent device.
- 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.
- the above step 301 is to instruct the vehicle control client device to locally release the binding relationship between the first vehicle and the vehicle control client device, and trigger the vehicle control proxy device to release the binding relationship between the first vehicle and the vehicle control client device in the above vehicle control proxy device.
- step 301 is to enable the vehicle control client device to locally release the binding relationship between the first vehicle and the vehicle control client device under the triggering of the vehicle control proxy device.
- the binding relationship between the vehicle control client device and the vehicle control proxy device may refer to a binding relationship between the vehicle control client device, the vehicle control proxy device and the first vehicle.
- 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.
- 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.
- step 301 is to indicate that the vehicle control client device, under the triggering of the vehicle control proxy device, locally releases the binding relationship among the vehicle control client device, the vehicle control proxy device and the first vehicle.
- 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.
- 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.
- FIG. 4 shows a flow chart of an unbinding method for vehicle management provided by an 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 Internet of Things device 110 in the network architecture shown in FIG. 1 , respectively.
- the method can include the following steps:
- Step 401 A connection is established between a vehicle control proxy device and a vehicle control client device.
- establishing a connection between the vehicle control proxy device and the vehicle control client device may be establishing a data channel between the vehicle control proxy device and the vehicle control client device.
- the vehicle control proxy device when there is a binding relationship between the vehicle control proxy device and the vehicle control client 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.
- Step 402 the vehicle control proxy device releases the binding relationship between the vehicle control proxy device and the vehicle control client device; the vehicle control client device releases the binding relationship between the vehicle control proxy device and the vehicle control client device.
- the binding relationship between the vehicle control proxy device and the vehicle control client device may be released.
- 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, and the step of the user confirming whether to initiate the unbinding can be performed before step 402 or before step 401.
- the car 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 above-mentioned car agent function cluster indicates the car control client bound to the car control agent device.
- CarAgent Cluster car agent function cluster
- 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.
- the vehicle control proxy device may also indicate the vehicle control client bound to the vehicle control proxy device by other means other than clustering (such as a binding relationship table).
- 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.
- 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.
- the vehicle proxy function cluster includes information of a vehicle control client bound to the vehicle control proxy device; wherein the information of the vehicle control client bound to the vehicle control proxy device includes at least one of the following information:
- the identification information of the vehicle bound to the vehicle control client is the identification information of the vehicle bound to the vehicle control client.
- 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, and the name, manufacturer, software version, and other information of the vehicle bound to the vehicle control client device.
- the identification information of the vehicle control client device may include the name and ID of the vehicle control proxy device.
- the above-mentioned vehicle identification information may include the vehicle ID and the like.
- the car control client device includes a car client function cluster (CarClient Cluster);
- 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.
- 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.
- the vehicle control client device may also indicate the vehicle control agent bound to the vehicle control client device by other means other than clustering (such as a binding relationship table).
- the information of the bound vehicle includes at least one of the following information:
- the information of the vehicle bound to the vehicle control client device may also include Contains other information, such as the name, manufacturer, and software version of the vehicle bound to the vehicle control client device, as well as the name, manufacturer, and software version of the vehicle control agent bound to the vehicle.
- the identification information of the vehicle control agent device may include the name and ID of the vehicle control agent device.
- the car client functional cluster supports at least one of the following commands:
- Remove vehicle response used to indicate whether the unbinding of the vehicle control client device and the vehicle is completed.
- releasing the binding relationship between the first vehicle corresponding to the vehicle control proxy device and the vehicle control client device includes:
- the vehicle control proxy 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;
- the vehicle control client device receives the vehicle removal request sent by the vehicle control proxy device;
- 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;
- the vehicle control client device returns a vehicle removal response to the vehicle control proxy device;
- the vehicle removal response includes the identification information of the first vehicle, the unbinding state, and the identification information of the vehicle control client device;
- the vehicle control proxy device receives a vehicle removal response returned by the vehicle control client device
- the identification information of the vehicle control agent device in the information of the bound vehicle corresponding to the first vehicle removed by the vehicle control client device includes:
- the identification information of the vehicle control proxy device is removed from the information of the bound vehicle corresponding to the first vehicle.
- the vehicle control client device after the vehicle control client device receives the request to remove the vehicle, it is also necessary 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 request to remove the vehicle 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 request to remove the vehicle is illegal. At this time, the vehicle control client device can discard/not process the request to remove the vehicle, and/or return a binding release failure response to the vehicle control proxy device.
- 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.
- 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:
- 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;
- the vehicle control proxy device receives a remove client request sent by the vehicle control client device, where the remove client request includes identification information of the first vehicle;
- 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.
- a remove client request is sent to devices corresponding to the at least two vehicle control agents respectively.
- 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.
- 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.
- the vehicle control client device 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.
- the vehicle control client device can also establish a bound vehicle information for each of the above multiple binding relationships, and the vehicle control agents in the information of the multiple bound vehicles are different.
- a removal client request is sent to the corresponding vehicle control agent device for the information of a certain bound vehicle among the information of the multiple bound vehicles corresponding to the first vehicle.
- the vehicle control client device can also send a removal client request to the corresponding removal client device for the information of the multiple bound vehicles corresponding to the first vehicle.
- the method further includes: removing information of a bound vehicle corresponding to the first vehicle in the vehicle client function cluster.
- 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 multiple binding relationships.
- 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 releases the binding relationship, the vehicle control client device may remove the information of the bound vehicle.
- 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.
- 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.
- 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 releases the binding relationship, or when the vehicle control client is idle, the vehicle control client device can also determine whether there is other identification information of the vehicle control agent in the information of the bound vehicle after removing the identification information corresponding to the vehicle control agent device 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.
- the method further 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 identification information of the vehicle, the vehicle control proxy device may remove the information of the vehicle control client corresponding to the vehicle control client device in the vehicle proxy function cluster.
- a vehicle control client device can also bind multiple vehicles in the same vehicle control proxy device. Accordingly, in a vehicle control proxy device, a vehicle control client may be bound multiple times, and each binding corresponds to a different vehicle, that is, a vehicle control client device may have multiple binding relationships in a vehicle control proxy device. In this case, 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.
- the vehicle control proxy device can also establish information of a vehicle control client for each of the multiple binding relationships, and the information of the multiple vehicle control clients each includes identification information of a vehicle.
- the proxy device respectively establishes information of a vehicle control client for the above-mentioned multiple binding relationships, when the binding relationship between the vehicle control client device and a certain vehicle is released, the information of the vehicle control client corresponding to the binding relationship can be removed.
- the vehicle control proxy device establishes information of a single vehicle control client for the multiple binding relationships
- 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 information of the vehicle control client, or when the vehicle control proxy device is idle, the vehicle control proxy device can determine whether the identification information of the vehicle still exists in the information of the vehicle control client, and if not, remove the information of the vehicle control client; otherwise, retain the information of the vehicle control client.
- the method also includes: when the vehicle control proxy device releases the binding relationship with the vehicle control client device, the vehicle control proxy device can remove the permissions corresponding to the vehicle control client device in the access control list (ACL).
- ACL access control list
- 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.
- the vehicle control proxy device may remove the permissions of the vehicle control client device to all vehicle-related contents in the ACL, or remove all permissions of the vehicle control client device in the ACL.
- Embodiment 1 is a diagrammatic representation of Embodiment 1:
- the car client function cluster contains the following attributes, which are defined as shown in Table 2:
- carInfo structure is defined as shown in Table 3 below:
- the car client function set includes the following commands, which are defined as shown in Table 4:
- removeCarReq is used by CarAgent to remove the binding relationship between the car and the CarClient. Its parameter definition is shown in the following Table 5:
- UnbindingAllCars 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.
- CarClient After receiving removeCarReq, CarClient shall 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 parameter definition is shown in Table 6 below:
- Status is the binding status
- True means the unbinding is successful
- False means the unbinding fails.
- the car agent function set includes the following attributes, which are defined as shown in Table 7:
- FIG. 5 shows a flowchart of unbinding for vehicle management involved in this application.
- the user can unbind the CarAgent implemented on the mobile phone from the CarClient implemented in the smart TV in the home network.
- the above process may include:
- CarClient returns removeCar Response, which contains all unbound CarIDs, as well as CarClient ID and unbinding status.
- CarAgent receives 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.
- Embodiment 2 is a diagrammatic representation of Embodiment 1:
- CarAgent After receiving removeClientReq, CarAgent should delete the corresponding CarID in CarList under the corresponding ClientID in boundClients. If CarList is empty after deletion, CarAgent should delete the Entry.
- FIG. 6 shows a flowchart of unbinding for vehicle management involved in this application.
- the user can unbind the CarClient implemented in the smart TV from the CarAgent implemented on the mobile phone.
- the process may include:
- the user unbinds the car on the smart home device, and CarClient sends a removeClient Request to the CarAgent corresponding to the CarID of the car in the boundCars attribute, with the parameter being the CarID of the car.
- CarClient deletes the corresponding CarID and CarAgent in the boundCars attribute.
- CarAgent deletes the CarID of the car unbound under the corresponding ClientID in 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.
- the difference in clustering between the third embodiment and the embodiment 1 is that the carInfo structure in the car client function cluster is defined as shown in the following Table 11:
- CarClient After CarClient receives removeCarReq, if the CarAgents field corresponding to CarID contains more than one CarAgent, CarClient can delete only the corresponding CarAgent in CarAgents without deleting the Entry. If the corresponding CarAgents is empty after deleting CarAgent, CarClient can delete the Entry.
- the difference between the 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.
- FIG. 7 shows a flowchart of unbinding for vehicle management involved in this application.
- the user can unbind the two through CarAgent implemented on the mobile phone or CarClient implemented in the smart TV.
- the process may include:
- the user unbinds one or more cars from CarClient on the mobile phone, and CarAgent sends a removeCar Request to CarClient, including all unbinding or all unbound CarIDs.
- CarClient 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.
- CarClient returns removeCar Response, which contains all unbound CarIDs, as well as CarClient ID and unbinding status.
- CarAgent receives 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.
- the user unbinds the car on the smart home device, and CarClient sends a removeClient Request to all CarAgents corresponding to the CarID of the car in the boundCars attribute, with the parameter being the Car ID of the car.
- CarClient deletes the Entry corresponding to the CarID in the boundCars attribute, including CarID, CarName, and all CarAgents.
- CarAgent deletes the CarID of the car unbound under the corresponding ClientID in 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.
- FIG8 shows a block diagram of an unbinding device for vehicle management provided by an embodiment of the present application.
- the unbinding device 800 for vehicle management has the function of implementing the method shown in FIG2 or FIG4 above, which is performed by the vehicle control agent device.
- the device may include:
- 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.
- the unbinding module 801 is used to:
- the binding relationship between the vehicle control proxy device, the first vehicle and the vehicle control client device is released.
- the vehicle control proxy device includes a vehicle proxy 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.
- 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:
- the identification information of the vehicle bound to the vehicle control client is the identification information of the vehicle bound to the vehicle control client.
- the unbinding module 801 is used to:
- the remove vehicle response includes identification information of the first vehicle, an unbinding state, and identification information of the vehicle control client device;
- 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.
- the unbinding module 801 is used to:
- 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.
- the apparatus further comprises:
- the information removal module is used 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.
- the apparatus further comprises:
- the permission removal module is used to remove the permission corresponding to the vehicle control client device in the ACL.
- FIG9 shows a block diagram of an unbinding device for vehicle management provided by an embodiment of the present application.
- the unbinding device 900 for vehicle management has the function of implementing the method shown in FIG3 or FIG4 above, which is performed by the vehicle control client device.
- the device may include:
- 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.
- the unbinding module 901 is used to:
- the binding relationship between the vehicle control proxy device, the first vehicle and the vehicle control client device is released.
- 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.
- 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:
- 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.
- the unbinding module 901 is used to:
- the vehicles indicated by the vehicle removal request to be unbound from the vehicle control client device include 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.
- the unbinding module 901 is used to remove the identification information of the vehicle control proxy device from the information of the bound vehicle corresponding to the first vehicle when there is a binding relationship between the first vehicle and the vehicle control proxy device.
- the unbinding module 901 is used to:
- a client removal request is sent to the vehicle control proxy device; the client removal request includes identification information of the first vehicle.
- the apparatus further comprises:
- 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.
- 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.
- the information removal module is used to send the client removal request to devices corresponding to the at least two vehicle control agents respectively when there is identification information of at least two vehicle control agents in the information of the bound vehicle corresponding to the first vehicle.
- FIG10 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 .
- the processor 1001 includes one or more processing cores, and the processor 1001 executes various functional applications and information processing by running software programs and modules.
- the receiver 1002 and the transmitter 1003 can be implemented as a communication component, and the communication component can be a communication chip.
- the communication chip can also be called a transceiver.
- the memory 1004 is connected to the processor 1001 via a bus 1005.
- the memory 1004 can be used to store computer programs, and the processor 1001 is used to execute the computer program to implement each step in the above method embodiment.
- memory 1004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, and volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, 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.
- the processor 1001 and/or the transceiver are used to bind the vehicle control client device to the vehicle control proxy device.
- the process performed by the processor 1001 and/or the transceiver in the above-mentioned computer device 1000 can refer to the various steps performed by the vehicle control proxy device in the method shown in either FIG. 2 or FIG. 4.
- the processor 1001 and/or the transceiver are used to bind the vehicle control client device to the vehicle control proxy device.
- the process performed by the processor 1001 and/or the transceiver in the computer device 1000 can refer to the steps performed by the vehicle control client device in the method shown in any one of FIG. 3 or FIG. 4.
- An embodiment of the present application also 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 all or part of the steps performed by a vehicle control agent device or a vehicle control client device in the method shown in Figure 2, Figure 3 or Figure 4 above.
- 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 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.
- the present application also provides a computer program product, the computer program product or computer program includes computer instructions, the computer instructions 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 the processor executes the computer instructions, so that the computer device executes all or part of the steps executed 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.
- 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 a vehicle control agent device or a vehicle control client device in the method shown in Figure 2, Figure 3 or Figure 4 above.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
Abstract
一种用于车辆管理的解绑方法、装置、设备、存储介质及产品，属于物联网技术领域。该方法由控车代理设备执行，包括：解除控车代理设备与控车客户端设备之间的绑定关系(201)。上述方案提供了一种对控车代理设备与控车客户端设备之间的绑定关系的管理方案，提高了控车客户端设备通过控车代理设备对车辆进行管理的可控性。
Description
本申请涉及物联网技术领域，特别涉及一种用于车辆管理的解绑方法、装置、设备、存储介质及产品。
随着物联网(Internet of Things，IoT)技术的不断发展，越来越多的物联网设备在智能家居、工业生产等诸多领域给用户的生产生活带来了极大的便利性。
在相关技术中，车辆可以有手机等移动终端设备进行远程控制。具体的，车辆的车机设备和用户的移动终端同时接入云端服务器，并在云端服务器中绑定，后续移动终端可以通过云端服务器向车机设备发送控制指令。
发明内容
本申请实施例提供了一种用于车辆管理的解绑方法、装置、设备、存储介质及产品。所述技术方案如下：
一方面，本申请实施例提供了一种用于车辆管理的解绑方法，所述方法由控车代理设备执行，所述方法包括：
解除所述控车代理设备对应的第一车辆与控车客户端设备之间的绑定关系。
一方面，本申请实施例提供了一种用于车辆管理的解绑方法，所述方法由控车客户端设备执行，所述方法包括：
解除控车代理设备对应的第一车辆与所述控车客户端设备之间的绑定关系。
另一方面，本申请实施例提供了一种用于车辆管理的解绑装置，所述装置包括：
解绑模块，用于解除所述控车代理设备对应的第一车辆与控车客户端设备之间的绑定关系。
另一方面，本申请实施例提供了一种用于车辆管理的解绑装置，所述装置包括：
解绑模块，用于解除控车代理设备对应的第一车辆与所述控车客户端设备之间的绑定关系。
另一方面，本申请实施例提供了一种计算机设备，所述计算机设备实现为信息上报设备，所述计算机设备包括处理器、存储器和收发器；
存储器中存储有计算机程序，处理器执行所述计算机程序，以使得计算机设备实现上述用于车辆管理的解绑方法。
再一方面，本申请实施例提供了一种计算机设备，所述计算机设备包括处理器、存储器和收发器，所述存储器存储有计算机程序，所述计算机程序用于被所述处理器执行，以实现上述用于车辆管理的解绑方法。
又一方面，本申请实施例还提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序，所述计算机程序由处理器加载并执行以实现上述用于车辆管理的解绑方法。
又一方面，本申请还提供了一种芯片，该芯片包括电路结构，所述芯片用于在计算机设备中运行，以使得所述计算机设备执行上述用于车辆管理的解绑方法。
又一方面，本申请提供了一种计算机程序产品，该计算机程序产品包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行上述用于车辆管理的解绑方法。
又一方面，本申请提供了一种计算机程序，该计算机程序由计算机设备的处理器执行，以实现上述用于车辆管理的解绑方法。
通过本申请实施例提供的技术方案，控车代理设备在预先与控车客户端设备绑定，以使得控车代理设备可以提供一种代理服务，可以实现物联网系统中的控车客户端设备可以对车辆进行管理的情况下，还可以解除控车代理设备与控车客户端设备之间的绑定关系，从而提供了一种对控车代理设备与控车客户端设备之间的绑定关系的管理方案，提高了控车客户端设备通过控车代理设备对车辆进行管理的可控性。
图1是本申请一个实施例提供的物联网的网络架构的示意图；
图2是本申请一个实施例提供的用于车辆管理的解绑方法的流程图；
图3是本申请一个实施例提供的用于车辆管理的解绑方法的流程图；
图4是本申请一个实施例提供的用于车辆管理的解绑的流程框架图；
图5是本申请涉及的一种用于车辆管理的解绑的流程图；
图6是本申请涉及的一种用于车辆管理的解绑的流程图；
图7是本申请涉及的一种用于车辆管理的解绑的流程图；
图8是本申请一个实施例提供的用于车辆管理的解绑装置的框图；
图9是本申请一个实施例提供的用于车辆管理的解绑装置的框图；
图10是本申请一个实施例提供的计算机设备的结构示意图。
请参考图1，其示出了本申请一个实施例提供的物联网的网络架构的示意图。该物联网的网络架构可以包括：物联网设备110(图1中示出为物联网设备110a、物联网设备110b、物联网设备110c、物联网设备110d)、代理设备120(图1中示出为代理设备120a和代理设备120b)以及车辆130(图1中示出为车辆130a、车辆130b、车辆130c)；可选的，该网络架构还可以包括桥接设备140；可选的，该网络架构还可以包括云端服务器150。
物联网设备110可以是指在物联网中，用于提供物联网协议对应的客户端功能或者服务端功能的设备。
比如，物联网设备110可以是智能家居设备，例如，智能电视、智能音箱、智能开关、智能灯具、智能空调、智能冰箱、智能微波炉、智能电饭煲、扫地机器人等等。
或者，物联网设备110可以是工业生产设备，例如，车床、工业机器人、太阳能面板、风力发电机等等。
或者，物联网设备110可以是商业服务设备，例如，无人售货机等等。
或者，物联网设备110可以是传感设备，例如，监控摄像头、红外传感器、声音传感器、温度传感器等等。
在一种可能的实现方式中，代理设备120是用户侧的终端设备。比如，代理设备120可以是智能手机、平板电脑、智能手表等等；或者，代理设备120也可以是个人电脑，比如台式电脑、便携式计算机、个人工作站等等。
在另一种可能的实现方式中，代理设备120是指基于终端设备运行的客户端实体(可以是虚拟实体)，例如，代理设备120可以是运行在终端设备中，用于对物联网设备进行访问、控制、以及管理等操作的应用程序(Application，APP)。
车辆130可以是具有与代理设备120进行通信的功能的车辆/车载设备，比如，车辆130可以车载设备(比如车机设备)等等。
其中，上述代理设备120可以通过云端服务器150，与车辆130建立连接。
桥接设备140用于实现支持不同物联网协议的两个设备之间的交互。桥接设备140在支
持不同物联网协议的物联网设备110之间，或者，在支持不同物联网协议的物联网设备110和代理设备120之间，提供信息转换和传递的服务。
桥接设备140可以是专用于进行桥接的设备，或者，桥接设备140也可以是具有桥接功能的智能设备，比如网关或者路由器等等。
云端服务器150用于提供物联网设备110与物联网生态之外的其它设备(比如上述代理设备120)之间的连接服务。其中，云端服务器150可以是物联网生态的云端平台服务器。
其中，代理设备120也可以直接与物联网设备110建立连接。
或者，代理设备120可以也通过云端服务器150，与物联网设备110建立连接。
或者，代理设备120可以也通过桥接设备140，与物联网设备110建立连接。
在本申请实施例中，上述物联网设备110、代理设备120、桥接设备140可以是满足相同或者不同的物联网协议的电子设备，比如，可以是满足连接标准联盟(Connectivity Standards Alliance，CSA)下的Matter协议的电子设备。
在图1中，当物联网设备110a和物联网设备110c之间支持相同的协议规范时，物联网设备110a和物联网设备110c之间可以建立安全连接，比如，基于Matter规范建立安全连接。
当物联网设备110b和物联网设备110d之间支持不同的协议规范，比如，物联网设备110b是Zigbee设备，而物联网设备110d是Matter设备时，物联网设备110b和物联网设备110d之间可以通过桥接设备140相连。
目前物联网中的解绑技术如下：
1)车控家解绑
解除绑定分为长期绑定关系的解除和临时绑定关系的解除。长期绑定关系可以分为IOTClient主动发起的绑定关系解除和IOTAgent主动发起的绑定关系解除。临时绑定并不记录在IOTAgent上的的smarthomebindingcluster中，因此临时绑定的解除分为用户主动发起的在IOTClient上清除绑定标识和IOTClient检测到连接丢失后的被动清除绑定标识。
IOTClient主动发起的绑定关系解除：
S1，用户在IOTClient发起解除长期绑定。
S2，IOTClient删除IOTClient中对应的绑定信息以及设备列表等信息。
S3，IOTClient通知IOTAgent中smarthomebinding cluster中的绑定信息。
S4，IOTAgent删除绑定关系。
S5，通知IOTClient绑定关系已删除。
IOTAgent主动发起的绑定关系解除：
S6，用户在IOTAgent发起解除长期绑定。
S7，IOTAgent删除smarthomebinding cluster中的绑定信息以及设备列表等信息。
S8，IOTAgent通知IOTClient删除绑定信息。
S9，IOTAgent删除绑定信息。
主动解除临时绑定：
S10，如果是临时绑定,当用户主动发起结束绑定关系时，IOTClient删除自身的绑定标识和可控设备列表。
S11，IOTClient发起结束连接。
被动解除临时绑定：
S12，如果是临时绑定，当IOTClient检测到底层连接丢失。
S13，IOTClient自动删除自身的绑定标识和可控设备列表。
2)Matter RemoveFibric命令
管理员使用此命令删除给定的Fabric和删除所有关联的Fabric-scoped的数据。
如果要删除的给定的Fabric是最后一个引用存储在受信任根证书列表中的给定受信任根
CA证书,则应删除该受信任根证书。
命令参数如下述表1所示：
表1
FabricIndex字段包含与要从设备中删除的Fabric相关的Fabric索引参考。
如果FabricIndex字段与Fabrics中任意条目的FabricIndex都不匹配，则状态码为InvalidFabricIndex的NOCResponse应为命令响应，并且不得对任何设备数据进行任何永久性的更改，否则将会出现以下结果之一：
1.如果FabricIndex与Fabrics列表中最后剩余的条目匹配，则设备应删除节点上自配置以来创建的所有与Matter相关的数据。这包括所有Fabric-Scoped数据，包括访问控制列表(Access Control Lists，ACL)、绑定、场景、组密钥、操作证书等。所有受信任的根也需删除。任何与事务相关的数据，包括日志、安全会话、交换和交互模型结构，也应被删除。由于此操作涉及删除可能支持当前交换集的安全会话数据，因此调用命令的节点在终止与目标的安全会话之前不应期待响应。
2.如果FabricIndex不等于访问Fabric索引，则设备应开始不可撤销地删除所有关联Fabric-scoped数据的过程，包括访问控制列表、绑定、组密钥、操作证书等。任何操作证书不再引用的任何剩余可信根也应被删除。所有与给定Fabric下的操作身份相关的安全会话、交换和交互模型结构也应被删除。删除后，应返回一个状态码为Ok的NOCResponse。
3.如果FabricIndex等于访问Fabric索引，则设备应开始不可撤销地删除所有关联Fabric-scoped数据数据的过程，包括访问控制条目、绑定、组密钥、操作证书等。任何操作证书不再引用的剩余可信根也应被删除。所有与给定Fabric下的操作身份相关的安全会话、交换和交互模型结构也应被删除。由于此操作涉及删除可能支持当前交换集的安全会话数据，因此调用命令的节点在终止与目标的安全会话之前不应期望响应。
请参考图2，其示出了本申请一个实施例提供的用于车辆管理的解绑方法的流程图，该方法可以由控车代理设备执行，比如，该控车代理设备可以是图1所示的网络架构中的代理设备120；该方法可以包括如下步骤：
步骤201，控车代理设备解除控车代理设备与控车客户端设备之间的绑定关系。
在一些实施例中，控车客户端设备与控车代理设备之间的绑定关系，可以是指第一车辆与控车客户端设备之间的绑定关系。比如，上述控车客户端设备与控车代理设备之间的绑定关系，可以是在控车代理设备和/或控车客户端设备中建立的，上述第一车辆与控车客户端设备之间的绑定关系，上述绑定关系可以通过绑定项目(比如一个绑定关系表，或者，一个群集中的属性/参数)的形式存储在控车代理设备和/或控车客户端设备中。
其中，上述第一车辆是控车代理设备对应的车辆。比如，上述第一车辆是与控车代理设备在云端绑定的车辆，或者，上述第一车辆是与控车代理设备建立有连接的车辆。
在上述实施例中，解除控车代理设备与控车客户端设备之间的绑定关系，可以是指解除第一车辆与控车客户端设备之间的绑定关系。比如，删除控车客户端设备与第一车辆之间的绑定项目，或者，删除控车客户端设备与第一车辆之间的绑定项目中的信息。
比如，上述步骤201是指控车代理设备在本地解除第一车辆与控车客户端设备之间的绑定关系，并触发控车客户端设备解除上述控车客户端设备中的第一车辆与控车客户端设备之间的绑定关系。
或者，上述步骤201是指控车代理设备在控车客户端设备的触发下，在本地解除第一车辆与控车客户端设备之间的绑定关系。
在一些实施例中，控车客户端设备与控车代理设备之间的绑定关系，可以是指控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系。比如，上述控车客户端设备与控车代理设备之间的绑定关系，可以是在控车代理设备和/或控车客户端设备中建立的，上述控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系。
在上述实施例中，解除控车代理设备与控车客户端设备之间的绑定关系，可以是指解除控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系。
比如，上述步骤201是指控车代理设备在本地解除控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系，并触发控车客户端设备解除上述控车客户端设备中的控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系。
或者，上述步骤201是指控车代理设备在控车客户端设备的触发下，在本地解除控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系。
其中，上述控车代理设备可以对应至少一个车辆，该至少一个车辆中包含上述第一车辆。
其中，上述控车客户端设备可以是物联网设备，比如上述图1所示的网络架构中的物联网设备110。
例如，上述控车客户端设备可以是智能电视、智能冰箱等物联网设备。
其中，上述将控车客户端设备与控车代理设备绑定，可以用于支持控车代理设备向控车客户端设备提供对第一车辆进行管理的代理服务。
比如，上述控车代理设备可以分别与控车客户端设备以及第一车辆建立连接，当用户需要通过控车客户端设备对第一车辆进行管理时，控车代理设备可以作为控车客户端设备和第一车辆之间的代理，根据控车客户端设备对第一车辆的管理请求，对第一车辆进行管理。
也就是说，上述管理请求由控车客户端设备发送给控车代理设备，然后，控车代理设备根据该管理请求，提供对第一车辆进行管理的服务，从而实现了通过物联网设备实现对车辆的管理功能。
在一些实施例中，上述管理包括以下至少一种：
对第一车辆进行控制；
对第一车辆的状态信息进行查看；
对第一车辆的状态信息进行订阅。
其中，对第一车辆进行控制，可以是指控车代理设备根据控车客户端设备发送的管理请求，向第一车辆发送控制指令，以便第一车辆执行该控制指令，从而实现对第一车辆的控制。
在一些实施例中，上述控制指令可以是锁车/解锁、打开/关闭车窗、打开/关闭空调、打开/关闭座椅加热等指令。
上述对第一车辆的状态信息查看，可以是指控车代理设备根据控车客户端设备发送的管理请求，单次向控车客户端设备返回第一车辆的状态信息。
上述对第一车辆的状态信息进行订阅，可以是指控车代理设备根据控车客户端设备发送的管理请求，向控车客户端设备返回第一车辆的状态信息，且后续检测到第一车辆的状态信息发生更新时，将第一车辆的状态信息中发生更新的部分通知给控车客户端设备。
在一些实施例中，上述第一车辆的状态信息可以由控车代理设备接收到管理请求时，向第一车辆获取的实时的状态信息；或者，上述第一车辆的状态信息也可以是由控车代理设备预先向第一车辆获取或订阅，并存储在控车代理设备本地的状态信息。
上述第一车辆的状态信息，可以指示第一车辆的各种状态，比如，锁车/解锁状态、车窗的开启/关闭状态、空调的开启/关闭状态、剩余电量/剩余燃油量、车内温度等等。
在一些实施例中，除了上述对第一车辆进行控制、对第一车辆的状态信息进行查看和订阅之外，还可以有其它的管理方式，比如，取消对第一车辆的状态信息的订阅等等。本申请各个实施例对于上述管理的方式不做限定。
在一些实施例中，为了支持控车代理设备向控车客户端设备提供对第一车辆进行管理的
代理服务，可以预先在控车代理设备中将第一车辆与控车客户端设备绑定，和/或，在控车客户端设备中，将第一车辆与控车代理设备绑定。
在一些实施例中，为了提高控车代理设备向控车客户端设备提供对第一车辆进行管理的代理服务的安全性和可控性，可以对控车代理设备与控车客户端设备之间的绑定关系进行解除。
综上所述，在本申请实施例中，控车代理设备在预先与控车客户端设备绑定，以使得控车代理设备可以提供一种代理服务，可以实现物联网系统中的控车客户端设备可以对车辆进行管理的情况下，还可以解除控车代理设备与控车客户端设备之间的绑定关系，从而提供了一种对控车代理设备与控车客户端设备之间的绑定关系的管理方案，提高了控车客户端设备通过控车代理设备对车辆进行管理的可控性。
请参考图3，其示出了本申请一个实施例提供的用于车辆管理的解绑方法的流程图，该方法可以由控车客户端设备执行，比如，该控车客户端设备可以是图1所示的网络架构中的物联网设备110；该方法可以包括如下步骤：
步骤301，控车客户端设备解除控车代理设备与控车客户端设备之间的绑定关系。
在一些实施例中，控车客户端设备与控车代理设备之间的绑定关系，可以是指第一车辆与控车客户端设备之间的绑定关系。
其中，上述第一车辆是控车代理设备对应的车辆。
在上述实施例中，解除控车代理设备与控车客户端设备之间的绑定关系，可以是指解除第一车辆与控车客户端设备之间的绑定关系。
比如，上述步骤301是指控车客户端设备在本地解除第一车辆与控车客户端设备之间的绑定关系，并触发控车代理设备解除上述控车代理设备中的第一车辆与控车客户端设备之间的绑定关系。
或者，上述步骤301是指控车客户端设备在控车代理设备的触发下，在本地解除第一车辆与控车客户端设备之间的绑定关系。
在一些实施例中，控车客户端设备与控车代理设备之间的绑定关系，可以是指控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系。
在上述实施例中，解除控车代理设备与控车客户端设备之间的绑定关系，可以是指解除控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系。
比如，上述步骤301是指控车客户端设备在本地解除控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系，并触发控车代理设备解除上述控车代理设备中的控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系。
或者，上述步骤301是指控车客户端设备在控车代理设备的触发下，在本地解除控车客户端设备、控车代理设备以及第一车辆三者之间的绑定关系。
综上所述，在本申请实施例中，控车客户端设备在预先与控车代理设备绑定，以使得控车代理设备可以提供一种代理服务，可以实现物联网系统中的控车客户端设备可以对车辆进行管理的情况下，还可以解除控车代理设备与控车客户端设备之间的绑定关系，从而提供了一种对控车代理设备与控车客户端设备之间的绑定关系的管理方案，提高了控车客户端设备通过控车代理设备对车辆进行管理的可控性。
请参考图4，其示出了本申请一个实施例提供的用于车辆管理的解绑方法的流程图，该方法可以由控车代理设备和控车客户端设备交互执行，该控车代理设备和控车客户端设备可以分别是图1所示的网络架构中的代理设备120和物联网设备110；该方法可以包括如下几个步骤：
步骤401，控车代理设备与控车客户端设备之间建立连接。
在一些实施例中，控车代理设备与控车客户端设备之间建立连接，可以是指控车代理设备与控车客户端设备之间建立数据通道。
在本申请实施例中，在控车代理设备与控车客户端设备之间存在绑定关系的情况下，控车代理设备可以向控车客户端设备提供对第一车辆进行管理的代理服务；相应的，控车管理设备通过控车代理设备对第一车辆进行管理。
步骤402，控车代理设备解除控车代理设备与控车客户端设备之间的绑定关系；控车客户端设备解除控车代理设备与控车客户端设备之间的绑定关系。
在本申请实施例中，如果控车客户端设备已经与控车代理设备绑定，则控车代理设备与控车客户端设备之间还可以解除相互之间的绑定关系。
其中，上述解除控车代理设备与控车客户端设备之间的绑定关系的步骤，可以由用户在控车代理设备或者控车客户端设备侧发起确认，用户确认是否发起解绑的步骤，可以在步骤402之前执行，也可以在步骤401之前执行。
在一些实施例中，控车代理设备中包含车代理功能群集(CarAgent Cluster)；车代理功能群集指示控车代理设备对应的车辆与控车客户端之间的绑定关系。或者说，上述车代理功能群集指示与控车代理设备绑定的控车客户端。
在本申请实施例中，控车代理设备中可以设置一个群集，用来存储和维护与控车代理设备绑定的控车客户端。
在一些实施例中，控车代理设备也可以通过群集之外的其它方式(比如绑定关系表)来指示与控车代理设备绑定的控车客户端。
其中，一个控车代理设备可以绑定多个控车客户端，每个控车客户端可以对应一个控车客户端设备。相应的，一个控车客户端设备可以绑定多个控车代理，每个控车代理可以对应一个控车代理设备。
在一些实施例中，车代理功能群集中包含与控车代理设备绑定的控车客户端的信息；其中，与控车代理设备绑定的控车客户端的信息，包括以下信息中的至少一种：
与控车代理设备绑定的控车客户端的标识信息；
与控车代理设备绑定的控车客户端的绑定类型的信息；
与控车客户端绑定的车辆的标识信息。
在本申请实施例中，除了上述信息之外，与控车代理设备绑定的控车客户端的信息还可以包含其它信息，比如，与控车代理设备绑定的控车客户端的名称、生产厂商、软件版本，以及，与控车客户端设备绑定的车辆的名称、生产厂商、软件版本等信息。
其中，上述控车客户端设备的标识信息可以包括控车代理设备的名称、ID等等。
上述车辆的标识信息可以包括车辆的ID等等。
在一些实施例中，控车客户端设备中包含车客户端功能群集(CarClient Cluster)；
车客户端功能群集指示各个控车代理对应的车辆与控车客户端之间的绑定关系；或者说，车客户端功能群集指示与控车客户端设备绑定的控车代理。
在本申请实施例中，控车客户端设备中页可以设置一个群集，用来存储和维护与控车客户端设备绑定的控车代理。
在一些实施例中，控车客户端设备也可以通过群集之外的其它方式(比如绑定关系表)来指示与控车客户端设备绑定的控车代理。
在一些实施例中，车客户端功能群集中包含与已绑定的车辆的信息；
其中，已绑定的车辆的信息，包括以下信息中的至少一种：
与控车客户端设备绑定的车辆的标识信息；
与控车客户端设备绑定的车辆的名称；
与车辆绑定的控车代理的标识信息。
在本申请实施例中，除了上述信息之外，与控车客户端设备绑定的车辆的信息还可以包
含其它信息，比如，与控车客户端设备绑定的车辆的名称、生产厂商、软件版本，以及，与车辆绑定的控车代理的名称、生产厂商、软件版本等信息。
其中，上述控车代理设备的标识信息可以包括控车代理设备的名称、ID等等。
在一些实施例中，车客户端功能群集支持以下命令中的至少一种：
移除车请求，用于指示与控车客户端设备解除绑定的车辆；
移除车响应，用于指示是否完成控车客户端设备与车辆的解绑。
在一些实施例中，解除控车代理设备对应的第一车辆与控车客户端设备之间的绑定关系，包括：
控车代理设备向控车客户端设备发送移除车请求；移除车请求所指示的与控车客户端设备解除绑定的车辆中包含第一车辆；
控车客户端设备接收控车代理设备发送的移除车请求；
控车客户端设备移除第一车辆对应的已绑定的车辆的信息中，控车代理设备的标识信息；
控车客户端设备向控车代理设备返回移除车响应；移除车响应中包含第一车辆的标识信息、解绑状态、控车客户端设备的标识信息；
控车代理设备接收控车客户端设备返回的移除车响应；
控车代理设备在解绑状态为解绑成功的情况下，移除车代理功能群集中与控车客户端设备对应的控车客户端的信息中的第一车辆的标识信息。
在一些实施例中，控车客户端设备移除第一车辆对应的已绑定的车辆的信息中，控车代理设备的标识信息，包括：
在第一车辆与控车代理设备之间存在绑定关系的情况下，移除第一车辆对应的已绑定的车辆的信息中，控车代理设备的标识信息。
在本申请实施例中，控车客户端设备接收到移除车请求后，还需要检测第一车辆与控车代理设备之间是否存在绑定关系，如果第一车辆与控车代理设备之间存在绑定关系，则说明该移除车请求是合法的请求，此时，控车客户端设备可以移除第一车辆对应的已绑定的车辆的信息中，控车代理设备的标识信息；反之，如果第一车辆与控车代理设备之间不存在绑定关系，则说明该移除车请求不合法，此时，控车客户端设备可以丢弃/不处理该移除车请求，和/或，向控车代理设备返回绑定解除失败响应。
在一些实施例中，控车客户端设备接收到移除车请求后，也可以在不检测第一车辆与控车代理设备之间是否存在绑定关系的情况下，移除第一车辆对应的已绑定的车辆的信息中，控车代理设备的标识信息；此时，检测第一车辆与控车代理设备之间是否存在绑定关系的步骤可以在控车代理设备中执行，比如，控车代理设备在发送移除车请求之前，先检测第一车辆与控车代理设备是否存在绑定关系，若是，则发送该移除车请求，否则不发送该移除车请求。
在一些实施例中，车代理功能群集支持移除客户端请求；移除客户端请求用于控车客户端移除与车辆的绑定。
在一些实施例中，解除控车代理设备对应的第一车辆与控车客户端设备之间的绑定关系的过程可以包括：
控车客户端设备移除第一车辆对应的已绑定的车辆的信息中，控车代理设备的标识信息；
控车客户端设备向控车代理设备发送移除客户端请求；移除客户端请求中包含第一车辆的标识信息；
控车代理设备接收控车客户端设备发送的移除客户端请求，移除客户端请求中包含第一车辆的标识信息；
控车代理设备移除车代理功能群集中与控车客户端设备对应的控车客户端的信息中的第一车辆的标识信息。
在一些实施例中，控车客户端设备向控车代理设备发送移除客户端请求，包括：
在与第一车辆对应的已绑定的车辆的信息中，存在至少两个控车代理的标识信息的情况下，向至少两个控车代理对应的设备分别发送移除客户端请求。
在本申请实施例中，一个车辆可以被多个控车代理绑定，相应的，在一个控车客户端设备中，可以能存在一个车辆被绑定多次，且每次绑定对应不同的控车代理的情况，也就是一个车辆在一个控车客户端设备中可以存在多个绑定关系，在这种情况下，对应同一车辆的多个绑定关系可以存储在一个已绑定的车辆的信息中。此时，控车客户端设备主动发起解除与第一车辆的绑定关系时，由于存在多个对应的控车代理，此时，控车客户端设备可以向上述多个控车代理分别对应的控车代理设备发送上述移除客户端请求，从而实现对同一车辆对应的绑定关系的批量删除。或者，控车客户端设备主动发起解除与第一车辆的绑定关系时，也可以针对与第一车辆对应的已绑定的车辆的信息中的某一个控车代理，向对应的控车代理设备发送移除客户端请求。
此外，当一个车辆在一个控车客户端设备中存在多个绑定关系的情况下，控车客户端设备也可以对上述多个绑定关系分别建立一个已绑定的车辆的信息，该多个已绑定的车辆的信息中的控车代理各不相同。在这种情况下，控车客户端设备主动发起解除与第一车辆的绑定关系时，针对与第一车辆对应的多个已绑定的车辆的信息中，某一个已绑定的车辆的信息，向对应的控车代理设备发送移除客户端请求。或者，控车客户端设备也可以针对与第一车辆对应的多个已绑定的车辆的信息，分别向对应的移除客户端设备发送移除客户端请求。
在一些实施例中，该方法还包括：将车客户端功能群集中与第一车辆对应的已绑定的车辆的信息移除。
在上述实施例中，在一个车辆在一个控车客户端设备中可以存在多个绑定关系，且控车客户端设备对上述多个绑定关系分别建立一个已绑定的车辆的信息的情况下，当控车客户端设备基于某一个绑定关系对应的已绑定的车辆的信息发送移除客户端请求，并成功解除绑定关系后，控车客户端设备可以将该已绑定的车辆的信息移除。
在一些实施例中，将车客户端功能群集中与第一车辆对应的已绑定的车辆的信息移除，包括：在与第一车辆对应的已绑定的车辆的信息中，不存在控车代理的标识信息的情况，将车客户端功能群集中与第一车辆对应的已绑定的车辆的信息移除。
在上述实施例的一种可能实现方案中，在一个车辆在一个控车客户端设备中可以存在多个绑定关系，且控车客户端设备对上述多个绑定关系建立单个已绑定的车辆的信息的情况下，当控车客户端设备基于某一个绑定关系对应的已绑定的车辆的信息发送移除客户端请求，并成功解除绑定关系后，或者，在控车客户端空闲时，控车客户端设备在将该已绑定的车辆的信息中对应该控车代理设备的标识信息移除后，还可以判断该已绑定的车辆的信息中是否还存在其他的控车代理的标识信息，若不存在，则移除该已绑定的车辆的信息；否则，保留该已绑定的车辆的信息。
在一些实施例中，上述方法还包括：若车代理功能群集中与控车客户端设备对应的控车客户端的信息中不包含车辆的标识信息，控车代理设备可以将车代理功能群集中与控车客户端设备对应的控车客户端的信息移除。
在本申请实施例中，一个控车客户端设备也可以在同一个控车代理设备中绑定多个车辆，相应的，在一个控车代理设备中，可以能存在一个控车客户端被绑定多次，且每次绑定对应不同的车辆的情况，也就是一个控车客户端设备在一个控车代理设备中可以存在多个绑定关系，在这种情况下，对应同一控车客户端设备的多个绑定关系可以存储在一个控车客户端的信息中。也就是说，一个控车客户端的信息中，可以包含多个车辆的标识信息。
此外，当一个控车客户端设备在一个控车代理设备中存在多个绑定关系的情况下，控车代理设备也可以对上述多个绑定关系分别建立一个控车客户端的信息，该多个控车客户端的信息分别包含一个车辆的标识信息。
在上述实施例中，在控车客户端设备在一个控车代理设备中存在多个绑定关系，且控车
代理设备对上述多个绑定关系分别建立一个控车客户端的信息的情况下，当解除控车客户端设备与某个车辆的绑定关系时，可以将该绑定关系对应的控车客户端的信息移除。
而在控车客户端设备在一个控车代理设备中存在多个绑定关系，且控车代理设备对上述多个绑定关系建立单个控车客户端的信息的情况下，当解除控车客户端设备与某个车辆的绑定关系时，可以将该车辆的标识信息从控车客户端设备对应的控车客户端的信息中删除；在控车代理设备每次从上述控车客户端的信息中删除一个车辆的标识信息，或者，当控车代理设备空闲时，控车代理设备可以判断该控车客户端的信息中是否还存在车辆的标识信息，若不存在，移除该控车客户端的信息；否则，保留控车客户端的信息。
在一些实施例中，该方法还包括：控车代理设备在解除与控车客户端设备的绑定关系的情况下，可以移除访问控制列(Access Control List，ACL)中与控车客户端设备对应的权限。
比如，当控车代理设备解除控车客户端设备与第一车辆之间的绑定关系的情况下，控车代理设备可以移除ACL中，控车客户端设备对第一车辆相关的内容的权限。
再比如，当控车代理设备移除了控车客户端设备对应的控车客户端的信息时，控车代理设备可以移除ACL中，控车客户端设备对所有车辆相关的内容的权限，或者，移除ACL中控车客户端设备的全部权限。
实施例一：
(1)智能家居设备上实现车客户端功能群集CarClient Cluster，用于记录CarClient绑定的车和CarAgent。
车客户端功能群集包含以下属性，定义如下表2所示：
表2
其中，carInfo结构体定义如下表3所示：
表3
车客户端功能集包含以下命令，定义如下表4所示：
表4
其中，removeCarReq用于CarAgent解除车与该CarClient的绑定关系。其参数定义如下表5所示：
表5
当UnbindingAllCars为True时，表示解除CarAgent所对应的全部车的绑定关系，此时忽略CarList参数的值；当UnbindingAllCars为False时，表示解除CarList所列出的车的绑定关系。
CarClient接收到removeCarReq后，应校验发送方是否与CarID存在绑定关系。若不存在绑定关系，则返回错误码。若存在绑定关系，则返回bindCarResp，其参数定义如下表6所示：
表6
其中，Status为绑定状态，True为解绑成功，False为解绑失败。
(2)手机上实现车代理功能集CarAgent Cluster，记录了绑定的CarClient。
车代理功能集包含以下属性，定义如下表7所示：
表7
其中，clientInfo结构体定义如下表8所示：
表8
其中，ClientType为该客户端的绑定类型，True为长期绑定，False为临时绑定。
请参考图5，其示出了本申请涉及的一种用于车辆管理的解绑的流程图。在本实施例中，用户可通过手机上实现的CarAgent与家庭网络中智能电视中实现的CarClient进行解绑，上述流程可以包括：
S1，CarClient与CarAgent双方已绑定并建立数据通道。
解绑流程：
S2，用户在手机上解除一个车或多个车与CarClient的绑定，CarAgent向CarClient发送removeCar Request，包含全部解绑或所有解绑的车的CarID。
S3，CarClient接收到removeCarReq后，校验CarAgent与CarID存在绑定关系，则删除boundCars属性中对应CarID及CarAgent。
S4，CarClient返回removeCar Response，包含所有解绑的CarID，以及CarClient ID和解绑状态。
S5，CarAgent收到removeCar Response，删除boundClients属性中相应ClientID下解绑的CarID，若ClientID下已无CarID，则删除该ClientID，并清除ACL中该客户端的相应权限。
实施例二：
与上述实施例一相比，在群集上的区别在于，车代理功能集包含以下命令，定义如下表9所示：
表9
其中，removeClientReq用于CarClient解除与一个车的绑定关系。该解除绑定的车用CarID标识。
removeClientReq参数定义如下表10所示：
表10
CarAgent收到removeClientReq后，应删除boundClients中相应ClientID下CarList中对应的CarID。若删除后CarList为空，则CarAgent应删除该Entry。
请参考图6，其示出了本申请涉及的一种用于车辆管理的解绑的流程图。在本实施例中，用户可通过智能电视中实现的CarClient与手机上实现的CarAgent进行解绑，该流程可以包括：
S1，CarClient与CarAgent双方已绑定并建立数据通道。
解绑流程：
S2，用户在智能家居设备上解除与车的绑定，CarClient向boundCars属性中该车的CarID对应的CarAgent发送removeClient Request，其参数为该车的CarID。
S3，CarClient删除boundCars属性中对应CarID及CarAgent。
S4，用户在手机上确认后，CarAgent在boundClients列表中删除相应ClientID下解绑的车的CarID，若ClientID下的CarList中已无CarID，则删除该ClientID，并清除ACL中该客户端的相应权限。
实施例三：
该实施例三与上述实施例一相比，在群集上的区别在于，车客户端功能群集中carInfo结构体定义如下表11所示：
表11
CarClient接收到removeCarReq后，若CarID对应的CarAgents字段包含不止一个CarAgent，CarClient可以仅删除CarAgents中的相应CarAgent，而无需删除该Entry。若删除CarAgent后相应的CarAgents为空，则CarClient可以删除该Entry。
该实施例三与上述实施例二相比，区别在于：若车代理功能群集中，CarID对应的CarAgents字段包含不止一个CarAgent，CarClient可以向CarAgents中的每一个CarAgent发送该请求。之后，CarClient可以删除该CarID对应的Entry。
请参考图7，其示出了本申请涉及的一种用于车辆管理的解绑的流程图。在本实施例中，用户可分别通过手机上实现的CarAgent或智能电视中实现的CarClient实现二者的解绑，该流程可以包括：
S1，CarClient与CarAgent双方已绑定并建立数据通道。
解绑流程：
(1)CarAgent发起解绑
S2，用户在手机上解除一个车或多个车与CarClient的绑定，CarAgent向CarClient发送removeCar Request，包含全部解绑或所有解绑的CarID。
S3，CarClient接收到removeCarReq后，校验CarAgent与CarID存在绑定关系，则删除boundCars属性中对应CarID下的CarAgent，若CarID下已无CarAgent，则删除该CarID。
S4，CarClient返回removeCar Response，包含所有解绑的CarID，以及CarClient ID和解绑状态。
S5，CarAgent收到removeCar Response，删除boundClients属性中相应ClientID下解绑的CarID，若ClientID下已无CarID，则删除该ClientID，并清除ACL中该客户端的相应权限。
(2)CarClient发起解绑
S6，用户在智能家居设备上解除与车的绑定，CarClient向boundCars属性中该车的CarID对应的所有CarAgent发送removeClient Request，参数为该车的Car ID。
S7，CarClient删除boundCars属性中该CarID对应的Entry，包含CarID、CarName及全部CarAgent。
S8，用户在手机上确认后，CarAgent在boundClients列表中删除相应ClientID下解绑的车的CarID，若ClientID下的CarList中已无CarID，则删除该ClientID，并清除ACL中该客户端的相应权限。
请参考图8，其示出了本申请一个实施例提供的用于车辆管理的解绑装置的框图。该用于车辆管理的解绑装置800具有实现上述图2或图4所示的方法中，由控车代理设备执行的功能。如图8所示，该装置可以包括：
解绑模块801，用于控车代理设备解除所述控车代理设备与控车客户端设备之间的绑定关系。
在一些实施例中，所述解绑模块801，用于，
解除第一车辆与控车客户端设备之间的绑定关系；
或者，解除所述控车代理设备、第一车辆以及控车客户端设备之间的绑定关系。
在一些实施例中，所述控车代理设备中包含车代理功能群集；
所述车代理功能群集指示所述控车代理设备对应的车辆与控车客户端之间的绑定关系。
在一些实施例中，所述车代理功能群集中包含与所述控车代理设备绑定的控车客户端的信息；
其中，与所述控车代理设备绑定的控车客户端的信息，包括以下信息中的至少一种：
与所述控车代理设备绑定的控车客户端的标识信息；
与所述控车代理设备绑定的控车客户端的绑定类型的信息；
与所述控车客户端绑定的车辆的标识信息。
在一些实施例中，所述解绑模块801，用于，
向所述控车客户端设备发送移除车请求；所述移除车请求所指示的与所述控车客户端设备解除绑定的车辆中包含所述第一车辆；
接收所述控车客户端设备返回的移除车响应；所述移除车响应中包含所述第一车辆的标识信息、解绑状态、所述控车客户端设备的标识信息；
在所述解绑状态为解绑成功的情况下，移除所述车代理功能群集中与所述控车客户端设备对应的控车客户端的信息中的所述第一车辆的标识信息。
在一些实施例中，所述车代理功能群集支持移除客户端请求；所述移除客户端请求用于控车客户端移除与车辆的绑定。
在一些实施例中，所述解绑模块801，用于，
接收所述控车客户端设备发送的所述移除客户端请求，所述移除客户端请求中包含所述
第一车辆的标识信息；
移除所述车代理功能群集中与所述控车客户端设备对应的控车客户端的信息中的所述第一车辆的标识信息。
在一些实施例中，所述装置还包括：
信息移除模块，用于若所述车代理功能群集中与所述控车客户端设备对应的控车客户端的信息中不包含车辆的标识信息，将所述车代理功能群集中与所述控车客户端设备对应的控车客户端的信息移除。
在一些实施例中，所述装置还包括：
权限移除模块，用于移除ACL中与所述控车客户端设备对应的权限。
请参考图9，其示出了本申请一个实施例提供的用于车辆管理的解绑装置的框图。该用于车辆管理的解绑装置900具有实现上述图3或图4所示的方法中，由控车客户端设备执行的功能。如图9所示，该装置可以包括：
解绑模块901，用于控车客户端设备解除控车代理设备与所述控车客户端设备之间的绑定关系。
在一些实施例中，所述解绑模块901，用于，
解除第一车辆与所述控车客户端设备之间的绑定关系；
或者，解除所述控车代理设备、第一车辆以及控车客户端设备之间的绑定关系。
在一些实施例中，所述控车客户端设备中包含车客户端功能群集；
所述车客户端功能群集指示各个控车代理对应的车辆与所述控车客户端之间的绑定关系。
在一些实施例中，所述车客户端功能群集中包含与已绑定的车辆的信息；
其中，所述已绑定的车辆的信息，包括以下信息中的至少一种：
与所述控车客户端设备绑定的车辆的标识信息；
与所述控车客户端设备绑定的车辆的名称；
与所述车辆绑定的控车代理的标识信息。
在一些实施例中，所述车客户端功能群集支持以下命令中的至少一种：
移除车请求，用于指示与所述控车客户端设备解除绑定的车辆；
移除车响应，用于指示是否完成所述控车客户端设备与车辆的解绑。
在一些实施例中，所述解绑模块901，用于，
接收所述控车代理设备发送的移除车请求；所述移除车请求所指示的与所述控车客户端设备解除绑定的车辆中包含所述第一车辆；
移除所述第一车辆对应的已绑定的车辆的信息中，所述控车代理设备的标识信息；
向所述控车代理设备返回移除车响应；所述移除车响应中包含所述第一车辆的标识信息、解绑状态、所述控车客户端设备的标识信息。
在一些实施例中，所述解绑模块901，用于在所述第一车辆与所述控车代理设备之间存在绑定关系的情况下，移除所述第一车辆对应的已绑定的车辆的信息中，所述控车代理设备的标识信息。
在一些实施例中，所述解绑模块901，用于，
移除所述第一车辆对应的已绑定的车辆的信息中，所述控车代理设备的标识信息；
向所述控车代理设备发送移除客户端请求；所述移除客户端请求中包含所述第一车辆的标识信息。
在一些实施例中，所述装置还包括：
信息移除模块，用于将所述车客户端功能群集中与所述第一车辆对应的已绑定的车辆的信息移除。
在一些实施例中，所述信息移除模块，用于在与所述第一车辆对应的已绑定的车辆的信息中，不存在控车代理的标识信息的情况，将所述车客户端功能群集中与所述第一车辆对应的已绑定的车辆的信息移除。
在一些实施例中，所述信息移除模块，用于在与所述第一车辆对应的已绑定的车辆的信息中，存在至少两个控车代理的标识信息的情况下，向所述至少两个控车代理对应的设备分别发送所述移除客户端请求。
请参考图10，其示出了本申请一个实施例提供的计算机设备1000的结构示意图。该计算机设备1000可以包括：处理器1001、接收器1002、发射器1003、存储器1004和总线1005。
处理器1001包括一个或者一个以上处理核心，处理器1001通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。接收器1002和发射器1003可以实现为一个通信组件，该通信组件可以是一块通信芯片。该通信芯片也可以称为收发器。存储器1004通过总线1005与处理器1001相连。存储器1004可用于存储计算机程序，处理器1001用于执行该计算机程序，以实现上述方法实施例中的各个步骤。
此外，存储器1004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器，可擦除可编程只读存储器，静态随时存取存储器，只读存储器，磁存储器，快闪存储器，可编程只读存储器。
在一个示例性的方案中，当计算机设备1000实现为上述控车代理设备时，所述处理器1001和/或收发器，用于将所述控车客户端设备与控车代理设备绑定。其中，上述计算机设备1000中的处理器1001和/或收发器执行的过程可以参考图2或图4任一所示的方法中，由控车代理设备执行的各个步骤。
在一个示例性的方案中，当计算机设备1000实现为控车客户端设备时，所述处理器1001和/或收发器，用于将所述控车客户端设备与控车代理设备绑定。其中，上述计算机设备1000中的处理器1001和/或收发器执行的过程可以参考上述图3或图4任一所示的方法中，由控车客户端设备执行的各个步骤。
本申请实施例还提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序，所述计算机程序由处理器加载并执行以实现上述图2、图3或图4所示的方法中，由控车代理设备或者控车客户端设备执行的全部或者部分步骤。
本申请还提供了一种芯片，该芯片包括电路结构，该芯片用于在计算机设备中运行，以使得计算机设备执行上述图4、图5或图7所示的方法中由控车代理设备或者控车客户端设备执行的全部或者部分步骤。
本申请还提供了一种计算机程序产品，该计算机程序产品或计算机程序包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得计算机设备执行上述图2、图3或图4所示的方法中，由控车代理设备或者控车客户端设备执行的全部或者部分步骤。
本申请还提供了一种计算机程序，该计算机程序由计算机设备的处理器执行，以实现上述图2、图3或图4所示的方法中，由控车代理设备或者控车客户端设备执行的全部或者部分步骤。
Claims (27)
- 一种用于车辆管理的解绑方法，其特征在于，所述方法由控车代理设备执行，所述方法包括：解除所述控车代理设备与控车客户端设备之间的绑定关系。
- 根据权利要求1所述的方法，其特征在于，所述解除所述控车代理设备与控车客户端设备之间的绑定关系，包括：解除第一车辆与控车客户端设备之间的绑定关系；或者，解除所述控车代理设备、第一车辆以及控车客户端设备之间的绑定关系。
- 根据权利要求1或2所述的方法，其特征在于，所述控车代理设备中包含车代理功能群集；所述车代理功能群集指示所述控车代理设备对应的车辆与控车客户端之间的绑定关系。
- 根据权利要求3所述的方法，其特征在于，所述车代理功能群集中包含与所述控车代理设备绑定的控车客户端的信息；其中，与所述控车代理设备绑定的控车客户端的信息，包括以下信息中的至少一种：与所述控车代理设备绑定的控车客户端的标识信息；与所述控车代理设备绑定的控车客户端的绑定类型的信息；与所述控车客户端绑定的车辆的标识信息。
- 根据权利要求3或4所述的方法，其特征在于，所述解除所述控车代理设备对应的第一车辆与控车客户端设备之间的绑定关系，包括：向所述控车客户端设备发送移除车请求；所述移除车请求所指示的与所述控车客户端设备解除绑定的车辆中包含所述第一车辆；接收所述控车客户端设备返回的移除车响应；所述移除车响应中包含所述第一车辆的标识信息、解绑状态、所述控车客户端设备的标识信息；在所述解绑状态为解绑成功的情况下，移除所述车代理功能群集中与所述控车客户端设备对应的控车客户端的信息中的所述第一车辆的标识信息。
- 根据权利要求3或4所述的方法，其特征在于，所述车代理功能群集支持移除客户端请求；所述移除客户端请求用于控车客户端移除与车辆的绑定。
- 根据权利要求6所述的方法，其特征在于，所述解除所述控车代理设备对应的第一车辆与控车客户端设备之间的绑定关系，包括：接收所述控车客户端设备发送的所述移除客户端请求，所述移除客户端请求中包含所述第一车辆的标识信息；移除所述车代理功能群集中与所述控车客户端设备对应的控车客户端的信息中的所述第一车辆的标识信息。
- 根据权利要求5或7所述的方法，其特征在于，所述方法还包括：若所述车代理功能群集中与所述控车客户端设备对应的控车客户端的信息中不包含车辆的标识信息，将所述车代理功能群集中与所述控车客户端设备对应的控车客户端的信息移除。
- 根据权利要求8所述的方法，其特征在于，所述方法还包括：移除ACL中与所述控车客户端设备对应的权限。
- 一种用于车辆管理的解绑方法，其特征在于，所述方法由控车客户端设备执行，所述方法包括：解除控车代理设备与所述控车客户端设备之间的绑定关系。
- 根据权利要求10所述的方法，其特征在于，所述解除控车代理设备与所述控车客户端设备之间的绑定关系，包括：解除第一车辆与所述控车客户端设备之间的绑定关系；或者，解除所述控车代理设备、第一车辆以及控车客户端设备之间的绑定关系。
- 根据权利要求10或11所述的方法，其特征在于，所述控车客户端设备中包含车客户端功能群集；所述车客户端功能群集指示各个控车代理对应的车辆与所述控车客户端之间的绑定关系。
- 根据权利要求12所述的方法，其特征在于，所述车客户端功能群集中包含与已绑定的车辆的信息；其中，所述已绑定的车辆的信息，包括以下信息中的至少一种：与所述控车客户端设备绑定的车辆的标识信息；与所述控车客户端设备绑定的车辆的名称；与所述车辆绑定的控车代理的标识信息。
- 根据权利要求12或13所述的方法，其特征在于，所述车客户端功能群集支持以下命令中的至少一种：移除车请求，用于指示与所述控车客户端设备解除绑定的车辆；移除车响应，用于指示是否完成所述控车客户端设备与车辆的解绑。
- 根据权利要求14所述的方法，其特征在于，所述解除所述控车代理设备对应的第一车辆与控车客户端设备之间的绑定关系，包括：接收所述控车代理设备发送的移除车请求；所述移除车请求所指示的与所述控车客户端设备解除绑定的车辆中包含所述第一车辆；移除所述第一车辆对应的已绑定的车辆的信息中，所述控车代理设备的标识信息；向所述控车代理设备返回移除车响应；所述移除车响应中包含所述第一车辆的标识信息、解绑状态、所述控车客户端设备的标识信息。
- 根据权利要求15所述的方法，其特征在于，所述移除所述第一车辆对应的已绑定的车辆的信息中，所述控车代理设备的标识信息，包括：在所述第一车辆与所述控车代理设备之间存在绑定关系的情况下，移除所述第一车辆对应的已绑定的车辆的信息中，所述控车代理设备的标识信息。
- 根据权利要求12或13所述的方法，其特征在于，所述解除所述控车代理设备对应的第一车辆与控车客户端设备之间的绑定关系，包括：移除所述第一车辆对应的已绑定的车辆的信息中，所述控车代理设备的标识信息；向所述控车代理设备发送移除客户端请求；所述移除客户端请求中包含所述第一车辆的标识信息。
- 根据权利要求15至17任一所述的方法，其特征在于，所述方法还包括：将所述车客户端功能群集中与所述第一车辆对应的已绑定的车辆的信息移除。
- 根据权利要求18所述的方法，其特征在于，所述将所述车客户端功能群集中与所述第一车辆对应的已绑定的车辆的信息移除，包括：在与所述第一车辆对应的已绑定的车辆的信息中，不存在控车代理的标识信息的情况，将所述车客户端功能群集中与所述第一车辆对应的已绑定的车辆的信息移除。
- 根据权利要求17所述的方法，其特征在于，所述向所述控车代理设备发送移除客户端请求，包括：在与所述第一车辆对应的已绑定的车辆的信息中，存在至少两个控车代理的标识信息的情况下，向所述至少两个控车代理对应的设备分别发送所述移除客户端请求。
- 一种用于车辆管理的解绑装置，其特征在于，所述装置包括：解绑模块，用于控车代理设备解除所述控车代理设备与控车客户端设备之间的绑定关系。
- 一种用于车辆管理的解绑装置，其特征在于，所述装置包括：解绑模块，用于控车客户端设备解除控车代理设备与所述控车客户端设备之间的绑定关系。
- 一种计算机设备，其特征在于，所述计算机设备包括处理器、存储器和收发器；所述存储器中存储有计算机程序，所述处理器执行所述计算机程序，以使得所述计算机设备实现如上述权利要求1至20任一所述的用于车辆管理的解绑方法。
- 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序，所述计算机程序用于被处理器执行，以实现如权利要求1至20任一所述的用于车辆管理的解绑方法。
- 一种芯片，其特征在于，所述芯片包括电路结构，所述芯片用于在计算机设备中运行，以使得所述计算机设备执行如权利要求1至20任一所述的用于车辆管理的解绑方法。
- 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机指令，所述计算机指令存储在计算机可读存储介质中；计算机设备的处理器从所述计算机可读存储介质读取所述计算机指令，并执行所述计算机指令，使得所述计算机设备执行如权利要求1至20任一所述的用于车辆管理的解绑方法。
- 一种计算机程序，其特征在于，所述计算机程序由计算机设备的处理器执行，以实现如权利要求1至20任一所述的用于车辆管理的解绑方法。
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202380095205.XA CN120836152A (zh) | 2023-06-16 | 2023-06-16 | 用于车辆管理的解绑方法、装置、设备、存储介质及产品 |
| PCT/CN2023/100849 WO2024254879A1 (zh) | 2023-06-16 | 2023-06-16 | 用于车辆管理的解绑方法、装置、设备、存储介质及产品 |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2023/100849 WO2024254879A1 (zh) | 2023-06-16 | 2023-06-16 | 用于车辆管理的解绑方法、装置、设备、存储介质及产品 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024254879A1 true WO2024254879A1 (zh) | 2024-12-19 |
Family
ID=93851139
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2023/100849 Ceased WO2024254879A1 (zh) | 2023-06-16 | 2023-06-16 | 用于车辆管理的解绑方法、装置、设备、存储介质及产品 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN120836152A (zh) |
| WO (1) | WO2024254879A1 (zh) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112540582A (zh) * | 2020-12-02 | 2021-03-23 | 深圳市欧瑞博科技股份有限公司 | 智能控制面板的数据处理方法、装置、介质及电子设备 |
| CN112584350A (zh) * | 2020-12-10 | 2021-03-30 | 北京百度网讯科技有限公司 | 处理信息的方法、装置、设备及可读存储介质 |
| US20210304219A1 (en) * | 2019-10-18 | 2021-09-30 | SZ DJI Technology Co., Ltd. | Methods, equipment and storage medium for unmanned aerial vehicle activation and unbinding |
| CN116112303A (zh) * | 2022-10-21 | 2023-05-12 | 漳州立达信光电子科技有限公司 | 设备离线控制方法、装置、设备及存储介质 |
-
2023
- 2023-06-16 CN CN202380095205.XA patent/CN120836152A/zh active Pending
- 2023-06-16 WO PCT/CN2023/100849 patent/WO2024254879A1/zh not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20210304219A1 (en) * | 2019-10-18 | 2021-09-30 | SZ DJI Technology Co., Ltd. | Methods, equipment and storage medium for unmanned aerial vehicle activation and unbinding |
| CN112540582A (zh) * | 2020-12-02 | 2021-03-23 | 深圳市欧瑞博科技股份有限公司 | 智能控制面板的数据处理方法、装置、介质及电子设备 |
| CN112584350A (zh) * | 2020-12-10 | 2021-03-30 | 北京百度网讯科技有限公司 | 处理信息的方法、装置、设备及可读存储介质 |
| CN116112303A (zh) * | 2022-10-21 | 2023-05-12 | 漳州立达信光电子科技有限公司 | 设备离线控制方法、装置、设备及存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN120836152A (zh) | 2025-10-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4804055B2 (ja) | 機器ネットワーク運用方法 | |
| CN102625310B (zh) | 无线网络接入方法、认证方法和装置 | |
| EP3404872B1 (en) | Device control method, network device, and network system | |
| CN111885026B (zh) | 基于区块链的互联互通方法和装置、存储介质及电子装置 | |
| CN111177695A (zh) | 一种基于区块链的智能家居设备访问控制方法 | |
| CN101340444A (zh) | 防火墙和服务器策略同步方法、系统和设备 | |
| WO2014101786A1 (zh) | 一种实现设备访问的方法、装置及系统 | |
| US20100030346A1 (en) | Control system and control method for controlling controllable device such as peripheral device, and computer program for control | |
| CN110519306A (zh) | 一种物联网的设备访问控制方法和装置 | |
| CN100438427C (zh) | 网络控制方法和设备 | |
| JP2020077919A (ja) | 車載通信装置、通信制御方法および通信制御プログラム | |
| CN105392137A (zh) | 家庭wifi防盗用的方法、无线路由器及终端设备 | |
| EP2153599B1 (en) | Methods and arrangements for security support for universal plug and play system | |
| CN105281957B (zh) | 一种在物联网中接入设备的方法及服务器 | |
| WO2014038820A1 (ko) | 무선 통신 시스템에서 서버의 단말의 리소스에 대한 접근 권한을 관리하기 위한 방법 및 이를 위한 장치 | |
| CN104079437B (zh) | 实现权限管理控制的方法及终端 | |
| WO2024254879A1 (zh) | 用于车辆管理的解绑方法、装置、设备、存储介质及产品 | |
| CN113612787B (zh) | 一种终端认证方法 | |
| CN113779516B (zh) | 一种设备控制方法、装置、存储介质及电子装置 | |
| CN107241332B (zh) | 网关权限的处理方法和装置 | |
| CN118140497A (zh) | 订阅权限信息处理方法、装置、计算机设备及存储介质 | |
| WO2024254877A1 (zh) | 车辆管理方法、装置、设备、存储介质及程序产品 | |
| CN114500617B (zh) | 互联网设备控制方法和装置、存储介质及电子设备 | |
| US12047421B2 (en) | Methods, systems, and devices for assigning policies in networking systems | |
| WO2024254878A1 (zh) | 用于车辆管理的绑定方法、装置、设备、存储介质及产品 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23941112 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 202380095205.X Country of ref document: CN |
|
| WWP | Wipo information: published in national office |
Ref document number: 202380095205.X Country of ref document: CN |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |