[FS_DCE_MED] Key Issue #4 - Description for Automatic Resumption
This contribution from Samsung addresses Key Issue #4 concerning Automatic Resumption functionality in the context of the FS_DCE_MED study. The document responds to an LS from GSMA (S4-250755) requesting technical improvements to support automatic resumption service requirements developed by GSMA TSG IMSDCAS in GSMA PRD NG.129.
Core Functionality:
- Automatic resumption enables users to resume streaming experiences from the point where they left off
- Provides session continuity in IMS data channel environments
- Commonly available on digital streaming platforms to maintain user engagement
The document identifies two primary use case categories:
1. Session Termination Scenarios:
- Abnormal or normal session termination (network-initiated or user-initiated)
- Enables application session continuation beyond single IMS session duration
- Enhances user engagement with the platform
2. System Notification Scenarios:
- User receives system notifications (e.g., security alerts)
- Allows user to suspend application to address notifications
- Enables resumption at appropriate point after handling notification
Automatic resumption must support:
- Peer-to-peer sessions: Direct communication between caller UE#1 and callee UE#2
- Call transfer cases: Scenarios where caller UE#1 is transferred to UE#3
Key Technical Element:
- Requires a persistent identifier serving as unique key for database storage of application context/state
- This identifier must be:
- Exchanged between peers
- Configurable with defined lifetime
Proposed Analysis:
The document proposes to analyze the technical feasibility of implementing this persistent identifier mechanism within the IMS data channel framework.
The contribution establishes the foundation for technical feasibility analysis of automatic resumption support, focusing on the identifier mechanism required to maintain and restore application state across session boundaries.