Contextualized information bus

1. A network element (NE) comprising:

a plurality of interfaces configured to communicatively couple to an information centric network (ICN), wherein each interface is configured to employ 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 from the interfaces based on the delivery metric; and

a transmitter coupled to the first interface and configured to transmit the data object.

2. The NE of claim 1 , further comprising a service sub-system coupled to the processor and 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.

3. The NE of claim 2 , wherein the processor is further configured to:

generate a link event notification when the event occurs; and

notify the service sub-system of the event.

4. The NE of claim 1 , further comprising a service sub-system coupled to the processor and configured to generate an action application programing interface (API) to request an action, wherein the action is at least one of data forwarding, data reception, interface selection, and mobility.

5. The NE of claim 4 , wherein the processor is further configured to perform the action.

6. The NE of claim 1 , 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 interfaces based on the updated delivery metric; and

deselect the first interface.

7. The NE of claim 6 , wherein the NE further comprises a second transmitter coupled to the second interface and configured to transmit a second data object associated with the data object identifier.

8. The NE of claim 1 , wherein the transmitter is further configured to further transmit the data object using mobile wireless transmission, wireless local area network transmission, or both mobile wireless transmission and wireless local area network transmission.

9. A method comprising:

communicatively coupling, by a plurality of interfaces, to an information centric network (ICN);

employing, by each interface, a different transmission mechanism;

generating a mapping of a data object identifier to a plurality of data type attributes of a data object;

computing a delivery metric for each interface based on the data type attributes;

selecting a first interface from the interfaces based on the delivery metric; and

transmitting the data object.

10. The method of claim 9 , further comprising generating, by a service sub-system, 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.

11. The method of claim 10 , further comprising:

generating a link event notification when the event occurs; and

notifying the service sub-system of the event.

12. The method of claim 9 , further comprising generating an action application programing interface (API) to request an action, wherein the action is at least one of data forwarding, data reception, interface selection, and mobility.

13. The method of claim 9 , further comprising:

computing an updated delivery metric for each interface based on the data type attributes;

selecting a second interface from the interfaces based on the updated delivery metric; and

deselecting the first interface.

14. A computer program product comprising instructions for storage on a non-transitory medium that, when executed by a processor, cause a network element (NE) to:

communicatively couple, via each of a plurality of interfaces employing a different transmission mechanism, to an information centric network (ICN);

store a mapping of a data object identifier to a plurality of data type attributes of a data object;

compute a delivery metric for each interface based on the data type attributes;

select a first interface from the interfaces based on the delivery metric; and

transmit the data object.

15. The computer program product of claim 14 , wherein the instructions further cause the NE 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.

16. The computer program product of claim 15 , wherein the instructions further cause the NE to:

generate a link event notification when the event occurs; and

notify a service sub-system of the event.

17. The computer program product of claim 14 , wherein the instructions further cause the NE to generate an action application programing interface (API) to request an action, wherein the action is at least one of data forwarding, data reception, interface selection, and mobility.

18. The computer program product of claim 17 , wherein the instructions further cause the NE to perform the action.

19. The computer program product of claim 14 , wherein the instructions further cause the NE to:

compute an updated delivery metric for each interface based on the data type attributes;

select a second interface from the interfaces based on the updated delivery metric;

deselect the first interface; and

transmit a second data object associated with the data object identifier.

20. The computer program product of claim 14 , wherein the instructions further cause the NE to further transmit the data object using mobile wireless transmission, wireless local area network transmission, or both mobile wireless transmission and wireless local area network transmission.