# Cloud-Enabled Deployment of 5G Core Network with Analytics Features
## 4 The Testbed
### Slicing Configuration
* SessionManagementSubscriptionData:

_curl-X GET -http2-prior-knowledge '[[http://192.168.58.110:16005/nudr-dr/v1/subscription-data/imsi-66601000000001/66601/provisioned-data/sm-data?single-nssai=URLencoded](http://192.168.58.110:16005/nudr-dr/v1/subscription-data/imsi-66601000000001/66601/provisioned-data/sm-data?single-nssai=URLencoded)]([http://192.168.58.110:16005/nudr-dr/v1/subscription-data/imsi-66601000000001/66601/provisioned-data/sm-data?single-nssai=URLencoded](http://192.168.58.110:16005/nudr-dr/v1/subscription-data/imsi-66601000000001/66601/provisioned-data/sm-data?single-nssai=URLencoded))'_. The attempt to access the AM data was successful using the given query. The returned response was in the form of JSON file and contained the subscribed Aggregate Maximum Bit Rate (AMBR) data and S-NSSAI information. Similarly, an attempt to retrieve the SM subscribed information was successful. Curl request returned a JSON containing the desired Session Management data. One must note that the curl request required an additional URL encoded S-NSSAI parameter of the pair [SST: 1, SD: '000001'] for the UE1 slice. According to the 3 GPP standard for Nudr SBI [46], the S_NSSAI for the PDU session is a mandatory query parameter in the HTTP/2 URL for a given SM resource. ### Design Details of a Quasi-NEF

The implementation of the NEF has faced challenges due to the limitations in accessing the necessary information from other NFs, such as the PCF. The initial plan to replace event exposure with the scraping of real-time and on-demand information from NFs involved in Session Management and Policing has been abandoned. The misaligned implementation of the PCF makes it currently impossible to retrieve on-demand PDU session policies, and the current release of Open5 GS does not allow for access to the network state. However, it is possible to access UE-specific data, such as subscriber data stored in MongoDB, through the UDR. Therefore, we designed, proposed, and implemented an interface to the Unified Data Repository function. The aim is to propose a quasi-NEF that can be easily integrated with virtualized cloud-based deployments of the 5 GCN. The proposed NF is written in Python, a general-purpose scripting language that proved useful during the initial prototyping phase. Additionally, the _pycurl_ module accurately replaced the curl CLI program, ensuring that the SBI services examined in the previous sections would behave in the same manner when accessed via Python scripts. The quasi-NEF's goal is to aggregate 5G-related data that would be useful for a mobile network operator or a private 5G slice tenant. The implemented function is expected to: list all preemption-vulnerable UEs, list all preemption-capable UEs, and summarize slice data. Such slice summary consists of the following parts:

ALL_SUPPORTING_IMSIS, which is a list of UEs that support a given S-NSSAI. PER_DNN_AGGREGATED_BITRATE, which denotes the total Uplink/Downlink aggregated bitrate for a DN in a given slice. PER_DNN_COMMON_SUPPORTED_SSC, a parameter that outlines all SSC [21] modes present in a DN. PER_DNN_DEFAULT_REQUIRED_SSC, a parameter which names the default SSC mode that is common for the UEs within a slice for a DN. TOTAL_AMBR_UL, a parameter denoting a total Aggregated Maximum Bitrate for Uplink in the slice. TOTAL_AMBR_DL, a parameter denoting a total Aggregated Maximum Bitrate for Downlink in the slice. TOTAL_IMSIS, which is a number of UEs that support a given slice. Listing 7 presents a summary of Session Management data for a [SST:1 SD:000001] slice returned by the implemented quasi-NEF. Full source codes are published in [42].