Method and system for controlling a vehicle

Abstract

A method and system for controlling a vehicle, which shortens a waiting time for a user to receive a result of a command when a car-to-home service is implemented through a server. The method includes: inquiring about a current state of an Internet of Things (IoT) device linked to implement remote control of a vehicle through a first server and storing the inquired current state of the IoT device; upon generation of a request from the vehicle, acquiring information about the current state of the IoT stored in the first server and displaying the information through a display; re-inquiring about the current state to update the information about the current state of the IoT stored in the first server; and if the displayed information about the current state of the IoT does not match the information about the updated current state in the first server, displaying the updated information about the current state of the IoT through the display.

Description

Technical Field

[0001] This disclosure relates to vehicles and methods and systems for controlling vehicles to enable vehicle-to-home services, which are implemented at remote sites via Internet of Things (IoT) devices to be controlled from the vehicle. Background Technology

[0002] They are researching a "car-to-home service" based on the Internet of Things (IoT), which would allow users to operate internet-connected lighting or heating devices through the vehicle's main unit.

[0003] In car-to-home services, IoT devices communicate with the vehicle's main unit via multiple servers. In other words, through these servers, IoT devices connect to an IoT application and send data or receive commands (control requests) to control actuators in the home, such as lighting or heating devices. The IoT application is installed on the vehicle's main unit and operated by the user (driver).

[0004] As mentioned above, because communication between the vehicle's main unit and remote IoT devices is performed through multiple servers, the transmission of information takes a long time. This results in increased waiting time for the user (driver) before they can check the results of commands (requests) generated from the vehicle's main unit. Consequently, the user may experience discomfort. Summary of the Invention

[0005] When implementing a car-to-home service that communicates through multiple servers, this disclosure provides a way to reduce the waiting time for users to receive the results of commands (requests).

[0006] Additional aspects of this disclosure are set forth in part in the description which follows, and in part should be obvious from the description or may be learned by practice of this disclosure.

[0007] According to one aspect of this disclosure, a method for controlling a vehicle is provided. The method includes querying the current state of an Internet of Things (IoT) device linked to enable remote vehicle control via a first server, and storing the queried current state of the IoT device. The method further includes, upon generating a request from the vehicle to query the current state of the IoT device, obtaining information about the current state of the IoT stored in the first server, and displaying the obtained information about the current state of the IoT via a display. The method also includes re-querying the current state of the IoT to update the information about the current state of the IoT stored in the first server. The method further includes, when the information about the current state of the IoT displayed on the display does not match the updated information about the current state of the IoT device in the first server, displaying the updated information about the current state of the IoT device in the first server on the display.

[0008] The first server could be operated by the vehicle manufacturer to enable IoT devices at remote sites to be controlled by the vehicle.

[0009] The first server can communicate with IoT devices through the second and third servers.

[0010] The second server can be a server operated by an IoT service company to provide IoT services through IoT devices; and the third server can be a server operated by an IoT device manufacturer to provide IoT-related content.

[0011] A request to query the current status of an IoT device can be sent from the first and second servers to the third server to perform the query. The query result of the IoT device's current status can be sent from the third and second servers to the first server, and the query result can be stored on the first server.

[0012] According to another aspect of this disclosure, a method for controlling a vehicle is provided. The method includes sending a command via a first server to a second server in response to generating a command from the vehicle for remotely controlling an Internet of Things (IoT) device located at a remote site. The method further includes, in response to successful transmission of the command from the first server to the second server, assuming the command has been executed based on successful transmission, and displaying the execution of the command on a display in the vehicle before checking the result of the command actually being executed in the IoT device. The method also includes sending a command from the second server to the IoT device and receiving the result of command execution in the IoT device. Finally, the method further includes, in response to the command not being executed in the IoT device, correctly indicating that the command was not executed and displaying a corrective result on the vehicle's display.

[0013] The first server could be operated by the vehicle manufacturer to enable IoT devices at remote sites to control the server from the vehicle.

[0014] The first server can communicate with IoT devices through the second and third servers.

[0015] The second server is operated by an IoT service company to provide IoT services through IoT devices; and the third server is operated by an IoT device manufacturer to provide IoT-related content.

[0016] Commands are sent from the first and second servers to the third server to execute corresponding controls. The results of executing the commands in the IoT device are then sent to the vehicle via the third, second, and first servers.

[0017] According to another aspect of this disclosure, a system for controlling a vehicle is provided. The system includes a host configured to remotely control an Internet of Things (IoT) device located at a remote site from the vehicle. The system also includes a display configured to display a user interface and information related to the remote control of the IoT device. The host is configured to query the current state of the IoT device linked to enable remote vehicle control via a first server and store the queried current state of the IoT device. The host is configured to, upon generating a request from the vehicle to query the current state of the IoT device, retrieve information about the current state of the IoT stored in the first server and display the retrieved information about the current state of the IoT via the display. The host is configured to re-query the current state of the IoT via the first server to update the information about the current state of the IoT stored in the first server, and compare the current state information about the IoT displayed on the display with the updated current state information about the IoT device in the first server to determine that the information about the current state of the IoT displayed on the display matches the updated current state information about the IoT device in the first server. The host is configured to display the updated information about the current state of the IoT device from the first server when the information about the current state of the IoT device displayed on the monitor does not match the updated information about the current state of the IoT device in the first server.

[0018] The first server could be operated by the vehicle manufacturer to enable IoT devices at remote sites to control the server from the vehicle.

[0019] The first server can communicate with IoT devices through the second and third servers.

[0020] The second server can be a server operated by an IoT service company to provide IoT services through IoT devices; and the third server can be a server operated by an IoT device manufacturer to provide IoT-related content.

[0021] The first and second servers send a request to the third server to query the current state of the IoT device, thereby executing the query. The query results of the current state of the IoT device are then sent to the first server via the third and second servers, and the query results are stored in the first server.

[0022] According to another aspect of this disclosure, a system for controlling a vehicle is provided. The system includes a host computer configured to remotely control an Internet of Things (IoT) device at a remote site from the vehicle. The system also includes a display configured to display a user interface and information related to the remote control of the IoT device. The host computer is configured to send a command to a second server via a first server in response to a command received from the vehicle for remotely controlling the IoT device located at the remote site. The host computer is further configured to, in response to successful transmission of a command from the first server to the second server, pre-display on the display that the command has been executed based on successful transmission of the command, prior to the actual execution of the command in the IoT device. The host computer is further configured to, in response to sending a command from the second server to the IoT device and receiving the result of executing the command in the IoT device, identify whether the command has been executed in the IoT device. The host computer is further configured to, in response to the command not being executed in the IoT device, correctly indicate that the command was not executed and display a corrective result on the vehicle's display.

[0023] The first server could be a server operated by the vehicle manufacturer to enable IoT devices at remote sites to be controlled from the vehicle.

[0024] The first server can communicate with IoT devices through the second and third servers.

[0025] The second server can be a server operated by an IoT service company to provide IoT services through IoT devices; and the third server can be a server operated by an IoT device manufacturer to provide IoT-related content.

[0026] Commands can be sent to the IoT device via a first server, a second server, and a third server, thereby executing the control corresponding to the command. The results of executing the command in the IoT device can be sent to the vehicle via the third server, the second server, and the first server. Attached Figure Description

[0027] These and / or other aspects of this disclosure should become apparent and more readily understood from the following description of the embodiments in conjunction with the accompanying drawings:

[0028] Figure 1 This is a diagram illustrating the configuration of a car-to-home service according to an embodiment of the present disclosure;

[0029] Figure 2 It is shown schematically. Figure 1 The diagram shows the components of the car-to-home service;

[0030] Figure 3This is a schematic diagram illustrating the process of querying the current status of an Internet of Things (IoT) device in a vehicle's car-to-home service according to an embodiment of the present disclosure; and

[0031] Figure 4 This is a diagram illustrating the process of controlling an IoT device in a vehicle-to-home service according to an embodiment of the present disclosure. Detailed Implementation

[0032] When a component, apparatus, element, etc., of this disclosure is described as having a purpose or performing an operation or function, the component, apparatus, or element shall be regarded herein as being "configured" to satisfy that purpose or perform that operation or function. Figure 1 This is a diagram illustrating the configuration of a car-to-home service according to an embodiment of the present disclosure.

[0033] refer to Figure 1 The present disclosure provides a vehicle-to-home service according to embodiments of the present disclosure to enable wireless communication between vehicle 100, original equipment manufacturer (OEM) server 110, main content provider (MCP) server 120 and content provider (CP) server 130.

[0034] Vehicle 100 communicates with OEM server 110 via head unit 102. Head unit 102 of vehicle 100 displays a user interface related to the car-to-home service on a monitor, allowing users to use the service by manipulating the user interface displayed on the head unit 102's monitor. For example, if a user in vehicle 100 wants to turn on the cooling system 140d before arriving at home 150, the user can invoke the car-to-home user interface and manipulate the service to turn on the cooling system 140d via the monitor of head unit 102 of vehicle 100. The monitor can be integrated with head unit 102 or can be installed separately from head unit 102.

[0035] OEM server 110 is a server operated by the manufacturer of vehicle 100 for vehicle-to-home services and is named OEM based on the reference vehicle manufacturer. OEM server 110 can also be referred to as a "vehicle manufacturer server". This OEM server 110 receives vehicle-to-home commands generated from host 102 of vehicle 100 and sends the commands to MCP server 120. Furthermore, OEM server 110 can send the processing results of the vehicle-to-home commands received from MCP server 120 back to host 102 of vehicle 100. The vehicle-to-home command may include a current status query request for querying the current status of Internet of Things (IoT) device 140.

[0036] MCP server 120 is a server operated by a home IoT service provider that provides IoT services used in the home; in other words, it provides home IoT services. It receives multiple home IoT services, eliminating the need for users to create accounts for multiple service providers. Instead, users simply subscribe to one MCP service with a single account, allowing them to use home IoT services from multiple downstream CPs subscribed to by that MCP. MCP server 120 transmits information about each IoT device registered by the user to OEM server 110. Furthermore, MCP server 120 sends vehicle-to-home commands received from OEM server 110 to IoT devices linked to MCP server 120 (e.g., [example devices]). Figure 1 The IoT device 140 in the system executes the commands in the IoT device and transmits the results to the OEM server 110. The OEM server 110 and the MCP server 120 can identify the user by matching (registering) the user's vehicle-to-home service account with the user's IoT service account.

[0037] CP server 130 is a server operated by each home IoT manufacturer that manufactures and sells IoT devices 140. For example, a home IoT manufacturer that manufactures and sells air purifier 140b provides users with home IoT content related to air purifier 140b and operates CP server 130 to provide home IoT content. Therefore, in Figure 1 In this context, multiple CP servers 130 may exist, depending on the manufacturer of each IoT device 140 provided at home 150. Figure 1 Only one CP server, 130, is shown in the image.

[0038] exist Figure 1 In this process, the MCP providing home IoT services obtains the status information of the IoT devices through the CP server 130 of the CP that manufactures / sells IoT devices, and sends the obtained status information to the host 102 of the vehicle 100 through the OEM server 110.

[0039] exist Figure 1 Examples of IoT devices 140 include a gas valve 140a, an air purifier 140b, a lighting device 140c, a cooling device 140d, and a heating device 140e. However, the IoT device 140 is not limited to... Figure 1 The ones shown, and their applications can be extended to all types of devices that can be controlled through car-to-home services.

[0040] Figure 2 It is shown schematically. Figure 1 The diagram shows the components of the car-to-home service.

[0041] refer to Figure 2The vehicle-to-home command generated by the host 102 of vehicle 100 is sent to IoT device 140 via OEM server 110, MCP server 120 and CP server 130. After receiving the vehicle-to-home command, IoT device 140 executes the command and sends the result of the execution to the host 102 of vehicle 100 via CP server 130, MCP server 120 and OEM server 110.

[0042] However, when the "vehicle arrives at home" command and the result of executing the command are sent in the aforementioned route, it takes a long time to transmit the information, and the user has to wait a long time to view the result after the "vehicle arrives at home" command is generated. To shorten the time spent checking the result after the "vehicle arrives at home" command is generated, the vehicle and its control method according to embodiments of the present invention can perform the following... Figure 3 and Figure 4 The information processing and transmission are shown.

[0043] Figure 3 This diagram illustrates the process of querying the current status of an IoT device in a vehicle's car-to-home service according to an embodiment of this disclosure. Figure 3 In this context, "[#n]" represents the division of information processing tasks, "t(sn)" represents the information sending time (sending time) according to the task, and "t(rn)" represents the information receiving time (receiving time) according to the task.

[0044] In [#1], the host 102 of vehicle 100 sends the current location, destination, and stopover points (if required) of vehicle 100 to OEM server 110 from the engine start time, for the following situations.

[0045] - When the engine of vehicle 100 is turned on or off, transmit the current location, destination, and intermediate stops (if necessary).

[0046] - When the destination / stopover of vehicle 100 is set or changed, send the current location, destination, and stopover (if necessary).

[0047] - When the management area of ​​the current location of vehicle 100 changes, send the current location, destination, and intermediate stops (if necessary).

[0048] In [#2], OEM server 110 queries MCP server 120 for the current status of IoT device 140 from when the engine of vehicle 100 is started until the engine is turned off, at a preset status query period. OEM server 110 also updates information about the current status of IoT device 140. The preset status query period for querying the current status of IoT device 140 can be determined as follows: When the current location of vehicle 100 and the current location of IoT device 140 are in the same administrative region, the status query period can be increased, making the status query interval shorter than the default value (e.g., once / 1 minute). Furthermore, even when the destination / intermediate stop of vehicle 100 is in the same administrative region as the current location of IoT device 140, the status query period can be increased, making the status query interval shorter than the default value (e.g., once / 1 minute). In other cases, the status query period can be decreased, making the status query interval longer than the default value (e.g., once / 10 minutes). When the current location of vehicle 100 is the same as the current location of IoT device 140, or when the destination / intermediate stop of vehicle 100 is the same as the current location of IoT device 140, as described above, setting the status query cycle upward has a shorter query interval, thereby enabling a faster response to requests for status information.

[0049] As described above, while information about the current state of IoT device 140 is stored in OEM server 110 through processes [#1] and [#2], when a request to query the current state of IoT device 140 connected to host 102 of vehicle 100 is generated in [#3], in [#4], OEM server 110 sends information about the current state of IoT device 140 currently stored in OEM server 100 to host 102 of vehicle 100. In [#5], host 102 of vehicle 100 displays the information about the current state of IoT device 140 received from OEM server 110 to the user via a display.

[0050] Although in [#4] OEM server 110 has already sent information about the current status of IoT device 140 currently stored in OEM server 110 to host 102 of vehicle 100, OEM server 110 again queries MCP server 120 for the current status of IoT device 140 and updates the result in [#6]. In [#7], if the information about the current status of IoT device sent in [#4] does not match the information about the current status of IoT device 140 updated in [#6], OEM server 110 will send the new information about the current status of IoT device 140 updated in [#6] to host 102 of vehicle 100. Host 102 of vehicle 100 displays the new information about the current status of IoT device 140 received in [#7] on a display so that the user can recognize more up-to-date current status information of IoT device 140.

[0051] Therefore, in embodiments of this disclosure, when querying the status information of IoT device 140, the current status information of IoT device 140 stored in OEM server 110 in [#4] is first displayed on the display of host unit 102, and if necessary, in [#7], the information about the current status is updated to the latest current status information of IoT device 140 and displayed on the display of host unit 102. This can shorten the waiting time of users in vehicle 100 by reducing the time spent displaying information about the current status of IoT device 140 to users in vehicle 100.

[0052] For example, such as Figure 3 As shown, if only the processing of [#6], [#7] and [#8] is performed without the processing of [#3] and [#4], and the current state of the IoT device 140 is directly queried and displayed on the display, the time spent by the user to receive information about the current state of the IoT device 140 can be equal to t(s1)+t(s2)+t(s3)+t(s4)+t(r4)+t(r3)+t(r2)+t(r1).

[0053] Unlike the above, embodiments of this disclosure provide that the current state information of the IoT device 140, already stored in the OEM server 110, is first displayed through processing [#3] and [#4], allowing the user to receive information about the current state of the IoT device 140 within a relatively short time of t(s1)+t(r1). Therefore, according to embodiments of this disclosure, the user can have a significantly shorter waiting time t(s1)+t(r1) than the existing waiting time t(s1)+t(s2)+t(s3)+t(s4)+t(r4)+t(r3)+t(r2)+t(r1).

[0054] In this disclosure, even though information about the current state is displayed in [#5] and then replaced by the latest current state information of the IoT device 140 and displayed in [#8], since the user mainly receives information about the current state of the IoT device 140 in [#4], the user may feel as if they are waiting for a very short time compared to waiting until point [#8].

[0055] Figure 4 This is a diagram illustrating the process of controlling an IoT device in a vehicle-to-home service according to an embodiment of the present disclosure. Figure 4 In this context, "[#n]" represents the division of information processing tasks, "t(sn)" represents the information sending time (sending time) according to the task, and "t(rn)" represents the information receiving time (receiving time) according to the task.

[0056] In [#11], a user in vehicle 100 can invoke the user interface of the host 102 of vehicle 100 and manipulate the user interface to generate a car-to-home command to control one of the IoT devices 140 in home 150.

[0057] In [#12], the vehicle-to-home command generated from the host 102 of the vehicle 100 is sent to the MCP server 120 via the OEM server 110.

[0058] MCP server 120 sends the vehicle-to-home command received from OEM server 110 to CP server 130 to request control corresponding to the vehicle-to-home command, and if the "control request" is executed according to the predetermined protocol, then in [#13], OEM server 110 is notified that the control request has been successfully executed.

[0059] In [#14], the OEM server 110 sends a message to the host 102 of the vehicle 100 indicating that the corresponding vehicle-to-home command has been executed successfully. In [#15], the host 102 displays on the screen that the corresponding vehicle-to-home command has been successfully executed so that the user can recognize the result of executing the vehicle-to-home command.

[0060] However, in the processing of [#11] to [#14], the successful execution of the car-to-home command is assumed and indicated by the display based solely on the normal transmission of the control request for the car-to-home command from MCP server 120 to CP server 130, rather than checking in practice whether the corresponding car-to-home command has been successfully executed.

[0061] In the processing of [#14] and [#15] in the host 102 of vehicle 100, MCP server 120 sends the corresponding vehicle-to-home command to CP server 130 in [#16], enabling the IoT device 140 to execute control corresponding to the vehicle-to-home command in the form of backend control. When the vehicle-to-home command is successfully executed in IoT device 140, in [#17], CP server 130 sends the control result of IoT device 140 and information about the current status of IoT device 140 to MCP server 120. MCP server 120 sends the control result and current status information of IoT device 140 to OEM server 110 in [#18].

[0062] In [#19], if the vehicle-to-home command generated in [#11] does not match the control result and current status information of [#18] (i.e., in the case of control failure), the OEM server 110 repeats the processing of #12 a predetermined number of times until control succeeds. If control fails even after the predetermined number of repetitions, the OEM server 110 notifies the host 102 of the vehicle 100 of the control failure in [#20], and the host 102 correctly indicates the control failure through the display in [#21].

[0063] If control based on the car-to-home command generated in [#11] fails, the previous success indication is corrected, and failure is indicated in [#20] and [#21]. Conversely, if control based on the car-to-home command generated in [#11] succeeds, there is no need to indicate success again, as success has already been indicated via the display on host 102 in [#15]. Therefore, since the control result based on the car-to-home command generated in [#11] is primarily represented in the processing of [#11] to [#15], the result of executing the car-to-home command is exposed to the user more quickly compared to the case where success is confirmed in practice and the result is indicated via processing of [#16] to [#21]. This can reduce the user's waiting time in vehicle 100 by shortening the time spent displaying the result of executing the car-to-home command to the user in IoT device 140.

[0064] For example, such as Figure 4 As shown, if the result of executing the car-to-home command in the IoT device 140 is displayed on the screen only through the processing of [#16] to [#21] and not through the processing of [#13] and [#14], the time when the user receives the result of the car-to-home command execution through the display of the host 102 can be equal to t(s11)+t(s12)+t(s13)+t(s14)+t(r14)+t(r13)+t(r12)+t(r11).

[0065] Unlike the above, in the embodiments of this disclosure, it is assumed that the success of the car-to-home command is based solely on the successful transmission of the car-to-home command from MCP server 120 to CP server 130 and the initial indication of success through processes [#13] and [#14]. This allows the user to recognize the success of the car-to-home command within a relatively short time of t(s11)+t(s12)+t(r12)+t(r11). Therefore, according to the embodiments of the present invention, it can be seen that the user's waiting time t(s11)+t(s12)+t(r12)+t(r11) is significantly shorter than the existing waiting time t(s11)+t(s12)+t(s13)+t(s14)+t(r14)+t(r31)+t(r12)+t(r11).

[0066] In this disclosure as described above, even if the successful execution of the car-to-home command is indicated in [#15] and then replaced by the failure of the car-to-home command as indicated in [#21], since the user mainly receives whether the car-to-home command was successful in [#15], the user can feel that the waiting time is relatively short compared to the case of waiting until the time [#21].

[0067] As is evident from the above, when implementing a car-to-home service that communicates through multiple servers, this disclosure can shorten the waiting time for users to receive the results of commands (requests).

[0068] The foregoing description of this disclosure is for illustrative purposes, and those skilled in the art will understand that other specific modifications can be readily made without departing from the technical spirit or essential characteristics of this disclosure. Therefore, the above embodiments should be considered illustrative rather than restrictive in all respects. The scope of this disclosure is not limited by the foregoing detailed description, but rather by the appended claims. It should also be understood that all variations or modifications derived from the definitions and scope of the claims and their equivalents fall within the scope of this disclosure.

Claims

1. A method for controlling a vehicle, the method comprising: The system queries the current status of the IoT devices linked to enable remote vehicle control from the first server and stores the current status of the queried IoT devices. When a request for querying the current status of the IoT device is generated from the vehicle, information about the current status of the IoT device stored in the first server is obtained, and the obtained information about the current status of the IoT device is displayed on a display. Re-query the current state of the IoT device to update the information about the current state of the IoT device stored in the first server; and When the information about the current state of the IoT device displayed on the display does not match the information about the current state of the IoT device updated in the first server, the information about the current state of the IoT device updated in the first server is displayed on the display. The first server is configured to receive the current state of the IoT device from the second server and update the current state of the IoT device during a preset period of each state query cycle. The first server is configured to set the time period of the preset cycle based on the location of the vehicle and the location of the IoT device. When the destination or intermediate stop of the vehicle changes, obtain the destination information or intermediate stop information of the vehicle. When at least one of the vehicle's destination and intermediate stop is located in the same administrative region as the location of the IoT device, the time period of the preset cycle is set as the first time period; when neither the vehicle's destination nor intermediate stop is located in the same administrative region as the location of the IoT device, the time period of the preset cycle is set as a second time period that is longer than the first time period.

2. The method according to claim 1, wherein, The first server is operated by the manufacturer of the vehicle to enable the IoT device at the remote site to be controlled by the vehicle.

3. The method according to claim 2, wherein, The first server communicates with the IoT device through the second and third servers.

4. The method according to claim 3, wherein, The second server is operated by an IoT service company to provide IoT services through the IoT device; and The third server is operated by the manufacturer of the IoT device to provide content related to the IoT device.

5. The method according to claim 4, wherein, The first server and the second server send a request to the third server to query the current state of the IoT device, so as to perform a query for the current state of the IoT device. Specifically, the query results of the current state of the IoT device are sent to the first server through the third server and the second server, and the query results of the current state of the IoT device are stored in the first server.

6. A method for controlling a vehicle, the method comprising: In response to a command generated from the vehicle for remotely controlling an Internet of Things (IoT) device located at a remote site, the command is sent from the first server to the second server; In response to the successful transmission of the command from the first server to the second server, before checking the result of the actual execution of the command in the IoT device, it is assumed that the command has been executed based on the successful transmission of the command, and the execution of the command is pre-displayed on the display of the vehicle; The second server sends the command to the IoT device and receives the result of executing the command and the current status information of the IoT device. Based on a comparison of the command, the result of executing the command, and the current state information of the IoT device, it is determined whether the command has been executed in the IoT device; In response to determining that the command was not executed in the IoT device, the first server repeatedly sends the command to the second server a predetermined number of times until the command is successfully executed. and In response to the command still not being successfully executed after the command has been repeatedly sent a predetermined number of times, the system correctively indicates that the command was not executed and displays the correction result on the display of the vehicle. The first server is configured to receive the current state of the IoT device from the second server and update the current state of the IoT device at a preset period. The first server is configured to set the time period of the preset cycle based on the location of the vehicle and the location of the IoT device.

7. The method according to claim 6, wherein, The first server is operated by the vehicle manufacturer to enable the IoT device at the remote site to be controlled by the vehicle.

8. The method according to claim 7, wherein, The first server communicates with the IoT device through the second and third servers.

9. The method according to claim 8, wherein, The second server is operated by an IoT service company to provide IoT services through the IoT device; and The third server is operated by the manufacturer of the IoT device to provide content related to the IoT device.

10. The method according to claim 9, wherein, The commands are sent from the first server and the second server to the third server to execute the control corresponding to the commands, and The result of executing the command in the IoT device is sent to the vehicle through the third server, the second server, and the first server.

11. A system for controlling a vehicle, the system comprising: The host is configured to perform remote control of IoT devices at remote sites from the vehicle. as well as The display is configured to show a user interface and information related to the remote control of the IoT device. The host is configured as follows: The system queries the first server to determine the current state of the IoT device linked to enable remote vehicle control, and stores the retrieved current state of the IoT device. When a request for querying the current status of the IoT device is generated from the vehicle, information about the current status of the IoT device stored in the first server is retrieved, and the information about the current status of the IoT device is displayed on the display. The first server re-queries the current state of the IoT device to update the information about the current state of the IoT device stored in the first server, and compares the information about the current state of the IoT device displayed on the display with the information about the current state of the IoT device updated in the first server to determine whether the information about the current state of the IoT device displayed on the display matches the information about the current state of the IoT device updated in the first server. When the information about the current state of the IoT device displayed on the display does not match the information about the current state of the IoT device updated in the first server, the information about the current state of the IoT device updated in the first server is displayed on the display. The first server is configured to receive the current state of the IoT device from the second server and update the current state of the IoT device during a preset period of each state query cycle. The first server is configured to set the time period of the preset cycle based on the location of the vehicle and the location of the IoT device. When the destination or intermediate stop of the vehicle changes, obtain the destination information or intermediate stop information of the vehicle. When at least one of the vehicle's destination and intermediate stop is located in the same administrative region as the location of the IoT device, the time period of the preset cycle is set as the first time period; when neither the vehicle's destination nor intermediate stop is located in the same administrative region as the location of the IoT device, the time period of the preset cycle is set as a second time period that is longer than the first time period.

12. The system according to claim 11, wherein, The first server is operated by the vehicle manufacturer to enable the IoT device at the remote site to be controlled by the vehicle.

13. The system according to claim 12, wherein, The first server communicates with the IoT device through the second and third servers.

14. The system according to claim 13, wherein, The second server is operated by an IoT service company to provide IoT services through the IoT device; and The third server is operated by the manufacturer of the IoT device to provide content related to the IoT device.

15. The system according to claim 14, wherein, The first server and the second server send a request to the third server to query the current state of the IoT device, so as to perform a query for the current state of the IoT device. Specifically, the query results of the current state of the IoT device are sent to the first server through the third server and the second server, and the query results of the current state of the IoT device are stored in the first server.

16. A system for controlling a vehicle, the system comprising: The host is configured to perform remote control of IoT devices at remote sites from the vehicle. as well as The display is configured to show a user interface and information related to the remote control of the IoT device. The host is configured as follows: In response to a command generated from the vehicle for remotely controlling the IoT device located at the remote site, the command is sent to a second server via a first server. In response to the successful transmission of the command from the first server to the second server, before checking the result of the actual execution of the command in the IoT device, it is assumed that the command has been executed based on the successful transmission of the command, and the execution of the command is pre-displayed on the display. In response to sending the command from the second server to the IoT device, the system receives the result of executing the command and the current status information of the IoT device. By comparing the command with the result of executing the command and the current status information of the IoT device, it is determined whether the command has been executed in the IoT device; In response to determining that the command was not executed in the IoT device, the command is repeatedly sent from the first server to the second server a predetermined number of times until the command is successfully executed; and In response to the command still not being successfully executed after the command has been repeatedly sent a predetermined number of times, the system correctively indicates that the command was not executed and displays the correction result on the display of the vehicle. The first server is configured to receive the current state of the IoT device from the second server and update the current state of the IoT device during a preset period of each state query cycle. The first server is configured to set the time period of the preset cycle based on the location of the vehicle and the location of the IoT device.

17. The system according to claim 16, wherein, The first server is operated by the vehicle manufacturer to enable the IoT device at the remote site to be controlled by the vehicle.

18. The system according to claim 17, wherein, The first server communicates with the IoT device through the second and third servers.

19. The system of claim 18, wherein the second server is a server operated by an IoT service company to provide IoT services through the IoT device; and in, The third server is operated by the manufacturer of the IoT device to provide content related to the IoT device.

20. The system according to claim 19, wherein, The command is sent to the IoT device through the first server and the second server, and through the third server, in order to execute the control corresponding to the command, and The result of executing the command in the IoT device is sent to the vehicle through the third server, the second server, and the first server.

Images