CN102231683B - COM layer communication time limit monitoring method based on AUTOSAR - Google Patents

Abstract

The invention discloses an AUTOSAR-based COM layer communication time limit monitoring method, the implementation steps of which are as follows: 1) establish a monitoring alarm that starts following the COM layer, and create time limit parameters and timing parameters when each communication entity is initialized; 2) The monitoring alarm traverses all communication entities at regular intervals, and updates the timing parameters of each communication entity during each traversal; 3) judges the state of the communication entity according to the time limit parameter and the timing parameter, and if the communication entity sends the timeout, it notifies the upper layer that the communication entity sends Failure; if the receiving time of the communication entity is overtime, notify the lower layer that the communication entity has failed to receive; if the time point of the communication entity sending mode comes, then transmit the communication entity to the lower layer, and reset the time limit parameter of the communication entity. The invention has the advantages of less resource occupation, simple maintenance, convenient debugging, fast processing speed and high transceiving efficiency.

Description

COM layer communication time limit monitoring method based on AUTOSAR

technical field

The invention relates to the field of smart cars, in particular to an implementation method of a communication entity unit time limit mechanism based on AUTOSAR.

Background technique

AUTOSAR (Automotive Open System Architecture) is an open and standardized automotive electronics software architecture, which is jointly established by global automakers, component suppliers and other electronics, semiconductor and software system companies. The AUTOSAR protocol stack is used for network communication between ECUs of automotive electronics and between ECUs. It is a protocol stack similar to the OSI seven-layer model. Information is transmitted to the protocol stack from the RTE (RunTime Environment) layer above. In the stack are packed into frames and passed to the underlying hardware. As shown in Figure 1, the COM layer communication entity units mainly include the following types:

(1) Signal (atomic message), used for interaction between the Com layer and the upper layer;

(2) SignalGroup (atomic message group), which is composed of a group of atomic messages, is used for the interaction between the Com layer and the upper layer;

(3) IPDU (interaction layer communication data unit): the carrier of Signal and SignalGroup in the Com layer, used for the interaction between the Com layer and the lower layer.

In the specification of the AUTOSAR standard, an important feature of the COM layer in the COM communication stack is that it is required to provide a timeout monitoring mechanism for the communication entity unit, mainly including time limit monitoring related to the deadline and time limit monitoring related to the sending mode. Time limit monitoring specifically involves the following:

(1) Signal transmission deadline monitoring: After Signal sends a sending request from the upper layer, whether it is sent to the lower layer through the IPDU where the Signal is located within the specified time interval and receives a successful transmission confirmation from the lower layer, if within the specified time If the transmission fails within a certain period of time, the notification mechanism will be activated to notify the upper layer, otherwise, the monitoring will be canceled at the time when the successful confirmation is received.

(2) Signal reception deadline monitoring: monitor whether the IPDU where the Signal is located has been extracted by the upper layer within the specified time interval since it received the data during the interruption, and if it has not been extracted within the specified time, start the notification mechanism to notify the upper layer , otherwise the monitoring will be canceled at the time when it is extracted by the upper layer.

(3) SignalGroup sending deadline monitoring: monitor whether the SignalGroup has been sent to the lower layer through the IPDU where the SignalGroup is located within the specified time interval since the sending request of the upper layer and received a successful transmission confirmation from the lower layer, if within the specified time If the transmission fails within a certain period, the notification mechanism will be activated to notify the upper layer, otherwise the monitoring will be cancelled.

(4) SignalGroup reception cut-off time monitoring: Monitor whether the IPDU where SignalGroup is located has been extracted by the upper layer within the specified time interval since it receives the data in the interrupt, and if it is not extracted within the specified time, start the notification mechanism to notify the upper layer , otherwise the monitoring will be canceled at the time when it is extracted by the upper layer.

(5) Time monitoring of IPDU periodic transmission mode: as shown in Figure 2, after the IPDU passes through a user-configured periodic time limit, the sending operation to the lower layer is performed, and then a new periodic time monitoring is restarted, and the IPDU is sent infinitely. Among them, the periodic sending mode is to directly execute the IPDU sending operation in a fixed period.

(6) Time monitoring of the direct sending mode of the IPDU: as shown in Figure 3, after the IPDU passes through a user-configured cycle time limit, the sending operation to the lower layer is performed, and then a new cycle time monitoring is restarted, and the number of IPDU sending times is N times. Wherein, N is the total number of transmissions configured by the user, and the direct transmission mode operation is to perform N times of IPDU transmission operations at a fixed interval. Among them, the start of sending IPDU directly is driven by the upper layer of COM, such as the upper layer requests to send a Signal/SignalGroup.

(7) Time monitoring of IPDU hybrid transmission mode: as shown in FIG. 4 , time monitoring of IPDU periodic transmission mode is performed, and time monitoring of IPDU direct transmission mode is performed.

In the past practice, a monitoring alarm (Alarm) is usually configured for each time-limit monitoring of each physical unit above to realize the time-limit mechanism required by the AUTOSAR standard. For example: 5 IPDUs are configured on the Com layer, and each IPDU is configured with 5 Signals and 4 SignalGroups respectively. In extreme cases, each Signal and SIgnalGroup is configured with sending deadline and receiving deadline monitoring. In this way, the total number of monitoring alarms required for each IPDU is (5*2+4*2+1*2)*5=100, so AUTOSAR OS needs to support at least 100 monitoring alarms at the same time. Therefore there is such problem in prior art:

(1) The user needs to configure too many monitoring alarms, which directly causes the problem of occupying too many alarm resources of the system, making it difficult to maintain and debug.

(2) During the maintenance process, it is necessary to traverse too many monitoring alarms, which takes too much time, and may cause too many operations in the interruption, resulting in too long interruption time of the clock off, which will affect the accuracy of the sending time.

Contents of the invention

The technical problem to be solved by the present invention is to provide an AUTOSAR-based COM layer communication time limit monitoring method that occupies less resources, is simple in maintenance, convenient in debugging, fast in processing speed, and high in sending and receiving efficiency.

In order to solve the problems of the technologies described above, the technical solution adopted in the present invention is:

A kind of COM layer communication time limit monitoring method based on AUTOSAR, its implementation steps are as follows:

1) Establish a monitoring alarm that follows the start of the COM layer, and create time limit parameters and timing parameters when each communication entity is initialized;

2) The monitoring alarm regularly traverses all communication entities, and updates the timing parameters of each communication entity each time it traverses;

3) Judging the state of the communication entity according to the time limit parameter and the timing parameter, if the sending time of the communication entity is overtime, then notify the upper layer that the communication entity has failed to send; if the communication entity receiving time is overtime, then notify the lower layer that the communication entity has failed to receive; When the time point of the mode comes, the communication entity is transmitted to the lower layer, and the time limit parameter of the communication entity is reset.

As a further improvement of the present invention:

When creating the time limit parameter in the described step 1), if the communication entity is IPDU then establish three kinds of time limit parameters of direct sending times, direct sending interval, periodic sending interval, and be set to be used for monitoring the sending counter of direct sending times in the direct sending mode; If the communication entity is in the direct sending mode, set the two time limit parameters of direct sending times and direct sending interval; if the communication entity is in the periodic sending mode, set a time limit parameter of periodic sending interval; if the communicating entity is in the mixed sending mode, set Three time limit parameters of direct sending times, direct sending interval, and periodic sending interval; when the time point of the communication entity sending mode in the step 2) comes, if the communication entity is in the direct sending mode, then when the timing parameter triggers the direct sending interval, the The communication entity transmits to the lower layer and updates the sending counter. If the sending counter is equal to the number of direct sending times, the communication entity is terminated; if the communication entity is in the periodic sending mode, the communication entity is sent to the communication entity when the timing parameter triggers the periodic sending interval. Lower layer transmission; if the communication entity is in the mixed sending mode, on the one hand, when the timing parameter triggers the direct sending interval, the communication entity will be transferred to the lower layer, and the sending counter will be updated. If the sending counter is equal to the number of direct sending times, the direct sending will be ended The communication entity is transmitted in the mode; at the same time, the communication entity is transmitted to the lower layer when the timing parameter triggers the periodic sending interval.

The present invention has the following advantages:

1. The present invention solves the time limit monitoring problem of all communication entities through a monitoring alarm, greatly saves the number of monitoring alarm resources of the AUTOSAR OS occupied by the COM layer, and also eliminates the space related to the data structure of the monitoring alarm, and has the advantages of occupying resources Less, simple maintenance, convenient debugging, fast processing speed, high sending and receiving efficiency.

2. Since the present invention only operates one monitoring siren, the monitoring siren trigger linked list of dynamic maintenance is converted into a static time limit parameter and timing parameter, which is very easy to operate, and reduces the overhead of data structure maintenance, so the sending and receiving overhead is small, Sending and receiving efficiency is higher.

Description of drawings

FIG. 1 is a schematic structural diagram of the interaction principle between the COM layer and the upper layer and the lower layer in the prior art.

FIG. 2 is a schematic diagram of transmission monitoring in the IPDU periodic transmission mode in the prior art.

Fig. 3 is a schematic diagram of transmission monitoring in the IPDU direct transmission mode in the prior art.

FIG. 4 is a schematic diagram of transmission monitoring in an IPDU mixed transmission mode in the prior art.

Fig. 5 is a schematic flowchart of an embodiment of the present invention.

FIG. 6 is a schematic diagram of transmission monitoring for transmitting two IPDUs in a periodic transmission mode according to an embodiment of the present invention.

FIG. 7 is a schematic diagram of sending an IPDU in a periodic sending mode and another IPDU in a direct sending mode according to an embodiment of the present invention.

Fig. 8 is a schematic diagram of sending and monitoring two Signals.

Detailed ways

As shown in Figure 5, the COM layer communication time limit monitoring method based on AUTOSAR of the embodiment of the present invention, its implementation steps are as follows:

1) Establish a monitoring alarm that follows the start of the COM layer, and create time limit parameters and timing parameters when each communication entity is initialized;

2) The monitoring alarm regularly traverses all communication entities, and updates the timing parameters of each communication entity each time it traverses;

3) Judging the state of the communication entity according to the time limit parameter and the timing parameter, if the sending time of the communication entity is overtime, then notify the upper layer that the communication entity has failed to send; if the communication entity receiving time is overtime, then notify the lower layer that the communication entity has failed to receive; When the time point of the mode comes, the communication entity is transmitted to the lower layer, and the time limit parameter of the communication entity is reset.

When creating the time limit parameter in step 1), if the communication entity is IPDU, then set up three time limit parameters of direct sending times, direct sending interval, and periodic sending interval, and set the sending counter for monitoring the direct sending times in the direct sending mode; if communication If the entity is in the direct sending mode, set the time limit parameters of direct sending times and direct sending interval; if the communication entity is in periodic sending mode, set a time limit parameter of periodic sending interval; if the communicating entity is in hybrid sending mode, set direct sending Times, direct sending interval, three kinds of time limit parameters of periodic sending interval; When the time point of the communication entity sending mode in the described step 2) comes, if the communication entity is the direct sending mode, then when the timing parameter triggers the direct sending interval, the communication The entity transmits to the lower layer and updates the sending counter. If the sending counter is equal to the number of direct sending, the transmission of the communication entity is ended; if the communication entity is in the periodic sending mode, the communication entity is transmitted to the lower layer when the timing parameter triggers the periodic sending interval ; If the communication entity is in the mixed sending mode, on the one hand, when the timing parameter triggers the direct sending interval, the communication entity will be transmitted to the lower layer, and the sending counter will be updated; if the sending counter is equal to the number of direct sending times, then the direct sending mode transmission will be ended The communication entity; at the same time, when the timing parameter triggers the periodic sending interval, the communication entity is transmitted to the lower layer.

The monitoring alarm (ComAlarm) has a callback function ComAlarmAction. In step 2), the callback function ComAlarmAction is executed periodically to trigger traversal of communication entities and update the timing parameters of each communication entity. The timing parameters are stored in the IPDU control structure. The timing time (tick) for executing the callback function ComAlarmAction is very short, and the time limit parameters involved in the time limit parameters are integer multiples of ticks.

If the currently received communication entity is Signal or SignalGroup, set the time limit parameter ComRxTimeout and the timing parameter CurRxTime. ComRxTimeout represents the timeout period for collection, and the timing parameter CurRxTime is updated when the current Signal or SignalGroup is traversed. The timing parameter CurRxTime is initialized to the time limit parameter ComRxTimeout during initialization, and the timing parameter CurRxTime is automatically decremented by 1 each time it is updated. When the timing parameter CurRxTime is 0, it means that the Signal or SignalGroup collection time has expired, and the lower layer is notified that the Signal or SignalGroup collection failure.

If the currently sent communication entity is Signal or SignalGroup, set the time limit parameter ComTxTimeout and the timing parameter CurTxTime. ComTxTimeout represents the timeout period for sending, and the timing parameter CurTxTime is updated when the current Signal or SignalGroup is traversed. The timing parameter CurTxTime is initialized to the time limit parameter ComTxTimeout during initialization, and the timing parameter CurTxTime is automatically decremented by 1 each time it is updated. When the timing parameter CurTxTime is 0, it means that the sending time of the Signal or SignalGroup has expired, and the upper layer will be notified that the Signal or SignalGroup failed to send.

In this embodiment, each IPDU has 3 parameters ComDNFactor, ComDPFactor and ComPPFactor, and the 3 parameters ComDNFactor, ComDPFactor and ComPPFactor are used to transfer IPDU transmission mode information and transmit transmission mode parameters. The relationship between the three parameters ComDNFactor, ComDPFactor and ComPPFactor and the IPDU sending mode is shown in the following table:

ComDNFactor ComDPFactor ComPPFactor IPDU sending mode efficient efficient invalid Direct send mode invalid invalid efficient Periodic sending mode efficient efficient efficient Mixed sending mode

The parameters of ComDNFactor, ComDPFactor and ComPPFactor transfer mode correspond to the number of direct transmissions (CurNFactor), direct transmission interval (CurDTFactor), and periodic transmission interval (CurPTFactor).

When the Com layer starts, the monitoring alarm (ComAlarm) starts together, and the initialization of the monitoring alarm (ComAlarm) needs to do the following: load the CurTxTime of each Signal/SignalGroup as an invalid value; load the CurRxTime of each Signal/SignalGroup as an invalid value ; The CurNFactor, CurDTFactor, and CurPTFactor loaded with each IPDU are invalid values, invalid values, and ComPPFactor, respectively, where CurPTFactor is passed through parameters, and CurNFactor and CurDTFactor are defined in the COM layer. The above invalid value can also be the maximum value of the corresponding type. If the upper layer requests to transmit a Signal or SignalGroup, set the CurTxTime of the Signal or SignalGroup to ComTxTimeout. If the IPDU sending mode of the Signal/SignalGroup is the direct sending mode, the CurNFactor of the IPDU is also set to ComDNFactor, and the CurDTFactor is ComDPFactor. If the lower layer interrupt prompts that a Signal or SignalGroup has been received, set the CurRxTime of this Signal or SignalGroup to ComRxTimeout.

The specific process of executing the callback function ComAlarmAction is as follows:

a) Traversing the sending deadline monitoring auxiliary parameters of Signal and SignalGroup carried by IPDUs in all sending directions, and if valid, perform a self-decrement operation. If it is detected that the deadline for a certain Signal/SignalGroup has expired, the configured notification mechanism will be used to notify the upper layer that the Signal/SignalGroup has failed to send, and modify the auxiliary parameter of the Signal/SignalGroup’s sending deadline to an invalid value.

b) Traversing the receiving cut-off time monitoring of Signal and SignalGroup carried by IPDUs in all receiving directions, if it is valid, perform the self-decrement operation. If it is detected that the deadline for a certain Signal/SignalGroup has expired, the configured notification mechanism will be used to notify the upper layer that the Signal/SignalGroup has failed to receive, and modify the auxiliary parameter of the Signal/SignalGroup’s reception deadline to an invalid value.

c) Traverse the time limit monitoring related to the sending mode of the IPDU in all sending directions, and if it is valid, perform the self-decrement and decrement operation. If the period time limit of an IPDU in a certain periodic transmission mode has expired, the IPDU is sent to the lower layer once through the service provided by the lower layer, and the relevant auxiliary parameters of the period time limit of the IPDU are reloaded.

If a certain is in the direct sending mode, and the CurNFactor of this IPDU is not an invalid value, maintain it. When the relevant interval time limit of this IPDU has expired, send this IPDU once to the lower layer through the service provided by the lower layer, and let the CurNFactor of this IPDU decrease automatically. , and reset the auxiliary parameters related to the direct sending interval time limit of this IPDU, if the CurNFactor has been reduced to 0, then load it as an invalid value, and end the transmission of this direct sending mode IPDU.

As shown in Figure 6, both IPDU1 and IPDU2 are in periodic transmission mode, where:

The parameters of IPDU1 are: ComDNFactor=0, ComDPFactor=0, ComPPFactor=3,

The parameters of IPDU2 are: ComDNFactor=0, ComDPFactor=0, ComPPFactor=5. The periodic sending interval of IPDU1 is 3Ticks, and the periodic sending interval of IPDU1 is 5Ticks.

Since both IPDU1 and IPDU2 are in periodic transmission mode, among the three time limit parameters of IPDU1 and IPDU2, CurNFactor and CurDTFactor are all invalid values, and CurPTFactor is 3 and 5 respectively. Due to the characteristics of periodically sending IPDUs, two IPDUs must perform a downward transmission at this time. After every Tick, ComAlarm completes a maintenance. During the maintenance process, only CurPTFactor is valid in the control structure of the two IPDUs, so only CurPTFactor is allowed to perform self-decreasing and decrementing operations.

When Ticks==3, ComAlarm detects that the CurPTFactor of IPDU1 is 0, that is, the periodic sending period of IPDU1 has arrived, and executes the second transmission operation of IPDU1 to the lower layer, and reloads the CurPTFactor of IPDU1 as the ComPPFactor configured by the user.

When Ticks==5, ComAlarm detects that the CurPTFactor of IPDU2 is 0, that is, the periodic sending cycle of IPDU2 has arrived, and executes the second transmission operation of IPDU2 to the lower layer, and reloads the CurPTFactor of IPDU2 as the ComPPFactor of IPDU2 configured by the user (ie 5).

Every time after 3*k (k>2, k is a natural number) Ticks, ComAlarm detects that the CurPTFactor of IPDU1 is 0, that is, the periodic sending period of IPDU1 has arrived, and executes the kth downward transmission operation of IPDU1, and repeats The CurPTFactor loaded with IPDU1 is the ComPPFactor of IPDU1 configured by the user (that is, 3).

Every time 5*k (k>2, k is a natural number) Ticks, ComAlarm detects that the CurPTFactor of IPDU2 is 0, that is, the periodic sending period of IPDU2 has arrived, and executes the kth transmission operation of IPDU2 to the lower layer, and repeats The CurPTFactor loaded with IPDU2 is the ComPPFactor of IPDU2 configured by the user (that is, 5).

In this way, this ComAlarm is used to solve the problem of IPDU time limit monitoring in both periodic sending modes. Similarly, this method is also feasible when the number of such IPDUs expands to many times.

As shown in Figure 7, IPDU1 is in periodic sending mode, and IPDU2 is in direct sending mode, where:

The parameters of IPDU1 are: ComDNFactor=0, ComDPFactor=0, ComPPFactor=5,

The parameters of IPDU2 are: ComDNFactor=3, ComDPFactor=3, ComPPFactor=0.

The periodic sending interval of IPDU1 is 5Ticks, the number of direct sending of IPDU1 is 3 times, and the direct sending interval is 3Ticks.

When Ticks=0, COM is initialized, ComAlarm starts, and the auxiliary parameters CurNFactor, CurDTFactor, and CurPTFactor of IPDU1 are initialized to invalid values, invalid values, and 5 respectively; the auxiliary parameters of IPDU2 CurNFactor, CurDTFactor, and CurPTFactor are initialized to invalid values, value, invalid value. Due to the characteristics of periodically sending IPDUs, IPDU1 needs to perform a downward transmission at this time.

When Ticks=1, IPDU2 starts transmission due to the upper layer driver (such as the upper layer needs to send a Signal/SignalGroup). At this time, ComAlarm needs to set the auxiliary parameters CurNFactor, CurDTFactor, and CurPTFactor of IPDU2 to 3, 3, and invalid values respectively. Due to the characteristics of sending IPDU directly, IPDU2 needs to perform a downward transmission at this time, and let CurNFactor decrement once.

When Ticks==4, ComAlarm detects that the CurDTFactor of IPDU2 is 0, that is, the time limit for direct sending of IPDU2 has expired, and the second transmission operation of IPDU2 to the lower layer is performed, and the CurNFactor is automatically decremented to 1, and the IPDU1 is reloaded CurDTFactor is the ComDPFactor of IPDU2 configured by the user (that is, 3).

When Ticks==5, ComAlarm detects that the CurPTFactor of IPDU1 is 0, that is, the periodic sending time limit of IPDU1 has expired, and executes the second transmission operation of IPDU1 to the lower layer, and reloads the CurPTFactor of IPDU1 as the ComPPFactor of IPDU1 configured by the user (ie 5).

When Ticks==7, ComAlarm detects that the CurDTFactor of IPDU2 is 0, that is, the time limit for direct sending of IPDU2 has arrived, and the third transmission operation of IPDU2 to the lower layer is executed, and CurNFactor is automatically decremented to 0. At this time, IDPU1 completes 3 transmissions, and the three auxiliary parameters are set to invalid values until the next Signal/SignalGroup that causes this IPDU to start transmission arrives and starts again.

Every time 5*k (k>2, k is a natural number) Ticks, ComAlarm detects that the CurPTFactor of IPDU1 is 0, that is, the periodic sending cycle of IPDU2 has arrived, and executes the kth transmission operation of IPDU2 to the lower layer, and repeats The CurPTFactor loaded with IPDU2 is the ComPPFactor of IPDU1 configured by the user (that is, 5).

In this way, a ComAlarm solves the time limit monitoring problem of two IPDUs, a periodic sending mode, and a direct sending mode with N=3. Obviously, it is also possible to expand the number of such IPDUs to many, and still use this ComAlarm to monitor.

Since the time limit monitoring of an IPDU in the mixed sending mode can be regarded as two IPDUs: one in the periodic sending mode and the other in the direct sending mode, it can also be solved with a ComAlarm. Since the IPDUs between various periodic transmission modes are independent, ComAlarm can be used to solve the time limit monitoring problems related to the transmission of all IPDUs.

As shown in Figure 8, when creating the time limit parameter, configure Signal1: ComTxTimeout=7; configure Signal2: ComTxTimeout=3. That is, the sending timeout period of Signal1 is 7Ticks, and the sending timeout period of Signal2 is 2Ticks.

When Ticks=0, COM is initialized, ComAlarm is started, and the auxiliary parameter CurTxTime of Signal1 and Signal2 are initialized to invalid values. Every time a Tick passes, ComAlarm completes maintenance. During the maintenance process, if the CurTxTime of Signal is not an invalid value, it will be automatically decremented. If the CurTxTime is 0, it will trigger the sending timeout action of Signal to notify the upper layer and set CurTxTime to an invalid value.

When Ticks=1, the COM upper layer sends Signal1. At this time, the auxiliary parameter CurTxTime of Signal1 needs to be loaded as 7 in the ComAlarm.

When Ticks=2, the COM upper layer sends Signal2. At this time, the auxiliary parameter CurTxTime of Signal1 needs to be loaded as 3 in the ComAlarm.

When Ticks=5, the CurTxTime of Signal2 is automatically decremented to 0, and its CurTxTime is set to an invalid value, and the sending timeout action of Signal2 is triggered to notify the upper layer. Signal2 completes monitoring.

When Ticks=6, the successful sending confirmation of Signal1 is received, and Signal1 is sent successfully. Set its CurTxTime to an invalid value. Signal1 completes monitoring.

In this way, a ComAlarm is used to solve the problem of monitoring the sending deadline of two Signals. Since SignalGroup's sending deadline monitoring problem is basically the same as Signal's sending deadline problem, a ComAlarm can also be used to solve SignalGroup's sending deadline monitoring problem. Also, the number of Signals and SignalGroups can be increased. In the same way, a ComAlarm can also be used to solve the receiving deadline monitoring problem of Signal and SignalGroup. And the number of Signal and SignalGroup can be increased arbitrarily.

Since the time limit monitoring problem related to the sending mode of IPDU and the monitoring problem related to the deadline of Signal/SignalGroup are independent, they can be solved by the same ComAlarm in parallel. So far, this article uses a ComAlarm to solve the time limit monitoring problem of all communication entity units in the Com layer.

The above descriptions are only preferred implementations of the present invention, and the scope of protection of the present invention is not limited to the above-mentioned implementations. All technical solutions belonging to the principle of the present invention belong to the scope of protection of the present invention. For those skilled in the art, some improvements and modifications made without departing from the principles of the present invention should also be regarded as the protection scope of the present invention.

Claims (1)

1. A COM layer communication time limit monitoring method based on AUTOSAR is characterized in that its implementation steps are as follows: 1) Establish a monitoring alarm that follows the start of the COM layer, and create time limit parameters and timing parameters when each communication entity is initialized; 2) The monitoring alarm regularly traverses all communication entities, and updates the timing parameters of each communication entity each time it traverses; 3) Judging the state of the communication entity according to the time limit parameter and timing parameter, if the sending time of the communication entity is overtime, notify the upper layer that the communication entity failed to send; if the communication entity receiving time exceeds the time limit, notify the lower layer that the communication entity failed to receive; When the time point of the mode arrives, transmit the communication entity to the lower layer, and reset the time limit parameter of the communication entity; When creating the time limit parameter in the step 1), if the communication entity is an IPDU, then establish three time limit parameters, the number of direct transmission times, the direct transmission interval, and the periodic transmission interval, and set a transmission counter for monitoring the number of direct transmissions in the direct transmission mode; If the communication entity is in the direct sending mode, set the two time limit parameters of the direct sending times and the direct sending interval; if the communication entity is in the periodic sending mode, set a time limit parameter of the periodic sending interval; if the communication entity is in the mixed sending mode, set There are three time limit parameters: direct sending times, direct sending interval, and periodic sending interval; when the time point of the sending mode of the communication entity in step 2) comes, if the communication entity is in the direct sending mode, when the timing parameter triggers the direct sending interval, it will The communication entity transmits to the lower layer and updates the sending counter. If the sending counter is equal to the number of direct transmissions, the communication entity is terminated; if the communication entity is in the periodic sending mode, the communication entity is sent to the communication entity when the timing parameter triggers the periodic sending interval. Lower layer transmission; if the communication entity is in the mixed sending mode, on the one hand, when the timing parameter triggers the direct sending interval, the communication entity will be transferred to the lower layer, and the sending counter will be updated. If the sending counter is equal to the number of direct sending times, the direct sending will be ended The mode transmits the communication entity; at the same time, the communication entity is transmitted to the lower layer when the timing parameter triggers the periodic sending interval.

Images