Pau Espin
2be12903cb
The use of the Gy interface (SMF acting as CTF towards an OCS node) is mandated through configuration file. Default value "enable: auto" will only make use of it in case a Diameter peer announcing support for the Credit-Control Application is found. Upon subscriber session creation, and after auth check over Gx, the SMF will create a Gy session with the OCS and only after that step the SMF will accept the session back to the subscriber. The OCS may then grant some traffic volumes/time and ask to be notified back with updated measurements. In order to get the measurements, the SMF relies on PFCP URR configured to the UPF through Session Repoort Request messages. When closing the subscriber session, the SMF will also terminate the Gy session at the OCS. So far only some specifics parts of the Gy interface as well as the PFCP side are implemented. Those should be enough to at least have volume/time thresholds granted by the OCS, which then will be able to track subsriber resource use. This patch doesn't implement the OCS side of the Gy interface, that's left as a future exercise. The interface was tested using an OCS emulator implemented in TTCN-3 [1] [1] https://cgit.osmocom.org/osmo-ttcn3-hacks/ |
||
|---|---|---|
| .. | ||
| freeDiameter | ||
| logrotate | ||
| newsyslog | ||
| open5gs | ||
| systemd | ||
| 310014.yaml.in | ||
| csfb.yaml.in | ||
| meson.build | ||
| non3gpp.yaml.in | ||
| sample.yaml.in | ||
| slice.yaml.in | ||
| srslte.yaml.in | ||
| volte.yaml.in | ||
| vonr.yaml.in | ||