Method and apparatus for directing a session to an application server

Abstract

One method includes: receiving traffic impact routing rules from an application function (AF) by a control plane (CP), the traffic impact routing rules including a service address representing a destination address of a route to an application server, the traffic impact routing rules specifying circumvention rules for packets destined for a communication device of the application server; storing the traffic impact routing rules in a policy control function (PCF) by the CP; and generating a traffic filter for packets of at least one service flow associated with the communication device by the CP, the traffic filter directing packets of at least one service flow destined for the application server to the service address, the traffic filter being generated according to the traffic impact routing rules.

Description

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 019,754, filed May 4, 2020, entitled “Apparatus and Methods for PDUSession Steering for Edge Computing,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present invention generally relates to methods and apparatus for digital communication, and in certain embodiments, to methods and apparatus for directing a session to an application server. Background Technology

[0003] Fifth Generation (5G) networks hosting edge computing (EC) sites close to the radio access network (RAN) can have segmented packet data unit (PDU) sessions, where the default PDU session path terminates at the central data network, and the local path terminates near the access network (AN) or RAN. Routing to the local path uses a user plane function (UPF), forwarding to the local UPF PDU session anchor (PSA) if the forwarding rules configured during PDU session establishment match. An example of such a UPF is the uplink classifier (ULCL) UPF.

[0004] EC services and application services typically use anycast Internet Protocol (IP) addresses to represent service addresses. The availability of the application server (AS) is programmed into the routing controller and advertised using Border Gateway Protocol (BGP) (or Interior Gateway Protocol (IGP)). This provides a scalable and flexible way for users to access the application server.

[0005] PDU sessions (or similar network access) to an edge application server (EAS) deployed at the mobile edge traverse from user equipment (UE) to the UPF, where the UPF selectively redirects traffic to the local UPF-PSA. Because the routes advertised by BGP, IGP, etc., are unknown, the UPF cannot redirect packets to the EAS unless it knows the application service at the edge. Therefore, a method and apparatus are needed for redirecting sessions to the application server. Summary of the Invention

[0006] According to a first aspect, a method is provided. The method includes: receiving traffic impact routing rules from an application function (AF) by a control plane (CP), the traffic impact routing rules including a service address representing a destination address of a route to an application server, the traffic impact routing rules specifying bypass rules for packets destined for a communication device of the application server; storing the traffic impact routing rules in a policy control function (PCF) by the CP; and generating a traffic filter for packets of at least one service flow associated with the communication device, the traffic filter directing packets of at least one service flow destined for the application server to the service address, the traffic filter being generated according to the traffic impact routing rules.

[0007] According to the first aspect, in a first implementation of the method, the traffic impact routing rule includes at least one of a traffic impact creation rule, a traffic impact update rule, or a traffic impact deletion rule.

[0008] According to the first aspect or any of the above implementations of the first aspect, in a second implementation of the method, the traffic-affected routing rule further includes at least one gateway address associated with the service address.

[0009] According to the first aspect or any of the above implementations of the first aspect, in a third implementation of the method, the traffic filter includes the service address and the at least one gateway address.

[0010] According to the first aspect or any of the above implementations of the first aspect, in a fourth implementation of the method, the traffic filter is based on network slice selection auxiliary information storage.

[0011] According to the first aspect or any of the above implementations of the first aspect, in a fifth implementation of the method, the method further includes: the CP sending a traffic impact routing rule response to the AF.

[0012] According to the first aspect or any of the above implementations of the first aspect, in a sixth implementation of the method, the traffic filter is stored in a unified data repository (UDR).

[0013] According to the first aspect or any of the above implementations of the first aspect, in a seventh implementation of the method, storing the flow filter includes updating an existing flow filter using the flow filter.

[0014] According to the first aspect or any of the above implementations of the first aspect, in the eighth implementation of the method, the service address includes an Internet Protocol address, a port address, and a protocol.

[0015] According to the first aspect or any of the above implementations of the first aspect, in a ninth implementation of the method, the method further includes: generating information associated with the flow filter by the CP.

[0016] According to the first aspect or any of the above implementations of the first aspect, in a tenth implementation of the method, the information includes single network slice selection assistance information (S-NSSAI).

[0017] According to a second aspect, a method is provided. The method includes: receiving, by a PCF, a traffic filter for packets of at least one service flow associated with a communication device, the traffic filter including traffic impact routing rules specifying circumvention rules for packets destined for an application server; deriving a network identifier associated with the traffic filter by the PCF; and providing the network identifier and the traffic filter by the PCF to a session management function (SMF).

[0018] According to the second aspect, in a first implementation of the method, the network identifier includes a data network access identifier (DNAI).

[0019] According to the second aspect or any of the above implementations of the second aspect, in the second implementation of the method, the traffic filter includes a service address and at least one gateway address.

[0020] According to the second aspect or any of the above implementations of the second aspect, in a third implementation of the method, the traffic filter further includes network slice selection auxiliary information.

[0021] According to the second aspect or any of the above implementations of the second aspect, in a fourth implementation of the method, providing the network identifier and the traffic filter includes initiating a session management policy control service.

[0022] According to a third aspect, a CP (Content Provider) is provided. The CP includes: a non-transitory memory including instructions; and one or more processors communicating with the memory, wherein the one or more processors execute the instructions to: receive a traffic impact routing rule from an AF (Application Provider), the traffic impact routing rule including a service address representing a destination address for a route to an application server, the traffic impact routing rule specifying a bypass rule for packets destined for a communication device to the application server; store the traffic impact routing rule in a PCF (Content Provider Function); and generate a traffic filter for packets of at least one service flow associated with the communication device, the traffic filter directing packets of at least one service flow destined for the application server to the service address, the traffic filter being generated according to the traffic impact routing rule.

[0023] According to the third aspect, in the first implementation of the CP, the traffic impact routing rule includes at least one of a traffic impact creation rule, a traffic impact update rule, or a traffic impact deletion rule.

[0024] According to the third aspect or any of the above implementations of the third aspect, in the second implementation of the CP, the traffic-affected routing rule further includes at least one gateway address associated with the service address.

[0025] According to the third aspect or any of the above implementations of the third aspect, in the third implementation of the CP, the traffic filter includes the service address and the at least one gateway address.

[0026] According to the third aspect or any of the above implementations of the third aspect, in the fourth implementation of the CP, the traffic filter is based on network slice selection auxiliary information storage.

[0027] According to the third aspect or any of the above implementations of the third aspect, the fifth implementation of the CP further includes: the CP sending a traffic impact routing rule response to the AF.

[0028] According to the third aspect or any of the above-described implementations of the third aspect, in the sixth implementation of the CP, the flow filter is stored in the UDR.

[0029] According to the third aspect or any of the above implementations of the third aspect, in the seventh implementation of the CP, storing the traffic filter includes updating an existing traffic filter using the traffic filter.

[0030] According to the third aspect or any of the above implementations of the third aspect, in the eighth implementation of the CP, the service address includes an Internet Protocol address, a port address, and a protocol.

[0031] According to the third aspect or any of the above implementations of the third aspect, in the ninth implementation of the CP, it further includes: generating information associated with the flow filter by the CP.

[0032] According to the third aspect or any of the above-described implementations of the third aspect, in the tenth implementation of the CP, the information includes S-NSSAI.

[0033] According to a fourth aspect, an NF is provided. The NF includes: a non-transitory memory including instructions; one or more processors communicating with the memory, wherein the one or more processors execute the instructions to: receive a traffic filter for packets of at least one service flow associated with a communication device, the traffic filter including traffic impact routing rules specifying circumvention rules for packets destined for an application server; derive a network identifier associated with the traffic filter; and provide the network identifier and the traffic filter to the SMF.

[0034] According to the fourth aspect, in the first implementation of the NF, the network identifier includes DNAI.

[0035] According to the fourth aspect or any of the above implementations of the fourth aspect, in the second implementation of the NF, the traffic filter includes a service address and at least one gateway address.

[0036] According to the fourth aspect or any of the above implementations of the fourth aspect, in the third implementation of the NF, the traffic filter further includes network slice selection auxiliary information.

[0037] According to the fourth aspect or any of the above implementations of the fourth aspect, in the fourth implementation of the NF, providing the network identifier and the traffic filter includes initiating a session management policy control service.

[0038] The advantage of the preferred implementation is that the knowledge of the edge application service helps user plane functions (UPFs), such as uplink classifiers (ULCLs), to route traffic to the UPF PDU session anchor (PSA) serving the edge location. Directing traffic to the UPF-PSA serving the edge location enables the selection of a local application service server, thereby reducing routing-related costs and latency. Attached Figure Description

[0039] To gain a more complete understanding of the invention and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:

[0040] Figure 1 A first exemplary communication system is shown;

[0041] Figure 2 A communication system supporting edge computing (EC) and edge application server (EAS) is illustrated, which supports existing technologies for programming and advertising routes;

[0042] Figure 3 A communication system is illustrated that supports programming the presence of EAS into the uplink classifier (ULCL) according to an exemplary implementation proposed herein, enabling the ULCL to make appropriate traffic steering decisions;

[0043] Figure 4 A diagram illustrating messages and processes performed by entities and functions of a communication system configured with traffic steering rules, according to an exemplary embodiment presented herein;

[0044] Figure 5 A communication system is shown that highlights a network segment according to an exemplary implementation proposed herein and maps adjacent EAS to a data network having a data network access identifier (DNAI).

[0045] Figure 6 The diagram illustrates the messages and processes shared by entities and functions of a communication system that updates user equipment (UE) policies and establishes segmented packet data unit (PDU) sessions, according to an exemplary embodiment presented herein.

[0046] Figure 7A diagram illustrating messages and processes performed by entities and functions of a communication system participating in a relocation server, according to an exemplary embodiment presented herein;

[0047] Figure 8A This illustrates the first communication system that emphasizes local access;

[0048] Figure 8B A first communication system emphasizing adjacent access is illustrated; in the communication system, according to the exemplary implementation presented herein, the UE connects to a data network and obtains services from the EAS via a stream;

[0049] Figure 9A A second communication system highlighting local access to the data network is shown;

[0050] Figure 9B A second communication system for prominent adjacency access to a data network is illustrated according to an exemplary embodiment proposed herein;

[0051] Figure 10 A communication system with a prominent exemplary configuration, as well as PDU sessions and application flows, is illustrated according to the exemplary embodiments presented herein;

[0052] Figure 11 A flowchart is shown illustrating exemplary operations performed in the network exposure function (NEF) according to an exemplary implementation of the present document;

[0053] Figure 12 A flowchart is shown illustrating exemplary operations performed in a policy control function (PCF) according to an exemplary implementation of the present document;

[0054] Figure 13 A flowchart is shown illustrating exemplary operations performed in the PCF of the Participation Partitioning Model (PDU) session establishment and traffic routing according to an exemplary implementation of the present document;

[0055] Figure 14 A flowchart is shown of exemplary operations performed in the session management function (SMF) of the participation partitioning model PDU session establishment and traffic routing according to the exemplary implementation proposed herein;

[0056] Figure 15 An exemplary communication system according to an exemplary embodiment presented herein is illustrated;

[0057] Figure 16A and Figure 16BExemplary devices are shown that can implement the methods and teachings according to this disclosure; and

[0058] Figure 17 This is a block diagram of a computing system that can be used to implement the devices and methods disclosed herein. Detailed Implementation

[0059] The structure and uses of the disclosed embodiments are described in detail below. However, it should be understood that the present invention provides many applicable concepts that can be implemented in a wide variety of specific contexts. The specific embodiments described are merely illustrative of the specific structure and use of the embodiments and do not limit the scope of the invention.

[0060] Figure 1 A first exemplary communication system 100 is illustrated. The communication system 100 includes an access node 110 having a coverage area 101, serving user equipment (UE), such as UE 120. Access node 110 is connected to a backhaul network 115, which provides connectivity to services and the Internet. In a first operating mode, communication to and from the UE passes through access node 110. In a second operating mode, communication to and from the UE does not pass through access node 110; however, access node 110 typically allocates resources for communication by the UE when specific conditions are met. In the second operating mode, communication between UE pairs occurs on a sidelink 125, which includes a unidirectional communication link. Communication between the UE and the access node pair also occurs via a unidirectional communication link, wherein the communication link between the UE and the access node is referred to as uplink 130, and the communication link between the access node and the UE is referred to as downlink 135.

[0061] Access nodes are typically also referred to as Node B, evolved Node B (eNB), next generation (NG) Node B (gNB), master eNB (MeNB), secondary eNB (SeNB), master gNB (MgNB), secondary gNB (SgNB), network controller, control node, base station, access point, transmission point (TP), transmission-reception point (TRP), cell, carrier, macro cell, femtocell, picocell, etc. UEs are also commonly referred to as mobile stations, mobile phones, terminals, users, subscribers, sites, etc. Access nodes can provide wireless access according to one or more wireless communication protocols, such as 3GPP Long Term Evolution (LTE), LTE-A, 5G, 5G LTE, 5G NR, Sixth Generation (6G), High Speed ​​Packet Access (HSPA), and IEEE 802.11 series standards, such as 802.11a / b / g / n / ac / ad / ax / ay / be, etc. While it is understood that a communication system could employ multiple access nodes capable of communicating with multiple UEs, for simplicity, only one access node and two UEs are shown.

[0062] As mentioned above, edge computing (EC) services and application services use anycast or unicast Internet Protocol (IP) addresses to represent service addresses. Application server (AS) availability is programmed into the routing controller and advertised using the Border Gateway Protocol (BGP) (or Interior Gateway Protocol (IGP)). This provides a scalable and flexible way for users to access the AS.

[0063] IP packet connections to the edge application server (EAS) (at the mobile edge) span from the UE to the user plane function (UPF), such as the uplink classifier (ULCL) UPF, which can direct traffic to the local UPF packet data unit (PDU) session anchor (PSA) or forward traffic to the central UPF PSA. However, because routes corresponding to the service destination (e.g., the EAS) are advertised using BGP, IGP, etc., the ULCL UPF is unaware of these routes. Therefore, unless the ULCL UPF knows the route corresponding to the EAS located at the edge, it will be unable to direct packets to the EAS.

[0064] Figure 2 A communication system 200 supporting EC and EAS is illustrated. The communication system 200 supports existing technologies for programming and advertising routes. The communication system 200 includes an application service 205. The application service 205 provides one or more servers to support applications or services and includes an application function (AF) 207 that interacts with the 5G core (5GC) control plane (CP) 209 via a network exposure function (NEF) 211 to access network capabilities. The AF 207 also interacts with local data networks (L-DNs) or local data centers (such as L-DN1 213 and L-DN2 215) and centrally located data networks (C-DNs) or data centers (such as C-DN 217). The L-DN includes EASs, such as EAS 219 and EAS 221, and is connected to the IP network via gateways (GWs), such as GW 223 and 225. The C-DN 217 includes a first autonomous system 227 associated with a first IP address and a second autonomous system 229 associated with a second IP address; however, the C-DN can include any number of autonomous systems associated with IP addresses (e.g., one, two, three, four, etc.). The C-DN 217 is connected to the IP network 231 via GW 233.

[0065] In addition to NEF 211, which provides external interfaces for edge network services and capabilities, 5GC CP 209 also includes a unified data repository (UDR) 235 (which can be a database of 5G-specific information), a policy control function (PCF) 237 (which is a control plane network function for controlling user and network policies), an access and mobility management function (AMF) 239 (which handles requests related to connectivity and mobility management), and a session management function (SMF) 241 (which handles requests related to session management).

[0066] The communication system 200 also includes UEs (e.g., UEs 243 and 245). The UEs connect to the IP network via access nodes and a UPF uplink classifier (ULCL), which forwards traffic to a local UPF PDU session anchor (PSA). For example, traffic from UE 243 reaches IP network 253 via access node 247, ULCL 249, and PSA 251.

[0067] Existing technologies involving programming and notification routing include:

[0068] Application Domain Service Configuration (Event 260) – AF 207 Provisioning servers in L-DN and C-DN. Provisioning includes service addresses advertised in a set of networks identified by an autonomous system number (ASN).

[0069] Domain Name Server (DNS) Provisioning (Event 262): AF 207 provisioned authoritative DNS (ADNS) 264 for the service. When a query is made using the service's fully qualified domain name (FQDN), ADNS 264 replies to the DNS resolver using the service's service address.

[0070] Application domain affects traffic routing (Event 266) — AF 207 installs traffic routing at NEF 211.

[0071] Mobile network installs routing rules (Event 268) - Routing rules are announced.

[0072] Directing application traffic (Event 270) – Data packets are sent to PSA 272, where they are then forwarded to the nearest EAS, AS 227. Since the data packets are sent to PSA 272, they are further forwarded to AS 227, which is the closest EAS to PSA 272, but may not be the desired outcome. The path taken by the data packets is shown as dashed line 274. Examples of expected results include lower latency, lower cost, load balancing, and improved network utilization.

[0073] Therefore, there is a need for methods and apparatus for directing sessions to application servers.

[0074] According to exemplary embodiments, methods and apparatus are provided for programming the presence of an EAS into a ULCL, enabling the ULCL to make appropriate traffic steering decisions. The ULCL can be programmed to have an EAS present, allowing the ULCL to make traffic steering decisions for different deployment scenarios, such as public routable applications, private applications with message-based security, virtual private network (VPN) access, etc. The new ULCL can configure traffic filters to guide traffic and support user (i.e., UE) mobility.

[0075] In this implementation, the application domain influences traffic routing within the mobile network. For example, service addresses and locations within the application domain are used to route traffic. These service addresses and locations are provided to the mobile network operator (MNO), such as 5GC CP 209, so that traffic for a PDU session can be routed, for example, using the service address and location. IP routing control mechanisms can be used to advertise routes. In this implementation, ULCL does not have an IP routing control mechanism, therefore an extension to the influence of AF traffic is provided. Details of an exemplary extension to the influence of AF traffic are provided below.

[0076] In this implementation, service routing and traffic steering rules generated based on the service address (server IP address) and location in the application domain are provided to the user plane, such as ULCL. For example, service routing and traffic steering rules can be provided when the UE establishes a PDU session. Details of exemplary service routing and traffic steering rules provided during PDU session establishment are shown below. These examples may also be applicable to deployments with distributed PSAs and no ULCL.

[0077] In this implementation, information related to the service address and location of the mobile edge application domain is translated, stored, and dispatched in the 5GC and user plane to direct data traffic to the nearest EAS.

[0078] In this implementation, data packets with destination addresses on edge data networks (e.g., L-DN 213 and 215) are directed to a local PSA (e.g., a global PSA, such as PSA 272) using configured traffic routing rules. Data packets are routed from the local PSA to the nearest EAS. For example, routing to the nearest EAS can be performed using standard IP anycast routing.

[0079] In this implementation, the Application Firewall (AF) in the application domain dispatches servers in a data center (on-premises or in the cloud) to generate a new request to the 5GC. This request provides the 5GC with a service address (e.g., an IP anycast address) and the dispatched server's data network access identifier (DNAI). For example, the AF uses the IP network's ASN to translate the DNAI. Furthermore, the AF can use this interface to update and delete servers when they are removed or fail.

[0080] In this implementation, the NEF supports handling new requests from the AF. No additional services are required at the NEF. The NEF adds network slice selection assistance information (NSSAI) or a single NSSAI (S-NSSAI) and forwards the requests as usual.

[0081] In its implementation, UDR stores new information as application data, AF transactions, or S-NSSAI and data network name (DNN). Other fields in the dataset include service address (IP anycast address), list of required DNAIs, etc.

[0082] In this implementation, the PCF follows existing procedures to subscribe to AF traffic impact requests. The PCF identifies a set of DNAIs that are close to each data network location (e.g., GW address). Determining the proximity of DNAIs and GW addresses (e.g., data network locations) involves the PCF obtaining a list of DNAIs and GWs that are topologically or administratively close to the OAM. For example, this information may be obtained as part of a configuration process. The PCF organizes the received information into a service address list (srv-IP-addr) for each DNAI.

[0083] In this implementation, the SMF receives a dataset for each DNAI, which contains a list of service addresses (e.g., IP addresses or IP anycast addresses) used for edge application routing. The SMF can select a local PSA located near the DNAI and construct a forwarding action rule (FAR) to be inserted into the ULCL. All service IP addresses (i.e., local PSAs) of the DNAI for which the PDU session terminates are inserted into the ULCL as FARs.

[0084] Figure 3 A communication system 300 is illustrated that supports programming the presence of an EAS into a ULCL, enabling the ULCL to make appropriate traffic guidance decisions. The communication system 300 includes various entities or functions, wherein entities or functions of the communication system 300 that share reference numerals with those of the communication system 200 behave similarly.

[0085] like Figure 3 As shown, AF 305 configures application domain services (Event 260). AF 305 provisiones servers in data centers (e.g., L-DN and C-DN). Provisioning includes specifying the service address (e.g., IP anycast address) centrally advertised through the network identified by the ASN.

[0086] AF 305 also dispatches DNS (Event 262). For example, ADNS 264 is the authoritative DNS for a service, ensuring that when a query is made using an FQDN specific to that service, ADNS 264 will respond to the DNS resolver using the service address associated with the service. ADNS 264 can be hosted or managed within the application domain.

[0087] AF 305 forwards the service address and location in the application domain to the MNO (Event 307). The service address and location in the application domain are forwarded to the MNO to direct data traffic for the PDU session. Normally, IP routing control mechanisms are used to advertise routes. However, since ULCL does not support IP routing control mechanisms, an extension of AF traffic impact is used.

[0088] For example, service addresses and locations in the application domain can be transmitted to NEF 309 of 5GC CP 209. NEF 309 provides service addresses and locations to UDR 235, PCF 237, and SMF 311. For example, 5GC CP 209 provides service addresses and locations to ULCLs such as ULCL 315 via SMF 311. For example, traffic routing rules associated with service addresses and locations are installed in the ULCLs. In one implementation, SMF 311 provides traffic routing rules associated with service addresses and locations to all ULCLs of communication system 300. In another implementation, SMF 311 provides traffic routing rules associated with service addresses and locations only to those ULCLs of communication system 300 that process data packets destined for services associated with service addresses and locations.

[0089] Data packets with a destination address to an edge data network (e.g., L-DN 213) are routed according to the traffic routing rules provided to ULCL by SMF 311 (Event 317). For example, data packets from UE 243 with a destination address for a service supported by a server in L-DN 213 of EAS-1 219 are routed to PSA 251 by ULCL 315 instead of PSA 272. The data packets are routed from PSA 251 to EAS-1 219 via GW 225. For example, the route to EAS-1 219 can use standard IP routing. The path of data packets from UE 243 with a destination address of L-DN 213 is... Figure 3 The number 319 is shown as a dashed line in the middle.

[0090] In this implementation, traffic routing rules (e.g., service routing) are configured by the application domain to influence traffic routing within the MNO. Configuring traffic routing rules in the application domain allows data packets to be routed based on their destination address.

[0091] Figure 4 Figure 400 illustrates the messages shared and the processes performed by entities and functions of a communication system that configure traffic steering rules. Entities and functions involved in configuring traffic steering rules include (e.g., UE 243) UPF 405, SMF 311, PCF 237, UDR 235, NEF 309, and AF 305.

[0092] AF 305 coordinates and configures applications in EAS and AS across different data center locations by generating AF requests (Box 410). This service can be exposed via DNS using an IP anycast service address (e.g., srv-IP-addr). For example, AF 305 uses the service or FQDN and address resolution configuration information to srv-IP-addr at ADNS 264.

[0093] AF 305 provides the MNO with application-related information (Event 412). For example, AF 305 provides information related to an IP anycast service address (e.g., srv-IP-addr) associated with the application. AF 305 also provides information about the L-DN location configured for the application. This information may include a list of L-DN locations or their respective Gateways. This information may be provided to the MNO in an AF information request, such as the Nnef_TrafficInsight_Create request message (e.g., NEF 309). Alternatively, the Nnef_TrafficInfluence_Update or Nnef_TrafficInfluence_Delete request messages may be used. In cases where multiple service addresses or redirect addresses exist in the EAS or AS, AF 305 can provide all relevant service addresses and provide information related to those service addresses to the MNO. Furthermore, FQDNs may not be included in the information provided by AF 305, as routes affected by the AF do not require FQDNs.

[0094] NEF 309 performs authorization control and adds slice information to the information provided by AF 305 (box 414). Slice information includes NSSAI or S-NSSAI. NEF 309 also stores information requests from AF 305. For example, information requests from AF 305 may be stored in UDR 235. Information requests stored at UDR 235 may include datasets, subsets, or keys. Section 4.3.6 of 3GPP TS 23.502 specifies the storage of information requests, the entire contents of which are incorporated herein by reference. NEF 309 also sends responses to AF information requests (event 416). Responses to AF information requests may be the Nnef_TrafficInsight_Create response message. Alternatively, the Nnef_TrafficInfluence_Update or Nnef_TrafficInfluence_Delete response messages may be used.

[0095] The notification has been subscribed to by PCF 237 (Event 418) regarding modifications to the dataset or subset affected by AF traffic. PCF 237 can be notified by UDR 235 using the Nudr_DM_Notify message. The Nudr_DM_Notify message includes NSSAI, srv-IP-addr, and information about the L-DN location. PCF 237 determines the DNAI of the data network (Box 420). PCF 237 can determine a set of DNAIs for the data network adjacent to each L-DN location (i.e., GW address). PCF 237 can obtain a list of DNAIs and GWs that are topologically or administratively close to operations, administration, and maintenance (OAM) as part of the configuration process. If the DNAIs of the data network and GW are managed by a single entity or multiple related entities, they are administratively closed. PCF 237 also stores the list of storage addresses (e.g., srv-IP-addrs) and DNAIs.

[0096] PCF 237 identifies PDU sessions affected by the new AF traffic impact dataset (Event 422). For example, PCF 237 identifies PDU sessions affected by the new AF traffic impact dataset by detecting PDU sessions with application destination addresses. For example, PCF 237 updates SMF 311 with new policy and charging control (PCC) rules for each PDU session identified as affected by the new AF traffic impact dataset.

[0097] SMF 311 reconfigures UPF 405 (step 424). For example, SMF 311 reconfigures UPF 405 for each received PCC rule. In relation to a PDU session modification for which a central PSA has already been established, SMF 311 combines the ULCL and the local PSA. In relation to a new PDU session, SMF 311 can establish a central PSA, as well as the ULCL and the local PSA. In the event of a PCC rule update due to a failure, SMF 311 can reselect either the local PSA or the ULCL.

[0098] The aforementioned entities and functions share messages and perform processing that utilize the basic AF (Automatic Assist) effect on traffic routing for PDU sessions not identified by the UE address, as detailed in Section 4.3.6.2 of 3GPP TS 23.502, the entire contents of which are incorporated herein by reference. As discussed, routing information corresponding to the services configured at the data network with a specific DNAI in the application domain is provided.

[0099] The messages and processes shared and executed by the aforementioned entities and functions can be used for publicly accessible or private applications. For example, a dedicated deployment with a VPN will only open the VPN connection GW. For a private deployment with zero trust and more granular access, each service with access can be opened individually (e.g., DNS queries over HTTPS (DoH), application services, etc.).

[0100] In the implementation, methods and apparatus are provided for determining the proximity of a data network to specific DNAI and L-DN locations. Figure 4 In box 420, PCF 237 determines the DNAI of GW and data network that are topologically or administratively close to each other. Exemplary techniques for determining proximity are provided below.

[0101] EAS and UPF are on different network segments. However, they can still be close in terms of topology or management. Figure 5 A communication system 500 is shown that highlights network segments and maps adjacent EAS to a data network with DNAI. The communication system 500 includes various network segments 505 hosting 5GC network functions, UPF, etc., and other network segments 507 hosting EAS, with a local IP network 509 in between. The ASN of the local IP network 509 is 123.

[0102] The OAM (e.g., implemented in 5GC 505) configures and manages the device and knows the administrative and topological distances between GWs (e.g., GW 511) in a data network (e.g., data network 515) with a specific DNAI, as well as between the GW and the local PSA (e.g., PSA 513). The OAM uses distance information (related to administrative and topological distances) to configure all nearby GWs for the PCF. For example, the OAM uses proximity information to configure the PCF: data network 515 (DNAI=D1) = (GW-1 511, GW-2 523, GW-3 525, GW-4 527, and GW-5 529), and the proximity information for data networks 517 (DNAI=D2) and 519 (DNAI=D3) is also equivalent to the proximity information for data network 515 (DNAI=D1). However, the proximity information for data network 521 (DNAI=D4) = (GW-11 531 and GW-12 533), which is related to... Figure 5 The proximity information for the other data networks shown is different.

[0103] like Figure 5As shown, GW-1 511 and GW-2 523 are connected to IP network 509, therefore GW-1 511 and GW-2 523 are close to each other. The data network is configured by OAM in UPF 405, while PCF 237 obtains a list of GWs connected to networks with a specific ASN, and a list of PSAs that have or do not have a nearest GW.

[0104] The proximity of data networks with specific DNAIs and GWs allows for routing configuration in SMF 311 during PDU session establishment. Details are as follows.

[0105] In implementation, PDU sessions following the partitioning model (where there is a default path from the UE (e.g., UE 243) to the central PSA (e.g., PSA 272) and another path from the UE to the local PSA (e.g., PSA 251)) need to have routing rules configured at the ULCL to support selective traffic routing to local destinations.

[0106] Figure 6 Figure 600 illustrates the shared messages and processes performed by the entities and functions of the communication system that update UE policies and establish partitioned PDU sessions. The entities and functions involved include UE 243, Access Node 605 of L-DN 213, UPF 607 of L-DN 213, EAS 609 of L-DN 213, AMF 239, SMF 311, PCF 237, and DNS 264.

[0107] UE 243 registers with AMF 239 (Box 610). For example, UE 243's registration with AMF 239 can utilize the process described in Section 4.2 of 3GPP TS23.502, the entire contents of which are incorporated herein by reference. Additionally, UE 243 can be configured or dynamically provided with UE route selection policy (URSP) rules that indicate network slices (e.g., network slices identified by S-NSSAI) for edge applications or subsets of applications.

[0108] UE 243 sends a PDU session establishment request (Event 612). The PDU session establishment request is sent to AMF 239. UE 243 can launch the application and select S-NSSAI for the PDU session. The PDU session establishment request is sent with the network slice identified by S-NSSAI. AMF 239 selects an SMF (e.g., SMF 311) and sends a request message to SMF 311 (Event 614). For example, the request message is an Nsmf_PDUSession_CreateSMContext request.

[0109] SMF 311 selects a PCF (e.g., PCF 237) and requests a policy for the PDU session (Event 616). For example, SMF 311 sends an Npcf_SMPolicy_Control request message to PCF 237 to request a policy for the PDU session. The PDU session is associated with S-NSSAI. PCF 237 obtains the policy (Box 618). PCF 237 obtains the policy for the PDU session. The policy obtained by PCF 237 includes a list of service IP addresses of the data network with DNAI. PCF 237 sends the policy to SMF 311 (Event 620). For example, PCF 237 sends an Npcf_SMPolicy_Control response message to send the policy to SMF 311. The Npcf_SMPolicy_Control response message includes the policy for the PDU session.

[0110] SMF 311 selects a UPF (e.g., UPF 607) (Box 622). SMF 311 selects UPF 607, for example, according to the technology described in Section 4.3.2.2.1 of 3GPP TS 23.502, the entire contents of which are incorporated herein by reference. In addition to the UPF selection, SMF 311 also selects a local PSA, which may also be selected based on the DNAI FAR of the data network in the srv-IP-addr in ULCL.

[0111] SMF 311 programs UPF 607 (Event 624). Programming of UPF 607 can be performed via the N4 interface. SMF 311 provides the local and central PSAs as defined in 3GPP TS 23.502, the entire contents of which are incorporated herein by reference. Additionally, ULCL configures DNAI FAR traffic filters for destination addresses corresponding to the service IP address list. This specific operation is forwarded to the local PSA.

[0112] The PDU session establishment process is complete (Box 626).

[0113] UE 243 sends a DNS query via the established PDU session (Event 628). The DNS query can be sent by UE 243 as an application message. If no routing rule exists for the DNS destination address, the application message (with the DNS query) is forwarded to the central PSA (e.g., PSA 272). However, if a routing rule exists for the DNS destination address (e.g., DoH in a private network), the ULCL (e.g., ULCL 315) forwards the application message to the local PSA (e.g., PSA 251). In the case of a VPN, all application messages will be forwarded to the matching destination address. Support for Do53, DNS over Transport Layer Security (DoT), and DoH is provided because there is no need to inspect DNS messages (e.g., DNS queries or DNS responses). UE 243 receives a DNS response (Event 630). For example, the DNS response may include an Authentication (A) or Authentication / Authorization / Accounting (AAA) record srv-IP1.

[0114] UE 243 sends an application request with a destination address of srv-IP1 (Event 632). For example, the application request is sent to UPF 607. UPF 607 checks the rules to determine a match with srv-IP1 (Box 634). If a successful rule match exists, UPF 607 forwards the application request to the local PSA, which in turn forwards the application request to EAS 609 (Event 636). A response to the application request is provided to UE 243.

[0115] In this implementation, the server can be relocated as needed. The application domain determines which server should be relocated to support the local network with segmented PDU sessions.

[0116] Figure 7 Figure 700 illustrates the messages shared and the processes performed by the entities and functions of the communication system participating in the relocation server. The entities and functions participating in the relocation server include UE 243, the first ULCL 705 of the current UPF 707, the first PSA 709 of the current UPF 707, the second ULCL 711 of the next UPF 713, the second PSA 715 of the next UPF 713, the first EAS 717 of the first L-DN 719, and the second EAS 721 of the second L-DN 723.

[0117] UE 243 establishes a PDU session (box 720). UE 243 attaches the PDU session and establishes it on the first PSA 709 of UPF 707, with the address UE-IP1. UE 243 also initiates an application. The application has DNS translation with an anycast address. The first EAS 717 can provide a redirect address, allowing the server (first EAS 717) to remain sticky even after the UE moves. Server stickiness means that the server will not relocate after the UE moves.

[0118] UE 243 sends an application message with anycast destination address A-IP (Event 722). The application message with anycast destination address A-IP matches the filtering rules at the first ULCL 705, and the first ULCL 705 forwards the application message to the first PSA 709. The router in the first L-DN 719 uses the anycast route to forward the application message to the first EAS 717.

[0119] The first EAS 717 notifies the AF (e.g., AF 305) of the IP address of UE 243 (box 724). AF notification can be performed in the application domain using application domain signaling. If the AF evaluates that a better EAS exists than the first EAS 717 (e.g., a second EAS 721), the AF can initiate a server relocation procedure.

[0120] For discussion purposes, consider the scenario where the AF initiates the server relationship process. UE 243 participates in the handover to a new access network or RAN (box 726). Furthermore, a second PSA 715 is selected. As a result of the handover, UE 243 has a new IP address, UE-IP2. The handover can be performed as specified in 3GPP TS 23.502. The old UPF (e.g., the first UPF 707) can be deleted after a delay. The removal of the old UPF may be as described below. Delaying the deletion of the old UPF can help minimize the loss of data packets in transit.

[0121] UE 243 continues sending application messages (Event 728). The new application message will be sent using the new IP address UE-IP2. The new application message includes the anycast destination address A-IP of the first EAS 717. In a typical request-response sequence, the first EAS 717 immediately knows the new IP address UE-IP2 because it is the source address in the request message. However, if the application mode is downlink biased (e.g., multicast video delivery) or notification, UE 243 may send a new request (e.g., subscription, multicast status report change, etc.) to initiate a redirect to the new UE location or new PSA (post-handover). UE 243's action informs the first EAS 717 of UE 243's new IP address.

[0122] The first EAS 717 notifies the AF of the new IP address of UE 243 (box 730). Application domain signaling can be used to notify the AF of the new IP address of UE 243. The AF re-evaluates either the first EAS 717 or the first L-DN 719. For discussion purposes, the AF determines that a relocation to the second EAS 721 is necessary.

[0123] Perform the process of reselecting the EAS (box 732). The reselection of the EAS involves the AF, the first EAS 717 (current EAS), and the second EAS 721 (target EAS). Initiate the mechanism for transmitting the context and related data of UE 243.

[0124] Once the second EAS 721 replicates the application state, the first EAS 717 sends an application layer redirection message (Event 734). The application layer redirection message is sent to UE 243 and may include the URL of the second L-DN 723 or the second EAS 721. UE 243 requests DNS translation of the URL (Box 736). For example, UE 243 may send a DNS request and receive a DNS response with the anycast address of the second L-DN 723.

[0125] UE 243 sends an application message (Event 738). The application message includes the source IP address of UE 243 (UE-IP2) and the destination address of the second L-DN 723. The destination address of the second L-DN 723 can be programmed in N6 to route to the second EAS 721 unless some kind of fault occurs. Therefore, the N6 router forwards the packet to the second EAS 721.

[0126] Access can take the form of local access or adjacency access. In local access, there is a one-to-one association between the 5GC and the edge application resource. However, in adjacency access, there are N-to-M associations between the 5GC and the edge application resource. The local access model means there is no separation between the 5GC and the edge application domain. This leads to security implications due to the lack of a separate policy domain. Each DNAI may need to have an edge application resource. The adjacency access model uses interconnection methods to separate multiple separate policy domains (e.g., ASN).

[0127] Mobility in communication systems supporting local access also leads to mobile EAS, which requires synchronization and complex signaling. Mobility in communication systems supporting adjacency access is independent of EAS relocation, thus eliminating complex signaling. Therefore, in the local access model, edge server relocation is complex because EAS relocation is coupled with local PSA relocation. This means that when a PDU session changes due to UE mobility, the EAS must be relocated. This can result in more jitter than simply moving one end. However, in the adjacency access model, there is a clear separation between the two domains, and an optimal routing method exists between the two domains. Therefore, UE mobility and server relocation in each domain can be performed independently. There is no need to synchronize mobility between the two domains, resulting in lower transmission jitter during movement because only one end is moved.

[0128] When an edge computing component fails in a communication system utilizing local access, coordination with the 5GC may be required to recover the failed component. However, in a communication system utilizing adjacency access, component relocation during edge computing component failure is independent of the 5GC. Resource provisioning in a communication system utilizing local access involves controllers (i.e., the 5GC and the AF or edge controller) synchronizing resources in different domains. In a communication system supporting adjacency access, resource provisioning involves the 5GC and the AF or edge controller only coordinating route changes. This is called loose coordination. In the local access model, a failure of application domain resources may result in the relocation of PDU sessions or DNAIs. This can cause a range of problems because controllers in two different resource domains (i.e., the 5GC and the edge application) attempt to coordinate recovery. In the adjacency access model, the AF can redirect to the next best (or automatically via anycast) server without requiring modifications to the PDU session. Resource domains control their resources independently.

[0129] Figure 8A A first communication system 800 with prominent local access is shown. In the communication system 800, a data network 805 has DNAI=D1. In the data network 805, EAS 807 is connected to AF 809. ULCL 811 is aware of the presence of EAS 807 and routes traffic from an access node, such as access node 813, to EAS 807 via PSA 815.

[0130] Figure 8BA first communication system 850 with prominent adjacency access is illustrated. In communication system 850, UE 243 is connected to data network 855 and obtains service from EAS 867 via flow 859. UE 243 also obtains service from AS 861 via flow 863. Traffic on flow 859 is routed to EAS 867 via PSA 869, GW 871, and GW 873 by ULCL 865. Traffic on flow 863 is routed to AS 861 via GW 871, network 875, GW 877, network 879, and PSA 881 by ULCL 865.

[0131] Figure 9A A second communication system 900 is shown, highlighting local access to a data network. Communication system 900 includes UE 243 connected to EAS 905 on data network 907. Packets from UE 243 are routed to EAS 905 via PSA 911 via ULCL 909. EAS 905 is connected to AF 913 and AS 915 via network 917.

[0132] PSA 911 and EAS 905 are on the same network segment, so there may be security issues between them. Furthermore, AF 913 needs to access EAS 905 for provisioning. This access is not done through a PDU session because provisioning uses a network-to-network interface (NNI) instead of a user-to-network interface (UNI).

[0133] Figure 9B A second communication system 950 is shown that provides prominent access to a data network. Communication system 950 includes a UE 243 connected to an EAS 955 adjacent to a data network 957. ULCL 959 directs traffic from UE 243 to EAS 955 via PSA 961, network 965, and GW 967. EAS 955 is connected to AF 969 and AS 971 via network 973.

[0134] Because the PSA 961 and EAS 955 are on different network segments, different routing and security policies can be implemented in these segments. The PSA 961, Network 965, and EAS 955 can be implemented as part of a single data center, or as different ASNs, thus supporting different policies. Procurement is managed by the same GW (e.g., GW 975) that grants access to remote resources.

[0135] Another issue discussed in this paper is how to route traffic to the nearest EAS when segmenting PDU sessions (with ULCL) requires rules to selectively redirect traffic. Some existing techniques use DNS agents (e.g., proxies, inspectors, relays, etc.) located at or near the ULCL to inspect requests and determine the intended destination of DNS service requests. The exemplary implementations presented in this paper independently manage and extend DNS while supporting Do53, DoT, and DoH.

[0136] The disadvantages of the DNS method include:

[0137] - Because the DNS proxy checks every request (even those without edge deployment), it can lead to higher DNS resolution latency.

[0138] Reconfiguring access (PDU session) during DNS resolution will cause DNS resolution to take additional time (not just conversion).

[0139] Access may be redirected and reconfigured based on the DNS requests being checked, which may result in additional latency.

[0140] - A switch may occur during the switchover process because DNS processing is required to handle the selection.

[0141] - Privacy may not be supported; for example, when using DoH, the resolver may be located on a third-party network. Alternatively, if a VPN is used, DNS requests may be invisible.

[0142] The exemplary implementation methods presented herein are characterized by:

[0143] - Routes in ULCL are allocated during PDU session processing. Therefore, there is no delay in processing DNS requests, as only DNS translation needs to be performed.

[0144] - No need to reconfigure access during DNS resolution.

[0145] - DNS resolvers can be deployed independently to improve scalability and resilience, without the need to place checkers near every access or UPF.

[0146] The switch will not be interrupted because DNS translation (IP address) remains effective even after the move.

[0147] - Because DNS requests are not checked, DoH, DoT, or DNS in a VPN can work without other changes.

[0148] Figure 10The communication system 1000 with a prominent exemplary configuration, along with PDU sessions and application flows, are shown. In event 1005, the interaction between AF 305 and 5GC 209 involves traffic-influenced routing with service IP addresses and data network locations. In this case, the dataset includes (IP-a, {data network 213, data network 217}), (IP-b, {data network 215, data network 217}), and (IP-c, {data network 215}). AF 305 does not send FQDNs; contracts are used only for routing, thus information exchange is minimal. NEF 309, PCF 237, etc., add DNN and S-NSSAI, and organize information according to DNAI.

[0149] In event 1007, UE 243 requested PDU session establishment ( Figure 10 (Not shown in the image), SMF 311 acquires policies including traffic-affected routing rules. SMF 311 selects UPFs (PSA 251 and 272, and ULCL 315) based on DNAI, etc. ULCL 315's N4 matching action filters: {IP-a, PSA 251}, {IP-b, PSA 251}, and {IP-c, PSA 251}.

[0150] In event 1009, UE 243 requests DNS 1011 to resolve the FQDN. DNS 1011 forwards the FQDN to ADNS264, which responds with IP-a. ULCL 315 has no filtering rules, so the DNS request is not redirected in this case. For private networks, VPNs, etc., DNS requests can also be redirected based on the influence of AF traffic on routing.

[0151] In event 1013, UE 243 sends an application request with a destination address of IP-a. ULCL 315 filters based on {IP-a, PSA251} and redirects to PSA 251. The local N6 network advertisement for anycast IP address IP-a (BGP, SDN) is forwarded to EAS219.

[0152] exist Figure 10 In the data network, AF 305 has already configured services (events 1015 and 1017). In event 1015, two services were configured: one with anycast IP address IP-a and the other with anycast IP address IP-b. ADNS 264 configured the corresponding FQDN and the resolution for IP-a and IP-b in event 1017.

[0153] Figure 11A flowchart of an exemplary operation 1100 occurring in NEF is shown. Operation 1100 may indicate an operation performed in NEF, such as NEF 309, when NEF supports the configuration of auxiliary information to facilitate group guidance.

[0154] Operation 1100 begins by receiving the service address from the NEF (Box 1105). For example, the service address can be received from the AF. For example, the service address can represent the destination address of a route to the application server. The service address can be received in service operation messages such as Nnef_TrafficInfluence_Create, Nnef_TrafficInfluence_Update, or Nnef_TrafficInfluence_Delete. The service address is in the form of an IP anycast address; an example service address is srv-IP-addr. The NEF also receives a list of network identifiers (Box 1107). For example, a list of network identifiers can be received from the AF. The list of network identifiers identifies the local data network location that configures the service address. For example, the list of network identifiers can be a list of gateways for the local data network location. The service address and the list of network identifiers can be received in a single message or in separate messages. The NEF stores the service address at the PCF.

[0155] NEF generates traffic filters (Box 1109). NEF can generate traffic filters based on a list of service addresses and network identifiers, such as authorization controls. NEF generates information about the traffic filters (Step 1111). The traffic filter information may include S-NSSAI. The traffic filters and their information can be stored in the UDR. NEF sends a response (Box 1113). For example, a response can be sent to the AF. The response can be a service operation message, such as Nnef_TrafficInfluence_Create, Nnef_TrafficInfluence_Update, or Nnef_TrafficInfluence_Delete response messages.

[0156] Figure 12 A flowchart of an exemplary operation 1200 occurring in a PCF is shown. Operation 1200 may indicate operations performed in a PCF, such as PCF 237, when the PCF supports the configuration of auxiliary information to facilitate packet guidance.

[0157] Operation 1200 begins by receiving traffic filter information from the PCF (step 1205). For example, traffic filter information can be received from the UDR. This information can be received in a Nudr_DM_Nofity message and may include the S-NSSAI, the address of the service, and a list of network identifiers. The PCF derives the network identifiers (box 1207). Network identifiers can be a set of DNAIs that are close to each local data network location (e.g., gateway address). The DNAIs and gateways are topologically or administratively close to each other. The network identifiers and traffic filter information are collectively referred to as the AF traffic impact dataset.

[0158] The PCF stores network identifiers and traffic filter information (box 1209). Network identifier and traffic filter information (e.g., service addresses) can be stored in local storage. The PCF updates network identifier and traffic filter information (box 1211). For example, the network identifier and traffic filter information for a PDU session are referred to as the AF traffic impact dataset. If multiple PDU sessions are affected by the AF traffic impact dataset, multiple PDU sessions are updated. Different PDU sessions can be updated with different information.

[0159] Figure 13 A flowchart is shown of an exemplary operation 1300 performed in a PCF participating in partitioned model PDU session establishment and traffic routing. Operation 1300 can indicate operations performed in a PCF such as PCF 237 when the PCF participates in partitioned model PDU session establishment and traffic routing.

[0160] Operation 1300 begins with PCF participation in UE registration (Box 1305). The UE registers via AMF. In addition to registration, the UE is configured or dynamically provided with URSP rules indicating network slices for edge applications or subsets of applications (e.g., identified by S-NSSAI). PCF receives a policy creation request (Box 1307). The policy creation request can be received from the SMF selected for managing the PDU session. The policy creation request can be received as an Npcf_SMPolicy_Control message, such as the Npcf_SMPolicy_Control_Create request message. For example, the policy creation request includes S-NSSAI.

[0161] PCF retrieves the policy (step 1309). The PCF retrieves the policy for the PDU session. The policy may include the DNAI and a list of service addresses for the DNAI. The PCF sends a policy creation response (box 1311). The policy creation response can be sent to the SMF and includes the policy retrieved by the PCF. The policy creation response can be sent as an Npcf_SMPolicy_Control message, such as the Npcf_SMPolicy_Control_Create response message.

[0162] Figure 14 A flowchart is shown of an exemplary operation 1400 performed in an SMF involved in partitioned model PDU session establishment and traffic routing. Operation 1400 can refer to operations performed in an SMF such as SMF 311, since the SMF is involved in partitioned model PDU session establishment and traffic routing.

[0163] Operation 1400 begins with SMF participation in UE registration (Box 1405). The UE registers via AMF. In addition to registration, the UE is configured or dynamically provided with URSP rules indicating network slices for edge applications or application subsets (e.g., identified by S-NSSAI). The SMF receives a Service Context Request (Box 1407). The Service Context Request can be received from the AMF. The Service Context Request can be received in the Nsmf_PDUSession_CreateSMContext request message. The Service Context Request includes the S-NSSAI for edge applications or application subsets.

[0164] The SMF sends a policy creation request (Box 1409). The policy creation request can be sent to the PCF selected to manage the PDU session. The policy creation request can be sent as an Npcf_SMPolicy_Control message, such as an Npcf_SMPolicy_Control_Create request message. For example, the policy creation request includes S-NSSAI. The SMF receives a policy creation response (Box 1411). The policy creation response can be received from the PCF and includes the policy retrieved by the PCF (i.e., the list of service addresses for DNAIs and the DNAI). The policy creation response can be sent as an Npcf_SMPolicy_Control message, such as an Npcf_SMPolicy_Control_Create response message.

[0165] The SMF selects the local PSA (Box 1413). The local PSA can be selected by the ULCL based on the DNAI FAR and service address. The SMF participates in N4 session establishment (Box 1415). N4 session establishment involves the SMF programming the UPF through the N4 interface, where the UPF is programmed using the DNAI FAR and service address list. The SMF also allocates PSAs (local and central) and allocates FAR traffic filters for destination addresses corresponding to the service address list to the ULCL.

[0166] Figure 15 An exemplary communication system 1500 is illustrated. Typically, system 1500 enables multiple wireless or wired users to send and receive data and other content. System 1500 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

[0167] In this example, the communication system 1500 includes electronic devices (EDs) 1510a to 1510c, radio access networks (RANs) 1520a to 1520b, a core network 1530, a public switched telephone network (PSTN) 1540, the Internet 1550, and other networks 1560. Although Figure 15 A certain number of these components or elements are shown, but the system 1500 may include any number of these components or elements.

[0168] EDs 1510a to 1510c are configured to operate and / or communicate within system 1500. For example, EDs 1510a to 1510c are configured to transmit or receive via a wireless or wired communication channel. Each ED 1510a to 1510c represents any suitable end-user equipment and may include (or be referred to as) devices such as: user equipment (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, personal digital assistant (PDA), smartphone, laptop computer, computer, touchpad, wireless sensor, or consumer electronic device.

[0169] RAN 1520a and 1520b here include base stations 1570a and 1570b, respectively. Each base station 1570a and 1570b is configured to have a radio connection with one or more ED 1510a to 1510c to enable access to the core network 1530, PSTN 1540, Internet 1550, and / or other networks 1560. For example, base stations 1570a and 1570b may include one or more of several well-known devices, such as a base transceiver station (BTS), Node-B (NodeB), evolved NodeB (eNodeB), next-generation (NG) NodeB (gNB), home NodeB, home eNodeB, site controller, access point (AP), or wireless router. ED 1510a to 1510c are configured to connect and communicate with the Internet 1550 and can access the core network 1530, PSTN 1540 or other networks 1560.

[0170] exist Figure 15 In the illustrated embodiment, base station 1570a constitutes part of RAN 1520a, which may include other base stations, components, and / or equipment. Similarly, base station 1570b constitutes part of RAN 1520b, which may include other base stations, components, or equipment. Base stations 1570a and 1570b operate independently, transmitting or receiving radio signals within a specific geographic region or area (sometimes referred to as a "cell"). In some embodiments, multiple-input multiple-output (MIMO) technology may be employed, with each cell having multiple transceivers.

[0171] Base stations 1570a to 1570b communicate with one or more of ED 1510a to 1510c via one or more air interfaces 1590 using wireless communication links. Air interface 1590 can utilize any suitable wireless access technology.

[0172] System 1500 is envisioned to utilize multi-channel access capabilities, including the schemes described above. In a specific implementation, the base station and ED implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and radio protocols can also be used.

[0173] RANs 1520a and 1520b communicate with the core network 1530 to provide voice, data, application, Voice over Internet Protocol (VoIP), or other services to EDs 1510a through 1510c. It should be understood that RANs 1520a and 1520b or the core network 1530 can communicate directly or indirectly with one or more other RANs (not shown). The core network 1530 can also serve as a gateway access for other networks (such as PSTN 1540, Internet 1550, and other networks 1560). Additionally, some or all of EDs 1510a through 1510c may include the ability to communicate with different wireless networks via different wireless links using different wireless technologies and / or protocols. Instead of wireless communication (or otherwise), EDs can communicate with service providers or switches (not shown) and Internet 1550 via wired communication channels.

[0174] Although Figure 15 An example of a communication system is shown, but it is possible to... Figure 15 Various modifications can be made. For example, the communication system 1500 can include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0175] Figure 16A and Figure 16B Exemplary devices are shown that can implement the methods and teachings according to this disclosure. In particular, Figure 16A An exemplary ED 1610 is shown, and Figure 16B An exemplary base station 1670 is shown. These components can be used in system 1500 or any other suitable system.

[0176] like Figure 16AAs shown, ED 1610 includes at least one processing unit 1600. The processing unit 1600 implements various processing operations of ED 1610. For example, the processing unit 1600 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables ED 1610 to operate in system 1500. The processing unit 1600 also supports the methods and teachings described in more detail above. Each processing unit 1600 includes any suitable processing or computing device configured to perform one or more operations. For example, each processing unit 1600 may include a microprocessor, microcontroller, digital signal processor, field-programmable gate array, or application-specific integrated circuit.

[0177] ED 1610 also includes at least one transceiver 1602. Transceiver 1602 is configured to modulate data or other content for transmission via at least one antenna or Network Interface Controller (NIC) 1604. Transceiver 1602 is also configured to demodulate data or other content received by at least one antenna 1604. Each transceiver 1602 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received wirelessly or wiredly. Each antenna 1604 includes any suitable structure for transmitting or receiving wireless or wired signals. One or more transceivers 1602 and one or more antennas 1604 may be used in ED 1610. Although transceiver 1602 is shown as a single functional unit, it may also be implemented using at least one transmitter and at least one separate receiver.

[0178] ED 1610 also includes one or more input / output devices 1606 or interfaces (e.g., wired interfaces to the Internet 1550). Input / output devices 1606 facilitate interaction with users or other devices on the network (network communication). Each input / output device 1606 includes any suitable structure for providing or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touchscreen, including network interface communication.

[0179] In addition, ED 1610 includes at least one memory 1608. Memory 1608 stores instructions and data used, generated, or collected by ED 1610. For example, memory 1608 may store software instructions or firmware instructions executed by processing unit 1600, as well as data for reducing or eliminating interference in incoming signals. Each memory 1608 includes any suitable volatile or non-volatile storage and retrieval device. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, etc.

[0180] like Figure 16B As shown, base station 1670 includes at least one processing unit 1650, at least one transceiver 1652, the transceiver 1652 including the functions of a transmitter and receiver, one or more antennas 1656, at least one memory 1658, and one or more input / output devices or interfaces 1666. A scheduler, as will be understood by those skilled in the art, is coupled to processing unit 1650. The scheduler may be included within or operate independently of base station 1670. Processing unit 1650 implements various processing operations of base station 1670, such as signal encoding, data processing, power control, input / output processing, or any other function. Processing unit 1650 may also support the methods and teachings described in more detail above. Each processing unit 1650 includes any suitable processing or computing device configured to perform one or more operations. For example, each processing unit 1650 may include a microprocessor, microcontroller, digital signal processor, field-programmable gate array, or application-specific integrated circuit.

[0181] Each transceiver 1652 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 1652 also includes any suitable structure for processing signals received wirelessly or wiredly from one or more EDs or other devices. Although the transmitter and receiver are shown as a combined transceiver 1652, the transmitter and receiver can be separate components. Each antenna 1656 includes any suitable structure for transmitting or receiving wireless or wired signals. Although the common antenna 1656 shown herein is coupled to the transceiver 1652, one or more antennas 1656 can be coupled to the transceiver 1652 if configured as separate components, allowing individual antennas 1656 to be coupled to both the transmitter and receiver. Each memory 1658 includes any suitable volatile or non-volatile storage and retrieval device. Each input / output device 1666 facilitates interaction with users or other devices in the network (network communication). Each input / output device 1666 includes any suitable structure for providing information to or receiving / from a user, including network interface communication.

[0182] Figure 17 This is a block diagram of a computing system 1700 that can be used to implement the devices and methods disclosed herein. For example, the computing system can be any entity in a UE, access network (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS). A particular device may utilize all of the components shown or only a subset of these components, and the degree of integration between devices may vary. Furthermore, the device may include multiple component instances, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 1700 includes a processing unit 1702. The processing unit includes a central processing unit (CPU) 1714, a memory 1708, and may also include a mass storage device 1704 connected to a bus 1720, a video adapter 1710, and an I / O interface 1712.

[0183] Bus 1720 can be one or more of several bus architectures of any type, including a memory bus or memory controller, a peripheral bus, or a video bus. CPU 1714 can include any type of electronic data processor. Memory 1708 can include any type of non-transitory system memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In an embodiment, memory 1708 may include ROM used at power-on and DRAM storing programs and data used during program execution.

[0184] Mass storage 1704 may include any type of nontransitory storage device configured to store data, programs, and other information, and make such data, programs, and other information accessible via bus 1720. Mass storage 1704 may include one or more of, for example, a solid-state drive, a hard disk drive, a disk drive, or an optical disk drive.

[0185] Video adapter 1710 and I / O interface 1712 provide interfaces to couple external input and output devices to processing unit 1702. Examples of input and output devices, as shown, include a display 1718 coupled to video adapter 1710 and a mouse, keyboard, and printer 1716 coupled to I / O interface 1712. Other devices may be coupled to processing unit 1702, and additional or fewer interface cards may be used. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface to external devices.

[0186] Processing unit 1702 also includes one or more network interfaces 1706, which may include wired links such as Ethernet cables or wireless links for accessing nodes or different networks. Network interfaces 1706 enable processing unit 1702 to communicate with remote units via a network. For example, network interfaces 1706 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In embodiments, processing unit 1702 is coupled to a local area network 1722 or a wide area network for processing data and communicating with remote devices such as other processing units, the Internet, or remote storage facilities.

[0187] It should be understood that one or more steps of the methods provided herein can be performed by corresponding units or modules. For example, a signal can be transmitted by a transmitting unit or transmitting module. A signal can be received by a receiving unit or receiving module. A signal can be processed by a processing unit or processing module. Other steps can be performed by a generating unit or module, a computing unit or module, a storage unit or module, a derivation unit or module, or a providing unit or module. Each unit or module can be hardware, software, or a combination thereof. For example, one or more of these units or modules can be integrated circuits, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0188] Although the present disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions and modifications can be made to the invention without departing from the scope of the invention as defined by the appended claims.

Claims

1. A method for routing a session to an edge application server, comprising: The control plane (CP) receives traffic impact routing rules from the application function (AF), the traffic impact routing rules including service addresses representing the destination addresses of routes to the edge application server, and the traffic impact routing rules specify circumvention rules for packets sent to communication devices destined for the edge application server; The CP stores the traffic-affected routing rules into the Policy Control Function (PCF); as well as A traffic filter is generated from packets of at least one service flow associated with the communication device by the CP. The traffic filter directs packets of the at least one service flow destined for the edge application server to the service address. The traffic filter is generated according to the traffic influence routing rules.

2. The method according to claim 1, wherein the traffic impact routing rule includes at least one of a traffic impact creation rule, a traffic impact update rule, or a traffic impact deletion rule.

3. The method according to any one of claims 1 to 2, wherein the traffic-affected routing rule further includes at least one gateway address associated with the service address.

4. The method according to claim 3, wherein the traffic filter includes the service address and the at least one gateway address.

5. The method according to any one of claims 3 to 4, wherein the traffic filter is selected based on network slice auxiliary information storage.

6. The method according to any one of claims 1 to 5, further comprising: The CP sends a traffic-affected routing rule response to the AF.

7. The method according to any one of claims 1 to 6, wherein the traffic filter is stored in a unified data repository (UDR).

8. The method according to any one of claims 1 to 7, storing the flow filter includes updating an existing flow filter using the flow filter.

9. The method according to any one of claims 1 to 8, wherein the service address includes an Internet Protocol address, a port address, and a protocol.

10. The method according to any one of claims 1 to 9, further comprising: The CP generates information associated with the flow filter.

11. The method of claim 10, wherein the information includes Single Network Slice Selection Auxiliary Information (S-NSSAI).

12. A method for routing a session to an edge application server, comprising: A traffic filter that receives packets for at least one service flow associated with a communication device by a policy control function (PCF), the traffic filter including traffic influence routing rules that specify circumvention rules for packets destined for an edge application server; The network identifier associated with the flow filter is derived from the PCF; as well as The PCF provides the network identifier and the traffic filter to the Session Management Function (SMF).

13. The method of claim 12, wherein the network identifier includes a Data Network Access Identifier (DNAI).

14. The method according to any one of claims 12 to 13, wherein the traffic filter comprises a service address and at least one gateway address.

15. The method according to any one of claims 12 to 14, wherein the traffic filter further includes network slice selection assistance information.

16. The method according to any one of claims 12 to 15, wherein providing the network identifier and the traffic filter includes initiating a session management policy control service.

17. A control plane (CP), comprising: Non-transitory memory, including instructions; and One or more processors communicate with the memory, wherein the one or more processors execute the instructions to: Receive traffic impact routing rules from the application function (AF), the traffic impact routing rules including a service address representing the destination address of the route to the edge application server, the traffic impact routing rules specifying bypass rules for packets sent to the communication device to the edge application server; Store the traffic-affected routing rules in the Policy Control Function (PCF); and A traffic filter is generated for packets of at least one service flow associated with the communication device. The traffic filter directs packets of at least one service flow destined for the edge application server to the service address. The traffic filter is generated based on the traffic influence routing rules.

18. The CP according to claim 17, wherein the traffic impact routing rule includes at least one of a traffic impact creation rule, a traffic impact update rule, or a traffic impact deletion rule.

19. The CP according to any one of claims 17 to 18, wherein the traffic-affected routing rule further includes at least one gateway address associated with the service address.

20. The CP according to claim 19, wherein the traffic filter includes the service address and the at least one gateway address.

21. The CP according to any one of claims 19 to 20, wherein the traffic filter is selected based on network slice auxiliary information storage.

22. The CP according to any one of claims 17 to 21, further comprising: The CP sends a traffic-affected routing rule response to the AF.

23. The CP according to any one of claims 17 to 22, wherein the flow filter is stored in a unified data repository (UDR).

24. The CP according to any one of claims 17 to 23, storing the flow filter includes updating an existing flow filter using the flow filter.

25. The CP according to any one of claims 17 to 24, wherein the service address includes an Internet Protocol address, a port address, and a protocol.

26. The CP according to any one of claims 17 to 25, further comprising: The CP generates information associated with the flow filter.

27. The CP according to claim 26, wherein the information includes Single Network Slice Selection Auxiliary Information (S-NSSAI).

28. A network function (NF), comprising: Non-transitory memory, including instructions; and One or more processors communicate with the memory, wherein the one or more processors execute the instructions to: A traffic filter that receives packets for at least one service flow associated with a communication device, the traffic filter including traffic influence routing rules that specify circumvention rules for packets destined for an edge application server; Derive the network identifier associated with the traffic filter; The network identifier and the traffic filter are provided to the Session Management Function (SMF).

29. The NF of claim 28, wherein the network identifier includes a Data Network Access Identifier (DNAI).

30. The NF according to any one of claims 28 to 29, wherein the traffic filter comprises a service address and at least one gateway address.

31. The NF according to any one of claims 28 to 30, wherein the traffic filter further includes network slice selection assistance information.

32. The NF according to any one of claims 28 to 31, wherein providing the network identifier and the traffic filter includes initiating a session management policy control service.

Images