Master Server Scheduling for Shared MBMS Bearers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication systems lack a technical solution for controlling the scheduling process of Broadcast/Multicast Service Centers (BM-SC) in Mission Critical Data (MCData) transmission, which results in inefficient resource allocation and prioritization across multiple public safety organizations sharing the same MBMS bearer.

Innovation Solution

Implementing a shared MBMS bearer system where a master server configures and controls sharing policies, authorizes servers, and manages queuing or interleaving non-real time data transmission policies to prioritize and schedule file transmissions across multiple servers using the xMB interface, allowing for efficient resource utilization and priority handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple public safety organizations share the same MBMS bearer, then resource utilization is improved, but scheduling control and priority handling become problematic

Engineering Contradiction:
Improveresource utilizationVSAvoidscheduling control
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a master server as an intermediary entity that mediates between multiple content providers and the BM-SC. The master server receives scheduling requests from content providers, determines priority based on predefined policies, and controls the scheduling process. This intermediary structure enables multiple organizations to share the same MBMS bearer while maintaining centralized scheduling control and priority handling capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If centralized scheduling control is implemented, then priority handling is improved, but system complexity increases

Engineering Contradiction:
Improvepriority handlingVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The master server implements self-service mechanisms by automatically determining priority based on predefined scheduling policies and service types. When receiving data from multiple content providers, the master server autonomously evaluates the data against stored policies (such as MCPTT high priority, MCData normal priority) and schedules transmissions without requiring complex real-time negotiations or manual intervention, thereby maintaining reliable priority handling while limiting system complexity growth.

Inventive Principle:
Principle #25Self-service

3Loss of energy

If MBMS bearers are shared across organizations, then resource efficiency is improved, but transmission priority control deteriorates

Engineering Contradiction:
Improveresource efficiencyVSAvoidtransmission priority control
Core Design Contradiction:
Loss of energyVSManufacturing precision

Solution Approach 1:

The system implements preliminary action by pre-configuring scheduling policies and priority levels for different service types before actual data transmission occurs. The master server stores predefined policies (e.g., MCPTT communications receive high priority, MCData receives normal priority) and automatically applies these pre-established rules when scheduling data from multiple content providers. This approach enables efficient resource sharing while maintaining precise transmission priority control through预先 established guidelines.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3909268B1Scheduling and priority handling for data transmission
Publication Date: 2024.03.06 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3909268B1 patent drawingFigure 1~2
  • EP3909268B1 patent drawingFigure 3
  • EP3909268B1 patent drawingFigure 4A~5A

AI summary

A method for using Multimedia Broadcast Multicast Services ( "MBMS" ) bearers in a network is provided, comprising: receiving properties and a sharing policy for an MBMS bearer and an instruction on which servers are authorized to share the MBMS bearer from a master server; and associating a session from an authorized server to the shared MBMS bearer according to the sharing policy when requested by the authorized server.