Q&A. Morning Session (Release R23-11)

Timecodes

0:00 Intro
0:32 Is Time Validation applicable for both CP and AP?
01:39 Is the Network Firewall available only at Network or Services Level and only for N-PDUs or N-packets?
04:56 What is the plan for releasing the virtualization and the vehicle API gateway concepts?
06:04 Does AUTOSAR provide some example use-cases for the Firewall and for how the filter rules can be configured?
07:23 Will the new SOME/IP Architecture be slower due to the additional validations steps?
08:33 Who is responsible for updating the ACL and why is updating the configuration out of scope?
10:06 Regarding the secure SOME/IP ACL, is PEP & PDP done at client or at server side?
10:45 How is the modeling for the generation of the secure SOME/IP ACL handled, when a service is offered by one ECU and the subscriber is located on a different ECU?
11:56 In the TSN streaming use case, are streams similar to the Ethernet Audio Video Bridge?
13:07 In which AUTOSAR specifications are the functions of deep packet inspection described?
15:38 Does the New AP Architecture support microservice based applications?
16:31 Are there any plans to support containers and standards related to containers, for example, Open Container Initiative (OCI)?
17:50 How is AUTOSAR contributing to SOAFEE?
18:41 How do API & Service Interfaces differ?
20:26 What is the main difference between Signal-Based Communication & Service-Oriented Communication?
22:37 Is AUTOSAR Classic still important in the Zone Controller / High Performance Architecture? Which ECU is probably running based on AUTOSAR Classic?
24:23 AUTOSAR raised a concept to install the Firewall in the switch with a lightweight AUTOSAR stack, which would be a good idea to offload the MCU and enhance the whole pretension. Does AUTOSAR plan to provide more detail about this variant in future releases?
27:17 Has AUTOSAR released any specifications regarding Big Data?
28:55 Conclusion