Multicast Service Information Update Notification in NB-IoT Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In NB-IoT and eMTC networks, there is a lack of effective mechanisms for timely notification of service information changes, particularly for emergency software updates, which affects power saving and data integrity due to limitations in simultaneous channel reception by user equipment (UE).

Innovation Solution

A method and apparatus for notifying service information changes in NB-IoT and eMTC networks, where an access network element sends update indications and service information to UE through system information blocks, single-cell multicast control channels, or paging messages, using techniques like logical exclusive OR operations on service identification and area information, ensuring timely updates and efficient power management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If the UE is required to keep detecting change notification of the SC-MCCH information, then the service information update timeliness is improved, but the power consumption of the UE increases significantly

Engineering Contradiction:
Improveservice information update timelinessVSAvoidpower consumption of UE
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The network configures the UE with discontinuous reception (DRX) parameters including onDuration, drxOffset, and drxPeriod, allowing the UE to periodically wake up to check for service information updates rather than continuously monitoring. This periodic action reduces power consumption while maintaining update timeliness by scheduling wake-up moments when update notifications are likely to occur.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The network sends change notification indicators (such as PDCCH with specific RNTI or MAC CE) to inform the UE when service information has been updated. This feedback mechanism allows the UE to sleep and only wake up when notified of changes, rather than continuously monitoring, thus reducing power consumption while ensuring timely update reception.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If the SC-MCCH and SC-MTCH are scheduled on different carriers, then the network scheduling flexibility is improved, but the UE cannot receive both channels simultaneously due to limited reception capability

Engineering Contradiction:
Improvenetwork scheduling flexibilityVSAvoiddata integrity of multicast service
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The service information is segmented into control information (SC-MCCH) and traffic data (SC-MTCH), which are scheduled on different carriers. The control carrier carries scheduling and configuration information, while the traffic carrier carries actual data. This segmentation allows the network to flexibly schedule on different carriers while the UE processes them sequentially based on scheduling indications, maintaining reliability despite limited simultaneous reception capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The PDCCH on the control carrier acts as an intermediary that provides scheduling information for the SC-MTCH on the traffic carrier. The UE first receives and decodes the PDCCH to obtain scheduling information, then uses this information to receive the corresponding SC-MTCH data. This intermediary mechanism enables the UE to handle multiple carriers sequentially rather than simultaneously, maintaining data integrity while allowing network scheduling flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If the network pushes emergency software update, then the update speed is improved, but the existing notification mechanism cannot deliver the update information in time

Engineering Contradiction:
Improveupdate speedVSAvoidupdate information delivery timeliness
Core Design Contradiction:
SpeedVSLoss of information

Solution Approach 1:

The network pre-configures the UE with DRX parameters, RNTI values, and scheduling information before emergency updates are needed. This preliminary configuration enables the UE to quickly wake up and receive emergency update notifications when they occur, without requiring complex real-time configuration during the emergency update process, thus achieving fast update delivery.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The PDCCH with specific RNTI (such as SC-N-RNTI or MCCH-RNTI) acts as an intermediary notification mechanism for emergency updates. When emergency software updates are needed, the network sends wake-up indicators or change notifications through this intermediary channel, which the UE monitors periodically. This allows rapid delivery of emergency update information while maintaining the power-saving periodic monitoring mode.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10952034B2Multicast service information change notification method and apparatus
Publication Date: 2021.03.16 ZTE CORP
  • US10952034B2 patent drawing
  • US10952034B2 patent drawing
  • US10952034B2 patent drawing

AI summary

A multicast service information change notification method comprises: an access network element sends to a UE a multicast service information update command; and the access network element indicates multicast service information to the UE service.