Reputation: 11
I have a small query regarding someip sd, in vsomeip
stack eventgroups
for the server are configured as follows
{
"eventgroup" : "0x4465",
"events" : [ "0x778", "0x779" ],
"is_multicast" : "true"
}
server offers a service for the eventgroup 0x4465, when client subscribes to the event group id 0x4465 , client gets the notifications with event id as 0x0778 in someip header, is it correct? or client should get the notifications with event id as 0x4465(same as eventgroup id) in someip header.which is correct way
Upvotes: 1
Views: 1963
Reputation: 51
Eventgroups are only used in service discovery, but will not appear in the actual SOME/IP messages transferring the events.
The event groups are just logical groups of events, i.e. you could group events together that users of the service probably always want to use together. E.g. you could have an eventgroup for a temperature sensor, that contains one with the measured temperature value and another event with the sensor status. Users of that temperature sensors are probably always interested in both. The eventgroup id is the id needed for subscription in the service discovery. The single event ids are not used in service discovery. After subscription, the service provider will send SOME/IP events only using the single event ids (placed in the "method ID" field of the SOME/IP header).
Even if you don't need to logically group your SOME/IP events, you have to map your event at least to one eventgroup to allow subscription in service discovery.
Upvotes: 0
Reputation: 1021
Event Groups are just logical grouping of events, they only exist at the service discovery level SOME/IP-SD
.
The events themselves contain no information about the event groups, and will use the ids 0x778
and 0x779
.
Upvotes: 2