3GPP 23.501 v20.2.0 — the document's own text
5.21.0 General
Taught in 27. Overload, energy, deployment and the rest (The 5G system architecture, in depth).
5GC supports different virtualized deployment scenarios, including but not limited to the options below:
- A Network Function instance can be deployed as distributed, redundant, stateless and scalable NF instance that provides the services from several locations and several execution instances in each location.
- This type of deployments would typically not require support for addition or removal of NF instances for redundancy and scalability. In the case of an AMF this deployment option may use enablers like, addition of TNLA, removal of TNLA, TNLA release and rebinding of NGAP UE association to a new TNLA to the same AMF.
- A Network Function instance can also be deployed such that several network function instances are present within a NF set provide distributed, redundant, stateless and scalability together as a set of NF instances.
- This type of deployments may support for addition or removal of NF instances for redundancy and scalability. In the case of an AMF this deployment option may use enablers like, addition of AMFs and TNLAs, removal of AMFs and TNLAs, TNLA release and rebinding of NGAP UE associations to a new TNLA to different AMFs in the same AMF set.
- The SEPP, although not a Network Function instance, can also be deployed distributed, redundant, stateless and scalable.
- The SCP, although not a Network Function instance, can also be deployed distributed, redundant and scalable.
Also, deployments taking advantage of only some or any combination of concepts from each of the above options is possible.