MBMS Key Update Service Continuity via Preliminary Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing MBMS key update procedure, specifically the solicited pull procedure, is incomplete and does not function as defined, leading to interruptions in user services like watching TV, as the Broadcast-Multicast Service Center (BM-SC) lacks information on refreshing the MBMS User Key (MUK) when it expires.
Innovation Solution
The proposed solution involves monitoring the validity of limited-validity key information, acquiring and generating new limited-validity transaction identification information, and transmitting it to network elements to ensure seamless key updates without service disruptions, by using existing protocols with new parameters to indicate service continuity and synchronize key lifetimes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the BM-SC uses the existing solicited pull procedure to update the MUK, then the key update process is initiated, but the procedure is incomplete and causes service interruptions because the BM-SC lacks information on refreshing the MUK when it expires
Solution Approach 1:
The UE performs a registration procedure with the BM-SC before the MUK actually expires, allowing the BM-SC to proactively refresh the MUK and maintain service continuity. This preliminary action prevents service interruptions by updating keys in advance rather than waiting for expiration.
Solution Approach 2:
The registration procedure establishes a feedback mechanism where the BM-SC receives information from the UE about key status and can respond by providing updated MUK information. This feedback loop ensures the BM-SC maintains current key refresh information without service interruptions.
2Reliability
If the UE performs a full de-registration and re-registration procedure to update the MUK, then the new MUK key is obtained, but the service is interrupted and the procedure is complex
Solution Approach 1:
The key update procedure is segmented into a lightweight registration step rather than requiring a complete de-registration and re-registration sequence. This segmentation allows the UE to maintain service connectivity while updating keys, avoiding full service interruption.
Solution Approach 2:
Instead of performing the complete de-registration and re-registration procedure, the UE performs only a partial registration action with the BM-SC. This partial action is sufficient to trigger MUK refresh while maintaining service continuity, avoiding the excessive complexity and interruption of a full procedure.
3Adaptability or versatility
If the BM-SC operates in pull mode to obtain key information, then the existing Zn reference point architecture is maintained, but the BM-SC cannot proactively obtain MUK refresh information from the UE
Solution Approach 1:
The information flow is inverted: instead of the BM-SC passively pulling key information from the UE, the UE actively pushes registration information to the BM-SC. This inversion allows the BM-SC to proactively receive MUK refresh information while maintaining the existing pull-mode architecture.
Data Source
AI summary
It is disclosed a method comprising monitoring validity of limited-validity key information, acquiring, from a network entity upon invalidity of the limited-validity key information, limited-validity transaction identification information based on unlimited-validity identification information identifying a terminal, generating new limited-validity key information based on the acquired limited-validity transaction identification information, and transmitting the acquired limited-validity transaction identification information to a network element.