[Editor's Note] Hyundai Mobis implemented NG-eCall and Hybrid eCall features into its products to address regulatory and technological changes in the European market. Initially, verification challenges arose due to equipment shortages, insufficient knowledge of LTE/5G and SIP signaling, and network simulation limitations. However, these challenges were overcome with the support of Anritsu's MX703330E and MD8475B equipment. Specifically, the company established a Hybrid eCall verification environment, leveraging automated conformance testing and clear log analysis capabilities to quickly identify error causes and enhance collaboration with the development team. This significantly improved the reliability and speed of the R&D process, and through its collaboration with Anritsu, Hyundai Mobis is strengthening its eCall verification capabilities and ensuring future mobility safety. Accordingly, our magazine had an opportunity to interview Jinseong Lee, a researcher at Hyundai Mobis' Electronic Control Test Cell, to learn about the collaboration with Anritsu during the development of NG-eCall and Hybrid eCall.



■ Please introduce Hyundai Mobis.

As a global automotive parts supplier, we strive to become a leader in the era of smart mobility, focusing on autonomous driving, connectivity, and electrification.

Based on three modular automotive components - chassis, cockpit, and front end - we are making driving safer and more convenient, and we also provide service parts that are best suited to the purpose.

Our vision is to provide differentiated mobility solutions that combine software and hardware in the upcoming mobility industry.

To realize this vision, we have expanded our business areas to include smart mobility, UAM (urban air mobility), and robotics, leveraging our R&D capabilities and production capabilities.

■ I'm curious about the main areas of responsibility.

We are responsible for comprehensive evaluation of the eCall functionality of our products (DCU, Data Connectivity Unit).

Key tasks include performing conformity testing according to EU regulations and ETSI standards, verifying functionality under various network conditions, and verifying interoperability with public service announcement centres (PSAPs).

Also, test scenario design, result error analysis and I am involved in reporting, writing technical assessments for certification preparation, and conducting simulations and troubleshooting using Anritsu equipment.

We are working with our development team to ensure product quality, and are currently participating in the evaluation of NG-eCall (Hybrid eCall), a next-generation IP-based feature.

■ What products of yours are equipped with NG-eCall and Hybrid eCall?

Currently, our products are equipped with the Hybrid eCall feature.

The reason for adopting Hybrid eCall is to simultaneously secure stability and compatibility during the transition period between the existing Circuit-Switched (CS)-based eCall and IP-based NG-eCall.

In the European market, the transition to NG-eCall is underway, but some regions still have CS-based infrastructure in operation, so Hybrid eCall is the optimal technology to provide eCall services in both environments.

This aims to ensure regulatory compliance as well as service continuity under various network conditions.

■ I would like to hear about the background behind applying NG-eCall to the product.

The background behind introducing NG-eCall into our products is to respond to technological and regulatory changes in the European market.

The existing eCall was designed based on 2G/3G circuit-switched (CS) networks, but these networks are expected to be phased out.

Accordingly, NG-eCall, which has been converted to LTE and 5G-based IMS (IP Multimedia Subsystem) method, will be mandatory for all new vehicles from 2026 according to EU regulations.

NG-eCall is faster than the existing methodSimultaneous transmission of voice calls and MSDs significantly improves emergency response efficiency, and this change is essential to ensure service continuity and future safety features, which is why we have implemented the NG eCall feature in our products.

■ Before introducing Anritsu's 'eCall Tester MX703330E', I am curious about what technical difficulties there were in applying NG-eCall to products.

There were three major difficulties in the early stages of NG-eCall function evaluation and environment construction.

1) Absence of equipment for evaluating Hybrid eCall
Although we had EN17240-based NG-eCall function evaluation equipment, as explained above, our product uses Hybrid eCall, making it difficult to establish an evaluation environment that could fully control the relevant functions.

When using existing equipment, there were many limitations to the evaluation scope, and for example, when LTE-based NG-eCall failed, the system would transition to a 2G/3G network and perform eCall, and there were situations where it was necessary to connect to public institutions such as actual domestic police stations and seek their understanding.

2) Lack of background knowledge about LTE/5G mobile communications and SIP signaling.
Personally, because I lacked experience and knowledge of LTE mobile communications and SIP signaling, I had difficulty determining whether an error occurred during evaluation due to a problem with the equipment settings or with the product itself under development.

3) Evaluation environment constraints for various network situations
Among the functions required by laws and regulations and our products, we repeatedly and stably simulate the operation of handovers or call disconnection due to signal strength weakening in a laboratory environment without the equipment.It was difficult to establish this. This also presented a major challenge in establishing an evaluation environment.

■ I am curious about how you overcame the technical difficulties you faced in implementing NG-eCall.

In the process of resolving technical difficulties to verify the NG-eCall function, the following approach was taken.

1) Absence of equipment for evaluating Hybrid eCall
To verify Hybrid eCall, we confirmed the availability of MD8475B and MX703330E equipment and beta version firmware from Anritsu. We proactively introduced these equipment and conducted a review before the official release. During the development period, we evaluated Hybrid eCall-related software changes and performed conformance testing, contributing to software bug fixes.

2) Lack of background knowledge about LTE/5G mobile communications and SIP signaling.
Beyond personal study, I utilized actual equipment to fill in any gaps. For example, I acquired background knowledge by analyzing SIP protocol behavior using the Sequence Log feature provided by the equipment. Additionally, I organized the settings by referring to the manual, and acquired the basic mobile communications knowledge required for eCall evaluation by repeatedly conducting network simulations through on-site support and phone calls from Anritsu personnel.

3) Evaluation environment constraints for various network situations
Network simulation was possible through the handover function and cell settings (signal strength adjustment/ECL/Service In&Out, etc.) provided by D8475B and MX703330E, and the evaluation situation was simulated to enable timely response to the evaluation schedule and SW verification.


■ I would like to hear what factors were behind your choice of Anritsu's 'MX703330E' test solution for NG-eCall verification.

Key decision-making factors include:

1) When evaluating Hybrid eCall, evaluation is possible using only standalone equipment.
Although additional equipment was required for evaluating Hybrid eCall when making a new investment, Anritsu's equipment had the advantage of being able to be configured standalone.

2) Improved SW change confirmation and debugging efficiency by using the same equipment as the development department.
By sharing the same test environment, problem reproduction and cause analysis became easier, and guidance on equipment settings was received for SW changes and collaboration with the development team was possible.I was able to improve the up speed.

■ I am curious about what other Anritsu test equipment is currently installed in the lab, aside from the 'MX703330E'.

There is no additional Anritsu equipment other than the MX703330E and MD8475B. However, the current option configuration is as follows.


■ I am curious about the difficulties encountered in configuring the existing system (e.g., shielded test chamber) in the laboratory and the 'MX703330E' test equipment.

Anritsu provided great help in installing the program.

There were no major issues with the installation process itself, but what was unexpected was that the USIM of the equipment provided did not support Test Call.

There was a Test Call during the suitability test items and product function evaluation, and Anritsu helped resolve the issue so that the USIM could be Test Call capable.

There were no other difficulties such as compatibility with existing DCU evaluations.

■ I would like to know what improvements have been made in the research and development process since the installation of Anritsu's 'MX703330E' test equipment, and if possible, I would also like to know figures such as the improvement rate and work time.

Since there are no separate quantitative indicators, I will only speak of qualitative indicators.

1) Seamless compatibility between the product (DCU) and the evaluation test environment
There was no difficulty in setting up the evaluation environment as compatibility between the product and the hardware interface was good. Additionally, by purchasing the Hybrid eCall Option, we were able to conduct stable and repetitive tests in the lab, and by configuring a semi-normal environment in addition to the normal environment, we were able to expand the scope of evaluation and secure flexibility.

2) Rapid response to suitability test and SW evaluation results
Automating conformance testing using SSM capabilities enabled automated network simulations, quickly providing evaluation results and reliable supporting evidence.

3) Provide clear logs for error analysis with the development team.
When a bug occurred, the Sequence and Message logs allowed immediate identification of whether the issue was a terminal error or a device configuration issue. This allowed the design team to report the terminal error, significantly reducing the time required for root cause analysis and resolution.

■ What do you think are the strengths of Anritsu products (not limited to the MX703330E)?

1) High reliability
The MD8475B has been in use for a long time since its platform launch, and its stability has been proven. During the evaluation process, the stability of the device allowed us to focus more on terminal error analysis.

2) Excellent technical support
We provide professional technical support during installation and troubleshooting, and we believe that quick responses to inquiries related to equipment setup and use are our greatest strengths. In particular, when we requested a tool to create an objective report on the test results during the aforementioned Test USIM support and suitability equipment review, we received positive feedback and were able to actually receive a report creation tool.

■ What areas do you think Anritsu needs to improve in terms of future product development or services (not limited to the MX703330E)?

1) Formal offline training is needed on equipment setup and background knowledge.
Currently, learning is done through in-person support, phone calls, emails, and manuals, but sometimes, the understanding is limited to fragments. Providing hands-on, offline training and quick guides to facilitate a comprehensive understanding would be invaluable. This type of training would shorten the initial setup time for new companies adopting this solution, enhance their understanding of the equipment, and contribute to efficient use.

2) Need to provide network simulation for abnormal situations such as call drops
Our product incorporates logic for abnormal (call drop) scenarios depending on network conditions, and we are currently evaluating this. Currently, we are conducting indirect evaluations by weakening cell signal strength to induce call drops. However, there are cases where the PSAP fails to recognize the call drop and maintains the call. If the MX703330E had the capability to directly simulate these abnormal situations, the accuracy and efficiency of the evaluation would be greatly improved.

■ Were there any experiences or cases that were particularly impressive while carrying out this collaboration?

1) Test USIM Quick Support
When setting up the initial evaluation environment, a problem arose because the provided USIM did not support Test Call. This could have delayed root cause analysis, whether it was a terminal software error or an equipment issue. However, Anritsu quickly identified the need for a separate Test Call-capable USIM and provided support. Thanks to this, the evaluation proceeded smoothly, demonstrating the speed and expertise of the collaboration.

2) Creating a tool to generate reports including equipment logs
The initial conformance test results report was unsatisfactory due to a lack of objective evidence to the certification body or relevant departments. We requested improvements to the report, and Anritsu addressed our needs. Specifically, they provided an updated report generation tool with the Hybrid eCall option firmware delivery, enabling us to present the evaluation results clearly and reliably. I believe this response has enhanced the value of our collaboration.

■ I am curious to know in what areas Hyundai Mobis expects to further cooperate with Anritsu in the future.

1) Plan to expand evaluation automation
Currently, we are prioritizing the stabilization of manual testing, and later plan to expand the testing scope by focusing on areas where automated evaluation is possible by utilizing the SSM function. However, due to structural limitations that prevent simultaneous control of the MD8475B and MX703330E, we are carefully reviewing the level and strategy of automation. These considerations will be a critical challenge in establishing an efficient testing process in the future.

2) Exploring the potential use of additional evaluation features
In addition to the eCall function, I understand that the device offers various evaluation features, including SMS transmission and throughput measurement. While we haven't yet confirmed the specific features, we are actively reviewing these features to maximize device usability. Through this, we hope to broaden the evaluation scope and secure opportunities to analyze product performance from various perspectives.