Currently, the IMSI and MSISDN properties are associated with a MobileDeviceFacet and SIMCardFacet respectively. This doesn't allow a concept of either property changing.
Requirements
Requirement 1: MobileAccountFacet must house the properties IMSI and MSISDN. (Note - it currently does.)
Requirement 2: SimCardFacet must reference a MobileAccount and drop direct storage of the IMSI string.
Requirement 3: MobileDeviceFacet must reference a MobileAccount and drop direct storage of the MSISDN string.
Benefits
By relating the properties to a MobileAccountFacet, it allows the concept of an IMSI or MSISDN changing within the
same SIMCard or MobileDevice.
Risks
A change to the existing properties has the risk of breaking the implementation of current adopters.
Competencies demonstrated
Competency 1
Solution summary
Requirements 2 and 3 also fully describe the solution, implemented in PR 354.
[x] Milestone 1 is resolving CASE-Examples Issue 53. That might be doable right now, or it might require working through the remainder of the present Issue.
[ ] Transcribe all relevant content from UCO CP-37 into this issue, and archive that Confluence page when finished.
[ ] Review relevant email thread(s) and apply refreshed understanding to Requirements in this proposal.
[ ] Requirements to be discussed in Ontology Committee (OC) meeting, date TBD
Background
Currently, the IMSI and MSISDN properties are associated with a
MobileDeviceFacetandSIMCardFacetrespectively. This doesn't allow a concept of either property changing.Requirements
Requirement 1:
MobileAccountFacetmust house the propertiesIMSIandMSISDN. (Note - it currently does.) Requirement 2:SimCardFacetmust reference aMobileAccountand drop direct storage of theIMSIstring. Requirement 3:MobileDeviceFacetmust reference aMobileAccountand drop direct storage of theMSISDNstring.Benefits
By relating the properties to a
MobileAccountFacet, it allows the concept of an IMSI or MSISDN changing within the same SIMCard or MobileDevice.Risks
A change to the existing properties has the risk of breaking the implementation of current adopters.
Competencies demonstrated
Competency 1
Solution summary
Requirements 2 and 3 also fully describe the solution, implemented in PR 354.
Coordination