DYNAMIC ACTIVATION OF LOCAL BREAKOUT WITH COORDINATION BETWEEN APPLICATION DOMAIN AND MOBILE NETWORK

Disclosed herein is a method performed by a network node and a network node performing the method, which implements a DNS function in a mobile network, the method comprising the actions: receiving; a DNS query that originated at a UE; in response to receiving; the DNS query, determining; to trigger dynamic activation of Local Break Out, LBO, for a session of the UE at a breakout site of the mobile network for traffic between the UE and an edge AS site that is connected to the breakout site; and upon determining; to trigger dynamic activation of LBO for the session of the UE at the breakout site of the mobile network for traffic between the UE and the edge AS site, triggering; dynamic activation of LBO for the session of the UE at the breakout site of the mobile network for traffic between the UE and the edge AS site.

BACKGROUND

FIG.1illustrates one example network topology (one part of a Mobile Network Operator (MNO) network). This example shows different network site types (local, regional, national). More specifically, a network consists of sites spread in different geographical locations. Functionality is spread to different sites depending on, e.g., requested performance, costs, security, and availability. This can vary between different ambitions of different operators as well as the size of the network. In large networks, there are different numbers of instances for each site type.Devices/Local networks—The actual device used by a user or a network set up by a user or enterprise outside the control of the operatorCustomer Premises Site (CS), Usage: customer equipment, Manning: unmanned, Security: low, Connectivity: below gigabit per second (Gbps)Access sites—Local sites which are as close as possible to the usersAntenna Site (AnS), Usage: antenna and Radio Frequency (RF) equipment (also complete micro/pico), Manning: unmanned, Security: low, Connectivity: 10 GbpsRadio Access Site (RS), Usage: telecom functionality, Radio Access Network (RAN) equipment, Manning: unmanned, Security: low, Connectivity: below terabit per second (Tbps)Distributed sites—Sites which are distributed for reasons of execution or transport efficiency or for local breakoutHub Site (HS), Usage: transport equipment, Manning: unmanned, Security: low, Connectivity: below TbpsLocal Access Site (LA), Usage: telecom functionality including RAN equipment, Manning: mostly unmanned, Security: medium, Connectivity: less than TbpsRegional Data Center (RDC), Usage: compute, storage and networking equipment, Manning: 24/7, Security: extremely high, Connectivity: very high bandwidthNational sites—National sites which are typically centralized within an operator's networkNational Access Site (NA), Usage: telecom functionality, Manning: 24/7 (or reachable within hours), Security: high, Connectivity: very high bandwidthNational Data Center (NDC), Usage: compute, storage and networking equipment, Manning: 24/7, Security: extremely high, Connectivity: very high bandwidthNetwork Operation Center (NOC), Usage: NOC equipment, Manning: 24/7, Security: high, Connectivity: some GbpsGlobal sites—Centralized sites which are publicly accessible from anywhere, typically a large data centerInternational Data Center (IDC), Usage: compute, storage and networking equipment, Manning: 24/7, Security: extremely high, Connectivity: very high bandwidth
Note that the CS, AnS, or RS are examples of a “radio site” referred to herein. The LA is an example of a “local site” as referred to herein. An RDC is an example of a “regional site” referred to herein. An NA is an example of a “national site” referred to herein.

FIG.2illustrates one network solution for traffic routing, e.g., for Application Servers (ASs)/Content Delivery Network (CDN) in a distributed cloud architecture. As illustrated, in this example, a mobile network includes a RAN including radio sites (e.g., base stations such as, e.g., enhanced or evolved Node Bs (eNBs) or New Radio (NR) base stations (gNBs)). In addition, the mobile network includes a core network (e.g., an Evolved Packet Core (EPC) or Fifth Generation (5G) core), where core network functionality (e.g., core network functions) are implemented at a number of sites. In the example ofFIG.2, these sites include a breakout site and a session anchor site. The breakout site may be, for example, a local site as described above with respect toFIG.1, but is not limited thereto. The session anchor site may be, for example, a national site (also referred to herein as a “central” site) as described above with respect toFIG.1, but is not limited thereto.

The solution for traffic routing illustrated inFIG.2is referred to as a “session breakout” or Local Break Out (LBO) solution. In the session breakout solution, the User Equipment (UE) has a PDU session with a core network User Plane (UP) part located at the session anchor site. In addition, a core network UP is located at the breakout site for the same UE PDU session. At the breakout site, some uplink traffic from the UE is routed to the core network UP part located at the session anchor site and, using LBO, some other uplink traffic from the UE is routed to, e.g., an AS or Domain Name System (DNS) connected to (e.g., an edge of) the breakout site. Note that session breakout is PDU session specific. If the UE has multiple PDU sessions, then each of those PDU sessions can use session breakout.

Session breakout is beneficial in various traffic routing or content delivery scenarios. For example, consider a streaming video service provider. In the normal scenario, the streaming service provider has a corresponding AS that is connected to the session anchor site (e.g., a national site). This AS is responsible for streaming video content to the UEs associated with the video streaming service (e.g., to subscribers of the video streaming service). However, in order to provide an improved experience to the user (e.g., lower latency), it is beneficial for such a streaming video service provider to also have “edge sites” (e.g., “edge ASs”) that are connected to breakout sites (e.g., local sites) and accessible using session breakout. For instance, consider a scenario in which a particular UE has a PDU session that is used by multiple applications including an Internet browser and an application client for streaming video service. Then, for example, an Uplink Classifier (ULCL) in the core UP part directs traffic for the streaming video service to the core UP Function (UPF) at the breakout site via session breakout and directs traffic for the Internet browser to the core UP at the session anchor site.

SUMMARY

There currently exist certain challenge(s). Using conventional LBO, the LBO is “always on”. In other words, the ULCL in the core UP part is static such that all traffic on the PDU session is always processed in the ULCL. This is very inefficient, particularly when much of the traffic is for services other than the service(s) for which there are local/edge site(s). Further, there is a need for systems and methods for efficiently handling DNS queries when using session breakout. Using conventional technology, LBO is always active at the breakout site, and a DNS server is also implemented at the breakout site. When a DNS query is received from the UE, this DNS query is always first processed by the DNS server at the breakout site. If the DNS server at the breakout site cannot serve the DNS query, then the DNS query is either forwarded to a DNS server at the session anchor site or the UE is redirected to the DNS at the session anchor site. Such a solution is very inefficient because all DNS queries from the UE must be processed by the DNS server at the breakout site even if there is only one edge AS connected (e.g., an edge AS associated with a particular service).

DETAILED DESCRIPTION

Radio Node: As used herein, a “radio node” is either a radio access node or a wireless device.

Radio Access Node: As used herein, a “radio access node” or “radio network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network, also called Next Generation Radio Access Network (NG-RAN), or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), also called Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node. Core Network Node: As used herein, a “core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing a Access and Mobility Function (AMF), a User Plane (UP) Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

Wireless Device: As used herein, a “wireless device” is any type of device that has access to (i.e., is served by) a cellular communications network by wirelessly transmitting and/or receiving signals to a radio access node(s). Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device.

It should also be noted that the embodiments herein focus on the use of a Protocol Data Unit (PDU) session. However, a PDU session is a 5G concept, and the embodiments are equally applicable to other types of connections (e.g., a Packet Data Network (PDN) connection such as that utilized in a Fourth Generation (4G) network).

Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Systems and methods are disclosed herein for dynamically activating/deactivating Local Break Out (LBO) and efficiently handling Domain Name System (DNS) queries in a mobile network. In some embodiments, LBO (i.e., Uplink Classifier (ULCL)/UPF at the breakout site that provide LBO) is dynamically activated when a distributed Application Server (AS) (also referred to herein as an “edge AS” or “edge site AS”) is selected by the application layer. Once the distributed application server is not used anymore, the ULCL/UPF is deactivated. In some embodiments, dynamic activation/deactivation LBO is based on the AS provider and the mobile network operator having a Service Level Agreement (SLA), which is referred to herein as a “traffic routing SLA” that defines (1) the application(s) (edge AS(s)) that are applicable for this functionality (e.g., defined by domain name(s), e.g., Fully Qualified Domain Name(s) (FQDN(s))), (2) the location(s) of edge site(s) at which the edge AS(s) are placed, referred to herein as “edge site/AS location”, (3) optionally (depending on the particular embodiment) an Internet Protocol (IP) address for an edge DNS server, and (4) optionally (depending on the particular embodiment) an IP address range for the edge site or the edge AS. With the above information, the mobile network can utilize the current location of the UE (e.g., determined in any desired manner such as, e.g., via the IP address of the UE) to perform AS selection. If the edge AS is selected, then the mobile network triggers activation of LBO (i.e., triggers activation of the ULCL and UPF at the breakout site for LBO to the edge site).

In this regard,FIG.3illustrates one example of a cellular communications system300, which also referred to herein as a mobile network, in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system300is a 5G System (5GS) including a NG-RAN and a 5G Core (5GC). However, the embodiments described herein are equally applicable to an Evolved Packet System (EPS) including a LTE RAN and an Evolved Packet Core (EPC). In this example, the RAN includes base stations302-1and302-2, which in NG-RAN are referred to as gNBs or Next Generation eNBs (NG-eNBs), controlling corresponding (macro) cells304-1and304-2. The base stations302-1and302-2are generally referred to herein collectively as base stations302and individually as base station302. Likewise, the (macro) cells304-1and304-2are generally referred to herein collectively as (macro) cells304and individually as (macro) cell304. The RAN may also include a number of low power nodes306-1through306-4controlling corresponding small cells308-1through308-4. The low power nodes306-1through306-4can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells308-1through308-4may alternatively be provided by the base stations302. The low power nodes306-1through306-4are generally referred to herein collectively as low power nodes306and individually as low power node306. Likewise, the small cells308-1through308-4are generally referred to herein collectively as small cells308and individually as small cell308.

Note that the base stations302each include a Control Plane (CP) part (sometimes referred to herein as a RAN CP or RAN CP part) and one or more UP parts (sometimes referred to herein as RAN UP or RAN UP part).

The cellular communications system300also includes a core network310, which in the 5GS is referred to as the 5GC. The base stations302(and optionally the low power nodes306) are connected to the core network310. For example, the base stations302are located at corresponding radio sites. Note, however, that in some embodiments the functionality of the RAN may be split into multiple parts (see, e.g.,FIG.6described below). For example, looking atFIG.6, the Distributed Unit (DU) is typically located at the radio site, while the Central Unit (CU) CP (CU-CP) and CU UP (CU-UP) may be either at the radio site or at any site higher up in the network (e.g., at the local site, regional site, or national site). In addition, the core network310includes UP parts (e.g., UPFs) located at various local, regional, and national (i.e., central) sites.

The base stations302and the low power nodes306provide service to wireless devices312-1through312-5in the corresponding cells304and308. The wireless devices312-1through312-5are generally referred to herein collectively as wireless devices312and individually as wireless device312. The wireless devices312are also sometimes referred to herein as UEs.

FIG.4illustrates a wireless communication system represented as a 5G network architecture composed of core NFs, where interaction between any two NFs is represented by a point-to-point reference point/interface.FIG.4can be viewed as one particular implementation of the system300ofFIG.3.

Seen from the access side the 5G network architecture shown inFIG.4comprises a plurality of UEs connected to either a RAN or an Access Network (AN) as well as an AMF. Typically, the R(AN) comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5G core NFs shown inFIG.4include a NSSF, an AUSF, a UDM, an AMF, a SMF, a PCF, and an Application Function (AF).

Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE and AMF. The reference points for connecting between the AN and AMF and between the AN and UPF are defined as N2 and N3, respectively. There is a reference point, N11, between the AMF and SMF, which provides the possibility for the AMF and SMF to interact in different ways. N4 is used by the SMF and UPF so that the UPF can be set using the control signal generated by the SMF, and the UPF can report its state to the SMF. N5 is the reference point for the connection between the PCF and AF. N6 is the reference point for the connection between the UPF and Data Network (DN). N9 is the reference point for the connection between different UPFs, and N14 is the reference point connecting between different AMFs, respectively. N15 and N7 are defined since the PCF applies policy to the AMF and SMF, respectively. N12 is required for the AMF to perform authentication of the UE. N8 and N10 are defined because the subscription data of the UE is required for the AMF and SMF. N22 is the reference point for the connection between the AMF and NSSF.

The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. InFIG.4, the UPF is in the UP and all other NFs, i.e., the AMF, SMF, PCF, AF, AUSF, and UDM, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP Functions (CPFs) in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.

The core 5G network architecture is composed of modularized functions. For example, the AMF and SMF are independent functions in the CP. Separated AMF and SMF allow independent evolution and scaling. Other CPFs like the PCF and AUSF can be separated as shown inFIG.4. Modularized function design enables the 5GC network to support various services flexibly.

Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.

FIG.5illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points/interfaces used in the 5G network architecture ofFIG.4. However, the NFs described above with reference toFIG.4correspond to the NFs shown inFIG.5. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. InFIG.5the service based interfaces are indicated by the letter “N” followed by the name of the NF, e.g. Namf for the service based interface of the AMF and Nsmf for the service based interface of the SMF etc. The NEF and the NRF inFIG.5are not shown inFIG.4discussed above. However, it should be clarified that all NFs depicted inFIG.4can interact with the NEF and the NRF ofFIG.5as necessary, though not explicitly indicated inFIG.4.

Some properties of the NFs shown inFIGS.4and5may be described in the following manner. The AMF provides UE-based authentication, authorization, mobility management, etc. A UE even using multiple access technologies is basically connected to a single AMF because the AMF is independent of the access technologies. The SMF is responsible for session management and allocates IP addresses to UEs based on the PDU session concept. It also selects and controls the UPF for data transfer. If a UE has multiple PDU sessions, different SMFs may be allocated to each session to manage them individually and possibly provide different functionalities per PDU session. The AF provides information on the packet flow to the PCF responsible for policy control in order to support Quality of Service (QoS). Based on the information, the PCF determines policies about mobility and session management to make the AMF and SMF operate properly. The AUSF supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM stores subscription data of the UE. The DN, not part of the 5GC network, provides Internet access or operator services and similar.

An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

FIG.6shows the internal architecture for an exemplifying gNB, i.e. referring to a base station supporting NR RAT in the (R)AN ofFIGS.4and5and called NG-RAN in this case (see 3GPP Technical Specification (TS) 38.401 for stage-2 description of NG-RAN).FIG.6assumes that both Higher Layer Split (HLS) and CP-UP split have been adopted within the gNB. The NG-RAN may also contain LTE NG-eNBs and HLS may later be supported also for NG-eNBs.

HLS means that the gNB is divided into a CU and a DU. CP-UP split further divides the CU into a CU-CP and a CU-UP and this part is currently being standardized in 3GPP. Note that the CU-CP is also sometimes referred to herein as RAN CP. The related study report is 3GPP Technical Report (TR) 38.806. The CU-CP hosts the Radio Resource Control (RRC) protocol and the Packet Data Convergence Protocol (PDCP) used for the CP part and the CU-UP hosts the Service Data Adaptation Protocol (SDAP) protocol and the PDCP used for the UP part. The CU-CP is controlling the CU-UP via an E1 interface. Although not shown inFIG.6, the CU-CP is the function that terminates the N2 interface from the AMF in 5GC, and the CU-UP is the function terminating the N3 interface from the UPF in 5GC (e.g., in relation toFIGS.4and5). Logically, a UE has one CU-UP per PDU session. Other terms used for N2 and N3 interfaces in 3GPP are Next Generation CP Interface (NG-C) and Next Generation UP Interface (NG-U).

FIGS.7A through7Hillustrate a system and corresponding method for dynamically activating LBO and efficiently handling a DNS query in one example of a mobile network700. As illustrated, the mobile network700includes a radio site702, a breakout site704, and a session anchor site706. The radio site702includes a RAN UP part708and a RAN CP part710. The breakout site704may include a RAN UP part712. The session anchor site706includes a core UP part714, which includes a UPF716, a core CP part718, and a Mobile Network Operator (MNO) DNS720. As discussed below in detail, the session anchor site706also includes a new DNS function722. In this example, the new DNS function722is separate from the core UP part714; however, the new DNS function722may alternatively be part of the core UP part714.

The UPF716at the session anchor site706is connected to an AS724and an AS site DNS726located at an AS site728, which is in the illustrated example part of a DN730(e.g., the Internet), through a gateway, which is in this example an Internet Exchange Point (IXP)732.

A UE734is connected to the mobile network700. The UE734includes one or more applications736including an Application Client (AC)738associated with the AS724, an Operating System (OS)740that includes an OS function742and an DNS function744, and one or more modems746including a 3GPP UE modem748.

A process for enabling and providing dynamic activation (and deactivation) of LBO at the breakout site will now be described with respect toFIGS.7A through7H.

As illustrated inFIG.7A, a traffic routing SLA is defined between the operator of the mobile network700and the service provider associated with the AS724. The traffic routing SLA includes: (A) a domain name (e.g., FQDN) associated with the AS724(and thus an edge AS750—see, e.g.,FIG.7B), (B) an edge site or edge AS location (i.e., location information for the edge AS750or an edge AS site752at which the edge AS750is located), (C) an IP address of an edge site DNS754(see, e.g.,FIG.7B), and (D) an IP address range of the edge AS site752(i.e., IP address range for the edge AS750and the edge site DNS754) or an IP address range for the edge AS750, depending on the particular embodiment. The information in the traffic routing SLA is utilized by the operator to configure the mobile network700. In particular, in this example, the information in the traffic routing SLA is used to configure the new DNS function722.

Looking atFIG.7B, the above traffic routing SLA information is for a specific distributed AS site (also referred to herein as an “edge site” or “edge AS site”), which is the edge AS site752in this example. Note that when there are multiple such distributed AS sites, then each of these may have its own traffic routing SLA with the related information. Also note that there may be multiple such traffic routing SLAs per AS site. So, these AS sites can contain multiple different ASs, which may have their own traffic routing SLAs. The traffic routing SLA information is made available in the new DNS function722and is used as described in the following. For the logic described in this embodiment, the new DNS function722uses the following information and capabilities in addition to the traffic routing SLA information:i. Information about the current UE location within the mobile network. This location needs to be in a format that can be mapped to the edge site/AS location in the Traffic Routing SLA. There are different ways for how the new DNS function can get the UE location, as will be appreciated by one of skill in the art. Any such way may be used.ii. Capability to trigger dynamic activation and/or deactivation of a distributed ULCL/UPF at a specific network site (e.g., at the breakout site704in this example) via the mobile network core CP part718. In addition, the new DNS function722is able to identify the current core CP node for the UE's PDU session, for example a specific SMF for a specific UE PDU session.

In the illustrated example, the new DNS function722is shown as a separate entity from the MNO DNS720, but these can also be the same entity.

As also illustrated inFIG.7B, the service provider deploys the edge AS750and the edge site DNS754at the edge AS site752. The edge AS site752is said to be closer to a site that is “further out” in the mobile network700in that it is connected to the breakout site704rather than the session anchor site706. Note that the edge AS750is the same as or some limited version of the AS724(e.g., the AS724may be an AS for a video streaming service and the edge AS750may be a cache for some subset of the video content that is available from the AS724).

As illustrated inFIG.7C, the UE734, and in particular the AC738at the UE734, triggers the DNS client744to perform a DNS query to resolve an IP address of the AS724. The response may either be an IP address of the edge AS750or the (central) AS724. The DNS query from the UE734is propagated through the mobile network700to the new DNS function722. In this embodiment, the new DNS function722(which may be a DNS server) first checks if the FQDN included in the DNS query is part of any traffic routing SLA information set defined by any traffic routing SLA(s) for which the new DNS722has been configured. If this is not the case, then the new DNS function722forwards the DNS query to the DNS infrastructure in the normal manner (e.g., via the MNO DNS720or other DNS server). If the FQDN included in the DNS query is part of one or more traffic routing SLA information sets, then the new DNS function722checks the current location of the UE734against the edge site/AS location in the traffic routing SLA information set(s) that matched the FQDN included in the DNS query. If the current location of the UE734does not match the edge site/AS location of any of the matching traffic routing SLA information set(s), then the new DNS function722forwards the DNS query to the DNS infrastructure in the normal manner, e.g. via the MNO DNS720or other DNS servers.

If the UE location matches the edge site/AS location from more than one of the traffic routing SLA information sets that matched the FQDN included in the DNS query, then the new DNS function722selects the traffic routing SLA information set for which the UE location most closely matches (e.g., is closest to) the edge site/AS location. If there is only one traffic routing SLA information set for which the UE location matches the edge site/AS location, then that traffic routing SLA information set is selected. In the illustrated example, the selected SLA information set is that for the edge AS site752(i.e., the edge AS750), and the new DNS function722forwards the DNS query to the IP address for edge DNS server754defined in the traffic routing SLA for the selected edge site/AS, as illustrated inFIG.7C. Note that in the discussion above, the new DNS function722first checks the FQDN and then checks location. However, the new DNS function722may alternatively check the location first and then check the FQDN.

It should be noted that the manner in which the new DNS function722determines whether the UE location matches an edge site/AS location depends on how these two locations are defined. For example, the edge site/AS location may, in some embodiments, be defined at a point (e.g., a physical address, a set of Global Positioning System (GPS) coordinates, or the like) where the UE location matches the edge site/AS location if, e.g., the UE location is within a predefined distance from that point or within a predefined geographic region. As another example, in some other embodiments, the edge site/AS location may be defined as a geographic region where the UE location matches the edge site/AS location if, e.g., the UE location is within that geographic region. Note that the above examples for determining whether the UE location matches the edge site/AS location are only examples. Any suitable technique may be used.

As illustrated inFIG.7C, the edge site DNS754may decide to serve the DNS query locally or the edge site DNS754may forward the DNS query to a more central site DNS (e.g., the AS site DNS726). In the latter case, the edge AS DNS server location is used by the central site DNS to decide where the AS should be selected. In the shown example, the edge AS750at the edge AS site752is selected, either by the edge site DNS754or by the central site DNS. The DNS response is returned to the new DNS function722, as illustrated inFIG.7D.

The new DNS function722checks if the IP address returned in the DNS response matches the IP address range (i.e., within the IP address range) for the edge AS site752or the edge AS750defined in the traffic routing SLA. In this case, there is a match, and the new DNS function722triggers the core CP part718to dynamically activate LBO at the breakout site704, as illustrated inFIG.7E. In other words, the new DNS function722triggers the core CP part718to dynamically activate a ULCL756and a UPF758in a core UP part760at the breakout site704to provide LBO for the PDU session of the UE734, as illustrated inFIG.7F. Note that while the ULCL756is in the core UP part760in this embodiment, the ULCL756may alternatively be implemented in the RAN (i.e., at the radio site702as part of or in association with the RAN UP part708. Also note that the trigger from the new DNS function722preferably includes an indication of the specific site at which LBO is being triggered. There are different possibilities for this indication of the actual site.

The new DNS function722also returns the DNS response to the UE734, as illustrated inFIG.7G. Thereafter, optimal traffic routing is enabled. In other words, traffic between the AC738and the edge AS750is routed, by the ULCL756, using LBO, as illustrated inFIG.7H.

Note that, in another embodiment, the IP address returned in the DNS response from the edge site DNS754may match an IP address range of another traffic routing SLA for another edge site or edge AS that also serves the FQDN included in the DNS query from the UE734and has an edge site/AS location that matches the current location of the UE734. In this case, the new DNS function722triggers the core CP part718to dynamically activate LBO at a breakout site for this other edge site/AS. In other words, the new DNS function722triggers the core CP part718to dynamically activate a ULCL and a UPF in a core UP760at the breakout site to provide LBO for the PDU session of the UE734to the other edge site/AS.

FIG.8is a flow chart that illustrates the operation of the new DNS function722in accordance with the embodiment described above with respect toFIGS.7A through7H. Optional steps are represented by dashed lines. As illustrated, the new DNS function722obtains (e.g., is configured with) the information for the edge AS site752(e.g., the information from the traffic routing SLA described above) (step800). The new DNS function722receives a DNS query from the UE734(step802) and determines whether the DNS query is applicable to any edge AS site or edge AS (step804). More specifically, the new DNS function722determines whether the FQDN included in the DNS query matches the domain name handled by any traffic routing SLA information set defined any traffic routing SLA of any edge AS site or edge AS for which the new DNS function722is configured. If this is not the case, then normal DNS query processing is performed (step818) (e.g., the new DNS function722forwards the DNS query to the DNS infrastructure in the normal manner (e.g., via the MNO DNS720or other DNS server)). If the FQDN included in the DNS query is part of one or more traffic routing SLA information sets, then the new DNS function722checks the current location of the UE734against the edge site/AS location in the traffic routing SLA information set(s) that match the FQDN included in the DNS query. If there are no matches, then normal DNS query process (step818) is performed.

However, if there are one or more traffic routing information sets that both match the FQDN included in the received DNS query and have edge site/AS locations that match the UE location, then the DNS query is applicable to the corresponding one or more edge sites/ASs. As such, the new DNS function722performs edge site/AS selection (step805). In particular, if the UE location matches the edge site/AS location from more than one of the traffic routing SLA information sets that matched the FQDN included in the DNS query, then the new DNS function722selects the edge site/AS corresponding one of those traffic routing SLA information sets (e.g., selects the edge site/AS that corresponds to one of those traffic routing SLA information sets for which the UE location most closely matches (e.g., is closest to) the edge site/AS location). If there is only one traffic routing SLA information set for which the UE location matches the edge site/AS location, then the edge site/AS that corresponds to that traffic routing SLA information set is selected. In the illustrated example, the selected SLA information set is that for the edge AS site752/edge AS750. As such, the edge AS site752/edge AS750is selected. Note that in the discussion above, the new DNS function722first checks the FQDN and then checks location. However, the new DNS function722may alternatively check the location first and then check the FQDN.

Upon selecting the edge AS site752/edge AS750, the new DNS function722sends the DNS query to the edge site DNS754(e.g., using the IP address of the edge site DNS754provided by the traffic routing SLA) (step806). The new DNS function722receives a DNS response (step808) and determines whether the IP address included in the DNS response is one that is served by the edge AS site752or edge AS750(e.g., is within the IP address range defined in the traffic routing SLA for the edge AS site752or edge AS750) (step810). If so, the new DNS function722triggers activation of LBO (e.g., triggers activation of the ULCL756and the UPF758at the respective breakout site704) (step812) and sends the DNS response to back towards the UE734(step814). If the IP address in the DNS response is not one served by the edge AS750, the new DNS function722does not trigger activation of LBO (step816) and sends the DNS response towards the UE734(step814).

Note that, in another embodiment, the IP address returned in the DNS response from the edge site DNS754may match an IP address range of another traffic routing SLA for another edge site or edge AS that also serves the FQDN included in the DNS query from the UE734and has an edge site/AS location that matches the current location of the UE734. In this case, the new DNS function722triggers the core CP part718to dynamically activate LBO at a breakout site for this other edge site/AS. In other words, the new DNS function722triggers the core CP part718to dynamically activate a ULCL and a UPF in a core UP760at the breakout site to provide LBO for the PDU session of the UE734to the other edge site/AS.

FIGS.9A through9Hillustrate an alternative embodiment of the present disclosure. As illustrated inFIG.9A, the traffic routing SLA is defined between the operator of the mobile network700and the service provider associated with the AS724, and the new DNS function722is configured with the traffic routing SLA information, as described above. Note, however, that in this embodiment, the traffic routing SLA need not define an IP address range for the edge AS site752or edge AS750. Looking atFIG.9B, the service provider deploys the edge AS750and the edge site DNS754at the edge AS site752. As illustrated inFIG.9C, the UE734, and in particular the AC738at the UE734, performs a DNS query to resolve an IP address of the AS724. The response may either be an IP address of the edge AS750or the (central) AS724. The DNS query from the UE734is propagated through the mobile network700to the new DNS function722.

In this embodiment, the new DNS function722(which may be a DNS server) first checks if the FQDN included in the DNS query is part of any traffic routing SLA information set defined by any traffic routing SLA(s) for which the new DNS722has been configured. If this is not the case, then the new DNS function722forwards the DNS query to the DNS infrastructure in the normal manner (e.g., via the MNO DNS720or other DNS server). If the FQDN included in the DNS query is part of one or more traffic routing SLA information sets, then the new DNS function722checks the current location of the UE734against the edge site/AS location in the traffic routing SLA information set(s) that matched the FQDN included in the DNS query. If the current location of the UE734does not match the edge site/AS location of any of the matching traffic routing SLA information set(s), then the new DNS function732forwards the DNS query to the DNS infrastructure in the normal manner, e.g. via the MNO DNS720or other DNS servers.

If the UE location matches the edge site/AS location from more than one of the traffic routing SLA information sets that matched the FQDN included in the DNS query, then the new DNS function722selects the traffic routing SLA information set for which the UE location most closely matches (e.g., is closest to) the edge site/AS location. If there is only one traffic routing SLA information set for which the UE location matches the edge site/AS location, then that traffic routing SLA information set is selected. Note that in the discussion above, the new DNS function722first checks the FQDN and then checks location. However, the new DNS function722may alternatively check the location first and then check the FQDN.

In the illustrated example, the selected SLA information set is that for the edge AS site752(i.e., the edge AS750), and the new DNS function722triggers the core CP part718to dynamically activate LBO at the breakout site704, as illustrated inFIG.9D. In other words, the new DNS function722triggers the core CP part718to dynamically activate a ULCL756and a UPF758at the breakout site704to provide LBO for the PDU session of the UE734. Note that the trigger from the new DNS function722preferably includes an indication of the specific site at which LBO is being triggered. There are different possibilities for this indication of the actual site. In addition, the new DNS function722redirects the UE734(and in particular the DNS function744of the UE734) to the edge site DNS754using the IP address defined in the traffic routing SLA for the edge site DNS754, as illustrated inFIG.9E.

Upon being redirected, the UE734, and in particular the DNS function744of the UE734, sends the DNS query to the IP address of the edge site DNS754, as illustrated inFIG.9F. Since LBO has been activated, the ULCL756routes the DNS query to the edge site DNS754via the UPF758using LBO. As illustrated inFIG.9F, the edge site DNS754may decide to serve the DNS query locally or the edge site DNS754may forward the DNS query to a more central AS DNS server (e.g., the AS site DNS726). In the latter case, the edge site DNS location is used by the central AS site DNS to decide where the AS should be selected. In the shown example, the edge AS750at the edge AS site752is selected, either by the edge site DNS754or by the central AS site DNS. The DNS response is returned to the UE734, as illustrated inFIG.9G. Thereafter, optimal traffic routing is enabled. In other words, traffic between the AC738and the edge AS750is routed, by the ULCL756, using LBO, as illustrated inFIG.9H.

FIG.10is a flow chart that illustrates the operation of the new DNS function722in accordance with the embodiment described above with respect toFIGS.9A through9H. Optional steps are represented by dashed lines. As illustrated, the new DNS function722obtains (e.g., is configured with) the information for the edge AS site752(e.g., the information from the traffic routing SLA described above) (step1000). The new DNS function722receives a DNS query from the UE734(step1002) and determines whether the DNS query is applicable to any edge AS site or edge AS (step1004). More specifically, the new DNS function722determines whether the FQDN included in the DNS query matches the domain name handled by any traffic routing SLA information set defined any traffic routing SLA of any the edge AS site or edge AS for which the new DNS function722is configured. If this is not the case, then normal DNS query processing is performed (step1010) (e.g., the new DNS function722forwards the DNS query to the DNS infrastructure in the normal manner (e.g., via the MNO DNS720or other DNS server)). If the FQDN included in the DNS query is part of one or more traffic routing SLA information sets, then the new DNS function722checks the current location of the UE734against the edge site/AS location in the traffic routing SLA information set(s) that match the FQDN included in the DNS query. If there are no matches, then normal DNS query process (step1010) is performed.

However, if there are one or more traffic routing information sets that both match the FQDN included in the received DNS query and have edge site/AS locations that match the UE location, then the DNS query is applicable to the corresponding one or more edge sites/ASs. As such, the new DNS function722performs edge site/AS selection (step1005). In particular, if the UE location matches the edge site/AS location from more than one of the traffic routing SLA information sets that matched the FQDN included in the DNS query, then the new DNS function722selects the edge site/AS corresponding one of those traffic routing SLA information sets (e.g., selects the edge site/AS that corresponds to one of those traffic routing SLA information sets for which the UE location most closely matches (e.g., is closest to) the edge site/AS location). If there is only one traffic routing SLA information set for which the UE location matches the edge site/AS location, then the edge site/AS that corresponds to that traffic routing SLA information set is selected. In the illustrated example, the selected SLA information set is that for the edge AS site752/edge AS750. As such, the edge AS site752/edge AS750is selected. Note that in the discussion above, the new DNS function722first checks the FQDN and then checks location. However, the new DNS function722may alternatively check the location first and then check the FQDN.

Upon selecting the edge AS site752/edge AS750, the new DNS function722triggers activation LBO (e.g., triggers activation of the ULCL756and the UPF758at the respective breakout site704) (step1006) and redirects the UE734to the edge site DNS754(step1008). If the DNS query is determined to not be applicable to the edge AS site752(or any other edge site for which the new DNS function722is configured with the respective traffic routing SLA information), the new DNS function722provides the DNS query for normal DNS processing (e.g., forwards the DNS query to the MNO DNS720) (step1010).

FIG.11illustrates an alternative embodiment in which the new DNS function722is integrated into the core UP part714. In this embodiment, existing signaling and/or triggers between the core UP part714and the core CP part718may be used to trigger activation/deactivation of LBO. Otherwise, the operation of the system for LBO activation/deactivation is the same as described above. Further, in some embodiments, the core CP part718, the core UP part714, and the new DNS function722may be integrated.

FIG.12illustrates another alternative embodiment in which the edge site DNS754is replaced with a breakout site DNS1200. In this embodiment, the breakout site DNS1200is populated with the rules/information for resolving DNS queries for the edge AS site752. In addition, the address information of the local site DNS1200indicates the location of the UE to the AS site DNS726located at an AS site728. Otherwise, the operation of the system for LBO activation/deactivation is the same as described above.

It should be noted that while the embodiments described herein focus on LBO at the breakout site704using the ULCL756in the core UP part760, the present disclosure is not limited thereto. Alternatively, the LBO may use a ULCL at the radio site702as described in U.S. Provisional Patent Application Ser. No. 62/878,982, filed Jul. 26, 2019, which is attached hereto as Appendix A. Thus, in some alternative embodiments, dynamic activation of LBO includes dynamic activation/deactivation of the ULCL in the radio site.

FIG.13is a schematic block diagram of a network node1300according to some embodiments of the present disclosure. The network node1300may be a network node that implements the new DNS function722or any other network node described above with respect toFIGS.7A-7H,FIG.8,FIGS.9A-9H,FIG.10,FIG.11, and/orFIG.12. As illustrated, the network node1300includes a control system1302that includes one or more processors1304(e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory1306, and a network interface1308. The one or more processors1304are also referred to herein as processing circuitry. In some embodiments, the network node1300is a radio access node (e.g., a base station302), and the network node1300also includes one or more radio units1310that each includes one or more transmitters1312and one or more receivers1314coupled to one or more antennas1316. The radio units1310may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s)1310is external to the control system1302and connected to the control system1302via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s)1310and potentially the antenna(s)1316are integrated together with the control system1302. The one or more processors1304operate to provide one or more functions of a network node1300as described herein (e.g., one or more functions of the new DNS function722or any other network node described above with respect toFIGS.7A-7H,FIG.8,FIGS.9A-9H,FIG.10,FIG.11, and/orFIG.12, as described herein). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory1306and executed by the one or more processors1304.

FIG.14is a schematic block diagram that illustrates a virtualized embodiment of the network node1300according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures.

As used herein, a “virtualized” network node is an implementation of the network node1300in which at least a portion of the functionality of the network node1300is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node1300includes one or more processing nodes1400coupled to or included as part of a network(s)1402. Each processing node1400includes one or more processors1404(e.g., CPUs, ASICs, FPGAs, and/or the like), memory1406, and a network interface1408. In some embodiments, the network node1300is a radio access node, and the network node1300also includes the control system1302and/or the one or more radio units1310, as described above. Notably, in some embodiments, the control system1302may not be included, in which case the radio unit(s)1310communicate directly with the processing node(s)1400via an appropriate network interface(s).

In this example, functions1410of the network node1300described herein (e.g., one or more functions of the new DNS function722or any other network node described above with respect toFIGS.7A-7H,FIG.8,FIGS.9A-9H,FIG.10,FIG.11, and/orFIG.12, as described herein) are implemented at the one or more processing nodes1400or distributed across the control system1302and the one or more processing nodes1400in any desired manner. In some particular embodiments, some or all of the functions1410of the network node1300described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s)1400.

FIG.15is a schematic block diagram of the network node1300according to some other embodiments of the present disclosure. The network node1300includes one or more modules1500, each of which is implemented in software. The module(s)1500provide the functionality of the network node1300described herein (e.g., one or more functions of the new DNS function722or any other network node described above with respect toFIGS.7A-7H,FIG.8,FIGS.9A-9H,FIG.10,FIG.11, and/orFIG.12, as described herein). This discussion is equally applicable to the processing node1400ofFIG.14where the modules1500may be implemented at one of the processing nodes1400or distributed across multiple processing nodes1400and/or distributed across the processing node(s)1400and the control system1302.

FIG.16is a schematic block diagram of a UE1600according to some embodiments of the present disclosure. The UE1600may be, e.g., the UE734. As illustrated, the UE1600includes one or more processors1602(e.g., CPUs, ASICs, FPGAs, and/or the like), memory1604, and one or more transceivers1606each including one or more transmitters1608and one or more receivers1610coupled to one or more antennas1612. The transceiver(s)1606includes radio-front end circuitry connected to the antenna(s)1612that is configured to condition signals communicated between the antenna(s)1612and the processor(s)1602, as will be appreciated by on of ordinary skill in the art. The processors1602are also referred to herein as processing circuitry. The transceivers1606are also referred to herein as radio circuitry. In some embodiments, the functionality of the UE1600described above may be fully or partially implemented in software that is, e.g., stored in the memory1604and executed by the processor(s)1602. Note that the UE1600may include additional components not illustrated inFIG.16such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the UE1600and/or allowing output of information from the UE1600), a power supply (e.g., a battery and associated power circuitry), etc.

FIG.17is a schematic block diagram of the UE1600according to some other embodiments of the present disclosure. The UE1600includes one or more modules1700, each of which is implemented in software. The module(s)1700provide the functionality of the UE1600described herein.

Some Embodiments

While not being limited thereto, some example embodiments of the present disclosure are provided below.1. A method performed by a network node that implements a Domain Name System, DNS, function (722) in a mobile network (700), the method comprising one or more of the following actions:

receiving (802;1002) a DNS query that originated at a User Equipment, UE, (734);

in response to receiving (802;1002) the DNS query, determining (804-810;1004) to trigger dynamic activation of Local Break Out, LBO, for a session (e.g., a Protocol Data Unit, PDU, session) of the UE (734) at a breakout site (704) of the mobile network (700) for traffic between the UE (734) and an edge Application Server, AS, site (752) that is connected to the breakout site (704); and

upon determining (804-810;1004) to trigger dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752), triggering (812;1006) dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752).2. The method of embodiment1wherein determining (804-810;1004) to trigger dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752) comprises:determining (804; YES) that the DNS query is applicable to one or more edge AS sites or one or more edge ASs located at the one or more edge sites (e.g., at any of a number of edge AS sites/edge ASs for which the DNS function (722) is configured); andselecting (805) the edge AS site (752) or an edge AS (750) at the edge AS site (752) from among the one or more edge sites or the one or more edge ASs;sending (806) the DNS query to either an edge site DNS (754) located at the edge AS site (752) or a breakout site DNS (1200) located at the breakout site (704);receiving (808) a DNS response comprising an Internet Protocol, IP, address for a domain name comprised in the DNS query; anddetermining (810) that the IP address comprised in the DNS response is within a set of IP addresses (e.g., within a range of IP addresses) for the edge AS site (752) or the edge AS (750).3. The method of embodiment 2 wherein triggering (812;1006) dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752) comprises:

triggering (812) dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752) upon determining (810, YES) that the IP address comprised in the DNS response is within the set of IP addresses for the edge AS site (752) or the edge AS (750).4. The method of embodiment 2 further comprising sending (814) the DNS response to the UE (734) through the mobile network (700).5. The method of any of embodiments 2-4 wherein determining (804) that the DNS query is applicable to the one or more edge AS sites or the one or more edge ASs comprises:

determining (804) that a domain name comprised in the DNS request matches a domain name handled by the one or more edge AS sites or the one or more edge ASs; and determining (804) that a current location of the UE (734) matches locations of the one or more edge AS sites or the one or more edge ASs.6. The method of embodiment 1 wherein determining (804-810;1004) to trigger dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752) comprises:

determining (1004) that the DNS query is applicable to one or more edge AS sites or one or more edge ASs located at the one or more edge sites; and

selecting (1005) the edge AS site (752) or the edge AS (750) from among the one or more edge AS sites or the one or more edge ASs.7. The method of embodiment 6 wherein triggering (812;1006) dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752) comprises:

triggering (1006) dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752) upon selecting (1005) the edge AS site (752) or the edge AS (750).8. The method of embodiment 7 further comprising redirecting (1008) the UE (734) to send the DNS query to either an edge site DNS (754) located at the edge site (752) or a breakout site DNS (1200) located at the breakout site (704).9. The method of any one of embodiments 1 to 8 wherein triggering (812;1006) dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752) comprises triggering dynamic activation of:

a user plane function (758) in a core user plane part (760) at the breakout site (704), the user plane function (758) being connected to the edge AS site (752); and

an uplink classifier (756) that directs traffic from the session of the UE (734) that is intended for the edge AS site (752) to the edge AS site (752) via the user plane function (758).10. The method of embodiment 9 wherein the uplink classifier (756) is implemented in the core user plane part (760) at the breakout site (704).11. The method of embodiment 9 wherein the uplink classifier (756) is implemented in a Radio Access Network, RAN, of the mobile network (700) (e.g., within or in association with a RAN user plane part (708) at a radio site (702) of the mobile network (700)).12. The method of any one of embodiments 1 to 11 wherein determining (804-810;1004) to trigger dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752) comprises determining (804-810;1004) to trigger dynamic activation of LBO for the session of the UE (734) at the breakout site (704) of the mobile network (700) for traffic between the UE (734) and the edge AS site (752) based on information defined in a traffic routing service level agreement between an operator of the mobile network (700) and a service provider associated with the edge AS site (752).13. The method of embodiment 12 wherein the information defined in the traffic routing service level agreement comprises a domain name handled by the edge AS site (752) and location information for the edge AS site (752) or edge AS (750).14. The method of embodiment 13 wherein the information defined in the traffic routing service level agreement further comprises an Internet Protocol, IP, address of the edge site DNS (754) at the edge AS site (752).15. The method of embodiment 13 or 14 wherein the information defined in the traffic routing service level agreement further comprises a set of IP addresses for the edge AS site (752) and/or the edge AS (750).16. A network node adapted to perform the method of any of embodiments 1 to 15.

Abbreviations

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).3GPP Third Generation Partnership Project4G Fourth Generation5G Fifth Generation5GC Fifth Generation Core5GS Fifth Generation SystemAC Application ClientAF Application FunctionAMF Access and Mobility FunctionAN Access NetworkAP Access PointAUSF Authentication Server FunctionCP Control PlaneCPF Control Plane FunctionCU-CP Central Unit Control PlaneCU-UP Central Unit User PlaneDN Data NetworkDNS Domain Name SystemDU Distributed UniteNB Enhanced or Evolved Node BEPC Evolved Packet CoreEPS Evolved Packet SystemE-UTRAN Evolved Universal Terrestrial Radio Access NetworkFQDN Fully Qualified Domain NamegNB New Radio Base StationHSS Home Subscriber ServerIP Internet ProtocolLA Local Access SiteLBO Local Break OutLTE Long Term EvolutionMME Mobility Management EntityMNO Mobile Network OperatorNEF Network Exposure FunctionNF Network FunctionNG-C Next Generation Control Plane InterfaceNG-eNB Next Generation Enhanced or Evovled Node BNG-U Next Generation User Plane InterfaceNG-RAN Next Generation Radio Access NetworkNR New RadioNRF Network Function Repository FunctionNSSF Network Slice Selection FunctionOS Operation SystemPCF Policy Control FunctionPDCP Packet Data Convergence ProtocolPDN Packet Data NetworkPDU Protocol Data UnitP-GW Packet Data Network GatewayQoS Quality of ServiceRAN Radio Access NetworkRDC Regional Data CenterRF Radio FrequencyRRC Radio Resource ControlSCEF Service Capability Exposure FunctionSLA Service Level AgreementSMF Session Management FunctionTR Technical ReportTS Technical SpecificationUDM Unified Data ManagementUE User EquipmentULCL Uplink ClassifierUP User PlaneUPF User Plane Function