# US 2014/0192717 A1 · Information Centric Networking Based Service Centric Networking

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0192717 A1
- Document ID: US20140192717A1
- Status: Published application
- Kind: A1
- Application number: 14/148,509
- Filed: 2014-01-06
- Published: 2014-07-10
- Earliest claimed: 2013-01-07
- Assignees: Futurewei Technologies, Inc.
- Applicants: Futurewei Technologies, Inc.
- Inventors: Xuan Liu; Ravishankar Ravindran; Guo-Qiang Wang
- Web page: https://patentgrep.com/patent/US20140192717A1

## CPC

- H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/63: Routing a service request depending on the request content or context
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

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.

## Claims

### Claim 1

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.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
determining, by querying a database in the SAL, that at least one instance of a service in the one or more services is available from at least one service provider residing in the service domain;
decomposing the service into two or more tasks, each of which represents an instance of the service; and
transmitting, in the ICN transport layer, service interest packets specifying one or more of the tasks to the at least one service provider.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
updating a database in the SAL to register a new service publish action from a service producer;
publishing the new service to a second network device functioning as a service profile manager (SPM);
receiving, in the ICN transport layer, information from the SPM indicating one or more resolution points of service producers who support the new service; and
further updating the database to include one or more entries specifying the one or more resolution points.

### Claim 4 (depends on 1)

The method of claim 1, wherein the contextual information determines that a plurality of services are needed to process the service request, wherein a plurality of SIDs are determined for the plurality of services, the method further comprising:
generating a service logic graph that uses the plurality of SIDs to describe logic relationships between the plurality of services;
generating, based on the service logic graph, a number of service navigation fields which describe the service request, the SIDs, and the logic relationships; and
transmitting, in the ICN transport layer, one or more service interest packets comprising at least one of the service logic graph and the service navigation fields.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
receiving, in the ICN transport layer, service data returned from one or more service providers that provide the plurality of services in response to receiving the service interest packets; and
forwarding, in the ICN transport layer, the returned service data to the UE in response to receiving the service request.

### Claim 6 (depends on 4)

The method of claim 4, wherein the service logic graph is generated based on the contextual information and service semantics, wherein the logic relationships specify an order in which the plurality of services need to be processed for the service request.

### Claim 7 (depends on 6)

The method of claim 6, wherein the service navigation fields are selected from the group consisting of a request ID, a source service ID, a current service ID, a rule, and a next service ID, wherein the request ID identifies the service request, the source service ID identifies a previously processed service according to the order, the current service ID identifies a current service under processing, the next service ID identifies a next hop service according to the order, and the rule specifies whether the next hop service should be in series or in parallel to the current service.

### Claim 8 (depends on 1)

The method of claim 1, wherein the access network is a wired, wireless, or mobile connection connected to the UE, and wherein the contextual information includes at least one of device context of the UE, mobility context of the UE, environment context of the UE, context of the access network, and personal or social context of a service consumer using the UE.

### Claim 9 (depends on 1)

The method of claim 1, wherein determining the one or more SIDs comprises:
translating the contextual information into a service description written in a standard service description language; and
resolving the service description to the one or more corresponding SIDs by using a policy database in the SAL.

### Claim 10 (depends on 1)

The method of claim 1, wherein the SRN corresponds to a global locator for a SID in the one or more SIDs, the method further comprising:
discovering, in the SAL, a heterogeneous access point (H-AP) that publishes the service;
updating a routing prefix of the service to be the H-AP; and
forwarding, in the ICN transport layer, the service request to the H-AP.

### Claim 11

A network device functioning as a heterogeneous access point (H-AP), the network device comprising:
at least one receiver configured to receive a publishing message that advertises a new service;
a service access controller (SAC) coupled to the receiver and configured to:
add a new entry to a service access strategy table (SAST) in the SAC to reflect availability of the new service; and
update the publishing message to generate an updated publishing message which comprises the H-AP as a prefix; and
at least one transceiver coupled to the SAC and configured to:
forward the updated publishing message; and
transmit, to a second network device functioning as a service routing node (SRN), a notification message indicating that the new service is available from the H-AP.

### Claim 12 (depends on 11)

The network device of claim 11, wherein the at least one transceiver is further configured to receive a network attachment request from a third network device functioning as a point of attachment (PoA), the network device further comprising a mobility controller (MC) coupled to the SAC and configured to store, in a mobility strategy table (MST) in the MC, network access context information for user devices, wherein the network access context information comprises a network connectivity prefix and a priority corresponding to the prefix.

### Claim 13 (depends on 11)

The network device of claim 11, wherein the at least one transceiver is further configured to receive a service interest packet requesting for a service that is identifiable via a service identity (SID), wherein the H-AP is a local locator for the SID in a service domain in which the H-AP and the UE reside, wherein the MC is further configured to:
determine a point of attachment (PoA) through which the service is provided; and
update a routing prefix of the service to be the PoA,
wherein the at least one transceiver is further configured to forward the interest packet to the PoA.

### Claim 14 (depends on 11)

The network device of claim 11, wherein the at least one transceiver is further configured to receive, from a point of attachment (PoA), a notification message indicating network registration of a user equipment (UE), wherein the MC is further configured to:
update an access profile database in the MC with information of the UE; and
update a mobility strategy table (MST) in the MC to include access context states of the UE and the PoA,
wherein the at least one transceiver is further configured to send, to the PoA, a prefix of the H-AP as a response to the notification message.

### Claim 15 (depends on 14)

The network device of claim 14, wherein the at least one transceiver is further configured to:
receive, from the PoA, a request for de-registration of the UE;
receive, from a second PoA, a second notification message indicating a new network registration of the UE; and
send, to the second PoA, a prefix of the H-AP as a response to the second notification message,
wherein the MC is further configured to update the MST to indicate the attachment of the UE to the second PoA.

### Claim 16 (depends on 15)

The network device of claim 15, wherein the SAC is further configured to determine that the service is still accessible from both the PoA and the second PoA and has a same priority, wherein the at least one transceiver is further configured to send the service interest to both the PoA and the second PoA.

### Claim 17 (depends on 11)

The network device of claim 11, wherein the at least one transceiver is further configured to receive, from a point of attachment (PoA), a request for permanent de-registration of a user equipment (UE), wherein the MC and the SAC are configured to update a service profile database, the MST, and the SAST to remove entries corresponding to the UE, and wherein the at least one transceiver is further configured to send, to a service profile manager (SPM), a message indicating the de-registration of the UE.

### Claim 18

A method implemented by a network device functioning as a point of attachment (PoA), the method comprising:
receiving, from a user equipment (UE), a request for network registration;
retrieving, from the request, access context of the UE which identifies the UE;
updating one or more data structures in the PoA to include the access context and a default priority set for the UE;
sending, to the UE, a prefix of the PoA as a response to the request; and
sending, to a second network device functioning as a heterogeneous access point (H-AP), a message notifying the H-AP of the registration request from the UE, wherein the PoA has registered with the H-AP.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
receiving a service interest for a service identifiable via a service identity (SID), wherein the PoA corresponds to a local locator for the SID;
determining, based on a data structure in the one or more data structures, that the UE provides the service;
updating a routing prefix of the service to be the UE; and
forwarding the service interest to the UE.

### Claim 20 (depends on 18)

The method of claim 18, further comprising:
receiving, from the UE, a request for de-registration of the UE;
updating the one or more data structures to remove the access context of the UE and the default priority set for the UE; and
sending, to the H-AP, a message notifying the H-AP of the de-registration request of the UE.