CN114978875A - Vehicle-mounted node management method and device and storage medium - Google Patents

Vehicle-mounted node management method and device and storage medium Download PDF

Info

Publication number
CN114978875A
CN114978875A CN202110202559.2A CN202110202559A CN114978875A CN 114978875 A CN114978875 A CN 114978875A CN 202110202559 A CN202110202559 A CN 202110202559A CN 114978875 A CN114978875 A CN 114978875A
Authority
CN
China
Prior art keywords
node
domain
service
current
center
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110202559.2A
Other languages
Chinese (zh)
Inventor
廖磊
李辉
石静迎
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Automobile Group Co Ltd
Original Assignee
Guangzhou Automobile Group Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangzhou Automobile Group Co Ltd filed Critical Guangzhou Automobile Group Co Ltd
Priority to CN202110202559.2A priority Critical patent/CN114978875A/en
Publication of CN114978875A publication Critical patent/CN114978875A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/10Active monitoring, e.g. heartbeat, ping or trace-route
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/50Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Medical Informatics (AREA)
  • Cardiology (AREA)
  • Hardware Redundancy (AREA)

Abstract

The invention discloses a vehicle-mounted node management method, a device and a storage medium, wherein the vehicle-mounted node management method comprises the following steps: establishing domain center nodes corresponding to all domains in the target domain according to the node information; the center node of the domain receives the service providing information and the service seeking information of each node in the current domain, and communicates the service providing information and the service seeking information of each node with the center nodes of other domains so as to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains; when the current domain center node fails, the optimal adjacent node can be selected as the domain center node of the current domain; when the current node fails, the service state of the current node is uploaded to the starting service middleware to pull up the failure process, and the central node of the domain of the current domain informs the nodes subscribed to the service of the failed node to remove the failed node. The invention can avoid the problem that the request fails because the whole cluster is disturbed during service discovery and a fault node cannot be detected and eliminated.

Description

Vehicle-mounted node management method and device and storage medium
Technical Field
The invention relates to the technical field of intelligent networking of vehicle-mounted communication, in particular to a vehicle-mounted node management method and device and a computer readable storage medium.
Background
With the rapid development of automobile intellectualization, networking, electromotion and sharing, the automobile Ethernet is applied therewith. Automotive ethernet is a physical network used to connect components within an automobile using a wired network. The vehicle-mounted Ethernet can meet the requirement of automobile manufacturers on bandwidth, and meanwhile, the network cost in the automobile can be reduced. At present, the vehicle-mounted ethernet usually knows the location, attribute and state information of the service through service discovery before service invocation, so that a service interface needs to adopt a broadcast mechanism, and the whole cluster service needs to passively receive broadcast messages.
Therefore, the prior art needs to be further improved and improved.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present invention is to provide a vehicle-mounted node management method, device, computer-readable storage medium, and vehicle-mounted terminal, which can avoid the problem that a request fails because a whole cluster is disturbed and a failed node cannot be detected and removed when a service is found.
In order to solve the above technical problem, an embodiment of the present invention provides a vehicle node management method, which is applicable to a vehicle ethernet and includes:
establishing domain center nodes corresponding to all domains in the target domain according to the node information;
periodically acquiring online heartbeat packets of the center node of the domain in the current domain to judge whether the center node of the domain fails, and when the center node of the domain fails, selecting an optimal adjacent node from a node selection model as the center node of the current domain;
the central node of the domain receives the service providing information and the service seeking information of each node in the current domain, and the central node of the domain intercommunicates with the central nodes of other domains to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains.
Further, the node selection model is:
d=ω cpu C cpumemory C memory
s.t.C cpu ≤C climit
C memory ≤C mlimit
wherein, C cpu As CPU occupancy rate, C memory For memory occupancy, ω cpu Weight of CPU occupancy, ω memory Weight of memory occupancy, C climit As a limit value of CPU occupancy, C mlimit The limit value is the occupancy rate of the memory; and the optimal adjacent node is the node with the minimum d value calculated according to the CPU occupancy rate and the memory occupancy rate. .
Further, before the step of receiving the service providing information and seeking the service information of each node in the current domain, the domain center node further includes:
periodically acquiring node heartbeat packets of all nodes in a current domain to judge whether the current node is a fault node;
when the current node is a fault node, setting the service state of the current node as unavailable, and uploading the service state of the current node to a service starting middleware
Further, after the step of uploading the service state of the current node to the service middleware, the method further includes:
the startup service middleware pulls up the failed process and notifies the nodes subscribing to the service of the failed node by the domain center node of the current domain to remove the failed node.
In order to solve the above technical problem, an embodiment of the present invention further provides a vehicle-mounted node management apparatus, including:
the node creating module is used for creating domain center nodes corresponding to each domain in the target domain according to the node information;
the judging module is used for judging whether the center node of the domain and each node in the domain have faults or not before the center node of the domain receives the service providing information and the service seeking information of each node in the current domain, and determining the corresponding availability and the access mode according to the fault condition;
and the service seeking module is used for receiving the service providing information and the service seeking information of each node in the current domain through the domain center node, and intercommunicating the service providing information and the service seeking information of each node with other domain center nodes so as to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains.
Further, the service seeking module is also used for, before the central node of the domain receives the service providing information and the service seeking information of each node in the current domain,
periodically acquiring online heartbeat packets of the central nodes in the domain in the current domain to judge whether the central nodes in the domain have faults or not;
and when the domain center node fails, selecting the optimal adjacent node selected by the node selection model as the domain center node of the current domain.
Further, the node selection model is:
d=ω cpu C cpumemory C memory
s.t.C cpu ≤C climit
C memory ≤C mlimit
wherein, C cpu Is CPU occupancy rate, C memory For memory occupancy, ω cpu Weight of CPU occupancy, ω memory Weight of memory occupancy, C climit As a limit value of CPU occupancy, C mlimit A limit value for memory occupancy rate; and the optimal adjacent node is the node with the minimum d value calculated according to the CPU occupancy rate and the memory occupancy rate.
Further, the service seeking module is also used for, before the central node of the domain receives the service providing information and the service seeking information of each node in the current domain,
periodically acquiring node heartbeat packets of all nodes in a current domain to judge whether the current node is a fault node;
and when the current node is a fault node, setting the service state of the current node as unavailable, and uploading the service state of the current node to the service starting middleware.
Further, the service seeking module is further configured to, after uploading the service state of the current node to the service middleware,
the startup service middleware pulls up the failed process and notifies the nodes subscribing to the service of the failed node by the domain center node of the current domain to remove the failed node.
An embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium includes a stored computer program; when running, the computer program controls the device where the computer-readable storage medium is located to execute the vehicle-mounted node management method.
Compared with the prior art, the embodiment of the invention provides a vehicle-mounted node management method, a device, a computer-readable storage medium and a vehicle-mounted terminal, wherein domain center nodes corresponding to each domain in a target domain are created according to node information; receiving the service providing information and the service seeking information of each node in the current domain through the domain center node, and communicating the service providing information and the service seeking information of each node with other domain center nodes so as to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains; when the current domain center node fails, the optimal adjacent node can be selected as the domain center node of the current domain; meanwhile, when the current node fails, the service state of the current node is uploaded to the startup service middleware to pull up the failure process, and the domain center node of the current domain notifies the core node subscribed to the service of the failed node to remove the failed node. Compared with the prior art that the vehicle-mounted Ethernet generally knows the position, the attribute and the state information of the service through service discovery before service call and broadcasts through a service interface, the invention can realize service discovery through the domain center node and avoid disturbance of excessive broadcast messages to the whole cluster in the node discovery process. Meanwhile, the center node of the domain can detect the health state of the node service in the domain, and when the node service is abnormal, the abnormal condition is removed immediately to avoid the request failure, thereby effectively improving the communication efficiency. In addition, when the central node of the domain fails, the service of the domain where the central node of the failed domain is located accesses the optimal adjacent node, high availability of service discovery is realized, and therefore the management experience of the user node is improved.
Drawings
Fig. 1 is a flowchart of a preferred embodiment of a vehicle-mounted node management method according to the present invention;
fig. 2 is a schematic view of an application environment of a vehicle-mounted node management method according to the present invention;
FIG. 3 is a data flow diagram of a vehicle node management method according to the present invention;
FIG. 4 is a schematic flow chart of another preferred embodiment of the present invention;
FIG. 5 is a data flow diagram of another preferred embodiment of the present invention;
FIG. 6 is a schematic flow chart of another preferred embodiment of the present invention;
FIG. 7 is a data flow diagram of another preferred embodiment of the present invention;
fig. 8 is a block diagram illustrating a structure of an on-vehicle node management apparatus according to the present invention;
fig. 9 is a block diagram of a preferred embodiment of the in-vehicle terminal provided by the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that, the step numbers in the text are only for convenience of explanation of the specific embodiments, and do not serve to limit the execution sequence of the steps. The method provided by the embodiment can be executed by the relevant server, and the server is taken as an example for explanation below.
As shown in fig. 1 to fig. 3, an embodiment of the present invention provides a vehicle node management method, which is suitable for a vehicle ethernet, and the method includes steps S11 to S12:
and step S11, creating domain center nodes corresponding to each domain in the target domain according to the node information.
Step S12, the domain center node receives the service providing information and service seeking information of each node in the current domain, and interworks the service providing information and service seeking information of each node with other domain center nodes to inform the availability and access mode of each node seeking service in the current domain and/or other domains.
The target domain includes, but is not limited to, a vehicle body domain, a power domain, a chassis domain, an automatic driving domain, and a cockpit domain. The vehicle body domain comprises vehicle body electronics and information related to the vehicle body electronics, the power domain comprises vehicle safety and information related to the safety, the chassis domain comprises vehicle body movement and information related to the vehicle body, the automatic driving domain comprises information related to auxiliary driving or driving, and the cockpit domain comprises entertainment information and information related to entertainment. In order to improve the high availability of service invocation, all parts and related parts in a vehicle body domain, a power domain, a chassis domain, an automatic driving domain and a cockpit domain need to be divided into a plurality of nodes, and a domain center node is created according to node information of the nodes in each domain.
Further, the nodes in each domain are connected to the corresponding domain center nodes, and the domain center nodes can communicate with each other. The central node of the domain can receive the service providing information and the service seeking information of each node in the current domain, and performs message intercommunication with the central nodes of other domains to obtain the availability and the access mode of each node for seeking service. Meanwhile, the domain center node can also inform the corresponding intra-domain node of the availability and the access mode of seeking services through other domain center nodes. It can be understood that, since the domain center node masters the service provision and service search entries of all the nodes and can inform the corresponding entry information of the nodes in the domain to complete the node discovery process, the broadcast message in the node discovery process is prevented from disturbing the whole cluster.
Specifically, referring to fig. 3, taking an example of service information interaction between the domain center node in the domain a and the domain center node in the domain B: if the domain center node of the domain A receives the message that the node 1 in the domain searches for the service 1 and provides the service 2; the domain center node of the B domain receives a message that node 2 in its domain provides service 1 and node 3 seeks service 2. Since the domain center node of the a domain and the domain center node of the B domain can perform message intercommunication, when the domain center node of the a domain performs message intercommunication between the service seeking information of the node 1 in the domain and the domain center node of the B domain, the domain center node of the B domain informs the domain center node of the a domain of the service providing information of the node 2 and the service seeking information of the node 3 in the domain. At this time, the domain center node of the a domain informs the node 1: node 2 provides service 1, node 3 seeks service 2; the domain center node of the B domain informs node 2: node 1 seeks service 1, informing node 3: node 1 provides service 2 so that node 1 requests service 1 and request service 2 from node 2 and node 3, respectively, while node 2 and node 3 respond to service 1 and respond to service 2, respectively.
In this embodiment, first, a domain center node corresponding to each domain in a target domain is created according to node information, then, the domain center node receives service providing information and service seeking information of each node in a current domain, and intercommunicates the service providing information and service seeking information of each node with other domain center nodes to inform availability and access mode of service seeking of each node in the current domain and/or other domains, so that a node discovery process is mainly processed by the domain center node, the domain center node grasps service providing and service seeking entries of all nodes and informs entry information corresponding to the nodes in the domain, interference of broadcast messages in the node discovery process to a whole cluster is avoided, and user service scheduling experience is improved.
As shown in fig. 4 to fig. 5, in a preferred embodiment, before the domain center node receives the service providing information and the service seeking information of each node in the current domain in step S12, it is further required to determine whether the domain center node and each node in the domain have a fault, and determine the corresponding availability and access mode according to the fault condition, specifically: s121 to S123:
and S121, periodically acquiring node heartbeat packets of each node in the current domain to judge whether the current node is a fault node.
And S122, when the current node is a fault node, setting the service state of the current node as unavailable, and uploading the service state of the current node to the service starting middleware.
S123, the starting service middleware pulls up the failure process, and the domain center node of the current domain informs the node subscribed to the failure node service to remove the failure node.
As described above, the central node in the domain acquires the node heartbeat packet of each node in the current domain in real time or periodically, discovers the working state of the node in the domain through the node heartbeat packet, sets the service state of the current node as unavailable when the current node is a faulty node, and uploads the service state of the current node to the start service middleware, the central nodes in other domains, or the associated controllers in the domain, so that the start service middleware, the central nodes in other domains, or the associated controllers in the domain pull up the fault process, and the central node in the domain in the current domain notifies the node subscribed to the service of the faulty node to remove the faulty node. Therefore, other nodes will not invoke the service of the failed node and will look for other nodes to provide the service to communicate. In addition, if the fault node has a standby service node, the standby service node is adopted to carry out interaction of service information; and if the fault node has no standby service node, fault tolerance degradation processing can be carried out.
Specifically, referring to fig. 5, taking an example of service information interaction between the domain center node in the domain a and the domain center node in the domain B: if the domain center node of the domain A provides the message of the service 1; message of domain center node of B domain for service 1. Since the domain center node of the a domain and the domain center node of the B domain can perform message intercommunication, when the domain center node of the a domain performs message intercommunication between the service providing information of the node 1 in the domain and the domain center node of the B domain, the domain center node of the B domain informs the domain center node of the domain of the node 2 in the B domain of the information of seeking the service 1. When a central node of a domain B detects that a node 2 in the domain fails, reporting the information that the node 2 fails to a service starting middleware to enable the service starting middleware to pull up a service process aiming at the node 2; meanwhile, the node B in the domain informs the node 1 of the failure of the node 2 in the domain through the node A in the domain, so that the node 1 removes the service for the failed node 2.
As shown in fig. 6 to 7, in the preferred embodiment, before the current domain center node performs message interworking with other domain center nodes, step S12 further includes: s124 to S125:
and S124, periodically acquiring online heartbeat packets of the central node in the domain in the current domain to judge whether the central node in the domain has a fault.
And S125, when the domain center node fails, taking the optimal adjacent node selected by the node selection model as the domain center node of the current domain.
As described above, the domain center node of each domain uploads the respective online heartbeat packet to the start service middleware, other domain center nodes or the relevant controller in the domain in real time or periodically, so that the domain center node monitors and judges the working state of the domain center node, and can select the optimal adjacent node as the domain center node of the current domain in time through the node selection model when the domain center node fails.
Wherein the node selection model is:
d=ω cpu C cpumemory C memory
s.t.C cpu ≤C climit
C memory ≤C mlimit
wherein, C cpu As CPU occupancy rate, C memory For memory occupancy, ω cpu Weight of CPU occupancy, ω memory Weight of memory occupancy, C climit As a limit value of CPU occupancy, C mlimit Is the limit value of the memory occupancy rate.
The optimal adjacent node is a node with the shortest distance (the minimum value of d) calculated according to a certain weight and the CPU occupancy rate and the memory occupancy rate by taking the resource occupancy condition as an index for measuring the distance.
Specifically, when a domain central node of a domain fails, because service names and corresponding addresses of the service names are synchronous among the domain central nodes, the service of the domain where the failed central node is located accesses the central node of the nearby domain controller, and high availability of service discovery is realized. For example, when a central node of the cockpit domain fails, the optimal adjacent central node selected by the node selection model is the central node of the autopilot domain, the service in the cockpit domain is connected to the central node of the autopilot domain, and the central node of the autopilot domain performs functions such as service discovery of the local domain and the cockpit domain, so that high availability of the service is realized. In addition, the node selection model takes the resource occupation condition as an index for measuring the distance, calculates the node closest to the node according to a certain weight and the CPU occupation rate and the memory occupation rate to be used as the optimal node for the resource occupation condition, takes the optimal node for the resource occupation condition as the optimal adjacent node, and can search the optimal adjacent node in a delayed manner when all the node resources exceed the limit value, thereby meeting the actual application requirement.
In this embodiment, when the domain center node fails, the optimal neighboring node selected by the node selection model is used as the domain center node of the current domain, so that service implementation among the domain center nodes is avoided, and high availability of service discovery is realized.
According to the vehicle-mounted node management method provided by the embodiment of the invention, a domain center node corresponding to each domain in a target domain is established according to node information; receiving the service providing information and the service seeking information of each node in the current domain through the domain center node, and communicating the service providing information and the service seeking information of each node with other domain center nodes so as to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains; when the current domain center node fails, the optimal adjacent node can be selected as the domain center node of the current domain; meanwhile, when the current node fails, the service state of the current node is uploaded to the startup service middleware to pull up the failure process, and the domain center node of the current domain notifies the node subscribed to the service of the failed node to remove the failed node. Compared with the prior art that the vehicle-mounted Ethernet generally knows the position, the attribute and the state information of the service through service discovery before service calling and broadcasts through a service interface, the invention can realize service discovery through the domain center node and avoid the disturbance of excessive broadcast messages to the whole cluster in the node discovery process. Meanwhile, the center node of the domain can detect the health state of the node service in the domain, and when the node service is abnormal, the abnormal condition is removed immediately to avoid the request failure, thereby effectively improving the communication efficiency. In addition, when the central node of the domain fails, the service of the domain where the central node of the failed domain is located accesses the optimal adjacent node, high availability of service discovery is realized, and therefore the management experience of the user node is improved.
It should be understood that, although the steps in the above-described flowcharts are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in the above-described flowcharts may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily sequential, but may be performed alternately or alternatingly with other steps or at least a portion of the sub-steps or stages of other steps.
The embodiment of the present invention further provides a vehicle-mounted node management device, which can implement all the processes of the vehicle-mounted node management method described in any of the above embodiments, and the functions and implemented technical effects of each module and unit in the device are respectively the same as those of the vehicle-mounted node management method described in the above embodiment, and are not described herein again.
As shown in fig. 8, the present invention is a block diagram of a preferred embodiment of an on-board node management apparatus, where the apparatus includes:
a node creating module 21, configured to create, according to the node information, a domain center node corresponding to each domain in the target domain; the target domain comprises a vehicle body domain, a power domain, a chassis domain, an automatic driving domain and a cockpit domain.
The determining module 22 is configured to determine whether the domain center node and each node in the domain have a fault before the domain center node receives the service providing information and the service seeking information of each node in the current domain, and determine a corresponding availability and an access mode according to a fault condition.
And the service seeking module 23 is configured to receive the service providing information and the service seeking information of each node in the current domain through the domain center node, and interwork the service providing information and the service seeking information of each node with other domain center nodes to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains.
The target domain includes, but is not limited to, a vehicle body domain, a power domain, a chassis domain, an automatic driving domain, and a cockpit domain. The vehicle body domain comprises vehicle body electronics and information related to the vehicle body electronics, the power domain comprises vehicle safety and information related to the safety, the chassis domain comprises vehicle body movement and information related to the vehicle body, the automatic driving domain comprises information related to auxiliary driving or driving, and the cockpit domain comprises entertainment information and information related to entertainment. In order to improve the high availability of service invocation, all components and related components in a vehicle body domain, a power domain, a chassis domain, an automatic driving domain and a cockpit domain need to be divided into a plurality of nodes, and a domain center node is created according to node information of the nodes in each domain.
Further, the nodes in each domain are connected to the corresponding domain center nodes, and the domain center nodes can communicate with each other. The central node of the domain can receive the service providing information and the service seeking information of each node in the current domain, and performs message intercommunication with the central nodes of other domains to obtain the availability and the access mode of each node for seeking service. Meanwhile, the domain center node can also inform the corresponding intra-domain node of the availability and the access mode of seeking services through other domain center nodes. It can be understood that, since the domain center node grasps the service provision of all nodes and searches for service entries, and can inform the corresponding entry information of the nodes in the domain, the node discovery process is completed, thereby avoiding the disturbance of the broadcast message in the node discovery process to the whole cluster.
Specifically, the service information interaction between the domain center node in the domain a and the domain center node in the domain B is as an example: if the domain center node of the domain A receives the message of searching for the service 1 and providing the service 2 of the node 1 in the domain A; the domain center node of the B domain receives the message of providing service 1 of node 2 in its domain, and searching service 2 of node 3 in the domain. Since the domain center node of the a domain and the domain center node of the B domain can perform message intercommunication, when the domain center node of the a domain performs message intercommunication between the service seeking information of the node 1 in the domain and the domain center node of the B domain, the domain center node of the B domain informs the domain center node of the a domain of the service providing information of the node 2 and the service seeking information of the node 3 in the domain. At this time, the domain center node of the a domain informs the node 1: node 2 provides service 1, node 3 seeks service 2; the domain center node of the B domain informs node 2: node 1 seeks service 1, informing node 3: node 1 provides service 2 so that node 1 requests service 1 and request service 2 from node 2 and node 3, respectively, while node 2 and node 3 respond to service 1 and respond to service 2, respectively.
In the embodiment, domain center nodes corresponding to each domain in a target domain are firstly created according to node information, then the provided service information and the sought service information of each node in the current domain are received through the domain center nodes, the provided service information and the sought service information of each node are communicated with other domain center nodes, so that the availability and the access mode of the sought service of each node in the current domain and/or other domains are informed, the node discovery process is mainly processed through the domain center nodes, the domain center nodes master the provided service and the sought service entries of all nodes and inform the corresponding entry information of the nodes in the domain, and the disturbance of broadcast messages in the node discovery process to the whole cluster is avoided, so that the user service scheduling experience is improved.
In a preferred embodiment, the apparatus further includes a determining module, configured to determine whether the node in the domain and the nodes in the domain have a fault before the node in the domain receives the service providing information and the service seeking information of the nodes in the current domain, and determine corresponding availability and access mode according to the fault condition, where the service seeking module 22 is specifically configured to,
periodically acquiring node heartbeat packets of all nodes in a current domain to judge whether the current node is a fault node;
when the current node is a fault node, setting the service state of the current node as unavailable, and uploading the service state of the current node to a service starting middleware;
the startup service middleware pulls up the failed process and notifies the nodes subscribing to the service of the failed node by the domain center node of the current domain to remove the failed node.
As described above, the central node in the domain acquires the node heartbeat packet of each node in the current domain in real time or periodically, discovers the working state of the node in the domain through the node heartbeat packet, sets the service state of the current node as unavailable when the current node is a faulty node, and uploads the service state of the current node to the start service middleware, the central nodes in other domains, or the associated controllers in the domain, so that the start service middleware, the central nodes in other domains, or the associated controllers in the domain pull up the fault process, and the central node in the domain in the current domain notifies the node subscribed to the service of the faulty node to remove the faulty node. Therefore, other nodes will not invoke the service of the failed node and will seek other nodes providing the service to communicate. In addition, if the fault node has a standby service node, the standby service node is adopted to carry out interaction of service information; and if the fault node has no standby service node, fault tolerance degradation processing can be carried out.
Specifically, the service information interaction between the domain center node in the domain a and the domain center node in the domain B is as an example: if the domain center node of the A domain provides the message of the service 1; message of domain center node of B domain for service 1. Since the domain center node of the a domain and the domain center node of the B domain can perform message intercommunication, when the domain center node of the a domain performs message intercommunication between the service providing information of the node 1 in the domain and the domain center node of the B domain, the domain center node of the B domain informs the domain center node of the domain of the node 2 in the B domain of the information of seeking the service 1. When a domain center node of a domain B detects that a node 2 in the domain fails, reporting the information that the node 2 fails to start a service middleware, so that the service process for the node 2 is pulled up by the service middleware; meanwhile, the node B in the domain informs the node 1 of the failure of the node 2 in the domain through the node A in the domain, so that the node 1 removes the service for the failed node 2.
In another preferred embodiment, before the current domain center node performs message interworking with other domain center nodes, the service seeking module 22 is further configured to,
periodically acquiring online heartbeat packets of the central nodes in the domain in the current domain to judge whether the central nodes in the domain have faults or not;
and when the domain center node fails, selecting the optimal adjacent node selected by the node selection model as the domain center node of the current domain.
As described above, the domain center node of each domain uploads the respective online heartbeat packet to the start service middleware, other domain center nodes or the relevant controller in the domain in real time or periodically, so that the domain center node monitors and judges the working state of the domain center node, and can select the optimal adjacent node as the domain center node of the current domain in time through the node selection model when the domain center node fails.
Wherein the node selection model is:
d=ω cpu C cpumemory C memory
s.t.C cpu ≤C climit
C memory ≤C mlimit
wherein, C cpu As CPU occupancy rate, C memory For memory occupancy, ω cpu Weight of CPU occupancy, ω memory Weight of memory occupancy, C climit As a limit value of CPU occupancy, C mlimit Is the limit value of the memory occupancy rate.
The optimal adjacent node is a node with the shortest distance (the minimum value of d) calculated according to a certain weight and the CPU occupancy rate and the memory occupancy rate by taking the resource occupancy condition as an index for measuring the distance.
Specifically, when a domain center node of a domain fails, since service names and corresponding addresses of the domain center nodes are synchronous, the service of the domain where the failed center node is located will access the center node of the nearby domain controller, and high availability of service discovery is realized. For example, when a central node of the cockpit domain fails, the optimal adjacent central node selected by the node selection model is the central node of the autopilot domain, the service in the cockpit domain is connected to the central node of the autopilot domain, and the central node of the autopilot domain performs functions such as service discovery of the local domain and the cockpit domain, so that high availability of the service is realized. In addition, the node selection model takes the resource occupation condition as an index for measuring the distance, calculates the node closest to the node according to a certain weight and the CPU occupation rate and the memory occupation rate to be used as the optimal node for the resource occupation condition, takes the optimal node for the resource occupation condition as the optimal adjacent node, and can search the optimal adjacent node in a delayed manner when all the node resources exceed the limit value, thereby meeting the actual application requirement.
In this embodiment, when the domain center node fails, the optimal neighboring node selected by the node selection model is used as the domain center node of the current domain, so that service implementation among the domain center nodes is avoided, and high availability of service discovery is realized.
According to the vehicle-mounted node management device provided by the embodiment of the invention, a domain center node corresponding to each domain in a target domain is established according to node information; receiving the service providing information and the service seeking information of each node in the current domain through the domain center node, and communicating the service providing information and the service seeking information of each node with other domain center nodes so as to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains; when the current domain center node fails, the optimal adjacent node can be selected as the domain center node of the current domain; meanwhile, when the current node fails, the service state of the current node is uploaded to the startup service middleware to pull up the failure process, and the domain center node of the current domain notifies the node subscribed to the service of the failed node to remove the failed node. Compared with the prior art that the vehicle-mounted Ethernet generally knows the position, the attribute and the state information of the service through service discovery before service calling and broadcasts through a service interface, the invention can realize service discovery through the domain center node and avoid the disturbance of excessive broadcast messages to the whole cluster in the node discovery process. Meanwhile, the center node of the domain can detect the health state of the node service in the domain, and when the node service is abnormal, the abnormal condition is removed immediately to avoid the request failure, thereby effectively improving the communication efficiency. In addition, when the central node of the domain fails, the service of the domain where the central node of the failed domain is located accesses the optimal adjacent node, high availability of service discovery is realized, and therefore the management experience of the user node is improved.
An embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium includes a stored computer program; when running, the computer program controls the device where the computer-readable storage medium is located to execute the vehicle-mounted node management method according to any one of the above embodiments.
An embodiment of the present invention further provides an in-vehicle terminal, which is shown in fig. 9 and is a block diagram of a preferred embodiment of the in-vehicle terminal provided by the present invention, where the in-vehicle terminal includes a processor 10, a memory 20, and a computer program stored in the memory 20 and configured to be executed by the processor 10, and the processor 10 implements the in-vehicle node management method according to any one of the embodiments when executing the computer program.
Preferably, the computer program can be divided into one or more modules/units (e.g. computer program 1, computer program 2,) which are stored in the memory 20 and executed by the processor 10 to accomplish the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used for describing the execution process of the computer program in the vehicle-mounted terminal.
The Processor 10 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, etc., the general purpose Processor may be a microprocessor, or the Processor 10 may be any conventional Processor, the Processor 10 is a control center of the in-vehicle terminal, and various interfaces and lines are used to connect various parts of the in-vehicle terminal.
The memory 20 mainly includes a program storage area that may store an operating system, an application program required for at least one function, and the like, and a data storage area that may store related data and the like. In addition, the memory 20 may be a high speed random access memory, may also be a non-volatile memory, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card), and the like, or the memory 20 may also be other volatile solid state memory devices.
It should be noted that the above-mentioned vehicle-mounted terminal may include, but is not limited to, a processor and a memory, and those skilled in the art will understand that the structural block diagram of fig. 9 is only an example of the vehicle-mounted terminal, and does not constitute a limitation to the vehicle-mounted terminal, and may include more or less components than those shown in the drawings, or may combine some components, or different components.
To sum up, according to the vehicle-mounted node management method, the vehicle-mounted node management device, the computer-readable storage medium and the vehicle-mounted terminal provided by the embodiment of the invention, the domain center node corresponding to each domain in the target domain is created according to the node information; receiving the service providing information and the service seeking information of each node in the current domain through the domain center node, and communicating the service providing information and the service seeking information of each node with other domain center nodes so as to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains; when the current domain center node fails, the optimal adjacent node can be selected as the domain center node of the current domain; meanwhile, when the current node fails, the service state of the current node is uploaded to the startup service middleware to pull up the failure process, and the domain center node of the current domain notifies the domain center node subscribed to the service of the failed node to remove the failed node. Compared with the prior art that the vehicle-mounted Ethernet generally knows the position, the attribute and the state information of the service through service discovery before service calling and broadcasts through a service interface, the invention can realize service discovery through the domain center node and avoid the disturbance of excessive broadcast messages to the whole cluster in the node discovery process. Meanwhile, the center node of the domain can detect the health state of the node service in the domain, and when the node service is abnormal, the abnormal condition is removed immediately to avoid the request failure, thereby effectively improving the communication efficiency. In addition, when the central node of the domain fails, the service of the domain where the central node of the failed domain is located accesses the optimal adjacent node, high availability of service discovery is realized, and therefore the management experience of the user node is improved.
The above description is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, several modifications and variations can be made without departing from the technical principle of the present invention, and these modifications and variations should also be regarded as the protection scope of the present invention.

Claims (10)

1. A vehicle-mounted node management method is applicable to a vehicle-mounted Ethernet, and comprises the following steps:
establishing domain center nodes corresponding to all domains in the target domain according to the node information;
periodically acquiring online heartbeat packets of the center node in the domain in the current domain to judge whether the center node in the domain fails, and when the center node in the domain fails, selecting an optimal adjacent node selected by a node selection model as the center node in the domain in the current domain;
the domain center node receives the service providing information and the service seeking information of each node in the current domain, and intercommunicates the service providing information and the service seeking information of each node with other domain center nodes to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains.
2. The vehicle node management method of claim 1, wherein the node selection model is:
d=ω cpu C cpumemory C memory
s.t.C cpu ≤C climit
C memory ≤C mlimit
wherein, C cpu As CPU occupancy rate, C memory For memory occupancy, ω cpu Weight of CPU occupancy, ω memory Weight of memory occupancy, C climit As a limit value of CPU occupancy, C mlimit The limit value is the occupancy rate of the memory; and the optimal adjacent node is the node with the minimum d value calculated according to the CPU occupancy rate and the memory occupancy rate.
3. The method for vehicle node management according to claim 1, wherein before the step of receiving the service providing information and seeking service information of each node in the current domain, the domain center node further comprises:
periodically acquiring node heartbeat packets of all nodes in a current domain to judge whether the current node is a fault node;
and when the current node is a fault node, setting the service state of the current node as unavailable, and uploading the service state of the current node to a service starting middleware.
4. The method for vehicle node management according to claim 3, wherein after the step of uploading the service status of the current node to the service middleware, further comprising:
the startup service middleware pulls up the failed process and notifies the nodes subscribing to the service of the failed node by the domain center node of the current domain to remove the failed node.
5. An on-vehicle node management device, characterized by comprising:
the node creating module is used for creating domain center nodes corresponding to each domain in the target domain according to the node information; the judging module is used for judging whether the center node of the domain and each node in the domain have faults or not before the center node of the domain receives the service providing information and the service seeking information of each node in the current domain, and determining the corresponding availability and the access mode according to the fault condition;
and the service seeking module is used for receiving the service providing information and the service seeking information of each node in the current domain through the domain center node, and intercommunicating the service providing information and the service seeking information of each node with other domain center nodes so as to inform the availability and the access mode of service seeking of each node in the current domain and/or other domains.
6. The on-board node management apparatus of claim 5, wherein the service seeking module is further configured to, before the center node of the domain receives the service providing information and the service seeking information of each node in the current domain,
periodically acquiring online heartbeat packets of the central nodes in the domain in the current domain to judge whether the central nodes in the domain have faults or not;
and when the domain center node fails, selecting the optimal adjacent node selected by the node selection model as the domain center node of the current domain.
7. The on-vehicle node management apparatus according to claim 6, wherein the node selection model is:
d=ω cpu C cpumemory C memory
s.t.C cpu ≤C climit
C memory ≤C mlimit
wherein, C cpu As CPU occupancy rate, C memory For memory occupancy, ω cpu Weight of CPU occupancy, ω memory Weight of memory occupancy, C climit As a limit value of CPU occupancy, C mlimit The limit value is the occupancy rate of the memory; and the optimal adjacent node is the node with the minimum d value calculated according to the CPU occupancy rate and the memory occupancy rate.
8. The on-board node management apparatus of claim 7, wherein the service seeking module is further configured to, before the center node of the domain receives the service providing information and the service seeking information of each node in the current domain,
periodically acquiring node heartbeat packets of all nodes in a current domain to judge whether the current node is a fault node;
and when the current node is a fault node, setting the service state of the current node as unavailable, and uploading the service state of the current node to the service starting middleware.
9. The on-board node management apparatus of claim 8, wherein the service seeking module is further configured to upload the service status of the current node after initiating service middleware,
the startup service middleware pulls up the failed process and notifies the nodes subscribing to the service of the failed node by the domain center node of the current domain to remove the failed node.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a stored computer program; wherein the computer program, when executed, controls an apparatus in which the computer-readable storage medium is located to perform the in-vehicle node management method according to any one of claims 1 to 4.
CN202110202559.2A 2021-02-23 2021-02-23 Vehicle-mounted node management method and device and storage medium Pending CN114978875A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110202559.2A CN114978875A (en) 2021-02-23 2021-02-23 Vehicle-mounted node management method and device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110202559.2A CN114978875A (en) 2021-02-23 2021-02-23 Vehicle-mounted node management method and device and storage medium

Publications (1)

Publication Number Publication Date
CN114978875A true CN114978875A (en) 2022-08-30

Family

ID=82954017

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110202559.2A Pending CN114978875A (en) 2021-02-23 2021-02-23 Vehicle-mounted node management method and device and storage medium

Country Status (1)

Country Link
CN (1) CN114978875A (en)

Citations (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1719782A (en) * 2005-03-24 2006-01-11 袁光辉 On vehicle network central control unit and its managing and controlling method for on-vehicle network
CN101094189A (en) * 2007-08-10 2007-12-26 中控科技集团有限公司 System of wireless sensor network, and cluster routing method based on the system
CN101237345A (en) * 2007-12-04 2008-08-06 奇瑞汽车有限公司 A network management method for CAN bus
CN102195769A (en) * 2011-06-02 2011-09-21 合肥工业大学 Clock synchronization method for automobile CAN (Control Area Network)
CN102658801A (en) * 2012-04-28 2012-09-12 浙江吉利汽车研究院有限公司杭州分公司 Controller area network (CAN) system network management method for new energy vehicle
CN103139011A (en) * 2011-11-30 2013-06-05 通用汽车环球科技运作有限责任公司 Integrated fault diagnosis and prognosis for in-vehicle communications
CN103607297A (en) * 2013-11-07 2014-02-26 上海爱数软件有限公司 Fault processing method of computer cluster system
CN104135391A (en) * 2014-08-19 2014-11-05 北京汽车股份有限公司 Management method and device for vehicle-mounted CAN partial networking
CN105611503A (en) * 2015-12-30 2016-05-25 东软集团股份有限公司 Information communication method and system in in-vehicle network environment
CN106254250A (en) * 2016-08-03 2016-12-21 成都之达科技有限公司 Car networking short-distance networking method
CN206932240U (en) * 2017-08-01 2018-01-26 风度(常州)汽车研发院有限公司 Vehicle-mounted ethernet communication system and intelligent automobile
CN107817779A (en) * 2016-09-12 2018-03-20 现代自动车株式会社 The system and method for the unregistered device of Information Authentication based on Ethernet switch
CN108833170A (en) * 2018-06-20 2018-11-16 长春工业大学 A kind of network level adaptation CAN bus method for diagnosing faults
CN109104351A (en) * 2017-06-21 2018-12-28 比亚迪股份有限公司 Train network node and train network node monitoring method based on CANopen agreement
CN109263581A (en) * 2018-11-08 2019-01-25 湖北汽车工业学院 A kind of real-time commitment method for automatic driving vehicle
CN109756407A (en) * 2019-01-17 2019-05-14 重庆菲斯塔新能源汽车科技有限公司 A kind of CAN bus based localized network management method
CN109787795A (en) * 2017-11-13 2019-05-21 比亚迪股份有限公司 Processing method, node and the electronic equipment of train network host node failure
CN109981473A (en) * 2019-02-15 2019-07-05 浙江吉利汽车研究院有限公司 A kind of real-time messages bus system
CN110086622A (en) * 2018-01-25 2019-08-02 南京汽车集团有限公司 In-vehicle network security architecture designs under a kind of intelligent network connection environment
CN111294845A (en) * 2020-02-13 2020-06-16 世纪龙信息网络有限责任公司 Node switching method and device, computer equipment and storage medium
CN111447126A (en) * 2019-12-05 2020-07-24 炬星科技(深圳)有限公司 Ethernet bus communication method, device, robot, equipment and computer readable storage medium
CN111532227A (en) * 2020-07-02 2020-08-14 深圳市法拉第电驱动有限公司 CAN network management method and system for electric vehicle controller
CN111781917A (en) * 2020-07-03 2020-10-16 华人运通(江苏)技术有限公司 Fault data processing method, domain controller and automobile
CN111891181A (en) * 2020-06-23 2020-11-06 株洲中车时代电气股份有限公司 Train network control system based on Ethernet
CN111935325A (en) * 2020-10-15 2020-11-13 广州汽车集团股份有限公司 OTA (over the air) upgrading method and device
CN112087351A (en) * 2020-09-24 2020-12-15 山东交通学院 Remote train network communication interface testing method
CN112131572A (en) * 2020-08-31 2020-12-25 华为技术有限公司 Control method of vehicle-mounted equipment, vehicle-mounted equipment and vehicle system
CN112181660A (en) * 2020-10-12 2021-01-05 北京计算机技术及应用研究所 High-availability method based on server cluster
CN112272366A (en) * 2020-10-27 2021-01-26 吉林大学 Automobile emergency information communication method based on block chain
CN112291194A (en) * 2020-09-27 2021-01-29 上海赫千电子科技有限公司 State management method and device based on ECU in vehicle-mounted network and intelligent automobile

Patent Citations (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1719782A (en) * 2005-03-24 2006-01-11 袁光辉 On vehicle network central control unit and its managing and controlling method for on-vehicle network
CN101094189A (en) * 2007-08-10 2007-12-26 中控科技集团有限公司 System of wireless sensor network, and cluster routing method based on the system
CN101237345A (en) * 2007-12-04 2008-08-06 奇瑞汽车有限公司 A network management method for CAN bus
CN102195769A (en) * 2011-06-02 2011-09-21 合肥工业大学 Clock synchronization method for automobile CAN (Control Area Network)
CN103139011A (en) * 2011-11-30 2013-06-05 通用汽车环球科技运作有限责任公司 Integrated fault diagnosis and prognosis for in-vehicle communications
CN102658801A (en) * 2012-04-28 2012-09-12 浙江吉利汽车研究院有限公司杭州分公司 Controller area network (CAN) system network management method for new energy vehicle
CN103607297A (en) * 2013-11-07 2014-02-26 上海爱数软件有限公司 Fault processing method of computer cluster system
CN104135391A (en) * 2014-08-19 2014-11-05 北京汽车股份有限公司 Management method and device for vehicle-mounted CAN partial networking
CN105611503A (en) * 2015-12-30 2016-05-25 东软集团股份有限公司 Information communication method and system in in-vehicle network environment
CN106254250A (en) * 2016-08-03 2016-12-21 成都之达科技有限公司 Car networking short-distance networking method
CN107817779A (en) * 2016-09-12 2018-03-20 现代自动车株式会社 The system and method for the unregistered device of Information Authentication based on Ethernet switch
CN109104351A (en) * 2017-06-21 2018-12-28 比亚迪股份有限公司 Train network node and train network node monitoring method based on CANopen agreement
CN206932240U (en) * 2017-08-01 2018-01-26 风度(常州)汽车研发院有限公司 Vehicle-mounted ethernet communication system and intelligent automobile
CN109787795A (en) * 2017-11-13 2019-05-21 比亚迪股份有限公司 Processing method, node and the electronic equipment of train network host node failure
CN110086622A (en) * 2018-01-25 2019-08-02 南京汽车集团有限公司 In-vehicle network security architecture designs under a kind of intelligent network connection environment
CN108833170A (en) * 2018-06-20 2018-11-16 长春工业大学 A kind of network level adaptation CAN bus method for diagnosing faults
CN109263581A (en) * 2018-11-08 2019-01-25 湖北汽车工业学院 A kind of real-time commitment method for automatic driving vehicle
CN109756407A (en) * 2019-01-17 2019-05-14 重庆菲斯塔新能源汽车科技有限公司 A kind of CAN bus based localized network management method
CN109981473A (en) * 2019-02-15 2019-07-05 浙江吉利汽车研究院有限公司 A kind of real-time messages bus system
CN111447126A (en) * 2019-12-05 2020-07-24 炬星科技(深圳)有限公司 Ethernet bus communication method, device, robot, equipment and computer readable storage medium
CN111294845A (en) * 2020-02-13 2020-06-16 世纪龙信息网络有限责任公司 Node switching method and device, computer equipment and storage medium
CN111891181A (en) * 2020-06-23 2020-11-06 株洲中车时代电气股份有限公司 Train network control system based on Ethernet
CN111532227A (en) * 2020-07-02 2020-08-14 深圳市法拉第电驱动有限公司 CAN network management method and system for electric vehicle controller
CN111781917A (en) * 2020-07-03 2020-10-16 华人运通(江苏)技术有限公司 Fault data processing method, domain controller and automobile
CN112131572A (en) * 2020-08-31 2020-12-25 华为技术有限公司 Control method of vehicle-mounted equipment, vehicle-mounted equipment and vehicle system
CN112087351A (en) * 2020-09-24 2020-12-15 山东交通学院 Remote train network communication interface testing method
CN112291194A (en) * 2020-09-27 2021-01-29 上海赫千电子科技有限公司 State management method and device based on ECU in vehicle-mounted network and intelligent automobile
CN112181660A (en) * 2020-10-12 2021-01-05 北京计算机技术及应用研究所 High-availability method based on server cluster
CN111935325A (en) * 2020-10-15 2020-11-13 广州汽车集团股份有限公司 OTA (over the air) upgrading method and device
CN112272366A (en) * 2020-10-27 2021-01-26 吉林大学 Automobile emergency information communication method based on block chain

Similar Documents

Publication Publication Date Title
CN108833122B (en) Wake-up method and device for vehicle-mounted communication controller and storage medium
CN105388858B (en) Method of operating a communication node in a network
US11368404B2 (en) Method of releasing resource reservation in network
CN107690149B (en) Method for triggering network policy update, management function entity and core network equipment
US8832053B2 (en) Relay device, communication system and communication method
CN107453895B (en) Method for configuring a communication path and first communication node forming a vehicle network
CN112578764A (en) Vehicle fault diagnosis method and system and vehicle
CN106341433A (en) Service system, signal server and intercom server
CN114978875A (en) Vehicle-mounted node management method and device and storage medium
EP3968665B1 (en) Wireless communication device, wireless communication system, and wireless communication method
JP2020086522A (en) On-vehicle system
WO2022001665A1 (en) Communication method for vehicle-mounted device, vehicle-mounted device, storage medium, and electronic apparatus
US11171806B1 (en) Dynamic quality of service control for automotive ethernet
WO2017149567A1 (en) Communication device
EP3992778A1 (en) A computer-implemented method for transferring ota data to a fleet of vehicles, a backend server, a transportation system
CN110677466A (en) Application program downloading method, device, gateway and storage medium
CN113162796A (en) Equipment updating method, device and equipment updating system
CN113377393A (en) Diagnosis refreshing system and method for vehicle-mounted system main node
JP2019129512A (en) On-vehicle relay device, relay method, information processing device, information processing system, and vehicle
CN111741532B (en) Terminal and data transmission method thereof
CN115499791B (en) Service-oriented communication method, device, electronic equipment and storage medium
WO2023119720A1 (en) Transfer apparatus
CN116248775A (en) Interaction method and device of DDS gateway, electronic equipment and storage medium
JP6812765B2 (en) Electronic control device
CN117560236A (en) Communication method, system, vehicle terminal and readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination