DE102004060301A1 - Method for initializing an electronic system comprising a plurality of plug-ins - Google Patents

Abstract

The invention relates to a method for initializing an electronic system (1) having a base interface (2) and a plurality of plug-in modules (3.1 to 3.n) connected thereto. In order to enable a flexible addition and removal of plug-ins (3.1 to 3.f), the invention proposes that in the context of the initialization of the system (1) the base interface (2) and the plug-ins exchange information. The plug-ins communicate which processes (priority, time grid, etc.) they contain. In addition, they tell you which variables (variables, functions, structures, etc.) they require to process the processes, and which quantities they can provide in the course of processing the processes. On the basis of the information obtained, the base interface (2) performs a linking of the individual plug-ins to one another, so that the plug-ins contain corresponding references, where they can access the required quantities during the processing of the processes. The references are, for example, pointer (13) to one memory area (14) or pointer (18) to a structure (19) in another plug-in.

Description

The The present invention relates to a method for initialization an electronic system that has a basic interface and several has connected thereto plug-in modular.

The Invention also relates a communication protocol for processing on at least one computing device an electronic system during the initialization of the electronic system. The electronic System comprises a basic interface and several connected modular Plug-ins.

Of Furthermore, the invention relates to a computer program for processing on a computing device a data processing system. The computer program includes several Plug-ins and one Base interface, with the plug-ins to the base interface are connected.

Finally, concerns the present invention also an electronic system with a computing device for processing a communication protocol. The electronic System comprises a basic interface and several connected modular Plug ins.

in the In the automotive sector, electronics were originally only in the form of individual, used electrified components, these components isolated and independent acted on each other. Later were These components are increasingly integrated into systems, with the components in the systems for the purposes of data exchange and mutual Influencing each other. Examples for such Integrated systems are engine control systems, brake control systems or driver information systems. Currently there is a trend towards networking all vehicle systems among each other and increasingly with the vehicle environment to observe.

• – neue Fahrzeugfunktionen sind häufig nur noch im Verbund unterschiedlicher Teilsysteme realisierbar und effektiv nutzbar,
• – damit wird eine funktionale Integration von Teilsystemen auch unterschiedlicher Zulieferer erforderlich,
• – die Wertigkeit und der Charakter von Fahrzeugen werden zunehmend durch komplexe Softwarefunktionen bestimmt, und
• – die Beherrschung der wachsenden Systemkomplexität wird für Fahrzeughersteller und Zulieferer in zunehmendem Maße wettbewerbsentscheidend hinsichtlich Geschwindigkeit, Kosten und Qualität der integrierten Systeme.

This recognizable merging of the systems brings with it considerable technical and organizational challenges:

• New vehicle functions are often only realizable and effectively usable in combination with different subsystems
• - this requires a functional integration of subsystems from different suppliers,
• The valence and character of vehicles are increasingly determined by complex software functions, and
• - Mastering the growing system complexity is becoming increasingly competitive for vehicle manufacturers and suppliers in terms of speed, cost and quality of integrated systems.

From the DE 100 44 319 A1 For example, an electronic system for vehicles is known, which consists of first components for carrying out control tasks in operational sequences and second components which coordinate an interaction of the first components. The first components carry out the control tasks through a combination of operating functions and basic functions. The operating functions are implemented in operating submodules (so-called plug-ins) and can be modularly integrated into the electronic system, re-used and exchanged or changed at any time. The basic functions are summarized in a base layer, which communicates with the operating modules via a suitable interface.

Between the base layer and the interface, a system layer is provided, which are the second components to coordinate the interaction the first components for performing the control tasks includes. There is an intelligence in the system layer which is required to integrate the plug-ins into the overall system is. In other words, the functionalities of plug ins build on the functionalities of System layer on and even require this. The plug-ins must be so on the functionalities be tuned to the system layer and can not readily in other electronic systems with other functionalities in the System layer can be used. Before using the plug-ins in another system environment is time-consuming and expensive Adaptation of plug-ins required. Furthermore, it may be necessary be in a change or supplement the functionalities of first components also adapt the functionalities of the system layer, there a revision the first components affect the coordination of the components, this means on the system layer, may have. In the known systems are So with respect the treatment of plug ins only isolated solutions provided which can not easily be transferred to other systems without extensive adaptations are.

In addition, will in the known electronic system, the initialization of Systems and the link the plug ins are not among each other by the plug-ins themselves, but rather solely through the system layer and / or an underlying operating system layer realized. The initialization is thus controlled centrally, a Communication between the system's plug-ins before or during the Initialization does not take place.

outgoing from this prior art, the present invention is the The object of the invention is to design the known method to such an extent and further that the initialization of the electronic Systems can be performed much more flexible than before. Especially should the shortcuts the plug-ins with each other during the initialization fully automatic be generated without the electronic system, the type and Number of connected plug-ins and their functionalities or Processes must be known in advance.

• – beim Initialisieren des elektronischen Systems der Basis-Schnittstelle durch die Plug-Ins jeweils Informationen zur Verfügung gestellt werden betreffend: – mindestens eine von dem jeweiligen Plug-In ausgeführte Funktionalität; – Größen, die von dem jeweiligen Plug-In zur Ausführung der mindestens einen Funktionalität benötigt werden; – Größen, die von dem jeweiligen Plug-In nach Ausführung der mindestens einen Funktionalität zur Verfügung gestellt werden,
• – den einzelnen Plug-Ins durch die Basis-Schnittstelle Informationen zur Verfügung gestellt werden betreffend: – welcher der übrigen Plug-Ins eine von dem Plug-In benötigte Größe zur Verfügung stellt, und
• – ein entsprechender Verweis auf denjenigen Plug-In, der die Größe zur Verfügung stellt, in demjenigen Plug-In abgelegt wird, der die Größe benötigt.

To solve this problem is proposed starting from the method of the type mentioned that

• - When initializing the electronic system of the base interface by the plug-ins information is made available concerning: - at least one executed by the respective plug-in functionality; Sizes required by the respective plug-in to perform the at least one functionality; Sizes which are made available by the respective plug-in after execution of the at least one functionality,
• - The individual plug-ins are provided by the base interface information regarding: - Which of the other plug-ins provides a required size of the plug-in, and
• - a corresponding reference to the plug-in that provides the size is placed in the plug-in that needs the size.

Advantages of invention

To the method according to the invention is As part of the initialization of the electronic system, first everyone the plug-in connected to the base interface for specific information queried. This information relates to, for example, those in the Plug-in implemented functionalities or the corresponding Processes. Furthermore The information concerns the processing of the processes detected and provided by the plug-in sizes, as well the sizes that the plug-in for execution the functionalities or to process the processes needed. Sizes in the sense of the present Invention are, for example, variables, functions, structures, etc. The plug-ins the inventive electronic Systems So over an additional Initialization functionality to respond to the corresponding requests from the base interface and the desired ones To submit information.

To Getting the information from a first plug-in asks the Basic interface the rest Plug-ins, whether they provide at least one of the required sizes can.

If That is the case, be the first plug-in through the base interface Information available posed regarding which of the other plug-ins the one needed by the first plug-in Sizes to disposal provides. Then it will be at a certain point in the first plug-in a corresponding reference to those plug-ins registered, which the needed Sizes to Make available. A plug-in of the inventive electronic Systems features So over the extra Initialization functionality to the received references to one or more plug-ins, which those needed by the plug-in Sizes to Make available Store at a suitable location.

Preferably At least one empty field is provided in the plug-ins where the Reference can be filed. Every time in the context of the processing a process in a first plug-in a certain size of one needed another plug-in will, the size is over the Referred to by the other plug-in. Of course, in the Plug-ins also have multiple references to various other plug-ins are stored, especially if in a plug-in different Sizes needed. References to the other plug-ins can be of any kind.

With the method according to the invention can in runtime during the initialization of the electrical system the links between the plug-ins, regardless of which Plug-ins actually connected to the base interface, and without that in the It must be known in advance which plug-ins are connected. The inventive method allows one Maximum flexibility in terms of Add, Remove and change of plug-ins of an electronic system.

The plug-ins can be designed as hardware (for example as plug-in cards with additional input / output interfaces, additional drivers, additional memory or computing capacities, etc. for a control unit) or as software (for example as operating submodules of a computer program). The basic interface has no functionality to supplement the functionality of the plug-ins. The purpose of the basic interface concerns only the linking of the plug-ins during initialization and the communication between the plug-ins during operation of the electrical system. The The necessary information about the plug-ins is obtained by the basic interface directly from the plug-ins during the initialization phase of the electronic system through a communication with the plug-ins.

According to one advantageous development of the invention it is proposed that the at least one functionality realized by at least one process. That means the functionalities of the plug-ins are realized by one or more processes. The transmission information regarding the functionality of the plug-ins thus affects any Information regarding the processes implemented in the plug-in. Advantageously, the information concerning the functionality of the plug-ins a time frame in which the at least one process is processed becomes, and a priority of the at least one process.

According to one preferred embodiment of Invention is proposed that in the plug-in, which has a specific Size needed, as Reference a pointer to a location is dropped on the the needed Size through one of the others Plug-ins is saved. The space referenced can be in one of the plug-ins, but also in the base interface or subordinate base functionality or basic software be. Working with pointers has several advantages. An advantage is that when you update the software in a plug-in the old software can remain in memory, the new software another new location is placed in memory and the pointer is simply converted to the new storage location. Another one Programming (so-called flashing) of the entire memory (deleting the old content and describing it with the new software) is thus not mandatory.

According to one another preferred embodiment The present invention proposes that in the plug-in, which needs a size than Reference a pointer to a structure is placed in the on a given position the required Size through one of the others Plug-ins is saved. According to this embodiment So it will not work for you every needed Size a separate one Pointer stored on a storage location where the required size is stored is, but only a single pointer to a structure filed, where all required sizes filed are. The structure comprises a certain number of fields, where certain sizes are stored in certain fields. So For example, it is defined in advance that a size A is always is stored at the third position in the structure. If in one Plug-in size A is needed is jumped from the plug-in to the beginning of the structure which the pointer points to. Dependent on from the needed Size is on the corresponding position or the corresponding field of the structure jumped, that is for the Size A will jumped to the third position, the required size is read and then returned to the plug-in again. The structure may be in the base interface or the child base functionality or base software be included. The content of the structure is determined by the plug-ins the corresponding sizes to Make available continuously updated. This embodiment has the advantage that in the plug-ins just a box for the pointer, which is at the beginning the structure shows needed even if more than one size is needed in the plug-in.

If a certain size of multiple plug-ins to disposal asked, which of the plug-ins is the size for the other plug-ins, which need the size to Make available should. In such a case, advantageously, the size of the one becomes Plug-in used for further processing, whose process for Determining the size has the highest priority. Because this process is the highest priority it will provide the required size before the other processes can.

Of further it may be advantageous under certain conditions that in such a case the size of the plug-in for disposal is provided by which the base interface gets the information first, that the plug-in or a process of the plug-in provide the required size can. Alternatively, it is suggested that the size of the plug-in for disposal the base interface is the last to receive the information gets that the plug-in or a process of the plug-in provide the required size can.

It makes sense for the base interface to access an initialization table with information on where each plug-in is stored. This table can - if the plug-ins are software-designed - flashing new plug-ins to be updated. When trained as software, but also as hardware Plug-ins, it is also conceivable that at the beginning of the initialization the plug-ins connected to the base interface and their (initial) Addresses are determined and the table updated accordingly becomes. The table is preferably stored in the basic interface. Based on this table, the base interface can then be the individual Query plug-ins and the desired ones To gather information.

If the electronic system is designed as a computer program, a structuring of the computer program into basic software without plug-ins, a Mas arranged above it ter interface and attached plug-ins and / or sub-interfaces to which further sub-interfaces and / or other plug-ins are connected conceivable. The basic software comprises a fixed, permanent part of the software, which is responsible, for example, for communication via bus drivers, etc. In this way, it is possible to achieve a cascaded structure of the electronic system. For this structure, a visibility concept can be realized, by means of which it is possible to limit the visibility of certain variables from below, that is, from higher-ranking areas, to certain lower-ranking areas of the structure. In this regard, a method for initializing an electronic system comprising a base interface and a plurality of plug-ins connected thereto is proposed, wherein one of the base interfaces as a master interface and the remaining base interfaces are designed as sub-interfaces and to the Master interface except the plug-ins are still connected to sub-interfaces, to which in turn further sub-interfaces and / or other plug-ins and so on are connected. The interfaces are divided into different areas (eg private, public, protected, etc.). Only the variables within the same area of the interfaces (variables, functions, etc.) are visible to subordinate (ie higher ranking) interfaces and thus also accessible. The same size can be applied to different areas of an interface. As a result, the sizes can be encapsulated in certain areas and are somewhat similar to local variables.

advantageously, the interfaces are in a private area and a public area Divided area. Only those at the public area of an interface adjoining public Sizes (variables, Functions, etc.) are for a subordinate interface is visible and thus accessible. The private ones attached to the private area of the interface Sizes are only in the relevant interface and public areas of above it Interfaces visible.

With this cascaded structure of the electronic system and the Distribution of interfaces in a private and a public Area can For example, completed in a computer program program areas be created. This is beneficial if a specific program area developed and programmed by external suppliers. Again Design, structure and actual programming (which Sizes, functions, Structures were used, which algorithms are executed, etc.) is designed in detail, is not for the client of Importance. The only important thing is that the program area is that of him required functionality Fulfills, this means that in him the required processes are realized, and that he child (that is higher ranking) interfaces the required public Sizes to disposal provides.

A subordinate interface only has access to the public Areas of the parent Interfaces adjacent sizes. The on The sizes applied to private areas are for the subordinate interface not visible and thus not accessible. So that's going on simple way an encapsulation of program areas or in it realized functionalities allows. The externally developed program areas can be created with the help of this visibility concept also easily and quickly integrated into an existing computer program become.

to easier handling of the sizes within the plug-ins and the base interface is suggested that everyone needed from the plug-ins or from the plug-ins available Asked size one for one defined area of the electronic system unique identifier is assigned. The defined area is preferably the means of the visibility concept completed area of the electronic System. The identifier includes, for example, an identification number and an indication of whether the size is public or private. Of course it is conceivable not only the variables, but also functions, Structures u. a. such or another unique identifier assigned.

advantageously, are the identifiers of the sizes in one List of identifiers to which the base interface during the Initialization of the electronic system can access.

It It is conceivable that in the identification list all in the electronic System theoretically available Sizes (variables, Functions, etc.) are listed and explained. The list will be for the Whole system and not for created the currently connected plug-ins. That's why she's independent of the type and number of connected plug-ins are always the same Content. In this respect can also be said that in the Invention the base interface in advance no information about the actually connected Plug-ins are available. The list preferably forms the basis for an interface agreement or interface definition and serves both the supplier software or plug-ins as well as the integrator as a basis.

• – beim Initialisieren des elektronischen Systems der Basis-Schnittstelle durch die Plug-Ins jeweils Informationen zur Verfügung gestellt werden betreffend: – mindestens eine von dem jeweiligen Plug-In ausgeführte Funktionalität; – Größen, die von dem jeweiligen Plug-In zur Ausführung der mindestens einen Funktionalität benötigt werden; – Größen, die von dem jeweiligen Plug-In nach Ausführung der mindestens einen Funktionalität zur Verfügung gestellt werden,
• – den einzelnen Plug-Ins durch die Basis-Schnittstelle Informationen zur Verfügung gestellt werden betreffend: – welcher der übrigen Plug-Ins eine von dem Plug-In benötigte Größe zur Verfügung stellt, und
• – ein entsprechender Verweis auf denjenigen Plug-In, der die Größe zur Verfügung stellt, in demjenigen Plug-In abgelegt wird, der die Größe benötigt.

As a further solution of the object of the present invention, it is proposed, based on the communication protocol of the type mentioned at the outset, that the communication protocol programmed so that

• - When initializing the electronic system of the base interface by the plug-ins information is made available concerning: - at least one executed by the respective plug-in functionality; Sizes required by the respective plug-in to perform the at least one functionality; Sizes which are made available by the respective plug-in after execution of the at least one functionality,
• - The individual plug-ins are provided by the base interface information regarding: - Which of the other plug-ins provides a required size of the plug-in, and
• - a corresponding reference to the plug-in that provides the size is placed in the plug-in that needs the size.

• – beim Initialisieren des elektronischen Systems die Plug Ins der Basis-Schnittstelle jeweils Informationen zur Verfügung stellen betreffend: – mindestens eine von dem jeweiligen Plug-In ausgeführte Funktionalität, – Größen, die von dem jeweiligen Plug-In zur Ausführung der mindestens einen Funktionalität benötigt werden, und – Größen, die von dem jeweiligen Plug-In nach Ausführung der mindestens einen Funktionalität zur Verfügung gestellt werden;
• – die Basis-Schnittstelle den einzelnen Plug-Ins Informationen zur Verfügung stellt betreffend: – welcher der übrigen Plug-Ins eine von dem Plug-In benötigte Größe zur Verfügung stellt; und
• – ein entsprechender Verweis auf denjenigen Plug-In, der die Größe zur Verfügung stellt, in demjenigen Plug-In abgelegt wird, der die Größe benötigt.

As yet another solution to the object of the present invention, it is proposed, based on the computer program of the type mentioned at the beginning, that

• - When initializing the electronic system, the plug-ins provide the base interface information respectively regarding: - at least one of the respective plug-in executed functionality, - sizes that are required by the respective plug-in to perform the at least one functionality , and - quantities provided by the respective plug-in after execution of the at least one functionality;
• The basic interface provides information to the individual plug-ins concerning: which of the remaining plug-ins provides a size required by the plug-in; and
• - a corresponding reference to the plug-in that provides the size is placed in the plug-in that needs the size.

In In this case, therefore, the electronic system is a computer program trained so that it is the plug-ins to operating submodules a computer program. Accordingly, therefore, the invention realized by the computer program.

• – die Plug-Ins im Rahmen der Initialisierung des elektronischen Systems der Basis-Schnittstelle jeweils Informationen zur Verfügung stellen betreffend: – mindestens eine von dem jeweiligen Plug-In ausgeführte Funktionalität; – Größen, die von dem jeweiligen Plug-In zur Ausführung der mindestens einen Funktionalität benötigt werden; – Größen, die von dem jeweiligen Plug-In nach Ausführung der mindestens einen Funktionalität zur Verfügung gestellt werden,
• – den einzelnen Plug-Ins durch die Basis-Schnittstelle Informationen zur Verfügung gestellt werden betreffend: – welcher der übrigen Plug-Ins eine von dem Plug-In benötigte Größe zur Verfügung stellt, und
• – ein entsprechender Verweis auf denjenigen Plug-In, der die Größe zur Verfügung stellt, in demjenigen Plug-In abgelegt wird, der die Größe benötigt.

As a further solution to the object of the present invention, starting from the electronic system of the type mentioned at the outset, it is proposed that

• - The plug-ins in the context of the initialization of the electronic system of the base interface each provide information regarding: - At least one of the plug-in executed functionality; Sizes required by the respective plug-in to perform the at least one functionality; Sizes which are made available by the respective plug-in after execution of the at least one functionality,
• - The individual plug-ins are provided by the base interface information regarding: - Which of the other plug-ins provides a required size of the plug-in, and
• - a corresponding reference to the plug-in that provides the size is placed in the plug-in that needs the size.

drawings

following become preferred embodiments of the invention explained in more detail with reference to FIGS. Show it:

1 an inventive electronic system according to a first preferred embodiment;

2 the construction of a plug-in;

3 a flow diagram of a method according to the invention according to a preferred embodiment; and

4 an inventive electronic system according to another preferred embodiment.

description the embodiments

In Control devices, in particular in motor vehicle control units are from the prior Technique for both Software as well for Hardware plug-and-play mechanisms realized. This can, for example in a control unit by simply programming an operating sub-module (a so-called Plug-ins) an additional or another functionality to disposal be put. In such a case, the plug-in component would be software educated.

It is also possible to change or expand the functionality of the control unit by mechanically plugging in and electrically contacting an additional hardware module. In such a case, the plug-in component would be hard ware trained. A particularly preferred field of use of plug-in components is in a control unit network, where additional control units can be added and connected, for example via a CAN bus with the other control units. As a result, additional or different functionalities can be made available to the ECU network.

The However, known plug-in mechanisms have the disadvantage that both the functionalities as well as the interfaces of the plug-ins, that is which ones Size them to disposal can make and what sizes they are need, must be known in advance and resources must be kept, regardless whether the plug-in components indeed connected or not. Advance means in this context at the time of integration of a new plug-in component. With In other words, before the new plug-in can be integrated, the be known information. That's why the information held centrally in the electronic system and can be retrieved from there if necessary.

One example for Such a known plug-in mechanism is for example the Integration of an ACC (Adaptive Cruise Control) function into one existing control unit network in a motor vehicle. As soon as required for the ACC function Hardware components are installed in the vehicle, send this either immediately or only after a restart of the Systems defined CAN messages in an engine control system the corresponding functionalities in a computer program, or the interfaces of functionalities activated. The disadvantage here is that regardless of whether the ACC hardware is installed in the motor vehicle or not, the ACC functionality in the computer program, or the corresponding operating sub-modules (Plug-ins), in which motor control must always be present. The is called, that even if a certain functionality in a motor vehicle is not realized, must appropriate resources are made available and kept to if necessary, the desired functionality unlock.

Furthermore it is disadvantageous in the known plug-in mechanisms that a to be integrated functionality always a manual modification of the rest of the system, for example integration of the new processes of the additionally provided operating submodules (Plug-ins), must be made. A subsequent integration of an additional functionality in an already programmed (flashed) control unit, that is a so-called Update or upgrade in the field, is also not or only with great effort possible.

Exactly This is where the present invention starts. It allows a simple, fully automatic, during the Initialization of the electronic system at runtime from new plug-ins to an existing system. It also offers the invention is the prerequisite for a particularly advantageous Visibility concept for the sizes used in the system (for Example variables, functions, structures, etc.).

With Help of the invention may have additional Plug-ins new or modified functionalities a control unit be integrated, without the remaining system of this controller, the Interfaces, or processes, be known in advance have to. The proposed concept allows for subsequent updates and upgrades functionalities, without that the complete control unit, For example, in a workshop, be reprogrammed (flashed) got to. After downloading the new functionalities the control unit they log in automatically in the system and are then in full Scope functional. In particular, according to the invention mechanisms for automatic Coordination of variable access and automatic integration of the Processes taking into account priorities of processes and variables proposed.

In 1 is an inventive electronic system in its entirety by the reference numeral 1 designated. The system 1 includes a base interface 2 and several connected plug-in components (short: plug-ins) 3.1 to 3.n , The electronic system 1 can be realized in hardware, with the plug-ins 3.1 to 3.n then represent hardware components that can be mechanically plugged into an existing system and electronically contacted. An example of such a hardware implemented plug-in is, for example, a plug-in card with processor, memory and computer program for controlling and / or regulating an ACC functionality in a motor vehicle. The additionally provided processor prevents that or the other processors of the electronic system 1 be overstretched by the additional ACC functionality. In general, the integration of an additional hardware plug-in is accompanied by the integration of a corresponding software plug-in.

At the in 1 illustrated embodiment are the plug-ins 3.1 to 3.n however realized in software. The entire electronic system 1 So is a computer program whose functionality by adding or removing plug-ins 3.1 to 3.n be extended, changed or reduced can.

Below the base interface 2 is a basic software 4 provided that includes a fixed, permanent part of the computer program, which is not changed by adding or removing plug-ins. The basic software relates, for example, to communication via bus drivers (for example, a CAN software). Also, in the base software 4 Defined the way the plug-ins work 3.1 to 3.n with the rest of the computer program, regardless of the number and type of plug-ins connected 3.1 to 3.n , It also includes the basic software 4 a so-called identification list 5 to which the base interface 2 during the initialization of the electronic system 1 at least indirectly. In the identification list 5 are all in the electronic system 1 theoretically available variables (variables, functions, etc.) are listed (see left column of the identification list 5 ; IDl to IDm) and explained (compare right column of the ID list 5 ; A, B, C to M). The identification list 5 becomes for the entire system 1 and not for the currently plug-ins 3.1 to 3.n created. That's why it's independent of the number and type of plug-ins connected 3.1 to 3.n always the same content. More precisely, the quantities are resolved via the corresponding names or Ids. These names or Ids are agreed in advance and in the identification list 5 managed.

The basic interface 2 is based on the base software 4 of the electronic system 1 is set up and is responsible for the resolution of the interfaces between each plug-in 3.1 to 3.n responsible. The basic software 4 represents the part of the computer program that is not structured according to the plug-in concept (for example, low-level software).

In the present invention, a distinction is made between actual plug-in part 9 and plug-in interface 10 , The structure of the plug-in 3.1 to 3.n is in 2 shown in more detail. The part 9 of the plug-in 3.1 to 3.n includes the actual functionality of the plug-in 3.1 to 3.n and the part 10 the actual initialization function. The part 9 the plug-ins 3.1 to 3.n includes at least one additional or modified functionality to the system 1 be made available during the term. This functionality may be realized by one or more processes included in the part 9 are included for the functionality. The plug-in interface 10 has no functionality at runtime of the computer program, but contains the information 8th (such as the sizes of functionality used 9 ), which are needed to initialize the function. The initialization itself takes over the basic interface 2 ,

Starting from the initialization function 10 becomes a so-called initialization table 22 called (reference number 23 ). Through the initialization table 22 knows the basic interface 2 the addresses of the initialization functions. The call contains the argument 23 a pointer to initialization routines that in another table 24 are stored. The initialization routines from the table 24 contain the actual functionality of the initialization functions. From the base interface 2 then becomes an address (or pointer) to the corresponding initialization routine in the table 24 to the initialization function 10 returned (reference number 25 ).

In 4 is another electronic system according to the invention 1 represented according to a further preferred embodiment. The system 1 includes a plurality of superimposed cascaded base interfaces 2 , A lower base interface 2 is considered a master interface 2.1 educated. The basic interfaces arranged above 2 are called sub-interfaces 2.2 educated. To all interfaces 2.1 . 22 are plug-ins 3.1 to 3.n and / or sub-interfaces 2.2 connected. The to the interfaces 2.1 . 2.2 connected plug-ins 3.1 to 3.n are in 4 only symbolic, dashed and in small numbers, shown. At the in 4 System structure shown are therefore some plug-ins 3.1 to 3.n not directly, but only indirectly via sub-interfaces 2.2 to the master interface 2.1 connected.

The interfaces 2.1 . 2.2 cover different areas. The visibility concept offers the possibility of using several mutually delimited variable areas, for example public, private, protected, etc.). The variables are encapsulated in the corresponding areas.

At the in 4 illustrated embodiment, the interfaces 2.1 . 2.2 only in two different areas, namely the public sector 11 and the private area 12 divided. Only those in the public area 11 an interface 2.1 . 2.2 attached public sizes are for a subordinate (and thus higher ranking) interface 2.1 . 2.2 visible, noticeable.

After initialization are in the system 1 out 4 So the following views are given: The public area 11 , starting from the master interface 2.1 , extends over the public areas 11 the sub-interfaces 2.2 with the designations C, D and F. That means from the public area 11 the master interface A can out to the public area 11 the sub-interface C, as well as the public Be rich 11 the sub-interface D are accessed. In other words, the public areas of the sub-interfaces C, D are from the public area 11 the master interface A out accessible. The public area 11 the sub-interface F is for the public area 11 the sub-interface D visible.

The public area 11 the sub-interface E is visible for the sub-interface C, but not for the master interface A. This is because of the public area 11 the sub-interface E applied sizes at the private area 12 the sub-interface C and therefore are not visible from the underlying interface A. The private area 12 , starting from the master interface A, extends over the private area 12 the master interface A and the public area 11 the sub-interface B.

The inventive initialization method for an electronic system 1 is based on the flowchart 3 explained in more detail below. The procedure begins in a function block 30 , In a functional block 31 turns the base interface 2 or the master interface 2.1 to a first plug-in 3.1 or to a sub-interface 2.2 , of the electronic system 1 , The plug-in 3.1 transmitted to the base interface 2 Information regarding the processes that it performs. This information relates, for example, to the time frame of the processes, the priorities of the individual processes, etc.

Besides, the plug-in shares 3.1 in a function block 32 with which variables (variables, functions, structures, etc.) he needs to process the processes.

Sub-interfaces 2.2 , are treated the same as plug-ins 3.1 to 3.n , Also a sub interface 2.2 sends information to the subordinate (ie higher-level) base interface 2 regarding the processes that are executed by the plug-ins that connect to the sub-interface 2.2 are connected. It also shares the sub-interface 2.2 which sizes are required by the plug-ins connected to them for the execution of their processes.

In the function block 32 starts the plug-in 3.1 with the transmission of the first required size to the basic interface 2 , To do this, the plug-in transmits 3.1 the appropriate identifier of the size to the base interface 2 , Then it will be in a function block 33 in turn for all other plug-ins 3.2 to 3.n or at all to the base interface 2 connected sub-interfaces 2.2 asked if they can provide the required size.

Once a plug-in 3.2 to 3.n can be provided, which can provide the required size, the further search can be set. It can also be set if a sub-interface 2.2 was found, which can provide the required size. In that case, the one plug-in would be 3.2 to 3.n or the sub-interface 2.2 provide the required size from or from the base interface 2 first learns that he or she can provide the required size.

But it is also conceivable that the search will continue until all other plug-ins 3.2 to 3.n and all sub-interfaces 2.2 were queried whether they can provide the required size. Out of all the plug-ins 3.1 to 3.n and sub-interfaces 2.2 , which can provide the required size, the one plug-in or that sub-interface 2.2 which has the process for determining the required size with the highest priority. In this case, the plug-in would 3.2 to 3.n or the sub-interface 2.2 be selected with the highest priority process for determining the required size.

Finally, it is also possible that just the last plug-in 3.2 to 3.n which can provide the required size is selected. Alternatively, also the last sub-interface 2.2 be selected, which can provide the required size.

When looking for a plug-in 3.2 to 3.n , which can provide the required size, or after a sub-interface 2.2 which can provide the needed size can be the base interface 2 also distinguish between public and private sizes. That means the base interface 2 the plug-ins 3.1 to 3.n and the sub-interfaces 2.2 queries whether they can provide the required size in the desired (private or public) area.

The key is that a plug-in 3.2 to 3.n or a sub-interface 2.2 which provides a certain size that the plug-in provides 3.1 needed during the execution of its processes. During the execution of its processes, the plug-in must 3.1 can access the provided size.

For this purpose, in a function block 34 then the plug-in 3.1 Information that allows him to access the required size in the appropriate place during the processing of its processes. For example wisely suggested that in the first plug-in 3.1 a pointer 13 is filed (cf. 1 ), which is on a storage area 14 in one of the other plug-ins 3.2 points. In the storage area 14 will be the one from the first plug-in 3.1 required size of the other plug-in 3.2 filed and possibly updated regularly. For the pointer 13 is in the plug-in 3.1 a field 15 provided in which the destination address of the pointer 13 can be stored. For other sizes, that of the plug-in 3.1 are needed for the execution of the processes are more fields 16 provided, in which also pointers can be stored in memory areas, where the required sizes can be picked up during the processing of the processes.

Alternatively, it is also possible that in a plug-in, for example in the plug-in 3.3 , only a single field 17 is reserved, though in the processes of the plug-in 3.3 several sizes are needed. In the field 17 is the address of a pointer 18 filed on a structure 19 points. The structure 19 can be in any plug-in 3.1 to 3.n or in the base software 4 be filed. In the structure 19 are stored at predetermined positions or in predetermined fields certain sizes. The sizes can either be directly in the fields of the structure 19 be stored, or in the fields are other pointers 20 stored on an appropriate storage area 21 in one of the plug-ins 3.1 to 3.n or in the base interface 2 refer where the required size is stored.

In this case, the plug-in becomes 3.3 When a certain size is needed, first at the beginning of the structure 19 jumped. There, depending on the required size, the corresponding field of the structure will be displayed 19 jumped. In the illustrated embodiment, the third field of the structure 19 jumped where an address of the pointer 20 on the storage area 21 in the plug-in 3.n is stored. From there, the current value of the required size is fetched. Thereafter, the processing of the interrupted process in the plug-in 3.3 continued.

Through the use of structures 19 can store space in the plug-ins for the pointers 13 . 18 be saved because instead of the fields 15 . 16 in plug-in 3.1 just a box in plug-in 3.3 must be kept.

In a query block 35 will check if the plug-in 3.1 information has been transmitted for all the quantities required by him, which allows him to access the variables during the processing of his processes. If not, becomes the function block 32 branches where the plug-in 3.1 with the transmission of the next required size to the basic interface 2 continues. The loop comprising the functional blocks 32 to 34 and the query block 35 will go through until the plug-in 3.1 for all sizes required by him information was transmitted.

Once that's the case, it becomes another query block 36 branches, where checked, whether all to the base interface 2 connected plug-ins 3.1 to 3.n and all sub-interfaces 2.2 the basic interface 2 have communicated what sizes they need to process their processes. If not, becomes the function block 31 branches where the next plug-in 3.2 or the next sub-interface 2.2 the basic interface 2 Informing about their processes. In the following loop comprising the blocks 32 to 35 will go to the next plug-in 3.2 then submit information where it can access the sizes it requires. The loop comprising the functional blocks 31 to 34 and the query blocks 35 and 36 will go through that until all at the base interface 2 connected plug-ins 3.1 to 3.n and all sub-interfaces 2.2 the basic interface 2 have communicated what sizes they need to process their processes. As soon as that is the case, the inventive method is in a functional block 37 completed.

Of course it is in deviation of in 3 also possible, initially all plug-ins 3.1 to 3.n and all sub-interfaces 2.2 inquire about the sizes they need and the answers of the plug-ins 3.1 to 3.n and sub-interfaces 2.2 first in a table or similar store. After that, all plug-ins 3.1 to 3.n and all sub-interfaces 2.2 then be queried which sizes they can provide in the context of the processing of the realized in them processes. These sizes could also be stored in a table or the like. Subsequently, the required and provided sizes stored in the tables would have to be appropriately correlated and the plug-ins would have to be correlated 3.1 to 3.n and the sub-interfaces 2.2 by means of the hands 13 . 18 be connected to each other.

Regardless of the specific implementation of the method according to the invention in detail, it is crucial that the system 1 connected plug-ins 3.1 to 3.n Information regarding the functions performed by them, that is, for example, in terms of priority, the time frame, etc. spend the processes realized in them. Likewise, the plug-ins would have 3.1 to 3.n specify the quantities that they need to process the processes they have realized, and specify the quantities that they use to process the processes be able to provide processes realized in them. All this information flows in the base interface 2 together and are processed there in a suitable manner. As a result of processing in the base interface 2 be to the plug-ins 3.1 to 3.n that need certain sizes, pointers 13 . 18 on storage areas 14 . 21 or structures 19 where they can pick up the required sizes during the execution of the processes, ie during the runtime of the computer program.

The method according to the invention is realized by a communication protocol that is based on at least one computing device of the electronic system 1 is processed. A computing device is in particular a microprocessor or a microcontroller. Such a computing device for processing the communication protocol is, for example, in the base interface 2 and in each of the plug-ins 3.1 to 3.n or in the sub-interfaces 2.2 available. When booting up the system 1 In addition to the operating system, the communication protocol for processing by the computing devices is loaded and executed fully automatically. Of course, the communication protocol may also be after a system reset 1 (so-called reset) are carried out without it a complete restart of the system 1 requirement.

If within the scope of the inventive initialization process, a request of the master interface 2.1 to a sub-interface 2.2 is directed to information regarding the executed functionalities, or processes, the required sizes and the sizes provided, directs the sub-interface 2.2 the request within the scope of the visibility concept to the plug-ins connected to it 3.1 to 3.n further.

In order to initialize from the various plug-ins 3.1 to 3.n and from the base software 4 To create a functional and executable program, the following steps are performed during initialization in addition to the steps described above:
The starting addresses of the processes to be executed from the plug-ins 3.1 to 3.n and the basic software 4 are entered in lists. These lists are from the master interface 2.1 for certain task periods of the operating system (for example 10 ms). During initialization, the processes to be called in the operating system tasks are entered in the corresponding lists of the scheduler. For split times (for example 30 ms), dividers are calculated which only start this call on the nth task pass (for example, in a 10 ms task every third time). The process lists of the master interface 2.1 are entered in the task management or the entries are retrieved from there. It should also be noted that a plug-in 3.1 to 3.n does not necessarily have to involve a process.

During the runtime of the computer program, ie after initialization, the plug-in functions access the hands 13 . 18 to the sizes they need. To have a clear communication between the plug-ins 3.1 to 3.n To ensure all sizes are referenced via a unique identifier, a so-called identification number ID. These identifiers include information about the physical content, unit, data type, and conversion formulas of the corresponding quantities. However, this requires a central point, which coordinates or manages all available identifiers. The coordination or administration of all available identifiers is carried out by the basic interface 2 under access to an identification list 5 ,

The initialization method according to the invention has a number of significant advantages:
On the one hand, it saves a considerable amount of time at the time of integration of the different plug-ins. If one or more of the plug-ins are supplied by a supplier, the supplier is responsible for structuring the plug-ins according to the visibility concept presented above. At the time of integration, only the plug-in needs to remain in the rest of the system 1 be inserted. Everything else is done by the master interface 2.1 fully automatic during initialization. That means the integrator does not have to make any adjustments to the rest system 1 (such as integration of processes or the like) make more. The system structure according to the invention can be used, for example, for a control unit, in particular for a motor vehicle control unit (eg an engine control unit), on which applications or functionalities are integrated by different suppliers.

Subsequent upgrades, this means a reloading of functionalities on a control unit in the field, is possible without having to reprogram it completely (flashing). The The system concept shown above enables the subsequent flashing of functionalities.

In retrospect, this means that a customer can download new program parts in the manner of a "software filling station". At a corresponding charging device, for example at a gas station or a workshop, a desired functionality can be downloaded (flashed) into a defined area of the control device. After initialization according to the method of the invention is this functionality in the overall system 1 or available in the vehicle without the customer having to intervene in any way.

Claims (16)

Method for initializing an electronic system ( 1 ) comprising at least one basic interface ( 2 ) and several plug-ins ( 3.1 , ... 3.n ), characterized in that - when initializing the electronic system ( 1 ) of the basic interface ( 2 ) through the plug-ins ( 3.1 , ... 3.n ) information is provided concerning: - at least one of the respective plug-in ( 3.1 , ... 3.n ) executed functionality; - sizes determined by the respective plug-in ( 3.1 , ... 3.n ) are required to perform the at least one functionality; - sizes determined by the respective plug-in ( 3.1 , ... 3.n ) after execution of the at least one functionality, - the individual plug-ins ( 3.1 , ... 3.n ) through the base interface ( 2 ) Information regarding: - which of the other plug-ins ( 3.1 , ... 3.n ) one of the plug-in ( 3.1 , ... 3.n ), and - an appropriate reference to the plug-in ( 3.1 , ... 3.n ), which provides the size, in that plug-in ( 3.1 , ... 3.n ), which requires the size. Method according to claim 1, characterized in that that the at least one functionality through at least one process is realized. Method according to claim 2, characterized in that that the information regarding the functionality is a time frame for executing the at least one process and a priority of at least involve a process. Method according to one of claims 1 to 3, characterized in that in the plug-in ( 3.1 , ... 3.n ), which requires a size, as a reference a pointer ( 13 ) to a memory location ( 14 ), at which the required size is replaced by one of the remaining plug-ins ( 3.1 , ... 3.n ) is stored. Method according to one of claims 1 to 3, characterized in that in the plug-in ( 3.1 , ... 3.n ), which requires a size, as a reference a pointer ( 18 ) on a structure ( 19 ) is stored, in which at a predetermined position, the required size is stored by one of the other plug-ins. Method according to claim 2 or 3, characterized in that, if a certain size of several plug-ins ( 3.1 , ... 3.n ), the size of the plug-in ( 3.1 , ... 3.n ) is used for further processing, whose process for determining the size has the highest priority. Method according to one of claims 1 to 5, characterized in that, if a certain size of several plug-ins ( 3.1 , ... 3.n ), the size of the plug-in ( 3.1 , ... 3.n ) is used for further processing, from which the basic interface ( 2 ) first receives the information that the plug-in ( 3.1 , ... 3.n ) or a process of the plug-in ( 3.1 , ... 3.n ) can provide the required size. Method according to one of claims 1 to 5, characterized in that, if a certain size of several plug-ins ( 3.1 , ... 3.n ), the size of the plug-in ( 3.1 , ... 3.n ) is used for further processing, from which the basic interface ( 2 ) receives the last information that the plug-in ( 3.1 , ... 3.n ) or a process of the plug-in ( 3.1 , ... 3.n ) can provide the required size. Method according to one of claims 1 to 8, characterized in that the basic interface ( 2 ) Access to an initialization table ( 22 ) with information about where each plug-in ( 3.1 , ... 3.n ) are stored. Method for initializing an electronic system ( 1 ) comprising at least one basic interface ( 2 ) and several plug-ins ( 3.1 , ... 3.n ), in particular according to one of the claims 1 to 9 , characterized in that one of the basic interfaces ( 2 ) as a master interface ( 2.1 ) and the other basic interfaces ( 2 ) as sub-interfaces ( 2.2 ), wherein to the master interface ( 2.1 ) except the plug-ins ( 3.1 , ... 3.n ) Sub-interfaces ( 2.2 ), to which in turn further sub-interfaces ( 2.2 ) and / or other plug-ins ( 3.1 , ... 3.n ) and so on, the interfaces ( 2.1 . 2.2 ) into different areas ( 11 . 12 ) and only those within the same range of interfaces ( 2.1 . 2.2 ) attached variables for subordinate interfaces ( 2.1 . 2.2 ) are visible. Method according to claim 10, characterized in that the interfaces ( 2.1 . 2.2 ) in a private area ( 12 ) and a public area ( 11 ) and only those in the public area ( 11 ) an interface ( 2.2 ) attached public sizes for a subordinate interface ( 2.1 . 2.2 ) are visible. Method according to one of claims 1 to 11, characterized in that each of the plug-ins ( 3.1 , ... 3.n ) or by the plug-ins ( 3.1 , ... 3.n ) one for a defined range of the electronic system ( 1 ) unique identifier (Id i) is assigned. Method according to Claim 12, characterized in that the identifiers (ID i) of the variables in an identification list ( 5 ) to which the basic interface ( 2 ) during the initialization of the electronic system ( 1 ) can access. Communication protocol for processing on at least one computing device of an electronic system ( 1 ), which has at least one basic interface ( 2 ) and several plug-ins ( 3.1 , ... 3.n ) during the initialization of the electronic system ( 1 ), characterized in that the communication protocol is programmed in such a way that - when initializing the electronic system ( 1 ) of the basic interface ( 2 ) through the plug-ins ( 3.1 , ... 3.n ) information is provided concerning: - at least one of the respective plug-in ( 3.1 , ... 3.n ) executed functionality; - sizes determined by the respective plug-in ( 3.1 , ... 3.n ) are required to perform the at least one functionality; - sizes determined by the respective plug-in ( 3.1 , ... 3.n ) after execution of the at least one functionality, - the individual plug-ins ( 3.1 , ... 3.n ) through the base interface ( 2 ) Information regarding: - which of the other plug-ins ( 3.1 , ... 3.n ) one of the plug-in ( 3.1 , ... 3.n ), and - an appropriate reference to the plug-in ( 3.1 , ... 3.n ), which provides the size, in that plug-in ( 3.1 , ... 3.n ), which requires the size. Computer program for processing on a computing device of a data processing system, wherein the computer program has at least one basic interface ( 2 ) and several plug-ins ( 3.1 , ... 3.n ), characterized in that - when the computer program is initialized, the plug-ins ( 3.1 , ... 3.n ) of the basic interface ( 2 ) provide information concerning: - at least one of the respective plug-in ( 3.1 , ... 3.n ), - sizes that are dependent on the respective plug-in ( 3.1 , ... 3.n ) are required for the execution of the at least one functionality, and sizes which are dependent on the respective plug-in ( 3.1 , ... 3.n ) are provided after execution of the at least one functionality; - the basic interface ( 2 ) the individual plug-ins ( 3.1 , ... 3.n ) Provides information concerning: - which of the other plug-ins ( 3.1 , ... 3.n ) one of the plug-in ( 3.1 , ... 3.n ) provides needed size; and - a corresponding reference to the plug-in ( 3.1 , ... 3.n ), which provides the size, in that plug-in ( 3.1 , ... 3.n ), which requires the size. Electronic system ( 1 ) with a computing device for processing a communication protocol, wherein the electronic system ( 1 ) at least one basic interface ( 2 ) and several plug-ins ( 3.1 , ... 3.n ), characterized in that - the plug-ins ( 3.1 , ... 3.n ) as part of the initialization of the electronic system ( 1 ) of the basic interface ( 2 ) provide information concerning: - at least one of the respective plug-in ( 3.1 , ... 3.n ) executed functionality; - sizes determined by the respective plug-in ( 3.1 , ... 3.n ) are required to perform the at least one functionality; - sizes determined by the respective plug-in ( 3.1 , ... 3.n ) after execution of the at least one functionality, - the individual plug-ins ( 3.1 , ... 3.n ) through the base interface ( 2 ) Information regarding: - which of the other plug-ins ( 3.1 , ... 3.n ) one of the plug-in ( 3.1 , ... 3.n ), and - an appropriate reference to the plug-in ( 3.1 , ... 3.n ), which provides the size, in that plug-in ( 3.1 , ... 3.n ), which requires the size.