Content delivery system

Abstract

A content delivery platform and a method of using the content delivery platform are disclosed. In one embodiment, the content delivery platform includes: one or more client devices, each of the one or more client devices having memory for storing an application and one or more processors for executing the application; and a first device having a physical local content cache for storing content to be directly provided to the one or more client devices, wherein, in response to executing the application via the one or more processors, each of the one or more client devices is operable to: automatically detect the presence of the first device; automatically connect to the first device; request content from the first device; obtain content from the first device; and disconnect from the first device after receiving content from the first device.

Description

[0001] Cross-reference to related applications

[0002] This PCT application claims the benefit of the earlier filing date of U.S. Provisional Patent Application No. 62 / 884,093, filed August 7, 2019, and U.S. Non-Provisional Patent Application No. 16 / 884,959, filed May 27, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Embodiments of the present invention generally relate to the field of data delivery via network download to a local content cache, which has fast local delivery to a client device. Background Technology

[0004] Thanks to massive investments from major internet companies, the delivery of large digital content, such as video, via the internet has improved. The internet backbone, the high-bandwidth dedicated connections between data centers, has significantly increased bandwidth within the cloud. Furthermore, large content caching data centers located at the internet's "edge" bring content closer to many client devices (users). However, one challenge in content delivery is the "last mile" of the network between Internet Service Providers (ISPs) and client devices. Some improvements have been made in this area through cable television cabling converted to ISP services, 4G cellular towers, and in some cases, fiber optic cabling. However, the demand for content delivery outweighs these investments. One challenge is how to get content closer to client devices, thereby reducing the need for costly networking in the last mile. This is the challenge addressed by the technology disclosed in this article. Summary of the Invention

[0005] According to one aspect of the present invention, a content delivery platform is provided, the content delivery platform comprising: one or more client devices, each of the one or more client devices having a memory for storing an application and one or more processors for executing the application; and a first device having a physical local content cache for storing content to be directly provided to the one or more client devices, each of the one or more client devices being operable to: automatically detect the presence of the first device; automatically connect to the first device; request content from the first device; obtain content from the first device; and disconnect from the first device after receiving content from the first device.

[0006] According to embodiments of this disclosure, a first device can deliver content without a network connection between the first device and a remote source of the content.

[0007] According to embodiments of this disclosure, a first device may be configured to receive content from a swappable memory device switched to the first device, and when the swappable device is connected to the first device, analytical data obtained from at least one of one or more client devices is stored in the swappable memory device.

[0008] According to embodiments of this disclosure, content can be delivered to a first device via networking with a mobile content recharge device, and analytics data from at least one of one or more client devices can be transmitted to the mobile content recharge device.

[0009] According to embodiments of this disclosure, content can be delivered to a first device via an Internet connection, and analytical data from at least one of one or more client devices can be transmitted from the first device to a remote location via an Internet connection.

[0010] According to embodiments of this disclosure, the delivery of content to the first device and the transmission of analytical data from the first device can occur during periods of off-peak bandwidth demand.

[0011] According to embodiments of this disclosure, a first device can be operated to authenticate at least one of one or more client devices without Internet access and intermediaries, and the one or more client devices can be operated to browse, request, and deliver content from the first device without Internet cloud authentication.

[0012] According to embodiments of this disclosure, a first device may be configured to automatically upload transaction and analytics data from one or more client devices when connected to each of one or more client devices, and the first device may be configured to upload the transaction and analytics data to a remote location via a content delivery method of the first device.

[0013] According to embodiments of this disclosure, at least one of one or more client devices is operable to upload analytical data to a first device, and the first device is configured to transmit the analytical data to a remote location.

[0014] According to another aspect of this disclosure, a method for content delivery is provided, the method comprising: executing an application using one or more processors via each of one or more client devices; automatically detecting the presence of a first device via at least one of the one or more client devices, the first device having a physical local content cache for storing content to be directly provided to the one or more client devices; automatically connecting to the first device via at least one of the one or more client devices; requesting content from the first device via at least one of the one or more client devices; obtaining content from the first device via at least one of the one or more client devices; and disconnecting from the first device via at least one of the one or more client devices after receiving content from the first device.

[0015] According to embodiments of this disclosure, the method may further include: delivering content via the first device to at least one of one or more client devices in the absence of a network connection between the first device and a remote source of the content.

[0016] According to embodiments of this disclosure, the method may further include: receiving content from a swappable memory device swapped into the first device by the first device before delivering content to at least one of the one or more client devices; and transmitting analysis data obtained from at least one of the one or more client devices to the swappable memory device when the swappable memory device is coupled to the first device.

[0017] According to embodiments of this disclosure, content can be delivered to a first device via networking with a mobile content recharge device, and analytics data from at least one of one or more client devices can be transmitted to the mobile content recharge device.

[0018] According to embodiments of this disclosure, content can be delivered to a first device via an Internet connection, and analytical data from at least one of one or more client devices can be transmitted from the first device to a remote location via an Internet connection.

[0019] According to embodiments of this disclosure, the delivery of content to the first device and the transmission of analytical data from the first device can occur during periods of off-peak bandwidth demand.

[0020] According to embodiments of this disclosure, the method may further include: authenticating one or more client devices via a first device without internet access and intermediaries; and at least one client device browsing, requesting, and delivering content from the first device without internet cloud authentication.

[0021] According to embodiments of this disclosure, the method may further include: automatically uploading transaction and analytics data from one or more client devices via a first device when connected to each of one or more client devices; and uploading the transaction and analytics data to a remote location via a content delivery method of the first device.

[0022] According to embodiments of this disclosure, the method may further include: uploading analysis data to a first device via at least one of one or more client devices; and transmitting the analysis data to a remote location via the first device.

[0023] According to another aspect of this disclosure, one or more non-transitory computer-readable storage media are provided, on which instructions are stored. When executed by a system having at least a processor and a memory, the instructions cause the system to perform a content delivery operation, the content delivery operation comprising: executing an application using one or more processors via each of one or more client devices; automatically detecting the presence of a first device via at least one of the one or more client devices, the first device having a physical local content cache for storing content to be directly provided to the one or more client devices; automatically connecting to the first device via at least one of the one or more client devices; requesting content from the first device via at least one of the one or more client devices; obtaining content from the first device via at least one of the one or more client devices; and disconnecting from the first device via at least one of the one or more client devices after receiving content from the first device.

[0024] According to embodiments of this disclosure, the operation may further include: delivering content to at least one of one or more client devices via the first device when there is no network connection between the first device and the remote source of the content. Attached Figure Description

[0025] The invention will be more fully understood from the following detailed description and the accompanying drawings of various embodiments thereof; however, these drawings should not be construed as limiting the invention to the specific embodiments, but are for illustration and understanding only.

[0026] Figure 1 It is a block diagram of one embodiment of the system and defines three independent software components of the system.

[0027] Figure 2 This is a block diagram of one embodiment of software running on a client device, referred to herein as a client.

[0028] Figure 3 This is a block diagram of the software running on the kiosk device, which is referred to herein as the content access point.

[0029] Figure 4 This is a block diagram of one embodiment of software running network services and websites on a server in the cloud, referred to herein as a dedicated network service server.

[0030] Figure 5 This is a communication diagram illustrating an example interaction between a content access point and a client application.

[0031] Figure 6 This is a block diagram of one embodiment of a client device.

[0032] Figure 7 This is a hardware block diagram of one embodiment of a content access point. Detailed Implementation

[0033] Content delivery systems deliver content quickly and securely between client devices and pre-loaded content caching devices or networks. In other words, they deliver large amounts of digital content rapidly to mobile devices with virtually no latency. This system is ideal for delivering large videos and other multimedia content that are frequently viewed on mobile devices.

[0034] In one embodiment, the content delivery system comprises three or more software components running on different types of hardware. Two of the basic components include a content access point, which is a local content repository with wireless access, and a client application (client app) that interacts with the content access point to initiate a download. In some embodiments, a third component, namely a dedicated network service, provides client application authorization and / or content access point content management.

[0035] In one embodiment, the content access point contains content data stored in a local cache or accessible via a local area network (LAN). The content access point has the ability to connect to mobile devices. In some embodiments, the content access point provides high-speed wireless connectivity, such as, but not limited to, Wi-Fi. With locally stored content and a high-speed connection, content can be transmitted at high speed with little or no latency. Through various different embodiments, the content access point is also able to determine which content a given client application is authorized to download.

[0036] A client application is an application that runs on a client device (e.g., a mobile device) and performs its functions when initiated or controlled by a user. The client application is responsible for initiating content downloads. In embodiments using wireless connectivity, the client application detects the presence of a content access point, connects to that access point (e.g., wireless connection), requests content, and receives the downloaded content. In one embodiment, many variations of the client run on corresponding variations of the client device, such as Android, iOS, etc. In one embodiment, the client software interacts with a private network service (PLAN) to create an account, register the device, and perform transactions to obtain authorization for the content. In one embodiment, the PLAN also wirelessly connects to the content access point to transmit pre-authorized content (and, in some embodiments, other functions, see below). Although the software is implemented using different languages ​​and libraries, all variations of the client software perform the same functions (e.g., as shown below) depending on the type of device running the software. Figure 2 (The functions shown). Furthermore, in one embodiment, the client software is compatible with software connectivity in content access points and private network services (e.g., discovery, HTTP, and API calls).

[0037] In one embodiment, the content access point runs on a kiosk device or network device. In one embodiment, the content access point is an identified physical device, such as an information kiosk. In one embodiment, the content access point has a user interface consisting of one or more of the following components: a display screen, a pointing method or device, and a keyboard. In one embodiment, a user can interact with the content access point interface, create an account, register the device, and perform transactions in a manner similar to a client. The software is implemented using different languages ​​and libraries, and all variants of the content access point software execute and... Figure 3 The same functionality is shown. Furthermore, in one embodiment, all client software is compatible with software connections in the client and dedicated network services (e.g., discovery, HTTP, and API calls).

[0038] In one embodiment, the content access point is one or more dedicated Wi-Fi signals from a Wi-Fi access point that can be detected by client software and devices. Therefore, the content access point can be a Wi-Fi network without a physical presence facing the user. In some embodiments, identifiers and physical objects are used to represent the location of the content access point, which is optional.

[0039] In one embodiment, the content access point also acts as a proxy network to access private network service software and servers. In this embodiment, the content access point manifests as a Wi-Fi access point.

[0040] In one embodiment, the content access point is temporarily not connected to the private network service and performs operations with the client (e.g., creating an account, registering a device, or a transaction). These operations are stored and transferred to the private network service later when the connection is re-established.

[0041] In one embodiment, the content access point connects to a dedicated network service only when a suitable wired or wireless connection becomes available. For example, if a bus, delivery truck, or other dispatch service arrives and connects to the content access point, then at that time, all appropriate content will be downloaded to the content access point and all appropriate data (e.g., analytics, customer interactions, etc.) will be uploaded.

[0042] In one embodiment, the content access point is continuously connected to a dedicated network service via a suitable Internet connection. Content can be downloaded to the content access point at any time, although the dedicated network service server may choose a time when better bandwidth is available or arguably the optimal time. In one embodiment, client data is continuously uploaded.

[0043] In one embodiment, a dedicated network service runs on a cloud server and performs the following backend functions. The system serves numerous client devices and preloads and coordinates the behavior of numerous content access point devices or networks. The software is implemented using different languages ​​and libraries, and depending on the type of network server running the software, all variants of the network software perform the same functions, such as... Figure 4 As shown. Furthermore, in one embodiment, the client software is compatible with software connections in the client and content access points (e.g., discovery, HTTP, and API calls).

[0044] definition

[0045] For the purposes of this article, a content delivery system is the software and hardware used to implement client device transactions, authentication, and content downloading.

[0046] Client devices are most commonly computers, laptops, tablets, or mobile phones, but are not limited to these devices. However, the technologies described herein are not limited to the types of client devices served. For example, set-top boxes, digital video recorders, smartwatches, and Internet of Things (IoT) devices can all be served by the content delivery system.

[0047] A preloaded content caching device or network, referred to hereinafter by the term content access point, is a physical device or network having memory for storing content (e.g., video content). The content access point also has wireless connectivity (e.g., Wi-Fi) and software to connect to client devices and deliver content. In one embodiment, the content access point is part of an identifier or physically identifiable device that allows a user to identify their location. In one embodiment, the content access point is a wireless network that a client device can automatically connect to. Finally, the content access point has one or more methods for preloading content (e.g., downloading from the Internet, loading from a similar device, or loading by a courier, etc.). In one embodiment, the content access point is the kiosk mentioned in U.S. Patent No. 10,104,046 B2, "Content Delivery System and Method". A dedicated network service is a combination of software and web servers that perform all backend cloud functions.

[0048] A client is an application running on a client device that initiates and receives pre-authorized content. On some client devices, content selection transactions can also be performed. On others, secure device registration implies content authorization. In this case, content selection occurs outside the client.

[0049] Digital Rights Management (DRM) is an encryption technology commonly used to protect content such as videos.

[0050] CRUD is an acronym that refers to common software data operations such as creating, reading, updating, and deleting.

[0051] Content typically includes video data. However, any type of data can be used. In one embodiment, the content delivery system uses the technology in U.S. Patent No. 8,751,795B2, "Secure Transmission and Tracking of Data Using a Removable Non-Volatile Storage Device," to protect, track, ensure usage rules, and provide analytics.

[0052] Content delivery system data stream

[0053] Figure 1 This illustrates the relationships between the components of the content delivery system. (Refer to...) Figure 1 Cloud 100 includes backend services for the dedicated network service module and any associated servers, such as content servers from content provider 101.

[0054] exist Figure 1The diagram identifies three functions of the Private Network Service. These will be described in more detail below. Specifically, the Private Network Service Content Management 102 module processes content data streams from content provider 101 to one or more content access points 105. Note that only one content access point 105 is shown to avoid obscuring the teachings disclosed herein. In one embodiment, content is preloaded onto content access point 105 via instructions from the Private Network Service Content Management 102. In another embodiment, the Private Network Service Content Management 102 responds to requests for content from content access point 105.

[0055] In one embodiment, the Private Network Service Content Management Module 102 directly manages content data storage. In another embodiment, the Private Network Service Content Management Module 102 acts as a proxy server for the data storage of the content provider 101.

[0056] Figure 1 A communication channel between content access point 105 and client 106 is shown. In one embodiment, client 106 automatically detects and connects to content access point 105 and transmits authorized content.

[0057] Figure 1 The diagram shows content traveling from content provider 101 to dedicated network service content management module 102 via content communication channel 107 (e.g., wireless connection, wired connection, etc.), then from dedicated network service content management module 102 to content access point 105 via content communication channel 108, and finally from content access point 105 to client 106 via content communication channel 109 (e.g., wireless connection, wired connection, etc.).

[0058] In one embodiment where content is preloaded at content access point 105, the content is delivered at different (asynchronous) times, first to content access point 105 and then to client 106.

[0059] In one embodiment where client 106 requests content that has not yet been preloaded onto content access point 105, the content data flows from content provider 107 (or, if it is data storage, from dedicated network service content management module 102) to content access point 105 and then to client 106 in roughly equal time, similar to streaming.

[0060] Figure 1 Two other functions are shown. The dedicated network service analysis module 103 receives and processes analysis signals from the content access point 105 and the client 106.

[0061] There is also bidirectional communication between the dedicated network service transaction module 104 and the client 106 used for purchasing content and receiving authorizations.

[0062] Similar bidirectional communication exists between client 106 and content access point 105 via transaction analysis communication channel 112 (e.g., wireless connection, wired connection, etc.). If there is no network connection between client 106 and private network service transaction module 104 or private network service analysis module 103, client 106 uses transaction analysis communication channel 112 for these functions.

[0063] The value and use of content delivery systems

[0064] Implementations of content delivery systems are of significant value to users, content providers, and network providers. This is important because all three stakeholders are involved in content delivery.

[0065] The value to users includes:

[0066] • Fast—Two hours of high-definition video in less than a minute.

[0067] • Excellent viewing experience – low latency, no buffering, no interruptions.

[0068] Convenient – ​​Seamless automatic download, no internet connection required.

[0069] Ideal for airports, trains, buses, bookstores, shops, shopping malls, gas stations, etc.

[0070] The value to content providers (Netflix, Amazon, Apple, Hulu, etc.) includes:

[0071] • Reaching untapped users worldwide – most parts of the world lack sufficient bandwidth.

[0072] • Security — Digital Rights Management (DRM) of Content

[0073] • Analysis – Understanding download, playback, and deletion behavior

[0074] • Versatile—Supports various content, sizes, and formats (e.g., HD, HDX, UHD / 4K, 8K, etc.).

[0075] The value to network and internet service providers (ISPs) (such as Comcast, AT&T, Verizon, etc.) includes:

[0076] New content delivery channels – potential new revenue streams.

[0077] • Reduce the burden of video demands on mobile devices

[0078] • Deploy inexpensive content access points.

[0079] Content includes, but is not limited to, movies, television, video games, health records, financial records, personnel records, training videos, educational videos, and sports.

[0080] Valuable places to use content delivery systems include, but are not limited to, airplanes, airports, buses, bus stations, trains, train stations, hospitals, restaurants, cafes, shops, hotels, squares, and public places.

[0081] The following is a description of embodiments of client software, content access point software, dedicated network service software, and other functionalities.

[0082] Client application

[0083] The client application is initiated or controlled by the user. In some embodiments, the client application only detects content access points (e.g., content access point signals), requests content, and downloads content while in the foreground (e.g., through a user interface exposed to the user). In some embodiments, the client application can perform these functions in the background.

[0084] In embodiments using wireless connectivity, the client application detects the presence of a content access point. For example, in one embodiment using Wi-Fi, the client application detects the signal via a Service Set Identifier (SSID), connects to the signal, requests content, and downloads the content data. In one embodiment, after downloading the content data, the client application disconnects from the content access point. In another embodiment, after disconnecting from the content access point, the client application reconnects to the Wi-Fi signal it previously connected to, if available.

[0085] In one embodiment, the client application is authorized to interact with all or specific content at the content access point. In one embodiment, the client application possesses one or more special codes for authorizing the download of any or specific content. In one embodiment, authentication of the client application is achieved through digital certificate exchange. In one embodiment, the client application provides a login name and password to the content access point.

[0086] In one embodiment, the client application obtains authorization for specific content through a prior transaction (e.g., purchase, gift, exchange, etc.) and receives an coded receipt for that transaction. In another embodiment, the operation of the client application itself implies authorization for any or specific content. That is, installing the client application requires a prior transaction (e.g., purchase) or subscription to any or specific content. In one embodiment, the client application is authorized to use limited download permissions (e.g., one-time gift download, a specific preset number of downloads).

[0087] In one embodiment, the client application can browse the content available on the content access point and allow the user to select which content to request for download. In one embodiment, when the content access point has internet access and acts as an internet access point, the client application can browse web services to obtain content and conduct transactions on the network. In one embodiment, the client application can conduct transactions directly with the content access point without an internet connection. Transactions, including the exchange of credit information (e.g., credit card numbers), will be recorded the next time the content access point is "recharged," as described in more detail below.

[0088] In some embodiments, the client application uploads analytics data to the content access point upon connection. This data may include information about what content was viewed, when it was viewed, and other similar analyses that are generally video-related.

[0089] Client software

[0090] This component of the client provides user-facing applications for browsing, accessing, and playing media content (e.g., DRM-enabled media content) on various mobile platforms.

[0091] In one embodiment, the client software is developed for a specific device platform (e.g., iOS devices - iPhone, iPad, Android devices - tablets, phones, Amazon devices, Windows devices, Mac laptops, game consoles, media devices (Roku, etc.), smart TVs, etc.).

[0092] In one embodiment, the client software includes various components from the backend interface, security, and core application modules. These components will be discussed below.

[0093] Reference Figure 2 The following is a description of the modules in the backend interface 200 of one embodiment of the client software.

[0094] Account / User Management 204

[0095] This is a dedicated network service interface component that allows users to perform the following tasks:

[0096] • Create new accounts (each account can have multiple users and devices)

[0097] • Create, view, update, or delete users in the account

[0098] Displays all users registered to this account.

[0099] • View details of each user assigned to this account

[0100] • Assign permission levels to each user on the account

[0101] • Set up parental viewing settings for account users

[0102] Equipment Management 205

[0103] This is a dedicated network service interface component that allows users to perform the following tasks:

[0104] • Remove device from account

[0105] View information about all devices registered to this account.

[0106] Warehouse Management 206

[0107] This is a dedicated network service interface component that allows users to perform the following tasks:

[0108] Display all licensed media (valid rental or purchase media) on your device and account.

[0109] • Display rental / purchase history

[0110] • Identify expired media and remove it from the client.

[0111] • Delete media from the client

[0112] • Request to download media to a specific device in the account.

[0113] Billing Management 207

[0114] This is a dedicated network service interface component that allows users to perform the following tasks:

[0115] • Create, view, update, or delete billing service options

[0116] • Display available billing options

[0117] • Select the default billing option

[0118] Reference Figure 2 The following is a description of the client software module in application component 201.

[0119] Shop interface 208

[0120] This is an application component that allows users to perform the following tasks:

[0121] • Browse the system catalog to find media you want to rent or buy.

[0122] • Find media by genre, title, or other meaningful search methods

[0123] • Find the media and display more details about it.

[0124] • Offers a range of media formats (SD, HD, HDX, and 4K for movies)

[0125] Network Core 209

[0126] This is the application component that provides infrastructure support and performs the following tasks:

[0127] • Obtain store data to populate the store interface

[0128] Download licensed media content

[0129] • Obtain media license

[0130] • Obtain customer data (e.g., accounts, users, devices, databases, etc.) from dedicated network services.

[0131] • Communication and file retrieval from devices to content access points or private network services.

[0132] • Download files incrementally from content access points or dedicated network services (partial download recovery)

[0133] • Upload Analysis

[0134] Download by range

[0135] Download Management 210

[0136] This is the application component that provides infrastructure support and performs the following tasks:

[0137] • Queue for downloading media content

[0138] • An interface for viewing, updating, or deleting activities or queued downloads.

[0139] File Management 211

[0140] This is the application component that provides infrastructure support and performs the following tasks:

[0141] • Manage and retrieve files that support the store page

[0142] • Manage media content on the device, including metadata and supporting files.

[0143] • Check the device's storage capacity to prevent retrieving media that is too large for local storage.

[0144] • Delete files when they are unnecessary or requested by the user.

[0145] • Clear storage cache when application exits

[0146] Persistent storage 212

[0147] This is the application component that provides infrastructure support and performs the following tasks:

[0148] • Storage mechanism for custom application options

[0149] Secure storage of credentials

[0150] Analysis Engine 213

[0151] This is the application component that provides infrastructure support and performs the following tasks:

[0152] • Collect usage and record data from user devices

[0153] Application Settings 214

[0154] This is an application component that allows users to perform the following tasks:

[0155] Customize the appearance of the client application.

[0156] • Interact with persistent storage to retrieve or store application or security settings

[0157] Content Access Point Locator 215

[0158] This is the application component that provides infrastructure support and performs the following tasks:

[0159] • Map interface used to locate content access points

[0160] • Set access points for saved content

[0161] • Search for them in the geographic area near the user

[0162] Resource cache 216

[0163] This is the application component that provides infrastructure support and performs the following tasks:

[0164] • A component for managing metadata, images, etc.

[0165] • Ensure that resources do not consume more than 80% of available system resources.

[0166] Reference Figure 2 The following is a description of a module in the security section 202 of an embodiment of the client.

[0167] Login 217

[0168] This is a security component that allows users to perform the following tasks:

[0169] • Login client and content delivery system

[0170] • Uniquely identifies the device used to access the system

[0171] • A unique identifier for the user logging in

[0172] Authentication Mechanism 218

[0173] This is a security component that allows users to perform the following tasks:

[0174] • Use a dedicated network service or a secure channel (SSL, TLS, etc.) using a content access point.

[0175] Register devices in user accounts

[0176] • Authentication via dedicated network services and content access points

[0177] • Access to purchase and acquisition process

[0178] DRM Media Player 219

[0179] This is a security component that allows users to perform the following tasks:

[0180] • Safe media playback

[0181] • Forward, rewind, stop, pause, and play

[0182] • A counter to track media progress

[0183] Full-screen capacity

[0184] Hide the control when not actively used.

[0185] • License data for storing media files

[0186] Content access point description

[0187] A content access point is a physical device that can be found in many locations. In one embodiment, a content access point includes content storage, a Wi-Fi access point that client applications can connect to, and computation for content management, client authentication, analytics collection, and "recharge management".

[0188] Recharge management here refers to the preloading, reloading, and updating of content. It also includes transmitting analytics and transaction data received from client applications that interact with the content access point. Finally, recharge management includes updating the list of any authorization information (e.g., authorization codes) required for client applications to connect to the content access point.

[0189] Recharging can be performed in many different ways. In one embodiment, the content access point is communicatively connected to the network service via Ethernet or other wired networks. In one embodiment, the content access point is communicatively connected to the network service via Wi-Fi or other wireless networks. In one embodiment, the content access point is communicatively connected to a Wi-Fi mesh network. In each of these embodiments, the network service directly recharges the content access point. The network service can continuously add or remove content data from the content access point based on one or more algorithms. In one embodiment, at least one algorithm predicts local demand for content. Alternatively, the network service can change the queue during times when bandwidth is available, such as during off-peak early morning hours.

[0190] In one embodiment, the content access point is recharged by adding physical storage containing new content. In another embodiment, the content access point is recharged by swapping physical storage containing new content. In one embodiment, the swapped-out physical storage includes analytics and / or transactional data obtained from the content access point when the physical storage is attached to the content access point, wherein the analytics and / or transactional data is obtained from the client device to the content access point upon connection. In another embodiment, the content access point is recharged by swapping one of the "disks" in a Redundant Array of Independent Disks (RAID) storage configuration. In this embodiment, the software recognizes the new disk as the "correct" disk and copies the content to the old disk—the opposite of typical RAID functionality.

[0191] In one embodiment, the content access point is charged via a portable storage device temporarily connected to the content access point. In another embodiment, the portable storage device is connected to the content access point via a wired connector (e.g., USB or Ethernet). In yet another embodiment, the portable storage device is connected to the content access point wirelessly (e.g., Bluetooth, Wi-Fi, etc.).

[0192] Upon connection, the content access point downloads all new content data and deletes any unwanted content. In one embodiment, the portable storage device includes instructions on which older content to delete. In another embodiment, the portable storage device uploads analytics and transaction information from the content access point. Subsequently, the portable storage device connects to another device (e.g., a host device) that controls all content, transactions, and analytics. In one embodiment, the host device is an internet network service.

[0193] The following describes a typical transaction between a content access point and a client application.

[0194] Content access points

[0195] This component of the content delivery system provides various services to support the delivery of licensed media from content access points to end clients. These components will be discussed below.

[0196] Reference Figure 3 The following is a description of the software modules in the Network Service API 300 in one embodiment of the content access point.

[0197] Store API 303

[0198] This is a web service API component that provides access to the following tasks:

[0199] • Request metadata to populate the storage interface

[0200] • Interface for requesting store catalog and store layout instructions

[0201] • An interface that requests the download of media for which the user has a license.

[0202] Content access point updater 304

[0203] This is the updater service component that performs the following tasks:

[0204] • New update to the download content access point service

[0205] • Ability to install, uninstall, start, and stop content access point services on content access point devices.

[0206] • Use a dedicated network service to perform heartbeat checks

[0207] • Able to update service

[0208] Store Data Update Program 305

[0209] This is the updater service component that performs the following tasks:

[0210] • Dedicated network service for checking new media packages based on content access points

[0211] • Download, add, update, or delete the current media package located at the content access point.

[0212] • Check new catalog or store layout files to update content access points and clients.

[0213] Reference Figure 3 The following is a description of the software modules in core functionality 301 of one embodiment of the content access point.

[0214] Analysis Engine 306

[0215] This is a core functional component and performs the following tasks:

[0216] • Collect usage and record data from user devices

[0217] Authentication mechanism 307

[0218] This is a core functional component and performs the following tasks:

[0219] • It has authentication capabilities for dedicated network services and authenticates clients.

[0220] • Authentication of content access points for dedicated network services to obtain DRM media content and additional data for intermediate storage.

[0221] 308 on startup page

[0222] This is the core functional component and performs the following tasks:

[0223] • This page introduces the content access point; if someone opens a browser while connected to the content access point router...

[0224] • Link to the client store to download the application (link to the client store should be enabled)

[0225] Reference Figure 3 The following is a description of the software module in library 302 of the content access point.

[0226] Store Warehouse 309

[0227] This is a library component that performs the following tasks:

[0228] • Store page layout that stores store data on client devices

[0229] • Store media metadata and images for use in the client's store interface.

[0230] • A directory that stores content access points and tracks the inventory of content access points.

[0231] Content Library 310

[0232] This is a library component that performs the following tasks:

[0233] • The DRM media content available for download or streaming is listed in the Content Access Points directory.

[0234] Trailer Library 311

[0235] This is a library component that performs the following tasks:

[0236] • The content access point directory lists media trailers that can be streamed.

[0237] Dedicated network service

[0238] This section provides an overview of cloud-level private network service capabilities supporting one embodiment of a content delivery system. (Refer to...) Figure 4 The following is a description of an embodiment of the software module in the dedicated network service software module of the client service 400.

[0239] User / Account Management 403

[0240] This is a client service component that allows users to perform the following tasks:

[0241] • Create a new account

[0242] Log in to an existing account

[0243] • Use third-party authentication (Google, Facebook, etc.)

[0244] • Delete the account and all users within it (account owner only).

[0245] • Create, view, update, or delete users in the account

[0246] Displays all users registered to this account.

[0247] • View details of each user assigned to this account

[0248] • Assign permission levels to each user on the account

[0249] • Set up parental viewing settings for account users

[0250] Storage Interface 404

[0251] This is a client service component that allows users to perform the following tasks:

[0252] Browse the system catalog to find products to rent or buy.

[0253] Search products by type, title, or other meaningful search methods.

[0254] • Ability to search for products in specific categories

[0255] • Perform appropriate sub-filtering and sorting on the product list.

[0256] • Able to display more detailed information about a specific product

[0257] • Access a range of product formats (for movies, SD, HD, etc.)

[0258] Pricing by product category

[0259] • Purchase media that users want

[0260] • Find content access points near the user's location

[0261] Add the product to your wishlist

[0262] User help link

[0263] • Flexible architecture allows for easy configuration of stores via a management dashboard.

[0264] Normal changes to store content and configuration do not require programming.

[0265] Equipment Management 405

[0266] This is a client service component that allows users to perform the following tasks:

[0267] • Remove device from account

[0268] View information about all devices registered to this account.

[0269] • Add devices to your account (via web API and the device player itself only)

[0270] Warehouse Management 406

[0271] This is a client service component that allows users to perform the following tasks:

[0272] Displays all licensed media in the account (valid rentals or purchases).

[0273] • Display rental / purchase history

[0274] • Identify expired media and delete it from the account

[0275] • Request to download owned / rented media to specific devices in the account

[0276] • Capable of streaming media from a user's account to the player

[0277] Billing Management 407

[0278] This is a client service component that allows users to perform the following tasks:

[0279] • Ability to create, view, update, or delete billing service options

[0280] • Display available billing options

[0281] • Select the default billing option

[0282] • Display transaction history

[0283] • Able to handle store transactions through the store interface or via network API calls

[0284] • Capable of utilizing various merchant gateways (such as PayPal, Google Cash, Square, Authorize.net, etc.)

[0285] Reference Figure 4 The following is a description of one embodiment of the dedicated network service software module in the management service 401. In one embodiment, the management service includes components for managing the entire platform. The management service manages user accounts (e.g., users, libraries, devices, etc.), remotely deployed content access points (e.g., status, current directory, logs, etc.), libraries, and analytics.

[0286] User / Account Management 408

[0287] This is a management service component that performs the following tasks:

[0288] • Users can perform all functions using their accounts.

[0289] Display all accounts in the system.

[0290] • View detailed information for a specific account

[0291] View a list of all users in the system.

[0292] • User accounts are flagged for various reasons

[0293] • Product licenses held by the management account

[0294] • Manage accounts, users, devices associated with accounts, and account media libraries

[0295] Store Management 409

[0296] This is a management service component that performs the following tasks:

[0297] • Web interface for managing the store for web clients

[0298] Generate store recipes that can be stored, modified, and used by the store.

[0299] Administrators can create new store interfaces without programming.

[0300] • Access the store's metadata, catalog, images, trailers, etc.

[0301] • Billing transaction functionality for purchasing or leasing media

[0302] Equipment Management 410

[0303] This is a management service component that performs the following tasks:

[0304] • Remove device from user account

[0305] • Default information regarding device type and compatible devices

[0306] View all devices in the system

[0307] • Analyze equipment usage, demographics, etc.

[0308] • Create, update, or delete devices in the device library.

[0309] Product Management 411

[0310] This is a management service component that performs the following tasks:

[0311] Main interface for managing the product database

[0312] • Displays all products in the system (with various sorting capabilities)

[0313] • Create, update, or delete products from the system

[0314] • Manage product-related media packages (metadata, thumbnails, backgrounds)

[0315] • Sort and filter products in the system.

[0316] • Support data used for updating, creating, and deleting main product data tables

[0317] • Manage images, videos, and other files for specific products

[0318] Content Access Point Management 412

[0319] This is a management service component that performs the following tasks:

[0320] • Main interface for managing all installed content access points

[0321] • Track the last check-in time of content access points

[0322] • Track transaction statistics for each content access point (login, browsing, purchase, rental, download, etc.)

[0323] • Update the interface (configuration) of the content access point software.

[0324] • List and directory of content access points

[0325] • Track the uptime of content access points

[0326] Analysis Engine 413

[0327] This is a management service component that performs the following tasks:

[0328] • Analyze transaction statistics

[0329] • Analyze user demographics, browsing history, etc.

[0330] • Analyze equipment usage

[0331] DRM Server 414

[0332] This is a management service component that performs the following tasks:

[0333] • Backend DRM security for media content

[0334] Personalization of client devices

[0335] • Provided through a third party (e.g., Widevine, PlayReady, etc.)

[0336] Cloud API 415

[0337] This is a management service component that performs the following tasks:

[0338] • Client API for client service functions

[0339] Content Access Point API for content access point management

[0340] • Client API for client transaction services

[0341] Reference Figure 4 The following is a description of the software modules in library 402 of one embodiment of Private Network Service x. This section provides components for storing and managing data prior to the transformation of business usage.

[0342] Account 416

[0343] This is a library component that performs the following tasks:

[0344] • Storage of all accounts within the system

[0345] • ORM access account information

[0346] User 417

[0347] This is a library component that performs the following tasks:

[0348] • Storage of all users and accounts within the system

[0349] ORM access to all user and account information

[0350] Equipment 418

[0351] This is a library component that performs the following tasks:

[0352] Storage of all devices within the system

[0353] • Default device graphics and information stored for each device type in the device library

[0354] • Default device for each available type

[0355] • ORM access to device information

[0356] Product 419

[0357] This is a library component that performs the following tasks:

[0358] Storage of all products within the system

[0359] • Store relevant data about the product (images, metadata, etc.)

[0360] • Will store links to supporting images, trailers, and actual videos.

[0361] Content access point 420

[0362] This is a library component that performs the following tasks:

[0363] • Store statistics about each content access point

[0364] • Store credentials for each content access point

[0365] • Location information for each content access point

[0366] Detailed description of the Dedicated Network Service Library

[0367] This section discusses the details of the collected data, namely the database schema, and its use in a dedicated network service.

[0368]

[0369]

[0370] User Information

[0371] Data Name Purpose Billing type PayPal, Authorize.net, credit cards, etc. Card types Visa, MC, AMEX, etc. card number Credit card number security code Credit card security code expiration date expiration date Street address Security verification City Security verification state Security verification postal code Security verification ？？？ More information is needed depending on the payment option (e.g., PayPal, etc.).

[0372] Billing Information

[0373] Data Name Purpose username Tag the account User List User set (each account ex1-6) Equipment List User set (each account ex1-12) Library List of contents owned by the account Event History Transaction history of this account

[0374] Account Information

[0375]

[0376] Equipment Information

[0377] Data Name Purpose Tablet PC Serial Number # Unique Identification Device Android ID Unique identifier for Android devices WI-FIMac Unique device identification; all devices using our system require Wi-Fi. Operating system version Tracking purpose

[0378] Data Name Purpose Movie name Display, picking, and search options Ratings Display, picking, and search options, as well as parental guidance. Genre Display, picking, and search options Length Display Purpose release date Display, picking, and search options rent Movie rental fees (standard definition, high definition, full high definition, and ultra-high definition) Purchase price Cost of purchasing movies (SD, HD, HDX, and UHD) actor Display Purpose director Display Purpose Document size Verify that the device has sufficient storage space and the intended display format (SD, HD, HDX, and UHD). describe Display Purpose release date Display, picking, and search options

[0379] Product Information

[0380] Data Name Purpose TV drama Title of the play Display, picking, and search options Performance Period Name Display, picking, and search options Performance period price Cost of the entire performance period describe Display Purpose TV series list Select purpose

[0381] Data Name Purpose TV series Title of the play Display, picking, and search options Ratings Display, picking, and search options Genre Display, picking, and search options Length Display Purpose rent Movie rental fees Purchase price The cost of purchasing TV series File size HD Verify if there is space on the device and the purpose of the display. File size HD Verify if there is space on the device and the purpose of the display. describe Display Purpose release date Display, picking, and search options

[0382] Design details of dedicated network services

[0383] This section covers design details of components in one embodiment of the content delivery system.

[0384] General Design

[0385] In one embodiment, this component of the content delivery system provides a user-facing application for browsing, accessing, and playing DRM-enabled media content on various mobile platforms.

[0386] • Both the client-side storefront and the management dashboard have the following characteristics:

[0387] Mobile-first design

[0388] • At least four media query conversion points

[0389] • Horizontal and vertical modes on the processing equipment

[0390] Include responsive images and SVGs whenever possible.

[0391] · Responsive typography

[0392] • The headers and footers of all portal websites should be identical for at least all content pages.

[0393] • Hovering impact on desktop / laptop users

[0394] Video / Image Processing

[0395] Small still images are encoded and bundled with HTML.

[0396] Larger images are compressed and resized to reduce their size while maintaining quality.

[0397] Larger or dynamic images are located behind a CDN.

[0398] Trailers and unencrypted videos are located behind a CDN.

[0399] All images and videos require appropriate licenses.

[0400] • All images have alternative text.

[0401] Front-end resources

[0402] Bundling all front-end resources

[0403] • Bundled between vendors (e.g., Bootstrap, etc.) and site-specific sources.

[0404] Styles and scripts are not bundled together (styles are loaded first, then scripts to reduce loading time).

[0405] • All sources have been narrowed down

[0406] • All JavaScript has been made ugly.

[0407] This website is designed for the United States; other countries will be localization projects.

[0408] The Flavicon icon is located at the root of the browser tab icon brand.

[0409] All text has been proofread and grammatically checked.

[0410] • Copyright text with the appropriate year must be in the footer.

[0411] The site runs on HTTPS

[0412] Custom error pages (e.g., 404, etc.)

[0413] Customer Service

[0414] This section describes the design and workflow of a client service based on one embodiment of the client.

[0415] Note: When storing credit card information, it complies with PCI. Third-party billing is recommended, as this is often one of the requirements of our partners.

[0416] Content delivery system store interface

[0417] This page is divided into 4 main sections:

[0418] Menu title

[0419] Giant Hero Carousel

[0420] Main content

[0421] ·footer

[0422] This page mimics the Amazon Prime Video homepage.

[0423] title

[0424] The header contains top-level page links to the most frequently used pages, including:

[0425] • Product-specific pages or filter pages (e.g., filters for movies, TV shows, or children).

[0426] Content access point locator

[0427] ·search

[0428] ·Ku

[0429] Wish List

[0430] ·set up

[0431] ·help

[0432] Login / Logout

[0433] footer

[0434] The footer contains links to the following pages:

[0435] Company page (About Us, Contact Us)

[0436] ·terms of use

[0437] Privacy Statement

[0438] • Any other legal pages

[0439] Giant Hero Carousel

[0440] This section contains numerous promotional activities for the current cycle. In one embodiment, each hero image has a link to a product details page, a promotional page, or any content linked from the management dashboard. In one embodiment, the carousel is configurable (e.g., no fewer than four main images, no more than eight main images, etc.). In one embodiment, the configurability of the store hero carousel is set in the management dashboard.

[0441] Main content section

[0442] This section features a series of customized carousels according to one embodiment. Each carousel has multiple banner thumbnails, a control title, and an option link that points to a more specific page filtered according to the carousel's filters.

[0443] The carousel is:

[0444] • Standard banner thumbnail carousel with title and optional deep links

[0445] In one embodiment, an optional configuration includes:

[0446] • Small square thumbnails with titles and optional deep links

[0447] Full-length banner

[0448] Banners of different sizes suitable for responsive frames

[0449] The purpose of different carousel configurations is to draw the customer's attention to different things. First, create a banner thumbnail bar as a standard. In one embodiment, the number of carousels can be configured via a management dashboard and the content within each bar. All tiles in the carousel have pop-up modal dialog boxes that provide more detail where appropriate. All tiles in the carousel also have links to product details pages or any content linked through the management dashboard.

[0450] Product-specific / filtered pages (e.g., filters for movies, TV shows, or children).

[0451] In one embodiment, product-specific pages or product filtering pages have the same interface as the store interface homepage. These pages can be configured from the management dashboard in the same way as the store homepage.

[0452] In one embodiment, these pages are filtered in the following way:

[0453] • Product type (movies, TV programs)

[0454] • Filters (e.g., content for children)

[0455] Further filtered pages, such as those displaying a "View More" link or genre thumbnails, create a grid of thumbnails or banner thumbnails without a hero carousel. The top-level page restrictions are similar to those of Amazon Prime. Further filtered pages function more like Vudu's page filtering. These pages are modeled after Amazon Prime's top-level filtered pages.

[0456] Content Access Point Locator

[0457] In one embodiment, the Content Access Point Locator page resembles Redbox's "FindaBox" page. It begins with a modal dialog box that requests the user's postal code or a "Find Nearby" option, which uses an HTML5 geolocation tool to pinpoint the user's location. Once either is activated, a Content Access Point Locator page appears.

[0458] In one embodiment, the page consists of the following components:

[0459] • Maps (Google, Bing, or others) with custom content access point icons.

[0460] Browse by postal code box

[0461] Content access point list

[0462] ·address

[0463] Distance from user location

[0464] • Browse Products button (browses the currently loaded content at a specific access point)

[0465] • Get route links (via Maps, Bing, Google, or other methods)

[0466] • Can be added to users' favorite content access points

[0467] search

[0468] In one embodiment, this component resembles Redbox's search component, providing filtered search results in a dialog-like mode without leaving the current page. In another embodiment, results are returned via an Ajax call to a backend search endpoint, and the search returns only product titles, but may include partial titles, actor names, and director names. A link to a product details page is provided after the returned name.

[0469] Library

[0470] The library page features a grid of user-generated content. It has a top-level filter for product type. It also has secondary filters on the right for sorting purposes. This page is similar to the Amazon Prime video library page.

[0471] Wish List

[0472] The Wishlist page features a grid of user-generated content added to a user's wishlist. It has a top-level filter for product types. It also has secondary filters on the right for sorting purposes. Thumbnails contain links to product detail pages and purchase options. The thumbnails use the same pop-up format as the store interface. This page is similar to Amazon Prime's Your Watchlist page.

[0473] set up

[0474] This section discusses the different user portal settings that users can manage in the client services section of the private network service. The areas covered here are:

[0475] Account settings

[0476] User Settings

[0477] Equipment settings

[0478] • Billing Management

[0479] Purchase history

[0480] One goal is to have an account with a library of associated accounts. An account can have multiple users, one of whom is the primary user. It can also have many devices. For example, an account with 6 users and 12 devices is similar to the design of Ultraviolet. This can be defined during the system setup for partners.

[0481] Account settings

[0482] The account settings page contains the following content (viewable based on user permissions):

[0483] Name field

[0484] User list

[0485] Equipment List

[0486] • Add user button

[0487] • Add device button

[0488] • Account Country (This version is only available for the United States; this feature will be added later)

[0489] The page is similar to how Ultraviolet performs this operation.

[0490] User Settings

[0491] User Settings 1e

[0492] ·surname

[0493] ·email address

[0494] ·username

[0495] User password

[0496] User types

[0497] • Date of birth (optional)

[0498] Users can be of three different types:

[0499] • Main – Account Owner

[0500] ·standard

[0501] • Restricted

[0502] Restricted users have the following capabilities:

[0503] Search for content in the library

[0504] • Request to send content to the device

[0505] • View content details (in the store or library)

[0506] Watch the trailer

[0507] This user does not have purchasing privileges.

[0508] Standard users have the following capabilities:

[0509] • Do everything that a limited number of users can do.

[0510] Purchase content

[0511] View user list

[0512] View device list

[0513] The main users have the following capabilities:

[0514] • Do everything a standard user can do.

[0515] Edit his account name

[0516] Add / edit or delete users

[0517] Add or remove devices

[0518] • Change the user's parental controls

[0519] • Define account country (This version is only available for the United States; this feature will be added later)

[0520] • Billing options for adding / editing or deleting accounts

[0521] • Close account

[0522] The page is similar to how Ultraviolet performs this operation.

[0523] Equipment settings

[0524] The user settings page contains the following content (viewable based on user permissions):

[0525] • List of devices in the account

[0526] • Add device button

[0527] • Add Device button (with the code entered by the user in the device settings)

[0528] The button next to the device can be removed if needed.

[0529] The page is similar to how Ultraviolet does this. Amazon and Vudu have similar pages.

[0530] Billing Management

[0531] The billing management page features (similar modeling to Vudu):

[0532] Payment methods list

[0533] • A button that marks an option as the default option

[0534] • Add payment options button (standard or third-party (PayPal))

[0535] Standard debit / credit payment options collection:

[0536] • Bill Street Address

[0537] ·City

[0538] ·state

[0539] ·postal code

[0540] The name on the card

[0541] ·card number

[0542] ·expiration date

[0543] CVC

[0544] Third-party payment systems have different mechanisms for linking to web apps. Each is handled as needed. Page is similar to how Ultraviolet does this.

[0545] Purchase history

[0546] The purchase history page has:

[0547] • List of purchased products

[0548] • List of rented products

[0549] ·Date of transaction

[0550] • Lease end date (Lease only)

[0551] Username for conducting transactions

[0552] • Meaningful sorting and filtering capabilities (by user, date, year, etc.)

[0553] • Rating (1 to 5 stars)

[0554] help

[0555] This page has links to other pages and / or expanded help options based on the amount of newly provided help information.

[0556] Login / Logout

[0557] This is a basic login page. It consists of the following basic information:

[0558] ·username

[0559] ·password

[0560] • Links to usage terms and privacy statement

[0561] Login button

[0562] • Create a link if the user needs to create an account.

[0563] There's no specific page or mode for logging out. It's just a link in the upper corner of the store interface page.

[0564] Product Details

[0565] The product details page has the following list (movies):

[0566] Product Name

[0567] • Star rating (user review system)

[0568] • Ratings (IMDb, Rotten Tomatoes, etc.)

[0569] • Running time (minutes)

[0570] MPAA rating (movies)

[0571] • Brief introduction

[0572] • Genre List

[0573] ·director

[0574] • Main cast (3 or fewer)

[0575] • Buy and rent buttons (in a drop-down menu format like Vudu's)

[0576] • Add to Wishlist button

[0577] • Watch trailer button

[0578] • Link to Terms of Use

[0579] • Share product links on social media

[0580] • List of related content thumbnails

[0581] ·Detailed information block

[0582] Genre

[0583] ·director

[0584] Leading actors

[0585] ·supporting role

[0586] ·studio

[0587] MPAA rating

[0588] • Subtitles and subtitles (may be added later)

[0589] • Audio (can be added and changed)

[0590] ·Format

[0591] ·release date

[0592] The product details page lists the following:

[0593] Product Name

[0594] • Star rating (user review system)

[0595] • Ratings (IMDb, Rotten Tomatoes, etc.)

[0596] Performance period year

[0597] ·Number of performances

[0598] TV ratings

[0599] A brief description of the performance period

[0600] • Genre List

[0601] • Buy and rent button blocks (for each season, similar blocks are listed below for each episode)

[0602] • Add season to wishlist button

[0603] • Watch trailer button (Msybe)

[0604] • Link to Terms of Use

[0605] • Share product links on social media

[0606] TV series list

[0607] Episodes

[0608] ·title

[0609] Short set description

[0610] TV ratings

[0611] ·run

[0612] ·release date

[0613] • Buy / Rent button block per episode

[0614] • List of related content thumbnails

[0615] Performance details

[0616] Genre

[0617] ·director

[0618] • Performance period announcement date

[0619] ·network

[0620] • Producers

[0621] ·Format

[0622] This page is similar to the product details page for Amazon Prime Video (which includes sections from Vudu).

[0623] Purchase page

[0624] In one embodiment, the purchase page is displayed via a link from the product details page or from a model in the store interface.

[0625] In one embodiment, the store does not have a shopping cart and purchases are made one at a time because hard copies of the product are not maintained in the inventory system. In another embodiment, the user simply purchases a license to view content on the device registered to the user's account, and the license is stored in the account's library. In yet another embodiment, the purchase page is not displayed if the user is not logged in or does not have billing information associated with the account.

[0626] The checkout process is largely similar to Vudu's. In one embodiment, the purchase is a two-phase commit. Two-phase commit limits accidental purchases, although it does add an extra step to the purchase process.

[0627] The purchase page displays as follows:

[0628] • Products purchased by the user (thumbnail, title, content creation date)

[0629] Purchase type: Rent or buy

[0630] Product formats: Standard definition, high definition, etc.

[0631] ·price

[0632] ·Tax

[0633] ·All

[0634] • Default billing option (e.g., PayPal)

[0635] Purchase button

[0636] This page is modeled after Vudu's checkout page.

[0637] Account creation page

[0638] This is a basic account creation page. It consists of the following basic information:

[0639] ·username

[0640] ·email address

[0641] ·password

[0642] • Password (re-enter)

[0643] • Links to usage terms and privacy statement

[0644] • Create button

[0645] • If the user already has an account, the link will allow them to log in.

[0646] Company page (About Us, Contact Us)

[0647] This page or schema contains company information, contact information, and any other content the company wishes to add to this section. In one embodiment, the structure and composition are defined by the executives.

[0648] terms of use

[0649] This page or schema is comprised of the terms of use for the content. The content and format of this page were legally generated.

[0650] Privacy Statement

[0651] This page or schema consists of the system's privacy notices. The content and format of this page were legally generated.

[0652] Content delivery system management service

[0653] This component of the content delivery system provides user-facing applications for browsing, accessing, and playing DRM-enabled media content on various mobile platforms.

[0654] In one embodiment, most actions in the system create a transaction log, indicating the action performed and who performed it (thus providing auditing capabilities). No user, administrator, or other person may delete anything from the audit table. Audits are only archived.

[0655] Content Delivery System Management Dashboard

[0656] This page is divided into 4 main sections:

[0657] • Top menu title

[0658] Side menu bar

[0659] Main content

[0660] ·footer

[0661] title

[0662] The title consists of top-level page links to the most frequently used pages, including:

[0663] Login / Logout

[0664] Side menu collapse / expand button

[0665] ·title

[0666] ·help

[0667] Side menu bar

[0668] This is the main menu for the dashboard system. It contains links to the following pages:

[0669] • Title (includes profile picture)

[0670] Products (movies, sets, TV series, TV series seasons, TV series episodes, etc.)

[0671] Product support data

[0672] • Account Management (Accounts, Users, Devices, Libraries)

[0673] Equipment Management

[0674] Content access point management

[0675] Store configuration management

[0676] Administrative Management

[0677] ·analyze

[0678] System Settings

[0679] Each of these menu items has an additional submenu within a side menu or within the content area of ​​its page.

[0680] Main content section

[0681] This section holds the content for all other pages in the dashboard system. Each content page is independent and provides the functionality needed to perform tasks related to its content. Some pages may contain submenu title bars that are limited to the page content area.

[0682] footer

[0683] The footer contains the following links to the following pages:

[0684] Company page (About Us, Contact Us)

[0685] ·terms of use

[0686] Privacy Statement

[0687] • Any other legal pages

[0688] Product Page

[0689] The menu items are essentially retainers of the sub-menu pages for the different products listed below:

[0690] ·product

[0691] ·Movie

[0692] • Bundling

[0693] ·TV drama

[0694] TV Season

[0695] TV series

[0696] All pages in this category have the following capabilities:

[0697] • A product list containing appropriate details

[0698] • View detailed information for a single product

[0699] • Create a new product that includes all the details (metadata, thumbnails, etc.)

[0700] Edit detailed information for a single product.

[0701] • Delete a product (deletion simply moves the product to an inactive state).

[0702] • Filter and sort all products

[0703] • Search for specific products

[0704] product

[0705] This page includes a complete list of products in the system. Products are defined by genre (such as movie) and format (such as SD). Individual prices can be attached to products, so each format can be priced differently according to the requirements of partners or content owners.

[0706] The products include the following:

[0707] Product type (movies, etc.)

[0708] • Links pointing to specific items (movie titles, movie series, or other bundles, etc.)

[0709] Available formats

[0710] • Price for each format (which may all be the same price)

[0711] Movie

[0712] This page deals with movie products. It provides the ability to add movies to the system. It includes the features previously listed in the main product section.

[0713] The film contains the following:

[0714] • Metadata (text) about the film

[0715] • Image links (thumbnails, backgrounds, banners, etc.)

[0716] Trailer link

[0717] • Video link (location used to store encrypted media in its format)

[0718] bondage

[0719] This page handles bundles. A bundle is simply multiple movies bundled together, such as the entire Star Wars series. Bundles can only be created using content already available in the system. A bundle is a product, and its pricing may differ from that of a single item sold separately.

[0720] TV drama

[0721] This page deals with television series. Television series are not typically sold as a product. It contains advanced information about the series. Seasons and episodes contain more detailed information about each. If an entire series is sold (such as a series that no longer releases new episodes, like Friends), it's considered a very large bundle but will be created in this category.

[0722] TV series season

[0723] This page deals with television seasons. A television season can be sold as a set of shows (which is usually the case), but individual shows can be sold separately at their own price.

[0724] TV series

[0725] This page is where you create specific episodes. At the heart of a TV series is a single episode. Each episode is added to a specific season of a particular series.

[0726] Note: Regarding television products. They are created in the following order: series, season, and episode. The episode screen has a drop-down menu that associates new episodes with a specific season of the series.

[0727] Product Support Data

[0728] This menu item contains several other product support pages to which you can add data. Everything from MPAA ratings to actor names is included in this section. There is no exhaustive list at present, but new items can be added to this section as needed.

[0729] Each specific supporting data page has the following functions:

[0730] • List all items in a specific supporting data category (e.g., a list of genres).

[0731] • Create a new project

[0732] Edit the current project

[0733] • Delete the project (only if the project is not in use)

[0734] Account Management

[0735] The account management page allows administrators to manage user accounts within the system. An account is a collection of users, devices, and associated databases.

[0736] Administrators can perform the following operations:

[0737] • Allow users to make most changes to their own accounts, except for purchasing products.

[0738] except

[0739] • A complete CRUD (Create, Read, Update, Delete) account

[0740] • Complete CRUD (Create, Read, Update, Delete) operations within the account

[0741] • Full CRUD (Create, Read, Update, Delete) device within the account

[0742] • Complete CRUD (Create, Read, Update, Delete) content in the account database

[0743] Administrators can suspend an account (and all connected users and devices).

[0744] Equipment Management

[0745] This section provides an embodiment of the device storage library and detailed data on each type of supported device.

[0746] Content access point management

[0747] The Content Access Point Management pages allow administrators to manage remote Content Access Points. These pages allow for catalog creation and allocation. They also provide the ability to provide new versions of Content Access Point software to Content Access Points.

[0748] Directory Management

[0749] The catalog management page allows you to create product catalogs to be stored in content access points. These product catalogs include the following:

[0750] Media packages for each product

[0751] Metadata for each product

[0752] Trailer link

[0753] • Image links (thumbnails, banners, etc.)

[0754] • Links to encrypted data

[0755] supply

[0756] The provisioning page allows content access points to update themselves after deployment. Once a new installation package is available, this page provides a way to define how to deploy the package. Deployment is defined via a manifest, similar to a catalog. The provisioning manifest contains links to the packages and a list of content access points to be provisioned. This allows administrators to selectively upgrade content access points for testing.

[0757] Store Configuration Management

[0758] The storage configuration management page allows you to create storage configurations that can be set up for use with the dedicated network service storage interface. These configurations include the following:

[0759] Configuration Name

[0760] Number of hero images

[0761] • List of links to hero images

[0762] • Number of carousel columns

[0763] Carousel configuration list

[0764] Carousel title

[0765] • Types of carousel banners (standard, small square, etc.)

[0766] • Product list displayed via carousel

[0767] Does the carousel display a "More" button and a link to a "More" page?

[0768] In one embodiment, configurations can be stored and reused. Only one activity can be set at a time.

[0769] Administrative Management

[0770] The management page allows the creation of administrator accounts. Because these differ from user accounts, more details are involved. Depending on our partners' requests, this feature may link to their HR systems to obtain data for these pages.

[0771] The management page includes standard employee contact information, avatars, etc. This page has the standard CRUD capabilities found in most dashboard pages.

[0772] analyze

[0773] The analytics page allows administrators to view the current analytics status of dedicated network services, content access point networks, and clients deployed to user groups.

[0774] The analytics engine is described in a separate specification, although all analytics evaluations originate from those pages. Initially, Firebase was used for analytics collection, as it now has functionality across all our platforms.

[0775] System Settings

[0776] The system settings page allows for the ability to configure settings for the global platform. Some of these may be as simple as a theme for each user, while others may affect the entire system, such as users for each account. Some settings may only be available during setup, as changing the user settings for each account during operation could have a significant impact on the system being used. All settings for dedicated network services and the general system are accessible from here.

[0777] Safety

[0778] This section discusses the security of the management services portion of the dedicated network service. Network authentication is handled by Firebase, providing an industry-strong authentication solution out of the box with a variety of login features and built-in analytics supporting login and logout services. Content is encoded and protected before being placed into our management system. Access to content and storage from the Admin Dashboard is restricted to those authorized to access the Admin Dashboard.

[0779] Network API (client and content access point)

[0780] This component of the invention provides APIs for clients and content access points to communicate with dedicated network services.

[0781] • Once the client and content access point LLD are complete, the requirements will be defined later.

[0782] Dedicated network service configuration

[0783] This section covers the details of how to configure a dedicated network service layer in the cloud.

[0784] Standard configuration

[0785] The following is a discussion of the folder structure and the details of content and media storage within our system.

[0786] GZip needs to be enabled on the hosting site.

[0787] CDN hosting

[0788] At certain times, static components can be moved to a CDN for responsiveness. These include:

[0789] ·picture

[0790] Style sheets

[0791] Script library

[0792] Trailer

[0793] Additional components

[0794] This section lists other embodiments and components that support or support the software described above.

[0795] Content access point streaming – providing localized streaming of encrypted media content at the content access point location. Clients can continuously stream content using traditional streaming technologies while remaining close to the content access point.

[0796] Windows device support – Supports universal Windows systems, including a large number of clients from laptops, tablets, phones, Xbox, HoloLens, and more.

[0797] OSX Support – Provides OSX clients for Apple computers through the Mac App Store.

[0798] Console support – Supports streaming and local downloading of media content to consoles such as Xbox 360, Xbox One, PS3, and PS4.

[0799] Smart TV and media device support – Supports streaming and local downloading of media content to media devices such as Roku, Apple TV, Amazon TV, Chromecast, etc. Also supports Google TV and other brands of smart TVs.

[0800] Homespot delivers its client and store interface directly to users' homes. It supports streaming to devices, as well as downloading directly from local cache to devices in the home.

[0801] Hub Server – Provides an intermediate caching server that serves a collection of content access points within a region, such as shopping malls or airports. The hub server provides a single point of access for updating all directories, media, etc., and all content access points within its collection. It can provide a single point of access for updating content access point software and content. It can also serve as a single analytics aggregation point for the collection of content access points.

[0802] MoviesOnFlash offers the ability to deliver secure content via flash drives. The content can still only be played by compatible players.

[0803] A dedicated web-based service store—a complete web-based store for buying and downloading DRM-enabled media content. Most of the components required to deploy the content access point will also support the existence of the online store.

[0804] Streaming content from a private network service – streaming directly from a private network service using traditional streaming technologies.

[0805] Alternative Clients – Supports client devices such as mobile devices running Android and iOS; media devices such as Amazon Kindle and Windows mobile devices; set-top boxes such as Roku, Amazon Fire TV, Neo TV, and Apple TV; and game consoles such as Xbox One X, Xbox One, PS3, and PS4.

[0806] Example communication between content access points and client applications

[0807] For illustrative purposes, this is an example of a communication session between a content access point and a client application for some embodiments. Furthermore, not all embodiments require some of the steps in this example. Finally, depending on the specific embodiment of the client application, a single content access point may interact differently with different client applications. For example, client applications may be embedded in proprietary applications from different companies and still use the same content access point (e.g., the Netflix and Hulu apps may use the same content access point). Client applications may be different versions or require different types of authentication. There may be different connection protocols (e.g., different from Wi-Fi) and different authentication methods.

[0808] In this example, the user launches client application 510. The client application stores information about existing Wi-Fi connections 511 to reconnect when the session ends. The client application then searches for the content access point SSID 501 broadcast by content access point 500. In one embodiment, the SSID is not broadcast and the client application attempts a blind connection. When client application 512 detects the SSID, it connects and sends password information 513 (if needed). The client application then requests session authorization and an ID 514 from content access point 500. If the authentication is valid, as determined by the content access point, the session ID is passed back to the client application 514.

[0809] Now that we have this session ID, the client application can perform any or all permitted operations. This may include, but is not limited to, browsing content on a content access point or web server (if available), purchasing or acquiring content on a content access point or web service (if available), or other functions. However, a primary function is requesting content 515 and receiving data 503. The client application will also publish (upload) analytics data 516 to the content access point analytics storage 504. Analytics data is all analytics captured since the last client connection to the content access point or web service.

[0810] When the transaction, content download, and analysis data transfer are complete, the client application terminates the session and disconnects from the content access point 517. The application then reconnects to the previously existing network connection 518, if any.

[0811] Figure 6 This is a block diagram of one embodiment of a client device. Examples of common client devices include, but are not limited to, laptops, smartphones, and tablets. Note that the basic hardware components are... Figure 6 The client device, shown in the diagram, includes other components and features not shown to avoid obscuring the invention. A Wi-Fi network connection 601 connects to a Wi-Fi network to enable wireless connectivity to a content access point. Input 602 includes a user input device that enables user control. A display 603 is used to display content. A speaker 604 is used to provide audio content. Content storage 610 is typically non-volatile memory, such as flash memory or magnetic storage, and is used to store downloaded content. A CPU 611 controls components of the client device, including those running client applications, and random access memory (RAM) 612 is memory used to run client applications.

[0812] Figure 7 This is a block diagram of one embodiment of a content access point. For example, a readily available Wi-Fi access point connects to a computer with a large amount of content storage. Note that the basic hardware components are... Figure 7 As shown, and the content access points include other components and features not shown, to avoid obscuring the invention. (See reference...) Figure 7 Wi-Fi network 701 is used to connect to client devices. Recharge connection 702 is used to exchange content and upload it for any client device analysis. In one embodiment, recharge connection 702 is a wired or wireless connection to a server or the Internet. In one embodiment, recharge connection 702 is a wired or wireless connection to a mobile device with content in its memory. In one embodiment, recharge connection 702 is a physical unit (e.g., a disk or flash memory) that is exchanged to perform recharge functionality.

[0813] Content memory 710 is typically non-volatile memory, such as, but not limited to, flash memory or magnetic memory, and is used to store content. CPU 711 runs content access point software and controls content access points. RAM 712 is used by CPU 711 to run content access point software.

Claims

1. A content delivery platform, comprising: One or more client devices, each of the one or more client devices having memory for storing an application and one or more processors for executing the application, wherein at least one of the one or more client devices uses a first network connection to connect to a network device; as well as A first access point, having a service set identifier and a physical local content cache associated with the service set identifier for storing content to be directly provided to the one or more client devices, wherein, in response to the execution of the application via the one or more processors, at least one of the one or more client devices is operable to: The first network connection in the automatic storage memory; In response to the storage, the service set identifier of the first access point is automatically searched; The service set identifier of the first access point is automatically detected based on the search. In response to the detection of the service set identifier, password information is automatically connected and sent to the first access point; Request content from the first access point based on the service set identifier and the password information; Receive the content from the first access point; as well as After receiving the content from the first access point, disconnect from the first access point and reconnect to the network device using the first network connection.

2. The content delivery platform according to claim 1, wherein, The first access point delivers the content without a network connection between the first access point and the remote source of the content.

3. The content delivery platform according to claim 1, wherein, The first access point is configured to receive the content from a swappable memory device switched to the first access point, and when the swappable memory device is connected to the first access point, analysis data obtained from at least one of the one or more client devices is stored in the swappable memory device.

4. The content delivery platform according to claim 1, wherein, The content is delivered to the first access point via a network connection to the mobile content recharge device, and analytics data from at least one of the one or more client devices is transmitted to the mobile content recharge device.

5. The content delivery platform according to claim 1, wherein, The content is delivered to the first access point via an Internet connection, and analytics data from at least one of the one or more client devices is transmitted from the first access point to a remote location via the Internet connection.

6. The content delivery platform according to claim 5, wherein, The delivery of the content to the first access point and the transmission of the analytical data from the first access point occur during periods of off-peak bandwidth demand.

7. The content delivery platform according to claim 1, wherein, The first access point can be operated to authenticate at least one of the one or more client devices without internet access and intermediaries, and the one or more client devices can be operated to browse, request, and deliver the content from the first access point without internet cloud authentication.

8. The content delivery platform according to claim 1, wherein, The first access point is configured to automatically upload transaction and analytics data from each of the one or more client devices when connected to them, and wherein the first access point is configured to upload the transaction and analytics data to a remote location via the content delivery method of the first access point.

9. The content delivery platform according to claim 1, wherein, At least one of the one or more client devices is operable to upload analytics data to the first access point, and the first access point is configured to transmit the analytics data to a remote location.

10. A method for content delivery, comprising: The application is executed using one or more processors through each of one or more client devices, wherein at least one of the one or more client devices uses a first network connection to connect to a network device; The first network connection is automatically stored in memory via at least one of the one or more client devices; In response to the storage, a service set identifier for a first access point is automatically searched via at least one of the one or more client devices. The first access point has a physical local content cache associated with the service set identifier for storing content to be directly provided to the one or more client devices. Based on the search, the service set identifier of the first access point is automatically detected through at least one of the one or more client devices. In response to detecting the service set identifier, the password information is automatically connected and sent to the first access point via at least one of the one or more client devices. Based on the service set identifier and password information, content is requested from the first access point through at least one of the one or more client devices. The content is received from the first access point via at least one of the one or more client devices; as well as After receiving the content from the first access point, the connection with the first access point is disconnected through at least one of the one or more client devices, and the connection with the network device is reconnected through at least one of the one or more client devices using the first network connection.

11. The method of claim 10, further comprising: In the absence of a network connection between the first access point and the remote source of the content, the content is delivered to at least one of the one or more client devices via the first access point.

12. The method of claim 11, further comprising: Before delivering the content to at least one of the one or more client devices, the first access point receives the content from a swappable memory device switched to the first access point, and when the swappable memory device is connected to the first access point, the analysis data obtained from the at least one of the one or more client devices is transmitted to the swappable memory device.

13. The method according to claim 11, wherein, The content is delivered to the first access point via a network connection to the mobile content recharge device, and analytics data from at least one of the one or more client devices is transmitted to the mobile content recharge device.

14. The method of claim 10, wherein, The content is delivered to the first access point via an Internet connection, and analytics data from at least one of the one or more client devices is transmitted from the first access point to a remote location via the Internet connection.

15. The method according to claim 14, wherein, The delivery of the content to the first access point and the transmission of the analytical data from the first access point occur during periods of off-peak bandwidth demand.

16. The method of claim 10, further comprising: In the absence of internet access and intermediaries, the one or more client devices are authenticated through the first access point; as well as The at least one client device browses, requests, and delivers the content from the first access point without Internet cloud authentication.

17. The method of claim 10, further comprising: When connecting to each of the one or more client devices, transaction and analysis data are automatically uploaded from the one or more client devices through the first access point; as well as The content delivery method of the first access point uploads transaction and analysis data to a remote location through the first access point.

18. The method of claim 10, further comprising: The analysis data is uploaded to the first access point through at least one of the one or more client devices; as well as The analytical data is transmitted to a remote location via the first access point.

19. One or more non-transitory computer-readable storage media, wherein instructions are stored on the non-transitory computer-readable storage media, the instructions, when executed by a system having at least a processor and a memory, causing the system to perform a content delivery operation, the content delivery operation comprising: The application is executed using one or more processors through each of one or more client devices, wherein at least one of the one or more client devices uses a first network connection to connect to a network device; The first network connection is automatically stored in memory via at least one of the one or more client devices; In response to the storage, a service set identifier for a first access point is automatically searched via at least one of the one or more client devices. The first access point has a physical local content cache associated with the service set identifier for storing content to be directly provided to the one or more client devices. Based on the search, the service set identifier of the first access point is automatically detected through at least one of the one or more client devices. In response to detecting the service set identifier, the password information is automatically connected and sent to the first access point via at least one of the one or more client devices. Based on the service set identifier and the password information, content is requested from the first access point through at least one of the one or more client devices. The content is received from the first access point via at least one of the one or more client devices; as well as After receiving the content from the first access point, the connection with the first access point is disconnected through at least one of the one or more client devices, and the connection is reconnected to the network device using the first network connection through at least one of the one or more client devices.

20. The storage medium according to claim 19, wherein, The operation further includes: in the absence of a network connection between the first access point and the remote source of the content, delivering the content to at least one of the one or more client devices through the first access point.

Images