Television fast application management and distribution method and device based on central warehouse, computer equipment and readable storage medium

Abstract

The invention discloses a television block application management and distribution method and device based on a central warehouse, computer equipment and a readable storage medium, and the method comprises the steps: firstly obtaining a login request, and logging in the central warehouse through Nginx; uploading the television block application to a central warehouse in response to an uploading instruction, and then uploading the television block application to the Nexus system; and obtaining an application obtaining request through Nginx, and after verification is passed, obtaining the television fast application from the Nexus system by means of a CDN (Content Delivery Network). According to the method, the management process is optimized, the distribution efficiency is improved, and timely acquisition and updating of the application are guaranteed.

Description

Technical Field

[0001] The present invention relates to the field of television quick application management, and in particular to a method, device, computer equipment and readable storage medium for managing and distributing television quick applications based on a central warehouse. Background Art

[0002] With the popularity of smart TVs, the number and types of TV quick apps are increasing. However, there are many problems with traditional TV quick app management and distribution methods, such as complex permission management, difficult version control, and low storage and distribution efficiency. These problems lead to poor experience for developers and users, and also increase management and maintenance costs. Therefore, an efficient, convenient and reliable TV quick app management and distribution method is needed. Summary of the invention

[0003] The object of the present invention is to provide a method, device, computer equipment and readable storage medium for managing and distributing TV quick applications based on a central warehouse.

[0004] In a first aspect, an embodiment of the present invention provides a TV quick application management and distribution method based on a central warehouse, including:

[0005] Get the login request and log in to the central warehouse through Nginx;

[0006] In response to the TV quick application upload instruction, uploading the TV quick application to the central warehouse;

[0007] Uploading the TV quick application to the Nexus system through the central warehouse;

[0008] An application acquisition request is obtained through the Nginx, and when the application acquisition request passes the verification, the TV quick application is obtained from the Nexus system through the CDN.

[0009] In a possible implementation, the application acquisition request is verified in the following manner, including:

[0010] Determining whether the application acquisition request includes a source field defined by a preset protocol;

[0011] If the source field defined by the preset protocol is included, the verification is passed;

[0012] If the source field defined by the preset protocol is not included, the verification fails and an error is reported.

[0013] In a possible implementation, obtaining the application acquisition request through the Nginx includes:

[0014] The application acquisition request is obtained based on Nginx configured with load balancing.

[0015] In a possible implementation, obtaining the TV quick app from the Nexus system through the CDN includes:

[0016] In the case where the TV quick application fails to be obtained from the Nexus system, the TV quick application is obtained by redirecting through the CDN.

[0017] In one possible implementation, the method includes:

[0018] Acquire a third-party warehouse and form an upstream and downstream relationship between the third-party warehouse and the central warehouse;

[0019] Based on the upstream and downstream relationship, the third-party warehouse is used as a proxy warehouse of the central warehouse to execute the step of responding to the TV quick application upload instruction, uploading the TV quick application to the central warehouse, and then uploading the TV quick application to the Nexus system through the central warehouse.

[0020] In a possible implementation, the method further includes:

[0021] When resources in the Nexus system are updated, the CDN is notified through an API to perform a cache update, or the CDN is used to actively check resource updates through a polling mechanism.

[0022] In a possible implementation, the method further includes:

[0023] The latest application resources are synchronized from the Nexus system to the CDN regularly to ensure that the CDN cache content is up to date.

[0024] In a second aspect, an embodiment of the present invention provides a TV quick application management and distribution device based on a central warehouse, including:

[0025] A management module, configured to obtain a login request, log in to the central warehouse through Nginx; upload the TV quick application to the central warehouse in response to a TV quick application upload instruction; and upload the TV quick application to the Nexus system through the central warehouse;

[0026] The distribution module is used to obtain the application acquisition request through the Nginx, and when the application acquisition request passes the verification, obtain the TV quick application from the Nexus system through the CDN.

[0027] In a third aspect, an embodiment of the present invention provides a computer device, comprising a processor and a non-volatile memory storing computer instructions, wherein when the computer instructions are executed by the processor, the computer device executes the method described in at least one possible implementation of the first aspect.

[0028] In a fourth aspect, an embodiment of the present invention provides a readable storage medium, wherein the readable storage medium includes a computer program, and when the computer program is run, the computer device where the readable storage medium is located is controlled to execute the method described in at least one possible implementation manner of the first aspect.

[0029] Compared with the prior art, the beneficial effects provided by the present invention include: adopting the TV quick application management and distribution method, device, computer equipment and readable storage medium based on the central warehouse disclosed by the present invention, by obtaining the login request, logging into the central warehouse through Nginx; responding to the upload instruction to upload the TV quick application to the central warehouse, and then uploading it to the Nexus system; obtaining the application acquisition request through Nginx, and after verification, obtaining the TV quick application from the Nexus system with the help of CDN. This method optimizes the management process, improves the distribution efficiency, and ensures the timely acquisition and update of the application. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only illustrate certain embodiments of the present invention and should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can also be obtained based on these drawings without creative work.

[0031] Figure 1 A schematic flow chart of the steps of a method for managing and distributing TV quick applications based on a central warehouse provided in an embodiment of the present invention;

[0032] Figure 2 A schematic block diagram of the structure of a TV quick application management and distribution device provided by an embodiment of the present invention;

[0033] Figure 3 A schematic block diagram of the structure of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0035] The specific implementation modes of the present invention are described in detail below in conjunction with the accompanying drawings.

[0036] In order to solve the technical problems in the aforementioned background technology, Figure 1 This is a flow chart of a TV quick application management and distribution method based on a central warehouse provided in an embodiment of the present disclosure. The TV quick application management and distribution method based on a central warehouse is introduced in detail below.

[0037] Step S201, obtain a login request and log in to the central warehouse through Nginx;

[0038] Step S202, in response to the TV quick app upload instruction, uploading the TV quick app to the central warehouse;

[0039] Step S203, uploading the TV quick app to the Nexus system through the central warehouse;

[0040] Step S204: obtaining an application acquisition request through the Nginx, and obtaining the TV quick application from the Nexus system through the CDN when the application acquisition request passes the verification.

[0041] In the embodiment of the present invention, for example, it is assumed that the server is deployed in a large data center and is responsible for handling the management and distribution of TV quick applications. On a certain weekday morning, a developer wants to upload a new TV quick application to the central warehouse. He enters his user name and password on his development terminal and clicks the login button. This login request is sent to the server.

[0042] After the server receives the login request, it is first processed by the Nginx server. As a high-performance reverse proxy server, Nginx quickly receives the request and performs preliminary parsing and verification. It checks whether the login information in the request conforms to the preset format and rules.

[0043] If the login information is valid, Nginx forwards the request to the login interface of the central warehouse. After receiving the request, the central warehouse will look up the corresponding user information in its database and verify whether the username and password match.

[0044] Assume that the developer's username is "developer001" and the password is "pass1234". The central warehouse finds the user "developer001" in its user database and verifies that the password "pass1234" is correct. Therefore, the login is successful and the developer obtains the permission to upload the TV quick app.

[0045] After successfully logging in, the developer selected the TV quick app file to be uploaded on his development terminal and clicked the upload button to issue an upload instruction.

[0046] After receiving the upload instruction, the server starts preparing to receive the uploaded file. The central warehouse assigns a unique identifier and storage space to each uploaded quick app.

[0047] Assume that the TV quick app that the developer wants to upload is an app called "TVGameApp" with a size of 50MB. The developer's network connection is stable and the upload speed is 5MB / s. The server continuously receives the uploaded file and monitors the upload progress in real time.

[0048] During the upload process, the server will perform integrity checks on the uploaded data, such as calculating the hash value of the file, to ensure that the uploaded file is not damaged or lost during the transmission process. If the data is found to be incomplete or damaged, the server will send an error message to the developer and ask him to re-upload.

[0049] After 10 seconds of uploading, the TV quick app "TVGameApp" was successfully uploaded to the central warehouse. The central warehouse records the relevant information of this app, such as name, version, size, upload time, etc., into the database for subsequent management and query.

[0050] After the TV quick app is successfully uploaded to the central warehouse, the central warehouse will automatically trigger the process of uploading it to the Nexus system.

[0051] First, the central warehouse establishes a connection with the Nexus system. This connection is achieved through a pre-configured network protocol and authorization mechanism to ensure the security and stability of data transmission.

[0052] Then, the central repository packages the "TVGameApp" files and related metadata (such as application description, developer information, etc.) into a format that meets the requirements of the Nexus system.

[0053] Assume that the Nexus system assigns a storage path " / tvapps / TVGameApp / version1.0" to this TV quick app. The central warehouse sends the packaged data to the storage path specified by the Nexus system through the network.

[0054] During the data transmission process, the server will continuously monitor the progress and status of the transmission. If there is a network interruption or transmission error, the server will automatically try to retransmit until the data is successfully uploaded to the Nexus system.

[0055] After a period of data transmission, the "TVGameApp" TV quick application was successfully uploaded to the Nexus system, and relevant records were updated in the Nexus system database, including the application's storage location, version information, etc.

[0056] At some point, a user turns on his smart TV and wants to download and install a new TV quick app. The TV sends an application acquisition request to the server.

[0057] This request first arrives at the Nginx server. Nginx quickly receives the request, parses it, and performs preliminary processing.

[0058] Assume that this application acquisition request is a request to obtain the TV Game App TV quick application. Nginx will check some key information in the request, such as the source of the request, the identity of the user, etc., for verification.

[0059] The verification method is to determine whether the request includes the source field defined by the preset protocol. If the request contains the correct source field, such as from a legitimate TV manufacturer or an authorized app store, the request passes the verification.

[0060] Assuming that the request contains the correct source field, indicating that it is from a legitimate TV manufacturer, Nginx forwards the request to the server's processing logic.

[0061] After receiving the request, the server will send an instruction to CDN to obtain the "TVGameApp" TV quick application.

[0062] The CDN will first check whether there is already a copy of the application in its cache. If so, it will directly return the application in the cache to the user.

[0063] Assuming that there is no "TVGameApp" TV quick app in the CDN cache, the CDN will send a request to the Nexus system to obtain the app.

[0064] After receiving the request, the Nexus system finds the "TVGameApp" TV quick app from its storage and returns it to the CDN.

[0065] After receiving the application, CDN forwards it to the user's smart TV. After the user's TV receives the application, it starts downloading and installing it, and the user can quickly use this new TV quick application.

[0066] Assume that the Nexus system is temporarily unavailable during the process of acquiring the application. The CDN will handle it according to the preset strategy, such as waiting for a period of time and then trying again, or returning a message to the server indicating that the acquisition failed. The server can take further measures based on the situation, such as checking the status of the Nexus system, acquiring the application from the backup, etc., to ensure that the user can obtain the required TV quick application as soon as possible.

[0067] Through the above more detailed and in-depth scenario examples, we can have a more comprehensive understanding of the various situations and processing methods of the TV quick application management and distribution method based on the central warehouse in actual operation, so as to better ensure the stability, reliability and efficiency of the system.

[0068] In the embodiment of the present invention, the application acquisition request is verified in the following manner, which can be implemented through the following example.

[0069] Determining whether the application acquisition request includes a source field defined by a preset protocol;

[0070] If the source field defined by the preset protocol is included, the verification is passed;

[0071] If the source field defined by the preset protocol is not included, the verification fails and an error is reported.

[0072] In the embodiment of the present invention, illustratively, in daily business operation, the server is continuously in a standby state, ready to process application acquisition requests from various parties.

[0073] At noon one day, the server received an application acquisition request from a smart TV terminal. The server first started the verification program and began to check whether the request contained the source field defined by the preset protocol.

[0074] The source field defined by the predefined protocol may include details such as the platform identifier of the origin of the request, the user's unique identifier, the model and serial number of the device, etc.

[0075] In this specific example, the request received by the server clearly contains the source platform identifier "SmartTVPlatformA", the user's unique identifier "User12345", and the device model "ModelX" and serial number "SerialNumberABC". The server compares the received information with the preset rules and legal values ​​in the database.

[0076] After comparison, the server confirms that the information of these source fields is complete and conforms to the preset legal format and range. This means that this application acquisition request contains the source fields defined by the preset protocol and the verification is passed.

[0077] The server then allows the subsequent process to continue and prepares to obtain the requested TV quick application from the Nexus system through the CDN.

[0078] In another scenario, on a weekend night, the server received another application acquisition request. However, in this request, after careful inspection and parsing, the server found that the key source fields defined by the preset protocol, such as the user's unique identifier, were missing.

[0079] Due to the lack of this important source field information, the server determines that the request does not meet the preset verification conditions. According to the established rules, the server immediately returns an error message to the terminal that issued the request. The error message may clearly state that "the request lacks the necessary user unique identifier and cannot pass the verification."

[0080] This way, end users will receive an error message and understand that their request cannot be processed because it does not meet the requirements.

[0081] For example, once the server received a request that contained a source field, but the source platform identifier was not a legitimate platform identifier preset by the server. In this case, the server also determined that the request failed verification and returned an error message to the requester, informing him that "the request source platform was not authorized and could not be processed."

[0082] Through such a strict and precise verification method, the server can effectively screen and process legitimate application acquisition requests, ensuring the security and standardization of TV quick application management and distribution. In the process of continuously processing various requests, the server continues to accumulate experience and data, continuously optimizes the verification process and improves processing efficiency to provide more stable and reliable services.

[0083] In the embodiment of the present invention, the obtaining of the application acquisition request through the Nginx can be implemented through the following example.

[0084] The application acquisition request is obtained based on Nginx configured with load balancing.

[0085] In the embodiment of the present invention, the following is an example of a server being the execution subject. During a busy TV quick application usage peak period, the data center where the server is located is facing a large number of application acquisition requests. At this time, Nginx configured with load balancing plays a key role.

[0086] Nginx is carefully configured as a front-end proxy for multiple server instances, which together form a processing cluster for application requests. For example, there are five servers Server1, Server2, Server3, Server4, and Server5 working together.

[0087] When the first application acquisition request is sent from the user's smart TV terminal, Nginx makes a judgment based on its load balancing algorithm. Assuming that the load of Server1 is low at this time, Nginx forwards this request to Server1. After receiving the request, Server1 starts to process the relevant business logic.

[0088] Soon after, a large number of requests came in. When the second request arrived at Nginx, it detected that the current load of Server2 was relatively light, so it routed the request to Server2 for processing.

[0089] As time goes by, the number of requests continues to increase. Nginx continues to intelligently distribute requests based on the real-time load of each server. For example, the third request is distributed to Server3, and the fourth request is distributed to Server4.

[0090] At a certain moment, Server1 has finished processing the current requests and its load has returned to a lower level. When a new batch of requests arrives, Nginx will assign some of the requests to Server1 again to make full use of its processing capacity.

[0091] Assume that during this process, Server5 has some temporary performance issues, such as excessive memory usage or increased network latency. Nginx can monitor this situation in real time and temporarily reduce the number of requests assigned to Server5, or even suspend assigning new requests to it in extreme cases to avoid affecting the overall service quality.

[0092] At the same time, Nginx will also identify and classify the type and priority of the request. For some urgent or high-priority application acquisition requests, such as users are acquiring real-time game applications, Nginx will prioritize assigning them to servers with lighter loads and stronger processing capabilities to ensure that these critical requests can be responded to quickly.

[0093] For example, users in a certain area send a large number of application acquisition requests. Due to network topology, these requests are assigned to data center servers close to the area for processing, which can reduce data transmission delays and improve response speed. Nginx will intelligently select the most appropriate server to process these requests from a specific area based on the user's IP address and network path information.

[0094] By obtaining application requests based on Nginx configured with load balancing, the server can efficiently respond to large-scale concurrent requests, ensuring that each request is processed promptly and accurately, providing users with a smooth and stable TV quick application acquisition experience.

[0095] During the continuous operation process, the server and Nginx continuously collect performance data and user behavior data to further optimize the load balancing strategy to adapt to the changing business needs and user usage patterns.

[0096] In the embodiment of the present invention, the obtaining of the TV quick application from the Nexus system through the CDN may be implemented through the following example.

[0097] In the case where the TV quick application fails to be obtained from the Nexus system, the TV quick application is obtained by redirecting through the CDN.

[0098] In the embodiment of the present invention, the server is exemplarily processing TV quick application acquisition requests from various terminals continuously. At this time, a user initiates a request to acquire a popular TV game quick application.

[0099] After receiving the request, the server immediately instructs the CDN to obtain the TV quick app from the Nexus system. The CDN first attempts to directly connect to the Nexus system to obtain the required application.

[0100] However, because the Nexus system was facing a sudden network failure at this time, or there was a temporary access restriction on the storage area where the application was located, the CDN's first attempt to obtain the TV quick application from the Nexus system failed.

[0101] In this case, CDN starts the response strategy according to the preset redirection mechanism. It checks its own cache node distribution information and looks for other nodes that may have copies of the TV quick app.

[0102] Suppose the CDN finds that the latest copy of the application is stored in a cache node of a data center in another region. The CDN immediately redirects the request to the cache node that has the copy.

[0103] During the redirection process, CDN will quickly update the requested routing path and related network parameters to ensure that data can be accurately obtained from the new node.

[0104] At the same time, CDN will also monitor and optimize the redirection process in real time. For example, it will dynamically adjust the data transmission rate and data packet size according to network congestion to ensure the efficiency and stability of the acquisition process.

[0105] When the TV quick app fails to be obtained from the Nexus system, the CDN finds that there is no copy of the app in all its cache nodes. At this time, the CDN will send a failed acquisition notification to the server.

[0106] After receiving the notification, the server will take further measures. It may communicate with the administrator of the Nexus system to understand the cause of the failure and the estimated recovery time, and feedback the relevant information to the user.

[0107] At the same time, the server will instruct the CDN to continuously monitor the status of the Nexus system, and once the Nexus system returns to normal, immediately try to obtain the TV quick app again.

[0108] In another case, when the acquisition fails and redirection is performed, although the new cache node has a copy of the application, the version is not the latest. CDN will first return this old version of the application to the user to meet the user's urgent needs. At the same time, the background will continue to obtain the latest version from the Nexus system and prompt the user to update after the acquisition is successful.

[0109] Through such a redirection mechanism, the server and CDN can effectively deal with the failure of obtaining TV quick applications from the Nexus system, minimize the impact on user experience, and ensure that users can obtain the TV quick applications they need as soon as possible.

[0110] In the embodiments of the present invention, the following implementation modes are also provided.

[0111] Acquire a third-party warehouse and form an upstream and downstream relationship between the third-party warehouse and the central warehouse;

[0112] Based on the upstream and downstream relationship, the third-party warehouse is used as a proxy warehouse of the central warehouse to execute the step of responding to the TV quick application upload instruction, uploading the TV quick application to the central warehouse, and then uploading the TV quick application to the Nexus system through the central warehouse.

[0113] In the embodiment of the present invention, illustratively, in the management and distribution system of the TV quick application, the server actively cooperates with the outside to expand the integration and utilization of resources.

[0114] The server received a cooperation intention from a well-known technology company, hoping to incorporate its third-party warehouse into the existing management and distribution process. The server immediately started the relevant docking procedures.

[0115] First, the server establishes a communication connection with the third-party warehouse and begins to obtain its detailed warehouse information, including the types, versions, and quantities of stored TV quick applications, as well as its existing management rules and permission settings.

[0116] After a series of data exchanges and verifications, the server successfully obtained the complete information of the third-party warehouse and analyzed and evaluated it.

[0117] Based on the evaluation results, the server determines the upstream and downstream relationship with the third-party warehouse. For example, some specific types of TV quick applications in the third-party warehouse, such as educational applications, complement the related applications in the central warehouse. Some basic functional applications in the central warehouse can provide support for advanced applications in the third-party warehouse, while professional educational applications in the third-party warehouse enrich the entire application ecosystem.

[0118] After establishing this upstream and downstream relationship, the server configures the third-party warehouse as a proxy warehouse for the central warehouse.

[0119] Subsequently, when a new TV quick app needs to be uploaded, the upload instruction first reaches the central warehouse. Since the third-party warehouse, as a proxy warehouse, has established a close connection with the central warehouse, the server will determine whether the application needs to be uploaded to the third-party warehouse for some preprocessing or verification based on the established rules and priorities.

[0120] Suppose a new children's educational TV quick app "Smart Baby" needs to be uploaded. The server first uploads it to the third-party warehouse according to the previously set rules. The specific verification program in the third-party warehouse conducts a preliminary test on the application for children's user experience and the accuracy of educational content. After the test passes, the server uploads it from the third-party warehouse to the central warehouse.

[0121] During the upload process to the central warehouse, the server follows strict security and quality control processes to ensure the integrity and availability of the application.

[0122] Then, the central warehouse uploads the "Smart Baby" TV quick app to the Nexus system for storage and distribution preparation according to the normal process.

[0123] For example, another third-party warehouse mainly stores some regional TV quick apps. When the server receives a request from a user in a specific region, it will first search and obtain the app from the third-party warehouse as a proxy warehouse. If the third-party warehouse does not have the app, it will be obtained from the central warehouse and Nexus system according to the normal process.

[0124] In this way, the server successfully integrated the resources of third-party warehouses to form a richer and more flexible TV quick application management and distribution system, providing users with more diverse and personalized application choices.

[0125] In the embodiment of the present invention, the embodiment of the present invention also provides the following implementation manner.

[0126] When resources in the Nexus system are updated, the CDN is notified through an API to perform a cache update, or the CDN is used to actively check resource updates through a polling mechanism.

[0127] In the embodiment of the present invention, illustratively, during the continuous operation of the TV quick application, the server always pays attention to the resource changes in the Nexus system.

[0128] The development team optimized and fixed important functions of a popular TV shopping app and uploaded the updated version to the Nexus system. The Nexus system detected the resource update and immediately triggered API communication with the server.

[0129] The server receives the resource update notification sent by the Nexus system through a pre-configured API. The notification contains the updated application name, version number, and related metadata information.

[0130] After receiving the notification, the server quickly parses the notification content and determines that the cache in the CDN needs to be updated. It immediately sends a clear instruction to the CDN, informing the CDN that the resources of the specific TV shopping quick application have been updated and the cache needs to be updated.

[0131] After receiving the server's instructions, CDN immediately suspends the distribution service for the old version of the application and obtains the latest resources from the Nexus system to update the local cache.

[0132] In another case, the server is configured with a polling mechanism of the CDN. For example, every hour the CDN will proactively ask the server for updates to the resources in the Nexus system.

[0133] When the scheduled polling time arrives, the CDN sends a polling request to the server. After receiving the request, the server checks the resource update records in the Nexus system since the last polling.

[0134] Assume that during this period, several TV quick apps have undergone minor version optimization and content updates. The server will sort out the updated application information and return it to the CDN.

[0135] Based on the update information returned by the server, CDN obtains the latest resources from the Nexus system and updates the local cache.

[0136] A TV video playback app has undergone a large-scale interface revision and video decoding optimization. After the Nexus system updates the resources, it notifies the server through the API. However, due to a brief network fluctuation, the server failed to receive the notification in time.

[0137] The CDN initiated the query on time according to the polling mechanism. When the server processed the polling request, it found the previously missed notification and notified the CDN of the update information of the video playback quick app, ensuring that the CDN could update the cache in time and provide users with the latest high-quality experience.

[0138] Through such timely and effective resource update notification and polling mechanism, the server can ensure that the cache in the CDN is always kept up to date, and users can get the best usage effect every time they obtain the TV quick application.

[0139] In the embodiment of the present invention, the embodiment of the present invention also provides the following implementation manner.

[0140] The latest application resources are synchronized from the Nexus system to the CDN regularly to ensure that the CDN cache content is up to date.

[0141] In the embodiment of the present invention, exemplarily, during the stable operation of the TV quick application, the server is responsible for the important task of regularly synchronizing resources to ensure the latest status of the CDN cache content.

[0142] For example, the server is set to perform synchronization of application resources at 3 a.m. every day. When this time point arrives, the server starts the preset synchronization program.

[0143] First, the server establishes a secure and reliable connection with the Nexus system to obtain a list of application resources, including detailed information such as the application name, version number, and update time.

[0144] The server will compare the obtained list with the information recorded during the last synchronization. Suppose it is found that a sports live broadcast app called "TVSport" has a new version, and the version number has been upgraded from 2.0 to 2.1.

[0145] The server then sends a request to the Nexus system to obtain the complete resource data of the TVSport quick app version 2.1. The Nexus system responds to the request and transmits the relevant data to the server.

[0146] When receiving data, the server will perform real-time integrity checks to ensure that the data is not lost or damaged. If any abnormality is found, the server will ask the Nexus system to resend the corresponding data fragment.

[0147] After successfully obtaining the complete resources of version 2.1 of the "TVSport" quick app, the server starts pushing them to the CDN. After receiving the new resources, the CDN updates its local cache and replaces the old version of the "TVSport" quick app.

[0148] In addition, the server also found that the resources of a music player quick application called "TVMusic" had some minor updates, such as the addition of copyrights for several popular songs. Similarly, the server obtained these updated resources according to the process and pushed them to the CDN for cache update.

[0149] Not only that, for some TV quick apps that are used very frequently by users, such as the "TVNews" news information app, the server will pay special attention to their updates, and give priority to synchronization and push to ensure that users can get the latest news content in a timely manner.

[0150] Sometimes, network congestion may occur during the synchronization process, resulting in slower data transmission speed. The server will intelligently adjust the transmission strategy, such as reducing the concurrent amount of data transmission or selecting a better network path, to ensure that the synchronization operation can be completed smoothly.

[0151] After a series of synchronization operations, the server successfully updated the latest application resources in the Nexus system to the CDN cache. In this way, when users request to obtain these TV quick applications at any time of the day, the CDN can quickly provide the latest version of the service, greatly improving the user experience.

[0152] Through this regular synchronization mechanism, the server effectively maintains the freshness and accuracy of the CDN cache content, providing solid support for the efficient distribution and high-quality service of TV quick applications.

[0153] Please refer to Figure 2 , Figure 2 A TV quick application management and distribution device 110 based on a central warehouse provided in an embodiment of the present invention includes:

[0154] The management module 1101 is used to obtain a login request and log in to the central warehouse through Nginx; in response to a TV quick application upload instruction, upload the TV quick application to the central warehouse; and upload the TV quick application to the Nexus system through the central warehouse;

[0155] The distribution module 1102 is used to obtain the application acquisition request through the Nginx, and when the application acquisition request passes the verification, obtain the TV quick application from the Nexus system through the CDN.

[0156] It should be noted that the implementation principle of the aforementioned TV quick application management and distribution device 110 can refer to the implementation principle of the aforementioned TV quick application management and distribution method, which will not be repeated here. It should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the TV quick application management and distribution device 110 can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The functions of the above TV quick application management and distribution device 110. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by an integrated logic circuit of hardware in a processor element or instructions in software form.

[0157] For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASIC), or one or more microprocessors (digital signal processors, DSP), or one or more field programmable gate arrays (FPGA), etc. For another example, when a module above is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0158] The embodiment of the present invention provides a computer device 100, which includes a processor and a non-volatile memory storing computer instructions. When the computer instructions are executed by the processor, the computer device 100 executes the aforementioned TV quick application management and distribution device 110. Figure 3 As shown, Figure 3The computer device 100 provided in the embodiment of the present invention is a structural block diagram. The computer device 100 includes a TV quick application management and distribution device 110, a memory 111, a processor 112 and a communication unit 113.

[0159] To achieve data transmission or interaction, the memory 111, the processor 112, and the communication unit 113 are electrically connected to each other directly or indirectly. For example, these components can be electrically connected to each other through one or more communication buses or signal lines. The TV quick application management and distribution device 110 includes at least one software function module that can be stored in the memory 111 in the form of software or firmware or solidified in the operating system (OS) of the computer device 100. The processor 112 is used to execute the TV quick application management and distribution device 110 stored in the memory 111, such as the software function modules and computer programs included in the TV quick application management and distribution device 110.

[0160] An embodiment of the present invention provides a readable storage medium, the readable storage medium includes a computer program, and when the computer program is running, the computer device where the readable storage medium is located is controlled to execute the aforementioned TV quick application management and distribution method.

[0161] For illustrative purposes, the foregoing description is made with reference to specific embodiments. However, the above illustrative discussion is not intended to be exhaustive or to limit the present disclosure to the precise form disclosed. Numerous modifications and variations are possible in accordance with the above teachings. These embodiments are selected and described in order to best illustrate the principles of the present disclosure and its practical application, so that those skilled in the art can best utilize the present disclosure and utilize various embodiments with different modifications to suit the intended specific application.

Claims

1. A TV quick application management and distribution method based on a central warehouse, characterized in that: include: Get the login request and log in to the central warehouse through Nginx; In response to the TV quick application upload instruction, uploading the TV quick application to the central warehouse; Uploading the TV quick application to the Nexus system through the central warehouse; An application acquisition request is obtained through the Nginx, and when the application acquisition request passes the verification, the TV quick application is obtained from the Nexus system through the CDN.

2. The method according to claim 1, characterized in that The application acquisition request is verified by: Determining whether the application acquisition request includes a source field defined by a preset protocol; If the source field defined by the preset protocol is included, the verification is passed; If the source field defined by the preset protocol is not included, the verification fails and an error is reported.

3. The method according to claim 1, characterized in that: The obtaining of the application acquisition request through the Nginx comprises: The application acquisition request is obtained based on Nginx configured with load balancing.

4. The method according to claim 1, characterized in that The obtaining the TV quick application from the Nexus system through the CDN includes: In the case where the TV quick application fails to be obtained from the Nexus system, the TV quick application is obtained by redirecting through the CDN.

5. The method according to claim 1, characterized in that The method comprises: Acquire a third-party warehouse and form an upstream and downstream relationship between the third-party warehouse and the central warehouse; Based on the upstream and downstream relationship, the third-party warehouse is used as a proxy warehouse of the central warehouse to execute the step of responding to the TV quick application upload instruction, uploading the TV quick application to the central warehouse, and then uploading the TV quick application to the Nexus system through the central warehouse.

6. The method according to claim 1, characterized in that The method further comprises: When resources in the Nexus system are updated, the CDN is notified through an API to perform a cache update, or the CDN is used to actively check resource updates through a polling mechanism.

7. The method according to claim 1, characterized in that The method further comprises: The latest application resources are synchronized from the Nexus system to the CDN regularly to ensure that the CDN cache content is up to date.

8. A TV quick application management and distribution device based on a central warehouse, characterized in that: include: Management module, used to obtain login requests and log in to the central warehouse through Nginx; In response to a TV quick application upload instruction, uploading the TV quick application to a central warehouse; uploading the TV quick application to a Nexus system through the central warehouse; The distribution module is used to obtain the application acquisition request through the Nginx, and when the application acquisition request passes the verification, obtain the TV quick application from the Nexus system through the CDN.

9. A computer device, characterized in that: The computer device comprises a processor and a non-volatile memory storing computer instructions. When the computer instructions are executed by the processor, the computer device executes the method according to any one of claims 1 to 7.

10. A readable storage medium, characterized in that: The readable storage medium includes a computer program, and when the computer program is executed, the computer device where the readable storage medium is located is controlled to execute the method according to any one of claims 1 to 7.

Images