Page 236 - 5G Basics - Core Network Aspects

1 Core network aspects

1 Scope
Soft network architecture for mobile (SAME) is a mobile packet core network, which bridges current legacy
mobile networks toward future networks. 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 packet 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 Recommendations 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 published. 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] 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 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 operators' 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 entities are independent from one another, and can be added, removed and bypassed.

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

226