Vehicle-mounted network communication method and system

Abstract

The embodiment of the invention discloses a vehicle-mounted network communication method and system. The method can be applied to a dynamic host configuration protocol service, the dynamic host configuration protocol service is deployed on a central device in a vehicle-mounted network, and the method can comprise the following steps: allocating an internet protocol address to a vehicle-mounted device initiating a dynamic host configuration protocol request in the vehicle-mounted network, the currently distributed internet protocol address is different from each internet protocol address which is used in the vehicle-mounted network before the current distribution; aiming at a network equipment list in which each Internet protocol address of the application is stored, adding the currently distributed Internet protocol address into the network equipment list, and updating; and in response to the list pushing event, pushing the network equipment list to the vehicle-mounted equipment in the vehicle-mounted network, so that the vehicle-mounted equipment receiving the network equipment list obtains the Internet protocol address. According to the technical scheme provided by the embodiment of the invention, the maintainability and the flexibility of the vehicle-mounted network can be improved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communication technology, and in particular to a vehicle-mounted network communication method and system. Background Technology

[0002] As automotive electronic and electrical architectures have evolved from traditional distributed electronic control units (ECUs) to domain-centralized and even vehicle-centralized architectures, modern vehicles have gradually developed multiple functional domains, such as the intelligent cockpit domain, intelligent driving domain, powertrain control domain, and body control domain. Based on this, high-speed data exchange occurs within each functional domain and between functional domains via networks, thus forming a complex in-vehicle local area network (hereinafter referred to as the in-vehicle network).

[0003] Based on this, for in-vehicle devices in the vehicle network, the current main approach is to manually configure the in-vehicle device to assign an Internet Protocol (IP) address, so that the in-vehicle device can obtain the IP address assigned to it, thereby enabling in-vehicle network communication.

[0004] However, the above solutions result in poor maintainability and flexibility of the in-vehicle network, which urgently needs to be addressed. Summary of the Invention

[0005] This invention provides a vehicle network communication method and system that solves the problems of poor maintainability and flexibility of vehicle networks.

[0006] According to one aspect of the present invention, a vehicle network communication method is provided, the method being applied to a Dynamic Host Configuration Protocol (DMP) service, the DMP service being deployed on a central device within the vehicle network, the method comprising:

[0007] In response to a Dynamic Host Configuration Protocol (DHCP) request, an Internet Protocol (IP) address is assigned to the vehicular device that initiated the DHCP request within the vehicular network. The IP address assigned at this time is different from the IP addresses used within the vehicular network before this assignment.

[0008] For the list of network devices that store the Internet Protocol addresses of the applications, add the currently assigned Internet Protocol addresses to the list of network devices to update the list of network devices;

[0009] In response to the list push event, the list of network devices is pushed to the in-vehicle devices within the vehicle network so that the in-vehicle devices that receive the list of network devices can obtain Internet Protocol addresses.

[0010] According to another aspect of the present invention, a vehicle network communication method is provided. This method can be applied to a server application deployed on a vehicle-mounted device within the vehicle network. The method may include:

[0011] The Dynamic Host Configuration Protocol (DHCP) request is sent to the central device within the vehicle network, so that the central device allocates an Internet Protocol (IP) address according to the DHCP request and adds the currently allocated IP address to the network device list to update the network device list and push the network device list into the vehicle network. The currently allocated IP address is different from the IP addresses used in the vehicle network before this allocation.

[0012] The system receives a list of network devices via the vehicle network in order to obtain Internet Protocol (IP) addresses from the list of network devices.

[0013] According to another aspect of the present invention, a vehicle network communication method is provided, which can be applied to a client application deployed on a vehicle-mounted device within the vehicle network. The method may include:

[0014] For the target service to be invoked, if a service declaration message matching the target service is detected, the Internet Protocol address corresponding to the service declaration message is obtained.

[0015] The first connection request is initiated based on the obtained Internet Protocol address to establish a connection with the server application that initiated the service announcement message and to make calls.

[0016] The Internet Protocol address of the in-vehicle device where the server application resides within the in-vehicle network is allocated by the central device within the in-vehicle network.

[0017] The Internet Protocol address assigned by the central device to the in-vehicle device where the server application resides is different from the Internet Protocol addresses of the applications within the in-vehicle network before this assignment.

[0018] According to another aspect of the present invention, a vehicle-to-everything (V2X) network communication system is provided, which may include: a Dynamic Host Configuration Protocol (DMP) service on a central device deployed within the V2X network and a server application on the V2X device deployed within the V2X network; wherein the DMP service includes an address allocation module, a list management module, and a list synchronization module, and the server application includes an address acquisition module; wherein,

[0019] The address allocation module is used to respond to a Dynamic Host Configuration Protocol (DHCP) request and allocate an Internet Protocol (IP) address to the vehicle device in the vehicle network that initiates the DHCP request. The IP address currently allocated is different from the IP addresses used in the vehicle network before this allocation.

[0020] The list management module is used to add the currently assigned Internet Protocol addresses to the list of network devices that store the Internet Protocol addresses of applications, so as to update the list of network devices.

[0021] The list synchronization module is used to push the list of network devices to the in-vehicle devices in the vehicle network in response to the list push event;

[0022] The address acquisition module is used to obtain Internet Protocol addresses from the received list of network devices.

[0023] According to another aspect of the present invention, a vehicle-mounted device is provided, which may include:

[0024] At least one processor; and

[0025] A memory that is communicatively connected to at least one processor; wherein,

[0026] The memory stores a computer program that can be executed by at least one processor, such that when the at least one processor executes the program, it implements the vehicle network communication method provided in any embodiment of the present invention.

[0027] According to another aspect of the present invention, a computer-readable storage medium is provided having computer instructions stored thereon for causing a processor to execute and implement the vehicle network communication method provided in any embodiment of the present invention.

[0028] According to another aspect of the present invention, a computer program product is provided, on which a computer program is stored, which, when executed by a processor, implements the vehicle network communication method provided in any embodiment of the present invention.

[0029] The technical solution of this invention, through a Dynamic Host Configuration Protocol (DHCP) service deployed on a central device within a vehicle network, responds to DHCP requests by allocating Internet Protocol (IP) addresses to vehicle devices that initiate DHCP requests within the vehicle network. The currently allocated IP address differs from the IP addresses used in the vehicle network prior to this allocation. For a list of network devices storing the applied IP addresses, the currently allocated IP address is added to the list to update the list. In response to a list push event, the list is pushed to the vehicle devices within the vehicle network, enabling the receiving vehicle devices to obtain IP addresses. The above technical solution selects a central device from the various vehicle-mounted devices in the vehicle network and deploys a Dynamic Host Configuration Protocol (DHCP) service on the central device. This DHCP service then dynamically assigns Internet Protocol (IP) addresses to each vehicle-mounted device in the vehicle network and dynamically maintains a network device list. The network device list is then synchronized to the vehicle-mounted devices in the vehicle network so that the devices can obtain IP addresses from the list. This achieves vehicle network communication with zero configuration, improving the maintainability and flexibility of the vehicle network.

[0030] It should be understood that the description in this section is not intended to identify key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0032] Figure 1 This is a flowchart of a vehicle network communication method provided according to an embodiment of the present invention;

[0033] Figure 2 This is a flowchart of another vehicle network communication method provided according to an embodiment of the present invention;

[0034] Figure 3 This is a flowchart of another vehicle network communication method provided according to an embodiment of the present invention;

[0035] Figure 4 This is a flowchart illustrating a zero-configuration vehicular network communication example based on service discovery, as provided in another vehicular network communication method according to an embodiment of the present invention.

[0036] Figure 5 This is a structural block diagram of an in-vehicle network communication system according to an embodiment of the present invention;

[0037] Figure 6 This is a schematic diagram of the structure of an in-vehicle device that implements the in-vehicle network communication method of this invention. Detailed Implementation

[0038] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0039] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. The same applies to "target," "original," etc., and will not be repeated here. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0040] It should be noted that the collection, gathering, updating, analysis, processing, use, transmission, and storage of user personal information involved in the technical solution of this invention all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to maintain user personal information security and network security.

[0041] Before introducing the embodiments of the present invention, the application scenarios of the embodiments of the present invention will be described by way of example. For example, multiple vehicle-mounted devices are connected within the vehicle network. These devices can be instrument panel controllers, smart cockpit domain controllers, passenger entertainment screens, rear-seat entertainment screens, smart vehicle terminals (Telematics Box, T-Box), or central gateways, etc., depending on the actual situation, and are not specifically limited here. In the embodiments of the present invention, one vehicle-mounted device (e.g., a central gateway) can be selected from the multiple vehicle-mounted devices as the network core to dynamically allocate IP addresses. For ease of distinction, this vehicle-mounted device is referred to as the central device. Furthermore, for the vehicle-mounted devices in the vehicle network other than the central device, one or more applications can be deployed on each device. These applications can be considered as server-side applications providing services or client-side applications calling services, depending on the usage scenario of the application. For example, taking the vehicle location and navigation coordination application on the smart cockpit domain controller as an example, as a server-side application, it can provide refined navigation command services, while as a client-side application, it can call route planning services.

[0042] Figure 1 This is a flowchart illustrating a vehicle network communication method provided in an embodiment of the present invention. This embodiment is applicable to situations where IP addresses are assigned to vehicle-mounted devices within a vehicle network, and particularly to situations where IP addresses are dynamically assigned to vehicle-mounted devices within a vehicle network. This method can be executed by the vehicle network communication device provided in this embodiment of the present invention. This device can be implemented in software and / or hardware. The device can be configured with a Dynamic Host Configuration Protocol (DHCP) service, which can be deployed on a central device. This central device can be one of the vehicle-mounted devices within the vehicle network that possesses both a fixed IP address and DHCP service functionality.

[0043] See Figure 1 The method of this invention specifically includes the following steps:

[0044] S110. In response to a Dynamic Host Configuration Protocol (DHCP) request, an Internet Protocol (IP) address is assigned to the vehicular device that initiated the DHCP request within the vehicular network, wherein the currently assigned IP address is different from the IP addresses used within the vehicular network before this assignment.

[0045] In this context, the in-vehicle network can be understood as a complex local area communication network consisting of multiple in-vehicle devices connected through in-vehicle buses or Ethernet. A Dynamic Host Configuration Protocol (DHCP) request can be understood as a request sent by an in-vehicle device (excluding the central device) to the central device to obtain an IP address when starting up or accessing the in-vehicle network. The central device's IP address is pre-fixed.

[0046] In this embodiment of the invention, when a new vehicle-mounted device powers on and connects to the vehicle network, it can act as a DHCP client and initiate a DHCP request to the central device, specifically the DHCP service deployed on the central device. Upon receiving the DHCP request, the central device can select an unused IP address from a pre-configured IP address pool, choosing one that is currently unused by any of the online vehicle-mounted devices within the vehicle network, and then assign that IP address to the vehicle-mounted device that initiated the DHCP request. For example, the central device can query the status information of all assigned and online vehicle-mounted device IP addresses in the network device list to ensure that the selected IP address is different from the IP addresses of applications within the vehicle network, thereby avoiding IP address conflicts. The IP address of the application can be understood as an IP address that has been assigned by the central device before this allocation, and more specifically, an IP address that has been assigned by the central device and for which the corresponding vehicle-mounted device is still online.

[0047] In this step, unique IP addresses are dynamically assigned to in-vehicle devices by the central device, especially the DHCP service deployed on the central device. This solves the problem of poor maintainability and flexibility of the in-vehicle network caused by relying on manual configuration schemes to assign IP addresses, and enables plug-and-play functionality for in-vehicle devices.

[0048] S120. For the list of network devices that store the Internet Protocol addresses of the applications, add the currently assigned Internet Protocol addresses to the list of network devices to update the list of network devices.

[0049] The network device list can be understood as a global and dynamically updated list actively maintained internally by the central device. It stores all assigned IP addresses, especially those of assigned and corresponding online vehicle-mounted devices. In addition, it can store metadata such as the unique identifier of each vehicle-mounted device, device type, and online time. This can be configured according to actual needs and is not specifically limited here. In other words, the network device list can be considered a global view or roster reflecting the network topology, especially the real-time network topology.

[0050] After assigning an IP address to the vehicle-mounted device that initiated the DHCP request, the central device can create a record for that vehicle-mounted device in its maintained network device list to update the network device list, thereby ensuring that the record is included in the network device list of subsequent applications. In this embodiment of the invention, the record contains at least the IP address assigned to the vehicle-mounted device, and may also contain at least one of the unique identifier, device type, and online time mentioned in the above examples. This can be set according to actual needs and is not specifically limited here.

[0051] Optionally, the central device can also periodically scan the vehicle network to detect if any in-vehicle devices are offline (e.g., T-Boxes are in sleep mode). Once detected, the record corresponding to that in-vehicle device can be removed from the network device list. Through continuous addition and deletion operations, the central device ensures that the network device list always accurately reflects the IP addresses of all currently online and applied devices.

[0052] In this step, the central device gains a precise understanding of the network topology of the vehicle network by dynamically maintaining this real-time updated list of network devices. This makes the central device not only an IP address allocator, but also the perception hub of the vehicle network, thereby helping to improve the level of intelligence in vehicle network management.

[0053] S130. In response to the list push event, push the network device list to the vehicle devices in the vehicle network so that the vehicle devices that receive the network device list can obtain Internet Protocol addresses.

[0054] The list push event can be understood as an event instructing the central device to push a list of network devices to other in-vehicle devices in the vehicular network. Based on this, and considering the application scenarios that may be involved in the embodiments of this invention, the list push event may optionally be triggered in at least one of the following situations: the current time is the target time, which is determined according to a preset time interval and the trigger time of the last time the list push event was triggered, i.e., periodic timed triggering; it is triggered when the network topology changes, such as detecting a new in-vehicle device added to the vehicular network and / or an in-vehicle device in the vehicular network going offline; it is triggered when a list query request for querying the network device list is initiated by an in-vehicle device; of course, it can also be triggered in other situations, which can be set according to actual needs and are not specifically limited here.

[0055] In response to the list push event, the network device list is pushed to the in-vehicle devices within the vehicular network. This can be achieved using one-to-many network communication methods such as multicast or broadcast. Optionally, the aforementioned in-vehicle devices can be understood as all in-vehicle devices within the vehicular network except for the central device, including those that have already obtained IP addresses and those that have just come online and are currently obtaining IP addresses; it can also be understood as any in-vehicle device that initiates a list query request; etc., depending on the specific circumstances, and no specific limitation is made here. Furthermore, the in-vehicle devices receiving the network device list can obtain IP addresses from it and then conduct in-vehicle network communication based on these IP addresses.

[0056] In this step, by pushing the list of network devices to the vehicle-mounted devices, when a vehicle-mounted device needs to communicate with another vehicle-mounted device, it does not need to pre-configure the other party's IP address or perform time-consuming network discovery. It can directly find the other party's IP address from the locally cached list of network devices, thereby greatly simplifying the process of application layer service discovery and invocation.

[0057] The technical solution of this invention, through a Dynamic Host Configuration Protocol (DHCP) service deployed on a central device within a vehicle network, responds to DHCP requests by allocating Internet Protocol (IP) addresses to vehicle devices that initiate DHCP requests within the vehicle network. The currently allocated IP address differs from the IP addresses used in the vehicle network prior to this allocation. For a list of network devices storing the applied IP addresses, the currently allocated IP address is added to the list to update the list. In response to a list push event, the list is pushed to the vehicle devices within the vehicle network, enabling the receiving vehicle devices to obtain IP addresses. The above technical solution selects a central device from the various vehicle-mounted devices in the vehicle network and deploys a Dynamic Host Configuration Protocol (DHCP) service on the central device. This DHCP service then dynamically assigns Internet Protocol (IP) addresses to each vehicle-mounted device in the vehicle network and dynamically maintains a network device list. The network device list is then synchronized to the vehicle-mounted devices in the vehicle network so that the devices can obtain IP addresses from the list. This achieves vehicle network communication with zero configuration, improving the maintainability and flexibility of the vehicle network.

[0058] Figure 2This is a flowchart of another vehicular network communication method provided by an embodiment of the present invention. This embodiment is applicable to the situation of allocating IP addresses to vehicular devices within a vehicular network, and is particularly applicable to the situation of dynamically allocating IP addresses to vehicular devices within a vehicular network. This method can be executed by the vehicular network communication device provided by this embodiment of the present invention. This device can be implemented by software and / or hardware, and can be configured on a server application, which can be deployed on vehicular devices within the vehicular network. The explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0059] See Figure 2 The method in this embodiment may specifically include the following steps:

[0060] S210. A Dynamic Host Configuration Protocol (DHCP) request is sent to a central device within the vehicle network, so that the central device allocates an Internet Protocol (IP) address according to the DHCP request, adds the currently allocated IP address to the network device list to update the network device list, and pushes the network device list into the vehicle network. The currently allocated IP address is different from the IP addresses used in the vehicle network before this allocation.

[0061] S220. Receive a list of network devices via the vehicle network to obtain Internet Protocol addresses from the list of network devices.

[0062] The technical solution of this invention involves a server application deployed on an in-vehicle device within the in-vehicle network initiating a Dynamic Host Configuration Protocol (DHCP) request to a central device. The central device then returns a list of network devices, from which the Internet Protocol (IP) addresses of each in-vehicle device can be obtained. This enables in-vehicle network communication with zero configuration, thereby improving the maintainability and flexibility of the in-vehicle network.

[0063] An optional technical solution includes a network device list that stores the addresses of various Internet Protocols used in the vehicular network prior to this allocation. The aforementioned vehicular network communication method further includes:

[0064] For Internet Protocol (IP) addresses obtained from the list of network devices, a service advertisement message is initiated based on the IP address to represent the services that can be provided.

[0065] In this embodiment, it is assumed that the technical solution is executed by a server application deployed on an in-vehicle device X within the vehicular network. This server application retrieves IP addresses from the network device list, specifically IP addresses other than those assigned to in-vehicle device X. Based on these IP addresses, it initiates service announcement messages. These service announcement messages can be understood as network data packets generated by the server application to announce its service capabilities (i.e., the services it provides) to other in-vehicle devices within the vehicular network. The in-vehicle devices corresponding to these IP addresses can all be considered potential service consumers.

[0066] For example, the server application can initiate service announcement messages in two modes: one is targeted announcement, which involves iterating through each obtained IP address and then sending a unicast service announcement message to it; the other is efficient multicast, which involves sending an announcement message to a predefined multicast address, and the vehicle device corresponding to each obtained IP address subscribes to the multicast address.

[0067] For another example, considering that multiple server applications may be deployed on the vehicle device X, in order to distinguish the service announcement messages initiated by different server applications, the service announcement message can be initiated based on the IP address and the port identifier of its corresponding service port, so that the vehicle device receiving the service announcement message can confirm which server application on the vehicle device X is providing this service.

[0068] In the above technical solution, the server application initiates a service announcement message based on the IP addresses of the received and trusted list of network devices, thereby announcing the services it can provide, thus ensuring the efficiency and accuracy of service announcement.

[0069] Figure 3 This is a flowchart of another vehicular network communication method provided by an embodiment of the present invention. This embodiment is applicable to the situation of allocating IP addresses to vehicular devices within a vehicular network, and is particularly applicable to the situation of dynamically allocating IP addresses to vehicular devices within a vehicular network. This method can be executed by the vehicular network communication device provided by the embodiment of the present invention. This device can be implemented by software and / or hardware, and can be configured on a client application, which can be deployed on vehicular devices within the vehicular network. The explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0070] See Figure 3 The method in this embodiment may specifically include the following steps:

[0071] S310. For the target service to be invoked, if a service declaration message matching the target service is detected, obtain the Internet Protocol address corresponding to the service declaration message.

[0072] In this embodiment, assuming that the technical solution is executed by a client application on an in-vehicle device Y deployed within the in-vehicle network, the target service can be understood as a service currently needed by the client application and provided by a server application deployed on another in-vehicle device besides the in-vehicle device Y. For example, when the vehicle location and navigation coordination application on the smart cockpit domain controller in the above example acts as a client application, its target service may be a route planning service provided by a server application on another in-vehicle device within the in-vehicle network.

[0073] Through this client application, the system continuously monitors service announcement messages propagating within the vehicle network. When a service announcement message matching the target service is detected, i.e., the service announced by the service announcement message is the target service, the system obtains the IP address corresponding to the service announcement message. For example, the IP address can be obtained from the service announcement message. This IP address is the IP address of the vehicle device Z where the server application that initiated the service announcement message is located.

[0074] S320. Initiate a first connection request based on the obtained Internet Protocol address to establish a connection with the server application that initiated the service advertisement message and make calls;

[0075] The Internet Protocol address of the in-vehicle device where the server application resides within the in-vehicle network is allocated by the central device within the in-vehicle network.

[0076] The Internet Protocol address assigned by the central device to the in-vehicle device where the server application resides is different from the Internet Protocol addresses of the applications within the in-vehicle network prior to this assignment.

[0077] Specifically, the client application initiates a first connection request based on the obtained IP address, thereby establishing a network connection with the vehicle-mounted device Z. More specifically, it can establish a network connection with the server application deployed on the vehicle-mounted device Z, and can call the server application after the network connection is successful.

[0078] The technical solution of this invention, through a client application deployed on an in-vehicle device within an in-vehicle network, can obtain an IP address and service content based on a received service announcement message without needing to pre-configure any IP address, thereby achieving the effect of dynamically discovering and connecting to server applications.

[0079] An optional technical solution, the above-mentioned vehicle-mounted equipment network communication method further includes:

[0080] The receiving center device sends a list of network devices, which stores the Internet Protocol addresses assigned by the center device to each in-vehicle device in the in-vehicle network.

[0081] For the Internet Protocol address obtained from the list of network devices, initiate a service query request based on the Internet Protocol address to query the services that the server application corresponding to the Internet Protocol address can provide;

[0082] If the queried service is the target service, a second connection request is initiated based on the Internet Protocol address to establish a connection with the server application and make the call.

[0083] In this context, a service query request can be understood as a request initiated by a client application to a specific vehicle device in the vehicle network (i.e., corresponding to the obtained IP address) to query the services provided by the server application deployed on it. This is a way for client applications to actively probe for services.

[0084] Based on this, the server application can return the service corresponding to the service query request (i.e., the service it can provide). If the service is the target service, a second connection request can be initiated based on the IP address to establish a connection with the server application and make a call.

[0085] The above technical solution can be considered a supplementary technical solution to the service discovery based on service declaration messages. By combining a network device list with an active probing mechanism, it can more flexibly and reliably discover and connect to the required services.

[0086] Building upon this, to better understand the various technical solutions described above, a service discovery-based zero-configuration vehicular network communication example will be provided below for illustrative purposes. For an example, see [link to example]. Figure 4 The specific implementation process is as follows:

[0087] Step 1: In-vehicle network initialization and IP address allocation.

[0088] After the vehicle network is powered on, a pre-designated central node is assigned a fixed IP address. This central node starts the DHCP service, acting as the DHCP server for the entire vehicle network. All other vehicle devices in the network, upon startup, send DHCP requests (i.e., DHCP discovery requests as shown in the diagram) to this central node in client mode and automatically obtain a dynamically assigned IP address.

[0089] Step 2: Vehicle network topology awareness and network device list maintenance.

[0090] The central node maintains a dynamic list of network devices internally. This list not only records the IP address of each assigned vehicle-mounted device, but also, extensibly, metadata such as unique identifiers, device types, and online times. The central node dynamically updates the network device list by listening for and responding to DHCP requests and periodically performing IP address scans to ensure consistency with the actual network topology.

[0091] Step 3: Active synchronization of the network device list.

[0092] The central node proactively pushes the updated list of network devices to all online vehicle devices in the vehicular network periodically or when it detects a change in network topology via multicast or broadcast. In this example, each vehicle device can also proactively query the central node for the list of network devices after startup.

[0093] Step 4: Collaborative announcement of the server application.

[0094] Each in-vehicle device within the vehicular network may run one or more server-side applications. After obtaining the latest list of network devices, these server-side applications can periodically send service announcement messages to all IP addresses (or via multicast addresses) in that list. These service announcement messages contain key information such as the service identifier, service interface, protocol version, and service port.

[0095] Step 5: Dynamic discovery and connection of client applications.

[0096] When a client application needs to invoke a service (i.e., the target service mentioned above), it first listens for service advertisement messages in the vehicular network. Once it detects a service advertisement message that matches its needs (i.e., the target service), the client application can directly initiate a connection request based on the IP address (from a list of trusted network devices) and service port in the service advertisement message. Alternatively, the client application can proactively send service query requests to the IP addresses in the known list of network devices during startup to discover available server applications.

[0097] The above example automates the entire process of vehicular network, from IP address allocation to service discovery. Once connected to the vehicular network, in-vehicle devices can obtain communication capabilities and service context without any configuration, achieving true zero-configuration and plug-and-play functionality, greatly simplifying the deployment, maintenance, and upgrade processes of vehicular networks.

[0098] Figure 5 This is a structural block diagram of a vehicle-mounted device network communication system provided in an embodiment of the present invention. This embodiment is applicable to situations where IP addresses are assigned to vehicle-mounted devices within a vehicle network, and is particularly suitable for situations where IP addresses are dynamically assigned to vehicle-mounted devices within a vehicle network.

[0099] See Figure 5 The vehicle-mounted device network communication system according to this embodiment of the invention includes: a Dynamic Host Configuration Protocol (DMP) service 40 deployed on a central device within the vehicle network and a server application 41 deployed on the vehicle device within the vehicle network; wherein, the DMP service 40 is configured with an address allocation module 401, a list management module 402, and a list synchronization module 403, and the server application 41 is configured with an address acquisition module 411; wherein,

[0100] Address allocation module 401 is used to allocate Internet Protocol addresses to vehicle devices that initiate Dynamic Host Configuration Protocol requests within the vehicle network in response to Dynamic Host Configuration Protocol requests, wherein the currently allocated Internet Protocol address is different from the Internet Protocol addresses used within the vehicle network before this allocation.

[0101] The list management module 402 is used to add the currently assigned Internet Protocol address to the list of network devices that store the Internet Protocol addresses of the application, so as to update the list of network devices.

[0102] The list synchronization module 403 is used to push the list of network devices to the in-vehicle devices in the vehicle network in response to the list push event;

[0103] Address acquisition module 411 is used to obtain Internet Protocol addresses from a received list of network devices.

[0104] Optionally, the server application 41 is also configured with a service declaration module 412; among which,

[0105] The service announcement module 412 is used to initiate a service announcement message based on the obtained Internet Protocol address to represent the services that can be provided.

[0106] Optionally, if the server application has a corresponding service port, the service announcement module 412 is specifically used to initiate a service announcement message based on the obtained Internet Protocol address and the port identifier of the service port to represent the services that can be provided.

[0107] Optionally, the aforementioned vehicle-mounted equipment communication system may further include: a client application 41 deployed on a vehicle-mounted device within the vehicle network; wherein, the client application 41 is configured with a service discovery module 413; wherein,

[0108] The service discovery module 413 is used to respond to the service declaration message that matches the target service to be called. For the service declaration message that is listened to, the Internet Protocol address corresponding to the service declaration message is obtained, and a first connection request is initiated based on the obtained Internet Protocol address to establish a connection with the server application 41 that initiated the service declaration message and make the call.

[0109] In addition, optionally, the service discovery module 413 is also used for:

[0110] The receiving center device sends a list of network devices, which stores the Internet Protocol addresses assigned by the center device to each in-vehicle device in the in-vehicle network.

[0111] For the Internet Protocol address obtained from the list of network devices, initiate a service query request based on the Internet Protocol address to query the services that the server application corresponding to the Internet Protocol address can provide;

[0112] If the queried service is the target service, a second connection request is initiated based on the Internet Protocol address to establish a connection with the server application and make the call.

[0113] The vehicle network communication system provided in this embodiment of the invention can realize vehicle network communication with zero configuration through the cooperation of various modules, thereby improving the maintainability and flexibility of the vehicle network.

[0114] It is worth noting that in the above embodiments of the vehicle network communication system, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional module are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0115] Figure 6 A schematic diagram of a vehicle-mounted device 10, which can be used to implement embodiments of the present invention, is shown. The vehicle-mounted device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The vehicle-mounted device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0116] like Figure 6As shown, the vehicle-mounted device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer programs stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the vehicle-mounted device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0117] Multiple components in the vehicle-mounted device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, optical disk, etc.; and a communication unit 19, such as a network card, modem, wireless transceiver, etc. The communication unit 19 allows the vehicle-mounted device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0118] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as in-vehicle network communication methods.

[0119] In some embodiments, the vehicle network communication method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the vehicle device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the vehicle network communication method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the vehicle network communication method by any other suitable means (e.g., by means of firmware).

[0120] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-chips or system-on-a-chips (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0121] Computer programs used to implement the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0122] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0123] To provide interaction with the user, the systems and techniques described herein can be implemented in an in-vehicle device having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the in-vehicle device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0124] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0125] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0126] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication unit 19, or installed from storage unit 18, or installed from ROM 12. When the computer program is executed by processor 11, it performs the functions defined in the methods of the embodiments of the present invention.

[0127] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0128] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A vehicle-mounted network communication method, characterized in that, The method, applied to a Dynamic Host Configuration Protocol (DMP) service deployed on a central device within a vehicular network, includes: In response to a Dynamic Host Configuration Protocol (DHCP) request, an Internet Protocol (IP) address is assigned to the vehicular device that initiated the DHCP request within the vehicular network, wherein the currently assigned IP address is different from the IP addresses previously used within the vehicular network. For a list of network devices that store the Internet Protocol addresses of applications, the currently assigned Internet Protocol addresses are added to the list of network devices to update the list of network devices; In response to the list push event, the network device list is pushed to the in-vehicle devices within the vehicle network, so that the in-vehicle devices that receive the network device list can obtain Internet Protocol addresses.

2. The method according to claim 1, characterized in that, The list push event is triggered under at least one of the following conditions: The current time is the target time, which is determined based on a preset time interval and the trigger time of the last time the list push event was triggered; New in-vehicle devices are added to the in-vehicle network; The in-vehicle equipment within the in-vehicle network is offline; and... A list query request for querying the list of network devices was detected.

3. A vehicle-mounted network communication method, characterized in that, Applied to a server-side application deployed on an in-vehicle device within an in-vehicle network, the method includes: A Dynamic Host Configuration Protocol (DHCP) request is sent to a central device within the vehicle network, so that the central device allocates an Internet Protocol (IP) address according to the DHCP request, adds the currently allocated IP address to the network device list to update the network device list, and pushes the network device list into the vehicle network. The currently allocated IP address is different from the IP addresses used in the vehicle network before this allocation. The system receives the list of network devices through the vehicle network to obtain Internet Protocol (IP) addresses from the list of network devices.

4. The method according to claim 3, characterized in that, The network device list also stores various Internet Protocol addresses used in the vehicle network prior to this allocation, and the method further includes: For each Internet Protocol address obtained from the list of network devices, a service announcement message is initiated based on the Internet Protocol address to represent the services that can be provided.

5. The method according to claim 4, characterized in that, The server application corresponds to a service port, and the service announcement message initiated based on the Internet Protocol address includes: Based on the Internet Protocol address and the port identifier of the service port, a service announcement message is initiated.

6. A vehicle-mounted network communication method, characterized in that, Applied to a client application deployed on an in-vehicle device within an in-vehicle network, the method includes: For the target service to be invoked, if a service announcement message matching the target service is detected, the Internet Protocol address corresponding to the service announcement message is obtained. The first connection request is initiated based on the obtained Internet Protocol address to establish a connection with the server application that initiated the service announcement message and to make a call. The Internet Protocol address of the in-vehicle device where the server application resides within the in-vehicle network is allocated by the central device within the in-vehicle network. The Internet Protocol address assigned by the central device to the vehicle-mounted device where the server application resides is different from the Internet Protocol addresses of the applications used in the vehicle network before this assignment.

7. The method according to claim 6, characterized in that, Also includes: The central device receives a list of network devices, wherein the list of network devices stores Internet Protocol addresses assigned by the central device to each vehicle device in the vehicle network. For the Internet Protocol address obtained from the list of network devices, a service query request is initiated based on the Internet Protocol address to query the services that the server application corresponding to the Internet Protocol address can provide. In response to the query finding that the service is the target service, a second connection request is initiated based on the Internet Protocol address to establish a connection with the server application and make a call.

8. A vehicle-mounted network communication system, characterized in that, include: The system includes a Dynamic Host Configuration Protocol (DMP) service deployed on a central device within the vehicular network and a server-side application deployed on the vehicular device within the vehicular network; wherein the DMP service is configured with an address allocation module, a list management module, and a list synchronization module, and the server-side application is configured with an address acquisition module; wherein... The address allocation module is used to allocate an Internet Protocol address to the vehicle device in the vehicle network that initiates the Dynamic Host Configuration Protocol request in response to a Dynamic Host Configuration Protocol request, wherein the currently allocated Internet Protocol address is different from the Internet Protocol addresses used in the vehicle network before this allocation. The list management module is used to add the currently assigned Internet Protocol address to the network device list that stores the Internet Protocol addresses of the applications, so as to update the network device list. The list synchronization module is used to push the network device list to the vehicle devices in the vehicle network in response to the list push event. The address acquisition module is used to obtain Internet Protocol addresses from the received list of network devices.

9. The system according to claim 8, characterized in that, The server-side application is also configured with a service announcement module; among which... The service announcement module is used to initiate a service announcement message based on the obtained Internet Protocol address to represent the services that can be provided.

10. The system according to claim 9, characterized in that, Also includes: A client application deployed on an in-vehicle device within the vehicle network; wherein the client application is configured with a service discovery module; The service discovery module is configured to, in response to a service declaration message matching the target service to be invoked, obtain the Internet Protocol address corresponding to the service declaration message, and initiate a first connection request based on the obtained Internet Protocol address to establish a connection with the server application that initiated the service declaration message and make the invocation.

Images