It is not a new service here, only a saved one that has come within range again.
 
The only way a service would have that many property changes would be if it were either a service coming within range, or a service that has had every possible property changed at the same time, in which case it would be a new service as the path would be different and not handled by this check. I think the chances of a known/saved service changing every property (or, rather, more than 20. In actuality it is 22) at the exact same time is rather slim. It wouldn't, as connman's paths are made up from name and encryption type.

To connman all it takes for it to create a new service is the encryption type or name being changed.