NEF Multicasting Ruleset for Mobile Originated Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 5G and previous generation telecommunications networks lack a standardized method for mobile originated data multicasting, leading to inefficient data traffic management and increased load on IoT devices, as well as the need for individual configuration of application functions to broadcast data, which is impractical and resource-intensive.

Innovation Solution

A network exposure function (NEF) is configured to receive deliver request messages and utilize a multicasting ruleset to dynamically route mobile originated data to multiple application function endpoints, enabling efficient multicasting or forking of data without requiring individual configuration of each destination, and can trigger NIDD configuration registrations as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual one-to-one PDU session mapping is used between NEF and AFs, then data delivery is straightforward and reliable, but the load on IoT devices increases significantly and multiple PDU sessions are required

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidIoT device energy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple one-to-one PDU session mappings into a single many-to-one mapping where multiple AFs share one PDU session with the NEF. This consolidation allows IoT devices to report data through a single session that is then distributed to multiple destination AFs, reducing device energy consumption while maintaining reliable delivery to all recipients.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The NEF acts as an intermediary that receives data from the IoT device through a single PDU session and then distributes it to multiple AFs. This mediator approach eliminates the need for the device to establish multiple sessions, reducing its energy burden while ensuring reliable delivery through the NEF's coordinated distribution mechanism.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If AF endpoints are configured to fork received MO data to other destinations, then data can reach multiple endpoints, but every AF must be individually configured which is impractical and resource-intensive

Engineering Contradiction:
Improvedata routing flexibilityVSAvoidAF configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Instead of having each AF individually configured to fork data to other destinations (bottom-up approach), the patent inverts the approach by having the NEF centrally configured to distribute data to multiple AFs (top-down approach). This centralization at the NEF reduces configuration complexity while maintaining routing flexibility through the exposure function's controlled distribution mechanism.

Inventive Principle:
Principle #13The other way round (Inversion)

3Productivity

If multiple PDU sessions are established for reporting to multiple AFs, then data can be delivered to all destinations, but not all IoT devices support the capability to maintain multiple PDU sessions

Engineering Contradiction:
Improvedata delivery efficiencyVSAvoiddevice compatibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal solution where a single PDU session serves multiple AFs through the NEF's many-to-one mapping capability. This multi-functional approach allows any IoT device, regardless of its ability to maintain multiple sessions, to efficiently deliver data to multiple destinations through the NEF's coordinated distribution, enhancing both productivity and device compatibility.

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

4Measurement precision

If individual NIDD configurations are mapped to individual context creation requests, then data delivery is precise and controlled, but a significant volume of NIDD message traffic flow is experienced on northbound and southbound interfaces

Engineering Contradiction:
Improvedata routing precisionVSAvoidNIDD message traffic volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The patent merges multiple individual NIDD configurations and context creation requests into a single aggregated mapping at the NEF. Instead of processing separate configurations for each AF, the NEF consolidates them into one many-to-one mapping, maintaining precise routing control while dramatically reducing the volume of NIDD message traffic on network interfaces.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11758368B2Methods, systems, and computer readable media for supporting mobile originated data multicasting in a communications network
Publication Date: 2023.09.12 ORACLE INT CORP
  • US11758368B2 patent drawing
  • US11758368B2 patent drawing
  • US11758368B2 patent drawing

AI summary

Methods, systems, and computer readable media for supporting mobile originated data multicasting in a communications network are disclosed. One method includes receiving, from a consumer network function (NF) in a communications network, a deliver request message containing mobile originated (MO) data corresponding to a protocol data unit (PDU) session, wherein NIDD context information stored at NEF and referred by a context identifier in the deliver request message includes a subscriber identifier and a data network identifier associated with a user device requesting the PDU session and determining that a rule entry belonging to a plurality of rule entries contained in a multicasting ruleset matches at least one of the subscriber identifier and the data network identifier included in the NIDD context information that is stored at the NEF and referred by the context identifier in the deliver request message. The method further includes accessing a list of NF identity objects in the rule entry in response to determining the rule entry matches at least one of the subscriber identifier and/or the data network identifier and delivering the MO data to each of a plurality of NF endpoints specified in the rule entry in accordance with a routing condition indicated in each of the NF identity objects respectively associated with each of the NF endpoints.