I noticed something suspicious in the AUSF implementation, but I'm not sure if it's actually a bug
a) global variable
var ausfContext AUSFContext // global variable
b) There are add functions, but no delete functions.
// Add
func AddAusfUeContextToPool(ausfUeContext *AusfUeContext) {
ausfContext.UePool.Store(ausfUeContext.Supi, ausfUeContext)
}
func AddSuciSupiPairToMap(supiOrSuci string, supi string) {
ausfContext.suciSupiMap.Store(supiOrSuci, newPair)
}
// there is no delete functions, such as:
// func DeleteAusfUeContextFromPool(supi string) { ... }
// func DeleteSuciSupiPairFromMap(supiOrSuci string) { ... }
With a massive number of users, this would lead to unbounded memory growth.
Is this a case of human resource constraints, or is there actually no need for this method?
I noticed something suspicious in the AUSF implementation, but I'm not sure if it's actually a bug
a) global variable
b) There are add functions, but no delete functions.
With a massive number of users, this would lead to unbounded memory growth.
Is this a case of human resource constraints, or is there actually no need for this method?