MEC Application Discovery via OMA DM Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Multi-Access Edge Computing (MEC) systems lack a method for users to discover MEC applications over Wi-Fi access networks without requiring the download of a service provider application, leading to friction and a non-seamless user experience due to the need for explicit client applications and authorization credentials.
Innovation Solution
A system utilizing Hotspot 2.0 technology to dynamically discover MEC applications by authenticating user devices through an authentication server and communication management platform, generating authorization tokens, and accessing MEC applications via existing interfaces, eliminating the need for explicit client applications by using captive portals or DNS-based operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a service provider application is downloaded on the mobile device to access MEC applications, then the user can access MEC applications, but the user experience becomes non-seamless due to friction in downloading and manually opening the application
Solution Approach 1:
The patent extracts the MEC application discovery and access functionality from the client device by implementing it on the network side through the OMA DM server. The server pushes application information to the mobile device, eliminating the need for users to download and manually operate a service provider application, thus resolving the contradiction between ease of operation and device complexity
Solution Approach 2:
The OMA DM server acts as an intermediary between the MEC system and the mobile device. It receives application information from the MEC system, processes it, and pushes it to the mobile device through standard protocols. This intermediary approach allows seamless access without requiring a dedicated client application on the user device
2Reliability
If the ETSI MEC management plane service API is used to get the list of MEC user applications, then the interface can be used by clients, but the user device requires an application to access this interface and must provide authorization credentials
Solution Approach 1:
The system implements self-service by having the OMA DM server automatically push application information to mobile devices without requiring user intervention for authentication or application installation. The server handles the authorization and information delivery autonomously, resolving the contradiction between reliable authorization control and ease of operation
Solution Approach 2:
The OMA DM server performs preliminary actions by pre-processing application information and pushing it to devices before users need to access it. This includes obtaining authorization credentials and preparing application data in advance, eliminating the need for users to manually provide credentials or access complex interfaces
3Adaptability or versatility
If users are not aware of the mobile APP offered by the service provider, then they cannot access MEC applications, but requiring awareness and manual action creates friction in the user journey
Solution Approach 1:
The system implements feedback mechanisms where the OMA DM server monitors user presence in MEC-enabled premises and automatically pushes relevant application information to their devices. This feedback loop ensures users receive information about available services without needing to actively search or be aware of the application, resolving the contradiction between service accessibility and time loss
Data Source
AI summary
A system dynamic discovery of MEC applications is disclosed here. A user device dynamically selects a communication network by comparing existing network selection parameters present in the user device as part of a profile with network selection parameters that are received from a communication network infrastructure when the user device with a profile enters the MEC enabled premises. The authentication server authenticates a secure connection with the user device, and uses one or more authentication protocols associated with the profile. The CMP generates an authorization token based on the profile, and accesses the MEC applications using the authorization token on behalf of the user device via a first interface. The second interface verifies the received authorization token. The CMP grants access to the user device to access the communication network and manages the MEC applications of the service provider on behalf of the user device.