Video-on-demand service implementation method and device for low-code platform, and medium

Abstract

The invention discloses a video-on-demand service implementation method and device for a low-code platform and a medium, and relates to the technical field of low-code platforms. The method comprises the following steps: uploading a preset video file to a low-code platform based on an attachment uploading service of the low-code platform; preprocessing the video file to generate a plurality of HLS fragment files with preset frame rates; under the condition that video-on-demand needs to be carried out, trigger information is obtained, the corresponding to-be-played HLS fragment file is retrieved based on the trigger information, and a front-end browser is called to carry out video playing. According to the method, the video-on-demand service is integrated in the low-code platform, more employees and enterprises can be helped to better master the low-code platform technology, and the application development efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of low-code platforms, and in particular to a method, device and medium for implementing a video-on-demand service for a low-code platform. Background Art

[0002] In the current context of rapid technological development, low-code platforms are becoming increasingly important as a key force in promoting enterprise digital transformation and accelerating the software development process. With their efficient, flexible and user-friendly features, these platforms have significantly lowered the technical threshold for software development, allowing people with non-technical backgrounds to actively participate in application construction and optimization, greatly promoting the innovation vitality within the enterprise and the ability to respond quickly to market dynamics.

[0003] With the widespread popularization and in-depth application of low-code platform technology, the market demand for professionals with low-code skills has surged, further promoting the development of related education and training resources. However, although the original intention of the low-code platform is to simplify the development process, to fully explore and utilize the rich function set and efficient tool chain it provides, developers still need to have certain professional knowledge and practical experience.

[0004] In particular, as multimedia content increasingly becomes the core carrier of information dissemination in the digital age, how to efficiently integrate video-on-demand services in low-code platforms has become a technical bottleneck that needs to be broken through. The realization of this capability can not only enrich the application scenarios of low-code platforms, but also provide users with an intuitive and interactive learning and practice platform, which helps them to understand and master low-code development technology more deeply, thereby promoting technological progress and efficiency improvement in the entire industry. Summary of the invention

[0005] The embodiments of the present application provide a method, device and medium for implementing a video on demand service for a low-code platform, so as to solve the following technical problems: how to integrate the video on demand service in the low-code platform to help more practitioners and enterprises better master the low-code platform technology and improve application development efficiency.

[0006] In the first aspect, an embodiment of the present application provides a method for implementing a video on demand service for a low-code platform, characterized in that the method includes: uploading a preset video file to the low-code platform based on the attachment upload service of the low-code platform; preprocessing the video file to generate several HLS segment files with preset frame rates; when video on demand is required, obtaining trigger information to retrieve the corresponding HLS segment file to be played based on the trigger information, and calling the front-end browser to play the video.

[0007] In one implementation of the present application, before uploading a preset video file to the low-code platform based on the attachment upload service of the low-code platform, the method also includes: building an attachment upload service function of the low-code platform, specifically including: defining interface specifications for attachment upload; wherein the interface specifications include file type restrictions, file size restrictions, and upload progress feedback mechanisms; designing and implementing a user interface for the upload component to enable users to select files and perform upload operations; configuring the background service of the low-code platform to process video files based on preset processing rules; wherein the processing rules include at least video file storage logic and video file naming rules.

[0008] In one implementation of the present application, a preset video file is uploaded to the low-code platform based on the attachment upload service of the low-code platform, specifically including: receiving the uploaded video file through the user interface provided by the low-code platform; verifying the type and size of the video file according to preset rules; if the verification passes, starting the upload process, transferring the video file to the specified location on the server, and providing real-time feedback on the upload progress during the upload process.

[0009] In one implementation of the present application, the video file is preprocessed to generate several HLS segment files with preset frame rates, specifically including: using a video processing library to read the video file; converting the video file into HLS format according to the preset frame rate, and cutting it into HLS segment files of corresponding clarity levels; generating a corresponding playlist file for each HLS segment file with a preset frame rate.

[0010] In one implementation of the present application, after preprocessing the video file to generate several HLS segment files with preset frame rates, the method also includes: storing the HLS segment files and their corresponding playlist files in the media resource library of the low-code platform, and establishing an index for subsequent retrieval; updating the database of the low-code platform to record the metadata information of the video file; wherein the metadata information includes the video title, description, upload time, and processed versions with different frame rates.

[0011] In one implementation of the present application, obtaining trigger information specifically includes: monitoring a video playback request initiated by a user interface; parsing parameters in the video request; wherein the parameter package includes at least a unique identifier of the video, a requested video quality level, and any possible user authentication information; and determining that the parameter is trigger information.

[0012] In one implementation of the present application, the corresponding HLS segment file to be played is retrieved based on the trigger information, specifically including: querying the corresponding metadata information in the database of the low-code platform according to the unique identifier in the trigger information; based on the video quality level requested by the user, retrieving the storage path or URL of the HLS segment file of the corresponding frame rate from the database.

[0013] In one implementation of the present application, calling a front-end browser to play a video specifically includes: based on an HLS video player pre-installed in the front-end browser, loading and playing the HLS segment file to be played.

[0014] In the second aspect, an embodiment of the present application also provides a video on demand service implementation device for a low-code platform, characterized in that the device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: upload preset video files to the low-code platform based on the attachment upload service of the low-code platform; pre-process the video files to generate several HLS segment files with preset frame rates; when video on demand is required, obtain trigger information to retrieve the corresponding HLS segment file to be played based on the trigger information, and call the front-end browser to play the video.

[0015] On the third aspect, the embodiment of the present application also provides a non-volatile computer storage medium for implementing a video on demand service of a low-code platform, storing computer executable instructions, characterized in that the computer executable instructions are configured to: upload a preset video file to the low-code platform based on the attachment upload service of the low-code platform; pre-process the video file to generate several HLS segment files with preset frame rates; when video on demand is required, obtain trigger information to retrieve the corresponding HLS segment file to be played based on the trigger information, and call the front-end browser to play the video.

[0016] The embodiments of the present application provide a method, device, and medium for implementing a video on demand service for a low-code platform, which have the following beneficial effects:

[0017] 1. By integrating video on demand services, the low-code platform is not limited to handling traditional business processes and data management, but also has powerful multimedia content management and playback capabilities. This greatly expands the application scenarios of the low-code platform and meets the needs of enterprises for video content management and distribution during the digital transformation process.

[0018] 2. Traditional video-on-demand systems are highly complex to develop, requiring professional developers and a lot of development time. However, this invention provides a set of implementation methods based on a low-code platform, allowing non-professional developers to easily build video-on-demand services, significantly lowering the development threshold and shortening the development cycle.

[0019] 3. Store the HLS segment files and their playlists in the media resource library of the low-code platform and create indexes to make the retrieval and management of video files more efficient. At the same time, by updating the database to record the metadata information of the video files, it facilitates subsequent video management and analysis.

[0020] 4. Users can customize the preset frame rate of video processing according to their needs and generate HLS segment files with various resolutions to meet the viewing needs of different user groups. At the same time, by monitoring the video playback request of the user interface, dynamically retrieving and distributing the corresponding video content, a flexible video distribution strategy is implemented.

[0021] 5. This application adopts modular design, making each part relatively independent and easy to replace or upgrade. For example, the video processing library can be replaced with a more efficient library as needed, and the HLS player can also be customized according to user needs. This design improves the scalability and maintainability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0023] Figure 1 A flow chart of a method for implementing a video on demand service for a low-code platform provided in an embodiment of the present application;

[0024] Figure 2 A schematic diagram of the internal structure of a device for implementing a video on demand service for a low-code platform provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0026] The embodiments of the present application provide a method, device and medium for implementing a video on demand service for a low-code platform, so as to solve the following technical problems: how to integrate the video on demand service in the low-code platform to help more practitioners and enterprises better master the low-code platform technology and improve application development efficiency.

[0027] The technical solution proposed in the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0028] Figure 1 A flowchart of a method for implementing a video on demand service for a low-code platform provided in an embodiment of the present application. Figure 1 As shown, the embodiment of the present application provides a method for implementing a video on demand service for a low-code platform, which specifically includes the following steps:

[0029] Step 101: Based on the attachment upload service of the low-code platform, upload the preset video file to the low-code platform.

[0030] In one embodiment of the present application, in order to implement a video on demand service for a low-code platform, it is first necessary to build an attachment upload service function of the low-code platform.

[0031] Specifically, define interface specifications for attachment uploading; wherein, the interface specifications include file type restrictions, file size restrictions, and upload progress feedback mechanism; design and implement the user interface of the upload component to enable users to select files and upload them; configure the background service of the low-code platform to process video files based on preset processing rules; wherein, the processing rules include at least video file storage logic and video file naming rules.

[0032] In one embodiment, to build the attachment upload service function of the low-code platform, it is first necessary to clarify the interface specifications for attachment upload to ensure the standardization and controllability of the upload process. The interface specifications specifically include the following aspects: (1) Clearly support the upload of video file formats, such as MP4, AVI, MOV, etc., and list them in detail in the interface document. This helps the front-end to filter the type when selecting files to reduce invalid uploads. At the same time, the back-end performs re-verification when receiving the file to ensure the security and compatibility of the file format. (2) According to the storage capacity and network bandwidth of the server, set a reasonable upper limit on the file size. For example, limit a single video file to no more than 2GB. Explain this limitation in the interface document, and provide clear prompt information on the front-end interface to help users understand and adjust the file size in advance. (3) Design a set of upload progress feedback APIs so that the front-end can obtain the upload progress in real time during the upload process and display it to the user in the form of a progress bar. This requires the back-end service to be able to record and respond to the amount of uploaded data during the upload process, and the front-end communicates with the back-end through polling or WebSocket to obtain the latest progress information.

[0033] Then, you need to design and implement the user interface of the upload component to ensure that users can complete file selection and upload operations intuitively and conveniently. The specific steps include: (1) Layout design: Use the UI design tools provided by the low-code platform to create a simple and clear upload interface. The interface should include elements such as file selection buttons, file information display area (displaying file name, size, type, etc.), upload progress bar, and upload button. (2) Interaction logic: Write the front-end logic to handle file browsing and selection operations after the user clicks the file selection button, and trigger the file upload request after the user clicks the upload button. At the same time, listen for upload progress events and update the progress bar display on the interface. (3) Error handling: Consider various error situations that may occur during the upload process (such as file type mismatch, file size, network problems, etc.), design corresponding error prompts and retry mechanisms to ensure that users can clearly understand the cause of the error and try to upload again.

[0034] Finally, the configuration of the backend service is the key to achieving effective processing and storage of video files. The specific steps include: (1) Video file storage logic: Select a suitable storage solution (such as local file system, cloud storage service, etc.) and design the storage path rules for video files. For example, you can create folders by year, month or date to store video files according to the rules. At the same time, ensure that the storage system has high availability and scalability. (2) Video file naming rules: Develop unified video file naming rules to facilitate file management and retrieval. The naming rules can include elements such as date and time stamps, unique identifiers (such as UUIDs), etc. to ensure the uniqueness and readability of the file name. (3) Processing rule implementation: Write the backend processing logic to process the uploaded video files according to the preset processing rules. This includes verifying the file type and size, calling the video processing library for transcoding and segmentation, storing the processed files and metadata, etc. Detailed logs should be recorded during the processing process to facilitate problem troubleshooting and performance optimization.

[0035] In one embodiment of the present application, after building the attachment upload service function of the low-code platform, the preset video file can be uploaded to the low-code platform based on the attachment upload service of the low-code platform.

[0036] Specifically, the uploaded video files are received through the user interface provided by the low-code platform; the type and size of the video files are verified according to preset rules; if the verification passes, the upload process is started, the video file is transferred to the specified location on the server, and the upload progress is fed back in real time during the upload process.

[0037] In one embodiment, when the user clicks the upload button on the interface or drags a file to the specified area, a file selection dialog box is triggered. After the user selects a video file from the local file system, the file name and preview image (if supported by the platform) will be displayed on the upload interface for the user to confirm. The system reads the file extension selected by the user and compares it with the preset supported video file format list. If the file type is not in the supported list, the interface will display an error message, prompting the user to select the correct video file format. The system obtains the file size and compares it with the preset file size limit. If the file exceeds the limit, an error message is also displayed on the interface, suggesting that the user reduce the file size or select a smaller video file. Once the file is verified, the system creates an upload task on the backend and generates a unique upload identifier (such as a UUID) associated with the task. This identifier will be used for subsequent file tracking and error handling. The system configures the necessary upload parameters, such as the URL of the target server, authentication information (if necessary), file metadata, etc. At the same time, the upload progress tracking mechanism is initialized to prepare to receive progress updates during the upload process. In order to improve the stability and efficiency of the upload, the system can adopt a fragmented upload technology. Split large files into multiple small pieces and upload them to the server in parallel. After each segment is successfully uploaded, the server will return a confirmation message. During the upload process, the system continuously calculates the ratio of the uploaded data to the total data volume to obtain the upload progress percentage. The calculated upload progress is fed back to the user interface in real time, usually in the form of a progress bar. The progress bar should include information such as the current upload speed and the estimated remaining time to improve the user experience.

[0038] Step 102: pre-process the video file to generate several HLS segment files with preset frame rates.

[0039] In one embodiment of the present application, after uploading a preset video file to a low-code platform, the video file is preprocessed to generate several HLS segment files with preset frame rates.

[0040] Specifically, a video processing library is used to read video files; the video files are converted into HLS format according to a preset frame rate, and are cut into HLS segment files of corresponding clarity levels; and a corresponding playlist file is generated for each HLS segment file of the preset frame rate.

[0041] In one embodiment, first, according to the compatibility, performance requirements and community support of the system, a suitable video processing library is selected, such as FFmpeg, OpenCV combined with FFmpeg's encapsulation library (such as FFmpegFrameGrabber in javacv), etc. The selected video processing library is used to initialize the video processing environment, including loading necessary codecs, filters and other components to ensure that the uploaded video files can be read and processed smoothly. Then, a preset frame rate list is read from the system configuration or database, which represents different video clarity levels, such as 30fps, 60fps, etc. For each preset frame rate, the corresponding transcoding parameters are set. This includes video codecs (such as H.264), audio codecs (such as AAC), resolution, bit rate, etc. In particular, it is necessary to ensure that the video frame rate is consistent with the preset frame rate. The original video file is transcoded into HLS (HTTP Live Streaming) format using the video processing library. HLS is an adaptive bitrate streaming media communication protocol based on HTTP that allows video streams to automatically adjust to different bandwidths and device capabilities under different network conditions. During the transcoding process, the video is divided into multiple shorter time segments (usually called "segments"), each of which is an independent HLS file (such as a .ts file). Further, during the HLS transcoding process, the video processing library automatically cuts the video into multiple .ts files according to the set time length (such as 10 seconds per segment). Each segment file contains video and audio data within a certain period of time. Since each preset frame rate represents a clarity level, a set of independent HLS segment files are generated for each clarity level during transcoding. Although these files have the same content, they have different encoding parameters (mainly frame rates), thus providing playback options with different clarity. Finally, the master playlist is a special M3U8 file that contains references to playlists at different clarity levels. The player will load the appropriate playlist based on the user's network conditions or user selection. For each clarity level, a variant playlist is generated. This list contains the URLs and sequence information of all HLS segment files at that clarity level, and the player will download and play these segment files in the order in the list. Use a text editor or the API provided by the video processing library to write the above information into a playlist file in M3U8 format. Make sure that the file path, URL format, etc. comply with the HLS specification.

[0042] In one embodiment of the present application, after preprocessing the video file to generate several HLS segment files with preset frame rates, the method also includes: storing the HLS segment files and their corresponding playlist files in the media resource library of the low-code platform, and establishing an index for subsequent retrieval; updating the database of the low-code platform to record the metadata information of the video file; wherein the metadata information includes the video title, description, upload time, and processed versions with different frame rates.

[0043] In one embodiment, first, determine the storage location of the HLS segment file and the playlist file in the low-code platform media resource library. This usually involves selecting or configuring a server or cloud storage service suitable for storing multimedia files. The pre-processed HLS segment files (such as .ts files) and the corresponding playlist files (such as .m3u8 files) are transferred from the temporary processing directory to the specified storage location. This can be achieved through file copy, move or upload API. For ease of management and retrieval, the files are named according to certain naming rules, and the file structure is organized according to the clarity level or other classification standards. For example, a separate directory can be created for each video in the media resource library, and all related HLS files and playlists can be stored in the directory. Then, according to the storage structure and retrieval requirements of the video file, a suitable indexing strategy is designed. The index can be based on multiple dimensions such as file name, video ID, clarity level, upload time, etc. Use a database or a specialized search engine tool (such as Elasticsearch) to create an index for the stored HLS files and playlist files. The index should contain enough information to quickly locate a specific file. Update and maintain the index regularly to ensure that it is synchronized with the files in the media resource library. When new files are added or existing files are deleted, the corresponding indexes should also be updated accordingly. Finally, design a table structure for storing video file metadata in the database of the low-code platform. The table should contain necessary fields such as video ID, title, description, upload time, list of clarity versions, etc. Collect necessary metadata information from the video upload and preprocessing process. This includes the video title and description provided by the user, the upload time recorded by the system, and a list of different clarity versions generated during the preprocessing process. Insert or update the collected metadata information into the corresponding records in the database. For each video file, ensure that there is a unique record corresponding to it in the database and contains all relevant metadata.

[0044] Step 103: When video on demand is required, trigger information is obtained to retrieve the corresponding HLS segment file to be played based on the trigger information, and the front-end browser is called to play the video.

[0045] In one embodiment of the present application, when video on demand is required, trigger information is first obtained.

[0046] Specifically, a video playback request initiated by a user interface is monitored; parameters in the video request are parsed; wherein the parameter package includes at least a unique identifier of the video, a requested video quality level, and any possible user authentication information; and the parameter is determined to be trigger information.

[0047] In one embodiment, first, a click or touch event listener is bound to the relevant video playback component of the user interface (UI). When the user clicks or touches the component to request to play the video, the event listener is triggered. Considering security, a request interception mechanism can be set on the front end or server side to ensure that all playback requests are verified to prevent illegal requests from affecting the system. Then, the parameters in the video request are parsed: the format of the video playback request is clarified, which is usually sent through an HTTP GET or POST request. The request should contain necessary parameters, which can be placed in the query string of the URL, or sent as form data or JSON payload of the POST request. After receiving the playback request on the server side, the parameters are extracted according to the format of the request. For the URL query string, the URL parsing library on the server side can be used; for the POST request, the form data or JSON payload may need to be parsed. The extracted parameters are verified to ensure that they meet the expected format and range. In particular, the unique identifier of the video should ensure its validity (such as confirming that the video does exist through a database query); the requested video quality level should be within the preset option range; user authentication information (such as tokens, session IDs, etc.) should be verified to confirm the user's identity and authority. Finally, determine the parameters as trigger information: After confirming that all necessary parameters are valid and comply with the rules, these parameters are regarded as valid trigger information for triggering video on demand. If the parameter verification fails (such as invalid video identifier, unsupported requested video quality level, user authentication failure, etc.), the corresponding error message is returned to the user and further processing is blocked. For each successful playback request, relevant log information is recorded, including the specific content of the trigger information, request time, user information, etc. This helps with subsequent monitoring, analysis, and troubleshooting.

[0048] In one embodiment of the present application, after the trigger information is obtained, the corresponding HLS segment file to be played is retrieved based on the trigger information.

[0049] Specifically, the corresponding HLS segment file to be played is retrieved based on the trigger information, which specifically includes: querying the corresponding metadata information in the database of the low-code platform according to the unique identifier in the trigger information; based on the video quality level requested by the user, retrieving the storage path or URL of the HLS segment file of the corresponding frame rate from the database.

[0050] In one embodiment, first, a unique identifier of the video (such as a video ID) is extracted from the trigger information. This identifier is the key to distinguishing different videos and ensures that the video requested by the user can be uniquely identified. Then, a connection is established with the low-code platform database. This usually involves configuring database connection parameters, such as database server address, port, user name, password, etc. Using the extracted unique identifier as a query condition, an SQL query statement is executed to retrieve metadata information related to the video in the database of the low-code platform. This metadata information includes, but is not limited to, video title, description, upload time, and HLS segment file information of different definition versions. According to the video quality level requested by the user (such as HD, SD, etc.), the corresponding file is found in the retrieved HLS segment file information. This usually involves comparing the requested quality level with the quality level identifier stored in the database to ensure that the two are consistent. If the video provides multiple definition versions and the quality level requested by the user is relatively broad (such as "HD"), it may be necessary to further determine the HLS segment file that best meets the user's needs based on specific parameters such as frame rate and resolution. Finally, the storage path or URL is extracted from the retrieved HLS segment file information. This information will be used in the subsequent video playback process to ensure that the player can accurately load and play the requested video content.

[0051] In one embodiment of the present application, after retrieving the corresponding HLS segment file to be played based on the trigger information, the front-end browser is called to play the video.

[0052] Specifically, based on the HLS video player pre-installed in the front-end browser, the HLS segment file to be played is loaded and played.

[0053] In one embodiment, first, based on the storage path or URL of the HLS segment file retrieved before, a complete URL required for playback is constructed. For HLS video streams, this is usually a URL pointing to the main playlist (.m3u8 file). Set the constructed playback URL as the source of the HLS video player. This is usually achieved by calling the player's API, such as player.src({type:'application / x-mpegURL', src:hlsUrl}); (taking video.js combined with hls.js as an example). After setting the source, initialize the HLS video player. This includes loading the player interface, preparing the playback buffer, etc. Some player libraries provide event monitoring for loading completion and playback errors, which can be used to enhance the user experience (such as displaying loading progress, handling playback errors, etc.). The playback process is controlled by the API of the HLS video player, such as playing, pausing, stopping, adjusting the volume, fast forward / fast rewind, etc. At the same time, playback events (such as playback start, playback end, playback position change, etc.) can be monitored as needed to execute specific logic (such as updating the playback progress bar, displaying relevant prompt information, etc.).

[0054] The above is an embodiment of the method proposed in this application. Based on the same inventive concept, the embodiment of this application also provides a video on demand service implementation device for a low-code platform, and its structure is as follows: Figure 2 shown.

[0055] Figure 2 A schematic diagram of the internal structure of a device for implementing a video on demand service for a low-code platform provided in an embodiment of the present application. Figure 2 As shown, the device includes:

[0056] at least one processor 201;

[0057] and, a memory 202 communicatively connected to the at least one processor;

[0058] The memory 202 stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor 201 to enable at least one processor 201 to:

[0059] Based on the attachment upload service of the low-code platform, upload the preset video file to the low-code platform;

[0060] Preprocess the video file to generate several HLS segment files with preset frame rates;

[0061] When video on demand is required, trigger information is obtained to retrieve the corresponding HLS segment file to be played based on the trigger information, and the front-end browser is called to play the video.

[0062] Some embodiments of the present application provide corresponding Figure 1 A non-volatile computer storage medium for implementing a video on demand service for a low-code platform, storing computer executable instructions, wherein the computer executable instructions are set to:

[0063] Based on the attachment upload service of the low-code platform, upload the preset video file to the low-code platform;

[0064] Preprocess the video file to generate several HLS segment files with preset frame rates;

[0065] When video on demand is required, trigger information is obtained to retrieve the corresponding HLS segment file to be played based on the trigger information, and the front-end browser is called to play the video.

[0066] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the IoT device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0067] The system and medium provided in the embodiments of the present application correspond one-to-one to the method. Therefore, the system and medium also have similar beneficial technical effects to the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the system and medium will not be repeated here.

[0068] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0069] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0070] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0071] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0072] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0073] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0074] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0075] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0076] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for implementing a video on demand service for a low-code platform. It is characterized in that The method comprises: Based on the attachment upload service of the low-code platform, the preset video file is uploaded to the low-code platform; Preprocessing the video file to generate several HLS segment files with preset frame rates; When video on demand is required, trigger information is obtained to retrieve the corresponding HLS segment file to be played based on the trigger information, and the front-end browser is called to play the video.

2. A method for implementing a video on demand service for a low-code platform according to claim 1, It is characterized in that Based on the attachment uploading service of the low-code platform, before uploading the preset video file to the low-code platform, the method further includes: Construct the attachment upload service function of the low-code platform, specifically including: Define the interface specification for attachment upload; wherein the interface specification includes file type restrictions, file size restrictions, and upload progress feedback mechanism; Design and implement the user interface of the upload component to allow users to select files and upload them; Configure the background service of the low-code platform to process the video file based on preset processing rules; wherein the processing rules at least include video file storage logic and video file naming rules.

3. A method for implementing a video on demand service for a low-code platform according to claim 2, It is characterized in that Based on the attachment upload service of the low-code platform, the preset video file is uploaded to the low-code platform, specifically including: Receive uploaded video files through the user interface provided by the low-code platform; Verifying the type and size of the video file according to preset rules; If the verification is successful, the upload process is started, the video file is transferred to the specified location on the server, and the upload progress is fed back in real time during the upload process.

4. A method for implementing a video on demand service for a low-code platform according to claim 1, It is characterized in that The video file is preprocessed to generate several HLS segment files with preset frame rates, specifically including: Using a video processing library to read the video file; According to the preset frame rate, the video file is converted into HLS format, and cut into HLS segment files of corresponding definition levels respectively; Generate a corresponding playlist file for each HLS segment file with a preset frame rate.

5. A method for implementing a video on demand service for a low-code platform according to claim 1, It is characterized in that After preprocessing the video file to generate several HLS segment files with preset frame rates, the method further includes: The HLS segment files and their corresponding playlist files are stored in the media resource library of the low-code platform, and indexed for subsequent retrieval; Update the database of the low-code platform to record the metadata information of the video file; wherein the metadata information includes the video title, description, upload time, and processed versions with different frame rates.

6. A method for implementing a video on demand service for a low-code platform according to claim 1, It is characterized in that Get trigger information, including: Monitor video playback requests initiated by the user interface; Parsing parameters in the video request; wherein the parameters include at least a unique identifier of the video, a requested video quality level, and any possible user authentication information; The parameter is determined to be trigger information.

7. According to claim 6, a method for implementing a video on demand service for a low-code platform, It is characterized in that Retrieving the corresponding HLS segment file to be played based on the trigger information specifically includes: According to the unique identifier in the trigger information, query the corresponding metadata information in the database of the low-code platform; Based on the video quality level requested by the user, the storage path or URL of the HLS segment file of the corresponding frame rate is retrieved from the database.

8. According to claim 1, a method for implementing a video on demand service for a low-code platform, It is characterized in that Call the front-end browser to play the video, including: Based on the HLS video player pre-installed in the front-end browser, the HLS segment file to be played is loaded and played.

9. A device for implementing video on demand services for low-code platforms, It is characterized in that The device comprises: at least one processor; and, a memory communicatively coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: Based on the attachment upload service of the low-code platform, the preset video file is uploaded to the low-code platform; Preprocessing the video file to generate several HLS segment files with preset frame rates; When video on demand is required, trigger information is obtained to retrieve the corresponding HLS segment file to be played based on the trigger information, and the front-end browser is called to play the video.

10. A non-volatile computer storage medium for implementing a video on demand service for a low-code platform, storing computer executable instructions, It is characterized in that The computer executable instructions are configured to: Based on the attachment upload service of the low-code platform, the preset video file is uploaded to the low-code platform; Preprocessing the video file to generate several HLS segment files with preset frame rates; When video on demand is required, trigger information is obtained to retrieve the corresponding HLS segment file to be played based on the trigger information, and the front-end browser is called to play the video.

Images