Page 240 - 5G Basics - Core Network Aspects
P. 240
1 Core network aspects
Appendix I
Scenarios of SAME
(This appendix does not form an integrated part of this recommendation.)
The clause focuses on the scenarios for SAME.
I.1 Flexible traffic steering
The identification and classification of traffic may be based on the radio access network (RAN) information
(e.g., RAN type, and RAN status), application characteristics (e.g., application type, application protocol),
user's subscription data, and direction (i.e., upstream or downstream) of the flow.
Scenario 1: traffic steering classified by application type
Descriptions
SAME routes the traffic based on application type.
Preconditions
Three service function entities are deployed by the operator, which are uniform resource locator (URL) filter,
protocol optimization and video optimization. Policies are defined such that the flow of a hypertext transport
protocol (HTTP) video service should go to the URL filter and video optimization, and the flow of the web
browsing service should go to the URL filter and protocol optimization.
Operational flows
Figure I.1 – Flexible traffic steering scenario
1) There are two groups of flows initiated by users: HTTP video; web browsing.
2) The flows of each group are identified and separated by mobile core network.
3) The HTTP video flow goes through URL filter and video optimization. The web browsing flow goes
through URL filter and protocol optimization.
Scenario 2: traffic steering classified by different tenant
Descriptions
The different MVNOs may have individual requirements on the data flows processing at the (S)Gi-LAN
position. The SAME network prepares appropriate service function entities and steers traffic based on the
identities of the MVNOs.
NOTE 1 – The service function entities could be prepared by mobile network operator (MNO), or by the MVNOs
themselves for specific data flows processing.
NOTE 2 – The service function entities prepared by the MVNOs could be an integrated entity of multiple sub-functions.
If one of the sub-functions is the same with the MNO's data flows processing function, SAME needs to guarantee not to
trigger the data flows going through the MNO's same function again.
230