Network Address Book Synchronization Across Multiple User Equipment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional address book technologies have single-purpose functions closely related to specific services, making them unable to serve as independent functions and ensuring consistency of contact information across multiple user equipment (UEs), especially for presence information.

Innovation Solution

A network address book (NAB) system that parses and updates user address books, synchronizing contact information across multiple UEs, using protocols like XCAP, SIP, and XDMS to manage and combine contact data according to user settings, ensuring consistency and independence from specific services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If address books are implemented through service-specific clients (XDMS Client, Presence Client) on each UE, then service functionality is provided, but device complexity increases and consistency across multiple UEs cannot be ensured

Engineering Contradiction:
Improveservice functionalityVSAvoidclient installation and management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Network Address Book (NAB) server as an intermediary that centralizes address book storage and management. Instead of having multiple service-specific clients on each UE, the NAB server acts as a mediator that all UEs access through a standardized interface, thereby reducing device complexity while maintaining service functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The NAB server provides a universal address book service that can be accessed by multiple UEs and various services (IM, PoC, presence, etc.) through a single standardized interface. This eliminates the need for separate service-specific address book implementations on each device, achieving multi-functionality through a single system.

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

2Speed

If address book data is stored locally on each UE, then access speed is fast, but consistency across multiple UEs deteriorates when data is updated

Engineering Contradiction:
Improveaccess speedVSAvoiddata consistency
Core Design Contradiction:
SpeedVSStability of the object's composition

Solution Approach 1:

The system implements a feedback mechanism where the NAB server maintains the master copy of address book data and automatically pushes updates to all subscribed UEs. When data is updated on any UE or externally, the NAB server detects the change and distributes it to all other UEs, ensuring consistency while allowing fast local access to the cached data.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The NAB server performs preliminary actions by pre-synchronizing address book data to all UEs before they are needed. This allows UEs to have local copies for fast access, while the NAB server has already prepared and queued any updates that need to be distributed, ensuring consistency is maintained proactively rather than reactively.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If multiple service clients are installed on UE to support various address book functions, then service capability is enhanced, but ease of operation deteriorates

Engineering Contradiction:
Improveservice capabilityVSAvoiduser operation simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The NAB server provides a universal interface that supports multiple services (IM, PoC, presence information, etc.) through a single address book system. Users interact with one unified address book regardless of which service they are using, eliminating the need to manage multiple service-specific clients and simplifying operation while maintaining enhanced service capability.

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

4Reliability

If address book functions are closely integrated with specific services, then service-specific functionality is optimized, but adaptability deteriorates

Engineering Contradiction:
Improveservice-specific functionalityVSAvoidindependence from services
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the address book functionality into two independent parts: the core address book management functions hosted on the NAB server, and the service-specific access layers. This segmentation allows the core address book service to be independent and adaptable, while each service (IM, PoC, presence) can maintain its own optimized access methods through standardized interfaces, achieving both reliability and adaptability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8332468B2Method and system for processing an address book
Publication Date: 2012.12.11 HUAWEI TECH CO LTD
  • US8332468B2 patent drawing
  • US8332468B2 patent drawing
  • US8332468B2 patent drawing

AI summary

A method and a system for processing an address book are provided. The method includes the following steps. A network address book (NAB) parses a user address book, and generates an acquisition request according to settings of the user address book. The NAB acquires contact information to be updated according to the acquisition request, and updates the user address book. The NAB synchronizes or transmits updated information of the user address book to a piece of user equipment (UE). By using the method, plenty of contact information is acquired according to the user settings. Therefore, the method solves the problems that the address books in the conventional technology have single-purpose functions and closely related to services and thus cannot serve as an independent function for providing services for the user. In addition, address book information on a plurality of UEs of the user can be updated synchronously, so that when one UE initiates address book information update, the address books on other UEs are updated accordingly. Therefore, the consistency between the address book information on the UEs is guaranteed.