Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Versions 1.9+ Wish List #15395

Open
lucasgonze opened this issue Mar 25, 2024 · 11 comments
Open

Versions 1.9+ Wish List #15395

lucasgonze opened this issue Mar 25, 2024 · 11 comments
Labels
tsc-discussion TSC discussions about process, proposal, amendments,

Comments

@lucasgonze
Copy link
Contributor

We need to define our goals.

@lucasgonze lucasgonze changed the title Versions 2+ Wish List Versions 1.9+ Wish List Mar 25, 2024
@barnsheltie
Copy link

Let's link this to the vision/roadmap repo content as well

@lucasgonze
Copy link
Contributor Author

Let's link this to the vision/roadmap repo content as well

Can you help find a link?

@barnsheltie
Copy link

The vision repo is here https://github.com/magma/magma/wiki/Goals-and-Vision,-Winter-2024

@jordanvrtanoski
Copy link
Contributor

jordanvrtanoski commented Mar 25, 2024

For regulatory purpose we need to implement

  • WRITE-REPLACE WARNING ELEMENTARY PROCEDURE for S1 and N1 to allow alert messages to be distributed from the core, and
  • TRACE ELEMENTARY PROCEDURES for S1 and N1 to allow tracing of the radio messaging

In addition, we need to continue the work on:

  • support full mobility (hand-over between AGWs)
  • support 5G (Nxx) interfaces for FeG to allow 5G roaming scenarios
  • IMS support
  • eSIM support

@jordanvrtanoski jordanvrtanoski added the tsc-discussion TSC discussions about process, proposal, amendments, label Mar 25, 2024
@edaspb
Copy link
Contributor

edaspb commented Mar 25, 2024

Duplicate from here

  1. Focus on stability. Investigate crashes, memory leaks, etc. v1.8 is still not production ready for WISP purposes.
  2. Subscriber scaling
  3. Support full mobility +1
  4. QoS Ploicies per DSCP/ToS.
  5. IMS support +1.
  6. eSIM support +1. As far as I see there is no technical obstacles to have eSIM with v1.8. Or some special support from the EPC is required?

@Radula76
Copy link

Radula76 commented Apr 9, 2024

eSIM is working in 1.8. the eSIM provider gives us a modified .csv file with the IMSI, OPC, K values. we add in data plan/profile/APN and provision in the Orc8r. The QR code images are supplied in a folder. the users need to have internet access to scan the QR code from the provider and download the profile. android devices are happy just to load the QR code and wait, iPhones try to immediately scan for the network and fail (if you are not in coverage). the profile still loads correctly. when the user is in coverage they need to manually select the eSIM data profile and activate on the network.
we are looking at adding in functionality to the Orc8r to make it easier to manage eSIM's, QR code loading, management from the provider website etc...

@edaspb
Copy link
Contributor

edaspb commented Apr 10, 2024

@Radula76, great experience! Thank you for sharing! Is it production scheme or you have implemented it in production?

@Radula76
Copy link

@edaspb We are in trials with friendly customers at the moment. We should launch some commercial networks this year.

@jao-tm
Copy link

jao-tm commented May 8, 2024

  • support full mobility (hand-over between AGWs) +1
  • support 5G (Nxx) interfaces for FeG to allow 5G roaming scenarios +1
  • IMS support +1
  • eSIM support +1
  • Focus on stability. Investigate crashes, memory leaks, etc +1

@lucasgonze
Copy link
Contributor Author

Kubernetes

@im-nonedone
Copy link

Quick question folks, when is this planning to be released?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tsc-discussion TSC discussions about process, proposal, amendments,
Projects
None yet
Development

No branches or pull requests

7 participants