MME White List Synchronization via NAS Rejection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The user-side white list may become inconsistent with the network-side white list when the Mobility Management Entity (MME) does not respond to Non Access Stratum (NAS) messages initiated by User Equipment (UE), leading to failed access and paging issues.
Innovation Solution
The MME acquires and stores information of CSGs to be deleted from the user-side white list and sends response messages to the UE, allowing it to delete specified CSGs, ensuring the user-side white list is consistent with the network-side white list, and enables successful paging by sending paging messages to the acquired CSGs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UE sets the user-side white list according to response messages from the MME, then the user-side white list can be updated, but when the MME does not respond to NAS messages, the user-side white list becomes inconsistent with the network-side white list
Solution Approach 1:
The MME proactively sends a rejection message to the UE containing information about CSGs that should be deleted from the user-side white list, even before the UE attempts to access those CSGs. This preliminary action ensures that the UE's white list is synchronized with the network-side white list, preventing inconsistency and eliminating the need for the UE to rely on positive responses for white list updates.
2Device complexity
If the UE deletes CSG from user-side white list only when receiving rejection message, then the white list update process is simple, but the UE cannot set the white list when MME does not send response message
Solution Approach 1:
Instead of the UE waiting for the MME to respond with acceptance or rejection messages to update the white list, the invention inverts the approach by having the MME send a rejection message that proactively provides information about CSGs to be deleted. This allows the UE to update its white list based on the rejection message alone, without needing positive responses, thereby maintaining simplicity while improving reliability.
3Productivity
If the MME pages the UE according to the network-side white list, then the paging process is efficient, but the paging fails when user-side white list is inconsistent with network-side white list
Solution Approach 1:
The MME sends a rejection message to the UE that includes feedback information about which CSGs should be deleted from the user-side white list. This feedback mechanism ensures that the UE's white list remains synchronized with the network-side white list, allowing the MME to successfully page the UE according to the network-side white list without encountering inconsistencies.
Data Source
AI summary
The present invention discloses methods and devices for setting user-side white list and paging UE, and relates to the field of communication. To solve the problem that the user-side white list is inconsistent with the network-side white list, the method for setting a user-side white list includes: Acquiring and storing information of CSG to be deleted from a user-side white list; receiving a second NAS message originated from a UE; and sending the UE a response message of the second NAS message, so that the UE deletes CSG specified by the information of the CSG from the user-side white list. To solve the problem that the MME may fail to pages the UE through the network-side white list when the user-side white list is inconsistent with the network-side white list, the method for paging UE includes: acquiring and storing information of CSG to be deleted from a user-side white list; and sending a UE paging message to CSG specified by the information of the CSG. The embodiments of the present invention can be applied to a mobile network accessed through an HeNB.


