Application-centric processing on servers using mobile network connectivity

Abstract

Systems, methods, apparatuses, and computer program products for computer program products for application-centric processing on servers using mobile network connectivity (e.g., 5G system (5GS) connectivity, 6G 5 system (6GS) connectivity, and so forth). A method may include getting information associated with data network terminations. The method may also include establishing, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. The method may further include ensuring that traffic related with edge application servers is sent on the tunnels based on a given quality of service requirement. In addition, the method may include ensuring a given quality of service requirement and / or packet classification information to the traffic.

Description

FIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR) access technology, or 5G beyond, or sixth generation (6G) access technology, or other communications systems. For example, certain example embodiments may relate to apparatuses, systems, and / or methods for application-centric processing on servers using mobile network connectivity (e.g., 5G system (5GS) connectivity, 6G system (6GS) connectivity, and so forth). BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, fifth generation (5G) radio access technology or new radio (NR) access technology and / or sixth generation (6G) radio access technology. Fifth generation (5G) and sixth generation (6G) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G and 6G network technology is mostly based on new radio (NR) technology, but the 5G / 6G (or NG) network can also build on E-UTRAN radio. It is estimated that NR may provide bitrates on the order of 10-20 Gbit / s or higher, and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (loT). SUMMARY:

[0003] Some example embodiments may be directed to a method. The method may include getting information associated with data network terminations. The method may also include establishing, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. The method may further include ensuring that traffic related with edge application servers is sent on the tunnels. In addition, the method may include ensuring a given quality of service requirement and / or packet classification information to the traffic.

[0004] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions that, when executed by a processor, cause the apparatus at least to get information associated with data network terminations. The apparatus may also be caused to establish, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. The apparatus may further be caused to ensure that traffic related with edge application servers is sent on the tunnels. In addition, the apparatus may be caused to ensure a given quality of service requirement and / or packet classification information to the traffic.

[0005] Other example embodiments may be directed to an apparatus. The apparatus may include means for getting information associated with data network terminations. The apparatus may also include means for establishing, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. The apparatus may further include means for ensuring that traffic related with edge application servers is sent on the tunnels. In addition, the apparatus may include means for ensuring a given quality of service requirement and / or packet classification information to the traffic.

[0006] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include getting information associated with data network terminations. The method may also include establishing, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. The method may further include ensuring that traffic related with edge application servers is sent on the tunnels. In addition, the method may include ensuring a given quality of service requirement and / or packet classification information to the traffic.

[0007] Other example embodiments may be directed to a computer program product that performs a method. The method may include getting information associated with data network terminations. The method may also include establishing, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. The method may further include ensuring that traffic related with edge application servers is sent on these tunnels. In addition, the method may include ensuring a given quality of service requirement and / or packet classification information to the traffic.

[0008] Other example embodiments may be directed to an apparatus that may include circuitry configured to get information associated with data network terminations. The apparatus may also include circuitry configured to establish, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. The apparatus may further include circuitry configured to ensure that traffic related with edge application servers is sent on these tunnels. In addition, the apparatus may include circuitry configured to ensure a given quality of service requirement and / or packet classification information to the traffic.

[0009] Further example embodiments may be directed to a method. The method may include providing, to a network element, information associated with data network terminations. According to certain example embodiments, the information triggers establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of data network terminations.

[0010] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus at least to provide, to a network element, information associated with data network terminations. According to certain example embodiments, the information triggers establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of data network terminations.

[0011] Other example embodiments may be directed to an apparatus. The apparatus may include means for providing, to a network element, information associated with data network terminations. According to certain example embodiments, the information triggers establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of data network terminations.

[0012] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include providing, to a network element, information associated with data network terminations. According to certain example embodiments, the information triggers establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of data network terminations.

[0013] Other example embodiments may be directed to a computer program product that performs a method. The method may include providing, to a network element, information associated with data network terminations. According to certain example embodiments, the information triggers establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of data network terminations.

[0014] Other example embodiments may be directed to an apparatus that may include circuitry configured to provide, to a network element, information associated with data network terminations. According to certain example embodiments, the information triggers establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of data network terminations. BRIEF DESCRIPTION OF THE DRAWINGS:

[0015] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0016] FIG. 1 illustrates an example of network data flow connections.

[0017] FIG. 2 illustrates an example of network data flow connections using two tunnels, according to certain example embodiments.

[0018] FIG. 3 illustrates another example of network data flow connections using two tunnels, according to certain example embodiments.

[0019] FIG. 4A illustrates an example signal diagram, according to certain example embodiments.

[0020] FIG. 4B illustrates the signal diagram continued from FIG. 4A, according to certain example embodiments.

[0021] FIG. 5 illustrates an example of another signal diagram, according to certain example embodiments.

[0022] FIG. 6 illustrates an example of a further signal diagram, according to certain example embodiments.

[0023] FIG. 7 illustrates an example flow diagram of a method, according to certain example embodiments.

[0024] FIG. 8 illustrates an example flow diagram of another method, according to certain example embodiments.

[0025] FIG. 9 illustrates a set of apparatuses, according to certain example embodiments. DETAILED DESCRIPTION:

[0026] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for application-centric processing on servers using mobile network connectivity (e.g., 5G system (5GS) connectivity, 6G system (6GS) connectivity, and so forth). For instance, certain example embodiments may enable application-centric processing on edge and central application servers using mobile network connectivity (e.g., 5G system (5GS) connectivity, 6G system (6GS) connectivity, and so forth).

[0027] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “an example embodiment,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “an example embodiment,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. Further, the terms “base station”, “cell”, “node”, “gNB”, “network” or other similar language throughout this specification may be used interchangeably.

[0028] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0029] Due to requirements of performance, data privacy, etc., a complex computing task may be split into several smaller compute operations, where each of the operations may be executed at a different compute node in a mobile network. Executing one or several compute operation(s) within a mobile network operator domain helps exploit the edge-cloud continuum (e.g., the availability of specific computing capabilities in different parts of the network including, for example, far edge, edge, aggregation, and central cloud).

[0030] In one example, a group of compute operations may include a video surveillance application, which is split into two compute operations deployed first on a local (part of) data network (L-DN), and second on a central (part of) data network (C-DN), or on a second local (part of) data network (L-DN). It has to be understood that L-DN and C-DN as used in this document do not always mean different data networks, but may refer to different subsets of the same data network. A user equipment (UE) deployed in the monitored area is only responsible for capturing video data. The data is sent to a L-DN on which a local edge application server (L-EAS) is deployed that is capable of detecting anomalies as the first compute operation of the video surveillance application. Once an anomaly is detected by the L-EAS, the information about the anomaly is further forwarded to a central edge application server (C-EAS) for alarming located in the C-DN, or to a second L-EAS for alarming located in the second L-DN, as the second compute operation of the video surveillance application.

[0031] Certain activities related to 6G network design may consider enhancing the cooperation of edge and central application servers. In the context of integration of network and computing (INC), optimal application instances hosted in local and central servers can be selected. Data can be computed on several nodes in a parallel or in a sequential manner (e.g., distributed / ubiquitous computing). As such, edge servers may not be the destination of data traffic. The packet data may first be computed on one or several local server(s) with specific software / hardware support and then the mobile network user plane (UP) can forward the packets, along with performing other UP functions (e.g., potential lawful interception, QoS enforcement, etc.), to the central server for further processing.

[0032] EASs may be local or central hosted by data centers identified by a data network access identifier (DNAI). A DNAI may correspond to an identifier of a UP access to one or more DN(s) where applications are deployed. An Application Function may be in charge of the management of EAS deployment information (EDI), and to provide EDI to a network exposure function (NEF) that is to ensure that the relevant session management function(s) (SMF) receive is information. This EDI may be stored in a unified data repository (UDR). Additionally, the EDI may indicate how edge services are deployed in each local part of the DN.

[0033] FIG. 1 illustrates an example of network data flow connections. In particular, FIG. 1 illustrates N6 and N9 connections defined by specifications of the 3rd Generation Partnership Project (3GPP). As illustrated in FIG. 1, traffic can be steered via an intermediate user plane function (I-UPF) and local protocol data unit (PDU) session anchor (L-PSA) user plane function (UPF) (local PDU session anchor = UPF interfacing the DN) to a L-DN on which a L-EAS is hosted. .

[0034] As illustrated in FIG. 1, traffic steering may involve N6-data forwarding (dashed line). In N6-data forwarding, the L-PSA UPF acts as a PSA UPF to the L-DN so that traffic data can be routed to the L-EAS deployed on the L-DN. For some edge computing use case scenarios, although application servers are deployed in the local N6-LAN, centrally deployed application server(s) may still be required for other processing. However, after data has been computed by the L-EAS, the data cannot be further forwarded to the C-DN via the PSA UPF if there is no connectivity defined from the L-DN to the C-DN via the UP (dashed-dotted line).

[0035] As further illustrated in FIG. 1, traffic steering may involve N9-data forwarded (non-dotted line). Here, the I-UPF forms a UPF chain together with the C-PSA UPF so that traffic data can be routed to the C-DN. However, data cannot be first directed to the L-EAS for computing and then forwarded to the C-DN. Traffic not related with

[0036] In view of the issues exhibited in N6 and N9-data forwarding, a possible solution may involve traffic routing via a public network (dashed-dotted line) (e.g., Internet). However, even with such a solution, connectivity between the L-DN and the C-DN may not be possible when the L-DN (and I-UPF + L-PSA UPF) are very decentralized (i.e., located in a far edge location such as at a gNB) due to the high potential cost to manage a large number of N6 connections. Furthermore, public networks are out of the network operator’s control, and UPF functions cannot be applied on this path (e.g., quality of service (QoS) enforcement).

[0037] From FIG. 1, another issue may arise in trying to ensure connectivity between the L-EAS located on two L-DNs such as, for example, when these L-EASs need to exchange contexts about a UE that has changed L-EAS (e.g., due to mobility a target L-EAS has taken over the application for a UE that has moved from a source RAN to a target RAN).

[0038] In view of the issues and challenges that currently exist, certain example embodiments may define ways for network nodes to be able to connect the L-DN and the C-DN, or to connect two L-DNs via a UP. Certain example embodiments may also enable traffic forwarding between L-EAS and C-EAS in the UP or to enable traffic forwarding between two L-EASs located on different data centers. As such, certain example embodiments may provide a way to steer UL traffic to a L-DN allowing an L-EAS in the L-DN to process the traffic before sending this traffic to a C-EAS in the C-DN, or to another L-EAS in another L-DN. Other example embodiments may provide a way to steer DL traffic from a C-EAS in the C-DN or from a L-EAS in an L-DN to be first handled by an L-EAS in the L-DN (for further local processing of the traffic), and then to be finally forwarded to the relevant UE.

[0039] The solution of certain example embodiments may be applicable to deployment where there is either no direct connectivity between L-DN and C-DN and / or between two / more L-DNs. Alternatively, in some example embodiments, it may be preferable to steer the traffic between the L-DN and the C-DN and / or two / more L-DNs via 5GC due to an application’s qualify of service (QoS) requirements. For instance, there may be no direct connectivity between the L-DN and the C-DN when the L-EAS / L-DN are deployed collocated with (many) RAN and, thus, there may be many decentralized L-DN. In such a case, it may be costly to support IP connectivity to the C-DN for the multiple L-DNs.

[0040] In certain example embodiments, traffic may be steered to be controlled by an application function (AF) that manages edge computing. Thus, certain example embodiments may also provide solutions on how an AF can control the 5GS to allow traffic to be forwarded by the 5GS UP between a C-DN and a L-DN, or between two L-DNs.

[0041] FIG. 2 illustrates an example of network data flow connections, according to certain example embodiments, and FIG. 3 illustrates another example of network data flow connections, according to certain example embodiments. In particular, FIG. 2 illustrates use of two tunnels including, for example, a UE tunnel (left side) and C-DN tunnel (right side). The tunnels may be used to connect the L-DN and the C-DN via the UP. Although one L-PSA UPF is shown in the configuration of FIG. 2, in other example embodiments, additional L-PSA UPFs may be utilized, and the data flows of the UE tunnel and the C-DN tunnel do not have to be directed to the same L-PSA UPF. Similarly, FIG. 3 illustrates use of two tunnels including, for example, a UE tunnel (left) and an LL-DN tunnel (center). These tunnels may be used to connect two L-DNs via a UP. As illustrated in FIGs. 2 and 3, different data paths may be established. For instance, a UE PDU session specific tunnel and a C-DN tunnel to the C-DN may be established to interconnect the UE and the C-EAS via the L-EAS, as illustrated in FIG. 2. Additionally, a UE PDU session specific tunnel and a LL-DN may be established to allow the UE to e.g. be served by two L-EASs, as illustrated in FIG. 3.

[0042] With the configurations illustrated in FIGs. 2 and 3, traffic forwarding may be achieved. For instance, UL / DL traffic between a C-DN and an L-DN may be forwarded via a C-DN tunnel, as illustrated in FIG. 2. Alternatively, the UL / DL traffic between two L-DNs may be forwarded via an LL-DN tunnel, as illustrated in FIG. 3.

[0043] As illustrated in FIGs. 2 and 3, the UE tunnel may be isolated from the C-DN / LL-DN tunnel. The UE tunnel (left side) may also be established between the UE and the L-PSA UPF towards the L-DN. In some example embodiments, the UE tunnel may be a PDU session, which may be established per 3GPP mechanisms. With the UE tunnel, UL traffic from the UE may be terminated at the L-DN for L-EAS processing, and the L-EAS processed DL traffic from the C-DN or from a second L-DN may continue to be steered to the relevant UE from the L-DN.

[0044] On the other hand, as illustrated in FIGs. 2 and 3, the C-DN tunnel (right side) (or respectively an LL-DN tunnel) may be established by the session management function (SMF) between the L-PSA UPF and the C-PSA UP (or respectively between 2 L-PSA UPF(s)) based on, for example, EAS deployment information (EDI) or traffic influence (TI) request information from the AF. With the C-DN / LL-DN tunnel, traffic that has been processed or generated by the L-EAS may be steered to the C-EAS in the C-DN or to a second L-EAS in the second L-DN. Additionally, the traffic from the C-DN or the second L-DN may be terminated at the L-DN for L-EAS processing.

[0045] According to certain example embodiments, the UE tunnels may be per PDU session, while the C-DN-LL-DN tunnel may be shared by all PDU sessions whose traffic requires joint handling by a L-EAS in the L-DN and either a C-EAS in the C-DN or a second L-EAS in the second L-DN. Based on operator policies, different C-DN(s) / LL-DN(s) may be used by different applications.

[0046] In some example embodiments, the L-EAS may establish a mapping relationship between traffic received on the C-DN / LL-DN tunnel and the impacted UE(s) (IP address and port) according to the application’s logic. Although only one SMF is shown in FIGs. 2 and 3, in other example embodiments, multiple SMFs within a same SMF set may use the same DN tunnel created by one SMF of the SMF set. If the SMFs are not in the same SMF set, these SMFs may build separate DN tunnels.

[0047] As further illustrated in FIGs. 2 and 3, in some example embodiments, the AF may request the 5GS to establish C-DN tunnels as well as LL-DN tunnels between pairs of L-DN(s) based on extended DNAI information with indicators in EDI (EASDF deployment information) or TI (Traffic Influence related rules). Pairs of TEIDs in L-PSA UPF and C-PSA UPF / a second L-PSA UPF may be generated to support the C-DN / LL-DN tunnel. This pair of TEIDs may be generated to establish the C-DN / LL-DN tunnel between the L-DN and the C-DN / the second L-DN. In other example embodiments, corresponding packet detection rules (PDRs) and forwarding action rules (FARs) may be communicated from the SMF to the UPFs to detect and to forward the UL and DL traffic accordingly in the C-DN / LL-DN tunnel. Moreover, packet header processing in the UP may be given. Although certain example embodiments described herein may relate to the establishment of the C-DN tunnel, similar procedures may be applicable for the establishment of the LL-DN tunnel. In some example embodiments, if the establishment of an LL-DN tunnel is required, the C-EAS / C-DN and C-PSA UPF under the C-DN tunnel establishment scenario may be replaced with the second L-EAS / L-DN and the second L-PSA UPF.

[0048] In the formation of the C-DN tunnels, the AF can initially request the 5GS to establish the C-DN tunnels (e.g., between each local DNAI and each central DNAI) between each pair of DNAI(s). For instance, a given application may have a list of DNAIs, each of which may be associated with indications of local / central DNs, connectivity together with a specific QoS requirement, traffic forwarding rules, etc. According to certain example embodiments, there may be several options for the SMF to get DNAI information. For example, one option may be through usage of EDI (EAS deployment information) via an extension of the per DNAI information currently in EDI as currently specified in 3GPP Technical Specification TS 23.548 VI8.4.0. Another option may be via an extension of the information currently in TI (Traffic Influence information corresponding to an AF request via Nnef TrafficInfluence service). In some example embodiments, the SMF (and I-SMF if necessary) may be instructed to select an L-PSA UPF and a C-PS A UPF for anchoring the L-DN and the C-DN via the EDI provided by AF to the NEF (from usage of EDI option described above) or a policy and charging control (PCC) rule from the policy control function (PCF) influenced by the AF (from usage of TI option described above). According to further example embodiments, although FIGs. 2 and 3 illustrate a termination point of the C-DN and LL-DN tunnels at a particular L-PSA UPF, the L-PSA UPF used to terminate the C-DN and LL-DN tunnels may differ from the L-PSA UPF used to terminate the UE tunnel as long as both L-PSA UPFs connect to the same local (part of) DN.

[0049] In certain example embodiments, the DNAI may include additional information such as various indicators. For instance, the DNAI may include one or more of (and in any combination): an indicator of whether the DNAI is to be considered local or central; an indicator of whether C-DN connectivity to central DNAI(s) is needed; and an indicator of whether C-DN connectivity to other local DNAI(s) is needed, routing information to reach the application instance indicated by the DNAI. In certain example embodiments, the indicator of whether C-DN connectivity to other DNAI(s) is needed may be applicable if the DNAI is to be considered as a local DNAI. In certain example embodiments, a QoS requirement and / or a packet classification information is included together with any of the indicators noted above. Such a requirement or classification information may include the traffic direction (e.g., UL and / or DL) that the requirement should be applied. The SMF may receive the information elements (IEs) as part of the EDI from the NEF, or as part of the TI. In the case of DNS query as an application, the DNS resolver and DNS authoritative server may be seen as specific types of EAS, and their information may be given for the C-DN tunnel establishment instead of L-EAS and C-EAS.

[0050] In some example embodiments, TI may be used to provide DNAI information to the SMF. The TI may include per DNAI to indicate the potential locations of applications. Such information may include one or more of (in any combination): routing information to reach the application instance indicated by the DNAI; an indicator whether the DNAI is to be considered local or central; an indicator whether C-DN connectivity to central DNAI(s) is needed; and an indicator whether C-DN connectivity to other local DNAI(s) is needed. In certain example embodiments, the indicator of whether C-DN connectivity to other DNAI(s) is needed may be applicable when the DNAI is to be considered as a local DNAI. In some example embodiments, a QoS requirement and packet classification information is included together with the any of the indicators noted above. Such a requirement or classification information may include whether the given QoS requirement applies on UL or DL traffic.

[0051] According to certain example embodiments, the AF may request to initiate the establishment of the C-DN tunnel. The AF request may also influence UPF (re)selection and (I-)SMF (re)selection, and allow routing traffic to the L-DN and C-DN identified by the DNAIs and routing information. In certain example embodiments, the PCF may obtain the AF request via NEF and unified data repository (UDR), and forward the information to the SMF via Policy and Charging Control (PCC) rules. In some example embodiments, the PCF derives the required QoS parameters of the PCC rule for the C-DN (or LL-DN) tunnel.

[0052] As previously described, FIG. 2 illustrates establishment of the C-DN tunnel to generate two TEIDs for the C-DN tunnel. For instance, the UE tunnel of FIG. 2 may be a PDU session between the UE and the L-DN. Additionally, the C-DN tunnel may be a regular general packet radio service (GPRS) tunneling protocol user plane (GTP-U) tunnel between the L-PSA UPF and the C-PSA UPF that is established by the SMF via regular N4 session signaling (creating associated FAR and PDR rules and QoS requirement). The SMF may also request the C-PSA UPF to assign the UL TEID, and request the L-PSA UPF to assign the DL TEID.

[0053] In certain example embodiments, for the establishment of the C-DN tunnel, the SMF may be initiated by the DNAI information received from the AF (e g., in EDI) to select a C-PSA UPF based on the received DNAI of C-EAS and a L-PSA UPF based on the received DNAI of L-EAS. Once initiated, the SMF may then, via N4 session signaling (PDRs, FARs and QoS requirement), request PSA UPF(s) to generate UL TEID in C-PSA UPF and DL TEID in L-PSA UPF. Generation of the UL TEID and DL TEID may be performed so that the C-DN tunnel may be established between the L-DN and the C-DN. All SMF instances in an SMF set may use the same C-DN and LL-DN tunnels.

[0054] FIG. 4 illustrates an example signal diagram to establish a C-DN tunnel, according to certain example embodiments, and FIG. 4B illustrates the signal diagram continued from FIG. 4A, according to certain example embodiments. As illustrated in FIG. 4, at 416, the AF 406 provides 5GC with a request to establish a C-DN tunnel. For example, the AF may invoke the Nnef_EASDeployment_Create / Update / Delete service operation when using the extended EDI, or the AF may invoke a Nnef TrafficInfluence Create service operation when using the extended TI. At 418, the SMF 400 is triggered to retrieve DNAI information. In some example embodiments, the trigger may be an NEF notification (related to EDI), a PCC rule (carrying information from the AF 406 traffic influence), or a 5GC event (e.g., PDU session establishment / modification, EAS (re-)discovery). The SMF 400 may retrieve DNAI information at 420 and 422 via EDI and PCC rules, respectively. In particular, at 420, the SMF 400 may retrieve the DNAI information from the NEF 404 via EDI based on EAS deployment information management in the SMF. Alternatively, at 422, the SMF 400 may retrieve the DNAI information from the PCF 402 via PCC rules based on AF TI. Once the DNAI information is retrieved by the SMF 400, the SMF 400 may determine to establish a C-DN tunnel based on the information received from the AF 406 and / or PCF 402.

[0055] At 424, the SMF 400 selects two UPFs as the L-PSA UPF and the C-PSA UPF based on the two retrieved DNAIs. At 426, the SMF 400 initiates an N4 session establishment procedure with the selected C-PSA UPF 412. The N4 message may include PDR3 and FAR3 defined in Table 1 below, and a QoS requirement for UL traffic. At 428, the C-PSA UPF 412 performs the session configuration and UL TEID selection. During this session configuration, the UL TEID (e g., UL TEID of the C-DN tunnel) may be used for L-PSA UPF 410 to forward L-DN’s UL traffic to C-DN via C-PSA UPF 412. At 430, the C-PSA UPF 412 responds to the SMF 400 by transmitting an N4 session establishment response to the SMF 400 including the UL TEID of the C-DN tunnel which is a part of the CN tunnel information.

[0056] At 432, the SMF 400 initiates an N4 session establishment procedure with the selected L-PSA UPF 410 to provide UL TEID of the C-DN tunnel to the L-PSA UPF 410. The SMF 400 also provides the L-PSA UPF 410 with PDR2 and FAR2 defined in Table 1, and a QoS requirement for UL traffic. At 434, the L-PSA UPF 410 performs the tunnel configuration and DL TEID of C-DN tunnel / LL-DN tunnel selection. At 436, during the tunnel configuration, DL TEID of the C-DN tunnel may be selected for L-PSA UPF 410 to forward UL traffic to the C-DN 414 via C-PSA UPF 412. At 438, the L-PSA UPF 410 responds to the SMF 400 by transmitting an N4 session establishment response to the SMF 400, which includes the DL TEID of the C-DN tunnel which is a part of the CN tunnel information.

[0057] At 440, the SMF 400 initiates an N4 session update procedure with the selected L-PSA UPF 410, and provides PDR5 and FAR5 defined in Table 2, and a QoS requirement for DL traffic. At 442, the L-PSA UPF 410 responds to the SMF 400 by transmitting an N4 session update response. At 444, the SMF 400 initiates an N4 session update procedure with the selected C-PSA UPF 412, and provides DL TEID of the C-DN tunnel to the C-PSA UPF 412, as well as PDR4 and FAR4 defined in Table 2, and a QoS requirement for DL traffic. At 446, during the tunnel configuration, UL TEID of the C-DN tunnel may be selected for L-PSA UPF 410 to forward DL traffic to the L-EAS 408 via C-PSA UPF 412. At 448, the C-PSA UPF 412 transmits an N4 session update response to the SMF 400. The N4 session update response may include a request to accept (success)Zreject if the UPF is not asked to report anything else in the update message. If the UPF is asked, it may indicate that the UP function has switched to a new F-TEID, or it may return the F-TEID(s) it has assigned to the PDR(s), etc.

[0058] According to certain example embodiments, traffic may be exchanged 5 via 5GS user plane between L-EAS(s) connected on the L-DN on one side, and the C-EAS(s) connected on the C-DN on the other side. Additionally, the UE tunnel may be stablished per 3GPP mechanisms, and the packet detection and forwarding action configuration of the UE tunnel’s L-PSA UPF may also be given as PDR1 and FAR1 m Tabei 1, and PDR6 and FAR6 in Table 2. io Table 1 - PDRs and FARs for UL traffic in L-PSA UPF and C-PSA UPF NF Rule Description L-PSA UPF PDR1 for UE Tunnel UL • Source Interface = access (N3 / N9) (optional) • Packet Filter Set: incoming GTP-u tunnel and • GTP-U outer header removal • FAR ID = 001 FAR1 for UE Tunnel UL • Rule ID 001 • Action = forward; and • Destination interface = N6 PDR2 for C-DN Tunnel UL • Source Interface = N6 (optional) • Packet Filter Set: IP SA = L-EAS IP (address range), IP DA = C-EAS IP (address range) • FAR ID = 002 FAR2 for C-DN Tunnel UL • Rule ID 002 • Action = forward • Destination interface = N9 • GTP-U outer header adding: GTP-u header that the SMF has received from the C-PSA C-PSA UPF PDR3 C-DN Tunnel UL • Source Interface = access (N9) • Packet Filter Set (optional): IP SA = L-EAS IP (address range), IP DA = C-EAS IP (address range) • GTP-U outer header removal • FAR ID = 003 FAR3 C-DN Tunnel UL • Rule ID 003 • Action = forward • Destination interface = N6 Table 2 - PDRs and FARs for DL traffic in L-PSA UPF and C-PSA UPF NF Rule Description L-PSA UPF PDR6 for UE Tunnel DL • Source Interface = N6 (optional) • Packet Filter Set: IP SA = L-EAS IP (range), IP DA = UE IP • FAR ID = 006 FAR6 for UE Tunnel DL • Rule ID 006 • Action = forward • Destination interface = access (N3 / N9) • GTP-U outer header adding PDR5 for C-DN Tunnel DL • Source Interface = access N9 (optional) • Packet Filter incoming GTP-U tunnel • GTP-U outer header removal • FAR ID = 005 FAR5 for C-DN Tunnel DL • Rule ID 005 • Action = forward • Destination interface = N6 C-PSA UPF PDR4 C-DN Tunnel DL • Source Interface = N6 (optional) • Packet Filter Set: IP SA = C-EAS IP (range), IP DA = L-EAS IP (range) • FAR ID = 004 FAR4 C-DN Tunnel DL • Rule ID 004 • Action = forward • Destination interface = access (N9) • GTP-U outer header adding: GTP-U header that the SMF has received from the L-PSA

[0059] In certain example embodiments, PDRs and FARs may be defined by the SMF to configure the L-PSA UPF and the C-PSA UPF for detecting 5 packets for each tunnel, and for forwarding packets to respective DNs. As illustrated in FIG. 4, the PDRs. FARs and QoS requirement(s) for DL and / or UL traffic may be conveyed from the SMF to the L-PSA UPF and the C-PSA UPF in N4 messages via session establishment and / or session setup services. The selection of the attributes of PDRs, FARs and QoS requirement(s) for DL and / or UL traffic may be based on parameters for N4 session management. The selection of the values of PDRs, FARs and QoS requirement(s) for DL and / or UL traffic may be based on information elements. Additionally, the rules for UL traffic in the L-PSA UPF and the C-PSA UPF are listed in Table 1, and the rules for DL traffic in the L-PSA UPF and the C-PSA UPF are listed in Table 2.

[0060] According to certain example embodiments, when there is a UE group, given that the UE tunnel and C-DN tunnel have been established for a UE, if a new UE from the same UE group requests the establishment of a PDU session, and if the SMF is triggered to provide a connection between the L-EAS and the C-EAS for the new UE, the SMF may establish a new PDU session as the UE tunnel to connect the UE and the L-EAS. Additionally, the existing C-DN tunnel may be reused for connecting the L-EAS and C-EAS.

[0061] In certain example embodiments, user plane traffic may be steered using the two created tunnels, and the SMF may ensure proper routing of the traffic. For instance, FIG. 5 illustrates an example signal diagram of UL traffic in the UE tunnel and the C-DN tunnel, according to certain example embodiments. In particular, FIG. 5 illustrates that packet payload may be modified by the L-EAS 506. For instance, at 512, the UE 500 sets up the UE’s address Granted as part of the PDU session as the source IP address of the packet, and the L-EAS’s overlay address as the destination IP address of the packet. At 514, after receiving the packet from the UE 500, the Access Network, such as, for example, RAN node 502, adds a GTP-U header for the packet. The source address in the GTP-U header may be the underlay address of the Access Network, such as, for example, RAN node 502, and the destination address in the GTP-U header may be the underlay address of the L-PSA UPF 504. It is noted that RAN is just an example of an Access Network and that other kinds of Access Networks such as Untrusted non-3GPP access network (terminated by a N3IWF) or Wireline access network (terminated by a W-AGF) may apply instead of a RAN and, thus, may apply instead of the RAN mentioned throughout this document. The packet may be forwarded to the L-PSA UPF 504. It is also noted that there may be intermediate UPF(s) between the Access Networks and the L-PSA UPF, but these intermediate UPF(s) are not mentioned to keep the description simple. If there is any intermediate UPF between the RAN node 502 and the L-PSA UPF 504, the destination address may be the underlay address of the next intermediate UPF.

[0062] At 516, after receiving the packet from the RAN node 502, the L-PSA UPF 504 removes the GTP-U header from the packet (configuration PDR1). The L-PSA UPF 504 follows the destination IP address stored in the IP header that the packet is sent to the L-EAS 506 (configuration FAR1). At 518, the packet is processed by the L-EAS 506, which is deployed on the L-DN. The application logic in the L-EAS 506 may decide to send traffic to the C-EAS 510 (packet with destination IP address = C-EAS). At 520, if the routing is configured for the L-EAS 506 to reach the L-PSA UPF 504, the L-EAS 506 sets up the L-EAS’s 506 overlay address as the source IP address and the C-EAS’ overlay address as the destination IP address of the packet. According to certain example embodiments, if the routing is not configured for the L-EAS 506 to reach the L-PSA UPF 504, the L-EAS 506 may apply a tunneling approach on the L-EAS - L-PSA UPF interface. Specifically, on top of the source and final destination (i.e., L-EAS’s overlay address and C-EAS’s overlay address), the L-EAS 506 may add another outer IP header, in which L-EAS’ overlay address is the source address, and L-PSA UPF’s overlay address is the destination address. In this case, the L-PSA UPF 508 removes the outer IP header before processing the packet based on outer header removal instructions from the SMF.

[0063] At 522, after receiving the packet from the L-EAS 506 (configuration PDR2), the L-PSA UPF 504 adds a GTP-U header for the packet (configuration FAR2). The source address in the GTP-U header may be the underlay address of the L-PSA UPF 504, and the destination address in the GTP-U header may be the underlay address of the C-PSA UPF 508 (unless there are some intermediate UPF(s) between the L-PSA UPF 504 and the C-PSA UPF 508 which is possible but not further mentioned to keep the description simple). The packet may be forwarded to the C-PSA UPF 508. If there is any intermediate UPF between the L-PSA UPF 504 and the C-PSA UPF 508, the destination address may be the underlay address of the next intermediate UPF. At 524, after receiving the packet from the L-PSA UPF 504, the C-PSA UPF 508 removes the GTP-U header from the packet (configuration PDR3). The C-PSA UPF 508 then transmits the traffic to the C-EAS 510 per configuration FAR3.

[0064] According to certain example embodiments, if the routing is configured for the C-PSA UPF 508 to reach the C-EAS 510 for the packets with IP address ranges of the L-EAS(s) 506, the C-PSA UPF 508 may follow the destination IP address stored in the IP header, and the packet may be forwarded based on the routing information. In other example embodiments, if the routing is not configured for the C-PSA UPF 508 to reach the C-EAS 510, several approaches may be applied by the C-PSA UPF 508. For example, in one approach, tunneling may be applied on the C-PSA UPF - C-EAS interface. The C-PSA UPF 508 may tunnel the packet destined to the C-EAS 510 by creating another outer IP header, setting up the C-PSA UPF’s overlay address as the source IP address of the packet and C-EAS’ overlay address as the destination IP address of the packet. In this case, the C-EAS 510 may remove the outer IP header before processing the packet. Another approach may involve the network address translation (NAT) approach on the C-PSA UPF - C-EAS interface. Here, a NAT enabled in the C-PSA UPF 508 may translate / replace the address of the L-EAS 506 with the address of the C-PSA UPF 508, which may be used as the new source IP address for the packet.

[0065] FIG. 6 illustrates an example signal diagram of DL traffic in the UE tunnel and the C-DN tunnel, according to certain example embodiments. At 612, the C-EAS 610 transmits some traffic to the L-EAS 606 via the 5GC. If the routing is configured for the C-EAS 610 to reach the C-PSA UPF 608, the C-EAS may set up the C-EAS’s overlay address as the source IP address, and the L-EAS’s overlay address as the destination IP address of the packet. In certain example embodiments, if the routing is not configured for the C-EAS 610 to reach the C-PSA UPF 608, several approaches may be available to the C-EAS 610. For example, a tunneling approach may be applied on the C-EAS - C-PSA UPF interface. In this example, the C-EAS 610 may tunnel the packet destined for the C-PSA UPF 608. For example, the C-EAS 610 may create another outer IP header, set up the C-EAS’ overlay address as the source IP address of the packet and CPS A UPF’s overlay address as the source IP address of the packet. In this case, the C-PSA UPF 608 may remove the outer IP header before processing the packet.

[0066] In another example, a NAT approach may apply on the C-EAS - C-PSA UPF interface. The L-EAS address handled by the C-EAS 610 corresponds to the C-PSA UPF 608. A NAT enabled in the C-PSA UPF 608 translates / replaces the overlay address of the C-PSA UPF 608 with the overlay address of the L-EAS 606, which may be used as the new source IP address for the packet.

[0067] At 614, after receiving the packet from the C-EAS 610 (configuration PDR4), the C-PSA UPF 608 adds a GTP-U header for the packet (configuration FAR4). The source address in the GTP-U header may be the underlay address of the C-PSA UPF 608, and the destination address in the GTP-U header may be the underlay address of the L-PSA UPF 604. The packet may be forwarded to the L-PSA UPF 604. According to certain example embodiments, if there is any intermediate UPF between the C-PSA UPF 608 and the L-PSA UPF 604, the destination address may be the underlay address of the next intermediate UPF.

[0068] At 616, after receiving the packet from the C-PSA UPF 608, the L-PSA UPF 604 removes the GTP-U header from the packet (configuration PDR5). The L-PSA UPF 604 may then follow the overlay address stored in the header, that the packet is sent to the L-DN (configuration FAR5). At 618, the packet is processed by the L-EAS 606, which is deployed on the L-DN. The application logic in the L-EAS 606 may decide to transmit traffic to the UE 600 (packet with destination IP address = UE). At 620, the L-EAS 606 sets up the L-EAS’ overlay address as the source IP address of the packet, and transmits the packet to the L-PSA UPF 605. In certain example embodiments, the UE’s 600 overlay address may be set as the destination IP address of the packet.

[0069] At 622, after receiving the packet from the L-EAS 606 in the L-DN (configuration PDR6), the L-PSA UPF 604 adds a GTP-U header for the packet (configuration FAR6). In certain example embodiments, the source address in the GTP-U header may be the underlay address of the L-PSA UPF 604, and the destination address in the GTP-U header may be the underlay address of the RAN node 602. As illustrated in FIG. 6, the packet is forwarded to the RAN node 602. If there is any intermediate UPF between the L-PSA UPF 604 and the RAN node 602, the destination address may be the underlay address of the next intermediate UPF. At 624, after receiving the packet from the L-PSA UPF 604, the RAN node 602 removes the GTP-U header from the packet, follows the destination IP address stored in the IP header, and transmits the packet to the UE 600.

[0070] FIG 7 illustrates an example flow diagram of a method, according to certain example embodiments. In an example embodiment, the method of FIG. 7 may be performed by a network entity, or a group of multiple network elements in a 3GPP system, such as LTE, 5G-NR, or 6G. For instance, in an example embodiment, the method of FIG. 7 may be performed by an SMF similar to one of apparatuses 10 or 20 illustrated in FIG. 9.

[0071] As illustrated in FIG. 7, the method may include, at 700, getting information associated with data network terminations. The method also includes, at 705, establishing, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. The method further includes, at 710, ensuring that traffic related with edge application servers is sent on the tunnels. In addition, the method may include, at 715, ensuring a given quality of service requirement and / or packet classification information to the traffic.

[0072] According to certain example embodiments, the information associated with data network terminations may be associated with edge application server deployment information or with traffic influence information related to at least a data network access identifier. According to some example embodiments, establishing the tunnels to setup connectivity between the plurality of data network terminations may include for each tunnel: selecting a plurality of user plane functions based on the information; requesting the plurality of user plane functions to generate one or more than one uplink tunnel endpoint identifier and downlink tunnel endpoint identifier; configuring the plurality of user plane functions with at least one rule for detecting data packets; configuring the plurality of user plane functions with at least one rule for forwarding data packets based on at least one forwarding action rule; configuring the plurality of user plane functions with at least one quality of service requirement information together with any of the indicators above; configuring the plurality of user plane functions with at least one packet classification information along with any of the indicators above.

[0073] In certain example embodiments, the tunnels may be established to allow traffic forwarding between a data network access identified as local and data network access identified as central. In some example embodiments, the tunnels may be established between a data network access identified as local and other data network access identified as local. In other example embodiments, configuring the plurality of user plane functions with at least one rule for detecting data packets may include at least one of: detecting data packets of a user equipment traffic; detecting data packets of a processed traffic at a local data network; or detecting data packets of a processed traffic at a central data network.

[0074] According to certain example embodiments, configuring the plurality of user plane functions with at least one rule for forwarding data packets based on at least one forwarding action rule may include at least one of: forwarding data packets for user equipment traffic; forwarding to a central data network data packets of traffic generated or processed at a local data network; forwarding to other local data network data packets of traffic generated or processed at a local data network; or forwarding to a local data network data packets of traffic generated or processed at a central data network. According to some example embodiments, configuring the plurality of user plane functions with at least one quality of service requirement and / or packet classification information may include at least one of: an indicator whether the given quality of service requirement and / or packet classification applies on downlink traffic; or an indicator whether the given quality of service requirement and / or packet classification applies on uplink traffic. According to some example embodiments, the method may also include configuring the plurality of user plane functions to use an existing central data network tunnel or a local-to-local data network tunnel for a same application traffic.. According to other example embodiments, getting information associated with the edge application server deployment information or the traffic influence information and related with at least a data network access identifier may be triggered by a network exposure function notification, a policy and charging control rule, or a 5G core event.

[0075] According to certain example embodiments, configuring the plurality of user plane functions with at least one quality of service requirement and / or packet classification information may include at least one of the following: an indicator whether the given quality of service requirement and / or packet classification applies on downlink traffic; or an indicator whether the given quality of service requirement and / or packet classification applies on uplink traffic.

[0076] In certain example embodiments, the plurality of user plane functions may include at least one of: a local protocol data unit session anchor user plane function; or a central protocol data unit session anchor user plane function. In some example embodiments, the information associated with data network terminations comprises at least one of: routing information to reach an application instance associated with a data network termination; an indicator of whether the data network termination is to be considered local or central; an indicator of whether connectivity of a local data network access to a central data network access is needed; an indicator of whether connectivity of the local data network access to other local data network accesses is needed; an indicator of whether a connectivity of any local data network access to any central data network access is needed; an indicator of whether a connectivity of any local data network access to any other local data network access is needed; a quality of service requirement information together with any of the indicators above; or a packet classification information together with any of the indicators above. In other example embodiments, the tunnels to setup connectivity between the plurality of data network terminations may be used to exchange traffic associated with one or multiple protocol data unit sessions.

[0077] FIG. 8 illustrates an example flow diagram of a method, according to certain example embodiments. In an example embodiment, the method of FIG. 8 may be performed by a network entity, or a group of multiple network elements in a 3GPP system, such as LTE, 5G-NR, or 6G. For instance, in an example embodiment, the method of FIG. 8 may be performed by an AF similar to one of apparatuses 10 or 20 illustrated in FIG. 9.

[0078] As illustrated in FIG. 8, the method may include, at 800, providing, to a network element, information associated with data network terminations. According to certain example embodiments, the information may trigger establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of data network terminations.

[0079] In certain example embodiments, the information associated with data network terminations may be associated with edge application server deployment information or with traffic influence information related to at least a data network access identifier. In some example embodiments, the information associated with data network terminations may be provided to a network exposure function or a policy control function. In other example embodiments, the information associated with data network terminations comprises at least one of: routing information to reach an application instance associated with a data network termination; an indicator of whether the data network termination is to be considered local or central; an indicator of whether connectivity of a local data network access to a central data network access is needed; an indicator of whether connectivity of the local data network access to other local data network accesses is needed; an indicator of whether a connectivity of any local data network access to any central data network access is needed; an indicator of whether a connectivity of any local data network access to any other local data network access is needed; a quality of service requirement information together with any of the indicators above; or a packet classification information together with any of the indicators above. In further example embodiments, the tunnels to setup connectivity between a plurality of data network terminations may be used to exchange traffic related to applications servers identified by the application request.

[0080] FIG. 9 illustrates a set of apparatuses 10 and 20 according to certain example embodiments. In certain example embodiments, apparatuses 10 and 20 may be elements in a communications network or associated with such a network. For example, apparatus 10 may be an SMF, or other similar radio communication computer device, and apparatus 20 may be an AF, or other similar radio communication computer device.

[0081] In some example embodiments, apparatuses 10 and 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and / or a user interface. In some example embodiments, apparatuses 10 and 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, 6G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatuses 10 and 20 may include components or features not shown in FIG. 9.

[0082] As illustrated in the example of FIG. 9, apparatuses 10 and 20 may include or be coupled to a processors 12 and 22 for processing information and executing instructions or operations. Processors 12 and 22 may be any type of general or specific purpose processor. In fact, processors 12 and 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, DSPs, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processors 12 and 22 is shown in FIG. 9, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatuses 10 and 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processors 12 may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0083] Processors 12 and 22 may perform functions associated with the operation of apparatuses 10 and 20 including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatuses 10 and 20, including processes and examples illustrated in FIGs. 1-8.

[0084] Apparatuses 10 and 20 may further include or be coupled to a memories 14 and 24 (internal or external), which may be respectively coupled to processors 12 and 24 for storing information and instructions that may be executed by processors 12 and 24. Memories 14 and 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and / or removable memory. For example, memories 14 and 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memories 14 and 24 may include program instructions or computer program code that, when executed by processors 12 and 22, enable the apparatuses 10 and 20 to perform tasks as described herein.

[0085] In certain example embodiments, apparatuses 10 and 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processors 12 and 22 and / or apparatuses 10 and 20 to perform any of the methods and examples illustrated inFIGs. 1-8.

[0086] In some example embodiments, apparatuses 10 and 20 may also include or be coupled to one or more antennas 15 and 25 for receiving a downlink signal and for transmitting via an UL from apparatuses 10 and 20. Apparatuses 10 and 20 may further include a transceivers 18 and 28 configured to transmit and receive information. The transceivers 18 and 28 may also include a radio interface (e.g., a modem) coupled to the antennas 15 and 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, 6G, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an UL.

[0087] For instance, transceivers 18 and 28 may be configured to modulate information on to a carrier waveform for transmission by the antennas 15 and 25 and demodulate information received via the antenna 15 and 25 for further processing by other elements of apparatuses 10 and 20. In other example embodiments, transceivers 18 and 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 10 may include an input and / or output device (I / O device). In certain example embodiments, apparatuses 10 and 20 may further include a user interface, such as a graphical user interface or touchscreen.

[0088] In certain example embodiments, memories 14 and 34 store software modules that provide functionality when executed by processors 12 and 22. The modules may include, for example, an operating system that provides operating system functionality for apparatuses 10 and 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatuses 10 and 20. The components of apparatuses 10 and 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, apparatuses 10 and 20 may optionally be configured to communicate each other (in any combination) via a wireless or wired communication links 70 according to any radio access technology, such as NR.

[0089] According to certain example embodiments, processors 12 and 22 and memories 14 and 24 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 18 and 28 may be included in or may form a part of transceiving circuitry.

[0090] For instance, in certain example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to get information associated with data network terminations. Apparatus 10 may also be controlled by memory 14 and processor 12 to establish, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. Apparatus 10 may further be controlled by memory 14 and processor 12 to ensure that traffic related with edge application servers is sent on the tunnels. In addition, apparatus 10 may be controlled by memory 14 and processor 12 to ensure a given quality of service requirement and / or packet classification information to the traffic.

[0091] In other example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to provide, to a network element, information associated with data network terminations. According to certain example embodiments, the information triggers establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of data network terminations.

[0092] In some example embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing the performance of the operations.

[0093] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for getting information associated with data network terminations. The apparatus may also include means for establishing, based on the received information, tunnels to setup connectivity between a plurality of data network terminations. The apparatus may further include means for ensuring that traffic related with edge application servers is sent on the tunnels. In addition, the apparatus may include means for ensuring a given quality of service requirement and / or packet classification to the traffic.

[0094] Other example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for providing, to a network element, information associated with data network terminations. According to certain example embodiments, the information triggers establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of data network terminations.

[0095] Certain example embodiments described herein provide several technical improvements, enhancements, and / or advantages with respect to application-centric processing on servers using mobile network connectivity (e.g., 5G system (5GS) connectivity, 6G system (6GS) connectivity, and so forth). For instance, in some example embodiments, it may be possible to define a method for network nodes to have the capability of connecting the L-DN and the C-DN or to connect two L-DNs via UP. In other example embodiments it may be possible to enable traffic forwarding between L-EAS and C-EAS in UP or to enable traffic forwarding between two L-EAS s located on different data centers (DNAI). Thus, in certain example embodiments, it may be possible to steer UL traffic to a L-DN enabling an L-EAS in the L-DN to process the traffic before sending this traffic to a C-EAS in the C-DN or to another L-EAS in another L-DN for further processing. It may also be possible to steer DL traffic from a C-EAS in the C-DN or from a L-EAS in a L-DN to be first handled by a L-EAS in the L-DN (for further local processing of the traffic), and then to be forwarded to the relevant UE.

[0096] A computer program product may include one or more computerexecutable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain example embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0097] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and / or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0098] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10 or apparatus 20), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0099] According to certain example embodiments, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[0100] One having ordinary skill in the art will readily understand that the disclosure as discussed above may be practiced with procedures in a different order, and / or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the disclosure has been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. Although the above embodiments refer to 5G NR and LTE technology, the above embodiments may also apply to any other present or future 3 GPP technology, such as LTE-advanced, and / or fourth generation (4G) technology.

[0101] Partial Glossary:

[0102] 3GPP 3rd Generation Partnership Project

[0103] 5G 5th Generation

[0104] 5GC 5G Core

[0105] 5GCN 5G Core Network

[0106] 5GS 5G System

[0107] AF Application Function

[0108] BS Base Station

[0109] C-DN Central Data Network

[0110] C-EAS Central Edge Application Server [01U]C-PSA UPF Central PSA UPF

[0112] DA Destination Address

[0113] DL Downlink

[0114] DN Data Network

[0115] EAS Edge Application Server [0U6]EASDF Edge Application Server Discovery Function

[0117] EDI EAS Deployment Information

[0118] eNB Enhanced Node B [0U9]E-UTRAN Evolved UTRAN

[0120] FAR Forwarding Action Rule

[0121] FQDN Fully Qualified Domain Name

[0122] gNB 5G or Next Generation NodeB

[0123] GTP-U GPRS Tunnelling Protocol User Plane

[0124] L-DN Local Data Network

[0125] L-EAS Local Edge Application Server

[0126] L-PSA UPF Local PSA UPF

[0127] NEF Network Exposure Function

[0128] NR New Radio

[0129] PDR Packet Detection Rule

[0130] PDU Protocol Data Unit

[0131] PSA PDU Session Anchor

[0132] RAN Radio Access Network

[0133] SA Source Address

[0134] TEID Terminal Endpoint Identifier

[0135] UDR Unified Data Repository

[0136] UE User Equipment

[0137] UL Uplink WE CLAIM:

Claims

1. An apparatus, comprising:means for getting information associated with data network terminations;means for establishing, based on the received information, tunnels to setup connectivity between a plurality of data network terminations;means for ensuring that traffic related with edge application servers is sent on the tunnels; andmeans for ensuring a given quality of service requirement and / or packet classification information to the traffic.

2. The apparatus according to claim 1, wherein the information associated with data network terminations is associated with edge application server deployment information or with traffic influence information related to at least a data network access identifier.

3. The apparatus according to claims 1 or 2, wherein the means for establishing the tunnels to setup connectivity between the plurality of data network terminations comprises for each tunnel:means for selecting a plurality of user plane functions based on the information;means for requesting the plurality of user plane functions to generate one or more than one uplink tunnel endpoint identifier and downlink tunnel endpoint identifier;means for configuring the plurality of user plane functions with at least one rule for detecting data packets;means for configuring the plurality of user plane functions with at least one rule for forwarding data packets based on at least one forwarding actionrule; andmeans for configuring the plurality of user plane functions with at least one quality of service requirement and / or packet classification information.

4. The apparatus according to any of claims 1-3, wherein the tunnels are established to allow traffic forwarding between a data network access identified as local and data network access identified as central.

5. The apparatus according to any of claims 1-3, wherein the tunnels are established between a data network access identified as local and other data network access identified as local.

6. The apparatus according to claim 3, wherein the means for configuring the plurality of user plane functions with at least one rule for detecting data packets comprises at least one of the following:means for detecting data packets of a user equipment traffic;means for detecting data packets of a processed traffic at a local data network; ormeans for detecting data packets of a processed traffic at a central data network.

7. The apparatus according to claim 3, wherein the means for configuring the plurality of user plane functions with at least one rule for forwarding data packets based on at least one forwarding action rule comprises at least one of the following:means for forwarding data packets for user equipment traffic;means for forwarding to a central data network data packets of traffic generated or processed at a local data network;means for forwarding to other local data network data packets of trafficgenerated or processed at a local data network; ormeans for forwarding to a local data network data packets of traffic generated or processed at a central data network.

8. The apparatus according to claim 3, wherein the means for configuring the plurality of user plane functions with at least one quality of service requirement and / or packet classification information comprises at least one of the following:an indicator whether the given quality of service requirement and / or packet classification applies on downlink traffic; oran indicator whether the given quality of service requirement and / or packet classification applies on uplink traffic.

9. The apparatus according to any of claims 1-8, further comprising: means for configuring the plurality of user plane functions to use an existing central data network tunnel or a local-to-local data network tunnel for a same application traffic.

10. The apparatus according to any of claims 1-9, wherein getting information associated with the edge application server deployment information or the traffic influence information and related with at least a data network access identifier is triggered by a network exposure function notification, a policy and charging control rule, or a 5G core event.

11. The apparatus according to any of claims 1-10, wherein the plurality of user plane functions comprises at least one of the following:a local protocol data unit session anchor user plane function; or a central protocol data unit session anchor user plane function.

12. The apparatus according to any of claims 1-11, wherein the information associated with data network terminations comprises at least one of the following:routing information to reach an application instance associated with a data network termination;an indicator of whether the data network termination is to be considered local or central;an indicator of whether connectivity of a local data network access to a central data network access is needed;an indicator of whether connectivity of the local data network access to other local data network accesses is needed;an indicator of whether a connectivity of any local data network access to any central data network access is needed;an indicator of whether a connectivity of any local data network access to any other local data network access is needed;a quality of service requirement information together with any of the indicators above; ora packet classification information together with any of the indicators above.

13. The apparatus according to any of claims 1-12, wherein the tunnels to setup connectivity between the plurality of data network terminations are used to exchange traffic associated with one or multiple protocol data unit sessions.

14. An apparatus, comprising:means for providing, to a network element, information associated with data network terminations,wherein the information triggers establishment of, based on reception of the information, tunnels to setup connectivity between a plurality of datanetwork terminations.

15. The apparatus according to claim 14, wherein the information associated with data network terminations is associated with edge application server deployment information or with traffic influence information related to at least a data network access identifier.

16. The apparatus according to claims 14 or 15, wherein the information associated with data network terminations is provided to a network exposure function or a policy control function.

17. The apparatus according to any of claims 14-16, wherein the information comprises at least one of the following:routing information to reach an application instance associated with a data network termination;an indicator of whether the data network termination is to be considered local or central;an indicator of whether connectivity of a local data network access to a central data network access is needed;an indicator of whether connectivity of the local data network access to other local data network accesses is needed;an indicator of whether a connectivity of any local data network access to any central data network access is needed;an indicator of whether a connectivity of any local data network access to any other local data network access is needed;a quality of service requirement information together with any of the indicators above; ora packet classification information together with any of the indicatorsabove.

18. The apparatus according to any of claims 14-17, wherein the tunnels to setup connectivity between a plurality of data network terminations are used to exchange traffic related to applications servers identified by the application request.

Images