we have observed some cases where the smf receives a CreateSessionRequest (from sgwc) for a preexisting session. Currently (when in state operational) the smf just silently drops this message, which in turn blocks the rest of the registration procedure. Preferred idempotent behavior would be to handle the CSR message by removing any active sessions and proceeding as if it were a new request.
we have observed some cases where the smf receives a CreateSessionRequest (from sgwc) for a preexisting session. Currently (when in state operational) the smf just silently drops this message, which in turn blocks the rest of the registration procedure. Preferred idempotent behavior would be to handle the CSR message by removing any active sessions and proceeding as if it were a new request.