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

S1 Paging failure #1134

Closed
RafalArciszewski opened this issue Aug 18, 2021 · 4 comments
Closed

S1 Paging failure #1134

RafalArciszewski opened this issue Aug 18, 2021 · 4 comments
Labels
Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request

Comments

@RafalArciszewski
Copy link

Hi @acetcom,
I am facing a problem with paging procedure on S1 interface with one of eNB from ZTE. Test was done with Open5gs v2.2.8.
After the UEContext is released MME is sending Paging message but this message is send on SCTP stream 0x1. This stream is regarded as 'UE-associatied-signalling'. In fact when I read 3gpp standard it seems that Paging messages should be send as a 'non UE-associatied-signalling' in SCTP stream 0x0.
This ZTE eNB has a strict implementation of SCTP streams and ignores the Paging messages. I had many problems related to SCTP with other EPCs to get connected.

Is it possible to change the MME code that Paging messages are sent as 'non UE-associated-signalling'?

3gpp reference 36.413 point 3.1 Definitions:
UE-associated signalling: When S1-AP messages associated to one UE uses the UE-associated logical S1-connection
for association of the message to the UE in eNB and EPC.
UE-associated logical S1-connection: The UE-associated logical S1-connection uses the identities MME UE S1AP ID
and eNB UE S1AP ID according to definition in TS 23.401 [11]. For a received UE associated S1-AP message the
MME identifies the associated UE based on the MME UE S1AP ID IE and the eNB identifies the associated UE based
on the eNB UE S1AP ID IE. The UE-associated logical S1-connection may exist before the S1 UE context is setup in
eNB.

I understand from above that after UEContextRelease procedure is done the MME and UE S1AP id are gone and Paging should be sent as 'non UE-associated signaling'.
Procedures described in this standard usually has a remark "The procedure uses UE-associated signalling". For Paging there is no such remark.

I attach also the pcaps for reference (one from Open5gs, second from other EPC):

open5gs_paging_fail.zip

d_paging_ok.zip

obraz

obraz

Regards,
Rafał Arciszewski

@acetcom
Copy link
Member

acetcom commented Aug 18, 2021

Hi @RafalArciszewski

I agree. So, I've changed to use Non-UE signalling connection when MME/AMF sends paging message.

Thank you so much!
Sukchan

@RafalArciszewski
Copy link
Author

Thanks for quick response and commit! I will test it.

Regards,
Rafał

@RafalArciszewski
Copy link
Author

It is working now. Thanks!

@pobk pobk added the Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request label Feb 18, 2023
@github-actions
Copy link

This issue has been closed automatically due to lack of activity. This has been done to try and reduce the amount of noise. Please do not comment any further. The Open5GS Team may choose to re-open this issue if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request
Projects
None yet
Development

No branches or pull requests

3 participants