Equipment management method, device and system on LIN bus, storage medium and electronic device

Abstract

The invention provides an equipment management method, device and system on an LIN bus, a storage medium and an electronic device.The method comprises the steps that a first scheduling table locally stored by a controller of the LIN bus of a vehicle is read according to a first scheduling period, the first dispatch table is used for storing a mapping relationship between the device identifiers of all pluggable devices and LIN communication message identifiers; a first scheduling request is sequentially sent to all pluggable devices on the LIN bus according to the first scheduling table, and the first scheduling request carries LIN communication message identifiers of the pluggable devices in the first scheduling table; monitoring a reply message returned by the first device based on the first scheduling request; and determining that the first equipment accesses the LIN bus according to the reply message. Through the embodiment of the invention, the technical problem that the LIN bus of the vehicle cannot realize hot plugging of equipment in the related technology is solved, resources are saved, and the safety and performance requirements are met.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicles, and in particular, to a method and device, a system, a storage medium, and an electronic device for device management on a LIN bus. Background Art

[0002] In related technologies, the automotive LIN (Local Interconnect Network) bus is an important part of an automobile and a technology in the development process. It is often used in the basic control system of an automobile, generally used for communication between an integrated switch module and a controller, such as a steering wheel switch and a controller; it is also used for communication between some special sensors and a controller, such as a rain sensor. However, such uses are all designed in advance. After clarifying the communication nodes and interaction protocols, it is clear during the vehicle development process that all interactions are carried out by components fixed on the vehicle, and hot plugging cannot be achieved on the LIN bus, resulting in poor flexibility of the LIN bus. It is impossible to realize communication between intelligent IOT devices and an automobile through the LIN bus. IOT devices generally use BLE (Bluetooth Low Energy), WiFi (Wireless Fidelity), or other wireless communication protocols as the basic communication protocol, and more communication modules need to be installed additionally, resulting in an increase in the material cost of the automobile.

[0003] In view of the above problems existing in related technologies, no efficient and accurate solution has been found yet. Summary of the Invention

[0004] The present invention provides a method and device, a system, a storage medium, and an electronic device for device management on a LIN bus to solve the technical problems in related technologies.

[0005] According to an embodiment of the present invention, a method for device management on a LIN bus is provided, which is applied to a controller of a master node of the LIN bus and includes: reading a first scheduling table locally stored in the controller of the LIN bus of the vehicle according to a first scheduling period, where the first scheduling table is used to store the mapping relationship between the device identifiers of all pluggable devices and the LIN communication message identifiers; sequentially sending a first scheduling request to all pluggable devices on the LIN bus according to the first scheduling table, where the first scheduling request carries the LIN communication message identifier of the pluggable device in the first scheduling table; monitoring a reply message returned by a first device based on the first scheduling request; and determining that the first device accesses the LIN bus according to the reply message.

[0006] Optionally, determining that the first device accesses the LIN bus according to the response message includes: parsing the padding data and the first message identifier in the response message; determining whether the padding data is empty; if the padding data is not empty, looking up a first device identifier that matches the first message identifier in the first scheduling table; and determining that the corresponding first device has accessed the LIN bus based on the first device identifier.

[0007] Optionally, after determining that the first device accesses the LIN bus according to the response message, the method further includes: looking up matching first LIN attribute information based on the first device identifier of the first device; and updating the first message identifier and the first LIN attribute information to a second scheduling table stored locally in the controller, where the second scheduling table is used to store the mapping relationship between the LIN communication message identifiers and the LIN attribute information of all currently pluggable devices connected to the vehicle.

[0008] Optionally, updating the device identifier to the second scheduling table stored locally includes: determining whether the first message identifier exists in the second scheduling table; if the first message identifier does not exist in the second scheduling table, associatively storing the first message identifier and the first LIN attribute information in the second scheduling table.

[0009] Optionally, the method further includes: reading the second scheduling table stored locally in the controller according to a second scheduling period, where the second scheduling table is used to store the mapping relationship between the LIN communication message identifiers and the LIN attribute information of all currently pluggable devices connected to the vehicle; sequentially sending a second scheduling request to all pluggable devices on the LIN bus according to the second scheduling table, where the second scheduling request carries the LIN communication message identifiers of the pluggable devices in the second scheduling table; monitoring the message response status of a second device for the second scheduling request; and determining that the second device is in an offline state on the LIN bus according to the message response status.

[0010] Optionally, determining that the second device is in an offline state on the LIN bus according to the message response status includes: if the message response status is a message loss status, looking up the second device to which a second message identifier belongs according to the first scheduling table; querying the historical message response status of the second device in several historical scheduling periods of the second scheduling table; and confirming that the second device is in an offline state on the LIN bus according to the historical message response status.

[0011] Optionally, confirming that the second device is in an offline state on the LIN bus according to the historical message response status includes: determining whether the historical message response statuses are all message loss statuses; if the historical message response statuses are all message loss statuses, determining that the second device is in an offline state on the LIN bus, and updating the second scheduling table.

[0012] Optionally, after determining whether the historical message response statuses are all message loss statuses, the method further includes: if the historical message response statuses are not all message loss statuses, determining that the second device is in a faulty state.

[0013] Optionally, before reading the first scheduling table locally stored in the controller of the LIN bus of the vehicle according to the first scheduling period, the method further includes: receiving a scheduling table update request from the cloud, where the scheduling table update request carries the first scheduling table of the latest version; locally updating the first scheduling table based on the scheduling table update request.

[0014] Optionally, receiving a scheduling table update request from the cloud includes: reading the first version information of the first scheduling table locally stored, and obtaining the second version information of the latest first scheduling table on the cloud; determining whether the first version information is the same as the second version information; if the first version information is not the same as the second version information, receiving the scheduling table update request from the cloud.

[0015] According to another embodiment of the present invention, there is provided a device management device on a LIN bus, which is applied to a controller of a main node of the LIN bus, and includes: a first reading module, configured to read a first scheduling table locally stored in the controller of the LIN bus of the vehicle according to a first scheduling period, where the first scheduling table is used to store the mapping relationship between the device identifiers of all pluggable devices and the LIN communication message identifiers; a first sending module, configured to sequentially send a first scheduling request to all pluggable devices on the LIN bus according to the first scheduling table, where the first scheduling request carries the LIN communication message identifier of the pluggable device in the first scheduling table; a first monitoring module, configured to monitor a reply message returned by the first device based on the first scheduling request; a first determining module, configured to determine that the first device is connected to the LIN bus according to the reply message.

[0016] Optionally, the first determining module includes: a parsing unit, configured to parse the padding data and the first message identifier in the reply message; a judging unit, configured to judge whether the padding data is empty; a searching unit, configured to, if the padding data is not empty, search for a first device identifier matching the first message identifier in the first scheduling table; a determining unit, configured to determine that the corresponding first device has been connected to the LIN bus based on the first device identifier.

[0017] Optionally, the device further includes: a lookup module, configured to, after the first determination module determines that the first device accesses the LIN bus according to the response message, look up matching first LIN attribute information based on the first device identifier of the first device; a first update module, configured to update the first message identifier and the first LIN attribute information to a second scheduling table locally stored in the controller, where the second scheduling table is used to store a mapping relationship between LIN communication message identifiers and LIN attribute information of all pluggable devices currently connected to the vehicle.

[0018] Optionally, the first update module includes: a judgment unit, configured to judge whether the first message identifier exists in the second scheduling table; a storage unit, configured to, if the first message identifier does not exist in the second scheduling table, associatively store the first message identifier and the first LIN attribute information in the second scheduling table.

[0019] Optionally, the device further includes: a second reading module, configured to read the second scheduling table locally stored in the controller according to a second scheduling period, where the second scheduling table is used to store a mapping relationship between LIN communication message identifiers and LIN attribute information of all pluggable devices currently connected to the vehicle; a second sending module, configured to sequentially send a second scheduling request to all pluggable devices on the LIN bus according to the second scheduling table, where the second scheduling request carries the LIN communication message identifier of the pluggable device in the second scheduling table; a second monitoring module, configured to monitor a message response status of a second device for the second scheduling request; a second determination module, configured to determine that the second device is in an offline state on the LIN bus according to the message response status.

[0020] Optionally, the second determination module includes: a lookup unit, configured to, if the message response status is a message loss status, look up the second device to which the second message identifier belongs according to the first scheduling table; a query unit, configured to query historical message response statuses of the second device in several historical scheduling periods of the second scheduling table; a determination unit, configured to confirm that the second device is in an offline state on the LIN bus according to the historical message response status.

[0021] Optionally, the determination unit includes: a judgment subunit, configured to judge whether all the historical message response statuses are message loss statuses; a first determination subunit, configured to, if all the historical message response statuses are message loss statuses, determine that the second device is in an offline state on the LIN bus and update the second scheduling table.

[0022] Optionally, the determining unit further includes: a second determining subunit, configured to, after the determining subunit determines whether all of the historical message response statuses are message loss statuses, if not all of the historical message response statuses are message loss statuses, determine that the second device is in a fault state.

[0023] Optionally, the apparatus further includes: a receiving module, configured to receive a scheduling table update request from the cloud before the first reading module reads a first scheduling table locally stored in a controller of a LIN bus of a vehicle according to a first scheduling period, where the scheduling table update request carries a first scheduling table of a latest version; and a second updating module, configured to update the first scheduling table locally based on the scheduling table update request.

[0024] Optionally, the receiving module includes: a reading unit, configured to read first version information of the first scheduling table locally stored and obtain second version information of the latest first scheduling table on the cloud; a determining unit, configured to determine whether the first version information is the same as the second version information; and a receiving unit, configured to receive the scheduling table update request from the cloud if the first version information is not the same as the second version information.

[0025] According to another embodiment of the present invention, there is provided a device management system on a LIN bus, including a main node, a plurality of slave nodes, and a cloud. The plurality of slave nodes are connected to the LIN bus, and the main node is communicatively connected to the cloud. Wherein, the main node includes the apparatus as described in the above embodiment; the slave node includes a pluggable LIN interface, configured to access a pluggable device and respond to a scheduling request of the main node; and the cloud is configured to manage a first scheduling table of the main node.

[0026] According to another aspect of the embodiments of the present application, there is also provided a storage medium, which includes a stored program, and when the program runs, it executes the above steps.

[0027] According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a processor, a communication interface, a memory, and a communication bus. The processor, the communication interface, and the memory communicate with each other through the communication bus. Wherein: the memory is configured to store a computer program; and the processor is configured to execute the steps in the above method by running the program stored on the memory.

[0028] The embodiments of the present application also provide a computer program product including instructions, which when running on a computer, causes the computer to execute the steps in the above method.

[0029] Advantages of the present invention: 1. After a pluggable device for LIN bus communication is connected to the LIN physical interface, it can be detected and recognized by the vehicle as a specific device, and new devices connected to the LIN bus can be detected in real time, which reflects the intelligence and automation of the vehicle, saves resources, meets safety and performance requirements, and also enhances the user experience of directly using the device after plugging it in; 2. Monitor the offline status of devices on the LIN bus based on the second scheduling table, and save the LIN resources of the entire vehicle during the dynamic adjustment process; 3. When the vehicle has left the factory but the vehicle manufacturer has developed a new pluggable device, and a new first scheduling table is updated in the cloud, the vehicle can update the pluggable device list without updating the controller software. After the user inserts a new device on the LIN bus at any time, the vehicle can detect the device and communicate with the new device. Description of the Drawings

[0030] The drawings described herein are used to provide a further understanding of the present invention and form a part of this application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation to the present invention. In the drawings: Figure 1 is a hardware structure block diagram of an automobile according to an embodiment of the present invention; Figure 2 is a flowchart of a device management method on a LIN bus according to an embodiment of the present invention; Figure 3 is a system architecture diagram of a LIN bus in an embodiment of the present invention; Figure 4 is a flowchart of detecting the access of a device on a LIN bus in an embodiment of the present invention; Figure 5 is a flowchart of detecting the offline of a device on a LIN bus in an embodiment of the present invention; Figure 6 is a flowchart of scheduling table update in an embodiment of the present invention; Figure 7 is a switching logic diagram of a scheduling table in an embodiment of the present invention; Figure 8 is a structure block diagram of a device management device on a LIN bus according to an embodiment of the present invention. Detailed Embodiments

[0031] To enable those skilled in the art to better understand the solution of this application, the following will clearly and completely describe the technical solutions in the embodiments of this application in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of this application. It should be noted that, without conflict, the embodiments in this application and the features in the embodiments can be combined with each other.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned accompanying drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of this application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, product, or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or devices.

[0033] Embodiment 1 The method embodiment provided by the first embodiment of this application can be executed in an automobile, a server, a processor, an autonomous driving / assisted driving / smart driving controller, or a similar processing device. Taking running on an automobile as an example, Figure 1 is a hardware structure block diagram of an automobile according to an embodiment of the present invention. As Figure 1 shown, the automobile may include one or more ( Figure 1 only one is shown in the figure) processors 102 (the processors 102 may include, but are not limited to, processing devices such as a microprocessor MCU or a field programmable gate array FPGA) and a memory 104 for storing data. Optionally, the above-mentioned automobile may further include a transmission device 106 for communication functions and an input / output device 108. Those of ordinary skill in the art can understand that, Figure 1 the structure shown is only schematic and does not limit the structure of the above-mentioned automobile. For example, the automobile may further include more or fewer components than those Figure 1 shown in the figure, or have a different configuration from that Figure 1 shown in the figure.

[0034] The memory 104 can be used to store automotive programs, such as software programs and modules of application software, such as the automotive program corresponding to the device management method on the LIN bus of an automotive vehicle in an embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the automotive program stored in the memory 104, thereby implementing the above-mentioned method. The memory 104 can include high-speed random access memory, and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory 104 can further include a memory remotely disposed relative to the processor 102, and these remote memories can be connected to the automotive vehicle through a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0035] The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network can include a wireless network provided by a communication provider of the automotive vehicle. In one instance, the transmission device 106 includes a network adapter (abbreviated as NIC), which can be connected to other network devices through a base station and thus can communicate with the Internet. In one instance, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0036] In this embodiment, a device management method on the LIN bus is provided. Figure 2 is a flowchart of a device management method on the LIN bus according to an embodiment of the present invention, as Figure 2 shown, and this process includes the following steps: Step S201, read a first schedule stored locally in a controller of the LIN bus of the vehicle according to a first scheduling period, where the first schedule is used to store a mapping relationship between device identifiers of all pluggable devices and LIN communication message identifiers; In the LIN bus of this embodiment, there is a master node and multiple slave nodes. The controller on the master node serves as the master node of LIN communication. The controller manages the first schedule and has the authority to schedule all IDs (identifiers) in the LIN schedule. The relationship between all pluggable device IDs and LIN communication message IDs is stored in the local storage unit. The device ID and the message ID have a mandatory and unique mapping relationship, which is uniformly managed by the system. The first schedule is also called the platform schedule. The device ID can be the device name, device code, etc. of the corresponding pluggable device. The message ID is used as the communication ID with the corresponding pluggable device, including the message ID carried in the retrieval request sent to the device and the message ID carried in the reply message received from the device.

[0037] Figure 3 It is the system architecture diagram of the LIN bus in the embodiment of the present invention. The LIN bus includes a controller and multiple LIN interfaces for accessing pluggable devices (such as pluggable device 1, pluggable device 2, etc.). The controller includes a processor and a storage unit, and the controller is connected to the cloud.

[0038] The system of the LIN bus consists of a controller with LIN communication function, an external pluggable device with LIN communication function, a LIN interface for the pluggable device to access the automotive LIN bus, a cloud facility providing LIN-related information, and a module with mobile network communication. The controller serves as the LIN communication master node, having the ability to schedule the slave nodes on this LIN bus, the ability to identify the feedback content of the nodes, and the ability to dynamically switch different scheduling tables; the pluggable device serves as each different slave node on this LIN bus, having the ability to reply with relevant information when responding to the master node's scheduling; the cloud facility has the ability to manage the scheduling table information and the pluggable device information; the module with mobile network communication has the ability to communicate with the cloud, verify the version, download the scheduling table and send it to the control; the slave nodes respond according to the master node's scheduling.

[0039] The LIN interface for the pluggable device to access the automotive LIN bus is connected to the controller through the vehicle harness. Through the exposed external interface, the pluggable device can access its LIN port; in addition, the controller pre-writes the relevant information of the currently accessible devices in the software and data storage unit. These relevant information contains the communication addresses corresponding to each pluggable device. The controller will schedule according to the currently connected devices, and at the same time periodically schedule the addresses of all the pluggable devices pre-stored on the LIN bus, and monitor whether the scheduled devices have fed back the corresponding content. If feedback is received, it is logically judged that this device is currently in the connected state, and this device's scheduling will be increased in the next scheduling.

[0040] Step S202: Send a first scheduling request to all the pluggable devices on the LIN bus in sequence according to the first scheduling table, where the first scheduling request carries the LIN communication message identifier of the pluggable device in the first scheduling table; Optionally, if the first scheduling table stores 10 pluggable devices, then a first scheduling request needs to be sent to these 10 pluggable devices. Each first scheduling request carries the LIN communication message identifier of one pluggable device in the first scheduling table. For example, if the sending interval of each pluggable device is 10 ms, then the duration of the first scheduling period is 100 ms.

[0041] Step S203: Monitor the reply message returned by the first device based on the first scheduling request; Optionally, the first device may be any pluggable device on the LIN bus, such as a rain sensor, a driving recorder, an ambient light, a speaker, etc.

[0042] If a pluggable device (such as the first device) in the first schedule is currently inserted into the LIN interface of the LIN bus, the pluggable device receives the LIN communication message identifier sent by the controller, and determines whether it is consistent with its own LIN communication message identifier. If they are consistent, according to the requirements of the LIN bus, supplement its own data after this LIN communication message identifier, encapsulate it into a reply message, and return it to the controller of the main node of the LIN bus. The LIN communication message identifier includes the first message identifier, the second message identifier, etc. described below.

[0043] Step S204, determining that the first device is connected to the LIN bus according to the reply message; Through the above steps, read the first schedule stored locally in the controller of the LIN bus of the vehicle according to the first scheduling period, where the first schedule is used to store the mapping relationship between the device identifiers of all pluggable devices and the LIN communication message identifiers; send the first scheduling request to all pluggable devices on the LIN bus in sequence according to the first schedule, where the first scheduling request carries the LIN communication message identifier of the pluggable device in the first schedule; monitor the reply message returned by the first device based on the first scheduling request; determine that the first device is connected to the LIN bus according to the reply message, which solves the technical problem that the LIN bus of the vehicle cannot achieve hot plugging of devices in the related art, discovers newly connected devices on the LIN bus in real time, reflects the intelligence and automation of the vehicle, saves resources, meets safety and performance requirements, and also increases the user experience of being able to directly use the device after plugging it in.

[0044] In an implementation manner of this embodiment, determining that the first device is connected to the LIN bus according to the reply message includes: parsing the padding data and the first message identifier in the reply message; determining whether the padding data is empty; if the padding data is not empty, searching for the first device identifier that matches the first message identifier in the first schedule; determining that the corresponding first device has been connected to the LIN bus based on the first device identifier.

[0045] Optionally, if the controller of the main node of the LIN bus does not receive the reply message returned by the first device based on the first scheduling request, it is considered that the first device is not connected to the LIN bus.

[0046] Optionally, if the padding data is not empty, it can be further determined whether the padding data matches the first message identifier. If it matches, the first device identifier that matches the first message identifier is searched for in the first scheduling table, and it is determined that the first device corresponding to the first device identifier has accessed the LIN bus.

[0047] Since the padding data is filled by a pluggable device (such as the first device) after receiving the first scheduling request sent by the controller of the master node of the LIN bus, the padding data of different pluggable devices can be different to prevent an unauthenticated third-party device from forging an authenticated pluggable device in the first scheduling table to access the LIN bus, thereby improving security.

[0048] In this embodiment, after determining that the first device has accessed the LIN bus according to the response message, it further includes: searching for matching first LIN attribute information based on the first device identifier of the first device; updating the first message identifier and the first LIN attribute information to a second scheduling table stored locally in the controller, where the second scheduling table is used to store the mapping relationship between the LIN communication message identifiers and LIN attribute information of all currently connected pluggable devices on the vehicle.

[0049] Optionally, the first LIN attribute information can be stored locally in the controller or in the cloud, and the controller of the master node is communicatively connected to the cloud.

[0050] Optionally, if three pluggable devices (device 1, device 2, device 3) are currently connected to the LIN bus of the vehicle, the second scheduling table will store the mapping relationship between the LIN communication message identifiers and LIN attribute information of the three pluggable devices.

[0051] Figure 4It is a flowchart of discovering device access on the LIN bus in an embodiment of the present invention. The platform schedule (the first schedule) has the IDs of all pluggable devices to the LIN bus and the LIN communication message IDs. The pluggable device is inserted into an exposed point (LIN interface) of a certain LIN network segment of the vehicle LIN bus and waits for the controller to schedule one of the message IDs of this plugged-in device on the LIN bus. The process includes: scheduling devices according to the platform schedule, the controller switches to the platform schedule, schedules according to the message IDs of all pluggable devices in the platform schedule, and sends a scheduling request; determines whether the slave node message replies. When the controller schedules a certain message ID, it sends the message ID to the LIN bus. The pluggable device receives the message ID sent by the controller, determines whether it is the same as its own message ID. If they are the same, according to the requirements of the LIN bus, after supplementing its own data after this message ID, it replies to the controller. If it is determined that it is not the same as its own message ID, it does not reply to the controller. The controller determines that there is data feedback for this message ID and considers that there is a device for this message ID, and determines that the device is LIN message online. If the device does not reply, it is determined that the device is LIN message offline; for the device with LIN message online, the controller maps it to the device online state, further queries the corresponding device information, and determines whether there is already the device information of this device in the actual vehicle schedule. If not, the device information of this device is added to the actual vehicle schedule and the actual vehicle schedule is updated. The controller identifies which pluggable device it belongs to according to the message ID replied by the device and the platform schedule, and then determines that this device belongs to the online state. At the same time, according to the associated information in the platform schedule, it confirms the device information such as the device ID and LIN attribute information corresponding to this message ID, and updates this device ID and LIN attribute information and other device information to the actual vehicle schedule (the second schedule).

[0052] In this way, the device is discovered, and according to the scheduling differences between the two schedules, the speed of the controller discovering device access to the LIN bus is improved.

[0053] Optionally, after determining that a certain device accesses the LIN bus, the device ID can be passed to the cockpit system and displayed on the human-machine interface to indicate that a new device has been discovered.

[0054] In one example, updating the device identifier to the second schedule stored locally includes: determining whether the first message identifier exists in the second schedule; if the first message identifier does not exist in the second schedule, associatively storing the first message identifier and the first LIN attribute information in the second schedule.

[0055] The second scheduling table in this embodiment is used to store the LIN communication message IDs and other LIN attribute information of all pluggable devices of the current vehicle, and is also called the in-vehicle scheduling table; the key attribute information related to the reception and transmission of communication messages included in the two scheduling tables is also stored in the second scheduling table, including but not limited to the LIN network segment ID of the LIN bus, the message ID under the network segment, the message ID attribute, the message ID transmission interval, the message ID scheduling order, the message data, the message length, etc.; among them, the LIN network segment ID is used for the controller to select which LIN network segment among all the LIN network segments accessed by this vehicle for the communication of this device; the message ID is used as the communication ID with this pluggable device, including the ID sent to the device and the ID for receiving the information sent by the device; the attribute of the message ID is used to let the controller identify that each ID is a communication with the device, whether it is the ID for sending information or the ID for receiving information; the ID transmission interval is used to adjust the frame interval time of LIN communication between different devices to adapt to the characteristics between different devices; the message ID scheduling order is used to adjust the sequence between different devices, so that devices with higher priority are scheduled first. At the same time, when the controller can only define a fixed-length array, it can identify invalid arrays and save chip resources; the message data is used to send the actual original message of LIN to the device or received from the device, and is used for the upper layer to parse the interaction information of this device; the message length is based on the fixed length of 8 Bytes of LIN bus data, but different devices may not require such a long length. The actual required length of data is identified by this field. For all attributes related to the reception and transmission of LIN bus messages, fields such as the above network segment ID, message ID, and message ID attribute can be defined according to the LIN bus standard or customized. The controller can be designed with specific fields to store and dynamically modify the parameters of these attributes.

[0056] In another implementation scenario of this embodiment, it further includes: reading the second scheduling table stored locally in the controller according to the second scheduling period, where the second scheduling table is used to store the mapping relationship between the LIN communication message identifiers and LIN attribute information of all currently connected pluggable devices on the vehicle; sending a second scheduling request to all pluggable devices on the LIN bus in sequence according to the second scheduling table, where the second scheduling request carries the LIN communication message identifiers of the pluggable devices in the second scheduling table; monitoring the message response status of the second device for the second scheduling request; determining that the second device is in an offline state on the LIN bus according to the message response status.

[0057] Optionally, the message response status includes a message loss status and a message reply status. If the second message responds to the second scheduling request and normally replies the message, it is in the message reply status. If the second message does not respond to the second scheduling request and does not normally reply the message (or does not reply the message), it is in the message loss status.

[0058] Currently, three pluggable devices (Device 1, Device 2, and Device 3) are connected to the LIN bus of the vehicle. Then, the second scheduling table sequentially sends second scheduling requests to Device 1, Device 2, and Device 3 according to the second scheduling period, and determines whether the device has gone offline according to the message response status of the corresponding device.

[0059] In one example, determining that the second device is in an offline state on the LIN bus according to the message response status includes: if the message response status is the message loss status, looking up the second device to which the second message identifier belongs according to the first scheduling table; querying the historical message response status of the second device in several historical scheduling periods of the second scheduling table; and confirming that the second device is in an offline state on the LIN bus according to the historical message response status.

[0060] Optionally, the historical message response status of the second device in the previous 2 historical scheduling periods can be queried, and whether it has gone offline is confirmed according to the message response status of the second device in three consecutive scheduling periods to prevent misjudgment. The historical message response status of this embodiment can be stored locally in the controller of the main node of the LIN bus or in the cloud.

[0061] In one implementation, confirming that the second device is in an offline state on the LIN bus according to the historical message response status includes: determining whether the historical message response statuses are all in the message loss status; if the historical message response statuses are all in the message loss status, determining that the second device is in an offline state on the LIN bus, and updating the second scheduling table.

[0062] If the second device is in an offline state on the LIN bus, the second device is deleted from the second scheduling table.

[0063] In another implementation, after determining whether the historical message response statuses are all in the message loss status, it further includes: if the historical message response statuses are not all in the message loss status, determining that the second device is in a faulty state.

[0064] If the second device simultaneously exhibits a message loss status and a message response status in multiple consecutive scheduling periods, the second device may be faulty, such as a loose plug interface or a malfunction of the internal controller of the second device.

[0065] Figure 5It is a flowchart for discovering that a device on the LIN bus is offline in an embodiment of the present invention. When a device is unplugged from the LIN bus, the device cannot communicate with the controller, and all messages cannot be communicated. The process for discovering a LIN bus device failure or offline state includes: The controller schedules the message IDs of all devices on the LIN bus according to the in-vehicle schedule table (the second schedule table). Since the device is unplugged, the slave node message is not replied, and the controller cannot receive all the messages of the device, and it is determined that the LIN message is lost; The messages of other slave nodes that are not unplugged from the LIN bus can be normally replied, and it is determined that the LIN message is online; The controller maps according to the response status of all messages to the device offline state, queries the corresponding device information, and determines whether all the LIN messages of the corresponding device are in the message loss state, and confirms whether all the messages associated with a certain device are lost. If they are all lost, it is determined that the device is offline.

[0066] Optionally, the controller can feedback this device offline state to the human-machine interaction system, and transmit the device offline information to the human-machine interaction system for display.

[0067] When the controller schedules the message ID of a pluggable device of a certain slave node in the in-vehicle schedule table, if a single message of the slave node is not replied, the controller feedbacks a fault message to the human-machine interaction system. If multiple scheduled request messages are not replied, it is determined to be offline.

[0068] In an implementation manner of this embodiment, before reading the first schedule table stored locally in the controller of the LIN bus of the vehicle according to the first scheduling period, it further includes: receiving a schedule table update request from the cloud, where the schedule table update request carries the latest version of the first schedule table; updating the first schedule table locally based on the schedule table update request.

[0069] Optionally, receiving the schedule table update request from the cloud includes: reading the first version information of the first schedule table stored locally, and obtaining the second version information of the latest first schedule table on the cloud; determining whether the first version information is the same as the second version information; if the first version information is not the same as the second version information, receiving the schedule table update request from the cloud.

[0070] Optionally, the schedule table update request can be actively sent by the cloud, or can be sent by the cloud after the controller of the master node of the LIN bus sends an update request to the cloud.

[0071] The cloud maintains the platform schedule table (the first schedule table): When there are new pluggable devices, the vehicle factory personnel enter the relevant information of this device in the cloud system, including the device ID, the LIN network segment it belongs to, the message IDs it owns, the relevant attributes of the IDs, the relevant attributes of the schedule table, etc., and generate a new version of the platform schedule table. Figure 6It is a flowchart of schedule update in an embodiment of the present invention. When the controller updates the platform schedule, it imports the latest platform schedule of the current node during generation, avoiding the problem of no network during vehicle production, which may lead to no platform schedule inside and the inability to detect equipment problems. When the vehicle has been produced but the vehicle factory has developed new pluggable devices and the cloud has updated the new platform schedule, when the controller needs to update the platform schedule, it goes through the mobile cellular network and the vehicle factory dedicated line, and performs a series of operations such as verifying and comparing the version number of the current platform schedule with that of the cloud. When the cloud determines that an update is needed or the integrated control determines that the schedule needs to be updated, the vehicle terminal downloads the latest platform schedule approved by the vehicle factory with the pluggable device ID and LIN-related information.

[0072] Since then, without updating the controller software, after the vehicle factory updates the pluggable device list and the user purchases the pluggable device and plugs it in, the vehicle can detect the device and communicate with it.

[0073] The first schedule (platform schedule) and the second schedule (actual vehicle schedule) of this embodiment can be cyclically retrieved. Figure 7 It is a switching logic diagram of the schedule in an embodiment of the present invention. The platform schedule has all the pluggable device information, while the actual vehicle schedule only has the information of the devices that have been plugged in currently. The two schedules are cyclically switched. By timing, the current time is determined to judge which schedule the current time corresponds to. For example, the total scheduling period is 100 ms, the scheduling period of the platform schedule is 90 ms, and the scheduling period of the actual vehicle schedule is 10 ms. If the current time has been timed for 60 ms, it corresponds to the platform schedule. Because the platform schedule has more comprehensive pluggable device information and a longer scheduling time, and the communication time between the pluggable device and the controller in a single cycle is relatively long, this schedule is only used to send the message IDs in this schedule to confirm whether a new device has been plugged in. If so, it will reply during the scheduling of the platform schedule, and the controller determines that a new device has been connected. Based on the characteristic that a vehicle cannot have all pluggable devices (for example, there are two switches in the platform schedule, but only one can be selected for a single vehicle), the actual vehicle schedule is mainly used for short-cycle information interaction between the devices that have been plugged in and the controller, which can improve communication efficiency and enhance the user experience. There is no requirement for time here, and all times belong to the schedule switching logic. The platform schedule only schedules one cycle; the actual vehicle schedule schedules no less than 20 cycles, and the actual number of cycles is automatically adjusted according to the number of IDs in the actual vehicle schedule to meet the requirement of fast response of functions when the user operates the device.

[0074] The solution of this embodiment provides a device management method on the LIN bus. After a pluggable device based on LIN bus communication in a vehicle is connected to the LIN physical interface, it can be discovered and recognized by the vehicle control system, and the communication time and content can be dynamically adjusted according to the number of specific devices. After the device is connected and interacts with the user for a series of operations, the relevant control of the vehicle is completed. In traditional vehicles, in order to ensure the user experience, the number of nodes on a single LIN bus of the pre-installed ECU based on the LIN bus usually does not exceed a certain number. And pluggable devices have the characteristics of flexibility in plugging and unplugging, and a large number of types. When these two requirements are combined, in the traditional solution, when multiple devices are defined on a single LIN bus but not all the defined devices are connected, the main node calling the empty device node will have the problem of occupying communication time; or when multiple LIN buses are developed in a vehicle to connect pluggable devices, but when no device is connected, it will occupy the vehicle bus resources. This solution meets the requirement of real-time device discovery and has a targeted improvement in dynamically adjusting the communication time. During the dynamic adjustment process, the LIN resources of the whole vehicle are also saved; the advantage of real-time device discovery is that the user does not need to interact with the plugged and unplugged devices according to the device addition scheme, which reflects the intelligence and automation of the vehicle, saves resources, meets safety and performance requirements, and also increases the user experience of directly using the device after plugging it in.

[0075] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence, or the part that makes a contribution to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions for causing a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the present invention.

[0076] Embodiment 2 In this embodiment, a device management device on the LIN bus is also provided. This device is used to implement the above embodiments and preferred implementation manners, and those that have been described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that can achieve a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.

[0077] Figure 8 is a structural block diagram of a device management device on the LIN bus according to an embodiment of the present invention, as Figure 8As shown, it is applied to the controller of the master node on the LIN bus. The device includes: A first reading module 81, configured to read a first scheduling table locally stored in the controller of the vehicle's LIN bus according to a first scheduling period, where the first scheduling table is used to store the mapping relationship between the device identifiers of all pluggable devices and the LIN communication message identifiers; A first sending module 82, configured to sequentially send a first scheduling request to all pluggable devices on the LIN bus according to the first scheduling table, where the first scheduling request carries the LIN communication message identifier of the pluggable device in the first scheduling table; A first monitoring module 83, configured to monitor a reply message returned by a first device based on the first scheduling request; A first determining module 84, configured to determine that the first device accesses the LIN bus according to the reply message.

[0078] Optionally, the first determining module includes: a parsing unit, configured to parse the padding data and the first message identifier in the reply message; a judging unit, configured to judge whether the padding data is empty; a searching unit, configured to, if the padding data is not empty, search for a first device identifier matching the first message identifier in the first scheduling table; and a determining unit, configured to determine that the corresponding first device has accessed the LIN bus based on the first device identifier.

[0079] Optionally, the device further includes: a searching module, configured to, after the first determining module determines that the first device accesses the LIN bus according to the reply message, search for matching first LIN attribute information based on the first device identifier of the first device; and a first updating module, configured to update the first message identifier and the first LIN attribute information to a second scheduling table locally stored in the controller, where the second scheduling table is used to store the mapping relationship between the LIN communication message identifiers and the LIN attribute information of all currently plugged-in devices on the vehicle.

[0080] Optionally, the first updating module includes: a judging unit, configured to judge whether the first message identifier exists in the second scheduling table; and a storing unit, configured to, if the first message identifier does not exist in the second scheduling table, associate and store the first message identifier and the first LIN attribute information in the second scheduling table.

[0081] Optionally, the device further includes: a second reading module, configured to read a second scheduling table locally stored in the controller according to a second scheduling period, where the second scheduling table is used to store a mapping relationship between LIN communication message identifiers and LIN attribute information of all currently plugged-in devices on the vehicle; a second sending module, configured to sequentially send second scheduling requests to all the plugged-in devices on the LIN bus according to the second scheduling table, where the second scheduling requests carry the LIN communication message identifiers of the plugged-in devices in the second scheduling table; a second monitoring module, configured to monitor a message response status of a second device for the second scheduling request; and a second determining module, configured to determine that the second device is in an offline state on the LIN bus according to the message response status.

[0082] Optionally, the second determining module includes: a searching unit, configured to search for a second device to which a second message identifier belongs according to the first scheduling table if the message response status is a message loss status; a querying unit, configured to query historical message response statuses of the second device in several historical scheduling periods of the second scheduling table; and a determining unit, configured to confirm that the second device is in an offline state on the LIN bus according to the historical message response status.

[0083] Optionally, the determining unit includes: a judging subunit, configured to judge whether all the historical message response statuses are message loss statuses; and a first determining subunit, configured to determine that the second device is in an offline state on the LIN bus and update the second scheduling table if all the historical message response statuses are message loss statuses.

[0084] Optionally, the determining unit further includes: a second determining subunit, configured to determine that the second device is in a fault state if the historical message response statuses are not all message loss statuses after the judging subunit judges whether all the historical message response statuses are message loss statuses.

[0085] Optionally, the device further includes: a receiving module, configured to receive a scheduling table update request from the cloud before the first reading module reads a first scheduling table locally stored in a controller of the LIN bus of the vehicle according to a first scheduling period, where the scheduling table update request carries a first scheduling table of the latest version; and a second updating module, configured to locally update the first scheduling table based on the scheduling table update request.

[0086] Optionally, the receiving module includes: a reading unit configured to read the first version information of the first scheduling table stored locally and obtain the second version information of the latest first scheduling table on the cloud; a determining unit configured to determine whether the first version information is the same as the second version information; and a receiving unit configured to receive a scheduling table update request from the cloud if the first version information is different from the second version information.

[0087] This embodiment also provides a device management system on a LIN bus, including a master node, a plurality of slave nodes, and a cloud. The plurality of slave nodes are connected to the LIN bus, and the master node is communicatively connected to the cloud. Among them, the master node includes the device described in the above embodiment; the slave node includes a pluggable LIN interface for accessing a pluggable device and responding to a scheduling request from the master node; and the cloud is configured to manage the first scheduling table of the master node.

[0088] It should be noted that the above-mentioned various modules can be implemented by software or hardware. For the latter, it can be achieved in the following ways, but not limited thereto: the above-mentioned modules are all located in the same processor; or, the above-mentioned various modules are respectively located in different processors in any combination form.

[0089] Embodiment 3 The embodiment of the present invention also provides a storage medium, in which a computer program is stored. Wherein, the computer program is configured to execute the steps in any one of the above method embodiments when running.

[0090] Optionally, in this embodiment, the above storage medium can be configured to store a computer program for executing the following steps: S1, reading the first scheduling table stored locally in the controller of the vehicle's LIN bus according to a first scheduling period, where the first scheduling table is used to store the mapping relationship between the device identifiers of all pluggable devices and the LIN communication message identifiers; S2, sequentially sending a first scheduling request to all pluggable devices on the LIN bus according to the first scheduling table, where the first scheduling request carries the LIN communication message identifier of the pluggable device in the first scheduling table; S3, monitoring a reply message returned by the first device based on the first scheduling request; S4, determining that the first device is connected to the LIN bus according to the reply message.

[0091] Optionally, in this embodiment, the above storage medium may include, but is not limited to: various media such as USB flash drives, read-only memories (ROMs), random access memories (RAMs), external hard drives, magnetic disks, or optical discs that can store computer programs.

[0092] An embodiment of the present invention further provides an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0093] Optionally, the above electronic device may further include a transmission device and input / output devices. Among them, the transmission device is connected to the above processor, and the input / output devices are connected to the above processor.

[0094] Optionally, in this embodiment, the above processor may be configured to execute the following steps through a computer program: S1, read a first scheduling table locally stored in a controller of the LIN bus of the vehicle according to a first scheduling period, where the first scheduling table is used to store a mapping relationship between device identifiers of all pluggable devices and LIN communication message identifiers; S2, sequentially send a first scheduling request to all pluggable devices on the LIN bus according to the first scheduling table, where the first scheduling request carries the LIN communication message identifier of the pluggable device in the first scheduling table; S3, monitor a reply message returned by a first device based on the first scheduling request; S4, determine that the first device accesses the LIN bus according to the reply message.

[0095] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiment and optional implementation manners, and details are not described herein again.

[0096] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0097] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the essence of the above technical solution, or the part that contributes to the relevant technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0098] It should be understood that the terms used herein are for the purpose of describing specific example embodiments only and are not intended to be limiting. Unless the context clearly indicates otherwise, as used herein, the singular forms "a", "an", and "the" may also include the plural forms. The terms "comprising", "including", "containing", and "having" are inclusive and thus specify the presence of the stated features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or their combinations. The method steps, processes, and operations described herein are not to be construed as necessarily requiring them to be performed in the particular order described or illustrated, unless the order of performance is explicitly stated. It should also be understood that additional or alternative steps may be used.

[0099] The above are only specific embodiments of the present invention, enabling those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to these embodiments shown herein, but rather will be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A device management method on a LIN bus, characterized in that Applied to the controller of the master node on the LIN bus, including: Read the first scheduling table stored locally in the controller of the vehicle's LIN bus according to the first scheduling period, where the first scheduling table is used to store the mapping relationship between the device identifiers of all pluggable devices and the LIN communication message identifiers; Send a first scheduling request to all pluggable devices on the LIN bus in sequence according to the first scheduling table, where the first scheduling request carries the LIN communication message identifier of the pluggable device in the first scheduling table; Monitor the reply message returned by the first device based on the first scheduling request; Determine that the first device accesses the LIN bus according to the reply message.

2. The method according to claim 1, wherein Determining that the first device accesses the LIN bus according to the reply message includes: Parse the padding data and the first message identifier in the reply message; Judge whether the padding data is empty; If the padding data is not empty, look up the first device identifier that matches the first message identifier in the first scheduling table; Determine that the corresponding first device has accessed the LIN bus based on the first device identifier.

3. The method according to claim 1, wherein After determining that the first device accesses the LIN bus according to the reply message, the method further includes: Look up the matching first LIN attribute information based on the first device identifier of the first device; Update the first message identifier and the first LIN attribute information to the second scheduling table stored locally in the controller, where the second scheduling table is used to store the mapping relationship between the LIN communication message identifiers and the LIN attribute information of all currently plugged-in devices on the vehicle.

4. The method according to claim 3, characterized in that, Updating the device identifier to the locally stored second scheduling table includes: Judge whether the first message identifier exists in the second scheduling table; If the first message identifier does not exist in the second scheduling table, associate and store the first message identifier and the first LIN attribute information in the second scheduling table.

5. The method according to claim 1, characterized in that The method further includes: Read the second scheduling table stored locally in the controller according to the second scheduling period, where the second scheduling table is used to store the mapping relationship between the LIN communication message identifiers and the LIN attribute information of all currently plugged-in devices on the vehicle; Send a second scheduling request to all pluggable devices on the LIN bus in sequence according to the second scheduling table, where the second scheduling request carries the LIN communication message identifier of the pluggable device in the second scheduling table; Monitor the message response status of the second device for the second scheduling request; Determine that the second device is in an offline state on the LIN bus according to the message response status.

6. The method according to claim 5, characterized in that, Determining that the second device is in an offline state on the LIN bus according to the message response status includes: If the message response status is a message loss status, look up the second device to which the second message identifier belongs according to the first scheduling table; Query the historical message response status of the second device in several historical scheduling periods of the second scheduling table; Confirm that the second device is in an offline state on the LIN bus according to the historical message response status.

7. The method according to claim 6, wherein Confirming that the second device is in an offline state on the LIN bus according to the historical message response status includes: Judging whether the historical message response statuses are all message loss statuses; If the historical message response statuses are all message loss statuses, determining that the second device is in an offline state on the LIN bus and updating the second scheduling table.

8. The method according to claim 7, wherein After judging whether the historical message response statuses are all message loss statuses, the method further includes: If the historical message response statuses are not all message loss statuses, determining that the second device is in a fault state.

9. The method according to claim 1, wherein Before reading the first scheduling table locally stored in the controller of the vehicle's LIN bus according to the first scheduling period, the method further includes: Receiving a scheduling table update request from the cloud, where the scheduling table update request carries the first scheduling table of the latest version; Updating the first scheduling table locally based on the scheduling table update request.

10. The method according to claim 9, wherein Receiving a scheduling table update request from the cloud includes: Reading the first version information of the first scheduling table locally stored and obtaining the second version information of the latest first scheduling table on the cloud; Judging whether the first version information is the same as the second version information; If the first version information is not the same as the second version information, receiving the scheduling table update request from the cloud.

11. A device management apparatus on a LIN bus, characterized in that Applied to the controller of the main node on the LIN bus, it includes: A first reading module, configured to read the first scheduling table locally stored in the controller of the vehicle's LIN bus according to the first scheduling period, where the first scheduling table is used to store the mapping relationship between the device identifiers of all pluggable devices and the LIN communication message identifiers; A first sending module, configured to sequentially send a first scheduling request to all pluggable devices on the LIN bus according to the first scheduling table, where the first scheduling request carries the LIN communication message identifier of the pluggable device in the first scheduling table; A first monitoring module, configured to monitor the reply message returned by the first device based on the first scheduling request; A first determining module, configured to determine that the first device accesses the LIN bus according to the reply message.

12. A device management system on a LIN bus, characterized in that Including a main node and several slave nodes, a cloud, the several slave nodes access the LIN bus, and the main node is communicatively connected to the cloud, where The main node includes the device as described in claim 11; The slave node includes a pluggable LIN interface for accessing a pluggable device and responding to the scheduling request of the main node; The cloud is used to manage the first scheduling table of the main node.

13. A storage medium, characterized in that, A computer program is stored in the storage medium, where the computer program is set to execute the method described in any one of claims 1 to 10 when running.

14. An electronic device, comprising a memory and a processor, characterized in that, A computer program is stored in the memory, and the processor is set to run the computer program to execute the method described in any one of claims 1 to 10.

Images