Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: amf determine ue.rattype in registration #144

Merged
merged 1 commit into from
Sep 23, 2024

Conversation

donald1218
Copy link
Contributor

@donald1218 donald1218 commented Sep 19, 2024

In TS 23.502 section 4.2.2.1, it is mentioned

the AMF determines the Access Type and RAT Type as defined in clause 5.3.2.3 of TS 23.501 [2]. 

However, the current AMF has not yet determined ue.rattype, which has caused ue.rattype to remain empty.


In TS 23.501 section 5.3.2.3 Registration Area management

For 3GPP access the AMF determines the RAT type the UE is camping on based on the Global RAN Node IDs 
associated with the N2 interface and additionally the Tracking Area indicated by NG-RAN.

Global RAN Node ID is define in TS 38.413
image

@ianchen0119 ianchen0119 merged commit 01f48e4 into free5gc:main Sep 23, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants