[mme] store paging info during context release #86
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spencersevilla
added a commit
that referenced
this pull request
Jan 17, 2024
spencersevilla
added a commit
that referenced
this pull request
Jan 24, 2024
spencersevilla
added a commit
that referenced
this pull request
Jan 25, 2024
spencersevilla
added a commit
that referenced
this pull request
Mar 7, 2024
spencersevilla
added a commit
that referenced
this pull request
Mar 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Somewhat convoluted bug with a simple fix. When MME receives a DownlinkDataNotification indicating an error and the UE is in state Connected, it (1) sends a UEContextRelease to teardown the existing S1AP sessions and then (2) sends a Paging message to the relevant enb to induce reconnection. We need to store Paging info in this function, before sending the ContextRelease, because otherwise we don't know the right bearer. If Paging info is not stored and the eNB never responds, we eventually get a crash emm-sm.c:140 because we cannot access the paging info.