AUTOSAR Partial Network Concept

KPIT
12/18/2019
Usage Guidelines

Do not forward this document to any non- authorized mail ID.

Contents of this material cannot be used in any other internal or external document without explicit
permission from Learning Organization at KPIT.

2 12/18/2019 © KPIT Technologies Limited

Copy Right Guidelines
© 2014 KPIT Technologies Limited, Bangalore, India. All Rights Reserved.

KPIT Technologies Limited believes the information in this document is accurate as of its publication
date; such information is subject to change without notice. KPIT Technologies Limited acknowledges
the proprietary rights of other companies to the trademarks, product names and such other
intellectual property rights mentioned in this document. Except as expressly permitted, neither this
documentation nor any part of it may be reproduced, stored in a retrieval system, or transmitted in
any form or by any means, electronic, mechanical, printing, photocopying, recording or otherwise,
without the prior permission of KPIT Technologies Limited and/ or any named intellectual property
rights holders under this document.

3 12/18/2019 © KPIT Technologies Limited

 Agenda

 Energy Management Introduction

 Partial Networking
 Partial Networking - Restrictions

© KPIT Technologies Limited

© KPIT Cummins Infosystems Ltd. 4
 Energy Management Introduction

The goal of efficient energy management in AUTOSAR is to provide mechanisms for power
saving, especially while bus communication is active (e.g. charging or clamp 15 active).
AUTOSAR R3.2 and R4.0.3 support only Partial Networking.

Partial Networking
 Allows for turning off network communication across multiple ECUs in case their provided
functions are not required under certain conditions. Other ECUs can continue to communicate on
the same bus channel.
 Uses NM messages to communicate the request/release information of a partial network cluster
between the participating ECUs

© KPIT Technologies Limited

© KPIT Cummins Infosystems Ltd. 5
 Energy Management Introduction

Partial Network Cluster (PNC)

PNC is a group of system signals necessary to support one or more vehicle functions that are
distributed across multiple ECUs in the vehicle network. This represents the system view of mapping a
group of buses to one ore more VFCs.

© KPIT Technologies Limited

© KPIT Cummins Infosystems Ltd. 6
 Energy Management – Partial Networking
Example scenario of a partial network going to sleep
Initial situation:
1
ECU A
 ECUs “A” and “B” are members of Partial Network Cluster (PNC) 1.
ECUs “B”, “C” and “D” are members of PNC 2.
1
 All functions of the ECUs are organized either in PNC 1 or PNC 2.
ECU B  Both PNCs are active.
2  PNC 2 is only requested by ECU “C”.
 The function requiring PNC 2 on ECU “C” is terminated, therefore ECU “C”
ECU C can release PNC 2.
2
This is what happens:
 ECU “C” stops requesting PNC 2 to be active.
ECU D
2  ECUs “C” and “D” are no longer participating in any PNC and can be
shutdown.
Physical CAN Bus  ECU “B” ceases transmission and reception of all signals associated with
PNC 2.
Partial Network Cluster 1
 ECU “B” still participates in PNC 1. That means it remains awake and
Partial Network Cluster 2
continues to transmit and receive all signals associated with PNC 1.
© KPIT Technologies Limited
 ECU “A” is not affected at all.
© KPIT Cummins Infosystems Ltd. 7
 Partial Networking
Role of Different BSW
Involved modules
modules in Partial
– Solution Networking
for CAN
Application Layer SW-C SW-C
• VFC to PNC to channel translation
• Coordination of I-PDU group • PNC management (request /
RTE switching Mode ComM_User release of PNCs)
or • Indication of PN states
• Start / stop I-PDU-groups request Request

System Services
Communication Services ComM_UserRequest
BswM ComM
PNC states
I-PDU GroupSwitch Network
PNC request/release Request Request
• Exchange PNC request / release
information between NM and ComM
COM information
NmIf ComMode

via NM user data

• Enable / disable I-PDU-groups

PduR Trigger Transmit

CanNm CanSM

Communication Hardware Abstraction

• Filter incoming NM messages CanIf
• Collect internal and external PNC requests
• Send out PNC request infocmation in NM user data
• Spontaneous sending of NM messages on PNC startup
CanTrcv

© KPIT Technologies Limited

© KPIT Cummins Infosystems Ltd. 8
 Partial Networking Restrictions
 Partial Networking (PN) is currently supported on CAN and FlexRay buses.
 LIN and CAN slave buses (i.e. CAN buses without network management) can be activated* using PN but no wake-
up or communication of PN information are supported on those buses
 To wake-up a PN ECU, a special transceiver HW is required as specified in ISO 11898-5.
 The standard wake-up without special transceiver HW known from previous AUTOSAR releases is still
supported.
 A VFC can be mapped to any number of PNCs (including zero)
 The concept of PN considers a VFC with only ECU-internal communication by mapping it to the internal
channel type in ComM as there is no bus communication and no physical PNC
 Restrictions for CAN
 J1939 and PN exclude each other, due to address claiming and J1939 start-up behavior
 J1939 need to register first their address in the network before they are allowed to start communication
after a wake-up.
 A J1939 bus not using address claiming can however be activated using PN as a CAN slave bus as described
above
 Restrictions on FlexRay
 FlexRay is only supported for requesting and releasing PNCs.
 FlexRay nodes cannot be shut down since there is no HW available which supports PN.
© KPIT Technologies Limited
© KPIT Cummins Infosystems Ltd. 9
 Partial Networking
Mapping of Virtual Function Cluster to Partial Network Cluster
SW-C SW-C SW-Component of VFC1
SW-C
4 6
2
SW-C SW-Component of VFC2
1 SW-C
SW-C 5 SW-C SW-Component of VFC3
3 7
CompositionType Communication Port

VFC1 VFC2 VFC3

Mapping of
VFC on PNC
PNC1 PNC2

ECU A ECU B ECU C

• Here both Partial Networks map to one CAN bus.

SW-C SW-C SW-C SW-C SW-C SW-C SW-C • One Partial Network can also span more than one
1 2 3 4 5 6 7 bus.

RTE RTE RTE

Basic Software Basic Software Basic Software PNC1 PNC2

ECU Hardware ECU Hardware ECU Hardware CAN

PNC1 CAN Bus PNC2

© KPIT Technologies Limited

© KPIT Cummins Infosystems Ltd. 10
 Questions

11 12/18/2019 © KPIT Technologies Limited

 Thank You

www.kpit.com

12 12/18/2019 © KPIT Technologies Limited