WO2024254878A1 - 用于车辆管理的绑定方法、装置、设备、存储介质及产品 - Google Patents

用于车辆管理的绑定方法、装置、设备、存储介质及产品 Download PDF

Info

Publication number
WO2024254878A1
WO2024254878A1 PCT/CN2023/100846 CN2023100846W WO2024254878A1 WO 2024254878 A1 WO2024254878 A1 WO 2024254878A1 CN 2023100846 W CN2023100846 W CN 2023100846W WO 2024254878 A1 WO2024254878 A1 WO 2024254878A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle
vehicle control
client device
control client
binding
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
Application number
PCT/CN2023/100846
Other languages
English (en)
French (fr)
Inventor
茹昭
吕小强
张军
杨宁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2023/100846 priority Critical patent/WO2024254878A1/zh
Priority to CN202380095206.4A priority patent/CN120770147A/zh
Publication of WO2024254878A1 publication Critical patent/WO2024254878A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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 a binding 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 binding method, device, equipment, storage medium and product for vehicle management.
  • the technical solution is as follows:
  • an embodiment of the present application provides a binding method for vehicle management, the method being executed by a vehicle control agent device, the method comprising:
  • an embodiment of the present application provides a binding method for vehicle management, the method being executed by a vehicle control client device, the method comprising:
  • the vehicle control client device is bound to the vehicle control proxy device.
  • an embodiment of the present application provides a binding device for vehicle management, the device comprising:
  • the binding module is used to bind the vehicle control client device to the vehicle control proxy device.
  • an embodiment of the present application provides a binding device for vehicle management, the device comprising:
  • the binding module is used to bind the vehicle control client device to the vehicle control proxy 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 binding 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 binding method for vehicle management.
  • an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored.
  • the computer program is loaded and executed by a processor to implement the above-mentioned binding method for vehicle management.
  • the present application also provides a chip, which includes a circuit structure, and the chip is used to run in a computer device so that the computer device executes the above-mentioned binding method for vehicle management.
  • 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 binding 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 binding method for vehicle management.
  • the vehicle control proxy device can be pre-bound to the vehicle control client device, so that the vehicle control proxy device can provide a proxy service, which can enable the vehicle control client device in the Internet of Things system to manage the vehicle, thereby expanding the interaction method between the Internet of Things device and the vehicle, expanding the application scenarios of the Internet of Things, and improving the user's management efficiency of the vehicle.
  • 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 a binding method for vehicle management provided by an embodiment of the present application.
  • FIG3 is a flow chart of a binding method for vehicle management provided by an embodiment of the present application.
  • FIG4 is a flowchart of a binding process for vehicle management provided by an embodiment of the present application.
  • FIG5 is a flow chart of a binding method for vehicle management involved in the present application.
  • FIG6 is a flow chart of a binding method for vehicle management involved in the present application.
  • FIG7 is a block diagram of a binding device for vehicle management provided by one embodiment of the present application.
  • FIG8 is a block diagram of a binding device for vehicle management provided by one embodiment of the present application.
  • FIG. 9 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 Internet of Things device 110 may refer to a device in the Internet of Things that is used to provide client functions or server functions corresponding to the Internet of Things protocol.
  • 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 IoT device 110 may be a commercial service device, such as an unmanned vending machine, etc.
  • 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.
  • 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 proxy device 120 refers to a client entity (which may be a virtual entity) running on a terminal device.
  • the proxy device 120 may be an application (Application, APP) running in the terminal device for accessing, controlling, and managing the IoT device.
  • Application Application, APP
  • 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 bridge device 140 is used to implement 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 IoT devices 110 supporting different IoT protocols and the proxy device 120.
  • 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.
  • 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 above-mentioned proxy device 120).
  • the cloud server 150 can be a cloud platform server of the IoT ecosystem.
  • the proxy device 120 may also directly establish a connection with the IoT device 110 .
  • the proxy device 120 may also establish a connection with the IoT device 110 through the cloud server 150 .
  • the proxy device 120 may also establish a connection with the IoT device 110 through the bridge device 140 .
  • 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
  • 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.
  • 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 .
  • the DNS-SD record can be set as follows:
  • the network configuration node can discover all available network access nodes waiting for network configuration:
  • the network configuration node can use the short identification code 3 to find the network access node waiting for network configuration:
  • the network configuration node can use the long identification code 840 to find the network access node waiting for network configuration:
  • the network configuration node can use Vendor ID 123 to discover the network access node waiting for network configuration:
  • the network configuration node can discover all network access nodes in the network configuration mode:
  • the distribution node can discover the Matter node using device type 81:
  • the DNS-SD record can be set up as follows:
  • the port number 22222 is given here as an example only.
  • One of the benefits of using DNS-SD is that the service is not restricted to using a single predetermined well-known port. This means that multiple instances of the Matter node control service can run on the same device at the same time, listening on different ports. The Matter controller discovers this port as well as the IPv6 address at runtime.
  • the Matter controller can discover the current IPv6 address and port of a known connected Matter node:
  • the DNS-SD record can be set as follows:
  • the above DNS-SD message includes the following functions:
  • Vendor ID is '123', Product ID is '456';
  • the device type is '35', a media player (the device type ID is 0x0023);
  • the device name is 'Living Room TV'.
  • a network access node can discover all network configuration nodes:
  • a network access node can discover a network configuration node with device type 35:
  • a network access node can discover the network distribution node with Vendor ID 123:
  • the binding part mainly completes the binding of IOTClient and IOTAgent. Only after binding, IOTClient can access the smart home system through IOTAgent. Before the binding process, IOTClient has established a communication channel with IOTAgent. The binding process is as follows:
  • 2IOTAgent discovers the identity of the smarthomeClient cluster of IOTClient and determines whether it supports access to smart home capabilities
  • 4[optional]IOTAgent obtains the list of devices supported by IOTClient: supporteddevicetype;
  • 9IOTClient sets the binding type to the smarthomeClient cluster.
  • FIG. 2 shows a flow chart of a binding 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 Binding a vehicle control client device to a vehicle control proxy device.
  • the vehicle control proxy device binds the vehicle control client device to the vehicle control proxy device, which may be that the vehicle control proxy device binds the vehicle control client device, the vehicle control proxy device and the first vehicle.
  • the vehicle control proxy device binding the vehicle control client device to the vehicle control proxy device may refer to binding the vehicle control client device to the first vehicle in the vehicle control proxy device.
  • the vehicle control proxy device may locally establish a binding project between the vehicle control client 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 status information of the first vehicle may be real-time status information obtained from the first vehicle when the vehicle control proxy device 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 proxy device and stored locally in the vehicle control proxy 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 first vehicle 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 pre-bound to the vehicle control client device 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.
  • the vehicle control proxy device can be pre-bound to the vehicle control client device, so that the vehicle control proxy device can provide a proxy service, which can enable the vehicle control client device in the Internet of Things system to manage the vehicle, thereby expanding the interaction method between the Internet of Things device and the vehicle, expanding the application scenarios of the Internet of Things, and improving the user's management efficiency of the vehicle.
  • FIG. 3 shows a flow chart of a binding 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 Bind the vehicle control client device to the vehicle control proxy device.
  • the vehicle control client device binds the vehicle control client device to the vehicle control proxy device, which may be that the vehicle control client device binds the vehicle control client device, the vehicle control proxy device and the first vehicle.
  • the vehicle control client device binds the vehicle control client device to the vehicle control proxy device, which can refer to the vehicle control client.
  • the vehicle control proxy device is bound to the first vehicle in the terminal device.
  • the vehicle control client device can locally establish a binding project between the vehicle control proxy device and the first vehicle.
  • the above-mentioned binding of the vehicle control client device and the vehicle control proxy device can be used to support the vehicle control client device to manage the first vehicle through the vehicle control proxy device using the vehicle control proxy device as a proxy.
  • the vehicle control client device can be pre-bound to the vehicle control client device, so that the vehicle control proxy device can provide a proxy service, which can enable the vehicle control client device in the Internet of Things system to manage the vehicle, thereby expanding the interaction method between the Internet of Things device and the vehicle, expanding the application scenarios for users to manage vehicles, and improving the efficiency of users' management of vehicles.
  • FIG. 4 shows a flow chart of a binding 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 The vehicle control proxy device discovers the vehicle control client device.
  • the process of the vehicle control proxy device discovering the vehicle control client device may include:
  • the vehicle control client device When the vehicle control proxy device is in an IP network environment, the vehicle control client device is discovered using the DNS-SD discovery method.
  • the vehicle control client device in the IP network can be discovered by means of DNS discovery.
  • the vehicle control client device when the vehicle control proxy device is in an IP network environment, the vehicle control client device is discovered using a DNS-SD discovery method, including:
  • the vehicle control client device also needs to pre-register the above DNS-SD record.
  • the vehicle control client device can register the DNS-SD record when it is in an IP network environment; the DNS-SD record is used for the vehicle control proxy device to discover the vehicle control client device.
  • the identification information of the vehicle control client device contained in the above DNS-SD record may be the ID of the vehicle control client device in the IP network, or the DNS-SD record may also include other identifications of the vehicle control client device, such as the identification ID in the Internet of Things.
  • the above-mentioned DNS-SD record may also include the client type of the vehicle control client device (the client type is used to indicate that the vehicle control client device has the function of managing the vehicle, that is, the vehicle control client) or capabilities (for example, the client device has a touch screen to support touch interaction, and/or, the client device supports voice interaction, etc.), so that the vehicle control proxy device can accurately discover the vehicle control client device that has the function of managing the vehicle.
  • the client type is used to indicate that the vehicle control client device has the function of managing the vehicle, that is, the vehicle control client
  • capabilities for example, the client device has a touch screen to support touch interaction, and/or, the client device supports voice interaction, etc.
  • discovering the vehicle control client device includes:
  • BLE Bluetooth Low Energy
  • the vehicle control proxy device when the vehicle control proxy device is not connected to the IP network, the vehicle control proxy device can discover surrounding vehicle control client devices through the BLE method.
  • the vehicle control proxy device when the vehicle control proxy device is connected to an IP network, it can also discover surrounding vehicle control client devices that are not connected to the IP network where the vehicle control proxy device is located through the BLE method.
  • the method further comprises:
  • the vehicle control client device can send BLE broadcasts; BLE broadcasts are used by the vehicle control proxy device to discover the vehicle control client device.
  • the vehicle control agent device discovers the vehicle control client device through the low-power Bluetooth BLE method
  • the following steps can be performed:
  • the vehicle control client device can actively send a BLE broadcast to inform the surrounding potential vehicle control agents.
  • the vehicle control client device is a client device with the function of managing the vehicle.
  • the vehicle control proxy device that receives the BLE broadcast can discover the vehicle control client device and obtain the information of the vehicle control client device carried in the BLE broadcast.
  • the method further comprises:
  • the vehicle control proxy device sends a BLE broadcast; the BLE broadcast is used to discover the vehicle control client device; accordingly, after receiving the BLE broadcast, the vehicle control client device returns the information of the vehicle control client device to the vehicle control proxy device via BLE, so that the vehicle control proxy device can discover the vehicle control client device.
  • the BLE broadcast includes at least one of the following information:
  • the identification information of the vehicle control client device may be a Bluetooth identification of the vehicle control client device, or an Internet of Things identification, etc.
  • the network information of the vehicle control client device may be the Wi-Fi network SSID;
  • the network information of the vehicle control client device can be the extended PAN ID
  • the network information of the vehicle control client device may be a network interface instance name of the operating system.
  • Step 402 The vehicle control proxy device establishes a connection with the vehicle control client device.
  • a connection may be established between the vehicle control proxy device and the vehicle control client device, which may be a data channel established between the vehicle control proxy device and the vehicle control client device.
  • a secure connection and data channel can be established between the vehicle control proxy device and the vehicle control client device based on the Matter specification.
  • a secure connection and data channel can be established between the vehicle control proxy device and the vehicle control client device based on the IP protocol.
  • a secure connection and data channel can be established between the vehicle control proxy device and the vehicle control client device based on BLE.
  • Step 403 the vehicle control proxy device binds the vehicle control client device to the vehicle control proxy device; the vehicle control client device binds the vehicle control client device to the vehicle control proxy device.
  • the vehicle control proxy device after the vehicle control proxy device discovers the vehicle control client device, it can prompt the user that a bindable vehicle control client device has been found, so that the user can confirm whether to initiate binding. If the user confirms to initiate binding, the vehicle control proxy device can bind the vehicle control client device to the vehicle control proxy device.
  • the step of the user confirming whether to initiate binding may be performed before step 402 or before step 403 .
  • the vehicle control agent device includes a car agent function cluster (CarAgent Cluster); the car agent function cluster indicates a vehicle control client bound to the vehicle 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).
  • one vehicle control proxy device can be bound to multiple vehicle control clients, and each vehicle control client can correspond to one vehicle control client device.
  • 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 device is the identification information of the vehicle bound to the vehicle control client device.
  • 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.
  • the car control client device includes a car client function cluster (CarClient Cluster);
  • the vehicle client function cluster indicates the vehicle control agent bound to the vehicle control client device.
  • a cluster may also be set in the vehicle control client device to store and maintain the vehicle control agent bound to the vehicle control client device.
  • 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 vehicle client function cluster includes information about the vehicle bound to the vehicle control client device
  • the information of the vehicle bound to the vehicle control client device includes at least one of the following information:
  • the identification information of the vehicle bound to the vehicle control client device The identification information of the vehicle bound to the vehicle control client device; the name of the vehicle bound to the vehicle control client device; the identification information of the vehicle control agent bound to the vehicle.
  • 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.
  • the process of binding the vehicle control client device to the vehicle control proxy device may include:
  • the vehicle control proxy device sends a vehicle binding request to the vehicle control client device; the vehicle binding request includes identification information of the vehicle control proxy device and identification information of the first vehicle; the vehicle control client device receives the vehicle binding request sent by the vehicle control proxy device; the vehicle control client device adds the identification information of the vehicle control proxy device and the identification information of the first vehicle to the information of the bound vehicle corresponding to the first vehicle; the vehicle control client device returns a vehicle binding response to the vehicle control proxy device; the vehicle binding response includes the identification information of the first vehicle and the binding status; the vehicle control proxy device receives the vehicle binding response returned by the vehicle control client device;
  • the vehicle control proxy device adds information of the vehicle control client corresponding to the vehicle control client device and identification information of the first vehicle in the vehicle proxy function cluster.
  • the vehicle control proxy device initiates a binding request and exchanges binding information with the vehicle control client device, so that both store the binding relationship between the vehicle control proxy device, the vehicle control client device and the first vehicle in their respective clusters.
  • the vehicle control client device adds the identification information of the vehicle control proxy device and the identification information of the first vehicle to the information of the bound vehicle corresponding to the first vehicle, including:
  • the vehicle client function cluster already includes information of a bound vehicle corresponding to the first vehicle, adding identification information of the vehicle control proxy device to the information of the bound vehicle corresponding to the first vehicle;
  • the bound vehicle information corresponding to the first vehicle is added to the vehicle client function cluster according to the identification information of the vehicle control agent device and the identification information of the first vehicle.
  • one vehicle in a vehicle client function cluster, can be bound to multiple vehicle control agents.
  • the vehicle control client device receives a vehicle binding request, if it is found that there is already information of a bound vehicle corresponding to the first vehicle, there is no need to establish new information of the bound vehicle, and the identification information of the vehicle control agent device can be directly written into the information of the bound vehicle.
  • the vehicle control client device may also add the bound vehicle information corresponding to the first vehicle in the vehicle client function cluster according to the identification information of the vehicle control proxy device and the identification information of the first vehicle. That is to say, in the vehicle client function cluster, when the vehicle control client device receives the vehicle binding request, if it is found that the bound vehicle information corresponding to the first vehicle already exists, it may re-establish the bound vehicle information and write the identification information of the vehicle control proxy device in the newly created bound vehicle information.
  • the vehicle binding request further includes the name of the first vehicle; the method further includes:
  • the vehicle client function cluster already includes information of a bound vehicle corresponding to the first vehicle, if the first name of the first vehicle included in the vehicle binding request and the first vehicle included in the information of the bound vehicle corresponding to the first vehicle If the second name of the vehicle is inconsistent, the second name is updated to the first name.
  • each vehicle in the vehicle client function cluster has only a unique name.
  • the vehicle control client device receives a vehicle binding request, if it is found that the name corresponding to the first vehicle already exists in the bound vehicle information corresponding to the first vehicle, and the name corresponding to the first vehicle is different from the name of the first vehicle in the vehicle binding request, then according to the name of the vehicle in the above vehicle binding request, the name corresponding to the first vehicle in the bound vehicle information corresponding to the first vehicle is updated.
  • the method further includes: the vehicle control proxy device reads the information of the bound vehicle from the vehicle control client device.
  • the vehicle control proxy device may also query the vehicle control client device about which vehicles it has bound, so that the vehicle bound to the vehicle control client device may be selected from the vehicles corresponding to the vehicle control proxy device.
  • the above process of selecting a vehicle to be bound to the vehicle control client device can be executed by the user; or, the above process of selecting a vehicle to be bound to the vehicle control client device can be executed by the vehicle control proxy device according to a preset selection rule, for example, the vehicle control proxy device gives priority to vehicles that are bound or not bound to the vehicle control client device, and establishes a binding relationship among the vehicle control proxy device, the vehicle control client device and the vehicle.
  • a preset selection rule for example, the vehicle control proxy device gives priority to vehicles that are bound or not bound to the vehicle control client device, and establishes a binding relationship among the vehicle control proxy device, the vehicle control client device and the vehicle.
  • the method further includes: setting vehicle control authority for the vehicle control client device in the vehicle control proxy device; the vehicle control authority is the authority to manage the vehicle.
  • the vehicle control authority of the vehicle control client device can also be set.
  • the vehicle control authority set above may be the management authority of the vehicle control client device over the currently bound vehicle; or, the vehicle control authority set above may be the management authority of the vehicle control client device over all vehicles.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the car agent function set CarAgent Cluster is implemented on the mobile phone, and the bound CarClient (car control client) is recorded.
  • the car agent function set includes the following attributes, which are defined in Table 1:
  • the clientInfo structure is defined as shown in Table 2 below:
  • ClientType is the binding type of the client, True is long-term binding, and False is temporary binding.
  • the car client function set includes the following attributes, which are defined in Table 3:
  • carInfo structure is defined as shown in Table 4 below:
  • the car client function set includes the following commands, which are defined in Table 5:
  • bindCarReq is used by CarAgent to bind a car to CarClient.
  • the bound car is identified by CarID. Its parameter definitions are shown in Table 6 below:
  • bindCarResp parameter definition is shown in Table 7 below:
  • Status is the binding status
  • True means binding is successful
  • False means binding fails.
  • Binding discovery CarAgent actively discovers CarClient in the following ways:
  • the DNS-SD discovery method can be used to discover the CarClient in the network.
  • the BLE discovery method can be used.
  • the DNS-SD service name used to discover CarClient is: _carclient._matter._tcp
  • the service instance name is the device ID in the smart home network. For example, if the device ID is FC7772401CD0696, the service instance name is also FC7772401CD0696. The service instance name should be unique within the home network.
  • the host name of CarClient is the MAC address of the device.
  • a device with a 48-bit MAC address of B75AFB458ECD and a device ID of FC7772401CD0696 should register the following DNS-SD record:
  • the port number 11111 is only an example.
  • CarAgent can discover the address and port number of the CarClient device through DNS-SD:
  • BLE discovery is initiated by CarClient, and CarAgent is in listening mode.
  • the BLE discovery broadcast should contain the following information: ClientID, NetworkInfo (network information where CarClient is located), as shown in Table 8:
  • NetworkID is the network identifier, which is defined as follows according to the network characteristics:
  • Wi-Fi network For a Wi-Fi network, it is the Wi-Fi network SSID;
  • CarAgent After CarAgent receives the discovery information broadcast by CarClient, it can choose to join the network where Car Client is located or directly establish a BLE connection.
  • Figure 5 shows a flow chart of a binding for vehicle management involved in the present application.
  • the user can discover the CarClient implemented in the smart TV in the home network through the CarAgent implemented on the mobile phone, and initiate the vehicle control binding.
  • the above process may include:
  • the mobile phone enters the home network, and the CarAgent on it uses DNS-SD to discover the CarClient; at the same time, the mobile phone can monitor the BLE broadcast and find the CarClient that is not in the home network (at this time, it may also receive the BLE broadcast sent by the CarClient in the home network, and such devices can be filtered out by NetworkID). The user can choose to switch to another target network for DNS-SD discovery.
  • CarClient provides address information through the DNS-SD service and makes a discovery response.
  • CarAgent prompts the user, and the user confirms on the mobile phone whether binding is required.
  • CarAgent sends a bindCar Request to CarClient, which includes CarID, car name and CarAgent ID; if CarAgent is associated with multiple cars, only one of them will be bound at a time, and the binding will be performed in multiple times.
  • CarClient adds the car and the car control agent to the boundCars attribute.
  • CarAgent adds the CarClient information to the boundClients attribute. If the corresponding Client already exists in the boundClients attribute list, the CarID of the bound car is added to the corresponding table item.
  • the user can set the car control permission for the CarClient on the CarAgent, and the default permission is O.
  • CarClient can control the car through CarAgent.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the difference in clustering lies in the carInfo structure in the car client function set CarClient Cluster on the smart home device, where the carInfo structure is defined as shown in Table 9 below:
  • Figure 6 shows a flowchart of a binding for vehicle management involved in this application.
  • the user can discover the CarClient implemented in the smart TV in the home network through the CarAgent implemented on the mobile phone, and initiate a vehicle control Binding, the process may include:
  • the mobile phone enters the home network, and the CarAgent on it uses DNS-SD to discover the CarClient; at the same time, the mobile phone can monitor the BLE broadcast and find the CarClient that is not in the home network (at this time, it may also receive the BLE broadcast sent by the CarClient in the home network, and such devices can be filtered out by NetworkID). The user can choose to switch to another target network for DNS-SD discovery.
  • CarClient provides address information through the DNS-SD service and makes a discovery response.
  • CarAgent prompts the user, and the user confirms on the mobile phone whether binding is required.
  • CarAgent queries the cars bound to CarClient by reading the boundCars attribute.
  • CarClient returns the query result, including the car’s CarID, car name, and CarAgent ID.
  • the user chooses to bind to the CarID returned in the previous step, or a new CarID or CarName.
  • the user can set the car control permission for the CarClient on the CarAgent, and the default permission is 0.
  • CarAgent sends a bindCar Request to CarClient, including CarID, the name of the car and CarAgent ID; when CarID already exists in the boundCars list, the execution of this command should be considered as adding a CarAgent to the Entry corresponding to CarID. If CarName is different from the corresponding name in the current boundCars list, it should be considered as modifying the displayed name of the car.
  • CarClient adds the car and the car control agent to the boundCars attribute.
  • CarAgent adds the CarClient information to the boundClients attribute. If the corresponding Client already exists in the boundClients attribute list, the CarID of the bound car is added to the corresponding table item.
  • CarClient can control the car through CarAgent.
  • FIG. 7 shows a block diagram of a binding device for vehicle management provided by an embodiment of the present application.
  • the binding device 700 for vehicle management has the function of implementing the method shown in FIG. 2 or FIG. 4 above, which is performed by the vehicle control agent device.
  • the device may include:
  • the binding module 701 is used to bind the vehicle control client device to the vehicle control proxy device.
  • the binding module 701 is used to bind the vehicle control client device, the vehicle control proxy device and the first vehicle.
  • the vehicle control proxy device includes a vehicle proxy function cluster
  • the vehicle proxy function cluster indicates a vehicle control client bound to the vehicle control proxy device.
  • 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 device is the identification information of the vehicle bound to the vehicle control client device.
  • the binding module 701 is used to:
  • the vehicle binding request includes identification information of the vehicle control proxy device and identification information of the first vehicle;
  • the vehicle binding response includes identification information and binding status of the first vehicle
  • the information of the vehicle control client corresponding to the vehicle control client device and the identification information of the first vehicle are added to the vehicle proxy function cluster.
  • the apparatus further comprises:
  • the reading module is used to read the information of the bound vehicle from the vehicle control client device.
  • the apparatus further comprises:
  • the authority setting module is used to set the vehicle control authority for the vehicle control client device in the vehicle control proxy device; the vehicle control authority is the authority to manage the vehicle.
  • the managing includes at least one of the following:
  • the apparatus further comprises:
  • a discovery module is used to discover the vehicle control client device.
  • the discovery module is used to discover the vehicle control client device by using a DNS-SD discovery method when the vehicle control proxy device is in an IP network environment.
  • the discovery module is used to:
  • DNS-SD record of the vehicle control client device, wherein the DNS-SD record includes identification information of the vehicle control client device;
  • the address and port number of the vehicle control client device are obtained according to the DNS-SD record.
  • the discovery module is used to discover the vehicle control client device via Bluetooth Low Energy (BLE).
  • BLE Bluetooth Low Energy
  • the discovery module is used to:
  • the information of the vehicle control client device is obtained according to the BLE broadcast.
  • the BLE broadcast includes at least one of the following information:
  • the network information of the vehicle control client device is the network information of the vehicle control client device.
  • FIG8 shows a block diagram of a binding device for vehicle management provided by an embodiment of the present application.
  • the binding device 800 for vehicle management has the function of implementing the method shown in FIG3 or FIG4 above, which is performed by the vehicle control agent device.
  • the device may include:
  • the binding module 801 is used to bind the vehicle control client device to the vehicle control proxy device.
  • the binding module 801 is used to bind the vehicle control client device, the vehicle control proxy device and the first vehicle.
  • the vehicle control client device includes a vehicle client function cluster
  • the vehicle client function cluster indicates a vehicle control agent bound to the vehicle control client device.
  • the vehicle client function cluster includes information of a vehicle bound to the vehicle control client device
  • the information of the vehicle bound to the vehicle control client device includes at least one of the following information:
  • the binding module 801 is used to:
  • the vehicle binding request includes identification information of the vehicle control proxy device and identification information of the first vehicle;
  • a vehicle binding response is returned to the vehicle control proxy device; the vehicle binding response includes identification information and binding status of the first vehicle.
  • the binding module 801 is used to:
  • the vehicle client function cluster already includes information of a bound vehicle corresponding to the first vehicle, adding identification information of the vehicle control proxy device to the information of the bound vehicle corresponding to the first vehicle;
  • the vehicle client function cluster does not include information of a bound vehicle corresponding to the first vehicle
  • information of a bound vehicle corresponding to the first vehicle is added to the vehicle client function cluster according to identification information of the vehicle control agent device and identification information of the first vehicle.
  • the vehicle binding request further includes the name of the first vehicle; and the device further includes:
  • a name update module is used to update the first name to the first name if the first name of the first vehicle contained in the bound vehicle request is inconsistent with the second name of the first vehicle contained in the information of the bound vehicle corresponding to the first vehicle, when the vehicle client function cluster already contains information of the bound vehicle corresponding to the first vehicle.
  • the apparatus further comprises:
  • the registration module is used to register a DNS-SD record when the vehicle control client device is in an IP network environment; the DNS-SD record is used by the vehicle control proxy device to discover the vehicle control client device.
  • the apparatus further comprises:
  • the sending module is used to send a BLE broadcast; the BLE broadcast enables the vehicle control proxy device to discover the vehicle control client device.
  • the BLE broadcast includes at least one of the following information:
  • the network information of the vehicle control client device is the network information of the vehicle control client device.
  • FIG9 shows a schematic diagram of the structure of a computer device 900 provided in one embodiment of the present application.
  • the computer device 900 may include: a processor 901 , a receiver 902 , a transmitter 903 , a memory 904 and a bus 905 .
  • the processor 901 includes one or more processing cores, and the processor 901 executes various functional applications and information processing by running software programs and modules.
  • the receiver 902 and the transmitter 903 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 904 is connected to the processor 901 via a bus 905.
  • the memory 904 can be used to store computer programs, and the processor 901 is used to execute the computer program to implement each step in the above method embodiment.
  • the memory 904 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, and the volatile or non-volatile storage device includes but is not limited to: a magnetic disk or an optical disk, an electrically erasable programmable read-only memory, an erasable programmable read-only memory, a static access memory, a read-only memory, a magnetic memory, a flash memory, and a programmable read-only memory.
  • the processor 901 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 901 and/or the transceiver in the above-mentioned computer device 900 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 901 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 901 and/or the transceiver in the computer device 900 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.
  • the present application also provides a computer-readable storage medium, wherein the storage medium stores a computer program.
  • the computer program is loaded and executed by the processor to implement all or part of the steps executed by the vehicle control agent device or the vehicle control client device in the method shown in FIG. 2 , FIG. 3 or FIG. 4 .
  • 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种用于车辆管理的绑定方法、装置、设备、存储介质及产品，属于物联网技术领域。该方法由控车代理设备执行，包括：将控车客户端设备与所述控车代理设备绑定(201)。上述方案扩展了物联网的应用场景，提高了用户对车辆的管理效率。

Description

用于车辆管理的绑定方法、装置、设备、存储介质及产品 技术领域
本申请涉及物联网技术领域，特别涉及一种用于车辆管理的绑定方法、装置、设备、存储介质及产品。
背景技术
随着物联网(Internet of Things，IoT)技术的不断发展，越来越多的物联网设备在智能家居、工业生产等诸多领域给用户的生产生活带来了极大的便利性。
在相关技术中，车辆可以有手机等移动终端设备进行远程控制。具体的，车辆的车机设备和用户的移动终端同时接入云端服务器，并在云端服务器中绑定，后续移动终端可以通过云端服务器向车机设备发送控制指令。
发明内容
本申请实施例提供了一种用于车辆管理的绑定方法、装置、设备、存储介质及产品。所述技术方案如下：
一方面，本申请实施例提供了一种用于车辆管理的绑定方法，所述方法由控车代理设备执行，所述方法包括：
将控车客户端设备与所述控车代理设备绑定。
一方面，本申请实施例提供了一种用于车辆管理的绑定方法，所述方法由控车客户端设备执行，所述方法包括：
将所述控车客户端设备与控车代理设备绑定。
另一方面，本申请实施例提供了一种用于车辆管理的绑定装置，所述装置包括：
绑定模块，用于将控车客户端设备与所述控车代理设备绑定。
另一方面，本申请实施例提供了一种用于车辆管理的绑定装置，所述装置包括：
绑定模块，用于将所述控车客户端设备与控车代理设备绑定。
另一方面，本申请实施例提供了一种计算机设备，所述计算机设备实现为信息上报设备，所述计算机设备包括处理器、存储器和收发器；
存储器中存储有计算机程序，处理器执行所述计算机程序，以使得计算机设备实现上述用于车辆管理的绑定方法。
再一方面，本申请实施例提供了一种计算机设备，所述计算机设备包括处理器、存储器和收发器，所述存储器存储有计算机程序，所述计算机程序用于被所述处理器执行，以实现上述用于车辆管理的绑定方法。
又一方面，本申请实施例还提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序，所述计算机程序由处理器加载并执行以实现上述用于车辆管理的绑定方法。
又一方面，本申请还提供了一种芯片，该芯片包括电路结构，所述芯片用于在计算机设备中运行，以使得所述计算机设备执行上述用于车辆管理的绑定方法。
又一方面，本申请提供了一种计算机程序产品，该计算机程序产品包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行上述用于车辆管理的绑定方法。
又一方面，本申请提供了一种计算机程序，该计算机程序由计算机设备的处理器执行，以实现上述用于车辆管理的绑定方法。
通过本申请实施例提供的技术方案，控车代理设备可以预先与控车客户端设备绑定，从而使得控车代理设备可以提供一种代理服务，可以实现物联网系统中的控车客户端设备可以对车辆进行管理，从而扩展了物联网设备与车辆之间的交互方式，扩展了物联网的应用场景，提高了用户对车辆的管理效率。
附图说明
图1是本申请一个实施例提供的物联网的网络架构的示意图；
图2是本申请一个实施例提供的用于车辆管理的绑定方法的流程图；
图3是本申请一个实施例提供的用于车辆管理的绑定方法的流程图；
图4是本申请一个实施例提供的用于车辆管理的绑定的流程框架图；
图5是本申请涉及的一种用于车辆管理的绑定的流程图；
图6是本申请涉及的一种用于车辆管理的绑定的流程图；
图7是本申请一个实施例提供的用于车辆管理的绑定装置的框图；
图8是本申请一个实施例提供的用于车辆管理的绑定装置的框图；
图9是本申请一个实施例提供的计算机设备的结构示意图。
具体实施方式
请参考图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)Matter DNS-SD发现
(1)入网节点发现
假设在Wi-Fi下的设备使用48-bit的MAC地址'B75AFB458ECD'，并且它的域名为'DD200C20D25AE5F7'作为服务的实例名称。DNS-SD记录可以如下设置：
dns-sd-R DD200C20D25AE5F7_matterc._udp，_S3，_L840，_CM.11111D＝840CM＝2
·短识别码可通过'_S3'子类型进行过滤，并通过'D＝840'进行算法过滤。
·长识别码通过'_L840'子类型过滤，并直接通过'D＝840'进行过滤。
·当管理员打开了配网窗口，入网节点现在是配网状态，可以通过'CM＝2'查询。
·如果发现入网节点进行初始配网，而不是随后的额外配网，则会发布'CM＝1'。
配网节点可以发现所有等待配网的可用入网节点：
dns-sd-B_matterc._udp
配网节点可以用短识别码3发现等待配网的入网节点：
dns-sd-B_matterc._udp，_S3
配网节点可以用长识别码840发现等待配网的入网节点：
dns-sd-B_matterc._udp，_L840
配网节点可以用Vendor ID 123发现等待配网的入网节点：
dns-sd-B_matterc._udp，_V123
配网节点可以发现所有配网模式下的入网节点：
dns-sd-B_matterc._udp，_CM
配网节点可以用设备类型81发现Matter节点：
dns-sd-B_matterc._udp，_T81
(2)操作发现
考虑使用B75AFB458ECD的48位设备MAC地址作为其主机名的Wi-Fi上的设备。的DNS-SD记录可以设置如下：
dns-sd-R 87E1B004E235A130-8FC7772401CD0696_matter._tcp.22222
端口号22222在此仅作为示例给出。使用DNS-SD的好处之一是，服务不受限制使用单个预先确定的已知端口。这意味着Matter节点控制服务的多个实例可以同时在同一设备上运行，监听不同的端口。Matter控制器在运行时发现该端口以及IPv6地址。
Matter控制器可以发现已知已入网Matter节点的当前IPv6地址和端口：
dns-sd-L 87E1B004E235A130-8FC7772401CD0696_matter._tcp
87E1B004E235A130-8FC7772401CD0696._matter._tcp.local.can be reached at
B75AFB458ECD.local.:22222
dns-sd-Gv6 B75AFB458ECD.local
fe80::f515:576f:9783:3f30
(3)配网节点发现
假设在Wi-Fi下的设备使用48-bit的MAC地址'B75AFB458ECD'。DNS-SD记录可以如下设置：
dns-sd-R DD200C20D25AE5F7_matterd._udp，_V123，_T35.33333
VP＝123+456DT＝35DN＝"LivingRoom TV"
上面的DNS-SD消息里包括了如下功能：
Vendor ID是'123'，Product ID是'456'；
设备类型是'35'，一个媒体播放器(设备类型ID是0x0023)；
设备名称是'Living Room TV'。
一个入网节点可以发现所有的配网节点：
dns-sd-B_matterd._udp
一个入网节点可以发现设备类型为35的配网节点：
dns-sd-B_matterd._udp，_T35
一个入网节点可以发现Vendor ID为123的配网节点：
dns-sd-B_matterd._udp，_V123
2)车控家绑定
绑定部分主要完成IOTClient与IOTAgent的绑定。绑定之后的IOTClient才可以通过IOTAgent去访问智能家居系统。在绑定流程之前IOTClient已经与IOTAgent完成了通信通道的建立。绑定过程如下：
①用户在手机侧启动绑定流程；
②IOTAgent发现IOTClient的smarthomeClient cluster的标识，确定其是否支持访问智能家居能力；
③返回IOTClient支持的协议版本：version id；
④[optional]IOTAgent获取IOTClient的支持的设备列表:supporteddevicetype；
⑤返回支持的可控设备列表；
⑥用户选择临时绑定还是长期绑定；
⑦如果是长期绑定，需将绑定关系设定到绑定表中；
⑧将绑定类型通知给IOTClient；
⑨IOTClient将绑定类型设定到smarthomeClient cluster中。
请参考图2，其示出了本申请一个实施例提供的用于车辆管理的绑定方法的流程图，该方法可以由控车代理设备执行，比如，该控车代理设备可以是图1所示的网络架构中的代理设备120；该方法可以包括如下步骤：
步骤201，将控车客户端设备与控车代理设备绑定。
在本申请实施例中，控车代理设备将控车客户端设备与控车代理设备绑定，可以是指控车代理设备将控车客户端设备、控车代理设备以及第一车辆进行绑定。
或者说，控车代理设备将控车客户端设备与控车代理设备绑定，可以是指在控车代理设备中将控车客户端设备与第一车辆进行绑定。比如，在将控车客户端设备与控车代理设备绑定的过程中，控车代理设备可以在本地建立控车客户端设备与第一车辆之间的绑定项目。
其中，上述控车代理设备可以对应至少一个车辆，该至少一个车辆中包含上述第一车辆。
其中，上述控车客户端设备可以是物联网设备，比如上述图1所示的网络架构中的物联网设备110。
例如，上述控车客户端设备可以是智能电视、智能冰箱等物联网设备。
其中，上述将控车客户端设备与控车代理设备绑定，可以用于支持控车代理设备向控车客户端设备提供对第一车辆进行管理的代理服务。
比如，上述控车代理设备可以分别与控车客户端设备以及第一车辆建立连接，当用户需要通过控车客户端设备对第一车辆进行管理时，控车代理设备可以作为控车客户端设备和第一车辆之间的代理，根据控车客户端设备对第一车辆的管理请求，对第一车辆进行管理。
也就是说，上述管理请求由控车客户端设备发送给控车代理设备，然后，控车代理设备根据该管理请求，提供对第一车辆进行管理的服务，从而实现了通过物联网设备实现对车辆的管理功能。
在一些实施例中，上述管理包括以下至少一种：
对第一车辆进行控制；
对第一车辆的状态信息进行查看；
对第一车辆的状态信息进行订阅。
其中，对第一车辆进行控制，可以是指控车代理设备根据控车客户端设备发送的管理请求，向第一车辆发送控制指令，以便第一车辆执行该控制指令，从而实现对第一车辆的控制。
在一些实施例中，上述控制指令可以是锁车/解锁、打开/关闭车窗、打开/关闭空调、打开/关闭座椅加热等指令。
上述对第一车辆的状态信息查看，可以是指控车代理设备根据控车客户端设备发送的管理请求，单次向控车客户端设备返回第一车辆的状态信息。
上述对第一车辆的状态信息进行订阅，可以是指控车代理设备根据控车客户端设备发送的管理请求，向控车客户端设备返回第一车辆的状态信息，且后续检测到第一车辆的状态信息发生更新时，将第一车辆的状态信息中发生更新的部分通知给控车客户端设备。
在一些实施例中，上述第一车辆的状态信息可以由控车代理设备接收到管理请求时，向第一车辆获取的实时的状态信息；或者，上述第一车辆的状态信息也可以是由控车代理设备预先向第一车辆获取或订阅，并存储在控车代理设备本地的状态信息。
上述第一车辆的状态信息，可以指示第一车辆的各种状态，比如，锁车/解锁状态、车窗的开启/关闭状态、空调的开启/关闭状态、剩余电量/剩余燃油量、车内温度等等。
在一些实施例中，除了上述对第一车辆进行控制、对第一车辆的状态信息进行查看和订阅之外，还可以有其它的管理方式，比如，取消对第一车辆的状态信息的订阅等等。本申请各个实施例对于上述管理的方式不做限定。
在一些实施例中，为了支持控车代理设备向控车客户端设备提供对第一车辆进行管理的代理服务，可以预先在控车代理设备中将第一车辆与控车客户端设备绑定，和/或，在控车客户端设备中，将第一车辆与控车代理设备绑定。
综上所述，在本申请实施例中，控车代理设备可以预先与控车客户端设备绑定，从而使得控车代理设备可以提供一种代理服务，可以实现物联网系统中的控车客户端设备可以对车辆进行管理，从而扩展了物联网设备与车辆之间的交互方式，扩展了物联网的应用场景，提高了用户对车辆的管理效率。
请参考图3，其示出了本申请一个实施例提供的用于车辆管理的绑定方法的流程图，该方法可以由控车客户端设备执行，比如，该控车客户端设备可以是图1所示的网络架构中的物联网设备110；该方法可以包括如下步骤：
步骤301，将控车客户端设备与控车代理设备绑定。
在本申请实施例中，控车客户端设备将控车客户端设备与控车代理设备绑定，可以是指控车客户端设备将控车客户端设备、控车代理设备以及第一车辆进行绑定。
或者说，控车客户端设备将控车客户端设备与控车代理设备绑定，可以是指在控车客户 端设备中将控车代理设备与第一车辆进行绑定。比如，在将控车客户端设备与控车代理设备绑定的过程中，控车客户端设备可以在本地建立控车代理设备与第一车辆之间的绑定项目。
其中，上述将控车客户端设备与控车代理设备绑定，可以用于支持控车客户端设备以控车代理设备为代理，通过控车代理设备对第一车辆进行管理。
综上所述，在本申请实施例中，控车客户端设备可以预先与控车客户端设备绑定，从而使得控车代理设备可以提供一种代理服务，可以实现物联网系统中的控车客户端设备可以对车辆进行管理，从而扩展了物联网设备与车辆之间的交互方式，扩展了用户对车辆进行管理的应用场景，提高了用户对车辆的管理效率。
请参考图4，其示出了本申请一个实施例提供的用于车辆管理的绑定方法的流程图，该方法可以由控车代理设备和控车客户端设备交互执行，该控车代理设备和控车客户端设备可以分别是图1所示的网络架构中的代理设备120和物联网设备110；该方法可以包括如下几个步骤：
步骤401，控车代理设备发现控车客户端设备。
在一些实施例中，控车代理设备发现控车客户端设备的过程可以包括：
在控车代理设备处于IP网络环境下，采用DNS-SD发现方式发现控车客户端设备。
其中，当控车代理设备接入IP网络时，可以通过DNS发现的方式，发现IP网络中的控车客户端设备。
在一些实施例中，在控车代理设备处于IP网络环境下，采用DNS-SD发现方式发现控车客户端设备，包括：
获取控车客户端设备的DNS-SD记录，DNS-SD记录中包含控车客户端设备的标识信息；
根据DNS-SD记录获取控车客户端设备的地址和端口号。
相应的，控车客户端设备也需要预先注册上述DNS-SD记录，具体的，控车客户端设备在处于IP网络环境下，可以注册DNS-SD记录；该DNS-SD记录用于控车代理设备发现控车客户端设备。
其中，上述DNS-SD记录中包含的控车客户端设备的标识信息，可以是控车客户端设备在IP网络中的ID，或者，DNS-SD记录中也可以包括控车客户端设备的其它标识，比如，在物联网中的标识ID。
在一些实施例中，上述DNS-SD记录还可以包含控车客户端设备的客户端类型(该客户端类型用于指示该控车客户端设备具有对车辆进行管理的功能，即控车客户端)或能力(比如该客户端设备具有触摸屏以支持触控交互，和/或，该客户端设备支持语音交互等等)，以便控车代理设备能够准确的发现具有对车辆进行管理的功能的控车客户端设备。
在一些实施例中，发现控车客户端设备包括：
通过低功耗蓝牙BLE方式发现控车客户端设备。
在本申请实施例中，控车代理设备未接入IP网络时，该控车代理设备可以通过BLE方式，发现周围的控车客户端设备。
或者，控车代理设备接入IP网络时，也可以通过BLE方式，发现周围未接入控车代理设备所在的IP网络的控车客户端设备。
在一些实施例中，该方法还包括：
控车客户端设备可以发送BLE广播；BLE广播用于控车代理设备发现控车客户端设备。
相应的，控车代理设备通过低功耗蓝牙BLE方式发现控车客户端设备时，可以执行以下步骤：
接收控车客户端设备发送的BLE广播；
根据BLE广播获取控车客户端设备的信息。
在上述实施例中，可以由控车客户端设备主动发送BLE广播，以告知周围潜在的控车代 理设备，该控车客户端设备是具有对车辆进行管理的功能的客户端设备，相应的，接收到BLE广播的控车代理设备可以发现该控车客户端设备，并获取BLE广播中携带的，控车客户端设备的信息。
在另一些实施例中，该方法还包括：
控车代理设备发送BLE广播；BLE广播用于发现控车客户端设备；相应的，控车客户端设备接收到该BLE广播后，通过BLE方式向控车代理设备返回控车客户端设备的信息，从而使得控车代理设备可以发现该控车客户端设备。
在一些实施例中，BLE广播中包含以下信息中的至少一种：
控车客户端设备的标识信息；
控车客户端设备的网络信息。
其中，控车客户端设备的标识信息可以是控车客户端设备的蓝牙标识，或者物联网标识等等。
其中，对于Wi-Fi网络，控车客户端设备的网络信息可以为Wi-Fi网络SSID；
对于Thread网络，控车客户端设备的网络信息可以为扩展的PAN ID；
对于以太网络，控车客户端设备的网络信息可以为操作系统的网络接口实例名称。
步骤402，控车代理设备与控车客户端设备建立连接。
在一些实施例中，控车代理设备发现控车客户端设备，并获取到控车客户端设备的信息后，控车代理设备与控车客户端设备之间可以建立连接，可以是指控车代理设备与控车客户端设备之间建立数据通道。
比如，控车代理设备与控车客户端设备之间可以基于Matter规范建立安全连接和数据通道。
再比如，控车代理设备与控车客户端设备之间可以基于IP协议建立安全连接和数据通道。
再比如，控车代理设备与控车客户端设备之间可以基于BLE建立安全连接和数据通道。
步骤403，控车代理设备将控车客户端设备与控车代理设备绑定；控车客户端设备将控车客户端设备与控车代理设备绑定。
在本申请实施例中，控车代理设备发现控车客户端设备后，可以提示用户已经发现可绑定的控车客户端设备，以便用户确认是否发起绑定，如果用户确认发起绑定，则控车代理设备可以将控车客户端设备与控车代理设备绑定。
其中，上述用户确认是否发起绑定的步骤，可以在步骤402之前执行，也可以在步骤403之前执行。
在一些实施例中，控车代理设备中包含车代理功能群集(CarAgent Cluster)；车代理功能群集指示与控车代理设备绑定的控车客户端。
在本申请实施例中，控车代理设备中可以设置一个群集，用来存储和维护与控车代理设备绑定的控车客户端。
在一些实施例中，控车代理设备也可以通过群集之外的其它方式(比如绑定关系表)来指示与控车代理设备绑定的控车客户端。
其中，一个控车代理设备可以绑定多个控车客户端，每个控车客户端可以对应一个控车客户端设备。
在一些实施例中，车代理功能群集中包含与控车代理设备绑定的控车客户端的信息；其中，与控车代理设备绑定的控车客户端的信息，包括以下信息中的至少一种：
与控车代理设备绑定的控车客户端的标识信息；
与控车代理设备绑定的控车客户端的绑定类型的信息；
与控车客户端设备绑定的车辆的标识信息。
在本申请实施例中，除了上述信息之外，与控车代理设备绑定的控车客户端的信息还可以包含其它信息，比如，与控车代理设备绑定的控车客户端的名称、生产厂商、软件版本， 以及，与控车客户端设备绑定的车辆的名称、生产厂商、软件版本等信息。
在一些实施例中，控车客户端设备中包含车客户端功能群集(CarClient Cluster)；
车客户端功能群集指示与控车客户端设备绑定的控车代理。
在本申请实施例中，控车客户端设备中也可以设置一个群集，用来存储和维护与控车客户端设备绑定的控车代理。
在一些实施例中，控车客户端设备也可以通过群集之外的其它方式(比如绑定关系表)来指示与控车客户端设备绑定的控车代理。
在一些实施例中，车客户端功能群集中包含与控车客户端设备绑定的车辆的信息；
其中，与控车客户端设备绑定的车辆的信息，包括以下信息中的至少一种：
与控车客户端设备绑定的车辆的标识信息；与控车客户端设备绑定的车辆的名称；与车辆绑定的控车代理的标识信息。
在本申请实施例中，除了上述信息之外，与控车客户端设备绑定的车辆的信息还可以包含其它信息，比如，与控车客户端设备绑定的车辆的名称、生产厂商、软件版本，以及，与车辆绑定的控车代理的名称、生产厂商、软件版本等信息。
在一些实施例中，上述将控车客户端设备与控车代理设备绑定的过程可以包括：
控车代理设备向控车客户端设备发送绑定车请求；绑定车请求中包含控车代理设备的标识信息、第一车辆的标识信息；控车客户端设备接收控车代理设备发送的绑定车请求；控车客户端设备将控车代理设备的标识信息，以及第一车辆的标识信息，添加到第一车辆对应的已绑定的车辆的信息；控车客户端设备向控车代理设备返回绑定车响应；绑定车响应中包含第一车辆的标识信息以及绑定状态；控车代理设备接收控车客户端设备返回的绑定车响应；
控车代理设备在绑定状态为绑定成功的情况下，在车代理功能群集中添加控车客户端设备对应的控车客户端的信息、第一车辆的标识信息。
在本申请实施例中，由控车代理设备发起绑定请求，并于控车客户端设备交互绑定的信息，以便两者在各自的群集中存储控车代理设备、控车客户端设备以及第一车辆之间的绑定关系。
在一些实施例中，控车客户端设备将控车代理设备的标识信息，以及第一车辆的标识信息，添加到第一车辆对应的已绑定的车辆的信息，包括：
在车客户端功能群集中已包含第一车辆对应的已绑定的车辆的信息的情况下，在第一车辆对应的已绑定的车辆的信息中添加控车代理设备的标识信息；
在车客户端功能群集中不包含第一车辆对应的已绑定的车辆的信息的情况下，根据控车代理设备的标识信息，以及第一车辆的标识信息，在车客户端功能群集中增加第一车辆对应的已绑定的车辆的信息。
在本申请实施例中，车客户端功能群集中，一个车辆可以绑定多个控车代理，当控车客户端设备接收到绑定车请求后，如果发现已经存在第一车辆对应的已绑定的车辆的信息，则不需要建立新的已绑定的车辆的信息，可以直接在该已绑定的车辆的信息中写入控车代理设备的标识信息。
在另一些实施例中，在车客户端功能群集中已包含第一车辆对应的已绑定的车辆的信息的情况下，控车客户端设备也可以根据控车代理设备的标识信息，以及第一车辆的标识信息，在车客户端功能群集中增加第一车辆对应的已绑定的车辆的信息。也就是说，车客户端功能群集中，当控车客户端设备接收到绑定车请求后，如果发现已经存在第一车辆对应的已绑定的车辆的信息，则可以重新建立一个已绑定的车辆的信息，并在新建的已绑定的车辆的信息中写入控车代理设备的标识信息。
在一些实施例中，绑定车请求中还包含第一车辆的名称；该方法还包括：
在车客户端功能群集中已包含第一车辆对应的已绑定的车辆的信息的情况下，若绑定车请求中包含的第一车辆的第一名称，与第一车辆对应的已绑定的车辆的信息中包含的第一车 辆的第二名称不一致，将第二名称更新为第一名称。
在本申请实施例中，车客户端功能群集中，每个车辆只有唯一的名称，当控车客户端设备接收到绑定车请求后，如果发现已经存在第一车辆对应的已绑定的车辆的信息中，对应该第一车辆的名称与绑定车请求中的第一车辆的名称不同，则根据上述绑定车请求中的车辆的名称，更新第一车辆对应的已绑定的车辆的信息中对应该第一车辆的名称。
在一些实施例中，该方法还包括：控车代理设备向控车客户端设备读取已绑定的车辆的信息。
在本申请实施例中，控车代理设备还可以向控车客户端设备查询其已经绑定了哪些车辆，从而可以从该控车代理设备对应的车辆中选择与控车客户端设备绑定的车辆。
比如，上述选择与控车客户端设备绑定的车辆的过程可以由用户执行；或者，上述选择与控车客户端设备绑定的车辆的过程可以由控车代理设备按照预设的选择规则执行，比如，控车代理设备优先选择控车客户端设备已绑定或未绑定的车辆，与控车客户端设备建立控车代理设备、控车客户端设备以及车辆这三者之间的绑定关系。
在一些实施例中，该方法还包括：在控车代理设备中为控车客户端设备设置控车权限；控车权限是对车辆进行管理的权限。
其中，控车代理设备将建立控车代理设备、控车客户端设备以及车辆这三者之间的绑定关系的过程中，还可以设置控车客户端设备的控车权限。
可选的，上述设置的控车权限，可以是控车客户端设备对当前绑定的车辆的管理权限；或者，上述设置的控车权限，可以是控车客户端设备对所有车辆的管理权限。
实施例一：
(1)手机上实现车代理功能集CarAgent Cluster，记录了绑定的CarClient(控车客户端)。
车代理功能集包含以下属性，定义如下表1所示：
表1
其中，clientInfo结构体定义如下表2所示：
表2
其中，ClientType为该客户端的绑定类型，True为长期绑定，False为临时绑定。
(2)智能家居设备上实现车客户端功能集CarClient Cluster，用于记录CarClient绑定的Car和CarAgent。
车客户端功能集包含以下属性，定义如下表3所示：
表3
其中，carInfo结构体定义如下表4所示：
表4

车客户端功能集包含以下命令，定义如下表5所示：
表5
其中，bindCarReq用于CarAgent绑定一个车到CarClient。所绑定的车用CarID标识。。其参数定义如下表6所示：
表6
bindCarResp参数定义如下表7所示：
表7
其中，Status为绑定状态，True为绑定成功，False为绑定失败。
(3)绑定发现
绑定发现由CarAgent主动发现CarClient，可采用以下方式：
当CarAgent终端处于IP网络环境中时，可采用DNS-SD发现方式发现网络中的CarClient。
当CarAgent终端需要发现所处IP网络以外的CarClient时，可采用BLE发现方式。
①DNS-SD发现
用于发现CarClient的DNS-SD服务名称为：_carclient._matter._tcp
具有CarClient能力的设备应注册DNS-SD发现服务，服务实例名称为设备在智能家居网络中的ID，如设备ID为FC7772401CD0696，则服务实例名称也为FC7772401CD0696。服务实例名称应在家庭网络内具有唯一性。
CarClient的主机名为设备的MAC地址。例如，一个48位MAC地址为B75AFB458ECD的设备，其设备ID为FC7772401CD0696，则应注册以下DNS-SD记录：
dns-sd-R FC7772401CD0696_carclient._matter._tcp.11111
端口号11111此处仅为示例。
CarAgent可以通过DNS-SD发现该CarClient设备的地址和端口号：
dns-sd-L FC7772401CD0696_carclient._matter._tcp FC7772401CD0696._carclient._matter._tcp.local.can be reached at B75AFB458ECD.local.:11111
dns-sd-Gv6 B75AFB458ECD.local fe80::f515:576f:9783:3f30
②BLE发现
当CarAgent或CarClient终端未接入任何网络时或者用户想要发现未在当前网络中的 CarAgent，用户可主动选择采用BLE的方式进行发现。
BLE发现由CarClient主动发起，CarAgent处于监听模式。BLE发现广播中应包含以下信息：ClientID，NetworkInfo(CarClient所在网络信息)，如表8所示：
表8
其中，NetworkID为网络标识，根据网络特点定义如下：
对于Wi-Fi网络，为Wi-Fi网络SSID；
对于Thread网络，为扩展的PAN ID；
对于以太网络，为操作系统的网络接口实例名称；
CarAgent接收到CarClient广播的发现信息后，可选择加入Car Client所在网络或者直接建立BLE连接。
请参考图5，其示出了本申请涉及的一种用于车辆管理的绑定的流程图。在本实施例中，用户可通过手机上实现的CarAgent发现家庭网络中智能电视中实现的CarClient，并发起控车绑定，上述流程可以包括：
发现流程：
S1，手机进入家庭网络，其上的CarAgent采用DNS-SD发现CarClient；同时，手机可监听BLE广播，发现不在家庭网络中的CarClient(此时，也可能接收到家庭网络中的CarClient发出的BLE广播，可通过NetworkID过滤掉这类设备)。用户可选择切换到另一目标网络中进行DNS-SD发现。
S2，CarClient通过DNS-SD服务提供地址信息，进行发现应答。
S3，当发现未绑定的CarClient时，CarAgent提示用户，用户在手机上确认是否需要进行绑定。
S4，双方建立数据通道。
绑定流程：
S5，CarAgent向CarClient发送bindCar Request，包含CarID，车的名称以及CarAgent ID；若CarAgent关联多辆车，则每次仅绑定其中一辆，分多次进行绑定。
S6，CarClient在boundCars属性中添加该车及控车代理。
S7，返回bindCar Response，包含CarID，CarClient ID以及绑定状态。
S8，CarAgent在boundClients属性中添加该CarClient信息，若boundClients属性列表中已存在对应的Client，则在相应的表项中添加该绑定车的CarID。
S9，用户可以在CarAgent上为该CarClient设置控车权限，默认权限为O。
控车流程：
S10，绑定后，CarClient可以通过CarAgent实现控车。
实施例二：
与上述实施例一相比，在群集上的区别在于智能家居设备上的车客户端功能集CarClient Cluster中的carInfo结构体，其中，carInfo结构体定义如下表9所示：
表9
请参考图6，其示出了本申请涉及的一种用于车辆管理的绑定的流程图。在本实施例中，用户可通过手机上实现的CarAgent发现家庭网络中智能电视中实现的CarClient，并发起控车 绑定，该流程可以包括：
发现流程：
S1，手机进入家庭网络，其上的CarAgent采用DNS-SD发现CarClient；同时，手机可监听BLE广播，发现不在家庭网络中的CarClient(此时，也可能接收到家庭网络中的CarClient发出的BLE广播，可通过NetworkID过滤掉这类设备)。用户可选择切换到另一目标网络中进行DNS-SD发现。
S2，CarClient通过DNS-SD服务提供地址信息，进行发现应答。
S3，当发现未绑定的CarClient时，CarAgent提示用户，用户在手机上确认是否需要进行绑定。
S4，双方建立数据通道。
绑定流程：
S5，CarAgent通过读取boundCars属性查询CarClient已绑定的车。
S6，CarClient返回查询结果，包含车的CarID，车的名称以及CarAgent ID。
S7，用户选择绑定到上一步返回的CarID，或者新的CarID或CarName。
S8，用户可以在CarAgent上为该CarClient设置控车权限，默认权限为O。
S9，CarAgent向CarClient发送bindCar Request，包含CarID，车的名称以及CarAgent ID；当CarID已存在于boundCars列表中时，该命令的执行应认为是向CarID对应的Entry添加一个CarAgent。若CarName与当前boundCars列表中对应的名称不同，则应认为是修改车所显示的名称。
S10，CarClient在boundCars属性中添加该车及控车代理。
S11，返回bindCar Response，包含CarID，CarClient ID以及绑定状态。
S12，CarAgent在boundClients属性中添加该CarClient信息，若boundClients属性列表中已存在对应的Client，则在相应的表项中添加该绑定车的CarID。
控车流程：
S13，绑定后，CarClient可以通过CarAgent实现控车。
请参考图7，其示出了本申请一个实施例提供的用于车辆管理的绑定装置的框图。该用于车辆管理的绑定装置700具有实现上述图2或图4所示的方法中，由控车代理设备执行的功能。如图7所示，该装置可以包括：
绑定模块701，用于将控车客户端设备与所述控车代理设备绑定。
在一些实施例中，所述绑定模块701，用于将所述控车客户端设备、所述控车代理设备以及第一车辆进行绑定。
在一些实施例中，所述控车代理设备中包含车代理功能群集；
所述车代理功能群集指示与所述控车代理设备绑定的控车客户端。
在一些实施例中，所述车代理功能群集中包含与所述控车代理设备绑定的控车客户端的信息；
其中，与所述控车代理设备绑定的控车客户端的信息，包括以下信息中的至少一种：
与所述控车代理设备绑定的控车客户端的标识信息；
与所述控车代理设备绑定的控车客户端的绑定类型的信息；
与所述控车客户端设备绑定的车辆的标识信息。
在一些实施例中，所述绑定模块701，用于，
向所述控车客户端设备发送绑定车请求；所述绑定车请求中包含所述控车代理设备的标识信息、所述第一车辆的标识信息；
接收所述控车客户端设备返回的绑定车响应；所述绑定车响应中包含所述第一车辆的标识信息、绑定状态；
在所述绑定状态为绑定成功的情况下，在所述车代理功能群集中添加所述控车客户端设备对应的控车客户端的信息、所述第一车辆的标识信息。
在一些实施例中，所述装置还包括：
读取模块，用于向所述控车客户端设备读取已绑定的车辆的信息。
在一些实施例中，所述装置还包括：
权限设置模块，用于在所述控车代理设备中，为所述控车客户端设备设置控车权限；所述控车权限是对车辆进行管理的权限。
在一些实施例中，所述管理包括以下至少一种：
对车辆进行控制；
对车辆的状态信息进行查看；
对车辆的状态信息进行订阅。
在一些实施例中，所述装置还包括：
发现模块，用于发现所述控车客户端设备。
在一些实施例中，所述发现模块，用于在所述控车代理设备处于IP网络环境下，采用DNS-SD发现方式发现所述控车客户端设备。
在一些实施例中，所述发现模块，用于，
获取所述控车客户端设备的DNS-SD记录，所述DNS-SD记录中包含所述控车客户端设备的标识信息；
根据所述DNS-SD记录获取所述控车客户端设备的地址和端口号。
在一些实施例中，所述发现模块，用于通过低功耗蓝牙BLE方式发现所述控车客户端设备。
在一些实施例中，所述发现模块，用于，
接收所述控车客户端设备发送的BLE广播；
根据所述BLE广播获取所述控车客户端设备的信息。
在一些实施例中，所述BLE广播中包含以下信息中的至少一种：
所述控车客户端设备的标识信息；
所述控车客户端设备的网络信息。
请参考图8，其示出了本申请一个实施例提供的用于车辆管理的绑定装置的框图。该用于车辆管理的绑定装置800具有实现上述图3或图4所示的方法中，由控车代理设备执行的功能。如图8所示，该装置可以包括：
绑定模块801，用于将所述控车客户端设备与控车代理设备绑定。
在一些实施例中，所述绑定模块801，用于将所述控车客户端设备、所述控车代理设备以及第一车辆进行绑定。
在一些实施例中，所述控车客户端设备中包含车客户端功能群集；
所述车客户端功能群集指示与所述控车客户端设备绑定的控车代理。
在一些实施例中，所述车客户端功能群集中包含与所述控车客户端设备绑定的车辆的信息；
其中，与所述控车客户端设备绑定的车辆的信息，包括以下信息中的至少一种：
与所述控车客户端设备绑定的车辆的标识信息；
与所述控车客户端设备绑定的车辆的名称；
与所述车辆绑定的控车代理的标识信息。
在一些实施例中，所述绑定模块801，用于，
接收所述控车代理设备发送的绑定车请求；所述绑定车请求中包含所述控车代理设备的标识信息、第一车辆的标识信息；
将所述控车代理设备的标识信息，以及所述第一车辆的标识信息，添加到所述第一车辆对应的已绑定的车辆的信息；
向所述控车代理设备返回绑定车响应；所述绑定车响应中包含所述第一车辆的标识信息以及绑定状态。
在一些实施例中，所述绑定模块801，用于，
在所述车客户端功能群集中已包含所述第一车辆对应的已绑定的车辆的信息的情况下，在所述第一车辆对应的已绑定的车辆的信息中添加所述控车代理设备的标识信息；
在所述车客户端功能群集中不包含所述第一车辆对应的已绑定的车辆的信息的情况下，根据所述控车代理设备的标识信息，以及所述第一车辆的标识信息，在所述车客户端功能群集中增加所述第一车辆对应的已绑定的车辆的信息。
在一些实施例中，所述绑定车请求中还包含所述第一车辆的名称；所述装置还包括：
名称更新模块，用于在所述车客户端功能群集中已包含所述第一车辆对应的已绑定的车辆的信息的情况下，若所述绑定车请求中包含的所述第一车辆的第一名称，与所述第一车辆对应的已绑定的车辆的信息中包含的所述第一车辆的第二名称不一致，将所述第二名称更新为所述第一名称。
在一些实施例中，所述装置还包括：
注册模块，用于在所述控车客户端设备处于IP网络环境下，注册DNS-SD记录；所述DNS-SD记录用于所述控车代理设备发现所述控车客户端设备。
在一些实施例中，所述装置还包括：
发送模块，用于发送BLE广播；所述BLE广播所述控车代理设备发现所述控车客户端设备。
在一些实施例中，所述BLE广播中包含以下信息中的至少一种：
所述控车客户端设备的标识信息；
所述控车客户端设备的网络信息。
请参考图9，其示出了本申请一个实施例提供的计算机设备900的结构示意图。该计算机设备900可以包括：处理器901、接收器902、发射器903、存储器904和总线905。
处理器901包括一个或者一个以上处理核心，处理器901通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。接收器902和发射器903可以实现为一个通信组件，该通信组件可以是一块通信芯片。该通信芯片也可以称为收发器。存储器904通过总线905与处理器901相连。存储器904可用于存储计算机程序，处理器901用于执行该计算机程序，以实现上述方法实施例中的各个步骤。
此外，存储器904可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器，可擦除可编程只读存储器，静态随时存取存储器，只读存储器，磁存储器，快闪存储器，可编程只读存储器。
在一个示例性的方案中，当计算机设备900实现为上述控车代理设备时，所述处理器901和/或收发器，用于将所述控车客户端设备与控车代理设备绑定。其中，上述计算机设备900中的处理器901和/或收发器执行的过程可以参考图2或图4任一所示的方法中，由控车代理设备执行的各个步骤。
在一个示例性的方案中，当计算机设备900实现为控车客户端设备时，所述处理器901和/或收发器，用于将所述控车客户端设备与控车代理设备绑定。其中，上述计算机设备900中的处理器901和/或收发器执行的过程可以参考上述图3或图4任一所示的方法中，由控车客户端设备执行的各个步骤。
本申请实施例还提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序， 所述计算机程序由处理器加载并执行以实现上述图2、图3或图4所示的方法中，由控车代理设备或者控车客户端设备执行的全部或者部分步骤。
本申请还提供了一种芯片，该芯片包括电路结构，该芯片用于在计算机设备中运行，以使得计算机设备执行上述图4、图5或图7所示的方法中由控车代理设备或者控车客户端设备执行的全部或者部分步骤。
本申请还提供了一种计算机程序产品，该计算机程序产品或计算机程序包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得计算机设备执行上述图2、图3或图4所示的方法中，由控车代理设备或者控车客户端设备执行的全部或者部分步骤。
本申请还提供了一种计算机程序，该计算机程序由计算机设备的处理器执行，以实现上述图2、图3或图4所示的方法中，由控车代理设备或者控车客户端设备执行的全部或者部分步骤。

Claims (31)

  1. 一种用于车辆管理的绑定方法，其特征在于，所述方法由控车代理设备执行，所述方法包括：
    将控车客户端设备与所述控车代理设备绑定。
  2. 根据权利要求1所述的方法，其特征在于，所述将所述控车客户端设备与所述控车代理设备绑定，包括：
    将所述控车客户端设备、所述控车代理设备以及第一车辆进行绑定。
  3. 根据权利要求1或2所述的方法，其特征在于，所述控车代理设备中包含车代理功能群集；
    所述车代理功能群集指示与所述控车代理设备绑定的控车客户端。
  4. 根据权利要求3所述的方法，其特征在于，所述车代理功能群集中包含与所述控车代理设备绑定的控车客户端的信息；
    其中，与所述控车代理设备绑定的控车客户端的信息，包括以下信息中的至少一种：
    与所述控车代理设备绑定的控车客户端的标识信息；
    与所述控车代理设备绑定的控车客户端的绑定类型的信息；
    与所述控车客户端设备绑定的车辆的标识信息。
  5. 根据权利要求3或4所述的方法，其特征在于，所述将所述控车客户端设备与所述控车代理设备绑定，包括：
    向所述控车客户端设备发送绑定车请求；所述绑定车请求中包含所述控车代理设备的标识信息、所述第一车辆的标识信息；
    接收所述控车客户端设备返回的绑定车响应；所述绑定车响应中包含所述第一车辆的标识信息、绑定状态；
    在所述绑定状态为绑定成功的情况下，在所述车代理功能群集中添加所述控车客户端设备对应的控车客户端的信息、所述第一车辆的标识信息。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述方法还包括：
    向所述控车客户端设备读取已绑定的车辆的信息。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述方法还包括：
    在所述控车代理设备中，为所述控车客户端设备设置控车权限；所述控车权限是对车辆进行管理的权限。
  8. 根据权利要求7所述的方法，其特征在于，所述管理包括以下至少一种：
    对车辆进行控制；
    对车辆的状态信息进行查看；
    对车辆的状态信息进行订阅。
  9. 根据权利要求1至8任一所述的方法，其特征在于，所述方法还包括：
    发现所述控车客户端设备。
  10. 根据权利要求9所述的方法，其特征在于，所述发现所述控车客户端设备包括：
    在所述控车代理设备处于IP网络环境下，采用DNS-SD发现方式发现所述控车客户端设备。
  11. 根据权利要求10所述的方法，其特征在于，所述在所述控车代理设备处于IP网络环境下，采用DNS-SD发现方式发现所述控车客户端设备，包括：
    获取所述控车客户端设备的DNS-SD记录，所述DNS-SD记录中包含所述控车客户端设备的标识信息；
    根据所述DNS-SD记录获取所述控车客户端设备的地址和端口号。
  12. 根据权利要求9所述的方法，其特征在于，所述发现所述控车客户端设备包括：
    通过低功耗蓝牙BLE方式发现所述控车客户端设备。
  13. 根据权利要求12所述的方法，其特征在于，所述通过低功耗蓝牙BLE方式发现所述控车客户端设备，包括：
    接收所述控车客户端设备发送的BLE广播；
    根据所述BLE广播获取所述控车客户端设备的信息。
  14. 根据权利要求13所述的方法，其特征在于，所述BLE广播中包含以下信息中的至少一种：
    所述控车客户端设备的标识信息；
    所述控车客户端设备的网络信息。
  15. 一种用于车辆管理的绑定方法，其特征在于，所述方法由控车客户端设备执行，所述方法包括：
    将所述控车客户端设备与控车代理设备绑定。
  16. 根据权利要求15所述的方法，其特征在于，所述将所述控车客户端设备与控车代理设备绑定，包括：
    将所述控车客户端设备、所述控车代理设备以及第一车辆进行绑定。
  17. 根据权利要求15或16所述的方法，其特征在于，所述控车客户端设备中包含车客户端功能群集；
    所述车客户端功能群集指示与所述控车客户端设备绑定的控车代理。
  18. 根据权利要求17所述的方法，其特征在于，所述车客户端功能群集中包含与所述控车客户端设备绑定的车辆的信息；
    其中，与所述控车客户端设备绑定的车辆的信息，包括以下信息中的至少一种：
    与所述控车客户端设备绑定的车辆的标识信息；
    与所述控车客户端设备绑定的车辆的名称；
    与所述车辆绑定的控车代理的标识信息。
  19. 根据权利要求17或18所述的方法，其特征在于，所述将所述控车客户端设备与控车代理设备绑定，包括：
    接收所述控车代理设备发送的绑定车请求；所述绑定车请求中包含所述控车代理设备的标识信息、第一车辆的标识信息；
    将所述控车代理设备的标识信息，以及所述第一车辆的标识信息，添加到所述第一车辆 对应的已绑定的车辆的信息；
    向所述控车代理设备返回绑定车响应；所述绑定车响应中包含所述第一车辆的标识信息以及绑定状态。
  20. 根据权利要求19所述的方法，其特征在于，所述将所述控车代理设备的标识信息，以及所述第一车辆的标识信息，添加到所述第一车辆对应的已绑定的车辆的信息，包括：
    在所述车客户端功能群集中已包含所述第一车辆对应的已绑定的车辆的信息的情况下，在所述第一车辆对应的已绑定的车辆的信息中添加所述控车代理设备的标识信息；
    在所述车客户端功能群集中不包含所述第一车辆对应的已绑定的车辆的信息的情况下，根据所述控车代理设备的标识信息，以及所述第一车辆的标识信息，在所述车客户端功能群集中增加所述第一车辆对应的已绑定的车辆的信息。
  21. 根据权利要求19或20所述的方法，其特征在于，所述绑定车请求中还包含所述第一车辆的名称；
    所述方法还包括：
    在所述车客户端功能群集中已包含所述第一车辆对应的已绑定的车辆的信息的情况下，若所述绑定车请求中包含的所述第一车辆的第一名称，与所述第一车辆对应的已绑定的车辆的信息中包含的所述第一车辆的第二名称不一致，将所述第二名称更新为所述第一名称。
  22. 根据权利要求15至21任一所述的方法，其特征在于，所述方法还包括：
    在所述控车客户端设备处于IP网络环境下，注册DNS-SD记录；所述DNS-SD记录用于所述控车代理设备发现所述控车客户端设备。
  23. 根据权利要求15至21任一所述的方法，其特征在于，所述方法还包括：
    发送BLE广播；所述BLE广播所述控车代理设备发现所述控车客户端设备。
  24. 根据权利要求23所述的方法，其特征在于，所述BLE广播中包含以下信息中的至少一种：
    所述控车客户端设备的标识信息；
    所述控车客户端设备的网络信息。
  25. 一种用于车辆管理的绑定装置，其特征在于，所述装置包括：
    绑定模块，用于将控车客户端设备与所述控车代理设备绑定。
  26. 一种用于车辆管理的绑定装置，其特征在于，所述装置包括：
    绑定模块，用于将所述控车客户端设备与控车代理设备绑定。
  27. 一种计算机设备，其特征在于，所述计算机设备包括处理器、存储器和收发器；
    所述存储器中存储有计算机程序，所述处理器执行所述计算机程序，以使得所述计算机设备实现如上述权利要求1至24任一所述的用于车辆管理的绑定方法。
  28. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序，所述计算机程序用于被处理器执行，以实现如权利要求1至24任一所述的用于车辆管理的绑定方法。
  29. 一种芯片，其特征在于，所述芯片包括电路结构，所述芯片用于在计算机设备中运行，以使得所述计算机设备执行如权利要求1至24任一所述的用于车辆管理的绑定方法。
  30. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机指令，所述计算机指令存储在计算机可读存储介质中；计算机设备的处理器从所述计算机可读存储介质读取所述计算机指令，并执行所述计算机指令，使得所述计算机设备执行如权利要求1至24任一所述的用于车辆管理的绑定方法。
  31. 一种计算机程序，其特征在于，所述计算机程序由计算机设备的处理器执行，以实现如权利要求1至24任一所述的用于车辆管理的绑定方法。
PCT/CN2023/100846 2023-06-16 2023-06-16 用于车辆管理的绑定方法、装置、设备、存储介质及产品 Ceased WO2024254878A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/100846 WO2024254878A1 (zh) 2023-06-16 2023-06-16 用于车辆管理的绑定方法、装置、设备、存储介质及产品
CN202380095206.4A CN120770147A (zh) 2023-06-16 2023-06-16 用于车辆管理的绑定方法、装置、设备、存储介质及产品

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/100846 WO2024254878A1 (zh) 2023-06-16 2023-06-16 用于车辆管理的绑定方法、装置、设备、存储介质及产品

Publications (1)

Publication Number Publication Date
WO2024254878A1 true WO2024254878A1 (zh) 2024-12-19

Family

ID=93851245

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/100846 Ceased WO2024254878A1 (zh) 2023-06-16 2023-06-16 用于车辆管理的绑定方法、装置、设备、存储介质及产品

Country Status (2)

Country Link
CN (1) CN120770147A (zh)
WO (1) WO2024254878A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108831478A (zh) * 2018-06-25 2018-11-16 奇瑞汽车股份有限公司 智能音箱控车方法和装置
CN112051748A (zh) * 2020-09-15 2020-12-08 北京百度网讯科技有限公司 智能家居车载控制方法、装置、设备以及存储介质
EP3873025A1 (en) * 2020-12-10 2021-09-01 Apollo Intelligent Connectivity (Beijing) Technology Co., Ltd. Information processing method, apparatus, device, and readable storage medium
CN114114940A (zh) * 2021-11-19 2022-03-01 蔚来汽车科技(安徽)有限公司 车辆与智能设备的交互方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108831478A (zh) * 2018-06-25 2018-11-16 奇瑞汽车股份有限公司 智能音箱控车方法和装置
CN112051748A (zh) * 2020-09-15 2020-12-08 北京百度网讯科技有限公司 智能家居车载控制方法、装置、设备以及存储介质
EP3873025A1 (en) * 2020-12-10 2021-09-01 Apollo Intelligent Connectivity (Beijing) Technology Co., Ltd. Information processing method, apparatus, device, and readable storage medium
CN114114940A (zh) * 2021-11-19 2022-03-01 蔚来汽车科技(安徽)有限公司 车辆与智能设备的交互方法及系统

Also Published As

Publication number Publication date
CN120770147A (zh) 2025-10-10

Similar Documents

Publication Publication Date Title
US8812670B2 (en) Architecture for virtualized home IP service delivery
US8561147B2 (en) Method and apparatus for controlling of remote access to a local network
WO2023138285A1 (zh) 一种智能家居设备的绑定方法和终端
CN112152969A (zh) 物联网网关及物联网设备接入网关的方法
JPWO2005114926A1 (ja) クライアント機器への接続をルーティングするためのサーバ
WO2004051947A1 (ja) クライアント機器への接続をルーティングするためのサーバ
WO2013107175A1 (zh) 家庭网络设备的控制方法及装置
CN104994158B (zh) 一种通过集中式网关安全控制家电的方法
WO2023108653A1 (zh) 订阅权限信息处理方法、装置、计算机设备及存储介质
WO2023082113A1 (zh) 对桥接设备进行配置的方法、装置、设备及存储介质
WO2024254878A1 (zh) 用于车辆管理的绑定方法、装置、设备、存储介质及产品
WO2024254877A1 (zh) 车辆管理方法、装置、设备、存储介质及程序产品
WO2025218214A1 (zh) 设备管控方法及智能管控设备
CN104320718B (zh) 一种避免多个dmc推送媒体播放产生冲突的方法及装置
CN115474186A (zh) 基于通讯系统的设备发现方法、设备及内网通讯系统
KR20040055446A (ko) 컨트롤 포인트 및 컨트롤 포인트 간의 인식 방법
CN102904978A (zh) 泛在网络内泛在设备实现通用即插即用的方法
WO2025145434A1 (zh) 场景处理方法、装置、设备、存储介质及产品
WO2023130405A1 (zh) 设备配置方法、装置、计算机设备及存储介质
CN118435579A (zh) 设备共享方法、装置、设备、存储介质及程序产品
WO2025147961A1 (zh) 设备信息处理方法、装置、设备、存储介质及产品
WO2024250301A1 (zh) 服务设备的连接管理方法、装置、设备、介质及程序产品
CN119654600A (zh) 设备控制方法、装置、设备、存储介质及程序产品
WO2025107146A1 (zh) 代理绑定方法、装置、设备、存储介质及产品
WO2024031681A1 (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: 23941111

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202380095206.4

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 202380095206.4

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE