Versions Compared

Old Version 1

changes.mady.by.user Eric Murray

Saved on

compared with

New Version 2

changes.mady.by.user Eric Murray

Saved on

Key

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

DRAFT

Attendees & Representation

...

  • Existing PRs:
    • PR #55: Update CAMARA Mobile Device Identifier API.yaml
      • Proposed changes:
        • Separates API into two endpoints:
          • retrieve-identifier to obtain individual device details
          • retrieve-type to obtain type of device
        • Add scopes for each endpoint
        • Add lastChecked field to indicate when information about device was last confirmed correct
        • Updates documentation on MSISDN being treated as secondary MSISDN by network
      • Fixes issues #47 and #30
  • Closed PRs:
    • None

Issues

  • New Issues
    • None
  • Existing Issues
    • Issue #47: Add ageOfInformation field to API response
      • Follows on from Discussion #35
      • Current API response gives no indication of when the physical device information was collected for the specified subscription identifier (e.g. phoneNumber). Dependent on the backend implementation, this information could have been collected some time earlier, and potentially be out of date
      • Current proposal is to introduce lastChecked response parameter, defined as follows:

...

AGREEMENT: Leave discussion open for now, but prioritise returning IMEI / IMEISV

  • Closed Discussions
    • None

Other Issues

  • Kevin raised the point that YAML schemas should use the common schemas defined in CAMARA_common.yaml where appropriate. Ideally, they could be directly referenced, though this can cause issues with some OAS viewers.
    • ACTION: Kevin to check how OAS viewers handle external references

Discussion on IMEI Fraud API

Note

This API will not be further discussed until API proponents attend the sub-project meetings.

For MTN proposal for the initial YAML, see here

  • See API Proposal submission here
  • Open Discussions:
    • #37: IMEI Fraud API Input
      • Proposal is just to use a single "IMEI" field, which would accept either IMEI or IMEISV
    • #34: What values should the IMEI Fraud API respond with to indicate reported ownership status?
      • The GSMA appear to have an existing Device Check service, which includes an API. How does the CAMARA proposal differ from this?
      • Kevin highlighted a GSMA video on their Device Check service.

...