1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.3323 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2016) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Future networks Requi
2、rements of soft network architecture for mobile Recommendation ITU-T Y.3323 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, app
3、lications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and
4、applications Y.1100Y.1199 Architecture, access, network capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y
5、.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and net
6、works in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y
7、.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure, connectivity and networks Y.4250Y.4399 Frameworks, architectures and protocols Y.4400Y.
8、4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.3323 (09/201
9、6) i Recommendation ITU-T Y.3323 Requirements of soft network architecture for mobile Summary Recommendation ITU-T Y.3323 defines the design principles and requirements of soft network architecture for mobile (SAME), i.e., flexible traffic steering, virtualization of SAME network functions, SAME net
10、work slice, and separation of control function and forwarding function. Its scenarios and problem statements are introduced in the appendices. SAME is a mobile packet core network, which bridges current legacy mobile network towards future networks. Though SAME does not aim to cover key requirements
11、 of IMT-2020 core network, these key requirements of SAME may be adopted in IMT-2020. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.3323 2016-09-29 13 11.1002/1000/13019 Keywords Control and forwarding separation, network function virtualization, network slice, soft netw
12、ork architecture for mobile, traffic steering. * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.3323 (09/2016) FOREWORD The
13、International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technica
14、l, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in
15、turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. N
16、OTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure
17、, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does n
18、ot suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning th
19、e evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, w
20、hich may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2017 All rights reserved. No part of this publication
21、 may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.3323 (09/2016) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 1 4 Abbreviations and acronyms 2 5 Co
22、nventions 2 6 Soft network architecture for mobile and its design principle 2 7 Requirements of SAME 3 Appendix I Scenarios of SAME 5 I.1 Flexible traffic steering . 5 I.2 Virtualization of network functions 6 I.3 SAME network slice for MVNO scenario . 7 I.4 Separation of control function and forwar
23、ding function 8 Appendix II Problem statement of current mobile packet core network 12 II.1 Problem in traffic steering 12 II.2 Problem caused by proprietary hardware . 12 II.3 Problem statement of the mobile packet core gateway 12 Appendix III Mapping between scenarios, problems, design principles
24、and requirements . 14 Bibliography. 15 Rec. ITU-T Y.3323 (09/2016) 1 Recommendation ITU-T Y.3323 Requirements of soft network architecture for mobile 1 Scope Soft network architecture for mobile (SAME) is a mobile packet core network, which bridges current legacy mobile networks toward future networ
25、ks. This Recommendation defines design principles of SAME, and its key requirements, i.e., flexible traffic steering, virtualization of SAME network functions, SAME network slice, and separation of control function and forwarding function. SAME scenarios and problem statements of current mobile pack
26、et core network are introduced in the appendices. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommend
27、ations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly pub
28、lished. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Y.2320 Recommendation ITU-T Y.2320 (2015), Requirements for virtualization of control network entities in next generation network evolution. ITU-T Y.3011
29、Recommendation ITU-T Y.3011 (2012), Framework of network virtualization for future networks. ITU-T Y.3012 Recommendation ITU-T Y.3012 (2014), Requirements of network virtualization for future networks. ITU-T Y.3015 Recommendation ITU-T Y.3015 (2016), Functional architecture of network virtualization
30、 for future networks. 3 Definitions 3.1 Terms defined elsewhere None. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 traffic steering: A technology which identifies and steers traffic to go through the related service function entities according to op
31、erators policy. NOTE 1 A service function entity is a traffic processing node that caches, transforms, inspects, filters, or otherwise manipulates traffic for purposes other than packet forwarding. Examples of service function entities are URL filter and video optimization. NOTE 2 Service function e
32、ntities are independent from one another, and can be added, removed and bypassed. 2 Rec. ITU-T Y.3323 (09/2016) 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: APN Access Point Name CAPEX Capital Expenditure GW Gateway HTTP Hypertext Transfer Protocol
33、MNO Mobile Network Operator MVNO Mobile Virtual Network Operator NFV Network Function Virtualization OPEX Operating Expenses QoE Quality of Experience QoS Quality of Service RAN Radio Access Network SAME Soft network Architecture for MobilE UE User Equipment URL Uniform Resource Locator VCN Virtuali
34、zation of Control Network entities VM Virtual Machine 5 Conventions In this Recommendation: The phrase “is required to“ indicates a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed. The phrase “is recommended“
35、 indicates a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be satisfied to claim conformance. 6 Soft network architecture for mobile and its design principle Facing growing mobile data traffic and the rapid change of new applications, new user
36、 requirements, new service requirements and operating policies, operators need to improve the flexibility of their networks, such as using network resources more efficiently and enhancing their network capabilities more quickly. In current mobile networks, it is often difficult for operators to quic
37、kly meet market requirements, because functions are implemented on dedicated equipment and adding new features into the current network usually takes a long time to complete through test, trial and deployment. In addition, new service function entities have to be added statically, which is not flexi
38、ble. Last but not least, control and forwarding functions are coupled such that they cannot be deployed flexibly and independently. To achieve the above goals, this Recommendation proposes soft network architecture for mobile (SAME), a mobile core network to be designed as an enhancement of Internat
39、ional mobile telecommunications-advanced (IMT-Advanced) mobile packet core network, to realize an even more flexible mobile packet core network that bridges the current legacy mobile network towards future networks. Although SAME does not aim to cover key requirements of IMT-2020 core network, the k
40、ey requirements of SAME may be adopted in IMT-2020. Rec. ITU-T Y.3323 (09/2016) 3 Based on the analysis of the scenarios and problems mobile operators face today, which are described in Appendices I and II, SAME focuses on implementing the following design principles: Efficient traffic steering: Tra
41、ffic can be flexibly steered to go through necessary service function entities to support quick addition of new capabilities. Efficient resource usage: Infrastructure can be shared among different network functions and slices. Flexible deployment of network functions: Control and forwarding function
42、s can be deployed in a centralized or distributed manner with minimum effect to other related functions. Flexible network scaling: Network functions can be dynamically adapted to users demands. Easy management of network: Resources and network functions can be managed with logically centralized, int
43、elligent and automatic operations. NOTE In this Recommendation, scaling includes scaling in/out, as described in b-ETSI GS NFV 003. The virtualization of control network entities (VCN) ITU-T Y.2320 can be supporting technology of SAME. 7 Requirements of SAME This clause focuses on the key requiremen
44、ts for SAME. R1 Support the capability of flexible traffic steering SAME aims to support flexible enhancement of new capabilities by adding specific service function entities without affecting existing service function entities. To achieve this, SAME is expected to satisfy the requirements below. It
45、 is required to support flexibly steering traffic passing through necessary service function entities according to the policies. It is required to define and update the traffic steering policies based on the following information: application characteristics of traffic such as application type, and
46、application protocol; access network information of traffic such as IMT-2000 access, IMT-Advanced access; users subscription information such as users priorities; service function entities status such as the failure of service function entities. It is required to support layer 3 through layer 7 (L3-
47、L7) traffic classification. R2 Support virtualization of SAME network functions In SAME, virtualization refers to those network entities and/or functions run on virtual computing, storage and networking resources, leveraging the hardware and software decoupling. On virtualization, SAME is expected t
48、o satisfy the requirements below. It is required to provide a capability for agile and flexible deployment of network functions. It is required to provide a capability for scalability of network capacity by auto scaling mechanism. It is required to provide a capability for efficient resource usage.
49、It is required to provide a capability for isolation of resource usage for different tenants. It is required to provide a capability for operation, maintenance management and orchestration of the infrastructure in an automatic and centralized manner. It is required to provide a capability to allow the virtualized resource usage to the third party. NOTE 1 The third party assumes network customer, e.g., a mobile virtual network operator (MVNO). The third party can ra
