Skip to content
This repository has been archived by the owner on Sep 4, 2021. It is now read-only.

Re-implement TR-069 Basic Provisioning #2

Closed
jarlah opened this issue May 19, 2019 · 1 comment
Closed

Re-implement TR-069 Basic Provisioning #2

jarlah opened this issue May 19, 2019 · 1 comment

Comments

@jarlah
Copy link
Collaborator

jarlah commented May 19, 2019

Following things must be implemented:

  1. IN -> INr, including auto discovery of unit, authentication etc.
    DONE
  2. IN -> INr -> EM -> [GPN -> GPNr ->] GPV -> GPVr -> SPV -> SPVr -> EM
    Partially done, tr069 controller will automatically answer EM with dummy GPV and onwards.
    Done:
  • If Discover param is 1, or if discovery mode is true, or if deviceParameters.length == 0 (meaning only system params)
    • GPN: Ask CPE for parameter names in <Keyroot>.ManagementServer. (or be explicit)
    • GPNr: Store all parameters in unit type that does not already exist
  • GPV/GPVr: Ask CPE for all values to parameters with Read Always flag
  • SPV/SPVr: Ask CPE to set new values for parameters that has different values in ACS (for initial provisioning this is obviously none). Always set new semi random PII.
@jarlah
Copy link
Collaborator Author

jarlah commented May 22, 2019

This is now complete with basic operations like discover unit type, provisioning parameters etc. It might not be 100% complete, but complete enough to use as a base system provisioning devices.

@jarlah jarlah closed this as completed May 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant