5G Paging Collision Handling During Ongoing 5GMM Procedures

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current wireless communication systems experience transaction failures due to collisions between paging or notification messages and 5GMM specific procedures or service request procedures, particularly in high load or congestion scenarios, leading to missed mobile terminated transactions.

Innovation Solution

The UE buffers paging or notification messages during ongoing 5GMM specific procedures and re-attempts the transaction with an access category that is not barred, ensuring the message is handled once the procedure is complete or fails.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the UE processes paging or notification messages during ongoing 5GMM specific procedures, then the network can maintain continuous communication with the UE, but transaction failures occur due to procedure collisions and access barring

Engineering Contradiction:

Improvetransaction success rateVSAvoidprocedure completion efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The UE checks whether a 5GMM specific procedure is already ongoing before processing paging or notification messages. This preliminary check prevents procedure collisions by identifying conflicting states in advance, allowing the UE to defer message processing until the ongoing procedure completes, thereby avoiding transaction failures while maintaining network communication continuity

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism (the procedure status check and collision detection logic) between the paging/notification reception and the actual message processing. This intermediary layer detects when procedures are colliding and mediates by deferring message handling, thus resolving the conflict between maintaining communication and avoiding transaction failures

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the UE ignores paging or notification messages during ongoing 5GMM specific procedures, then procedure collisions are avoided, but mobile terminated transactions are missed

Engineering Contradiction:

Improveprocedure execution reliabilityVSAvoidmissed paging or notification messages

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The UE implements a feedback mechanism where it monitors the completion status of ongoing 5GMM specific procedures. When a paging or notification message is received during an ongoing procedure, the UE waits for procedure completion feedback, then processes the deferred message. This feedback loop ensures that messages are not lost but processed after the conflicting procedure completes, maintaining both procedure reliability and message delivery

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The UE performs a preliminary check of procedure status before ignoring or processing messages. By checking whether a 5GMM specific procedure is ongoing before taking action, the UE can make informed decisions about message handling, ensuring that messages are preserved and processed appropriately after procedure completion rather than being permanently ignored

Inventive Principle:

Principle #10Preliminary action

3Reliability

If the UE re-attempts transactions with different access categories, then access barring is bypassed and messages are delivered, but additional signaling overhead and delay are introduced

Engineering Contradiction:

Improvemessage delivery reliabilityVSAvoidtransaction completion time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The UE takes preliminary anti-action by checking access category barring status before attempting message processing. When access barring is detected, the UE proactively changes the access category to an unbanned one before processing the paging or notification message. This preliminary adjustment prevents transaction failures due to barring without requiring multiple retry attempts, thus reducing overall delay while maintaining reliable message delivery

Inventive Principle:

Principle #9Preliminary anti-action

Data Source

PatentUS12520226B2Paging collision with 5GMM specific procedure or service request procedure

Publication Date: 2026.01.06 APPLE INC

AI summary

If a paging or notification message is received by a user equipment (UE) when a UE-initiated 5GMM specific procedure or service request procedure is ongoing, a UE may buffer the paging or notification message. To buffer the paging or notification message, the UE may remember the pending mobile terminated transaction and re-attempt the registration or request procedure with the access category 0 (=MT_acc), if the ongoing UE-initiated 5GMM specific procedure or service request procedure fails due to access barring. If a 5GMM specific procedure or service request procedure is received by the network when a MT transaction is ongoing (i.e. a paging message with the access type set to 3GPP access or notification message via non-3GPP access with the access type indicating 3GPP access) the network may complete the incoming MT transaction and may remember the pending mobile terminated transaction and continue it once the MO transaction is completed.