EA043324B1 - SYSTEM AND METHOD FOR DIGITAL DATA DELIVERY THROUGH A MULTILEVEL CONTENT DELIVERY NETWORK (CDN) - Google Patents

Description

Field of technology

The disclosure relates generally to a data delivery system and method and architecture for last mile delivery of data required to operate a digital service (mobile application/website/game/software application).

Prior Art

The Internet and associated networks used by the consumer/consumer device to access the digital service, as shown in FIG. 1 are well known. The Internet allows various pieces of content/data required for a digital service to be delivered to a device using a last mile network, similar to the smartphone shown in FIG. 1. Internet, as shown in FIG. 1, is a combination of all the physical blocks distributed around the globe that contain all the information in the world. An Internet data center is a series of distributed physical units that contain all networking and computing equipment, including redundant and redundant components, power infrastructure, data connections, media controls, and various security devices. CDN infrastructure is a geographically distributed network of servers that reside at the data center of the Internet that provide most of the Internet content today, especially web objects (text, graphics, scripts), downloadable objects (multimedia files, software, documents), applications, real-time streaming media, on-demand streaming media and social media, the architecture of which is well known and the operation of which is also known. The Internet, together with the Internet Data Center and CDN infrastructure, are collectively defined as the Internet infrastructure. A digital service provider includes all persons/companies/entities that use the Internet infrastructure to provide a service to consumers. The consumer platform is/are the mobile applications/websites/any interface through which the user accesses the service of the digital service provider. Telecommunications infrastructure is the infrastructure installed by telecommunications companies that uses licensed wireless frequencies to access the Internet (2G/3G/4G/LTE - collectively, cellular data connections), and Wi-Fi infrastructure is the infrastructure installed by Internet service providers. services to provide broadband connectivity/connectivity through a leased line to access the Internet, or access point(s) providing connectivity to access the Internet wirelessly using an unlicensed frequency.

Using the conventional system shown in FIG. 1, the service (mobile application) shown in FIG. 1 works as follows. All information provided by the digital service provider is stored/provided either through server(s) maintained by the digital service provider or via a CDN. Based on data access patterns (what data is consumed where), the CDN infrastructure caches certain data (a subset of all information) across multiple servers distributed across geographic areas. Edge (Edge) CDN servers (EDGE1, ... EDGEn in Fig. 1) are distributed globally and are hosted within third party globally distributed Internet data centers and data centers operated by Internet service providers and telecommunications service providers. When a consumer needs to access a service, the service needs to access server(s) hosted by the digital service provider and a CDN through the last mile, which is the data connection between the consumer (smartphone device, for example in Fig. 1) and the Internet infrastructure ( either through an Internet service provider, telecommunications service provider, or any other form of Internet connectivity option). A consumer's ability to access a service depends on the consumer's last mile availability, and the consumer's experience with the service depends on the reliability and capacity available at the last mile. More importantly, as the number of users and data consumption per user increases, the load on existing Internet infrastructure increases exponentially, impacting the user experience in densely populated areas.

Using a modern traditional system, access to the service occurs as follows. When a user opens a digital service on a device (such as a smartphone), the digital service attempts to access the Internet infrastructure using the last mile connectivity available to the device at that time. The consumer's smartphone operating system (OS) (see FIG. 1) determines the availability of connectivity over a cellular data connection (such as 4G/LTE, as shown in FIG. 1) or Wi-Fi. If connectivity is available using only one connection, the OS uses the available connection route. If both connectivity options are available, the OS determines which connection provides more stable and faster bandwidth availability and uses that connection to transmit data packets with the priority assigned to Wi-Fi. If the above scenario changes at any time, the OS automatically switches between the two unless the user manually connects or disconnects to/from either of the two available options. The user can access the service

- 1 043324 while one of the two connections is available. The user's experience of using the service depends on the stability and available bandwidth on these connections. In the event that the user loses connectivity to both connections, the service ceases to function, except for any functionality that may be cached on the user device (downloads in the case of a streaming service).

In fig. Figure 2 shows how a regular CDN works. As shown in FIG. 2, Traditional CDN is usually a multi-tier network of storage and computing servers. In general, it is an on-demand retrieval-based CDN in which the response to the requestor's unique request is cached at the point closest to the requestor - the CDN Edge server, which is the last layer of the CDN network. When the requester makes the first request for a file, the Edge CDN server also caches the file from the CDN's Origin server when delivering the file to the requestor (as in the top part of Fig. 2). When the next requester makes the same request, instead of being served from the CDN Origin server where the response originates, it is served from the cache (CDN Edgeserver), thereby reducing the time it takes to serve the next requester's request. This action also reduces the overall load on the origin server and the Internet bandwidth requirement of the origin server. As shown in FIG. 2, CDN typically uses many edge servers distributed geographically to serve a large number of requesters. A common location for CDN edge servers is at an ISP or telecommunications infrastructure data centers. By providing cached content, it also provides Internet bandwidth savings to the ISP or telecom. In a typical infrastructure:

1. The CDN origin server is connected to the Internet.

2. The edge server is connected to the origin CDN server over the Internet.

3. The edge CDN server is located at the ISP/telecom operator's data center and therefore has connectivity with the ISP/telecom fabric.

4. When Requester 1 requests a piece of content, the edge CDN server also caches the response in itself when servicing Requester 1's request.

5. When requester 2 requests the same piece of content, it is served directly from the edge CDN server.

Thus, existing systems have the technical problem that access to data/service is entirely dependent on the last mile, without which the CDN or servers hosted by the digital service provider are not able to deliver any data to the service/requester. Thus, it is desirable to be able to provide a technical solution that is a new CDN whose edge devices are closer to each requestor, and which is self-sufficient and delivers data to the user using a different connection path, resulting in faster delivery of data to the user regardless of access user to the last mile connection.

Brief description of drawings

Fig. Figure 1 illustrates how the Internet infrastructure functions.

Fig. Figure 2 illustrates how a typical CDN works.

Fig. Figure 3 illustrates how a digital service operates using Internet infrastructure, of which a traditional CDN is an integral part.

Fig. 4 illustrates a new CDN system with CDN servers also deployed outside the Internet infrastructure and having a last mile connection to the CDN servers.

Fig. Figure 5 illustrates the architecture and functionality of the new CDN system.

Fig. 6 illustrates how a digital service using the new CDN system operates in a scenario similar to that shown in FIG. 5 (both the CDN server and the user device have connectivity to the Internet).

Fig. 7 illustrates how the new CDN system works in a case where a traditional CDN system would not work. This illustration is intended for the case in which the user device does not have connectivity to the Internet, but the server of the new CDN system does.

Fig. Figure 8 illustrates how the new CDN system works in a case where a traditional CDN system would not work. This illustration is intended for the case in which the CDN server does not have connectivity to the Internet, but the user device does.

Fig. Figure 9 illustrates how the new CDN system works in a case where a traditional CDN system would not work. This illustration is for the case where both the CDN server and the user device have no connectivity to the Internet.

Carrying out the invention

The disclosure is particularly applicable to a digital service (mobile application/website/game/software application) installed on a computing device (smartphone/tablet/laptop/desktop/smartwatch, etc.) as shown in the drawings, with using the system and method of content delivery, and it is in this context that it will be described

- 2 043324 disclosure. However, it should be understood that the disclosed system and method have great utility, for example, for implementation on various computing devices that may be used to access content from a digital service provider. In addition, an exemplary CDN system may also be used to optimize the delivery of content or data from other systems and may be used in any system in which it is desired to optimize consumer access and service experience. For purposes of this disclosure, a service provided to a user may be a piece of content (audio, visual and/or text) or any piece of digital data delivered to the consumer through any interface including a browser, mobile application, software application, etc. P.

Fig. 3 illustrates more details of the new CDN system 300. The system 300 may further comprise one SugarBox of hardware elements 402, 404, 406 that may be connected to the Internet infrastructure in an Internet data center and may also be connected to each of the computing devices 302 over a global computing network. network (WLAN) that provides an additional communication channel for each application request. Each SugarBox piece of hardware, known as a SugarBox CDN server, can be implemented as one or more server computers, which are also equipped with dedicated last-mile Wi-Fi in each edge CDN server, providing the following key functionality:

SugarBox CDN is connected to the existing Internet infrastructure and acts as an infrastructure complementary to the Internet. However, with dedicated last mile Wi-Fi, data from the SugarBox CDN is delivered using a last mile that is outside the existing Internet (LAN) infrastructure, thereby:

frees up bandwidth in existing Internet infrastructure, especially last mile provided by Internet Service Providers/Telecommunications Operators;

does not overload the existing last mile Internet infrastructure as the number of users accessing or consumption per user increases.

SugarBox CDN allows a user who has not had access to the Internet, using any of the existing connectivity options (Internet service provider or telecommunications operator), to experience all or part of any service.

SugarBox CDN can continue to operate even when CDN edge server connectivity to the CDN infrastructure is unavailable because the last mile can provide data cached in the CDN edge server to the service, thereby allowing service access in an area without reliable and supported connectivity (transport, remote locations, etc.).

The SugarBox CDN Edge Server is always one hop (hop) further away from the user (as it is accessible to the user over the local network) than a traditional CDN Edge Server, thereby delivering faster data delivery and facilitating a better user experience.

SugarBox CDN uses a dedicated last mile, while the last mile in the existing Internet infrastructure is a shared last mile for the CDN and all other services running on the Internet, thereby enabling faster data delivery and promoting a better user experience.

SugarBox CDN operates on the last mile, which operates on unlicensed bandwidth, thereby making the last mile scalability virtually unlimited, thereby allowing the service to provide a guarantee to consumers on availability, reliability and bandwidth availability when using the service.

The SugarBox CDN edge server can be placed in places of interest (buses, trains, airplanes, shopping malls, commercial centers, airports, cafes, restaurants, bars, hotels, educational institutions, hospitals, clinics, residential complexes, corporate parks, public parks, theme parks, public places, etc.), which provides a service to provide a contextual experience to the user based on the user's proximity to a place of interest, without using the device's location.

SugarBox CDN optimizes and revolutionizes the way the Internet works. The ecosystem ensures that the service does not add load to the existing Internet infrastructure, regardless of the number of users or consumption per user, thereby making the Internet more efficient.

In more detail, the new CDN 300 system may have the following elements:

SugarBox Origin & Mid 402 servers that reside within the Internet data center and are part of the existing Internet infrastructure. These servers operate similarly to the origin server in a typical CDN.

SugarBox Static Edge 404, which is connected to SugarBox Origin using a physical high-speed connection (P2P/MPLS) and has an attached Wi-Fi installation exposed to the user.

SugarBox Mobile Edge (mobile edge server) 406, which from a hardware point of view

- 3043324 tools and software stack is the same as SugarBox Static Edge, but instead of having a physical connection to the SugarBox CDN infrastructure, it is connected wirelessly using one of the two routes below:

using MPLS/cellular data connectivity over a telecommunications network (may be intermittent and may not be high speed);

using Wi-Fi and associated physical connectivity from SugarBox Edge (always periodic when the Mobile Edge server is part of the Static Edge server network, and is high-speed).

The service requires access to the following 6 key elements to function:

API requests/HTTP requests, security requests - DRM/AES/SSL, analytics requests, content requests - content/downloadable objects/web objects, advertisement requests, payment requests.

Typically, analytics, payment and security requests are served directly by the service provider through its own/third party servers. All other requests are forwarded via CDN, as shown in FIG. 4. SugarBox CDN works as follows:

In the absence of a SugarBox CDN, the service uses last-mile connectivity (ISP equipment, either over Ethernet, Wi-Fi, or cellular data service) to access all requests.

When a user comes within the Wi-Fi range of a SugarBox CDN edge server, the service uses the user's cellular data connection to process all requests that are served by the service provider;

SugarBox CDN replaces the traditional CDN to handle all requests that are sent through the CDN.

The SugarBox Edge Server can support certain functionality such as DRM, local payments, etc., which is maintained locally by the Edge Server.

In one example, a new CDN system could be implemented in hardware and software as follows:

Brief description of hardware:

SugarBox Origin & Mid computing servers, storage servers, networking equipment;

SugarBox Static & Mobile Edge compute + storage server, networking equipment, Wi-Fi equipment.

Brief description of the software stack:

SugarBox Origin & Mid content delivery software,

DNS

DHCP, registration & monitoring, databases;

SugarBox Static & Mobile content delivery software,

DNS

DHCP, registration & monitoring, databases.

How the service operates using existing Internet infrastructure.

To better understand the operation of the new CDN and its elements, how the service currently operates using existing Internet infrastructure and traditional CDN is described with reference to FIG. 4. The service requires a response to many types of requests in order to function. These requests are made over any device connection to the Internet. Due to the nature of requests, they can either be cached through the CDN or not cached at all. Requests that are cacheable are cached by the CDN to ensure that server load at IDC is reduced and the request is served from the closest point to the subscriber, optimizing delivery speed and cost.

The service works using existing Internet infrastructure as follows:

1. There is a cellular data connection (the last mile of telecommunications) from the user device to the Internet.

- 4 043324

2. There is a Wi-Fi connection (last mile ISP) from the user device to the Internet.

3. Edge CDN servers also have a connection to the Internet.

4. Servers that accept analytics requests also require an Internet connection.

5. Servers that accept payment requests also require an Internet connection.

6. Servers that provide content decryption keys (DRM keys) also require an Internet connection.

7. Content, text, graphics, etc. are provided by servers in the Internet Data Center (IDC). Serving these requests is typically done through a CDN with an associated Time to Live (TTL) for a specific piece of content. This is done to ensure that content is available closer to the consumption of the aforementioned content.

8. Server-side ad serving at IDC is also provided via a CDN to ensure that ad content is available closer to where it will be consumed.

9. 'Ad Tags' feature is provided via CDN with TTL to ensure fast tag delivery.

10. Response to API requests that are not user-specific are cached in the CDN with TTL to ensure lower load on the API server. API requests that are user-specific are either cached on the user's device or delivered directly through the API server.

For a traditional CDN, the user depends on the availability of the last mile connection to access the Internet through which the service accesses all requests to provide user functionality and access to the service. In addition, the user and the service depend on the bandwidth available on the user's last mile connectivity and its reliability, which determines the user's perception of the service experience.

How does SugarBox CDN work?

Fig. 5 illustrates how the service operates using the new CDN system and how the new CDN operates. SugarBox CDN is a multi-tier CDN architecture with SugarBox Origin CDN 402 forming the first tier, SugarBox CDN Mid servers 402 forming the second tier, and SugarBox CDN Edge servers 404 forming the third tier.

SugarBox CDN Edge servers can be one of 2 types - Static (static) or Mobile (mobile). The Static Edge server has wired high-speed connectivity to the SugarBox CDN infrastructure. The Mobile Edge Server does not have wired high-speed connectivity to the SugarBox CDN infrastructure. Instead, it receives periodic high-speed connectivity to the SugarBox CDN infrastructure through a dedicated WiFi SSID in each Static Edge server, and also receives periodic infrastructure connectivity (not necessarily high-speed) using the cellular data services offered by the telecom provider.

Unlike a regular CDN, which operates on a caching model based on on-demand retrieval, SugarBox CDN operates on a hybrid model based on on-demand retrieval and non-request distribution. SugarBox CDN Edge Server (Static & Mobile) can be located at a Point of Interest (POI) that is characterized by specific user demographics and service access patterns.

Based on the above, the Edge server in the SugarBox CDN can be instructed to get a list of content that it should cache. Whenever the Edge Server has a high-speed connection to the SugarBox CDN infrastructure, the Edge Server begins downloading content from the previous layer and updating internal data structures to indicate that the content has been downloaded, as well as updating various other telemetry information. When each Edge server starts serving data to users, the consumption data is fed to machine learning algorithms to generate content lists based on user demographics and service access patterns on the Edge server.

Each of the SugarBox Edge Servers also has a Wi-Fi last mile configured to cover the entire POI, which is used to serve content that is cached in the Edge Server to the subscriber. SugarBox CDN Edge servers create a local network with autonomous DNS and DHCP services to enable subscriber mobile devices to connect to SugarBox.

1. The SugarBox Origin CDN is hosted inside the ISP/Telecom data center as shown in FIG. 5, and is connected to the existing Internet infrastructure.

2. SugarBox Mids are also hosted inside ISP/telecom data centers and connected to existing Internet infrastructure and SugarBox Origin.

3. Each Static Edge Server has a wired high-speed connection to SugarBox Mid.

4. Each Static Edge server also provides a last mile Wi-Fi connection that the user connects to when using the service.

5. Each Static Edge Server also has a dedicated SSID, which is used by other Mobile Edge Servers to connect to the Static Edge Server and use high-speed connectivity,

- 5 043324 available on the Static Edge server to communicate with the SugarBox CDN infrastructure.

6. Each Mobile Edge Server also has connectivity to the SugarBox CDN infrastructure using the telecom operator's cellular data connection. However, this connectivity is periodic and may not be high-speed.

7. Each Mobile Edge Server also provides a last mile Wi-Fi connection to which the user connects while using the service.

How the service works with SugarBox CDN.

When a subscriber starts a service supported by CDN SugarBox while in a POI where a Static or Mid Edge server is installed, the following 4 scenarios can exist.

Scenario 1.

The user has cellular data, and the SugarBox CDN Edge server also has high-speed connectivity to the CDN infrastructure (shown in Figure 6).

When both the Edge server has connectivity to the SugarBox infrastructure and the user has cellular data connectivity, the user's cellular data is used to process analytics and payment requests. The edge server also executes a local DRM solution. Regarding security requests, the request is either served locally on the Edge server or served using the user's cellular data connectivity. All other requests are served by the Edge server. If a subscriber requests content that is not present on the Edge server, then the request is served like a traditional CDN with the content cached on the Edge server and then served to the subscriber. This ensures that the subscriber can experience the complete service as intended.

The service can function as follows.

1. The user connects to the Internet via cellular data.

2. The user simultaneously connects to the Edge server using the last mile provided over Wi-Fi and the SSID that is open to the user of the service supported through SugarBox CDN.

3. The Edge server has high-speed connectivity with the SugarBox private cloud.

4. SB CDN Origin/Mid has high-speed access to the Edge server through the SugarBox private cloud.

5. The service provider's analytics server is connected to the Internet.

6. The service provider's payment server is connected to the Internet.

7. The service provider's security server is connected to the Internet.

8. SugarBox CDN Origin caches all content from the service provider's content server.

9. SugarBox CDN Origin caches all ads from the service provider's ad server.

10. SugarBox CDN Origin caches all ad tags from the service provider's ad server.

11. SugarBox CDN Origin caches all non-user specific API requests from the service provider's API server. For all user-specific API requests, the SugarBox CDN infrastructure acts as a backbone to deliver data from the service provider's API server to the user.

Scenario 2.

The user does not have cellular data, but the SugarBox CDN Edge server has high-speed connectivity to the SugarBox CDN infrastructure (shown in Figure 7).

In this case, everything works the same as in scenario 1 above, except for the following:

The SugarBox CDN infrastructure acts as a backbone for delivering data from the service provider's analytics server to the user and vice versa;

SugarBox CDN infrastructure acts as a backbone for delivering data from the service provider's payment server to the user and vice versa;

For all security requests that cannot be fulfilled by the Edge server locally, the SugarBox CDN infrastructure acts as a backbone to deliver data from the service provider's security server to the user and vice versa.

Scenario 3.

The user has cellular data, but the SugarBox Edge server does not have high-speed connectivity to the CDN infrastructure (Fig. 8).

In this case, the service operates exactly as it would in the absence of SugarBox, except for the following:

all content requests that are cached on the SugarBox Edge server are served using SugarBox;

all requests for ads and ad tags that are cached on the SugarBox Edge server are served through SugarBox;

all non-user specific API requests that are cached in SugarBox are served through SugarBox;

- 6 043324 all DRM/security requests that can be generated locally on the SugarBox Edgeserver are served through SugarBox.

Scenario 4.

The user does not have cellular data, and the SugarBox Edge server also does not have high-speed connectivity to the CDN infrastructure (Fig. 9).

This is the only case when the subscriber does not have access to the full functionality of the service. However, even in this scenario, SugarBox CDN ensures that the user can continue using the service. Below are the restrictions that the user will encounter in this case:

only APIs cached on the user's device or cached in SugarBox will be available to the user;

only content cached on the user's device or cached on the SugarBox will be available to the user;

only ads cached on SugarBox will be available to the user;

all analytics requests will be buffered by the service on the user device. This does not in any way affect the user's functionality;

Only offline payment options (prepaid vouchers purchased at POI by cash payment, or offline credit card transactions if supported) will be available to the user.

The above description, for purposes of explanation, has been described with reference to specific embodiments. However, the above illustrative discussions are not intended to be exhaustive or to limit the disclosure to the specific forms disclosed. Many modifications and changes are possible taking into account the above ideas. The embodiments have been selected and described to best explain the principles of the disclosure and its practical applications, thereby enabling others skilled in the art to best use the disclosure and the various embodiments with various modifications as appropriate for the particular intended use.

The system and method disclosed herein may be implemented by or distributed among one or more components, systems, servers, devices, other subcomponents. When implemented as a system, such systems may include and/or use, among other things, components such as software modules, OS library(s), firmware, etc., found in mainframe computers. In implementations where innovation resides on a server, such server may include or use components such as software modules, OS library(s), firmware, such as those found in mainframe computers.

In addition, the system and method as described herein may be implemented through implementations with different or entirely different software, hardware and/or firmware components than those set forth above. With respect to such other components (e.g., software, processing components, etc.) and/or computer-readable media associated with or embodying the present inventions, for example, aspects of the innovations disclosed herein may be implemented in accordance with multiple computing systems or general purpose or special purpose configurations. Various exemplary computing systems, environments and/or configurations that may be suitable for use with the innovations disclosed herein may include, but are not limited to, software or other components included in or embodied in personal computers, servers or server computing devices such as routing/connectivity components, portable or portable devices, multiprocessor systems, microprocessor-based systems, set-top boxes, consumer electronic devices, networked PCs, other existing computer platforms, distributed computing environments that include one or more of the above systems or devices, etc.

In some cases, aspects of the system and method may be implemented or executed by logic and/or logical instructions, including program modules executable, for example, in association with such components or circuits. In general, program modules may include procedures, programs, objects, components, data structures, etc., that perform specific tasks or implement specific instructions disclosed herein. The inventions may also be implemented in the context of distributed software, computer or circuit settings, where the circuit is connected via communication buses, circuits or communication lines. In distributed settings, control/instructions can come from both local and remote computer storage media, including memory devices.

The software, circuitry and components herein may also include and/or use one or more types of computer readable media. Computer readable media may be any available media that is located in, associated with, or accessible by such circuits and/or computing components. By way of example, and not limitation, computer readable media may include computer storage media and communications media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVDs) or other optical storage devices, magnetic tape, magnetic disk drive or others magnetic storage devices, or any other medium that can be used to store the required information and can be accessed by the computing component. The communication medium may include computer-readable instructions, data structures, program modules, and/or other components. In addition, the communication medium may include a wired medium, such as a wired network or a direct wired connection, but no medium of any such type includes a transient medium. Combinations of any of the above are also included within the scope of computer readable media.

In this specification, the terms component, module, device, etc. can refer to any type of logical or functional software elements, circuits, blocks and/or processes that can be implemented in a variety of ways. For example, the functions of different circuits and/or blocks can be combined with each other into any other number of modules. Each module may even be implemented as a software program stored in tangible memory (such as random access memory, read-only memory, CD-ROM memory, hard disk drive, etc.) to be read by the central processor to implement functions of the present invention. Or the modules may contain programming instructions transmitted to a general purpose computer or processing hardware/graphics hardware via a transmission carrier wave. Additionally, the modules may be implemented as hardware logic that implements the functions covered by the present invention. Finally, modules can be implemented using special instructions (SIMD instructions), field programmable gate arrays, or any combination thereof that provides the desired level of performance and cost. In addition to the embodiments described above in which the settings/rules, code and configuration are implemented in the NCO in the application, the settings/rules, code and configuration can be implemented at the network layer through network layer elements that perform the same processes as described above.

As disclosed herein, features consistent with the disclosure may be implemented by computer hardware, software, and/or firmware. For example, the systems and methods disclosed herein may be implemented in various forms, including, for example, a data processor such as a computer, which also includes a database, digital electronic circuit, firmware, software, or combinations thereof. In addition, while some of the disclosed implementations describe specific hardware components, systems and methods consistent with the disclosed innovations, they may be implemented using any combination of hardware, software and/or firmware. In addition, the above-mentioned features and other aspects and principles of the present invention may be implemented in a variety of environments. Such environments and associated applications may be specifically designed to perform the various routines, processes and/or operations of the invention, or they may include a general purpose computer or computing platform that is selectively activated or reconfigurable by code to provide the required functionality. The processes disclosed herein are not necessarily specific to any particular computer, network, architecture, environment or other device and may be implemented by a suitable combination of hardware, software and/or firmware. For example, various general purpose machines may be used with programs written in accordance with the teachings of the invention, or it may be more convenient to construct a specialized device or system to perform the required methods and methods.

Aspects of the method and system described herein, such as logic, may also be implemented as functionality programmed into any of a variety of circuits, including programmable logic devices (PLDs), such as field programmable gate arrays (FPGAs), programmable matrix logic devices ( PAL), electrically programmable logic and memory devices and standard cell-based devices, as well as application-specific integrated circuits. Some other possibilities for implementing aspects include: memory devices, microcontrollers with memory (such as EEPROM), embedded microprocessors, firmware, software, etc. In addition, aspects may be

-

Claims (13)

lyzed in microprocessors having software-based circuit emulation, discrete logic (sequential and combinatorial), custom devices, fuzzy (neural) logic, quantum devices, and hybrids of any of the above types of devices. The underlying device technologies can be provided in a variety of component types, such as MOSFET technology such as complementary MOS (CMOS), bipolar technologies such as emitter-coupled logic (ECL), polymer technologies (for example, silicon-conjugated polymer and metal-conjugated polymer-metal structures), mixed analog and digital, and so on. It should also be noted that the various logic and/or functions disclosed herein may be provided using any number of combinations of hardware, firmware and/or as data and/or instructions embodied in various machine-readable or computer-readable media , in terms of their behavioral characteristic, register transfer, logical component and/or other characteristics. Computer-readable media on which such formatted data and/or instructions may be embodied include, but are not limited to, nonvolatile storage media in various forms (e.g., optical, magnetic, or semiconductor storage media), although again do not include transient environment. Unless the context clearly requires otherwise, throughout the description the words contain, containing, etc. should be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense, that is, in a sense including but not limited to it. Words using singular or plural also include plural or singular, respectively. In addition, words herein, hereunder, above, below, and words of similar meaning refer to this application as a whole and not to any specific portions of this application. When the word or is used in reference to a list of two or more items, the word covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list. While specific presently preferred embodiments of the invention have been specifically described herein, those skilled in the art to which the invention relates will appreciate that changes and modifications to the various implementations shown and described herein may be made without departing from the spirit and scope of the invention. Accordingly, the invention is intended to be limited only to the extent required by the applicable rules of law. Although the foregoing has been described with reference to a specific embodiment of the disclosure, those skilled in the art will appreciate that changes to this embodiment may be made without departing from the principles and spirit of the disclosure, the scope of which is defined by the appended claims. CLAIM 1. Digital data delivery system containing: a multi-tier content delivery network (CDN) having an origin server at a first tier, one or more intermediate servers at a second tier connected to the origin server, a plurality of servers at a third tier connected to one or more intermediate servers at a second tier, and a plurality of computing devices that are configured to send requests to a multi-layer content delivery network using a wireless cellular data connection and a wireless Wi-Fi connection; wherein each third layer server is configured to periodically connect to a multi-layer content delivery network, wherein each specific third layer server is physically installed in said predetermined location and includes means for wirelessly connecting via Wi-Fi to form a Wi-Fi coverage area in this predetermined place; wherein the content delivery network is configured to implement a hybrid model for retrieving and distributing content, in which each said third-level server is configured to retrieve content from the content delivery network and distribute the content to a computing device located in the Wi-Fi coverage area of the third-level server, located in a predetermined location, after sending a request by any of the computing devices that have or do not have access to the Internet, through the use of the zone and means of Wi-Fi coverage of a third-level server, wherein said specific third-level server is configured to generate a list of content on based on user demographics and service access patterns associated with the predetermined location, cache content in accordance with the generated content list, and retrieve portions of the content in accordance with the generated content list from the multi-tier content delivery network for the predetermined location. 2. The system according to claim 1, in which the plurality of third-level servers may additionally contain - 9 043324 static third-level server, which has a Wi-Fi interface and a wired high-speed connection to one or more intermediate servers. 3. The system according to claim 2, in which the plurality of third-level servers may further comprise a mobile third-level server, which is configured to connect to a static third-level server via Wi-Fi SSID for high-speed communication, and is also configured to connect to a multi-level infrastructure content delivery networks over a cellular data network or other wireless means. 4. The system according to claim 3, in which the wireless communication means of each third level server, forming a Wi-Fi coverage area of said predetermined location, provide the ability to deliver content hosted by this third level server to a user's computing device that is located there in advance specific location, over a local network (LAN). 5. The system of claim 4, wherein each third-tier server is configured to operate without a connection to the multi-tier content delivery network because the last mile allows delivery of data cached on the third-tier server to support delivery of the digital service. 6. The system of claim 5, wherein each third-layer server is further configured to perform one or more of the following operations: generating security keys, generating ad tags, and generating API responses. 7. The system according to claim 6, in which each third-level server is always one hop away from the computing device, thereby ensuring faster delivery of content data for better user perception. 8. The system according to claim 7, wherein the multi-layer content delivery network is configured to use a dedicated last mile, which allows content delivery not to be shared with other services running on the Internet, thereby ensuring faster delivery of digital content data for better delivery. user perception. 9. The system of claim 8, wherein each third-tier server allows a user who does not have access to the last mile of the Internet through one of a cellular data connection or Wi-Fi to receive the full functionality of a digital service when the third-tier server is connected to infrastructure of a multi-level content delivery network. 10. The system of claim 9, wherein each third layer server allows a user who does not have access to the last mile of the Internet through one of the cellular data connections or Wi-Fi to receive a digital service with limited functionality when the third layer server does not connected to the infrastructure of a multi-layer content delivery network. 11. The system of claim 10, wherein each piece of data transmitted from each layer three server does not add load to the Internet infrastructure or the last mile of the Internet, thereby freeing up the bandwidth of the existing Internet infrastructure. 12. The system of claim 1, wherein each third-tier server is configured with machine learning capabilities to generate a content list based on user demographics and service access patterns associated with said predetermined location. 13. A method for accessing digital data, comprising the steps of forming a content request through one of the user's computing devices to a multi-layer content delivery network (CDN) using a wireless cellular data connection and a wireless Wi-Fi connection; perform content retrieval and distribution in accordance with a hybrid model in which each tier 3 server physically located at a predetermined location retrieves content from the content delivery network for that predetermined location, with each tier 3 server periodically connecting to the multi-layer content delivery network and has means for forming a Wi-Fi coverage area for the user's computing devices at said predetermined location; receiving, through third-layer servers located at said predetermined location, a plurality of pieces of content from one or more intermediate servers located in the second layer, and from a content delivery network source server to which the one or more intermediate servers are connected; forwarding content that was requested by any computing device located in a Wi-Fi coverage area formed by a third-layer server physically located in said predetermined location to this computing device, with or without Internet access, via Wi-Fi means and third-level server coverage areas; generating on each third tier server a content list based on user demographics and service access patterns associated with said predetermined location; and cache content on each third-level server in accordance with the generated content list, when retrieving parts of the content in accordance with the generated content list from the multi-level content delivery network for computing devices located in the coverage area -