Smart Library Software Deployment on MNO Host Hardware

Solution Overview

Problem

Specialized hardware equipment for network services like 5G requires lengthy and costly software updates, and high electrical energy consumption, with operators needing efficient solutions for managing and deploying software applications.

Innovation Solution

Smart libraries are used to deploy software modules, or 'apps,' on specialized hardware equipment, allowing for the installation of specific apps without full software revisions and reducing energy consumption by running apps that provide needed network services, such as improved performance and log management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional full software revisions are deployed on specialized hardware equipment, then new problems can be addressed, but deployment time increases and costs increase

Engineering Contradiction:

Improveability to address new problemsVSAvoidsoftware deployment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The software is segmented into modular components: a core operating system and separate apps. This allows individual apps to be deployed independently without requiring full software revisions, enabling rapid deployment of specific problem-solving modules while keeping the core system stable.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system transitions from static full-software-update model to dynamic app-based updates. Apps can be dynamically added, removed, or updated on-demand based on specific needs, allowing the system to adapt quickly to new problems without rigid deployment cycles.

Inventive Principle:

Principle #15Dynamics

2Adaptability or versatility

If traditional full software revisions are deployed on specialized hardware equipment, then new problems can be addressed, but costs increase

Engineering Contradiction:

Improveability to address new problemsVSAvoidsoftware deployment cost

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The software is segmented into modular components: a core operating system and separate apps. This allows individual apps to be deployed independently without requiring full software revisions, enabling rapid deployment of specific problem-solving modules while keeping the core system stable.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Apps are designed as lightweight, disposable software modules that can be quickly created, deployed, and discarded. This eliminates the need for expensive, lengthy full-software-development cycles for each new problem, significantly reducing deployment costs.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

3Adaptability or versatility

If specialized hardware equipment runs all network services, then comprehensive service coverage is achieved, but electrical energy consumption increases

Engineering Contradiction:

Improvenetwork service coverageVSAvoidelectrical energy consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by stationary object

Solution Approach 1:

Specific functions are extracted from the hardware and implemented as software apps. This allows the hardware to maintain comprehensive service coverage capability while actually running only the necessary apps, reducing energy consumption by avoiding continuous operation of all possible functions.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system transitions from static full-software-update model to dynamic app-based updates. Apps can be dynamically added, removed, or updated on-demand based on specific needs, allowing the system to adapt quickly to new problems without rigid deployment cycles.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS11736578B2Managing a software application

Publication Date: 2023.08.22 RAKUTEN MOBILE INC

AI summary

A server of a mobile network operator (MNO) executes network control logic for unbundling vertically integrated software on specialized hardware equipment, referred to here as a host. For example, the server performs a handshake with the host, and establishes an encrypted channel. The server then negotiates with the host, and determines those interfaces that the host will expose to third party software. The server, based on a current need of the MNO for a network service, compares the negotiation results with contents of a smart library. If the smart library does not have a registered and suitable app for the network service, the server obtains metadata corresponding to the app from a software supplier. The server then, for example, tests the metadata on a mockup of the host, under the control of the server. The host eventually runs the app, providing the network service without requiring an entire software revision of the host.