Page 130 - 5G Basics - Core Network Aspects

1 Core network aspects

Figure 3 – An example of LINP federation without LINP exchangers

Service deployment in each of the administrative domains is conducted on the federated LINPs by a same
service developer. When service deployment functions are implemented by network operators, as in Figure
3, the service developer functions use multiple service deployment functions that individually reside in
different administrative domains.
NOTE – [b-ITU-T Y.3511] presents the following three patterns as inter-cloud connections: "inter-cloud peering", "inter-
cloud federation", and "inter-cloud intermediary". These patterns are distinguished primarily by whether common
application programming interfaces (APIs) are used or not and whether there is an intermediary cloud service provider
or not. In this document, the term "federation" is used regardless of whether or not common NNIs and/or VMIs are
used or LINP exchangers exist. LINP federation can involve reconciliation of different protocols at the reference points
and/or of different administrative policies in any cases. The example shown in Figure 3 can be viewed as equivalent to
the inter-cloud peering or the inter-cloud federation as described in [b-ITU-T Y.3511].

7 Resources and LINPs

7.1 Physical resources

As shown in Figure 4, physical resources are classified into four categories: physical link resources, transport
resources, computing resources, and storage resources. A physical link resource may consist of a single layer,
such as VLAN, or a combination of multiple layers, such as generic routing encapsulation (GRE) and IP.
Examples of transport resources include routers and switches. Examples of computing resources include
central processing units (CPUs) and memories. Examples of storage resources include devices holding high
volume of data.

120