DCCF-DCCF Coordination for UE Mobility Context Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP standards do not specify how to handle UE mobility, leading to anomalous behavior when a user equipment (UE) moves outside the serving area of a DCCF or MFAF, resulting in duplicate data requests and failed notifications due to unchanged notification endpoints.
Innovation Solution
Implement methods for DCCF-DCCF and MFAF coordination by transferring UE context and updating notification endpoints when a UE moves, ensuring seamless data collection and analytics delivery by determining new DCCF and MFAF instances through Network Resource Function (NRF) queries and context transfers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If notification endpoints are kept unchanged when a UE moves, then the data collection process can continue without reconfiguration, but duplicate data requests are generated and notifications fail because the old DCCF or MFAF is no longer serving the UE's current area
Solution Approach 1:
The patent applies preliminary action by having the source DCCF proactively transfer the UE context to the target DCCF before the UE completely leaves the source area or upon detecting the mobility event. This提前 transfer prevents the notification endpoint from becoming invalid, ensuring continuous reliable notification delivery while avoiding duplicate requests. The context transfer includes subscription information and notification endpoint details, so the target DCCF is immediately ready to handle notifications without waiting for failure detection.
Solution Approach 2:
The patent implements feedback mechanisms where the source DCCF receives confirmation from the target DCCF about successful context transfer. This feedback loop ensures that the notification endpoint is properly updated and prevents duplicate data requests. The feedback also allows the source DCCF to stop sending notifications to the old endpoint and redirect them to the new endpoint, maintaining reliability while coordinating with other DCCFs.
2Productivity
If DCCF context is transferred when a UE moves between serving areas, then seamless data collection is maintained, but additional signaling and coordination overhead is introduced between DCCF instances
Solution Approach 1:
The patent applies preliminary action by initiating the context transfer process as soon as a mobility event is detected or when the UE approaches the edge of the source DCCF's serving area. This ensures that the target DCCF is already prepared with all necessary UE context information before the UE actually moves to its new area, maintaining data collection continuity without interruption. The transfer includes pre-configured subscription details and notification endpoints.
Solution Approach 2:
The patent uses the NRF (Network Resource Function) as an intermediary to facilitate DCCF context transfer. The source DCCF queries the NRF to identify the target DCCF serving the UE's new area, and the NRF assists in routing the context transfer signaling. This intermediary mechanism streamlines the coordination process, reducing signaling overhead and transfer time by providing a centralized directory service for DCCF instances.
3Adaptability or versatility
If multiple DCCF instances serve overlapping areas, then coverage is improved and mobility is supported, but coordination complexity increases and duplicate data requests may occur
Solution Approach 1:
The patent employs the NRF as a mediator that maintains a registry of DCCF instances and their serving areas. When a UE moves or when coverage overlap occurs, the NRF assists in determining which DCCF should serve the UE by providing DCCF profile information and area coverage details. This intermediary coordination mechanism enables multiple DCCFs to serve overlapping areas flexibly while preventing duplicate data requests through centralized arbitration.
Solution Approach 2:
The patent implements feedback mechanisms where DCCF instances communicate with each other and with the NRF to confirm their serving status. When a UE is served by multiple DCCFs due to area overlap, the feedback loop ensures that only the appropriate DCCF (determined by current UE location and service quality) actively collects data and sends notifications. This coordination feedback prevents duplicate requests while maintaining the flexibility of overlapping coverage areas.
Data Source
AI summary
A method at a first data collection coordination functional entity for coordinating, in a first area, a data and/or analytics collection related to at least one mobile terminal, the method comprising: determining, based on an obtained mobile terminal mobility event notification, that the at least one mobile terminal is no longer in the first area and/or no longer in a second area served by a first messaging framework adaptor functional entity; based thereon, identifying at least one of a second data collection coordination functional entity coordinating a data and/or analytics collection in a third area in which the at least one mobile terminal resides if it does not reside in the first area and a second messaging framework adaptor functional entity serving a fourth area in which the at least one mobile terminal resides if it does not reside in the second area; and based thereon, initiating a transfer or a setup of at least one of a respective data collection coordination functional entity context associated with the at least one mobile terminal to or at the second data collection coordination functional entity and a respective messaging framework adaptor functional entity context associated with the at least one mobile terminal to or at the second messaging framework adaptor functional entity.