< draft-geng-teas-network-slice-mapping-01.txt		draft-geng-teas-network-slice-mapping-02.txt >
	Network Working Group X. Geng		Network Working Group X. Geng
	Internet-Draft J. Dong		Internet-Draft J. Dong
	Intended status: Informational Huawei Technologies		Intended status: Informational Huawei Technologies
	Expires: October 25, 2020 R. Pang		Expires: January 14, 2021 R. Pang
	China Unicom		China Unicom
	L. Han		L. Han
	China Mobile		China Mobile
	T. Niwa		T. Niwa
	KDDI		KDDI
	J. Jin		J. Jin
	LG U+		LG U+
	C. Liu		C. Liu
	China Unicom		China Unicom
	N. Nageshar		N. Nageshar
	Individual		Individual
	April 23, 2020		July 13, 2020
	5G End-to-end Network Slice Mapping from the view of Transport Network		5G End-to-end Network Slice Mapping from the view of Transport Network
	draft-geng-teas-network-slice-mapping-01		draft-geng-teas-network-slice-mapping-02
	Abstract		Abstract
	Network Slicing is one of the core featrures in 5G. End-to-end		Network Slicing is one of the core featrures in 5G. End-to-end
	network slice consists of 3 major types of network segments: Access		network slice consists of 3 major types of network segments: Access
	Network (AN), Mobile Core Network (CN) and Transport Network (TN).		Network (AN), Mobile Core Network (CN) and Transport Network (TN).
	This draft describes the procedure of mapping relationship between 5G		This draft describes the procedure of mapping relationship between 5G
	end-to-end network slice and transport network slice defined in IETF.		end-to-end network slice and transport network slice defined in IETF.
	This draft also intends to expose some gaps in the existing network		This draft also intends to expose some gaps in the existing network
	management plane and data plane to support inter-domain network slice		management plane and data plane to support inter-domain network slice
	skipping to change at page 2, line 12 ¶		skipping to change at page 2, line 12 ¶
	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 October 25, 2020.		This Internet-Draft will expire on January 14, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 40 ¶		skipping to change at page 2, line 40 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Network Slice Mapping Structure . . . . . . . . . . . . . . . 4		3. Network Slice Mapping Structure . . . . . . . . . . . . . . . 4
	3.1. Requirements Profile . . . . . . . . . . . . . . . . . . 5		3.1. Requirements Profile . . . . . . . . . . . . . . . . . . 5
	3.2. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 6		3.2. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 6
	3.3. Relevant functions . . . . . . . . . . . . . . . . . . . 6		3.3. Relevant functions . . . . . . . . . . . . . . . . . . . 6
	4. Network Slice Mapping Procedure . . . . . . . . . . . . . . . 7		4. Network Slice Mapping Procedure . . . . . . . . . . . . . . . 7
	4.1. Network Slice Mapping in Management Plane . . . . . . . . 8		4.1. Network Slice Mapping in Management Plane . . . . . . . . 8
	4.2. Network Slice Mapping in Control Plane . . . . . . . . . 9		4.2. Network Slice Mapping in Control Plane . . . . . . . . . 9
	4.3. Network Slice Mapping in data plane . . . . . . . . . . . 9		4.3. Network Slice Mapping in data plane . . . . . . . . . . . 10
	4.3.1. Data Plane Mapping Considerations . . . . . . . . . . 10		4.3.1. Data Plane Mapping Considerations . . . . . . . . . . 10
	4.3.2. Data Plane Mapping Design . . . . . . . . . . . . . . 10		4.3.2. Data Plane Mapping Design . . . . . . . . . . . . . . 10
	5. Network Slice Mapping Summary . . . . . . . . . . . . . . . . 14		5. Network Slice Mapping Summary . . . . . . . . . . . . . . . . 15
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 15		7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
	9. Normative References . . . . . . . . . . . . . . . . . . . . 15		9. Normative References . . . . . . . . . . . . . . . . . . . . 15
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
	1. Introduction		1. Introduction
	Driven by the new applications of 5G, the concept of network slicing		Driven by the new applications of 5G, the concept of network slicing
	is defined to provide a logical network with specific capabilities		is defined to provide a logical network with specific capabilities
	skipping to change at page 8, line 7 ¶		skipping to change at page 8, line 7 ¶
	the end-to-end network slice instance , which is defined in Service		the end-to-end network slice instance , which is defined in Service
	Profile([TS28541] section 6.3.3).		Profile([TS28541] section 6.3.3).
	3. NSMF derives transport network slice related requirements from		3. NSMF derives transport network slice related requirements from
	the Service profile, and maintains them in Transport Network Slice		the Service profile, and maintains them in Transport Network Slice
	Profile, So as to CN Slice Profile and AN Slice Profile, in order to		Profile, So as to CN Slice Profile and AN Slice Profile, in order to
	decide on the constituent NSSIs(including AN NSSI, CN NSSI and TN		decide on the constituent NSSIs(including AN NSSI, CN NSSI and TN
	NSSI) of the NSI, based on the service profile and the endpoint		NSSI) of the NSI, based on the service profile and the endpoint
	information(AN/CN edge nodes).		information(AN/CN edge nodes).
	4. NSMF sends the Transport Network Slice Profile to TN NSSMF for TN		4. NSMF sends the Transport Network Slice Profile, endpoint
			information, along with other TS NBI attributes to TN NSSMF for TN
	NSSI allocation.		NSSI allocation.
	5. TN NSSMF allocates TN NSSI which could satisfy the requirement of		5. TN NSSMF allocates TN NSSI which could satisfy the requirement of
	Transport Network Slice Profile between the specified endpoints (AN/		Transport Network Slice Profile between the specified endpoints (AN/
	CN edge nodes) and sends the TN NSSI Identifier to NSMF.		CN edge nodes) and sends the TN NSSI Identifier to NSMF.
	6. NSMF acquires the mapping relationship between NSI and TN NSSI.		6. NSMF acquires the mapping relationship between NSI and TN NSSI.
	7. NSMF matains the mapping relationship between NSI and S-NSSAI and		7. NSMF matains the mapping relationship between NSI and S-NSSAI and
	the mapping relationship between TN NSSI and TNSII, which could be		the mapping relationship between TN NSSI and TNSII, which could be
	skipping to change at page 9, line 32 ¶		skipping to change at page 9, line 33 ¶
	attributes.		attributes.
	TN NSSI resource reservation should be considered to avoid over		TN NSSI resource reservation should be considered to avoid over
	allocation from multiple requests from NSMF (but the detailed		allocation from multiple requests from NSMF (but the detailed
	mechanism should be out of scope in the draft)		mechanism should be out of scope in the draft)
	TN NSSMF sends the selected or newly allocated TN NSSI identifier to		TN NSSMF sends the selected or newly allocated TN NSSI identifier to
	NSMF. The mapping relationship between NSI identifier and TN NSSI		NSMF. The mapping relationship between NSI identifier and TN NSSI
	identifier is maintained in both NSMF and TN NSSMF.		identifier is maintained in both NSMF and TN NSSMF.
			YANG data model for the Transport Slice NBI, which could be used by a
			higher level system which is the Transport slice consumer of a
			Transport Slice Controller (TSC) to request, configure, and manage
			the components of a transport slices, is defined in
			[I-D.wd-teas-transport-slice-yang].
	4.2. Network Slice Mapping in Control Plane		4.2. Network Slice Mapping in Control Plane
	There is no explicit interaction between transport network and AN/CN		There is no explicit interaction between transport network and AN/CN
	in the control plane, but the S-NSSAI defined in [TS23501] is treated		in the control plane, but the S-NSSAI defined in [TS23501] is treated
	as the end-to-end network slice identifier in the control plane of AN		as the end-to-end network slice identifier in the control plane of AN
	and CN, which is used in UE registration and PDU session setup. In		and CN, which is used in UE registration and PDU session setup. In
	this draft, we assume that there is mapping relationship between		this draft, we assume that there is mapping relationship between
	S-NSSAI and NSI in the management plane, thus it could be mapped to a		S-NSSAI and NSI in the management plane, thus it could be mapped to a
	transport network slice .		transport network slice .
	skipping to change at page 15, line 48 ¶		skipping to change at page 16, line 11 ¶
	[GST] "Generic Network Slice Template",		[GST] "Generic Network Slice Template",
	<https://www.gsma.com/newsroom/all-documents/generic-		<https://www.gsma.com/newsroom/all-documents/generic-
	network-slice-template-v2-0/>.		network-slice-template-v2-0/>.
	[I-D.contreras-teas-slice-nbi]		[I-D.contreras-teas-slice-nbi]
	Contreras, L., Homma, S., and J. Ordonez-Lucena,		Contreras, L., Homma, S., and J. Ordonez-Lucena,
	"Considerations for defining a Transport Slice NBI",		"Considerations for defining a Transport Slice NBI",
	draft-contreras-teas-slice-nbi-01 (work in progress),		draft-contreras-teas-slice-nbi-01 (work in progress),
	March 2020.		March 2020.
			[I-D.wd-teas-transport-slice-yang]
			Bo, W., Dhody, D., Han, L., and R. Rokui, "A Yang Data
			Model for Transport Slice NBI", draft-wd-teas-transport-
			slice-yang-02 (work in progress), July 2020.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[TS23501] "3GPP TS23.501",		[TS23501] "3GPP TS23.501",
	<https://portal.3gpp.org/desktopmodules/Specifications/		<https://portal.3gpp.org/desktopmodules/Specifications/
	SpecificationDetails.aspx?specificationId=3144>.		SpecificationDetails.aspx?specificationId=3144>.
	[TS28530] "3GPP TS28.530",		[TS28530] "3GPP TS28.530",
End of changes. 9 change blocks.
	7 lines changed or deleted		19 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/