JP7403030B2 - Content distribution routing on aircraft edge servers - Google Patents

Description

In a wireless communication system, a satellite communication system may provide in-flight entertainment for several devices communicatively coupled to a satellite terminal. The entertainment presented on the device may be content located onboard the aircraft, such as a movie set stored on a hard drive located on the aircraft. Media content stored onboard an aircraft may be limited due to size, weight, and power constraints onboard the aircraft. Therefore, limiting media content items for passengers only to media content stored on the aircraft may degrade the passenger's media experience.

The described features generally relate to providing a comprehensive system for requesting routing of content from a requesting client device to a server, including an onboard edge server. A content distribution network (CDN) may be defined that includes a server layer. The first server tier (eg, an aircraft-based edge server) may be an on-board server of various mobile vehicles, such as an aircraft. The second server tier may be servers located on the ground in various regions. Subsequent server tiers may be connected to the second server tier. Different servers may store or have access to different media content items. The techniques described herein process requests for media content items across this layered connectivity topology.

A request routing system may route requests for media content items from devices located within a mobile platform connected to a satellite terminal in a satellite communication system. For example, each customer or passenger may use a device located onboard the aircraft to request media content items that may or may not be stored onboard the aircraft. The techniques described herein may route requests from a requesting client device to an onboard edge server or to a ground server to locate a source that has access to a media content item. For example, a passenger on an airplane may request a movie to play on the passenger's mobile device. A CDN domain name system (DNS) (eg, on the ground or onboard an aircraft) may receive the request and determine whether the requested media content item is already stored onboard the aircraft. If the requested media content item is stored onboard the aircraft, the onboard edge server provides the media content item to the mobile device. However, if the requested media content item is not stored onboard the aircraft, the system routes the request along with the media content to a ground server (e.g., directly or through another ground server) and, in some cases, Different servers may be associated with different content providers and may have access to different materials. The media content item may be an on-demand content item or a live-streamed content item.

The techniques described herein provide different ways to use the topography of the network to serve content to client devices, perform handovers, and maintain and update the CDN layer connection topology. Once the server containing the requested media content item is found, the CDN may provide the onboard edge server or client device with the network address of the server containing the requested media content item. In some examples, the server is selected because it may be the closest server to the client device in terms of network proximity, but not necessarily geographic location. The client device or edge server then requests the media content item from the server. The server may stream media content items to the client device as long as the aircraft remains within the coverage area of one or more satellite access nodes associated with the server. Once the aircraft begins to fly out of the coverage area, a handover to another server containing the requested media content item may be performed.

The foregoing has outlined rather broadly the features and technical advantages of examples according to this disclosure in order that the detailed description that follows may be better understood. Further features and advantages are described below. The concepts and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The nature of the concepts disclosed herein, both their organization and method of operation, and associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Dew. Each of the figures is provided for purposes of illustration and description only, and not as a definition of a limitation on the scope of the claims.

A further understanding of the nature and advantages of the present disclosure can be realized by reference to the following drawings. In the accompanying drawings, similar components or features may have the same reference label. Additionally, various components of the same type may be distinguished by following reference labels with a dash and a second label that distinguishes among similar components. If only a first reference label is used herein, the description applies to any one of the similar components having the same first reference label, regardless of the second reference label. It is possible.

FIG. 1 depicts a diagram of a satellite communications environment in accordance with aspects of the present disclosure. FIG. 2 depicts a diagram of a satellite communications environment in accordance with aspects of the present disclosure. FIG. 3 illustrates a block diagram of an example satellite path in a satellite communications environment, in accordance with various aspects of the present disclosure. FIG. 4 depicts a block diagram of an example terrestrial content distribution network hierarchy in a satellite communication environment in accordance with various aspects of the present disclosure. FIG. 5 illustrates a block diagram of an example terrestrial content distribution network hierarchy in a satellite communication environment in accordance with aspects of the present disclosure. FIG. 6 illustrates an example content distribution routing process flow for an aircraft-based edge server in accordance with various aspects of the present disclosure. FIG. 7 illustrates an example content distribution routing process flow using an aircraft-based edge server in accordance with various aspects of the present disclosure. FIG. 8 illustrates an example content delivery routing process flow using an aircraft-based edge server in accordance with various aspects of the present disclosure. FIG. 9 depicts a diagram of example content distribution routing using an onboard edge server in accordance with various aspects of the present disclosure. 10A and 10B illustrate network handoff diagrams of example layer connection topologies in accordance with various aspects of the present disclosure. FIG. 11 depicts a flowchart illustrating an example method of layer connection management in accordance with aspects of the present disclosure. FIG. 12 depicts a flowchart illustrating an example method for performing handover during content delivery to an onboard client device, according to aspects of the present disclosure. FIG. 13 depicts a flowchart illustrating an example method for performing handover during content delivery to an onboard client device, in accordance with aspects of the present disclosure. FIG. 14 depicts a flowchart illustrating an example method for content distribution routing using an aircraft-based edge server in accordance with various aspects of the present disclosure. FIG. 15 depicts a flowchart illustrating an example method for content distribution routing using an aircraft-based edge server in accordance with various aspects of the present disclosure. FIG. 16 depicts a flowchart illustrating an example method for content distribution routing using an aircraft-based edge server in accordance with various aspects of the present disclosure.

A satellite terminal (eg, a multi-user access terminal) within a satellite communication system may employ a communication antenna to establish a communication link between the satellite terminal and the communication satellite. A communication link may be configured for bidirectional communication (eg, transmit and receive, etc.) or unidirectional communication (eg, receive) in some cases. Such communication links may provide communication services between ground-based networks and mobile platforms, including satellite terminals. These communication links may be used to provide services to devices for passengers located on the mobile platform (eg, user devices such as cell phones, tablets, and laptops).

The techniques described herein provide content items, such as media items, at a client device located on a mobile platform aircraft, such as an aircraft, with connectivity to an external network via a satellite communication system. Satellite communication systems relay network traffic for particular content items between client devices and content distribution networks. That is, the techniques described herein provide for delivery of content to client devices on a mobile platform via a content distribution network while the mobile platform is en route. Content distribution networks may include terrestrial servers located on the ground and edge servers located on mobile platforms such as aircraft, ships, trains, spacecraft, etc. A content distribution network may include one or more terrestrial server tiers and one or more edge server tiers. The satellite terminal may connect a mobile edge server of an edge server tier of the content distribution network to at least one terrestrial server of a terrestrial server tier of the content distribution network via one or more satellite communication links. Content stored on one or more terrestrial server tiers may be provided to a mobile edge server or directly to a client device via a satellite communication link. A mobile edge server may transfer content to client devices on mobile platforms.

According to aspects of the present disclosure, a content distribution network may provide one or more content items to a satellite terminal. A satellite terminal may provide content items to devices onboard a mobile platform that is in communication with the satellite terminal. A CDN may locate the closest server in terms of network proximity to the client device. A CDN may use a content replication system to determine which server has the requested media content item. Once a suitable source is located, the CDN may provide the server's network address to the client device or associated edge server. A client device or edge server may use the network address to obtain media content items from the server.

In some examples, the CDN returns the address of the associated edge server to the client device. The client device may then request media content items from the edge server. If the edge server stores the media content item, the edge server may serve the media content item to the client device. If the edge server does not store the media content item, the edge server may then begin requesting media content items through the connected server tier.

The techniques described herein may also allow a CDN to push media content items to different servers for storage. For example, a CDN may command media content items stored on a remote server to be pushed to a closer server or even to an edge server.

In some examples, content items may be on-demand or live-streamed. A satellite terminal may facilitate access to content items by acting as a relay for network activity. In some examples, content items may be multicast as a live stream, where the live content is streamed to multiple devices simultaneously.

This specification provides examples and is not intended to limit the scope, applicability, or configuration of embodiments of the principles described herein. Rather, the following description will provide those skilled in the art with an enabling explanation for implementing embodiments of the principles described herein. Various changes may be made in the function and arrangement of elements.

Accordingly, various embodiments may omit, substitute, or add various steps or components as appropriate. For example, it is to be understood that the methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, aspects and elements described with respect to particular embodiments may be combined in various other embodiments. Additionally, the following systems, methods, devices, and software, individually or collectively, may be components of a larger system, and other procedures may supersede their application or provide other methods. It is understood that you may modify those applications.

FIG. 1 depicts a diagram of a satellite communication environment 100 in accordance with aspects of the present disclosure. Satellite communications environment 100 includes a wireless communications system 105, and in the example shown in FIG. 1, wireless communications system 105 is a communications satellite system. Exemplary satellite communication system 105 includes one or more communication satellites 102, one or more gateways 110, and one or more satellite terminals 112. Satellite terminal 112 may be a multi-user access terminal that provides network access connectivity to multiple user devices on mobile platform 160. Satellite communication environment 100 may include CDN 122. CDN 122 may include one or more mobile platform edge servers 170, a terrestrial CDN tier 120, and one or more origin servers 130.

The one or more communications satellites 102 in the satellite communications system 105 may include any suitable type of communications satellite configured for wireless communication with one or more gateways 110 and one or more satellite terminals 112. . In some examples, some or all of the communication satellites 102 may be in geostationary orbit such that their position relative to ground devices may be relatively fixed or subject to operating tolerances or other orbital windows. can be fixed within. In other examples, any suitable orbit (eg, low earth orbit (LEO), medium earth orbit (MEO), etc.) for one or more communication satellites 102 of satellite communication system 100 may be used.

Satellite terminal 112 may include a satellite terminal communications antenna configured to receive signals 106 from communications satellite 102 and transmit signals 106 to communications satellite 102 . Thus, satellite terminal 112 may be configured for unidirectional or bidirectional communication with one or more communication satellites 102 of satellite communication system 105. In some examples, the satellite terminal communication antenna may be directional. For example, a satellite terminal communications antenna may have a peak gain (eg, antenna boresight) along the principal axis. In some examples, the peak gain may roll off sharply in an off-axis direction. A steep roll-off in antenna gain may be referred to as a narrow field of view of the antenna. In some examples, a satellite terminal communication antenna may be configured with a narrow field of view through a fixed configuration of focusing and/or reflecting elements, such as a parabolic dish reflector or an antenna with an array of antenna elements. The satellite terminal communications antenna may be positioned (eg, to point at communications satellite 102) by a positioner (eg, an elevation/azimuth positioner). In some examples, a satellite terminal communication antenna may be configured with a narrow field of view via beamforming, where the field of view includes an array of antenna elements for signal transmission and/or reception along a desired direction. may be electronically configurable.

Communication satellites 102 may communicate via service beams 108 directed at service beam coverage areas 109 that include satellite terminals 112 . For illustrative purposes, FIG. 1 shows a collection of service beams 108, each service beam 108 may be associated with a service beam coverage area 109. Service beam coverage area 109 may cover any suitable service area (e.g., circular, elliptical, hexagonal, local, regional, national, etc.) and may include any number of satellites located within service beam coverage area 109. Services may be provided to terminal 112. In some examples, communications satellite 102 may be a multi-beam satellite, with multiple service beams 108 covering multiple service beam coverage areas 109 that may or may not overlap with adjacent service beam coverage areas. may have.

Communications satellite 102 may transmit a forward link signal in signal 106 via service beam 108 that is received by satellite terminal 112 . Satellite terminal 112 may receive forward link signals using a satellite terminal communication antenna. In order to establish a suitable communications link for the forward link signal between satellite terminal 112 and communications satellite 102, the forward link signal is based on the transmission power of communications satellite 102, the alignment and position of the satellite terminal communications antenna, and the satellite received at a satellite terminal 112 with a signal strength or signal-to-noise ratio (SNR) above a threshold, which may depend on the attenuation environment around the terminal communication antenna (e.g., the attenuation environment between the satellite terminal 112 and the communication satellite 102); can be done.

Communications satellite 102 may communicate with one or more of gateways 110 by transmitting and/or receiving signals 104 via one or more gateway beams 132, each of which is connected to a respective gateway. May be associated with beam coverage area 136. Gateway beam 132 may, for example, carry communications traffic for one or more satellite terminals 112 (eg, relayed by communications satellite 102) or other communications between communications satellite 102 and gateway 110.

Satellite terminal 112 may transmit a return link signal via signal 106 to communication satellite 102, and communication satellite 102 may relay the return link signal via signal 104 to one or more gateways 110. In order to establish a suitable communication link for the return link signal between the satellite terminal 112 and the communication satellite 102, the return link signal also depends on the transmission power of the satellite terminal 112, the alignment of the satellite terminal communication antenna of the satellite terminal 112, etc. received at a communications satellite 102 with a signal strength and/or SNR above a threshold, which may depend on the location and the attenuation environment around the satellite terminal communications antenna (e.g., the attenuation environment between the satellite terminal 112 and the communications satellite 102). can be done. For example, a satellite terminal communications antenna may be configured to detect a target (e.g., a communications satellite) when the satellite terminal 112's transmitted signal has sufficient antenna gain in the direction of the target to enable signal communication with desired performance characteristics. 102) can be considered to be accurately aligned.

Satellite terminal 112 may be part of a satellite terminal antenna assembly, which may also include various hardware for mounting a satellite terminal antenna that may be attached to mobile platform 160. Mobile platform 160 may carry or be coupled to satellite terminal 112, which may include a satellite terminal assembly and a satellite terminal receiver. The satellite terminal antenna assembly also converts between radio frequency (RF) satellite communication signals (e.g., signal 106) and satellite terminal communication signals transmitted between the satellite terminal communication antenna and the satellite terminal receiver. For example, it may include circuitry and/or processors for performing frequency conversion, modulation/demodulation, multiplexing/demultiplexing, filtering, forwarding, etc.). Such circuits and/or processors may be included in an antenna communications assembly, which may be mounted outside the mobile platform 160 (eg, outside the fuselage of an aircraft). Additionally or alternatively, the satellite terminal receiver includes circuitry and/or a processor for performing various RF signal operations (e.g., receiving, performing frequency conversion, modulating/demodulating, multiplexing/demultiplexing, etc.) May include.

Satellite terminal 112 may be connected via a wired or wireless connection to one or more devices within mobile platform 160 and provides streamed network access, specific to each of the devices, via satellite communication environment 100. Multiple content offerings may be provided, such as services (eg, Internet access, content items, etc.) or other communication services (eg, broadcast media, etc.). Devices within mobile platform 160 include, but are not limited to, mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, or other devices for connectivity or content consumption. may include user devices such as other display devices (eg, televisions, computer monitors, etc.) used for display purposes. In some examples, satellite terminal 112 provides two-way communication between the device and terrestrial CDN layer 120 via communication satellite 102 and gateway 110.

Satellite communications environment 100 (including communications satellite 102, gateway 110, satellite terminal 112, etc.) may operate in one or more frequency bands. For example, a wireless communication system may operate in the International Telecommunication Union (ITU) Ku, K, or Ka band, C band, X band, S band, L band, etc.

Satellite terminal 112 may be located on mobile platform 160. Mobile platform 160 may be any device, apparatus, or object capable of supporting and relocating satellite terminal 112. For example, mobile platform 160 may be a mobile platform carrier such as an aircraft, a ship, a vehicle (eg, a car, a bus, a train), a spacecraft, or the like. As illustrated in FIG. 1, mobile platform 160 is an aircraft, but in other examples, other types of mobile platforms, such as boats, ships, trains, or buses, may be connected to satellite terminal 112 and/or A server 170 may be included. FIG. 1 shows three mobile platforms 160, a first mobile platform 160-1 with a first edge server 170-1, a second mobile platform 160-2 with a second edge server 170-2, and a second mobile platform 160-2 with a second edge server 170-2. An nth mobile platform 160-n is depicted having n edge servers 170-n.

One or more gateways 110 may transmit and receive signals 104 to and from communication satellites 102 of a satellite communication system using gateway antenna systems. The gateway antenna system is bidirectional and can be designed with moderate transmit power and receive sensitivity to reliably communicate with at least one communication satellite 102 of the satellite communication system. Gateway 110 may also communicate with terrestrial content distribution network layer 120. Satellite terminals 112 within satellite communication environment 100 may access terrestrial CDN layer 120 via one or more gateways 110. Terrestrial CDN layer 120 may include a local area network (LAN), metropolitan area network (MAN), wide area network (WAN), or any other suitable public or private network, and may include the Internet, telephone network (e.g. , public switched telephone network (PSTN), etc.).

Terrestrial CDN layer 120 may represent the terrestrial portion of a content distribution network and may include one or more server tiers. Each server tier may include one or more servers. In some examples, the server tier includes multiple servers located throughout a geographic area. A server may store or have access to stored media content items. Some of the media content items may be stored on only one server, or may be stored on only one server, while other media content items may be stored on multiple servers. , or may be stored on multiple servers. In some examples, each of the servers in a server tier stores the same content items, while in other examples, a server in a server tier stores at least some content items relative to other servers in that server tier. Unique media content items may be stored.

Terrestrial CDN hierarchy 120 may include two or more server tiers and one or more origin servers 130. The first server tier may include a first amount of servers geographically distributed throughout the service area. The second server tier may include a second server quantity that is less than the first server quantity. Although the second server tier may also be geographically distributed, the second server tier generally includes connections between or peripheral connections between servers in a network (e.g., where users or gateways 110 may be located) and a second The server tier may have greater geographic or networking distance with any given server. In some examples, servers in the second server tier may generally store more content (eg, have greater storage capacity) than servers in the first server tier.

One or more origin servers 130 may be part of the terrestrial CDN hierarchy 120 as the last server tier. That is, there may not be another server tier connected after the origin server 130. For example, the terrestrial CDN layer 120 connects a first server tier, a second server tier connected to the first server tier, a third server tier connected to the second server tier, etc. The layers may be connected to one or more origin servers 130.

Origin server 130 may represent one or more servers that ultimately store media content items that are replicated throughout a content distribution network. That is, one or more of the media content items stored on origin server 130 may be copied onto other servers in other server tiers. In some examples, origin server 130 may include media content items that are not stored on any other server. In such a case, origin server 130 serves the media content item when requested. In some examples, origin server 130 may be associated with a content provider and may be separate from CDN hierarchy 120. Thus, CDN 122 may serve CDN services for one or more content providers, with each content provider associated with a different origin server 130.

A terrestrial server (eg, of a first server tier of terrestrial CDN hierarchy 120) may be coupled with gateway 110 and one or more other servers. In various examples, the terrestrial servers may be co-located or otherwise located near one or more gateways 110, or may be intertwined with the terrestrial network serving the gateways 110 and other networks. may be installed at an Internet Exchange Point (IXP) between Thus, the terrestrial server may communicate with the gateway 110 and/or the terrestrial CDN layer 120 via one or more wired and/or wireless communication links.

Terrestrial CDN hierarchy 120 may include a content replication system 140 and a domain name system 150. Content replication system 140 may manage and control the operation of content distribution network 122, including terrestrial CDN tier 120 and edge servers 170. Domain name system 150 may maintain a list of domain names and addresses for each server in CDN 122 and one or more origin servers 130 (eg, if external to CDN 122). Domain name system 150 may be queried when satellite communication environment 100 receives a request for a media content item (eg, from a device on mobile platform 160). Portions of content replication system 140 and domain name system 150 may be located in various servers of CDN 122, including terrestrial servers, origin servers 130, or edge servers 170.

As described, CDN 122 includes a terrestrial CDN tier 120 and a plurality of mobile edge servers 170. This network topology provides flexibility in what media content is stored on the onboard mobile platform. For example, due to aircraft size, weight, and power (SWaP) requirements, CDN 122 may have a "hybrid" CDN topology. That is, due to SWaP requirements, edge server 170 may have relatively low storage capacity compared to at least some of the servers in terrestrial CDN tier 120. For example, a server in terrestrial CDN tier 120 may effectively be a high-capacity data center. This topology allows devices on mobile platform 160 to access a much greater amount of media content than would otherwise be available on airborne mobile platform 160. make it possible. In some examples, the number of edge servers 170 may be greater than the number of servers in terrestrial CDN tier 120. In other words, multiple edge servers 170 may be associated with the same server in terrestrial CDN hierarchy 120. Association may mean that the ground server and one or more edge servers may be connected in a network layer connection topology.

Satellite communication environment 100 may route media content items to one or more devices on mobile platform 160 in response to requests for media content items using techniques described herein. Media content may be provided regardless of the location of mobile platform 160. Satellite communication environment 100 may provide communication between onboard devices and a ground-based CDN that hosts media content items. These techniques reduce costs, improve streaming functionality, ease the size, weight, and power requirements of onboard mobile platforms, and deliver more personalized and relevant media content items to passengers. and reduce network traffic.

FIG. 2 depicts a diagram of a wireless environment 200 in accordance with various aspects of the present disclosure. The communication environment 200 is a wireless communication system illustrated in FIG. 2 as a satellite communication system that includes at least one satellite 102-a, a gateway 110-a, and a satellite terminal 112-a onboard a mobile platform 160-a (eg, an aircraft). It includes a communication system 105-a. Communication environment 200 also includes a CDN 122-a, which may include a terrestrial CDN layer 120-a, an origin server 130-a, and an edge server 170-a onboard a mobile platform 160-a. Terrestrial CDN layer 120-a may communicate with gateway 110-a. In operation, the wireless communication system 105-a connects devices on the mobile platform 160-a, including the edge server 170-a, and terrestrial networks, including the terrestrial CDN layer 120-a and other networks (e.g., the Internet). Provides two-way communication between The satellite 102-a, gateway 110-a, satellite terminal 112-a, origin server 130-a, and terrestrial CDN layer 120-a are respectively the satellite 102, gateway 110, satellite terminal 112, origin server 130, and terrestrial CDN layer 120-a in FIG. and terrestrial CDN layer 120 or may include aspects of these.

One or more satellites 102-a in satellite communication system 105-a may include any suitable type of communication satellite. In some examples, some or all of the satellites may be in geosynchronous orbit or geostationary earth orbit (GEO). In other examples, any suitable orbit (e.g., medium earth orbit (MEO), low earth orbit (LEO), etc.) may be used for satellite communication system 105-a. . Some or all of the satellites 102-a of the satellite communication system 105-a may be multi-beam satellites configured to serve multiple service beam coverage areas in a given geographic service area.

Gateway 110-a is bidirectional and may be designed with adequate transmit power and receive sensitivity to reliably communicate with satellite communication system 105-a. Satellite communication system 105-a may communicate with gateway 110-a by transmitting and receiving signals 104-a over one or more beams. Gateway 110-a transmits and receives signals 104-a to and from satellite communication system 105-a using a gateway antenna system. Gateway 110-a may be connected to one or more networks and terrestrial CDN layers 120-a.

Terrestrial CDN tier 120-a may include content replication system 140-a. Content replication system 140-a may include a replication manager 240, a server index 242, a CDN domain name system (DNS) 244, and a tier connectivity topology 246. Replication manager 240 may manage the replication of content within terrestrial CDN tier 120-a and airborne edge servers, such as edge server 170-a. Media content items may only be stored on a single server, or media content items may be replicated on two or more servers. For example, newer or more popular media content items may be stored on a number of servers, which may include ground servers or airborne edge servers. In contrast, obscure, outdated, or less popular media content items may be stored on fewer servers. Replication manager 240 may track where media content items are stored, control the replication of particular media content items on particular servers, provide commands for replication or deletion, etc. Replication manager 240 may use server index 242 to determine where media content items are stored. Server index 242 may be an index of content stored on an edge server, such as onboard edge server 170-a, and on each of the various servers in terrestrial CDN tier 120-a.

CDN DNS 244 may receive domain name system queries for requested content items that may be generated based on requests for content made by client device 220 or 222. CDN DNS 244 may resolve DNS queries for requested content. CDN DNS 244 may map DNS requests to appropriate CDN servers to enable requesting client device 220 or 222 to obtain the requested content. A suitable CDN server may be part of the terrestrial CDN hierarchy 120-a or may be an edge server. Mapping the DNS request to the appropriate CDN server may be preceded by an initial DNS request to a non-CDN DNS server (hereinafter referred to as a "DNS resolver") that redirects the DNS query to the CDN DNS 244. CDN DNS 244 may use server index 242 and layer connectivity topology 246 to determine the closest server currently storing the requested content.

CDN DNS 244 may use a variety of techniques to resolve DNS queries. For example, each satellite access node (or other entity in satellite communication system 105, such as a core node) may include a DNS resolver that receives DNS queries from client devices 220 or 222. As another example, each aircraft 160-a may include a DNS resolver. The DNS resolver may append information to the DNS query and provide the modified DNS query to CDN DNS 244. For example, the added information may identify the aircraft from which the request originated. In such a case, CDN DNS 244 may store a table indicating which aircraft has which edge servers, and reference the identifying information to determine the edge server on the aircraft from which the request originated. As another example, the added information may identify an edge server on an aircraft. Upon determining the edge server on the aircraft, the CDN DNS may then use layer connectivity topology 246 to return the address of the appropriate CDN server to client device 220 or 222 (e.g., as illustrated in FIGS. 6-8). using some of the techniques described above).

In some examples, such as the example illustrated in FIG. 6, CDN DNS 244 may return the address of the closest server from which the requesting client device 220 or 222 can then obtain content. In examples where CDN DNS 244 returns the address of the server closest to the requesting client device (nearest in network proximity, not necessarily physical proximity) that currently stores the requested content, CDN DNS 244 returns Index 242 may be used to determine whether a particular server currently stores content. In an alternative example, such as the example illustrated in FIG. , or is responsible for retrieving content from a locally stored copy.

Tier connectivity topology 246 manages the association or relationship between edge servers and servers in terrestrial CDN tier 120-a. For example, layer connectivity topology 246 may tell how different servers are connected to each other in various networks. Tier connectivity topology 246 may also know which servers are in which tiers of terrestrial CDN hierarchy 120-a.

CDN DNS 244 may use layer connectivity topology 246 to return the address of the appropriate CDN server to client device 220 or 222. Tier connectivity topology 246 may also be used by a given CDN server in terrestrial CDN tier 120-a to request content from which "upstream" server if a given CDN server does not currently store the content. You can know what to do. For example, a tier connectivity topology between an onboard edge server and a tier 2 server (or servers) may allow the onboard edge server to retrieve requested content that is not currently stored on the onboard edge server. It is a place where you can.

In examples where there are multiple server tiers in the terrestrial CDN hierarchy 120-a, the tier connectivity topology 246 may indicate the relationships between the servers in those various tiers. Content replication system 140-a may distribute tier connectivity topology information to various servers of the CDN (eg, CDN 122) and may send updates as needed due to changes in the tier connectivity topology. In particular, due to the mobility of aircraft 160-a, the satellite access node serving aircraft 106-a may change as aircraft 106-a moves to a different user beam. As a result, the server in the terrestrial CDN tier 120-a that is closest in network proximity to the edge server on the aircraft 160-a may change over time. Thus, content replication system 140-a may update tier connectivity topology 246 of edge server 170-a to improve content delivery. In addition to network proximity, content replication system 140-a may take other factors into account (eg, load balancing, network speed, etc.) when managing tier connectivity topology 246.

Aircraft communications equipment 206 includes satellite terminal 112-a (which may be, be part of, or include aspects of a multi-user access terminal), edge server 170-a, network access unit 214, wireless access point 216 and user devices 220 and 222. Satellite terminal 112-a may include one or more mobile terminal antennas, a transceiver 210, and a modem 212.

Aircraft 160-a includes aircraft communications equipment 206 that includes a satellite terminal 112-a that includes an antenna, which may be an antenna array. Aircraft 160-a may communicate with satellite communication system 105-a via one or more signals 108-a using the antenna of satellite terminal 112-a. Portions of the satellite terminal 112-a (eg, antenna, transceiver 210) may be mounted outside the fuselage or elsewhere on the exterior of the aircraft 160-a, and may be located under the radome. In other examples, other types of housings may be used to house portions of satellite terminal 112-a. Other parts of satellite terminal 112-a may be on the interior of the aircraft (eg, modem 212). Satellite terminal 112-a may operate in ITU Ku, K, or Ka bands. Alternatively, satellite terminal 112-a may operate in other frequency bands, such as C-band, X-band, S-band, L-band, etc.

The data transmitted to the satellite communication system 105-a via the downlink and uplink via one or more signals 104-a and 108-a may be customized to the satellite or other in the industry. may be formatted using a modulation and coding scheme (MCS) that may be similar to . For example, an MCS may have multiple coding rates, each associated with a modulation technique (e.g., BPSK, QPSK, 16QAM, 64QAM, 256QAM, etc.) and a coding rate based on the ratio of coded information bits to the total number of coded bits, including redundant information. May contain code points.

Edge server 170-a may be located onboard aircraft 160-a and may include a processor 230, a network interface 232, and memory 234. Processor 230 may execute instructions stored in memory 234 to perform the functions of edge server 170-a. Memory 234 may store instructions for the operation of edge server 170-a, a local copy of the content, and may also store an index 236. Index 236 may be an index of content stored in memory 234. In some examples, index 236 may be an index of content stored on another server and indicate where the content is stored. Index 236 may be used to determine whether the requested content is stored locally and whether the requested content can be retrieved.

The onboard communications system of aircraft 160-a may provide communication services to client devices 220 and 222 of aircraft 160-a via modem 212. Client devices 220 and 222 may connect to and access terrestrial CDN layer 120-a via modem 212. Client devices 220 and 222 may be mobile devices or other devices within aircraft 160-a. Client devices 220 and 222 are connected to a modem via network access unit 214, which may provide network services such as DNS, IP address management (e.g., Dynamic Host Configuration Protocol (DHCP)), network address translation (NAT), etc. 212. Client device 220 or 222 may connect to network access unit 214 via a wired or wireless connection. For example, client device 222 may connect to network access unit 214 via a wireless access point (WAP) 216 that may provide wireless connectivity within aircraft 160-a. The wireless connectivity may, for example, follow a wireless local area network (WLAN) technology, such as IEEE 802.11 (Wi-Fi), or other wireless communication technology.

In the example of FIG. 222) are shown. In other examples, other numbers of devices 220 and 222 may be included. Client device 220 may be a mobile device, such as a wireless device, remote device, handheld device, subscriber device, or some other suitable terminology, where "device" also refers to a unit, station, terminal, or client. may be called. Client device 220 may also be a personal electronic device such as a mobile phone, personal digital assistant (PDA), tablet computer, laptop computer, personal computer, or the like. Client device 222 may be a device located within aircraft 160-a, such as a seatback display screen or monitor.

Client device 220 or 222 may generate a request for a content item. For example, a user associated with client device 220-a can use the connectivity provided by WAP 216, network access unit 214, and satellite terminal 112-a to access a media provider associated with CDN 122-a. (eg, a connection to origin server 130-a or other servers in terrestrial CDN hierarchy 120-a). Upon selecting a content item to accept, the user submits a request for the content item that may identify the selected content item and any other related information, including requested functionality, content duration, related content, recommended content, etc. The client device 220 may be prompted to send the . CDN 122-a may be used to serve content to client device 220-a. For example, if the content is stored locally on edge server 170-a, edge server 170-a may serve the content (eg, via network access unit 214 and WAP 216). If the content is not stored locally, servers in terrestrial CDN tier 120-a may serve the content (eg, may be served via satellite terminal 112-a, network access unit 214, and WAP 216).

Satellite communication environment 200 may route requests for media content items to client devices on mobile platform 160 using techniques described herein. CDN 122-a may provide network addresses of one or more servers from which media content items may be obtained by client devices or associated edge server 170-a. Media content items may be provided regardless of the location of mobile platform 160 and by servers that may be geographically more distant than other servers storing media content items (e.g., satellite 102- (close in network topology considering connections via gateway 110-a and gateway 110-a). These techniques reduce costs, improve streaming functionality, alleviate size, weight, and power limitations of onboard mobile platforms, and provide passengers with more personalized and relevant media content items. or provide a wider range of media content items to passengers, or reduce network traffic.

FIG. 3 illustrates a block diagram of an example satellite track 310 in a communications environment 300, in accordance with various aspects of the present disclosure. Communication environment 300 includes a wireless communication system, depicted in FIG. 3 as satellite communication system 105-b. Satellite communication system 105-b includes at least one satellite 102-b and multiple satellite access nodes 110-b (also referred to herein as gateways 110-b). Communication environment 300 also includes a CDN 122-a, including a ground-based CDN hierarchy 120-b, an origin server 130-b, and edge servers 170-b located on various mobile platforms on an aircraft, which may be an aircraft. Satellite communication system 105-b, satellite 102-b, gateway 110-b, and CDN 122-b may be examples of or include satellite communication system 105, satellite 102, gateway 110, and CDN 122 of FIGS. 1 and 2. This may include the following aspects.

Satellite communication system 105-b may provide communication connectivity between satellite access node 110-b and edge server 170-b. Satellite access nodes 110-b may be distributed over a wide geographic area. Each satellite access node 110-b may use one or more of the satellite tracks 310 to communicate with a terminal (eg, mobile terminal 112) within the satellite communication system 105-b. Each satellite access node 110-b may communicate with terminals in one or more user beam groups 320 via satellite track 310.

The correspondence between gateway 110-b and user beam group 320 may be fixed or dynamic. In examples where the correspondence between satellite access nodes 110-b and user beam groups 320 is dynamic, the user beam groups 320 for a particular satellite access node 110-b may change over time. However, in the example of FIG. 3, the correspondence between satellite access nodes 110-b and user beam groups 320 is fixed, which means that the user beam groups associated with a particular satellite access node 110-b 320 means that it does not change over time. In some examples, the user beams within user beam group 320 are fixed, while in other examples, the user beams may be dynamic (eg, active or inactive).

As shown in FIG. 3, the aircraft and the aircraft edge server 170-b may communicate with a particular satellite access node 110-b depending on the user beam group 320 that the aircraft is within. Thus, as the aircraft moves between user beam groups 320, the aircraft may change which satellite access node 110-b provides connectivity. The correspondence between the onboard edge server 170-b and the user beam group 320 is represented by the user beam/edge server link 330, which is indicated by an arrow representing a change over time.

Edge server 170-b may provide content items to client devices onboard the aircraft. If a content item is not available on a given edge server 170-b, the content item may be retrieved from the origin server 130-b or from another server in the terrestrial CDN hierarchy 120-b. Which satellite access node 110-b provides connectivity to the requesting aircraft's edge server 170-b may depend on the aircraft's location at the time of requesting or distributing the content item. Because the communications satellite access node 110-b may change as the aircraft moves to different locations covered by different user beam groups 320, the proximity between the edge server 170-b and the servers of the terrestrial CDN hierarchy is May change over time.

FIG. 4 depicts a block diagram of an example content distribution network hierarchy 400 in a satellite communication environment in accordance with various aspects of the present disclosure. The content distribution network layer 400 includes an origin server 130-c, a terrestrial CDN layer 120-c, a plurality of satellite access nodes 110-c, a satellite track and user beam group 410, and an edge server layer 402 (e.g., edge server 170-c). -1, 170-c-2, and 170-c-n). The origin server 130-c, the terrestrial CDN tier 120-c, the plurality of satellite access nodes 110-c, the satellite track and user beam group 410, and the edge server layer 402 are the terrestrial CDN tier 120 of FIGS. 1-3, respectively. Gateway 110, satellite track 310, user beam group 320, user beam/edge server link 330, and edge server 170 may be examples or include aspects of these.

Servers within CDN hierarchy 400 may be grouped into different tiers. For example, an edge server layer 402, which may be onboard an aircraft, may be organized into the first layer of the CDN hierarchy 400. Terrestrial CDN tier 120-c may also be divided into one or more tiers, such as a second server tier 404 and an Nth server tier 406. There may be any number of server tiers between the second server tier 404 and the Nth server tier 406. Second server tier 404 and Nth server tier 406 may each include one or more servers that may store content items. The server tier may include servers that are geographically widespread.

When a content item is requested by a client device onboard an aircraft, the content distribution network layer 400 retrieves the content from the server layer closest in terms of network proximity to the requesting client device that stores the content item. Items can be retrieved. Content replication system 140-b may be used to manage content items within content distribution network hierarchy 400. If the content item is stored on an edge server on the aircraft, the content replication system 140-b retrieves the content from closest in network proximity to the aircraft, which would be the edge server on the aircraft in the first server tier 402. Take out the item. If the content item is not stored on-board, the content replication system 140-b may proceed according to the hierarchy to look for the content item down the server tier. For example, content replication system 140-b may query servers in second server tier 404 associated with a given edge server for content items. If the server in the second server tier 404 has the content item, the server in the second server tier 404 may provide the content item to the client device (eg, via the satellite access node 110-c). If a server in the second server tier 404 does not store the content item, the content replication system 140-b will update the associated server in the next server tier, which in the example of FIG. 4 is the Nth server tier 406. Please inquire. An associated server in the Nth server tier 406 may serve the content item if the associated server in the Nth server tier 406 stores the content item. Otherwise, content replication system 140-b proceeds to query associated servers in subsequent server tiers.

There may be an association between the airborne edge servers of the first server tier 402 and the satellite path/user beam group 410, and between the satellite access node 110-c and the servers of the terrestrial CDN tier 120-c. The association between the airborne edge servers of the first server tier 402 and the satellite track/user beam group 410 may change as the aircraft moves along its flight path. In contrast to the association between the airborne edge server in the first server tier 402 and the satellite access node 110-c that frequently changes as the aircraft moves, the satellite access node 110-c and the terrestrial CDN tier The association between 120-c and the server may be fixed. In some examples, the association between satellite access node 110-c and a server in terrestrial CDN hierarchy 120-c may not be fixed, but may change relatively infrequently (e.g., due to network upgrades, due to reconfiguration or maintenance). For example, the association between the satellite access node 110-c and the servers in the terrestrial CDN tier 120-c is greater than the association between the airborne edge servers in the first server tier 402 and the satellite path/user beam group 410. May change infrequently.

FIG. 5 depicts a block diagram of an example content distribution network hierarchy 500 in a satellite communication environment in accordance with various aspects of the present disclosure. The content distribution network layer 500 includes a first layer of an origin server 130-d, a terrestrial CDN layer 120-d, a plurality of satellite access nodes 110-d, a satellite path and user beam group 410-a, and an edge server 170-d. 402-a. The origin server 130-d, the terrestrial CDN hierarchy 120-d, the plurality of satellite access nodes 110-d, the satellite path/user beam group 410-a, and the edge server 170-d each correspond to the terrestrial CDN of FIGS. 1-4. Tier 120 , satellite access node or gateway 110 , satellite path 310 , user beam group 320 , user beam/edge server link 330 , first tier of edge server 170 402 , satellite path/user beam group 410 may be examples , or may include these aspects.

Servers within CDN hierarchy 500 may be grouped into different tiers, as in FIG. 4. For example, edge server tier 170-d, which may be onboard an aircraft, may be first server tier 402-a in CDN hierarchy 500. Terrestrial CDN tier 120-d may also be arranged by one or more tiers, such as a second server tier 404-a and a third server tier 406-a. Terrestrial CDN layer 120-d may include additional server layers other than the two shown in FIG. Terrestrial CDN layer 120-d may also include an origin server 130-d. Content replication system 140-c may be used to manage content items within content distribution network hierarchy 500.

Each server in a given server tier may be associated with one server in a higher (eg, N+1) server tier. For example, each server in the second server tier 404-a may be associated with one server in the third server tier 406-b, and so on. Each server in the Nth server tier may be associated with one or more servers in a lower (eg, N-1) server tier. In some cases, a given server may be associated with servers in non-adjacent server tiers. For example, a server in the second server tier 404-a may be associated with a server in a fourth server tier (e.g., there are no servers in the third server tier that are in network proximity to servers in the second server tier). case).

For example, each edge server 170-d of the first server tier 402-a may be associated with one server 522 of the second server tier 404-a. The association of edge server 170-d with server 522 of second server tier 404-a is such that edge server 170-d is associated with satellite access node 110-d serving the user beam serving the aircraft in which edge server 170-d is located. may be based on network proximity between For example, edge server 170-d onboard an aircraft that is within a user beam served by satellite access node 110-d-1 (eg, via satellite path/user beam group 410-a) may may be associated with server 522-a of server tier 404-a. A server 522 of the second server tier 404-a may be associated with an edge server 170-d in a beam group served by multiple satellite access nodes 110-d. For example, edge server 170-d onboard an aircraft that is within a user beam served by satellite access node 110-d-2 (eg, via satellite path/user beam group 410-a) may also The second server tier 404-a may be associated with the server 522-a of the second server tier 404-a. Also, as illustrated in FIG. Edge servers 170-d onboard an aircraft located at may be associated with servers 522-b and 522-n, respectively, of second server tier 404-a.

Similarly, servers in the third server tier 406-a may each be associated with one server in a higher server tier and one or more servers in a lower server tier. For example, servers 522-a and 522-b of second server tier 404-a are associated with server 532-a of third server tier 406-a, while server 522-c is associated with server 522-a of third server tier 406-a. It is associated with server 532-b of server layer 406-a. Each of the highest tier servers in terrestrial CDN hierarchy 120-d may be associated with an origin server 130-d. Thus, each branch of terrestrial CDN hierarchy 120-d may terminate at an origin server 130-d. In some cases, CDN hierarchy 120-d may represent a network topology of servers within the hierarchy. For example, the servers in a given server tier may not communicate directly with each other, or the network connectivity topology for CDN tier 120-d may not include connections between servers in a given server tier.

CDN DNS 244-a may use these associations when determining which server containing the content item is closest in terms of network proximity to the requesting client device or onboard edge server. Associations may be used to retrieve content items.

FIG. 6 depicts an example content distribution routing process flow 600 for an airborne edge server 170-b in accordance with various aspects of the present disclosure. Process flow 600 includes origin server 130-e, CDN DNS 244-b, second tier server 522-db, edge server 170-e, aircraft 160-b, and client device 220-c. Origin server 130-e, CDN DNS 244-a, second tier server 522-d, edge server 170-e, aircraft 160-b, and client device 220-c each correspond to origin server 130 of FIGS. 1-5. , CDN DNS 244, second tier server 522, edge server 170, aircraft 160, and client device 220 or 222. In some examples, process flow 600 may be performed by at least a portion of a content distribution network hierarchy or satellite communication environment described in FIGS. 1-5.

Process flow 600 illustrates actions taken by different devices in line over time as requests for content items are processed. Process flow 600 provides an example of how requests for content items may be generated, routed, processed, and fulfilled by one or more different servers. In particular, process flow 600 illustrates how a request for a content item, Item A, may be routed through a content distribution network hierarchy. In this example, the CDN DNS 244-a uses the server indexes of the edge server tier and the second server tier to identify the edge server 170-e, the corresponding tier 2 server (e.g., the second tier server 522-d) , or return the network address of origin server 130-e. In the example of FIG. 6, only two server tiers (edge server tier and second server tier) are shown. In other examples, there may be more than two server tiers.

Aircraft 160-b may include an edge server 170-e and client device 220-c. Aircraft 160-b may include two or more client devices, an example of which may be client device 220 or 222 as described in FIG. Client device 220-c initiates a request for content item A, which can be a multimedia item, movie, game, show, live streaming event, etc. At 602, a domain name system request for item A is generated. The DNS request is forwarded to CDN DNS 244-a. For example, CDN DNS 244-a may be associated with the content provider for content item A, and requests (eg, HTTP requests) for content item A may be made to the content provider address.

At 604, CDN DNS 244-a may determine edge server 170-b located on aircraft 160-b. The determination may include identifying aircraft 160-b and which edge server among the plurality of edge servers is located onboard aircraft 160-b. Identifying the aircraft may include referencing the sending address of the request (which may be associated with a network access unit 214 that may encapsulate or perform NAT for the request). Identifying the edge server may include sending a query to the aircraft 160-b, examining a database that indexes the aircraft and the edge server, and the like. Determining may further include determining a unique identifier or network address of edge server 170-b.

At 606, CDN DNS 244-a may determine whether item A is stored on edge server 170-b. If so, CDN DNS 244-a may return the address of edge server 170-b to client device 220-c at 608. For example, CDN DNS 244-a may send a redirect to client device 220-c using the address of edge server 170-b. At 620, client device 220-c may request item A from edge server 170-b. Edge server 170-b may receive the request at 622 and provide item A to client device 220-c. Alternatively, CDN DNS 244-a may send the message directly to edge server 170-b, which then sends the message as if it were coming from the address of content provider or origin server 130-e. , may provide item A to client device 220-c. For example, CDN DNS 244-a may provide edge server 170-b with cryptographic or other information (eg, a secure socket layer (SSL) certificate) to respond directly to client device 220-c. At 624, client device 220-c may receive item A from edge server 170-b. Upon receiving item A, client device 220-c may display or otherwise output item A. In some examples, client device 220-c may query edge server 170-b directly for item A.

Returning to 606, if CDN DNS 244-a determines that item A is not stored on edge server 170-e, process flow 600 continues to 630. At 630, CDN DNS 244-a may determine the identity of a second tier server associated with edge server 170-e. In this example, second tier server 522-d is associated with edge server 170-e. At 632, CDN DNS 244-a determines whether Item A is stored on second tier server 522-d. If so, process flow 600 continues to 634, where CDN DNS 244-a returns the address of second tier server 522-d to client device 220-c (eg, in a redirect message). At 640, client device 220-c receives the address of second tier server 522-d and requests 642 item A from second tier server 522-d. Alternatively, CDN DNS 244-a may send a message directly to second tier server 522-d, which then sends a message from the address of content provider or origin server 130-e. As such, item A may be provided to client device 220-c. For example, CDN DNS 244-a may provide cryptographic or other information (eg, an SSL certificate) to second tier server 522-d for responding directly to client device 220-c. Second tier server 522-d may provide item A to client device 220-c. At 644, client device 220-c may receive item A from second tier server 522-d. Upon receiving item A, client device 220-c may display or otherwise output item A.

Returning to 632, if CDN DNS 244-a determines that item A is not stored on second tier server 522-d, process flow 600 continues to 650. At 650, CDN DNS 244-a provides the address of origin server 130-e to client device 220-c (eg, in a redirect message). At 652, client device 220-c may request item A from origin server 130-e at 654. Alternatively, CDN DNS 244-a may send a message directly to origin server 130-e, which then forwards item A to client device 220-e as if it were coming from the content provider's address. c. For example, CDN DNS 244-a may provide origin server 130-e with encryption or other information (eg, an SSL certificate) to respond directly to client device 220-c. Origin server 130-e may provide item A to client device 220-c at 656. Upon receiving item A at 656, client device 220-c may display or otherwise output item A.

The example of FIG. 6 shows only a single server tier between the edge server tier and the origin server. However, in examples with additional server layers, before CDN DNS 244-a returns the address of origin server 130-e to client device 220-c, CDN DNS 244-a queries the additional server layer for item A. You may. Upon determining that a server in the additional server layer stores item A, CDN DNS 244-a may send the address of that server to client device 220-c (e.g., in a redirect message) or may be instructed to respond to the request with item A.

In some examples, another device onboard the aircraft other than client device 220-c may be a recipient of the address of the server storing Item A. For example, a satellite terminal, transceiver, modem, network access unit, edge server, or wireless access point may receive and process the address (eg, acting as a proxy server for client device 220-c).

The example process flow 600 includes an edge server layer located on a mobile platform served by a wireless communication link of a communication system, and at least one terrestrial server layer geographically distributed within the communication system. A method for use in a communication system including a content distribution network. Process flow 600 may include receiving a request for a media content item from a device within a mobile platform served via a wireless communication link of a communication system. Process flow 600 may further include determining the identity of a mobile edge server located on the mobile platform based at least in part on the network address of the device associated with the request. Process flow 600 may determine whether a media content item is stored on a mobile edge server. If the media content item is stored on the mobile edge server, process flow 600 may redirect the request for the media content item to the mobile edge server. If the media content item is not stored on a mobile edge server, process flow 600 determines whether the media content item is stored on a first terrestrial server of a first server tier of the at least one terrestrial server tier. The first terrestrial server may be coupled to an access node (eg, a satellite access node) serving a mobile platform and associated with a mobile edge server for a content distribution network. If the media content item is stored on a first terrestrial server of the first server tier, process flow 600 may include redirecting a request for the media content item to the first terrestrial server.

FIG. 7 illustrates an example content delivery routing process flow 700 using an airborne edge server in accordance with various aspects of the present disclosure. Process flow 700 includes origin server 130-f, CDN DNS 244-b, second tier server 522-e, edge server 170-f, aircraft 160-c, and client device 220-d. Origin server 130-f, CDN DNS 244-b, second tier server 522-c, edge server 170-f, aircraft 160-c, and client device 220-d each correspond to origin server 130 of FIGS. 1-6. , CDN DNS 244, second tier server 522, edge server 170, aircraft 160, and client device 220 or 222. In some examples, process flow 700 may be performed by at least a portion of a content distribution network hierarchy or satellite communication environment described in FIGS. 1-5.

The example of FIG. 7 illustrates how requests for content items may be generated, routed, processed, and fulfilled by one or more different servers. In particular, process flow 700 illustrates how a request for a content item, Item A, may be routed through a content distribution network hierarchy. In process flow 700, CDN DNS 244-b may return the network address of edge server 170-f to client device 220-d whenever CDN DNS 244-b receives a request for a content item from client device 220-d. Edge server 170-f is then responsible for delivering content items to client devices 220-d. In the example of FIG. 7, only two server tiers (edge server tier and second server tier) are shown. Alternatively, there may be more than two server tiers.

Aircraft 160-c may include an edge server 170-f and client device 220-d. Aircraft 160-c may include two or more client devices, which may be client devices 220 or 222 as described in FIG. Client device 220-d may initiate a request for at least content item A, which may be a movie, game, show, live streaming event, etc. At 702, a domain name system request for item A is generated. The DNS request is forwarded to CDN DNS 244-b.

At 704, CDN DNS 244-b may determine edge server 170-f located on aircraft 160-c. The determining may include identifying which edge server among the plurality of edge servers is located onboard the aircraft 160-c, which may include sending a query to the aircraft 160-c, This may include examining a database that indexes the edge server, detecting the identifier of edge server 170-f in the DNS request for item A, and the like. Determining may further include determining a unique identifier or network address of edge server 170-f.

At 706, CDN DNS 244-b may return the address of edge server 170-f to client device 220-d (eg, in a redirect message). At 708, in response to receiving the address of edge server 170-f, client device 220-d may request item A from edge server 170-f. Edge server 170-f may receive the request and determine whether edge server 170-f stores item A at 710. If edge server 170-f stores item A, edge server 170-f provides item A to client device 220-d at 712. At 714, client device 220-d receives item A from edge server 170-f. Upon receiving item A, client device 220-d may display or otherwise output item A. In some examples, client device 220-d may directly query edge server 170-f for item A instead of going through a CDN DNS that is external to aircraft 160-c. Direct queries may be facilitated by a network access unit (e.g., network access unit 214) onboard aircraft 160-c (e.g., network access unit 214 resolves the address of the query to edge server 170-f). ).

Returning to 710, if edge server 170-f determines that edge server 170-f does not store item A, process flow 700 continues to 720. At 720, edge server 170-f may request item A from a second tier server associated with edge server 170-f. In this example, second tier server 522-e is associated with edge server 170-f. At 722, the second tier server 522-e determines whether the second tier server 522-e stores item A. If so, process flow 700 continues to 724 where second tier server 522-e provides item A to edge server 170-f. At 726, edge server 170-f may forward item A to client device 220-d. At 728, client device 220-d receives item A from edge server 170-f. Upon receiving item A, client device 220-d may display or otherwise output item A.

Returning to 722, if the second tier server 522-e determines that the second tier server 522-e does not store item A, the process flow 700 continues to 730. At 730, second tier server 522-e requests item A from origin server 130-f. In other examples with additional server tiers between the edge server tier and the origin server 130-f, the second tier server 522-e may , the next server layer may be queried for item A.

At 732, origin server 130-f receives the request for item A and provides item A to second tier server 522-e. At 734, second tier server 522-e receives item A and provides item A to edge server 170-f. Edge server 170-f may then provide item A to the client device at 736. Upon receiving item A at 738, client device 220-d may display, output, or otherwise use item A.

The example of FIG. 7 shows that each server supplies item A to neighboring servers in the CDN hierarchy. Alternatively, the requesting server may provide the next server with the address of edge server 170-f or client device 220-d. In such an example, the server storing item A may send item A directly to edge server 170-f or client device 220-d. For example, origin server 130-f may provide item A directly to edge server 170-f (eg, without passing through second tier server 522-e).

In some examples, rather than the edge server 170-f requesting item A from the second tier server 522-e as at 720, the edge server 170-f requests the client device 220-d from the second tier server 522-e. tier server 522-e. However, some content items may involve several requests, so due to the inherent delay in each round trip through the satellite network, this alternative may result in significant delays. In process flow 700, edge server 170-f may reduce the number of requests, eg, by receiving all or different portions of a content item in each request. For example, when a single request identifying a content item (e.g., a movie or other streaming content) is received at edge server 170-f, edge server 170-f may The request from the second tier server 522-e may directly respond to the request of the client device 220-d, thus not incurring delays for each request for a smaller portion of the content item.

The example process flow 700 includes an edge server layer located on a mobile platform served by a wireless communication link of a communication system, and at least one terrestrial server layer geographically distributed within the communication system. A method for use in a communication system including a content distribution network. Process flow 700 may include receiving, at a mobile edge server located on a mobile platform, a request for a media content item for a device within the mobile platform, where the request is from a server of a content delivery network external to the mobile platform. redirected. Process flow 700 further includes determining whether the media content item is stored on the mobile edge server and determining whether the media content item is stored on the mobile edge server to provide the media content item to the device. obtain. If the media content item is not stored on a mobile edge server, process flow 700 transfers at least one terrestrial server layer for the media content item via an access node serving the mobile platform via a wireless communication link. may receive media content items from the at least one terrestrial server and provide the media content items to the device.

FIG. 8 illustrates an example content delivery routing process flow 800 using an aircraft-based edge server in accordance with various aspects of the present disclosure. Process flow 800 includes origin server 130-g, CDN DNS 244-c, second tier server 522-f, edge server 170-g, aircraft 160-d, and client device 220-e. Origin server 130-g, CDN DNS 244-c, second tier server 522-f, edge server 170-g, aircraft 160-d, and client device 220-e each correspond to origin server 130 of FIGS. 1-7. , CDN DNS 244, second tier server 522, edge server 170, aircraft 160, and client device 220 or 222. In some examples, process flow 800 may be performed by at least a portion of a content distribution network hierarchy or satellite communication environment described in FIGS. 1-5.

The example of FIG. 8 illustrates how requests for content items may be generated, routed, processed, and fulfilled by one or more different servers, and decisions may be made to store the requested items on the various servers. Show that. In particular, process flow 800 illustrates how a request for a content item, Item A, is routed through the content delivery network hierarchy and a store decision/may not be made. . In process flow 800, CDN DNS 244-c sends the network address of edge server 170-g (e.g., in a redirect message) to client device 220-e when CDN DNS 244-c receives a request for a content item from client device 220-e. It can be returned to e. CDN DNS 244-c may also determine whether to store the content item on a particular server. In the example of FIG. 8, only two server tiers (edge server tier and second server tier) are shown. Alternatively, there may be more than two server tiers.

Aircraft 160-d may include an edge server 170-g and client device 220-e. Aircraft 160-d may include two or more client devices, which may be client devices 220 or 222 as described in FIG. Client device 220-e may initiate a DNS request for at least content item A, which may be a movie, game, show, live streaming event, etc. At 802, a domain name system request for item A is generated. The DNS request is forwarded to CDN DNS 244-c. For example, CDN DNS 244-c may be associated with the content provider for content item A, and requests (eg, HTTP requests) for content item A may be made to the content provider address.

At 804, CDN DNS 244-c may determine edge server 170-g located on aircraft 160-d. The determination may include identifying the aircraft 160-d and identifying which edge server among the plurality of edge servers is located on board the aircraft 160-d, as shown in FIG. may be performed as described above with reference to 604. At 806, CDN DNS 244-c may determine whether edge server 170-g stores item A. If edge server 170-g stores item A, CDN DNS 244-c may return the network address of edge server 170-g to client device 220-e at 808 (eg, in a redirect message). At 810, client device 220-e may receive the address of edge server 170-g from CDN DNS 244-c and request item A from edge server 170-g. At 812, edge server 170-g may provide item A to client device 220-e. Alternatively, CDN DNS 244-c may send the message directly to edge server 170-g, which then sends the item as if it were coming from the address of content provider or origin server 130-g. A may be provided to client device 220-e. For example, CDN DNS 244-c may provide edge server 170-g with encryption or other information (eg, an SSL certificate) to respond directly to client device 220-e. Upon receiving item A at 814, client device 220-e may use, display, or otherwise output item A.

Returning to 806, if CDN DNS 244-c determines that edge server 170-g does not store item A, process flow 800 continues to 820. At 820, CDN DNS 244-c may determine which second tier server is associated with edge server 170-g. In this example, second tier server 522-f is associated with edge server 170-g. At 822, CDN DNS 244-e determines whether second tier server 522-f stores item A. If so, process flow 800 continues to 824 where CDN DNS 244-c determines whether to store item A on edge server 170-g. If CDN DNS 244-c decides to store item A on edge server 170-g, CDN DNS 244-c either pushes item A to edge server 170-g at 826 or sets the edge server address at 808. It is returned to the client device 220-e. Pushing item A to edge server 170-g may include instructing the server closest in network proximity to edge server 170-g to forward item A to edge server 170-g. Edge server 170-g may store item A. As shown in FIG. 8, the DNS 244-c determines for each item whether to store the item in the edge server 170-g in step 824. Alternatively, each item may be pushed to the edge server 170-g from the terrestrial server where it is located (eg, in this case, tier 2 server 522-f). Edge server 170-g may then determine whether to store the item. This technique may be used for other items that may be stored in other layers of the terrestrial CDN hierarchy.

Once item A is directed or successfully pushed to edge server 170-g, CDN DNS 244-c may return the edge server address to client device 220-e at 808. Process flow 800 may proceed along 810, 812, and 814, as described above with reference to 610, 612, and 614 of FIG. 6, respectively.

Factors that may be considered when determining whether to store item A on the edge server include, among other factors, how often item A is requested by client devices onboard aircraft 160-d. or as may be requested, item A's storage size, network latency, network load, network traffic, time of day, item A's popularity, item A's rating, item A's publication date, digital rights associated with item A, or Other legal rights may include the available storage space at edge server 170-g, the network proximity of the closest server currently storing item A, and the remaining duration of aircraft 160-d's flight. One or more of these factors may be used in conjunction to determine whether to store a content item on an edge server.

If CDN DNS 244-c determines at 824 not to store item A on the edge server, CDN DNS 244-d returns at 830 the network address of second tier server 522-f to client device 220-e. At 832, client device 220-e may request item A from second tier server 522-f. At 834, second tier server 522-f provides item A to client device 220-e. Alternatively, CDN DNS 244-d may send the message directly to second tier server 522-f, which then sends a message from the address of content provider or origin server 130-g. As such, item A may be provided to client device 220-e. For example, CDN DNS 244-c may provide second tier server 522-f with encryption or other information (eg, an SSL certificate) to respond directly to client device 220-e. At 836, client device 220-e may receive item A from second tier server 522-f. Upon receiving item A, client device 220-e may display or otherwise output item A.

Returning to 822, if the second tier server 522-f determines that the second tier server 522-f does not store item A, process flow 800 continues to 840. At 840, CDN DNS 244-c returns the network address of origin server 130-g to client device 220-e (eg, in a redirect message). At 842, client device 220-e may request item A from origin server 130-g. At 844, origin server 130-g may provide item A to client device 220-e. At 846, client device 220-e may receive item A from origin server 130-g. Upon receiving item A, client device 220-e may display or otherwise output item A.

In addition to providing request routing, the process flow 800 determines whether the content should be stored on a different server and transfers the content to the edge server 170 as part of servicing the content to the requesting device. allows it to be stored in Storing items on a server closer in network proximity to the requesting client device may reduce delay, improve speed, and reduce traffic for items that may be requested again.

FIG. 9 depicts a map illustrating a communication environment 900 that includes an example content distribution network 122-c, in accordance with various aspects of the present disclosure. Communication environment 900 may include a satellite communication system 105-c, which may include a satellite 102-c and a plurality of gateways 110-e. CDN 122-c may include an onboard edge server 170-h, an origin server 130-h, and two terrestrial CDN layers. The first terrestrial CDN layer is a second server layer that includes four servers 522-g, 522-h, 522-i, and 522-j (collectively referred to as second server layer 404-b). obtain. The second terrestrial CDN layer may be a third server tier including servers 532-c, 532-d (collectively referred to as third server tier 406-b). The satellite communication system 105-c, the plurality of gateways 110-e, the onboard edge server 170-h, the second server tier 404-b, the origin server 130-h, and the third server tier 406-b each include: This may be an example of the satellite communication system 105, the plurality of gateways 110, the onboard edge server 170, the origin server 130, the second server tier 404, and the third server tier 406 of FIGS. 1-8, or aspects.

Although the map shows CDN 122-c distributed throughout the continental United States, other regions may be included in other examples. In some instances, CDN122-c extends across national borders. The tiers of servers 404-b and 406-b may also be geographically distributed.

In the example of FIG. 9, edge server 170-h is located on an aircraft over the eastern part of the continental United States. Edge server 170-h is in communication with satellite communication system 105-c. When a client device onboard an aircraft requests a media content item, edge server 170-h sends a DNS request for the content item via satellite communication system 105-c. In this example, CDN 122-c determines that the closest server in terms of network proximity that has the requested content item is second tier server 522-g. CDN 122-c provides the network address of edge server 170-h or second server tier server 522-g to client devices, as described herein.

As illustrated, the client device is connected to a server located on the west side of the continental United States, even though the aircraft is located on the east side and there are other satellite access nodes and servers physically closer to the aircraft. may receive content items from. This is because associations within the CDN hierarchy may be based on proximity to satellite access nodes that may communicate with the aircraft, rather than on the aircraft's geographic location. Proximity of satellite access nodes serving an airplane may be based on satellite track and user beam group 320 (e.g., satellite track/user beam group 410), as discussed with reference to FIGS. 3-5. . That is, the physical location of the aircraft may be less relevant to how the servers in the ground CDN hierarchy are associated with the onboard edge servers 170-h. Rather, the association may be based on proximity to the aircraft and, therefore, the satellite access node in communication with the onboard edge server 170-h.

10A and 10B illustrate an example handover of communication links between a satellite terminal onboard an aircraft and multiple satellite access nodes as the aircraft moves. FIG. 10A depicts a network handoff diagram of an example layer connectivity topology 1000 in accordance with various aspects of the present disclosure. FIG. 10A tracks aircraft 160-e from a first time (time A) to a second time (time B) as aircraft 160-e flies. FIG. 10B continues the flight of aircraft 160-e from a third time (time C) to a fourth time (time D). Layer connectivity topology 1000 includes an aircraft 160-e, an onboard edge server 170-i, a plurality of satellite access nodes 110-f, a second server tier 404-c, a third server tier 406-c, and an origin server 130. - Contains i. The second server tier 404-c may include four servers as shown and may be the first terrestrial CDN tier. The third server tier 406-c may include four servers as shown and may be a second terrestrial CDN tier. Aircraft 160-e, onboard edge server 170-i, plurality of satellite access nodes 110-f, second server tier 404-c, third server tier 406-c, and origin server 130-i each include: The aircraft 160, the edge server 170, the plurality of satellite access nodes 110, the second server tier 404, the third server tier 406, and the origin server 130 of FIGS. may be included.

Tier connectivity topology 1000 shows a first satellite access node 110-f associated with a first server of a second server tier 404-c, which first server is connected to a third server tier 406-c. , which is associated with the origin server 130-i. The tier connectivity topology 1000 also shows a second satellite access node 110-f associated with a second server of the second server tier 404-c, which is associated with a second server of the third server tier 406-c. is associated with the first server of f. The third satellite access node 110-f is associated with a third server of the second server tier 404-c, which third server is a second server of the third server tier 406-c. This second server is associated with origin server 130-i. Finally, a fourth satellite access network 110-f is associated with a fourth server of the second server tier 404-c, which is a fourth server of the third server tier 406-c. This second server is associated with origin server 130-i. Layer connectivity topology 1000 is just one example network topology. As discussed herein, associated for a CDN topology means that requests that cannot be fulfilled by a server are sent or redirected to the associated node or server. In other examples, other numbers of satellite access nodes, server tiers, and servers may be used. In some examples, various connections may be formed between various nodes and servers.

At time A, aircraft 160-e is within the first user beam 1030-a. In this example, first user beam 1030-a is associated with first satellite access node 110-f. Associations between ground servers and edge servers 170-i may be determined by layer network topology 1000. Now, since the aircraft 160-e is in the first user beam 1030-a, any DNS request originating from the aircraft 160-e sends the first satellite access node 110-f to the second server layer 404. -c, then the first server of the third server tier 406-c, and then the network path 1010 represented by the dark line connecting the origin server 130-i. will be routed through. This is an example of how CDN DNS may route DNS requests throughout layer connectivity topology 1000 when aircraft 160-e is in the first user beam 1030-a.

At time B, aircraft 160-e moved from within first user beam 1030-a to second user beam 1030-b. In this example, the second user beam 1030-b is served via the second satellite access node 110-f. When aircraft 160-e moves to be served via a second satellite access node 110-f, the association of edge servers 170-i in layer connectivity topology 1000 changes from the first server to the second server. The second server in layer 404-b is changed. Thus, a DNS request originating from aircraft 160-e while aircraft 160-e is in second user beam 1030-b sends second satellite access node 110-f to second server layer 404-c. through a network path 1020 represented by a dark line that connects with a second server of the third server tier 406-c, which then connects with the first server of the third server tier 406-c, and then with the origin server 130-i. will be routed. This is an example of how CDN DNS may route DNS requests throughout layer connectivity topology 1000 when aircraft 160-e is in second user beam 1030-b.

FIG. 10B depicts a network handoff diagram of an example layer connectivity topology 1000 in accordance with various aspects of the present disclosure. FIG. 10B tracks aircraft 160-e from time B to time C and then to time D in FIG. 10A. Layer connection topology 1000 may be the same as described above with respect to FIG. 10A.

At time C, aircraft 160-e has moved from within second user beam 1030-b to third user beam 1030-c. In this example, the third user beam 1030-c is served by the third satellite access node 110-f. When aircraft 160-e moves to be served via a third satellite access node 110-f, the association of edge server 170-i in layer connectivity topology 1000 changes from the second server to the second server. The third server in layer 404-b is changed. A DNS request originating from aircraft 160-e while aircraft 160-e is in third user beam 1030-c sends third satellite access node 110-f to the second server layer 404-c. 3 of the third server tier 406-c, which in turn connects with the second server of the third server tier 406-c, and then with the origin server 130-i. The Rukoto. This is an example of how CDN DNS may route DNS requests throughout layer connectivity topology 1000 when aircraft 160-e is in the third user beam 1030-c.

At time D, aircraft 160-e moved from within third user beam 1030-c to fourth user beam 1030-d. In this example, a fourth user beam 1030-d is associated with a fourth satellite access node 110-f. When aircraft 160-e moves to be served via a fourth satellite access node 110-f, the association of edge server 170-i in layer connectivity topology 1000 changes from the third server to the second server. The server is changed to the fourth server in layer 404-b. Any DNS request originating from aircraft 160-e while aircraft 160-e is within fourth user beam 1030-d sends fourth satellite access node 110-f to second server layer 404-c. Routed through a network path 1070 represented by a dark line that connects to a fourth server, which in turn connects to a second server of third server tier 406-c, and then connects to origin server 130-i. It will be done. This is an example of how CDN DNS may route DNS requests throughout layer connectivity topology 1000 when aircraft 160-e is in the fourth user beam 1030-d.

As shown in this example, the layer connectivity topology for the edge server may change over time as the aircraft moves between various user beams. Although described as being dependent only on the particular satellite access node serving the current user beam, the association of edge server 170-i may be associated with second server tier 404-c or third server tier 406. It may depend on additional factors such as the load on one or more of the ground server tiers, such as -c.

FIG. 11 depicts a flowchart illustrating an example method 1100 of layer connection management in accordance with aspects of the present disclosure. Some or all of the steps of example method 1100 may be implemented in various devices of a satellite communication environment or CDN, such as satellite terminal 112 of satellite communication system 105, as described with reference to FIGS. 1-10B. , communications satellite 102 , gateway or satellite access node 110 , CDN DNS 244 , edge server 170 , or client device 220 . In the description of method 1100, one or more devices in a satellite communication environment may perform each of the steps described. In some examples, one device in a satellite communication environment may perform the steps.

Method 1100 may illustrate how layer connectivity management may be performed and updated as a mobile transportation vehicle moves around a geographic area. At 1110, method 1100 may include maintaining a CDN layer connection topology. A CDN layer connection topology may be determined based on associating an edge server layer with servers of a second server layer (eg, a first ground server layer). For example, the CDN layer connectivity topology may be based on satellite access nodes serving the mobile transport vehicle's current location. Method 1100 may include maintaining a CDN layer connectivity topology for a particular mobile transportation vehicle, such as an aircraft.

At 1120, method 1100 may include obtaining instructions for handover of an aircraft from a first satellite access node to a second satellite access node. A handover may be indicated because the aircraft has moved from a first user beam associated with a first satellite access node to a second user beam associated with a second satellite access node. However, the aircraft may be in both the first user beam and the second user beam and still have indicated handovers based on different network conditions, for example. In some examples, a satellite communication system may indicate a handover to a CDN. For example, a modem or network access unit on the aircraft, or a satellite access node may notify the aircraft's edge server, or the ground server of the CDN, or the CDN DNS when a handover occurs.

At 1130, method 1100 may include determining whether to modify one or more ground servers associated with an edge server on the aircraft. If method 1100 determines not to change the server, method 1100 returns to 1110 and maintains the CDN layer connection topology. One example of why method 1100 may not require server changes may include that the second satellite access node presented in the handover is the same as the first satellite access node (e.g., the first user beam and The second user beam is served by the same satellite access node). Another reason may be that the server is associated with multiple satellite access nodes in the topology. In other examples, other reasons may be used to keep the CDN layer connection topology intact (eg, servers are loaded).

Alternatively, if method 1100 determines to change servers, method 1100 proceeds to 1140. At 1140, method 1100 updates the CDN layer connection topology. The method 1100 includes a method 1100 in which an aircraft is in a new user beam group served by a second satellite access node, and the second satellite access node is closer to a different server in a particular layer of the CDN (e.g., a first ground server layer). The CDN layer connection topology may change for reasons including, but not limited to, locating network proximity services.

FIG. 12 shows a flowchart illustrating an example method 1200 for performing handover during content delivery to an onboard device, according to aspects of the present disclosure. Some or all of the steps of example method 1200 may be performed on various devices in a satellite communications environment, such as satellite terminal 112 of a satellite communications system, communications satellite, etc., as described with reference to FIGS. 1-10B. 102, gateway 110, content replication system 140-d, edge server 170, or client device 220. FIG. 12 shows a client device 220-f and an onboard edge server 170-j of an aircraft 160-f, a first server 522-k of a second server tier, and a second server 522-k of a second server tier. 1, and actions taken by content replication system 140-d. Aircraft 160-f, client device 220-f, onboard edge server 170-k, servers 522-k and 522-l, and content replication system 140-d are the same as aircraft 160 and edge server of FIGS. 1-9, respectively. 170, client device 220, server 522, and content replication system 140.

Method 1200 may include client device 220-f requesting and obtaining media content items from a content distribution network. In this example, client device 220-f may communicate directly with a server storing the desired media content item. At 1202, client device 220-f may request a media content item. Based on the current location of aircraft 160-f, the first tier 2 server 522-k is connected to a network to aircraft 160-f that stores or has access to media content items. It can be the closest server in terms of proximity. At 1204, the first tier 2 server 522-k streams the media content item to the client device 220-f and continues to stream the media content item at 1206.

While the media content item is being streamed, the aircraft 160-f is in an area where the first tier 2 server 522-k is no longer the closest in terms of network proximity to the aircraft 160-f (e.g., new satellite access new user beams served by the node). At 1208, the content replication system 140-d updates the CDN tier connection topology so that the second tier 2 server 522-l that stores or has access to the media content item: It may be indicated that it is closest in network proximity to aircraft 160-f. Content replication system 140-d is configured to detect network connectivity with the aircraft because the aircraft 160-f has moved out of the user beam served by the first satellite access node and the network connection with the aircraft has been handed over to a second satellite access node. , can perform this update. In another example, the content replication system 140-d determines that the first tier 2 server 522-k no longer has access to the media content item or is under other circumstances, such as being under a high network load. This update may be done for any reason.

At 1210, content replication system 140-d may send a message to first tier 2 server 522-k that content replication system 140-d has made a CDN tier connection topology update. The message directs the first tier 2 server 522-k to notify the client device 220-f of an update or for the client device 220-f to request a media content item from the second tier 2 server 522-l. can give instructions. At 1212, the first tier 2 server 522-k may send a message (eg, a redirect message) to the client device 220-f requesting a media content item from the second tier 2 server 522-l. At 1214, client device 220-f requests a media content item from second tier 2 server 522-l. At 1216, the second tier 2 server 522-l may stream the media content item to the client device 220-f.

In some examples, buffering or other techniques may be performed to uninterrupted streaming of media content items at client device 220-f. In some examples, edge server 170-j may execute requests and receive any updates on behalf of client device 220-f, as shown in FIG. 13. Method 1200 may be performed as many times as necessary throughout a flight of aircraft 160-f.

FIG. 13 shows a flowchart illustrating an example method 1300 for performing handover during content delivery to an onboard device, according to aspects of the present disclosure. Some or all of the steps of example method 1300 may be performed on various devices of a satellite communication environment, such as satellite terminal 112 of satellite communication system 105, communication It may be performed by one or more of satellite 102 , gateway or satellite access node 110 , content replication system 140 , edge server 170 , or client device 220 . FIG. 13 shows a client device 220-g and an edge server 170-k onboard an aircraft 160-g, a first server 522-m of a second server tier, and a second server 522-m of a second server tier. n, and actions taken by content replication system 140-e, which include actions taken by aircraft 160, edge server 170, client device 220, server 522, and content replication system 140 of FIGS. 1-9 and 12, respectively. Examples may include or include these aspects.

Method 1300 may include client device 220-g requesting and obtaining a media content item from a content distribution network and may illustrate a method for identifying a server for distribution of the media content item. In the example method 1300, client device 220-g communicates with edge server 170-k to obtain a desired media content item. At 1302, client device 220-g may request a media content item from edge server 170-k. Edge server 170-k may determine which server in the CDN storing the media content item is closest in network proximity. Based on the current location of the aircraft 160-g, the first tier 2 server 522-m is the closest server in terms of network proximity that stores or has access to the media content item. It can be a nearby server. Edge server 170-k may request a media content item from first tier 2 server 522-m at 1304. At 1306, the first tier 2 server 522-m streams the media content item to the edge server 170-k and continues to stream the media content item at 1310. Edge server 170-k forwards the streaming data to client device 220-g at 1308 and 1312.

While the media content item is being streamed, aircraft 160-g may begin to fly out of the user beam area of the first satellite access node and a handover may be appropriate. At 1314, the content replication system 140-d updates the CDN tier connection topology so that the second tier 2 server 522-n storing or having access to the media content item: It may be indicated that aircraft 160-g is closest in network proximity (eg, based on aircraft 160-g being served by a second satellite access node). At 1316, content replication system 140-e may send a message to edge server 170-k that content replication system 140-e has made the CDN layer connection topology update. The message may notify edge server 170-k to request the media content item from second tier 2 server 522-n. At 1318, edge server 170-k may request a media content item from second tier 2 server 522-n. At 1320, the second tier 2 server 522-n begins streaming the media content item to the edge server 170-k. At 1322, edge server 170-k forwards the streaming data to client device 220-g.

FIG. 14 shows a flowchart illustrating a method 1400 for supporting content distribution routing using an aircraft-based edge server, according to aspects of the present disclosure. The operations of method 1400 may be implemented by a content distribution network or a component of a content distribution network as described herein. For example, the operations of method 1400 may be performed by a CDN as described with reference to FIGS. 1-13. In some examples, the CDN may execute a set of instructions to control functional elements of the CDN to perform the functions described below. Additionally or alternatively, a CDN may use specialized hardware to perform aspects of the functionality described below.

At 1405, the CDN may receive a request for a media content item from a device within a mobile platform served via a wireless communication link of the communication system. For example, a CDN may receive media content requests from client devices or edge servers. At 1410, the CDN may determine the identity of the mobile edge server located on the mobile platform based on the network address of the device associated with the request.

At 1415, the CDN may determine whether the media content item is stored on the mobile edge server. In some examples, determining whether a media content item is stored on a mobile edge server located within a mobile platform includes one or more media content items stored on one or more servers including a mobile edge server. The method further includes querying a server index that identifies the media content item. In other examples, determining whether a media content item is stored on a Mobile Edge Server may include sending a request to the Mobile Edge Server to determine whether the media content item is stored on the Mobile Edge Server. and receiving a message from the mobile edge server indicating whether the media content item is stored on the mobile edge server.

At 1420, the CDN may redirect the request for the media content item to the mobile edge server if the media content item is stored on the mobile edge server. In some examples, redirecting the request for the media content item to the mobile edge server further includes providing an address of the mobile edge server to the device in response to the request for the media content item. In other examples, redirecting the request for the media content item to the mobile edge server may include, in response to the request for the media content item, sending instructions to the mobile edge server to serve the media content item. .

At 1425, the CDN determines whether the media content item is stored on the first terrestrial server of the first server tier of the at least one terrestrial server tier, if the media content item is not stored on the mobile edge server. A first terrestrial server is coupled to an access node serving a mobile platform and associated with a mobile edge server for a content distribution network.

At 1430, the CDN redirects the request for the media content item to the first terrestrial server if the media content item is stored on the first terrestrial server of the first server tier.

In some examples, the method 1400 determines whether the media content item is stored on a second terrestrial server of a second server tier of the at least one terrestrial server tier if the media content item is not stored on the first terrestrial server. The method may include determining whether the second terrestrial server is associated with the first terrestrial server. The method may include redirecting a request for the media content item to the second terrestrial server if the media content item is stored on the second terrestrial server. In some examples, method 1400 may include redirecting a request for a media content item to an origin server of a content distribution network if the media content item is not stored on the second terrestrial server.

In some examples, method 1400 may include mapping a request for a media content item to a proxy server associated with an access node of a wireless communication link serving a mobile platform. In other examples, method 1400 may include sending the media content item to a mobile edge server for storage on the mobile edge server if the media content item is not stored on the mobile edge server. In other examples, the access node of the wireless communication link serving the mobile platform is a first access node, and the method determines that the mobile platform has transitioned to be served by a second access node. and updating an association of a mobile edge server of the content distribution network to be associated with a second terrestrial server coupled to the second access node.

The operations of 1405, 1410, 1415, 1420, 1425, and 1430 may be performed according to the methods described herein. In some examples, aspects of the operations of 1405, 1410, 1415, 1420, 1425, and 1430 may be performed by a CDN as described with reference to FIGS. 1-13. In some examples, a CDN includes components (eg, content replication system 140) that include memory and a processor that can perform the method 1400 described herein. For example, memory may include instructions that, when executed by a processor, cause the processor to perform method 1400.

FIG. 15 shows a flowchart illustrating a method 1500 of supporting content distribution routing using an aircraft-based edge server, according to aspects of the present disclosure. The operations of method 1500 may be implemented by an edge server or a component of an edge server, as described herein. For example, the operations of method 1500 may be performed by an edge server as described with reference to FIGS. 1-13. An edge server may be located on a mobile platform (eg, an aircraft). In some examples, an edge server may execute a set of instructions to control functional elements of the edge server to perform the functions described below. Additionally or alternatively, an edge server may use specialized hardware to perform aspects of the functionality described below.

At 1505, the edge server receives a request for a media content item for a device within the mobile platform, and the request was redirected from a server of a content distribution network outside of the mobile platform. At 1510, the edge server may determine whether the media content item is stored on the mobile edge server. At 1515, the edge server may serve the media content item to the device if the media content item is stored on the mobile edge server.

At 1520, the edge server sends at least one terrestrial network for the media content item via an access node serving the mobile platform via a wireless communication link if the media content item is not stored on the mobile edge server. Querying at least one terrestrial server of the server layer, receiving media content items from the at least one terrestrial server, and providing media content items to the device.

In some examples, querying the at least one terrestrial server comprises querying a first terrestrial server of a first server tier of the at least one terrestrial server tier for the media content item; A first terrestrial server is coupled to an access node servicing the mobile platform and associated with a mobile edge server of the content distribution network for querying and media content items stored on the first terrestrial server. receiving the media content item from the first terrestrial server if the media content item is not stored on the first terrestrial server; and if the media content item is not stored on the first terrestrial server; receiving a message indicating.

In other examples, querying the at least one terrestrial server may include contacting a second server of the at least one terrestrial server tier for the media content item if the media content item is not stored on the first terrestrial server. querying a second terrestrial server of the layer, the second terrestrial server being associated with the first terrestrial server of the content distribution network; receiving the media content item from the second terrestrial server, if the media content item is stored on the second terrestrial server; and, if the media content item is not stored on the second terrestrial server, storing the media content item on the second terrestrial server; receiving a message indicating that the user has not been registered. Querying the at least one terrestrial server includes querying an origin server of a content distribution network for the media content item if the media content item is not stored on the second terrestrial server; and retrieving the media content item from the origin server. The method may further include receiving.

In some examples, method 1500 may include storing the media content item on a mobile edge server in response to receiving the media content item from at least one terrestrial server.

The operations of 1505, 1510, 1515, and 1520 may be performed according to the methods described herein. In some examples, aspects of the operations of 1505, 1510, 1515, and 1520 may be performed by an edge server as described with reference to FIGS. 1-13. In some examples, the edge server includes memory and a processor that can perform the method 1400 described herein.

FIG. 16 shows a flowchart illustrating a method 1600 for supporting content distribution routing using an aircraft-based edge server, according to aspects of the present disclosure. The operations of method 1600 may be implemented by a device or a component of a content distribution network as described herein. For example, the operations of method 1600 may be performed by a CDN, an edge server, or a satellite node, as described with reference to FIGS. 1-13. In some examples, a device in a CDN may execute a set of instructions to control functional elements of the device to perform the functions described below. Additionally or alternatively, the device may use specialized hardware to perform aspects of the functionality described below.

At 1605, the device may determine that a modem on a mobile platform of the set of mobile platforms is provided with communications via a first satellite beam served by a first satellite access node. At 1610, the device determines whether the first server of the at least one terrestrial server tier connects to the first satellite based on the topology of the network of the at least one terrestrial server tier and the location of the first satellite access node. may be determined to be closest in network proximity to the access node.

At 1615, the device connects the mobile edge server located on the mobile platform to the at least one terrestrial server layer based on determining that the first server is closest in network proximity to the first satellite access node. The server may be associated with a first server.

In some examples, method 1600 involves handing over a modem on a mobile platform from being served communications by a first satellite access node to being served communications by a second satellite access node. may include obtaining instructions. The method 1600 also includes determining whether a second server of the at least one terrestrial server tier is a determining that the second server is closer in network proximity than the first server; and determining that the second server is closer in network proximity than the first server. associating the mobile edge server with the second server based on the nature of the mobile edge server.

In some examples of method 1600, the mobile platform is located at a first location, and the first location is geographically closer to a second server of the terrestrial server tier.

Method 1600 includes determining a first satellite beam based at least in part on determining a group of satellite beams associated with a first satellite access node and the first satellite beam being a member of the group of satellite beams. selecting a satellite access node to communicate with a mobile edge server located on the mobile platform. In some examples, the method is based at least in part on a topology of the network of at least one terrestrial server layer and a serving satellite access node location of each of the plurality of satellite access nodes of the communication system. , including associating each of the edge server tiers with a respective server of the terrestrial server tier.

In some examples, method 1600 includes receiving a request for a media content item from a mobile edge server located on a mobile platform and transmitting the request for the media content item to a first server of at least one terrestrial server tier. including transferring and. Some examples may include receiving a media content item from a first server of at least one terrestrial server tier and forwarding the media content item to a mobile edge server located on a mobile platform. . Further examples include receiving a media content item from a second server of at least one terrestrial server tier, or an origin server of at least one terrestrial server tier, and transmitting the media content item to a mobile device located on a mobile platform. and forwarding to an edge server. Method 1600 may include receiving a media content item from an origin server of at least one terrestrial server tier and forwarding the media content item to a mobile edge server located on a mobile platform.

The operations of 1605, 1610, and 1615 may be performed according to the methods described herein. In some examples, aspects of the operations of 1605, 1610, and 1615 may be performed by a network device as described with reference to FIGS. 1-13. In some examples, a CDN includes components (eg, content replication system 140) that include memory and a processor that can perform the method 1400 described herein. In other examples, an edge server or satellite node includes memory and a processor that may perform the method 1400 described herein.

The detailed description set forth above in conjunction with the accompanying drawings is illustrative and does not represent the only example that may be practiced or that is within the scope of the claims. As used herein, the term "example" means "serving as an example, instance, or illustration," and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the techniques described. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be generated by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. may be expressed.

Various exemplary blocks and components described in connection with the disclosure herein include general purpose processors, digital signal processors (DSPs), ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic devices, etc. , discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a DSP and a microprocessor, multiple microprocessors, a combination of microprocessors with a DSP core, or any other such configuration.

The functionality described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software that is executed by a processor, the functions may be stored on or transmitted over as instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to their software nature, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing functionality may also be physically located at various locations, including being distributed such that portions of functionality are implemented at different physical locations. As used herein, including in the claims, the term "and/or" when used in a list of two or more items means that any one of the listed items is taken on its own. or any combination of two or more of the listed items may be employed. For example, if a composition is described as containing components A, B, and/or C, the composition may include A only, B only, C only, a combination of A and B, a combination of A and C. , a combination of B and C, or a combination of A, B, and C. Also, as used herein, including in the claims, in a list of items (e.g., a list of items prefaced by phrases such as "at least one" or "one or more") "or" may be used, for example, such that the list "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). shows a disjunctive list.

Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example and not limitation, a computer-readable medium may be in the form of RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage device, magnetic disk storage device or other magnetic storage device, or instructions or data structures. May include any other medium that can be used to carry or store the desired program code means and that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor. can. Also, any connection is properly termed a computer-readable medium. For example, the software may be transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless techniques such as infrared, radio, and microwave. If so, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless techniques such as infrared, radio, and microwave are included in the definition of medium. Disc and disc as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy discs and Blu-ray discs; ) typically reproduce data magnetically, and discs (discs) typically reproduce data optically using a laser. Combinations of the above are also included within the scope of computer-readable media.

As used herein, the phrase "based on" shall not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" shall be construed in the same manner as the phrase "based at least in part on."

The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (37)

A method for use in a communication system (100), the communication system (100) comprising an edge server located on a mobile platform (160) served by a wireless communication link (106) of the communication system. a content distribution network (122) including a layer (402) and at least one terrestrial server layer (404) geographically distributed within the communication system, the method comprising:
receiving a request for a media content item (1202) from a device (220) within a mobile platform (160) served via a wireless communication link (106) of the communication system;
determining the identity of a mobile edge server (170-a) located on the mobile platform based at least in part on a network address of the device associated with the request;
determining whether the media content item is stored on the mobile edge server;
redirecting the request for the media content item to the mobile edge server if the media content item is stored on the mobile edge server;
If the media content item is not stored on the mobile edge server, the media content item is stored on the first terrestrial server (522-a) of the first server tier (404) of the at least one terrestrial server tier. ), the first terrestrial server (522-a) coupled to a first access node (110-d-1) serving the mobile platform; and associated with the mobile edge server for the content delivery network;
If the media content item is stored on the first terrestrial server (522-a) of the first server tier, the request for the media content item is sent to the first terrestrial server (522-a). and redirect to
determining that the mobile platform has transitioned to being serviced by a second access node (110-d-3) while the mobile platform is in transit;
updating the association of the mobile edge server with the content distribution network to be associated with a second terrestrial server (522-b) coupled to the second access node (110-d-3); , including a method. if the media content item is not stored on the first terrestrial server;
determining whether the media content item is stored on the second terrestrial server (532) of a second server tier (406) of the at least one terrestrial server tier; terrestrial server is associated with the first terrestrial server;
The method of claim 1, further comprising: redirecting the request for the media content item to the second terrestrial server if the media content item is stored on the second terrestrial server. . 3. The method of claim 2, further comprising redirecting the request for the media content item to an origin server (130) of the content distribution network if the media content item is not stored on the second terrestrial server. the method of. Redirecting the request for the media content item to the mobile edge server comprises:
A method according to any preceding claim, comprising providing an address of the mobile edge server to the device in response to the request for the media content item. Redirecting the request for the media content item to the mobile edge server comprises:
A method according to any one of claims 1 to 4, comprising sending instructions to the mobile edge server for serving the media content item in response to the request for the media content item. Determining whether the media content item is stored on the mobile edge server located within the mobile platform comprises:
The method according to any one of claims 1 to 5, further comprising querying a server index (242) identifying one or more media content items stored on at least the mobile edge server. Determining whether the media content item is stored on the mobile edge server comprises:
sending a request (1302) to the mobile edge server to check whether the media content item is stored on the mobile edge server;
A method according to any one of claims 1 to 6, further comprising receiving a message from the mobile edge server indicating whether the media content item is stored on the mobile edge server. Any of claims 1 to 7, further comprising mapping the request for the media content item to a proxy server (216) associated with the first access node of the wireless communication link serving the mobile platform. The method described in paragraph (1). 9. The method of claims 1-8, further comprising, if the media content item is not stored on the mobile edge server, transmitting the media content item to the mobile edge server for storage on the mobile edge server. The method described in any one of the above. A method for use in a communication system (100), the communication system (100) comprising an edge server located on a mobile platform (160) served by a wireless communication link (106) of the communication system. a content distribution network (122) including a layer (402) and at least one terrestrial server layer (404) geographically distributed within the communication system, the method comprising:
Receiving, at a mobile edge server (170-a) located on a mobile platform (160), a request for a media content item (1202) for a device (220) in the mobile platform, the request comprising: receiving redirected from a server (404) of said content distribution network external to a mobile platform;
determining whether the media content item is stored on the mobile edge server;
if the media content item is stored on the mobile edge server, providing the media content item to the device;
if the media content item is not stored on the mobile edge server;
querying a first terrestrial server of the at least one terrestrial server layer for the media content item via a first access node (110) serving the mobile platform via a wireless communication link (106); And,
receiving the media content item from the first terrestrial server;
providing the media content item to the device;
determining that the mobile platform has transitioned to being serviced by a second access node (110-d-3) while the mobile platform is in transit;
updating the mobile edge server's association with the content distribution network to be associated with a second terrestrial server (522-b) coupled to the second access node (110-d-3); including methods. Querying the first ground server includes:
querying the first terrestrial server (522-a) of a first server tier (404) of the at least one terrestrial server tier for the media content item; is coupled to the first access node serving the mobile platform and associated with the mobile edge server for the content delivery network;
receiving the media content item from the first terrestrial server, if the media content item is stored on the first terrestrial server;
10. If the media content item is not stored on the first terrestrial server, receiving a message indicating that the media content item is not stored on the first terrestrial server. The method described in. Querying the first ground server includes:
a third terrestrial server of the second server tier (406-b) of the at least one terrestrial server tier for the media content item if the media content item is not stored on the first terrestrial server; (532-a), wherein the third terrestrial server is associated with the first terrestrial server for the content distribution network;
receiving the media content item from the third terrestrial server, if the media content item is stored on the third terrestrial server;
12. If the media content item is not stored on the third terrestrial server, receiving a message indicating that the media content item is not stored on the third terrestrial server. The method described in. Querying the first ground server includes:
querying an origin server (130) of the content distribution network for the media content item if the media content item is not stored on the third terrestrial server;
13. The method of claim 12, comprising: receiving the media content item from the origin server. 14. The method according to any one of claims 10 to 13, further comprising storing the media content item on the mobile edge server in response to receiving the media content item from the first terrestrial server. Method. A method for use in a communication system (100), the communication system (100) comprising an edge network located on a plurality of mobile platforms (160) served by a wireless communication link (106) of the communication system. a content distribution network (122) comprising: a server layer (402) of a computer; and at least one terrestrial server layer (404) geographically distributed within the communication system;
A modem (212) on a mobile platform (160-a) of said plurality of mobile platforms communicates via a first satellite beam (108) served by a first satellite access node (102). determining that it is supplied;
a first server (120) of the at least one terrestrial server tier based at least in part on a topology (120) of a network of the at least one terrestrial server tier; and a location of the first satellite access node; 522-a) is closest in network proximity to the first satellite access node;
the mobile edge server (170-a) located on the mobile platform based at least in part on the determining that the first server is closest in network proximity to the first satellite access node; associating with the first server at least one terrestrial server tier. of the modem on the mobile platform from being provided with the communications by the first satellite access node to being provided with the communications by a second satellite access node (110-d-2); obtaining handover instructions; and
a second server (522) of the at least one terrestrial server tier based at least in part on the topology of the network of the at least one terrestrial server tier and a location of the second satellite access node; -b) is closer in network proximity to the first satellite access node than the first server;
associating the mobile edge server with the second server based at least in part on the determining that the second server is closer in network proximity than the first server. 16. The method of claim 15. 17. The method of claim 16, wherein the mobile platform is located at a first location, and the first location is geographically closer to the second server of the at least one terrestrial server tier. determining a group (1030) of satellite beams associated with the first satellite access node;
Selecting the first satellite access node based at least in part on the first satellite beam (1030-a) being a member of the group of satellite beams, 18. The method according to any one of claims 15 to 17, further comprising: communicating with a mobile edge server. based at least in part on the topology of the network (122) of the at least one terrestrial server layer and the location of a serving satellite access node of each of the plurality of satellite access nodes (110) of the communication system; , further comprising associating each of the edge server tiers with a respective server of the at least one terrestrial server tier. receiving (1304) a request for a media content item from the mobile edge server located on the mobile platform;
The method according to any one of claims 15 to 19, further comprising forwarding the request for the media content item to the first server of the at least one terrestrial server tier. receiving the media content item from the first server of the at least one terrestrial server tier;
21. The method of claim 20, further comprising transferring the media content item to the mobile edge server located on the mobile platform. receiving the media content item from a second server (522-b) of the at least one terrestrial server tier or an origin server (130) of the at least one terrestrial server tier;
22. The method of claim 20 or 21, further comprising: transferring the media content item to the mobile edge server located on the mobile platform. receiving the media content item from an origin server (130) of the at least one terrestrial server layer;
23. A method according to any one of claims 20 to 22, further comprising transferring the media content item to the mobile edge server located on the mobile platform. A communication system (100),
an edge server layer (402) located on a mobile platform (160) serviced by a wireless communication link (106) of said communication system and at least one terrestrial server geographically distributed within said communication system; a content distribution network (122) comprising a layer (404);
a processor (230);
a memory (234) in electronic communication with the processor;
instructions stored in the memory, the instructions being transmitted by the processor to the communication system;
receiving a request for a media content item (1202) from a device (220) within a mobile platform (160-a) served via a wireless communication link (108-a) of the communication system;
determining the identity of a mobile edge server (170-a) located on the mobile platform based at least in part on a network address of the device associated with the request;
determining whether the media content item is stored on the mobile edge server;
redirecting the request for the media content item to the mobile edge server if the media content item is stored on the mobile edge server;
If the media content item is not stored on the mobile edge server, the media content item is stored on the first terrestrial server (522-a) of the first server tier (404) of the at least one terrestrial server tier. ), the first terrestrial server (522-a) coupled to a first access node (110-d-1) serving the mobile platform; and associated with the mobile edge server for the content delivery network;
If the media content item is stored on the first terrestrial server (522-a) of the first server tier, the request for the media content item is sent to the first terrestrial server (522-a). and redirect to
determining that the mobile platform has transitioned to being serviced by a second access node (110-d-3) while the mobile platform is in transit;
updating the association of the mobile edge server with the content distribution network to be associated with a second terrestrial server (522-b) coupled to the second access node (110-d-3); , a communication system (100). The instructions stored in the memory and executable by the processor cause the communication system to:
If the media content item is not stored on the first terrestrial server, the media content item is stored on the second terrestrial server (532) of the second server tier (406) of the at least one terrestrial server tier. ), the second terrestrial server is associated with the first terrestrial server;
25. The method of claim 24, further comprising: redirecting the request for the media content item to the second terrestrial server if the media content item is stored on the second terrestrial server. Communications system. The instructions stored in the memory and executable by the processor cause the communication system to:
26. The method of claim 25, further comprising redirecting the request for the media content item to an origin server (130) of the content distribution network if the media content item is not stored on the second terrestrial server. Communication system as described. The instructions stored in the memory and executable by the processor cause the communication system to:
providing an address of the mobile edge server to the device in response to the request for the media content item, or instructions for serving the media content item in response to the request for the media content item. A communication system according to any one of claims 24 to 26, further causing the mobile edge server to transmit. A communication system,
an edge server layer (402) located on a mobile platform (106) serviced by a wireless communication link of the communication system; and at least one terrestrial server layer (404) geographically distributed within the communication system. ); a content distribution network (122);
a processor (230);
a memory (234) in electronic communication with the processor;
instructions stored in the memory, the instructions being transmitted by the processor to the communication system;
Receiving, at a mobile edge server (170-a) located on a mobile platform (160), a request for a media content item (1202) for a device (220) in the mobile platform, the request comprising: receiving redirected from a server (404) of said content distribution network external to a mobile platform;
determining whether the media content item is stored on the mobile edge server;
if the media content item is stored on the mobile edge server, providing the media content item to the device;
if the media content item is not stored on the mobile edge server;
querying a first terrestrial server of the at least one terrestrial server layer for the media content item via a first access node (110) serving the mobile platform via a wireless communication link (106); And,
receiving the media content item from the first terrestrial server;
providing the media content item to the device;
determining that the mobile platform has transitioned to being serviced by a second access node (110-d-3) while the mobile platform is in transit;
updating the mobile edge server's association with the content distribution network to be associated with a second terrestrial server (522-b) coupled to the second access node (110-d-3); A communication system that allows you to do this. The instructions for querying the first ground server stored in the memory and executable by the processor cause the communication system to:
querying the first terrestrial server (522-a) of a first server tier (404) of the at least one terrestrial server tier for the media content item; is coupled to the first access node serving the mobile platform and associated with the mobile edge server for the content delivery network;
receiving the media content item from the first terrestrial server, if the media content item is stored on the first terrestrial server;
If the media content item is not stored on the first terrestrial server, receiving a message indicating that the media content item is not stored on the first terrestrial server. 29. The communication system according to item 28. The instructions for querying the first ground server stored in the memory and executable by the processor cause the communication system to:
a third terrestrial server of the second server tier (406-b) of the at least one terrestrial server tier for the media content item if the media content item is not stored on the first terrestrial server; (532-a), wherein the third terrestrial server is associated with the first terrestrial server for the content distribution network;
receiving the media content item from the third terrestrial server, if the media content item is stored on the third terrestrial server;
If the media content item is not stored on the third terrestrial server, receiving a message indicating that the media content item is not stored on the third terrestrial server. 30. The communication system according to item 29. The instructions stored in the memory and executable by the processor cause the communication system to:
31. Responsive to receiving the media content item from the first terrestrial server, further causing the mobile edge server to store the media content item. communication system. A communication system (100),
an edge server layer (402) located on a plurality of mobile platforms (160) serviced by wireless communication links (106) of the communication system; and at least one terrestrial network geographically distributed within the communication system. a content distribution network (122) comprising a server layer (404) of;
a processor (230);
a memory (234) in electronic communication with the processor;
instructions stored in the memory, the instructions being transmitted by the processor to the communication system;
A modem (212) on a mobile platform (160-a) of said plurality of mobile platforms communicates via a first satellite beam (108) served by a first satellite access node (102). determining that it is supplied;
a first server (120) of the at least one terrestrial server tier based at least in part on a topology (120) of a network of the at least one terrestrial server tier; and a location of the first satellite access node; 522-a) is closest in network proximity to the first satellite access node;
the mobile edge server (170-a) located on the mobile platform based at least in part on the determining that the first server is closest in network proximity to the first satellite access node; and associating at least one terrestrial server tier with said first server. The instructions stored in the memory and executable by the processor cause the communication system to:
of the modem on the mobile platform from being provided with the communications by the first satellite access node to being provided with the communications by a second satellite access node (110-d-2); obtaining handover instructions; and
a second server (522) of the at least one terrestrial server tier based at least in part on the topology of the network of the at least one terrestrial server tier and a location of the second satellite access node; -b) is closer in network proximity to the first satellite access node than the first server;
associating the mobile edge server with the second server based at least in part on the determining that the second server is closer in network proximity than the first server. 33. The communication system according to claim 32. The instructions stored in the memory and executable by the processor cause the communication system to:
determining a group (1030) of satellite beams associated with the first satellite access node;
Selecting the first satellite access node based at least in part on the first satellite beam (1030-a) being a member of the group of satellite beams, 34. The communication system according to claim 32 or 33, further comprising: communicating with a mobile edge server. The instructions stored in the memory and executable by the processor cause the communication system to:
based at least in part on the topology of the network (122) of the at least one terrestrial server layer and the location of a serving satellite access node of each of the plurality of satellite access nodes (110) of the communication system; , further comprising associating each of the edge server tiers with a respective server of the at least one terrestrial server tier. The instructions stored in the memory and executable by the processor cause the communication system to:
receiving (1304) a request for a media content item from the mobile edge server located on the mobile platform;
36. The communication system according to any one of claims 32 to 35, further comprising: forwarding the request for the media content item to the first server of the at least one terrestrial server tier. The instructions stored in the memory and executable by the processor cause the communication system to:
receiving the media content item from the first server of the at least one terrestrial server tier;
37. The communication system of claim 36, further comprising: transferring the media content item to the mobile edge server located on the mobile platform.

Images