DE102021110435A1 - Components for a mobile communication network, method for a mobile communication network, and computer program - Google Patents

Abstract

A component for a mobile communication network is provided. The component for a mobile communication network comprises one or more interfaces that are configured to communicate with a third party from an external data network; and processing circuitry configured to control the one or more interfaces. Furthermore, the processing circuitry is configured to be communicated to the third party, e.g. B. a third party application, access to the provision of a service function chain, SF chain, policy for the use of the SF chain, which is used in the mobile communication network, is granted.

Description

area

The present disclosure relates to the field of network communication. In particular, the examples relate to a component for a mobile communication network, a method for a mobile communication network and a computer program.

background

The traffic control that z. B. is used in the Gi / SGi local network (Gi / SGi-LAN), a load distribution of this network can improve. In order to achieve an improved load distribution, z. B. the concatenation of network services can be used. A network operator can use this to set up suites or catalogs of paths for traffic to traverse. Each path can consist of any combination of connected services, depending on the requirements of the traffic. Different demands on the data traffic can be more security, lower latency times or an overall high quality of service. In the 5G context, the aspect of traffic control has not been investigated further. Therefore, there could be a need to improve traffic control in the 5G context.

Figure list

• zeigt ein Blockschaltbild eines Beispiels einer Komponente für ein mobiles Kommunikationsnetz;
• zeigt Beispiele für einen Anwendungsfall der Komponente;
• zeigt Implantationen einer SFC in dem in beschriebenen Bauteil;
• zeigt ein Beispiel für eine Service-Funktionskette mit einer oder mehreren Service-Funktionen und Service-Funktionspfaden in der Anwenderebene;
• zeigt Beispiele für Single PDU Session mit mehreren PDU Session Anchors;
• zeigt Beispiele für Methoden zur Konfiguration einer UE-Policy-Zustellung;
• zeigt Beispiele für den Informationsfluss der NEF-Dienstoperationen;
• zeigt ein Beispiel für ein Verfahren zur Bereitstellung von dienstspezifischen Informationen;
• zeigt ein Flussdiagramm eines Beispiels für ein Verfahren;
• illustriert ein Netzwerk gemäß verschiedener Ausführungsformen; und
• zeigt schematisch ein drahtloses Netzwerk in Übereinstimmung mit verschiedenen Ausführungsformen.

Some examples of devices and / or methods are described below by way of example only and with reference to the accompanying figures, in which

• shows a block diagram of an example of a component for a mobile communication network;
• shows examples of an application of the component;
• shows implantations of an SFC in the in described component;
• shows an example of a service function chain with one or more service functions and service function paths in the user level;
• shows examples of a single PDU session with multiple PDU session anchors;
• shows examples of methods for configuring UE policy delivery;
• shows examples of the flow of information of NEF service operations;
• shows an example of a method for providing service-specific information;
• Figure 3 shows a flow diagram of an example of a method;
• illustrates a network in accordance with various embodiments; and
• Figure 3 schematically shows a wireless network in accordance with various embodiments.

Detailed description

• [1] 3GPP TR22.808, Version 13.0.0, Freigabe 13: Studie über Flexible Mobile Service Steering (FMSS);
• [2] 3GPP TS22.101, Version 17.1.0: Universal Mobile Telecommunications System (UMTS); Service-Aspekte; Service-Prinzipien;
• [3] 3GPP TS 23.502 Version 16.4.0: Prozeduren für das 5G-System (5GS);
• [4] 3GPP TS23.503, Version 16.4.1: 5G; Policy and Charging Control Framework für das 5G-System; Stufe 2; und
• [5] 3GPP TS 23.501 Version 16.4.0: 5G; Systemarchitektur für das 5G-System.

In the following, some examples are explained using a 3GPP system (from 3rd Generation Partnership Project). Details on the background of these systems can be found in the specifications of the 3GPP. Examples of these specifications are:

• [1] 3GPP TR22.808, Version 13.0.0, Release 13: Study on Flexible Mobile Service Steering (FMSS);
• [2] 3GPP TS22.101, version 17.1.0: Universal Mobile Telecommunications System (UMTS); Service aspects; Service principles;
• [3] 3GPP TS 23.502 version 16.4.0: Procedures for the 5G system (5GS);
• [4] 3GPP TS23.503, version 16.4.1: 5G; Policy and Charging Control Framework for the 5G system; Level 2; and
• [5] 3GPP TS 23.501 version 16.4.0: 5G; System architecture for the 5G system.

• • Ein fehlendes konsolidiertes Netzmanagement und/oder Management der SFC zwischen z. B. einem 5G-Netz und einem N6-LAN kann ein potenzielles Interoperabilitätsproblem verursachen. Dieses Problem kann auch innerhalb eines Mobilfunknetzes desselben Netzbetreibers auftreten und zu unkoordinierten und ineffizienten Service-Function-Path (SFP)-Einstellungen für das Routing von End-to-End- (E2E-) Diensten mit einer gewünschten Service-Funktion führen;
• • Eine reduzierte Kontrolle über die Dienstfunktion (SF). Die SF kann z. B. von Betreibern und/oder Dritten im (S)Gi-LAN/N6-LAN anstelle des 5GS bereitgestellt werden. Die Verkettung von SFs im (S)Gi-LAN/N6-LAN kann zu Verzögerungen in jedem Hop beitragen, was zu Latenzproblemen führt. Die Latenz kann für verschiedene Dienste, die auf eine extrem niedrige Latenz abzielen, von entscheidender Bedeutung sein, z. B. interaktive Augmented Reality (AR)/ Virtual Reality (VR)-Spiele, Fernsteuerung von unbemannten Luftfahrzeugen (UAV), Produktion von audiovisuellen Diensten, industrielle Automatisierung, kritische medizinische Anwendungen, selbstfahrende Fahrzeuge usw.;
• • Eine verringerte Benutzererfahrung bei der Berücksichtigung der Dienstkontinuität, z. B. in Roaming-Szenarien zwischen dem heimischen öffentlichen Land-Mobilfunknetz (HPLMN) und dem virtuellen öffentlichen Land-Mobilfunknetz (VPLMN) oder zwischen dem öffentlichen Land-Mobilfunknetz (PLMN) und dem nicht-öffentlichen Netz (NPN);
• • Erschwerte Bedingungen bei der Unterstützung von Service-Funktionen im N6-LAN in verschiedenen Netzwerken und Service-Einsatzszenarien und bei der Erfüllung erforderlicher Key-Performance-Indikatoren (KPIs) für diese Services aufgrund einer erhöhten Nachfrage nach Unterstützung vielseitiger vertikaler Services in 5GS.; und
• • Fehlender Zugang zu fortgeschrittenen Funktionen von 5GS im Vergleich zu (S)Gi-LAN/N6-LAN (oder allgemeinerem Netzwerk mit flexibler Steuerung mobiler Dienste, FMMS und/oder erweitertem FMMS, eFMMS), z. B. Netzwerk-Slicing, Netzwerkfunktionsvirtualisierung und Edge Computing usw.

The use of Service Function Chaining (SFC) beyond the (S) Gi interface is discussed in [1], but does not mention 5G systems (5GS). Furthermore, the traffic control on the (S) Gi- Interface discussed in [2]. However, it only shows for the assumption that the (S) Gi-LAN is outside the 5G range. The same assumption also applies to N6 LAN in the 5G context. By considering the (S) Gi-LAN / N6-LAN outside the 5GS area, the chaining of services within the (S) Gi-LAN / N6-LAN can only be controlled by a system that is separate from 5GS. However, this separation of the individual service functions in the N6 LAN from the 5GS architecture can have some disadvantages. For example:

• • A lack of consolidated network management and / or management of the SFC between z. B. a 5G network and an N6 LAN can cause a potential interoperability problem. This problem can also occur within a cellular network of the same network operator and lead to uncoordinated and inefficient Service Function Path (SFP) settings for the routing of end-to-end (E2E) services with a desired service function;
• • Reduced control over the service function (SF). The SF can e.g. B. provided by operators and / or third parties in the (S) Gi-LAN / N6-LAN instead of the 5GS. The chaining of SFs in the (S) Gi-LAN / N6-LAN can contribute to delays in each hop, which leads to latency problems. Latency can be critical for various services that aim for extremely low latency, such as: B. Interactive Augmented Reality (AR) / Virtual Reality (VR) games, remote control of unmanned aerial vehicles (UAV), production of audiovisual services, industrial automation, critical medical applications, self-driving vehicles, etc .;
• • A reduced user experience when considering service continuity, e.g. B. in roaming scenarios between the domestic public land mobile network (HPLMN) and the virtual public land mobile network (VPLMN) or between the public land mobile network (PLMN) and the non-public network (NPN);
• • Difficult conditions when supporting service functions in the N6 LAN in various networks and service deployment scenarios and when meeting the required key performance indicators (KPIs) for these services due to the increased demand for support for versatile vertical services in 5GS .; and
• • Lack of access to advanced functions of 5GS compared to (S) Gi-LAN / N6-LAN (or more general network with flexible control of mobile services, FMMS and / or extended FMMS, eFMMS), e.g. B. Network Slicing, Network Function Virtualization and Edge Computing, etc.

By integrating an SFC functionality into the 5GS, which enables the 5GS to both generate an SFC and to grant a third party access to this SFC, improved control of the SFC by the 5GS can be achieved, resulting in a more stringent one Control of the SFC can result, thereby reducing one of the disadvantages mentioned.

Various examples will now be described more fully with reference to the accompanying drawings, in which some examples are shown. In the figures, the thicknesses of lines, layers and / or areas may be exaggerated for clarity.

Accordingly, other examples with various modifications and alternative forms are possible, some specific examples of which are shown in the figures and then described in detail. However, this detailed description does not limit other examples to the particular forms described. Other examples may cover all modifications, equivalents, and alternatives that fall within the scope of the disclosure. Throughout the description of the figures, the same reference symbols refer to the same or similar elements which, when compared with one another, may be identical or implemented in a modified form while providing the same or a similar functionality.

It will be understood that when an element is referred to as being “connected” or “coupled” to another element, the elements may be connected or coupled directly, or through one or more intermediate elements. When two elements A and B are combined using an "or" it is to be understood that all possible combinations are disclosed; H. only A, only B and A and B. An alternative formulation for the same combinations is “at least one from group A and B”. The same applies to combinations of more than two elements.

The terminology used herein to describe particular examples is not intended to be limiting of additional examples. When a singular form, e.g. B. "ein, an" and "der, die, das" is used and the use of only a single element is neither explicitly nor implicitly defined as mandatory, further examples can also use plural elements to implement the same function. Likewise, if functionality is described below as being implemented with multiple elements, other examples may implement the same functionality with a single element or a single processing unit. It is further to be understood that the terms “comprises”, “containing”, “includes” and / or “including”, when used, the presence of the specified features, integers, steps, operations, processes, acts, elements and / or specify components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, processes, acts, elements, components and / or a group thereof.

Unless otherwise defined, all terms (including technical and scientific terms) are used herein with their customary meaning of the subject area to which the examples belong.

Figure 3 shows a block diagram of an example of a component 30th for a mobile communication network. The component 30th comprises one or more interfaces configured to communicate with a third party outside of the mobile communication network. The component also includes 30th processing circuitry 34 configured to control the one or more interfaces and to be shared with the third party, e.g. A third party application is granted access to provide a service function chain, SF chain, policy on the use of the SF chain employed in the mobile communications network.

A third party can be a trusted data network and / or an external data network, e.g. B. a packet data network for streaming. The cellular network can be a 5G cellular network (e.g. a 5GS).

In one example, the processing circuitry can be further configured to enable Service Function Chaining, SFC, by controlling and / or managing the SF chain based on the SF chain policy; and forwards data through the SF chain. By controlling and / or managing the SF chain and providing access to third parties, the processing circuitry 34 enabled to perform SFC. The provision of access for the third party can, for example, be achieved by receiving the SFC policy and forwarding packets / frames / flows to / from the third party via the interface 32 based on the received SFC policy.

The SFC (in the 5GS) can be activated by a network function, e.g. B. a Service Function Chaining Function (SFCF) are supported. The SFCF can be in a user level function (UPF; this is also referred to as SFCF-U) or a control plane function (CPF; this is also referred to as SFCF-C) or be combined in the UPF and the CPF (also referred to as SFCF-UC). Optionally or alternatively, the SFCF can be supported by existing (5G) network functions, e.g. B. Policy Control Function (PCF), Session Management Function (SMF) (for SFCF-C, SFCF-UC) or UPF (for SFCF-U, SFCF-UC).

In order to support SFC for 5G networks, a network operator can, for example, define guidelines for the chaining of services in order to direct the data traffic associated with the application and its users on a UE basis to suitably ordered service functions.

To control access to the SFC, it can have SFC policies that only allow access for a certain third party. The SFC policies can dynamically change from an application function (AF) to a network function (NF), e.g. B. PCF, SFCF-U, SFCF-C or an operation, administration and maintenance function (OAM) can be provided. For example, a third party (AF) can make an SFC policy available to the 5G network (e.g. via AF of a control level). The SFC policy can contain parameters and / or a configuration of the SF chain. For example, the application (AS) of a third party can send and / or receive data traffic to the SFC in the 5G network.

In addition, if the SFC policies are provided as part of the quality of service agreement (SLA) between the 5G network operator and third parties for the SFC service, the 5G network can still have a 3GPP management service for the control and orchestration of the SFC in the SFCF Provide U based on standard service function chaining policies contained in the service level agreement (SLA).

For example, the network operator must be able to define and change guidelines for the chaining of services in order to control the data traffic per application and per end device through the necessary chaining of services with ordered services in order to ensure the QoE (Quality of experience) of the Improve user.

For example, the policy for the chaining of services must be able to differentiate between upstream and downstream traffic.

So z. B. the coexistence of traffic with and without service function chaining can be supported.

For example, the SFC must provide suitable means for authorized third parties to request a chain of service functions, which are provided by the network operator, based on the operator's guidelines for the chaining of service functions.

For example, the management of the service functions must enable the operator to create, change and delete a service function on the basis of the operator's guidelines for the chaining of service functions.

For example, the administration of the service functions must enable the operator to create, configure and control a chain of service functions for each application and its users on the basis of the operator's guidelines or requests from third parties.

In one example, the SFC can include at least one element from the group of network address translation, NAT, IP tunnel endpoints, packet classifiers, deep packet inspection, DPI, lawful inspection, LI, Transmission Communication Protocol (TCP) proxies, load balancer, firewall Features include transcoders, video optimizers, application detection and control, antimalware, KPI monitoring, distributed denial of service (DDoS) protection, and parental controls. This is not an exhaustive list and the solutions have no limitation for the mentioned SFs.

As in 1 shown, the respective interface (s) 32 with the respective processing circuitry 34 on the component 30th coupled. In examples, the processing circuitry may 34 using one or more processing units, one or more processing devices, any means for processing, such as for example a processor, a computer or a programmable hardware component that is operable with appropriately adapted software. Likewise, the described functions of the processing circuit arrangement 34 also be implemented in software, which is then executed on one or more programmable hardware components. Such hardware components may include a general purpose processor, a digital signal processor (DSP), a microcontroller, and so on. The processing circuitry 34 is able to interface 32 to control so that any data transfer that occurs over the interface and / or any interaction in which the interface may be involved by the processing circuitry 34 can be controlled.

In one example, the control unit 30th a memory and at least one processing circuitry 34 operably coupled to the memory and configured to perform the method described below.

In examples, the one or more interfaces 32 correspond to any means for obtaining, receiving, transmitting or providing analog or digital signals or information, e.g. B. any connector, contact, pin, register, input connection, output connection, conductor, trace, etc., which enables the provision or receipt of a signal or information. An interface can be wireless or wired and it can be configured in such a way that it communicates information with further internal or external components, ie sends or receives signals. The one or more interfaces 32 may include further components to enable communication between vehicles. Such components can be transceiver components (transmitter and / or receiver), such as e.g. B. one or more low-noise amplifiers (LNAs), one or more power amplifiers (PAs), one or more duplexers, one or more diplexers, one or more filters or filter circuits, one or more converters, one or more mixers, appropriately adapted high-frequency components, etc. .

Further details and aspects are mentioned in connection with the examples described below. This in The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed concept or one or more examples described below (e.g. - ) to be named.

shows examples of an application of the component. In the three in 2a - 2c Examples shown can be a component 30th as in relation to 1 described, can be used.

2a shows an example for a user 201a , 202a , 203a , the content from a third party, e.g. a packet data network 210a , requests. The packet data network 210a can be three different third parties 221a , 222a , 223a include, e.g. B. Content Providers 221a , 222a , 223a for streaming. In the 5GS 200a , e.g. B. a 3GPP network 200a , an SFC can be from the component 30th be generated. The SFC can have three different service function paths (SFP) 211a , 212a , 213a each include a specific content provider 221a , 222a , 223a are assigned, e.g. B. for streaming. Any content provider 221a , 222a , 223a may require different service functions, e.g. B. for the video optimization security functions based on the subscription of the user, the subscription of the network service etc. These different functions can be provided by the SFC, in particular by the provision of three different SFPs 211a , 212a , 213a . By controlling, managing and orchestrating the SFCs in the 3GPP network 200a, a mobile radio network operator (MNO) can provide the service chaining service for the inclusion of value-added services and security functions for the providers of content services.

shows an example of an AR / VR production in a cellular network 200b , e.g. an NPN 200b . Different third parties 221b , 222b , e.g. B. different stations 221b , 222b , may need different SFs for their devices 201b , 202b , 203b , 204b on site, e.g. B. Camera 201b , 203b or microphone 202b , 204b . These different SFs can be obtained from the NPN 200b provided, e.g. B. from a component 30th that generate SFs and provide access for the third party 221b , 222b what can enable SFCs 211b , 212b leads. This from the component 30th in the NPN 200b Enabled SFC service can enable the NPN provider to use the third party providers 221b , 222b to offer an SFC service and the third-party providers to configure the required SFPs for their devices 201b , 202b , 203b , 204b to enable. This eliminates the need for each transmitter to manually configure their N6-LAN or to make the configuration of the N6-LAN available to the NPN provider as part of a service contract.

shows an example of a Vehicle to Everything (V2X) communication. The vehicle 240 can be in its a cellular network 201c , e.g. an HPLMN or in different roaming networks 200c , 202c , e.g. move HPLMN, VPLMN and / or PLMN. The vehicle 40 can be done via the respective SFC 211c , 212c , 213c for every cellular network 200c , 201c , 202c with a third party 210c , for example a data packet network. The SFC can e.g. B. have the same service functionality, e.g. B. TCP proxies, transcoder, firewall, etc. This functionality can be provided and / or managed by the cellular network operator. This can enable the provider to ensure the provision of the required key performance indicators (KPIs) and security features with consistent carrier-grade performance in the 5G network (e.g. as in TS22.886 section 5.27.6 described: Support of automated driving in multi-PLMN environments), which leads to improved performance.

Further details and aspects are mentioned in connection with the examples described above and / or below. This in 2 The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed concept or one or more of the above (e.g. 1 ) and / or below (e.g. 3 - 11 ) are mentioned examples.

shows implantations of an SFC in the in described component. In one example, the SFC can be used in a user level, UP, and / or a control level, CP, of the component by an SFCF.

shows an example of a reference architecture that uses the SF chain in a UPF of the in component described (reference point representation; subnetwork functions are included in this reference architecture). In one example, the SFCF (SFCF-U) may be enabled and located in a user level function, UPF, of the component. The SFCF-U 350 can in the UPF 360 integrated, the N6 reference points with a trustworthy data network 322 or an external data network 321 concludes. The N6 reference points can generate an N6 interface.

In one example, the processing circuitry may be further configured to allow a third party application server, AS, to access the SFC located in the UPF using N6 reference points. An AS can be in the trustworthy data network 322 as well as in the external data network 321 are located. A policy to route traffic through a specific SFP may be required, which PCF can configure through SMF.

For AS in the external data network 321 An application function (AF) can derive the guidelines for the chaining of service functions via a network exposure function (NEF) via an N33 interface. For AS in the trustworthy data network 322 can provide the AF Service Function Chaining Policies (Policy for SFC) directly via PCF via the N5 interface.

shows an example of a reference architecture that supports an independent service function chain (reference point representation; subnetwork functions are contained in this reference architecture).

In one example, the SFC (SFCF-U) can be a stand-alone network function that is between a UPF 360 the component and a third-party AS 321 , 322 is located. The UPF 360 can include an SFC (in not shown). The third party 321 , 322 can be a trusted DN 322 and / or an external DN 321 be.

In one example, the processing circuitry may be further configured to work for a third party AS 321 , 322 access to the SFC 350 (SFCF-U) using N6 and / or extended N6, N6e, reference points and / or N9 reference points. An interface between UPF 360 and SFCF-U 350 can be an N6 interface, N6e interface (enhanced N6) or N9 interface. An interface between the SFCF-U 350 and an AS of each DN 321 , 322 can be an N6 interface. Both UPF and SFC may need to be configured to set the SFPs.

In one example, the processing circuitry may be further configured to assign the UP for a Protocol Data Unit (PDU) using a session management function (SMF). A policy for a specific PDU session for data traffic that must run via an SFP can be configured by the PCF directly via a new interface Nx or via SMF / UPF. For the AS in the external data network 312 , 322 AF can infer the guidelines for the chaining of services via NEF via the N33 interface. For the AS in the trustworthy data network, the AF can provide guidelines for the chaining of services directly via PCF via the N5 interface.

shows the reference architecture that forms an independent service function chain at the end of N6 supported (service-based representation; subnet functions are included in this reference architecture). In can SFCF-U 350 with UPF 360 work together via a new reference point N6S to the UPF 360 control received traffic.

shows a service-based architecture that includes an SFCF-UC in (User Plane and) Control Plane (service-based representation; subnetwork functions are included in this reference architecture). In one example, the SFCF (SFCF-UC) may be enabled and located in the UPF and a control level function (CPF) of the component. The UPF 360 consists of an SFCF-U (not shown). The SFCF-UC is a combined function for the control level (SFCF-U) and the user level (SFCF-C), which includes an SFCF-C 351 for the control level and an SFCF-U (not shown, in the UPF 360 included) for the user level. The SFCF-C 351 located in a CPF that coincides with the UPF 360 cooperates via a new reference point Nx to keep track of the traffic (in the UPF 360 ) to control.

In one example, the SFCF in the UP can work together with the UPF via a reference point Nx in order to control the traffic in the UPF and / or the service SFCF in the CP contains the SFC. The SFC policies may be needed to direct the traffic that needs to be routed through a particular SFP. A guideline for the control of the data traffic that has to be routed through a specific SFP can be found on the SFCF-C 351 and SMF can be configured directly from the PCF. The SMF can use the UPF 360 configure for traffic that requires SFCF-U handling.

In one example, the processing circuitry may be further configured to configure the SMF for traffic requiring service function chaining services, the UPF to route traffic to the SFCF in the UP to pass through a configured SFP, and the SFCF to route traffic back to the UPF. The UPF 360 can route traffic to the SFCF-U to route it through the configured SFPs and then route the traffic back to the UPF 360 . For an AS in an external data network, the AF can inference the guidelines for the chaining of services via NEF via the N33 interface. For AS in the trustworthy data network, the AF can provide guidelines for the chaining of services directly via PCF via the N5 interface.

shows a service-based architecture that uses an SFCF-C 351 in the control level and an SFCF-U 350 at the user level (service-based representation; subnet functions are included in this reference architecture). In a separation of CP and UP functions for the SFC service be applied. In one example, the SFCF can perform a variety of network functions 350 , 351 include, with a first SFCF (SFCF-U, 350 ) is activated and located in the UPF and a second SFCF (SFCF-C, 351 ) is activated and located in the CPF.

The SF chain can be in an SFCF-C 351 handled to manage SFC policies and the SFCF-U 350 to be configured via a new interface Nx in which the SFCF-U and the UPF 360 cooperates via a new reference point N6S to the UPF 360 control received traffic.

In one example, the processing circuitry may be further configured to configure the UPF through the SMF for traffic that requires SCF services and to route the traffic over an N6S interface to the SCFC in the UP to pass an SFP and forward the traffic over an N6 interface. An SFC policy for routing the data traffic that must be routed through a specific SFP can be sent to SFCF-U 350 by SCFC-C 351 can be configured. The SMF can create a UPF with routing paths to one or more SFCF-U (s) 350 configure for SFC services. The UPF 360 can forward the data traffic to one or more SFCF-U (s) in order to route it via configured SFPs. For an AS in the external data network, the AF can transfer the guidelines for the chaining of services via NEF via the N33 interface to SFCF-C. For an AS in the trustworthy data network, the AF can provide guidelines for the chaining of services directly or via PCF via the N5 interface to SFCF-C.

Note that if PCF can support SFC configuration, i. H. with the functionality of the SFCF-C function, which SFCF-C can be located at PCF.

Further details and aspects are mentioned in connection with the examples described above and / or below. This in 3 The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed concept or one or more of the above (e.g. 1 - 2 ) and / or below (e.g. 4th - 11 ) described examples.

shows an example of a service function chain 400 with one or more service functions 440 , 441 , 442 , 443 and service function paths 445 , 446 , 447 in the user level. In one example, the PDU session may contain a flow of traffic that is transported over identical or different service function paths, SFPs. An SFCF in a user level, e.g. B. a UPF with SFCF-U capabilities (e.g. or SFCF-U (e.g. , contains an SFC with SFs 440 , 441 , 442 , 443 that have one or more SFPs 445 , 446 , 447 can form.

In one example, the processing circuitry may be further configured to include a service functional path, SFP, the SFC 480 to configure based on an SFC policy for the traffic flow of the PDU session using the SMF and / or the SFCF (SFCF-C). The SFPs 445 , 446 , 447 can be ordered in a specific order. In every SFP 445 , 446 , 447 can the traffic through the ordered SFs 440 , 441 , 442 , 443 flow.

In one example, when the traffic flow is not assigned to an SFP, the traffic flow can skip all SFs in the SFC. Each SFC can e.g. B. one or more SFs 440 , 441 , 442 , 443 contain. So z. B. different SFCs 480 an identical or a different group of SFs in the UP 440 , 441 , 442 , 443 contain. For example, the traffic classifier can be 450 , the SF (s) 480 and the traffic declassifier 452 are in the same or a different network function.

The SF can, for example, a function from the group (but not limited to) network address translation (NAT), IP tunnel endpoints, packet classifiers, deep packet inspection (DPI), lawful inspection (LI), TCP proxies, load balancers, firewall Functions that include transcoders, url filters, application detection and control (ADC) and video optimizers.

In one example, an SFC parameter and / or a traffic classifier 450 for the SFC policy for the AS at least one element of the group SFC display, the SFC configuration, the SFP configuration, the application ID and the corresponding SFP index, the associated PDU session parameters, including the PDU session type or of a slice / service type, SST, and the slice differentiator, SD.

• - SFC-Service-ID: die Service-ID dieses Satzes von SFC-Parametern für den SFC-Service;
• - SFC-Konfiguration: ein oder mehrere SFs mit den entsprechenden SF-Parametern;
• - SFP-Konfiguration: den SFP-Index mit den entsprechenden geordneten SFs;
• - SFC-Routing-Richtlinie und
• - Gültigkeitsparameter für den SFC-Dienst identifiziert durch die SFC-Service-ID.

In an example, the SFC parameter of the SFC service can contain an element from the following group:

• - SFC service ID: the service ID of this set of SFC parameters for the SFC service;
• - SFC configuration: one or more SFs with the corresponding SF parameters;
• - SFP configuration: the SFP index with the corresponding ordered SFs;
• - SFC routing policy and
• - Validity parameters for the SFC service identified by the SFC service ID.

• ◯ der Verkehrsklassifizierer 450 kann die Abbildung zwischen einem SPF-Index und Verkehrsfilterungsregeln für die Weiterleitung von Verkehr an den ersten SF in einem SFP anzeigen, der durch einen SFP-Index identifiziert wird, und
• ◯ der Verkehrsentklassifizierer 451 kann mit Traffic-Filterregeln zum Kombinieren von Traffic aus dem letzten SF in einem SFP, der durch einen SFP-Index identifiziert wird, angeben.

In one example, the SFC routing policy may include a traffic classifier that indicates the mapping between an SPF index and traffic filtering rules for forwarding traffic to the first SF in an SFP identified by an SFP index and / or a traffic declassifier indicating rules for combining traffic from an SF in an SFP identified by an SFP index. For example:

• ◯ the traffic classifier 450 can display the mapping between an SPF index and traffic filtering rules for forwarding traffic to the first SF in an SFP identified by an SFP index, and
• ◯ the traffic declassifier 451 can specify traffic filtering rules to combine traffic from the last SF into an SFP identified by an SFP index.

• ◯ Dauer;
• ◯ Geplante Zeitspanne, z. B. täglich 8-20 Uhr, etc.;
• ◯ Anwendungs-ID(s); und
• ◯ Zugehörige PDU-Sitzungsparameter, einschließlich PDU-Sitzungstyp, z. B. IP/Ethernet/Unstructure, DNN, oder ein Slice/Service-Typ (SST) (z. B. eMBB, URLLC, MIoT, V2X usw.) und optionaler Slice Differentiator (SD).

In one example, the validity parameters for the SFC, the validity parameters for the SFC service can contain an element from the following group:

• ◯ duration;
• ◯ Planned time period, e.g. B. daily 8 a.m.-8 p.m., etc .;
• ◯ application ID (s); and
• Associated PDU session parameters, including PDU session type, e.g. B. IP / Ethernet / Unstructure, DNN, or a slice / service type (SST) (e.g. eMBB, URLLC, MIoT, V2X etc.) and optional slice differentiator (SD).

In one example, the traffic classifier provides 450 an SPF index assigned to an SFC classifier. The traffic classifier 450 may provide an SPF index associated with the SFC classification policy that may contain one or more of the following information at different levels or granularities per package, e.g. B. UE address, application ID, media type and / or traffic priorities.

In one example, the traffic classifier comprises 450 a DPI capability that can be used to share the traffic payload. If information is only available in the traffic payload, the DPI capability on the traffic classifier may be 450 to be required.

In one example, the traffic declassifier 451 an N6 tunnel ID, which is the N6 reference point of a DNAI, data network access ID, for a DN 210 complete with the mapping to the SFC reclassification guideline. For example, the traffic declassifier 451 provide an "N6 tunnel ID" which is the N6 reference point of a DNAI (data network access ID) for a DN 210 concludes with the mapping to the SFC reclassification policy that includes one or more of the following information to combine traffic from one or more SFPs before forwarding them to an application's application server, such as: B. UE address, application ID, media type, traffic priorities and / or SPF index. In one example, the SFC reclassification policy may contain one of the following group: UE address, application ID, media type, traffic priorities, and / or SPF index.

In one example, the traffic declassifier comprises 451 a DPI capability that can be used to release traffic payload. If information may only be in one traffic payload, the DPI capability on the traffic declassifier may be a problem 451 are needed.

Further details and aspects are mentioned in connection with the examples described above and / or below. This in 4th The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed Concept or one or more above (e.g. 1 - 3 ) and / or below (e.g. 5 - 11 ) described examples were mentioned.

shows examples of single PDU sessions with several PDU session anchors (state of the art; [5]). shows an example of a user plane architecture for the uplink classifier. shows a multi-homed PDU session: case of continuity of service.

• - Die UPF, die jede dieser Schnittstellen abschließt, soll die Funktionalität eines PDU-Sitzungsankers (PSA) unterstützen, wobei jeder PSA, der eine PDU-Sitzung unterstützt, einen anderen Zugriff auf denselben DN bietet.
• - Die UPF, die in der Lage ist, mehrere PSAs zu terminieren, kann mit UL Classifier- (UL CL-) Funktionalität für eine PDU-Sitzung gemäß Abschnitt 5.6.4.2 oder mit IPv6-Multihoming-Funktionalität für eine PDU-Sitzung gemäß Abschnitt 5.6.4.3 sein.

According to [5], the SMF can control the data path of a PDU session in order to support the selective traffic routing or the service continuity to the DN according to Section 5.6.9.2.3 so that the PDU session can correspond to several N6 interfaces at the same time.

• The UPF that terminates each of these interfaces is intended to support the functionality of a PDU session anchor (PSA), with each PSA that supports a PDU session providing a different access to the same DN.
• - The UPF, which is able to terminate several PSAs, can be used with UL Classifier (UL CL) functionality for a PDU session in accordance with Section 5.6.4.2 or with IPv6 multihoming functionality for a PDU session in accordance with Section 5.6.4.3.

If the PSA is on the local entrance near the RAN node, it enables edge computing support. In one example, the processing circuitry can be further configured to add a PSA at a local access near the RAN node, thereby enabling edge computing. Edge computing can be enabled for the PDU session.

If SFC is supported, the SMF can assign a UL-CL capable UPF or an IPv6 branchable UPF with multiple PSAs with SFCs for a PDU session where each PSA supports SFC with different SFs and one or more SFPs and on different ones N6 terminated to the same DN.

• - Beispiel 1: Der UPF ermöglicht die Unterstützung von Verkehrsklassifizierern für SFC und die Lenkung der Verkehrsströme zu verschiedenen SFP in verschiedenen SFC an der PSA.
• - Beispiel 2: SFCs auf mehreren Ebenen können unterstützt werden, indem sowohl der Verkehrsklassifizierer als auch die SFC am UL CL/IPv6-Verzweigungs-UPF aktiviert werden, bevor die Verkehrsströme zu verschiedenen SFCs an der PSA geleitet werden.

The following example can be supported for the UL CL UPF or IPv6 branching UPF:

• - Example 1: The UPF enables the support of traffic classifiers for SFC and the routing of traffic flows to different SFPs in different SFCs at the PSA.
• - Example 2: Multi-level SFCs can be supported by enabling both the traffic classifier and the SFC on the UL CL / IPv6 branch UPF before the traffic flows are directed to different SFCs on the PSA.

• - Beispiel 1, der UL CL UPF in und die IPv6-Verzweigung in hat einen Verkehrsklassifizierer für SFC, um die Verkehrsströme in Richtung PSA1 und PSA2 zu lenken, basierend auf den SFP-Richtlinien.
• - Beispiel 2, der UL CL UPF in oder die IPv6-Verzweigung in ermöglicht einen SFC der ersten Schicht. Die PSA1 und PSA2 ermöglichen darüber hinaus eine SFC der zweiten Schicht, indem sie Verkehrsklassifizierer verwenden, um Verkehrsströme zu SPFs zu lenken.

and show the schematic of two examples of UL CL UPF or IPv6 branching.

• - Example 1, the UL CL UPF in and the IPv6 branch in has a traffic classifier for SFC to direct the traffic flows towards PSA1 and PSA2 based on the SFP guidelines.
• - Example 2, the UL CL UPF in or the IPv6 branch in enables a first layer SFC. The PSA1 and PSA2 also enable a second layer SFC by using traffic classifiers to direct traffic flows to SPFs.

In one example, the processing circuitry can be further configured to obtain information for the assignment / configuration using the SMF from a Unified Data Repository (UDR) of the mobile communication network that the service subscription of a user equipment (UE) via a Policy Control Function (PCF ) of the mobile communication network that stores the UE service policy.

For example, when the SMF assigns a UPF to a UE for a PDU session of a UE, the SFC can be applied based on the UE service policy stored in the PCF and a UE service subscription stored in the UDR. For example, SFCF-U can be supported with UPF. The SMF can configure a UPF with SFCF-U that contains an SFC with one or more SFPs for the PDU session. The assignment of SFCF-U and SFPs can be based on the UE service policy stored in the PCF and the UE service subscription stored in the UDR.

In one example, the processing circuitry may be further configured to assign UPF with SFCF and / or standalone SFCF using the SMF for the PDU session in which each PSA supports SFC with different ordered SFs and one or more SFPs, and That you have the UPFs with SFCF and / or standalone SFCF to different N6 interfaces to the same data network, DN, terminated. For example, the SMF can configure a UPF with SFCF-U information to route traffic to the SFCF-U with one or more SFPs for the PDU session. The assignment of SFCF-U and SFPs can be based on the UE service policy stored in the PCF and the UE service subscription stored in the UDR.

For example, the SFCF-U can be configured by the SMF with the SFC configuration provided by the PCF. For example, the SFCF-U can be configured by the SFCF-C and make the information available to the SMF.

In one example, the processing circuitry can be further configured to control a data path of the traffic flows of the PDU session using the SMF so that the PDU session can include multiple N6 interfaces at the same time based on the routing policy issued by the AS is requested via the AF of the mobile communication network.

The PSA can forward the traffic to the standalone SFCF (SFCF-U) via the N6S interface.

If the SFC is supported, the SMF can assign a UL-CL capable UPF or an IPv6 branchable UPF with multiple PSAs for a PDU session where each PSA can handle traffic to the SFCF / SFCF-U) with required SFs and a or several SFPs that end on different N6 interfaces to the same DN.

• - Wenn SFC unterstützt wird, kann das SMF einen UL-CL-fähigen UPF oder einen IPv6-verzweigungsfähigen UPF mit mehreren PSAs für eine PDU-Sitzung zuweisen, bei der jeder PSA den Verkehr in Richtung verschiedener SFCFs mit erforderlichen SFs und einem oder mehreren SFPs weiterleitet und zu jedem PSA zurückkehrt, die an verschiedenen N6 zum selben DN enden.
• - Das SMF konfiguriert UL CL/IPv6 Branching UPF und PSAs für den Verkehr, der eine SFCF-Behandlung erfordert. Die PSA leitet den Datenverkehr zum SFCF, um ihn über konfigurierte SFPs zu leiten, und leitet den Datenverkehr dann zurück zur PSA.

In one example, the processing circuitry can be further configured to use multiple UPFs by using uplink classification functionality (UL CL) and / or IPv6 branching functionality to control the data path, including a UPF capable of multiple PDU session anchor, PSA, schedule, and several UPFs that support the PDU session anchor, PSA, functionality. The policy for routing the data traffic may be required to pass a specific SFP and can be configured on the SCFC and SMF directly from the PCF.

• - If SFC is supported, the SMF can assign a UL-CL capable UPF or an IPv6 branchable UPF with multiple PSAs for a PDU session, where each PSA can handle traffic towards different SFCFs with required SFs and one or more SFPs forwards and returns to any PSA ending on different N6 to the same DN.
• - The SMF configures UL CL / IPv6 branching UPF and PSAs for traffic that requires SFCF handling. The PSA routes traffic to the SFCF to route it through configured SFPs and then routes the traffic back to the PSA.

• - Wenn SFC unterstützt wird, kann das SMF einen UL-CL-fähigen UPF oder einen IPv6-verzweigungsfähigen UPF mit mehreren PSAs für eine PDU-Sitzung zuweisen, in der jeder PSA den Verkehr zu verschiedenen SFCF-U mit erforderlichen SFs und einem oder mehreren SFPs weiterleitet, die an verschiedenen N6 zum selben DN enden.

The policy for routing data traffic may be required to pass a specific SFP and can be configured on the SCFC-U by SFCF-C.

• - If SFC is supported, the SMF can assign a UL-CL capable UPF or an IPv6 branchable UPF with multiple PSAs for a PDU session in which each PSA can handle traffic to different SFCF-U with required SFs and one or more Forwards SFPs that end on different N6s on the same DN.

When using IPv6 branching, the UE has been assigned two IPv6 prefixes (provided there are two PSAs). The UE can direct the traffic with different IPv6 prefixes in the direction of the DN.

• - SFC-Anzeige: zeigt an, dass die Parameter der UE-Policy für die SFC-Dienstkonfiguration sind;
• - SFC-Service-ID: die Service-ID dieses Satzes von SFC-Parametern für den SFC-Service;
• - SFC-Konfiguration: ein oder mehrere SFs mit den entsprechenden SF-Parametern;
• - SFP-Konfiguration: den SFP-Index mit den entsprechenden geordneten SFs;
• - SFC-Routing-Richtlinie:
  • o Verkehrsklassifizierer zeigt die Zuordnung zwischen einem SPF-Index und Verkehrsfilterungsregeln für die Weiterleitung von Verkehr an den ersten SF in einem SFP an, der durch einen SFP-Index identifiziert wird.
  • o Verkehrsentklassifizierer zeigt mit Traffic-Filterregeln an, wie der Verkehr vom letzten SF in einem SFP, der durch einen SFP-Index identifiziert wird, zusammengefasst wird.
• - Gültigkeitsparameter für den SFC-Dienst, der durch die SFC-Service-ID identifiziert wird, z. B.:
  • o Dauer
  • o Geplante Zeitspanne, z. B. jeden Tag 8-20 Uhr, usw.
  • o Anwendungs-ID(s)
  • o Zugehörige PDU-Sitzungsparameter, einschließlich PDU-Sitzungstyp, z. B. IP/Ethernet/Unstructure, DNN, oder ein Slice/Service-Typ (SST) (z. B. eMBB, URLLC, MIoT, V2X usw.) und optionaler Slice Differentiator (SD).

The UE can be updated with the UE configuration for the SFC parameters of the SFC service configuration and apply traffic classifiers and SFs based on the UE policy for SFC parameters of the SFC service configuration on the UE:

• - SFC indicator: indicates that the parameters of the UE policy are for the SFC service configuration;
• - SFC service ID: the service ID of this set of SFC parameters for the SFC service;
• - SFC configuration: one or more SFs with the corresponding SF parameters;
• - SFP configuration: the SFP index with the corresponding ordered SFs;
• - SFC routing guideline:
  • o Traffic Classifier shows the association between an SPF index and traffic filtering rules for forwarding traffic to the first SF in an SFP identified by an SFP index.
  • o Traffic declassifier uses traffic filter rules to show how the traffic from the last SF is summarized in an SFP, which is identified by an SFP index.
• - Validity parameters for the SFC service that is identified by the SFC service ID, e.g. B .:
  • o Duration
  • o Planned time period, e.g. B. every day 8 a.m. - 8 p.m., etc.
  • o Application ID (s)
  • Associated PDU session parameters, including PDU session type, e.g. B. IP / Ethernet / Unstructure, DNN, or a slice / service type (SST) (e.g. eMBB, URLLC, MIoT, V2X etc.) and optional slice differentiator (SD).

• - UE-Adresse
• - Applikations-ID
• - Medientyp
• - Verkehrsprioritäten

The traffic classifier can provide an SPF index mapping to the SFC classification policy that contains one or more of the following information based on different levels or granularities per packet, e.g. B:

• - UE address
• - Application ID
• - media type
• - transport priorities

If information is only available in the traffic payload, the DPI capability on the traffic classifier is required.

• - UE-Adresse
• - Applikations-ID
• - Medientyp
• - Verkehrsprioritäten
• - SPF-Index

The traffic declassifier maps each of the IPv6 prefixes to an SFC reclassification / declassification policy that contains one or more of the following information to combine traffic from one or more SFPs before forwarding them to an application's application server: z. B:

• - UE address
• - Application ID
• - media type
• - transport priorities
• - SPF index

If information may only be available in one traffic payload, the DPI capability on the traffic declassifier may be required.

The procedure for updating the UE configuration can e.g. B. initiated by the PCF. For example, the SFCF-C on the SFCF can be requested by the PCF service to initiate an update procedure for the UE configuration.

In one example, the SFC configuration can include a video optimizer and the SF parameters can include the video parameters for optimization at the SF of the video optimizer.

The SFC configuration can e.g. For example, it could contain a load balancer, and the SF parameters could contain the criteria for balancing the application loads.

Further details and aspects are mentioned in connection with the examples described above and / or below. This in 5 The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed concept or one or more of the above (e.g. 1 - 4th ) and / or below (e.g. 6th - 11 ) described examples.

shows examples of methods for configuring UE policy delivery. shows a UE configuration update procedure for a transparent UE policy transmission (prior art; [3], section 4.17.6). The UPF can enable the support of SFC functionalities. The flow of the UE configuration policy is in which refers to [3] section 4.2.4.3 for the transparent UE policy transmission. This procedure is initiated when the PCF wants to update the UE access selection and the PDU session selection-related policy information (ie the UE policy) in the UE configuration. In the non-roaming case, the V-PCF is not involved and the role of the H-PCF is taken over by the PCF. In the roaming scenarios, the V-PCF interacts with the AMF and the H-PCF with the V-PCF.

• - Schritt 1 610: Das SMF kann die SFC-Anzeige in eine Nnrf NFManagement NFStatusSubscribe-Nachricht an das NRF aufnehmen, um die Benachrichtigung über verfügbare UPF mit SFC-Funktionalitäten zu abonnieren.
• - Schritt 3: UPF kann aktiviert werden SFC-Funktionalitäten werden eingesetzt und von UPF an OAM mit Angabe von SFC bereitgestellt.
• - Schritt4: Das OAM kann die UPF-Instanz mit aktiviertem SFC konfigurieren.
• - Schritt5, 6: das UPF kann mit SFC aktiviert werden oder OAM registriert UPF-Instanz auf NRF einschließlich SFC-Anzeige.

shows an example of the procedure from with the support of SFCF-U at the UPF. The SMF can get an available UPF instance activated with SFC functionalities based on the procedure of SMF provision of available UPFs using OAM or the NRF in [3] section 4.17.6 with the following additions:

• Step 1 610: The SMF can include the SFC advertisement in an Nnrf NFManagement NFStatusSubscribe message to the NRF in order to subscribe to the notification of available UPFs with SFC functionalities.
• - Step 3: UPF can be activated SFC functionalities are used and made available by UPF to OAM with specification of SFC.
• - Step 4: The OAM can configure the UPF instance with the SFC activated.
• - Step5, 6: the UPF can be activated with SFC or OAM registers UPF instance on NRF including SFC display.

• - Step1: Das SMF kann die SFC-Anzeige in eine Nnrf_NFManagement_NFStatusSubscribe-Nachricht an das NRF aufnehmen, um die Benachrichtigung über verfügbare SFCF-U zu abonnieren;
• - Schritt3: SFCF-U wird eingesetzt und von SFCF-U für OAM bereitgestellt;
• - Schritt4: Das OAM kann die SFCF-U-Instanz konfigurieren;
• - Schritt5, 6: Das SFCF-U oder OAM kann die SFCF-U-Instanz beim NRF registrieren.

shows an example of the procedure from with the support of SFCF-U. The Service Function Chaining Function (SFCF-U) can be an independent NF, SMF, that receives available SFCF instances from NRF or OAM, based on the same method of SMF provision of available UPFs using the NRF in [ 3] Section 4.17.6, whereby the UPFs are replaced by SFCF-U. SFCF-U can be an independent NF. The high-level description of the message flow can be as in look shown.

• Step1: The SMF can include the SFC advertisement in a Nnrf_NFManagement_NFStatusSubscribe message to the NRF in order to subscribe to the notification of available SFCF-U;
• - Step 3: SFCF-U is used and provided by SFCF-U for OAM;
• - Step 4: The OAM can configure the SFCF-U instance;
• - Step5, 6: The SFCF-U or OAM can register the SFCF-U instance with the NRF.

• - UPF und SFCF-U ist keine Eins-zu-Eins-Zuordnung;
• - SMF kann SFCF-U mehr als einem UPF zuordnen.

When configuring UPF for a PDU session of a UE that requires SFC based on the SFC service policy, the SMF can provide the UPF with the configuration of the traffic flows and the information of an available SFCF instance using the following principles:

• - UPF and SFCF-U is not a one-to-one assignment;
• - SMF can assign SFCF-U to more than one UPF.

Figure 3 shows an example of an NF service registration procedure. SMF can obtain available SFCF-U instances from NRF or OAM, where SFCF-U can be collocated with SFCF-C and can be registered by SFCF-C with the NRF using the NRF service, as in shown. The SFCF can contain an SFCF-C in the CP and an SFCF-U in the UP.

• - UPF und SFCF-U in SFCF ist keine Eins-zu-eins-Zuordnung;
• - SMF kann SFCF-U mehr als einem UPF zuweisen, indem es die Verkehrsrouting-Policen in Richtung eines oder mehrerer SFCF-Us in SFCFs konfiguriert.

When configuring UPF for a PDU session of a UE, the SMF can provide UPF the configuration of the traffic flows and the information of an available SFCF-U instance with the following principles:

• - UPF and SFCF-U in SFCF is not a one-to-one assignment;
• - SMF can assign SFCF-U to more than one UPF by configuring the traffic routing policies in the direction of one or more SFCF-Us in SFCFs.

• Step1: SFCF als NF-Service-Consumer, z. B. kann eine NF-Instanz eine Nnrf_NFManagement_NFRegister Request-Nachricht an das NRF senden, um das NRF über sein NF-Profil zu informieren, wenn der NF-Service-Consumer zum ersten Mal operativ wird. [3], Abschnitt 5.2.7.2.2 enthält relevante NF-Profil-Parameter, in denen das NF-Profil des NF-Service-Consumers vom OAM-System konfiguriert wird.
• Step2: Das NRF kann das NF-Profil des NF-Service-Verbrauchers speichern und markiert den NF-Service-Verbraucher als verfügbar.
• Step3: Das NRF kann die Annahme der NF-Registrierung durch eine Antwort Nnrf_NFManagement NFRegister bestätigen

The steps according to can be for example:

• Step1: SFCF as NF service consumer, e.g. B. an NF instance can send a Nnrf_NFManagement_NFRegister request message to the NRF in order to inform the NRF about its NF profile when the NF service consumer becomes operational for the first time. [3], Section 5.2.7.2.2 contains relevant NF profile parameters in which the NF profile of the NF service consumer is configured by the OAM system.
• Step2: The NRF can save the NF profile of the NF service consumer and marks the NF service consumer as available.
• Step3: The NRF can confirm the acceptance of the NF registration with a response Nnrf_NFManagement NFRegister

shows an example of the procedure from with the support of SFCF-U. The SFCF in can include a control level SFCF-C and a user level SFCF-U. The service SFCF-C can be a control level NF and the SFCF-U can be a user level NF.

The SFCF-C can obtain available SFCF-U instances from the NRF or OAM, based on the same method of SMF provisioning of available UPFs using the NRF in [3] section 4.17.6, the SMF being defined by SFCF-C and the UPFs are replaced by SFCF-U.

• - Schritt1: Das SFCF-C kann eine Nnrf_NFManagement_NFStatusSubscribe-Nachricht an das NRF senden, um die Benachrichtigung über verfügbare SFCF-U zu abonnieren.
• - Schritt3: Wenn SFCF-U eingesetzt wird, kann die SFCF-C-Sofortinformation von SFCF-U an OAM übermittelt werden.
• - Schritt4: Das OAM kann die SFCF-U-Instanz konfigurieren.
• - Schritt5, 6: Das SFCF-U oder OAM kann die SFCF-U-Instanz beim NRF registrieren.
• - Schritt7: Die NRF kann die verfügbaren SFCF-U-Informationen an die SFCF-C weitergeben.

The high-level description of the message flow can be as in look shown.

• Step 1: The SFCF-C can send an Nnrf_NFManagement_NFStatusSubscribe message to the NRF to subscribe to the notification of available SFCF-U.
• - Step 3: If SFCF-U is used, the SFCF-C immediate information can be transmitted from SFCF-U to OAM.
• - Step 4: The OAM can configure the SFCF-U instance.
• - Step5, 6: The SFCF-U or OAM can register the SFCF-U instance with the NRF.
• - Step 7: The NRF can forward the available SFCF-U information to the SFCF-C.

• - SMF fordert eine oder mehrere SFCF-U-Informationen von SFCF-C an;
• - UPF und SFCF-U ist keine Eins-zu-Eins-Zuordnung;
• - SMF kann Richtlinien für das Verkehrsrouting bei UPF konfigurieren, um den Verkehr an einen oder mehrere SFCF-U für die SFC-Behandlung weiterzuleiten.

When configuring UPF for a PDU session of a UE, the SMF can provide UPF the configuration of the traffic flows and the information of an available SFCF-U instance with the following principles:

• - SMF requests one or more SFCF-U pieces of information from SFCF-C;
• - UPF and SFCF-U is not a one-to-one assignment;
• - SMF can configure policies for traffic routing at UPF to route traffic to one or more SFCF-U for SFC handling.

shows a UE configuration update procedure for a transparent UE policy transmission (state of the art; [5], .1.2-4). The UPF can act as a Service Communication Proxy (SCP) between the SMF and SFCF-U. It enables SCP functionalities at the user level.

For example, the SMF (NF A) can request a service from the SFCF-U (NF B) via the UPF (act as SCP), as in FIG ([5]) shown. An inquiry-response can use an indirect communication method. For example, the SMF (NF-A) can request a service from SFCF-U (NF-B) via SFCF-C (as SCP).

shows an example of a method for subscribe-notify with indirect communication (state of the art; [5], Fig. 7.1.2-5). For example, the SMF (NF_A) can subscribe to the notification service from the SFCF (NF_B) via UPF (act as SCP), as in shown in a subscription notification method in which the notification destination is a NF-C, e.g. B. NEF, can be.

For example, the SMF (NF_A) can subscribe to the notification service of SFCF-U (NF_B) via SFCF-C (as SCP), as in shown in a subscription notification method in which the notification destination is a NF-C, e.g. B. NEF, can be.

Further details and aspects are mentioned in connection with the examples described above and / or below. This in 6th The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed Concept or one or more above (e.g. 1 - 5 ) and / or below (e.g. 7th - 11 ) described examples.

• - Schritt0: Die PCF (NF) kann die UDM-Benachrichtigung über Informationsaktualisierungen des SFC-Dienstes abonnieren, indem sie Teilnehmerdaten angibt, die sich auf den SFC-Dienst beziehen, z. B. eine Anwendung, die mit einem von einer AF angeforderten SFC-Dienst verbunden ist.
• - Step1: AF stellt dem NEF die SFC-Parameter der zu aktualisierenden SFC-Dienstkonfigurationen am UDR im Nnef_ParameterProvision_Update Request zur Verfügung (wobei die SFC-Parameter wie oben beschrieben sein können, z. B. ).
• - Schritt 2: Wenn die AF von der NEF autorisiert ist, die Parameter bereitzustellen, fordert die NEF die Aktualisierung und Speicherung der bereitgestellten Parameter als Teil der Teilnehmerdaten über die Nachricht Nudm ParameterProvision_Update Request an. Die bereitgestellten SFC-Parameter können wie oben beschrieben sein, z. B. .
• - Schritt3: Der UDM gibt den SFC-Dienst an, z. B. die SFC-Dienst-ID, in der Nudr_DM_Query/Nudar_DM_Request-Nachricht.
• - Schritt4: Der UDR speichert die bereitgestellten Daten als Teil der Abonnementdaten und antwortet mit der Antwortnachricht Nudr_DM Update.
• - Schritt7: Das UDM benachrichtigt die abonnierte Netzwerkfunktion (z. B. PCF/SFCF/SFCF-C) über die aktualisierten Teilnehmerdaten per Nudm_SDM_Notification Notify-Nachricht, wobei die Teilnehmerdaten die SFC-Parameter wie oben beschrieben enthalten können, z. B. .

shows examples of the information flow of the NEF service operations. shows an Nnef_ParameterProvision_update request / response operation (prior art; [3], .15.6.2-1). As in referring to [3], section 4.15.6.2: Information flow of the NEF service operation with the following additions:

• - Step0: The PCF (NF) can subscribe to the UDM notification about information updates of the SFC service by providing subscriber data relating to the SFC service, e.g. B. an application that is connected to an SFC service requested by an AF.
• - Step1: AF provides the NEF with the SFC parameters of the SFC service configurations to be updated on the UDR in the Nnef_ParameterProvision_Update request (whereby the SFC parameters can be as described above, e.g. ).
• Step 2: If the AF is authorized by the NEF to provide the parameters, the NEF requests the updating and storage of the parameters provided as part of the subscriber data via the Nudm ParameterProvision_Update Request message. The SFC parameters provided can be as described above, e.g. B. .
• - Step 3: The UDM specifies the SFC service, e.g. B. the SFC service ID, in the Nudr_DM_Query / Nudar_DM_Request message.
• Step 4: The UDR saves the data provided as part of the subscription data and replies with the response message Nudr_DM Update.
• - Step 7: The UDM notifies the subscribed network function (e.g. PCF / SFCF / SFCF-C) of the updated subscriber data via Nudm_SDM_Notification Notify message. The subscriber data can contain the SFC parameters as described above, e.g. B. .

In one example, the processing circuitry may be further configured to receive a request from the AF to dynamically inference the SFP routing for the application of the AS. The AF can request the SFC service and the provision of the SFC parameters via the NEF in order to save the SFC service configuration on the UDR, the SMF can request the SFC parameters of the SFC service configuration directly from the UDR or via PCF / SFCF-U / SFCF-C (as described above for handling the PDU sessions of the UEs, e.g. in - .

The AF requests may concern UE (s) with an established PDU session or future PDU sessions, with the AF contacting the NEF and the NEF storing the AF request information in the UDR so that PCF (s) / SFCF (s) / SFCF-C (s) received a corresponding notification if they had subscribed to the creation / modification / deletion of the AF request information according to the UDR data keys / data sub-keys.

• - AF-Anfragen, die ein einzelnes UE anhand einer UE-Adresse für eine laufende PDU-Sitzung ansprechen.
• - AF-Anforderungen, die auf ein einzelnes UE durch eine GPSI, eine Gruppe von UE(s) oder ein beliebiges UE abzielen, das auf eine Kombination von DNN und S-NSSAI zugreift.

Information Name Anwendbar für PCF oder NEF (HINWEIS 1) Nur für NEF anwendbar Kategorie Verkehr Beschreibung Definiert den zu beeinflussenden Zielverkehr, dargestellt durch die Kombination aus DNN und optional S-NSSAI sowie Anwendungskennung oder Verkehrsfilterungsinformationen. Der Zielverkehr kann durch AF-Service-Identifier dargestellt werden, anstelle der Kombination aus DNN und optional S-NSSAI. Obligatorisch Anforderungen an das Traffic Routing Routing-Profil-ID und/oder N6-Verkehrsrouting-Informationen, die jeder DNAI entsprechen, und/oder eine Angabe zur Behandlung von Verkehr mit unbekannter Zieladresse und eine optionale Angabe zur Verkehrskorrelation. k.A. Optional In addition, the AF can request dynamic traffic routing for SFPs with corresponding traffic descriptions, as shown in Tab. 1 ([5] Table 5.6.7-1): Information element contained in the AF request using the following two methods for Processing of AF requests to affect traffic routing for sessions with the following cases:

• AF queries that address an individual UE using a UE address for an ongoing PDU session.
• AF requests targeting a single UE through a GPSI, a group of UE (s) or any UE accessing a combination of DNN and S-NSSAI.

Information name Applicable for PCF or NEF (NOTE 1) Applicable to NEF only category Traffic description Defines the target traffic to be influenced, represented by the combination of DNN and optionally S-NSSAI as well as application identifier or traffic filtering information. The target traffic can be represented by AF service identifier instead of the combination of DNN and optionally S-NSSAI. Mandatory Traffic routing requirements Routing profile ID and / or N6 traffic routing information corresponding to each DNAI and / or an indication of the handling of traffic with an unknown destination address and an optional indication of the traffic correlation. n / a Optional

Tab. 1 Information element contained in the AF request (part table).

The SFC parameters of the SFC service configuration can be provided by the AF in the AF request. For example, the AF inferencing request can be sent to PCF via NEF (e.g. - ). For example, the AF inferencing request can be sent to SFCF (SFCF-UC) via NEF (e.g. ). For example, the AF inferencing request can be sent to SFCF-C via NEF (e.g. .

The UDR can save the provided "SFC parameters of the SFC service configuration configurations".

• SFC-Anzeige, SFC-Konfiguration, SFP-Konfiguration, Applikations-ID und der entsprechende SFP-Index, zugehörige PDU-Session-Parameter, einschließlich PDU-Session-Typ oder ein Slice/Service-Typ, SST, SD.

shows an example of the processing of AF requests to influence traffic routing for sessions that are not identified by a UE address. Processing can take place without a UE address. In one example, the request can be an Nnef_TrafficInfluence_Create / Update / Delete message that includes at least one element of the group:

• SFC display, SFC configuration, SFP configuration, application ID and the corresponding SFP index, associated PDU session parameters, including PDU session type or a slice / service type, SST, SD.

• Step1: Um eine neue Anfrage zu erstellen, ruft die AF eine Nnef_TrafficInfluence_Create-Dienstoperation auf. Der Inhalt dieser Service Operation (AF request) ist in [3], Abschnitt 5.2.6.7 definiert. Die AF-Anfrage enthält auch eine AF-Transaktions-ID. Die AF-Anforderung kann SFC-Parameter der SFC-Dienstkonfiguration enthalten.

The following steps can be included:

• Step1: To create a new request, the AF calls a Nnef_TrafficInfluence_Create service operation. The content of this service operation (AF request) is defined in [3], Section 5.2.6.7. The AF request also includes an AF transaction ID. The AF request can contain SFC parameters of the SFC service configuration.

If it subscribes to events in connection with PDU sessions, the AF also indicates where it would like to receive the corresponding notifications (AF notification reporting information).
To update or remove an existing request, the AF calls a service operation Nnef_TrafficInfluence_Update or Nnef_TrafficInfluence_Delete and specifies the corresponding AF transaction ID.
Step2: The AF sends its request to the NEF. If the request is sent directly from the AF to the PCF, the AF reaches the PCF that was selected for the existing PDU session by configuration or by calling the Nbsf management discovery service. The message Nnef_TrafficInfluence_Create / Update / Delete can contain the SFC parameters of the SFC service configuration, e.g. B. the SFC service ID to be created / updated / deleted as specified above, e.g. B. .
The NEF ensures the necessary authorization control, including the throttling of AF requests and, as described in Section 4.3.6.1, the mapping of the information provided by the AF into the information required by the 5GC.
Step3: (in the case of Nnef_TrafficInfluence_Create or Update): The NEF can save the AF request information in the UDR (data record = application data;
Subset of data = AF traffic influence request information, data key = AF transaction internal ID, S-NSSAI and DNN and / or internal group identifier or
SUPI).
The NEF can match the AF request information in the UDR with information from the SFC service configuration, e.g. B. SFPs, save.
NOTE 3: Both the AF Transaction Internal ID and S-NSSAI and DNN and / or Internal Group Identifier or SUPI are considered to be data keys if the AF request information is stored in the UDR, see [3], Table 5.2.12.2.1 -1.
In the case of Nnef_TrafficInfluence_delete: The NEF deletes the AF requests in the UDR (Data Set = Application Data; Data Subset = AF traffic influence request information, Data Key = AF Transaction Internal ID).
The NEF responds to the AF.
Step4: The PCF (s) / SFCF (s) / SFCF-C (s) who have subscribed to changes to AF requests (Data Set = Application Data; Data Subset = AF traffic influence request information, Data Key = S-NSSAI and DNN and / or Internal Group Identifier or SUPI) can receive a Nudr_DM_Notify notification of a data change from the UDR. The PCF, SFCF (SFCF-UC) and / or the SFCF-C can save the information of the SFC service configuration and check the subscription to the notification. If the subscription is valid, the UDR can send the notification to PCF (s) / SFCF (s) (SFCF-UC (s)) / SFCF-C (s) directly or to SFCF (s) (SFCF-UC (s )) / SFCF-C (s) via PCF (s). Step5: The PCF determines whether existing PDU sessions are potentially affected by the AF request. For each of these PDU sessions, the PCF can update the SMF with the corresponding new PCC rule (s) by calling the service operation Npcf_SMPolicyControl UpdateNotify, as described in steps 5 and 6 in section 4.16.5.
If the AF request contains a request for notification notification for a UP path change, the PCF inserts into the PCC rule (s) the information necessary for notification of the event, including the notification destination address that points to the NEF or AF and the notification correlation ID containing the internal ID of the AF transaction.

• • Zum Beispiel kann das PCF das SMF über die Richtlinienaktualisierungen der SFC-Parameter der SFC-Dienstkonfiguration informieren.
• • Zum Beispiel kann der SFCF-C in SFCF (SFCF-UC) SMF direkt oder über PCF für die Richtlinienaktualisierungen für die SFC-Parameter der SFC-Dienstkonfiguration benachrichtigen.
• • Zum Beispiel kann der SFCF-C das SMF für die Policy-Updates der SFC-Parameter der SFC-Dienstkonfiguration benachrichtigen.

The PCF / SFCF / SFCF-C sends Npcf_SMPolicyControl_UpdateNotify / Nsfcf_SMPolicyControl_UpdateNotify / Nsfcf-c_SMPolicyControl_UpdateNotify to SMF.

• • For example, the PCF can notify the SMF of the policy updates to the SFC parameters of the SFC service configuration.
• • For example, the SFCF-C in SFCF (SFCF-UC) can notify SMF directly or via PCF for the policy updates for the SFC parameters of the SFC service configuration.
• • For example, the SFCF-C can notify the SMF for the policy updates of the SFC parameters of the SFC service configuration.

• • Hinzufügen, Ersetzen oder Entfernen eines UPF im Datenpfad, um z. B. als UL CL oder Verzweigungspunkt zu fungieren, wie in Abschnitt 4.3.5. beschrieben;
• • Weisen Sie dem UE ein neues Präfix zu (wenn IPv6 Multi-Homing gilt);
• • Aktualisieren der UPF in der Ziel-DNAI mit neuen Verkehrslenkungsregeln;
• • Abonnieren Sie Benachrichtigungen der AMF für ein Interessengebiet über den Dienstvorgang Namf_EventExposure_Subscribe.

Step6: When a PCC rule is received from the PCF, the SMF can take appropriate measures to reconfigure the user level of the PDU session, e.g. B:

• • Adding, replacing or removing a UPF in the data path, e.g. B. to act as a UL CL or Junction Point as in Section 4.3.5. described;
• • Assign a new prefix to the UE (if IPv6 multi-homing applies);
• • Update the UPF in the target DNAI with new routing rules;
• • Subscribe to AMF notifications for an area of interest using the Namf_EventExposure_Subscribe service process.

In addition, SMF performs a reconfiguration for user plane traffic routing and SFC routing.

shows an example of the handling of an AF request targeting a single UE address to the corresponding PCF. The processing can be done with a UE address as a destination. In one example, the processing circuitry may be further configured to receive a request from the NF to set up a connection between the NF and the NEF in order for the NF to provide the SFC policy to the UE. Processing can be done as in be shown with the following additions. For example, the AF inferencing request can be sent to PCF via NEF (e.g. - ). For example, the AF inferencing request can be sent to SFCF (SFCF-UC) via NEF (e.g. ). For example, the AF inferencing request can be sent to SFCF-C via NEF (e.g. .

• • Hinzufügen, Ersetzen oder Entfernen von UPF(s) im Datenpfad, z. B. um als UL CL, Verzweigungspunkt und/oder PDU-Sitzungsanker zu fungieren, z. B. wie in Abschnitt 4.3.5 beschrieben.
• • Weisen Sie dem UE ein neues Präfix zu (wenn IPv6 Multi-Homing gilt).
• • Aktualisieren der UPF bezüglich der Ziel-DNAI mit neuen Verkehrslenkungsregeln.
• • Abonnieren Sie Benachrichtigungen der AMF für ein Interessengebiet über den Dienstvorgang Namf_EventExposure_Subscribe.
• • Hinzufügen, Ersetzen oder Entfernen der SFC-Behandlung im Datenpfad:
  • - Zum Beispiel das Verkehrsrouting in UPF(s) mit SFCF-U-Fähigkeiten (z. B. .
  • - Zum Beispiel das Verkehrsrouting zu SFCF-U(s), die N6 terminieren (z. B. .
  • - Zum Beispiel das Verkehrsrouting von UPF(s) zu SFCF-U(s) in SFCF(s) (z. B. ).
  • - Zum Beispiel das Verkehrsrouting zu SFCF-U(s), die N6 terminieren (z. B. .

Depending on the use of the AF (see [5], Section 6.2.10), the AF can send the AF request directly to the PCF, in this case step 1 can be skipped, or via the NEF.
Step1: [Condition] If the NF is allowed to send the NF request via the NEF, the NF sends the Nnef TrafficInfluenceCreate / Update / Delete request with the goal of a single UE address to the NEF. This request corresponds to an AF request for influencing traffic routing, which is aimed at a single UE address.
When the NEF receives an AF request from the AF, it ensures the necessary authorization control and, as described in Section 4.3.6.1, the mapping of the information provided by the AF into the information required by the 5GC. The NEF responds to the AF.
The message Nnef_TrafficInfluence_Create / Update / Delete contains the SFC parameters of the SFC service configuration as specified above (e.g. ).
Step2: [Condition] AF / NEF can use the service operation Nbsf Management Discovery (which provides at least the UE address) to find out the address of the relevant PCF if the PCF address is not available on the NEF due to the local configuration, otherwise step 1 is skipped.
NOTE: The AF / NEF finds the BSF using the local configuration or using the NRF
Step3: BSF delivers the PCF address in the response Nbsf Management Discovery to AF / NEF.
Step4: If step 1 has been carried out, the NEF calls the Npcf_PolicyAuthorization service at the PCF in order to transmit the AF request. When an AF sends the AF request directly to the PCF, the AF calls the Npcf PolicyAuthorization service and the PCF replies to the AF.
The PCF (e.g. ) / SFCF (e.g. ) / SFCF-C (e.g. saves the information of the SFP configuration for the application of the UE. Step5: The PCF / SFCF / SFCF-C updates the SMF with the corresponding new PCC rule (s) with the SM Policy Association Modification procedure initiated by the PCF as described in [3], Section 4.16.5.2.
When a PCC rule is received from the PCF, the SMF may take appropriate action to reconfigure the user level of the PDU session, such as: B .:

• • Adding, replacing, or removing UPF (s) in the data path; To act as a UL CL, Junction Point and / or PDU session anchor, e.g. B. as described in Section 4.3.5.
• • Assign a new prefix to the UE (if IPv6 multi-homing applies).
• • Update the UPF regarding the target DNAI with new routing rules.
• • Subscribe to AMF notifications for an area of interest using the Namf_EventExposure_Subscribe service process.
• • Adding, replacing or removing the SFC handling in the data path:
  • - For example, traffic routing in UPF (s) with SFCF-U capabilities (e.g. .
  • - For example, traffic routing to SFCF-U (s) that terminate N6 (e.g. .
  • - For example the traffic routing from UPF (s) to SFCF-U (s) in SFCF (s) (e.g. ).
  • - For example, traffic routing to SFCF-U (s) that terminate N6 (e.g. .

shows an example of setting up an NF session with the procedure for the required SFC parameters. In one example, the component can be further configured to establish an NF session with the required SFC parameters of the SFC service configuration procedure. The AF session can be for an existing PDU session or a future session of a UE identified by UE address / GPSI, a group of UE identified by a list of UE addresses / external group identifier, or any UE for the application, which is also specified in the SFC parameters for SFC services sponsored by the application service provider.

For example, the AF session for the SFC policy on the PCF can be established via the NEF (e.g. ). For example, the AF session for the SFC policy for SFCF-C can be established in SFCF via NEF (e.g. ). For example, the AF session for the SFC policy with SFCF-C can be established via NEF (e.g. .

Step1: When establishing the connection between NF and 5GS with the required SFC parameters of the SFC service configuration for a UE, a group of UEs or any UE, the NF can send an Nnef AFsessionWithSFC Create request message (UE-ID (s), NF ID, description of the application processes, SFC parameters) to the NEF. The Nnef_AFsessionWithSFC_Create request message can contain the SFC parameters of the SFC service configuration, e.g. E.g. contain the SFC service ID that is to be created / updated / deleted (as described above, e.g. ).

• • Für ein einzelnes UE kann die UE-ID GPSI oder UE IP/Ethernet-Adresse sein
• • Für eine Gruppe von UEs kann die UE-ID(s) ein externer Gruppenbezeichner oder eine Liste von UE-IP/Ethernet-Adressen sein
• • Wenn die UE-ID nicht angegeben wird, gilt die AF-Anforderung für jedes UE mit den Anwendungen, die auch in den SFC-Parametern für SFC-Dienste angegeben sind.

The UE ID can be:

• • For a single UE, the UE ID can be GPSI or UE IP / Ethernet address
• • For a group of UEs, the UE ID (s) can be an external group identifier or a list of UE IP / Ethernet addresses
• • If the UE ID is not specified, the AF request applies to each UE with the applications that are also specified in the SFC parameters for SFC services.

• • IP/Ethernet-Filterinformationen,
• • gesponserte SFC-Service-Informationen, z. B. Application Service Provider ID, Edge Application Service Provider ID oder Edge Computing Service Provider ID, etc.
• • Referenz-ID (falls von der AF erhalten) und
• • Sponsoring Status (falls von der AF erhalten), z. B. aktiv oder inaktiv.

Optionally, a time period or a traffic volume for the requested SFC parameters can be included in the AF request.
The NEF can assign a Transaction Reference ID to the Nnef_AFsessionWithSFC_Create request.
Step2: The NEF can authorize the AF request and can apply guidelines to control the predefined SFs that are authorized for the AF. If the authorization is not granted, steps 3 and 4 can be skipped and the NEF will respond to the AF with a score indicating that the authorization failed. Step3: The NEF can interact with the PCF / SFCF (SFCF-UC) / SFCF-C by triggering a request Npcf_PolicyAuthorization_Create or Nsfcf_PolicyAuthorization_Create or Nsfcf-c PolicyAuthorization Create and providing the following information:

• • IP / Ethernet filter information,
• • Sponsored SFC service information, e.g. B. Application Service Provider ID, Edge Application Service Provider ID or Edge Computing Service Provider ID, etc.
• • Reference ID (if received from AF) and
• • Sponsoring status (if received from AF), e.g. B. active or inactive.

The PCF / SFCF (SFCF-UC) / SFCF-C can derive the SFC guidelines based on the information provided by the NEF and determine whether these SFC guidelines are allowed (according to the SFCF / PCF configuration for this AF), and can report the result to the NEF.
The PCF / SFCF (SFCF-UC) / SFCF-C can inform the NEF whether or not the transmission resources corresponding to the SFC request have been set up.
Step4: The PCF / SFCF (SFCF-UC) / SFCF-C can determine whether the request is permitted and can notify the NEF if the request is not permitted. If the request is not authorized, the NEF can respond in step 5 with a score indicating that the authorization failed.
Step5: The NEF can send a response message Nnef AFsessionWithSFC Create (Transaction Reference ID, Result) to the AF. A result indicates whether the request is granted or not.

Further details and aspects are mentioned in connection with the examples described above and / or below. This in 7th The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed concept or one or more of the above (e.g. 1 - 6th ) and / or below (e.g. 9 - 11 ) described examples.

• • nur bei den UE(s)
• • bei den UE(s) und NFs, z. B. SFCF-U in 5GC
• • an den UE(s), NFs in 5GC und SFC in Edge-Anwendung Datennetz.

shows an example of a method for providing service-specific information. The procedure for providing service-specific parameters of the SFC via NEF and 5G network functions for a UE / a group of UEs / any UE if the SFC can be activated in the following cases:

• • only for the UE (s)
• • in the UE (s) and NFs, z. B. SFCF-U in 5GC
• • at the UE (s), NFs in 5GC and SFC in Edge application data network.

The service-specific parameters of SFC can be an SFC parameter of the SFC service configuration, as described above, e.g. B. .

The AF can make requests on behalf of applications that do not belong to the PLMN serving the UE, as in FIG which shows the procedure for the provision of service-specific parameters for the SFC service at the UE, in which the AF uses the service Nnef ServiceParameter to make the service-specific parameters available to the PLMN and the UE.

• - Dienstbeschreibung: die Informationen zur Identifizierung eines Dienstes, auf den die Dienstparameter angewendet werden. Die Service Description in der AF-Anfrage kann durch die Kombination von DNN und S-NSSAI, einen AF-Service-Identifier oder einen Application Identifier dargestellt werden.
• - Dienstparameter: die dienstspezifischen Informationen, die im Netz bereitgestellt und an das UE geliefert werden müssen, um den durch die Dienstbeschreibung identifizierten Dienst zu unterstützen. Die Service-Parameter enthalten die Informationen zu den oben angegebenen SFC-Parametern der SFC-Servicekonfiguration, z. B. .
• - Ziel-UE(s) oder eine Gruppe von UEs (optional): Ziel-UE(s) oder eine Gruppe von UEs geben das/die UE(s) an, dem/denen die Dienstparameter zugestellt werden sollen.

• • Einzelne UEs können durch GPSI, oder eine IP-Adresse/Präfix oder eine MAC-Adresse identifiziert werden.
• • Gruppen von UEs können durch einen External Group Identifier identifiziert werden.
• • Wenn die Kennungen der Ziel-UEs oder einer Gruppe von UEs nicht angegeben werden, dann werden die Dienstparameter an alle UEs geliefert, die den durch die Dienstbeschreibung identifizierten Dienst nutzen.

The NF request sent to the NEF may contain the information listed below:

• - Service Description: the information identifying a service to which the service parameters are applied. The service description in the AF request can be represented by a combination of DNN and S-NSSAI, an AF service identifier or an application identifier.
• Service parameters: the service-specific information that must be made available in the network and delivered to the UE in order to support the service identified by the service description. The service parameters contain the information on the SFC parameters of the SFC service configuration specified above, e.g. B. .
• Target UE (s) or a group of UEs (optional): Target UE (s) or a group of UEs specify the UE (s) to which the service parameters are to be delivered.

• • Individual UEs can be identified by GPSI, or an IP address / prefix or a MAC address.
• • Groups of UEs can be identified by an external group identifier.
• If the identifiers of the target UEs or of a group of UEs are not specified, then the service parameters are supplied to all UEs that use the service identified by the service description.

• Step1: Um eine neue Anfrage zu erstellen, ruft die AF eine Nnef ServiceParameter Create Service Operation auf und um eine bestehende Anfrage zu aktualisieren oder zu löschen, ruft die AF eine Nnef_ServiceParameter_Update oder Nnef_ServiceParameter_Delete Service Operation zusammen mit der entsprechenden Transaktionsreferenz-ID auf, die der AF in der Antwortnachricht Nnef_ServiceParameter_Create mitgeteilt wurde.
• Der Inhalt dieser Service-Operation (AF-Anfrage) umfasst die in [3], Abschnitt 5.2.6.11 beschriebenen Informationen und die SFC-Parameter der SFC-Servicekonfiguration, z. B. die SFC-Service-ID, die wie oben angegeben erstellt/aktualisiert/gelöscht werden sollen, z. B. .
• Step2: Die AF sendet ihre Anfrage an die NEF. Das NEF autorisiert die vom NF erhaltene NF-Anfrage und speichert die Informationen im UDR als „Anwendungsdaten“.

This in Procedures shown may include:

• Step1: To create a new request, the AF calls an Nnef ServiceParameter Create Service Operation and to update or delete an existing request, the AF calls an Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete Service Operation together with the corresponding transaction reference ID that the AF was notified in the response message Nnef_ServiceParameter_Create.
• The content of this service operation (AF request) includes the information described in [3], section 5.2.6.11 and the SFC parameters of the SFC service configuration, e.g. B. the SFC service ID to be created / updated / deleted as specified above, e.g. B. .
• Step2: The AF sends its request to the NEF. The NEF authorizes the NF request received from the NF and saves the information in the UDR as "application data".

• • Abbildung des AF-Service-Identifiers in DNN- und S-NSSAI-Kombination, bestimmt durch lokale Konfiguration.
• • Abbildung der GPSI in Target UE Identifier in SUPI, entsprechend der vom UDM erhaltenen Informationen.
• • Die externe Gruppenkennung in der Ziel-UE-Kennung auf die interne Gruppenkennung abbilden, entsprechend der vom UDM erhaltenen Informationen.

The AF request contains the SFC parameters of the SFC service configuration, e.g. B. the SFC service ID to be created / updated / deleted as specified above, e.g. B. . In the case of Nnef ServiceParameter Create, the NEF issues a transaction reference ID to the Nnef_ServiceParameter_Create request. The NEF performs the following mappings:

• • Mapping of the AF service identifier in DNN and S-NSSAI combination, determined by the local configuration.
• • Mapping of the GPSI in the Target UE Identifier in SUPI, according to the information received from the UDM.
• • Map the external group identifier in the target UE identifier to the internal group identifier, according to the information received from the UDM.

• • Informationen zur Bereitstellung der AF-Dienstparameter,
• • SUPI,
• • Datensatzeinstellung auf „Anwendungsdaten“,
• • Data Subset-Einstellung auf „Service specific information“.

Step3: In the case of Nnef_ServiceParameter_Create or Update, the NEF saves the AF request information in the UDR as "Application Data" (data subset setting to "Service specific information") together with the assigned Transaction Reference ID.
The AF request contains the SFC parameters of the SFC service configuration, e.g. B. the SFC service ID to be created / updated / deleted as specified above, e.g. B. . With Nnef_ServiceParameter_delete, the NEF deletes the AF request information from the UDR.
Step4: The NEF responds to the AF.
In the case of the response message Nnef_ServiceParameter_Create, the response message contains the assigned transaction reference ID.
The following steps are carried out when the UE is registered in the network and the PCF subscribes to the notification of the data changed in the UDR by calling Nudr_DM_Subscribe and providing the following information in step 0:

• • Information on the provision of the AF service parameters,
• • SUPI,
• • Data set setting to "application data",
• • Data subset setting to "Service specific information".

Step5: The PCF receives a Nudr_DM_Notify notification from the UDR about a data change specified in the AF request. The PCF does not have to subscribe to the application-specific information for each UE, for example if the PCF has already received the application-specific information for a group of UEs or for a DNN through a subscription to other UEs. The same application specific information is provided to each UE in a group or DNN.
The data change specified in the AF request contains the SFC parameters of the SFC service configuration, e.g. B. the SFC service ID to be created / updated / deleted as specified above, e.g. B. .
Step 6: The PCF initiates the delivery of the UE policy as in . If the UE can be reached, the service parameters are sent directly by the PCF (e.g. ) or by the PCF at the request of the SFCF (e.g. ) / SFCF-C (e.g. delivered to the targeted UE.

• - SFC-Anzeige: zeigt an, dass die Parameter der UE-Policy für die SFC-Dienstkonfiguration sind;
• - SFC-Service-ID: die Service-ID dieses Satzes von SFC-Parametern für den SFC-Service;
• - SFC-Konfiguration: ein oder mehrere SFs mit den entsprechenden SF-Parametern;
• - SFP-Konfiguration: den SFP-Index mit den entsprechenden geordneten SFs;
• - SFC-Routing-Richtlinie:
  • ◯ Verkehrsklassifizierer zeigt die Zuordnung zwischen einem SPF-Index und Verkehrsfilterungsregeln für die Weiterleitung von Verkehr an den ersten SF in einem SFP an, der durch einen SFP-Index identifiziert wird.
  • ◯ Verkehrsentklassifizierer zeigt mit Traffic-Filterregeln an, wie der Verkehr vom letzten SF in einem SFP, der durch einen SFP-Index identifiziert wird, zusammengefasst wird.
• - Gültigkeitsparameter für den SFC-Dienst, der durch die SFC-Service-ID identifiziert wird, z. B.:
  • ◯ Dauer
  • ◯ Geplante Zeitspanne, z. B. jeden Tag 8-20 Uhr, usw.
  • ◯ Anwendungs-ID(s)
  • ◯ Zugehörige PDU-Sitzungsparameter, einschließlich PDU-Sitzungstyp, z. B. IP/Ethernet/Unstructure, DNN oder ein Slice/Service-Typ (SST) (z. B. eMBB, URLLC, MIoT, V2X usw.) und optionaler Slice Differentiator (SD).

In step 6, for example, the UE can be updated with the UE configuration for the SFC parameters of the SFC service configuration and use traffic classifiers and SFs based on the UE policy for the SFC parameters of the SFC service configuration on the UE (cf. B. ):

• - SFC indicator: indicates that the parameters of the UE policy are for the SFC service configuration;
• - SFC service ID: the service ID of this set of SFC parameters for the SFC service;
• - SFC configuration: one or more SFs with the corresponding SF parameters;
• - SFP configuration: the SFP index with the corresponding ordered SFs;
• - SFC routing guideline:
  • ◯ Traffic Classifier shows the association between an SPF index and traffic filtering rules for routing traffic to the first SF in an SFP identified by an SFP index.
  • ◯ Traffic declassifier uses traffic filter rules to show how the traffic from the last SF is summarized in an SFP, which is identified by an SFP index.
• - Validity parameters for the SFC service that is identified by the SFC service ID, e.g. B .:
  • ◯ duration
  • ◯ Planned time period, e.g. B. every day 8 a.m. - 8 p.m., etc.
  • ◯ Application ID (s)
  • Associated PDU session parameters, including PDU session type, e.g. B. IP / Ethernet / Unstructure, DNN or a slice / service type (SST) (e.g. eMBB, URLLC, MIoT, V2X etc.) and optional slice differentiator (SD).

• - UE-Adresse
• - Applikations-ID
• - Medientyp
• - Verkehrsprioritäten

The traffic classifier can provide an SPF index mapping to the SFC classification policy that contains one or more of the following information based on different levels or granularities per packet, e.g. B:

• - UE address
• - Application ID
• - media type
• - transport priorities

If information is only available in the traffic payload, the DPI capability on the traffic classifier is required.

• - UE-Adresse
• - Applikations-ID
• - Medientyp
• - Verkehrsprioritäten
• - SPF-Index

The traffic declassifier maps each of the IPv6 prefixes to an SFC reclassification / declassification policy that contains one or more of the following information to address the Combine traffic from one or more SFPs before forwarding them to an application's application server; B:

• - UE address
• - Application ID
• - media type
• - transport priorities
• - SPF index

If information may only be available in one traffic payload, the DPI capability on the traffic declassifier may be required.

Further details and aspects are mentioned in connection with the examples described above and / or below. This in 8th The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed concept or one or more of the above (e.g. 1 - 7th ) and / or below (e.g. 9 - 11 ) described examples.

Figure 3 shows a flow chart of an example of a method 900 . The procedure 900 includes generating 910 of an SCF in the cellular network. The method also includes 900 providing 920 access to the third party, e.g. B. a third party application to provide a service function chain, SF chain, policy for the use of the SF chain employed in the mobile communications network.

Further details and aspects are mentioned in connection with the examples described above and / or below. This in 9 The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed concept or one or more of the above (e.g. 1 - 8th ) and / or below (e.g. 10 - 11 ) described examples.

shows a network 1000 in accordance with various embodiments. The network 1000 can be operated in a manner that complies with the technical specifications of 3GPP for LTE or SG / NR systems. The network 1000 can consist of one component, as described above (e.g. 1 ). However, the exemplary embodiments are not limited in this regard and the described embodiments can also apply to other networks that benefit from the principles described here, e.g. B. future 3GPP systems or the like.

The network 1000 can a UE 1002 which may include any mobile or non-mobile computing device capable of communicating with a RAN 1004 is designed via an over-the-air connection. The UE 1002 a smartphone, a tablet computer, a portable computing device, a desktop computer, a laptop computer, an infotainment device in the vehicle, an entertainment device in the vehicle, an instrument cluster, a head-up display device, an onboard Diagnostic device, a mobile dash top device, a mobile data terminal, an electronic engine management system, an electronic / engine control device, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked device, a machine communication device, be but not limited to an M2M or D2D device, an IoT device, etc.

In some embodiments, the network 1000 comprise a plurality of UEs that are directly coupled to one another via a sidelink interface. The UEs can be M2M / D2D devices that communicate via physical sidelink channels, such as B. PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc., but are not limited to these.

In some embodiments, the UE 1002 additionally with an AP 1006 communicate over an over-the-air connection. The AP 1006 can manage a WLAN connection, which can be used to take part / all of the network traffic from the RAN 1004 to relieve. The connection between the UE 1002 and the AP 1006 can be done with any IEEE 802.11 protocol, with the AP 1006 could be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, the UE 1002 , the RAN 1004 and the AP 1006 use a cell WLAN aggregation (e.g. LWA / LWIP). With cell WLAN aggregation, the UE 1002 from the RAN 1004 can be configured to use both cellular radio resources and WLAN resources.

The RAN 1004 may contain one or more access nodes, e.g. B. AN 1008 . AT 1008 can use air interface protocols for the UE 1002 terminate by providing access layer protocols including RRC, PDCP, RLC, MAC and LI protocols. In this way, the AN 1008 a data / voice connection between CN 1020 and the UE 1002 enable. In some embodiments, this may be AN 1008 be implemented in a discrete device or as one or more software entities running on server computers as part of e.g. B. run a virtual network, which can be referred to as CRAN or virtual baseband unit pool. The AN 1008 can be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 1008 can be a macro cell base station or a base station with low power for the provision of femtocells, picocells or similar cells which, compared to macro cells, have a smaller coverage area, a lower user capacity or a higher bandwidth.

In embodiments where the RAN 1004 contains a large number of ANs, these can be accessed via an X2 interface (if the RAN 1004 is an LTE-RAN) or an Xn interface (if the RAN 1004 a 5G-RAN) must be coupled to one another. the X2 / Xn interfaces, which in some embodiments may be separated into control / user plane interfaces, allow ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

The ANs of the RAN 1004 can each manage one or more cells, cell groups, component carriers, etc. to the UE 1002 provide an air interface for network access. The UE 1002 may be connected to multiple cells at the same time from the same or different ANs of the RAN 1004 to be provided. For example, the UE 1002 and the RAN 1004 Use carrier aggregation to manage the UE 1002 to enable connection to a large number of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN can be a master node providing an MCG and a second AN can be a secondary node providing an SCG. The first / second ANs can be any combination of eNB, gNB, ng-eNB, etc.

The RAN 1004 can provide the air interface via a licensed spectrum or an unlicensed spectrum. For operation in the unlicensed spectrum, the nodes can use LAA, eLAA and / or feLAA mechanisms based on CA technology with PCells / Scells. Before accessing the unlicensed spectrum, the nodes can perform a media / carrier capture, e.g. B. based on a listen-before-talk (LBT) protocol.

In V2X scenarios, the UE 1002 or AN 1008 be or act as an RSU, which can refer to any traffic infrastructure unit used for V2X communication. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-Type RSU”; an eNB can be referred to as "eNB type RSU"; a gNB can be referred to as "gNB type RSU"; and the same. In one example, an RSU is a computing device that is coupled to a radio frequency circuit located on the roadside that supports connectivity for passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, and applications / software for capturing and controlling ongoing vehicle and pedestrian traffic. The RSU can provide the very low latency communication required for high-speed events such as: B. Accident avoidance, traffic warnings and the like. Additionally or alternatively, the RSU can offer further mobile radio / WLAN communication services. The components of the RSU can be packaged in a weatherproof enclosure suitable for outdoor installation and can contain a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic light controller or a backhaul network.

In some embodiments, the RAN 1004 an LTE-RAN 1010 with eNBs, for example eNB 1012. The LTE RAN 1010 can provide an LTE air interface with the following properties: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; Turbo codes for data and TBCC for control; etc. The LTE air interface can refer to CSI-RS for CSI acquisition and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation and CRS for Support cell search and initial acquisition, channel quality measurements and channel estimation for coherent demodulation / detection at the UE. The LTE air interface can work on bands below 6 GHz.

In some embodiments, the RAN 1004 an NG-RAN 1014 with gNBs, for example gNB 1016 , or ng-eNBs, for example ng-eNB 1018 , be. The gNB 1016 can connect to 5G-capable UEs via a 5G NR interface. The gNB 1016 can connect to a 5G core via an NG interface, which can include an N2 interface or an N3 interface. The ng-eNB 1018 can also connect to the 5G core via an NG interface, but can also connect to a UE via an LTE air interface. The gNB 1016 and the ng-eNB 1018 can connect to each other via an Xn interface.

In some embodiments, the NG interface can be split into two parts, an NG-U interface (NG-U), which carries traffic data between the nodes of the NG-RAN 1014 and a UPF 1048 (e.g. N3 interface) transmits, and an NG-Control-Plane-Interface (NG-C), which is a signaling interface between the nodes of the NG-RAN 1014 and an AMF 1044 (e.g. N2 interface).

The NG-RAN 1014 can provide a 5G NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; Polar, repetition, simplex and reed-Muller codes for control and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface can be based on CSI-RS, PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH and a reference signal for time tracking. The 5G NR air interface can operate on FR1 bands, which include bands below 6 GHz, or FR2 bands, which include bands from 24.25 GHz to 52.6 GHz. The 5G NR air interface may include an SSB, which is a portion of a downlink resource grid that includes PSS / SSS / PBCH.

In some embodiments, the 5G NR air interface can use BWPs for various purposes. BWP can e.g. B. can be used to dynamically adapt the SCS. For example, the UE 1002 configured with multiple BWPs, with each BWP configuration having a different SCS. If the UE 1002 a BWP change is indicated, the SCS of the transfer is also changed. Another application example for BWP relates to energy saving. In particular, several BWPs can be used for the UE 1002 be configured with a different amount of frequency resources (e.g. PRBs) to support data transmission under different traffic load scenarios. A BWP that contains a smaller number of PRBs can be used for data transmission with a low traffic load and at the same time enables energy saving at the UE 1002 and in some cases with the gNB 1016 . For scenarios with a higher traffic load, a BWP containing a larger number of PRBs can be used.

The RAN 1004 is communicative with the CN 1020 coupled, which contains network elements to perform various functions in support of data and telecommunication services for customers / subscribers (e.g. users of the UE 1002 ) to provide. The components of the CN 1020 can be implemented in a physical node or in separate physical nodes. In some embodiments, NFV can be used to call any or all of the network elements of the CN 1020 to virtualize the functions provided on physical computing / storage resources in servers, switches, etc. A logical instantiation of the CN 1020 can be referred to as a network slice, and a logical instantiation of part of the CN 1020 can be referred to as a network sub-slice.

In some embodiments, the CN 1020 an LTE CN 1022 which can also be referred to as EPC. The LTE CN 1022 can MME 1024 , SGW 1026 , SGSN 1028 , HSS 1030 , PGW 1032 and PCRF 1034 that are coupled to one another via interfaces (or "reference points"), as shown. The functions of the elements of the LTE CN 1022 can be briefly introduced as follows.

The MME 1024 can implement mobility management functions to a current location of the UE 1002 track to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

The SGW 1026 can terminate an S1 interface to the RAN and data packets between the RAN and the LTE CN 1022 forward onto. The SGW 1026 can be a local mobility anchor point for inter-RAN node handover and can also provide an anchor for inter-3 GPP mobility. Other tasks can include lawful interception, charging, and enforcing some policies.

The SGSN 1028 can be a location of the UE 1002 track and perform security functions and access control. In addition, the SGSN 1028 Inter-EPC node signaling for mobility between different RAT networks, PDN and S-GW selection according to the MME 1024 , carry out the MME selection for handover etc. The S3 reference point between the MME 1024 and the SGSN 1028 can enable the exchange of user and bearer information for inter-3GPP access network mobility in the idle / active state.

The HSS 1030 may contain a database for network users including subscription-related information to aid in the handling of communication sessions by the network entities. The HSS 1030 can provide support for routing / roaming, authentication, authorization, name / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1030 and the MME 1024 can transfer subscription and authentication data for authentication / authorization of user access to the LTE CN 1020 enable.

The PGW 1032 can be an SGi interface to a data network (DN) 1036 schedule that an application / content server 1038 may contain. The PGW 1032 can send data packets between the LTE CN 1022 and the data network 1036 routes. The PGW 1032 can with the SGW 1026 be coupled via an S5 reference point in order to facilitate tunneling at the user level and tunnel management. The PGW 1032 may also contain a policy enforcement and billing data collection node (e.g. PCEF). In addition, the SGi reference point between the PGW 1032 and the data network 10 36 an operator-external public, a private PDN or an operator-internal packet data network, e.g. B. to provide IMS services. The PGW 1032 can use a Gx reference point with a PCRF 1034 be coupled

The PCRF 1034 is the policy and charge control element of the LTE CN 1022 . The PCRF 1034 can be communicative with the app / content server 1038 be coupled to determine suitable QoS and charging parameters for service flows. The PCRF 1032 can provide associated rules in a PCEF (via Gx reference point) with the corresponding TFT and QCI.

In some embodiments, the CN 1020 a 5GC 1040 be. The 5GC 1040 can an AUSF 1042 , AMF 1044 , SMF 1046 , UPF 1048 , NSSF 1050 , NEF 1052 , NRF 1054 , PCF 1056 , UDM 1058 and AF 1060 that are coupled to one another via interfaces (or "reference points"), as shown. The functions of the elements of the 5GC 1040 can be briefly introduced as follows

The AUSF 1042 can provide data for the authentication of the UE 1002 store and process authentication-related functions. The AUSF 1042 can enable a common authentication framework for different types of access. In addition to communicating with other elements of the 5GC 1040 Via reference points, as shown, the AUSF 1042 have a Nausf service based interface.

The AMF 1044 can do other functions of the 5GC 1040 allow with the UE 1002 and the RAN 1004 to communicate and notify of mobility events related to the UE 1002 to subscribe. The AMF 1044 can be used for registration management (e.g. for the registration of the UE 1002 ), connection management, availability management, mobility management, lawful interception of AMF-related events and access authentication and authorization. The AMF 1044 can provide transport for SM messages between the UE 1002 and the SMF 1046 and act as a transparent proxy for routing SM messages. AMF 1044 can also transport SMS messages between UE 1002 and provide an SMSF. The AMF 1044 can with the AUSF 1042 and the UE 1002 interact to perform various security anchor and context management functions. In addition, the AMF 1044 be a termination point of a RAN-CP interface, which is an N2 reference point between the RAN 1004 and the AMF 1044 may contain or be; and the AMF 1044 can be a termination point of the NAS ( N1 ) Signaling and performing NAS encryption and integrity protection. AMF 1044 can also do NAS signaling with the UE 1002 support via an N3 IWF interface.

The SMF 1046 can be responsible for SM (e.g. session establishment, tunnel management between UPF 1048 and on 1008 ); Assignment and management of UE IP addresses (including optional authorization); Selection and control of the UP function; Configuration of the traffic control on the UPF 1048 to get traffic to the right destination; Termination of interfaces to policy control functions; Control of part of the policy enforcement, charging and QoS functions; legally compliant interception (for SM Events and interface to the LI system); Termination of SM parts of NAS messages; Downlink data notification; Initiation of AN-specific SM information that is sent via AMF 1044 via N2 to AN 1008 be sent; and determining the SSC mode of a session. SM can refer to the management of a PDU session, and a PDU session or "session" can refer to a PDU link service which enables the exchange of PDUs between the UE 1002 and the data network 1036 provides or enables.

The UPF 1048 can be used as an anchor point for intra-RAT and inter-RAT mobility, as an external PDU session point for connection to the data network 1036 and serve as a branch point to support multi-homed PDU sessions. The UPF 1048 can also perform packet routing and forwarding, perform packet inspection, enforce the part of the policy rules for the user level, intercept packets lawfully (UP collection), create traffic usage reports, perform QoS handling for a user level (e.g. packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g. SDF-to-QoS flow mapping), perform packet marking at transport level in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 1048 may include an uplink classifier to aid in routing traffic flows to a data network.

The NSSF 1050 may be a set of network slice instances that the UE 1002 operate, select. The NSSF 1050 can also determine the permitted NSSAI and the mapping to the subscribed S-NSSAIs if necessary. The NSSF 1050 can also determine the AMF rate required to operate the UE 1002 to be used, or a list of candidate AMFs based on appropriate configuration and possibly by querying the NRF 1054 . The selection of a set of network slice instances for the UE 1002 can through the AMF 1044 be triggered in which the UE 1002 by interacting with the NSSF 1050 is registered, which can lead to a change in the AMF. The NSSF 1050 can with the AMF 1044 interact via an N22 reference point; and can communicate with another NSSF on a visited network through an N31 reference point (not shown). In addition, the NSSF 1050 have an Nnssf service based interface.

The NEF 1052 services and capabilities provided by 3GPP network functions can be securely available to third parties, internal exposure / re-exposure, AFs (e.g. AF 1060 ), Edge computing or fog computing systems, etc. In such embodiments, the NEF 1052 authenticate, authorize or throttle the AFs. NEF 1052 can also translate information with the AF 1060 and information that is exchanged with internal network functions. The NEF 1052 can, for example, translate between an AF service identifier and internal 5GC information. The NEF 1052 can also receive information from other NFs based on the exposed capabilities of other NFs. This information can be found in the NEF 1052 be stored as structured data or in a data memory NF with standardized interfaces. The stored information can then be used by the NEF 1052 passed on to other NFs and AFs or for other purposes, e.g. B. analyzes can be used. In addition, the NEF 1052 have an Nnef service-based interface

The NRF 1054 can support service discovery functions, receive NF discovery requests from NF instances and make the information of the discovered NF instances available to the NF instances. NRF 1054 also manages information about available NF instances and their supported services. As used herein, the terms "instantiate", "instantiate" and the like can refer to the creation of an instance, and an "instance" can refer to a specific occurrence of an object that e.g. B. can occur during the execution of program code. In addition, the NRF 1054 have the nnrf service-based interface

The PCF 1056 can make policy rules available to the functions of the control level in order to enforce them, and can also support a uniform policy framework for regulating network behavior. The PCF 1056 can also implement a front end to access subscription information necessary for policy decisions in a UDR of the UDM 1058 are relevant. In addition to the communication shown with functions via reference points, the PCF 1056 an npcf service based interface

The UDM 1058 can process subscription-related information to aid in the handling of communication sessions by the network entities; and subscription data of the UE 1002 to save. For example, subscription data can be shared between the UDM 1058 and the AMF 1044 communicated. The UDM 1058 can contain two parts, an application Front end and a UDR. The UDR can store subscription data and policy data for the UDM 1058 and the PCF 1056 and / or structured data for exposure and application data (including PFDs for application detection, application requirement information for multiple UEs 1002 ) for the NEF 1052 to save. The Nudr service-based interface can be used by the UDR 221 issued to the UDM 1058 , PCF 1056 and NEF 1052 allow access to a specific set of the stored data as well as reading, updating (e.g. adding, changing), deleting and subscribing to notifications of relevant data changes in the UDR. The UDM may contain a UDM VU that is responsible for processing login information, site management, subscription management, and so on. Several different front ends can serve the same user in different transactions. The UDM-VU accesses the subscription information stored in the UDR and performs the processing of authentication credentials, the handling of the user identification, the access authorization, the registration / mobility management and the subscription management. In addition to communicating with other NFs via reference points, as shown, the UDM 1058 have the service-based interface Nudm

The AF 1060 can give the application influence on traffic control, provide access to the NEF and interact with the policy framework for policy control.

In some embodiments, the 5GC 1040 Enable edge computing by selecting operator / third party services that are geographically close to a point where the UE 1002 connected to the network. This can reduce latency and load on the network. To provide edge computing implementations, the 5GC 1040 a UPF 1048 near the UE 1002 Select and route traffic from the UPF 1048 to the data network 1036 Carry out via the N6 interface. This can be based on the UE subscription data, the UE location and that of the AF 1060 information provided. In this way, the AF 1060 affect UPF (re-) selection and traffic routing. When AF 1060 is regarded as a trustworthy entity, the network operator AF 1060 allow you to interact directly with the relevant NFs. In addition, the AF 1060 have a Naf service based interface

The data network 1036 can represent various network operator services, Internet access or third-party services that can be provided by one or more servers, e.g. B. the application / content server 1038 .

Further details and aspects are mentioned in connection with the examples described above and / or below. This in 10 The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed concept or one or more of the above (e.g. 1 - 9 ) and / or below (e.g. 11 ) described examples.

shows schematically a wireless network 1100 in accordance with various embodiments. The wireless network 1100 can a UE 1102 in wireless communication with an AN 1104 contain. The UE 1102 and on 1104 may be similar and substantially interchangeable with like components described elsewhere herein.

The UE 1102 can through the connection 1106 with the AN 1104 be communicatively coupled. The connection 1106 is shown as an air interface to enable communicative coupling and may conform to cellular communication protocols such as an LTE protocol or an SGNR protocol operating at mmWave or sub-6GHz frequencies

The UE 1102 can be a host platform 1108 included that with a modem platform 1110 is coupled. The host platform 1108 can be an application processing circuit 1112 included with a circuit for protocol processing 1114 the fashion platform 1110 can be coupled. The application processing circuit 1112 can do different applications for the UE 1102 execute, generate / lower the application data. The application processing circuit 1112 can also implement one or more layer operations to send / receive application data to / from a data network. These layers can include transport (e.g. UDP) and Internet (e.g. IP) operations. The protocol processing circuitry 1114 may implement one or more of the layer operations to transmit or receive data over the link 1106 to facilitate. Those from the protocol processing circuitry 1114 implemented shift operations can e.g. B. MAC, RLC, PDCP, RRC and NAS operations.

The fashion platform 1110 can also use a digital baseband circuit 1116 that may implement one or more layer operations that are "below" layer operations required by protocol processing circuitry 1114 run on a network protocol stack. These operations can include, for example, PHY operations, including one or more HARQ-ACK functions, scrambling / descrambling, coding / decoding, layer mapping / de-mapping, modulation symbol mapping, determination of the received symbols / bit metric, precoding / decoding of multiple antenna connections, which can comprise one or more space-time, space-frequency or spatial encodings, reference signal generation / detection, generation and / or decoding of preamble sequences, generation / detection of synchronization sequences, blind decoding of control channel signals and other related functions

The fashion platform 1110 can also have a transmission circuit 1118 , a receiving circuit 1120 , an RF circuit 1122 and an RF front end (RFFE) 1124 contain one or more antenna fields 1126 may contain or be associated with them. In short, the transmission circuit 1118 a digital-to-analog converter, mixer, intermediate frequency components (IF), etc. The receiving circuit 1120 may contain an analog-to-digital converter, mixer, IF components, etc.; the RF circuit 1122 may include a low noise amplifier, a power amplifier, power tracking components, etc .; the RFFE 1124 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phasing antenna components), etc. The selection and arrangement of the components of the transmission circuit 1118 , the receiving circuit 1120 , the RF circuit 1122 , the RFFE 1124 and the antenna panels 1126 (commonly referred to as "transmit / receive components") can be specific to the details of a particular implementation, such as: Whether the communication is TDM or FDM, in mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components can be arranged in several parallel transmit / receive chains, they can be in the same or in on different chips / modules, etc. In some embodiments, the protocol processing circuitry 1114 contain one or more instances of control circuits (not shown) in order to provide control functions for the transmitting / receiving components

UE reception can be through and via the antenna fields 1126 who have favourited RFFE 1124 who have favourited RF circuit 1122 , the receiving circuit 1120 who have favourited digital baseband circuit 1116 and the protocol processing circuitry 1114 getting produced. In some embodiments, the antenna panels 1126 a transfer from the contractor 1104 by receiving beamforming of signals received from a plurality of antenna / antenna elements of the one or more antenna arrays 1126 be received.

UE transmission can be to and from the protocol processing circuitry 1114 who have favourited digital baseband circuit 1116 , the transmission circuit 1118 who have favourited RF circuit 1122 who have favourited RFFE 1124 and the antenna fields 1126 being constructed. In some embodiments, the transmission components of the UE 1104 apply a spatial filter to the data to be transmitted in order to form a transmit beam that is emitted by the antenna elements of the antenna arrays 1126 is sent out.

Similar to the UE 1102 can the AN 1104 a host platform 1128 include those with a modem platform 1130 is coupled. The host platform 1128 can use circuits for application processing 1132 included with circuits for protocol processing 1134 the fashion platform 1130 are coupled. The modem platform can also have a digital baseband circuit 1136 , a transmission circuit 1138 , a receiving circuit 1140 , an RF circuit 1142 , an RFFE circuit 1144 and antenna fields 1146 contain. The components of the AN 1104 can be similar and essentially interchangeable with components of the UE with the same name 1102 be. In addition to performing data transmission / reception, as described above, the components of the AN 1108 perform various logical functions, e.g. B. RNC functions such as radio bearer management, dynamic uplink and downlink radio resource management and data packet scheduling.

Further details and aspects are mentioned in connection with the examples described above. This in 11 The example shown may include one or more optional additional features that correspond to one or more aspects related to the proposed concept or one or more examples described above (e.g. 1 - 10 ) were mentioned.

The aspects and features that are described in connection with a specific one of the previous examples can also be combined with one or more of the further examples to form a to replace an identical or similar feature of this further example or to additionally introduce the feature into the further example.

Examples can furthermore be or relate to a (computer) program with a program code for executing one or more of the above methods when the program is executed on a computer, a processor or some other programmable hardware component. Steps, operations or processes of various of the methods described above can therefore also be carried out by programmed computers, processors or other programmable hardware components. Examples can also include program storage devices, e.g. Digital data storage media that are machine-, processor- or computer-readable and encode or contain machine-executable, processor-executable or computer-executable programs and instructions. Program storage devices can e.g. B. digital storage devices, magnetic storage media such as magnetic disks and tapes, hard disk drives or optically readable digital data storage media or be. Other examples can also include computers, processors, control units, (field) programmable logic arrays ((F) PLAs), (field) programmable gate arrays ((F) PGAs), graphics processing units (GPU), application-specific integrated circuits (ASICs), integrated circuits (ICs), or system-on-a-chip systems (SoCs) programmed to perform the steps of the methods described above.

It is also understood that the disclosure of several steps, processes, operations or functions disclosed in the description or the claims should not be interpreted as necessarily in the order described, unless this is explicitly stated in the individual case or is absolutely necessary for technical reasons . Therefore, the foregoing description does not limit the performance of multiple steps or functions to any particular order. In addition, in further examples, a single step, a function, a process or an operation can contain and / or be subdivided into several sub-steps, functions, processes or operations.

If some aspects have been described in relation to a device or system, these aspects should also be understood as a description of the corresponding method. So z. B. a block, a device or a functional aspect of the device or system a feature, such as. B. correspond to a process step of the corresponding process. Accordingly, aspects that are described in relation to a method are also to be understood as a description of a corresponding block, a corresponding element, a property or a functional feature of a corresponding device or a corresponding system.

In one or more embodiments, at least one of the components shown in one or more of the preceding figures can be configured to perform one or more operations, techniques, processes and / or methods to support the PDU session “Anchor”, as follows Example section described. For example, the baseband circuit arrangement, as described above in connection with one or more of the preceding figures, can be designed to operate in accordance with one or more of the examples listed below. In another example, the circuit arrangement associated with a UE, a base station, a network element, etc., as described above in connection with one or more preceding figures, can be designed to operate according to one or more of the examples below in the examples section.

The following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate example. It should also be noted that although in the claims one dependent claim refers to a particular combination with one or more other claims, other examples may also include a combination of the dependent claim with the subject matter of any other dependent or independent claim. Such combinations are hereby explicitly suggested, unless it is stated in the individual case that a certain combination is not intended. Furthermore, features of a claim should be included for every other independent claim as well, even if that claim is not defined directly as dependent on that other independent claim.

One example (e.g. Example 1) relates to a component for a mobile communication network that includes one or more interfaces that are configured to communicate with a third party from an external data network; and processing circuitry configured to control the one or more interfaces and: the third party, e.g. B. an application of the third party, Access to the provision of a service function chain, SF chain, a guideline for the use of the SF chain that is used in the mobile communication network is granted. Another example (e.g. example 2) relates to an example described above (e.g. example 1) at the processing circuitry is further configured to enable service function chaining (SFC) by controlling and / or managing the SF chain based on the SF chain policy; and forwards data through the SF chain.

• network Address Translation (NAT), IP-Tunnel-Endpunkte, Paketklassifizierer, Deep Packet Inspection (DPI), Lawful Inspection (LI), Transmission Communication Protocol (TCP), Proxies, Load Balancer, Firewall-Funktionen, Transcoder, Video-Optimierer, Funktionen zur Anwendungserkennung und -kontrolle, Anti-Malware, Key Performance Indicator (KPI), Monitoring, Distributed-Denial-of-Service (DDoS) und Parental Control.

Another example (e.g. example 3) relates to an example described above (e.g. one of examples 1-2) in which the SF chain comprises at least one service function from the group of:

• network address translation (NAT), IP tunnel endpoints, packet classifiers, deep packet inspection (DPI), lawful inspection (LI), transmission communication protocol (TCP), proxies, load balancer, firewall functions, transcoder, video optimizer, Functions for application detection and control, anti-malware, key performance indicators (KPI), monitoring, distributed denial-of-service (DDoS) and parental control.

Another example (e.g. Example 4) relates to an example described above (e.g. one of Examples 2-3) in which the SFC is in a user level, UP, and / or a control level, CP, the Component is used by a service function chaining function, SFCF.

Another example (e.g. Example 5) relates to an example described above (e.g. Example 4) in which the SFCF is activated and is in a user level function, UPF, of the component.

Another example (e.g. Example 6) relates to an example previously described (e.g. Example 5) in which the processing circuitry is further configured to allow an application server, AS, of the third party to access the in the SFCF located at the UPF using N6 reference points.

Another example (e.g. Example 7) relates to an example described above (e.g. one of Examples 4-6) in which the SFCF is an independent network function that is between a UPF of the component and an AS of the third-party provider is located.

Another example (e.g., Example 8) relates to an example previously described (e.g., one of Examples 4-7) in which the processing circuitry is further configured to allow a third-party AS to access the SFCF using N6, extended N6, N6e, and / or N9 reference points.

Another example (e.g., Example 9) relates to an example previously described (e.g., one of Examples 4-8) in which the processing circuitry is further configured to provide the UP for a Protocol Data Unit, PDU, Assigns a session using a session management function, SMF.

Another example (e.g. Example 10) relates to an example described above (e.g. one of Examples 4-9) in which the SFCF is activated and is in the UPF and a control level function, CPF, of the component is located.

Another example (e.g. example 11) relates to an example described above (e.g. example 10) in which the SFCF in the UP cooperates with the UPF via a reference point Nx in order to direct the traffic in the UPF and / or the service SFCF in the CP contains the SFC.

Another example (e.g., Example 12) relates to an example previously described (e.g., any of Examples 10-11) wherein the processing circuitry is further configured to configure: the SMF for traffic that Requires service function chaining; the UPF to route traffic to the SFCF in the UP to pass through a configured SFP; and the SFCF to route traffic back to the UPF.

Another example (e.g. Example 13) relates to an example described above (e.g. one of Examples 10-12)

Another example (eg example 3) relates to an example described above (eg one of examples 1-2), the SFCF comprising a multiplicity of network functions, a first SFCF being activated and located in the UPF and a second SFCF activated and located in the CPF.

Another example (e.g., Example 14) relates to an example previously described (e.g., Example 13) in which the processing circuitry is further configured to configure the UPF through the SMF for traffic, the SCF- Services, and routes traffic over an N6S interface to the SCFC in the UP to pass an SFP and forward the traffic using an N6 interface.

Another example (e.g. Example 15) relates to an example described above (e.g. one of Examples 10-14) in which the PDU session contains a traffic flow that is via identical or different service function paths, SFPs, is transported.

Another example (e.g., Example 16) relates to an example previously described (e.g., Example 15), wherein the processing circuitry is further configured to set a service function path, SFP, of the SFC based on an SFC policy for the Configure the traffic flow of the PDU session using the SMF and / or the SFCF.

Another example (e.g., Example 17) relates to an example previously described (e.g., any of Examples 15-16) in which the processing circuitry is further configured to skip all service functions, SFs, of a traffic flow that is not assigned to an SFP.

Another example (e.g. Example 18) relates to an example described above (e.g. one of Examples 16-17), where an SFC parameter and / or a traffic classifier for the SFC policy for the AS at least one element of the group comprises: SFC display; SFC configuration; SFP configuration; Application ID and the corresponding SFP index; associated PDU session parameters, including PDU session type or a slice / service type, SST; and Slice Differentiator, SD.

Another example (e.g. example 19) relates to an example described above (e.g. example 18) in which the SFC parameter of the SFC service contains an element from the following group: SFC service ID ; SFC configuration; SFP configuration; SFC Routing Policy; and validity parameters for the SFC service identified by the SFC service ID.

Another example (e.g. Example 20) relates to an example previously described (e.g. Example 19), where the SFC routing policy includes a traffic classifier that maps between an SPF index and traffic filtering rules for routing Indicates traffic to the first SF in an SFP identified by an SFP index and / or a traffic declassifier specifying rules for combining traffic from an SF in an SFP identified by an SFP index, includes.

Another example (e.g. Example 21) relates to an example described above (e.g. one of Examples 19-20) in which the validity parameters for the SFC service contain an element from the following group: duration; Planned time span; Application id; and associated PDU session parameters, including PDU session type.

Another example (e.g. Example 3) relates to a previously described example (e.g. one of Examples 1-2), which further comprises ...

Another example (e.g., Example 22) relates to an example previously described (e.g., any of Examples 18-21) in which processing circuitry is further configured to provide an SPF index that is assigned to an SFC classifier.

Another example (e.g., Example 23) relates to an example previously described (e.g., one of Examples 20-22) in which the traffic declassifier provides an N6 tunnel ID which is the N6 reference point of a DNAI , Data network access ID, for a DN concludes with the assignment to an SFC reclassification policy.

Another example (e.g. Example 24) relates to an example described previously (e.g. Example 23) in which the SFC reclassification can contain an element from the following group: UE address, application ID, Media type, traffic priorities and SPF index.

Another example (e.g., Example 25) relates to an example previously described (e.g., any of Examples 9-24) wherein the processing circuitry is further configured to retrieve information for assignment / configuration using the SMF from a Unified Data Repository , UDR, des Mobile communication network that stores the service subscription of a user equipment, UE, receives via a policy control function, PCF, of the mobile communication network that stores the UE service policy.

Another example (e.g., Example 26) relates to an example previously described (e.g., one of Examples 9-25) wherein the processing circuitry is further configured to provide a data path of the traffic flows of the PDU session using the Control the SMF so that the PDU session can include multiple N6 interfaces at the same time, based on a routing policy requested by the AS via the AF of the mobile communication network.

Another example (e.g., Example 27) relates to an example previously described (e.g., Example 26) in which the processing circuitry is further configured to use multiple UPFs by using uplink classifiers, UL CL, functionality, and / or IPv6 branching functionality used to control the data path, including a UPF capable of terminating multiple PDU session anchors, PSA, and multiple UPFs supporting PDU session anchor, PSA, functionality.

Another example (e.g. Example 28) relates to an example previously described (e.g. Example 27) wherein the processing circuitry is further configured to: UPF with SFCF and / or standalone SFCF using the SMF for the Assign PDU session, each PSA supporting SFC with different ordered SFs and one or more SFPs; and terminate the UPFs with SFCF and / or standalone SFCF on different N6 interfaces to the same data network, DN.

Another example (e.g., Example 29) relates to an example previously described (e.g., one of Examples 1-28) in which the processing circuitry is further configured to connect a PSA to a local access in the Adds proximity to the RAN node, enabling edge computing.

Another example (e.g., Example 30) relates to an example previously described (e.g., one of Examples 1-29) in which the processing circuitry is further configured to receive an SFC service request from an AF AS through a network exposure function, NEF.

Another example (e.g., Example 31) relates to an example previously described (e.g., Example 30) in which the processing circuitry is further configured to receive an SFC policy with an SFC parameter from the AF receives.

Another example (e.g. example 32) relates to an example described above (e.g. example 31), the SFC parameter of the SFC policy comprising at least one element of the group: SFC display, SFC configuration , SFP configuration, application ID and the corresponding SFP index, associated PDU session parameters, including PDU session type or an SST, and SD.

Another example (e.g., Example 33) relates to an example previously described (e.g., one of Examples 31-32), wherein the processing circuitry is further configured to update the SFC Policy with SFC- Requests parameters and storage as part of the subscription data via a Nudm_ParameterProvision_Update request message of the SFC parameter from a UDR.

Another example (e.g., Example 34) relates to an example previously described (e.g., Example 33) in which the processing circuitry is further configured to provide notification of the updated signer data via Nudm_SDM_Notification Notify message from a UDM.

Another example (e.g., Example 35) relates to an example previously described (e.g., any of Examples 30-34) wherein the processing circuitry is further configured to respond to a request to dynamically infer the SFP routing for the application the AS receives from the AF.

Another example (e.g. example 36) relates to an example described above (e.g. example 35), wherein the request is an Nnef_TrafficInfluence_Create / Update / Delete message that includes at least one element of the group: SFC -Display, SFC configuration, SFP configuration, application ID and the corresponding SFP index, associated PDU session parameters, including PDU session type or a slice / service type, SST, SD.

Another example (e.g., Example 37) relates to an example previously described (e.g., one of Examples 30-36), wherein the processing circuitry is further configured to receive a request from the NF to set up a connection between the NF and the NEF to enable the NF to provide the SFC policy to the UE.

Another example (e.g. example 38) relates to an example described above (e.g. example 37) in which the component is still configured in such a way that it has an NF session with the required SFC parameters of the SFC -Service configuration procedure builds up.

Another example (e.g. Example 39) relates to a method for a mobile communication network that includes generating an SCF in the mobile communication network; and providing access to the third party, e.g., a third party application, to provide a service function chain, SF chain, policy on the use of the SF chain employed in the mobile communications network.

Another example (e.g. example 40) relates to a computer program with a program code for performing the method according to the method described above (e.g. example 39) when the computer program is executed on a computer, a processor or a programmable hardware component.

Example A1 may include a method for activating the service function chaining function in a 5G system.

Example A2 may include the method of Example A1 or another example herein, wherein the service function chain function, which includes one or more service functions, includes, but is not limited to, the following service function: Network Address Translation (NAT), IP tunnel endpoints, Packet classifier, deep packet inspection (DPI), lawful inspection (LI), TCP proxies, load balancer, firewall functions, transcoder, video optimizer.

Example A3 may include the method of Example A2 or another example herein, wherein the service function chain function is in UPF that terminates N6 reference points with trusted data networks or external data networks.

Example A4 can include the method of example A2 or another example herein, wherein the service function chain function is an independent network function that is located between the UPF and the application server via the interface N6S and the service function chain terminates N6 reference points with trustworthy data networks or external data networks.

Example A5 may include the method of Examples A3 or A4, or another example herein, wherein a UPF for a PDU session of a UE is assigned by an SMF and the SMF can configure an SFC with one or more SFPs for the PDU session.

Example A6 may include the method of Example A5 or another example herein, wherein the assignment of SFCs and SFPs may be based on the UE service policy stored in the PCF and the UE service subscription stored in the UDR.

Example A7 may include the method of Example A6, or another example herein, wherein an SFC includes service functions that may form one or more service function paths (SPFs) in which traffic in each SFP flows through the ordered service functions.

Example A8 may include the method of Example A7, or another example herein, wherein the traffic streams that do not have an SFP assigned skip all SFs in the SFC.

Example A9 may include a method from Example A1-A8 or any other example herein, wherein the SMF controls the data path of a PDU session that simultaneously correspond to multiple N6 interfaces to the same packet data network via multiple UPFs, including a UPF that is included in the Is able to terminate multiple PDU Session Anchors (PSA) and multiple UPFs that support the functionality of PDU Session Anchors (PSA).

Example A10 may include the method of Example A9 or another example herein, wherein the UPF capable of terminating multiple PDU session anchors (PSA) may be with uplink classification functionality or IPv6 branching functionality.

Example A11 may include the method of Example A10 or another example herein, where if SFC is supported, the SMF can assign the UPFs with SFCs for a PDU session in which each PSA SFC with different service functions (SFs) and one or more service function paths (SFPs) are supported and terminated at different N6 to the same DN.

Example A12 may include the method of Example A11 or any other example herein, wherein if the PSA is at the local access near the RAN node, the PDU session enables edge computing support.

Example A13 may include the method of Example A12 or another example herein, wherein for a UPF that is IPv6 branching, two IPv6 prefixes have been assigned to the UE and the UE routes traffic with different IPv6 prefixes to the DN.

Example A14 may include the method of Example A13 or another example herein, wherein the UE is updated with the UE configuration by the PCF for the following SFC parameters and applying traffic classifiers and SFs based on the UE policy for SFC parameters: SFC indicator: indicates that the parameters are for the SFC service; SFC configuration: defines the parameters of each SF; SFP configuration, which contains the SFP index and the corresponding ordered SFs; Application ID and the corresponding SFP index; optional associated PDU session parameters, including PDU session type, e.g. B. IP, DNN or a slice / service type (SST) (e.g. eMBB, URLLC, MIoT, V2X etc.) and optional slice differentiator (SD). Example A15 may include the method of Example A14 or another example herein, where the SFC configuration includes the video optimizer and the SF parameters include the video parameters for optimization at the SF of the video optimizer.

Example A16 may include the method of Example A14 or any other example herein, where the SFC configuration includes Load Balancer and the SF parameters include the criteria for balancing application loads.

Example A17 may include the method of Example A1 or another example herein wherein the SFC service is requested by an AF (application function) via NEF.

Example A18 may include the method of Example A17 or another example herein, wherein the AF provides the NEF with SFC parameters to be updated in Nnef_ParameterProvision_Update Request, which contains the SFC parameters: SFC display: indicates that the Parameters for the SFC service are; SFC configuration: defines the parameters of each SF; SFP configuration, which contains the SFP index and the corresponding ordered SFs; Application ID and the corresponding SFP index; optional associated PDU session parameters, including PDU session type, e.g. B. IP, DNN or a slice / service type (SST) (e.g. eMBB, URLLC, MIoT, V2X etc.) and optional slice differentiator (SD).

Example A19 may include the method of Example A18 or another example herein, wherein if the AF is authorized by the NEF to provide the parameters, the NEF requests the update and storage of the provided parameters as part of the subscriber data via a Nudm_ParameterProvision_Update request message, which contains the parameters provided: SFC display: indicates that the parameters are for the SFC service; SFC configuration: defines the parameters of each SF; SFP configuration, which contains the SFP index and the corresponding ordered SFs; Application ID and the corresponding SFP index; optional associated PDU session parameters, including PDU session type, e.g. B. IP, DNN or a slice / service type (SST) (e.g. eMBB, URLLC, MIoT, V2X etc.) and optional slice differentiator (SD).

Example A20 may include the method of example A19 or another example herein, wherein the UDR stores the data provided as part of the subscriber data and responds with the message Nudr DM Update Response and the UDM transfers the subscribed network function (e.g., PCF) the updated subscriber data via the message Nudm_SDM_Notification Notify, the subscriber data containing the SFC indication: indicate that the parameters are for the SFC service; the SFC configuration: define the parameters of each SF; the SFP configuration, which contains the SFP index and the corresponding ordered SFs; the application ID and the corresponding SFP index; optional associated PDU session parameters, including PDU session type, e.g. E.g. B. IP, DNN, or a slice / service type (SST) (e.g. eMBB, URLLC, MIoT, V2X etc.) and optional slice differentiator (SD).

Example B1 may include a method for activating the service function chaining in a 5G system.

Example B2 may include the method of Example B1, wherein the service function chain service is provided by a service function that includes one or more service functions in the user plane that include, but are not limited to, the following service function: Network Address Translation (NAT), IP tunnel endpoints, packet classifiers, deep packet inspection (DPI), lawful inspection (LI), TCP proxies, load balancers, firewall functions, transcoders, video optimizers, URL filters, application detection and control (ADC).

Example B3 can include the method of example B2, the service function chain function being in the user level at UPF, which terminates N6 reference points with trustworthy data networks or external data networks.

Example B4 can include the method of example B2, wherein the service function chain function in the user level is an independent network function that is located between the UPF and the application server via the interface N6S and the service function chain terminates N6 reference points with trustworthy data networks or external data networks.

Example B5 may include the method of Example B3 or B4, where a UPF for a PDU session of a UE is assigned by an SMF and the SMF can configure a user-level SFCF with one or more SFPs for the PDU session.

Example B6 can include the method of Example B5, wherein the assignment of SF (s) in the user plane and SFPs can be based on the UE service policy stored in the PCF and the UE service subscription stored in the UDR.

Example B7 may include the method of Example B6, where an SFC includes service functions that may form one or more service function paths (SPFs) in which traffic in each SFP flows through the ordered service functions.

Example B8 may include the method of Example B7, where the traffic flows that do not have an SFP assigned skip all SFs in the SFC.

The method of claim

Example B9 may include the method of example B2, where the service function chain function is both a function of the control plane and a function of the user plane, the service function chain function in the user plane having an interface with UPF via a new reference point Nx to route the traffic in UPF , and the service function chain function in the control plane contains the SFC guidelines for routing the traffic that must pass through a particular service function path (SFP).

Example B10 may include the method of Example B9, where the UPF is configured by the SMF for traffic that requires service function chaining services, and the UPF routes the traffic to the service function chaining function in the user plane to traverse configured SFPs and then forwards the traffic back to the UPF .

Example B11 may include the method of Example B2, where the service function chain service is provided by two separate network functions, including the control plane function and the user plane function, the service function chain function in the user plane having an interface with UPF via a new reference point N6S to route the traffic in UPF, and the service function chain function in the control plane contains the SFC guidelines for routing the traffic that must go through a particular service function path (SFP).

Example B12 may include the method of Example B11, wherein the UPF is configured by the SMF for traffic that requires service function chaining services and the UPF is configured for the traffic Controls service function chaining function in the user plane over the N6S interface to pass configured SFPs before forwarding the traffic to the N6 interface.

Example B13 can include the method of Example B1, wherein the SFC parameters of the SFC service can contain at least one of the following information: SFC service ID as the service ID of this set of SFC parameters for the SFC service; SFC configuration as one or more SFs with the corresponding SF parameters; SFP configuration as the SFP index with the corresponding ordered SFs;

Example B14 can include the method of example B13, wherein the SFC parameters of the SFC service also contain the information of the SFC routing policy, which contains a traffic classifier that maps between an SPF index and traffic filter rules for the forwarding of traffic to the first SF in an SFP identified by an SFP index, and a traffic declassifier displaying traffic filtering rules for aggregating traffic from the last SF in an SFP identified by an SFP index.

Example B15 can include the method of example B13 or B14, the SFC parameters of the SFC service also including the information of the validity parameters for the SFC service identified by the SFC service ID, which includes one or more of the following information may include: duration, planned time period, application ID (s), associated PDU session parameters, including PDU session type, e.g. B. IP / Ethernet / Unstructure, DNN or a slice / service type (SST) (e.g. eMBB, URLLC, MIoT, V2X etc.) and optional slice differentiator (SD).

Example B16 may include the method of Example B13, where the traffic classifier provides an SPF index associated with the SFC classification policy based on different levels or granularities per packet, which may contain one or more of the following information, but not on UE address , Application ID, media type, traffic priorities are restricted.

Example B17 may include the method of Example B13, wherein the traffic declassifier provides an "N6 tunnel ID" that completes the N6 reference point of a DNAI (data network access ID) for a data network with the association with the SFC reclassification policy that includes an or contains some of the following information to combine traffic from one or more SFPs before forwarding them to an application's application server.

Example B18 can include the method of Example B17, wherein the policy can be based on the information UE address, application ID, media type, traffic priorities, SPF index, but is not limited thereto.

Example B19 can include the method of example B16 or claim B17, whereby the DPI capability on the traffic classifier is required if the information for the policy is only available in the traffic payload.

Example Z01 may contain an apparatus that comprises means for performing one or more elements of a method that is described in or is related to one of Examples 39, A1-A20, B1-B19 or another method or process described herein.

Example Z02 may include one or more non-transitory computer-readable media that include instructions to cause an electronic device, when the instructions are executed by one or more processors of the electronic device, to perform one or more elements of a method described in any of Examples 39 , A1-A20, B1-B19 or any other method or process described herein or relates to it.

Example Z03 may include a device that includes logic, modules, or circuitry to perform one or more elements of a method described in or with any of Examples 39, A1-A20, B1-B19, or any other method or process described herein related.

Example Z04 may comprise a method, a technique or a process as described in or associated with any of Examples 39, A1-A20, B1-B19 or in parts thereof.

Example Z05 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method to perform the techniques or the process as described in or associated with any of Examples 39, A1-A20, B1-B19 or parts thereof.

Example Z06 may contain a signal as described in or relating to Examples 39, A1-A20, B1-B19 or in sections or parts thereof.

Example Z07 may contain a datagram, packet, frame, segment, protocol data unit (PDU) or message as described in or as described in Examples 39, A1-A20, B1-B19 or in sections or parts thereof otherwise described in the present disclosure.

Example Z08 may include a signal encoded with data as described in Examples 39, A1-A20, B1-B19, or in portions or portions thereof, or otherwise described in the present disclosure.

Example Z09 can contain a signal that is encoded with a datagram, packet, frame, segment, a protocol data unit (PDU) or a message, as described in Examples 39, A1-A20, B1-B19 or in sections or parts thereof or otherwise described in the present disclosure.

Example Z10 may include an electromagnetic signal carrying computer readable instructions, the execution of the computer readable instructions by one or more processors serving to cause the one or more processors to use the method, technique, or process, as in any of the examples 39, A1-A20, B1-B19 or parts thereof described or associated with them.

Example Z11 may contain a computer program that comprises instructions, the execution of the program by a processing element serving to cause the processing element to implement the method, the techniques or the process, as in one of the examples 39, A1-A20, B1-B19 or parts thereof described or associated with it.

Example Z12 may contain a signal on a wireless network as shown and described herein.

Example Z13 may include a method of communicating in a wireless network as shown and described herein.

Example Z14 may include a system for providing wireless communication as shown and described herein.

Example Z15 may include a device for providing wireless communication as shown and described herein. Any of the examples described above can be combined with any other example (or a combination of examples), unless expressly stated otherwise. The foregoing description of one or more implementations has provided an illustration and description, but is not intended to be exhaustive or to limit the scope of the exemplary embodiments to the particular form disclosed. Modifications and variations are possible in light of the preceding teachings and can be obtained from the practice of various exemplary embodiments.

Abbreviations

Unless otherwise used here, the terms, definitions and abbreviations correspond to the terms, definitions and abbreviations defined in 3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of the present document, the following abbreviations can be applied to the examples and working examples discussed herein. 3GPP Third Generation Partnership Project 4G (fourth generation); Fourth generation 5G (fifth generation); Fifth generation 5GC (5G Core network); 5G core network 5GS G system ACK (Acknowledgment); confirmation AF (Application Function); Application function AT THE (Acknowledged Mode); confirmed mode AMBR Aggregated maximum bit rate AMF Access and mobility management function AT (Access Network); Access network ANR Automatic Neighbor Relation AP An application protocol, antenna connection, access point API Application programming interface APN (Access point name); Access point name ARP-Z Allocation and storage priority ARQ (Automatic Repeat Request); automatic repeat request AS (Access Stratum); Access stratum ASN. 1 Abstract syntax notation one EXEC (Authentication Server Function); Authentication server function AWGN Additive white Gaussian noise BAP Backhaul customization protocol BCH (Broadcast Channel); Broadcast channel BER (Bit Error Ratio); Bit error rate BFD Beam failure detection BLER (Block Error Rate); Block error rate BPSK (Binary Phase Shift Keying); binary phase shift keying BRAS -Broadband remote access server BSS (Business Support System); Business support system BS (Base Station); Base station BSR (Buffer Status Report); Buffer status report BW (Bandwidth); Bandwidth BWP (Bandwith Part); Bandwidth section C-RNTI Cell Radio Network Temporary Identity CA approx irrier aggregation, certification body CAPEX (CAPital EXpenditure); Capital expenditure CBRA Contention Based Random Access CC Co mponent carrier, country code, cryptographic checksum CCA (Clear Channel Assessment); Free channel assessment CCE (Control Channel Element); Control channel element CCCH (Common Control Channel); common control channel CE (Coverage Enhancement); Coverage improvements CDM (Content Delivery Network); Content delivery network CDMA (Code-Division Multiple Access); Code division multiple access CFRA Contention Free Random Access CG (Cell Group); Cell group CI (Cell Identity) cell identity CID Cell ID (e.g. positioning method) CIM Common Information Model CIR (Carrier to Interference Ratio); Carrier-to-Interference Ratio CK (Cipher key); Encryption key CM Connection management, conditionally mandatory CMAS Commercial Mobile Alert Service CMD (Command); command CMS (Cloud Management System); Cloud management system CO (Conditional Optional); conditionally optional COMP Coordinated multi-point CORES ET (Control Resource Set); Tax Resource Rate COTS (Commercial Off-the-Shelf); common commercial standard CP Control Plane, Cyclic Prefix, Connection Point CPD End point descriptor CPE Coworkers own devices CPICH (Common Pilot Channel); common pilot channel CQI (Channel Quality Indicator) 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); Communal Resource Block CRC (Cyclic Redundancy Check); cyclical redundancy check CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI (Cell-RNTI); Cell RNTI CS (Circuit Switched); circuit switched CSAR (Cloud Service Archive); Clound service archive CSI (Channel State Information); Channel state information CSI-IM CSI interference measurement CSI-RS (CSI Reference Signal); CSI reference signal CSI-RSRP CSI reference signal received power CSI-RS RQ CSI reference signal reception quality CSI-SINR (CSI signal-to-noise and interference ratio); CSI Signal-to-noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSS Ge common search space, cell-specific search space CTS (Clear-to-Send); Readiness to send CW (Codeword); code word CWS Contention Window Size); Conflict window size D2D (Device-to-device); Device-to-device DC Dual connectivity, direct current DCI- Downlink control information DD DoSDistributed Denial of Service DF (Deployment Flavor); Provisioning flavor DL Downlink DMTF Distributed Management Task Force DPDK Data Plane Development Kit DM-RS, DMRS Demodulation reference signal DN (Data network); Data network DRB (Data Radio Bearer); Radio data carriers DRS (Discovery Reference Signal); Detection reference signal DRX (Discontinuous Receotion): discontinuous receipt DSL Thu male-specific language. Digital Subscriber Line DSLAM (DSL Access Multiplexer); DSL access multiplexer DwPTS (Downlink Pilot Time Slot); Downlink pilot time slot E-LAN Ethernet local area network E2E (End-to-end); End-to-end (ECCA CCA); lung, extended clear channel assessment; extended extended free channel assessment-extended CCA ECCE E Extended control channel element, enhanced CCE ED (Energy Detection); Energy detection EDGE E increased data rates for GSM Evolution (GSM Evolution) EGMF Exposure governance management function EGPRS (Enhanced GPRS), improved GPRS EIR Equipment Identity Register eLAA enhanced Licensed Assisted Access, extended LAA EM (Element Manager); Element manager eMBB Enhanced Mobile Broadband EMS (Element Management System); Element management system eNB evolved NodeB, E-UTRAN Node B EN-DC E-UTRA-NO Dual connectivity EPC Evolved Packet Core EPDCC H enhanced PDCCH, enhanced physical downlink control cannel EPREE Energy per resource element EPS Evolved Packet System EREG extended REG, extended resource element groups ETSI European Telecommunications Standards Institute ETWS Earthquake and Tsunami Warning System eUICC embedded UICC, embedded Universal Integrated Circuit Card E-UTRA, (Evolved UTRA); developed UTRAN E-UTRA, N (Evolved UTRAN); developed UTRAN EV2X (Enhanced V2X); improved V2X F1AP (F1 Application Protocol S1 application protocol F1-C (F1 Control plane interface); F1 control plane interface F1-U (F1 User plane interface); F1 user level interface FACCH Fast Associated Control CHannel FACCH / F Fast Associated Control Channel / full rate FACCH / H Fast Associated Control Channel / Half Rate SUBJECT (Forward Access Channel); Forward access channel FAUSCH Fast uplink signaling channel FB (Functional Block); Functional block FBI (Feedback information); Feedback information FCC Federal Communications Commission FCCH (Frequency Correction Channel); Frequency correction channel FDD (Frequency Division Duplex); Frequency duplex FDM Frequency division multiplex FDMA Frequency Division Multiple Access FE (Front-end); Front end FEC (Forward Error Correction); Forward error correction FFS (For Further Study); for further investigation FFT S Fast Fourier transform feLAA further improved Licensed Assisted Access, further improved LAA FN (Frame Number); Frame number FPGA Field programmable gate array FR (F requency range); Frequency range GR (GERAN Radio Network Temporary Identity); GERAN cell radio network system identity N porärTI GER AN GSM EDGE RAN, GSM EDGE Radio Access Network GGS N (Gateway GPRS Support Node); Gateway GPRS support node GLO tionss NASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Global Navigation Satellite System) gNB (Next Generation NodeB); Next generation NodeB gNB- CU gNB-centralized unit, Next Generation NodeB centralized unit gNB- DU gNB-distributed unit, Next Generation NodeB distributed unit GNSS Global navigation satellite system GPRS General Packet Radio Service GSM Global System for Mobile Communications, Groupe Special Mobile GTP (GPRS Tunneling Protocol); GPS tunneling log GTP- U GPRS tunneling protocol for the user level GTS Go To Sleep Signal (based on WUS) GUM MEI Globally Unique MME Identifier GOOD Globally unique temporary UE identity HARQ Hybrid ARQ, Hybrid Automatic Repeat Request HANDO (Handover); handing over HFN (HyperFrame Number); Hyper frame number HHO (Hard handover); hard handover HLR (Home Location Register); Home Location Register HN (Home Network); Home network HO (Handover); handing over HPLMN Home Public Land Mobile Network HSDPA High speed downlink packet access HSN (Hopping Sequence Number); Hopping sequence number HSPA High speed packet access HSS Home Subscriber Server HSUPA High speed uplink packet access HTTP Hyner Text Transfer Protocol HTTPS Hyper Text Transfer Protocol Secure (https is http / 1.1 over SSL, i.e. port 443) I block (Information block); Information block ICCID (Integrated Circuit Card Identification); Integrated circuit card identification IAB Integrated access and backhaul ICIC (Inter-Cell Interference Coordination); Inter-cell interference coordination ID Identity, identifier IDFT Inverse Discrete Fourier Transform IE Information element IBE (In-band emission); In-band emission IEEE Institute of Electrical and Electronic Engineers IEI Information element identifier IEIDL Information Element Identifier Data Length IETF Initernet Engineering Task Force IF Infrastructure IN THE- Interference measurement, intermodulation, IP multimedia IMC (IMS Credentials); IMS credentials IMEI In iternational identifier for mobile devices IMGI In international mobile group identity IMPI IP Multimedia private identity IMPU IP Multimedia PUblic identity IMS IP Multimedia subsystem IMSI Initernational mobile subscriber identity IoT Internet of Things; (Internet of Things) IP Internet Protocol Ipsec (IP Security, Internet Protocol Security); IP security, internet protocol security IP-CAN (IP Connectivity Access Network); IP connectivity access network IP-M IP multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol version 6 IR Infrared IS In Sync IRP (Integration Reference Point); Integration reference point ISDN Integrated Services Digital Network ISIM (IM Services Identity Module); IM services identity module ISO I international organization for standardization ISP Internet Service Provider); Internet service provider IMF (Interworking function); Transition function I-WL AN (Interworking WLAN); Transitional WLAN Convolutional code length restriction, USIM individual key kB Kilobytes (1000 bytes) kbps Kilobits per second Kc (Ciphering key); Encryption key Ki tification (Individual subscriber) Individual subscription (authentication key) Authentication key KPI Key performance indicator KQI Key Quality Indicator KSI (Key Set Identifier); Key phrase identifier ksps Kilo symbols per second KVM Kernel virtual machine L1 Layer 1 (physical layer) L1-R SRP Received power of the layer 1 reference signal L2 Layer 2 (Data Link Layer) L3 Layer 3 (Network Layer) LAA (Licensed Assisted Access); licensed assisted access LAN (Local Area Network); local network LBT Listen Before Talk LCM (LifeCycle Management); Lifecycle management LCR Low Chip Rate low chip rate LCS (Location Services); Location services LCID Logical channel ID LI (Layer Indicator); Layer indicator LLC Logical Link Control, Low Layer Compatibility LPLM N Local PLMN LPP (LTE Positioning Protocol); LTE positioning protocol LSB (Least Significant Bit); least significant bit LTE Long Term Evolution LWA (LTE-WLAN aggregation); LTE WiFi aggregation LWIP LTE / WLAN radio level integration with IPsec tunnel LTE L ong term evolution M2M (Machine-to-machine); Machine-to-machine MAC edium Access Control (context of protocol layering) MAC Message authentication code (security / encryption context) MAC-A T WG3-MAC, which is used for authentication and key agreement (TSG context) MAC-IMAC Context) used for the data integrity of signaling messages (TSG T WG3 MANO Management and orchestration MBMS Multimedia Broadcast and Multicast Service MBSFN Multimedia broadcast multicast service single frequency network MCC Mobile Country Code MCG (M aster Cell Group); Master (parent) cell group MCOT Maximum channel occupancy time MCS (M modulation and coding scheme); Modulation and coding scheme MDAF M Management data analytics function MDAS M management data analysis service MDT (Minimization of Drive Tests); Minimization of drive tests ME M obile equipment; (Mobile equipment) MeNB (master eNB); Master (higher-level) eNB MER (Message Error Ratio); Message error rate MGL (Measurement Gap Length); Measuring gap length MGRP Measurement gap repetition period MIB Masster Information Block, Management Information Base MIMO Multiple input multiple output MLC (Mobile Location Center); mobile location center MM (M); Mobility management MME Mobility Management Mobility Management Entity MN (Master node); Master (parent) node MNO Mobile network operator MnS Management service MO Measurement object, mobile originated MPBCH MTC Physical Broadcast CHannel MPDCC H MTC Physical Downlink Control CHannel MPDSC H MTC Physical Downlink Shared CHannel MPRAC H MTC Physical Random Access CHannel MPUSC H MTC Physical Uplink Shared Channel MPLS MultiProtocol Label Switching MS (Mobile Station); Mobile station MSB (Most Significant Bit); most significant bit MSC (Mobile Switching Center); Mobile switching center MSI Minimum system information, MCH scheduling information MSID (Mobile Station Identifier); Mobile station identifier MSIN Mobile Station Identification Number MSISDN Mobile subscriber ISDN number MT obile terminated, mobile termination MTC Machine-type communication mMTC massive MTC, massive machine-type communications MU-M IMO (Multi User MIMO); Multiple-user MIMO MWUS MTC wake-up signal, MTC WUS NACK (Negative Acknowledgment); negative confirmation NAI Network Access Identifier); Network access identifier NAS N on-access stratum, non-access layer NCT N network connection topology NC-JT Inconsistent joint transmission NEC Network capability exposure NE-DC NR-E-UTRA Dual connectivity NEF N network exposure function NF Network Function); Network function NFP (Network Forwarding Path); Network forwarding path NPPD Network Forwarding Path Descriptor NFV Virtualization of network functions NFVI NFV infrastructure NFVO NFV orchestrator NG (Next Generation, Next Gen); Next Generation NGEN-DC NG-RAN E-UTRA-NR Dual connectivity NM (Network Manager); Network manager NMS (Network Management System); Network management system N-PoP (Network Point of Presence); Network point of presence NMIB, N-MIB (Narrowband MIB); Narrowband MIB NPBC H Narrowband Physical Broadcast CHannel NPDC CH Narrowband Physical Downlink Control CHannel NPDS CH Narrowband Physical Downlink Shared CHannel NPRA CH Narrowband Physical Random Access CHannel NPUS CH Narrowband Physical Uplink Shared CHannel NPSS Narrow band primary sync signal NSSS Narrow band secondary synchronization signal NO New Radio, (Neighbor Relation); Neighbor relationship NRF (NF Repository Function); NF repository function NRS Narrowband reference signal NS (Network Service); Network service NSA Non-standalone operation NSD (Network Service Descriptor); Network Service Descriptor NSR (Network Service Record); Network Service Records NSSAI Network slice selection guide information S-NNSAI (Single-NSSAI); Single NSSAI NSSF Network slice selection function NW (Network); network NWUS (Narrowband wake-up signal, Narrowband WUS); Narrowband wake-up signal, and-WUS NZP N on-zero power OAM Operation, administration and maintenance O&M (Operation and Maintenance); Operation and maintenance ODU2 Optical channel data unit - type 2 OFDM (Orthogonal Frequency Division Multiplexing); orthogonal frequency division multiplexing OFD MA plexzugr (Orthogonal Frequency Division Multiple Access); Orthogonal frequency multiplex OOB (Out-of-band); out of band OOS Out of sync OPEX (Operating Expense); Business expenses OSI (Other System Information); other system information OSS (Operation Support System); Operation support system OTA (over-the-air); Above-the-air PAPR Peak-to-average power ratio PAR (Peak to Average Ratio); Tip-to-middle ratio PBCH (Physical Broadcast Channel); physical broadcast channel Pc Power Control, Personal Computer PCC Primary component carrier, primary CC PCell (Primary Cell); primary cell PCI Physical cell ID, physical cell identity PCEF Policy and Charging Enforcement Function PCF (Poliev Control FunctionV 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); 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); Log data unit PEI (Permanent Equipment Identifiers); permanent equipment identifier PFD (Packet Flow Description); Packet flow description P-GW PDN gateway PHICH channel (Physical hybrid-ARQ indicator channel); physical hybrid ARQ indicator PHY Physical layer PLMN Public land cellular network pin code (Personal Identification Number); personal identification number PM (Performance Measurement); Performance measurement PMI (Precoding Matrix Indicator); Precoding matrix indicator PNF (Physical Network Function); physical network function PNFD Physical network function descriptor PNFR Physical Network Function Record POC PTT over cellular PP, PTP (Point-to-point); Point-to-point PPP (Point-to-Point Protocol); Point-to-point protocol SPEECH (Physical RACH); physical RACH PRB (Physical resource block); physical resource block PRG Physical resource block group ProSe Proximity Services, Proximity-Based Service PRS Positioning reference signal PRR (Packet Reception Radio); Packet receiving radio device PS (Packet Services); Parcel services PSBCH Sidelink physical broadcast channel PSDCH Physical sidelink downlink channel PSCCH Physical sidelink control channel PSFCH Physical sidelink return channel PSSCH Physical sidelink shared channel PSCell (Primary Scell); primary SCell PSS Primary synchronization signal PSTN Public Switched Telephone Network PT-RS Phase tracking reference signal PTT Push to talk; (Press to speak) PUCCH Physical uplink control channel PUSCH (Physical Sidelink Shared Channel); physical uplink - shared channel QAM (Quadrature Amplitude Modulation); Quadrature amplitude modulation QCI (QoS class of identifier); QoS class of identifier QCL (Quasi co-location); Quasi-co-location QFI (QoS Flow ID, QoS Flow Identifier); QoS flow ID, QoS flow identifier QoS Quality of Service QPSK Quadrature phase shift keying (quaternary) QZSS (Quasi-Zenith Satellite System); Quasi-Zenith satellite system RA-RNTI (Random Access RNTI); Random Access RNTI RAB Radio Access Bearer, Random Access Burst RACH (Random Access Channel); Random access channel RADIUS Remote authentication dial-in user service RAN (Radio Access Network); Radio access network EDGE RANDom number (used for authentication) RAR (Random Access Response); Random Access Response ADVICE (Radio Access Technology); Radio access technology ROUGH (Routing Area Update); Routing area update RB (Resource block, Radio Bearer); Resource block, radio bearer RBG (Resource block group); Resource block group REG (Resource Element Group); Resource element group Rel (Release); release REQ (REQuest); requirement RF (Radio frequency); Radio frequency RI (Rank Indicator) RIV (Resource indicator value); Resource indicator value RL (Radio Link); Radiolink RLC Radio Link Control, Radio Link Control Layer RLC AM RLC Acknowledged mode RLC UM RLC Unacknowledged Mode RLF (Radio Link Failure); Radio link failure RLM (Radio Link Monitoring); Radio link surveillance RLM-RS (Reference Signal for RLM); Reference signal for RLM RM (Registration Management); Registration management RMC Reference measuring channel RMSI MSI Remaining, Minimum System Information Remaining RN (Relay Node); Relay node RNC (Radio Network Controller); Radio network control 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); Radio resource management RS (Reference signal); Reference signal RSRP (Reference Signal Received Power); Reference signal received power RSRQ (Reference Signal Received Quality); Reference signal reception quality RSSI (Received Signal Strength Indicator); Received signal strength indicator RSU (Road Side Unit); Roadside unit RSTD (Reference Signal Time difference); Reference signal time difference RTP Real Time Protocol RTS Ready-to-send RTT (Round Trip Time); Round trip time Rx (Reception, Receiving, Receiver); Receiving, receiving, receiver S1AP (S1 Application Protocol), S1 application protocol S1-MME S1 for the control level S1-U S1 for the user level S-GW Serving gateway S-RNTI identity (SRNC Radio Network Temporary Identity); SRNC radio network - temporary S-TMSI ident (SAE Temporary Mobile Station Identifier); SAE temporary mobile stationer) SA (Standalone operation mode); independent operating mode SAE (System Architecture Evolution); System architecture evolution SAP (Service Access Point); Service access point SAPD (Service Access Point Descriptor); Service Access Point Descriptor SAPI (Service Access Point Identifier); Service Access Point Identifier SCC (Secondary Component Carrier, Secondary CC); secondary component carrier, secondary CC SCell (Secondary Cell); secondary cell SC-FDMA (Single Carrier Frequency Division Multiple Access); Single carrier frequency division multiplex access SCG (Secondary Cell Group); secondary group of cells SCM (Security Context Management); Security context management SCS (Subcarrier Spacing); Partial Carrier Spacing SCTP Stream Control Transmission Protocol SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer Service Data Service Data Protocol SDL (Adaptation Protocol, Adaptation Layer Supplementary Downlink), supplementary downlink SDNF (Structured Data Storage Network Function); structured data storage network function SDP Session Description Protocol SDSF (Structured Data Storage Function); structured data storage function SDU (Service Data Unit); Service data unit SEAF (Security Anchor Function); Safety anchor function SeNB (secondary eNB); secondary eNB SEPP Security Edge Protection Proxy SFI (Slot format indication); Slot format indication SFTD (Space-Frequency Time Diversity, SFN and frame timing difference); Spatial frequency time diversity, SFN and frame timing difference SFN System frame number or single frequency network SgNB (Secondary gNB); secondary gNB SGSN Serving GPRS Support Node S-GW Serving gateway SI (System Information); System information SI-RNTI (System Information RNTI); System information-RNTI SIB (System Information Block); System information block SIM Subscriber Identity Module SIP Session Initiated Protocol SiP System-in-package SL Sidelink SLA Service level agreement SM (Session Management); Session management SMF (Session Management Function); Session management function SMS (Short Message Service); Short message service SMSF SMS function SMTC SSB based measurement timing configuration SN Secondary node, sequence number SoC (System on Chip); System-on-a-chip SON (Self-Organizing Network); self-organizing network SpCell (Special Cell); Special cell SP-CSI-RNTI (Semi-Persistent CSI RNTI); semi-persistent CSI-RNTI PLC (Semi-Persistent Scheduling); semi-persistent scheduling SQN (Sequence number); Sequence number SR (Scheduling Request); Scheduling requirement SRB (Signaling Radio Bearer); Signaling radio bearer SRS (Sounding Reference Signal); Probing reference signal SS (Synchronization Signal); Synchronization signal SSB SS block SSBRI SSB resource indicator SSC (Session and Service Continuity); Session and Service Continuity SS-RS RP synchronization signal based reference signal received power SS-RS RQ Synchronization signal-based reference signal reception quality SS-SINR Synchronization signal based on noise and interference ratio SSS Secondary synchronization signal SSSG (Search Space Set Group); Search space phrase group SSSIF (Search Space Set Indicator); Search space sentence indicator SST Slice / service types SU-MIMO (Single user MIMO); Single user MIMO SUL (Supplementary Uplink); complementary uplink TA Timing advance, tracking area TAC Tracking Area Code DAY (Timing Advance Group); Timing Advance Group DEW (Tracking Area Update); Tracking area update TB (Transport block); Transport block TBS (Transport Block Size); Transport block size TBD (To Be Defined); still to define TCI Transmission configuration display TCP Transmission communication protocol TDD (Time Division Duplex); Time duplex TDM (Time Division Multiplexing); Time division multiplexing TDMA (Time Division Multiple Access); Time division multiple access TE (Terminal Equipment); End device TEID (Tunnel End Point Identifier); Tunnel endpoint identifier TFT (Traffic Flow Template); Traffic flow template TMSI Temporary Mobile Subscriber Identity TNL Transport Network Layer TPC (Transmit Power Control), transmit power control TPMI Transmitted Precoding Matrix Indicator TR (Technical Report); technical report TRP, TR × P send / receive point TRS (Tracking Reference Signal); Tracking reference signal TRx (Transceiver); Transceiver TS Technical specifications, technical standard TTI (Transmission Time Interval); Transmission time interval Tx Transmission, sending transmitter U-RNTI (UTRAN Radio Network Temporary Identity); UTRAN radio network - temporary identity UART Universal Asynchronous Receiver and Transmitter UCI (Uplink Control Information); Uplink control information UE (User Equipment); User terminal UDM Unified data management UDP User Datagram Protocol UDR Unified data repository UDSF Unstructured data storage network function UICC Universal Integrated Circuit Card UL Uplink AROUND (Unacknowledged Mode); unconfirmed mode UML (Unified Modeling Language), unified modeling language UMTS Universal mobile telecommunication system UP (User Plane); User level UPF (User Plane Function); User level function URI Uniform Resource Identifier Url Uniform Resource Locator URLLC (Ultra-Reliable and Low Latency); ultra-reliable and low-latency USB (Universal Serial Bus); universal serial bus USIM Universal Subscriber Identity Module USS (UE-specific search space); UE-specific search area UTRA UMTS terrestrial radio access UTRAN Universal terrestrial radio access network UwPTS (Uplink Pilot Time Slot); Uplink pilot time slot V2I Vehicle-to-Infrastruction Vehicle-to-Infrastructure V2P (Vehide-to-Pedestrian); Vehicle-to-pedestrian V2V (Vehicle-to-Vehicle), vehicle-to-vehicle V2X (Vehicle-to-everything); Vehicle-to-X VIM Virtualized Infrastructure Manager VL (Virtual Link); virtual link VLAN Virtual LAN, virtual local network VM (Virtual Machine); virtual machine VNF Virtualized network function VNFFG (VNF Forwarding Graph); VNF forwarding graph VNFFGD VNF Forwarding Graph Descriptor VNFMVNF -Manager VoIP Voice-over-IP, voice transmission over the Internet protocol VPLMN Visited Public Land Mobile Network VPN (Virtual Private Network); virtual private network VRB (Virtual Resource Block); virtual resource block WiMAX Worldwide interoperability for microwave access WIRELESS INTERNET ACCESS (Wireless Local Area Network); wireless local area network WMAN Wireless Metropolitan Area Network WPAN Wireless Personal Area Network X2-C (X2 control plane); X2 control level X2-U (X2 user plane); X2 users XML eXtensible Markup Language XRES (EXpected user RESponse); expected user response XOR (eXclusive OR); exclusive OR ZC Zadoff-Chu ZP Zero power; (Zero power)

terminology

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The term "service function (SF)", as used here, refers to a function that specifically represents a network service function that is responsible for a specific handling of received packets that are supported by the normal standard functions of an IP router ( e.g. IP forwarding and routing functions) on the network path between a source host and a destination host deviates from, is part of, or includes them.

As used herein, the term "service function chain (SF chain)" refers to a chain that defines an ordered set of abstract service functions and ordering constraints that are applied to packets and / or frames and / or flows selected as a result of a classification and / or guideline, or is part of or includes such a chain.

The term “Service Function Chaining (SFC)”, as used here, refers to a mechanism for setting up service function chains and for forwarding packets / frames / flows through them, is part of them or contains them.

As used herein, the term "service function path (SFP)" refers to a path that defines an ordered set of specific instantiations of service functions that packets and / or frames and / or flows within a particular service function chain must or are to visit Part of or includes such a path. (Note: A service function path is determined among the relevant service function paths within a particular service function chain, whereby the capacity and QoS requirements of the service functions and their links are met. There is typically a 1: n relationship between a service function chain and a service function chain. Function path.).

The term "service routing" as used here refers to a uniform service that supports platforms built on DSN, is part of it, or includes it. She delivers that Mechanisms for the registration, publication, detection, triggering and access to services as well as advanced functions for optimizing the service delivery.
As used herein, the term “user plane” refers to a set of traffic routing components through which traffic flows, is part of, or includes.

The term “circuit” as used herein refers to hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated or group) and / or memory (shared, dedicated or group), an application-specific integrated Circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD) , a structured ASIC or a programmable SoC), digital signal processors (DSPs), etc. configured to provide the functionality described. In some embodiments, the circuit can execute one or more software or firmware programs to provide at least some of the functions described. The term “circuit” can also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code can be referred to as a particular type of circuit.

As used herein, the term “processor circuit” refers to a circuit that is or is capable of sequentially and automatically executing a series of arithmetic or logical operations or recording, storing and / or transmitting digital data Part of it. The processing circuitry may include one or more processor cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuit" can refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core Processor and / or any other device capable of executing computer-executable instructions, e.g. B. program code, software modules and / or functional processes to execute or otherwise operate. The processing circuitry may include other hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators can e.g. B. Computer Vision (CV) and / or Deep Learning (DL) accelerators. The terms “application circuits” and / or “baseband circuits” can be viewed as synonymous with “processor circuits” and can be designated as such

As used herein, the term “interface circuit” refers to a circuit that enables the exchange of information between two or more components or devices, or is part of or comprises such a circuit. The term "interface circuit" can refer to one or more hardware interfaces, e.g. B. on buses, I / O interfaces, interfaces of peripheral components, network interface cards and / or the like.

As used herein, the term “user device” or “UE” refers to a device with radio communication capabilities and can describe a remote user of network resources on a communication network. The term "user device" or "UE" can be used as a synonym for client, mobile device, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable radio , reconfigurable mobile device, etc., and can be referred to as such. In addition, the term “user device” or “UE” can include any type of wireless / wired device or any computing device with a wireless communication interface.

As used herein, “network element” refers to physical or virtualized devices and / or infrastructure used to provide wired or wireless communication network services. The term "network element" can be used as a synonym for and / or as a designation for a networked computer, network 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 can be considered.

As used herein, the term “computer system” refers to any type of interconnected electronic device, computing device, or component thereof. In addition, the term “computer system” and / or “system” can refer to various components of a computer that are communicatively coupled with each other. In addition, the term “computer system” and / or “system” can refer to a plurality of computing devices and / or a plurality of computer systems that are communicatively coupled to one another and configured to share computer and / or network resources.

The term “device”, “computing device” or the like, as used herein, refers to a computing device or computer system with program code (e.g. software or firmware) that is specially designed to provide a particular computer resource. A “virtual application” is a virtual machine image that is implemented by a hypervisor-equipped device that virtualizes or emulates a computer application or is otherwise dedicated to providing a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a particular device, such as a computer. B. Computing devices, mechanical devices, storage space, processor / CPU time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network sockets, channel / Link allocation, throughput, memory usage, network, database and applications, workload units and / or the like. A “hardware resource” can refer to computing, storage and / or network resources provided by one or more physical hardware elements. A “virtualized resource” can refer to computing, storage, and / or network resources provided by a virtualization infrastructure for an application, device, system, and so on. The term “network resource” or “communication resource” may refer to resources that computing devices / systems can access over a communication network. The term “system resources” can refer to any type of shared unit for the provision of services and can include computer and / or network resources. System resources can be thought of as a set of coherent functions, network data objects, or services accessible through a server, such system resources residing on a single host or multiple hosts and being uniquely identifiable.

The term “channel” as used here refers to any tangible or intangible transmission medium that is used to transmit data or a data stream. The term "channel" can be synonymous and / or synonymous with "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "connection", "data connection", "carrier", " Radio Frequency Carrier ”and / or any other similar term used to designate a path or medium over which data is transmitted. In addition, as used herein, the term “link” refers to a connection between two devices over a RAT for the purpose of sending and receiving information.

The terms “instantiating”, “instantiating” and the like used here refer to the creation of an instance. An “instance” also refers to a specific occurrence of an object, e.g. B. can occur when executing program code.

The terms “coupled”, “communicatively coupled” along with derivatives thereof are used herein. The term “coupled” can mean that two or more elements are in direct or indirect physical or electrical contact with one another, can mean that two or more elements contact one another indirectly, but continue to work or interact with one another, and / or can mean that one or more other elements are coupled or connected between the elements that are coupled together. The term “directly coupled” can mean that two or more elements are in direct contact with one another. The term “communicatively coupled” can mean that two or more elements can be in contact with one another via a means of communication, e.g. B. via a wire or other connection link, via a wireless communication channel or a wireless connection and / or the like.

The term “information element” refers to a structure element that contains one or more fields. The term “field” refers to the individual content of an information element or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement time configuration that is configured with SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS / PBCH block. The term "primary cell" refers to the MCG cell operating on the primary frequency on which the UE is either performing the initial connection establishment procedure or initiating the connection establishment procedure.

The term “primary SCG cell” refers to the SCG cell in which the UE carries out random access when it carries out the “Reconfiguration with Sync” procedure for DC operation.

The term “secondary cell” refers to a cell that provides additional radio resources over a special cell for a UE configured with CA.

The term “secondary cell group” refers to the subset of serving cells that includes the PSCell and zero or more secondary cells for a DC configured UE.

The term “serving cell” refers to the primary cell for a UE in RRC_CONNEC-TED not configured with CA / DC there is only one serving cell, which consists of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells that includes the special cell (s) and all secondary cells for a UE in RRC_CONNECTED configured with CA /.

The term “special cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise the term “special cell” refers to the Pcell.

Claims (20)

Component for a mobile communication network, consisting of one or more interfaces configured to communicate with a third party from an external data network; and Processing circuitry configured to control the one or more interfaces and: Third party access, e.g. A third party application to provide a service function chain, SF chain, policy for the use of the SF chain deployed in the mobile communications network. The component after Claim 1 wherein the processing circuitry is further configured to enable service function chaining, SFC, by controlling and / or managing the SF chain based on the SF chain policy; and forwards data through the SF chain. The component after Claim 1 or 2 , wherein the SF chain comprises at least one service function from the group of: network address translation, NAT; IP tunnel endpoints, packet classifiers; Deep packet inspection, DPI; legal inspection, LI; Transmission communication protocol, TCP, proxies; Load balancer; Firewall functions; Transcoders; Video optimizer; Functions for recognizing and controlling applications; Anti-malware; Key performance indicators, KPI, monitoring; Distributed Denial of Service (DDoS) protection; and parental control. The component after one of the Claims 2 or 3 , whereby the SFC is used in a user level, UP, and / or a control level, CP, of the component through a service function chaining function, SFCF. The component after one of the Claims 4 , with the SFCF enabled and located in a user level function, UPF, of the component. The component after Claim 5 wherein the processing circuitry is further configured to allow an application server, AS, of the third party vendor to access the SFCF located in the UPF using N6 reference points. The component after one of the Claims 4 until 6th , where the SFCF is a stand-alone network function that is located between a UPF of the component and an AS of the third-party provider. The component after one of the Claims 4 until 7th wherein the processing circuitry is further configured to provide access to the SFCF for a third party AS using N6, N6, N6e, and / or N9 extended reference points. The component after one of the Claims 4 until 8th wherein the processing circuitry is further configured to assign the UP for a protocol data unit, PDU, session using a session management function, SMF. The component after Claim 4 until 9 , with the SFCF enabled and located in the UPF and a control plane function, CPF, of the component. The component after Claim 10 , whereby the SFCF in the UP cooperates with the UPF via a reference point Nx in order to control the traffic in the UPF and / or the service SFCF in the CP contains the SFC. The component after Claim 10 or 11 wherein the processing circuitry is further configured to configure: the SMF for traffic requiring services to concatenate services; the UPF to route traffic to the SFCF in the UP to pass through a configured SFP; and the SFCF to route traffic back to the UPF. The component after one of the Claims 10 until 12th wherein the SFCF comprises a variety of network functions, with a first SFCF enabled and located in the UPF and a second SFCF enabled and located in the CPF. The component after Claim 10 until 14th , wherein the PDU session contains a traffic flow that is transported over identical or different service function paths, SFPs. The component after Claim 14 wherein the processing circuitry is further configured to configure a service function path, SFP, the SFC based on an SFC policy for the traffic flow of the PDU session using the SMF and / or the SFCF. The component after one of the Claims 9 until 15th wherein the processing circuitry is further configured to receive information for assignment / configuration using the SMF from a Unified Data Repository, UDR, the mobile communications network that stores the service subscription of a user equipment, UE, via a Policy Control Function, PCF, of the mobile communication network which stores the UE service policy. The component of any preceding claim, wherein the processing circuitry is further configured to add a PSA to a local access near the RAN node, thereby enabling edge computing. The component of any preceding claim, wherein the processing circuitry is further configured to receive an SFC service request from an AF of an AS via a network exposure function (NEF). A method for a mobile communication network, comprising generating an SCF in the mobile communication network; and providing access to the third party, e.g. B. a third party application to provide a service function chain, SF chain, guideline for the use of the SF chain used in the mobile communications network. Computer program with a program code for carrying out the method according to Claim 19 when the computer program is executed on a computer, a processor or a programmable hardware component.

Images