Agenda

Antitrust Policy

• Action Items Review
•   Any comment on previous meeting minutes

Minutes

Administrative stuff

• CodeOwners: 

  • Pull request #8
  • Krishna Venkatachalam  for MTN
  • Ludovic Robert for Orange
  • Other Others

• Maintainers
  • Pull request #9
  • @sanjayoct14 , @KarishmaTayal for MTN
  • Ludovic Robert for Orange
  • Other Others

API Design

• Device Swap API could provided 2 distinct information:

  • Request last Device Swap date (When was the last device swap for the mobile line identified by the phone number +123456799?)
  • Check last Device swap by providing a delay (Does we had a device swap for the last 240 hours for the mobile line identified by the phone number +123456799?)
  •   Are we sharing same expectations of the API?
    • From Orange & Telefonica Yes
• Are we considering this information as independent one from the other ? We can have different privacy requirement, different way to commercialize it. Technical implementation feasibility should be considered.
  • TEFJorge: If both endpoints consider the same kind of data age limitation (maxAge maximum value equal to the retrieve date maximum age), both endpoints should be considered as common and it will mostly be up to the developer to choose the best mechanism for retrieving the information.
  • OrangeLudovic: slight preference to split in order to be more flexible (avoid partial implementation, marketing could differ). If the team prefere prefer to kep keep them in one yaml probably we should consider adding a monitorPeriod attribut to limit date retrieval (see discussion in SIM Swap here)
  • For Stefano during previous meeting this is 2 distinct commercial information and from business perspective this is different to sell.
• How multi-SIM can affect this design?
  • TEFJorge: See Jorge Garcia Hospital proposal : Proposal is to only consider new devices as a valid device swap event, e.g. establishing a margin of 1 or several months in which a device can be used in the same MSISDN without considering it a device Swap event, as no valuable information for the API consumers. Source here.
  • Probably we need to explore how 3GPP Montoting event CHANGE_OF_IMSI_IMEI_ASSOCIATION  works for multi-SIM.
  • Is Multi-SIM behaviour behavior a stopper to complete API design?  probably no...

Action items

•  Ludovic Robert to ask to Herbert Damker to proceed with administrative stuff for Maintainers & CodeOwners