Service function chaining services in edge data networks and 5G networks

Abstract

Various embodiments herein provide techniques for service function chaining (SFC) in wireless cellular networks and / or edge data networks. In some embodiments, a service function path (SFP) is configured across both the wireless cellular network and the edge data network. In other embodiments, the SFP is configured in the edge data network. Other embodiments may be described and claimed.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to U.S. Provisional Patent Application No. 63 / 045,761, filed June 29, 2020, and U.S. Provisional Patent Application No. 63 / 052,187, filed July 15, 2020.

[0002] [Technical field] Various embodiments may relate generally to the field of wireless communications. [Background technology]

[0003] In the 3rd Generation Partnership Project (3GPP®) Release 13, Flexible Mobile Service Steering (FS_FMSS) was discussed in 3GPP Technical Report (TR) 22.808 v14.1.0 (2015-12-17) (referred to herein as "TR22.808" or [1]). In this discussion, there were numerous use cases that mentioned the use of service function chaining over the (S)Gi interface. However, in the normative stage, the only service requirement in 3GPP Technical Standard (TS) 22.101 v17.1.0 (2019-12-20) (referred to herein as "TS22.101" or [2]) was for traffic steering over the (S)Gi interface, assuming that the (S)Gi-Local Area Network (LAN) was outside the 3GPP scope. The same assumption applies to N6-LAN in the 5G context. [Brief explanation of the drawings]

[0004] [Figure 1] It shows that different service function paths (SFPs) in a service function chain (SFC) in SGi_LAN are applied to different users. [Figure 2] Shows the different SFCs used in SGi-LAN. [Figure 3]This figure shows a service-based representation of a reference architecture for a policy and charging control framework for 5G systems. [Figure 4] 1 shows a reference point representation of a reference architecture for a policy and charging control framework for 5G systems. [Figure 5] 10 illustrates processing of an AF request to affect traffic routing for a session not identified by a UE address. [Figure 6] 1 illustrates an application architecture for enabling edge applications. [Figure 7] 1 illustrates a reference architecture including an SFC network within an edge data network, according to various embodiments. [Figure 8] 1 illustrates an example of an SFC enabler in an edge data network and / or a 5G network, according to various embodiments. [Figure 9] 1 depicts an example SFC network of an edge data network having one or more service function paths (SFPs). [Figure 10] 1 illustrates an application architecture of an edge data network that enables SFC services over an SFC network and uses SFC services provided by a 5G network, according to various embodiments. [Figure 11] 1 illustrates a corresponding service-based architecture with an SFC enabler in a 5G network, according to various embodiments. [Figure 12] 1 illustrates an example of coordination of SFC services in an edge data network and a 5G network, according to various embodiments. [Figure 13] 1 illustrates an example procedure for SFC configuration coordination between SFC services in an edge data network and SFC services in a 5G network, according to various embodiments. [Figure 14]10 illustrates an example procedure for setting up an AF session with required SFC parameters procedure, according to various embodiments. [Figure 15A] 10 illustrates an example of a modified / updated Nnef_ParameterProvision_update request / response procedure according to various embodiments. [Figure 15B] 10 illustrates an example of a modified / updated Nnef_ParameterProvision_update request / response procedure according to various embodiments. [Figure 16] 1 illustrates an exemplary service-specific information provisioning procedure, according to various embodiments. [Figure 17] 1 illustrates an example UE configuration update procedure for a transparent UE policy distribution procedure, according to various embodiments. [Figure 18] 10 illustrates an example procedure for processing an AF request to affect traffic routing for a session not identified by a UE address, according to various embodiments. [Figure 19] 1 illustrates a procedure according to various embodiments. [Figure 20] 1 illustrates a reference architecture including an SFC network within an edge data network, according to various embodiments. [Figure 21] 1 further illustrates an application architecture of an edge data network that enables SFC services over an SFC network, according to various embodiments. [Figure 22] 1 illustrates an example procedure including message flows for SFC configuration and AF requests for interfering with traffic routing, according to various embodiments. [Figure 23] 10 illustrates another exemplary procedure including message flows for SFC configuration and AF requests for interfering with traffic routing, according to various embodiments. [Figure 24] 1 illustrates a network in accordance with various embodiments. [Figure 25]1 illustrates a schematic diagram of a wireless network in accordance with various embodiments. [Figure 26] FIG. 1 is a block diagram illustrating components, according to some example embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein. [Figure 27] 1 illustrates an exemplary procedure for practicing various embodiments discussed herein. [Figure 28] 1 illustrates an exemplary procedure for practicing various embodiments discussed herein. DETAILED DESCRIPTION OF THE INVENTION

[0005] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this document, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0006] As mentioned above, TR 22.808 [1] considered Flexible Mobile Service Steering as part of Flexible Mobile Service Steering. In this study, there were many use cases that mentioned the use of service function chaining across the (S)Gi interface. However, in the normative stage, the only service requirement in 3GPP Technical Standard (TS) 22.101 v17.1.0 (2019-12-20) (referred to herein as "TS 22.101" or [2]) was for traffic steering over the (S)Gi interface, assuming that the (S)Gi-LAN was outside the 3GPP scope. The same assumption applies to the N6-LAN in the 5G context. For example, Figure 1 shows that different service function paths (SFPs) in the service function chain (SFC) in the SGi_LAN are applied to different users. Additionally, Figure 2 shows that different SFCs are used in the SGi-LAN.

[0007] By considering N6-LAN outside the 3GPP scope, we assume that the service function chaining within N6-LAN is controlled by a separate system that is different from 5GS. However, this separation of individual service functions within N6-LAN from the 5G architecture creates challenges in many aspects of the 5G network. First, the lack of integrated network management and orchestration of service function chaining between 5G networks and N6-LANs can lead to interoperability issues even within the same network operator's mobile network, resulting in uncoordinated and inefficient service function path configuration for routing E2E services with desired service functions. - Second, if SFs are chained and service functions within the N6-LAN provided by operators and third parties cannot be controlled, contributing to latency at every hop, it will be difficult to achieve the latency requirements for some services that target ultra-high reliability and low latency, such as interactive AR / VR games, remote control of UAVs, audiovisual service production, industrial automation, critical medical applications, and autonomous vehicles. - Third, when considering service continuity, for example, in roaming scenarios between HPLMN and VPLMN or between PLMN and NPN networks, from the user's point of view, the service experience may be impaired. - Fourth, 5G will increase the demand for supporting versatile vertical services, which will bring challenges in supporting service capabilities within the N6-LAN in different network and service deployment scenarios and meeting the KPIs required for the services. - Fifth, 5G networks have some advanced features that are not considered in FMSS / eFMSS, such as network slicing, network function virtualization, and edge computing.

[0008] A solution to address the above-mentioned challenges includes enabling service function chaining services in 5GS, which provides tighter control of service function chaining. The present disclosure provides a solution for enabling SFC networks in edge data networks (DNs) and / or 5G networks.

[0009] For example, the present disclosure provides embodiments for scenarios where the SF in an SFC path spans both an edge data network and a 5G network. These embodiments include: - Embodiment 1: An SFC enabler for both edge data networks and 5G networks. - Embodiment 2: SFC parameters for SFC network configuration. - Embodiment 3: SFC service coordination between an edge data network and a 5G network. - Embodiment 4: An operation, administration, and maintenance (OAM) entity provides SFCF-U configuration information for an SFCF-U instance. -Embodiment 5: SFC configuration in the 3GPP management plane. - Embodiment 6: The SFCF-C configures the SFP to cooperate with the SFC network in the edge data network.

[0010] Additionally, the present disclosure provides embodiments for enabling SFC services in edge data networks. These embodiments include: - Embodiment 7: Enabling SFC network support in edge data networks. Embodiment 8: Application architecture with support for SFC networks in edge data networks Embodiment 9: SFC parameters for SFC network configuration - Embodiment 10: Application Server Provider (ASP) provides SFC service Embodiment 11: An edge computing service provider (ECSP) provides SFC services in an edge data network. - Embodiment 12: SFC configuration in 3GPP management plane Embodiment 13: EAS triggered AF inference traffic routing in 5GS (with DPI capability)

[0011] Aspects of various embodiments herein may be used in combination or separately. The embodiments herein solve challenges / problems presented by previous and existing solutions. In some implementations, the embodiments turn these challenges into benefits. Additionally, the introduction of SFC services in edge data networks enables support for integrated orchestration and management in the 3GPP management plane.

[0012] Figures 3 and 4 (corresponding to Figures 5.2.1-1 and 5.2.1-1a of TS 23.503) show the overall architecture for the policy and charging framework in a 5G system in both a service-based and a reference point representation. The reference architecture for the policy and charging control framework for 5G includes a policy control function (PCF), a session management function (SMF), a user plane function (UPF), an access and mobility management function (AMF), a network exposure function (NEF), a network data analysis function (NWDAF), a charging function (CHF), an application function (AF), and a unified data repository (UDR). Figure 3 shows the service-based representation, and Figure 4 shows the reference point representation of the reference architecture for the policy and charging control framework for a 5G system.

[0013] The N4 reference point is not part of the 5G Policy Framework architecture but is shown in the diagram for completeness (see, for example, 3GPP TS23.501 v16.4.0(2020-03-27) ("TS23.501" or [4]) for the definition of the N4 reference point). How the PCF / NEF stores / retrieves information about policy subscription data or application data is specified in TS23.501. The Nchf service for online and offline charging consumed by the SMF is specified in TS32.240 v16.1.0(2019-12) ("TS32.240" or [8]). The Nchf service for Spending Limit Control consumed by the PCF is specified in TS23.502 v16.4.0(2020-03-27) ("TS23.502" or [5]).

[0014] According to clause 4.3.6 of TS 23.502 [5], the AF influences traffic routing as described in clause 5.6.7 of TS 23.501 [4]. The AF may send a request to influence SMF routing decisions for user plane traffic of a PDU session. The AF request may influence UPF (re)selection and enable routing of user traffic to the local access to the data network (identified by the DNAI). The AF may also provide subscriptions to SMF events in the request. Figure 5 (corresponding to Figure 4.3.6.2-1 of TS 23.502) shows the processing of an AF request to influence traffic routing for a session not identified by a UE address.

[0015] Figure 6 shows an application architecture for enabling edge applications. The edge data network is a local data network. The edge application server(s) and edge enabler server are included within the EDN. The edge configuration server provides configuration for the EES, including details of the edge data network that hosts the EES. The UE includes application client(s) and edge enabler client. The edge application server(s), edge enabler server, and edge configuration server may interact with the 3GPP core network.

[0016] Interactions between edge enabler servers and edge enabler clients related to enabling edge computing are supported by the EDGE-1 reference point, which supports registration and deregistration of edge enabler clients with edge enabler servers, retrieval and provisioning of configuration information for UEs, and discovery of available edge application servers in the edge data network.

[0017] The edge enabler layer interaction between the edge enabler server and the 3GPP network is supported by the EDGE-2 reference point, which supports access to 3GPP network functions and APIs to retrieve network capability information via, for example, the SCEF and NEF APIs as specified in 3GPP TS23.501[4], TS23.502[5], TS29.522[9], TS29.122

[10] , and by the EES acting as a trusted AF in 5GC (see clause 5.13 of TS23.501[4]). The EDGE-2 reference point reuses interfaces from the SA2-defined 3GPP reference points, N33, or EPS or 5GS to allow for different deployment models.

[0018] The interactions regarding the edge enabler layer between the edge enabler server and the edge application server are supported by the EDGE-3 reference point, which supports the registration of edge application servers with availability information (e.g., time constraints, location constraints), deregistration of edge application servers from the edge enabler server, and providing access to network capability information (e.g., location information). The following cardinality rules apply to EDGE-3 (between EAS and EES): a) one EAS may communicate with only one EES; b) one EES may communicate with one or multiple EASs simultaneously.

[0019] The edge enabler layer interaction between the edge data network configuration server and the edge enabler client is supported by the EDGE-4 reference point, which supports the provisioning of edge data network configuration information to the edge enabler client in the UE.

[0020] Interaction between application client(s) and edge enabler clients within the UE is supported by the EDGE-5 reference point, which supports obtaining information about edge application servers to which application clients request to connect; notification about events related to the connection between application clients and their corresponding edge application servers, such as when an application client needs to reconnect to a different edge application server; providing application client information (such as its profile) used for various tasks such as identifying an appropriate edge application server instance to connect to; and providing the identity of the desired edge application server to the edge enabler client so that it can use that identity as a filter when requesting information about the edge application server.

[0021] The interaction between the edge data network configuration server and the edge enabler server regarding the edge enabler layer is supported by the EDGE-6 reference point, which supports the registration of edge enabler server information with the edge enabler network configuration server.

[0022] The edge enabler layer interaction between the edge enabler server and the 3GPP network is supported by the EDGE-2 (or EDGE-7) reference point. The EDGE-7 reference point supports access to 3GPP network functions and APIs to retrieve network capability information via the SCEF and NEF APIs as specified in 3GPP TS23.501[4], TS23.502[5], TS29.522[9], TS29.122

[10] , for example, and by the EAS acting as a trusted AF in 5GC (see clause 5.13 of TS23.501[4]). The EDGE-7 reference point reuses the interfaces of the SA2-defined 3GPP reference points, N6, or EPS or 5GS to allow for different deployment models.

[0023] Interaction between the edge data network configuration server and the 3GPP network is supported by the EDGE-8 reference point, which supports edge data network configuration provisioning to the 3GPP network using network exposure services.

[0024] The EDGE-9 reference point enables interaction between two Edge Enabler Servers. The EDGE-9 reference point can be provided between EESs in different EDNs (Figure 6.4.10-1 of TS 23.758) and within the same EDN (Figure 6.4.10-2 of TS 23.758).

[0025] The Edge Enabler Server (EES) provides the necessary support functions for the Edge Application Server and the Edge Enabler Client. The Edge Enabler Server functionality is: a) provisioning of configuration information to the Edge Enabler Client, enabling the exchange of application data traffic with the Edge Application Server; b) support of the API Invoker and API Exposer functionality as specified in

[11] ; c) interaction with the 3GPP Core Network to access the capabilities of the Network Functions directly (e.g., via the PCF) or indirectly (e.g., via the SCEF / NEF / SCEF+NEF); and d) support of the Application Context Transfer functionality.

[0026] The following cardinality rules apply to edge enabler servers: a) one or more EESs may be located within the EDN; b) one or more EESs may be located within the EDN per ECSP.

[0027] An edge application server (EAS) is an application server that resides in an edge data network and performs server functions. Application clients connect to the edge application server to utilize the services of the application with the benefits of edge computing. The server functions of an application may be available only as an edge application server. However, if the server functions of an application are available both as an edge application server and as an application server residing in the cloud, the functions of the edge application server and the application server may not be the same. In addition, if the functions of the edge application server and the application server are different, the application data traffic may also be different.

[0028] The edge application server may consume 3GPP core network capabilities in various ways, for example, a) if it is an entity trusted by the 3GPP core network, it may call a 3GPP core entity function API directly, b) it may call 3GPP core network capabilities through an edge enabler server, or c) it may call 3GPP core network capabilities through a capability exposure function (e.g., SCEF or NEF).

[0029] The following cardinality rules apply to edge application servers: a) One or more EASs may be located within an EDN. EAS(s) belonging to the same EAS ID may be provided by multiple ECSPs within the EDN.

[0030] The edge enabler server ID (EESID) is the FQDN of the edge enabler server, and each edge enabler server ID is unique within a PLMN domain.

[0031] The Edge Application Server ID (EASID) identifies a specific application, e.g., SA6Video, SA6Game, etc. For example, all EDGE SA6Video servers would share the same Edge Application Server ID. The format of the EAS ID is outside the scope of this specification. Table 0-8.2.4-1 shows the Edge Application Server Profile IE. [Table 1] Edge application server service KPIs provide information about the characteristics of services provided by edge application servers (see, for example, Table 0-8.2.5-1). [Table 2] The Edge Enabler Server Profile contains information about the EES and the services it provides (see, for example, Table 0-8.2.6-1). [Table 3]

[0032] The network capability exposure to the edge application server(s) depends on the business relationship between the ASP / ECSP and the PLMN operator and the deployment scenario. The following mechanisms are supported: direct network capability exposure and / or network capability exposure via an edge enabler server.

[0033] In some implementations, network capability exposure to the EAS(s) depends on the business relationship between the ASP / ECSP and the PLMN operator and the deployment scenario. The following mechanisms are supported: direct network capability exposure and / or network capability exposure via an edge enabler server. In some implementations, charging functionality, where deployment options vary depending on the business relationship between the edge application service provider, edge computing service provider, and SFC service provider, is outside the scope of this disclosure (SA5 discussion).

[0034] TS23.203

[12] describes a solution for handling traffic steering policies in coordination with SFC in (S)Gi-LANs, which is outside the scope of the 3GPP system.

[0035] Among other things, the present disclosure provides embodiments related to SFC in the following scenarios: - SFs within the Service Function Path (SFP) for service chaining span both edge data networks and 5G networks, which has never been considered in any previous or existing solutions. An SFC network having an SF and a service function path (SFP) is provided by an edge data network, for example, by an edge application service provider and / or an edge computing service provider.

[0036] Service Chaining with Service Function Paths Across Edge Data Networks and 5G Networks This embodiment solves the above-mentioned problems and turns these problems into benefits, and also enables the coordination of SFC services between edge data networks and 5G networks to support unified orchestration and management in the 3GPP management plane.

[0037] In various embodiments and example implementations discussed herein, network capability exposure to the edge application server(s) may depend on the business relationship between the ASP / ECSP and the PLMN operator and the deployment scenario. The following mechanisms are supported: direct network capability exposure and / or network capability exposure via an edge enabler server. Charging functionality, with different deployment options depending on the business relationship between the edge application service provider, edge computing service provider, and SFC service provider, is outside the scope of this disclosure.

[0038] FIG. 7 illustrates a reference architecture including an SFC network within an edge data network (this reference architecture includes partial network functions) according to various embodiments. Service function chaining services are provided in the edge data network by enabling support for a service function chaining network (SFC network), which terminates at the N6 reference point with the trusted or external data network. Service function chaining policies for steering traffic that must pass through a specific service function path (SFP) within the SFC network can be configured by the AS, AF, or 3GPP OAM. For an application server (AS) in the external data network, the AF can infer traffic routing, for example, via the NEF on the N33 interface toward the SFC network of the edge data network via N6. For an AS in the trusted data network, the AF can directly influence traffic routing, for example, via the PCF on the N5 interface toward the SFC network of the edge data network via N6.

[0039] Figure 8 illustrates an example of an SFC enabler in an edge data network and / or a 5G network, according to various embodiments. Figure 9 depicts an example of an SFC network in an edge data network having one or more SFPs. In particular, Figure 9 illustrates an example of an SFC network having a traffic classifier, a traffic declassifier, one or more SFs, and an SFP, where traffic flows within each SFP are transported through ordered service functions.

[0040] 8 and 9, the SFC network includes a traffic classifier, a traffic declassifier, and an SF, which can process one or more SFPs. Each SFP includes an ordered SF through which traffic must pass. The one or more SFs can be provided by the same or different service providers, for example, edge application service provider(s), edge computing service provider(s), SFC service provider, or network operator(s). Depending on the deployment option, the SFC network configuration can be supported on EDGE-X and EDGE-Y accordingly.

[0041] EDGE-X is the interface between the SF / traffic classifier / traffic declassifier and the EAS in the SFC network. EDGE-Y is the interface between the SF / traffic classifier / traffic declassifier and the EES in the SFC network. The traffic classifier and traffic declassifier have traffic filtering policies to classify and combine traffic flows for each SFP before and after SFP processing, respectively. For traffic flows that do not have an assigned SFP, they skip all SFs in the SFC network.

[0042] As a non-limiting example, the SFs in Figures 8 and 9 can be one of the following functions: - Network Address Translation (NAT), - IP tunnel endpoints, - packet classifier, - Deep Packet Inspection (DPI), - Legal Inspection (LI), - TCP proxy, - load balancer, - Firewall functionality, - transcoder, - URL filters, - Application Detection and Control (ADC), - Video Optimizer.

[0043] In an embodiment, an SFC having SFs in one or more SFC paths spans both an SFC network in an edge data network and an SFC function (SFCF) in a 5G network. That is, to configure one or more service function paths, some SFs are in the 5G network and some SFs are in the edge data network. In an embodiment, an SFC enabler in an edge data network is in the SFC network and includes SFs for one or more SFPs, which may be provided by an edge application service provider, an edge computing service provider, or an SFC network service provider. In an embodiment, an SFC enabler in a 5G network may provide SFC services to edge application servers, which may be provided by a network function having SFC capabilities, including SFC configuration, SFC control, and traffic transport for SFPs. In an embodiment, an SFC enabler in a 5G network or an edge data network supports the following SFC functions:

[0044] Embodiment 1: SFC enabler in both edge data networks and 5G networks FIG. 10 illustrates an application architecture of an edge data network that enables SFC services over an SFC network and uses SFC services provided by a 5G network, according to various embodiments.

[0045] In embodiment 1.1, the SFC network terminates the N6 reference point with the trusted edge data network or external edge data network, depending on the business relationship and deployment scenario between the edge application service provider or edge computing service provider and the PLMN operator.

[0046] The EAS or EES of an edge data network can support the AF to interact with the 5G network via the 5G network's northbound API, e.g., the 5G Network Capability Exposure API (Nnef_trafficInferencing_Create / Update / Delecte messages), on the EDGE-7 or EDGE-2 interface, respectively. For edge data networks within an external data network, the AF can infer traffic routing with or without SFC (e.g., toward the edge data network's SFC network via N6) via the NEF on the N33 interface (e.g., EDGE-7 / EDGE-2). For edge data networks within a trusted data network, the AF can directly influence traffic routing with or without SFC, i.e., toward the edge data network's SFC network via N6, via the PCF on the N5 interface (e.g., EDGE-7 / EDGE-2).

[0047] As shown in Figures 8, 9, and 10, an SFC network providing SFC services includes a service function and one or more service function paths with corresponding ordered SFs through which traffic must pass. EDGE-X is the interface between the SFs / traffic classifiers / traffic declassifiers in the SFC network and the EAS. EDGE-Y is the interface between the SFs / traffic classifiers / traffic declassifiers in the SFC network and the EES. The traffic classifiers and traffic declassifiers have traffic filtering policies for classifying and combining traffic flows for each SFP before and after SFP processing, respectively. For traffic flows that do not have an assigned SFP, all SFs in the SFC network are skipped.

[0048] The SFC services of the SFC network may be provided by one or more service providers, including edge service provider(s), edge computing service provider(s), SFC network service provider(s), or network operator(s).

[0049] Depending on the deployment option, the SFC network configuration, including service function chaining policies for steering traffic that needs to traverse specific service function paths (SFPs) within the SFC network, may be configured by 3GPP OAM or by EAS(s) and EES(s) via EDGE-X and EDGE-Y, as appropriate.

[0050] a. Embodiment 1.2: SFC Enabler in 5G Networks In embodiment 1.2, the service function chain in a 5G network can be supported in an NF with the following SFC capabilities: - SFC User Plane Function (SFCF-U): Primarily for transporting traffic, it can be a standalone user plane function for SFC services or it may be supported by an extended UPF with SFCF-U functionality for SFC services. The SFCF-U can be a standalone user plane function or an extended UPF with SFCF-U functionality for SFC processing. - SFC Control Plane Function (SFCF-C): Manages SFC policies and configures the SFCF-U via a new interface Nx, where the SFCF-U interfaces with the UPF via a new reference point N6S to steer traffic received from the UPF, as shown in Figure 10. The SFCF-C has functionality as an SMF and PCF, which may be an alternative architectural design to augment the SMF and / or PCF with SFCF-C functionality for SFC services.

[0051] According to various embodiments, SFCF-C and SFCF-U are used to indicate support for SFC enablers in the control plane and user plane, respectively, in 5G networks, however the solution is not limited to standalone NFs, i.e., the solution is applicable to different deployment options, including extensions of the UPF for SFCF-U, and extensions of the SMF and PCF with SFC capabilities for SFCF-C.

[0052] Figure 11 shows a corresponding service-based architecture with an SFC enabler in a 5G network. SFC policies for steering traffic that needs to traverse a specific service function path (SFP) can be configured in the SFCF-U by the SFCF-C. The SMF configures the UPF with routing paths towards one or more SFCF-U(s) for the SFC service. · The UPF forwards the traffic to one or more SFCF-U(s) to pass through the configured SFPs identified by the SFP ID(s). · SMF is based on SFC policies provided by SFCF-C via a new interface Nz. The Edge Data Network AF can interact with the SFCF-C directly or through the NEF. In this case, messages between the SFCF-C and the NEF are routed through a new interface Ny to support SFC configuration.

[0053] Alternatively, there are the following alternative options: - If the SMF has SFC functionality for steering traffic for SFC services in the SFCF-U based on the SFC configuration, i.e., has part of the functionality of the SFCF-C function, the SMF configures the SFCF-U via a new interface Nw. - If the PCF can support the processing of SFC configurations, i.e., has part of the functionality of the SFCF-C function, then the SFCF-C is in the PCF. - If the UPF can support SFCF-U capabilities, the UPF can forward traffic to the UPF with SFCF-U via the N9 interface.

[0054] b. Embodiment 1.3: Coordination of SFC services in edge data networks and 5G networks According to embodiments 1.1, 1.2, and / or any other embodiment herein, in embodiment 1.3, an SFC service for an application may be provided by an EDGE DN and a 5G network. For example, as shown in FIG. 12, SF1 and SF2 may be in the 5G network, SF3 and SF4 may be in the SFC network of the edge data network, SFP1 includes SF2 and SF3, and SFP2 includes SF1 and SF4. The EAS configures the SFC network with SF3 and SF4 and parts of SFP1 and SFP2 directly or via the EES, sends an AF request to the 5G network to configure SF1 and SF2 in the 5G network with parts of SFP1 and SFP2, and steers traffic for the corresponding SFP1 and SFP2 through N6 toward the SFC network.

[0055] Embodiment 2: SFC parameters for SFC network configuration According to embodiments 1.1, 1.2, 1.3 and / or any other embodiments herein, the SFC parameters of the SFC service in the edge data network or 5G network may include the following information: - SFC Service ID: Service ID of this set of SFC parameters for the SFC service - SFC configuration: one or more SFs with corresponding SF parameters - SFP configuration: SFP index with corresponding ordered SFs. - SFC routing policy: Traffic classifier indicates a mapping between an SFP index and a traffic filtering rule for forwarding traffic to the first SF in the SFP identified by the SFP index. Traffic declassifier indicates the traffic filter rules for combining traffic from the last SF in the SFP identified by the SFP index. - Validity parameters for the SFC service identified by the SFC service ID, for example: Duration A scheduled time period, for example, 8:00 AM to 8:00 PM every day. Application ID(s) PDU session type, e.g., IP / Ethernet / Unstructured, DNN, or associated PDU session parameters, including slice / service type (SST) (e.g., eMBB, URLLC, MIoT, V2X, etc.) and optional slice differentiators (SD)

[0056] The traffic classifier provides the SFP index along with a mapping to an SFC classification policy based on different levels or granularity per packet, including one or more of the following information, for example: - UE address - Application ID - Media Type - Traffic Priority

[0057] DPI capabilities in traffic classifiers are necessary when information is only available in the traffic payload.

[0058] The traffic declassifier provides an "N6 Tunnel ID" terminating the N6 reference point of the DNAI (Data Network Access ID) for the data network to combine traffic from one or more SFPs before forwarding to the application server of the application, along with a mapping to an SFC reclassification policy containing one or more of the following information, for example: - UE address - Application ID - Media Type - Traffic Priority - SFP Index

[0059] DPI capabilities in the traffic declassifier are necessary when information is only available in the traffic payload.

[0060] Embodiment 3: SFC service coordination between edge data network and 5G network According to embodiment 2 and / or any other embodiment herein, the EAS or EES may initiate an AF request to coordinate an SFC service in a 5G network with an SFC service in an edge data network. In the case of an EES with AF, the EAS may use an EES API via an EDGE-3 interface to request the triggering of an AF request from the EES to the 5G network, for example, to the NEF via N33 if the EES / EAS is in an external edge data network, to the PCF via N5 if the EES / EAS is in a trusted edge data network, or to the SFCF-C via Nxx.

[0061] c. Solution 3.1: Edge Application Server Provider (EASP) provides SFC services According to embodiment 2 and / or any other embodiment herein, in embodiment 3.1, the AF request is sent by the EAS directly towards the NEF / PCF / SFCF-C or sent via the EES using an EES API to trigger the AF in the EES to further create an AF request using a 5G network capability exposure API to interact with the NF in the 5G network.

[0062] 13 illustrates an example procedure for SFC configuration coordination between an SFC service in an edge data network and an SFC service in a 5G network, according to various embodiments. The procedure of Example 13 may operate as follows. Step 1: The EAS configures the SFC network either directly via EDGE-X or via EES through EDGE-3 using the EES API and EDGE-Y interface. Depending on the deployment scenario as shown in embodiment 1, in which an EASP or an ECSP provides SFC services in an SFC network, the following two cases can be supported. - Case 1: An EASP provides SFC services to EAS(s) of an edge data network. The EASP can use one of its EAS(s) to provision SFC parameters of the SFC network for SFC services over the EDGE-X interface by sending an SFC configuration request message to control and configure SFs and SFPs in the SFC network. - Case 2: ECSP provides SFC services to EAS(s) via EES in the edge data network. Based on the EES API to EAS for provisioning SFC parameters for SFC services on the EDGE-3 interface, the EES can trigger an SFC configuration request message on a new interface EDGE-Y to control and configure SFs and SFPs in the SFC network. Step 2-3: If the EES supports AF, the EAS using the EES capability exposure API can request the EAS to send an AF request using the 5G network capability exposure to the SFC service in the 5G network. Step 4-5: If the EAS supports AF, the EAS can send the AF request directly to the PCF / SFCF-C or via the NEF. Step 6: The AF request may request the following operations: Performing SFC configuration directly in the PCF / SFCF-C (embodiment 3.1) or via UDM / UDR (embodiment 3.2) Performing SFC configuration in the UE via the PCF / SFCF-C (embodiment 3.3) Performing user plane traffic inference in the UPF / SFCF-U (embodiment 3.4) or in the UE (embodiment 3.3)

[0063] d. Embodiment 3.1: Northbound API for AF requests to coordinate SFC services in 5GS with SFC networks in edge data networks According to embodiment 3 and / or any other embodiment herein, the EAS sends an AF request message (EAS ID and AF Request) directly through the AF or through the AF of the edge enabler server over EDGE-3 and N33 / N5 / Nxx. The AF request is for setting up an AF session with the required SFC parameters of the SFC service configuration procedure. The AF session is for an existing PDU session or a future session of a UE identified by a UE address / GPSI, a group of UEs identified by a list of UE addresses / external group identifier, or any UE for an application, or any UE for an SFC service identified by an SFC service ID where the target of the SFC service is indicated in the SFC parameters for the SFC service.

[0064] FIG. 14 illustrates an exemplary procedure for setting up an AF session with required SFC parameters procedure, according to various embodiments. Step 1:,When setting up a connection between an AF and a 5GS with the required SFC parameters of the SFC service configuration for a UE, a group of UEs, or any UE, the AF sends an Nnef_AFsessionWithSFC_Create request message (UE-ID(s), AF identifier, application flow description, SFC parameters) to the NEF. The Nnef_AFsessionWithSFC_Create request message includes the SFC parameters, such as the SFC service ID, of the SFC service configuration to be created / updated / deleted as shown in embodiment 2. The UE-ID can be: - For an individual UE, the UE-ID can be a GPSI or UE IP / Ethernet address - For a group of UEs, the UE-ID(s) can be a list of external group identifiers or UE IP / Ethernet addresses - If UE-ID is not provided, the AF request is for any UE that also has an application or SFC service indicated in the SFC parameter for the SFC service. Optionally, the time duration or traffic volume of the requested SFC parameters may be included in the AF request. The NEF assigns a transaction reference ID to the Nnef_AFsessionWithSFC_Create request. Step 5: The NEF sends an Nnef_AFsessionWithSFC_Create response message (transaction reference ID, result) to the AF. The result indicates whether the request is allowed or not.

[0065] e. Embodiment 3.2: Northbound API for AF request for service-specific parameter provisioning to a UE / UE group / any UE by coordinating SFC services across SFC networks in the UE, 5G network, and edge data network. According to embodiment 3 and / or any other embodiment herein, the UDR stores the provisioned "SFC parameters of the SFC service configuration." An AF request, for example, an Nnef_ParameterProvisioning_Update request, is to provision SFC parameters for the SFC service configuration via the NEF and store the SFC service configuration in the UDM / UDR.

[0066] 15A and 15B show an example of a modified / updated Nnef_ParameterProvision_update request / response procedure according to various embodiments. This procedure is a modified version of Figure 4.15.6.2-1 in Section 4.15.6.2 of [5], adding steps 0b and 7b. As shown by Figures 15A and 15B, the NEF service operation information is as follows: 0. The NF subscribes to UDM notifications of UE and / or group subscription data updates. NOTE 1: The NF subscribes to group subscription data from the UDM in this step and can be notified of group subscription data updates in step 7 using the shared data function specified in TS 29.503

[52] . 0b. [Conditional, when using NWDAF assistance value] The AF may subscribe to the NWDAF via the NEF to learn UE mobility analytics and / or UE communication analytics for a UE or a group of UEs by applying the procedure specified in clause 6.1.1.2 of

[50] . The Analysis ID is set to one of the values ​​specified in clause 6.7.1 of

[50] . 0c. [Conditional, when using NWDAF assistance values] The AF validates the received data and derives one of the expected UE behavior parameters specified in clause 4.15.6.3 of [5] for the UE or group of UEs. An 0x.NF (e.g., PCF / SFCF-C) can subscribe to UDM or UDR notifications of information updates for an SFC service by indicating subscriber data related to the SFC service, e.g., the application associated with the SFC service requested by the AF. 1. The AF provides the NEF with one or more parameters to be created or updated in a Nnef_ParameterProvision_Create or Nnef_ParameterProvision_Update or Nnef_ParameterProvision_Delete request. The GPSI identifies the UE and the transaction reference ID identifies the transaction request between the NEF and the AF. In the case of Nnef_ParameterProvision_Create, the NEF assigns a transaction reference ID to the Nnef_ParameterProvision_Create request. The NEF checks whether the requester is authorized to perform the requested service operation by checking the requester's identifier (ie, AF ID). For create requests associated with a 5G VN group, the external group ID identifies the 5G VN group. The payload of the Nnef_ParameterProvision_Update request contains one or more of the following parameters: - expected UE behavior parameters (see clause 4.15.6.3), or - network configuration parameters (see Section 4.15.6.3a), or - External group ID and 5G VN group data (i.e., 5G-VN configuration parameters) (see clause 4.15.6.3b), or - 5G VN group membership management parameters (see clause 4.15.6.3c of [5]). - Location Privacy Indication parameter in the "LCS Privacy" data subset of Subscription Data (see Section 5.2.3.3.1 and Section 7.1 of

[51] ). The AF may request to delete the 5G VN configuration by sending Nnef_ParameterProvision_Delete to the NEF. The AF provides the SFC parameters of the SFC service configuration to be updated in the UDR to the NEF in an Nnef_ParameterProvision_Update request, where the SFC parameters are in accordance with embodiment 2. 2. If the AF is authorized by the NEF to provision parameters, the NEF requests that the provisioned parameters be created, updated and stored, or deleted as part of the subscriber data via a Nudm_ParameterProvision_Create, Nudm_ParameterProvision_Update, or Nudm_ParameterProvision_Delete request message, where the message includes the provisioned data and the NEF reference ID. If the AF is not authorized to provision the parameters, the NEF proceeds to step 6 and indicates the reason for the failure in the Nnef_ParameterProvision_Create / Update / Delete response message. In this case, step 7 does not apply. NOTE 2: In non-roaming cases, where authorization or validation by the UDM is not required and the request is not associated with a 5G VN group, the NEF may forward the external parameters directly to the UDR via a Nudr_DM_Update request message. In this case, the UDR responds to the NEF via a Nudr_DM_Update response message. 3. The UDM may read the corresponding subscription information using Nudr_DM_Query from the UDR to verify the necessary data updates and authorize these changes for this subscriber or corresponding group of AFs. 4. Once the AF is authorized by the UDM to provision parameters for this subscriber, the UDM changes the GPSI to SUPI and requests to create, update, or delete the provisioned parameters as part of the subscriber data via a Nudr_DM_Create / Update / Delete request message, where the message includes the provisioned data. If a new 5G VN group is created, the UDM shall assign a unique internal group ID to the 5G VN group and include the newly assigned internal group ID in the Nudr_DM_Create request message. If the list of 5G VN group members changes or if the 5G VN group data changes, the UDM shall update the UE and / or group subscription data according to the AF / NEF request. The UDR stores the provisioned data as part of the UE and / or group subscription data and responds with a Nudr_DM_Create / Update / Delete response message. When the 5G VN group data (described in Section 4.15.6.3b) is updated, the UDR notifies subscribed PCFs by sending a Nudr_DM_Notify as specified in Section 4.16.12.2. If the AF is not authorized to provision the parameters, the UDM proceeds to step 5 and indicates the reason for the failure in the Nudm_ParameterProvision_Update response message, and step 7 is not performed. The UDM classifies the received parameters (i.e., expected UE behavior parameters or network configuration parameters or 5G VN configuration parameters or location privacy indication parameters) into AMF-related parameters and SMF-related parameters. The UDM may associate the received parameters with a specific subscribed DNN and / or S-NSSAI using the AF ID received from the NEF in step 2. The UDM stores the SMF-related parameters under the corresponding session management subscription data type. Each parameter or parameter set may be associated with a validity time, which is stored in the UDM / UDR and in each NF to which the parameter is provisioned (e.g., in the AMF or SMF). When the validity time expires, each node autonomously deletes the parameter without explicit signaling. 5. The UDM responds to the request with a Nudm_ParameterProvision_Create / Update / Delete response. If the procedure failed, the cause value indicates the reason. 6. NEF responds to the request with a Nnef_ParameterProvision_Create / Update / Delete response. If the procedure failed, the cause value indicates the reason. The NEF provides the results of the AF request for updating the SFC policy in the UDM / UDR. 7. [Conditional, this step occurs only after step 4 is successful] The UDM notifies subscribed network functions (e.g., AMF) of the updated UE and / or group subscription data via the Nudm_SDM_Notification notification message. a) If the NF is an AMF, the UDM executes the Nudm_SDM_Notification (SUPI or internal group identifier, AMF-related parameters, etc.) service operation. The AMF identifies whether overlapping parameter set(s) exist and, if necessary, merges those parameter set(s) in the expected UE behavior. The AMF uses the received AMF-related parameters to derive appropriate UE configuration for NAS parameters and derive core network-assisted RAN parameters. The AMF may determine the registration area based on parameters such as the Stationary indication or the Expected UE Moving Trajectory. b) If the NF is an SMF, the UDM executes the Nudm_SDM_Notification (SUPI or internal group identifier, SMF-related parameter sets, DNN / S-NSSAI, etc.) service operation. The SMF stores the received SMF-related parameters and associates them with a PDU session based on the DNN and S-NSSAI included in the message from the UDM. The SMF identifies whether there are overlapping parameter set(s) in the expected UE behavior and merges those parameter set(s) if necessary. The SMF may use the SMF-related parameters as follows: - The SMF configures the UPF accordingly. The SMF can configure the UPF with the number of downlink packets to buffer using the Scheduled Communication Type parameter or the Suggested Number of Downlink Packets parameter. The SMF can decide to deactivate the UP connection using the Communication duration time parameter and perform a CN-initiated selective deactivation of the UP connection of an existing PDU session. The SMF may derive SMF-derived CN-supported RAN information for the PDU session. The SMF provides the SMF-derived CN-supported RAN information to the AMF as described in the PDU session establishment procedure or PDU session modification procedure. Note 3: The NEF (Note 1) or UDM (Step 3) can also update the corresponding UDR data via Nudr_DM_Create / Delete as appropriate. 7b. The UDR sends a Nudr_DM_Notify to the NF.

[0067] f. Embodiment 3.3: AF Request for UE Service Parameter Update via AMF According to embodiment 3.2 and / or any other embodiment herein, the AF request indicates UE service parameters for the SFC service configuration. Provisioning of the service-specific parameters includes a procedure for enabling the AF to provide the service-specific parameters to the 5G system via the NEF. The AF may issue requests on behalf of applications that are not owned by the PLMN serving the UE. In architectures without CAPIF support, the AF is locally configured with API termination points for the service. In architectures with CAPIF support, the AF obtains service API information from the CAPIF core function via service API event notifications or service discovery response availability, as specified in 3GPP TS 23.222

[54] . The AF request sent to the NEF contains the following information: 1) Service Description: The service description is information that identifies the service to which the service parameters apply. The service description in the AF request can be represented by a combination of a DNN and an S-NSSAI, an AF service identifier, or an application identifier. 2) Service Parameters: Service parameters are service-specific information that needs to be provisioned in the network and conveyed to the UE to support the service identified by the service description. 3) Target UE(s) or group of UEs: The target UE(s) or group of UEs indicates the UE(s) to which the service parameters should be delivered. Individual UEs can be identified by GPSI, or IP address / prefix or MAC address. A group of UEs can be identified by an external group identifier as specified in TS 23.682

[23] . If the identifier of the target UE(s) or group of UEs is not provided, the service parameters shall be delivered to any UE using the service identified by the service description. The NEF authorizes the AF request received from the AF and stores the information in the UDR as "application data." The service parameters are delivered to the target UE by the PCF when the UE is reachable. Figure 4.15.6.7-1 of [5] shows the procedure for provisioning service-specific parameters. The AF provides the service-specific parameters to the PLMN and the UE using the Nnef_ServiceParameter service.

[0068] Figure 16 shows an exemplary service-specific information provisioning procedure based on Figure 4.15.6.7-1 of [5]. The procedure of FIG. 16 may operate as follows: 0. The SFC policy in the PCF / SFCF-C is associated between the AMF and the PCF / SFCF-C when the UE registers. 1. To create a new request, the AF calls the Nnef_ServiceParameter_Create service operation. To update or delete an existing request, the AF invokes the Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete service operation with the corresponding transaction reference ID provided to the AF in the Nnef_ServiceParameter_Create response message. The content of this service action (AF request) includes the information described in Section 5.2.6.11 of [5]. The AF request is to update the SFC policy in the UDR and potentially to trigger the PCF / SFCF-C to update the SFC policy in the UE on existing or future PDU sessions. 2. The AF sends the request to the NEF. The NEF authorizes the AF request. The NEF performs the following mapping: - Map the AF service identifier to a combination of DNN and S-NSSAI determined by local configuration. - Map the GPSI in the target UE identifier to the SUPI according to the information received from the UDM. - Map external group identifiers in the target UE identifier to internal group identifiers according to information received from the UDM. (For Nnef_ServiceParameter_Create): The NEF assigns a transaction reference ID to the Nnef_ServiceParameter_Create request. 3. (For Nnef_ServiceParameter_Create or Update): The NEF stores the AF request information in the UDR as "application data" (data subset set in "service-specific information") along with the assigned transaction reference ID. (In the case of Nnef_ServiceParameter_Delete): The NEF deletes the AF request information from the UDR. 4. The NEF responds to the AF. In the case of a Nnef_ServiceParameter_Create response message, the response message includes the assigned transaction reference ID. The NEF provides the results of the SFC policy update in the UDR. In step 0, when the UE is registered with the network and the PCF subscribes to notifications for data modified in the UDR by calling Nudr_DM_Subscribe(AF Service Parameter Provisioning Information, SUPI, Data Set set in "Application Data", Data Subset set in "Service Specific Information"), the following steps are performed: 5. The PCF(s) receive a data change notification Nudr_DM_Notify from the UDR. The UDR notifies the PCF / SFCF-C of the change in the SFC service configuration in the UDR. NOTE 2: The PCF does not need to subscribe to application-specific information for each UE if, for example, the PCF has already received application-specific information for a group of UEs or a DNN through subscriptions of other UEs. The same application-specific information is delivered to all UEs in the group or DNN. 6. The PCF initiates UE policy delivery as specified in clause 4.2.4.3. The PCF initiates the UE policy delivery procedure for SFC service configuration in the UE as shown in the following figure.

[0069] 17 illustrates an exemplary UE configuration update procedure for a transparent UE policy distribution procedure, according to various embodiments. This procedure is initiated when the PCF wants to update UE access selection and PDU session selection related policy information (i.e., UE policy) in the UE configuration. In non-roaming cases, the V-PCF is not involved and the role of the H-PCF is performed by the PCF. In roaming scenarios, the V-PCF interacts with the AMF, and the H-PCF interacts with the V-PCF. 0. The PCF decides to update the UE policy based on a trigger condition such as initial registration, registration to 5GS when the UE moves from EPS to 5GS, or the need to update the UE policy as follows: - In case of initial registration and registration to 5GS when the UE moves from EPS to 5GS, the PCF compares the list of PSI contained in the UE access selection and PDU session selection related policy information in the Npcf_UEPolicyControl_Create request and determines whether the UE access selection and PDU session selection related policy information needs to be updated and provided to the UE via the AMF using the DL NAS TRANSPORT message as described in clause 6.1.2.2.2 of 3GPP TS23.503. - In case of a UE policy update triggered by the network (e.g., change of UE location, change of subscribed S-NSSAI as described in clause 6.1.2.2.2 of TS 23.503), the PCF checks the latest list of PSIs to determine which UE access selection and / or PDU session selection related policies need to be sent to the UE. The PCF checks whether the size of the resulting UE access selection and PDU session selection related policy information exceeds a predetermined limit: - If the size is below that limit, the UE access selection and PDU session selection related policy information is included in a single Namf_Communication_N1N2MessageTransfer service operation as described below. If the size exceeds a predetermined limit, the PCF splits the UE access selection and PDU session selection related policy information into smaller, logically independent pieces of UE access selection and PDU session selection related policy information, ensuring that the size of each is below the predetermined limit. Each UE access selection and PDU session selection related policy information will then be sent in a separate Namf_Communication_N1N2MessageTransfer service operation, as described below. Note 1: The NAS message from the AMF to the UE does not exceed the maximum size limit allowed in the NG-RAN (PDCP layer), so the predetermined size limit in the PCF is related to that limit. NOTE 2: The mechanism used to split UE access selection and PDU session selection related policy information is described in 3GPP TS29.507. 1. The PCF invokes the Namf_Communication_N1N2MessageTransfer service operation provided by the AMF. The message includes a SUPI and a UE policy container. 2. If the UE is registered and reachable by the AMF over either a 3GPP access or a non-3GPP access, the AMF shall transparently forward the UE policy container to the UE over the registered and reachable access. If a UE is registered to both 3GPP and non-3GPP accesses, is reachable in both accesses, and is served by the same AMF, the AMF shall transparently forward the UE policy container to the UE via one of the accesses based on the AMF local policy. If the UE is not reachable by the AMF via both 3GPP and non-3GPP accesses, the AMF reports to the PCF that the UE Policy Container cannot be delivered to the UE using Namf_Communication_N1N2TransferFailureNotification as in step 5 of clause 4.2.3.3 of [5]. If the AMF decides to transparently forward the UE policy container to the UE over 3GPP access, for example, if the UE is registered and reachable by the AMF only in 3GPP access, or if the UE is registered and reachable by the AMF in both 3GPP and non-3GPP accesses served by the same AMF and the AMF decides to transparently forward the UE policy container to the UE over 3GPP access based on a local policy, and the UE is CM-IDLE and reachable by the AMF in 3GPP access, the AMF shall initiate a paging procedure by sending a paging message as described in step 4b of the Network Triggered Service Request (clause 4.2.3.3 of [5]). Upon receiving the paging request, the UE shall initiate a UE Triggered Service Request procedure (clause 4.2.3.2 of [5]). 3. If the UE is CM-CONNECTED via 3GPP access or non-3GPP access, the AMF transparently forwards the UE policy container (UE access selection and PDU session selection related policy information) received from the PCF to the UE. The UE policy container contains a list of policy sections as described in TS 23.503. 4. The UE updates the UE policy provided by the PCF and sends the result to the AMF. 5. If the AMF receives the UE policy container and the PCF is subscribed to be notified of the receipt of the UE policy container, the AMF forwards the UE's response to the PCF using Namf_Communication_N1MessageNotify. The PCF maintains an up-to-date list of PSI delivered to the UE and updates the up-to-date list of PSI in the UDR by invoking the Nudr_DM_Update(SUPI, policy data, policy set entry, updated PSI data) service operation. If the PCF is notified about the UE policy delivery failure, the PCF may initiate the UE Policy Association Modification procedure and provide a new trigger "Connectivity State Change" in the Policy Control Request Trigger for the UE policy association to the AMF as specified in clause 4.16.12.2. NOTE 3: For backward compatibility, the PCF may subscribe to the "Connectivity State Change (IDLE or CONNECTED)" event in Rel-15 AMF as specified in section 5.2.2.3.

[0070] g. Embodiment 3.4: AF Request for Traffic Inference via SMF Without Identified UE Address In accordance with embodiment 3 and / or any other embodiment herein, the AF request indicates traffic inference for an SFC service controlled by the SMF / SFCF-C. Figure 18 illustrates an example procedure for processing an AF request to affect traffic routing for a session not identified by a UE address, according to various embodiments. NOTE 1: It is assumed that the 5GC functions used in this scenario all belong to the same PLMN (HPLMN in non-roaming cases, or VPLMN in case of PDU sessions in LBO mode). NOTE 2: The Nnef_TrafficInfluence_Create or Nnef_TrafficInfluence_Update or Nnef_TrafficInfluence_Delete service operations invoked from an AF located within the HPLMN for local breakout and home routed roaming scenarios are not supported. 0. The PCF or SFCF-C subscribes to notifications of SFC policy changes in the UDR. 1. To create a new request, the AF invokes the Nnef_TrafficInfluence_Create service operation. The contents of this service operation (AF Request) are specified in clause 5.2.6.7 of [5]. This request also contains an AF transaction ID. When subscribing to events related to a PDU session, the AF also indicates where it would like to receive the corresponding notifications (AF Notification Report Information). To update or delete an existing request, the AF invokes the Nnef_TrafficInfluence_Update or Nnef_TrafficInfluence_Delete service operation providing the corresponding AF transaction ID. The AF request is to update the SFC policy in the UDR targeting traffic inference at the UPF / SFCF / U, which can potentially trigger the SMF / SFCF-C for traffic inference for existing or future PDU sessions in step 6. 2. The AF sends the request to the NEF. If the request is sent directly from the AF to the PCF, the AF reaches the PCF selected for the existing PDU session by configuration or by calling the Nbsf_management_Discovery service. The NEF ensures the necessary authorization control, including throttling of AF requests and mapping from information provided by the AF to information required by the 5GC, as described in Section 4.3.6.1 of [5]. 3. (If Nnef_TrafficInfluence_Create or Update): The NEF stores the AF request information in the UDR (data set = application data, data subset = AF traffic influence request information, data key = AF transaction internal ID, S-NSSAI and DNN and / or internal group identifier or SUPI). NOTE 3: When AF request information is stored in the UDR, both the AF transaction internal ID and the S-NSSAI and DNN and / or internal group identifier or SUPI are considered as data keys (see Table 5.2.12.2.1-1 in [5]). (For Nnef_TrafficInfluence_delete): The NEF deletes the AF requirements in the UDR (data set = application data, data subset = AF traffic impact request information, data key = AF transaction internal ID). The NEF responds to the AF. 3b. NEF provides the results of SFC policy updates in the UDR. 4. PCF(s) subscribed to modifications of AF requests (data set = application data; data subset = AF traffic impact request information, data key = S-NSSAI and DNN and / or internal group identifier or SUPI) receive notification of data change Nudr_DM_Notify from UDR. 5. The PCF determines which existing PDU sessions may be affected by the AF request. For each of these PDU sessions, the PCF updates the SMF with the corresponding new PCC rule(s) by invoking the Npcf_SMPolicyControl_UpdateNotify service operation as described in steps 5 and 6 of clause 4.16.5 of [5]. If the AF request contains a notification report request for a UP path change, the PCF includes in the PCC rule(s) the information required to report the event, such as a Notification Target Address pointing to the NEF or AF and a Notification Correlation ID containing the AF transaction internal ID. 6. When the PCC rule is received from the PCF, the SMF may take appropriate action to reconfigure the user plane of the PDU session, such as: - Adding, replacing, or removing a UPF in a data path, e.g., to act as a UL CL or Branching Point, as described in clause 4.3.5 of [5]. - Allocate a new prefix to the UE (if IPv6 multihoming applies). - Updating the UPF in the target DNAI with new traffic steering rules Subscribe to notifications from AMF for an area of ​​interest via the Namf_EventExposure_Subscribe service operation.

[0071] Embodiment 4: OAM provides SFCF-U configuration information for SFCF-U instances Provisioning the available UPFs in the SMF using the NRF is discussed in clause 6.3.3 of [4] and clause 4.17.6 of [5]. This optional node-level step occurs before selecting a UPF for the PDU session, followed by the N4 node-level procedure specified in clause 4.4.3 of [5], where the UPF and SMF exchange information such as support for optional functionality and capabilities. Optionally, UPF(s) may register with the NRF. This registration phase uses the Nnrf_NFManagement_NFRegister operation and therefore does not use N4. For SMF provisioning of available UPFs, the SMF learns about available UPFs using the Nnrf_NFManagement_NFStatusSubscribe, Nnrf_NFManagement_NFStatusNotify, and Nnrf_NFDiscovery services. The protocol used by UPFs to interact with the NRF is described in TS 29.510. The UPF may be associated with UPF Provisioning Information in the NRF, which includes: - List of (S-NSSAI,DNN) - UE IPv4 address range and / or IPv6 prefix range(s) per (S-NSSAI, DNN), and Note 2: The above information may be used by the SMF for UPF selection when static IP address / prefix allocation is required for the UE. - SMF area identities that the UPF can serve. The SMF area identity allows restricting SMF provisioning of UPF(s) using the NRF to the UPF(s) associated with a specific SMF area identity. This can be used, for example, if the SMF is only allowed to control UPF(s) configured in the NRF as belonging to a specific SMF area identity. - Supported ATSSS steering functionality, i.e., whether MPTCP functionality or ATSSS-LL functionality or both are supported. The SMF area identity and the UE IPv4 address range and / or IPv6 prefix range(s) are optional in the UPF provisioning information. According to embodiment 3 and / or any other embodiment herein, the SFCF-C obtains an SFC configuration from the EAS, the SFC configuration including one or more SFs and corresponding parameters for an SFC service provided by the 5G network. The SFCF-C receiving the SFC parameters for the SFC service configuration can check for existing available SFCF-U instances that have the SFs required for the requested SFC service for a UE, a group of UEs, or any UE, or any UE of an application, or any UE of an SFC service. To obtain an available SFCF-U instance, the SFCF-C provides the following two mechanisms: 1- The SFCF-C requests an SFCF-U instance from the NRF indicating the requirements of one or more supported SFs of the SFCF-C instance. 2-SFCF-C subscribed to the NRF service for notifications of status changes of available SFCF-U NFs. The SFCF-C obtains an available SFCF-U instance with information on one or more supported SFs from the NRF or OAM based on the same procedure as the SMF provisioning of available UPFs using the NRF in clause 4.17.6 of [5], with the SMF replaced by the SFCF-C and the UPF replaced by the SFCF-U.

[0072] The procedure in Figure 19 may operate as follows when the SMF expects to be informed of the UPFs available in the network: 1. The SMF issues an Nnrf_NFManagement_NFStatusSubscribe service operation providing the target UPF provisioning information of interest. The SFCF-C sends an Nnrf_NFManagement_NFStatusSubscribe message to the NRF to subscribe to notifications of available SFCF-Us, where the message may include information of one or more supported SFs of the SFCF-U instance. If the SFCF-C does not provide requirements for the supported SFs of the SFCF-U instance, the NRF notifies all available SFCF-U instances with the supported SFs of the SFCF-U instance in step 7. If the SFCF-C indicates requirements for supported SFs of SFCF-U instances, the NRF advertises only available SFCF-U instances with supported SFs in step 7. 2. The NRF issues a Nnrf_NFManagement_NFStatusNotify with a list of all UPFs that currently satisfy the SMF subscription. This notification indicates the subset of target UPF provisioning information supported by each UPF. The procedure of Figure 19 may operate as follows when a new UPF instance is deployed: 3. A new UPF instance is deployed at any time. When an SFCF-U is deployed, the SFCF-C instance information is provided to OAM by the SFCF-U. 4. The UPF instance is configured with the NRF identity to contact for registration and its UPF provisioning information. The UPF does not need to understand the UPF provisioning information beyond using this information to register in step 5. The OAM configures the SFCF-U instance. 5. The UPF instance issues a Nnrf_NFManagement_NFRegister request operation providing its NF type, the FQDN or IP address of its N4 interface, and the UPF provisioning information configured in step 4. 6. Alternatively (for steps 4 and 5), the OAM registers with the NRF a UPF indicating the same UPF provisioning information as provided in step 5. This configuration mechanism is outside the scope of this specification. 5 or 6. The SFCF-U or OAM registers the SFCF-U instance with the NRF, and the NRF's Nnrf_NFManagement_NFRegister or OAM configuration includes information of one or more supported SFs for the SFCF-U instance. 7. Based on the subscriptions in step 1, the NRF issues Nnrf_NFManagement_NFStatusNotify to all SMFs that have subscriptions that match the UPF provisioning information of the new UPF. The NRF provides the SFCF-C with available SFCF-U information. The SFCF-U information includes one or more supported SFs for the SFCF-U instance.

[0073] h. Embodiment 4.1: OAM configures SFCF-U instance with application information According to step 4 of embodiment 4 and / or any other embodiment herein, the OAM configures the new SFCF-U instance with information of the application indicated by the application ID supported for this SFCF-U instance. - Step 6: The NRF's OAM configuration associates this SFCF-U instance with the application ID and SFC service ID as additional information. - Step 7: If the application ID and SFC service ID are provided in step 6, the NRF provides the application ID and SFC service ID to the SFCF-U in a notification message, for example Nnrf_NFManagement_NFStatusNotify. The SFCF-C configures the SFP based on the SFC service ID, the SFC application ID, and information on the supported SF information of the SFCF-U instance. This embodiment supports coordination between SFC services in edge data networks and SFC services in 5G networks via OAM.

[0074] Embodiment 5: SFC configuration in 3GPP management plane According to embodiment 2 and / or any other embodiment herein, an EAS or EES or SFC network provider providing an SFC service in an SFC network may provide SFC parameters of an SFC service configuration in an SLA with a network operator for the use of 3GPP orchestration and management services for coordination between the SFC service in the edge data network and the SFC service in the 5G network via OAM. i. Embodiment 5.1: OAM configures PCF / SFCF-C According to embodiment 5 and / or any other embodiment herein, based on the SLA for the SFC service in the 5G network, the OAM configures a static SFC configuration in the PCF / SFCF-C to manage the SFC policy. j. Embodiment 5.2: OAM directly configures SMF / SFCF-C

[0075] According to embodiment 5 and / or any other embodiment herein, based on the SLA for the SFC service in the 5G network, the OAM configures the SMF / SFCF-C with the SFC service configuration.

[0076] Embodiment 6: SFCF-C configures SFP to cooperate with SFC network in edge data network

[0077] In accordance with embodiments 5.1, 5.2, 4.1, and / or any other embodiment herein, the SFCF-C may configure an SFP with ordered SFs in each SFCF-U, identified by an SFP ID, configured by one or more SFCF-U instances with different SFs, based on the following information: - SFC Service ID - SFC Application ID - Supported SFCF-U instances - Address information of the ordered SFCF-U(s), e.g., the ingress address and port and egress address and port of each SFCF-U. This embodiment supports coordination between SFC services in edge data networks and SFC services in 5G networks via OAM.

[0078] Service function chaining using service functions and service function paths provided by edge data networks Embodiments are also provided for an SFC network having SFs and SFPs provided by an edge data network, for example, by an edge application service provider or an edge computing service provider.

[0079] Embodiment 7: SFC Enabler in Edge Data Networks This solution proposes a solution that enables service function chaining services in edge data networks, as shown in Figure 20. With SFC services in edge data networks, this solution enables unified orchestration and management support in the 3GPP management plane.

[0080] Figure 20 illustrates a reference architecture including an SFC network within an edge data network (this reference architecture includes partial network functions), according to various embodiments. Service function chaining services are provided in the edge data network by enabling support for a service function chaining network (SFC network), which terminates the N6 reference point with the trusted data network or external data network. Service function chaining policies for steering traffic that needs to traverse a specific service function path (SFP) within the SFC network are: AS, AF, or 3GPP OAM For an application server (AS) in an external data network, the AF can infer traffic routing via the NEF on the N33 interface, for example, toward the SFC network of the edge data network via N6. For an AS in a trusted data network, the AF can directly influence traffic routing via the PCF on the N5 interface, for example, toward the SFC network of the edge data network via N6.

[0081] FIG. 21 further illustrates an edge data network application architecture that enables SFC services over an SFC network, according to various embodiments.

[0082] In Figure 21, an edge application server uses the SFC service provided by the SFC network in the edge data network by using AF inference traffic routing to steer N6 traffic toward the SFC network in the edge data network.

[0083] The SFC network providing the SFC service includes a service function and one or more service function paths in the edge data network, where a traffic classifier terminates N6 in the SFC network to process traffic from the 3GPP network before initiating the SFC service, and a traffic declassifier further combines traffic flows through the same or different SFPs before forwarding the traffic towards the EAS on the EDGE-X interface.

[0084] SFC services may be offered by one or more service providers, including edge service provider(s), edge computing service provider(s), SFC network service provider(s), or network operator(s). Depending on deployment options, SFC network configurations may be supported on EDGE-X and EDGE-Y, and therefore by EAS(s) and EES(s).

[0085] Depending on the business relationship between the edge application service provider or edge computing service provider and the PLMN operator and the deployment scenario, the edge data network can be in a trusted domain or an external data network. The EDGE-2 and EDGE-7 reference points allow the EAS and EES to interact with the PCF directly over the N5 or via the NEF over the N33 interface, respectively. As shown in Figure 20, different deployment options exist for support of AF, including: Embodiment 7.1: The AF is located in an Edge Application Server (EAS) that can interact with the 3GPP network via the EDGE7 reference point. The EAS uses the 5G network capability exposure API to interact directly with the 5GC, and / or Embodiment 7.2: The AF is in an edge enabler server (EES) that can interact with the 5G network through the EDGE2 reference point. The EES further uses a 5G network capability exposure API to provide the EAS with an EES capability exposure API for interacting with the 5GC. For example, the EAS uses an edge enabler server capability exposure API, such as a Nnef_trafficInferencing_Create / Update / Delecte message, to trigger the 5G network capability exposure API for interacting with the 5GC, to request the required information for triggering AF inference traffic routing from the AF in the edge enabler server.

[0086] Embodiment 8: Application architecture with support for SFC networks in edge data networks According to embodiment 7, the SFC network includes a traffic classifier, a traffic declassifier, and an SF, which can process one or more SFPs. Each SFP includes ordered SFs through which traffic needs to pass. The one or more SFs can be provided by the same or different service providers, for example, edge application service provider(s), edge computing service provider(s), SFC service provider(s), or network operator(s). Depending on the deployment option, the SFC network configuration can be supported on EDGE-X and EDGE-Y accordingly.

[0087] EDGE-X is the interface between the SF / traffic classifier / traffic declassifier and the EAS in the SFC network. EDGE-Y is the interface between the SF / traffic classifier / traffic declassifier and the EES in the SFC network. The traffic classifier and traffic declassifier have traffic filtering policies to classify and combine the traffic flows of each SFP before and after SFP processing, respectively.

[0088] For traffic flows that do not have an assigned SFP, all SFs in the SFC network are skipped.

[0089] As mentioned above, Figure 9 depicts an example SFC network of an edge data network having one or more SFPs. In particular, Figure 9 shows an example SFC network having a traffic classifier, a traffic declassifier, one or more SFs, and an SFP, where traffic flows within each SFP are transported through ordered service functions.

[0090] SF can be, but is not limited to, one of the following functions: - Network Address Translation (NAT), - IP tunnel endpoints, - packet classifier, - Deep Packet Inspection (DPI), - Legal Inspection (LI), - TCP proxy, - load balancer, - Firewall functionality, - transcoder, - URL filters, - Application Detection and Control (ADC), - Video Optimizer.

[0091] Embodiment 9: SFC parameters for SFC network configuration According to embodiment 8, the SFC parameters of the SFC service may include the following information: - SFC network configuration :Define the following SFC parameters for the SFC service: SFC Service ID: Service ID of one set of SFC parameters for the SFC service SFC configuration: one or more SFs with corresponding SF parameters and SF address information SFP Configuration: Indicates the SFP index with the corresponding ordered SF for one or more traffic rules configured in the traffic classifier. SFC routing policy: - A traffic classifier indicates a mapping between an SFP index and a traffic filtering rule for forwarding traffic to the first SF in the SFP identified by the SFP index. - The traffic declassifier indicates the traffic filter rules for combining traffic from the last SF in the SFP identified by the SFP index. Validity parameters for the SFC service identified by the SFC service ID, e.g.: - Duration - A scheduled time period, for example, 8am-8pm every day. - Application ID(s) - PDU session type, e.g., IP / Ethernet / Unstructured, DNN, or associated PDU session parameters, including slice / service type (SST) (e.g., eMBB, URLLC, MIoT, V2X, etc.) and optional slice differentiators (SD)

[0092] The traffic classifier provides the SFP index along with a mapping to an SFC classification policy based on different levels or granularity per packet, including one or more of the following information, for example: - UE address - Application ID - Media Type - Traffic Priority

[0093] DPI capabilities in traffic classifiers are necessary when information is only available in the traffic payload.

[0094] The traffic declassifier provides an "Edge Application Server ID (EAS ID)" that identifies the target edge application server terminating the EDGE-X reference point to combine traffic from one or more SFPs before forwarding to the application server of the application, along with a mapping to an SFC reclassification policy that includes one or more of the following information, for example: - UE address - Application ID - Media Type - Traffic Priority - SFP Index

[0095] DPI capabilities in the traffic declassifier are necessary when information is only available in the traffic payload.

[0096] Embodiment 10: Edge Application Server Provider (EASP) provides SFC services According to embodiment 9, the EASP provides SFC services to edge application servers in an edge data network. The EASP may use one of its EAS(s) to provision the SFC parameters of the SFC network for SFC services over the EDGE-X interface. - Furthermore, based on the EES API to the EAS and the 5GC network capability exposure API to the EES, the EAS can request the edge enabler server to trigger AF inference traffic routing towards the SFC network.

[0097] Additionally, the SFC service may be provided by the SFC network service provider to the EASP of the edge data network based on an SLA between the SFC network service provider and the EASP.

[0098] Figure 22 illustrates an exemplary procedure according to various embodiments, including a message flow for SFC configuration and AF requests to interfere with traffic routing.

[0099] The procedure of FIG. 22 may operate as follows: Step 1: The edge application server sends an SFC configuration request including SFC parameters with its EAS ID for controlling and configuring SFs and SFPs in the SFC network, and a transaction ID for identifying this request message. In addition, the request message may indicate the creation, update, or deletion of an SFC parameter configuration. Step 2: The SFC network returns an SFC configuration response message (result) to the edge application server regarding the results of the SFC and SFP. Step 3: The edge application server uses the EES capability exposure API to the EAS to request 5G network capability exposure from the AF in the EES to infer traffic routing on the N6 tunnel between the UPF and the SFC network. In addition, the request message may indicate a create, update, or delete AF request to infer traffic routing. Step 4: The edge enabler server uses the AF to trigger the AF inference traffic routing procedure, as shown in embodiment 7. Step 5: The edge enabler server responds with the result of the AF inference traffic routing request. Step 6: Traffic can begin to travel between the UPF and the edge application server over the SFC network.

[0100] Embodiment 11: An edge computing service provider (ECSP) provides SFC services in an edge data network.

[0101] According to embodiment 10, the ECSP provides SFC services to the edge application server via an edge enabler server in the edge data network. Based on the EES API to the EAS for provisioning SFC parameters for SFC services on the EDGE-3 interface, the Edge Enabler Server can trigger an SFC configuration request message to control and configure SFC in the SFC network on the new interface EDGE-Y. - Furthermore, based on the EES API to the EAS and the 5GC network capability exposure API to the EES, the edge enabler server can trigger an AF request to trigger AF inference traffic routing towards the SFC network.

[0102] Additionally, the SFC service may be provided by the SFC network service provider to the ECSP of the edge data network based on an SLA between the SFC network service provider and the ECSP.

[0103] 23 illustrates an exemplary procedure according to various embodiments. Figure 23 includes a message flow for SFC configuration and AF requests to interfere with traffic routing. The procedure of Figure 23 may operate as follows: Step 1: In step 1a, the edge application server sends an SFC configuration request including SFC parameters for controlling and configuring SFs and SFPs in the SFC network via the EES capability exposure API to the EAS. In step 1b, the edge enabler server generates a transaction ID and forwards an SFC configuration request message indicating the SFC parameters and the transaction ID to the SFC network. In addition, the request message may indicate the creation, update, or deletion of an SFC parameter configuration. Step 2: In step 2a, the SFC network returns an SFC configuration response message to the edge application server, indicating the transaction ID and the result of the SFC parameter configuration of the SFC and SFP. In step 2b, the edge enabler server forwards the SFC configuration response message with the result of the SFC configuration to the requested edge application server. Step 3: The edge application server uses the EES capability exposure API to the EAS provided by the edge enabler server to request 5G network capability exposure from the AF in the EES to infer traffic routing on the N6 tunnel between the UPF and the SFC network. In addition, the request message may indicate a create, update, or delete AF request to infer traffic routing. Step 4: The edge enabler server uses the AF to trigger the AF inference traffic routing procedure, as shown in embodiment 13. Step 5: The edge enabler server responds with the result of the AF inference traffic routing request. Step 6: Traffic can begin to travel between the UPF and the edge application server over the SFC network.

[0104] Embodiment 12: SFC configuration in 3GPP management plane According to embodiment 10 or 11, an EAS or EES or SFC network provider providing SFC services in an SFC network can provide SFC parameters of the SFC network in an SLA with a network operator for SFC configuration using 3GPP orchestration and management services.

[0105] Embodiment 13: EAS triggered AF inference traffic routing in 5GS (with DPI capability) According to embodiments 10, 11, and / or 12, the EAS sends an AF inference traffic routing request message (EAS ID and AF request) directly through the AF or through the AF of the edge enabler server over EDGE-3 and N33.

[0106] For traffic filtering information in the AF request, if the UPF / PSA requires DPI (Deep Packet Inspection) functionality, the DPI indicator is provided with DPI rules and policies for traffic classification based on information contained in, for example, packet headers or packet payloads, and the DPI policies are configured to classify network traffic flows toward the indicated N6 tunnel based on the N6 traffic routing information.

[0107] For example, a DPI policy can be configured to classify different priority traffic based on packet payload information, allowing high priority traffic to pass through the N6 tunnel with higher throughput.

[0108] For example, a DPI policy may be configured to classify different media types based on packet payload information and allow traffic having different media types to pass through different N6 tunnels with different throughputs.

[0109] Embodiment 13.1 According to embodiment 13, and referring to clause 5.6.7 of TS23.501 and clause 4.3.6 of TS23.502, the AF request for N6 traffic routing toward the SFC network may include the following information: - AF Transaction Identifier: Provided to reference the AF request. - DNN and one or more DNAI(s): Provided to identify an edge data network, where the DN Access Identifier (DNAI) is an identifier of user plane access to one or more DN(s) where applications are deployed. A PLMN supporting edge computing services provides connectivity to edge application servers located in the EDN, each corresponding to one or more DNAI(s). - One or more N6 traffic routing information for each DNAI for the N6 tunnel: provided to steer traffic towards edge application servers in the SFC network and edge data network, where the address information includes IP addresses and port numbers for IP packets and / or Ethernet MAC addresses for Ethernet traffic. - Traffic description for each N6 traffic routing information: Provided to identify the target traffic to be affected, which can be represented by a combination of DNN and optionally S-NSSAI and traffic filtering information based on application identifier (APP-ID) or IP / Ethernet packet header information. - Target UE Identifier(s): Provided to indicate the UE(s) that are the target of the AF request, which can be represented by a GPSI for an individual UE, or an external group identifier for a group of UEs, or any UE that has access to a combination of DNN, S-NSSAI, and DNAI(s).

[0110] Embodiment 13.2: Additional information in AF requests According to embodiment 13.1, the following additional information may be provided: - Spatial Validity Condition: Provided to indicate that the request applies only to the traffic of UE(s) located within a specified location represented by a list of validity area or geographical zone identifier(s). - Temporal validity condition: provided to indicate the time interval(s) or duration(s) for carrying out an inference request from the AF.

[0111] 1. System and Implementation 24-26 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.

[0112] 24 illustrates a network 2400 according to various embodiments. Network 2400 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this respect, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0113] The network 2400 may include a UE 2402, which may include any mobile or non-mobile computing device designed to communicate with the RAN 2404 over a wireless connection. The UE 2402 may be communicatively coupled to the RAN 2404 by a Uu interface. The UE 2402 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a head-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networking device, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0114] In some embodiments, the network 2400 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH.

[0115] In some embodiments, the UE 2402 may additionally communicate with the AP 2406 via an over-the-air connection. The AP 2406 may manage the WLAN connection, which may serve to offload some / all network traffic from the RAN 2404. The connection between the UE 2402 and the AP 2406 may conform to any IEEE 802.2.11 protocol, where the AP 2406 may be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, the UE 2402, RAN 2404, and AP 2406 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may include the UE 2402 being configured by the RAN 2404 to utilize both cellular radio resources and WLAN resources.

[0116] The RAN 2404 may include one or more access nodes, such as the AN 2408. The AN 2408 may terminate air interface protocols for the UE 2402 by providing access stratum protocols, including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 2408 may enable data / voice connectivity between the CN 2420 and the UE 2402. In some embodiments, the AN 2408 may be implemented as a separate device or as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN or virtual baseband unit pool, for example. The AN 2408 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 2408 may be a macrocell base station or a low-power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0117] In embodiments where the RAN 2404 includes multiple ANs, they may be coupled to one another via an X2 interface (if the RAN 2404 is an LTE RAN) or an Xn interface (if the RAN 2404 is a 5G RAN). In some embodiments, the X2 / Xn interface, which may be separated into control / user plane interfaces, may allow the ANs to communicate information regarding handover, data / context transfer, mobility, load management, interference coordination, etc.

[0118] Each AN of the RAN 2404 may manage one or more cells, cell groups, component carriers, etc. to provide the UE 2402 with an air interface for network access. The UE 2402 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 2404. For example, the UE 2402 and the RAN 2404 may use carrier aggregation to enable the UE 2402 to connect with multiple component carriers, each corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0119] The RAN 2404 may provide an air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques using PCell / SCell. Before accessing the unlicensed spectrum, the node may perform a medium / carrier sensing operation, for example, based on a listen-before-talk (LBT) protocol.

[0120] In a V2X scenario, the UE 2402 or AN 2408 may be or function as an RSU, which may refer to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in or by an appropriate AN or a fixed (or relatively fixed) UE. An RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an eNB may be referred to as an “eNB-type RSU,” a gNB may be referred to as a “gNB-type RSU,” and so on. In one example, the RSU is a computing device coupled with radio frequency circuits located on the roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for detecting and controlling ongoing vehicular and pedestrian traffic. The RSU may provide very low-latency communications necessary for high-speed events such as collision avoidance and traffic warnings. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be housed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0121] In some embodiments, the RAN 2404 may be an LTE RAN 2410 having an eNB, such as eNB 2412. The LTE RAN 2410 may provide an LTE air interface with characteristics such as a 15 kHz SCS; a CP-OFDM waveform for DL ​​and an SC-FDMA waveform for UL; turbo codes for data and TBCC for control. The LTE air interface may rely on a CSI-RS for CSI acquisition and beam management; a PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and a CRS for channel estimation for cell search and initial acquisition, channel quality measurements, and coherent demodulation / detection at the UE. The LTE air interface may operate on sub-6 GHz bands.

[0122] In some embodiments, the RAN 2404 may be an NG-RAN 2414 having a gNB, such as, for example, a gNB 2416, or an ng-eNB, such as, for example, an ng-eNB 2418. The gNB 2416 may connect to a 5G-capable UE using a 5G NR interface. The gNB 2416 may connect to a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 2418 may also connect to the 5G core through an NG interface, but may connect to a UE via an LTE air interface. The gNB 2416 and the ng-eNB 2418 may connect to each other over an Xn interface.

[0123] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface (e.g., N3 interface), which carries traffic data between nodes in the NG-RAN 2414 and nodes in the UPF 2448, and an NG Control Plane (NG-C) interface (e.g., N2 interface), which is the signaling interface between nodes in the NG-RAN 2414 and nodes in the AMF 2444.

[0124] The NG-RAN 2414 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL ​​and CP-OFDM and DFT-s-OFDM for UL; polar, repetitive, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface, like the LTE air interface, may rely on CSI-RS and PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for PDSCH phase tracking, and tracking reference signals for time tracking. The 5G-NR air interface may operate on the FR1 band, which includes sub-6 GHz bands, or the FR2 band, which includes bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid that includes PSS / SSS / PBCH.

[0125] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of the SCS. For example, a UE 2402 may be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 2402, the SCS of the transmission is also changed. Another example use case of BWPs relates to power conservation. In particular, multiple BWPs may be configured for a UE 2402 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP with a smaller number of PRBs may be used for data transmission with a light traffic load while enabling power conservation at the UE 2402 and, potentially, at the gNB 2416. A BWP with a larger number of PRBs may be used for scenarios with higher traffic loads.

[0126] The RAN 2404 is communicatively coupled to the CN 2420, which includes network elements for providing various functions to customers / subscribers (e.g., users of UEs 2402) to support data and telecommunication services. The components of the CN 2420 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 2420 onto physical compute / storage resources within servers, switches, etc. A logical instantiation of the CN 2420 may be referred to as a network slice, and a logical instantiation of a portion of the CN 2420 may be referred to as a network sub-slice.

[0127] In some embodiments, the CN 2420 may be an LTE CN 2422, which may also be referred to as an EPC. The LTE CN 2422 may include an MME 2424, an SGW 2426, an SGSN 2428, an HSS 2430, a PGW 2432, and a PCRF 2434 coupled to each other over interfaces (or "reference points") as shown. The functionality of the elements of the LTE CN 2422 may be briefly introduced as follows.

[0128] The MME 2424 may implement mobility management functions to track the current location of the UE 2402 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0129] The SGW 2426 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 2422. The SGW 2426 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0130] The SGSN 2428 may track the location of the UE 2402 and perform security functions and access control. In addition, the SGSN 2428 may perform inter-EPC node signaling for mobility between different RAT networks, PDN and S-GW selection as specified by the MME 2424, MME selection for handover, etc. The S3 reference point between the MME 2424 and the SGSN 2428 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active state.

[0131] The HSS 2430 may include a database for network users, including subscription-related information to support network entity handling of communication sessions. The HSS 2430 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. An S6a reference point between the HSS 2430 and the MME 2424 may enable the transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 2420.

[0132] The PGW 2432 may terminate an SGi interface toward a data network (DN) 2436, which may include an application / content server 2438. The PGW 2432 may route data packets between the LTE CN 2422 and the data network 2436. The PGW 2432 may be coupled to the SGW 2426 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 2432 may further include a node (e.g., PCEF) for policy enforcement and charging data collection. Additionally, the SGi reference point between the PGW 2432 and the data network 2436 may be, for example, an operator-external public, private PDN, or an intra-operator packet data network for provisioning of IMS services. The PGW 2432 may be coupled to the PCRF 2434 via a Gx reference point.

[0133] The PCRF 2434 is the policy and charging control element of the LTE CN 2422. The PCRF 2434 may be communicatively coupled to an app / content server 2438 to determine appropriate QoS and charging parameters for a service flow. The PCRF 2432 may provision the associated rules (via the Gx reference point) to the PCEF with the appropriate TFT and QCI.

[0134] In some embodiments, CN2420 may be 5GC2440. 5GC2440 may include AUSF2442, AMF2444, SMF2446, UPF2448, NSSF2450, NEF2452, NRF2454, PCF2456, UDM2458, and AF2460 coupled together over interfaces (or "reference points") as shown. The functionality of the elements of 5GC2440 may be briefly introduced as follows.

[0135] The AUSF 2442 may store data and process authentication-related functionality for authentication of the UE 2402. The AUSF 2442 may facilitate a common authentication framework for various access types. As shown, in addition to communicating with other elements of the 5GC 2440 over reference points, the AUSF 2442 may expose a Nausf service-based interface.

[0136] The AMF 2444 may enable other functions of the 5GC 2440 to communicate with the UE 2402 and the RAN 2404 and subscribe to notifications about mobility events related to the UE 2402. The AMF 2444 may be responsible for registration management (e.g., for registering the UE 2402), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 2444 may provide transport for SM messages between the UE 2402 and the SMF 2446 and act as a transparent proxy for routing SM messages. The AMF 2444 may also provide transport for SMS messages between the UE 2402 and the SMSF. The AMF 2444 may interact with the AUSF 2442 and the UE 2402 to perform various security anchor and context management functions. Additionally, the AMF 2444 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the RAN 2404 and the AMF 2444; the AMF 2444 may be the termination point of the NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 2444 may also support NAS signaling with the UE 2402 over the N3 IWF interface.

[0137] The SMF 2446 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 2448 and the AN 2408); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering in the UPF 2448 to route traffic to the appropriate destination; terminating the interface towards the policy control function; controlling policy enforcement, charging, and parts of QoS; lawful intercept (for SM events and the interface to the L1 system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent over N2 to the AN 2408 via the AMF 2444; and determining the SSC mode of the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 2402 and the data network 2436.

[0138] The UPF 2448 may function as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 2436, and a branch point for supporting multi-homed PDU sessions. The UPF 2448 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic validation (e.g., SDF to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering. The UPF 2448 may include an uplink classifier to support routing of traffic flows to the data network.

[0139] The NSSF 2450 may select a set of network slice instances to serve the UE 2402. The NSSF 2450 may also determine the allowed NSSAIs and their mapping to subscribed S-NSSAIs, if necessary. The NSSF 2450 may also determine an AMF set, or a list of candidate AMFs, to be used to serve the UE 2402 based on an appropriate configuration and possibly by querying the NRF 2454. The selection of a set of network slice instances for the UE 2402 may be triggered by the AMF 2444 to which the UE 2402 is registered by interacting with the NSSF 2450, which may cause an AMF change. The NSSF 2450 may interact with the AMF 2444 via the N22 reference point and may communicate with another NSSF in a visited network via the N31 reference point (not shown). Additionally, the NSSF 2450 may exhibit an Nnssf service-based interface.

[0140] The NEF 2452 may securely expose services and capabilities offered by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g., AF 2460), edge computing or fog computing systems, etc. In such embodiments, the NEF 2452 may authenticate, authorize, or throttle AFs. The NEF 2452 may also translate information exchanged with the AF 2460 and with internal network functions. For example, the NEF 2452 may translate between AF service identifiers and internal 5GC information. The NEF 2452 may receive information from other NFs based on the other NFs' exposed capabilities. This information may be stored in the NEF 2452 as structured data or in a data storage NF using a standardized interface. The stored information may then be exposed again by the NEF 2452 to other NFs and AFs or used for other purposes, such as analytics. Additionally, the NEF 2452 may exhibit an NEF service-based interface.

[0141] The NRF 2454 supports service discovery functionality, receives NF discovery requests from NF instances, and can provide information about discovered NF instances to the NF instances. The NRF 2454 also maintains information about available NF instances and their supported services. As used herein, terms such as "instantiate" and "instantiation" may refer to the creation of an instance, and "instance" may refer to a specific occurrence of an object that may occur, for example, during the execution of program code. Additionally, the NRF 2454 may present an Nnrf service-based interface.

[0142] The PCF 2456 may provide policy rules and control plane functions to enforce them, and may support a unified policy framework to govern network behavior. The PCF 2456 may also implement a front end for accessing subscription information related to policy decisions within the UDRs of the UDM 2458. In addition to communicating with functions over reference points as shown, the PCF 2456 exposes an Npcf service-based interface.

[0143] The UDM 2458 may process subscription-related information to support network entity processing of communication sessions and may store subscription data for the UE 2402. For example, the subscription data may be communicated via the N8 reference point between the UDM 2458 and the AMF 2444. The UDM 2458 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 2458 and the PCF 2456, and / or application data (including PFDs for application discovery, application requirement information for multiple UEs 2402) and structured data for exposure for the NEF 2452. A Nudr service-based interface may be exposed by the UDR 221 to enable the UDM 2458, PCF 2456, and NEF 2452 to access specific sets of stored data and to read, update (e.g., add, modify), delete, and subscribe to notifications of changes to associated data in the UDR. The UDM may include a UDM-FE responsible for credential processing, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 2458 may expose a Nudm service-based interface.

[0144] The AF 2460 provides application influence over traffic routing, provides access to the NEF, and may interact with the policy framework for policy control.

[0145] In some embodiments, the 5GC 2440 may enable edge computing by selecting operator / third-party services to be geographically close to the point where the UE 2402 connects to the network. This may reduce latency and load on the network. To provide an edge computing implementation, the 5GC 2440 may select a UPF 2448 close to the UE 2402 and perform traffic steering from the UPF 2448 to the data network 2436 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 2460. In this way, the AF 2460 may influence UPF (re)selection and traffic routing. Based on the operator's deployment, if the AF 2460 is considered a trusted entity, the network operator may allow the AF 2460 to interact directly with associated NFs. Additionally, the AF 2460 may exhibit a NAF service-based interface. The data network 2436 may represent various network operator services, Internet access, or third-party services, which may be provided by one or more servers, including, for example, the application / content server 2438.

[0146] FIG. 25 schematically illustrates a wireless network 2500 according to various embodiments. The wireless network 2500 may include a UE 2502 in wireless communication with an AN 2504. The UE 2502 and the AN 2504 are similar to similarly named components described elsewhere herein and may be substantially interchangeable. The UE 2502 may be communicatively coupled to the AN 2504 via a connection 2506. The connection 2506 is illustrated as an air interface for enabling the communicative coupling and may correspond to a cellular communication protocol, such as a 5G NR protocol or an LTE protocol operating in mmWave or sub-6 GHz frequencies. The UE 2502 may include a host platform 2508 coupled to a modem platform 2510. The host platform 2508 may include an application processing circuit 2512 that may be coupled to a protocol processing circuit 2514 of the modem platform 2510. The application processing circuit 2512 may execute various applications for the UE 2502 to source / sink application data. The application processing circuit 2512 may further implement one or more layer operations for sending / receiving application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

[0147] The protocol processing circuit 2514 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 2506. The layer operations implemented by the protocol processing circuit 2514 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations. The modem platform 2510 may further include a digital baseband circuit 2516 that may implement one or more layer operations that are “lower” layer operations performed by the protocol processing circuit 2514 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding which may include one or more of space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions. The modem platform 2510 may further include transmit circuitry 2518, receive circuitry 2520, RF circuitry 2522, and an RF front end (RFFE) 2524 that may include or connect to one or more antenna panels 2526. Briefly, the transmit circuitry 2518 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc., the receive circuitry 2520 may include analog-to-digital converters, mixers, IF components, etc., the RF circuitry 2522 may include low noise amplifiers, power amplifiers, power tracking components, etc., and the RFFE 2524 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the transmit circuitry 2518, receive circuitry 2520, RF circuitry 2522, RFFE 2524, and antenna panel 2526 components (collectively referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether communication is TDM or FDM, mmWave frequencies or sub-6 GHz frequencies, etc.In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be located on the same or different chips / modules, etc.

[0148] In some embodiments, the protocol processing circuit 2514 may include one or more instances of control circuitry (not shown) to provide control functions to the transmit / receive components. UE reception may be established by and through the antenna panel 2526, the RFFE 2524, the RF circuitry 2522, the receive circuitry 2520, the digital baseband circuitry 2516, and the protocol processing circuit 2514. In some embodiments, the antenna panel 2526 may receive transmissions from the AN 2504 by way of receive beamforming signals that are received by multiple antennas / antenna elements of one or more antenna panels 2526.

[0149] UE transmissions may be established by and through the protocol processing circuitry 2514, the digital baseband circuitry 2516, the transmit circuitry 2518, the RF circuitry 2522, the RFFE 2524, and the antenna panel 2526. In some embodiments, the transmit components of the UE 2504 may apply spatial filters to data to be transmitted to form transmit beams emitted by the antenna elements of the antenna panel 2526. Similar to the UE 2502, the AN 2504 may include a host platform 2528 coupled to a modem platform 2530. The host platform 2528 may include an application processing circuitry 2532 coupled to the protocol processing circuitry 2534 of the modem platform 2530. The modem platform may further include a digital baseband circuitry 2536, a transmit circuitry 2538, a receive circuitry 2540, an RF circuitry 2542, an RFFE circuitry 2544, and the antenna panel 2546. The components of AN 2504 may be similar to, and substantially interchangeable with, similarly named components of UE 2502. In addition to performing data transmission / reception as described above, the components of AN 2508 may perform various logical functions, including RNC functions such as, for example, radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0150] Figure 26 is a block diagram illustrating components that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein, according to some demonstrative embodiments. Specifically, Figure 26 shows a diagrammatic representation of hardware resources 2600, including one or more processors (or processor cores) 2610, one or more memory / storage devices 2620, and one or more communication resources 2630, each of which may be communicatively coupled via a bus 2640 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 2602 may execute to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 2600.

[0151] Processor 2610 may include, for example, processor 2612 and processor 2614. Processor 2610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0152] The memory / storage device 2620 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 2620 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0153] Communications resources 2630 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 2604 or one or more databases 2606 or other network elements over network 2608. For example, communications resources 2630 may include wired communications components (e.g., for coupling via USB, Ethernet, etc.), cellular communications components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communications components.

[0154] The instructions 2650 may include software, programs, applications, applets, apps, or other executable code for causing at least one of the processors 2610 to perform any one or more of the methodologies discussed herein. The instructions 2650 may reside, completely or partially, within at least one of the processors 2610 (e.g., in a processor's cache memory), the memory / storage device 2620, or any suitable combination thereof. Furthermore, any portion of the instructions 2650 may be transferred to the hardware resources 2600 from any combination of the peripheral device 2604 or the database 2606. Thus, the processor's memory 2610, the memory / storage device 2620, the peripheral device 2604, and the database 2606 are examples of computer-readable and machine-readable media.

[0155] Example Procedure In some embodiments, the electronic device(s), network(s), system(s), chip(s), or component(s) of FIGS. 24-26 or some other figures herein, or portions or implementations thereof, may be configured to perform one or more processes, techniques, or methods described herein, or portions thereof. For example, FIG. 27 shows process 2700 according to various embodiments. At 2702, process 2700 may include receiving configuration information for a service function path (SFP) that specifies one or more ordered service functions for service function chaining (SFC). At 2704, process 2700 may further include configuring the SFP based on the configuration information to coordinate with an SFC function in the edge data network to provide the one or more ordered service functions via the SFP across the wireless cellular network and the edge data network. In some embodiments, process 2700 may be performed by an SFC control plane function (SFCF-C) or portion thereof.

[0156] 28 shows another process 2800 according to various embodiments. At 2802, process 2800 may include receiving a request from a service function chaining (SFC) control plane function (SFCF-C) for information associated with one or more SFC user plane function (SFCF-U) instances supporting one or more ordered service functions associated with a service function path. At 2804, process 2800 may further include sending the information associated with the one or more SFCF-U instances to the SFCF-C. In some embodiments, process 2800 may be performed by an operations, administration, and maintenance (OAM) entity or a portion thereof.

[0157] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the exemplary section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below. For another example, circuitry associated with a UE, a base station, a network element, etc., as described above in connection with one or more of the preceding figures, may be configured to operate according to one or more of the examples described in the exemplary section below.

[0158] Example Additional examples of the presently described embodiments include the following non-limiting implementations, each of which may stand alone or may be combined in any permutation or combination with any one or more of the other examples provided below or throughout this disclosure.

[0159] Example A01 includes a method for enabling coordination of service function chaining services in a 5G system and an edge data network.

[0160] Example A02 includes the method of example A01 and / or some other example(s) herein, wherein the SFC service in the edge data network can be provided by an edge service provider or an edge computing service provider or an SFC network provider, which can include SFC parameters of the SFC service configuration in an SLA (service level agreement) with the network operator for use of 3GPP orchestration and management services.

[0161] Example A03 includes the method of example A02 and / or some other example(s) herein, wherein based on an SLA for an SFC service in a 5G network, the OAM configures a static SFC configuration in the PCF / SFCF-C to manage the SFC policy.

[0162] Example A04 includes the method of example A02 and / or some other example(s) herein, wherein based on an SLA for an SFC service in a 5G network, the OAM configures the SMF / SFCF-C with the SFC service configuration.

[0163] Example A05 includes the method of examples A03-A04 and / or some other example(s) herein, wherein the SFCF-C configures the SFP to cooperate with the SFC network in the edge data network.

[0164] Example A06 includes the method of example A05 and / or some other example(s) herein, wherein the SFP is identified by an SFP ID configured by one or more SFCF-U instances having different SFs based on information such as an SFC service ID, an SFC application ID, supported SFs of the SFCF-U instance, and address information of the ordered SFCF-U(s), e.g., an ingress address and port and an egress address and port of each SFCF-U.

[0165] Example A07 includes the method of example A01 and / or some other example(s) herein, wherein the SFCF-C obtains from the EAS an SFC configuration including one or more SFs and corresponding parameters for an SFC service provided by the 5G network.

[0166] Example A08 includes the method of example A07 and / or some other example(s) herein, wherein the SFCF-C receiving the SFC parameters for the SFC service configuration can check an existing available SFCF-U instance having the SF required for the requested SFC service for the UE, a group of UEs, or any UE, or any UE of the application, or any UE of the SFC service.

[0167] Example A09 includes the method of example A08 and / or some other example(s) herein, wherein the SFCF-C obtains an available SFCF-U instance by requesting an SFCF-U instance from the NRF, the SFCF-C instance indicating requirements of one or more supported SFs of the SFCF-C instance.

[0168] Example A10 includes the method of example A08 and / or some other example(s) herein, wherein the SFCF-C subscribed to the NRF service for notification of status changes of available SFCF-U NFs.

[0169] Example A11 includes the method of examples A09-A10 and / or some other example(s) herein, wherein the SFCF-C obtains, from the NRF or OAM, an available SFCF-U instance having one or more supported SF information.

[0170] Example A12 includes the method of example A11 and / or some other example(s) herein, wherein the OAM configures the SFCF-U instance.

[0171] Example A13 includes the method of example A12 and / or some other example(s) herein, wherein the OAM configuration of the NRF includes information of one or more supported SFs for the SFCF-U instance.

[0172] Example A13 includes the method of example A13 and / or some other example(s) herein, wherein the SFCF-U or OAM registers the SFCF-U instance with the NRF, and the NRF's Nnrf_NFManagement_NFRegister or OAM configuration includes information of one or more supported SFs for the SFCF-U instance.

[0173] Example A15 includes the method of example A14 and / or some other example(s) herein, wherein the NRF provides available SFCF-U information to the SFCF-C, the SFCF-U information including one or more supported SFs of the SFCF-U instance.

[0174] Example A16 includes the method of example A12 and / or some other example(s) herein, wherein the OAM configures a new SFCF-U instance with information of an application indicated by an application ID supported for the SFCF-U instance.

[0175] Example A17 includes the method of example A16 and / or some other example(s) herein, wherein the OAM configuration of the NRF associates this SFCF-U instance with an application ID and an SFC service ID as additional information.

[0176] Example A18 includes the method of example A17 and / or some other example(s) herein, wherein if an application ID and an SFC service ID are provided in step 6, the NRF provides the application ID and the SFC service ID to the SFCF-U in a notification message, for example, Nnrf_NFManagement_NFStatusNotify.

[0177] Example A19 includes the method of example A15, A18 and / or some other example(s) herein, wherein the SFCF-C configures the SFP based on information about the SFC service ID, the SFC application ID, and the supported SF information of the SFCF-U instance.

[0178] Example B01 includes a method for coordinating service function chaining (SFC) services in a 5G system (5GS) and an edge data network (EDN), the method including steps of instructing, by an SFC user plane function (SFCF-U) and an SFC control plane function (SFCF-C), support for an SFC enabler in the control plane and user plane of the 5G network, respectively.

[0179] Example B02 includes the method of example B01 and / or some other example(s) herein, wherein the SFC service in the EDN is provided by an edge service provider, an edge computing service provider, or an SFC network provider, which may include SFC parameters of the SFC service configuration in an SLA (service level agreement) with the network operator for use of 3GPP orchestration and management services.

[0180] Example B03 includes the method of example B02 and / or some other example(s) herein, wherein based on an SLA for an SFC service in the 5G network, the OAM configures a static SFC configuration in the PCF / SFCF-C to manage the SFC policy.

[0181] Example B04 includes the method of Examples B02-B03 and / or some other example(s) herein, wherein the OAM configures the SFCF-C with an SFC service configuration based on the SLA for the SFC service in 5GS.

[0182] Example B05 includes the method of examples B03-B04 and / or some other example(s) herein, wherein the SFCF-C configures the SFP to cooperate with the SFC network in the EDN.

[0183] Example B06 includes the method of example B05 and / or some other example(s) herein, wherein the SFP is identified by an SFP ID configured by one or more SFCF-U instances having different SFs based on information such as an SFC service ID, an SFC application ID, supported SFs of the SFCF-U instance, and address information of the ordered SFCF-U(s) (e.g., an ingress address and port and an egress address and port of each SFCF-U).

[0184] Example B07 includes the method of Examples B01-B06 and / or some other example(s) herein, wherein the SFCF-C obtains from the EAS an SFC configuration including one or more SFs and corresponding parameters for an SFC service provided by the 5G network.

[0185] Example B08 includes the method of example B07 and / or some other example(s) herein, wherein the SFCF-C receiving the SFC parameters for the SFC service configuration can check an existing available SFCF-U instance having the SF required for the requested SFC service for the UE, a group of UEs, or any UE, or any UE of the application, or any UE of the SFC service.

[0186] Example B09 includes the method of example B08 and / or some other example(s) herein, wherein the SFCF-C obtains an available SFCF-U instance by requesting an SFCF-U instance from the NRF, the SFCF-C instance indicating requirements of one or more supported SFs of the SFCF-C instance.

[0187] Example B10 includes the method of Examples B08-B09 and / or some other example(s) herein, wherein the SFCF-C subscribed to the NRF service for notification of status changes of available SFCF-U NFs.

[0188] Example B11 includes the method of examples B09-B10 and / or some other example(s) herein, wherein the SFCF-C obtains, from the NRF or OAM, an available SFCF-U instance having one or more supported SF information.

[0189] Example B12 includes the method of example B11 and / or some other example(s) herein, wherein the OAM configures the SFCF-U instance.

[0190] Example B13 includes the method of example B12 and / or some other example(s) herein, wherein the OAM configuration of the NRF includes information of one or more supported SFs for the SFCF-U instance.

[0191] Example B14 includes the method of example B13 and / or some other example(s) herein, wherein the SFCF-U or OAM registers the SFCF-U instance with the NRF, and the NRF's Nnrf_NFManagement_NFRegister or OAM configuration includes information of one or more supported SFs for the SFCF-U instance.

[0192] Example B15 includes the method of example B14 and / or some other example(s) herein, wherein the NRF provides available SFCF-U information to the SFCF-C, the SFCF-U information including one or more supported SFs of the SFCF-U instance.

[0193] Example B16 includes the method of Examples B12-B15 and / or some other example(s) herein, wherein the OAM configures the new SFCF-U instance with information of an application indicated by an application ID supported for the SFCF-U instance.

[0194] Example B17 includes the method of example B16 and / or some other example(s) herein, wherein the OAM configuration of the NRF associates this SFCF-U instance with an application ID and an SFC service ID as additional information.

[0195] Example B18 includes the method of example B17 and / or some other example(s) herein, wherein if an application ID and an SFC service ID are provided in step 6, the NRF provides the application ID and the SFC service ID to the SFCF-U in a notification message (e.g., Nnrf_NFManagement_NFStatusNotify).

[0196] Example B19 includes the method of Examples B15-B18 and / or some other example(s) herein, wherein the SFCF-C configures the SFP based on information about the SFC service ID, the SFC application ID, and the supported SF information of the SFCF-U instance.

[0197] Example B20 includes the method of Examples A01-A19, B01-B19, and / or some other example(s) herein, wherein the SFCF-U is a UPF in 5GS, the SFCF-C is a PCF, NEF, or SMF in 5GS, and the edge enabler is an AF in 5GS.

[0198] Example C1 includes a method for enabling a service function chaining service in an edge computing data network having an edge application server and an edge enabler server.

[0199] Example C2 includes the method of example C1 and / or some other example(s) herein, wherein the service function chaining service enables support of a service function chaining network (SFC network), which terminates an N6 reference point between the 5G network and a trusted edge computing data network or an external edge computing data network, depending on the business relationship and deployment scenario between the edge application service provider or edge computing service provider and the PLMN operator.

[0200] Example C3 includes the method of example C2 and / or some other example(s) herein, wherein an edge application server (EAS) and an edge enabler server (EES) are in an external edge computing data network, and an application function (AF) in the EAS or EES can infer traffic routing toward the SFC network of the edge data network via N6 via the NEF on the N33 interface.

[0201] Example C4 includes the method of example C2 and / or some other example(s) herein, wherein an edge application server (EAS) and an edge enabler server (EES) are in a trusted edge computing data network, and an application function in the EAS or EES can interfere with traffic routing toward the SFC network of the edge data network via N6 directly on the N5 interface via the PCF.

[0202] Example C5 includes the method of example C3 or C4 and / or some other example(s) herein, wherein the edge application server uses the SFC service provided by the SFC network in the edge data network by using AF inference traffic routing to steer N6 traffic toward the SFC network in the edge data network.

[0203] Example C6 includes the method of example C2 and / or some other example(s) herein, wherein the SFC network providing the SFC service includes a service function and one or more service function paths in the edge computing data network, wherein a traffic classifier terminates N6 in the SFC network to process traffic from the 3GPP network before initiating the SFC service, and a traffic declassifier further combines traffic flows through the same or different SFPs before forwarding the traffic toward the EAS over the EDGE-X interface.

[0204] Example C7 includes the method of example C2 and / or some other example(s) herein, wherein a service function chaining policy for steering traffic that needs to pass through a specific service function path (SFP) in the SFC network can be configured by an edge application server, an edge computing enabler server, or a 3GPP OAM.

[0205] Example C8 includes the method of example C7 and / or some other example(s) herein, wherein the SFC service may be provided by one or more service providers, including edge service provider(s), edge computing service provider(s), SFC network service provider(s), or network operator(s).

[0206] Example C9 includes the method of example C8 and / or some other example(s) herein, wherein the SFC network configuration may be supported on EDGE-X and EDGE-Y by EAS(s) for SFs provided by an edge application service provider and EES(s) for SFs provided by an edge computing service provider, respectively.

[0207] Example C10 includes the method of example C5 and / or some other example(s) herein, wherein the AF inference traffic routing is sent by the EAS using a 5G network capability exposure API for directly interacting with the 5G network.

[0208] Example C11 includes the method of example C8 and / or some other example(s) herein, wherein the AF inference traffic routing is sent by an edge enabler server (EES) upon receiving an EAS request using an EES capability exposure API for interacting with a 5G network.

[0209] Example C12 includes the method of example C6 and / or some other example(s) herein, wherein the service function chain service is provided by a service function including functions in the user plane, including one or more service functions having service functions such as, but not limited to, network address translation (NAT), IP tunnel endpoint, packet classifier, deep packet inspection (DPI), lawful inspection (LI), TCP proxy, load balancer, firewall function, transcoder, video optimizer, URL filter, and application detection and control (ADC).

[0210] Example C13 includes the method of example C12 and / or some other example(s) herein, wherein the SFC parameters of the SFC service may include at least one of the following information: an SFC service ID as a service ID of the set of SFC parameters for the SFC service; an SFC configuration as one or more SFs with corresponding SF parameters; and an SFP configuration as an SFP index with corresponding ordered SFs.

[0211] Example C14 includes the method of example C13 and / or some other example(s) herein, wherein the SFC parameters of the SFC service also include information of the SFC routing policy, including a traffic classifier indicating a mapping between an SFP index and a traffic filtering rule for forwarding traffic to a first SF in the SFP identified by the SFP index, and a traffic declassifier indicating a traffic filtering rule for combining traffic from a last SF in the SFP identified by the SFP index.

[0212] Example C15 includes the method of example C13 or C14 and / or some other example(s) herein, wherein the SFC parameters of the SFC service also include validity parameter information for the SFC service identified by the SFC service ID, which may include one or more of the following information: duration, scheduled time period, application ID(s), PDU session type, e.g., IP / Ethernet / Unstructured, DNN, or associated PDU session parameters including slice / service type (SST) (e.g., eMBB, URLLC, MIoT, V2X, etc.) and an optional slice differentiator (SD).

[0213] Example C16 includes the method of example C14 and / or some other example(s) herein, wherein the traffic classifier provides the SFP index along with a mapping to an SFC classification policy based on different levels or granularity per packet, and the SFC classification policy may include, but is not limited to, one or more of a UE address, an application ID, a media type, and a traffic priority.

[0214] Example C17 includes the method of example C14 and / or some other example(s) herein, wherein the traffic declassifier provides an edge application server ID (EAS ID) terminating the EDGE-Z reference point for the target edge application server, along with a mapping to an SFC reclassification policy including one or more of the following information for combining traffic from one or more SFPs before forwarding to the application server of the application:

[0215] Example C18 includes the method of example C16 or example C17 and / or some other example(s) herein, wherein the policy can be based on information such as, but not limited to, a UE address, an application ID, a media type, a traffic priority, and an SPF index.

[0216] Example C19 includes the method of example C18 and / or some other example(s) herein, wherein DPI capabilities in the traffic classifier or traffic declassifier are required when information for the policy is only available in the traffic payload.

[0217] Example C20 includes a method for enabling a service function chaining (SFC) service that includes one or more service function paths (SFPs).

[0218] Example C21 includes the method of example C20 and / or some other example(s) herein, wherein the SFC service enables support of an SFC network terminating an N6 reference point between the 5G network and at least one edge computing data network (ECDN).

[0219] Example C22 includes the method of examples C20-21 and / or some other example(s) herein, wherein the ECDN includes one or more edge application servers and / or one or more edge enabler servers.

[0220] Example C23 includes the method of Examples C21-22 and / or some other example(s) herein, wherein the ECDN is one or more trusted edge computing data networks (ECDNs) and / or one or more external ECDNs.

[0221] Example C24 includes the method of example C23 and / or some other example(s) herein, wherein an edge application server (EAS) and an edge enabler server (EES) are in an external edge computing data network, and an application function (AF) in the EAS or EES can infer traffic routing toward the SFC network of the edge data network via N6 via the NEF on the N33 interface.

[0222] Example C25 includes the method of example C23 and / or some other example(s) herein, wherein an edge application server (EAS) and an edge enabler server (EES) are in a trusted edge computing data network, and an application function in the EAS or EES can interfere with traffic routing toward the SFC network of the edge data network via N6 directly on the N5 interface via a PCF.

[0223] Example C26 includes the method of examples C24-C25 and / or some other example(s) herein, wherein the edge application server uses the SFC service provided by the SFC network in the edge data network by using AF inference traffic routing to steer N6 traffic toward the SFC network in the edge data network.

[0224] Example C27 includes the method of Examples C1-C26 and / or some other example(s) herein, wherein the SFC network providing the SFC service includes a service function and one or more service function paths in the edge computing data network, wherein a traffic classifier terminates N6 in the SFC network to process traffic from the 3GPP network before initiating the SFC service, and a traffic declassifier further combines traffic flows through the same or different SFPs before forwarding the traffic toward the EAS over the EDGE-X interface.

[0225] Example C28 includes the method of Examples C1 to C27 and / or some other example(s) herein, wherein a service function chaining policy for steering traffic that needs to traverse a particular service function path (SFP) in the SFC network can be configured by an edge application server, an edge computing enabler server, or a 3GPP OAM.

[0226] Example C29 includes the method of example C28 and / or some other example(s) herein, wherein the SFC service may be provided by one or more service providers, including edge service provider(s), edge computing service provider(s), SFC network service provider(s), or network operator(s).

[0227] Example C30 includes the method of example C29 and / or some other example(s) herein, wherein the SFC network configuration may be supported on EDGE-X and EDGE-Y by EAS(s) for SFs provided by an edge application service provider and EES(s) for SFs provided by an edge computing service provider, respectively.

[0228] Example C31 includes the method of examples C26-C30 and / or some other example(s) herein, wherein the AF inference traffic routing is sent by the EAS using a 5G network capability exposure API for directly interacting with the 5G network.

[0229] Example C32 includes the method of examples C29-C31 and / or some other example(s) herein, wherein the AF inference traffic routing is sent by an edge enabler server (EES) upon receiving an EAS request using an EES capability exposure API to interact with a 5G network.

[0230] Example C33 includes the method of Examples C29-C32 and / or some other example(s) herein, wherein the service function chain service is provided by a service function including a function in the user plane, including one or more service functions having service functions such as, but not limited to, network address translation (NAT), IP tunnel endpoint, packet classifier, deep packet inspection (DPI), lawful inspection (LI), TCP proxy, load balancer, firewall function, transcoder, video optimizer, URL filter, and application detection and control (ADC).

[0231] Example C34 includes the method of example C33 and / or some other example(s) herein, wherein the SFC parameters of the SFC service may include at least one of the following information: an SFC service ID as a service ID of this set of SFC parameters for the SFC service; an SFC configuration as one or more SFs with corresponding SF parameters; and an SFP configuration as an SFP index with corresponding ordered SFs.

[0232] Example C35 includes the method of example C34 and / or some other example(s) herein, wherein the SFC parameters of the SFC service also include information of the SFC routing policy, including a traffic classifier indicating a mapping between an SFP index and a traffic filtering rule for forwarding traffic to a first SF in the SFP identified by the SFP index, and a traffic declassifier indicating a traffic filtering rule for combining traffic from a last SF in the SFP identified by the SFP index.

[0233] Example C36 includes the method of Examples C33 to C35 and / or some other example(s) herein, wherein the SFC parameters of the SFC service also include validity parameter information for the SFC service identified by the SFC service ID, which may include one or more of the following information: duration, scheduled time period, application ID(s), PDU session type, e.g., IP / Ethernet / Unstructured, DNN, or associated PDU session parameters including slice / service type (SST) (e.g., eMBB, URLLC, MIoT, V2X, etc.), and an optional slice differentiator (SD).

[0234] Example C37 includes the method of examples C35-C36 and / or some other example(s) herein, wherein the traffic classifier provides the SFP index along with a mapping to an SFC classification policy based on different levels or granularity per packet, and the SFC classification policy may include, but is not limited to, one or more of a UE address, an application ID, a media type, and a traffic priority.

[0235] Example C38 includes the method of examples C35-C37 and / or some other example(s) herein, wherein the traffic declassifier provides an edge application server ID (EAS ID) terminating the EDGE-Z reference point for the target edge application server, along with a mapping to an SFC reclassification policy including one or more of the following information for combining traffic from one or more SFPs before forwarding to the application server of the application:

[0236] Example C39 includes the method of examples C37-C38 and / or some other example(s) herein, wherein the policy can be based on information such as, but not limited to, a UE address, an application ID, a media type, a traffic priority, and an SPF index.

[0237] Example C40 includes the method of examples C38-C39 and / or some other example(s) herein, where DPI capabilities in the traffic classifier or traffic declassifier are required when information for the policy is available only in the traffic payload.

[0238] Example D1 includes one or more non-transitory computer-readable media (NTCRMs) storing instructions that, when executed by one or more processors, cause a device of a wireless cellular network to receive configuration information for a service function path (SFP) that specifies one or more ordered service functions for service function chaining (SFC), and configure the SFP based on the configuration information to coordinate with an SFC function in the edge data network to provide the one or more ordered service functions via the SFP across the wireless cellular network and the edge data network.

[0239] Example D2 includes the one or more NTCRMs of example D1, wherein the configuration information is received from an operation, administration, and maintenance (OAM) entity or a network capability repository function (NRF) of the wireless cellular network.

[0240] Example D3 includes one or more NTCRMs of examples D1-D2, wherein the configuration information includes one or more SFC parameters based on a service level agreement (SLA) for SFC services in the wireless cellular network.

[0241] Example D4 includes one or more NTCRMs of any of Examples D1 to D3, wherein the configuration information is received from an edge application server (EAS) and indicates one or more ordered service features and associated parameters to be provided by the wireless cellular network.

[0242] Example D5 includes one or more NTCRMs of any of Examples D1 to D4, and configuring the SFP includes configuring one or more SFC user plane functions (SFCF-U) to provide one or more ordered service functions.

[0243] Example D6 includes one or more NTCRMs of example D5, and the configuration information includes an indication of one or more SFCF-U instances that support one or more of the one or more ordered service functions.

[0244] Example D7 includes the one or more NTCRMs of example D6, wherein the instructions, when executed, further cause the device to send a request for configuration information associated with one or more SFCF-U instances, the request identifying one or more ordered service functions.

[0245] Example D8 includes one or more NTCRMs of example D6 or example D7, and the configuration information further includes at least one of an SFC application ID or an SFC service ID associated with each of the one or more SFCF-U instances.

[0246] Example D9 includes one or more NTCRMs of any of examples D1-D8, wherein the device implements an SFC control plane function (SFCF-C).

[0247] Example D10 includes one or more non-transitory computer-readable media (NTCRMs) storing instructions that, when executed by one or more processors, cause an operations, administration, and maintenance (OAM) entity to receive, from a service function chaining (SFC) control plane function (SFCF-C), a request for information associated with one or more SFC user plane function (SFCF-U) instances supporting one or more service ordering functions associated with a service function path, and send, to the SFCF-C, the information associated with the one or more SFCF-U instances.

[0248] Example D11 includes the one or more NTCRMs of example D10, wherein the instructions, when executed, further cause the OAM entity to determine that an SFCF-U instance supporting a first service function of the one or more ordered service functions is not available, and, based on the determination, configure a new SFCF-U instance to support the first service function.

[0249] Example D12 includes the one or more NTCRMs of examples D10-D11, wherein the instructions, when executed, further cause the OAM entity to register the new SFCF-U instance with a network function repository function (NRF).

[0250] Example D13 includes one or more NTCRMs of example D12, wherein registering the new SFCF-U instance with the NRF includes providing information regarding at least one of an application ID and an SFC service ID associated with the SFCF-U instance.

[0251] Example D14 includes one or more NTCRMs of any of Examples D10 to D13, and the service function path includes one or more ordered service functions to be provided by the wireless cellular network and one or more other ordered service functions to be provided by the edge data network.

[0252] Example D15 includes an edge data network device comprising: a traffic classifier that receives service function chaining (SFC) traffic from a wireless cellular network and routes the SFC traffic to one or more ordered service functions via a service function path (SFP); and a traffic declassifier that receives SFP traffic from the SFP and provides the SFP traffic to an edge application server or an edge enabler server.

[0253] Example D16 includes the apparatus of example D15, wherein the traffic classifier further receives SFC policy information, and identifies an SFP to route the SFC traffic based on the SFC policy information.

[0254] Example D17 includes the apparatus of example D16, in which the SFC policy information is received from an edge application server, an edge enabler server, or an operations, administration, and maintenance (OAM) entity of the wireless cellular network.

[0255] Example D18 includes the apparatus of any of examples D15-D17, wherein SFC traffic is received on the N6 interface and SFP traffic is provided via the EDGE-X or EDGE-Y interface.

[0256] Example D19 includes the apparatus of any of examples D15-D18, wherein the traffic declassifier combines SFP traffic from the multiple SFPs and provides the combined SFP traffic to an edge application server or an edge enabler server.

[0257] Example D20 includes the device of any of Examples D15-D19, wherein the one or more service functions include one or more of a network address translation (NAT), an Internet Protocol (IP) tunnel endpoint, a packet classifier, a deep packet inspection (DPI), a lawful inspection (LI), a transmission control protocol (TCP) proxy, a load balancer, a firewall function, a transcoder, a video optimizer, a uniform resource locator (URL) filter, or an application detection and control (ADC).

[0258] Example D21 includes the apparatus of any of Examples D15-D19, wherein the traffic classifier receives SFC parameters for an SFC service associated with the SFC traffic, the SFC parameters including one or more of an SFC service ID, an SFC configuration including one or more service functions and associated service function parameters, or an SFP configuration including an SFP index and associated ordered service functions, and the traffic classifier routes the SFC traffic further based on the SFC parameters.

[0259] Example D22 includes the device of example D21, wherein the SFC parameters further include one or more validity parameters for the SFC service, the one or more validity parameters including one or more of a duration, a scheduled time period, one or more application IDs, a packet data unit session type or other related PDU session parameter, or a slice differentiator.

[0260] Example D23 includes the apparatus of any of examples D15-D22, wherein the SFC traffic includes one or more of a user equipment (UE) address, an application ID, a media type, or a traffic priority.

[0261] Example Z01 includes an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples A01-A19, B01-B20, C1-C40, D1-D23, or any other method or process described herein.

[0262] Example Z02 includes one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of the electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of examples A01-A19, B01-B20, C1-C40, D1-D23, or any other method or process described herein.

[0263] Example Z03 includes an apparatus including logic, modules, or circuitry for performing one or more elements of a method described or related to any of examples A01-A19, B01-B20, C1-C40, D1-D23, or any other method or process described herein.

[0264] Example Z04 includes any method, technique, or process described in or related to any of Examples A01-A19, B01-B20, C1-C40, D1-D23, or any portion or parts thereof.

[0265] Example Z05 includes an apparatus having one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of Examples A01-A19, B01-B20, C1-C40, D1-D23, or portions thereof.

[0266] Example Z06 includes signals described in or related to any of Examples A01-A19, B01-B20, C1-C40, D1-D23 or any part or portion thereof.

[0267] Example Z07 includes a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples A01-A19, B01-B20, C1-C40, D1-D23, or any part or portion thereof, or otherwise described in this disclosure.

[0268] Example Z08 includes a signal encoded with data described in or related to any of Examples A01-A19, B01-B20, C1-C40, D1-D23, or any part or portion thereof, or otherwise described in this disclosure.

[0269] Example Z09 includes a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples A01-A19, B01-B20, C1-C40, D1-D23, or any part or portion thereof, or otherwise described in this disclosure.

[0270] Example Z10 includes an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any of Examples A01-A19, B01-B20, C1-C40, D1-D23, or portions thereof.

[0271] Example Z11 includes a computer program including instructions, where execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any of Examples A01-A19, B01-B20, C1-C40, D1-D23, or portions thereof.

[0272] Example Z12 includes a signal in a wireless network as shown and described herein.

[0273] Example Z13 includes a method of communicating in a wireless network as shown and described herein.

[0274] Example Z14 includes a system for providing wireless communication as shown and described herein.

[0275] Example Z15 includes a device for providing wireless communication as shown and described herein.

[0276] An example implementation is an edge computing system that includes respective system processing devices and nodes for invoking or performing the operations of Examples A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein.

[0277] Another exemplary implementation is a client endpoint node operable to invoke or perform operations of embodiments A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein. Another exemplary implementation is an aggregation node, network hub node, gateway node, or core data processing node within or coupled to an edge computing system operable to invoke or perform operations of embodiments A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein. Another exemplary implementation is an access point, base station, roadside unit, or on-premises unit within or coupled to an edge computing system operable to invoke or perform operations of embodiments A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein. Another example implementation is a node provisioning node, a service orchestration node, an application orchestration node, or a multi-tenant management node within or coupled to an edge computing system operable to invoke or perform the operations of examples A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein. Another example implementation is an edge node operating edge provisioning services, application or service orchestration services, virtual machine deployment, container deployment, function deployment, and compute management within or coupled to an edge computing system operable to invoke or perform the operations of examples A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein. Another example implementation is an edge computing system operable to invoke or perform the operations of Examples A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein, operable as an edge mesh, as an edge mesh with sidecar loads, or with inter-mesh communication.Another example implementation is an edge computing system that includes aspects of network functions, acceleration functions, acceleration hardware, storage hardware, or computational hardware resources operable to invoke or perform the use cases discussed herein using embodiments A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein. Another example implementation is an edge computing system that supports client mobility, vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or vehicle-to-infrastructure (V2I) scenarios, and optionally adapted to operate in accordance with the ETSI MEC specifications, operable to invoke or perform the use cases discussed herein using embodiments A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein. Another example implementation is an edge computing system adapted for mobile wireless communications, including configuration with 3GPP, 4G / LTE, or 5G network capabilities, operable to invoke or perform the use cases discussed herein using examples A01-A19, B01-B20, C1-C40, D1-D23, or other subject matter described herein.

[0278] Unless otherwise stated, any of the above-described examples may be combined with any other example (or combination of examples). The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0279] Abbreviation Unless used differently herein, the terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR21.905 v16.0.0(2019-06). For purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein: 3GPP 3rd Generation Partnership Project 4G 4th Generation 5G (5th Generation) 5GC 5G Core Network ACK Acknowledgment AF Application Features AM Confirmation Mode AMBR Total Maximum Bitrate AMF Access and Mobility Management Functions AN Access Network ANR Automatic Adjacency AP application protocol, antenna port, access point API Application Programming Interface APN Access Point Name ARP Allocation and Retention Priority ARQ Automatic Repeat Request AS access layer ASN.1 Abstract Syntax Notation 1 ASP Application Service Provider AUSF authentication server function AWGN Additive White Gaussian Noise BAP Backhaul Adaptation Protocol BCH Broadcast Channel BER Bit Error Rate BFD Beam Failure Detection BLER Block Error Rate BPSK binary phase shift keying BRAS Broadband Remote Access Server BSS Business Support System BS base station BSR Buffer Status Report BW Bandwidth BWP Bandwidth Portion C-RNTI Cell Radio Network Temporary Identifier CA Carrier Aggregation, Certification Authority CAPEX capital investment CBRA Collision-Based Random Access CC Component Carrier, Country Code, Cryptographic Checksum CCA Clear Channel Rating CCE Control Channel Element CCCH Common Control Channel CE Coverage Extension CDM Content Delivery Network CDMA code division multiple access CFRA Contention-Free Random Access CG cells CI Cell Identity CID Cell ID (e.g., positioning method) CIM Common Information Model CIR Carrier to Interference Ratio CK encryption key CM Connection Management, conditionally required CMAS Commercial Mobile Alert Service CMD command CMS Cloud Management System CO Conditional Options CoMP Coordinated Multipoint CORESET Control resource set COTS Commercial Off-the-Shelf CP Control Plane, Cyclic Prefix, Attachment Point CPD Connection Point Descriptor CPE Customer Premises Equipment CPICH Common Pilot Channel CQI Channel Quality Indicator CPU CSI processing unit, central processing unit C / R Command / Response Field Bit CRAN Cloud Radio Access Network, Cloud RAN CRB Common Resource Block CRC Cyclic Redundancy Check CRI Channel State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI Cell RNTI CS Circuit Switched CSAR Cloud Services Archive CSI Channel State Information CSI-IM CSI interference measurement CSI-RS CSI reference signal CSI-RSRP CSI reference signal received power CSI-RSRQ CSI reference signal reception quality CSI-SINR CSI signal to noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSS common search space, cell-specific search space CTS Sendable CW Codeword CWS Contention Window Size D2D Device to Device DC Dual Connectivity, Direct Current DCI Downlink Control Information DF Deployment Flavor DL Downlink DMTF Distributed Management Task Force DPDK Data Plane Development Kit DM-RS DMRS demodulation reference signal DN Data Network DRB Data Radio Bearer DRS Discovery Reference Signal DRX Intermittent Reception DSL Domain Specific Language, Digital Subscriber Line DSLAM DSL Access Multiplexer DwPTS Downlink Pilot Time Slot E-LAN ​​Ethernet Local Area Network E2E End-to-End EAS Edge Application Server ECCA Enhanced Clear Channel Assessment, Enhanced CCA ECCE Extended Control Channel Element, Extended CCE ECSP Edge Computing Service Provider ED Energy Detection EDGE Enhanced Data Rates for GSM Evolution (GSM Evolution) EES Edge Enabler Server EGMF Exposure Regulatory Management Function EGPRS Enhanced GPRS EIR Equipment Identity Register eLAA Extended License Assisted Access, Extended LAA EM Element Manager eMBB Enhanced Mobile Broadband EMS Element Management System eNB Evolved Node B, E-UTRAN Node B EN-DC E-UTRA-NR dual connectivity EPC Evolved Packet Core EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel EPRE Energy per Resource Element EPS Evolved Packet System EREG Extended REG, Extended Resource Element Group ETSI European Telecommunications Standards Institute ETWS Earthquake and Tsunami Warning System eUICC Embedded UICC, Embedded Universal Integrated Circuit Card E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN EV2X Enhanced V2X F1AP F1 Application Protocol F1-C F1 control plane interface F1-U F1 user plane interface FACCH Fast Associated Control Channel FACCH / F Fast Associated Control Channel / Full Rate FACCH / H Fast Associated Control Channel / Half Rate FACH Forward Access Channel FAUSCH High Speed ​​Uplink Signaling Channel FB Function Block FBI Feedback Information FCC Federal Communications Commission FCCH Frequency Correction Channel FDD Frequency Division Duplex FDM Frequency Division Multiplexing FDMA Frequency Division Multiple Access FE Front End FEC Forward Error Correction FFS Future considerations FFT Fast Fourier Transform feLAA Further Enhanced License Assisted Access, Further Enhanced LAA FMSS Flexible Mobile Service Steering FN Frame Number FPGA Field Programmable Gate Array FR Frequency Range G-RNTI GERAN Radio Network Temporary Identity GERAN GSM EDGE RAN, GSM EDGE Radio Access Network GGSN Gateway GPRS Support Node GLONASS Global Navigation Satellite System gNB Next generation NodeB gNB-CU gNB-Centralized Unit, Next Generation Node B Centralized Unit gNB-DU gNB-Distributed Unit, Next Generation Node B Distributed Unit GNSS Global Navigation Satellite System GPRS General Packet Radio Service GSM Global System for Mobile Communications, Groupe Special Mobile (the "e" in "Special" is an acute accent) GTP GPRS Tunneling Protocol GTP-U: GPRS Tunneling Protocol for the User Plane GTS Go To Sleep signal (related to WUS) GUMMEI Globally Unique MME Identifier GUTI Globally Unique Temporary UE Identity HARQ Hybrid ARQ, Hybrid Automatic Repeat Request HANDO Handover HFN Hyperframe Number HHO Hard Handover HLR Home Location Register HN Home Network HO Handover HPLMN Home Public Land Mobile Network HSDPA High-Speed ​​Downlink Packet Access HSN Hopping Sequence Number HSPA High Speed ​​Packet Access HSS Home Subscriber Server HSUPA High Speed ​​Uplink Packet Access HTTP Hypertext Transfer Protocol HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, e.g., port 443). I-Block Information Block ICCID Integrated Circuit Card Identification IAB Integrated Access and Backhaul ICIC Inter-cell Interference Coordination ID identity, identifier IDFT Inverse Discrete Fourier Transform IE Information Elements IBE In-Band Emissions IEEE Institute of Electrical and Electronics Engineers IEI Information Element Identifier IEIDL Information Element Identifier Data Length IETF Internet Engineering Task Force IF Infrastructure IM Interference measurement, intermodulation, IP multimedia IMC IMS Credentials IMEI International Mobile Equipment Identity IMGI International Mobile Group Identity IMPI IP Multimedia Private Identity IMPU IP Multimedia Public Identity IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IoT Internet of Things IP Internet Protocol Ipsec IP Security, Internet Protocol Security IP-CAN IP Connectivity Access Network IP-M IP Multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol version 6 IR Infrared IS in sync IRP Integrated Reference Point ISDN Integrated Services Digital Network ISIM IM Service Identity Module ISO International Organization for Standardization ISP Internet Service Provider IWF Interworking Function I-WLAN Interworking WLAN K is the constraint length of the convolutional code, USIM individual key kB kilobyte (1000 bytes) kbps kilobits per second Kc encryption key Ki Individual subscriber authentication key. KPI Key Performance Indicator KQI Key Quality Indicators KSI Key Set Identifier ksps kilosymbols per second KVM Kernel Virtual Machine L1 Layer 1 (physical layer) L1-RSRP Layer 1 Reference Signal Received Power L2 Layer 2 (Data Link Layer) L3 Layer 3 (Network Layer) LAA License Assisted Access LAN Local Area Network LBT Listen Before Talk LCM Lifecycle Management LCR Low Chip Rate LCS Location Services LCID Logical Channel ID LI Layer Indicator LLC Logical Link Control, Low Layer Integrity LPLMN Local PLMN LPP LTE Positioning Protocol LSB least significant bit LTE Long Term Evolution LWA LTE-WLAN aggregation LTE / WLAN radio-level integration using LWIP IPsec tunnels LTE Long Term Evolution M2M machine to machine MAC Medium Access Control (context of protocol layering) MAC Message Authentication Code (security / encryption context) MAC-A MAC used for authentication and key agreement (in the context of TSG TWG3) MAC-I MAC used for data integrity of signalling messages (in the context of TSG TWG3) MANO Management and Orchestration MBMS Multimedia Broadcast Multicast Service MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MCC Mobile Country Code MCG Master Cell Group MCOT Maximum Channel Occupancy Time MCS modulation and coding scheme MDAF Management Data Analysis Function MDAS Managed Data Analysis Service Minimizing MDT Drive Tests ME Mobile Device MeNB Master eNB MER Message Error Rate MGL Measurement gap length MGRP measurement gap repetition period MIB Master Information Block, Management Information Base MIMO Multiple Input Multiple Output MLC Mobile Location Center MM Mobility Management MME Mobility Management Entity MN Master Node MN Management Service MO measurement target, mobile origination MPBCH MTC Physical Broadcast Channel MPDCCH MTC Physical Downlink Control Channel MPDSCH MTC Physical Downlink Shared Channel MPRACH MTC Physical Random Access Channel MPUSCH MTC Physical Uplink Shared Channel MPLS Multiprotocol Label Switching MS mobile station MSB Most Significant Bit MSC Mobile Switching Center MSI Minimum System Information, MCH Scheduling Information MSID Mobile Station Identifier MSIN Mobile Station Identification Number MSISDN Mobile Subscriber ISDN Number MT Mobile Terminated, Mobile Termination MTC Machine Type Communication mMTC Large-scale MTC, Large-scale Machine Type Communication MU-MIMO Multi-User MIMO MWUS MTC wake-up signal, MTC WUS NACK Negative Acknowledgment NAI Network Access Identifier NAS non-access layer, non-access layer NCT Network Connection Topology NC-JT Non-coherent Joint Transmission NEC Network Capacity Exposure NE-DC NR-E-UTRA dual connectivity NEF Network Exposure Function NF Network Function NFP Network Transfer Path NFPD Network Forwarding Path Descriptor NFV Network Functions Virtualization NFVI NFV Infrastructure NFVO NFV Orchestrator NG Next Generation NGEN-DC NG-RAN E-UTRA-NR dual connectivity NM Network Manager NMS Network Management System N-PoP Network Point of Presence NMIB, N-MIB Narrowband MIB NPBCH Narrowband Physical Broadcast Channel NPDCCH Narrowband Physical Downlink Control Channel NPDSCH Narrowband Physical Downlink Shared Channel NPRACH Narrowband Physical Random Access Channel NPUSCH Narrowband Physical Uplink Shared Channel NPSS Narrowband Primary Synchronization Signal NSSS Narrowband Secondary Synchronization Signal NR New Radio, Adjacent Relationships NRF NF Repository Function NRS Narrowband Reference Signal NS Network Services NSA Non-Standalone Operation Mode NSD Network Service Descriptor NSR Network Service Record NSSAI Network Slice Selection Support Information S-NNSAI Single NSSAI NSSF Network Slice Selection Function NW Network NWUS Narrowband wake-up signal, narrowband WUS NZP Non-Zero Power O&M Operation and Maintenance ODU2 Optical Channel Data Unit - Type 2 OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OOB Out of Band OOS Out of Sync OPEX Operating Expenses OSI and other system information OSS operation support system Over-the-air (OTA) PAPR Peak to Average Power Ratio PAR Peak to Average Ratio PBCH Physical Broadcast Channel PC power control, personal computer PCC Primary Component Carrier, Primary CC PCell Primary Cell PCI Physical Cell ID, Physical Cell Identity PCEF Policy and Charging Enforcement Function PCF Policy Control Function PCRF policy control and charging rules function PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDN Packet Data Network, Public Data Network PDSCH Physical Downlink Shared Channel PDU Protocol Data Unit PEI Permanent Equipment Identifier PFD Packet Flow Description P-GW PDN Gateway PHICH Physical Hybrid ARQ Indicator Channel PHY Physical Layer PLMN Public Land Mobile Network PIN Personal Identification Number PM performance measurement PMI Precoding Matrix Indicator PNF Physical Network Function PNFD Physical Network Function Descriptor PNFR Physical Network Function Record POC PTT over cellular PP, PTP Point-to-Point PPP Point-to-Point Protocol PRACH Physical RACH PRB Physical Resource Block PRG Physical Resource Block Group ProSe Proximity Services, Proximity-Based Services PRS Positioning Reference Signal PRR packet receiving radio PS Packet Service PSBCH Physical Sidelink Broadcast Channel PSDCH Physical Sidelink Downlink Channel PSCCH Physical Sidelink Control Channel PSFCH Physical Sidelink Feedback Channel PSSCH Physical Sidelink Shared Channel PSCell Primary SCell PSS Primary Synchronization Signal PSTN Public Switched Telephone Network PT-RS Phase Tracking Reference Signal PTT Push to Talk PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QAM Quadrature Amplitude Modulation QCI QoS Class Identifier QCL pseudo-collocation QFI QoS Flow ID, QoS Flow Identifier QoS Quality of Service QPSK Quadrature (quadrature) phase shift keying QZSS Quasi-Zenith Satellite System RA-RNTI Random Access RNTI RAB Radio Access Bearer, Random Access Burst RACH Random Access Channel Remote Authentication Dial in RADIUS User Service RAN Radio Access Network RAND Random number (used for authentication) RAR Random Access Response RAT Radio Access Technology RAU Routing Area Update RB Resource Block, Radio Bearer RBG Resource Block Group REG Resource Element Group Rel Release REQ request RF radio frequency RI Rank Indicator RIV Resource Indicator Value RL Radio Link RLC Radio Link Control, Radio Link Control Layer RLC AM RLC confirmation mode RLC UM RLC unacknowledged mode RLF Radio Link Failure RLM Radio Link Monitoring RLM-RS Reference signal for RLM RM Registration Management RMC Reference Measurement Channel RMSI Remaining MSI, Minimum Remaining System Information RN Relay Node RNC Radio Network Controller RNL Radio Network Layer RNTI Radio Network Temporary Identifier ROHC Robust Header Compression RRC Radio Resource Control, Radio Resource Control Layer RRM Radio Resource Management RS reference signal RSRP reference signal received power RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator RSU roadside unit RSTD Reference signal time difference RTP Real Time Protocol RTS ready to send RTT Round Trip Time Rx (receive, receive, receiver) S1AP S1 Application Protocol S1-MME S1 for control plane S1-U S1 for user plane S-GW Serving Gateway S-RNTI SRNC Radio Network Temporary Identity S-TMSI SAE temporary mobile station identifier SA Standalone Operation Mode SAE System Architecture Evolution SAP Service Access Point SAPD Service Access Point Descriptor SAPI Service Access Point Identifier SCC Secondary Component Carrier, Secondary CC SCell Secondary Cell SC-FDMA Single Carrier Frequency Division Multiple Access SCG Secondary Cell Group SCM Security Context Management SCS Subcarrier Spacing SCTP Stream Control Transmission Protocol SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer SDL Auxiliary Downlink SDNF Structured Data Storage Network Function SDP Session Description Protocol SDSF Structured Data Storage Facility SDU Service Data Unit SEAF Security Anchor Function SeNB Secondary eNB SEPP Security Edge Protection Proxy SFC Service Function Chaining SFP Service Function Path(s) SFI Slot Format Indication SFTD Space Frequency Time Diversity, SFN and Frame Timing Difference SFN System Frame Number or Single Frequency Network SgNB Secondary gNB SGSN Serving GPRS Support Node S-GW Serving Gateway SI System Information SI-RNTI System Information RNTI SIB System Information Block SIM Subscriber Identity Module SIP Session Initiation Protocol SiP System in Package SL Side Link SLA Service Level Agreement SM Session Management SMF Session Management Facility SMS Short Message Service SMSF SMS function SMTC SSB-based measurement timing configuration SN Secondary Node, Sequence Number SoC System on Chip SON Self-Organizing Network SpCell Special Cell SP-CSI-RNTI Semi-persistent CSI RNTI SPS semi-persistent scheduling SQN Sequence Number SR Scheduling Request SRB Signaling Radio Bearer SRS Sounding Reference Signal SS Sync Signal SSB SS Block SSBRI SSB Resource Indicator SSC Session and Service Continuity SS-RSRP synchronization signal-based reference signal received power SS-RSRQ Synchronization Signal-Based Reference Signal Reception Quality SS-SINR Synchronization signal based signal-to-noise and interference ratio SSS Secondary Synchronization Signal SSSG Search Space Set Group SSSIF Search Space Set Indicator SST Slice / Service Type SU-MIMO Single User MIMO SUL Auxiliary Uplink TA Timing Advance, Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAU Tracking Area Update TB Transport Block TBS Transport Block Size TBD undefined TCI Transmit Configuration Indicator TCP transmission communication protocol TDD Time Division Duplex TDM time division multiplexing TDMA Time Division Multiple Access TE Terminal Equipment TEID Tunnel Endpoint Identifier TFT Traffic Flow Template TMSI Temporary Mobile Subscriber Identity TNL Transport Network Layer TPC transmit power control TPMI Transmit Precoding Matrix Indicator TR Technical Report TRP, TRxP transmitting and receiving points TRS Tracking Reference Signal TRx Transceiver TS Technical Specifications, Technical Standards TTI Transmission Time Interval Tx (transmit, send, transmitter) U-RNTI UTRAN Radio Network Temporary Identity UART Universal Asynchronous Receiver and Transmitter UCI Uplink Control Information UE User Equipment UDM Unified Data Management UDP User Datagram Protocol UDR Unified Data Repository UDSF Unstructured Data Storage Network Facility UICC Universal Integrated Circuit Card UL Uplink UM Unconfirmed Mode UML Unified Modeling Language UMTS Universal Mobile Telecommunications System UP User Plane UPF User Plane Function URI Uniform Resource Identifier URL Uniform Resource Locator URLLC Ultra-reliable low latency USB Universal Serial Bus USIM Universal Subscriber Identity Module USS UE specific search space UTRA UMTS Terrestrial Wireless Access UTRAN Universal Terrestrial Radio Access Network UwPTS Uplink Pilot Time Slot V2I Vehicle to Infrastructure V2P Vehicle-to-Pedestrian V2V Vehicle to Vehicle V2X Vehicle to Everything VIM Virtualization Infrastructure Manager VL Virtual Link VLAN Virtual LAN, Virtual Local Area Network VM Virtual Machine VNF Virtualized Network Functions VNFFG VNF forwarding graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNF Manager VoIP Voice over IP, Voice over Internet Protocol VPLMN Visited Public Land Mobile Network VPN Virtual Private Network VRB Virtual Resource Block WiMAX Global Interoperable Microwave Access WLAN Wireless Local Area Network WMAN Wireless Metropolitan Area Network WPAN Wireless Personal Area Network X2-C X2-Control Plane X2-U X2-User Plane XML Extensible Markup Language XRES Expected User Response XOR exclusive OR ZC Zadoff-Chu ZP Zero Power

[0280] term For purposes of this document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0281] The terms "coupled" and "communicatively coupled," along with their derivatives, are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may contact each other by means of communication, for example, through a wire or other interconnection, through a wireless communication channel or ink, and / or the like.

[0282] As used herein, the term “circuitry” refers to, is a part of, or includes hardware components, such as electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (shared, dedicated, or group), application-specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-performance PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc., configured to provide described functionality. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or circuitry used in an electrical or electronic system) and program code used to perform the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0283] As used herein, the term “processor circuitry” refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. A processing circuit may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core processors, dual-core processors, triple-core processors, quad-core processors, and / or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes. A processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuitry” and / or “baseband circuitry” may be considered synonymous with and may be referred to as “processor circuitry.”

[0284] As used herein, the terms "memory" and / or "memory circuitry" refer to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM, and / or SDRAM, core memory, ROM, magnetic storage media, optical storage media, flash memory devices, or other machine-readable media for storing data. The term "computer-readable medium" can include, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions or data.

[0285] As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral interface, a network interface card, and / or the like.

[0286] As used herein, the term "user equipment" or "UE" refers to a device having wireless communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0287] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communications network services. The term "network element" may be considered synonymous with and / or may be referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and / or the like.

[0288] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or component thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the terms "computer system" and / or "system" may refer to multiple computing devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

[0289] As used herein, "appliance," "computer appliance," The term "appliance" or similar terms refers to a computing device or computer system having program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computing appliance or is otherwise dedicated to providing specific computing resources. The term "element" refers to a unit that is indivisible at a given level of abstraction and has clearly defined boundaries; an element can be any type of entity, including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof. The term "device" refers to a physical entity embedded within or attached to another physical entity in the vicinity and has the ability to communicate digital information to or from that physical entity. The term "entity" refers to a separate component of an architecture or device, or information transferred as a payload. The term "controller" refers to an element or entity that has the ability to affect a physical entity, such as by changing its state or moving the physical entity.

[0290] The term "cloud computing" or "cloud" refers to a paradigm for enabling network access to a scalable, elastic pool of shareable computing resources with on-demand, self-service provisioning and management, and without active management by users. Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities provided through cloud computing that are invoked using a defined interface (e.g., an API, etc.). The term "computing resource" or simply "resource" refers to any physical or virtual component with limited availability within a computer system or network, or the use of such a component. Examples of computing resources include the use of / access to a server, processor(s), storage equipment, memory devices, memory areas, networks, power, input / output (peripheral) devices, mechanical devices, network connections (e.g., channels / links, ports, network sockets, etc.), operating systems, virtual machines (VMs), software / applications, computer files, etc., for a period of time. A "hardware resource" may refer to a computational, storage, and / or network resource provided by a physical hardware element(s). A "virtualized resource" may refer to a computational, storage, and / or network resource provided to an application, device, system, etc. by a virtual infrastructure. The terms "network resource" or "communication resource" may refer to a resource accessible by a computer device / system over a communication network.The term "system resource" may refer to any type of shared entity for providing a service and may include computing and / or network resources. A system resource may be considered a coherent set of functions, network data objects, or services accessible through a clearly identifiable server, where such system resources reside on a single host or multiple hosts. Cloud computing can be considered a set of services or services. As used herein, the term "cloud service provider" (or CSP) refers to an organization that operates typically large-scale "cloud" resources consisting of centralized data centers, regional data centers, and edge data centers (e.g., when used in the context of a public cloud). In other examples, a CSP may also be referred to as a cloud service operator (CSO). References to "cloud computing" generally refer to computing resources and services provided by a CSP or CSO in remote locations with at least some increased latency, distance, or constraints relative to edge computing.

[0291] As used herein, the term "data center" refers to a purpose-designed structure intended to house multiple high-performance computing and data storage nodes, such that a large amount of computing, data storage, and network resources reside in a single location. This often requires specialized rack and enclosure systems, appropriate heating, cooling, ventilation, security, fire suppression, and power supply systems. The term may also refer to computing and data storage nodes in some contexts. Data centers may vary in size between centralized or cloud data centers (e.g., the largest), regional data centers, and edge data centers (e.g., the smallest).

[0292] As used herein, the term “edge computing” refers to the implementation, coordination, and use of computing and resources at locations closer to the “edge” or collection of “edges” of a network. Deploying computing resources at the edge of a network may reduce application and network latency, reduce network backhaul traffic and associated energy consumption, improve service capacity, improve compliance with security or data privacy requirements (especially compared to traditional cloud computing), and improve total cost of ownership. As used herein, the term “edge compute node” refers to a real-world, logical, or virtualized implementation of a computable element in the form of a device, gateway, bridge, system or subsystem, component, whether operating in server mode, client mode, endpoint mode, or peer mode, and whether located at the “edge” of the network or at a location further connected within the network. As used herein, references to a "node" are generally interchangeable with "device," "component," and "subsystem," while references to an "edge computing system" or "edge computing network" generally refer to a distributed architecture, organization, or collection of multiple nodes and devices that are organized to achieve or provide some aspect of a service or resource in an edge computing setting.

[0293] Additionally or alternatively, the term "Edge Computing" refers to the concept of enabling operator and third-party services to be hosted close to the UE's access point of connection to achieve efficient service delivery through reduced end-to-end latency and load on the transport network, as described in [4].

[0294] As used herein, the term "Edge Computing Service Provider" refers to a mobile network operator or third-party service provider that offers edge computing services.

[0295] As used herein, the term "Edge Data Network" refers to a local data network (DN) that supports an architecture for enabling edge applications.

[0296] As used herein, the term "edge hosting environment" refers to an environment that provides the support necessary to run an edge application server.

[0297] As used herein, the term "application server" refers to application software residing in the cloud that performs server functions.

[0298] The term "Internet of Things" or "IoT" refers to a system of interrelated computing devices, machines, and digital machines capable of transferring data with little or no human intervention and may involve technologies such as real-time analytics, machine learning and / or AI, embedded systems, wireless sensor networks, control systems, and automation (e.g., smart home, smart building, and / or smart city technologies). IoT devices are typically low-power devices without heavy computational or storage capabilities. An "Edge IoT device" may be any type of IoT device deployed at the edge of a network.

[0299] As used herein, the term “cluster” refers to a set or grouping of entities as part of one edge computing system (or multiple edge computing systems), in the form of physical entities (e.g., different computing systems, networks, or network groups), logical entities (e.g., applications, functions, security constructs, containers), etc. In some places, a “cluster” is also referred to as a “group” or a “domain.” Membership of a cluster may be modified or influenced based on conditions or functions, including from dynamic or property-based membership, from network or system management scenarios, or from various exemplary techniques described below that may add, modify, or remove entities in a cluster. A cluster may also include or be associated with multiple layers, levels, or characteristics, including variations in security features and results based on such layers, levels, or characteristics.

[0300] As used herein, the terms "instance," "instantiation," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object that may occur, for example, during the execution of program code.

[0301] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element or the data element that contains the contents.

[0302] The term "channel," as used herein, refers to any tangible or intangible transmission medium used to communicate data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar term indicating a path or medium over which data is communicated. Additionally, the term "link," as used herein, refers to a connection between two devices via a RAT for the purpose of transmitting and receiving information.

[0303] As used herein, the term "wireless technology" refers to technology for the wireless transmission and / or reception of electromagnetic radiation for information communication. The term "radio access technology" or "RAT" refers to technology used for the underlying physical connection to a radio-based communications network.

[0304] As used herein, the term "communications protocol" (wired or wireless) refers to a standardized set of rules or instructions implemented by a communications device and / or system to communicate with other devices and / or systems, including instructions for packetizing / depacketizing data, modulating / demodulating signals, implementing a protocol stack, and / or the like.

[0305] As used herein, the term "service function" or "SF" refers to a function that specifically represents a network service function responsible for specific processing of received packets other than the normal standard functions of an IP router on a network (e.g., IP forwarding and routing functions) between a source host and a destination host (see, e.g., [3]).

[0306] As used herein, the term "service function chain" or "SF chain" refers to a chain that defines an ordered set of abstract service functions and ordering constraints that must be applied to packets and / or frames and / or flows selected as a result of classification and / or policy.

[0307] As used herein, the term "service function chaining" or "SFC" refers to a mechanism for building service function chains and forwarding packets / frames / flows through them.

[0308] As used herein, the term "service function path" or "SFP" refers to a path that defines an ordered set of specific instantiations of service functions that a packet and / or frame and / or flow must visit within a particular service function chain. The SFP is determined from among the related service function paths within a particular service function chain to meet the capacity and QoS requirements of the service functions and their connecting links. Typically, there is a 1:n relationship between service function chains and service function paths.

[0309] As used herein, the term "service routing" refers to a unified service support platform built on DSN, which provides service registration, publication, discovery, triggering and access mechanisms, as well as enhanced capabilities for optimizing service delivery.

[0310] As used herein, the term "user plane" refers to the set of traffic forwarding components through which traffic flows.

Claims

1. One or more non-transitory computer readable media (NTCRMs) having instructions stored thereon that, when executed by one or more processors, cause a device of a wireless cellular network to: receiving configuration information for a service function path (SFP) that specifies a plurality of ordered service functions for service function chaining (SFC), the service function path including one or more ordered service functions to be provided by the wireless cellular network and one or more other ordered service functions to be provided by an edge data network, the edge data network being a local data network; configuring the SFP based on the configuration information to cooperate with an SFC function in the edge data network to provide the plurality of ordered service functions via the SFP across the wireless cellular network and the edge data network; One or more NTCRMs that cause the

2. The one or more NTCRMs of claim 1 , wherein the configuration information is received from an Operations, Administration, and Maintenance (OAM) entity or a Network Capabilities Repository Function (NRF) of the wireless cellular network.

3. The one or more NTCRMs according to claim 1 or 2, wherein the configuration information includes one or more SFC parameters based on a Service Level Agreement (SLA) for SFC services in the wireless cellular network.

4. 4. The one or more NTCRMs of claim 1, wherein the configuration information is received from an Edge Application Server (EAS) and indicates the plurality of ordered service features and associated parameters to be provided by the wireless cellular network.

5. 5. The one or more NTCRMs of claim 1, wherein configuring the SFP includes configuring one or more SFC User Plane Functions (SFCF-U) to provide the plurality of ordered service functions.

6. 6. The one or more NTCRMs of claim 5, wherein the configuration information includes an indication of one or more SFCF-U instances that support one or more of the plurality of ordered service functions.

7. 7. The one or more NTCRMs of claim 6, wherein the instructions, when executed, further cause the device to send a request for the configuration information associated with the one or more SFCF-U instances, the request identifying the plurality of ordered service functions.

8. The one or more NTCRMs according to claim 6 or 7, wherein the configuration information further comprises at least one of an SFC application ID or an SFC service ID associated with the respective one or more SFCF-U instances.

9. The one or more NTCRMs according to any one of claims 1 to 8, wherein the device implements an SFC Control Plane Function (SFCF-C).

10. One or more non-transitory computer readable media (NTCRMs) storing instructions that, when executed by one or more processors, cause an operations, administration, and maintenance (OAM) entity to: receiving, from a Service Function Chaining (SFC) Control Plane Function (SFCF-C), a request for information associated with one or more SFC User Plane Function (SFCF-U) instances supporting a plurality of ordered service functions associated with a service function path, the service function path including one or more ordered service functions to be provided by a wireless cellular network and one or more other ordered service functions to be provided by an edge data network, the edge data network being a local data network; sending said information associated with said one or more SFCF-U instances to said SFCF-C; One or more NTCRMs that cause the

11. The instructions, when executed, further cause the OAM entity to: determining that an SFCF-U instance supporting a first service function of the plurality of ordered service functions is not available; configuring a new SFCF-U instance to support the first service function based on the determination; 11. The one or more NTCRMs of claim 10.

12. 12. The one or more NTCRMs of claim 11, wherein the instructions, when executed, further cause the OAM entity to register the new SFCF-U instance with a Network Function Repository Function (NRF).

13. 13. The one or more NTCRMs of claim 12, wherein registering the new SFCF-U instance with the NRF includes providing information regarding at least one of an application ID and an SFC service ID associated with the SFCF-U instance.

14. An edge data network device, comprising: a traffic classifier that receives service function chaining (SFC) traffic from a wireless cellular network and routes the SFC traffic to a plurality of ordered service functions via a service function path (SFP), the service function path including one or more ordered service functions to be provided by the wireless cellular network and one or more other ordered service functions to be provided by the edge data network, the edge data network being a local data network; a traffic declassifier that receives SFP traffic from the SFP and provides the SFP traffic to an edge application server or an edge enabler server; An apparatus comprising:

15. 15. The apparatus of claim 14, wherein the traffic classifier further receives SFC policy information, the SFC traffic classifier identifying the SFP to route the SFC traffic based on the SFC policy information.

16. The apparatus of claim 15 , wherein the SFC policy information is received from the edge application server, the edge enabler server, or an operations, administration, and maintenance (OAM) entity of the wireless cellular network.

17. 17. The apparatus of claim 14, wherein the SFC traffic is received on an N6 interface and the SFP traffic is provided via an EDGE-X or EDGE-Y interface.

18. 18. The apparatus of claim 14, wherein the traffic de-classifier combines SFP traffic from multiple SFPs and provides the combined SFP traffic to the edge application server or the edge enabler server.

19. 19. The apparatus of claim 14, wherein the plurality of ordered service functions comprises one or more of a network address translation (NAT), an internet protocol (IP) tunnel endpoint, a packet classifier, a deep packet inspection (DPI), a lawful inspection (LI), a transmission control protocol (TCP) proxy, a load balancer, a firewall function, a transcoder, a video optimizer, a uniform resource locator (URL) filter, or an application detection and control (ADC).

20. 19. The apparatus of claim 14, wherein the traffic classifier receives SFC parameters for an SFC service associated with the SFC traffic, the SFC parameters including one or more of an SFC service ID, an SFC configuration including one or more service functions and associated service function parameters, or an SFP configuration including an SFP index and associated ordered service functions, and wherein the traffic classifier routes the SFC traffic further based on the SFC parameters.

21. 21. The apparatus of claim 20, wherein the SFC parameters further include one or more validity parameters for the SFC service, the one or more validity parameters including one or more of a duration, a scheduled time period, one or more application IDs, a packet data unit session type or other associated PDU session parameter, or a slice differentiator.

22. The apparatus of claim 14 , wherein the SFC traffic includes one or more of a user equipment (UE) address, an application ID, a media type, or a traffic priority.

Images