Issue Description
Q:
When configure service port traffic profile in N2000 BMS system, we can not confirm the traffic profile index in the host system.Some customer application systems configure service by the traffic profile index, for insuring the devices of a same model have same traffic profile index, with the devices we need to configure some traffic profiles, which include same index and parameter items.
There are two general versions of BMS V200R011 and V200R012, do they have same naming mechanism while synchronize traffic profile?
Handling Process
A:
1.With V200R011, BMS confirms reference relationship by comparing traffic profile parameters. For example, BMS system has a traffic profile "DEFAULT", someone device has a traffic profile with an index "7", both profiles have same parameters, when you add the device, BMS firstly compare the parameters, because both profile have same ones, so BMS will create a device profile with name "DEFAULT" and index "7", so BMS confirms the reference relationship.
2.With V200R012, BMS confirms reference relationship by comparing traffic profile name, For example, BMS system has a traffic profile "DEFAULT", someone device has a traffic profile with an index "7", both profiles have same parameters, when you add the device, BMS firstly looks for reference relationship by device traffic profile name from BMS global profiles.Because all traffic profiles have no name in the host device, so BMS can not find a suitable matching relationship, from BMS global profiles, so BMS have to name the device traffic profile as "ubr+(car rate value in the profile)".
