Hi there, my name is Samir
Bhagwat and I'm with Intrepid Control Systems. I am the Director
of Quality Assurance and Engineering Services I'm here and gonna talk about service
oriented architectures and specifically about SOME/IP. With the new technologies for data
and autonomy, we do see a need of high data transmits and a complex data type communications.
With traditional signal-based communications there are certain limitations in SOME/IP and service
oriented architectures try to addres
s those needs. Intrepid has been part of providing products and
solutions for SOME/IP and essentially Vehicle Spy X and neoVI are the products which have our
own SOME/IP service discovery stack. This means when you are going to test your architectures for
SOME/IP, these products could be helpful for you. So this is neoVI Pi which has a Raspberry
Pi along with our CAN interface hardware and this is one of the devices I would highly
recommend to use for profiling and running your SOME/IP stac
ks. It has Linux because there is
Raspberry in there and this device along with a media converter and a switch can form a good
platform to architect your SOME/IP running inside an ECU. Along with this, I would recommend using
Vehicle Spy X. Vehicle Spy X has our own service discovery stack and it is also accessible through
python interface. As you know, Vehicle Spy X is our cross platform, new, modern, architecture BUS
analyzer and it has our own AutoSAR Com stack for communication network
testing. Conceptually, a
service oriented architecture is different than signal oriented architecture because here there
is a process where you can discover what services are offered by which endpoints and that is called
Service Discovery. Once Service Discovery happens, a provider and a consumer establish a
contract, a runtime dynamic contract, where a provider is going to provide needed
services to a consumer ECU. These architectural changes are driven because of things like zonal
archit
ectures and software defined vehicles. So service oriented communication is the future we
believe and with the new Zonal Architecture and software defined vehicle architectures allows,
with the help of the OTA, post-production update of the vehicles which is absolutely possible today
because of technologies like service oriented architectures and SOME/IP. SOME/IP is something
not very new and BMW in fact introduced that in 2011 as a middleware to do transactions when they
wanted to have thi
ngs which are independent of underlying hardware layers. More traction of
this technology has happened in recent years when actually AutoSAR specified it very clearly
and in the specifications in November release, the recent November release, they have a major
change in upgrade to SOME/IP specifications, including Service Discovery. And AutoSAR remains
on the forefront of the for specifications on SOME/IP and that is the technology currently every
OEM is following for service oriented archi
tecture in the the main part is the description of the
entire SOME/IP architecture and how the data is transacted is very well defined in AutoSAR
AR XML. Intrepid supports AR XML technology and Intrepid supports SOME/IP through different
product lines. One of the talks I have today is about how to use our media converters and switch
to have different endpoints, talk to each other on service architecture. Thanks for watching, this
is Samir Bhagwat from Intrepid Control Systems.
Comments
Idid not get one thing. Sameer said in this video neovi pi can be used to profile some/ip stack. And at same time neovi pi have its own some/ip stack. So for profiling am i suppose to run some /ip stack on neovi pi?