KR20230045932A - Network management method for vehicle - Google Patents

Abstract

The present invention relates to a network management method for a vehicle and the objective of the present invention is to provide a method for using partial network communication (PNC) in a vehicle network with a service-based architecture to flexibly manage the network status of controllers. To achieve this, the network management method for a vehicle comprises the steps of: allowing a first controller corresponding to a client among controllers in a vehicle capable of communicating through a vehicle network to transmit a service discovery (SD) message to find a desired service through the vehicle network, and allowing a first controller corresponding to a server within the PNC, which has received the first controller's SD message, to provide available service information thereof; when the first controller finds the desired service, allowing the first controller to transmit an SD message requesting event group subscription to a second controller corresponding to a server within the PNC, which provides a corresponding service, and allowing the second controller to transmit, to the first controller, an SD message notifying that the event group subscription is approved; allowing the first controller to request PNC information for a new service and allowing the second controller to respond and return the PNC information for the corresponding service; and allowing the first controller and the second controller to update the PNC information to indicate that the service subscription is added to the first controller.

Description

Vehicle network management method {Network management method for vehicle}

The present invention relates to a method for managing a vehicle network, and more particularly, to a method for flexibly managing network states of controllers by utilizing Partial Network (PN) communication in a vehicle network to which a service-based architecture is applied.

As the electronicization of vehicle parts progresses rapidly, the types and number of electronic devices mounted on vehicles are greatly increasing, and their complexity also tends to gradually increase. Examples of such electronic devices include ECU (Electronic Control Unit), which includes not only a powertrain control system for controlling an engine, motor, and transmission, but also a body control system, chassis control system, vehicle network, and multimedia system. etc. can be used. In such a system, the ECU is used as a controller to control devices in the system.

In a typical vehicle, the body control system may include a body electronic parts control system, a convenience device control system, a lamp control system, and the like, and a chassis control system may include a steering control system, a brake control system, a suspension control system, and the like. . In addition, the vehicle network may include a CAN (Controller Area Network), a FlexRay-based network, a MOST (Media Oriented System Transport)-based network, and the like, and a multimedia system may include a navigation device system, a telematics system, and an infotainment system. etc. may be included.

Electronic devices (eg, ECUs) of the system are connected through a vehicle network, and thus, a vehicle network capable of supporting functions of each of the electronic devices is required. For example, CAN can support a transmission rate of up to 1 Mbps, and can support automatic retransmission of collided frames, CRC (Cycle Redundancy Check) based error detection, and the like. A FlexRay-based network can support a transmission speed of up to 10 Mbps, and can support simultaneous data transmission through 2 channels and synchronous data transmission. The MOST-based network is a communication network for high-quality multimedia and can support a transmission rate of up to 150 Mbps.

In addition, an Ethernet-based network may be considered in a vehicle to solve various problems known in vehicle networks, such as transmission speed, system scalability, cost, and the like. An Ethernet-based network can support bi-directional communication through a pair of windings and can support a transmission rate of up to 10 Gbps.

As such, the plurality of electronic devices mounted on the vehicle perform network management functions by transmitting and receiving network management (NM) messages to each other. Here, the network management (NM) simultaneously changes a plurality of electronic units (ECUs) connected to the network to a low power mode (sleep mode) when network communication is not required for efficient management of vehicle power, and network communication is required again. including changing from low power mode to normal mode.

Recently, as vehicle networks have become more complex with the development of vehicle technology, network management has become an important issue. Recently, as autonomous driving and connectivity are strengthened in vehicles, controllers such as ECUs that exchange information through vehicle networks are increasing. is being consumed

In order to cope with these issues, a Partial Network (PN) technology standard is introduced and used for CAN communication and Ethernet communication. A partial network (PN) is a detailed technology of network management. In general, network management (NM) is a control technique that synchronizes the start and end of communication of a network controller.

If the network management (NM) wakes up and sleeps all controllers on the network at the same time, then the partial network (PN) can selectively wake up and put the controllers to sleep. That is, a partial network (PN) supported transceiver can detect its own relevant message (e.g., wakeup frame) and wakes up the microcomputer only if the message is valid.

Hereinafter, the prior art related to network management and partial networks will be described in more detail.

Controllers using vehicle networks basically perform the following operations based on NM (Network Management) specifications.

The controller transmits an NM message to the network when network use is required, and when network use is not required, the controller monitors the NM message within the network to determine the next network state according to the NM specification.

That is, if there is an NM message in the network, the controller should not transition to the network sleep state, and if there is no NM message in the network, the controller should transition to the network sleep state.

In addition, the existing NM algorithm specifies the specification of a PN (Partial Network) function capable of selectively wakeup/sleep, and based on this, the controllers perform the following operations.

In order to perform the PN function, the controllers transmit PN information in addition to the existing NM message. At this time, the transmitting controller transmits the NM message by specifying the PNC (Partial Network Cluster) configured as a combination of the corresponding controller and other controllers requiring communication. .

Subsequently, when receiving the NM message, the receiving controller checks the PNC information included in the receiving controller to determine whether its own PN should be maintained. . On the other hand, if the PN to which it belongs does not need to be continuously maintained, the reception controller must perform transition to the network sleep state.

In the case of current PNC information, PNC 1 to PNC 32 are allocated for some areas (eg, 4 bytes) of the format of the NM message, and allocation is possible for a total of 32 combinations. In addition, the current PNC is statically configured and managed based on a pre-determined combination of controllers. In the operation of such a static PN configuration, when new functions and services are added, specifications and implementation of controllers for network state management must be changed.

However, as new functions and use cases need to be added as well as various physical networks for each vehicle model or class in the future, the number of controller combinations that require PNC allocation for selective wakeup and sleep increases. can do.

In addition, as SOA (Service-Oriented Architecture) is recently expanded and deployed in vehicles, existing static functions and network configurations should not be maintained during vehicle operation, but network configurations should be changed at any time by adding or changing new services. Therefore, there is a need to flexibly manage the network state of the controller.

As such, with the recent introduction of a service-based architecture, a more flexible network configuration during vehicle operation is required compared to the characteristics of existing static vehicle networks. In addition, it is possible to subscribe or cancel a new service while the vehicle is in operation, and there is a demand for adding a new service through OTA (Over-The-Air Programming) after vehicle development is completed. Accordingly, there is an urgent need for a method for existing controllers to provide or utilize new services using SOME/IP (Scalable Service-Oriented Middleware on Ethernet/IP) communication.

Therefore, the present invention was created to solve the above problems, and provides a method for flexibly managing the network state of controllers by utilizing PN (Partial Network) communication in a vehicle network to which a service-based architecture is applied. There is a purpose.

The object of the present invention is not limited to the object mentioned above, and other objects not mentioned are clearly understood from the description below to those of ordinary skill in the art to which the present invention belongs (hereinafter referred to as 'ordinary technician'). It could be.

In order to achieve the above object, according to an embodiment of the present invention, in a vehicle network capable of SOME/IP (Scalable Service-Oriented Middleware on Ethernet/IP) communication, it is set as a combination of controllers that operate in conjunction with specific services and functions. As a method for managing a service-based dynamic PNC (Partial Network Cluster), a first controller corresponding to a client among in-vehicle controllers communicable through a vehicle network transmits an SD (Service Discovery) message through the vehicle network to find a desired service and informing, by a controller corresponding to a server in the PNC that has received the SD message of the first controller, information on services that it can provide; When the first controller finds a desired service, it transmits an SD message requesting event group subscription to a second controller corresponding to a server in the PNC providing the corresponding service, and the second controller sends an SD notifying approval of the event group subscription. sending the message to the first controller; the first controller requesting PNC information for a new service, and the second controller responding and returning PNC information for the corresponding service; and updating PNC information in the first controller and the second controller with the addition of the service subscription of the first controller.

Thus, according to the vehicle network management method according to the present invention, various services can be provided in the vehicle, and each controller can freely subscribe/cancel the corresponding service as needed, so whether to apply the selective sleep and change the timing of the selective sleep. It is possible to respond flexibly through an algorithm even if the requirements such as

In addition, according to the present invention, flexible network management that can increase the effectiveness of the service-based architecture is possible, and even if the power management requirements of the controller are changed according to the change in functional requirements, there is no need for a separate implementation change. There is an advantage of improving development efficiency.

1 is a diagram illustrating Partial Networking Information (PNI) in the present invention.
2 is a diagram for explaining the outline of a SOME/IP communication scheme in the present invention.
3 is a diagram illustrating a network structure and a PNC configuration in the present invention.
4 is a diagram for explaining functions performed between a server and a client in the present invention.
5 is a diagram showing an example in which a PNC configuration is updated after service discovery and subscription in the present invention.
6 is a diagram for explaining an example in which a PNC configuration is updated in the present invention.
7 is a diagram illustrating a SOME/IP message format for requesting PNC information in the present invention.

Specific structural or functional descriptions presented in the embodiments of the present invention are merely exemplified for the purpose of explaining embodiments according to the concept of the present invention, and embodiments according to the concept of the present invention may be implemented in various forms. In addition, it should not be construed as being limited to the embodiments described in this specification, but should be understood to include all modifications, equivalents, or substitutes included in the spirit and scope of the present invention.

Meanwhile, in the present invention, terms such as first and/or second may be used to describe various elements, but the elements are not limited to the above terms. The above terms are used only for the purpose of distinguishing one component from other components, for example, within a range not departing from the scope of rights according to the concept of the present invention, a first component may be referred to as a second component, Similarly, the second component may also be referred to as the first component.

It should be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, but other elements may exist in the middle. something to do. On the other hand, when an element is referred to as “directly connected” or “directly in contact with” another element, it should be understood that no other element exists in the middle. Other expressions used to describe the relationship between components, such as "between" and "directly between" or "adjacent to" and "directly adjacent to" should be interpreted similarly.

Like reference numbers indicate like elements throughout the specification. Terms used in this specification are for describing embodiments, and are not intended to limit the present invention. In this specification, the singular form also includes the plural form unless specifically stated in the phrase. As used herein, “comprises” and/or “comprising” means the presence of one or more other components, steps, operations, and/or elements in which a stated component, step, operation, and/or element is present. or do not rule out additions.

An object of the present invention is to provide a method for flexibly managing the network state of controllers by utilizing PN (Partial Network) communication in a vehicle network. In addition, the present invention is to provide an efficient PN utilization method for securing service-based architecture flexibility.

As new services or functions are added in the vehicle network, requirements for network state control and power management of each controller may change. Accordingly, the present invention enables efficient network operation by providing a method for allocating and managing service/function-based dynamic PNCs.

In addition, the present invention provides a method that can flexibly respond to network management (hereinafter referred to as 'NM') according to the activation/deactivation of functions or addition of new services using the SOME/IP communication method.

In the present invention, by utilizing the characteristics of SOME/IP SD (Service Discovery), the PNC information, which was fixedly allocated for each existing controller, is linked to the subscription/unsubscription (unsubscribe) of each service to subscribe to the corresponding service. A combination of controllers allocates and manages PNCs.

Since controllers can freely join/leave to the corresponding PNC through PNC allocation by service, even if the operation requirements of the network-connected controller change due to the addition of a new service (at the time of selective sleep) change, etc.) does not affect the configuration of the upper application.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating Partial Networking Information (PNI) in the present invention. To support a partial network (hereinafter referred to as 'PN'), an NM message includes PNC information as illustrated in FIG. 1, where each PNC bit consists of a combination of current controllers. The controllers determine whether the network sleeps or not by determining whether the PNC bit to which they belong is set in the received NM message.

2 is a diagram for explaining the outline of the SOME/IP communication method in the present invention, illustrating a state in which service notification (SD-OfferService) and subscription request (SD-Subscribe) are made between a server and an offer. are doing

SOME/IP (Scalable Service-Oriented Middleware on Ethernet/IP) sends only necessary data at the time of need and supports a protocol to subscribe or unsubscribe to a service. Accordingly, when a use case occurs in which a specific controller uses a corresponding service while not using an existing service, dynamic operation is possible through a subscription request.

3 is a diagram illustrating a network structure and a PNC configuration in the present invention. Controllers using the network all use NM/PN algorithms based on NM specifications. If only some controllers need power-on and network use in a specific situation, they are defined as one PNC (combination of controllers that can be grouped into the same category).

For example, as shown in FIG. 3, PNC 1 is a case in which allocated ECUs 1 to 3 among all controllers (ECUs) require an operation in connection with the corresponding function, and the three controllers (ECUs) are converted into corresponding bits. assign to The PNC defined in this way is specified in the NM message so that all nodes in the network can recognize it.

If, among all PNCs, only controllers corresponding to a specific PNC are to be powered on, only information corresponding to the corresponding PNC is written in the NM message and transmitted. That is, controllers that do not correspond to the specific PNC in the network transition to a network sleep state after recognizing that the use of the network is terminated, and performs a power-off process. On the other hand, in the case of a controller corresponding to the specific PNC in the network, it recognizes that the network is continuously used and continues to operate without transitioning to the network sleep state.

In the example of FIG. 3 , the PNC configuration itself is already statically configured, and accordingly, only network wakeup and sleep are selectively performed. In addition, if a controller with functions related to PNC 1 is created due to the addition of new functions and cooperative control functions, it is necessary to change specifications and implement changes according to PNC configuration changes.

4 is a diagram for explaining functions performed between a server and a client in the present invention, and FIG. 5 is a PNC configuration after service discovery (SD) and subscription in an existing PNC configuration This is a drawing showing an updated example. An example of a case where a client is ECU 5 (first controller) and a server is ECU 1 (second controller) among all nodes communicatively connected through a vehicle network, that is, all controllers (ECUs). In FIG. 5, (a) illustrates an existing PNC configuration and (b) illustrates an updated PNC configuration after service discovery and subscription.

When SOME/IP communication is applied, a service discovery (hereinafter referred to as 'SD') process is performed between the server and the client to find and provide new services. will do The scenario of each controller is changed according to the new service subscription/cancellation procedure, and PNC information is updated for flexible control.

As can be seen in FIG. 4, the client (ECU 5) transmits an SD message (FindService SD message) to the server (ECU 1) to find the service it wants to receive, and searches for the desired service (in FIG. 4, 'SD: See 'FindService'). Accordingly, the server (ECU 1) transmits a response message (OfferService SD message) to the client (ECU 5) to inform the client (ECU 5) of the service it provides (refer to 'SD: OfferService' in FIG. 4).

Then, when the client finds the desired service, it sends an SD message requesting subscription to the event group to the server providing the service ('SD: Subscribe EVG'). ('SD: Subscribe EVG ACK').

Next, the client requests PNC information on the new service ('Request PNC info'), and in response, the server returns PNC information on the corresponding service ('Response PNC info'). Then, the client updates the PNC table based on the received PNC information, and uses the updated PNC information when transmitting or receiving the next NM message.

In addition, the server receives the result of updating PNC information from the client, returns a confirmation approval message, and updates the PNC table. Afterwards, the client transmits a SOME/IP request message to receive data from the server, and the server transmits the corresponding service information upon receiving the service request message from the client.

The service discovery mechanism described above operates when the controller is booted when the vehicle is started, finds a service required at that time (Find), informs the network of the service that can be provided (Offer), and determines whether or not the service is subscribed and subscribed based on this. Decide.

This is not done only when the vehicle is started, and if the service is no longer needed while the vehicle is in operation, whether or not to subscribe to the new service is dynamically changed. Accordingly, the PNC configuration can also be dynamically changed during vehicle operation, as shown in FIG. 6, and an update can be made according to the above-described procedure without a change in specifications or implementation of the controller.

Referring to FIG. 6, the configuration of the existing PNC 1 includes ECUs 1, 2, and 3 as shown in (a), but as shown in (b), the PNC configuration can be updated after subscribing to SD. there is. Referring to (b), it can be seen that ECU 5 is added to the controller group of PNC 1 by newly adding a service related to PNC 1 in ECU 5.

Also, as shown in (c), the PNC configuration may be updated after canceling the SD subscription. Referring to (c), it can be seen that ECU 3 is deleted from the controller group of PNC 1 by unsubscribing from ECU 3 of a service related to PNC 1.

Referring to FIG. 4, the process of updating the PNC information to which the new controller requested service subscription by applying for a new service subscription has been described. Even in the case of service subscription cancellation, a message between the server and the client Through transmission and reception processes, PNC information may be updated in which the controller requesting cancellation of the service subscription is deleted.

That is, a controller corresponding to a client among in-vehicle controllers communicable through a vehicle network transmits an SD message requesting unsubscription from an event group (unsubscription from a service) through the vehicle network, and transmits an SD message from a controller corresponding to the client Upon reception, the controller corresponding to the server in the PNC transmits the SD message notifying the approval of unsubscribing from the event group to the client. Subsequently, the server and the client each update PNC information to indicate that the subscription of the client requesting cancellation has been cancelled.

In this way, the above-described vehicle network management method of the present invention can be summarized as follows.

In the vehicle network management method according to the present invention, a first controller corresponding to a client among in-vehicle controllers communicable through a vehicle network transmits an SD (Service Discovery) message for finding a desired service through the vehicle network, and 1. A controller corresponding to a server in the PNC receiving the SD message from the controller may inform information on services that can be provided by the controller.

In addition, in the vehicle network management method according to the present invention, when the first controller finds a desired service, it transmits an SD message requesting event group subscription to a second controller corresponding to a server in a PNC providing the service, The method may include transmitting, by the second controller, an SD message informing of an event group subscription approval to the first controller.

In addition, the vehicle network management method according to the present invention includes the steps of the first controller requesting PNC information for a new service, and the second controller responding and returning PNC information for the corresponding service; and updating PNC information with the service subscription of the first controller added in the first controller and the second controller, respectively.

Further, in the vehicle network management method according to the present invention, the step of canceling the service subscription includes the first controller, the second controller, the third controller, and the fourth controller among controllers in the vehicle capable of communicating through the vehicle network. The third controller corresponding to a client in the event group transmits an SD message requesting unsubscribing from the event group through the vehicle network, and the fourth controller corresponding to a server in the PNC that receives the SD message of the third controller transmitting, by the controller, an SD message informing of approval of unsubscribing from the event group to a third controller; and updating PNC information in each of the first controller, the second controller, the third controller, and the fourth controller to indicate that the service subscription of the third controller has been cancelled.

7 is a diagram illustrating a SOME/IP message format for requesting PNC information in the present invention. PNC information request and response are defined as a service unit, and the header of the SOME/IP message is a service ID (Service ID). ) item, and the service ID is defined as a PNC information request ID (PNC Info Request ID).

In addition, the header of the SOME/IP message further includes a method ID or event ID predefined to be supported in the header for PNC information update through PNC information request and response, and PNC information confirmation. In order to do so, PNC information on the new service must be requested, and PNC information on the corresponding service must be responded and returned, so it is applied as a method ID capable of requesting and responding.

In addition, the header of the SOME/IP message further includes message type information, which is for distinguishing between a PNC information request and its response. That is, a message requesting PNC information (eg, Message Type [0x00]) and a reply message returned as a response (eg, Message Type [0x80]) are set to different message types to distinguish each other.

In addition, the header of the SOME/IP message further includes return code information, which is used to inform whether the request has been successfully processed. For example, it can be set to [0x00] in case of successful processing (E_OK) and [0x02] in case of not (E_NOT_OK).

As described above, the vehicle network management method according to the present invention has been described in detail. Conventionally, various architectures for each vehicle type and vehicle class are required, but each function is fixed and the configuration of the interface is statically defined accordingly. Specifications had to be diversified, and communication specifications had to be constantly updated according to changes in requirements of controllers for each vehicle type and vehicle class.

On the other hand, according to the present invention, various services can be provided in a vehicle, and each controller can freely subscribe/unsubscribe to the corresponding service as needed, so whether selective sleep is applied or not, selective sleep timing change, etc. Flexible response through algorithm is possible even if requirements are changed in various ways.

In addition, according to the present invention, flexible network management that can increase the effectiveness of the service-based architecture is possible, and even if the power management requirements of the controller are changed according to the change in functional requirements, there is no need for a separate implementation change. There is an advantage of improving development efficiency.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concept of the present invention defined in the following claims It is also included in the scope of the present invention.

Claims (5)

As a management method of a service-based dynamic partial network cluster (PNC) set as a combination of controllers operating in conjunction with specific services and functions in a vehicle network capable of SOME/IP (Scalable Service-Oriented Middleware on Ethernet/IP) communication,
Among the in-vehicle controllers communicable through the vehicle network, a first controller corresponding to a client transmits an SD (Service Discovery) message for finding a desired service through the vehicle network, and in the PNC receiving the SD message of the first controller guiding, by a controller corresponding to a server, service information that can be provided by the controller;
When the first controller finds a desired service, it transmits an SD message requesting event group subscription to a second controller corresponding to a server in the PNC providing the corresponding service, and the second controller sends an SD notifying the event group subscription approval. sending the message to the first controller;
the first controller requesting PNC information for a new service, and the second controller responding and returning PNC information for the corresponding service;
and updating PNC information by adding the service subscription of the first controller in the first controller and the second controller, respectively.
The method of claim 1,
The first controller updates the PNC table based on the PNC information returned from the second controller and transmits an update result, and the second controller receives the update result from the first controller and transmits an acknowledgment message to the first controller. A vehicle network management method characterized in that the PNC table is updated thereafter.
The method of claim 1,
After updating the PNC information, the first controller transmits a service request message, and when the second controller receives the service request message from the first controller, transmits corresponding service information according to the service request to the first controller. A method for managing a vehicle network, further comprising steps.
The method of claim 1,
In an event group including the first controller, the second controller, the third controller, and the fourth controller among in-vehicle controllers communicable through the vehicle network, the third controller corresponding to the client requests cancellation of the event group subscription. transmitting an SD message through the vehicle network, and transmitting, by the fourth controller corresponding to a server in the PNC that has received the SD message of the third controller, an SD message informing of approval of unsubscribing to an event group to a third controller; and
The vehicle network management method of claim 1 , further comprising updating PNC information in the first controller, the second controller, the third controller, and the fourth controller to indicate that the service subscription of the third controller has been cancelled.
The method of claim 1,
The header of the SOME / IP message for requesting the PNC information,
A service ID predefined as a PNC information request ID by defining a PNC information request and response as a service unit;
Method ID predefined to be supported in the header for PNC information update through PNC information request and response;
message type information that distinguishes between a PNC information request and a response thereof; and
A method for managing a vehicle network, characterized in that it includes return code information for notifying whether the PNC information request has been successfully processed.

Images