LLCP Partitioning for NFC Power and Memory Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing implementation of Logical Link Control Protocol (LLCP) functionality in Near Field Communication (NFC) devices is costly in terms of power consumption and memory usage, as it requires the device host to handle all responsibilities, including symmetry procedures, which can lead to inefficiencies in power management and memory utilization.

Innovation Solution

The proposed solution partitions LLCP responsibilities between the NFC controller (NFCC) and the device host (DH), where the NFCC handles lower-layer LLCP functions like symmetry procedures, and the DH handles higher-layer functions, allowing for more efficient power management and memory usage by defining parameters such as symmetry timers and link timeouts to optimize communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the device host handles all LLCP responsibilities including symmetry procedures, then complete LLCP functionality is achieved, but power consumption increases and memory usage increases

Engineering Contradiction:
ImproveLLCP functionality completenessVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the LLCP functionality into two parts: symmetry procedures are handled by the NFCC (lower layer), while higher-layer LLCP functions are handled by the device host. This segmentation allows the power-intensive symmetry procedures to be offloaded from the device host, reducing its power consumption while maintaining complete LLCP functionality through the collaborative operation of both components.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the device host handles all LLCP responsibilities including symmetry procedures, then complete LLCP functionality is achieved, but memory usage increases

Engineering Contradiction:
ImproveLLCP functionality completenessVSAvoidmemory usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the LLCP functionality into two parts: symmetry procedures are handled by the NFCC (lower layer), while higher-layer LLCP functions are handled by the device host. This segmentation allows memory-intensive operations to be distributed, with the NFCC handling symmetry-related memory requirements and the device host focusing on higher-layer functions, thereby reducing overall memory usage while maintaining complete LLCP functionality.

Inventive Principle:
Principle #1Segmentation

3Use of energy by moving object

If the NFCC handles symmetry procedures, then power consumption is reduced, but device complexity increases

Engineering Contradiction:
Improvepower consumptionVSAvoidLLCP responsibility partitioning
Core Design Contradiction:
Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary communication interface between the NFCC and device host that handles the coordination of LLCP responsibilities. This intermediary layer manages the partitioning of duties, allowing the NFCC to handle symmetry procedures while maintaining a standardized interface for higher-layer functions, thereby reducing power consumption without significantly increasing overall device complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2798862B1Methods and apparatus for improving NFC LLCP partitioning
Publication Date: 2018.08.01 QUALCOMM INC
  • EP2798862B1 patent drawingFigure 1
  • EP2798862B1 patent drawingFigure 2
  • EP2798862B1 patent drawingFigure 3

AI summary

Aspects disclosed herein relate to partitioning LLCP responsibilities between the NFCC and DH. In an example, with a NFC device a DH maybe configured to establish a LLCP link with a remote NFC endpoint through a NFCC, and partition LLCP related responsibilities between the DH and the NFCC when the NFCC is operable for LLCP split communications. Further, the NFCC may be operable to receive a PDU from a remote NFC endpoint, determine whether the received PDU is a SYMM PDU or a link deactivation PDU, and communicate the received PDU to a DH upon a determination that the received PDU is not a SYMM PDU or a link deactivation PDU.