When enodebd sends a GetState with installation params inside the CBSD entity should be updated in the db (with one exception).
The CBSD database entity is identified by the cbsd_serial_number.
When enodebd asks for CBSD's state (GetCbsdState), Domain Proxy looks it up by a matching serial number in the database.
Aside from sending back the CBSD State response to enodebd, Domain Proxy does one of two things:
If it finds a matching record withoutdigitalSignature field populated, it updates its installation parameters in the database with the ones that came from enodebd.
If it finds a matching record withdigitalSignature, it does not update its installation parameters.
NOTE: Please consider a scenario when a User can edit non-installation parameters. And special case here is editing CBSD serial_number - in which case such update should clear all installation parameters for that CBSD.
When
enodebdsends aGetStatewithinstallation paramsinside the CBSD entity should be updated in the db (with one exception).The CBSD database entity is identified by the
cbsd_serial_number.When
enodebdasks for CBSD's state (GetCbsdState), Domain Proxy looks it up by a matching serial number in the database.Aside from sending back the CBSD State response to
enodebd, Domain Proxy does one of two things:digitalSignaturefield populated, it updates its installation parameters in the database with the ones that came fromenodebd.digitalSignature, it does not update its installation parameters.NOTE: Please consider a scenario when a User can edit non-installation parameters. And special case here is editing CBSD
serial_number- in which case such update should clear all installation parameters for that CBSD.