# US 10,122,632 B2 · Anchoring IP devices in ICN networks > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,122,632 B2 - Document ID: US10122632B2 - Status: Granted - Kind: B2 - Application number: 15/518,688 - Filed: 2015-10-14 - Published: 2017-08-17 - Granted: 2018-11-06 - Earliest claimed: 2014-10-14 - Assignees: IDAC Holdings, Inc. - Applicants: Idac Holdings, Inc. - Inventors: Dirk Trossen; Sebastian Robitzsch - Web page: https://patentgrep.com/patent/US10122632B2 ## CPC - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L 45/741: Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6 - H04L 45/745: Address table lookup; Address filtering - H04L 45/748: using longest matching prefix - H04L 61/45: Network directories; Name-to-address mapping - H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching - H04L 2101/33: containing protocol addresses or telephone numbers - H04L 2212/00: Encapsulation of packets - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Procedures, methods and architectures for anchoring communication between IP-based devices in an ICN network or across an IP peer network are disclosed. Embodiments may enable the communication between two IP-based devices connected to an ICN, or one IP-based device connected to an ICN network while another IP-based device is connected either to an ICN network or IP network. In an embodiment, IP packets originating from an IP-based device may be encapsulated into ICN packets and forwarded via an ICN network. In an embodiment, IP packets received via an ICN network may be encapsulated in ICN packets and forwarded to an IP-based device. In an embodiment, IP packets originating from an IP-based device may be forwarded and received via an ICN network towards another IP network. In an embodiment, IP packets received by an ICN network may be forwarded towards an IP-based device via the ICN network. ## Claims ### Claim 1 A method of anchoring communication between Internet Protocol (IP)-based devices in an information centric networking (ICN) network or across an IP peer network, the method comprising: receiving, by a network access point (NAP) of an ICN network, an IP packet from an IP-only wireless transmit/receive unit (WTRU); determining, by the NAP, an appropriate ICN name for the IP packet based on an IP address of an intended destination of the IP packet, wherein the ICN name comprises a hierarchy of a root identifier for IP over ICN communication, a first sub-scope identifier for within ICN communication and a second sub-scope identifier for outside ICN communication below the root identifier, and one or more levels of IP subnet identifiers below the first sub-scope identifier and the second sub-scope identifier; encapsulating, by the NAP, the IP packet into an ICN packet by inserting the ICN name into a packet header; and sending, by the NAP, the ICN packet to a plurality of devices subscribed to the ICN name. ### Claim 2 (depends on 1) The method of claim 1, wherein each of the one or more levels of IP subnet identifiers comprise a group of the IP address. ### Claim 3 (depends on 1) The method of claim 1, wherein the IP address is in IPv4 format and each of the one or more levels of IP subnet identifiers comprise a decimal number representing 8 bits of the IP address. ### Claim 4 (depends on 1) The method of claim 1, wherein the IP address is in IPv6 format and each of the one or more levels of IP subnet identifiers comprise a group of four hexadecimal digits representing 16 bits of the IP address. ### Claim 5 (depends on 1) The method of claim 1, wherein the root identifier comprises: first prefix scopes for IP operator-internal IP prefix ranges; and second prefix scopes for scopes for external IP prefix ranges. ### Claim 6 (depends on 5) The method of claim 5, wherein the first prefix scopes and the second prefix scopes are determined through a combination of the IP address and subnet mask information of IP routing prefixes. ### Claim 7 (depends on 5) The method of claim 5, wherein the second prefix scopes are calculated and published under the root scope by an operator management system based on known IP prefix configurations of an IP border gateway (GW) of the operator. ### Claim 8 (depends on 5) The method of claim 5, wherein the second prefix scopes are calculated and published by an IP border gateway (GW). ### Claim 9 (depends on 5) The method of claim 5, wherein the first prefix scopes are published by an internal management entity. ### Claim 10 (depends on 1) The method of claim 1, wherein the one or more of the plurality of devices are subscribed to different levels of the IP subnet identifiers. ### Claim 11 An information centric networking (ICN) network access point (NAP) for anchoring communication between Internet Protocol (IP)-based devices in an ICN network or across an IP peer network, the NAP comprising: a circuitry configured to receive an IP packet from an IP-only wireless transmit/receive unit (WTRU); the circuitry further configured to determine an appropriate ICN name for the IP packet based on an IP address of an intended destination of the IP packet, wherein the ICN name comprises a hierarchy of a root identifier for IP over ICN communication, a first sub-scope identifier for within ICN communication and a second sub-scope identifier for outside ICN communication below the root identifier, and one or more levels of IP subnet identifiers below the first sub-scope identifier and the second sub-scope identifier; encapsulate the IP packet into an ICN packet by inserting the ICN name into a packet header; and the circuitry further configured to send the ICN packet to a plurality of devices subscribed to the ICN name. ### Claim 12 (depends on 11) The NAP of claim 11, wherein each of the one or more levels of IP subnet identifiers comprise a group of the IP address. ### Claim 13 (depends on 11) The NAP of claim 11, wherein the IP address is in IPv4 format and each of the one or more levels of IP subnet identifiers comprise a decimal number representing 8 bits of the IP address. ### Claim 14 (depends on 11) The NAP of claim 11, wherein the IP address is in IPv6 format and each of the one or more levels of IP subnet identifiers comprise a group of four hexadecimal digits representing 16 bits of the IP address. ### Claim 15 (depends on 11) The NAP of claim 11, wherein the root identifier comprises: first prefix scopes for IP operator-internal IP prefix ranges; and second prefix scopes for scopes for external IP prefix ranges. ### Claim 16 (depends on 15) The NAP of claim 15, wherein the first prefix scopes and the second prefix scopes are determined through a combination of the IP address and subnet mask information of IP routing prefixes. ### Claim 17 (depends on 15) The NAP of claim 15, wherein the second prefix scopes are calculated and published under the root scope by an operator management system based on known IP prefix configurations of an IP border gateway (GW) of the operator. ### Claim 18 (depends on 15) The NAP of claim 15, wherein the second prefix scopes are calculated and published by an IP border gateway (GW). ### Claim 19 (depends on 15) The NAP of claim 15, wherein the first prefix scopes are published by an internal management entity. ### Claim 20 (depends on 11) The NAP of claim 11, wherein the one or more of the plurality of devices are subscribed to different levels of the IP subnet identifiers.