Page 399 - 5G Basics - Core Network Aspects

Core network aspects 1

MSRP Message Session Relay Protocol

MT-FE Multimedia Telephony Functional Entity
MUE Multi-connection User Equipment

MUP-FE Multi-connection User Profile Functional Entity
NAB-FE Network Address Book Functional Entity

OCS Online Charging System
PR-FE Presence and Group Management Functional Entity
PS Packet Switched

QoS Quality of Service
RTP Real-time Transport Protocol

SCF Service Control Function
SDP Session Description Protocol
SIP Session Initiation Protocol

SMS Short Messaging Service
SRTP Secure Real-time Transport Protocol

TF Transport Function
UE User Equipment

UNI User-to-Network Interface
VoIP Voice over Internet Protocol

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.
The keywords "is not recommended" indicate a requirement which is not recommended but which is not
specifically prohibited. Thus, conformance with this specification can still be claimed even if this requirement
is present.
The keywords "can optionally" indicate an optional requirement which is permissible, without implying any
sense of being recommended. This term is not intended to imply that the vendor's implementation must
provide the option and the feature can be optionally enabled by the network operator/service provider.
Rather, it means the vendor may optionally provide the feature and still claim conformance with the
specification.

389