Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 22.830  Word version:  16.1.0

Top   Top   None   None   Next
1…   5…

 

1  Scopep. 6

The present document examines the business role models for network slicing in order to identify potential requirements that will enable a 3GPP system to adequately support those models, including:
  • Business role models for network slicing,
  • Trust relationships between MNOs and 3rd parties under various business role models,
  • Security relationships based on business role models,
  • Relationship of business role models with slice characteristics (e.g., slice scalability, slice flexibility), and
  • 3GPP enhancements needed to support the business role models for slices.
Up

2  Referencesp. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.261: "Service requirements for the 5G system".
[3]
TR 22.804: "Study on Communication for Automation in Vertical Domains";
[4]
ETSI TR 103 588 v1.1.1: "Reconfigurable Radio Systems (RRS); Feasibility study on temporary spectrum access for local high-quality wireless networks".
[5]
5G NORMA Deliverable D3.3: "5G NORMA network architecture - Final report".
Up

3  Definitions, symbols and abbreviationsp. 6

3.1  Definitionsp. 6

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
non-public network:
a network that is intended for non-public use
private slice:
a dedicated network slice deployment for the sole use by a specific 3rd party.

3.2  Abbreviationsp. 7

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5G
5th Generation
5GC
5G core network
A/V
Audio/Visual
CD/DVD
Compact Disc/Digital Versatile Disc
IoT
Internet of Things
KPI
Key Performance Indicator
LSA
Licensed Shared Access
MIoT
Massive Internet of Things
MNO
Mobile Network Operator
OTT
Over the Top
SCEF
Service Capability Exposure Function
SPaaS
Spectrum as a Service
URLLC
Ultra Reliable Low-Latency Communications
V/NFs
Virtual Network Functions
Up

4  Overviewp. 7

4.1  Business, stakeholder and management role modelsp. 7

5G supports new business role models relevant for 3GPP systems. In previous generations, business role models centered on two key types of relationships: those between Mobile Network Operators (MNOs) and their subscribers and those between MNOs (e.g., roaming, RAN sharing). To a limited extent, relationships between MNOs and 3rd party application providers have also been supported in the form of APIs (e.g., by the SCEF interface - see TS 23.682) allowing access to specific network capabilities, such as those used by 3rd party applications to access UE location information. 5G opens the door to new business role models for 3rd parties, allowing 3rd parties more control of system capabilities. This document considers these new business roles and how 3GPP can best support the trust relationships between MNOs and 3rd parties resulting from these new business role models.
In 5G three role models are envisaged for stakeholders.
  1. The MNO owns and manages both the access and core network.
  2. An MNO owns and manages the core network, the access network is shared among multiple operators (i.e., RAN sharing).
  3. Only part of the network is owned and/or managed by the MNO, with other parts being owned and/or managed by a 3rd party.
The first two are essentially those found in previous generations of 3GPP systems, where MNOs are operating PLMNs. In 5G it is expected that a 3rd party can take on the role of an MNO, however in this case the 3rd party would operate its own network. From a 3GPP perspective, stakeholder role models 1 and 2 are the same whether an MNO or vertical 3rd party is involved. Basic support for the 3rd party stakeholder role model was provided in previous generations via APIs which allowed minimal access to or management of network capabilities. In contrast, the 5G enhancements will allow greater control and ownership by the 3rd party, which will require increased trust between the MNO and 3rd party. These new trust relationships become even more impactful when network slicing is considered, particularly where the 3rd party is authorized to control some aspects of network slices that are owned by the MNO.
With the introduction of network slicing, the third stakeholder role model above warrants additional investigation to understand the trust relationships between MNOs and 3rd parties. There are four potential business relationship models impacting the trust relationships for stakeholder role model 3.
  • Model 3a: MNO provides the virtual/physical infrastructure and V/NFs; a 3rd party uses the functionality provided by the MNO,
  • Model 3b: MNO provides the virtual/physical infrastructure and V/NFs; a 3rd party manages some V/NFs via APIs exposed by the MNO,
  • Model 3c: MNO provides virtual/physical infrastructure; a 3rd party provides some of the V/NFs,
  • Model 3d: a 3rd party provides and manages some of the virtual/physical infrastructure and V/NFs.
Model 3a Model 3b Model 3c Model 3d
Virtual/physical Infrastructure (3GPP architecture)CorephysicalMNOMNOMNOMNO and 3rd party
virtualMNOMNOMNOMNO and 3rd party
RANphysicalMNOMNOMNOMNO and 3rd party
virtualMNOMNOMNOMNO and 3rd party
Virtual Network Functions (Applications/Servers)ProviderMNOMNOMNO and 3rd partyMNO and 3rd party
ManagerMNOMNO and 3rd partyMNO and 3rd partyMNO and 3rd party
 
Of these models, 3a and 3b have been addressed by the requirements in place in TS 22.261. Provision has been made to ensure appropriate APIs and management functions to support this extended 3rd party access and control of capabilities provided by the MNO, and to do so in a secure manner. Within these two models, the 3rd party has increasing control over the network capabilities that support its service. However, this control is limited to what is allowed by the MNO through the provided APIs.
Models 3c and 3d provide extended control for the 3rd party on the network capabilities supporting its service. However, these models still require ensuring appropriate levels of security are maintained for any communications.
In four potential business relationship models, three management role models can be considered for models 3c and 3d.
  1. MNO manages all virtual/physical infrastructure and all V/NFs including 3rd party's ones,
  2. 3rd party manages its own virtual/physical infrastructure and/or its own V/NFs; MNO manages the others.
  3. 3rd party manages virtual/physical infrastructure and/or V/NFs including its own virtual/physical infrastructure and/or V/NFs and some MNO's virtual/physical infrastructure and/or V/NFs; MNO manages the others.
From the 3rd party perspective, the management role models 2 and 3 support the 3rd party management function and provide extended management for the MNO to coordinate with the 3rd party management. The 3rd party may use suitable APIs provided by the MNO to directly manage the V/NFs as well as the infrastructure resources so that it can properly handle when their business requirements are changed.
Up

4.2  Trust relationshipsp. 8

The degree of trust between the MNO and 3rd party has an impact on the 3GPP system. In model 3a, the 3rd party must be able to trust the MNO to provide the necessary capabilities. In the other models, the MNO must also be able to ensure that the degree of control provided to the 3rd party does not allow the 3rd party to negatively impact the MNOs network. TS 22.261 addresses the trust relationships for models 3a and 3b. For models 3c and 3d to be supported, additional consideration is needed on the mechanisms to provide the isolation and interfaces that give the 3rd party the appropriate level of control while securing the PLMN.
Specifically for models 3c and 3d, where the 3rd party provides V/NFs or provides and manages some of the virtual/physical infrastructure and V/NFs, SLAs may be used to address some trust issues, such as what each party will provide and manage. However, the principles of trust and verification also come into play. The 3rd party must be able to verify, though the management interface, that all terms of the SLA are being met by the MNO. Similarly, the MNO must be able to verify that the 3rd party is managing resources appropriately so that there is no adverse impact to the rest of the network. Appropriate management interfaces are needed to support both the network operator and 3rd party.
The underlying trust relationships support such models and may lead to new 3GPP requirements, such as the abilities to provide slice based authentication and slice based encryption and integrity protection. The present document considers the trust relationships related to extended control by a 3rd party.
Up

Up   Top   ToC