File Repair Server Selection via Load Status Feedback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In Multimedia Broadcast and Multicast Services (MBMS), file repair procedures are inefficient due to the random selection of File Repair Servers, leading to increased delays and additional signaling when the initial server is overloaded, causing errors and requiring multiple requests for file repair.

Innovation Solution

A system and method where a User Equipment (UE) receives status update messages from a Broadcast Multicast Service Centre (BM-SC) regarding the load and capacity of available File Repair Servers, allowing it to select a server with lower load and higher capacity for file repair, reducing the likelihood of server overload and error messages, and distributing load more homogeneously across servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the UE randomly selects a File Repair Server, then the selection process is simple, but the delay increases and the success rate decreases when the server is overloaded

Engineering Contradiction:
Improvesimplicity of server selectionVSAvoidsuccess rate of file repair request
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The BM-SC performs preliminary actions by obtaining status information about File Repair Servers before the UE needs to select one. The BM-SC proactively sends status update messages containing server load and capacity information to the UE, enabling the UE to make informed selections rather than random choices, thus improving success rate while maintaining selection simplicity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A feedback mechanism is established where the BM-SC continuously monitors File Repair Server status and provides this information back to the UE through status update messages. This feedback loop allows the UE to adapt its server selection based on current server conditions, improving the reliability of file repair requests without complicating the selection process

Inventive Principle:
Principle #23Feedback

2Speed

If the UE randomly selects a File Repair Server, then the selection process is quick, but additional signaling is introduced when the server cannot engage in file repair

Engineering Contradiction:
Improvespeed of server selectionVSAvoidsignaling load over the air
Core Design Contradiction:
SpeedVSLoss of information

Solution Approach 1:

The BM-SC performs preliminary actions by obtaining and caching status information about File Repair Servers before the UE needs to select one. By proactively sending status update messages with server availability information, the BM-SC enables the UE to make informed selections in a single attempt, avoiding multiple retry signaling exchanges and reducing overall signaling load

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The feedback mechanism provides the UE with advance knowledge of server status, enabling the UE to select an appropriate server on the first attempt. This prevents the need for multiple request-rejection-retry signaling cycles, thereby reducing signaling load over the air while maintaining fast selection speed

Inventive Principle:
Principle #23Feedback

3Speed

If the UE requests file repair from an overloaded File Repair Server, then the request is sent quickly, but the probability of rejection increases

Engineering Contradiction:
Improvespeed of sending file repair requestVSAvoidprobability of request rejection
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The BM-SC provides feedback to the UE about the load and capacity status of File Repair Servers through status update messages. This feedback enables the UE to identify and select servers with available capacity, ensuring that file repair requests are sent to servers that can actually handle them, thereby reducing rejection probability while maintaining request speed

Inventive Principle:
Principle #23Feedback

4Productivity

If the load is not distributed homogeneously across File Repair Servers, then some servers remain underutilized, but the overall system efficiency decreases due to overload on other servers

Engineering Contradiction:
Improvesystem efficiencyVSAvoidload distribution complexity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The BM-SC implements a feedback mechanism that continuously monitors the load status of all File Repair Servers and provides this information to the UE. This enables UEs to select servers with lower current load, automatically distributing requests more homogeneously across the system. The feedback-driven selection improves system efficiency and productivity without adding operational complexity for the UE

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system changes the parameter used for server selection from random selection to selection based on server status parameters (load and capacity). By using these dynamic parameters, the system automatically achieves more homogeneous load distribution across servers, improving overall productivity while keeping the selection mechanism simple for the UE

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP2907264B1A UE, a BM-SC, a status management server, a load balancing server and a file repair server and respective methods therein are provided for file repair procedure
Publication Date: 2021.08.11 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP2907264B1 patent drawingFigure 1~2
  • EP2907264B1 patent drawingFigure 3~4
  • EP2907264B1 patent drawingFigure 5

AI summary

A UE, a File Repair Server, a Load Balancing Server, a Status Management Server, a BM-SC and respective methods therein are provided for performing a file repair procedure and at the same time balancing the load between different File Repair Servers. The UE receives (110), from a Broadcast Multicast Service Centre, BM-SC, a status update message comprising information on load and/or capacity of File Repair Servers available for the UE. The UE selects(120) a File Repair Server to request a file repair procedure from based on the status update message; and sends (130) a file repair request to the selected File Repair Server.