Network edge application service system

Abstract

The present invention relates to the field of edge computing. Provided are a network edge application service system, comprising: a system self-owned subnet address pool, which allocates a unique subnet address to an application service provider and an edge service provider, wherein a fixed Internet address is provided to the application service provider, and the Internet address is provided to the edge service provider; and a network tunnel, which is established on the basis of the subnet address and the Internet address. A request data packet of a terminal is sent to a scheduler subnet address of the application service provider, a scheduler receives the request data packet to perform processing, configures a reply data packet to be redirected to a server subnet address of the edge service provider, and transmits the reply data packet to the terminal; and a second request data packet of the terminal is sent to the server subnet address, so as to acquire data content. An address is allocated to a mobile terminal by means of a fixed private network or public network address pool, so that high public network subnet costs are avoided, and the network operation and maintenance management is simplified by means of tunnel technology, thereby reducing delays caused by updating and convergence of a routing table.

Description

An application service system at the edge of the network Technical Field

[0001] The present invention relates to the field of edge computing, and in particular to an application service system at the edge of a network. Background Art

[0002] Traditional network architectures typically use fixed public network address pools and subnets to allocate IP addresses to mobile routers and mobile devices. Carrier networks also manage routing through the Interior Gateway Protocol (IGP) and Border Gateway Protocol (BGP) to ensure efficient communication within and outside the network. However, with the increasing use of mobile devices and mobile servers, mobile servers obtain different IP addresses when accessing the internet at different locations. Due to these dynamic IP address changes, traditional network architectures cannot effectively handle continuous connectivity and stable service between mobile servers and devices.

[0003] Although mobile servers can establish connections with fixed IP servers on the internet and initiate requests, because the mobile server's IP address constantly changes, the fixed IP server can only respond to requests initiated by the mobile server. Because the fixed IP server cannot track the mobile server's constantly changing IP address, it cannot proactively establish a connection with the mobile server and obtain its information. Therefore, the mobile server cannot provide app services on the internet to mobile terminals. Summary of the Invention

[0004] Based on the high cost and complex operation and maintenance problems of maintaining a fixed public network subnet address pool in the existing technology, especially the significant transmission delay caused by frequent routing information updates in a mobile environment, and the complexity of synchronous updating of multi-node content sources, an efficient network edge application service system is proposed. The purpose of the present invention can be achieved through the following technical solutions.

[0005] The present invention provides an application service system at the edge of a network, comprising an application service provider and an edge service provider. The system has its own subnet address pool, which allocates unique and fixed subnet addresses to the application service provider and the edge service provider. The application service provider has a fixed Internet address, and the edge service provider has an Internet address. At the same time, the gateways of the application service provider and the edge service provider are configured with network address translation for address translation between subnet addresses and Internet addresses.

[0006] The edge service provider includes terminals, servers, and gateways, and internal communications are based on the fixed subnet address of the edge service provider;

[0007] The application service provider includes servers, schedulers, and gateways, and internal communications are based on the application service provider's fixed subnet address;

[0008] A network tunnel is established based on a subnet address and an Internet address. The network tunnel includes internal routing. The internal routing adopts a tunnel binding strategy intranet and operates on data packets whose destination and source addresses are subnet addresses. The tunnel source address end encapsulates the data packet in the tunnel for transmission. The tunnel destination address end decapsulates the data packet into a data packet whose destination and source addresses are subnet addresses. When the destination address or source address in the network tunnel changes to the Internet address of the edge service provider, the network tunnel parameters are adjusted and the internal routing is rebuilt. The tunnel source address end and the tunnel destination address end include the application service provider and the edge service provider.

[0009] Based on internal routing and internal communication, the terminal's request data packet is sent to the scheduler subnet address of the application service provider through internal routing. The scheduler receives the request data packet for processing and sets the reply data packet to redirect to the server subnet address of the edge service provider, and transmits it to the terminal of the edge provider through internal routing; the terminal's second request data packet is sent to the corresponding server subnet address based on the internal communication of the edge service provider to obtain the data content cached in the server.

[0010] Furthermore, an application source is included, the application source has an Internet address, and preloads data content to a server of an application service provider, and the server of the application service provider preloads the data content to a server of an edge service provider;

[0011] The network tunnel also includes an external route, which uses a tunnel binding strategy external network to process data packets whose destination address or source address is an application source Internet address. The tunnel source address end encapsulates the data packet in the tunnel and sends it, and decapsulates the data packet at the tunnel destination address end into a data packet whose destination address or source address is an application source Internet address. When the destination address or source address in the network tunnel changes to the Internet address of the edge service provider, the network tunnel parameters are adjusted and the external route is rebuilt; wherein the tunnel source address end and the tunnel destination address end include the application source service provider and the edge service provider;

[0012] The application source and the application service provider are provided with a dispatcher, which is used to redirect the request to the dispatcher subnet address of the corresponding application service provider in response to the terminal requesting data content through the network tunnel. The terminal requests the corresponding data content according to the dispatcher subnet address of the redirected application service provider, including:

[0013] The terminal of the edge service provider sends a request data packet to the application source to obtain the data content in the application source; the request data packet is routed externally to the application service provider, and the application service provider converts the source address of the request data packet into the Internet address of the application service provider through the network address and sends it to the application source; the application source redirects the reply data packet to the scheduler subnet address of the application service provider through the internal scheduler, and reaches the application service provider; it reaches the terminal through the network address translation and external routing of the application service provider.

[0014] Furthermore, the scheduler of the application service provider stores and records the subnet address and server subnet address of the edge service provider; the scheduler matches the subnet address of the corresponding edge service provider according to the source address of the request data packet, obtains the server subnet address of the corresponding edge provider, and is used to set the reply data packet to be redirected to the server subnet address of the edge service provider, and returns the reply data packet through internal routing and the edge service provider.

[0015] Furthermore, when the edge service provider's server does not contain the data content requested by the terminal, it requests the data content from the upstream application service provider's server through internal routing. The application service provider's server responds to the request and forwards the data content to the edge service provider's server through internal routing to respond to the terminal's second request data packet.

[0016] Furthermore, the dispatcher of the application source is used to record the data content preloaded to the server of the application service provider, and to record the Internet address of the application service provider and the corresponding dispatcher subnet address;

[0017] After the application source matches the data content requested by the request data packet with the server content preloaded into the application service provider, it matches the source address of the request data packet with the Internet address of the application service provider, obtains the corresponding scheduler subnet address of the application service provider, sets the reply data packet to redirect to the scheduler subnet address of the application service provider, and returns the reply data packet to the application service provider; when the data content requested by the request data packet of the application source does not match the server content preloaded into the application service provider, it returns the corresponding data packet to the application service provider.

[0018] Furthermore, the application service provider is also used to manage the allocation of subnet address pools; the network address translation configured by the application service provider's gateway is used to convert the terminal's subnet address into the application service provider's Internet address, or to convert the application service provider's Internet address into the corresponding terminal's subnet address.

[0019] Furthermore, the application service provider and edge service provider are also configured with corresponding DNS servers and equipped with application source records for recording the Internet address of the application source, which includes the application source domain name and IP address;

[0020] The application source record in the DNS server of the application service provider is transmitted to the DNS server of the edge service provider manually or automatically, so that the gateway of the application service provider and the edge service provider can encapsulate the request data packet whose target address is the Internet address of the application source record and send it through external routing; at the same time, when the terminal sends a request data packet for the domain name of the application source, the DNS server of the edge service provider looks up the IP address corresponding to the application source domain name.

[0021] Furthermore, it also includes a second application source, a dedicated second server and a second scheduler of the application service provider, and a dedicated second server of the edge service provider; wherein

[0022] The second application source preloads data content to a dedicated second server of the application service provider, and the dedicated second server preloads data content to a dedicated second server of the edge service provider;

[0023] The dispatcher of the second application source records the Internet address of the application service provider and the subnet address of the second dispatcher; the second dispatcher records the subnet address of the edge service provider and the subnet address of the second server of the edge service provider;

[0024] At the same time, a tunnel binding strategy is adopted to establish a second external route based on a data packet whose target address or source address is the Internet address of the second application source. The source address end encapsulates the data packet in a tunnel and sends it, and decapsulates the data packet into a data packet whose destination address or source address is the Internet address of the second application source through the network conversion address of the gateway at the tunnel target address end. Among them, the tunnel source address end and the tunnel destination address end include the application source service provider and the edge service provider.

[0025] Furthermore, the request data packet sent by the terminal to the second application source reaches the gateway of the application service provider through the second external route, and after decapsulation, it is converted into the Internet address of the application service provider through the Internet and reaches the second application source; and the DNS server of the application service provider is provided with a second application source record, which is transmitted to the DNS server of the edge service provider manually or automatically.

[0026] Furthermore, the edge service provider is provided with multiple network connection interfaces and is configured with corresponding network addresses, wherein the network connection interfaces include WiFi, Ethernet and satellite 4 / 5G networks, wherein WiFi and Ethernet are used to connect to high-speed fiber-optic Internet, and satellite 4 / 5G networks are used to connect to low-speed Internet. At the same time, the network connection interface for connecting to high-speed fiber-optic Internet is given priority.

[0027] Furthermore, the system also includes an external server for caching the server content of the application service provider, wherein

[0028] Edge service providers have records linking network addresses connected to high-speed fiber optic internet and external server addresses;

[0029] The edge service provider also records the association between geographic location information and external server addresses;

[0030] Based on any one of the matching external server addresses according to the network address and the association record, the edge service provider server synchronizes and updates the data content with the external server through the network connection interface.

[0031] Furthermore, the server of the edge service provider sends a request data packet based on the subnet address through the gateway of the edge server to the external server. Based on the fact that the gateway of the edge server does not match the network tunnel, the source address is converted into the network address of the network connection interface connected to the high-speed fiber optic Internet through the network address translation of the gateway, and then the request data packet is sent to the corresponding external server address for the server content update of the edge service network provider.

[0032] Furthermore, the external server is provided with an Internet address, and the domain name and IP address are registered in the DNS server. After the edge service provider's server obtains the network address of the network connection interface connected to the high-speed fiber-optic Internet based on the gateway, it searches the DNS server for the domain name to which the external server belongs and finds the corresponding IP address of the external server.

[0033] Furthermore, it also includes a second edge service provider, which is connected to the high-speed fiber optic Internet and has a fixed or dynamic network address; the gateway of the second edge service provider is connected to the gateway of the edge service provider via WIFI, and the edge service provider obtains the subnet address of the second edge service provider, connects to the internal routing of the high-speed fiber optic Internet and the application service provider, and the subnet address of the server of the second edge service provider in the association record of the external server is the external server address.

[0034] Further, the server of the second edge service provider responds to the request data packet for content update of the server of the edge service provider, the gateway of the edge service provider converts the source address of the request data packet into the subnet address of the edge service provider at the second edge service provider through network address translation, and sends the request data packet to the gateway of the second edge service provider;

[0035] At the gateway of the second edge service provider, the destination address of the request data packet is the server subnet address of the second edge service provider, and the source address is the subnet address of the edge service provider at the second edge service provider. Based on the internal route that does not match the tunnel of the second edge service provider, the data packet is sent to the second edge server subnet address; the server of the edge service provider obtains the server content update of the second edge service provider.

[0036] Furthermore, the edge service provider's gateway sets the network interface route connected to the high-speed fiber optic Internet as priority; the system rebuilds the high-speed tunnel, high-speed internal route and high-speed external route; the edge service provider's gateway sets the network interface route priority connected to the high-speed fiber optic Internet as the same, and the tunnel uses the original network interface address parameters to keep the tunnel, internal route and external route consistent.

[0037] The technical solution proposed in this application has at least the following beneficial technical effects:

[0038] This invention uses fixed private or public network address pools to allocate addresses to mobile server terminals, avoiding high public network subnet fees. It also simplifies network operations and management through tunneling technology, reducing latency associated with routing table updates and convergence. Specifically, mobile terminals use private or public network addresses assigned by the operator without occupying fixed public network subnet address pools, significantly reducing operating costs. Within the operator's network, tunneling technology eliminates the need for traditional route establishment, simplifies operations and management, reduces latency, and improves network efficiency.

[0039] Compared to traditional Interior Gateway Protocol (IGP) or Border Gateway Protocol (BGP), this invention reduces latency and ensures real-time data transmission in mobile environments by dynamically allocating private or public network addresses and automatically reestablishing tunnels. Using tunneling technology, data sent from a terminal to a content source is directly processed by the content source and redirected to the nearest mobile server through scheduling, thus reducing data transmission paths, lowering latency, and improving transmission efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Other features, objects and advantages of the present invention will become more apparent upon reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0041] FIG1 is a structural diagram of a first component of a single application source according to an embodiment of the present invention;

[0042] FIG2 is a structural diagram of a second component of a single application source according to an embodiment of the present invention;

[0043] FIG3 is a structural diagram of a third component of a single application source according to an embodiment of the present invention;

[0044] FIG4 is a diagram of a request processing process of a single application source in an embodiment of the present invention;

[0045] FIG5 is a flowchart of a request process of a single application source according to an embodiment of the present invention, wherein FIG5a is the first part of the flowchart, and FIG5b is the second part of the flowchart continuing from FIG5a;

[0046] 6 is a structural diagram of a first component of a single application source adding a DNS server according to an embodiment of the present invention;

[0047] 7 is a diagram of a request processing process for adding a DNS server to a single application source according to an embodiment of the present invention;

[0048] FIG8 is a structural diagram of a first component of multiple application sources according to an embodiment of the present invention;

[0049] 9 is a second component structure diagram of multiple application sources according to an embodiment of the present invention;

[0050] 10 is a structural diagram of a dedicated server and a first component of a dedicated server used by an application source in an embodiment of the present invention;

[0051] 11 is a second component structure diagram of an application source using a dedicated server and a scheduler according to an embodiment of the present invention;

[0052] FIG12 is a diagram illustrating a first component architecture of an ESP including a second ESP in an embodiment of the present invention;

[0053] FIG13 is a diagram of a second component architecture of an ESP including a second ESP in an embodiment of the present invention;

[0054] 14 is a diagram of an application scenario in which an ESP includes a second ESP according to an embodiment of the present invention;

[0055] FIG15 is a diagram of a first component architecture including two ESP connections and interfaces according to an embodiment of the present invention;

[0056] FIG16 is a diagram of a second component architecture including two ESP connections and interfaces according to an embodiment of the present invention;

[0057] 17 is a diagram of a scenario application including two ESP connections and interfaces in an embodiment of the present invention;

[0058] 18 is a component architecture diagram of adding a common server in an embodiment of the present invention;

[0059] FIG19 is a diagram showing an application scenario of adding a common server in an embodiment of the present invention. DETAILED DESCRIPTION

[0060] The present invention will be described in detail below with reference to specific embodiments. The following examples will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those skilled in the art, several changes and improvements can be made without departing from the scope of the present invention. These all fall within the scope of protection of the present invention.

[0061] First embodiment

[0062] This embodiment will describe in detail how to implement the aforementioned method and system through practical examples, focusing on specific application scenarios in various network environments, including but not limited to tunnel connection examples in various network environments. As shown in Figure 1, the architecture includes an application service provider (ASP) 1000, an edge service provider (ESP) 1020, a service network (SN) 1010, and an application source (APP) 1030. ASP 1000 connects to ESP 1020 via service network SN 1010 and communicates with application source (APP) 1030 via the Internet 1040. ASP 1000 manages an address pool (AP) 1001, which has either a public or private IP address and allocates different subnet addresses to its internal devices. ASP 1000 has a unique subnet 1002, whose address resides in address pool 1001 within ASP 1000. ESP 1020 resides in the address pool of ASP 1001 and has its own dedicated subnet address 1021. Terminal 1022 is assigned an IP address from ESP subnet 1021 and can communicate with ASP 1000 and APP 1030 through SN 1010. APP 1030 represents an Internet application server, supporting applications such as voice, video, imaging, and gaming, and providing interactive services with terminal 1022. The entire architecture achieves efficient data transmission and service provision through the collaborative work of ASPs and ESPs.

[0063] As shown in Figure 2, ASP 1000 includes a gateway router GW 2000, a scheduler 2001, and a server 2002. These components can be computer programs, Docker containers, virtual machines (VMs), or bare metal devices. They can access subnet 1002 through assigned addresses in subnet 1002.

[0064] GW 2000 connects to the Internet 1040 and subnet 1002 via network interfaces and is responsible for routing traffic between subnet 1002, the Internet 1040, and SN 1010. In Figure 3, GW 2000 has two interfaces: one connecting to the Internet 1040 and the other connecting to the service network SN 1010 via the Internet 1040. ESP 1020 components, including gateway router GW 2005, server 2006, and terminal 1022, can also be computer programs, Docker containers, virtual machines, or bare metal devices. They can be accessed from subnet 1021 using subnet-assigned addresses. GW 2005 connects to the Internet 1040 and subnet 1021 via interfaces and provides routing functions, ensuring data flow between subnet 1021, the Internet 1040, and the Internet-based SN 1010.

[0065] Service network SN 1010 uses network tunneling technologies such as MPLS, Layer 3 VPN, and VLAN to provide a reachable internal routing path from ASP 1000 subnet 1002 to ESP 1020 subnet 1021. SN / VPN 1010 provides a reachable route or path between the IP address of APP 1030 and ESP 1020 subnet 1021 through ASP 1000. This is called the external route between APP 1030's IP address and subnet 1021.

[0066] The server 2002 of ASP 1000 preloads the content from APP 1030 , and the server 2006 of ESP 1020 obtains and preloads the content through the server 2002 .

[0067] Dispatcher DP 2001 has a record of the address of subnet 1021 and the address of server 2006 in subnet 1021. DP 2001 can be a program, a Docker container, a VM, a bare-metal device, or a server remotely accessed by ESP 1020 and APP 1030. ASP 1000 connects to Internet 1040 via a public IP address on GW 2000. Source NAT in GW 2000 is located on the Internet interface of APP 1040. ESP 1020 connects to Internet 1040 using a public IP address or private address from the IP address of GW 2005. Source NAT in GW 2005 is located on the Internet interface to Internet 1040. ASP 1000's public IP address for APP 1030 and the address of DP 2001 are registered with APP 1030.

[0068] APP 1030 preloads the content to the server 2002 of ASP 1000, and the content is loaded to the server 2006 of ESP 1020. APP 1030 has the content tracking record of ASP 1000 server 2002, ASP 1000 public IP address and DP 2001 address.

[0069] The specific request processing flow is shown in Figure 4. In this system, the request processing flow begins when terminal 1022 sends a request packet to application APP 1030 in ESP 1020. This request is first received by ESP's gateway GW 2005, which verifies that the packet's source IP address, terminal 1022, is within subnet 1021 and that the destination IP address, APP 1030, is the IP address of the request from 1022. These two IP addresses match the external route of SN 1010 between APP 1030's IP address and subnet 1021. GW 2005 then sends the request packet to SN 1010, encapsulates the packet in the SN 1010 tunnel, and sends it to GW 2000 in ASP 1000.

[0070] In ASP 1000, GW 2000 receives the packet from the SN 1010 tunnel and decapsulates the packet. It recovers the source IP address of Terminal 1022 and the destination IP address of APP 1030 within Subnet 1021. GW 2000 forwards the packet to APP 1030 through the Internet interface 1040. Source NAT on the GW 2000 interface translates the packet's source IP address to APP 1030's public IP address on the interface to the Internet 1040.

[0071] APP 1030 receives the data packet and checks the source IP address of the data packet for a match with the registered IP address of the interface in ASP 1000 to the Internet 1040. APP 1030 checks the content record of ASP 1000 server 2002 for the requested content.

[0072] If the requested content is in the content record, then in FIG5B, APP 1030 redirects the HTTP packet to an IP address reachable by dispatcher DP 2001 in subnet 1002 of ASP 1000. Then, the packet is replied to ASP 1000, and the target IP of its IP address is the public IP of GW 2000 of ASP 1000.

[0073] ASP 1000's GW 2000 receives the packet and uses source NAT to restore the destination IP address to that of Terminal 1022. GW 2000 checks that the destination IP address of Terminal 1022 is within the range of Subnet 1021 and that the source IP address is that of APP 1030. These two IP addresses match the external route of SN 1010. GW 2000 sends the packet to SN 1010. The packet is encapsulated in the tunnel from SN 1010 to ESP 1020.

[0074] GW 2005 of ESP 1020 receives the data packet from SN 1010 tunnel, decapsulates the data packet into a data packet with the destination IP address of terminal 1022 within the range of subnet 1021 and the source IP address of APP 1030. GW 2005 sends the data packet to terminal 1022.

[0075] As shown in Figure 4C, Terminal 1022 receives the packet, processes the redirection in the HTTP packet, and resends the request packet with the IP address of Dispatcher DP 2001, which is reachable within Subnet 1002 in ASP 1000, to GW 2005. GW 2005 checks that the source IP address of the packet is within Subnet 1021 for Terminal 1022 and the destination IP address is reachable from Dispatcher DP 2001 within Subnet 1002. These two IP addresses match the internal route of SN 1010 between Subnet 1002 and Subnet 1021. GW 2005 sends the request packet to SN 1010. The packet is encapsulated in the SN 1010 tunnel to ASP 1000.

[0076] In ASP 1000, GW 2000 receives the data packet from SN 1010 tunnel and decapsulates the data packet into a data packet where the source IP of terminal 1022 is within the range of 1021 and the destination IP address can reach the dispatcher DP 2001.

[0077] As shown in D, DP 2001 checks that the source IP of terminal 1022 is within the range 1021 and matches the address record of subnet 1021 with the address reachable by server 2006 in subnet 1021. Based on the source IP of terminal 1022 being within the range 1021, DP 2001 redirects the data packet to the address reachable by server 2006 in subnet 1021 and replies the data packet to GW 2000.

[0078] GW 2000 examines the packet and finds that the destination IP address of terminal 1022 is within the 1021 range, and the source IP address is reachable by DP 2001. These two IP addresses match the internal route of SN 1010 between subnet 1002 and subnet 1021. GW 2000 sends the packet to SN 1010. The packet is encapsulated in the VPN 1010 tunnel leading to ESP 1020.

[0079] GW 2005 of ESP 1020 receives the data packet from SN 1010 tunnel, and decapsulates the data packet into a data packet whose destination IP address of terminal 1022 is within the range of subnet 1021 and source IP address can reach DP 2001. GW 2005 sends the data packet to terminal 1022.

[0080] 4E, terminal 1022 receives the packet and processes the redirection in http, and resends the request packet with the destination being the address in subnet 1021 reachable by server 2006 to GW 2005 in ESP 1020. Server 2006 replies to terminal 1022 using the request content preloaded from APP 1030.

[0081] In B and H, APP 1030 checks the content records of ASP 1000 server 2002 for the requested content. If the requested content is not in the content records of ASP 1000 server 2002 or ESP server 2006, APP 1030 replies the content to ASP 1000. This data packet is a reply to ASP 1000, and its destination IP address is the public IP address of ASP 1000's GW 2000.

[0082] ASP 1000's GW 2000 receives the packet and uses source address translation (NAT) to restore the destination IP address to that of terminal 1022. GW 2000 checks that the destination IP address in the packet is terminal 1022, within subnet 1021, and that the source IP address is that of APP 1030. These two IP addresses match the external route of SN 1010. GW 2000 sends the packet to SN 1010. The packet is encapsulated in the tunnel from SN 1010 to ESP 1020.

[0083] GW 2005 of ESP 1020 receives the data packet from SN 1010 tunnel, and decapsulates the data packet into a data packet whose destination IP address is terminal 1022 within subnet 1021 and whose source IP address is the IP of APP 1030. GW 2005 sends the data packet to terminal 1022.

[0084] Terminal 1022 receives the packets and content.

[0085] APP 1030 preloads the content to ASP 1000 server 2002, and server 2002 preloads the content to ESP 1020 server 2006. In some cases, the content of server 2002 and server 2006 are not synchronized.

[0086] As shown in E in FIG. 4 , the terminal 1022 receives the packet and processes the redirection in the HTTP packet, and resends the request packet destined for an address in the subnet 1021 where the server 2006 can be reached to the GW 2005 in the ESP 1020 .

[0087] If the server 2006 does not have the content requested by the terminal 1022, such as 1, the server 2006 sends the request to the ASP 1000 server 2002 through the internal routing of the SN 1010 between the subnet 1002 and the subnet 1021. For example, the reverse proxy server 2006 has an HTTP upstream server address that is the ASP 1000 server 2002 address.

[0088] As J, server 2002 sends the content to server 2006 via the internal routing of SN 1010 between subnet 1002 and subnet 1021.

[0089] GW 2005 of ESP 1020 receives the data packet from SN 1010 tunnel and decapsulates the data packet into a data packet whose destination IP address is the address of server 2006 in subnet 1021 and whose source IP address is the IP of server 2002 in ASP 1000. GW 2005 sends the data packet to server 2006.

[0090] The server 2006 forwards the data to the terminal 1022. The terminal 1022 receives the packets and the content.

[0091] Throughout the entire process, internal and external routing, tunneling technology, and source NAT translation critically support the correct transmission and routing of data packets, ensuring the efficiency and accuracy of request and response content.

[0092] As explained below with reference to FIG5 , terminal 1022 sends a request to obtain the content of application APP 1030. The request first reaches ESP gateway GW 2005. GW 2005 matches the route and sends the request to ASP gateway GW 2000 through SN 1010 external routing. After GW 2000 receives the request packet, the source NAT on the GW 2000 interface converts the packet source IP address to the public IP of APP 1030 to the interface to the Internet 1040, passes the request to the Internet 1040, and finally reaches the application source APP 1030.

[0093] APP 1030 searches for the content and checks its cache to see if the requested content exists in any of the ASPs recorded in APP 1030. If the requested content is not cached in the ASP server recorded in APP 1030, APP 1030 sends the content to GW 2000. GW 2000 then receives the packet and uses source address translation (NAT) to restore the destination IP address to the IP address of terminal 1022. The uncached requested content is then returned to terminal 1022 via the matching external routes of GW 2000 and GW 2005, and then through the external routing of SN 1010.

[0094] When the ASP server registered by APP 1030 caches the requested content, APP 1030 matches the source address of the request packet with the Internet address of ASP 1000, finding an IP address reachable by Dispatcher DP 2001 in ASP 1000's subnet 1002. APP 1030 then redirects the packet to the IP address reachable by Dispatcher DP 2001 in ASP 1000's subnet 1002. The packet is then sent back to ASP 1000, with the destination IP address set to the public IP address of ASP 1000's GW 2000. ASP 1000's GW 2000 receives the packet and uses source NAT to restore the destination IP address to the IP address of Terminal 1022. GW 2000 verifies that the destination IP address of Terminal 1022 in the packet is within the range of Subnet 1021 and that the source IP address is APP 1030's IP address. These two IP addresses match the external routing information of SN 1010. GW 2000 sends the data packet to SN 1010. The data packet is encapsulated in the tunnel from SN 1010 to ESP 1020. GW 2005 of ESP 1020 receives the data packet from the SN 1010 tunnel and decapsulates the data packet into a data packet with a destination IP address of terminal 1022 within the range of subnet 1021 and a source IP address of APP 1030. GW 2005 then sends the data packet to terminal 1022.

[0095] Terminal 1022 receives the packet and processes the redirect in the HTTP packet, and resends the request packet with the destination being the IP address of dispatcher DP 2001 within the range of subnet 1002 reachable in ASP 1000, routed internally through GW 2005 and SN 1010 of GW 2000, and reaching GW 2000, DP 2001. DP 2001 checks that the source IP of terminal 1022 is within the range of 1021, and matches the address record of subnet 1021 reachable by server 2006 in subnet 1021. DP 2001 redirects the data packet to the reachable address of server 2006 within subnet 1021 based on the source IP address of terminal 1022, which is within the range of 1021. DP 2001 then replies to GW 2000. Through internal route matching within SN 1010, GW 2005 receives the data packet through the SN 1010 tunnel and decapsulates the data packet into a data packet with the destination IP address of terminal 1022 within the range of subnet 1021 and the source IP address reachable to DP 2001. GW 2005 then sends the data packet to terminal 1022.

[0096] The terminal 1022 resends the request and resends the request packet, whose destination is an address in the subnet 1021 reachable by the server 2006, to the GW 2005 in the ESP 1020. The server 2006 replies to the terminal 1022 using the request content preloaded from the APP 1030.

[0097] If server 2006 does not pre-cache the requested content, server 2006 sends the request to ASP 1000 server 2002 via the internal routing of SN 1010 between subnet 1002 and subnet 1021. Server 2002 sends the content to server 2006 via the internal routing of SN 1010 between subnet 1002 and subnet 1021. Server 2006 forwards the data to terminal 1022. Terminal 1022 receives the packets and the content.

[0098] To further illustrate the request processing functionality within a system that includes DNS servers, we'll explore the architecture and processes shown in Figures 6 and 7. These diagrams illustrate an enhanced network architecture consisting of application service providers (ASPs) and edge service providers (ESPs), interconnected through a service network (SN) and interacting with applications on the Internet. This architecture specifically emphasizes the role of DNS servers, which are located at key nodes in the network to support domain name resolution and optimize network request paths.

[0099] In Figure 6, we see an extended network system that includes four key DNS servers located close to the ASPs and ESPs in the Internet. This system is designed with network efficiency and optimized domain name resolution processes in mind:

[0100] DNS server 4003 is located near ESP 1020 in Internet 1040, DNS server 4001 is located within ESP 1020, and DNS server 4002 is located near ASP 1000 in Internet 1040, with DNS server 4000 located within ASP 1000. APP 1030 is a server whose public IP address and domain name are registered with DNS servers 4002 and 4003. ASP 1000 includes GW 2000, scheduler 2001, server 2002, and DNS server 4000. An ASP can be a computer running a program, a Docker container, a VM, or a bare metal device. They can be in subnet 1002 or have addresses assigned from subnet 1002.

[0101] ASP 1000 is connected to the Internet 1040 via the public IP address on GW 2000, and DNS 4002 is assigned to DNS 4000 as a remote DNS server. ESP 1020 includes GW 2005, server 2006, DNS 4001, and terminal 1022. ESP 1020 can be a computer running a program, a Docker container, a VM, or a bare metal device, including GW 2005, server 2006, DNS 4001, and terminal 1022. They are reachable within subnet 1021, or are assigned addresses from subnet 1021.

[0102] ESP 1020 connects to the Internet 1040 using a private or public IP address from the ISP on GW 2005, and DNS 4003 is assigned to DNS 4001 as a remote DNS server. Source NAT in GW 2005 is located on the Internet interface to Internet 1040. App 1030 registers its public IP address and domain name with DNS 4002 and 4003. DNS 4000 can obtain the IP address and domain name of App 1030 from DNS 4002. The IP address and domain name of App 1030 are obtained from DNS 4002 and manually or automatically transferred to DNS 4001 on ESP 1020 for configuration. DNS 4001 can be configured by using the hosts file on a Linux system with the IP address and domain name, or by configuring a local DNS server on ESP 1020. ESP 1020 can then obtain the IP address and domain name of App 1030 from DNS 4001. APP 1030 preloads content onto ASP 1000 server 2002, which then loads the content onto ESP 1020 server 2006. APP 1030 has the content tracking record from ASP 1000 server 2002, the ASP 1000 public IP address, and the address of DP 2001. This configuration optimizes network paths, reduces domain name resolution time, and ensures that data packets are quickly and accurately transmitted to their destinations.

[0103] Figure 7 details the processing flow for a network request with a DNS server. Compared to the previous configuration, this process includes an additional step for domain name resolution to ensure the validity and efficiency of network requests: In ESP 1020, terminal 1022 sends a request packet with the domain name APP 1030. ESP 1020 DNS 4001 obtains APP 1030's IP address. The request for APP 1030's IP address is sent to GW 2005. GW 2000 receives the packet from the SN 1010 tunnel, decapsulates the packet, and recovers the source IP address of terminal 1022 within the subnet 1021 range, and the destination IP address of APP 1030. GW 2000 forwards the packet to APP 1030 through the Internet 1040 interface. GW 2000 verifies APP 1030's IP address from DNS 4000 through reverse DNS and PTR checks before forwarding the packet. Source NAT on the interface of GW 2000 translates the source IP address of the data packet from terminal 1022 into the public IP of the interface between APP 1030 and the Internet 1040. This process not only ensures efficient access to the target application, but also optimizes the data transmission path, reduces network latency, and improves overall network performance.

[0104] Figures 8 and 9 illustrate a complex network system that includes not one, but multiple application sources (APPs). In this example, a second application, APP 6000, is featured as a new addition to the system. This configuration demonstrates how the system can flexibly support multiple applications while maintaining efficient data processing and optimized network communication. The system's design allows application service providers (ASPs) and edge service providers (ESPs) to efficiently manage and distribute content from multiple sources, ensuring users receive stable and responsive service.

[0105] There are 2dn APPs in the system as APP 6000.

[0106] ASP 1000 with server 2002 preloads content from APP 6000.

[0107] The ESP 1030 with the server 2006 is preloaded with content from the APP 6000 .

[0108] APP 6000 registers the public IP address from ASP 1000 to APP 6000 and the address reachable by DP 2001. APP 6000 registers its public IP address and domain name in DNS 4002 and 4003. DNS 4000 can obtain APP 6000's IP and domain name from DNS 4002 and 4003. APP 6000's IP and domain name are manually or automatically transferred to DNS 4001 of ESP 1020. Terminal 1022 in ESP 1020 can obtain APP 6000's IP and domain name from DNS 4001. SN 1010 provides a reachable route and path between APP 6000's IP and domain and ESP 1020's subnet 1021 through ASP 1000. This is called the external route between APP 6000's IP and subnet 1021. APP 6000 uses server 2002 to preload content to ASP 1000, and then uses server 2006 to load the content to ESP 1020. APP 6000 has content tracking records in ASP 1000 server 2002, ASP 1000 public IP address to APP 1030 public IP address and DP 2001 address.

[0109] As shown in Figures 10 and 11, for the second application source APP, such as APP 7000, a dedicated server and a dedicated scheduler are provided in ASP 1000 and ESP 1020. Unlike the first application source APP 1030, the second application source APP 7000 requires dedicated resources to ensure the security or management of its content. These resources include a dedicated ASP server 7002 added to ASP 1000 and a dedicated ESP server 7003 added to ESP 1020. The dedicated server preloads the content from APP 7000.

[0110] Dedicated dispatcher DP 7001 is added to ASP 1000 and includes the address of subnet 1021 and the address of dedicated ESP server 7003 in that subnet in its records. The content inspection process for APP 7000 is the same as described above. ASP 1000 registers APP 7000's public IP address and the address of dedicated dispatcher DP 7001 with APP 7000, ensuring that the terminal can retrieve the correct content upon request. In the DNS system, APP 7000's public IP address and domain name are registered with DNS 4002 and DNS 4003. DNS 4000 can obtain APP 7000's IP address and domain name from DNS 4002 and then provide them to terminal 1022 of ESP 1020 via DNS 4001. SN / Tunnel 1010 provides routing between APP 7000 and the IP and domain of ESP 1020 subnet 1021 through ASP 1000, which is called external routing between APP 7000 IP and subnet 1021.

[0111] Terminal 1022 sends a request to the domain name of APP 7000, obtaining the IP address of APP 7000 from DNS 4001. The request then passes through SN 1010 and ASP 1000, ultimately reaching APP 7000. APP 7000 redirects the request to the IP address of dedicated dispatcher DP 7001 in ASP 1000's subnet 1002 via an HTTP packet. After ASP 1000 receives the packet, it transmits it to ESP 1020 via SN 1010, ultimately reaching terminal 1022. Terminal 1022 processes the redirection and resends the request to dedicated dispatcher DP 7001 via SN 1010. Dedicated dispatcher DP 7001 determines whether terminal 1022's IP address is within subnet 1021 and redirects the HTTP packet to the address of dedicated ESP server 7003 in subnet 1021. Finally, the data packet returns to the GW 2000 of the ASP 1000 and reaches the terminal 1022 through the SN 1010. The terminal 1022 processes the redirection and sends a request to the dedicated ESP server 7003, thus completing the data transmission.

[0112] The specific example is applied to the mini portal / playlist service, and APP 7000 will preload or clear the content in the dedicated ASP server 7002 in ASP 1000 and the dedicated ESP server 7003 in ESP 1020. The dedicated ESP server 7003 builds and maintains a list of content titles, and generates a mini portal page for the content stored therein, in which the content name and URL are paired to form an accessible entrance. In the HLS (HTTP Live Streaming) streaming video service, the mini portal page also contains the name of the playlist file and its storage path so that the terminal can obtain the streaming content. When the terminal 1022 initiates a request to the APP 7000, the traffic will be redirected to the dedicated ESP server, which will send the mini portal page to the terminal 1022. The terminal 1022 browses and selects the required content in the mini portal page. After selection, the terminal 1022 sends the content request containing the URL to the dedicated ASP server 7003. After receiving the request, the dedicated ASP server 7003 will return the requested content to the terminal 1022 according to the URL of the content, and at the same time record the selection of the terminal 1022 on the mini portal page and the security verification process.

[0113] As shown in Figures 12-14, in the network architecture, the second ESP 8000 is designed as a submodule embedded within ESP 1020, typically installed on a mobile carrier such as an airplane, train, or ship. This design allows the ESP 8000 to synchronize and update data via a high-speed, cost-effective connection when located near ESP 1020, such as at an airport, train station, or port.

[0114] ESP 8000 is located inside ESP 1020, acting like a terminal within ESP 1020. ESP 1020 is located at airports, train stations, and ports, which have fast, low-cost fiber optic networks. Server 8006 can quickly obtain content updates from ASP 1000. ESP 8000 can be installed on airplanes, trains, and ships, connecting via slow and expensive satellite wireless internet or mobile 4G / 5G. Server 8006 obtains content updates from ASP 1000 at a slow and costly rate. When ESP 8000 arrives at the airport, train station, or port, GW 8005 connects to the low-cost, high-speed internet on ESP 1020 (GW 2005) via Wi-Fi or Ethernet. ESP 8000 GW 8005 connects to ESP 1020 GW 2005, which is assigned an address in subnet 1021. DNS 8007 is served by DNS 4001. ESP 1020 includes GW 2005, ESP server 2006, DNS 4001, terminal 1022, and ESP 8000. They are reachable in subnet 1021.

[0115] GW 2005 has interfaces to the Internet 1040 and subnet 1021, and routes to subnet 1021, the Internet 1040, and SN 1010. GW 8005 has interfaces to subnet 1021 and subnet 8001, and routes to subnet 1021, subnet 8001, and SN 8010 through the Internet 1040 and subnet 1021.

[0116] ESP 8000 server 8006 is preloaded with content from APP 1030. Dispatcher DP 2001 has a record of the address of subnet 1021 and the address of server 2006 in subnet 1021, as well as a record of the address of subnet 8001 and the address of server 8006 in subnet 8001. ESP 8000 connects subnet 8001 to the Internet 1040 using the IP address on GW 2005.

[0117] The source NAT in GW 8005 is located on the interface to subnet 1021. The NAT creates a hole that is open for destinations to ASP 1000's subnet 1002 and also for destinations to APP 1030. Packets tunneled by SN 8010, with a destination address of ASP 1000's subnet 1002 and APP 1030, and a source address of subnet 8001, enter GW 2005. These packets do not match either the external or internal routing of GW 2005's SN 1010 and are sent to the Internet 1040. GW 2005's NAT translates them to the source IP address of the Internet on GW 2005.

[0118] ASP 1000 returns a packet to GW 2000 with the destination address being the Internet IP address of GW 2005. GW 2005's NAT restores the packet's destination address to the 8001 subnet address. GW 2005 routes the packet to GW 8005.

[0119] SN 8010 tunnel built to ASP 1000 via WiFi fiber optic internet.

[0120] SN 8010 does not use SN 1010 via subnet 1021 and Internet 1040 .

[0121] SN 8010 provides routes between ASP 1000 subnet 1002 and ESP 8000 subnet 8001. These routes are internal routes between subnet 1002 and subnet 8001.

[0122] SN 8010 provides routing between APP 1030's IP and domain and ESP 8000's subnet 8001 through ASP 1000, which is called external routing between APP 1030's IP and subnet 8001.

[0123] Terminal 8008 requests the content datagram packet of APP 1030, enters GW 8005, is externally routed by SN 8010, and is redirected to scheduler DP 2001. Scheduler DP 2001 redirects the request to scheduler DP 8001. Scheduler DP 8001 redirects the request to server 8006.

[0124] Terminal 8008 sends a datagram to a destination IP outside the route of SN 8010, enters gateway GW 8005, does not match the route of SN 8010, and the source NAT in gateway GW 8005 converts the source address of the datagram to the address of the interface to subnet 1021 and sends it to gateway GW 2005.

[0125] In this highly dynamic network architecture, ESP 8000, as a subsystem embedded in ESP 1020, allows ESP 8000 to efficiently synchronize data in mobile environments such as airplanes, trains or ships using network resources in static environments such as airports, train stations or ports.

[0126] The ESP 8000 server 8006 updates the content from the ESP server 2006 via low-cost fast WiFi / Ethernet at airports, train stations, and ports.

[0127] The gateway GW 2005 has an interface 9001 to the Internet 1040 , a WiFi AP 9000 to the subnet 1021 , and an Ethernet 9002 to the subnet 1021 .

[0128] The gateway GW 8005 has many WAN network interfaces, a high cost slow Satcom / 4G interface 9007 connected to the Internet 1040, a low cost fast WiFi 9003 connected to the subnet 1021 and Ethernet 9004.

[0129] Gateway GW 8005 monitors the status of WiFi interfaces. When WiFi interface 9003 is turned on within the range of an airport, train station, or port, GW obtains an address from subnet 1021. If the routing cost metric for WiFi interface 9003 on GW 8005 is the lowest, GW obtains an address from subnet 1021. If the routing cost metric for WiFi interface 9003 on GW 8005 is the lowest, datagrams automatically prioritize routing through WiFi interface 9003. SN 8010 tunnels the WiFi fiber optic internet to ASP 1000, automatically updating tunnel parameters.

[0130] ESP 8000 has a record associating the address of server 8006 with subnet address 1021. Based on the subnet prefix of WiFi 9003's IP address, ESP 8000 obtains the IP address of server 2006. Server 8006 manually or automatically updates the content from server 2006. Server 8006 sends a datagram to the address of server 2006. The datagram enters GW 8005, where it does not match the route of SN 8010. The source NAT in GW 8005 translates the source address of the datagram to the address of the interface on subnet 1021. The datagram is then sent to GW 2005, where it reaches server 2006. Server 2006 returns the content packet to the interface address on subnet 1021 on GW 8005. The source NAT in GW 8005 restores the destination address to the address of server 8006, updating the content on server 8006.

[0131] As shown in Figures 15-17, multiple ESP devices (such as the ESP 8000 and ESP 1020) are connected via Wi-Fi or Ethernet at airports, train stations, and ports. The ESP 8000 also connects to the internet via satellite or 4G. The SN 8010 remains in place, ensuring network connectivity between the devices.

[0132] The ESP 8000 connects to a WiFi access point (WiFi AP 9000) via WiFi interface 9003 and then to the Internet via gateway GW 2005. ESPs with satellite / 4G connectivity can also connect to the Internet via GW 8005. GW 8005 monitors the status of WiFi interface 9003. When a device enters the coverage area of ​​WiFi AP 9000, WiFi interface 9003 turns on, and gateway GW 8005 obtains an IP address using subnet 1021.

[0133] ESP 8000 queries the IP address record for server 2006 associated with subnet 1021 based on the subnet prefix of the IP address of WiFi interface 9003. ESP 8000 obtains the IP address of server 2006. Server 8006 retrieves the content from server 2006 and sends the content data packet to GW 8005. GW 8005 uses source NAT (Network Address Translation) to modify the source address to the address of WiFi interface 9003 in subnet 1021. The data packet is then forwarded to GW 2005 and reaches server 2006, where it retrieves the content and returns to ESP 8000.

[0134] When the ESP 8000 needs to update its content, it can obtain server content from other ESP devices (such as ESP 2 or ESP 3) located in train stations, airports, or terminals via a high-speed Internet connection (through ESP 2 or ESP 3). The update process maintains a low-speed tunnel VPN connection and locates and updates content by associating geographic location information or IP address prefixes with server IP addresses.

[0135] As shown in Figures 18-19, in some locations, such as airports and train stations, where there is no ESP equipment available and only a high-speed, low-cost Wi-Fi fiber network is available, the ESP 8000 and GW 8005 devices will switch to a Wi-Fi Ethernet connection, replacing the high-cost satellite or 4G link. In this case, the SN 8010 will establish a connection with the ASP 1000 via the Wi-Fi fiber network, and the GW 8005 will continuously monitor the status of the Wi-Fi interface. When the device enters the Wi-Fi coverage area of ​​the airport, train station, or port, Wi-Fi interface 9003 automatically turns on. The GW 8005 obtains an address from subnet 1021. If Wi-Fi interface 9003 has the lowest routing metric, data packets will be preferentially routed through Wi-Fi interface 9003. When the SN 8010 reaches the ASP 1000 via the Wi-Fi fiber network, it will automatically update tunnel parameters to ensure a stable connection.

[0136] The server 8006 located in the ESP 800 can manually or automatically update the content from the server 2002 in the ASP 1000. The update process is as follows:

[0137] Server 8006 sends a datagram to the server 2002 address of ASP 1000, enters through GW 8005, matches the SN 8010 route, continues to be forwarded to GW 2000, and finally reaches server 2002.

[0138] Server 2002 returns the content data packet, which is resent to the address of server 8006 through GW 8005, thereby updating the content in server 8006.

[0139] At the same time, in nearby places such as train stations and airports, ESP 8000 can also obtain updated content through server 1200. Server 1200 is connected to the local area network (LAN) of the train station or airport via the Internet 1040 and provides updated content for APP 1030. To find the nearest server 1200, use the IP address prefix or other information to search, as follows:

[0140] The ESP 8000 has a pre-stored association record of the server 1200 IP address and the Internet 1040 IP addresses of locations such as train stations and airports. The ESP 8000 compares the Internet 1040 IP address of the GW 8005 with the subnet prefix of the IP address of the WiFi interface 9003 to find the server 1200 IP associated with it.

[0141] ESP 8000 can also search for geographic location records associated with the IP address of server 1200 based on location information such as GPS, Beidou, and Galileo. When approaching a station, airport, or other location, ESP 8000 uses location information to identify and select the nearest server 1200 for content update.

[0142] The server 1200 is a server with the domain name www.xxx.com, which stores and updates the content of the APP 1030 and provides update services through the server 2002 of the ASP 1000.

[0143] The specific process of the server 8006 updating the content from the server 1200 is as follows:

[0144] The Internet 1040 near the station, airport, or terminal includes the station, airport, or terminal's local area network (LAN). Server 1200 connects to Internet 1040 near the station, airport, or terminal and obtains an IP address. The IP address may include geographic location information. Server 1200 stores and updates the content of App 1030 via Server 2002 of ASP 1000. At the station, airport, or terminal, ESP 8000 needs to locate the nearest server 1200 and store and update the content of App 1030 via high-speed fiber-optic internet.

[0145] (1) ESP 8000 has a pre-stored record of associations between the server 1200 IP address and the Internet 1040 IP address of the station, airport, or terminal. ESP 8000 compares the address association record with the Internet 1040 IP address of gateway 8005, such as the WiFi 9003 IP or the 9003 IP address subnet prefix, and obtains the nearest server 1200 IP address.

[0146] (2) The ESP 8000 has pre-stored location information (GPS, Beidou, Galileo, and base station location systems) and a record of its association with the nearest 8000 server IP. When the ESP 8000 approaches a station, airport, or terminal, it reads its own location information and compares the location information range with the records of its association with the 1200 server IP. The ESP 8000 then finds the nearest 1200 server IP.

[0147] (3) Server 1200 is a server for the domain www.xxx.com. Its IP address and domain name are registered in DNS 2010-2009. ESP 8000 connects to the fiber optic high-speed Internet (WAN), WiFi, Ethernet, or 5G at the airport terminal GW 8005 and obtains a new address assigned by Internet 1040 as its external WAN address. DNS 2010-2009 updates the IP address of www.xxx.com in DNS 8007 and the nearest server 1200 based on the new address assigned by Internet 1040 by ESP 8000. Server 8006 sends a datagram to DNS 8007 to look up the server IP address for the domain www.xxx.com and obtains the IP address of the nearest server 1200.

[0148] ESP 8000 checks whether high-speed network connections such as Internet (WAN), WiFi, Ethernet, and 5G are connected.

[0149] Server 8006 sends the datagram destination address to the server 1200 IP address. The datagram enters GW 8005 and does not match the internal and external routes of SN 8010. The source NAT in GW 8005 converts the datagram source address server 8006 IP address into the address of the interface to the Internet 1040, sends it to the Internet 1040, and reaches server 1200.

[0150] Server 1200 returns the content data packet to the interface IP address of GW 8005 on the Internet 1040. The source NAT in GW 8005 restores the destination address of the data packet to the IP address of server 8006 and updates the content of server 8006.

[0151] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the system, method and computer program product according to multiple embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part of a program segment or instruction, and a part of a program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the function marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the function involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0152] While various embodiments of the present disclosure have been described above, the foregoing description is intended to be illustrative, non-exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or technological improvements in the marketplace, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. An application service system at the network edge, characterized in that, Including an application service provider and an edge service provider; a system-owned subnet address pool that assigns unique and fixed subnet addresses to the application service provider and the edge service provider; the application service provider has a fixed Internet address, and the edge service provider has an Internet address. At the same time, the gateways of the application service provider and the edge service provider are configured with network address translation for address translation between the subnet address and the Internet address; The edge service provider includes terminals, servers, and the gateway, and conducts internal communication based on the fixed subnet address of the edge service provider; The application service provider includes servers, dispatchers, and the gateway, and conducts the internal communication based on the fixed subnet address of the application service provider; The network tunnel established based on the subnet address and the Internet address. The network tunnel includes an internal route. The internal route adopts a tunnel binding policy for the intranet and operates on data packets with the target address and source address being the subnet address. The tunnel source address end encapsulates the data packet in the tunnel for transmission, and the tunnel target address end de-encapsulates it into the data packet with the target address and source address being the subnet address. When the Internet address of the edge service provider in the network tunnel changes for the target address or the source address, adjust the network tunnel parameters and reconstruct the internal route; the tunnel source address end and the tunnel destination address end include the application service provider and the edge service provider; Based on the internal route and the internal communication, the request data packet of the terminal is sent to the dispatcher subnet address of the application service provider through the internal route. The dispatcher receives the request data packet for processing and sets the reply data packet to be redirected to the server subnet address of the edge service provider, and is transmitted to the terminal of the edge provider through the internal route; the second request data packet of the terminal is sent to the corresponding server subnet address based on the internal communication of the edge service provider to obtain the data content cached in the server.

2. The application service system according to claim 1, wherein It also includes an application source that has the Internet address and pre-loads the data content into the servers of the application service provider, and the servers of the application service provider pre-load the data content into the servers of the edge service provider; The network tunnel further includes the external router, which uses the tunnel binding policy for the external network to process the data packets with the target address or the source address being the application source Internet address. The tunnel source address end encapsulates the data packets in the tunnel and sends them, and at the tunnel target address end, the data packets are decapsulated into the data packets with the destination address or the source address being the application source Internet address. When the Internet address of the edge service provider changes for the target address or the source address in the network tunnel, the network tunnel parameters are adjusted and the external router is rebuilt; wherein, the tunnel source address end and the tunnel destination address end include the application source service provider and the edge service provider; A scheduler is provided in the application source and the application service provider. When the terminal requests the data content through the network tunnel, the scheduler redirects the request to the scheduler subnet address of the corresponding application service provider. The terminal requests the corresponding data content according to the redirected scheduler subnet address of the application service provider, including: The terminal of the edge service provider sends a request data packet to the application source to obtain the data content in the application source; the request data packet reaches the application service provider through the external router, and the application service provider converts the source address of the request data packet through the network address into the Internet address of the application service provider and sends it to the application source; the application source sets the reply data packet to be redirected to the scheduler subnet address of the application service provider through the internally set scheduler and reaches the application service provider; it reaches the terminal through the network address conversion and the external router of the application service provider.

3. The application service system according to claim 2, wherein The scheduler of the application service provider stores and records the subnet address of the edge service provider and the server subnet address; The scheduler matches the corresponding subnet address of the edge service provider according to the source address of the request data packet, obtains the server subnet address of the corresponding edge provider, is used to set the reply data packet to be redirected to the server subnet address of the edge service provider, and returns the reply data packet through the internal router and the edge service provider.

4. The application service system according to claim 2, wherein When the server of the edge service provider does not have the data content requested by the terminal, it requests the data content from the server of the upstream application service provider through the internal router. The server of the application service provider responds to the request and forwards the data content to the server of the edge service provider through the internal router to respond to the second request data packet of the terminal.

5. The application service system according to claim 2, characterized in that, The scheduler of the application source is used to record the data content pre-loaded to the server of the application service provider, and record the Internet address of the application service provider and the corresponding scheduler subnet address; After the application source matches the data content requested by the request data packet with the content pre-loaded into the server of the application service provider, it matches the source address of the request data packet and the Internet address of the application service provider, obtains the corresponding scheduler subnet address of the application service provider, sets the reply data packet to be redirected to the scheduler subnet address of the application service provider, and returns the reply data packet to the application service provider; When the data content requested by the request data packet of the application source does not match the content pre-loaded into the server of the application service provider, the corresponding data packet is returned to the application service provider.

6. The application service system according to claim 2, wherein The application service provider is also used to manage the allocation of the subnet address pool; the network address translation configured by the gateway of the application service provider is used to convert the subnet address of the terminal into the Internet address of the application service provider, or convert the Internet address of the application service provider into the corresponding subnet address of the terminal.

7. The application service system according to claim 2, characterized in that, The application service provider and the edge service provider are also configured with corresponding DNS servers and are equipped with application source records for recording the Internet address of the application source, and the Internet address includes the application source domain name and the IP address; The application source record in the DNS server of the application service provider is transmitted to the DNS server of the edge service provider manually or automatically, so that the gateways of the application service provider and the edge service provider encapsulate the request data packet with the Internet address of the application source record as the target address and send it through the external router; at the same time, when the terminal issues a request data packet for the domain name of the application source, the DNS server of the edge service provider looks up the IP address corresponding to the application source domain name.

8. The application service system according to claim 2, characterized in that It also includes a second application source, a dedicated second server of the application service provider, a second scheduler, and a dedicated second server of the edge service provider; Wherein The second application source pre-loads the data content to the dedicated second server of the application service provider, and the dedicated second server pre-loads the data content to the dedicated second server of the edge service provider; The scheduler of the second application source records the Internet address of the application service provider and the second scheduler subnet address; The second scheduler records the subnet address of the edge service provider and the second server subnet address of the edge service provider; Meanwhile, the tunnel is adopted to bind to the policy external network, and a second external route is established for the data packet whose destination address or source address is the Internet address of the second application source. The source address end encapsulates the data packet in the tunnel and sends it, and the data packet is decapsulated into the data packet whose destination address or source address is the Internet address of the second application source through the network translation address of the gateway at the tunnel destination address end, where the tunnel source address end and the tunnel destination address end include the application source service provider and the edge service provider.

9. The application service system according to claim 8, wherein, The request data packet sent by the terminal to the second application source reaches the gateway of the application service provider through the second external route, and after decapsulation, it reaches the second application source through the Internet after being translated into the Internet address of the application service provider through network address translation; and a second application source record is set in the DNS server of the application service provider and is transmitted to the DNS server of the edge service provider in a manual or automatic manner.

10. The application service system according to claim 9, characterized in that, The edge service provider is provided with multiple network connection interfaces and is configured with corresponding network addresses. Among them, the network connection interfaces include WiFi, Ethernet, and satellite 4 / 5G network. Among them, the WiFi and the Ethernet are used to connect to the high-speed fiber Internet, and the satellite 4 / 5G network is used to connect to the low-speed Internet. At the same time, the network connection interfaces for connecting to the high-speed fiber Internet are given priority.

11. The application service system according to claim 10, characterized in that, The system further includes an external server for caching the server content of the application service provider, where the edge service provider records the association record between the network address connecting to the high-speed fiber Internet and the external server address; the edge service provider also records the association record between the geographical location information and the external server address; Based on any one of the above, the corresponding external server address is matched according to the network address and the association record, and the edge service provider server synchronizes and updates the data content with the external server through the network connection interface.

12. The application service system according to claim 11, characterized in that, The server of the edge service provider sends the request data packet to the external server through the gateway of the edge server based on the subnet address. Since the gateway of the edge server does not match the network tunnel, after the source address is translated into the network address of the network connection interface connecting to the high-speed fiber Internet through the network address translation of the gateway, the request data packet is sent to the corresponding external server address for updating the server content of the edge service network provider.

13. The application service system according to claim 10, characterized in that, The external server has the Internet address, and the domain name and the IP address are registered in the DNS server. After the server of the edge service provider obtains the network address of the network connection interface connecting to the high-speed fiber Internet based on the gateway, it looks up the domain name to which the external server belongs in the DNS server and finds the IP address of the corresponding external server.

14. The application service system according to claim 13, characterized in that, It further includes a second edge service provider, which is connected to the high-speed fiber Internet and has a fixed or dynamic network address; the gateway of the second edge service provider is connected to the gateway of the edge service provider through the WIFI, and the edge service provider obtains the subnet address of the second edge service provider, connects to the internal routing of the high-speed fiber Internet and the application service provider, and the subnet address of the server of the second edge service provider in the associated record of the external server is the external server address.

15. The application service system according to claim 14, wherein The server of the second edge service provider responds to the request data packet for the content update of the server of the edge service provider. The gateway of the edge service provider converts the source address of the request data packet into the subnet address of the edge service provider in the second edge service provider through network address translation and sends the request data packet to the gateway of the second edge service provider. At the gateway of the second edge service provider, the target address of the request data packet is the server subnet address of the second edge service provider, and the source address is the subnet address of the edge service provider in the second edge service provider. Based on the internal routing that does not match the tunnel of the second edge service provider, the data packet is sent to the second edge server subnet address; the server of the edge service provider obtains the content update of the server of the second edge service provider.

16. The application service system according to claim 15, characterized in that, The gateway of the edge service provider sets the routing priority of the network interface connecting to the high-speed fiber Internet to be the highest; the system reconstructs the high-speed tunnel, high-speed internal routing, and high-speed external routing; the gateway of the edge service provider sets the routing priorities of the network interfaces connecting to the high-speed fiber Internet to be the same, and the tunnel uses the original network interface address parameters to keep the tunnel, the internal routing, and the external routing consistent.

Images