Service Access Layer Decouples Identity and Location in ICN

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Internet Protocol (IP) networks pre-bind service identity and location, leading to service disruptions during migration, limiting user and device mobility, and preventing the exploitation of multi-homing features.

Innovation Solution

An Information Centric Networking (ICN)-based Service Centric Networking (SCN) framework with a Service Access Layer (SAL) that dynamically resolves service names and locators based on contextual information, enabling context-aware service logistics and mobility by using a service routing mechanism and heterogeneous access points.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If service identity and location are pre-bound in IP networks, then service resolution is simplified, but service mobility is limited and sessions are interrupted during migration

Engineering Contradiction:
Improveservice resolutionVSAvoidservice mobility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the service identification process into two independent components: service identity (name) and service location (address). The service name remains bound to the service instance, while the service address can be dynamically updated. This segmentation allows the service to maintain its identity while changing location, enabling mobility without interrupting sessions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a service binding mechanism that acts as an intermediary between service identity and location. This binding layer decouples the direct relationship between service names and addresses, allowing the service location to be updated independently while maintaining the service identity. The intermediary enables dynamic location updates without affecting the service resolution process.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If service location is dynamically updated, then service mobility is improved, but host-level stack modifications are required

Engineering Contradiction:
Improveservice mobilityVSAvoidhost-level stack modifications
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service binding mechanism serves as an intermediary that handles location updates at the network layer without requiring modifications to the host application stack. The binding layer abstracts the complexity of location management, allowing services to be mobile while keeping the host stack unchanged.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds a new dimension to service management by introducing service binding as a separate layer between service identity and location. This dimensional addition allows location updates to occur independently without affecting the existing service stack, enabling mobility without host-level modifications.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of operation

If pre-binding is used for service resolution, then service access is simplified, but user mobility and device mobility are limited

Engineering Contradiction:
Improveservice accessVSAvoiduser and device mobility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments service access into identity-based access and location-based routing. Service consumers can access services using stable service names, while the network handles location updates independently. This segmentation enables both simplified service access and enhanced user/device mobility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic service binding that allows service locations to be updated in real-time while maintaining stable service identities. This dynamic mechanism enables users and devices to move freely while service access remains simplified through consistent service name resolution.

Inventive Principle:
Principle #15Dynamics

4Measurement precision

If service name resolution returns a fixed IP address, then service location is determined, but multi-homing features cannot be exploited

Engineering Contradiction:
Improveservice location determinationVSAvoidmulti-homing support
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic service binding where the service address can be updated to reflect multiple network interfaces or home networks. Instead of returning a fixed IP address, the system maintains a binding between service identity and multiple possible locations, enabling multi-homing while preserving precise service location determination.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The service binding mechanism provides universal service location management that works across multiple network interfaces and home networks. The same binding mechanism handles both single-homing and multi-homing scenarios, making the system versatile while maintaining precise service location determination.

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

Data Source

PatentEP2932657B1Information centric networking based service centric networking
Publication Date: 2020.08.05 HUAWEI TECH CO LTD
  • EP2932657B1 patent drawingFigure 1A
  • EP2932657B1 patent drawingFigure 1B
  • EP2932657B1 patent drawingFigure 2

AI summary

A method implemented by a network device residing in a service domain, wherein the network device comprises an information centric networking (ICN) transport layer and a service access layer (SAL) for handling context-aware service logistics and service mobility overlaid on the ICN transport layer, the method comprising receiving, in the ICN transport layer, a message comprising a service request that originates from a user equipment (UE), in the SAL, retrieving, from the service request, contextual information relevant to the UE or an access network connected to the UE, determining, based on the contextual information, one or more services needed to execute the service request, and determining one or more service identities (SIDs) each of which identifies one of the one or more services.