Telecommunication Service Continuity via Master Node Data Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing backup systems in telecommunication networks are inefficient in resource utilization and fail to guarantee service continuity during network failures, particularly in geographically distributed networks, where detection of access point failures is challenging, and data coherence is not maintained during network outages.

Innovation Solution

A method and system where a client sends data packets to a master service server, with a master node maintaining a local copy and verifying its operational state; if the master server fails, the data packets are seamlessly redirected to a slave service server, ensuring continuous service delivery with reduced recovery time and efficient resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a primary server and backup server are connected via telecommunication network for distributed backup, then service availability is increased, but network resources are consumed inefficiently and recovery time is extended

Engineering Contradiction:
Improveservice availabilityVSAvoidrecovery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring the backup server with all necessary service data, applications, and system state before failure occurs. The backup server maintains a ready-to-assume state with synchronized data, so when the primary server fails, the takeover is immediate without requiring data transfer or system initialization during recovery.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent extracts the backup server from a passive data-copying role and makes it an active, fully-functional service provider. The backup server is equipped with complete service capabilities and can independently handle client requests, rather than merely storing data to be restored later.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If multiple geographically distributed backup servers are used to ensure service continuity, then service availability is improved, but network resource consumption increases

Engineering Contradiction:
Improveservice continuityVSAvoidnetwork resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by implementing backup capabilities at a single strategically located server rather than distributing multiple backup servers across geographically dispersed locations. This single backup server maintains sufficient redundancy to ensure service continuity without the overhead of managing multiple distributed backup nodes.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent merges the backup functionality into a single consolidated backup server that handles all backup operations for the primary server. This combines multiple backup functions into one resource, reducing network resource consumption compared to maintaining separate backup servers at each location.

Inventive Principle:
Principle #5Merging (Combining)

3Stability of the object's composition

If backup servers continuously synchronize with master server via TCP/IP network, then data coherence is maintained, but network bandwidth is consumed

Engineering Contradiction:
Improvedata coherenceVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Stability of the object's compositionVSLoss of energy

Solution Approach 1:

The patent applies periodic action by synchronizing data between the primary and backup servers at scheduled intervals rather than continuously. The backup server receives updated data copies at regular periods, which maintains data coherence while significantly reducing network bandwidth consumption compared to continuous real-time synchronization.

Inventive Principle:
Principle #19Periodic action

4Reliability

If a backup algorithm redirects traffic to backup server upon primary server failure, then service continuity is provided, but detection of access point failures is challenging

Engineering Contradiction:
Improveservice continuityVSAvoidaccess point failure detection
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements feedback mechanisms where the backup server continuously monitors the operational status of the primary server through health checks and status signals. When the primary server becomes unresponsive or fails, the backup server detects this through the absence of expected feedback signals and automatically activates to maintain service continuity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP2939401B1Method for guaranteeing service continuity in a telecommunication network and system thereof
Publication Date: 2017.05.24 TELECOM ITALIA SPA
  • EP2939401B1 patent drawingFigure 1
  • EP2939401B1 patent drawingFigure 2
  • EP2939401B1 patent drawingFigure 3

AI summary

It is disclosed a method for guaranteeing the service continuity of a telecommunication network (110), wherein a first node (104) of the network (110) receives a service request sent by a client computer (102) to a first service server (100) providing said service, said first service server (100) accessing the network (110) by means of said first node (104), the method being characterized by comprising the steps of: - storing a local copy of data packets related to said received service request; - starting a server state verification procedure in order to check the operative state of said first service server (100); and - transmitting said data packets to a second service server (101) if said server state verification procedure detects a failure in the operative state of said first service server (100), said second service server (101) being configured to act as a backup server for said service to be provided.