-
Notifications
You must be signed in to change notification settings - Fork 611
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
docs: Magma Outbound Roaming support #11690
Conversation
Issue: #11689 |
Thanks for opening a PR! 💯
Howto
More infoPlease take a moment to read through the Magma project's
If this is your first Magma PR, also consider reading
|
@Arsenii-Oganov do you still plan to move forward with this change? If yes then rebase and fix any other failing checks |
3701915
to
079bb9b
Compare
Oops! Looks like you failed the Howto
♻️ Updated: ❌ The check is still failing the Markdown lint check after the last commit. |
@Arsenii-Oganov similar to the CDR availability proposal, this one also needs Testing plan and Roadmap schedule as required from the TSC grant review guidelines |
@ardzoht this was added in magma/grants#23, here focus on technical design |
The following existing services will be ported to run in the Roaming Gateway: | ||
|
||
- Health | ||
- S8_proxy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as mentioned on gdocs, S8_proxy is a feg service. You shouldnt be labeling the service with the same name
Lets first fix everything on gdocs, and then complete the PR. Otherwise you will be working twice
https://docs.google.com/document/d/17OYrYw6PMxFEWi_Ubx8eD1Qt3UT2VbchR_FIT5ivxI0/edit#heading=h.8bgsd6xc866i
079bb9b
to
1ee4444
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The markdown lint check is failing and needs to be fixed.
@@ -0,0 +1,136 @@ | |||
# Outbound Roaming | |||
|
|||
Link to discussed detailed doc <https://docs.google.com/document/d/17OYrYw6PMxFEWi_Ubx8eD1Qt3UT2VbchR_FIT5ivxI0> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use proper markdown syntax for links.
|
||
When outbound roaming, the standard interfaces are s6a and s8 which allow the VPLMN to authenticate the SIM credentials with the home network and route user traffic back to the home network. See diagram below from 3GPP TS 23.401 V17.3.0 (2021-12). | ||
|
||
![arch](https://user-images.githubusercontent.com/93994458/154709583-14f9bb52-486b-4908-b250-e521627b6f04.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mermaid diagrams should be preferred over binary blob includes. They work in Github and DocuSaurus.
|
||
The Roaming Gateway diagram shows the services which will run in the Roaming gateway. These services will support the user plane data transport for both inbound roaming GTP aggregation and outbound roaming when traffic is home routed. | ||
|
||
![roaming gateway](https://user-images.githubusercontent.com/93994458/154709967-7cd453ba-2070-4733-9e3f-dcc6f38624d2.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mermaid diagrams should be preferred over binary blob includes. They work in Github and DocuSaurus.
|
||
Overall, when combined with the orchestrator and federation gateway, the proposed architecture is depicted below showing all key interfaces for inbound and outbound roaming. | ||
|
||
![arch](https://user-images.githubusercontent.com/93994458/154710530-f535e6c1-8221-4de4-9e7b-5fc974f2ee3d.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mermaid diagrams should be preferred over binary blob includes. They work in Github and DocuSaurus.
|
||
##### 3.2.1.1 Health (modified) | ||
|
||
In addition to the health metrics added in the GTP Gateway proposal for inbound roaming, the following health metrics will also be added to health: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to health
- This is either an superfluous suffix or there is a word (e.g. endpoint
) missing here.
|
||
##### 3.2.1.2 PolicyDB + SessionD + PipelineD + MobilityD(modified) | ||
|
||
The combination of policyDB, sessiond, and pipelined provide the PCEF functionality to the Roaming gateway for home routed data sessions. This ensures that policy rules, QoS profiles, Rating Groups, and charging can be applied to subscriber sessions while getting services from a VPLMN. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PCEF
acronym should be explained.
|
||
![arch](https://user-images.githubusercontent.com/93994458/154709583-14f9bb52-486b-4908-b250-e521627b6f04.png) | ||
|
||
Currently, Magma supports only inbound roaming where magma is the VPLMN and another operator/core is the HPLMN. Magma supports the client side of both S6a and S8 interfaces. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The acronyms VPLMN
and HPLMN
should be explained.
|
||
UE IP address allocation will be provided by MobilityD. The UE IP request will be moved from MME function to sessiond to provide consistency across Roaming Gateway and AGW. IP allocation via NAT will be supported with a configurable NAT pool for IPs. Other IP address allocation schemes are out of scope. | ||
|
||
In this phase, default bearer and general internet access is provided to home routed sessions. Dedicated bearer and other services are out of scope. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean by In this phase
? Maybe currently
was meant? Or is it part to be implemented?
The statement should be made unambiguous.
|
||
In the call flow below, red number messages indicate new functionality supported by a Magma element. | ||
|
||
![call flow](https://user-images.githubusercontent.com/93994458/154710857-f8f23a91-415a-48b9-ab08-cf58450a21c6.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mermaid diagrams should be preferred over binary blob includes. They work in Github and DocuSaurus.
|
||
## 4 Schedule & Commercials | ||
|
||
TBD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This content should be added before merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
new commit force pushed
Signed-off-by: Arsenii Oganov <[email protected]>
1ee4444
to
8668e77
Compare
This issue or pull request has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs in the next 14 days. |
This issue or pull request has exceeded its lifecylce and was automatically closed. Should you wish to continue working on this, please reopen it. |
Signed-off-by: Arsenii Oganov [email protected]
Summary
Magma Outbound Roaming support
Issue - #11689