# Cloud-Enabled Deployment of 5G Core Network with Analytics Features
## 4 The Testbed
### Slicing Configuration
According to the 3 GPP TS 29.508 specification [45], NEF relays SMF events to third-party applications via the _Nsmf_EventExposure service_. A code analysis of the Open5 GS SMF implementation showed that this service was unavailable. Furthermore, when accessing the _Namf_EventExposure_ service with a proper POST request, a _Invalid Resource_ code is returned. The above steps were repeated for the AMF-related _Namf_EventExposure_ service to check if mobility information could be exposed. Unfortunately, the result was the same. Since it is not possible to access the necessary resources to implement the NEF function, a different approach has been taken. The desired events are related to UE mobility and session management, so an alternative solution is to provide on-demand access to this information instead of using the Subscribe-Notify model. From the perspective of a mobile network operator, such a module would be very useful. The provided information should include the number and type of established PDU sessions, the anchoring AMF per UE, policy enforcement, QoS statistics, and overall slice capacity. Data related to active PDU sessions and QoS policies are provided by the PCF and can be extracted through the _Npcf_SMPolicyControl_ service API. The data regarding the overall PDU sessions can be accessed through UDR. _SessionManagementSubscriptionData_ is the Session Management data storage. The mobility information of the UE can also be accessed via UDR resource: _AccessAndMobilitySubscriptionData_. As stated above, the SMPPolicyControl service should be accessible for extraction of an individual Session Management (SM) Policy that is provided by the PCF. The data of a specific SM policy is supposed to be accessible by SMF at the _[apiRoot/npcf-smpolicycontrol/v1/sm-policies/smPolicy/ld]_ resource. However, issuing the HTTP/2 request returned an unexpected error code: '403 Invalid HTTP method', which is not defined in the PCF specification. However, the error is not relevant, as the GET method is supposed to be used to access a selected SM policy. Further investigation revealed that the PCF code responsible for handling the Npcf interface returns an error for any request that does not comply with the syntax _[apiRoot/npcf-smpolicycontrol/v1/sm-policies/smPolicy/delete]_. The PCF allows only for deletion of a given SM policy. Any attempt to extract the SM policy data with the GET method causes the PCF SBI server to return an error. As defined in UDR specification [46], the Access and Mobility Subscription Data, along with the Session Management Subscription Data, should be accessible through the following endpoints:

* AccessAndMobilitySubscriptionData \(\rightarrow\)

_/subscription-data/ueld/seringPlmnld/provisioned-data/am-data._
* SessionManagementSubscriptionData \(\rightarrow\)

_/subscription-data/ueld/seringPlmnld/provisioned-data/sm-data._

The HTTP/2 GET requests are designed to get the Subscription Data of UE1 and includes its IMSI in the URL:

* AccessAndMobilitySubscriptionData:

_curl-X GET -http2-prior-knowledge '[[http://192.168.58.110:16005/nudr-dr/v1/subscription-data/imsi-66601000000001/66601/provisioned-data/am-data](http://192.168.58.110:16005/nudr-dr/v1/subscription-data/imsi-66601000000001/66601/provisioned-data/am-data)]([http://192.168.58.110:16005/nudr-dr/v1/subscription-data/imsi-66601000000001/66601/provisioned-data/am-data](http://192.168.58.110:16005/nudr-dr/v1/subscription-data/imsi-66601000000001/66601/provisioned-data/am-data))'_.