Versions Compared

Old Version 3

changes.mady.by.user Zicheng Wang

Saved on

compared with

New Version Current

changes.mady.by.user Zicheng Wang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

○ only a distributor can only a Mobile Network Operator can allocate an MSISDN;


Detail Steps:

  1. Schema Creation, Credential Definition Creation. 
    1. Both Distributor (Mobile Network Operator is the Telecom company) and Producer (Manufacturer) (Tele Company) with create schemas )  with create schema (Telecom Schema) as standard in the entire supply chain. Both Producer (Manufacturer, called pineapple in our demo) and QA team ( is the QA team of theManufacturerthe Manufacturer) will together create Credential Definition.
    2. To simplify the reality, in the use case, the Manufacturer is a different entity compare to MNO (although could be the same some times). Also usually you have several distributors in this case GSMA, assumed only one to make it easier.
  2. Device Creation
    1. Once the device is created, the corresponding identity (DID Documents) of the device will be created. The device will be treated as an independent thing and receive the credential from Producer. The device shall receive the Credential from Producer, and shall shall  shall be assigned the series number from manufacturer.
  3. QA Testing
    1. The device will be passed through QA testing. In the demo, assume passing the QA.
    2. After QA pass, manufacturer will offer a Credential Offer for the device. The device shall receive the Credential from manufacturer. (currently, our credential including: manufacturer, sequence_id, bandwidth, QA_status, history = null)
  4. Passing device through Distributor
    1. After receiving 2 Credential from Producer and QA Team, the Distributor (Mobile Network Operator) will assigned and MSISDN in DID Documents of device. After that, the device can connect to the internet.

...

DID and Verkey: DIDs work as the role of trust anchor to the ledger, as we create Steward’s DID. The actions (including owner’s action and manufacturer's action) is written on the ledger, generate new DID/Verkey pairs. After that, Prover uses Credential Offer to create Credential Request. Trust Anchor then uses Prover's Credential Request to issue a Credential. Steward is then responsible of creating other actors like manufacturer (production line), QA team, distributor (mobile operator) and end customer at various stages. For all the actors, the Steward will onboarding actors mentioned above and then grant verinym and a trust anchor role.


Implementation

https://github.com/quantumcatwang/Telecom-IoT-device-SSI