Vehicle management method and apparatus, and device, storage medium and program product

Abstract

A vehicle management method and apparatus, and a device, a storage medium and a program product, which belong to the technical field of the Internet of Things. The method is executed by a vehicle-control agent device, and comprises: providing to a vehicle-control client device an agent service for managing a first vehicle (401). The solution expands application scenarios of the Internet of Things, and improves the efficiency of a user managing a vehicle.

Description

Vehicle management method, device, equipment, storage medium and program product Technical Field

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

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

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

[0004] Summary of the Invention

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

[0006] In one aspect, an embodiment of the present application provides a vehicle management method, which is executed by a vehicle control agent device and includes:

[0007] An agent service for managing the first vehicle is provided to the vehicle control client device.

[0008] In one aspect, an embodiment of the present application provides a vehicle management method, which is executed by a vehicle control client device and includes:

[0009] Manage vehicles through vehicle control agent equipment.

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

[0011] The proxy module is used to provide a proxy service for managing the first vehicle to the vehicle control client device.

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

[0013] The management module is used to manage vehicles through the vehicle control agent device.

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

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

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

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

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

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

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

[0021] Through the technical solution provided in the embodiments of the present application, 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 mode between the Internet of Things device and the vehicle, expanding the application scenarios of the Internet of Things, and improving the user's management efficiency of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0023] FIG2 is a schematic diagram of an interaction for OCF involved in this application;

[0024] FIG3 is a schematic diagram of the interaction of device discovery involved in this application;

[0025] FIG4 is a flow chart of a vehicle management method provided by one embodiment of the present application;

[0026] FIG5 is a flow chart of a vehicle management method provided by one embodiment of the present application;

[0027] FIG6 is a flowchart of a vehicle management process according to an embodiment of the present application;

[0028] FIG7 is a flow chart of a vehicle management method provided by one embodiment of the present application;

[0029] FIG8 is a flow chart of a vehicle management method involved in this application;

[0030] FIG9 is a flow chart of a vehicle management method involved in this application;

[0031] FIG10 is a block diagram of a vehicle management device provided by one embodiment of the present application;

[0032] FIG11 is a block diagram of a vehicle management device provided by one embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0053] 1) Open Connectivity Foundation (OCF) cloud-to-cloud interface

[0054] The OCF Universal Cloud Interface is built on secure and industry-standard underlying technologies, with OAuth2.0 providing the necessary authentication and Hypertext Transfer Protocol Secure (HTTPS) providing a secure connection. This set of clearly defined Application Programming Interfaces (APIs) enables the acquisition and update of device information, as well as the subscription of device events. The use of the API is independent of the data model, so all data models that OCF has published and will publish can be used for this set of APIs. The data model is a description of the payload of the RESTful verb, and the OCF Universal Cloud Interface transparently transmits the data model without making any modifications to it. The media type used by the payload can be determined through negotiation of the Accept header of the HTTP mechanism. Please refer to Figure 2, which shows an interaction diagram for OCF involved in this application.

[0055] After the account is linked, the client cloud can call the device API provided by the device cloud to obtain complete device information. A single HTTP GET request is sufficient to trigger the required HTTP response, which contains the device information hosted by the user (on the device cloud), as well as the resources and current status of these devices. Figure 3 shows an interactive diagram of the device discovery involved in this application. From a user experience perspective, users experience the same experience when operating devices on the same cloud platform and devices on linked cloud platforms.

[0056] The request interfaces mentioned above are shown in Table 1 below:

[0057] Table 1

[0058] The response payload attributes are shown in Table 2 below:

[0059] Table 2

[0060] The device attributes are shown in Table 3 below:

[0061] Table 3

[0062] 2) Car Control

[0063] S1, IOTClient (IoT client) discovers the agent capabilities of IOTAgent (IoT agent);

[0064] S2, IOTClient obtains the controllable device list: getDeviceListReq;

[0065] S3, IOTAgent generates a list of controllable devices. If IOTAgent does not save this content, you need to obtain it from IOTEcosystem;

[0066] S4, IOTClient sends the controllable device list to IOTAgent: getDeviceListResp;

[0067] S5, IOTClient displays the list of controllable devices;

[0068] S6: The user issues a command to control the IOT device, and the IOTClient sends the device control command to the IOTAgent: Source:IOTClient Destination:IOTAgentpath:targetNodeID / [targetOperationObject];

[0069] In the IOTClient-to-IOTAgent access permission, set the agent capability to "Accessible by Everyone" and the IOTAgent needs to save the control list sent to the IOTClient. The IOTClient can only access devices on the control list.

[0070] After receiving the above message, IOTAgent needs to convert the message into Source:IOTAgent Destination:targetNodeIDpath:targetNodeID / [targetOperationObject] and send it to the IOT ecological device.

[0071] Resource Cluster: This cluster is only contained in endpoint 0. The control end can obtain the server-side device resource information by reading the server-side cluster.

[0072] Cluster definitions are shown in Table 4 below:

[0073] Table 4

[0074] Attribute definitions are shown in Table 5 below:

[0075] Table 5

[0076] EpStruct is defined as shown in Table 6 below:

[0077] Table 6

[0078] DeviceTypeStruct is defined as shown in Table 7 below:

[0079] Table 7

[0080] Users can obtain a list of all endpoints and device types under the endpoints, as well as the Server / Client Cluster under each endpoint, by reading the Resource Cluster under endpoint0.

[0081] Users can obtain the Cluster's FeatureMap, Attribute List, Command List, and Event List by reading the Global Elements under the Cluster.

[0082] Among them, the above-mentioned OCF solution is suitable for the client control interface in cloud-to-cloud interconnection. Its implementation on the client side is relatively fixed and lacks the flexibility of local device connection. The connection between IOTClient and IOTAgent in the car-to-home solution is simple and is not suitable for more complex home network interconnection environments.

[0083] Please refer to FIG4 , which shows a flow chart of a vehicle management method provided by one embodiment of the present application. The method may be executed by a vehicle control agent device. For example, the vehicle control agent device may be the agent device 120 in the network architecture shown in FIG1 . The method may include the following steps:

[0084] Step 401: Provide an agent service for managing a first vehicle to a vehicle control client device.

[0085] In the embodiment of the present application, the above-mentioned vehicle control agent device may correspond to at least one vehicle, and the at least one vehicle includes the above-mentioned first vehicle.

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

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

[0088] Among them, the above-mentioned vehicle control proxy device can establish connections with the vehicle control client device and the first vehicle respectively. When the user needs to manage the first vehicle through the vehicle control client device, the vehicle control proxy device can act as an agent 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.

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

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

[0091] controlling the first vehicle;

[0092] Checking status information of the first vehicle;

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

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

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

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

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

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

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

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

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

[0102] To sum up, in the embodiments of the present application, 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 mode 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.

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

[0104] Step 501: Manage a first vehicle through a vehicle control agent device.

[0105] To sum up, in the embodiments of the present application, 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 mode between the Internet of Things device and the vehicle, expanding the application scenarios of users managing vehicles, and improving the efficiency of users managing vehicles.

[0106] Through the solutions shown in Figures 4 and 5 of the present application, the vehicle control client device can manage the vehicle through the vehicle control proxy device, thereby realizing the application scenario of managing the vehicle through the Internet of Things device.

[0107] Taking the example of a vehicle control agent device being a smartphone, a vehicle control client device being a smart TV, and the smartphone and the smart TV being connected via an IoT system, and the smartphone and the vehicle being connected via a cloud server, please refer to FIG6 , which shows a process framework diagram of vehicle management provided by one embodiment of the present application. In one possible application scenario, as shown in FIG6 , a smartphone 61 is connected to a smart TV 62 in an IoT ecosystem (for example, the IoT ecosystem can be a smart home system), and at the same time, is also connected to a cloud server 63 via a wireless network, and the cloud server 63 is connected to a vehicle 64 via a wireless network.

[0108] When a user is at home and needs to manage a vehicle 64 parked outside, they can turn on their smart TV 62 and call up the vehicle management interface of the smart TV 62. The vehicle management interface displays the vehicles that can be managed via the smartphone 61. The user can then select the vehicle 64 on the vehicle management interface and send a management request to the smartphone 61. The management request can be a request to view / subscribe to the status information of the vehicle 64 or a request to control the vehicle 64. After receiving the management request, the smartphone 61 can return the status information of the vehicle 64 to the smart TV 62 or send a control command to the vehicle 64.

[0109] For example, after a user selects vehicle 64 on the vehicle management interface displayed on smart TV 62 and selects a command to view the status information of vehicle 64, smart TV 62 then sends a request to view the status of vehicle 64 to smartphone 61. Smart phone 61 then returns the status information of vehicle 64 to smart TV 62, including whether the vehicle is locked / unlocked, whether the vehicle's windows are closed / open, the interior temperature, whether the air conditioner is on / off, the air conditioner set temperature, etc. Smart TV 62 displays the above status information on the vehicle management interface. When the user finds that the vehicle is unlocked, they can lock the vehicle through the vehicle management interface. Smart TV 62 then sends a request to lock vehicle 64 to smartphone 61. Smart phone 61 sends a lock command to vehicle 64 via cloud server 63. After receiving the lock command, vehicle 64 locks and returns a lock success / failure response to smartphone 61. Smart phone 61 sends the lock success / failure response to smart TV 62, and smart TV 62 updates the status information displayed on the vehicle management interface based on the lock success / failure response. In addition, when the user needs to continuously monitor one or more statuses of the vehicle 64, the user can subscribe to the one or more statuses from the smartphone 61. For example, if the user needs to continuously monitor the interior temperature of the vehicle 64, the user can subscribe to the interior temperature status through the vehicle management interface. The smart TV 62 then sends a subscription request for the interior temperature of the vehicle 64 to the smartphone 61. The smartphone 61 sends the current interior temperature of the vehicle 64 to the smart TV 62, which then displays the interior temperature in the vehicle management interface. Subsequently, when the smartphone 61 learns that the interior temperature of the vehicle 64 has changed, the smartphone 61 notifies the smart TV 62 of the changed interior temperature, which then updates the interior temperature in the vehicle management interface.

[0110] Please refer to FIG7 , which shows a flow chart of a vehicle management method provided by one embodiment of the present application. The method may be interactively executed by a vehicle control agent device and a vehicle control client device. The vehicle control agent device and the vehicle control client device may be the agent device 120 and the IoT device 110 in the network architecture shown in FIG1 , respectively. The method may include the following steps:

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

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

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

[0114] In the embodiment of the present application, before establishing a connection between the vehicle control proxy device and the vehicle control client device, the vehicle control client device may first discover a connectable vehicle control proxy device.

[0115] In some embodiments, the car control agent device includes a car agent discovery function cluster (CarAgent Discovery Cluster);

[0116] The vehicle agent discovery function cluster is used by the vehicle control client device to discover the vehicle control agent device.

[0117] In some embodiments, the above-mentioned vehicle agent discovery function cluster is used to maintain one or more commands, which can be used for the vehicle control client device and the vehicle control agent device to interact when establishing a data channel, so that the vehicle control client device can discover available vehicle control agent devices around it.

[0118] In other embodiments, the above-mentioned vehicle agent discovery function cluster may also be used for the vehicle control agent device to send information to the vehicle control client device.

[0119] In some embodiments, the car agent discovery function cluster supports at least one of the following commands:

[0120] Discovery proxy request, used by the vehicle control client device to request information about the vehicle control proxy device from the vehicle control proxy device;

[0121] The discovery agent response is used to return the information of the vehicle control agent device to the vehicle control client device.

[0122] The discovery proxy request may be a request sent by the vehicle control client device; the discovery proxy response is a response returned by the vehicle control proxy device to the vehicle control client device, corresponding to the discovery proxy request.

[0123] In some embodiments, the car agent discovery function cluster may also support other commands besides the discovery agent request and discovery agent response. For example, the car agent discovery function cluster may support at least one of the following commands:

[0124] The client announcement message is used to announce the existence of the vehicle control client device to the surrounding vehicle control proxy devices;

[0125] The client declaration response is used to return a response to the vehicle control client device indicating receipt of the client declaration message. Optionally, the client declaration response includes identification information of the vehicle control proxy device.

[0126] Among them, the above-mentioned client declaration message can be sent by the vehicle control client device; the above-mentioned client declaration response can be a response returned by the vehicle control proxy device to the vehicle control client device after receiving the client declaration message, which is used to notify the vehicle control client device that the client declaration message it sent has been successfully received by the vehicle control proxy device.

[0127] In some embodiments, the discovery agent request includes identification information of the second vehicle.

[0128] In some embodiments, the discovery agent request may not include the vehicle identification information.

[0129] In some embodiments, the discovery agent response includes at least one of the following information:

[0130] Identification information of the vehicle control agent device;

[0131] The identification information of the vehicle bound to the vehicle control proxy device.

[0132] In some embodiments, the discovery agent response may also include other information in addition to the identification information of the vehicle control agent device and the identification information of the vehicle bound to the vehicle control agent device. For example, the above discovery agent response may also include the identification information of the vehicle to which the vehicle control agent device is currently connected.

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

[0134] The above-mentioned vehicle identification information may include the vehicle's name, ID, etc.

[0135] In an embodiment of the present application, the vehicle control proxy device may carry the identification information of the vehicle control proxy device in the discovery proxy response, and send the identification information of the vehicle bound to the vehicle control proxy device to the vehicle control client device through other messages other than the discovery proxy response.

[0136] Alternatively, the vehicle control proxy device may carry the identification information of the vehicle bound to the vehicle control proxy device in the discovery proxy response, and send the identification information of the vehicle control proxy device to the vehicle control client device through other messages other than the discovery proxy response.

[0137] Alternatively, the vehicle control proxy device may include its identification information and the identification information of the vehicle bound to it in the discovery proxy response. In this case, the vehicle control client device can use the discovery proxy response to discover available vehicle control proxy devices and which vehicles can be managed by these available vehicle control proxy devices.

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

[0139] The vehicle control client device sends a discovery proxy request; the vehicle control proxy device receives the discovery proxy request sent by the vehicle control client device;

[0140] When the discovery proxy request includes the identifier of the second vehicle, the vehicle control proxy device returns a discovery proxy response to the vehicle control client device when the vehicles bound to the vehicle control proxy device include the second vehicle. That is, the discovery proxy response is sent by the vehicle control proxy device when the vehicles bound to the vehicle control proxy device include the second vehicle; the vehicle control client device receives the discovery proxy response sent by the vehicle control proxy device.

[0141] In an embodiment of the present application, when the vehicle proxy discovery function cluster supports discovery proxy requests, the vehicle control client device can discover the vehicle control proxy device corresponding to a certain vehicle through the discovery proxy request. For example, the discovery proxy request can carry the identification information of the second vehicle to indicate that the discovery proxy request is used to discover the vehicle control proxy device corresponding to the second vehicle. After the vehicle control proxy device receives the above-mentioned discovery proxy request, if it determines that the identification information of the second vehicle carried in the discovery proxy request matches the identification information of a vehicle bound to itself, it can return a discovery proxy response to the vehicle control client device; optionally, if the vehicle control proxy device determines that the identification information of the second vehicle does not match the identification information of any vehicle bound to itself, it may not return a discovery proxy response.

[0142] In some embodiments, when the discovery proxy request includes the identifier of the second vehicle, and when the vehicle control proxy device includes the second vehicle in the vehicles bound to the vehicle control proxy device, the process of returning the discovery proxy response to the vehicle control client device may include:

[0143] If the vehicle control proxy device includes a second vehicle in the vehicles bound to the vehicle control proxy device, and the second vehicle is in an available state (eg, the Accessible state is True), the vehicle control proxy device returns a discovery proxy response to the vehicle control client device.

[0144] On the contrary, if the second vehicle is in an unavailable state (for example, the Accessible state is False), the vehicle control proxy device may not return a discovery proxy response to the vehicle control client device.

[0145] In some embodiments, when a discovery proxy request does not include vehicle identification information, the discovery proxy request can be used to discover a vehicle control proxy device corresponding to any vehicle. For example, a discovery proxy request may not include any vehicle identification information to indicate that the discovery proxy request is used to discover any vehicle control proxy device. Upon receiving the discovery proxy request, the vehicle control proxy device may return a discovery proxy response to the vehicle control client device.

[0146] The vehicle control proxy device corresponding to the second vehicle may be a vehicle control proxy device pre-bound to the second vehicle, or a vehicle control proxy device pre-connected to the second vehicle.

[0147] In some embodiments, the vehicle control client device sending a discovery proxy request includes: the vehicle control client device sending the discovery proxy request within a multicast group. Correspondingly, the vehicle control proxy device receiving the discovery proxy request sent by the vehicle control client device includes: receiving the discovery proxy request sent by the vehicle control client device within the multicast group when the vehicle control client device and the vehicle control proxy device are in the same multicast group.

[0148] In an embodiment of the present application, the vehicle control client device can send the above-mentioned discovery proxy request in a multicast / broadcast manner within its own multicast group, so that the vehicle control proxy devices in the multicast group can respond to the discovery proxy request, thereby discovering possible vehicle control proxy devices in the multicast group. In other words, in this embodiment, for the vehicle control client device to discover the vehicle control proxy device, it is necessary for the vehicle control client device and the vehicle control proxy device to be in the same multicast group, and this multicast group has a unique multicast group ID.

[0149] In some embodiments, before sending the above-mentioned discovery agent request, the vehicle control client device may first send the above-mentioned client declaration message in the multicast group. The vehicle control agent device that receives the client declaration request returns a client declaration response to the vehicle control client device. After that, the vehicle control client device unicasts the above-mentioned discovery agent request to the vehicle control agent device based on the identification information of the vehicle control agent device carried in the client declaration response.

[0150] In step 702 , the vehicle control proxy device provides a proxy service for managing the first vehicle to the vehicle control client device; accordingly, the vehicle control management device manages the first vehicle through the vehicle control proxy device.

[0151] In some embodiments, managing includes at least one of:

[0152] controlling the first vehicle;

[0153] Checking status information of the first vehicle;

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

[0155] In some embodiments, the car control agent device includes a car agent function cluster (CarAgent Cluster);

[0156] The vehicle agent function cluster indicates at least one of the following information:

[0157] Information about the vehicle control client device bound to the vehicle control proxy device;

[0158] Information about the vehicle bound to the vehicle control proxy device.

[0159] Among them, the above-mentioned car proxy function cluster may include information of the car control client device bound to the car control proxy device, or the above-mentioned car proxy function cluster may include information of the vehicle bound to the car control proxy device, or the above-mentioned car proxy function cluster may simultaneously include information of the car control client device bound to the car control proxy device, and information of the vehicle bound to the car control proxy device.

[0160] In some embodiments, the information of the vehicle bound to the vehicle control agent device includes at least one of the following information:

[0161] The identification information of the vehicle bound to the vehicle control agent device;

[0162] Information on the accessibility status of vehicles bound to the vehicle control agent device;

[0163] The endpoint information of the vehicle bound to the vehicle control agent device.

[0164] Among them, the above-mentioned information on the accessibility status of the vehicle bound to the vehicle control proxy device can indicate whether the corresponding vehicle can receive messages sent from the vehicle control proxy device. That is, the accessibility status here refers to whether the message sent from the vehicle control proxy device can reach the vehicle.

[0165] In another embodiment, the above-mentioned information on the accessible status of the vehicle may also be used to indicate whether the corresponding vehicle is currently allowed to access.

[0166] The endpoint information of the vehicle bound to the vehicle control agent device can be used to indicate which endpoints the corresponding vehicle has, and can be further used to indicate which information in the corresponding vehicle can be viewed or subscribed to, which functions can be controlled, etc.

[0167] In some embodiments, the car agent functional cluster supports at least one of the following commands:

[0168] Get vehicle information request, used to obtain vehicle information of the vehicle bound to the vehicle control proxy device from the vehicle control proxy device;

[0169] The vehicle information acquisition response is used to return the vehicle information of the vehicle bound to the vehicle control proxy device to the sender of the vehicle information acquisition request.

[0170] Optionally, the above-mentioned vehicle information acquisition response may also be used to return the vehicle information of the vehicle that is bound to the vehicle control proxy device and currently connected to the vehicle control proxy device to the sender of the vehicle information acquisition request.

[0171] In some embodiments, the vehicle information acquisition request may include a vehicle information acquisition identifier, indicating that the request is for acquiring vehicle information associated with the vehicle control proxy device. For example, the identifier may be a bit value at a specific bit position. For example, a bit value of 1 or 0 at the specific bit position indicates that the request is for acquiring vehicle information associated with the vehicle control proxy device.

[0172] In some embodiments, the above-mentioned vehicle information acquisition response includes a vehicle information list; the vehicle information list includes at least one item of vehicle information.

[0173] For example, the above vehicle information list may include a list consisting of multiple pieces of vehicle information, and each piece of vehicle information corresponds to the information of one vehicle.

[0174] In other embodiments, the above-mentioned vehicle information acquisition response includes single vehicle information. For a vehicle control proxy device, if the vehicle control proxy device is bound to multiple vehicles, multiple vehicle information responses can be sent, and each vehicle information response carries the vehicle information of one vehicle.

[0175] In some embodiments, the vehicle information includes at least one of the following information:

[0176] The identification information of the vehicle bound to the vehicle control agent device;

[0177] The endpoint information of the vehicle bound to the vehicle control agent device.

[0178] Optionally, the vehicle information may further include other information, such as the name of the vehicle bound to the vehicle control proxy device, the accessibility status of the vehicle bound to the vehicle control proxy device, the connection status / online status of the vehicle bound to the vehicle control proxy device, etc. The embodiment of the present application does not limit the type of information included in the vehicle information.

[0179] In some embodiments, the endpoint information of the vehicle bound to the vehicle control agent device includes:

[0180] The endpoint structure of the vehicle endpoint bound to the vehicle control proxy device;

[0181] Or, the endpoint number of the vehicle endpoint bound to the vehicle control proxy device.

[0182] The endpoint structure and endpoint number may be as shown in Table 6 above.

[0183] Alternatively, the above-mentioned endpoint structure may also have certain differences from the above-mentioned Table 6. For example, the above-mentioned endpoint structure may remove or add some items based on Table 6. For example, the above-mentioned endpoint structure may add the endpoint availability status (indicating whether the corresponding endpoint is currently available), the endpoint management authority, etc. based on the above-mentioned Table 6; for another example, the above-mentioned endpoint structure may remove the device type list based on the above-mentioned Table 6, etc.

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

[0185] The vehicle control client device sends a request for obtaining vehicle information to the vehicle control proxy device; the vehicle control proxy device receives the request for obtaining vehicle information sent by the vehicle control client device;

[0186] The vehicle control proxy device returns a vehicle information acquisition response to the vehicle control client device; the vehicle control client device receives the vehicle information acquisition response returned by the vehicle control proxy device; the vehicle information acquisition response is used to indicate the vehicle information of the vehicle bound to the vehicle control proxy device.

[0187] In some embodiments, the vehicle control client device includes a vehicle client function cluster; the vehicle client function cluster is used to record vehicles and agents bound to the vehicle control client device.

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

[0189] Get current proxy request, used to obtain information about the proxy currently associated with the third vehicle in the vehicle control client device;

[0190] Obtaining a current proxy response, which is used to indicate information about the proxy currently associated with the third vehicle in the vehicle control client device;

[0191] The current proxy request is set to set the proxy currently associated with the fourth vehicle in the vehicle control client device.

[0192] The proxy currently associated with the third vehicle refers to the vehicle control client device currently managing the third vehicle through the vehicle control proxy device corresponding to the proxy.

[0193] By obtaining the current proxy request, obtaining the current proxy response, and setting the current proxy request, the vehicle control proxy device can view the proxy currently used by the vehicle control client device to manage a certain vehicle, and set the proxy currently used by the vehicle control client device to manage a certain vehicle.

[0194] In some embodiments, the method further includes: the vehicle control proxy device sends a current proxy acquisition request to the vehicle control client device, and the vehicle control client device receives the current proxy acquisition request sent by the vehicle control proxy device; the vehicle control client device returns a current proxy acquisition response to the vehicle control proxy device, and the vehicle control proxy device receives the current proxy acquisition response returned by the vehicle control client device.

[0195] In some embodiments, the identification information of the third vehicle is included in the current proxy request. For example, after receiving the current proxy request, the vehicle control client device may query the locally stored information of the proxy currently associated with the third vehicle based on the identification information of the third vehicle, and then return a current proxy response based on the found information.

[0196] The get current proxy response includes information about the proxy currently associated with the third vehicle in the vehicle control client device. For example, after receiving the get current proxy response, the vehicle control proxy device can read information about the proxy currently associated with the third vehicle in the vehicle control client device.

[0197] Optionally, the current proxy request may also include a path to the identification information of the third vehicle. After receiving the current proxy request, the vehicle control client device may obtain the identification information of the third vehicle through the path to the identification information of the third vehicle.

[0198] Optionally, the above-mentioned current proxy request may also include the path of the information of the proxy currently associated with the third vehicle in the vehicle client device. After the vehicle control proxy device receives the above-mentioned obtain current proxy response, it can obtain the information of the proxy currently associated with the third vehicle in the above-mentioned vehicle control client device through the path of the information of the proxy associated with the third vehicle.

[0199] In some embodiments, the above-mentioned obtaining of the current proxy response includes: identification information of the proxy currently associated with the third vehicle in the vehicle control client device.

[0200] That is to say, in the above-mentioned vehicle control client device, the information of the agent currently associated with the third vehicle may be identification information of the corresponding agent, such as the name, ID, etc. of the corresponding agent.

[0201] In some embodiments, obtaining the current proxy response further includes: identification information of the third vehicle.

[0202] In some embodiments, the method further includes: the vehicle control proxy device sends a set current proxy request to the vehicle control client device; the set current proxy request is used to set the proxy currently associated with the fourth vehicle in the vehicle control client device as the vehicle control proxy device; the vehicle control client device receives the set current proxy request sent by the vehicle control proxy device, and according to the set current proxy request, sets the proxy currently associated with the fourth vehicle in the vehicle control client device as the vehicle control proxy device.

[0203] In which, in the process of setting the current proxy request, the above-mentioned vehicle control client device sets the proxy currently associated with the fourth vehicle in the vehicle control client device as the vehicle control proxy device. When the vehicle control client device determines that it has been bound to the vehicle control proxy device and the above-mentioned fourth vehicle, it sets the proxy currently associated with the fourth vehicle in the vehicle control client device as the vehicle control proxy device.

[0204] Among them, the above-mentioned setting current proxy request can include the identification information of the fourth vehicle. The vehicle control client device can query the project of the agent currently associated with the fourth vehicle according to the setting current proxy request, and replace the identification information of the agent in the project of the agent currently associated with the fourth vehicle with the identification information of the above-mentioned vehicle control proxy device, so as to set the agent currently associated with the fourth vehicle in the vehicle control client device as the vehicle control proxy device.

[0205] Alternatively, the vehicle control client device queries the project of the agent currently associated with the fourth vehicle based on the request to set the current agent, deletes the queried project, and creates a new project of the agent currently associated with the fourth vehicle. The identification information of the agent in the newly created project is the identification information of the above-mentioned vehicle control agent device, thereby setting the agent currently associated with the fourth vehicle in the vehicle control client device as the vehicle control agent device.

[0206] In some embodiments, the car client functional cluster supports current car agent change events;

[0207] The current vehicle proxy change event is used to indicate that the proxy currently associated with the fourth vehicle has changed in the vehicle control client device.

[0208] In the embodiment of the present application, the vehicle client function cluster can also record or send a current vehicle proxy change event, thereby recording / retaining a change request for the proxy associated with the vehicle.

[0209] In some embodiments, the current vehicle agent change event includes at least one of the following information:

[0210] identification information of the fourth vehicle;

[0211] identification information of the last agent associated with the fourth vehicle in the vehicle control client device;

[0212] Identification information of the agent currently associated with the fourth vehicle in the vehicle control client device.

[0213] Optionally, the current vehicle agent change event includes identification information of two or more or all agents previously associated with the fourth vehicle.

[0214] In an embodiment of the present application, the current vehicle agent change event can record which vehicle-associated agent changes from which agent to which agent, thereby being able to record the change process of the vehicle-associated agent in detail and improving the perceptibility and traceability of the agent change.

[0215] In some embodiments, the vehicle control proxy device provides a proxy service for managing the first vehicle to the vehicle control client device. The process of the vehicle control client device managing the vehicle through the vehicle control proxy device may include:

[0216] The vehicle control client device sends a vehicle control instruction to the vehicle control proxy device, where the vehicle control instruction is used to control the first vehicle, so that the vehicle control proxy device sends a control instruction to the first vehicle based on the vehicle control instruction, and the control instruction is executed by the first vehicle to realize the remote control function of the first vehicle; the vehicle control proxy device receives the vehicle control instruction sent by the vehicle control client device; the vehicle control proxy device sends a control instruction to the first vehicle based on the vehicle control instruction, and the control instruction is executed by the first vehicle to realize the control function of the first vehicle.

[0217] Among them, the above-mentioned vehicle control instructions and control instructions can contain the same content, that is, the vehicle control instructions sent by the vehicle control client device can be executed by the first vehicle, and the vehicle control agent device sends the content in the vehicle control instructions as control instructions to the first vehicle.

[0218] Alternatively, the above-mentioned vehicle control instructions and control instructions may contain different contents. For example, the vehicle control instructions sent by the vehicle control client device cannot be executed by the first vehicle. The vehicle control agent device converts the vehicle control instructions into control instructions executable by the first vehicle and sends the control instructions to the first vehicle.

[0219] In some embodiments, the vehicle control proxy device sends a control instruction to the first vehicle based on the vehicle control instruction, including: the vehicle control proxy device sends a control instruction to the first vehicle based on the vehicle control instruction when the vehicle control client device has authority to control the first vehicle.

[0220] In an embodiment of the present application, the vehicle control proxy device can record the authority of the vehicle control client device to manage the first vehicle. After receiving the vehicle control instruction, the vehicle control proxy device can query whether the vehicle control client device has the authority to control the first vehicle. If so, a control instruction is sent to the first vehicle based on the vehicle control instruction; optionally, if the vehicle control client device does not have the authority to control the first vehicle, a failure response can be returned to the vehicle control client device, and the failure response can carry the reason for the failure: lack of control authority.

[0221] The method for setting the authority of the vehicle control client device to control the first vehicle may include: the vehicle control proxy device uses an access control list ACL to set access control authority for each control interface of the vehicle accessible to the vehicle control client device.

[0222] In some embodiments, the above-mentioned vehicle control client device has the authority to control the first vehicle, which may be to indicate that the vehicle control client device has the authority corresponding to the requested control of the first vehicle; for example, if the above-mentioned vehicle control instruction requests to lock / unlock the vehicle, then the above-mentioned vehicle control client device has the authority corresponding to the requested control of the first vehicle, which means that the vehicle control client device has the authority to lock / unlock the first vehicle.

[0223] Alternatively, the above-mentioned vehicle control client device has the authority to control the first vehicle, which may mean that the vehicle control client device has a single authority to trigger the vehicle control proxy device to send a control instruction to the first vehicle, that is, the authority does not distinguish between the functions requested to be controlled, or in other words, the authority applies to all functions of the vehicle.

[0224] For example, the above-mentioned authority to control the first vehicle may be a single authority or may include multiple authorities of different levels; when it includes multiple authorities of different levels, the above-mentioned process of querying whether the vehicle control client device has the authority to control the first vehicle may refer to querying whether the current authority of the vehicle control client device to control the first vehicle is equal to or higher than the authority required for the above-mentioned vehicle control instruction. If so, it is determined that the vehicle control client device has the authority to control the first vehicle; otherwise, it is determined that the vehicle control client device does not have the authority to control the first vehicle.

[0225] In other embodiments, the vehicle control proxy device may also send a control instruction to the first vehicle based on the vehicle control instruction without querying whether the vehicle control client device has the authority to control the first vehicle.

[0226] In some embodiments, the path of the vehicle control instruction includes: a target operation object in a service cluster of a target endpoint in the vehicle control proxy device;

[0227] Sending a control instruction to the first vehicle based on the vehicle control instruction includes: converting the vehicle control instruction into a control instruction based on a path of the vehicle control instruction.

[0228] In an embodiment of the present application, when the path of the vehicle control instruction includes the target operation object in the service cluster of the target endpoint in the vehicle control proxy device, the vehicle control proxy device can determine which function of the first vehicle the vehicle control client device requests to control based on the path of the vehicle control instruction. At this time, the vehicle control proxy device can generate a control instruction corresponding to the function based on the determined information.

[0229] Optionally, in addition to indicating which function of the first vehicle is to be controlled, the vehicle control instruction may further indicate the control method of the function of the first vehicle. For example, taking the control of the air-conditioning temperature of the first vehicle as an example, the above-mentioned vehicle control instruction, in addition to indicating how to control the air-conditioning temperature of the first vehicle, also needs to indicate how to adjust the air-conditioning temperature (such as how many degrees to increase / lower / to how many degrees, etc.).

[0230] In one possible implementation, the above-mentioned vehicle control instruction can indicate the control method of the function of the first vehicle through a path. For instance, taking the air-conditioning temperature adjustment as an example, the service cluster of the target endpoint in the vehicle control agent device may include an operation object for increasing the degree / an operation object for decreasing the degree / an operation object for adjusting to the degree. At this time, the path of the above-mentioned vehicle control instruction can not only indicate the adjustment of the air-conditioning temperature of the first vehicle, but also indicate the specific adjustment method.

[0231] In another possible implementation, the above-mentioned vehicle control instruction may carry a control method for the function of the first vehicle. For example, taking the air conditioning temperature adjustment as an example, the service cluster of the target endpoint in the vehicle control agent device may include the target operation object of the air conditioning temperature. The path of the above-mentioned vehicle control instruction indicates that the function for controlling the first vehicle is the air conditioning temperature adjustment function, but does not indicate the adjustment method for the air conditioning temperature. At this time, the vehicle control instruction may also carry information on the method for adjusting the air conditioning temperature, for example, carrying information to increase / decrease the air conditioning temperature by N degrees, or carrying the target temperature for the air conditioning temperature adjustment.

[0232] In some embodiments, the vehicle control proxy device provides a proxy service for managing the first vehicle to the vehicle control client device. The process of the vehicle control client device managing the vehicle through the vehicle control proxy device may include:

[0233] The vehicle control client device sends a subscription request to the vehicle control proxy device, and the vehicle control proxy device receives the subscription request sent by the vehicle control client device, where the subscription request is used to request subscription to the status information of the first vehicle;

[0234] The vehicle control agent device sends the status information of the first vehicle to the vehicle control client device; the vehicle control client device receives the status information of the first vehicle sent by the vehicle control agent device;

[0235] The vehicle control client device sends a status report to the vehicle control proxy device, and the vehicle control proxy device receives the status report sent by the vehicle control client device, where the status report is used to indicate whether the vehicle control client device has successfully received the status information of the first vehicle;

[0236] When the status report indicates that the vehicle control client device successfully receives the status information of the first vehicle, the vehicle control proxy device sends a subscription response to the vehicle control client device, and the vehicle control client device receives the subscription response sent by the vehicle control proxy device. The subscription response is used to indicate that the subscription is completed.

[0237] In a possible implementation, the vehicle control client device may subscribe to the status information of the first vehicle from the vehicle control proxy device through a subscription request. In this process, the vehicle control proxy device may act as a subscription proxy to provide a proxy subscription service to the vehicle control client device.

[0238] In another possible implementation, the vehicle control client device may serve as a subscription source device to provide subscription services to the vehicle control client device.

[0239] In some embodiments, sending the status information of the first vehicle to the vehicle control client device includes:

[0240] In a case where the vehicle control client device has permission to subscribe to the status information of the first vehicle, the status information of the first vehicle is sent to the vehicle control client device.

[0241] In an embodiment of the present application, the vehicle control proxy device can record the authority of the vehicle control client device to manage the first vehicle. After receiving the subscription request, the vehicle control proxy device can query whether the vehicle control client device has the authority to subscribe to the status information of the first vehicle. If so, the status information of the first vehicle is sent to the vehicle control client device; optionally, if the vehicle control client device does not have the authority to subscribe to the status information of the first vehicle, a subscription failure response can be returned to the vehicle control client device, and the subscription failure response can carry the reason for the failure: lack of subscription authority.

[0242] The method for setting the permission for the vehicle control client device to subscribe to the status information of the first vehicle may include: the vehicle control proxy device uses an access control list (ACL) to set access control permissions for the status information of each vehicle accessible to the vehicle control client device.

[0243] In some embodiments, the above-mentioned vehicle control client device has the authority to subscribe to the status information of the first vehicle, which may be to indicate that the vehicle control client device has the authority corresponding to the information requested to be subscribed to for the first vehicle; for example, if the subscription request is used to request to subscribe to the locked / unlocked status of the vehicle, then the above-mentioned vehicle control client device has the authority corresponding to the information requested to be subscribed to for the first vehicle, which means that the vehicle control client device has the authority to subscribe to the locked / unlocked status of the first vehicle.

[0244] Alternatively, the above-mentioned vehicle control client device has the authority to subscribe to the first vehicle, which may mean that the vehicle control client device has a single authority to subscribe to any status information in the first vehicle, that is, the authority does not distinguish the type of information requested for subscription, or the authority applies to all status information of the vehicle.

[0245] For example, the above-mentioned permission to subscribe to the first vehicle can be a single permission or can include multiple permissions of different levels; when it includes multiple permissions of different levels, the process of querying whether the vehicle control client device has the permission to subscribe to the status information of the first vehicle can refer to querying whether the current permission of the vehicle control client device to subscribe to the status information of the first vehicle is equal to or higher than the permission required for the status information subscribed by the above-mentioned subscription request. If so, it is determined that the vehicle control client device has the permission to subscribe to the status information of the first vehicle; otherwise, it is determined that the vehicle control client device does not have the permission to subscribe to the status information of the first vehicle.

[0246] In other embodiments, the vehicle control proxy device may also send the status information of the first vehicle to the vehicle control client device without querying whether the vehicle control client device has the authority to subscribe to the status information of the first vehicle.

[0247] In some embodiments, the method further includes: in response to a change in the status information of the first vehicle, the vehicle control proxy device notifying the vehicle control client device of the changed status information of the first vehicle. Accordingly, when the status information of the first vehicle changes, the vehicle control client device receives the changed status information of the first vehicle from the vehicle control proxy device.

[0248] Example 1:

[0249] For example, the vehicle control agent device is a mobile phone, and the vehicle control client device is a smart home device (such as a smart TV):

[0250] (1) Implement the CarAgent Discovery Cluster on the mobile phone, which is used by the CarClient to discover the CarAgent.

[0251] The car agent discovery function set includes the following commands, which are defined in Table 8 below:

[0252] Table 8

[0253] Among them, C represents the client, S represents the server, N represents no response, and M represents mandatory implementation.

[0254] The parameters of discoverAgentReq are defined as shown in Table 9 below:

[0255] Table 9

[0256] The parameters of discoverAgentResp are defined as shown in Table 10 below:

[0257] Table 10

[0258] (2) The CarAgent Cluster is implemented on the mobile phone, and the bound CarClient is recorded.

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

[0260] Table 11

[0261] The carStatus structure is defined as shown in Table 12 below:

[0262] Table 12

[0263] Among them, Accessible is the accessible status of the car, True means it is currently accessible, and False means it is currently inaccessible.

[0264] The car agent function set includes the following commands, which are defined in Table 13 below:

[0265] Table 13

[0266] getCarInfoReq is used by CarClient to obtain information about currently accessible cars from CarAgent. The information about accessible cars is returned via getCarInfoResp.

[0267] The getCarInfoResp parameter definition is shown in Table 14 below:

[0268] Table 14

[0269] The carInfo structure is defined as shown in Table 15 below:

[0270] Table 15

[0271] The EpStruct structure can be referred to as shown in Table 6 and will not be described in detail here.

[0272] Please refer to Figure 8, which shows a flow chart of a vehicle management involved in this application. In this embodiment, the user can use the CarClient implemented on the smart TV in the home network to control the car through the CarAgent implemented on the mobile phone. The above process is:

[0273] S1: A CarClient in a smart home network discovers a CarAgent in the network through MultiCast. At this point, the CarClient and CarAgent are in the same MultiCast group. The CarClient sends a discoverAgentReq message.

[0274] S2, CarAgent responds with a discovery request via discoverAgentResp.

[0275] S3, both parties establish a data channel.

[0276] S4: CarClient sends the getCarInfoReq command to CarAgent to obtain the controllable vehicles and their corresponding Endpoints, as well as the vehicle control functions corresponding to the Endpoints.

[0277] S5, CarAgent returns the controllable car and all corresponding vehicle control functions through getCarInfoResp.

[0278] S6: CarClient displays the vehicle control interface to the user.

[0279] S7: When the car is accessible, CarClient sends a car control command to CarAgent. The path is the endpoint corresponding to the car control on CarAgent:

[0280] Source:CarClient;

[0281] Destination:CarAgent path:targetEndpointNumber / ServerCluster / [targetOperationObject].

[0282] S8, CarAgent receives the vehicle control command, and after passing the verification authority, it converts the processing on the corresponding Endpoint into the corresponding third-party command (i.e., control command) and sends it to the vehicle.

[0283] S9: CarClient sends a subscription request to CarAgent to subscribe to the car's status.

[0284] S10, CarAgent obtains the corresponding status information of the car and reports the subscribed current status to CarClient.

[0285] S11, after receiving the reported status data, CarClient returns a Status Report, indicating whether the reception is successful or failed.

[0286] S12: If successful, CarAgent returns a subscription response to CarClient to complete the subscription.

[0287] After that, CarAgent regularly obtains the car's status information. When the subscribed status changes, CarAgent can notify CarClient through data reporting.

[0288] Example 2:

[0289] Let's take the example where the vehicle control agent device is a mobile phone and the vehicle control client device is a smart home device (such as a smart TV):

[0290] (1) Implement the CarAgent Discovery Cluster on the mobile phone to enable CarClient to discover CarAgent.

[0291] The vehicle agent discovery function set includes commands, which are defined in Table 8. The discoverAgentReq parameter definition is shown in Table 9.

[0292] The definition of discoverAgentResp parameters is shown in Table 10.

[0293] (2) The CarAgent Cluster is implemented on the mobile phone, and the bound CarClient is recorded.

[0294] The attributes included in the car agent function set are defined as shown in Table 11.

[0295] The carStatus structure definition is shown in Table 12.

[0296] The car agent function set includes commands, as defined in Table 13.

[0297] The getCarInfoResp parameter definition is shown in Table 14.

[0298] The carInfo structure is defined as shown in Table 16 below:

[0299] Table 16

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

[0301] The car client function set includes the following commands, which are defined in Table 17 below:

[0302] Table 17

[0303] The getCurrentAgentReq method is used to retrieve the CarAgent currently associated with a car in the boundCars list. When the CarAgents field of an entry in the boundCars list contains more than one CarAgent, only one CarAgent can be associated with the CarID of a CarClient at a time. The CarClient's vehicle control commands are forwarded to the corresponding car via the associated CarAgent. Its parameters are defined in Table 18 below:

[0304] Table 18

[0305] The parameters of getCurrentAgentResp are defined as shown in Table 19 below:

[0306] Table 19

[0307] setCurrentAgentReq is used to set the requester to the CarAgent currently associated with the CarClient's car. The car is identified by the CarID parameter carried in the request.

[0308] The parameter definitions are shown in Table 20 below:

[0309] Table 20

[0310] After receiving setCurrentAgentReq, CarClient should verify whether the sender has a binding relationship with the CarID. If no binding relationship exists, an error code will be returned.

[0311] The car client function set includes the following events, which are defined in Table 21:

[0312] Table 21

[0313] A Priority of INFO indicates that the event priority is a general notification for the client. The V in the Access field indicates that the notification data is observable and subscribing.

[0314] The currentCarAgentChanged event contains the following notification data shown in Table 22:

[0315] Table 22

[0316] Please refer to Figure 9, which shows a flow chart of a vehicle management involved in this application. In this embodiment, the user can use the CarClient implemented on the smart TV in the home network to control the car through the CarAgent implemented on the mobile phone. The above process is:

[0317] S1: A CarClient in a smart home network uses MultiCast to discover a CarAgent in the network. At this point, the CarClient and CarAgent are in the same MultiCast group. The CarClient sends a discoverAgentReq request.

[0318] S2, CarAgent responds with a discovery request via discoverAgentResp.

[0319] S3, both parties establish a data channel.

[0320] S4: CarAgent sends a getCurrentAgent Request to CarClient to obtain the currently associated Agent.

[0321] S5, CarClient returns the currently associated Agent through getCurrentAgent Response.

[0322] S6: If the CarClient is not currently associated with itself, the CarAgent sends a setCurrentAgent Request to the CarClient to set itself as the currently associated Agent. If the currently associated Agent changes, the CarClient sends a change notification to the device that subscribes to the currentCarAgentChanged event.

[0323] S7: CarClient sends the getCarInfoReq command to CarAgent to obtain the controllable cars and their corresponding Endpoints.

[0324] In step S8, CarAgent returns the controllable cars and their corresponding Endpoints through getCarInfoResp. Endpoints are represented by Endpoint Numbers. Afterwards, CarClient can query the description information of each Endpoint based on the Endpoint Number to obtain the car control functions included in the Endpoint.

[0325] S9, CarClient displays the vehicle control interface to the user.

[0326] S10: When the car is accessible, CarClient sends a car control command to CarAgent. The path is the endpoint corresponding to the car control on CarAgent:

[0327] Source:CarClient;

[0328] Destination:CarAgent path:targetEndpointNumber / ServerCluster / [targetOperationObject].

[0329] S11, CarAgent receives the vehicle control command, and after passing the verification authority, it converts the processing on the corresponding Endpoint into the corresponding third-party command and sends it to the car.

[0330] S12: CarClient sends a subscription request to CarAgent to subscribe to the car's status.

[0331] S13, CarAgent obtains the corresponding status information of the car and reports the subscribed current status to CarClient.

[0332] S14, after receiving the reported status data, CarClient returns a Status Report, indicating whether the reception is successful or failed.

[0333] S15: If successful, CarAgent returns a subscription response to CarClient to complete the subscription.

[0334] After that, CarAgent regularly obtains the car's status information. When the subscribed status changes, CarAgent can notify CarClient through data reporting.

[0335] Please refer to Figure 10, which shows a block diagram of a vehicle management device provided by an embodiment of the present application. The vehicle management device 1000 has the functions of implementing the method shown in Figure 4 or Figure 7 above, which is performed by the vehicle control agent device. As shown in Figure 10, the device may include:

[0336] The proxy service module 1001 is configured to provide a proxy service for managing the first vehicle to the vehicle control client device.

[0337] In some embodiments, the management includes at least one of the following: controlling the first vehicle; viewing the status information of the first vehicle; and subscribing to the status information of the first vehicle.

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

[0339] The vehicle proxy function cluster indicates at least one of the following information: information of a vehicle control client device bound to the vehicle control proxy device; information of a vehicle bound to the vehicle control proxy device.

[0340] In some embodiments, the information of the vehicle bound to the vehicle control proxy device includes at least one of the following information: identification information of the vehicle bound to the vehicle control proxy device; information on the accessible status of the vehicle bound to the vehicle control proxy device; and information on the endpoint of the vehicle bound to the vehicle control proxy device.

[0341] In some embodiments, the car agent functional cluster supports at least one of the following commands:

[0342] A vehicle information acquisition request is used to acquire vehicle information of a vehicle bound to the vehicle control agent device from the vehicle control agent device;

[0343] The vehicle information acquisition response is used to return the vehicle information of the vehicle bound to the vehicle control agent device to the sender of the vehicle information acquisition request.

[0344] In some embodiments, the vehicle information acquisition response includes a vehicle information list; the vehicle information list includes at least one item of the vehicle information.

[0345] In some embodiments, the vehicle information includes at least one of the following information: identification information of the vehicle bound to the vehicle control proxy device; and information of an endpoint of the vehicle bound to the vehicle control proxy device.

[0346] In some embodiments, the information of the endpoint of the vehicle bound to the vehicle control proxy device includes: an endpoint structure of the endpoint of the vehicle bound to the vehicle control proxy device; or an endpoint number of the endpoint of the vehicle bound to the vehicle control proxy device.

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

[0348] A receiving module, configured to receive the vehicle information acquisition request sent by the vehicle control client device;

[0349] The sending module is used to return the vehicle information acquisition response to the vehicle control client device.

[0350] In some embodiments, the proxy service module 1001 is used to:

[0351] receiving a vehicle control instruction sent by the vehicle control client device, wherein the vehicle control instruction is used to control the first vehicle;

[0352] Based on the vehicle control instruction, a control instruction is sent to the first vehicle, and the control instruction is executed by the first vehicle to achieve a control function for the first vehicle.

[0353] In some embodiments, the proxy service module 1001 is configured to send a control instruction to the first vehicle based on the vehicle control instruction when the vehicle control client device has authority to control the first vehicle.

[0354] In some embodiments, the path of the vehicle control instruction includes: a target operation object in a service cluster of a target endpoint in the vehicle control proxy device;

[0355] The proxy service module 1001 is configured to convert the vehicle control instruction into the control instruction based on the path of the vehicle control instruction.

[0356] In some embodiments, the proxy service module 1001 is used to:

[0357] receiving a subscription request sent by the vehicle control client device, wherein the subscription request is used to request subscription to the status information of the first vehicle;

[0358] Sending the status information of the first vehicle to the vehicle control client device;

[0359] receiving a status report sent by the vehicle control client device, wherein the status report is used to indicate whether the vehicle control client device has successfully received the status information of the first vehicle;

[0360] In a case where the status report indicates that the vehicle control client device has successfully received the status information of the first vehicle, a subscription response is sent to the vehicle control client device, where the subscription response is used to indicate that the subscription is completed.

[0361] In some embodiments, the proxy service module 1001 is configured to send the status information of the first vehicle to the vehicle control client device if the vehicle control client device has permission to subscribe to the status information of the first vehicle.

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

[0363] The sending module is configured to notify the vehicle control client device of the changed status information of the first vehicle in response to a change in the status information of the first vehicle.

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

[0365] The vehicle agent discovery function cluster is used by the vehicle control client device to discover the vehicle control agent device.

[0366] In some embodiments, the car agent discovery function cluster supports at least one of the following commands:

[0367] Discovery proxy request, used by the vehicle control client device to request information of the vehicle control proxy device from the vehicle control proxy device;

[0368] The discovery agent response is used to return the information of the vehicle control agent device to the vehicle control client device.

[0369] In some embodiments, the discovery agent request includes identification information of the second vehicle.

[0370] In some embodiments, the discovery agent response includes at least one of the following information: identification information of the vehicle control agent device; and identification information of a vehicle bound to the vehicle control agent device.

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

[0372] A receiving module, configured to receive the discovery proxy request sent by the vehicle control client device;

[0373] The sending module is configured to return the discovery proxy response to the vehicle control client device when the vehicles bound to the vehicle control proxy device include the second vehicle.

[0374] In some embodiments, the receiving module is configured to receive the discovery proxy request sent by the vehicle control client device in the multicast group when the vehicle control client device and the vehicle control proxy device are in the same multicast group.

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

[0376] A sending module, configured to send a request to obtain a current proxy to the vehicle control client device; the request is used to obtain information of a proxy currently associated with a third vehicle in the vehicle control client device;

[0377] The receiving module is configured to receive a current proxy acquisition response returned by the vehicle control client device; the current proxy acquisition response is used to indicate information of a proxy currently associated with a third vehicle in the vehicle control client device.

[0378] In some embodiments, the obtaining current proxy request includes identification information of the third vehicle;

[0379] The obtaining current proxy response includes information about the proxy currently associated with the third vehicle in the vehicle control client device.

[0380] In some embodiments, the obtaining of the current proxy response includes: identification information of the proxy currently associated with the third vehicle in the vehicle control client device.

[0381] In some embodiments, the obtaining of the current proxy response further includes: identification information of the third vehicle.

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

[0383] The sending module is used to send a set current proxy request to the vehicle control client device; the set current proxy request is used to set the proxy currently associated with the fourth vehicle in the vehicle control client device as the vehicle control proxy device.

[0384] Please refer to Figure 11, which shows a block diagram of a vehicle management device provided by an embodiment of the present application. The vehicle management device 1100 has the functions of implementing the method shown in Figure 5 or Figure 7 above, which is performed by the vehicle control client device. As shown in Figure 11, the device may include:

[0385] The management module 1101 is configured to manage the first vehicle through a vehicle control agent device.

[0386] In some embodiments, the management includes at least one of the following: controlling the first vehicle; viewing the status information of the first vehicle; and subscribing to the status information of the first vehicle.

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

[0388] A sending module, configured to send a request for obtaining vehicle information to the vehicle control agent device;

[0389] The receiving module is used to receive the vehicle information acquisition response returned by the vehicle control agent device; the vehicle information acquisition response is used to indicate the vehicle information of the vehicle bound to the vehicle control agent device.

[0390] In some embodiments, the vehicle information acquisition response includes a vehicle information list; the vehicle information list includes at least one item of the vehicle information.

[0391] In some embodiments, the vehicle information includes at least one of the following information: identification information of the vehicle bound to the vehicle control proxy device; and information of an endpoint of the vehicle bound to the vehicle control proxy device.

[0392] In some embodiments, the information of the endpoint of the vehicle bound to the vehicle control proxy device includes: an endpoint structure of the endpoint of the vehicle bound to the vehicle control proxy device; or an endpoint number of the endpoint of the vehicle bound to the vehicle control proxy device.

[0393] In some embodiments, the management module 1101 is used to send vehicle control instructions to the vehicle control agent device, and the vehicle control instructions are used to control the first vehicle, so that the vehicle control agent device sends control instructions to the first vehicle based on the vehicle control instructions, and the control instructions are executed by the first vehicle to realize the remote control function of the first vehicle.

[0394] In some embodiments, the path of the vehicle control instruction includes: a target operation object in a service cluster of a target endpoint in the vehicle control proxy device.

[0395] In some embodiments, the management module 1101 is used to send a subscription request to the vehicle control proxy device, where the subscription request is used to request subscription to the status information of the first vehicle; receive the status information of the first vehicle sent by the vehicle control proxy device; send a status report to the vehicle control proxy device, where the status report is used to indicate whether the vehicle control client device has successfully received the status information of the first vehicle; and receive a subscription response sent by the vehicle control proxy device when the status report indicates that the vehicle control client device has successfully received the status information of the first vehicle, where the subscription response is used to indicate that the subscription is complete.

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

[0397] The receiving module is configured to receive the changed status information of the first vehicle sent by the vehicle control agent device when the status information of the first vehicle changes.

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

[0399] A sending module, configured to send a discovery agent request; the discovery agent request is used to request information of the vehicle control agent device;

[0400] The receiving module is used to receive a discovery agent response sent by the vehicle control agent device; the discovery agent response is used to indicate information of the vehicle control agent device.

[0401] In some embodiments, the sending module is used to send the discovery agent request within a multicast group.

[0402] In some embodiments, the discovery proxy request includes identification information of the second vehicle; and the discovery proxy response is sent by the vehicle control proxy device when the second vehicle is included in the vehicles bound to the vehicle control proxy device.

[0403] In some embodiments, the discovery agent response includes at least one of the following information: identification information of the vehicle control agent device; and identification information of a vehicle bound to the vehicle control agent device.

[0404] In some embodiments, the vehicle control client device includes a vehicle client function cluster; the vehicle client function cluster is used to record vehicles and agents bound to the vehicle control client device.

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

[0406] Get current proxy request, used to obtain information of the proxy currently associated with the third vehicle in the vehicle control client device;

[0407] Obtaining a current proxy response, which is used to indicate information of a proxy currently associated with the third vehicle in the vehicle control client device;

[0408] The current proxy setting request is used to set the proxy currently associated with the fourth vehicle in the vehicle control client device.

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

[0410] A receiving module, configured to receive the current proxy acquisition request sent by the vehicle control proxy device;

[0411] The sending module is used to return the current proxy response to the vehicle control proxy device.

[0412] In some embodiments, the obtaining current proxy request includes identification information of the third vehicle;

[0413] The obtaining current proxy response includes information about the proxy currently associated with the third vehicle in the vehicle control client device.

[0414] In some embodiments, the obtaining of the current proxy response includes: identification information of the proxy currently associated with the third vehicle in the vehicle control client device.

[0415] In some embodiments, the obtaining of the current proxy response further includes: identification information of the third vehicle.

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

[0417] A receiving module, configured to receive the setting current proxy request sent by the vehicle control proxy device;

[0418] The setting module is configured to set the proxy currently associated with the fourth vehicle in the vehicle control client device as the vehicle control proxy device according to the setting current proxy request.

[0419] In some embodiments, the car client functional cluster supports current car agent change events;

[0420] The current vehicle proxy change event is used to indicate that the proxy currently associated with the fourth vehicle in the vehicle control client device has changed.

[0421] In some embodiments, the current vehicle agent change event includes at least one of the following information:

[0422] Identification information of the fourth vehicle; identification information of the agent last associated with the fourth vehicle in the vehicle control client device; identification information of the agent currently associated with the fourth vehicle in the vehicle control client device.

[0423] Please refer to FIG12 , which shows a schematic diagram of the structure of a computer device 1200 provided in one embodiment of the present application. The computer device 1200 may include: a processor 1201 , a receiver 1202 , a transmitter 1203 , a memory 1204 , and a bus 1205 .

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

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

[0426] In an exemplary embodiment, when computer device 1200 is implemented as the aforementioned vehicle control proxy device, processor 1201 and / or transceiver are configured to provide a proxy service for managing the first vehicle to the vehicle control client device. The processes executed by processor 1201 and / or transceiver in computer device 1200 may refer to the steps executed by the vehicle control proxy device in the method shown in either FIG. 4 or FIG. 7 .

[0427] In an exemplary embodiment, when computer device 1200 is implemented as a vehicle control client device, processor 1201 and / or transceiver are configured to manage the first vehicle via the vehicle control proxy device. The processes executed by processor 1201 and / or transceiver in computer device 1200 may refer to the steps executed by the vehicle control client device in the method shown in either FIG. 5 or FIG. 7 .

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

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

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

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

Claims

1. A vehicle management method, characterized in that: The method is executed by a vehicle control agent device, and the method includes: An agent service for managing the first vehicle is provided to the vehicle control client device.

2. The method according to claim 1, characterized in that The management includes at least one of the following: controlling the first vehicle; Checking the status information of the first vehicle; Subscribe to the status information of the first vehicle.

3. The method according to claim 1 or 2, characterized in that: The vehicle control agent device includes a vehicle agent function cluster; The vehicle agent function cluster indicates at least one of the following information: Information of the vehicle control client device bound to the vehicle control proxy device; Information about the vehicle bound to the vehicle control agent device.

4. The method according to claim 3, characterized in that The information of the vehicle bound to the vehicle control agent device includes at least one of the following information: Identification information of the vehicle bound to the vehicle control proxy device; Information on the accessible status of the vehicle bound to the vehicle control agent device; The endpoint information of the vehicle bound to the vehicle control agent device.

5. The method according to claim 3 or 4, characterized in that: The car agent function cluster supports at least one of the following commands: A vehicle information acquisition request is used to acquire vehicle information of a vehicle bound to the vehicle control agent device from the vehicle control agent device; The vehicle information acquisition response is used to return the vehicle information of the vehicle bound to the vehicle control proxy device to the sender of the vehicle information acquisition request.

6. The method according to claim 5, characterized in that The vehicle information acquisition response includes a vehicle information list; the vehicle information list includes at least one item of the vehicle information.

7. The method according to claim 5 or 6, characterized in that: The vehicle information includes at least one of the following information: Identification information of the vehicle bound to the vehicle control proxy device; The endpoint information of the vehicle bound to the vehicle control agent device.

8. The method according to claim 7, characterized in that The information of the endpoint of the vehicle bound to the vehicle control proxy device includes: The endpoint structure of the endpoint of the vehicle bound to the vehicle control proxy device; or, The endpoint number of the vehicle endpoint bound to the vehicle control proxy device.

9. The method according to any one of claims 5 to 8, characterized in that: The method further comprises: Receiving the vehicle information acquisition request sent by the vehicle control client device; The vehicle information acquisition response is returned to the vehicle control client device.

10. The method according to any one of claims 1 to 9, characterized in that: The providing the vehicle control client device with an agent service for managing the first vehicle includes: receiving a vehicle control instruction sent by the vehicle control client device, wherein the vehicle control instruction is used to control the first vehicle; Based on the vehicle control instruction, a control instruction is sent to the first vehicle, and the control instruction is executed by the first vehicle to implement a control function for the first vehicle.

11. The method according to claim 10, characterized in that The sending a control instruction to the first vehicle based on the vehicle control instruction includes: In a case where the vehicle control client device has the authority to control the first vehicle, a control instruction is sent to the first vehicle based on the vehicle control instruction.

12. The method according to claim 11, characterized in that The path of the vehicle control instruction includes: a target operation object in a service cluster of a target endpoint in the vehicle control proxy device; The sending a control instruction to the first vehicle based on the vehicle control instruction includes: Based on the path of the vehicle control instruction, the vehicle control instruction is converted into the control instruction.

13. The method according to any one of claims 1 to 9, characterized in that: The providing the vehicle control client device with an agent service for managing the first vehicle includes: Receiving a subscription request sent by the vehicle control client device, wherein the subscription request is used to request to subscribe to the status information of the first vehicle; Sending the status information of the first vehicle to the vehicle control client device; Receive a status report sent by the vehicle control client device, the status report is used to indicate whether the vehicle control client device has successfully received to the status information of the first vehicle; In a case where the status report indicates that the vehicle control client device has successfully received the status information of the first vehicle, a subscription response is sent to the vehicle control client device, where the subscription response is used to indicate that the subscription is completed.

14. The method according to claim 13, characterized in that The sending the state information of the first vehicle to the vehicle control client device includes: In a case where the vehicle control client device has the authority to subscribe to the status information of the first vehicle, the status information of the first vehicle is sent to the vehicle control client device.

15. The method according to claim 13 or 14, characterized in that The method further comprises: In response to a change in the state information of the first vehicle, the changed state information in the first vehicle is notified to the vehicle control client device.

16. The method according to any one of claims 1 to 15, characterized in that: The vehicle control agent device includes a vehicle agent discovery function cluster; The vehicle agent discovery function cluster is used by the vehicle control client device to discover the vehicle control agent device.

17. The method according to claim 16, characterized in that The vehicle agent discovery function cluster supports at least one of the following commands: Discovery agent request, used by the vehicle control client device to request information of the vehicle control agent device from the vehicle control agent device; The discovery agent response is used to return the information of the vehicle control agent device to the vehicle control client device.

18. The method according to claim 17, characterized in that The discovery agent request includes identification information of the second vehicle.

19. The method according to claim 17 or 18, characterized in that The discovery agent response includes at least one of the following information: Identification information of the vehicle control agent device; The identification information of the vehicle bound to the vehicle control proxy device.

20. The method according to claim 18, characterized in that The method further comprises: Receiving the discovery proxy request sent by the vehicle control client device; In a case where the second vehicle is included in the vehicles bound to the vehicle control proxy device, the discovery proxy response is returned to the vehicle control client device.

21. The method according to claim 20, characterized in that The receiving the discovery proxy request sent by the vehicle control client device includes: When the vehicle control client device and the vehicle control proxy device are in the same multicast group, the discovery proxy request sent by the vehicle control client device in the multicast group is received.

22. The method according to any one of claims 1 to 21, characterized in that: The method further comprises: Sending a request to obtain a current proxy to the vehicle control client device; the request to obtain a current proxy is used to obtain information of a proxy currently associated with a third vehicle in the vehicle control client device; A current proxy acquisition response returned by the vehicle control client device is received; the current proxy acquisition response is used to indicate information of a proxy currently associated with a third vehicle in the vehicle control client device.

23. The method according to claim 22, characterized in that The obtaining of the identification information of the third vehicle included in the current proxy request; The obtaining current proxy response includes information about the proxy currently associated with the third vehicle in the vehicle control client device.

24. The method according to claim 22 or 23, characterized in that The acquisition of the current proxy response includes: The identification information of the agent currently associated with the third vehicle in the vehicle control client device.

25. The method according to claim 24, characterized in that The obtaining of the current proxy response also includes: Identification information of the third vehicle.

26. The method according to any one of claims 1 to 25, characterized in that: The method further comprises: A request for setting a current proxy is sent to the vehicle control client device; the request for setting a current proxy is used to set a proxy currently associated with a fourth vehicle in the vehicle control client device as the vehicle control proxy device.

27. A vehicle management method, characterized in that: The method is executed by a vehicle control client device, and the method includes: The first vehicle is managed through the vehicle control agent device.

28. The method according to claim 27, characterized in that The management includes at least one of the following: controlling the first vehicle; Checking the status information of the first vehicle; Subscribe to the status information of the first vehicle.

29. The method according to claim 27 or 28, characterized in that The method further comprises: Sending a request for obtaining vehicle information to the vehicle control agent device; Receive the vehicle information acquisition response returned by the vehicle control proxy device; the vehicle information acquisition response is used to indicate the vehicle information binding with the vehicle control proxy device. The vehicle information of the specified vehicle.

30. The method according to claim 29, characterized in that The vehicle information acquisition response includes a vehicle information list; the vehicle information list includes at least one item of the vehicle information.

31. The method according to claim 29 or 30, characterized in that The vehicle information includes at least one of the following information: Identification information of the vehicle bound to the vehicle control proxy device; The endpoint information of the vehicle bound to the vehicle control agent device.

32. The method according to claim 31, characterized in that The information of the endpoint of the vehicle bound to the vehicle control proxy device includes: The endpoint structure of the endpoint of the vehicle bound to the vehicle control proxy device; or, The endpoint number of the vehicle endpoint bound to the vehicle control proxy device.

33. The method according to any one of claims 27 to 32, characterized in that: The vehicle management by the vehicle control agent device includes: A vehicle control instruction is sent to the vehicle control proxy device, where the vehicle control instruction is used to control the first vehicle, so that the vehicle control proxy device sends a control instruction to the first vehicle based on the vehicle control instruction, and the control instruction is executed by the first vehicle to realize a remote control function of the first vehicle.

34. The method according to claim 33, characterized in that The path of the vehicle control instruction includes: a target operation object in a service cluster of a target endpoint in the vehicle control proxy device.

35. The method according to any one of claims 27 to 32, characterized in that: The vehicle management by the vehicle control agent device includes: Sending a subscription request to the vehicle control proxy device, wherein the subscription request is used to request to subscribe to the status information of the first vehicle; Receiving the status information of the first vehicle sent by the vehicle control agent device; Sending a status report to the vehicle control proxy device, wherein the status report is used to indicate whether the vehicle control client device has successfully received the status information of the first vehicle; When the status report indicates that the vehicle control client device has successfully received the status information of the first vehicle, a subscription response sent by the vehicle control proxy device is received, where the subscription response is used to indicate that the subscription is completed.

36. The method according to claim 35, characterized in that The method further comprises: When the state information of the first vehicle changes, the changed state information of the first vehicle is received and sent by the vehicle control agent device.

37. The method according to any one of claims 27 to 36, characterized in that: The method further comprises: Sending a discovery agent request; the discovery agent request is used to request information of the vehicle control agent device; A discovery proxy response sent by the vehicle control proxy device is received; the discovery proxy response is used to indicate information of the vehicle control proxy device.

38. The method according to claim 37, characterized in that The sending of the discovery agent request comprises: The discovery agent request is sent within a multicast group.

39. The method according to claim 37 or 38, characterized in that The discovery agent request includes identification information of the second vehicle; The discovery proxy response is sent by the vehicle control proxy device when the vehicles bound to the vehicle control proxy device include the second vehicle.

40. The method according to any one of claims 37 to 39, characterized in that: The discovery agent response includes at least one of the following information: Identification information of the vehicle control agent device; The identification information of the vehicle bound to the vehicle control proxy device.

41. The method according to any one of claims 27 to 40, characterized in that The vehicle control client device includes a vehicle client function cluster; the vehicle client function cluster is used to record the vehicles and agents bound to the vehicle control client device.

42. The method according to claim 41, characterized in that The car client function cluster supports at least one of the following commands: Obtaining a current proxy request, used to obtain information of a proxy currently associated with a third vehicle in the vehicle control client device; Obtaining a current proxy response, which is used to indicate information of a proxy currently associated with a third vehicle in the vehicle control client device; The current proxy request is set, and is used to set the proxy currently associated with the fourth vehicle in the vehicle control client device.

43. The method according to claim 42, characterized in that The method further comprises: Receiving the current proxy acquisition request sent by the vehicle control proxy device; The current proxy response is returned to the vehicle control proxy device.

44. The method according to claim 42 or 43, characterized in that The obtaining of the identification information of the third vehicle included in the current proxy request; The obtaining current proxy response includes information about the proxy currently associated with the third vehicle in the vehicle control client device.

45. The method according to any one of claims 42 to 44, characterized in that The acquisition of the current proxy response includes: The identification information of the agent currently associated with the third vehicle in the vehicle control client device.

46. ​​The method according to claim 45, characterized in that The obtaining of the current proxy response also includes: Identification information of the third vehicle.

47. The method according to claim 42, characterized in that The method further comprises: Receiving the setting current proxy request sent by the vehicle control proxy device; According to the setting current proxy request, the proxy currently associated with the fourth vehicle in the vehicle control client device is set as the vehicle control proxy device.

48. The method according to any one of claims 42 to 47, characterized in that The car client function cluster supports current car proxy change events; The current vehicle proxy change event is used to indicate that the proxy currently associated with the fourth vehicle in the vehicle control client device has changed.

49. The method according to claim 48, characterized in that The current vehicle agent change event includes at least one of the following information: identification information of the fourth vehicle; In the vehicle control client device, identification information of the last agent associated with the fourth vehicle; The identification information of the agent currently associated with the fourth vehicle in the vehicle control client device.

50. A vehicle management device, characterized in that: The device comprises: The proxy service module is used to provide a proxy service for managing the first vehicle to the vehicle control client device.

51. A vehicle management device, characterized in that: The device comprises: The management module is used to manage the first vehicle through the vehicle control agent device.

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

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

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

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

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

Images