| Internet-Draft | A 5G Integrated Security Service System | June 2026 |
| Ahn, et al. | Expires 25 December 2026 | [Page] |
This document presents a mobility-aware distributed security framework for 5G edge networks using the Interface to Network Security Functions (I2NSF) architecture. The proposed system uses Intent-Based Networking (IBN) to allow users or administrators to declare high-level security intents, which are translated into network and application policies. Network-level security policies may be enforced through distributed Network Security Functions (NSFs) deployed near User Plane Functions (UPFs), while application-level policies may be enforced on User Equipment (UE) through distributed IBN Controllers. This architecture is intended to support adaptive, context-aware, and distributed policy enforcement in response to dynamic edge conditions and user mobility scenarios such as handovers. Closed-loop monitoring and analytics provide feedback for maintaining policy consistency across heterogeneous 5G environments.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 25 December 2026.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Network softwarization technologies such as Network Functions Virtualization (NFV) [ETSI-NFV] and Software-Defined Networking (SDN) [RFC7149], together with Intent-Based Networking (IBN) [RFC9315], provide a foundation for automated and adaptive security orchestration in 5G edge environments. Through IBN, high-level security intents can be translated into network and application policies with reduced manual configuration.¶
This document defines a mobility-aware security framework for distributed 5G edge networks using the Interface to Network Security Functions (I2NSF) architecture [RFC8329]. The framework introduces intent-driven policy translation, distributed policy enforcement, and closed-loop monitoring mechanisms for adaptive security management across 5G edge domains. The proposed architecture considers interaction with 5G core functions such as the Policy Control Function (PCF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Network Exposure Function (NEF).¶
To support mobility-aware security management, the framework uses distributed Network Security Functions (NSFs) deployed near User Plane Functions (UPFs) in edge environments. During mobility events such as handovers between gNBs or transitions across UPFs, the framework is designed to support policy continuity through policy synchronization and policy re-application mechanisms. This approach provides a basis for context-aware and mobility-aware security orchestration in distributed 5G edge services.¶
This section provides definitions of the key terms and concepts used throughout this document. The terminology is intended to establish a common understanding of the architectural elements, interfaces, and operational principles discussed in the context of intent-based security management in 5G networks. These terms are used to describe 5G network automation based on the Intent-Based Networking (IBN) and Interface to Network Security Functions (I2NSF) framework.¶
Intent: A set of operational objectives and expected outcomes that a network is expected to fulfill, expressed in a declarative manner that focuses on desired outcomes rather than implementation details [RFC9315]. The data model and transport mechanism used to exchange an intent can be selected according to the requirements of each deployment.¶
I2NSF User Function (IUF): A functional component representing the I2NSF user role described in [RFC8329]. It provides an interface through which an administrator or application expresses high-level security intents and submits them to the Security Control Function (SCF).¶
Security Control Function (SCF): A functional component representing the security-controller role of the I2NSF framework [RFC8329]. The SCF translates high-level security intents into security policies and coordinates delivery of the resulting policies to the relevant NSFs and other authorized security enforcement components.¶
Security Data Analytics Function (SDAF): A functional component that collects and analyzes monitoring data to evaluate policy-enforcement status and the operation of security services. The SDAF supports feedback-driven validation and refinement of security policies within the proposed framework.¶
Network Security Function (NSF): A security enforcement component that performs functions such as traffic filtering, traffic blocking, and access control according to policies delivered by the SCF [RFC8329].¶
Policy Context: A set of policy rules, policy identifiers, policy versions, UE or session identifiers, target enforcement information, and enforcement state used to apply a security policy consistently across distributed 5G edge environments.¶
Policy Migration: A procedure by which the SCF transfers, synchronizes, or re-instantiates an active policy context from a source edge enforcement point to a target edge enforcement point during a mobility event such as UE handover.¶
Standby NSF: An NSF instance that is deployed at a target edge site but remains inactive for a specific UE until the corresponding policy context is migrated and the target enforcement point is selected for service continuity.¶
N2-Based Handover: An inter-NG-RAN node handover in which the handover procedure is coordinated through the 5G Core over the N2 interface, as specified in 3GPP TS 23.502 [TS-23.502].¶
Target Enforcement Point: The target NSF, and its associated target UPF or edge site, that enforces the migrated policy context after the user-plane path is switched during handover.¶
Mobility and Session Context: Information used by the proposed framework to associate a mobility event with a UE or PDU session and a selected target UPF. This context carries the identifiers and target user-plane information required to coordinate policy continuity during handover.¶
Policy-Ready Indication: A coordination signal indicating that the target NSF has installed and activated the applicable policy context. The signal communicates target-enforcement readiness to the relevant security-orchestration and mobility-coordination components.¶
IBN Controller: A device-side component that receives application-level policies, performs localized policy enforcement, and generates monitoring reports for adaptive security management. The IBN Controller participates in the distributed policy-enforcement and feedback loop of the proposed framework.¶
This section defines an architectural framework for 5G security management automation by introducing its essential components and explaining how each of them is designed to interconnect with functions in the 5G core networks [TS-23.501]. The framework is grounded in intent-based networking principles, which enable high-level user or application intents to be automatically translated into actionable policies. These policies can then be enforced and monitored across both the core and edge domains with reduced manual intervention.¶
As 5G networks become more distributed and support a growing number of latency-sensitive services and heterogeneous devices, traditional static security mechanisms may be difficult to operate at the scale and pace required by dynamic edge environments. Manual configuration may also become difficult to scale, motivating the use of automated security orchestration to support consistent policy application, shorter response times, and reduced configuration error.¶
To realize this, the framework leverages a set of I2NSF-based functional modules that collectively support policy translation, enforcement, and continuous monitoring. By integrating these components into the 5G architecture, the system is intended to support scalable, adaptive, and context-aware security operations tailored to the needs of dynamic and heterogeneous edge environments.¶
+------------------------------------+ +--------------------+
| 5G Core NFs | | |
| +-----+ +-----+ +-----+ +-----+ | | +-----+ +-----+ |
| |NSSF | | UDM | | NRF | | PCF | | | | IUF | | SDAF| |
| +---+-+ +---+-+ +---+-+ +---+-+ | | +--+--+ +--+--+ |
| | | | | | | | | |
| --+-+------+-+------+-+---+--+-+---+-+----+---+----+----- |
| | | | | | | | |
| +-+---+ +-+---+ +-+---+ +-+---+ | | +-----+ |
| | AUSF| | AMF | | SMF | | NEF | | | | SCF | |
| +-----+ +-+-+-+ +--+--+ +-----+ | | +-----+ |
| | | | | | Intent-Based |
| +-----+ +--+ +------+ | | Security Services |
+------+----------+-----------+------+ +--------------------+
| | |
+--+--+ +---+---+ +--+---+ +--+---+ +--------------+
| UE +---+ (R)AN +----+ UPFs +---+ NSFs +---+ Data Network |
+-----+ +-------+ +--+---+ +------+ +--------------+
Figure 1 illustrates a mobility-aware distributed security architecture for 5G edge networks based on the I2NSF framework [RFC8329]. An intent-based management strategy is used between the 5G Core network and distributed edge domains to support automated configuration and security enforcement across heterogeneous edge environments.¶
On the right side of the architecture, the Intent-Based Security Services represent functional modules responsible for generating, translating, monitoring, and orchestrating security intents and policies. These functions support distributed security management across 5G edge environments. They also serve as the interface between external users or applications and the intent-based security system. These services are composed of several key modules, including the I2NSF User Function (IUF), the Security Control Function (SCF), and the Security Data Analytics Function (SDAF), which collectively support intent interpretation, policy translation, distributed enforcement, and monitoring across the network.¶
The security intent generated by the IUF is first interpreted as a high-level objective reflecting the desired behavior of the network or specific applications. This intent is then processed by the Security Control Function (SCF), which includes a Security Policy Translator responsible for translating abstract intents into concrete security policies. Through this translation process, the SCF generates both network-level policies and application-level policies for distributed security enforcement across 5G edge environments.¶
Once these policies are generated, authorized 5G capabilities may be accessed through the Network Exposure Function (NEF), where applicable. The NEF provides exposure of selected 5G Core capabilities to external application functions according to 3GPP-defined procedures. When coordination with the 5G Core is required, the framework uses authorized 5G Core capabilities exposed through the NEF. To support flexible deployment and orchestration, the I2NSF components can be implemented as containerized microservices and managed using Kubernetes[Kubernetes].¶
The AMF, SMF, PCF, and other 5G Core functions retain their 3GPP-defined responsibilities, while I2NSF NSFs perform network-level security enforcement near or in the traffic path of distributed UPFs. Applicable 5G Core configuration is performed through the corresponding 3GPP interfaces and service operations. This functional separation combines standardized 5G Core control with localized security enforcement and mobility-aware policy adaptation.¶
For mobility support, the SCF maintains or retrieves policy contexts associated with UEs, PDU sessions, application flows, and target edge domains. The SCF obtains mobility and target-UPF context through the NEF and the relevant 5G Core capability-exposure mechanisms. The information can be derived from mobility context associated with AMF procedures and from PDU-session and selected target-UPF context maintained by the SMF. The exposure layer aggregates this context and provides it to the SCF for policy-continuity coordination. In this deployment model, an edge server can host a UPF and one or more NSFs, while another edge server can host a target UPF with a standby NSF. The target NSF is prepared during handover preparation so that the applicable security policy is available when the user-plane path is switched.¶
This section describes a use case where high-level user intents are automatically translated into enforceable network and application policies. Leveraging the I2NSF (Interface to Network Security Functions) framework [RFC8329] within a 5G Core environment, this architecture supports automated, intent-driven security management and can reduce reliance on manual configuration and static rule sets.¶
The system is designed to support distributed policy enforcement by integrating key I2NSF components such as the IUF, Security Control Function (SCF), and Security Data Analytics Function (SDAF). These components work collaboratively to process intents, generate appropriate policies, and enforce them dynamically across both the core network and the edge.¶
+----------------------+
| User Equipment |
| IBN Controller |
+----------^-----------+
| Application Policy
+-----+ +-------------+-------------+
| IUF |------>| Security Control Function |
+-----+Intent | (SCF / Policy Translator) |
+------+----------------+---+
| :
Network Policy | : 5GC Capability
v : Exposure through NEF
+-------------+ v
| Edge NSF / | +-----+
| Edge Router | | NEF |
+-------------+ +-----+
Figure 2 shows the procedure for automated 5G edge security management, including the creation of user intents and the generation of corresponding network and application policies. The process begins when a user or administrator expresses a security-related intent through the IUF. The intent is passed to the Security Control Function (SCF), whose Security Policy Translator converts the high-level intent into network-level and application-level policies. Network-level policies are delivered to the relevant edge NSF or security component, while application-level policies are delivered to the target UE. When policy processing requires 5G Core capabilities, the SCF coordinates with the 5G Core through the NEF and the corresponding authorized service operations.¶
User Equipment 1 (SmartPhone) User Equipment 2 (IoT Device)
+---------------------+ +---------------------+
| +-----------------+ | | +-----------------+ |
| |Service Functions| | | |Service Functions| |
| | (SFs) | | | | (SFs) | |
| +-----------------+ | | +-----------------+ |
| ^ | | | ^ | |
|Monitoring| | API | |Monitoring| | API |
| Data | |Command | | Data | |Command |
| | V | | | V |
| +--------------+ | | +--------------+ |
| |IBN Controller| | | |IBN Controller| |
| +--------------+ | | +--------------+ |
| ^ | | | ^ | |
+----------+--+-------+ +--------+-------+----+
| | | |
| +---------------------------------+
| | |
+--------------+-----+-------+----+ +
Application Policy | | | |
(Configuration) | | | |
| | | |
+---------------------------+-----+-----+ | |
| | | | | |
+--------+ | +------+ +-----+ +--+--+ | | | |
| Data +--|---+ NSFs +---+ UPF +---+ gNB | | | | |
| Network| | +------+ +--+--+ +--+--+ | | | |
+--------+ | | | | | | |
| +--+--+ +--+--+ | | | |
| | SMF | | AMF +--+ | | |
| +--+--+ +--+--+ | +-+--+---+
| | | | | Edge |
| --------+----+----+----+--- | | Router +---+
| | | | +---+----+ |
| +--+--+ +--+--+ | | |
| | SCF | | NEF |<--+--------+ |
| +--+--+ +--+--+ | Network |
| | Policy |
| | (Firewall |
+---------------------------------------+ & Web Filter) |
5G Core Network and I2NSF Security Services |
Monitoring |
Report |
V
+-------------------+
| Security Data |
| Analytics Function|
+---------+---------+
|
+---------------+---------+
| Monitoring Data Storage |
+-------------------------+
Figure 3 illustrates how intent-driven network policies and application policies are applied across distributed edge environments and user equipment. Network-level policies are delivered to the relevant NSFs and edge security components, where they are enforced in the user-plane traffic path. Where interaction with the 5G Core is required, an implementation may map the policy to authorized 5G Core configuration or service operations through authorized integration mechanisms consistent with the 5GS architecture [TS-23.501]. At the same time, application-level policies are delivered to user devices, such as smartphones and IoT nodes, whose embedded controllers interpret and enforce the received policies locally. These distributed controllers enable localized and mobility-aware policy enforcement at the device edge. Figure 3 presents a logical service-flow view in which the SCF coordinates policy delivery with the NEF, distributed NSFs, edge security components, and device-side IBN Controllers.¶
This allows each device to adjust its behavior according to the defined security or operational requirements. In parallel, network-based security functions can apply controls such as access restrictions or traffic filtering, helping align device-side and network-side enforcement with the original intent. This distributed approach supports flexible and adaptive policy enforcement across the mobile network environment. Distributed NSFs deployed near UPFs further support localized security enforcement and policy adaptation during mobility events in edge environments.¶
To support adaptive security validation, each user equipment's IBN Controller periodically generates monitoring reports based on local policy enforcement status. These reports are sent to the Security Data Analytics Function (SDAF), which analyzes the monitoring data to evaluate whether the applied policies are effectively enforced. All collected data is stored in a centralized Monitoring Data Storage module, supporting ongoing policy validation and historical auditing. The operational workflow is summarized as follows:¶
Intent submission and policy translation: An intent is delivered from an application or user service to the Security Control Function (SCF), where the Security Policy Translator converts the high-level intent into network-level and application-level policies.¶
Network-policy delivery: The network policy is delivered to the relevant NSFs and edge security components for enforcement. Where interaction with the 5G Core is required, the corresponding configuration or service operation is coordinated through authorized 5G Core capability exposure.¶
Application-policy delivery: The application policy is sent to the IBN Controllers on target user devices, enabling automated delivery of policy instructions to the applicable device-side controllers.¶
Local policy enforcement: Each device applies the policy to adjust its settings and behavior so that local operation reflects the system-wide intent.¶
Device monitoring: Devices monitor their status and send relevant data back to their IBN Controllers, providing continued visibility into policy impact at the device level.¶
Monitoring-report generation: The IBN Controllers compile and forward the data as monitoring reports, which provide a basis for evaluating the effectiveness of the applied policies.¶
Analytics and storage: The reports are analyzed to determine whether the policies are operating as intended, and the results are stored for future use. This completes the feedback loop that supports adaptive policy refinement.¶
Through this process, the system supports intent-driven security management across core network functions and user devices. By translating high-level intents into policies and monitoring their effects, the architecture can support ongoing adaptation to network conditions and user behavior. This feedback is intended to help maintain consistent and context-aware policy enforcement across distributed edge environments. Moreover, the closed-loop structure provides a foundation for scalable and feedback-driven policy management in distributed 5G edge networks.¶
This section describes a policy-continuity procedure that combines an inter-NG-RAN node N2-based handover with I2NSF policy migration and target-NSF activation. Figure 4, Figure 5, and Figure 6 form one continuous operational flow. Figures 4 and 6 illustrate the handover preparation and execution stages based on 3GPP TS 23.502 [TS-23.502], while Figure 5 introduces the I2NSF functions performed between target user-plane preparation and user-plane path switching. Together, these stages prepare the target user-plane path, migrate and activate the applicable policy context at the target NSF, and complete the UE handover while maintaining policy continuity.¶
In this procedure, the source and target NG-RAN nodes are served by the same AMF, and one PDU session is handed over. The target UPF is associated with a target NSF that receives and activates the migrated policy context. When the same UPF and NSF remain in use after the handover, the SCF verifies or updates the existing policy binding and maintains the active policy context at the current enforcement point.¶
The integrated procedure proceeds as follows:¶
The source NG-RAN initiates the handover by sending Handover Required to the AMF.¶
The AMF and SMF prepare the target NG-RAN, target UPF, and target user-plane path.¶
The NEF provides the mobility and session context to the SCF.¶
The SCF migrates the active policy context and activates the target NSF.¶
The UE accesses the target NG-RAN after receiving the Handover Command.¶
The AMF and SMF switch the user-plane path to the target UPF, and the SCF removes the source policy context after policy continuity is verified.¶
Figure 4 shows the handover-preparation stage based on the inter-NG-RAN node N2-based handover procedure in 3GPP TS 23.502, Clause 4.9.1.3.2 [TS-23.502]. This stage determines the target NG-RAN and target user-plane context that are used by the subsequent I2NSF policy-migration procedure.¶
S-NG-RAN AMF SMF T-UPF T-NG-RAN
| | | | |
| Handover Decision | | |
| Handover Required | | |
|---------->| | | |
| | | | |
| | PDU Session Update Request |
| |----------->| | |
| | | Target User-Plane |
| | | Selection and Preparation
| | |--------->| |
| | |<---------| |
| | | | |
| | PDU Session Update Response |
| |<-----------| | |
| | Handover Request | |
| |---------------------------------->|
| | Handover Request Acknowledge |
| |<----------------------------------|
The source NG-RAN sends Handover Required to the AMF after making the handover decision. The AMF requests the SMF to update the PDU-session context, and the SMF selects or confirms the target UPF and prepares the target user-plane path. The AMF then requests handover resources from the target NG-RAN and receives the Handover Request Acknowledge. At this point, the target UPF and target NG-RAN are available for the policy-migration and handover-execution stages.¶
The security orchestration system uses the selected target UPF to determine the corresponding edge site and target NSF. This mapping allows the SCF to select the target enforcement point and coordinate migration of the active policy context from the source NSF when the enforcement point changes.¶
Figure 5 shows the policy-migration stage between target user-plane preparation and user-plane path switching. The objective of this stage is to make the target NSF policy-ready before UE traffic begins to traverse the target UPF.¶
NEF SCF S-UPF+NSF1 T-UPF+NSF2
| | | |
| Mobility and Session Context | |
| (UE, PDU session, target UPF) | |
| I2NSF Context Exposure | |
|-------------->| | |
| | Active Policy Context Request |
| |--------------->| |
| | Active Policy Context Response |
| |<---------------| |
| Policy Migration and Target NSF Activation |
| |--------------------------------------->|
| | Target NSF Activation Response |
| |<---------------------------------------|
| Policy-Ready Indication | |
|<--------------| | |
The NEF provides the SCF with mobility and session context containing the UE or PDU-session identifier and the selected target UPF. Using this information, the SCF identifies the source enforcement point and the NSF associated with the target UPF. The SCF sends an Active Policy Context Request to the source NSF associated with the source UPF and receives the currently enforced policy context, including the applicable policy rules, identifiers, versions, UE or session bindings, and enforcement state.¶
The SCF then transfers or re-instantiates the policy context at the target NSF associated with the target UPF. The target NSF installs the policy, associates it with the target user-plane context, and activates the required security functions. The Target NSF Activation Response confirms that the target enforcement point is ready. The SCF then provides a Policy-Ready Indication through the NEF to report target-enforcement readiness. The resulting policy-ready state ensures that the applicable security policy is available when UE traffic begins to traverse the target user-plane path.¶
Figure 6 shows the handover-execution and path-update stage based on 3GPP TS 23.502, Clause 4.9.1.3.3 [TS-23.502]. This stage moves the UE to the target NG-RAN and switches the PDU-session user-plane path to the prepared target UPF.¶
UE S-NG-RAN T-NG-RAN AMF SMF T-UPF
| | | | | |
| | Handover Command | | |
| |<--------------------------| | |
| Handover Command | | | |
|<----------| | | | |
| | Uplink RAN Status Transfer| | |
| |-------------------------->| | |
| | | Downlink RAN Status | |
| | | Transfer | | |
| | |<------------| | |
| [Target-Cell Synchronization] | | |
| Handover Confirm | | | |
|------------------------>| | | |
| | | Handover Notify | |
| | |------------>| | |
| | | | PDU Session Context |
| | | | Update | |
| | | |------------>| |
| | | | | User-Plane |
| | | | | Path Update |
| | | | |------------>|
| | | [Target User-Plane Path Establishment] |
The AMF delivers the Handover Command through the source NG-RAN, and the RAN status is transferred to the target NG-RAN. The UE synchronizes with the target cell and sends Handover Confirm. The target NG-RAN then sends Handover Notify to the AMF. In response, the AMF and SMF update the PDU-session context and switch the user-plane path to the target UPF.¶
Because the target NSF has already installed and activated the migrated policy context, traffic forwarded through the target UPF is subject to the same security policy that was enforced on the source path. The source policy context remains available until the target enforcement state is confirmed, after which the SCF can remove the source-side policy context. This ordering maintains policy continuity across handover preparation, policy migration, UE movement, and user-plane path switching.¶
In the context of intent-based edge security management in 5G networks, several important security aspects must be considered to ensure robust and trustworthy system behavior. One key concern involves the potential for malicious manipulation of user intents. Since intents are high-level expressions of user goals that drive the automated generation of network and application policies, any unauthorized alteration could lead to unintended or insecure outcomes. Ensuring that each intent originates from a trusted source and is protected by integrity validation mechanisms is therefore essential.¶
Another important consideration is the accuracy and reliability of the policy translation and enforcement process. When translating abstract intents into concrete policies, the system must preserve the user's original intent while maintaining consistent and validated configurations. Implementations should incorporate validation checks, authorization controls, and feedback mechanisms to ensure that policies are correctly interpreted and consistently enforced.¶
Additional security considerations arise in distributed edge environments where policies and related security contexts are dynamically migrated across distributed enforcement points during mobility events. Ensuring policy consistency and secure synchronization between distributed NSFs is important for maintaining continuous security enforcement during handovers.¶
For mobility-aware policy migration, the SCF and distributed NSFs need to protect migrated policy contexts against unauthorized modification, replay, and disclosure. A migrated policy context should be bound to explicit identifiers such as the UE, PDU session, target UPF, policy identifier, policy version, and validity period. The activation of the target NSF should be acknowledged before the source policy context is removed or deactivated, in order to avoid a temporary gap in policy enforcement during handover. Implementations should also log migration events and activation results so that the SDAF can verify policy continuity and detect inconsistent or failed migrations.¶
The implementation applies an explicit continuity policy when target-NSF activation extends beyond the available handover-preparation interval. Available actions include retaining enforcement at a reachable source or central NSF, postponing the policy cutover, or applying a fail-closed rule for protected traffic. The I2NSF security-orchestration layer applies the selected behavior in coordination with the ongoing handover procedure.¶
This document presented a mobility-aware distributed security framework for 5G edge networks based on the I2NSF architecture and Intent-Based Networking. The handover example combines the preparation and execution stages of an N2-based handover with the proposed I2NSF policy-migration and NSF-activation operations. The framework is designed to support adaptive policy translation, distributed security enforcement, and policy continuity during mobility events through distributed NSFs and edge-aware orchestration mechanisms. Closed-loop monitoring and mobility-aware policy management provide a basis for scalable and resilient security orchestration in future 5G edge environments.¶
This document has no IANA actions.¶
This work was supported by Institute of Information & Communications Technology Planning & Evaluation (IITP) grant funded by the Korea Ministry of Science and ICT (MSIT) (No. RS-2024-00398199 and RS-2022-II221015).¶
This document is made by the group effort of NMRG, greatly benefiting from inputs and texts by Linda Dunbar (Futurewei), Yong-Geun Hong (Daejeon University), and Joo-Sang Youn (Dong-Eui University). The authors sincerely appreciate their contributions.¶
The following is the coauthor of this document:¶