Maritime M2M Priority Management for Satellite Bandwidth

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In maritime M2M communication systems, satellite bandwidth is inefficiently used due to congestion and legal requirements that change with location, leading to delays in critical data transmission and 'registration storms' when devices try to reconnect after an outage, which can result in critical alarms being delayed or lost.

Innovation Solution

A system with a network node that detects communication loss or congestion and selects recovery modes to prioritize critical data transmission, allowing only alarm information and filtered or prioritized data to be sent during congestion, and gradually increasing allowed traffic as conditions improve, using existing radio interface standards and broadcast channels to manage M2M device behavior.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If all M2M devices transmit status information simultaneously when cellular service becomes available, then the backlog of status information can be cleared, but the network becomes overloaded and satellite bandwidth is wasted

Engineering Contradiction:
Improvedata transmission throughputVSAvoidsatellite bandwidth waste
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system implements periodic transmission slots where devices are scheduled to transmit at different time intervals. The network controller assigns transmission time slots to different devices, transforming the simultaneous transmission problem into a periodic, structured sequence that clears backlogs efficiently without overloading the network at any single moment.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system dynamically adjusts transmission parameters based on network conditions. When the network is congested, transmission rates and timing are adapted in real-time. The network controller monitors load conditions and dynamically reassigns transmission slots, allowing the system to optimize between clearing backlogs quickly and preventing network overload.

Inventive Principle:
Principle #15Dynamics

2Loss of time

If M2M devices send all accumulated status information at once, then the backlog is cleared quickly, but critical alarms may be delayed by voluminous low priority data

Engineering Contradiction:
Improvebacklog clearance timeVSAvoidcritical alarm delivery
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system applies different transmission priorities to different types of data. Critical alarm messages are assigned high priority with dedicated transmission opportunities, while routine status reports are assigned lower priority. This local differentiation ensures that when devices transmit, critical information reaches the network immediately while non-critical data fills in during lower-priority slots.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The transmission process is segmented into different priority levels and time slots. Rather than treating all data uniformly, the system divides data into critical alarms, important status updates, and routine reports. Each segment is transmitted according to its priority level, ensuring critical alarms are not buried in voluminous low-priority traffic.

Inventive Principle:
Principle #1Segmentation

3Productivity

If the onboard base station operates continuously to maintain cellular service, then M2M devices can transmit data without interruption, but legal requirements in territorial waters cannot be complied with

Engineering Contradiction:
Improvedata transmission continuityVSAvoidlegal compliance
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by storing data locally in devices' memory before transmission opportunities arise. When the base station must shut down in territorial waters, devices continue to collect and store status information locally. Upon returning to international waters, the pre-stored data is transmitted without interruption, maintaining productivity while complying with legal requirements.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary storage layer between the M2M devices and the satellite network. Data is first stored in local memory on devices or the base station, then transmitted to the satellite network when conditions permit. This intermediary buffer decouples the continuous data generation from the intermittent transmission opportunities, allowing legal compliance without sacrificing data collection.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If terrestrial base stations are used when at port, then M2M devices can transmit status information without backlog, but network agreements and coverage availability limit access

Engineering Contradiction:
Improvedata transmission availabilityVSAvoidnetwork access flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system implements a universal transmission architecture that can operate with multiple types of base stations. Devices are configured to work with both terrestrial base stations when available and onboard base stations when required. This multi-functionality allows the system to adapt to different network environments - using terrestrial infrastructure at ports when permitted, and switching to satellite-based onboard base stations in international waters or when terrestrial access is unavailable.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP3063957B1Maritime machine-to-machine (M2M) application priority management
Publication Date: 2019.03.06 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3063957B1 patent drawing
  • EP3063957B1 patent drawing
  • EP3063957B1 patent drawing

AI summary

A network node communicates with a radio access node that communicates application traffic on behalf of machine-to-machme (M2M) devices via a satellite link. The network node comprises a database and a control unit;. The database stores a plurality of recovery modes. Each recovery mode indicates one or more types of application traffic that M2M devices arc or are not allowed to transmit when operating according to that recovery mode. The control unit detects a loss of communication across, or congestion on, the satellite link, selects one of the recovery modes, and requests the radio access node to broadcast the selected recovery mode over a 3GPP- based broadcast channel in order to instruct the M2M devices to transmit only application traffic allowed in accordance with the selected recovery mode.