free5gc / amf Goto Github PK

License: Apache License 2.0

Go 100.00%

amf's Introduction

What is free5GC

The free5GC is an open-source project for 5th generation (5G) mobile core networks. The ultimate goal of this project is to implement the 5G core network (5GC) defined in 3GPP Release 15 (R15) and beyond.

For more information, please refer to free5GC official site.

Documentation

For document, please refer to free5gc.org/guide/.

Discussion

For questions and support please use the official forum. The issue list of this repo is exclusively for bug reports and feature requests.

Contributing

We welcome you for contribution via GitHub Pull Request.

Release Note

Detailed changes for each release are documented in the release notes. Detailed changes for each release are documented in the release notes.

License

free5GC is now under Apache 2.0 license.

amf's People

Contributors

Stargazers

Watchers

Forkers

ziseputi bjoern-r mrlnc am677 endrigoshi oldmonk-97 lexcc lfelipecunha craftone my5g free5gc-plus blaxmirror blorticus aweimeow ralfkundel zhonglin6666 stevenchiu30801 williamlin0504 chch1970 libaoyuan242 jay16213 jandbacker felixhuang9977 muthuramanecs03g vthiruveedula caixiong110 huanqiurenwu sutanuk yourtotoro umakantkulkarni mariakagi ryuichinamba-fj matsumu-y thakurajayl fasferraz jothuma nrg-uw aweglteo brchiu irenelou waetw s123tg chliu-nems ciromacedo ianchen0119 jordan0210 namssob eggegg123 swankoski tahamohamedabdalla haotingc teramoto-g bearjim t-matz tim-ywliu pruthvir28 sanxophone shouheinishi akhila-s06 ayoubchoura maazkhaleeq trilogy-group ubrovc cubukcuaykut callmeprofessorduan mahmoodgh giuliocarot0 gravestench abdul-rahuman-seeni-mohamed sabdulrahuman thevirg niranjankhare aviweit open6gc roy-hu brianchennn juanmagal ikcfl joshevanch hakiitakeru pzeina danielh1204 iamelisahi yekyli honysyang youshengliu andy89923 leon777-coder abrahamhwj naivepoi tim1207 donald1218 hanhongchen tsc11539 sashamelentyev gatici chiller2121 nathalie21005 thelurkingcat abousselmi

amf's Issues

Amf Event Exposure Subscription causes panic

Hey,
We're trying to post an AmfCreateEventSubscription, and encountered this erorr:

We can see that within the code it's trying to perform the following:

probably causes due that in line 39 there is a null pointer dereference

Unable to build the library

Hello,
I'm trying to build the library locally, but the build fails with compile errors, from a dependancy:

# git.cs.nctu.edu.tw/calee/sctp /Users/niru/go/pkg/mod/git.cs.nctu.edu.tw/calee/[email protected]/sctp.go:446:15: assignment mismatch: 4 variables but c.SCTPRead returns 3 values /Users/niru/go/pkg/mod/git.cs.nctu.edu.tw/calee/[email protected]/sctp.go:723:18: assignment mismatch: 4 variables but c.conn.SCTPRead returns 3 values /Users/niru/go/pkg/mod/git.cs.nctu.edu.tw/calee/[email protected]/sctp.go:788:28: too many arguments in call to listenSCTPExtConfig have (string, *SCTPAddr, InitMsg, *RtoInfo, *AssocInfo, func(string, string, syscall.RawConn) error) want (string, *SCTPAddr, InitMsg, func(string, string, syscall.RawConn) error) /Users/niru/go/pkg/mod/git.cs.nctu.edu.tw/calee/[email protected]/sctp.go:792:26: too many arguments in call to dialSCTPExtConfig have (string, *SCTPAddr, *SCTPAddr, InitMsg, *RtoInfo, *AssocInfo, func(string, string, syscall.RawConn) error) want (string, *SCTPAddr, *SCTPAddr, InitMsg, func(string, string, syscall.RawConn) error)

I'm compiling with go 1.14:

go version go version go1.14.15 darwin/amd64
Does the sctp library dependency need fixes, or amf needs to update the dependency to one that works?

Thanks in advance!

Fix AMF sends Registration Reject if Capability5GMM is nil

Hi,

The AMF is configured to set a registration reject if 5GMM Capability IE is not included. In some cases, for example with the OAI UE, the UE does not include this IE. I suggest we change the behavior to simply print a log warning and continue the registration procedure.

I'll make a PR to fix this issue.

Thanks.

AMF remains in the ContextSetup state after UE has sent SecurityModeReject and new InitialRegistration

According to 3GPP TS 24.501 the AMF should guard the NAS Security Mode procedure using the timer T3560.

Upon receipt of the SECURITY MODE REJECT message, the AMF shall stop timer T3560. The AMF shall also abort the ongoing procedure that triggered the initiation of the NAS security mode control procedure. Both the UE and the AMF shall apply the 5G NAS security context in use before the initiation of the security mode control procedure, if any.

On the first expiry of the timer T3560, the AMF shall retransmit the SECURITY MODE COMMAND message and shall reset and start timer T3560. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3560, the procedure shall be aborted.

So the AMF shall - at some point - exit the ContextSetup state and be ready to process the next Registration Request sent by the UE. Instead, the UE is sending Registration Request all the time that remains unanswered by the AMF in the ContextSetup state for the UE.

The AMF:

2022-01-19T10:34:30Z [INFO][AMF][App] amf
2022-01-19T10:34:30Z [INFO][AMF][App] AMF version:
        free5GC version: v3.0.6
        build time:      2021-11-16T15:25:18Z
        commit hash:     b3e99f97
        commit time:     2021-09-24T09:44:32Z
        go version:      go1.14.4 linux/amd64

The N2 interface:

2022-01-20T00:31:02Z [INFO][AMF][NGAP] Create a new NG connection for: 10.10.20.204:38412
2022-01-20T00:31:02Z [INFO][AMF][NGAP][10.10.20.204:38412] Handle NG Setup request
2022-01-20T00:31:02Z [INFO][AMF][NGAP][10.10.20.204:38412] Send NG-Setup response
2022-01-20T00:31:02Z [INFO][AMF][NGAP][10.10.20.204:38412] Handle Initial UE Message
2022-01-20T00:31:02Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750] Handle Registration Request
2022-01-20T00:31:02Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750] Authentication procedure
2022-01-20T00:31:02Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750] Send Authentication Request
2022-01-20T00:31:02Z [INFO][AMF][NGAP][10.10.20.204:38412][AMF_UE_NGAP_ID:750] Send Downlink Nas Transport
2022-01-20T00:31:02Z [INFO][AMF][NGAP][10.10.20.204:38412] Handle Uplink Nas Transport
2022-01-20T00:31:02Z [INFO][AMF][NGAP][10.10.20.204:38412][AMF_UE_NGAP_ID:750] Uplink NAS Transport (RAN UE NGAP ID: 1)
2022-01-20T00:31:02Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750] Handle Authentication Response
2022-01-20T00:31:02Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] Send Security Mode Command
2022-01-20T00:31:02Z [INFO][AMF][NGAP][10.10.20.204:38412][AMF_UE_NGAP_ID:750] Send Downlink Nas Transport
2022-01-20T00:31:02Z [INFO][AMF][NGAP][10.10.20.204:38412] Handle Uplink Nas Transport
2022-01-20T00:31:02Z [INFO][AMF][NGAP][10.10.20.204:38412][AMF_UE_NGAP_ID:750] Uplink NAS Transport (RAN UE NGAP ID: 1)
2022-01-20T00:31:02Z [WARN][AMF][NAS][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] Received Plain NAS message
2022-01-20T00:31:02Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] Handle Security Mode Reject
2022-01-20T00:31:02Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] Reject Cause: Security mode rejected, upspecified (24)
2022-01-20T00:31:02Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] UE reject the security mode command, abort the ongoing procedure
2022-01-20T00:31:27Z [INFO][AMF][NGAP][10.10.20.204:38412] Handle Uplink Nas Transport
2022-01-20T00:31:27Z [INFO][AMF][NGAP][10.10.20.204:38412][AMF_UE_NGAP_ID:750] Uplink NAS Transport (RAN UE NGAP ID: 1)
2022-01-20T00:31:27Z [WARN][AMF][NAS][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] Received Plain NAS message
2022-01-20T00:31:27Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] Handle Registration Request
2022-01-20T00:31:27Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] Authentication procedure
2022-01-20T00:31:27Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] Handle InitialRegistration
2022-01-20T00:31:27Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:750][SUPI:imsi-999990000000091] Send Registration Reject
2022-01-20T00:31:27Z [INFO][AMF][NGAP][10.10.20.204:38412][AMF_UE_NGAP_ID:750] Send Downlink Nas Transport
2022-01-20T00:31:27Z [ERRO][AMF][GMM] Capability5GMM is nil
2022-01-20T01:01:27Z [INFO][AMF][NGAP][10.10.20.204:38412] Handle Initial UE Message
2022-01-20T01:01:27Z [INFO][AMF][NGAP][10.10.20.204:38412][AMF_UE_NGAP_ID:750] Implicit Deregistration - RanUeNgapID[1]
2022-01-20T01:01:27Z [WARN][AMF][NAS][AMF_UE_NGAP_ID:750] Received Plain NAS message
2022-01-20T01:01:27Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:750] state mismatch: receieve gmm message[message type 0x41] at ContextSetup state
2022-01-20T01:01:52Z [INFO][AMF][NGAP][10.10.20.204:38412] Handle Initial UE Message
2022-01-20T01:01:52Z [INFO][AMF][NGAP][10.10.20.204:38412][AMF_UE_NGAP_ID:750] Implicit Deregistration - RanUeNgapID[1]
2022-01-20T01:01:52Z [WARN][AMF][NAS][AMF_UE_NGAP_ID:750] Received Plain NAS message
2022-01-20T01:01:52Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:750] state mismatch: receieve gmm message[message type 0x41] at ContextSetup state
...

Note, the GNB simulator is re-using the RAN UE NGAP ID all the time. If this seems to be the issue, please indicate when the GNB shall assign a new RAN UE NGAP ID. But then the AMF may pile up orphan data?

Also, there seems to be a Registration Reject (cause 111 - protocol error) to the first Registration attempt after the Security Mode Reject was processed by the AMF. The Capability5GMM is nil because the UE has no security context established. And because Capability5GMM is a non-cleartext IE, it would be included in the NAS Registration Request sent inside the NAS Security Mode Complete message. This did not happen due to the Security Mode Reject. Is this the reason for the protocol error?

After the Registration Reject, the AMF no longer responds to any Registration Request sent with the RAN UE NGAP ID. The Registration Request (the same content all the time - cleartext IEs only):

{"time":"2022-01-20T18:28:17Z","level":"debug","msg":"Ngap PDU [000f006c00000500550002000100260042417e00417900350199f999f0ff0101e7f676c1cb924e2bcca7e75f6ae2265460156b2d1bbea93003a83d046ad99f368a43fdbf67a008c54cb1d272762e0480a000000079000f4099f9990000e0001099f999000001005a4001180070400100]"}
{"time":"2022-01-20T18:28:17Z","level":"debug","msg":"Handler [cucpNgc] is sending NGAP [InitiatingMessage] message [15:initialUeMessage]"}

AMF Event Exposure NotifURL is not worked with CONTINUOUS and PERIODIC report.

Hi @free5gc-org,

I am trying to create a subscription from NEF to AMF using URL : http://X.X.X.X/namf-evts/v1/subscriptions and parameters are as below:

{
"subscription": {
"eventList": [
{
"type": "LOCATION_REPORT",
"immediateFlag": true,
"refId": 0
}
],
"eventNotifyUri": "http://localhost:9052/nnef-eventexposure/v1/subscriptions",
"notifyCorrelationId": "string",
"nfId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"subsChangeNotifyUri": "string",
"subsChangeNotifyCorrelationId": "string",
"anyUE": false,
"supi": "imsi-208930000000003",
"options": {
"trigger": "CONTINUOUS",
"maxReports": 30,
"expiry": "2022-07-20T11:30:31.124Z",
"repPeriod" : 1
}
},
"supportedFeatures": "FFFF"
}

event notify report URL of NEF is mentioned in "eventNotifyUri": "http://localhost:9052/nnef-eventexposure/v1/subscriptions" but NEF didn't get any CONTINUOUS LOCATION_REPORT of mentioned supi on eventNotifyUri.

is this feature is available or not ? if it is available, how to enable it and if not, is there any roadmap to develop this feature ?

Identity Procedure when UE GUTI is unknown

Last year I was PR'ing a patch: #28

If UE registers with 5G-GUTI (it has a context), free5gc may search
for a context on another AMF. If no context is found, it should
signal that to UE to trigger re-registration. Otherwise the UE may use
the (invalid) context again.

I think I made a mistake and misunderstood the standard; the behavior from the patch is wrong.

Current behavior:
If AMF cannot find a 5G-GUTI, it will send Registration Reject with cause "UE Identity cannot be derived".
That worked on the UE I tested last year, triggering a full re-attach.

Seems that NAS only specifies that cause for Service Request and Registration Update procedure, but not initial Registration Request.

Better:
If the AMF cannot interpret the GUTI, it should send an Identity Request for SUCI/IMSI. So the AMF would wait for the response and then carry on handling the initial Registration Request.

import path correction

Hello we need to correct import path in amf. For example,
"free5gc/lib/path_util" ==> github.com/free5gc/path_util
All files should be changed

AMF fails in Initial Context Setup when no SD is provisioned in the S-NSSAI delivered in NG Setup

2022-01-21T16:58:42Z [INFO][AMF][App] amf
2022-01-21T16:58:42Z [INFO][AMF][App] AMF version:
        free5GC version: v3.0.6
        build time:      2021-11-16T15:25:18Z
        commit hash:     b3e99f97
        commit time:     2021-09-24T09:44:32Z
        go version:      go1.14.4 linux/amd64

NG Setup:

bytes:
00150034000004001b00090099f999300000e0000052400a0380676e622d637563700066000d00000000010099f999000000080015400100

tAISliceSupportList: 1 item
    Item 0
        SliceSupportItem
            s-NSSAI
                sST: 01

AMF:
Fails to construct the Initial Context Setup Request

2022-01-21T16:48:27Z [DEBU][LIB][Aper] Encoding OpenType *ngapType.AllowedNSSAI to temp RawData (marshal.go:589) (/go/pkg/mod/github.com/free5gc/[email protected]/aper.go:24 github.com/free5gc/aper.perTrace)
2022-01-21T16:48:27Z [ERRO][AMF][NGAP][10.10.20.204:38412][AMF_UE_NGAP_ID:1] Build InitialContextSetupRequest failed : SEQUENCE OF Size is lower than lowerbound (/go/src/free5gc/NFs/amf/ngap/message/send.go:368 github.com/free5gc/amf/ngap/message.SendInitialContextSetupRequest)

after 6 sec the T3550 expires and the Registration Accept is retransmitted in a Downlink NAS Transport NGAP message.

2022-01-21T16:48:33Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-999990000000091] T3550 expires, retransmit Registration Accept (retry: 1) (/go/src/free5gc/NFs/amf/gmm/message/send.go:383 github.com/free5gc/amf/gmm/message.SendRegistrationAccept.func1)

With this, the UE is registered, but no Initial Context is set up.

Adding the SD in the NgSetup fixes the problem, but note, the SD in an optional parameter in the S-NSSAI.

UERANSIM + AMF CreateSmContextRequest Error: server no response

Hi Sir,
I am using UERAMSIM to do gnb and ue simulator.
The AMF side keep logging:
amf | 2022-03-17T06:04:09Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:84][SUPI:imsi-208930000000003] CreateSmContextRequest Error: server no response
amf | 2022-03-17T06:04:22Z [INFO][AMF][NGAP][10.100.200.1:35206] Handle Uplink Nas Transport
amf | 2022-03-17T06:04:22Z [INFO][AMF][NGAP][10.100.200.1:35206][AMF_UE_NGAP_ID:84] Uplink NAS Transport (RAN UE NGAP ID: 84)
amf | 2022-03-17T06:04:22Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:84][SUPI:imsi-208930000000003] Handle UL NAS Transport
amf | 2022-03-17T06:04:22Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:84][SUPI:imsi-208930000000003] Transport 5GSM Message to SMF
amf | 2022-03-17T06:04:22Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:84][SUPI:imsi-208930000000003] Select SMF [snssai: {Sst:1 Sd:010203}, dnn: internet]
nssf | 2022-03-17T06:04:22Z [INFO][NSSF][NsSelect] Handle NSSelectionGet
nssf | 2022-03-17T06:04:22Z [INFO][NSSF][GIN] | 200 | 10.100.200.102 | GET | /nnssf-nsselection/v1/network-slice-information?nf-id=7a2473f2-99f6-4d3c-b3a7-4497d470a749&nf-type=AMF&slice-info-request-for-pdu-session=%7B%22sNssai%22%3A%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D%2C%22roamingIndication%22%3A%22NON_ROAMING%22%7D |
nrf | 2022-03-17T06:04:22Z [INFO][NRF][DSCV] Handle NFDiscoveryRequest
nrf | 2022-03-17T06:04:22Z [INFO][NRF][GIN] | 200 | 10.100.200.102 | GET | /nnrf-disc/v1/nf-instances?dnn=internet&preferred-locality=area1&requester-nf-type=AMF&service-names=nsmf-pdusession&snssais=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D&target-nf-type=SMF&target-plmn-list=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
amf | 2022-03-17T06:04:25Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:84][SUPI:imsi-208930000000003] CreateSmContextRequest Error: server no response
mongodb | {"t":{"$date":"2022-03-17T06:04:26.988+00:00"},"s":"I", "c":"STORAGE", "id":22430, "ctx":"WTCheckpointThread","msg":"WiredTiger message","attr":{"message":"[1647497066:988193][1:0x7fa4c3005700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 264, snapshot max: 264 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0) base write gen: 15042"}}
amf | 2022-03-17T06:04:38Z [INFO][AMF][NGAP][10.100.200.1:35206] Handle Uplink Nas Transport
amf | 2022-03-17T06:04:38Z [INFO][AMF][NGAP][10.100.200.1:35206][AMF_UE_NGAP_ID:84] Uplink NAS Transport (RAN UE NGAP ID: 84)
amf | 2022-03-17T06:04:38Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:84][SUPI:imsi-208930000000003] Handle UL NAS Transport
amf | 2022-03-17T06:04:38Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:84][SUPI:imsi-208930000000003] Transport 5GSM Message to SMF
amf | 2022-03-17T06:04:38Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:84][SUPI:imsi-208930000000003] Select SMF [snssai: {Sst:1 Sd:010203}, dnn: internet]
nssf | 2022-03-17T06:04:38Z [INFO][NSSF][NsSelect] Handle NSSelectionGet
nssf | 2022-03-17T06:04:38Z [INFO][NSSF][GIN] | 200 | 10.100.200.102 | GET | /nnssf-nsselection/v1/network-slice-information?nf-id=7a2473f2-99f6-4d3c-b3a7-4497d470a749&nf-type=AMF&slice-info-request-for-pdu-session=%7B%22sNssai%22%3A%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D%2C%22roamingIndication%22%3A%22NON_ROAMING%22%7D |
nrf | 2022-03-17T06:04:38Z [INFO][NRF][DSCV] Handle NFDiscoveryRequest
nrf | 2022-03-17T06:04:38Z [INFO][NRF][GIN] | 200 | 10.100.200.102 | GET | /nnrf-disc/v1/nf-instances?dnn=internet&preferred-locality=area1&requester-nf-type=AMF&service-names=nsmf-pdusession&snssais=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D&target-nf-type=SMF&target-plmn-list=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
amf | 2022-03-17T06:04:41Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:84][SUPI:imsi-208930000000003] CreateSmContextRequest Error: server no response

Then the UE side keep logging：
UERANSIM v3.2.6
[2022-03-17 02:00:34.881] [nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2022-03-17 02:00:34.881] [rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2022-03-17 02:00:34.881] [nas] [info] Selected plmn[208/93]
[2022-03-17 02:00:34.881] [rrc] [info] Selected cell plmn[208/93] tac[1] category[SUITABLE]
[2022-03-17 02:00:34.881] [nas] [info] UE switches to state [MM-DEREGISTERED/PS]
[2022-03-17 02:00:34.881] [nas] [info] UE switches to state [MM-DEREGISTERED/NORMAL-SERVICE]
[2022-03-17 02:00:34.881] [nas] [debug] Initial registration required due to [MM-DEREG-NORMAL-SERVICE]
[2022-03-17 02:00:34.881] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:00:34.881] [nas] [debug] Sending Initial Registration
[2022-03-17 02:00:34.881] [nas] [info] UE switches to state [MM-REGISTER-INITIATED]
[2022-03-17 02:00:34.881] [rrc] [debug] Sending RRC Setup Request
[2022-03-17 02:00:34.882] [rrc] [info] RRC connection established
[2022-03-17 02:00:34.882] [rrc] [info] UE switches to state [RRC-CONNECTED]
[2022-03-17 02:00:34.882] [nas] [info] UE switches to state [CM-CONNECTED]
[2022-03-17 02:00:34.920] [nas] [debug] Authentication Request received
[2022-03-17 02:00:34.937] [nas] [debug] Security Mode Command received
[2022-03-17 02:00:34.937] [nas] [debug] Selected integrity[2] ciphering[0]
[2022-03-17 02:00:35.008] [nas] [debug] Registration accept received
[2022-03-17 02:00:35.008] [nas] [info] UE switches to state [MM-REGISTERED/NORMAL-SERVICE]
[2022-03-17 02:00:35.009] [nas] [debug] Sending Registration Complete
[2022-03-17 02:00:35.009] [nas] [info] Initial Registration is successful
[2022-03-17 02:00:35.009] [nas] [debug] Sending PDU Session Establishment Request
[2022-03-17 02:00:35.009] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:00:51.898] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:00:51.898] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:01:07.914] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:01:07.914] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:01:23.930] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:01:23.930] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:01:39.946] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:01:39.946] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:01:55.962] [nas] [error] PDU Session Establishment procedure failure, no response from the network after 5 attempts
[2022-03-17 02:01:55.962] [nas] [debug] Aborting SM procedure for PTI[1], PSI[1]
[2022-03-17 02:01:56.355] [nas] [debug] Sending PDU Session Establishment Request
[2022-03-17 02:01:56.355] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:02:12.979] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:02:12.979] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:02:28.995] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:02:28.995] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:02:45.011] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:02:45.011] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:03:01.027] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:03:01.027] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:03:17.043] [nas] [error] PDU Session Establishment procedure failure, no response from the network after 5 attempts
[2022-03-17 02:03:17.043] [nas] [debug] Aborting SM procedure for PTI[1], PSI[1]
[2022-03-17 02:03:17.244] [nas] [debug] Sending PDU Session Establishment Request
[2022-03-17 02:03:17.244] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:03:34.060] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:03:34.060] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:03:50.076] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:03:50.076] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:04:06.092] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:04:06.092] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:04:22.108] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:04:22.108] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:04:38.124] [nas] [error] PDU Session Establishment procedure failure, no response from the network after 5 attempts
[2022-03-17 02:04:38.124] [nas] [debug] Aborting SM procedure for PTI[1], PSI[1]
[2022-03-17 02:04:38.202] [nas] [debug] Sending PDU Session Establishment Request
[2022-03-17 02:04:38.202] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:04:55.141] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:04:55.141] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:05:11.157] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:05:11.157] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:05:27.173] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:05:27.173] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-03-17 02:05:43.189] [nas] [warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[2022-03-17 02:05:43.189] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]

Would you mind giving me some advice?
Thank you in advance.

Best,
Ziran