CN116193472B - Vehicle-mounted network management method and device, electronic equipment and storage medium - Google Patents

Vehicle-mounted network management method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN116193472B
CN116193472B CN202211715408.8A CN202211715408A CN116193472B CN 116193472 B CN116193472 B CN 116193472B CN 202211715408 A CN202211715408 A CN 202211715408A CN 116193472 B CN116193472 B CN 116193472B
Authority
CN
China
Prior art keywords
message
pnc
gateway
ecu
wake
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.)
Active
Application number
CN202211715408.8A
Other languages
Chinese (zh)
Other versions
CN116193472A (en
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 CN202211715408.8A priority Critical patent/CN116193472B/en
Publication of CN116193472A publication Critical patent/CN116193472A/en
Application granted granted Critical
Publication of CN116193472B publication Critical patent/CN116193472B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/48—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for in-vehicle communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • Y—GENERAL 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE 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/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

The application provides a vehicle-mounted network management method, a device, electronic equipment and a storage medium, wherein the method comprises the following steps: sending a first message based on a network segment of the gateway so that an ECU (electronic control unit) positioned in the network segment registers a PNC (network management center) after receiving the first message; receiving a second message returned by the ECU after the PNC registration is completed, wherein the second message comprises PNC information registered by the corresponding ECU; different PNC information corresponds to different PNCs, wherein the PNC information is preset for the PNC where the corresponding ECU is located; and associating the ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC. The technical scheme of the embodiment of the application is beneficial to the change and expansion of the ECU, and can improve the efficiency of vehicle-mounted network management.

Description

Vehicle-mounted network management method and device, electronic equipment and storage medium
Technical Field
The present invention relates to the field of vehicle-mounted network technologies, and in particular, to a vehicle-mounted network management method, device, electronic equipment, and storage medium.
Background
As the usage scenarios and functions of vehicles increase, the number of controller ECU (Electronic Control Unit ) inside the vehicles increases, and the vehicle-mounted network architecture becomes more complex. The vehicle-mounted network of the traditional distributed controller architecture gradually does not meet the design requirement of the whole vehicle, and new forms of vehicle-mounted networks based on the central domain controller and regional controller architecture and the like are gradually evolved. The new vehicle network form generally represents a multi-level network structure and a convergence of various communication protocols, such as LIN (Local Interconnect Network, local area network)/CAN (Controller Area Network ) and the like.
The current vehicle-mounted network management strategy is generally designed into a fixed wake-up strategy, wherein the fixed wake-up strategy cannot be changed after the whole vehicle software is frozen, and the fixed wake-up strategy comprises various strategies such as a whole network wake-up strategy, PNC (Partial Network Cluster-virtual local network) network management and the like. When any wake-up event occurs, an event source ECU (controller) wakes up the whole vehicle and the whole network, and the wake-up nodes are not distinguished according to the function requirement; while PNC network management designs a plurality of PNCs in advance according to a functional scenario, each PNC includes network channels of a plurality of ECUs in the whole vehicle, when network wakeup is performed, only selected network channels for waking up the ECUs in a specific PNC are needed, but the strategy generally needs to set all PNCs and network wakeup paths in advance according to a functional list and a usage scenario in the whole vehicle design stage, then the set PNCs and network wakeup paths are written into a vehicle-mounted network, once network structure or function change is needed, if the ECU in a certain PNC is added or reduced, the related PNCs and wakeup paths need to be manually changed and designed again, and then the changed PNCs and wakeup paths are written into the vehicle-mounted network, which is not beneficial to the change and expansion of the ECU, and the workload of vehicle-mounted network management is greatly increased.
Disclosure of Invention
To solve the above technical problems, embodiments of the present application provide a vehicle-mounted network management method and apparatus, an electronic device, a computer readable storage medium, and a computer program product.
According to an aspect of the embodiments of the present application, there is provided a vehicle-mounted network management method, applied to a gateway, the method including: sending a first message based on a network segment of the gateway so that an ECU (electronic control unit) positioned in the network segment registers a PNC (network management center) after receiving the first message; receiving a second message returned by the ECU after the PNC registration is completed, wherein the second message comprises PNC information registered by the corresponding ECU; different PNC information corresponds to different PNCs, wherein the PNC information is preset for the PNC where the corresponding ECU is located; and associating the ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC.
In an embodiment, before associating the ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC, the method further includes:
transmitting a registration response based on a network segment of the gateway to count the number of registered ECUs in the network segment for which PNC registration has been performed;
If the number of the registered ECUs corresponding to the registration response is smaller than the number of ECUs in the network segment, the network segment based on the gateway is executed again to send a first message, so that the ECUs in the network segment of the gateway register PNC after receiving the first message;
and if the number of the registered ECUs corresponding to the registration response is not less than the number of ECUs in the network segment, executing the step of associating ECUs with the same PNC information in the second message to form a wake-up path under the corresponding PNC.
In an embodiment, the network segment of the gateway further comprises a sub-gateway, and the network segment where the sub-gateway is located comprises a sub-ECU; the gateway-based network segment sends a first message so that an ECU (electronic control unit) located in the network segment registers a PNC (network management center) after receiving the first message, and the method comprises the following steps:
and sending a first message based on the network segment of the gateway, so that the sub-gateway positioned in the network segment sends a third message to the sub-ECU of the sub-gateway after receiving the first message, and the sub-ECU carries out PNC registration after receiving the third message.
In an embodiment, before the gateway-based network segment sends the first message, so that the ECU located in the network segment performs PNC registration after receiving the first message, the method further includes:
And if the ECU in the gateway is required to be updated, receiving a registration notification, and executing the step of sending a first message based on the network segment of the gateway after receiving the registration notification so that the ECU in the network segment of the gateway carries out PNC registration after receiving the first message.
According to an aspect of the embodiments of the present application, there is provided an in-vehicle network management method applied to an ECU, the method including: receiving a first message sent by a gateway; generating an initial second message based on the first message; setting the registered PNC information in the initial second message to obtain a second message; wherein different PNC information corresponds to different PNCs; and sending the second message to the gateway so that the gateway associates ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC.
In an embodiment, after the sending the second message to the gateway so that the gateway associates ECUs with the same PNC information according to the second message to form a wake-up path under a corresponding PNC, the method includes:
receiving a wake source indicating a wake target PNC;
And sending a wake-up message to the gateway according to a target wake-up path where the ECU is located, so that the gateway enables all ECUs under the target PNC to be based on the target wake-up path.
According to an aspect of an embodiment of the present application, there is provided an in-vehicle network management apparatus configured on a gateway, the apparatus including: the first message sending module is configured to send a first message based on a network segment of the gateway so that an ECU (electronic control unit) positioned in the network segment can register a PNC (network management center) after receiving the first message; the second message receiving module is configured to receive a second message returned by the ECU after the PNC registration is completed, wherein the second message comprises PNC information registered by the corresponding ECU; different PNC information corresponds to different PNCs, wherein the PNC information is preset for the PNC where the corresponding ECU is located; and the wake-up path configuration module is configured to associate ECUs with the same PNC information according to the second message to form wake-up paths under the corresponding PNCs.
According to an aspect of the embodiments of the present application, there is provided an in-vehicle network management apparatus configured on an ECU, the apparatus including: the first message receiving module is configured to receive a first message sent by the gateway; an initial second message generation module configured to generate an initial second message based on the first message; the second message generating module is configured to set the registered PNC information in the initial second message to obtain a second message; wherein different PNC information corresponds to different PNCs; and the second message sending module is configured to send the second message to the gateway so that the gateway associates ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC.
According to one aspect of embodiments of the present application, there is provided an electronic device comprising one or more processors; and storage means for storing one or more computer programs which, when executed by the one or more processors, cause the electronic device to implement the method of in-vehicle network management as described above.
According to an aspect of the embodiments of the present application, there is provided a computer-readable storage medium having stored thereon computer-readable instructions, which when executed by a processor of a computer, cause the computer to perform the in-vehicle network management method as described above.
According to an aspect of embodiments of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the in-vehicle network management method provided in the above-described various alternative embodiments.
According to an aspect of embodiments of the present application, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the steps of the in-vehicle network management method as described above.
In the technical scheme provided by the embodiment of the application, the self-adaptive generation of the PNC wake-up path in the vehicle-mounted network can be completed through the message interaction between the gateway and the ECU, the related PNC and wake-up path are not required to be manually changed and designed, and the changed PNC and wake-up path are written into the vehicle-mounted network, so that the change and expansion of the ECU are facilitated, and the vehicle-mounted network management is efficiently realized.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. It is apparent that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art. In the drawings:
FIG. 1A is a schematic illustration of one implementation environment to which the present application relates;
FIG. 1B is a schematic illustration of another implementation environment to which the present application relates;
FIG. 2 is a flow chart of an in-vehicle network management method shown in an exemplary embodiment of the present application;
Fig. 3 is a schematic structural diagram of an NM message according to an exemplary embodiment of the present application;
FIG. 4 is a flow chart of step S210 in the embodiment shown in FIG. 2 in an exemplary embodiment;
FIG. 5 is a flow chart of an in-vehicle network management method shown in another exemplary embodiment of the present application;
FIG. 6 is a flow chart of an in-vehicle network management method shown in another exemplary embodiment of the present application;
fig. 7 is a schematic view of a management structure of an in-vehicle network shown in an exemplary embodiment of the present application;
fig. 8 is a schematic structural view of an in-vehicle network management apparatus shown in an exemplary embodiment of the present application;
fig. 9 is a schematic structural view of an in-vehicle network management device shown in another exemplary embodiment of the present application;
fig. 10 shows a schematic diagram of a computer system suitable for use in implementing the electronic device of the embodiments of the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
Also to be described is: reference to "a plurality" in this application means two or more than two. "and/or" describes an association relationship of an association object, meaning that there may be three relationships, e.g., a and/or B may represent: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
Referring first to fig. 1A and 1B, fig. 1A and 1B are schematic diagrams of an implementation environment according to the present application. The implementation environment may rely on blockchain technology.
Specifically, for the implementation environment in fig. 1A, it is a schematic structural diagram in the vehicle network, and specifically includes a central gateway 101A, a plurality of regional gateways 102A and a plurality of ECUs 103A, where the central gateway 101A may be communicatively connected to the regional gateways 102A and the plurality of ECUs 103A through its network segments, and each regional gateway 102A may also be communicatively connected to the plurality of ECUs 103A through its network segments, that is, the central gateway 101A may be connected to the regional gateways 102A and the ECUs 103A in a downlink manner, and the regional gateways may be connected to the ECUs 103A in a downlink manner.
It should be understood that the number of regional gateways 102A and ECUs 103A in fig. 1A is merely illustrative. There may be any number of regional gateways 102A and ECU103A as desired.
In some embodiments of the present application, the vehicle network management method is completed by the structure in fig. 1A, when vehicle network management is required, the central gateway 101A sends an NM (network management) message to the regional gateway 102A and the ECU103A subordinate thereto through its own network segment, so as to inform the regional gateway 102A subordinate thereto and the ECU103A to perform PNC registration, where, of course, the central gateway 101A sends only the NM message to the ECU103A subordinate thereto and does not send the NM message to the ECU103A subordinate thereto of the regional gateway 102A, and after receiving the NM message sent by the central gateway, the regional gateway 102A sends the NM message to the ECU103A subordinate thereto of each regional gateway 102A, so as to notify the ECU103A subordinate thereto of the regional gateway 102A to perform PNC registration, and at this time, the ECUs in the whole vehicle network all start PNC registration.
Of course, after sending NM messages, the central gateway 101A and the regional gateway 102A start to count the registration Time (Register Time), in the registration Time, they receive NM messages returned by the ECU103A under each gateway, and when the registration Time is completed, return registration responses (Register Response) to each network segment, count the number of ECUs 103A that perform PNC registration under each gateway, and of course, after the regional gateway 102A counts the number, return the data of registration response statistics to the central gateway 101A, and meanwhile, return the data of registration response statistics of each gateway to the network segment where each gateway is located, so that an engineer can determine whether the ECU in the whole vehicle-mounted network is completed based on the network segment detection registered data.
After receiving the NM message sent by the gateway, each ECU103A sets related information in the respective NM message, for example, sets corresponding PNC information in the NM message, where the PNC information is used to indicate to which PNC each ECU103A will belong, one PNC information corresponds to a different PNC, the PNC information set in the ECU103A is preset, and one ECU103A may set multiple PNC information, which indicates that the ECU103A is located in multiple PNCs, after the ECU103A sets its NM message, the NM message is returned to the upper gateway central gateway 101A or the regional gateway 102A, after receiving the NM message returned by its lower ECU103A, the regional gateway 102A also sends the NM message returned by the ECU103A to the central gateway, so, the central gateway receives the NM message returned by the ECU in the vehicle network, and at the same time, the central gateway determines whether all the PNCs return the PNC messages based on the data of the registration response, if so, the corresponding wake-up paths of the PNC information of all the PNCs returned by all the ECU can be formed, and the subsequent PNCs can be associated with the corresponding PNC information of the subsequent PNC of the ECU returns on the subsequent PNC path. Of course, if it is determined that not all the ECUs have returned the NM message, the central gateway will issue the NM message again at this time, and prompt to re-register the PNC.
When the PNC in the vehicle network performs table updating, if an ECU needs to be added or deleted in a certain PNC, at this time, only PNC information in the changed ECU needs to be set, then the central gateway 101A issues the NM message by itself, and the PNC registration of the vehicle network is performed again to obtain a new wake-up path, so that the related PNC and wake-up path are not required to be changed and designed, and then the changed PNC and wake-up path are written into the vehicle network, which is beneficial to changing and expanding functions in the vehicle network, and effectively reduces management and design workload of the vehicle network.
Specifically, for the implementation environment in fig. 1B, it is a schematic structural diagram in the vehicle network, specifically including the regional gateway 102B and the multiple ECUs 103B, where the regional gateway 102B is also connected to the multiple ECUs 103B by a network segment for communication.
It should be understood that the number of regional gateways 102B and ECUs 103B in fig. 1B is merely illustrative. There may be any number of regional gateways 102B and ECU103B as practical.
In some embodiments of the present application, the vehicle network management method is completed by the structure in fig. 1B, when vehicle network management is required, the regional gateway 102B sends an NM message to the subordinate ECU103B of each regional gateway 102B, and notifies the subordinate ECU103B of the regional gateway 102B to perform PNC registration, where the ECUs in the entire vehicle network start to perform PNC registration.
Referring to the processing procedure of the implementation environment in fig. 1A, after sending the NM message, the regional gateway 102B also starts to count the registration Time (Register Time), in the registration Time, it receives the NM message returned by the ECU103B under each of the regions, and returns a registration response (Register Response) to the network segment when the registration Time is completed, counts the number of ECUs 103B performing PNC registration under each gateway, and if the value returned by the registration response indicates that all the ECUs under the gateway have returned NM messages, i.e. performed PNC registration, the gateway generates wake-up paths under different PNCs based on the NM message returned by the ECU103B, otherwise, re-issues the NM message through the regional gateway to perform PNC registration of each ECU.
The NM message returned by the ECU103B includes corresponding PNC information, where the PNC information is used to indicate to which PNC each ECU103B will belong, one PNC information corresponds to a different PNC, PNC information set in the ECU103B is preset, and one ECU103B may set multiple PNC information, which indicates that the ECU103B is located in multiple PNCs, and when the subsequent regional gateway receives the NM message returned by the ECU103B, the ECU with the same PNC information may associate based on the PNC information in the NM message, so as to form a wake-up path under the corresponding PNC, and the ECU under the target PNC may be subsequently woken up through the wake-up path.
When the PNC in the vehicle network performs table updating, if an ECU needs to be added or deleted in a certain PNC, at this time, only PNC information in the changed ECU needs to be set, then the regional gateway 102B issues the NM message by itself, and the PNC registration of the vehicle network is performed again to obtain a new wake-up path, so that the related PNC and wake-up path are not required to be changed and designed, and then the changed PNC and wake-up path are written into the vehicle network, which is beneficial to changing and expanding functions in the vehicle network, and effectively reduces management and design workload of the vehicle network.
The central gateway 101A, the regional gateway 102A, and the regional gateway 102B may be independent physical servers disposed in a vehicle-mounted network, or may be cloud servers that provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content delivery networks), and basic cloud computing services such as big data and artificial intelligence platforms, which are not limited herein. The ECU103A, ECU B is an electronic control unit that is installed in the in-vehicle network and that can realize a certain function alone in combination.
It should be noted that this embodiment is only an exemplary implementation environment provided for the convenience of understanding the concepts of the present application, and should not be construed as providing any limitation on the scope of use of the present application.
Fig. 2 is a flowchart illustrating an on-vehicle network management method according to an exemplary embodiment, which is applicable to the central gateway 102A of fig. 1A and the regional gateway 102B of fig. 1B, and it should be understood that the method may also be used in other exemplary implementation environments and be specifically executed by devices in other implementation environments, and the embodiment is not limited to the implementation environment to which the method is applicable.
In an exemplary embodiment, the method may include steps S210 to S250, which are described in detail as follows:
step S210: and the gateway-based network segment transmits a first message so that the ECU located in the network segment can register the PNC after receiving the first message.
In this embodiment, when the wake-up path is divided for the first time for the ECU in the vehicle-mounted network or the functional structure in the vehicle-mounted network is changed (for example, a PNC in the original wake-up path needs to be added or deleted with one ECU), at this time, a registration notification is sent to the gateway, so that the gateway sends a first message to the network segment where the gateway is located, and notifies the subordinate ECU of the gateway to perform PNC registration.
The first message is an NM message, the NM message may refer to fig. 2, where the NM message includes a plurality of fields, different fields correspond to different contents, such as NM ID (NM message ID), PNC Register Request (PNC registration request), PNC Type (PNC Type), PNC Info (PNC information), PNC Register Response (PNC registration response), etc., and the contents of the NM messages sent by different devices set in each field are different, for example, PNC Register Request may be used for the gateway to send PNC registration notification to the subordinate ECU, or may be used to indicate PNC registration request of the subordinate ECU; and the first message PNC Register Request sent by the gateway is set to indicate that all the lower-level ECUs are notified to perform PNC registration, and start timing Register Time.
After receiving the first message, the ECU performs PNC registration in a Register Time, sets PNC related information into the NM message of the ECU to obtain a second message with PNC information, and returns the second message to the gateway after PNC registration is completed.
Step S230: and receiving a second message returned by the ECU after the PNC registration is completed, wherein the second message comprises PNC information registered by the corresponding ECU.
In this embodiment, the second message is also an NM message, unlike the first message, which is an NM message sent by the ECU, specifically, the ECU sets PNC Register Request in the NM message itself, which indicates that PNC registration is performed, a PNC Type value corresponding to PNC Type set, and sets a position corresponding to a PNC to be registered in PNC Info, so that multiple PNCs may be registered simultaneously.
The PNC Type value set by the PNC Type is the role played by the ECU in the corresponding PNC network, and the selectable values of the PNC Type are M (Member), W (Waker and Member) and WM (Waker and Member), wherein M represents that the ECU can only be awakened by other ECUs in the PNC network where the ECU is located, but the ECU cannot actively awaken the PNC network; w represents that the ECU can only actively wake up the PNC network where the ECU is located and cannot be woken up by other ECUs in the PNC network; WM stands for the ECU that can either actively wake up the PNC in which it is located or can be woken up by other ECUs in the corresponding PNC network.
Specifically, after the wake-up path in the PNC Type identifier vehicle-mounted network is fixed, if the ECU can wake up the corresponding PNC network, that is, if the PNC Type of the ECU is M or WM, the PNC network where the ECU is located can be woken up by the ECU, and if the PNC Type of the ECU is W, the PNC network where the ECU is located can not be woken up by the ECU, and only the PNC network can be woken up by the ECU where other PNC types in the PNC network are M or WM.
PNC Info is PNC information, which indicates that the PNC network where the ECU is located, different PNCs can be represented by different PNC information, and the PNC where one ECU is located is obtained by presetting, if the PNC is to be divided into PNC1 with the ECU1, PNC information corresponding to the PNC1 is preset in the ECU1, and in addition, information set in PNC Type is also the Type played by the ECU1 in the PNC 1.
Of course, one ECU may preset multiple PNC information, that is, one ECU may be in multiple PNCs, for example, for ECU1, it is preset in PNC1 and PNC2, and when PNC Info is set, this ECU1 sets PNC information for identifying PNC1 and PNC2 corresponding to PNC information, and of course, PNC Type may also set PNC types under different PNCs, and PNC types in PNC1 and PNC2 of ECU1 may be the same or different.
After setting related information in the NM message, the ECU obtains a second message, and then sends the second message to the gateway, and the processes of PNC registration and second message sending by the ECU are completed in a Register Time: after the Register Time arrives, the gateway returns Register Response to the network segment, counts the number of the second messages received, namely the number of registered ECUs for completing PNC registration, and when the number of the registered ECUs is smaller than the number of the lower ECUs of the gateway, the gateway proves that one ECU does not Register PNC, at the moment, the gateway needs to send the first message again, and the ECUs in the vehicle-mounted network Register PNC again.
Of course, the gateway returns Register Response to the network segment, so that the engineer can detect whether the ECUs in the vehicle-mounted network are all registered by the PNC through the network segment, and if the ECUs are different, a registration notification is sent to the gateway, and the gateway is notified to resend the first message.
Step S250: and associating the ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC.
If the number of the registered ECUs is not less than the number of the subordinate ECUs of the gateway, the gateway finds ECUs with the same PNC information according to the second message of the ECUs, and associates the ECUs with the PNC information, so that wake-up paths under different PNCs are generated according to the information.
Of course, there may be a case where the number of registered ECUs is greater than the number of subordinate ECUs of the gateway, and at this time, a problem occurs in the data transmission process in the vehicle-mounted network, the gateway should be notified to resend the first message, and the ECU should be notified to perform PNC registration.
After the gateway obtains the wake-up paths of different PNCs, related data are sent to the network segment where the gateway is located, and after a certain PNC needs to be subsequently awakened, the PNC can be awakened through the network segment and the wake-up paths of the PNC in the gateway.
In this embodiment, through the message interaction between the gateway and the ECU, the adaptive generation of the PNC wake-up path in the vehicle network can be completed, when the vehicle network function is changed, the related PNC and wake-up path are not required to be changed and designed again by manpower, the changed PNC and wake-up path are written into the vehicle network, the gateway issues the first message, and the message interaction between the gateway and the ECU completes the generation of the new wake-up path.
Fig. 4 is a flowchart of step S210 in an exemplary embodiment in the embodiment shown in fig. 2. As shown in fig. 4, in an exemplary embodiment, the network segment of the gateway further includes a sub-gateway, where the network segment where the sub-gateway is located includes a sub-ECU; step S210 of sending a first message based on the network segment of the gateway, so that the process of PNC registration by the ECU located in the network segment after receiving the first message may include step S410, which is described in detail below:
step S410: the gateway-based network segment sends a first message, so that a sub-gateway positioned in the network segment sends a third message to a sub-ECU of the sub-gateway after receiving the first message, and the sub-ECU performs PNC registration after receiving the third message.
In this embodiment, if the network segment of the gateway further includes a sub-gateway, the structure of the vehicle network may refer to fig. 1A, that is, the gateway is a central gateway, the sub-gateway is an area gateway, the lower level of the central gateway includes an area gateway in addition to the ECU, and the lower level of the area gateway includes the ECU.
When the vehicle-mounted network management is carried out in the vehicle-mounted network, the gateway still sends a first message to the network segment, the lower-level ECU in the gateway carries out PNC registration after receiving the first message, and the sub-gateway sends a third message to the lower-level ECU (sub-ECU) of the sub-gateway through the network segment of the sub-gateway after receiving the first message, wherein the third message is similar to the first message, and PNC Register Request in the third message is set to inform all the lower-level ECUs of the third message to carry out PNC registration, and meanwhile, the timing Register Time is started.
Of course, when the gateway issues the first message, the gateway also counts the Register Time, and the Register Time indicates the Time limit Time from the gateway to send the PNC registration notification to the subordinate ECU to finish the PNC registration, the gateway and the subordinate ECU thereof must finish the handshake interaction of the PNC registration process during this period, otherwise the PNC registration is incomplete or fails; in the structure with the sub-gateway, the sub-gateway also sends the Register Time when sending the third message, in this process, the sub-ECU of the sub-gateway returns the NM message to the sub-gateway, and then the sub-gateway sends the NM message of the sub-ECU to the gateway, so the Register Time of the gateway should start before the Register Time of each sub-gateway.
After the sub-gateway sends a third message to the sub-ECU of the sub-gateway, the sub-ECU performs PNC registration, the registration process may refer to fig. 2, which is the same as the ECU registration process of the gateway, after the sub-ECU performs PNC registration again, the sub-gateway returns the NM message with the related PNC information to the sub-gateway, after the sub-gateway finishes its own Register Time, the sub-ECU also returns Register Response to count the number of registered sub-ECUs of the sub-gateway performing PNC registration, and after the Register Time of the gateway finishes, the sub-ECU number of registration counted by the sub-gateway is returned to the gateway, so that the gateway determines whether all ECUs in the vehicle network have completed PNC registration based on the number of registered ECUs counted by the gateway and the number of registered sub-ECUs, after determining that the PNC registration is completed, the related result is still sent to the network segment, after the sub-gateway receives the related information, the related result is also sent to the network segment of the sub-gateway, and the wake-up of the corresponding PNC can be completed based on the wake-up path by the network segment of the gateway, the sub-gateway and the sub-gateway.
Of course, only PNC registration of the sub-ECU is shown in fig. 4, as in the scheme proposed in fig. 2-3, after the gateway is actually used to send the first message, the subordinate ECU located under the gateway performs PNC registration, which is not shown in fig. 4, and the specific step of PNC registration by the gateway subordinate ECU may refer to the embodiment shown in fig. 2, or refer to the above description, and at the same time, the second message returned by the ECU in step S230 in fig. 4 includes the second message returned by the subordinate ECU under the gateway and the second message of the sub-ECU forwarded by the sub-gateway, and at the same time, the gateway should perform simultaneous operation on the sub-ECU and the subordinate ECU of the gateway when performing ECU association, that is, there may be the subordinate ECU of the sub-ECU and the gateway in a wake-up path.
In this embodiment, it is proposed that, when a multistage architecture exists in the vehicle-mounted network, adaptive generation of a PNC wake-up path in the complex vehicle-mounted network can be completed by means of step-by-step transmission of messages for interaction.
Fig. 5 is a flowchart illustrating a method of in-vehicle network management according to another exemplary embodiment. The vehicle-mounted network management method can be applied to the ECU103A in FIG. 1A and the ECU 103B in FIG. 1B
It should be understood that the method may be used in other exemplary implementation environments and be specifically executed by devices in other implementation environments, and the implementation environments to which the method is applicable are not limited by the present embodiment.
As shown in fig. 5, in an exemplary embodiment, the method may include steps S510 to S570, described in detail below:
step S510: and receiving a first message sent by the gateway.
The embodiment shown in fig. 5 belongs to the same concept as the embodiment shown in fig. 2, specifically, when the wake-up path is divided for the first Time for the ECU in the vehicle-mounted network or the functional structure in the vehicle-mounted network is changed (for example, a PNC in the original wake-up path needs to be added or deleted, and one ECU), at this Time, a registration notification is sent to the gateway, so that the gateway sends a first message to the network segment where the gateway is located, and after receiving the first message, the ECU starts PNC registration, and starts timing Register Time.
Step S530: an initial second message is generated based on the first message.
In this embodiment, after receiving the first message, the ECU generates an initial second message, that is, an NM message with the structure shown in fig. 3, where relevant information in the NM message is not yet set.
Step S550: and setting the registered PNC information in the initial second message to obtain the second message.
In this embodiment, the ECU sets PNC Register Request in the initial second message, which indicates that PNC registration is performed, PNC Type value corresponding to PNC Type setting, PNC information corresponding to PNC Info setting, multiple PNC information can be set by the same ECU, different PNC information corresponds to different PNCs, and each ECU sets PNC related information preset by itself in the initial second message, so as to obtain the second message.
Step S570: and sending the second message to the gateway so that the gateway associates the ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC.
The ECU sends respective second messages to the gateway through the network segment, the gateway returns Register Response to the network segment after the Register Time is finished, the number of registered ECUs which finish PNC registration is counted, when the number of registered ECUs is smaller than the number of lower ECUs of the gateway, one ECU is proved to be not subjected to PNC registration, at the moment, the gateway needs to issue the first message again, otherwise, the gateway finds ECUs with the same PNC information according to the second messages of the ECUs, associates the ECUs with the PNC information, and generates wake-up paths under different PNCs according to the information, so that the vehicle-mounted network can wake up the corresponding PNCs and ECUs under the PNCs through the wake-up paths.
In the embodiment, through message interaction between the gateway and the ECU, when the vehicle-mounted network is changed or designed, the self-adaptive generation of the PNC wake-up path in the vehicle-mounted network can be completed.
Fig. 6 is a flowchart illustrating a method of in-vehicle network management according to another exemplary embodiment. As shown in fig. 6, in an exemplary embodiment, after the method is implemented in step S570 of fig. 5, the method may specifically include steps S610 to S630, which are described in detail as follows:
step S610: a wake source is received indicating a wake target PNC.
In this embodiment, after the wake-up paths of different PNCs are obtained in the vehicle-mounted network through the embodiment of fig. 5, if a certain ECU in the vehicle-mounted network receives the wake-up source, the target PNC where the ECU is located needs to wake up, that is, all the ECUs under the target PNC need to be woken up.
Of course, if the ECU that receives the wake-up source needs to wake up the target PNC, the PNC Type needs to be M or WM, otherwise, even if the ECU receives the wake-up source, the ECU will not wake up.
Step S630: and sending a wake-up message to the gateway according to a target wake-up path where the ECU is located, so that the gateway enables all ECUs under the target PNC to be based on the target wake-up path.
After receiving the wake-up source, the ECU sends a wake-up message through a network segment between the ECU and the gateway, and the wake-up message arrives at the gateway from the network segment where the ECU is located, as known before, wake-up paths of different PNCs are also stored in the network segment, so that after receiving the wake-up message, if one ECU exists in the target wake-up path (i.e., in the target PNC) and the ECU sending the wake-up message belong to the same network segment, the ECU also receives the wake-up message sent by the network segment and is then woken up.
The gateway is awakened after receiving the awakening message, and meanwhile, the awakening message is forwarded to the ECUs which do not belong to a network segment with the ECUs sending the awakening message based on the target awakening path, at the moment, the ECUs under the target PNC in other network segments are awakened, and thus, all the ECUs under the target PNC are awakened.
Referring to fig. 7, in an embodiment, a management structure diagram of a vehicle network is shown, in the network, there are 8 nodes including a gateway and ECU1 to ECU7, NET1, NET2, and NET3 are network segments, where ECU1, ECU2, and ECU6 belong to PNC1, in an original wake-up path, all ECU1 needing to wake up PNC1 appear a wake-up source, ECU1 sends out an NM wake-up message, and after receiving the wake-up message with ECU1, ECU2 located in the same network segment is woken up, meanwhile, the wake-up message reaches the gateway through NET1, after receiving the wake-up message, the gateway is woken up, then forwards the wake-up message to NET3 based on the wake-up path of PNC1, and ECU6 on NET3 is woken up similarly after receiving NET 3. Up to this point, the ECU1, the ECU2, and the ECU6 in the PNC1 are all successfully awakened.
In a specific embodiment, if the new ECU4 needs to be added to the PNC1 in fig. 7, the wake-up path needs to be regenerated by the method shown in fig. 2 to 5, first, the gateway sends the first message to each of NET1, NET2 and NET3, after the ECU in NET1, NET2 and NET3 receives the first message, the second messages returned by each of ECU1, ECU2, ECU4 and ECU6 include PNC information corresponding to PNC1, after Register Time is reached, the gateway updates the wake-up path according to all the received second message information, and then, the ECU1, ECU2, ECU4 and ECU6 can be set in the wake-up path under PNC1, for example, when the ECU1 again wakes up the PNC1, the gateway forwards the wake-up message to each of NET2 and NET3, and wakes up both ECU6 and ECU 4.
In this embodiment, a PNC wake-up mode in a vehicle-mounted network is provided, so that all ECUs of the vehicle-mounted network do not need to work together to realize a certain function, and the power consumption of the whole vehicle is effectively reduced while the vehicle-mounted function is realized based on the PNC.
Fig. 8 is a schematic structural diagram of an in-vehicle network management apparatus according to an exemplary embodiment.
As shown in fig. 8, in an exemplary embodiment, the in-vehicle network management device is configured on a gateway, and includes:
A first message sending module 810, configured to send a first message based on a network segment of the gateway, so that an ECU located in the network segment performs PNC registration after receiving the first message;
a second message receiving module 830, configured to receive a second message returned by the ECU after the PNC registration is completed, where the second message includes PNC information registered by the corresponding ECU; different PNC information corresponds to different PNCs, and the PNC information is preset for the PNC where the corresponding ECU is located;
the wake-up path configuration module 850 is configured to associate the ECUs with the same PNC information according to the second message, so as to form a wake-up path under the corresponding PNC.
The vehicle-mounted network management device provided by the embodiment can be used for self-adaptive PNC vehicle-mounted network management, is beneficial to the whole vehicle network change design and function update expansion, and saves design workload.
In an embodiment, the in-vehicle network management apparatus further includes:
a registration ECU number acquisition module configured to send a registration response based on the network segment of the gateway to count the number of registration ECUs in the network segment that have performed PNC registration;
the first judging module is configured to execute the step of sending a first message based on the gateway network segment again if the number of the registered ECUs corresponding to the registration response is smaller than the number of ECUs in the network segment, so that the ECUs of the network segment positioned at the gateway register PNCs after receiving the first message;
And the second judging module is configured to execute the step of associating the ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC if the number of the registered ECUs corresponding to the registration response is not less than the number of the ECUs in the network segment.
In an embodiment, the network segment of the gateway further comprises a sub-gateway, and the network segment where the sub-gateway is located comprises a sub-ECU; the first message sending module comprises:
and the sub-gateway receiving unit is configured to send a first message based on the network segment of the gateway, so that the sub-gateway positioned in the network segment sends a third message to the sub-ECU of the sub-gateway after receiving the first message, and the sub-ECU carries out PNC registration after receiving the third message.
In an embodiment, the in-vehicle network management apparatus further includes:
and the updating module is configured to receive the registration notification if the ECU in the gateway is required to be updated, and execute the step of sending a first message based on the gateway network segment after receiving the registration notification so that the ECU in the network segment performs PNC registration after receiving the first message.
Fig. 9 is a schematic structural view of an in-vehicle network management apparatus according to another exemplary embodiment. As shown in fig. 9, in an exemplary embodiment, the in-vehicle network management device is configured on an ECU, and includes:
A first message receiving module 910, configured to receive a first message sent by the gateway;
an initial second message generation module 930 configured to generate an initial second message based on the first message;
a second message generating module 950 configured to set the registered PNC information in the initial second message, to obtain a second message; wherein different PNC information corresponds to different PNCs;
and the second message sending module 970 is configured to send a second message to the gateway, so that the gateway associates the ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC.
In an embodiment, the in-vehicle network management apparatus further includes:
a wake source receiving module configured to receive a wake source indicating a wake target PNC;
and the wake-up module is configured to send a wake-up message to the gateway according to a target wake-up path where the ECU is located, so that the gateway can make all ECUs under the target PNC based on the target wake-up path.
It should be noted that, the vehicle-mounted network management device provided in the foregoing embodiment and the vehicle-mounted network management method provided in the foregoing embodiment belong to the same concept, and a specific manner in which each module and unit perform an operation has been described in detail in the method embodiment, which is not repeated herein.
The embodiment of the application also provides electronic equipment, which comprises: one or more processors; and a storage means for storing one or more programs that, when executed by the one or more processors, cause the electronic device to implement the in-vehicle network management method provided in the above-described respective embodiments.
Fig. 10 shows a schematic diagram of a computer system suitable for use in implementing the electronic device of the embodiments of the present application.
It should be noted that, the computer system 1000 of the electronic device shown in fig. 10 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.
As shown in fig. 10, the computer system 1000 includes a central processing unit (Central Processing Unit, CPU) 1001 which can perform various appropriate actions and processes, such as performing the method in the above-described embodiment, according to a program stored in a Read-Only Memory (ROM) 1002 or a program loaded from a storage section 1008 into a random access Memory (Random Access Memory, RAM) 1003. In the RAM 1003, various programs and data required for system operation are also stored. The CPU 1001, ROM 1002, and RAM 1003 are connected to each other by a bus 1004. An Input/Output (I/O) interface 1005 is also connected to bus 1004.
The following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output portion 1007 including a Cathode Ray Tube (CRT), a liquid crystal display (Liquid Crystal Display, LCD), and a speaker; a storage portion 1008 including a hard disk or the like; and a communication section 1009 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 1009 performs communication processing via a network such as the internet. The drive 1010 is also connected to the I/O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is installed on the drive 1010 as needed, so that a computer program read out therefrom is installed into the storage section 1008 as needed.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising a computer program for performing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 1009, and/or installed from the removable medium 1011. When executed by a Central Processing Unit (CPU) 1001, the computer program performs various functions defined in the system of the present application.
It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with a computer-readable computer program embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by means of software, or may be implemented by means of hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
Another aspect of the present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements an in-vehicle network management method as before. The computer-readable storage medium may be included in the electronic device described in the above embodiment or may exist alone without being incorporated in the electronic device.
Another aspect of the present application also provides a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions so that the computer device performs the in-vehicle network management method provided in the above-described respective embodiments.
The foregoing is merely a preferred exemplary embodiment of the present application and is not intended to limit the embodiments of the present application, and those skilled in the art may make various changes and modifications according to the main concept and spirit of the present application, so that the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A method for managing an on-board network, applied to a gateway, the method comprising:
sending a first message based on a network segment of the gateway so that an ECU (electronic control unit) positioned in the network segment registers a PNC (network management center) after receiving the first message;
receiving a second message returned by the ECU after the PNC registration is completed, wherein the second message comprises PNC information registered by the corresponding ECU; different PNC information corresponds to different PNCs, wherein the PNC information is preset for the PNC where the corresponding ECU is located;
and associating the ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC.
2. The method of claim 1, wherein before associating ECUs with the same PNC information according to the second message to form a wake-up path under a corresponding PNC, the method further comprises:
transmitting a registration response based on a network segment of the gateway to count the number of registered ECUs in the network segment for which PNC registration has been performed;
if the number of the registered ECUs corresponding to the registration response is smaller than the number of ECUs in the network segment, the network segment based on the gateway is executed again to send a first message, so that the ECUs in the network segment of the gateway register PNC after receiving the first message;
And if the number of the registered ECUs corresponding to the registration response is not less than the number of ECUs in the network segment, executing the step of associating ECUs with the same PNC information in the second message to form a wake-up path under the corresponding PNC.
3. The method of claim 1, wherein the network segment of the gateway further comprises a sub-gateway, and the network segment of the sub-gateway comprises a sub-ECU; the gateway-based network segment sends a first message so that an ECU (electronic control unit) located in the network segment registers a PNC (network management center) after receiving the first message, and the method comprises the following steps:
and sending a first message based on the network segment of the gateway, so that the sub-gateway positioned in the network segment sends a third message to the sub-ECU of the sub-gateway after receiving the first message, and the sub-ECU carries out PNC registration after receiving the third message.
4. The method of claim 1, wherein prior to the gateway-based segment sending a first message to cause an ECU located at the segment to perform PNC registration after receiving the first message, the method further comprises:
and if the ECU in the gateway is required to be updated, receiving a registration notification, and executing the step of sending a first message by the network segment based on the gateway after receiving the registration notification so that the ECU in the network segment performs PNC registration after receiving the first message.
5. A vehicle-mounted network management method, characterized by being applied to an ECU, comprising:
receiving a first message sent by a gateway;
generating an initial second message based on the first message;
setting the registered PNC information in the initial second message to obtain a second message; wherein different PNC information corresponds to different PNCs;
and sending the second message to the gateway so that the gateway associates ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC.
6. The method of claim 5, wherein after the sending the second message to the gateway to enable the gateway to associate ECUs with the same PNC information according to the second message to form a wake-up path under a corresponding PNC, the method comprises:
receiving a wake source indicating a wake target PNC;
and sending a wake-up message to the gateway according to a target wake-up path where the ECU is located, so that the gateway wakes up all ECUs under the target PNC based on the target wake-up path.
7. An in-vehicle network management apparatus, disposed on a gateway, comprising:
The first message sending module is configured to send a first message based on a network segment of the gateway so that an ECU (electronic control unit) positioned in the network segment can register a PNC (network management center) after receiving the first message;
the second message receiving module is configured to receive a second message returned by the ECU after the PNC registration is completed, wherein the second message comprises PNC information registered by the corresponding ECU; different PNC information corresponds to different PNCs, wherein the PNC information is preset for the PNC where the corresponding ECU is located;
and the wake-up path configuration module is configured to associate ECUs with the same PNC information according to the second message to form wake-up paths under the corresponding PNCs.
8. An in-vehicle network management apparatus, provided in an ECU, comprising:
the first message receiving module is configured to receive a first message sent by the gateway;
an initial second message generation module configured to generate an initial second message based on the first message;
the second message generating module is configured to set the registered PNC information in the initial second message to obtain a second message; wherein different PNC information corresponds to different PNCs;
and the second message sending module is configured to send the second message to the gateway so that the gateway associates ECUs with the same PNC information according to the second message to form a wake-up path under the corresponding PNC.
9. An electronic device, comprising:
one or more processors;
storage means for storing one or more computer programs which, when executed by the one or more processors, cause the electronic device to implement the method of any of claims 1-6.
10. A computer readable storage medium having stored thereon computer readable instructions which, when executed by a processor of a computer, cause the computer to perform the method of any of claims 1 to 6.
CN202211715408.8A 2022-12-27 2022-12-27 Vehicle-mounted network management method and device, electronic equipment and storage medium Active CN116193472B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211715408.8A CN116193472B (en) 2022-12-27 2022-12-27 Vehicle-mounted network management method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211715408.8A CN116193472B (en) 2022-12-27 2022-12-27 Vehicle-mounted network management method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN116193472A CN116193472A (en) 2023-05-30
CN116193472B true CN116193472B (en) 2024-03-22

Family

ID=86443513

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211715408.8A Active CN116193472B (en) 2022-12-27 2022-12-27 Vehicle-mounted network management method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116193472B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110224915A (en) * 2018-03-01 2019-09-10 上海汽车集团股份有限公司 Localized network working method and system in a kind of vehicle-mounted hybrid network
CN111726340A (en) * 2020-05-22 2020-09-29 东风汽车集团有限公司 Local network management method and system based on AUTOSAR
CN111885173A (en) * 2020-07-27 2020-11-03 大陆汽车研发（重庆）有限公司 ECU (electronic control unit) conforming to AUSTOSAR (autonomous Underwater vehicle assisted synthetic aperture radar) architecture and sleep/wake-up management method thereof
CN114828177A (en) * 2022-04-18 2022-07-29 北京汽车研究总院有限公司 Vehicle-mounted multi-gateway collaborative dormancy and awakening method, system and storage medium
CN115167218A (en) * 2022-07-20 2022-10-11 重庆长安汽车股份有限公司 Vehicle-mounted local network management method and system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220158523A (en) * 2021-05-24 2022-12-01 현대자동차주식회사 Vehicle system, server, and method for secure communication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110224915A (en) * 2018-03-01 2019-09-10 上海汽车集团股份有限公司 Localized network working method and system in a kind of vehicle-mounted hybrid network
CN111726340A (en) * 2020-05-22 2020-09-29 东风汽车集团有限公司 Local network management method and system based on AUTOSAR
CN111885173A (en) * 2020-07-27 2020-11-03 大陆汽车研发（重庆）有限公司 ECU (electronic control unit) conforming to AUSTOSAR (autonomous Underwater vehicle assisted synthetic aperture radar) architecture and sleep/wake-up management method thereof
CN114828177A (en) * 2022-04-18 2022-07-29 北京汽车研究总院有限公司 Vehicle-mounted multi-gateway collaborative dormancy and awakening method, system and storage medium
CN115167218A (en) * 2022-07-20 2022-10-11 重庆长安汽车股份有限公司 Vehicle-mounted local network management method and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
局部网络在AUTOSAR架构中的应用及优化;皇甫仁杰;汽车电器;20160229(第02期);全文 *

Also Published As

Publication number Publication date
CN116193472A (en) 2023-05-30

Similar Documents

Publication Publication Date Title
CN108683539B (en) Block chain network management method, block chain network management device, block chain network management medium and electronic equipment
CN111385191B (en) Vehicle-mounted interconnection gateway, vehicle OTA upgrading system and method, and computer storage medium
CN107465588B (en) State control method and device of multi-channel bus network and network management system
CN107659494B (en) Data processing method and intelligent vehicle-mounted gateway
CN110311983B (en) Service request processing method, device and system, electronic equipment and storage medium
CN109886693B (en) Consensus realization method, device, equipment and medium for block chain system
CN112463190A (en) Vehicle upgrading method and device
CN103237060B (en) A kind of data object acquisition, Apparatus and system
US9830333B1 (en) Deterministic data replication with conflict resolution
CN110113381A (en) The method and device of theme is subscribed in a kind of block chain
CN110781373B (en) List updating method and device, readable medium and electronic equipment
CN113723840B (en) Internet of vehicles scene calculation method, device and system
CN110417876B (en) Session method, node server in distributed system and master control equipment
CN111464642A (en) Method and device for pushing messages of vehicle machine
JP2023518402A (en) Certificate list update method and device
CN116193472B (en) Vehicle-mounted network management method and device, electronic equipment and storage medium
WO2024078204A1 (en) Bus communication control method and apparatus, and device and storage medium
CN115685843A (en) Local network management grouping method and device, electronic equipment and storage medium
WO2017000256A1 (en) Positioning method and corresponding apparatus
CN116366275A (en) Safety verification method, device, equipment and storage medium based on vehicle controller
CN115696266A (en) Vehicle-mounted controller upgrading method, device, equipment and storage medium
CN115344644A (en) Data synchronization method and device, electronic equipment and computer readable storage medium
CN115167351A (en) Controller function updating method and system, vehicle and server
CN112988738B (en) Data slicing method and device for block chain
CN113553206A (en) Data event execution method and device, electronic equipment and computer readable 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
GR01 Patent grant
GR01 Patent grant