Page 319 - 5G Basics - Core Network Aspects
P. 319
Core network aspects 1
1) One or more packet header field (e.g., destination IP address), transport header field
(e.g., destination port number), or application header field (e.g., RTP header fields [b-RFC 3550]);
2) One or more characteristics of the packet itself (e.g., number of MPLS labels, etc.);
3) One or more of fields derived from packet treatment (e.g., next hop IP address, the output interface,
etc.).
3.2 Terms defined in this Recommendation
None.
4 Abbreviations and acronyms
This Recommendation uses the following abbreviations and acronyms:
2G Second Generation
3G Third Generation
3GPP 3rd Generation Partnership Project
AC-FE Access Control FE
FE Functional Entity
FSC Flow-based Service Continuity
IAS Intelligent Access Selection
IP Internet Protocol
MC-FE Multi-connection Coordination FE
MAS-F Multi-connection Application Support Function
MMF Multi-connection Media Function
MPC-FE Multi-connection Policy Control FE
MR-FE Multi-connection Registration FE
MTC-FE Multi-connection Terminal Control FE
MUE Multi-connection User Equipment
MUP-FE Multi-connection User Profile FE
QOS Quality of Service
SC Service Continuity
SCF Service Control Function
WLAN Wireless Local Area Network
5 Conventions
In this Recommendation:
The keywords "is required to" indicate a requirement which must be strictly followed and from which no
deviation is permitted if conformance to this document is to be claimed.
The keywords "is prohibited from" indicate a requirement which must be strictly followed and from which
no deviation is permitted if conformance to this document is to be claimed.
The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely
required. Thus this requirement need not be present to claim conformance.
309