Node and method for handling information centric networking based communications

Abstract

A base station and wireless device, as well as corresponding methods, for Information Centric Networking (ICN) based communications with radio bearers, to provide a means for using ICN bearers in parallel with standard Packet Data Network (PDN) bearers.

Claims

1. A method, in a base station, for Information Centric Networking (ICN) based communications with radio bearers, the method comprising: establishing a default bearer in response to a request from a wireless device to establish a default bearer; establishing an ICN dedicated radio bearer separate from but in parallel with the default bearer, wherein the ICN dedicated radio bearer is terminated locally on the base station and the default bearer is tunneled through the base station towards a core network gateway; receiving, from the wireless device, a request for content on the ICN dedicated radio bearer; determining if the content in the request is in a cache associated to or in the base station; and when the content is cached, sending, to the wireless device, the content; when the content is not cached, sending, to an ICN based network, the request on an interface dedicated for ICN communications.

2. The method of claim 1, further comprising: receiving an indication that the wireless device is compatible for ICN based communications prior to establishing the ICN dedicated radio bearer.

3. The method of claim 1, further comprising registering, within the base station, the request for content with respect to the wireless device.

4. The method of claim 1, wherein the content is multimedia data.

5. The method of claim 1, wherein the wireless device is a machine-to-machine (M2M) device and the content is M2M related data.

6. The method of claim 1, wherein the interface dedicated for ICN communications is further dedicated for communications to and from the wireless device.

7. The method of claim 1, further comprising: receiving, from the ICN based network, a content response; and transmitting, to the wireless device, the content response on the ICN dedicated radio bearer.

8. The method of claim 1, further comprising: determining a frequency in which the content has been requested; and when the frequency is above a predetermined threshold, caching the content within the base station.

9. A base station for Information Centric Networking (ICN) based communications with radio bearers, the base station comprising: a receiver configured to receive, from a wireless device, a request to establish a default bearer; processing circuitry configured to establish the default bearer with the wireless device and to establish an ICN dedicated radio bearer separate from but in parallel with the default bearer such that the ICN dedicated radio bearer is terminated locally on the base station and the default bearer is tunneled through the base station towards a core network gateway; the receiver being further configured to receive, from the wireless device, a request for content on the ICN dedicated radio bearer; the processing circuitry being configured to determine if the content in the request is in a cache associated to or in the base station; and a transmitter configured to: when the content is cached, transmit, to the wireless device, the content, and when the content is not cached, transmit, to an ICN based network, the request on an interface dedicated for ICN communications.

10. The base station of claim 9, wherein the receiver is further configured to receive an indication that the wireless device is compatible for ICN based communications, and wherein the processing circuitry is further configured to establish the ICN dedicated bearer in response to the indication.

11. The base station of claim 9, wherein the processing circuitry is further configured to register, within the base station, the request for content with respect to the wireless device.

12. The base station of claim 9, wherein the content is multimedia data.

13. The base station of claim 9, wherein the wireless device is a machine-to-machine (M2M) device and the content is M2M related data.

14. The base station of claim 9, wherein the interface dedicated for ICN communications is further dedicated for communications to and from the wireless device.

15. The base station of claim 9, wherein the receiver is further configured to receive, from the ICN based network, a content response, and wherein the transmitter is further configured to transmit, to the wireless device, the content response on the ICN dedicated radio bearer.

16. The base station of claim 9, wherein the processing circuitry is further configured to determine a frequency in which the content has been requested, and when the frequency is above a predetermined threshold, the processing circuitry is further configured to cache the content within the base station.

17. A method, in a wireless device, for Information Centric Networking (ICN) based communications with radio bearers, the method comprising: sending, to a base station, a request for establishment of a default bearer to provide always on connectivity for the wireless device; establishing the default bearer with the base station, the default bearer being tunneled through the base station towards a core network gateway; receiving from the base station a signal to establish an ICN dedicated radio bearer separate from but in parallel with the default bearer; establishing the ICN dedicated radio bearer with the base station such that the ICN dedicated radio bearer is terminated locally on the base station; determining, via an Application Programming Interface (API), a need for ICN compatible content; and sending, to a base station, a request for content on the ICN dedicated radio bearer.

18. The method of claim 17, wherein the content is multimedia data.

19. The method of claim 17, wherein the wireless device is a machine-to-machine (M2M) device and the content is M2M related data.

20. The method of claim 17, further comprising receiving, from the base station, a content response on the ICN dedicated radio bearer.

21. A wireless device for Information Centric Networking (ICN) based communications with radio bearers, the wireless device comprising: a transmitter configured to transmit, to a base station, a request for establishment of a default bearer to provide always on connectivity for the wireless device; processing circuitry configured to establish the default bearer with the base station, the default bearer being tunneled through the base station towards a core network gateway; a receiver configured to receive from the base station a signal to establish an ICN dedicated radio bearer separate from but in parallel with the default bearer; the processor circuitry being further configured to: establish the ICN dedicated radio bearer with the base station such that the ICN dedicated radio bearer is terminated locally on the base station; and determine, via an Application Programming Interface (API), a need for ICN compatible content; and the transmitter being further configured to transmit, to the base station, a request for content on the ICN dedicated radio bearer.

22. The wireless device of claim 21, wherein the content is multimedia data.

23. The wireless device of claim 21, wherein the wireless device is a machine-to-machine (M2M) device and the content is M2M related data.

24. The wireless device of claim 21, wherein the receiver is further configured to receive, from the base station, a content response on the ICN dedicated radio bearer.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The foregoing will be apparent from the following more particular description of the example embodiments, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the example embodiments.

(2) FIG. 1 is an illustrative example of a wireless network featuring ICN and IP based components, according to some of the example embodiments;

(3) FIG. 2 is an illustrative working example of the bearer connections between a wireless device and a base station, according to some of the example embodiments,

(4) FIG. 3 is an example node configuration of a base station, according to some of the example embodiments;

(5) FIG. 4 is an example node configuration of a wireless device, according to some of the example embodiments,

(6) FIG. 5A is a flow diagram depicting example operations that may be taken by the base station of FIG. 3, according to some of the example embodiments;

(7) FIG. 5B is an illustrative example of modules which may carry out the example operations of FIG. 5A;

(8) FIG. 6A is a flow diagram depicting example operations that may be taken by the wireless device of FIG. 4, according to some of the example embodiments; and

(9) FIG. 6B is an illustrative example of modules which may carry out the example operations of FIG. 6A.

DETAILED DESCRIPTION

(10) In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular components, elements, techniques, etc. in order to provide a thorough understanding of the example embodiments. However, it will be apparent to one skilled in the art that the example embodiments may be practiced in other manners that depart from these specific details. In other instances, detailed descriptions of well-known methods and elements are omitted so as not to obscure the description of the example embodiments. The terminology used herein is for the purpose of describing the example embodiments and is not intended to limit the embodiments presented herein. It should be appreciated that the terms wireless device, UE and user equipment may be used interchangeably herein. It should be appreciated that all of the example embodiments presented herein may be applicable to a GERAN, UTRAN or E-UTRAN based system.

(11) General Overview

(12) In order to provide a better explanation of the example embodiments presented herein, a problem will first be identified and discussed. Today, content distribution in ad-hoc networks rely of host based (Internet Protocol, IP) mechanisms for content retrieval and distribution. The research community is in agreement that host based communication paradigms do not scale well as content distribution becomes the dominant part of traffic load globally. The most efficient technique is to run media optimized protocols, e.g. the Content Centric Networking (CCN) protocols over the wire without any IP underneath.

(13) Another issue with current content distribution is how to reach all the way to the terminals that are served. Ideally, content traffic to terminals will follow a path where all traffic is carried using CCN over the wire and end-to-end, i.e. not CCN layered on top of IP. However, since it is inherently difficult to predict exactly how terminals connect to a network (e.g. via a public WiFi hotspot, or via a private hotspot in the home or other), supporting CCN would require a forklift of the entire Internet. Thus, it is extremely challenging in today's networks to start to introduce CCN. One could create walled gardens, e.g. virtual groups, but these would then typically require IP underneath, as a bridge between CCN islands, thus counteracting the intention of efficient media distribution.

(14) Another issue with CCN is that it is session based, e.g. the UE needs to send an interest packet towards the network, after which it will get the content back. In most scenarios with CCN, the idea is to only use CCN to the terminals, which in turn requires that non-session based protocols, e.g. TCP/IP, be emulated over CCN. This adds ample complexity to CCN.

(15) A third issue with CCN is that it currently doesn't support publisher mobility although there are research proposals to that end. So if a wireless device connected to an access point moves from that access point to another access point, CCN has no support to find the new access point and inform the rest of the CCN community. To deal with this, many mechanisms have been proposed, but none that makes inherent use of mobility management inherent to 3GPP networks.

Overview of Some of the Example Embodiments

(16) When a LTE UE connects to a LTE network, according to 3GPP it will automatically establish a default bearer towards a PDN Gateway (PGW). This bearer will provide the always-on connectivity inherent to LTE.

(17) Some of the example embodiments are directed towards a method for establishing another bearer which is used for the purpose of carrying ICN/CCN (Information/Content Centric Networking Protocols) over-the-wire or rather over-the-radio-bearer. The latter implies that the UE in the Uplink direction (UL) will map e.g. CCN PDUs straight into the radio bearer established for that purpose. That CCN PDU will at some point inside the network, typically on the macro RBS or a small cell deployed in a hotspot such as a shopping mall, be extracted and injected into a CCN-enabled network, and vice-versa in the Downlink direction (DL).

(18) The above operational model would be in accordance with 3GPP standards in the radio access network (RAN), in particular the use of local break out of bearers, e.g. as is done for Local IP Access (LIPA) in 3GPP.

(19) On the UE, both CCN and host based sockets (for TCP/UDP/IP) will be available, so that parallel host-based and CCN-based communication is supported. Alternatively, the use of CCN on the UE will be implemented inside the modem parts, so that the UE applications use their normal TCP/IP APIs but 3GPP compliant filters inside the UE modem will direct the CCN packets over the CCN bearer in a way transparent to the applications. The IP layer would then just be a dummy layer that is used to simplify the interaction with the API eco system.

(20) Publisher mobility mechanisms, when UEs are the publishers, shall rely on reuse of 3GPP facilities in support of mobility management and control.

(21) Example embodiments presented herein are directed towards a base station and wireless device, as well as corresponding methods therein, for Information Centric Networking (ICN) based communications with radio bearers. The example embodiments provide a means for using ICN bearers in parallel with standard Packet Data Network (PDN) bearers.

(22) In the future Networked Society, virtually all devices will be wireless. It is likely that both LTE/5G and WiFi will play a key role in delivering the necessary wireless links to all those devices.

(23) The example embodiments presented herein may apply to LTE and its evolution towards 5G. The latter will most likely be an evolution of LTE in higher frequency bands, and LTE with different scaling than today (e.g. up-scaled bandwidth and down-scaled transmission time intervals for lower latency, etc.). LTE has proven to be very robust in its basic structures and there is little evidence to suggest that its fundamentals will change.

(24) Over the air interface, LTE makes use of radio bearers, which provide separate logical channels of various QoS and other characteristics. Combined with the equivalent bearers on the core side, the radio bearers form the so called EPS (Evolved Packet Service) Bearers. An EPS typically ties the UE to some internet interface outside of the mobile network.

(25) FIG. 1 illustrates an example network in which the example embodiments may be applied. When a LTE UE, or wireless device 500, connects to a LTE network, according to 3GPP it will automatically establish a default EPS bearer towards a PDN Gateway (PGW), for example the bearers 2 in FIG. 1. This bearer will provide the always-on connectivity inherent to LTE. This always-on connectivity provides the IP-presence of LTE UEs.

(26) The LTE core network determines when to establish additional bearers aside the default one. The core network will do so in cooperation with the signaling entities on the UE.

(27) According to some of the example embodiments, the UE installs a CCN API providing CCN sockets or similar to the UE applications making use of CCN for various purposes, e.g. content distribution, Internet-of-Things, and software upgrades from the network side to devices of various kinds, e.g. cellular phones, meters, actuators etc.

(28) Based on some default or other mechanism, which could be triggered through policy and/or subscription and availability (e.g. the 3GPP HLR/HSS, Home Location register/Home Subscription Service), the network will recognize the UE as CCN-capable. It will then signal to the UE that a new dedicated bearer, for example bearer 1, be established alongside the default bearer, for example bearer 2. The idea is to use this new bearer to carry CCN traffic natively over the radio interface. The network, in this case the MME, will of course know that that particular radio bearer shall be terminated on the RBS and connected to some adjacent CCN network, i.e. similar to what is used today for local break-out of LTE bearers (e.g. LIPA, 3GPPs Local IP Access solution). Logically this CCN network is separate from the IP network used for regular 3GPP bearers. Contrary to LIPA however, the MME will typically just make sure that the radio bearer is terminated to a CCN network connected to the RBS, with no further actions from the MME to the CCN network beyond that.

(29) In case the APIs on the UE 500 prefer to use traditional IP sockets for CCN this shall not be excluded from the example embodiments. In this case, CCN will be carried over a dummy IP interface that is transported over the CCN bearer. On the RBS 401, this dummy IP address will be terminated and traffic treated as if CCN traffic had not used IP.

(30) In case the media device on the end-user side is connected via WiFi, the example embodiments presented herein still apply, as illustrated in FIG. 1. For example, a WiFi-only TV set will need to connect to a WiFi-LTE tethering device, which will act as a proxy to distribute the CCN media packets from LTE towards the local WiFi connection. By using tethering towards WiFi, the solution still secures an end-to-end control of CCN distributed media over LTE. Such example embodiments could make use of WiFi multicasting on the radio access side.

(31) In case devices (UEs) have caching capabilities, the solution shall allow for reuse of LTE eMBMS (enhanced Multicast Broadcast Multimedia Services) such that the CCN node serving the RBS may inject eMBMS packets towards the RAN and thus act in the role of MBMS GW. Nor shall any future bearers be excluded from the example embodiments presented herein, e.g. group data radio bearers.

(32) The CCN bearer established can be devised along several schemes: A dedicated bearer for uplink and downlink. A dedicated bearer for uplink but combined with a MBMS bearer downlink. In this scheme, CCN traffic from the UEs will relate a MBMS multicast channel in the downlink to the aforementioned uplink. This alternative is preferred in situations of heavy radio air interface load.

Working Example

(33) FIG. 2 illustrates a non-limiting working example of some of the example embodiments presented herein. In general, when UE1 and UE2 roam into the cell or are switched on in the cell, a default LTE EPS bearer (Evolved Packet Service) will be established automatically, e.g. over interface 1 for UE 1 and interface 2 for UE2. This bearer will carry standard LTE traffic, IP based. From the base station, those bearers will be tunneled into nodes of the 3GPP network and typically eventually end up in a Packet Data Network gateway (PGw) of the Evolved Packet Core that connects to the Internet. The above bearers will provide the terminals with always-on connectivity of the UEs During the process of bearer establishment, the MME/HSS in the EPC core will determine that UE1 and UE2 are ICN-capable, i.e. that they have the capabilities to use ICN protocols on the UE, e.g. to send an Interest Message for a content file or that have the capabilities to inject content into ICN At this point, the MME will cooperate (signal) with the UE1 and U2 to establish a separate bearer, to be used by ICN APIs on the UE side. This will be along standard 3GPP procedures for radio data bearer establishment. The base station will also know that those ICN bearers shall be terminated locally on the ICN bearer handling entity, so when these new bearers have been established the base station will create new ICN interfaces for UE1 and UE2, e.g., interfaces 1A and 2A respectively, on the ICN bearer handling entity residing inside the base station. The base station will then make sure to terminate radio interface protocols from UE1 and UE2 for those bearers and then forward whatever it receives from UE1 on the dark shaded bearer to i/f 1A and whatever it receives from UE2 on the dark shaded bearer on i/f 2A. Note that when UE1 connects to Base Station, then this will be registered in Forwarding Info (e.g. Prefix UE1; Interface 1A), so that an Interest from some other device in the ICN network can propagate towards UE1. If the UEs move to another cell, handover of standard 3GPP bearers will be according to well-known seamless mobility management procedures involving signaling between MME, base station and UE. As for the ICN bearers, they don't need seamless mobility. Instead, the procedure of above can be repeated. When a UE moves out of cell coverage and into a new cell, Forwarding Info in the ICN bearer handling will be deleted from the, unless the Base Station is instructed to keep specific data in its cache, even though the source has moved. For example, if UE1 has published a picture via interface 1A, and then this picture is cached in the base station's Content Cache, then the strategy might be chosen in this network to keep this data in the Base Station's cache for an extended time, even though the UE itself has moved.

(34) FIG. 2 provides an illustrative example of the bearer connections between two wireless devices 500A and 500B and a base station 401. In the illustrated example, each wireless device 500A and 500B comprises two bearers. The first wireless device 500A comprises an ICN dedicated bearer 1A and a PDN dedicated bearer 1B. The second wireless device 500B similarly comprises an ICN dedicated bearer 2A and a PDN dedicated bearer 2B.

(35) According to some of the example embodiments, an API associated with the wireless device may determine that the wireless devices requests content which is ICN compatible. Based on this determination, the wireless device 501A may send a request for content to the base station 401 on the ICN dedicated bearer 1A. The request for content will comprise the name of the content the wireless device 501A wishes to receive.

(36) Once the base station 401 receives the request for content, the base station 401 will recognize the request is intended for an ICN based network since the request was received on the ICN dedicated bearer 1A. According to some of the example embodiments, upon receiving the request for content, the base station 401 may first search a content cache to see if the requested content is cached within the base station. According to some of the example embodiments, the content may be indexed according to the name associated with the content. If the base station 401 determines that the requested content is cached, the base station may send the requested content to the wireless device 501A via the ICN dedicated bearer 1A. Thus, the wireless device 500A may receive the requested content without any messaging to the ICN based network, thereby reducing the amount of signaling resources used.

(37) If it is determined that the requested content is not cached within the base station 401, the base station may register the requested content within a pending table. The pending table may keep track of all the different ICN based content requests that the base station 401 receives from the various wireless devices the base station serves. If it is determined that a certain content is requested often, for example, if the number of requests surpasses a predetermined threshold value, the base station may decide to cache the content in the content cache thereby avoiding the need to communication with the ICN based network.

(38) According to some of the example embodiments, each base station 401 may have a dedicated interface 3 between itself and the ICN based network, as illustrated in FIG. 1. It should be appreciated that in FIG. 1, the interface 3 is used by all wireless devise connected via an ICN bearer to the base station 401. Thus, there need not be a dedicated ICN based network interface per wireless device.

(39) In FIG. 2, the interface between the base station 401 and the ICN based network are interfaces 1C and 2C, in this case there are two interfaces. Thus, in the forwarding table, the base station 401 may take note of which content it is expected to receive and on which interface it is expected to receive it on. For example, if wireless device 500A requests content named Video 1, assuming that this content is not already cached on the base station, this interest in Video 1 will first be registered in the Pending Table. The prefix of the forwarding table may be Video 1 and the interface may be listed as 1A. The base station will propagate the interest in Video 1 to that interface. Thus, once the base station receives this data on interface 3A or 3B, the base station will know, by looking into the Pending table, that the data shall forwarded to the wireless device 500A on the dedicated ICN bearer 1A.

(40) It should be appreciated that during the operations described above, the base station may also be configured to handle communications for the wireless device 500A via the PDN based bearer 1B in parallel. Furthermore, it should be appreciated that the base station 401 may also simultaneously be configured to handle any form for communications, ICN based or IP based, from any number of other wireless devices, for example, wireless device 500B. The example embodiments provide a means for using ICN bearers in parallel with standard Packet Data Network (PDN) bearers.

(41) Thus, in summary, the example embodiments described herein may be used to: Use 3GPP bearer control to terminate/originate data radio bearers (DRBs), from/to a UE, onto a ICN/CCN enabled network that operates in parallel to the existing 3GPP end-to-end network encompassing the normative end-to-end EPS bearers. Also including the situation where UEs are preprogrammed to establish an ICN/CCN bearer by default whenever they have this option. Enable the emulation of the MBMS GW role on the point where the ICN/CCN traffic is sent/received to/from the UEs. Using mobility management facilities of 3GPP systems to provide better support for publisher mobility of ICN/CCN nodes. Enriching capillary (e.g. WiFi, Bluetooth, ZigBee etc)-to-3GPP tethering devices such that they can cache content (e.g. IoT or media) locally for distribution towards non-3GPP devices, according to the bearer mechanisms of this invention. Controlling the UE from the network so that CCN bearers are established, or content is distributed over an IP enabled bearer (new or existing). Applying the above for any version of ICN, NDN (Named Data Networking) etc. Using System Information Blocks (SIB) or similar to inform about the ICN/CCN bearers. Provide mechanisms on the UE (modem level or OS level or application level) in support of bearer selection depending on radio, core etc. e.g. where one application on a UE is instructed to switch socket interface from TCP/IP to ICN/CCN or vice versa, or where this switch is performed transparently to application and sockets, e.g. inside the modem Use 3GPP traffic flow templates and related constructs to identify which traffic is to be carried over the ICN/CCN bearer(s). Allow different ICN/CCN bearers to be used over different ICN/CCN logical domains, e.g. for roaming users. Adapt the radio scheduler on the modems (UE and/or RBS) to adapt to ICN/CCN characteristics, e.g. in how resources are scheduled. Use carrier aggregation (LTE, WCDMA, GSM, LTE unlicensed, WiFi, 5G etc) for the purpose of ICN/CCN bearers. Treating other types of radio bearer mechanisms the same way as in applicable claims above, e.g. for spurious machine-type communication from wireless devices using GSM SMS to publish IoT (Internet of Things) data into the ICN/CCN network. Introducing ICN/CCN all the way to 3GPP UEs by means of similar procedures as 3GPP feature rollout, e.g. on a few RBS, in a region, across many countries for a multinational operator etc. Applying the above for indoor usage or any other heterogeneous (mix of small cell, large cells) or homogeneous network. Equipping RBSs with ICN/CCN capabilities that terminate and originate ICN/CCN traffic. Using the above principles also in cases where a virtual RAN or similar construct is employed, e.g. when the RBS's RAN is split into a lower layer part (e.g. PHY, MAC, RLS) and a higher level part (e.g. PDCP, RRC) including where IP bearer PDCPs are located elsewhere compared to ICN/CCN bearer PDCPs or equivalent. Combining this invention with the use of CPRI or similar, e.g. in the case where CPRI or equivalent packets/frames of one antenna-carrier flow is switched to an ICN/CCN node. The use of the above methods in situations where ICN/CCN is carried over one frequency band or equivalent and where other traffic (e.g. IP) is carried over a different band.
Example Node Configurations

(42) FIG. 3 illustrates an example node configuration of a base station 401. The base station 401 may perform some of the example embodiments described herein. The base station 401 may comprise radio circuitry, a communication port or a receiver 410A and transmitter 410B that may be configured to receive and/or transmit communication data, instructions, messages and/or any information related to ICN and PDN bearer based communications. It should be appreciated that the radio circuitry, a communication port or a receiver 410A and transmitter 410B may be comprised as any number of transceiving, receiving, and/or transmitting units, modules or circuitry. It should further be appreciated that the radio circuitry, a communication port or a receiver 410A and transmitter 410B may be in the form of any input or output communications port known in the art. The radio circuitry, a communication port or a receiver 410A and transmitter 410B may comprise RF circuitry and baseband processing circuitry (not shown).

(43) The base station 401 may also comprise a processing module, unit or circuitry 420 which may be configured for ICN based communications with radio bearers as described herein. The processing circuitry 420 may be any suitable type of computation unit, for example, a microprocessor, digital signal processor (DSP), field programmable gate array (FPGA), or application specific integrated circuit (ASIC), or any other form of circuitry.

(44) The base station 401 may further comprise a memory unit or circuitry 430 which may be any suitable type of computer readable memory and may be of volatile and/or non-volatile type. The memory 430 may be configured to store received, transmitted, and/or measured data, device parameters, communication priorities, any form of information and/or executable program instructions. The base station 401 may further comprise a network interface 440 that may be configured to interact with a PDN or IP based network as well as a ICN based network as described herein.

(45) FIG. 4 illustrates an example node configuration of a wireless device 500. The wireless device 500 may perform some of the example embodiments described herein. The wireless device 500 may comprise radio circuitry, a communication port or a receiver 510A and transmitter 510B that may be configured to receive and/or transmit communication data, instructions, messages and/or any information related to ICN and PDN bearer based communications. It should be appreciated that the radio circuitry, a communication port or a receiver 510A and transmitter 510B may be comprised as any number of transceiving, receiving, and/or transmitting units, modules or circuitry. It should further be appreciated that the radio circuitry, a communication port or a receiver 510A and transmitter 510B may be in the form of any input or output communications port known in the art. The radio circuitry, a communication port or a receiver 510A and transmitter 510B may comprise RF circuitry and baseband processing circuitry (not shown).

(46) The wireless device 500 may also comprise a processing module, unit or circuitry 503 which may be configured for ICN based communications with radio bearers as described herein. The processing circuitry 503 may be any suitable type of computation unit, for example, a microprocessor, digital signal processor (DSP), field programmable gate array (FPGA), or application specific integrated circuit (ASIC), or any other form of circuitry.

(47) The wireless device 500 may further comprise a memory unit or circuitry 505 which may be any suitable type of computer readable memory and may be of volatile and/or non-volatile type. The memory 505 may be configured to store received, transmitted, and/or measured data, device parameters, communication priorities, any form information and/or executable program instructions.

(48) Example Node Operations

(49) FIG. 5A is a flow diagram depicting example operations which may be taken by the base station 401 as described herein for ICN based communications. It should also be appreciated that FIG. 5A comprises some operations which are illustrated with a solid border and some operations which are illustrated with a dashed border. The operations which are comprised in a solid border are operations which are comprised in the broadest example embodiment. The operations which are comprised in a dashed border are example embodiments which may be comprised in, or a part of, or are further operations which may be taken in addition to the operations of the boarder example embodiments. It should be appreciated that these operations need not be performed in order. Furthermore, it should be appreciated that not all of the operations need to be performed. The example operations may be performed in any order and in any combination.

(50) FIG. 5B illustrates modules which may carry out at least some of the example operations illustrated in FIG. 5A.

(51) Example Operation 10

(52) According to some of the example embodiments, the base station may be configured to receive 10 an indication that the wireless device is compatible for ICN based communications. The receiver 410A may be configured to receive the indication that the wireless device is compatible for ICN based communications.

(53) According to some of the example embodiments, the receiving 10 may occur during an attach procedure when the wireless device connects to the network the base station is serving. The indication, which the base station receives, may be sent by a mobility management node, for example, a MME, SGSN, or a S4-SGSN. The mobility management node may determine the need for th indication based on any policies or subscription data related to the wireless device. Such policy or subscription data may be obtained from the HSS or HLR or any similar nodes such as a policy manager.

(54) Example Operation 12

(55) According to some of the example embodiments, upon receiving 10 the indication, the base station may create 12 the ICN dedicated bearer. The processing circuitry 420 is configured to create the ICN dedicated bearer in response to the indication.

(56) Operation 14

(57) The base station is configured to receive, from a wireless device, a request for content on an ICN dedicated radio bearer. The receiver 410A is configured to receive, from the wireless device, the request for the content on the ICN dedicated bearer. The receiving module 14A is further configured to perform the receiving 14.

(58) It should appreciated that the base station is comprised in an IP based wireless communications network. For example, a LTE, GERAN, UTRAN, E-UTRAN, Wi-Fi based system. This IP based wireless communications network works in parallel to the ICN based communications, so that host based protocols use IP based communications and content centric communications use ICN based communications. The IP and ICN based communications are logically separate but may be implemented on common resources. Radio bearers carrying ICN traffic are terminated on ICN and need not be processed by the IP base communications.

(59) According to some of the example embodiments, the content is multimedia data. It should be appreciated that multimedia data may comprise any form of or a combination of text, audio, still images, animation, video, or interactivity content forms. Multimedia data may also comprise any data related to the Internet of Things and/or any software upgrades. It may also comprise emulation of host-based communications emulated over ICN.

(60) According to some of the example embodiments, the wireless device is a M2M device. In such example embodiments, the content may be M2M related data. According to some of the example embodiments, M2M related data may comprise measurements obtained by the M2M device. In such example embodiments, the base station may cache such data. Thus, when the ICN based networks sends a requests for such data, the base station may send the information to the ICN based network rather than attempting to send the request to the M2M device. As the M2M device typically engages in long sleep cycles where it is not reachable by the network, the ability of the base station to cache such information is advantageous as it reduces unnecessary signaling.

(61) Example Operation 16

(62) According to some of the example embodiments, the base station may be further configured to register 16, within the base station itself, the request for content with respect to the wireless device. The processing circuitry 420 is configured to register, within the base station itself, the request for content with respect to the wireless device.

(63) According to some of the example embodiments, the base station may be configured to provide a book keeping of the various ICN content based requests it receives. By doing so, the base station may decide to cache content which is frequently requested.

(64) Furthermore, in some instances, the wireless device may wish to send content to the ICN based network, therefore the request may comprise data to be transmitted. In such instances, the base station may transmit this data or cache this data and send the cached data to the ICN based network once the base station receives a request from the ICN based network for such data.

(65) Operation 18

(66) The base station is further configured to determine 18 if the content in the request is in a cache associated to or in the base station. The processing circuitry 420 is configured to determine if the content in the request is in a cache associated to or in the base station. The determining module 18A is further configured to perform the determining.

(67) Operation 20

(68) Based on the determining 18, if the content is cached, the base station is further configured to send 20, to the wireless device, the content. The transmitter 410B is configured to send, to the wireless device, the content if the content is cached. The sending module 20A is further configured to perform the sending 20.

(69) Operation 22

(70) Based on the determining 18, if the content is not cached, the base station is further configured to send 22, to an ICN based network, the request on an interface dedicated for ICN communications. The transmitter 410B is configured to send, to an ICN based network, the request on an interface dedicated for ICN communications if the content is not cached. The sending module 22A is further configured to perform the sending 22.

(71) According to some of the example embodiments, the interface dedicated for ICN communications is further dedicated for communications to and from the wireless device.

(72) Example Operation 24

(73) According to some of the example embodiments, the base station is further configured to receive 24, from the ICN based network, a content response. The receiver 410A is configured to receive, from the ICN based network, the content response.

(74) According to some of the example embodiments, the content request and response are transmitted and received on a first frequency and general IP communications are transmitted and received on a second frequency, wherein the first frequency is different than the second frequency.

(75) If information has been requested in the content request, the content response may comprise the requested information. If the content request comprised a request to send information to the ICN based network, the content response may comprise a confirmation that such information was transmitted.

(76) Example Operation 26

(77) Upon receiving 24 the content response, the base station is further configured to transmit 26, to the wireless device, the content response on the ICN dedicated radio bearer. The transmitter 410B is configured to transmit, to the wireless device, the content response on the ICN dedicated radio bearer.

(78) According to some of the example embodiments, the content request and response are transmitted and received on a first frequency and general IP communications are transmitted and received on a second frequency, wherein the first frequency is different than the second frequency.

(79) If information has been requested in the content request, the content response may comprise the requested information. If the content request comprised a request to send information to the ICN based network, the content response may comprise a confirmation that such information was transmitted.

(80) Example Operation 28

(81) Upon the receiving 24 and transmitting 26, the base station may be further configured to determine 28 a frequency in which the content has been requested. The processing circuitry 420 is configured to determine the frequency in which the content has been requested.

(82) According to some example embodiments, if the base station determines that the content which has been requested is often requested, the base station may choose to cache the content thereby reducing the amount of signaling required in order to supply the wireless device with the requested content. Specifically, by caching the content, the base station may eliminate the need of sending the request to the ICN based network in the future.

(83) Example Operation 30

(84) Upon determining 28 the frequency in which the content has been requested, the base station is further configured to cache 30 the content within the base station itself if the frequency is above a predetermined threshold. The processing circuitry 420 is configured to cache the content within the base station itself if the frequency is above a predetermined threshold.

(85) According to some example embodiments, if the base station determines that the content which has been requested is often requested, the base station may choose to cache the content thereby reducing the amount of signaling required in order to supply the wireless device with the requested content. Specifically, by caching the content, the base station may eliminate the need of sending the request to the ICN based network in the future.

(86) FIG. 6A is a flow diagram depicting example operations which may be taken by the wireless device 500 as described herein for ICN based communications. It should also be appreciated that FIG. 6A comprises some operations which are illustrated with a solid border and some operations which are illustrated with a dashed border. The operations which are comprised in a solid border are operations which are comprised in the broadest example embodiment. The operations which are comprised in a dashed border are example embodiments which may be comprised in, or a part of, or are further operations which may be taken in addition to the operations of the boarder example embodiments. It should be appreciated that these operations need not be performed in order. Furthermore, it should be appreciated that not all of the operations need to be performed. The example operations may be performed in any order and in any combination.

(87) FIG. 6B illustrates modules which may be used to perform at least some of the example operations illustrated in FIG. 6A.

(88) Operation 40

(89) The wireless device is configured to determine 40, via an API, a need for ICN compatible content. The processing circuitry 503 is configured to determine, via the API, the need for ICN compatible content. The determining module 40A is configured to perform the operation of determining 40.

(90) According to some of the example embodiments, the content is multimedia data. It should be appreciated that multimedia data may comprise any form of or a combination of text, audio, still images, animation, video, or interactivity content forms. Multimedia data may also comprise any data related to the Internet of Things and/or any software upgrades. It may also comprise any data related to the Internet of Things and/or any software upgrades. It may also comprise emulation of host-based communications emulated over ICN.

(91) According to some of the example embodiments, the wireless device is a M2M device and the content is M2M related data. According to some of the example embodiments, M2M related data may comprise measurements obtained by the M2M device. In such example embodiments, the base station may cache such data. Thus, when the ICN based networks sends a requests for such data, the base station may send the information to the ICN based network rather than attempting to send the request to the M2M device. As the M2M device typically engages in long sleep cycles where it is not reachable by the network, the ability of the base station to cache such information is advantageous as it reduces unnecessary signaling.

(92) Operation 42

(93) Upon the determining 40, the wireless device is further configured to send 42, to a base station, a request for content on an ICN dedicated radio bearer. The transmitter 501B is configured to send, to the base station, the request for content on the ICN dedicated radio bearer. The sending module 42A is configured to perform the operation of sending 42.

(94) It should appreciated that the base station is comprised in an IP based wireless communications network. For example, a LTE, GERAN, UTRAN, E-UTRAN, Wi-Fi based system. This IP based wireless communications network works in parallel to the ICN based communications, so that host based protocols use IP based communications and content centric communications use ICN based communications. The IP and ICN based communications are logically separate but can be implemented on common resources. Radio bearers carrying ICN traffic are terminated on ICN and need not be processed by the IP base communications.

(95) Example Operation 44

(96) According to some of the example embodiments, the wireless device may be further configured to receive 44, from the base station, a content response on the ICN dedicated radio bearer. The receiver 501A is configured to receive, from the base station, the content response on the ICN dedicated radio bearer.

(97) According to some of the example embodiments, the content request and response are transmitted and received on a first frequency and general IP communications are transmitted and received on a second frequency, wherein the first frequency is different than the second frequency.

(98) If information has been requested in the content request, the content response may comprise the requested information. If the content request comprised a request to send information to the ICN based network, the content response may comprise a confirmation that such information was transmitted.

(99) It should be noted that although terminology from 3GPP LTE has been used herein to explain the example embodiments, this should not be seen as limiting the scope of the example embodiments to only the aforementioned system. Other wireless systems, including WCDMA, WiMax, UMB, WiFi and GSM, may also benefit from the example embodiments disclosed herein.

(100) The description of the example embodiments provided herein have been presented for purposes of illustration. The description is not intended to be exhaustive or to limit example embodiments to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of various alternatives to the provided embodiments. The examples discussed herein were chosen and described in order to explain the principles and the nature of various example embodiments and its practical application to enable one skilled in the art to utilize the example embodiments in various manners and with various modifications as are suited to the particular use contemplated. The features of the embodiments described herein may be combined in all possible combinations of methods, apparatus, modules, systems, and computer program products. It should be appreciated that the example embodiments presented herein may be practiced in any combination with each other.

(101) It should be noted that the word comprising does not necessarily exclude the presence of other elements or steps than those listed and the words a or an preceding an element do not exclude the presence of a plurality of such elements. It should further be noted that any reference signs do not limit the scope of the claims, that the example embodiments may be implemented at least in part by means of both hardware and software, and that several means, units or devices may be represented by the same item of hardware.

(102) Also note that terminology such as user equipment should be considered as non-limiting. A device or user equipment as the term is used herein, is to be broadly interpreted to include a radiotelephone having ability for Internet/intranet access, web browser, organizer, calendar, a camera (e.g., video and/or still image camera), a sound recorder (e.g., a microphone), and/or global positioning system (GPS) receiver; a personal communications system (PCS) user equipment that may combine a cellular radiotelephone with data processing; a personal digital assistant (PDA) that can include a radiotelephone or wireless communication system; a laptop; a camera (e.g., video and/or still image camera) having communication ability; and any other computation or communication device capable of transceiving, such as a personal computer, a home entertainment system, a television, etc. It should be appreciated that the term user equipment may also comprise any number of connected devices. Furthermore, it should be appreciated that the term user equipment shall be interpreted as defining any device which may have an internet or network access.

(103) The various example embodiments described herein are described in the general context of method steps or processes, which may be implemented in one aspect by a computer program product, embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by computers in networked environments. A computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), compact discs (CDs), digital versatile discs (DVD), etc. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

(104) In the drawings and specification, there have been disclosed exemplary embodiments. However, many variations and modifications can be made to these embodiments. Accordingly, although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation, the scope of the embodiments being defined by the following claims.