Page 333 - 5G Basics - Core Network Aspects

Core network aspects 1

3 Definitions

3.1 Terms defined elsewhere

This Recommendation uses the following terms defined elsewhere:
3.1.1 application [ITU-T Y.2261]: A structured set of capabilities, which provide value-added functionality
supported by one or more services, which may be supported by an API interface.

3.1.2 call [ITU-T Q.2981]: An association between two or more users using a telecommunication service
to communicate through one or more networks.

3.1.3 connection [ITU-T X.200]: A connection is an association established for the transfer of data
between two or more peer-(N)-entities. This association binds the peer-(N)-entities together with the (N–1)-
entities in the next lower layer.
3.1.4 handover [ITU-T Q.1706]: The ability to provide services with some impact on their service level
agreements to a moving object during and after movement.

3.1.5 IP flow [ITU-T Y.1221]: An IP flow at a given interface is defined as the occurrence at that interface
of the set of IP packets which match a given classification. An IP flow may consist of packets from a single
application session, or it may be an aggregation comprising the combined traffic from a number of application
sessions. When a classification may be subdivided into different sub-classifications (separate or overlapping),
different IP subflows may be recognized in the corresponding IP flow.

3.1.6 service continuity [ITU-T Q.1706]: The ability for a moving object to maintain ongoing service over
including current states, such as user's network environment and session for a service.

3.1.7 session [ITU-T T.140]: A logical connection between two or more user terminals for the purpose of
exchanging information in text format on a real-time basis.

3.2 Terms defined in this Recommendation
This Recommendation defines the following terms:
3.2.1 multi-connection: The functionality which provides capability to the user equipment (UE) and
network to maintain more than one access network connection simultaneously.
NOTE 1 – All connections are coordinated to provide service to higher layer entities.
NOTE 2 – In a multi-connection communications at least one UE is required to be a multi-connection UE.

3.2.2 service component: Part of a service which cannot be further decomposed.
3.2.3 service decomposition: Act of decomposing a service into several service components.
NOTE – The original service logic can be restructured transparently to the end user and application.

3.2.4 service transfer: Act of moving, one or more services or service components belonging to a single
multi-connection UE, from one access network associated with one interface of the multi-connection UE to
another access network(s) associated with other interface(s) of the multi-connection UE.

4 Abbreviations and acronyms
This Recommendation uses the following abbreviations and acronyms:

2G Second Generation wireless telephone technology
3G Third Generation wireless telephone technology
3GPP 3rd Generation Partnership Project

AP Access Point
API Application Programming Interface

BSS Base Station Subsystem

323