Service Request Message Setting for RRC Fallback Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication standards, such as 3GPP TS 24.501, fail to adequately describe the setting of service type and uplink data status information elements in service request messages when a user equipment receives a fallback indication from the radio resource control layer, leading to incomplete or incorrect handling of service request procedures.
Innovation Solution
The apparatus, method, and computer program provide mechanisms for determining specific conditions based on user equipment status to set appropriate service type and uplink data status information elements in service request messages, including handling various scenarios like emergency services, high priority access, and pending data sessions, ensuring accurate and complete message settings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If existing communication standards (3GPP TS 24.501) are used to handle service request procedures, then the basic service request functionality is provided, but the setting of service type and uplink data status information elements is incomplete or incorrect when fallback indication is received
Solution Approach 1:
The patent applies parameter changes by dynamically adjusting the service type and uplink data status information elements based on the fallback indication received from the RRC layer. When a fallback indication is detected, the service type is set to 'emergency services fallback' and the uplink data status is configured accordingly, transforming the message parameters to reflect the emergency fallback scenario accurately
Solution Approach 2:
The patent segments the service request handling into distinct scenarios by checking for the presence of fallback indication separately from other service request conditions. This segmentation allows the system to identify and handle emergency fallback cases specifically, ensuring that the information elements are set correctly for this particular scenario without affecting other service request types
2Productivity
If the service request procedure is invoked without checking specific conditions, then the procedure can be initiated quickly, but the service type and uplink data status information elements may be set incorrectly
Solution Approach 1:
The patent applies preliminary action by checking for the fallback indication condition at the beginning of the service request procedure, before invoking the actual service request. This preliminary check ensures that the correct information elements are prepared and configured in advance, preventing incorrect settings while maintaining efficient procedure initiation
Solution Approach 2:
The patent uses feedback from the RRC layer by monitoring the fallback indication signal and using this feedback to dynamically configure the service type and uplink data status information elements. This feedback mechanism ensures that the NAS layer has accurate information about the fallback scenario and can set the message parameters correctly without delaying the service request initiation
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Herein, an user equipment, a method and a computer program are provided. The user equipment comprises: at least one processor; and at least one memory including computer program code which, when executed by the at least one processor, causes the user equipment at least to: receive a fallback indication; invoke a service request procedure; and set a service type information element in a service request message.