# US 2014/0195641 A1 · Contextualized Information Bus > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0195641 A1 - Document ID: US20140195641A1 - Status: Published application - Kind: A1 - Application number: 14/149,558 - Filed: 2014-01-07 - Published: 2014-07-10 - Earliest claimed: 2013-01-07 - Assignees: Futurewei Technologies, Inc. - Applicants: Futurewei Technologies, Inc. - Inventors: Guo-Qiang Wang; Ravishankar Ravindran - Web page: https://patentgrep.com/patent/US20140195641A1 ## CPC - H04L 67/63: Routing a service request depending on the request content or context - H04L 45/04: {Interdomain routing, e.g. hierarchical routing} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract An NE comprising a plurality of physical interfaces configured to communicate to a plurality of remote NEs in an ICN, a receiver coupled to the plurality of physical interfaces and configured to receive a request for a service from a first of the remote NE via the ICN, wherein the service request comprises a requested service name and a requested service context, a memory comprising a service profile comprising a supported service associating with a supported service name and a supported service context, a processor coupled to the memory and the receiver and configured to generate a service response when the requested service name matches the supported service name and the requested service context matches the supported service context, and a transmitter coupled to the processor and the plurality of physical interfaces and configured to transmit the service response to the first NE via the ICN. ## Claims ### Claim 1 A network element (NE) comprising: a plurality of physical interfaces configured to communicate with a plurality of remote NEs in an information centric network (ICN); a receiver coupled to the plurality of physical interfaces, and configured to receive a request for a service from a first of the remote NEs via the ICN, wherein the service request comprises a requested service name comprising a hierarchical name structure identifying the requested service and a requested service context comprising a service type attribute of the requested service; a memory comprising: a service profile comprising a supported service, wherein the supported service is associated with a supported service name and a supported service context; and a forwarding information base (FIB); a processor coupled to the memory and the receiver and configured to: generate a service response when the requested service name matches the supported service name and the requested service context matches the supported service context; and store a routing path in a FIB, wherein the routing path identifies a physical interface where the service request is received; and a transmitter coupled to the processor and the plurality of physical interfaces and configured to transmit the service response to the first NE according to the routing path via the ICN. ### Claim 2 (depends on 1) The NE of claim 1, wherein the processor is further configured to: generate a request for a second service comprising a second service name and a second service context; instruct the transmitter to transmit the second service request to the remote NEs via all of the plurality of physical interfaces via the ICN; receive from the ICN via the receiver, a second service response from a second of the remote NEs, wherein the second NE supports a service with a service name and a service context matching the second service request; and perform self-clustering with the second NE without supervision from a central network management entity. ### Claim 3 (depends on 1) The NE of claim 1, wherein the processor is further configured to: generate a request for a second service comprising a second service name and a second service context; instruct the transmitter to transmit the second service request to a central management entity via at least of one of the physical interfaces via the ICN; and receive from the ICN via the receiver, a second service response from the central management entity indicating a second of the NEs, wherein the second NE supports a service with a service name and a service context matching the second service request ### Claim 4 (depends on 1) The NE of claim 1, wherein the processor is further configured to perform name resolution by mapping a data identifier comprising a name of a data object and a context of the data object to a locator of the data object. ### Claim 5 (depends on 1) The NE of claim 1, wherein the processor is further configured to perform mobility management by: tracking a locator of a data object based on a name of the data object and a context of the data object; and determining a set of interfaces for handover based on the name of the data object and the context of the data object. ### Claim 6 (depends on 1) The NE of claim 1, wherein the processor is further configured to perform security management by authorizing, a data object based on a name of the data object and a context of the data object, authenticating the data object based on the name of the data object and the context of the data object, or combinations thereof. ### Claim 7 (depends on 1) The NE of claim 1, further comprising an application sub-system coupled to the processor and configured to generate a service request application programming interface (API) call to request an operation for a second service with a parameter list comprising a second service name and a second service context, wherein the processor is further configured to process the API call according to the second service name and the second service context, and wherein the requested service operation comprises the discovery of the second service, a subscription to the second service, a connection to the second service, a composition of the second service, an orchestration of the second service, or combinations thereof. ### Claim 8 (depends on 1) The NE of claim 1 further comprises an application sub-system coupled to the processor, wherein the application sub-system is configured to: generate a get request application programming interface (API) call to fetch a first data object from one of the remote NEs with a get parameter list comprising a first data name of the first data object and a first context of the first data object; and generate a put request API call to publish a second data object to at least one of the remote NEs with a put parameter list comprising a second name of the second data object and a second context of the second data object, and wherein the processor is further configured to: process the get request API call according to the first name and the first context; and process the put request API call according to the second name and the second context. ### Claim 9 (depends on 1) The NE of claim 1, wherein the receiver is further configured to receive a data object comprising a name of the data object and a context of the data object via one of the physical interfaces via the ICN, and wherein the transmitter is further configured to forward the data object based on the name and the context of the data object via all of the physical interfaces except the receiving physical interface. ### Claim 10 A method for interfacing with an information centric network (ICN) protocol layer, wherein the method comprises: generating a service request primitive based on a data object name comprising a hierarchical name structure identifying the data object and a data object context comprising a data type attribute; and sending the service request primitive to the ICN protocol layer for delivery to a remote network element (NE) in an ICN based on the data object name and the data object context. ### Claim 11 (depends on 10) The method of claim 10, wherein the service request primitive comprises a get operation and a parameter list comprising the data object name and the data object context, wherein the get operation requests delivery of the data object from the remote NE via the ICN based on the data object name and the data object context, and wherein the method further comprises receiving a service response primitive comprising the requested data object from the remote NE via the ICN across the ICN protocol layer. ### Claim 12 (depends on 10) The method of claim 10, wherein the service request primitive comprises a put operation and a parameter list comprising the data object name and the data object context, and wherein the put operation requests publication of the data object to the remote NE via the ICN based on the data object name and the data object context. ### Claim 13 (depends on 10) The method of claim 10, wherein the service request primitive comprises a delete operation and a parameter list comprising the data object name and the data object context, and wherein the delete operation requests deletion of the data object from the remote NE based on the data object name and the data object context. ### Claim 14 (depends on 10) The method of claim 10 further comprising: generating an action request primitive comprising an action request and a parameter list comprising a name of an action and a context of the action, wherein the action comprises a network registration, network de-registration, a service subscription, a content subscription, or combinations thereof; and sending the action request primitive to the ICN protocol layer for delivery to the remote NE in the ICN based on the action name and the action context. ### Claim 15 (depends on 10) The method of claim 10 further comprising: generating an event notification primitive comprising a notification of an event and a parameter list comprising a name of the event and a context of the event; and sending the event notification primitive to the ICN protocol layer for delivery to the remote NE in the ICN based on the event name and the event context. ### Claim 16 A network element (NE) comprising: a plurality of interfaces configured to couple to an information centric network (ICN), wherein each interface employs a different transmission mechanism; a memory comprising a mapping of a data object identifier to a plurality of data type attributes of a data object; a processor coupled to the memory and configured to: compute a delivery metric for each interface based on the data type attributes; and select a first interface based on the delivery metric; and a transmitter coupled to the first interface and configured to transmit the data object associated with the identifier. ### Claim 17 (depends on 16) The NE of claim 16, further comprising a service sub-system coupled to the processor, wherein the service sub-system is configured to generate a subscription application programing interface (API) call to subscribe to an event of a transmission link coupled to the ICN via one of the interfaces, and wherein the processor is further configured to: generate a link event notification when the subscribed event occurs; and notify the service sub-system of the subscribed event. ### Claim 18 (depends on 17) The NE of claim 17, further comprising a service sub-system coupled to the processor and configured to generate an action API to request an action, wherein the action comprises data forwarding, data reception, interface selection, mobility, or combinations thereof, and wherein the processor further configured to perform the requested action. ### Claim 19 (depends on 16) The NE of claim 16, wherein the processor is further configured to: compute an updated delivery metric for each interface based on the data type attributes; select a second interface from the plurality of the interfaces based on the updated delivery metric; and deselect the first interface, wherein the NE further comprises a second transmitter coupled to the second interface to transmit a second data object associated with the identifier. ### Claim 20 (depends on 16) The NE of claim 16, wherein the transmission mechanisms comprise mobile wireless transmission, wireless local area network transmission, or combinations thereof.