< draft-irtf-icnrg-icn-lte-4g-11.txt		draft-irtf-icnrg-icn-lte-4g-12.txt >
	ICN Research Group Prakash Suthar		ICN Research Group Prakash Suthar
	Internet-Draft Google Inc.		Internet-Draft Google Inc.
	Intended status: Informational Milan Stolic		Intended status: Experimental Milan Stolic
	Expires: 1 August 2022 Anil Jangam, Ed.		Expires: 22 September 2022 Anil Jangam, Ed.
	Cisco Systems Inc.		Cisco Systems Inc.
	Dirk Trossen		Dirk Trossen
	Huawei Technologies		Huawei Technologies
	28 January 2022		Ravi Ravindran
			F5 Networks
			21 March 2022
	Experimental Scenarios of ICN Integration in 4G Mobile Networks		Experimental Scenarios of ICN Integration in 4G Mobile Networks
	draft-irtf-icnrg-icn-lte-4g-11		draft-irtf-icnrg-icn-lte-4g-12
	Abstract		Abstract
	4G mobile network uses IP-based transport for the control plane to		4G mobile network uses IP-based transport for the control plane to
	establish the data session at the user plane for the actual data		establish the data session at the user plane for the actual data
	delivery. In the existing architecture, IP-based unicast is used for		delivery. In the existing architecture, IP-based unicast is used for
	the delivery of multimedia content to a mobile terminal, where each		the delivery of multimedia content to a mobile terminal, where each
	user is receiving a separate stream from the server. From a		user is receiving a separate stream from the server. From a
	bandwidth and routing perspective, this approach is inefficient.		bandwidth and routing perspective, this approach is inefficient.
	Evolved multimedia broadcast and multicast service (eMBMS) provides		Evolved multimedia broadcast and multicast service (eMBMS) provides
	skipping to change at page 2, line 10 ¶		skipping to change at page 2, line 10 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on 1 August 2022.		This Internet-Draft will expire on 22 September 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2022 IETF Trust and the persons identified as the		Copyright (c) 2022 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 26, line 24 ¶		skipping to change at page 26, line 24 ¶
	1. It decides the forwarding strategy for a user data request coming		1. It decides the forwarding strategy for a user data request coming
	from mobile terminal. The strategy can decide based on		from mobile terminal. The strategy can decide based on
	preference indicated by the application, such as congestion,		preference indicated by the application, such as congestion,
	cost, QoS, and so on.		cost, QoS, and so on.
	2. eNodeB to provide open Application Programming Interface (API) to		2. eNodeB to provide open Application Programming Interface (API) to
	external management systems, to provide capability to eNodeB to		external management systems, to provide capability to eNodeB to
	program the forwarding strategies.		program the forwarding strategies.
	+---------------+ |		+---------------+ |
	| MT request | | ICN +---------+		| MT request | | ICN +---------+
	+---> | content using |--+--- transport -->| |		+---->| content using |--+--- transport -->| |
	| |ICN protocol | | | |		| |ICN protocol | | | |
	| +---------------+ | | |		| +---------------+ | | |
	| | | |		| | | |
	| +---------------+ | | |		| +---------------+ | | |
	+-+ | | MT request | | IP |To mobile|		+-+ | | MT request | | IP |To mobile|
	| |---+---> | content using |--+--- transport -->| GW |		| |-+---->| content using |--+--- transport -->| GW |
	+-+ | | IP protocol | | |(SGW,PGW)|		+-+ | | IP protocol | | |(SGW,PGW)|
	MT | +---------------+ | | |		MT | +---------------+ | | |
	| | | |		| | | |
	| +---------------+ | | |		| +---------------+ | | |
	| | MT request | | Dual stack | |		| | MT request | | Dual stack | |
	+---> | content using |--+--- IP+ICN -->| |		+---->| content using |--+--- IP+ICN -->| |
	|IP/ICN protocol| | transport +---------+		|IP/ICN protocol| | transport +---------+
	+---------------+ |		+---------------+ |
	eNodeB S1u		eNodeB S1u
	Figure 8: Integration of Native ICN in eNodeB		Figure 8: Integration of Native ICN in eNodeB
	3. eNodeB can be upgraded to support three different types of		3. eNodeB can be upgraded to support three different types of
	transport: IP, ICN, and dual transport IP+ICN towards mobile		transport: IP, ICN, and dual transport IP+ICN towards mobile
	gateways, as depicted in Figure 8. It is also proposed to deploy		gateways, as depicted in Figure 8. It is also proposed to deploy
	IP and/or ICN forwarding capabilities into eNodeB, for efficient		IP and/or ICN forwarding capabilities into eNodeB, for efficient
	transfer of data between eNodeB and mobile gateways. Following		transfer of data between eNodeB and mobile gateways. Following
	are choices for forwarding a data request towards mobile		are choices for forwarding a data request towards mobile
	gateways:		gateways:
	skipping to change at page 36, line 21 ¶		skipping to change at page 36, line 21 ¶
	the principles by implementing prototype and/or proof of concept in		the principles by implementing prototype and/or proof of concept in
	the lab and in the production environment.		the lab and in the production environment.
	9. Acknowledgements		9. Acknowledgements
	We thank all contributors, reviewers, and the chairs for the valuable		We thank all contributors, reviewers, and the chairs for the valuable
	time in providing comments and feedback that helped improve this		time in providing comments and feedback that helped improve this
	draft. We specially want to mention the following members of the		draft. We specially want to mention the following members of the
	IRTF Information-Centric Networking Research Group (ICNRG), listed in		IRTF Information-Centric Networking Research Group (ICNRG), listed in
	alphabetical order: Kashif Islam, Thomas Jagodits, Luca Muscariello,		alphabetical order: Kashif Islam, Thomas Jagodits, Luca Muscariello,
	David R. Oran, Akbar Rahman, Ravishankar Ravindran, Martin J. Reed,		David R. Oran, Akbar Rahman, Martin J. Reed, Thomas C. Schmidt,
	Thomas C. Schmidt, and Randy Zhang.		and Randy Zhang.
	The IRSG review was provided by Colin Perkins.		The IRSG review was provided by Colin Perkins.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[TS24.008] 3GPP, "Mobile radio interface Layer 3 specification; Core		[TS24.008] 3GPP, "Mobile radio interface Layer 3 specification; Core
	network protocols; Stage 3", 3GPP TS 24.008 3.20.0, 15		network protocols; Stage 3", 3GPP TS 24.008 3.20.0, 15
	December 2005,		December 2005,
	skipping to change at page 42, line 29 ¶		skipping to change at page 42, line 29 ¶
	[TS33.320] 3GPP, "Security of Home Node B (HNB) / Home evolved Node B		[TS33.320] 3GPP, "Security of Home Node B (HNB) / Home evolved Node B
	(HeNB)", 3GPP TS 33.320 10.5.0, 29 June 2012,		(HeNB)", 3GPP TS 33.320 10.5.0, 29 June 2012,
	<http://www.3gpp.org/ftp/Specs/html-info/33320.htm>.		<http://www.3gpp.org/ftp/Specs/html-info/33320.htm>.
	Authors' Addresses		Authors' Addresses
	Prakash Suthar		Prakash Suthar
	Google Inc.		Google Inc.
	Mountain View, California 94043		Mountain View, California 94043
	United States of America		United States of America
	Email: psuthar@google.com		Email: psuthar@google.com
	Milan Stolic		Milan Stolic
	Cisco Systems Inc.		Cisco Systems Inc.
	Naperville, Illinois 60540		Naperville, Illinois 60540
	United States of America		United States of America
	Email: mistolic@cisco.com		Email: mistolic@cisco.com
	Anil Jangam (editor)		Anil Jangam (editor)
	Cisco Systems Inc.		Cisco Systems Inc.
	San Jose, California 95134		San Jose, California 95134
	United States of America		United States of America
	Email: anjangam@cisco.com		Email: anjangam@cisco.com
	Dirk Trossen		Dirk Trossen
	Huawei Technologies		Huawei Technologies
	Riesstrasse 25		Riesstrasse 25
	80992 Munich		80992 Munich
	Germany		Germany
	Email: dirk.trossen@huawei.com		Email: dirk.trossen@huawei.com
			Ravi Ravindran
			F5 Networks
			3545 North First Street
			San Jose, 95134
			United States of America
			Email: r.ravindran@f5.com
End of changes. 12 change blocks.
	29 lines changed or deleted		28 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/