Content delivery network system and method

CONTENT DELIVERY NETWORK SYSTEM AND METHOD

FIELD OF THE INVENTION

Disclosure generally refers to a system and method for the distribution of data and an architecture for the distribution of the data in a last mile, necessary for the operation of a digital service (mobile application / website / game / software application ).

BACKGROUND

The Internet and associated networks used by a consumer/consumer device to access a digital service, as shown in Figure 1, are well known. The Internet allows the different contents/data necessary for the operation of a digital service to reach a device, using a last-mile network, such as the smartphone shown in figure 1. The Internet, as shown in figure 1, is the combination of all the physical units distributed throughout the world that house all the information in the world. The Internet data center is a series of distributed physical units that house all network and computing equipment, including backup and redundant components, infrastructure for power supply, data communications connections, environmental controls and various security devices. The CDN infrastructure is a geographically distributed network of servers that are hosted in the Internet data center that provide most of the content on the Internet today, especially web objects (text, graphics, scripts), downloadable objects (multimedia files, , software, documents), applications, live streaming media, on-demand streaming media, and social networks whose architecture is well known and whose operation is well known. The Internet, together with the Internet data center and CDN infrastructure, are collectively referred to as the Internet infrastructure. A digital service provider includes all persons/companies/entities that use the infrastructure of the Internet to provide a service to consumers. The consumer platform is the mobile applications / websites / any interface through which a user accesses the service of a digital service provider. Telecom Infra is an infrastructure setup by telecommunications companies using licensed wireless frequencies

I give to access the Internet (2G / 3G / 4G / LTE - collectively, cellular data connections) and Wi-Fi Infra is the infrastructure set up by Internet service providers to provide broadband connectivity / leased line connectivity to access to the Internet or to which the access point can be connected to access the Internet wirelessly using the license-free frequency.

By using the conventional system shown in figure 1, the Service (Mobile Application) shown in figure 1 works as follows. All information made available by a digital service provider is stored/served via servers hosted by the digital service provider or via a CDN. Based on data access patterns (what data is consumed and where), the CDN infrastructure caches certain data (a subset of all information) on multiple servers spread across different geographies. CDN edge servers (EDGE1,..., EDGE in Figure 1) are distributed globally and are colocated within globally distributed third-party 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 the servers hosted by the digital service provider and the CDN through a “last mile”, which is the data connection between the consumer (the smartphone device , for example, in Figure 1) and Internet infrastructure (either through an Internet service provider, a telecommunications service provider or any other form of Internet connectivity option). The consumer's ability to access the service depends on the availability of the last mile to the consumer, and the consumer's experience of the service depends on the reliability and performance available in the last mile. More importantly, as the number of users and data consumption per user increases, the load on the existing Internet infrastructure increases exponentially, affecting the user experience in densely concentrated areas.

By using a current convention 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 operating system (OS) of the smartphone

Three Consumer (see Figure 1) detects the availability of connectivity through a cellular data connection (such as 4G/LTE as shown in Figure 1) or Wi-Fi. If connectivity is available using only one connection, the OS uses the available connectivity path. If both connectivity options are available, the OS detects which connection offers faster and more stable bandwidth availability and uses that connection to perform packet data transactions, with priority assigned to Wi-Fi. If the above scenario changes at any time, the OS automatically switches between the two, unless the user manually logs in or out of either of the two available options. The user can access the service whenever one of the two connections is available. The user experience when using the service depends on the stability and the available bandwidth on those connections. In case the user loses connectivity with both connections, the service stops working, except for any functionality that may be cached on the user's device (downloads in case of a streaming service).

Figure 2 illustrates how a conventional CDN works. As shown in Figure 2, a traditional CDN is typically a multi-tiered network of computing and storage servers. This is typically a pull-based CDN, where the response to a single request from a requester is cached closer to the requestor: the CDN edge server, which is the last tier of the CDN. When a requester makes a first request for a file, the CDN edge server, while delivering the file to the requester, also caches the file from the CDN origin server (as shown at the top of Figure 2). When the next requester makes the same request, instead of serving it from the CDN origin server where the response originated, it is delivered from the cache (the CDN edge server), thus 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 for the origin server. As shown in Figure 2, a CDN typically employs multiple geographically distributed edge servers to serve a large number of requesters. The location of the CDN edge servers is usually the ISP or the data centers of the telecom infrastructure. By serving cached content, it also equates to saving internet bandwidth for the ISP or telecom. In typical infrastructure:

four1. Origin CDN connects to the Internet

2. The edge server is connected to the origin CDN via

Internet.

3. The CDN edge server is located in a data center of the ISP/telecom operator and therefore has connectivity to the ISP/telecom infrastructure.

4. When requester 1 requests a piece of content, the CDN edge server, while serving requester 1's request, also caches the response itself.

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

Therefore, existing systems have the technical problem that access to data/services is completely dependent on the last mile, without which the CDN or servers hosted by a digital service provider cannot deliver any data to the service/ applicant. So you want to be able to provide a technical solution that is a novel CDN whose edge devices are closer to each requestor, that 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 the user's access to a last-mile connection.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 illustrates how the Internet infrastructure works.

Figure 2 illustrates how a conventional CDN works

Figure 3 illustrates how a digital service works using the infrastructure of the Internet, of which the conventional CDN is an integral part.

Figure 4 illustrates a new CDN system with CDN servers also deployed outside of the Internet infrastructure and with a last mile connected to the CDN servers.

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

Figure 6 illustrates how a digital service works using the new CDN system in a scenario similar to Figure 5 (both the CDN servers and the user device have Internet connectivity).

Five

Figure 7 illustrates how the new CDN system works in a case where a conventional CDN system would not work. This illustration is for a case where the user's device does not have Internet connectivity, but the new CDN server does.

Figure 8 illustrates how the new CDN system works in a case where a conventional CDN system would not work. This illustration is for a case where the CDN server does not have Internet connectivity, but the user's device does.

Figure 9 illustrates how the new CDN system works in a case where a conventional CDN system would not work. This illustration is for a case where both the CDN server and the user's device do not have Internet connectivity.

DETAILED DESCRIPTION OF ONE OR MORE EMBODIMENTS

The disclosure is particularly applicable to the digital service (mobile app/website/game/software app) installed on a computing device (smartphone/tablet/laptop/desktop/smartwatch, etc.) as shown in the figures that is used with a content distribution system and method and in this context the disclosure will be described. However, it will be appreciated that the disclosed system and method have greater utility, for example, to be implemented on a number of different computing devices that can be used to access content from a digital service provider. Furthermore, the exemplary CDN system can also be used to optimize the delivery of content or data from other systems and can be used in any system where it is desired to optimize consumer access and experience of a service. For purposes of this disclosure, the “service” provided to the consumer may be a piece of content (audio, visual, and/or textual) or any piece of digital data that is delivered to the consumer through any interface, including a browser, a mobile application, a software application and the like.

Figure 3 illustrates more details of the new CDN system 300. System 300 may further comprise one or more SugarBox hardware fragments 402, 404, 406 that can be connected to the Internet infrastructure in the Internet data center and can also be attaching to each of the computing devices 302 via a wide local area network (WLAN) that provides a communication path

Six additional communications for each application request. Each SugarBox piece of hardware, known as a SugarBox CDN server, can be deployed as one or more server computers that are also equipped with a dedicated last mile over Wi-Fi at each CDN edge that provides the following key functionalities:

• SugarBox CDN is connected to the existing Internet infrastructure and acts as a complementary infrastructure to the Internet. However, with the dedicated last mile junction over Wi-Fi, SugarBox CDN data is distributed using a last mile that is outside the scope of the existing Internet infrastructure (LAN), so:

o Frees up bandwidth on existing Internet infrastructure, especially in the last mile provided by Internet Service Providers/Telecom Operators or Does not burden existing last-mile Internet infrastructure with an increase in the number of users accessing or consumption per user • SugarBox CDN allows a user who does not have access to the Internet, using any of the existing connectivity options (Internet Service Provider or Telecom Operator), experience all or part of any service • SugarBox CDN can continue to function even when connectivity from a CDN edge server to the CDN infrastructure is down available, as the last mile can expose cached data at the CDN edge with the service, thus allowing access to the service in an area without reliable and sustained connectivity (transportation, remote locations, etc.) • The SugarBox CDN edge is always one hop away from the user (since it is available to the user through a network local area) compared to a traditional edge CDN, thus providing faster data delivery and facilitating a better user experience • SugarBox CDN utilizes a dedicated last mile, while the last mile on the existing internet infrastructure is a shared last mile for the CDN and all other services running on the internet, providing faster data delivery and facilitating a better user experience.

SugarBox CDN works in a last mile that works in a width

License-free band seven, making last-mile scalability virtually unlimited, thus allowing the service to provide a guarantee to consumers about the availability, reliability, and availability of bandwidth while using the service.

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

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

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

• The originating and intermediate 402 SugarBox servers that reside within an Internet data center and are part of the existing Internet infrastructure. These servers work similar to an origin server in a typical CDN.

• The Static Edge SugarBox 404 is connected to the source SugarBox using high-speed physical connectivity (P2P / MPLS) and has an attached Wi-Fi configuration exposed to the user • The Mobile Edge SugarBox 406, which from the point of view of the hardware and software stack is the same as the static edge SugarBox, but instead of having physical connectivity to the SugarBox CDN infrastructure, it connects wirelessly using one of the following two paths:

o Use of MPLS / cellular data connectivity through a telecommunications network (may be intermittent and may not have high speed) or Use of Wi-Fi and corresponding physical connectivity from a

Edge SugarBox (Always flashing when the mobile edge enters the network of a static edge and has high speed)

Eight

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

• API Requests / HTTP Requests • Security Requests: DRM / AES / SSL • Analysis Requests • Content Requests: Content / Downloadable Objects / Web Objects • Ad Requests • Payment Requests

In general, the analysis, payment and security requests are handled directly by the service provider through its own servers or third parties. All other requests are directed by a CDN as shown in Figure 4.

The SugarBox CDN works as follows:

• In the absence of the SugarBox CDN, the service uses last-mile connectivity (Internet Service Provider facility, either via Ethernet or Wi-Fi, or a cellular data service) to access all requests.

• When the user is within range of the SugarBox CDN edge server's Wi-Fi network or The service uses the user's cellular data connectivity to process all requests that are served directly by the service provider.

o The SugarBox CDN replaces the traditional CDN to process all requests that are directed by the CDN

The SugarBox edge server may support certain functionality such as DRM, local payments, etc., which are provided locally by the edge server.

In an example, the new CDN system can be implemented in hardware and software as follows:

Hardware Summary:

• Origin and intermediate SugarBox

Nine or Compute Servers or Storage Servers or Network Equipment • Static and Mobile Edge SugarBox or Compute Server + Storage or Network Equipment or Wi-Fi Equipment

Summary of the software stack:

• Source and Intermediate SugarBox or Content Service Software or DNS or DHCP or Logging and Monitoring or Databases • Static and Mobile SugarBox or Content Service Software or DNS or DHCP or Logging and Monitoring or Databases

How a service works using the existing Internet infrastructure:

To better understand how the new CDN and its elements work, we describe how a service works today using the existing Internet infrastructure and the traditional CDN with reference to Figure 4. A service needs a response in order for various types of services to work. requests. These requests are made through any connection to a device that has the Internet. By the nature of the requests, a CDN might cache or not cache them. Requests that can be cached are

Ten cache through a CDN to ensure that the load on the server on the IDC is reduced and the request is served from the closest point to the subscriber, optimizing speed and cost of delivery.

The service works, using the existing Internet infrastructure, as follows:

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

2. There is a WiFi connection (last mile from ISP) from the user's device to the Internet.

3. The CDN edge servers also have connectivity to

Internet.

4. Servers that accept analytics requests also require Internet connectivity.

5. Servers that accept payment requests also require Internet connectivity.

6. The servers that serve the keys to decrypt content (DRM keys) also require Internet connectivity.

7. The content, text, graphics, etc. they are served by servers in an Internet Data Center (IDC). The service for these requests is typically run by a CDN with an appropriate Time to Live (TTL) for the particular content. This is done to ensure that the content is available closer to the consumption of the previous content.

8. Ad serving from a server at an IDC is also run by a CDN to ensure ad content is available closer to where it will be consumed.

9. The ad tag service is run by CDNs with a TTL to ensure fast tag delivery.

10. Responses to API requests that are not specific to a user are cached on the CDN with a TTL to ensure less load on the API server. API requests that are specific to a user are either cached on the user's device or dispatched directly through the API server.

Eleven

For traditional CDN, a user relies on the availability of last-mile connectivity to access the Internet, through which a service gains access to all requests to provide the user with functionality and access to the service. In addition, the user and the service depend on the performance available in the user's last-mile connectivity and it is the reliability, which determines the user's experience of the service.

How SugarBox CDN works:

Figure 5 illustrates how a service using the new CDN system works and how the new CDN works. The SugarBox CDN is a multi-tier CDN architecture with the originating SugarBox CDN 402 forming the first tier, intermediate SugarBox CDN servers 402 forming the second tier, and edge SugarBox 404 servers forming the third tier.

SugarBox edge servers can be of 2 types: static or mobile. A static edge server has high-speed wired connectivity to the SugarBox CDN infrastructure. A mobile edge server does not have high-speed wired connectivity to the SugarBox CDN infrastructure. Instead, you get intermittent high-speed connectivity to the SugarBox CDN infrastructure through a dedicated WiFi SSID on each static edge server, and you also get intermittent connectivity to the SugarBox infrastructure (not necessarily high-speed) using services from Cellular data offered by a telecommunications provider.

Unlike a regular CDN, which works on a pull-based caching model, SugarBox CDN works on a hybrid push and push model. An edge SugarBox server (static and mobile) can be located at a point of interest (POI) that is characterized by specific user demographic and service access patterns.

Based on the above, an edge server within the SugarBox CDN can be told to get a list of the content it needs to cache. As long as the edge server has high-speed connectivity to the SugarBox CDN infrastructure, the edge server starts downloading content from the previous tier and updates the internal data structures to indicate that the content has been downloaded and also updates other content information. telemetry. As each edge server begins to deliver data to the

Voce users, consumption data is sent to machine learning algorithms to generate content lists based on user demographics and service access patterns at the edge server.

Each of the SugarBox edge servers also has a last mile over Wi-Fi, configured to cover the entire POI, which is used to serve the subscriber the content that is cached on the edge server. SugarBox CDN edge servers create a local network with autonomous DNS and DHCP services to allow subscribers' mobile devices to connect to SugarBox.

1. The source SugarBox is hosted within a data center of

ISP/telecom as shown in Figure 5 and is connected to the existing Internet infrastructure.

2. Intermediate SugarBoxes are also housed within ISP/telco data centers and are connected to the existing Internet infrastructure and the source SugarBox.

3. Each static edge server has high speed wired connectivity with an intermediate SugarBox

4. Each static edge server also provides last-mile connectivity via Wi-Fi, which a user connects to while using a service.

5. Each Static Edge Server also has a dedicated SSID that is used by another mobile Edge Server to connect to the Static Edge Server and use the high-speed connectivity 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 by using a telecommunications operator's cellular data connection. However, this connectivity is intermittent and may not be high speed.

7. Each mobile edge server also provides last-mile connectivity via Wi-Fi, which a user connects to while using a service.

How a service works with SugarBox CDN:

Thirteen

When a subscriber launches a SugarBox CDN compatible service, while at a POI where a static or middle edge server is installed, the following 4 scenarios can exist:

Scenario 1 – A user has cellular data and the edge SugarBox server also has high-speed connectivity to the SugarBox CDN infrastructure (shown in Figure 6)

When 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 runs a local DRM solution. For security requests, the request is either served locally at the edge server or served using the user's cellular data connectivity. All other requests are served by the edge server. If the subscriber requests content that is not present on the edge server, the request is served as a traditional CDN and the content is cached on the edge server and then delivered to the subscriber. This ensures that the subscriber can experience the full service as intended.

The service can work as follows:

1. The user is connected to the Internet via cellular data.

2. The user is simultaneously connected to the edge server using the last mile provided over Wi-Fi and an SSID that is exposed to the user of a SugarBox CDN compatible service

3. The edge server has high-speed connectivity to the SugarBox private cloud

4. The origin/intermediate SB CDN has high-speed access to the edge server via the SugarBox private cloud

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

Internet

6. The payment server of the service provider is connected to

Internet.

7. The service provider's firewall is connected to

Internet.

Fourteen

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

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

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

eleven. The origin SugarBox CDN caches all non-user-specific API requests from the service provider's API server. For all user-specific API requests, the SugarBox CDN infrastructure only acts as a pipeline to distribute data from the service provider's API server to the user.

Scenario 2: A user does not have cellular data, but the edge SugarBox 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 described above, except the following:

• The SugarBox CDN infrastructure acts as a pipeline to distribute data from the service provider's analytics server to the user and vice versa.

• The SugarBox CDN infrastructure acts as a pipeline to distribute data from the service provider's payment server to the user and vice versa.

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

Scenario 3 – A user has cellular data, but the SugarBox edge server does not have high-speed connectivity to the SugarBox CDN infrastructure (Figure 8)

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

• All requests for content that are cached in the

Fifteen edge SugarBox servers are served by SugarBox • All ad requests and ad tags that are cached on the edge SugarBox server are served by SugarBox • All non-user-specific API requests that are cached in SugarBox are served by SugarBox

All DRM/security requests that can be generated locally on the edge SugarBox server are served through SugarBox

Scenario 4 – A user does not have cellular data and the edge SugarBox server also does not have high-speed connectivity to the SugarBox CDN infrastructure (Figure 9)

This is the only case where the subscriber does not get access to the full functionality of the Service. However, even in this scenario, SugarBox CDN ensures that the user can continue to use the service. Below are the limitations a user will face in this case:

• Only APIs cached on the user's device or cached on the 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 in SugarBox will be available to the user • All scan requests will be buffered by the service on the user's device. This does not affect user functionality in any way.

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

The above description, for the purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit disclosure to the precise forms disclosed. Many modifications and variations are possible in

Sixteen view of the above teachings. The embodiments have been chosen and described in order to better explain the principles of the disclosure and their practical applications, thereby enabling others skilled in the art to better utilize the disclosure and various embodiments with various modifications that may be suitable for the particular contemplated use. .

The system and method disclosed herein may be implemented across one or more components, systems, servers, devices, other sub-components, or distributed among such items. When implemented as a system, such systems may include and/or involve, among others, components such as software modules, OS libraries, firmware, etc., found in general purpose computers. In implementations where the innovations reside on a server, that server may include or involve components such as software modules, OS libraries, firmware, such as those found in general purpose computers.

Furthermore, the present system and method can be achieved by implementations with disparate or entirely different software, hardware and/or firmware components, beyond what is stated above. With respect to other components (eg, software, processing components, etc.) and/or computer-readable media associated with or incorporating the present inventions, for example, some aspects of the innovations herein may be implemented consistent with many general or special purpose computer systems or configurations. Various exemplary computer systems, environments, and/or configurations that may be suitable for use with the innovations herein may include, but are not limited to: software or other components within or embedded in personal computers, servers, or server computing devices such as routing/connectivity components, portable or handheld devices, multiprocessor systems, microprocessor-based systems, set-top boxes, consumer electronic devices, network PCs, others Existing computing platforms, distributed computing environments that include one or more of the above systems or devices, etc.

In some cases, the system and method aspects may be achieved or performed by logic instructions and/or logic instructions including program modules, executed in association with said components or circuitry, for example. In general, program modules can include routines,

Sixteen^seven programs, objects, components, data structures, etc. that perform particular tasks or implement particular instructions herein. The inventions may also be practiced in the context of distributed software, computer, or circuit configurations where circuits are connected via buses, circuits, or communication links. In distributed configurations, control/instructions can occur from local and remote computer storage media, including memory storage devices.

The software, circuitry, and components hereof may also include and/or use one or more types of computer-readable media. Computer-readable media can be any available media that is resident, mappable, or accessible to such circuitry and/or computing components. By way of example, and not limitation, computer-readable media may include computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for the storage of 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-ROMs, digital versatile disks (DVDs) or other optical storage, magnetic tape, magnetic disk storage, or other storage devices. magnetic storage, or any other means that can be used to store the desired information and that can be accessed by a computer component. The communication media may comprise computer-readable instructions, data structures, program modules, and/or other components. In addition, the means of communication can include wired means, such as a wired network or a direct cable connection; however, no such media herein includes transient media. Combinations of any of the above are also included in the scope of computer-readable media.

In the present description, the terms component, module, device, etc. they can refer to any type of logical or functional software elements, circuits, blocks and/or processes that can be implemented in various ways. For example, the functions of several circuits and/or blocks can be combined with one another in any other number of modules. Each module can even be implemented

Eighteen as a software program stored in tangible memory (for example, random access memory, read-only memory, CD-ROM memory, hard disk drive, etc.) to be read by a central processing unit to implement the functions of innovations in the present. Or, the modules may comprise programming instructions transmitted to a general purpose computer or processing/graphics hardware via a transmission carrier wave. Furthermore, the modules can be implemented as hardware logic circuits that implement the functions comprised by the innovations herein. Finally, modules can be implemented using special purpose instructions (SIMD instructions), field programmable logic arrays, or any combination thereof that provides the desired level of performance and cost. In addition to the implementations described above in which settings/rules, code, and configuration are deployed to the NCO in the application, settings/rules, code, and configuration that may be implemented at the network level are element-level elements. network that perform the same processes described above.

As disclosed herein, features consistent with the disclosure may be implemented through computer hardware, software, and/or firmware. For example, the systems and methods disclosed herein can be implemented in a variety of forms, including, for example, a data processor, such as a computer that also includes a database, digital electronic circuitry, firmware, software, or combinations thereof. . Furthermore, while some of the disclosed implementations describe specific hardware components, systems and methods consistent with the innovations herein may be implemented with any combination of hardware, software, and/or firmware. In addition, the features mentioned above and other aspects and principles of the innovations herein can be implemented in various environments. Such environments and related applications may be specially built to perform the various routines, processes and/or operations according to the invention or may include a general purpose computer or computing platform selectively activated or reconfigured by code to provide the necessary functionality. The processes disclosed herein are not intrinsically related to any particular computer, network, architecture, environment, or other apparatus, and may be implemented by any suitable combination of hardware, software, and/or firmware. For example, you can use multiple

Nineteen general purpose machines with programs written in accordance with the teachings of the invention, or it may be more convenient to build a specialized apparatus or system to carry out the required methods and techniques.

Aspects of the method and system described herein, such as logic, can also be implemented as programmed functionality in any variety of circuitry, including programmable logic devices (PLDs), such as field programmable gate arrays (FPGAs), field programmable gate arrays (FPGAs), Programmable Array Logic (PAL), electrically programmable memory and logic devices, and standard cell-based devices, as well as application-specific ICs. Other possibilities for implementing aspects include: memory devices, microcontrollers with memory (such as EEPROM), embedded microprocessors, firmware, software, etc. In addition, aspects can be incorporated into microprocessors with software-based circuit emulation, discrete logic (sequential and combinatorial), custom devices, fuzzy logic (neural), quantum devices, and hybrids of any of the above device types. The underlying device technologies can be provided in a variety of component types, for example, metal oxide semiconductor field effect transistor (MOSFET) technologies such as complementary metal oxide semiconductor (CMOS), bipolar technologies such as logic Emitter Coupled Technology (ECL), polymer technologies (eg, silicon-conjugated polymer and metal-conjugated polymer-metal structures), mixed analog and digital, etc.

It should also be noted that the various logic and/or functions disclosed herein may be enabled using any number of combinations of hardware, firmware, and/or as embedded data and/or instructions on various machine- or computer-readable media, in terms of its behavior, record transfer, logical component and/or other characteristics. Computer-readable media into which such data and/or formatted instructions may be embedded include, but are not limited to, non-volatile storage media in various forms (for example, optical, magnetic, or semiconductor storage media) although again they do not include transient media. . Unless the context clearly requires otherwise, throughout the description, the words comprise, comprising, and the like are to be construed in an inclusive sense as opposed to a general sense.

Twenty exclusive or exhaustive; that is, in the sense of including, but not limited to. Words that use the singular or plural also include the plural or singular respectively. In addition, the words herein, below, above, below, and words of similar importance refer to this application as a whole and not to particular parts of it. When the word or is used in reference to a list of two or more items, that word encompasses 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. list.

Although certain presently preferred implementations of the invention have been specifically described herein, it will be apparent to those skilled in the art to which the invention pertains that variations and modifications of the various implementations shown and described herein may be made without departing from of the spirit and scope of the invention. Accordingly, it is intended that the invention be limited only to the extent required by applicable law.

While the foregoing has been made with reference to a particular embodiment of the disclosure, those skilled in the art will appreciate that changes may be made to this embodiment without departing from the principles and spirit of the disclosure, the scope of which is defined by the claims. attached.