Page 431 - 5G Basics - Core Network Aspects

Core network aspects 1

9.1 Access independence

Services and features offered via FMC are required to be access-independent so that services are offered to
users regardless of how they gain access.

9.2 Uniform authentication and uniform authorization mechanism
Due to the nature of FMC (see Appendix I for an analysis of FMC scenarios), FMC is required to provide a
uniform authentication and a uniform authorization mechanism at the FMC service stratum applicable to any
given configuration.

NOTE 1 – Uniform security mechanism (authentication or authorization) is meant to encompass a single, common,
generic security mechanism and is understood in the sense to bridge both for wireless- and for wire-based access
networks at the FMC service stratum. Thus, the notion of uniform applies only to the security mechanism as such but
does not impose any requirements to use uniform security keys/credentials, such as used by a single-sign on mechanism
for example.
NOTE 2 – As FMC may contain access-specific or access-dependent parts, a uniform authentication and uniform
authorization mechanism may not be available at the FMC transport stratum. For different users, the data relating to
authentication and authorization may vary, and the parameters in the related messages may also differ, but the
procedure for handling these is uniform.

It is left for future study to identify FMC security requirements for uniform authentication and authorization
mechanisms (i.e., authentication and authorization combined).

9.3 Charging and management

FMC is required to provide charging and management mechanisms.
NOTE – This requirement supports collecting resource usage information and managing data relating to subscriber
resource usage.

9.4 Service access environment
FMC is required to provide the capabilities to access a wide range of application servers or service platforms.
The underlying network may be circuit-based or packet-based.

9.5 Quality of service
FMC is required to provide QoS mechanisms.

NOTE – This requirement enables service level agreements supporting user and service requirements, such as dynamic
negotiation of QoS parameters between the service and transport layers, including both the access and the core
networks.

9.6 Interworking
FMC is required to support interworking with existing networks, e.g., the legacy PSTN.
Interworking does not impose any new requirements upon existing, non-FMC-capable networks other than
to provide interfaces to interworking functions according to standardized mechanisms that are already
supported by existing networks.

9.7 Reliability requirements
FMC is required to support reliable communications, including appropriate overload control and failure
recovery mechanisms. The support of specific overload control and failure recovery mechanisms to manage
and mitigate the consequences of such events to achieve the required level of reliability is not needed if the
transport network and the processing systems are considered to yield sufficient reliability and are able to
adequately mitigate overload situations.

9.8 Security requirements

FMC is required to provide security mechanisms to meet service requirements.

421