MEC V2X API for Multi-Operator Service Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multi-access edge computing (MEC) and cellular vehicle-to-everything (C-V2X) communication systems face challenges in providing seamless service continuity across different network providers and ensuring end-to-end performance, particularly in scenarios involving multiple public land mobile networks (PLMNs), leading to disruptions and latency issues.
Innovation Solution
The integration of MEC with IoT and Fog networking, utilizing a MEC V2X application programming interface (API) to manage V2X communication authorizations and configuration parameters, enabling vehicles from different operators to communicate effectively by negotiating a common set of V2X configuration parameters across multiple PLMNs, even in areas with limited or no cellular coverage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MEC is integrated with multiple PLMNs to provide seamless service continuity, then service reliability is improved, but system complexity increases
Solution Approach 1:
The patent introduces a V2X application function and MEC platform as intermediary components that mediate between multiple PLMNs and V2X services. These intermediaries manage authorization, configuration parameters, and service coordination, thereby improving service continuity across networks while containing system complexity through centralized management functions.
Solution Approach 2:
The MEC platform is designed to perform multiple functions including V2X service authorization, configuration management, coordination across PLMNs, and support for both in-coverage and out-of-coverage scenarios. This multi-functionality allows a single system to handle diverse requirements, improving reliability without proportionally increasing complexity.
2Reliability
If V2X configuration parameters are negotiated across multiple PLMNs, then communication reliability is improved, but latency increases
Solution Approach 1:
The patent implements preliminary authorization and configuration provision by the V2X application function before actual V2X communication occurs. Configuration parameters are pre-negotiated and stored, allowing UEs to quickly establish communications without real-time parameter negotiation, thus reducing latency while maintaining reliability.
Solution Approach 2:
The system creates and distributes copies of V2X configuration parameters to multiple PLMNs and UEs in advance. These parameter copies enable local execution of V2X communications without repeated requests to the home PLMN, reducing communication latency while ensuring consistent configuration across networks.
3Adaptability or versatility
If MEC hosts are deployed in multiple PLMNs for out-of-coverage support, then service availability is improved, but network complexity increases
Solution Approach 1:
The patent segments the V2X service support functionality by deploying separate MEC hosts in different PLMNs, each capable of independently providing out-of-coverage support. This segmentation allows service availability to be maintained across multiple networks while managing complexity through modular, distributed deployment rather than a single complex centralized system.
Solution Approach 2:
The V2X application function acts as an intermediary that coordinates between multiple MEC hosts deployed in different PLMNs. It manages authorization and configuration distribution to these MEC hosts, enabling them to work together seamlessly without requiring complex direct interconnections, thus improving service availability while controlling network complexity.
Data Source
AI summary
A computing device includes communications circuitry to communicate with a first access network and processing circuitry. The processing circuitry is to perform operations to transmit an authorization request for a vehicle-to-everything (V2X) communication to a V2X application function within a service coordinating entity, the request transmitted from the device via the first access network V2X configuration parameters are received from the service coordinating entity, via the first access network. The V2X configuration parameters are received in response to the authorization request and based on V2X subscription information received by the V2X application function via a V2X application programming interface (API) within the service coordinating entity. A V2X communication link for the V2X communication is established with a second device based on the V2X configuration parameters, the second device associated with a second access network.