JpU Frequently Asked Questions.
HyperCore is not merely a connectivity management platform. It is a fully functional mobile network core with built-in connectivity management capabilities. This means that JpU HyperCore helps you to cut the costly expenses associated with traditional mobile core and connectivity management platforms. The JpU HyperCore platform enables service providers to maintain ARPU and offer competitive pricing.
All vEPC products focus on the delivery of 4G and 5G data services. Only a few very expensive solutions currently offer voice and text messages. None of the available solutions on the market offer backward compatibility to 2G and 3G networks. The JpU HyperCore platform is purpose-built for the IoT and M2M ecosystem and supports 2G/3G/4G networks with upcoming support for a 5G software mobile core. The JpU HyperCore platform is cost sensitive to the needs of IoT and utilizes only the minimum required network elements needed to provide dedicated cores, without a full EPC. In contrast to a typical EPC, the JpU HyperCore supports data, voice and text services over 2G/3G/4G. Many IoT devices are less costly when connected to a 2G or 3G network and they do not need broadband connectivity. In these cases, the JpU platform is an ideal solution.
The JpU HyperCore is run by the enterprise that operates the devices. This enables the enterprise to control the Layer 3 IP configuration of the connected devices. All capabilities are performed via a self-service web application very similar to the way an organization intranet works. Customers can group devices in private LANs and define inbound and outbound firewall rules on demand. The ability to control the IP network on top of the public cellular network simplifies daily operation by managing security at the network level instead of the device level.
To reduce costs, JpU HyperCore includes a basic built-in billing system designed for the handling of relatively simple IoT plans. All JpU billing capabilities are fully accessible via APIs and can be integrated with any third party CRM platform. In general, when an external billing system is used, the JpU HyperCore can be deployed and integrated using a common Gy interface.
When a Local Breakout is defined, mobile subscribers can sign up to an alternative roaming provider which is different from the Home Public Land Mobile Network (HPLMN). This enables inbound roamers to receive data services directly from the visited mobile network instead of tunneling back to the HPLMN. This method results in lower latency experienced by the roaming device and has a lower GRX bandwidth requirement between the home network and visited network.
A major benefit of Local Breakouts is that mobile subscribers can sign up to an alternative roaming provider. By targeting inbound roamers that choose to turn off mobile data instead of paying standard roaming charging rates, the solution allows the MNO to generate revenue from a previously non-monetized source.
Because there are an infinite number of IoT use cases it is not possible to predict the network requirements for a given use case. This makes the engineering and the planning of a mobile core network an impossible task. A dedicated core running in parallel to the legacy core enables the service provider to rapidly launch IOT services which have their own specific network requirements without disrupting the legacy mobile core. This eases the engineering effort of the network and reduces the costs and risks of making changes in the legacy core.
In some situations, several use cases share similar profiles. In these situations network operators can “slice” the same dedicated core into multiple services where each network slice is managed independently, similar to the way a multi-tenant system works. Slicing reduces capital investment and operational costs significantly. The JpU HyperCore can be deployed as a dedicated core with or without network slices. Service operators manage a single core and each enterprise customer can manage its own slice independantly. JpU HyperCore supports both slicing models for 3G, 4G and 5G networks.
JpU HyperCore supports all the new standards – LTE-M, LTE Cat-0, 1, M1, NB1, NB-LTE. This enables cellular operators to provide a low-power, low throughput, wireless technology required by IoT solutions. One key advantage of JpU HyperCore is that cellular operators can implement the new standards with a simple upgrade of the network software, without the need to deploy new antennas. This leads to a significant cost reduction.
No, the JpU HyperCore platform does not currently handle mobile device management. However, the JpU platform does manage trusted identities, but at the SIM card/eSIM level -not at the device level.
JpU HyperCore is designed to address the transport, connectivity and security levels. At this stage we expect MDM requirements will be fulfilled on top of the platform by a third party system. The JpU product team intends to evaluate the possibility of including some basic MDM capabilities as part of the HyperCore platform to address certain costs issues.
When integrated with IoT applications, JpU HyperCore can report any event in the network as a webhook and transfer the data to third party applications. This capability combined with a wide range of JpU APIs enables customers to create smart IoT applications and automate most of operational workflows. In addition, the JpU platform stores all events in a big data engine which enables users to browse data, monitor KPIs, and generate reports from the raw events. At this stage, the platform does NOT perform any deep packet inspection on the content and can apply security rules based on headers only.
The security features and control capabilities of the JpU Hypercore platform can be deployed to serve as a generic enterprise mobility solution. We do get some demand from organizations such as Banks & Insurance companies who want to gain control over their mobile devices at the transport level and optimize mobility costs.