Method, device, medium and electronic device for adjusting version and reading content

Abstract

The embodiments of the present application provide a method, device, computer-readable medium and electronic device for adjusting versions and reading content. By setting a work version mapping table to record the current version identifier corresponding to each work, and setting a version information table to record each version identifier and its corresponding version information, the management efficiency of the versions of each work and its corresponding version information is improved. By querying the pending version identifier and its corresponding target work from the work version mapping table, and then obtaining the target version identifier that is greater than the pending version identifier from the version information table, the target work is revised, and finally the current version identifier corresponding to the target work in the work version mapping table is updated according to the version identifier of the revised work, so as to facilitate the storage and reading of the work version. The solution of this embodiment is suitable for version updates when the content structure is adjusted, which reduces the amount of manual operations for data updates and migrations, and improves the update efficiency of the work content version.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, computer-readable medium, and electronic device for adjusting versions and reading content. Background Art

[0002] Many platforms for displaying content store and display data based on a predefined content structure. This approach requires extensive manual work when content structures are subject to change or revision. For example, changes to the content structure require updating the storage location and format of the content data, as well as performing data migration operations. These methods significantly impact the revision process, leading to heavy workloads and low efficiency. Summary of the Invention

[0003] The embodiments of the present application provide a method, device, computer-readable medium and electronic device for adjusting versions and reading content, which can reduce the manual operations of data updates and migrations to a certain extent, and improve the update efficiency of the work content version.

[0004] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by practice of the present application.

[0005] According to one aspect of an embodiment of the present application, a method for adjusting versions is provided, comprising: querying a pending version identifier and a target work corresponding to the pending version identifier from a work version mapping table, wherein the work version mapping table is used to record a current version identifier corresponding to each work, and the pending version identifier is less than or equal to a set version identifier in the version mapping table; obtaining a target version identifier greater than the pending version identifier and target version information corresponding to the target version identifier from a version information table, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier; revising the target work based on the target version information to obtain a revised work of the target work corresponding to the target version identifier; and updating the current version identifier corresponding to the target work in the work version mapping table according to the version of the revised work.

[0006] According to one aspect of an embodiment of the present application, a method for reading content is provided, including: obtaining a read request for a specified work; based on the read request, obtaining a current version identifier from a work version mapping table, wherein the work version mapping table is used to record the current version identifier corresponding to each work; obtaining version information corresponding to the current version identifier from a version information table, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier; based on the version information, reading version data corresponding to the specified work.

[0007] According to one aspect of an embodiment of the present application, a device for adjusting a version is provided, comprising: a query unit, configured to query a pending version identifier and a target work corresponding to the pending version identifier from a work version mapping table, wherein the work version mapping table is configured to record a current version identifier corresponding to each work, and the pending version identifier is less than or equal to a set version identifier in the version mapping table; a first acquisition unit, configured to acquire a target version identifier greater than the pending version identifier and target version information corresponding to the target version identifier from a version information table, wherein the version information table is configured to record each version identifier and the version information corresponding to each version identifier; a revision unit, configured to revise the target work based on the target version information to obtain a revised work of the target work corresponding to the target version identifier; and an update unit, configured to update the current version identifier corresponding to the target work in the work version mapping table according to the version of the revised work.

[0008] In some embodiments of the present application, based on the aforementioned scheme, the query unit includes: a first detection unit, used to detect whether there is a new version in the version information table; a first query unit, used to query the pending version identifier and the target work corresponding to the pending version identifier from the work version mapping table when there is a new version in the version information table.

[0009] In some embodiments of the present application, based on the aforementioned scheme, the device for adjusting the version also includes: a fifth acquisition unit, used to obtain a current version identifier when a new work is detected, and the current version identifier is a pending version identifier in the work version mapping table; a sixth acquisition unit, used to obtain a target entry version identifier that is higher than or equal to the current version identifier from the version information table based on the current version identifier, and a target entry version information corresponding to the target entry version identifier; an entry unit, used to enter the new work based on the target entry version information.

[0010] In some embodiments of the present application, based on the aforementioned scheme, the device for adjusting the version also includes: a minimum version acquisition unit, which is used to obtain the pending version identifier from the work version mapping table after each update of the work version mapping table; and a current version update unit, which is used to update the current version identifier to the pending version identifier if the current version identifier is smaller than the pending version identifier.

[0011] In some embodiments of the present application, based on the aforementioned scheme, the device for adjusting the version also includes: a read request acquisition unit, used to obtain a read request for a specified work; a version identification acquisition unit, used to obtain a current version identification based on the read request; a version information acquisition unit, used to obtain version information corresponding to the current version identification based on the current version identification; and a version data reading unit, used to read the current version data corresponding to the specified work based on the data storage location in the version information.

[0012] In some embodiments of the present application, based on the aforementioned scheme, the revision unit includes: a rule acquisition unit, used to obtain the revision rules between the version identifier to be processed and the target version identifier; a revision processing unit, used to perform revision processing on the target work based on the target version information and the revision rules, and obtain a revised work of the target work corresponding to the target version identifier.

[0013] In some embodiments of the present application, based on the aforementioned scheme, the target work includes video data, and the revised work includes audio data; the target version information includes mapping information for representing the audio data corresponding to the target work; the revision processing unit is used to: extract the audio data in the video work based on the revision rules for converting the video work into the audio work; process the audio data based on the target version information to generate the audio data corresponding to the target version identifier of the video data.

[0014] In some embodiments of the present application, based on the aforementioned scheme, the device for adjusting the version also includes: a storage location acquisition unit, used to obtain the data storage location corresponding to the target version identifier based on the version information corresponding to the target version identifier in the version information table; and a work storage unit, used to store the revised work based on the data storage location.

[0015] In some embodiments of the present application, based on the aforementioned scheme, the device for adjusting the version also includes: a new information acquisition unit, used to acquire new version information, the new version information including a new version identifier and its corresponding version information; a new information adding unit, used to add the new version identifier and its corresponding version information to the version information table.

[0016] In some embodiments of the present application, based on the aforementioned scheme, the query unit is configured to: obtain a set version update cycle; based on the version update cycle, detect whether there is a new version in the version information table; when there is a new version in the version information table, query the pending version identifier and the target work corresponding to the pending version identifier from the work version mapping table.

[0017] According to one aspect of an embodiment of the present application, a device for reading content is provided, including: a second acquisition unit, used to obtain a read request for a specified work; a third acquisition unit, used to obtain a current version identifier from a work version mapping table based on the read request, wherein the work version mapping table is used to record the current version identifier corresponding to each work; a fourth acquisition unit, used to obtain version information corresponding to the current version identifier from a version information table, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier; and a reading unit, used to read version data corresponding to the specified work based on the version information.

[0018] According to one aspect of an embodiment of the present application, a computer-readable medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for adjusting the version and reading the content as described in the above embodiments is implemented.

[0019] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the method of adjusting versions and reading content as described in the above embodiments.

[0020] According to one aspect of an embodiment of the present application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods for adjusting a version and reading content provided in the various optional implementations described above.

[0021] In the technical solutions provided by some embodiments of the present application, by setting a work version mapping table to record the current version identifier corresponding to each work, and at the same time setting a version information table to record each version identifier and its corresponding version information, the management efficiency of the versions of each work and its corresponding version information is improved. It is also possible to query the pending version identifier and the target work corresponding to the pending version identifier from the work version mapping table, and then obtain the target version identifier that is greater than the pending version identifier from the version information table, so as to revise the target work based on the target version information corresponding to the target version identifier, obtain the updated revised work, and finally update the current version identifier corresponding to the target work in the work version mapping table according to the version identifier of the revised work, so as to facilitate the storage and reading of the work version. The solution of this embodiment can be applied to version updates when the content structure is adjusted, reducing the amount of manual operations for data updates and migrations, and improving the update efficiency of the work content version.

[0022] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, explaining the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can derive other drawings based on these drawings without inventive effort. In the drawings:

[0024] Figure 1 A schematic diagram showing an exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied;

[0025] Figure 2 A schematic diagram of an exemplary system architecture for a technical solution for reading content provided in an embodiment of the present application;

[0026] Figure 3 The following schematically shows a system for processing work versions according to an embodiment of the present application;

[0027] Figure 4 A schematic diagram schematically illustrates work management according to an embodiment of the present application;

[0028] Figure 5 Schematically shows a flow chart for entering new works according to an embodiment of the present application;

[0029] Figure 6 Schematically shows a schematic diagram of writing works based on a writing proxy server according to an embodiment of the present application;

[0030] Figure 7 A schematic diagram schematically illustrates a work of writing an initial version according to an embodiment of the present application;

[0031] Figure 8 A flowchart schematically illustrates a method for adjusting content versions according to an embodiment of the present application;

[0032] Figure 9 Schematically shows a schematic diagram of writing data after adding version 2 according to an embodiment of the present application;

[0033] Figure 10 Schematically shows a flow chart of performing revision processing based on revision rules according to an embodiment of the present application;

[0034] Figure 11 A schematic diagram schematically illustrates storage of work data according to an embodiment of the present application;

[0035] Figure 12 Schematically shows a flow chart of a method for reading content according to an embodiment of the present application;

[0036] Figure 13 Schematically shows a schematic diagram of reading a work according to an embodiment of the present application;

[0037] Figure 14 Schematically shows a schematic diagram of reading work 1 according to an embodiment of the present application;

[0038] Figure 15 Schematically shows a schematic diagram of reading work 2 according to an embodiment of the present application;

[0039] Figure 16 A block diagram schematically shows an adjusted version of a device according to an embodiment of the present application;

[0040] Figure 17 A block diagram schematically shows an apparatus for reading content according to an embodiment of the present application;

[0041] Figure 18 A schematic diagram of the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0042] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be thorough and complete and will fully convey the concepts of the example embodiments to those skilled in the art.

[0043] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner.In the following description, many specific details are provided so as to provide a full understanding of the embodiments of the present application. However, it will be appreciated by those skilled in the art that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps etc. can be adopted. In other cases, known methods, devices, implementations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0044] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0045] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0046] Figure 1 A schematic diagram shows an exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied.

[0047] like Figure 1 As shown, the system architecture may include terminal devices (such as Figure 1 101, tablet computer 102, and portable computer 103, which may also be a desktop computer, etc.), network 104, and server 105. Network 104 is a medium for providing a communication link between the terminal device and server 105. Network 104 can include various connection types, such as wired communication links, wireless communication links, etc.

[0048] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as needed. For example, the server 105 may be a server cluster consisting of multiple servers.

[0049] In one embodiment of the present application, a user can use a terminal device to interact with a server 105 via a network 104 to receive or send messages, etc. The server 105 can be a server that provides various services. For example, a user can use a terminal device 103 to upload, update, or download work data, etc., wherein the work data is stored in the server 105. When adjusting the version of a work, the server 105 queries the work version mapping table for the pending version identifier and the target work corresponding to the pending version identifier, wherein the work version mapping table is used to record the current version identifier corresponding to each work; obtains the target version identifier greater than the pending version identifier and the target version information corresponding to the target version identifier from the version information table, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier; revises the target work based on the target version information to obtain a revised work corresponding to the target version identifier of the target work; and updates the current version identifier corresponding to the target work in the work version mapping table according to the version of the revised work.

[0050] The above solution improves the management efficiency of each version and its corresponding version information by setting up a work version mapping table to record the current version identifier corresponding to each work, and setting up a version information table to record each version identifier and its corresponding version information. Furthermore, the solution can query the pending version identifier and the target work corresponding to the pending version identifier from the work version mapping table, then obtain the target version identifier greater than the pending version identifier from the version information table, and revise the target work based on the target version information corresponding to the target version identifier to obtain the updated revised work. Finally, the current version identifier corresponding to the target work in the work version mapping table is updated based on the version identifier of the revised work. This solution is applicable to version updates when various content structures are adjusted, reducing the manual operation of data updates and migrations, and improving the efficiency of updating work content versions.

[0051] It should be noted that the method for adjusting the content version provided in the embodiment of the present application is generally executed by the server 105, and accordingly, the device for adjusting the content version is generally set in the server 105. However, in other embodiments of the present application, the terminal device may also have similar functions as the server, thereby executing the solution for adjusting the content version provided in the embodiment of the present application.

[0052] Figure 2 A schematic diagram of an exemplary system architecture for a technical solution for reading content provided in an embodiment of the present application.

[0053] In one embodiment of the present application, Figure 2As shown, a user can obtain the version data corresponding to the current version identifier through terminal device 201. Specifically, terminal device 201 sends a read request to server 203, and server 203 receives the read request for a specified work; based on the read request, the current version identifier is obtained from the work version mapping table, where the work version mapping table is used to record the current version identifier corresponding to each work, and the current version identifier is the pending version identifier in the work version mapping table; the version information corresponding to the current version identifier is obtained from the version information table, where the version information table is used to record each version identifier and the version information corresponding to each version identifier; and based on the version information, the version data corresponding to the specified work is read.

[0054] Specifically, in this embodiment, the method for adjusting the version includes steps S210 to S240, which are described in detail as follows:

[0055] In step S210, the pending version identifier and the target work corresponding to the pending version identifier are queried from the work version mapping table, wherein the work version mapping table is used to record the current version identifier of each work, and the pending version identifier is less than or equal to the set version identifier in the version mapping table.

[0056] In one embodiment of the present application, a work version mapping table is pre-set to record the current version identifiers of various works. In this embodiment, the work version mapping table can be used to determine the pending version identifier. Specifically, the version identifier in the work version mapping table is compared with the set version identifier. The version identifier that is less than or equal to the set version identifier is used as the pending version identifier. After determining the pending version identifier, the target work corresponding to the pending version identifier is determined based on the records in the work version mapping table. Based on the pending version identifier and its corresponding target work, the target work is updated.

[0057] In step S220, a target version identifier greater than the version identifier to be processed and target version information corresponding to the target version identifier are obtained from a version information table, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier.

[0058] In one embodiment of the present application, after determining the version identifier to be processed and its corresponding target work, a target version identifier greater than the version identifier to be processed is obtained from the version information table as the target for updating the target work, that is, updating the target work from the current version to the target version.

[0059] In this embodiment, a version information table is pre-set, which is used to obtain a target version identifier greater than the version identifier to be processed from the version information table. The version information may include information such as storage location, version content, version format, and version structure. After determining the target version identifier, the version information corresponding to the target version identifier is determined from the version information table, and the target work is processed based on the version information.

[0060] In step S230, the target work is revised based on the target version information to obtain a revised work of the target work corresponding to the target version identifier.

[0061] In one embodiment of the present application, after determining the target version information, the target work is revised based on information such as the version format, version structure, and version content in the target version information. By converting the data in the target work to data corresponding to the target version, the target work is updated, resulting in a revised version corresponding to the target version identifier.

[0062] In step S240, the current version identifier corresponding to the target work in the work version mapping table is updated according to the version of the revised work.

[0063] In one embodiment of the present application, after the target work is updated, a revised work corresponding to the target version identifier is obtained. That is, the version identifier currently corresponding to the target work also changes to the target version identifier. In this embodiment, after the target work is updated, the record in the version mapping table is also updated. That is, the current version identifier corresponding to the target work in the work version mapping table is updated based on the version identifier of the revised work. This ensures that the record in the version mapping table is always up to date, thereby ensuring the accuracy of version adjustments.

[0064] In the above solution, by setting up a work version mapping table to record the current version identifier corresponding to each work, and simultaneously setting up a version information table to record each version identifier and its corresponding version information, the management efficiency of each version and its corresponding version information is improved. Furthermore, when reading content, a read request can be made to obtain the current version identifier corresponding to the pending version identifier from the work mapping table, and then obtain the version information corresponding to the current version identifier from the version information table. Based on this version information, the version data corresponding to the specified work can be read. This improves the efficiency of searching and reading each version of a work, thereby demonstrating high management efficiency of each version of the work data.

[0065] In one embodiment of the present application, the work may include posts, articles, and other content.

[0066] Figure 3A schematic diagram of a work version processing system provided in an embodiment of the present application.

[0067] In one embodiment of the present application, Figure 3 As shown, for mobile phone users corresponding to various terminal devices, the terminal device 310 corresponding to the poster can perform management operations on the post, such as publishing and deleting; the terminal device 320 corresponding to the reader can perform operations such as reading, liking, and commenting. The system's logic layer 330 may include services such as a work details service, a publisher service, and a personal homepage service. The work details service may include a work storage 340, specifically storing works via elasticsearch corresponding to various versions; in addition, the personal homepage service may include a personal homepage storage 350, specifically storing works uploaded to a personal account to generate a personal work list, such as by recording works in a personal account via REDIS-ZSET storage.

[0068] Figure 4 A schematic diagram of work management provided in an embodiment of the present application.

[0069] like Figure 4 As shown, the services in this embodiment may include: a work details service 410, a publisher service 440, etc. In the work details service 410, the system's current content structure version 430 is obtained through an Elasticsearch read agent 420, for example, the current version is identified as version 1. Simultaneously, a content structure version history table 460 (i.e., a version information table) and a (work, content structure version) mapping table 470 (i.e., a work version mapping table) are also obtained. The structure version history table 460 and the mapping table 470 can also be modified based on the Elasticsearch write agent 450.

[0070] Specifically, the work version mapping table in this embodiment is used to record the current version identifier corresponding to each work. Figure 4 In the example, the version corresponding to work 1 is identified as version 1, the version corresponding to work 2 is identified as version 2, the version corresponding to work 3 is identified as version 3, and so on. In addition, in this embodiment, the data corresponding to each work and each version is stored in a classified manner. For example, the data is stored by content structure version 480 to facilitate data query and reading.

[0071] In one embodiment of the present application, during the operation of the system, new works and new versions need to be continuously added. The specific method of adding works is as follows:

[0072] Figure 5 A flowchart for entering new works is provided in an embodiment of the present application.

[0073] like Figure 5 As shown, in one embodiment of the present application, the method for adjusting the version further includes steps S510 to S530:

[0074] In step S510, when a new work is detected, a current version identifier is obtained, which is the version identifier to be processed in the work version mapping table.

[0075] In step S520, based on the current version identifier, a target entry version identifier that is higher than or equal to the current version identifier and target entry version information corresponding to the target entry version identifier are obtained from the version information table.

[0076] In step S530, newly added works are entered based on the target entry version information.

[0077] Specifically, in one embodiment of the present application, when a new work is written to a terminal device, the new work needs to be entered into the system based on the current version identifier. This embodiment detects the new work and, upon detection, obtains the pending version identifier from the work version mapping table as the current version identifier. A target entry version identifier greater than or equal to the current version identifier, as well as the target entry version information corresponding to the target entry version identifier, is obtained from the version information table. The new work is then entered based on the target entry version information.

[0078] Optionally, in this embodiment, when writing and storing new works, you can use the elasticsearch write proxy server. Please refer to the following example:

[0079] Figure 6 A schematic diagram of writing works based on a writing proxy server provided in an embodiment of the present application.

[0080] like Figure 6 As shown, when writing a new work, the publishing server obtains the write request for the new work i and sends the write request for the work i to the elasticsearch write proxy server, so that the elasticsearch write proxy server performs the following steps:

[0081] 1.1 Get the current version identifier from the current content structure version information;

[0082] 1.2 Returns the current version ID;

[0083] 2.1 Obtain the version information that is greater than or equal to the current version identifier from the content structure version history table;

[0084] 2.2 Return detailed information of multiple versions;

[0085] 3.1 For each content version returned in 2.2, perform data conversion on work i and write it to the corresponding data storage;

[0086] 3.2 Return storage information.

[0087] Figure 7 This is a schematic diagram of writing an initial version of a work in one embodiment of the present application.

[0088] like Figure 7 As shown, in one embodiment of the present application, the publishing server obtains a write request for Work 1 and sends the write request for Work 1 to the elasticsearch write proxy server. When writing Work 1, the following steps are performed through the elasticsearch write proxy server:

[0089] 1.1 Get the current version identifier from the current content structure version information, that is, version 1;

[0090] 1.2 returns the current version identifier, which is version 1;

[0091] 2.1 Obtain the version information that is greater than or equal to the current version identifier from the content structure version history table;

[0092] 2.2 Since only version 1 is currently available, detailed information about version 1 is returned;

[0093] 3.1 Since there is only version 1 currently, only the content structure version 1 is written to elasticsearch and the corresponding data is stored;

[0094] 3.2 Return the stored results;

[0095] 4.1 Update the mapping record in the work version mapping table to (work 1, version 1);

[0096] 4.2 Return the updated result.

[0097] Figure 8 A flowchart showing a method for adjusting a content version according to an embodiment of the present application is shown. The method for adjusting a content version can be executed by a server, which can be Figure 1 Refer to the server shown in . Figure 8 As shown, the method for adjusting the content version includes at least steps S810 to S840, which are described in detail as follows:

[0098] In step S810, the version identifier to be processed and the target work corresponding to the version identifier to be processed are searched from the work version mapping table, wherein the work version mapping table is used to record the current version identifier corresponding to each work.

[0099] In one embodiment of the present application, various revisions may occur during the upload, update, or storage of a work. Furthermore, due to changes in user needs or system requirements, revisions may also occur. Therefore, when revisions are made, different works may have different versions. For example, the current version of Work 1 is version 2, and the current version of Work 2 is version 3.

[0100] In one embodiment of the present application, in order to avoid possible confusion between works and versions, a work version mapping table is preset in this embodiment to record the current version identifier corresponding to each work.

[0101] For example, in this embodiment, when querying the work version mapping table for the pending version identifier and the target work corresponding to the pending version identifier, for example, if the current version of Work 1 is version 2 and the current version of Work 2 is version 3, the pending version identifier is determined to be version 2, and the target work corresponding to version 2 is Work 1.

[0102] Please continue to refer to Figure 6 As shown, in Figure 6 In step 5.1, a timer is triggered to retrieve the minimum version number from all records in the mapping table, and one record is retrieved. In step 5.2, (work i, version m) is returned. This means that, as of now, among all records in the work version mapping table, the minimum version number is version m, and the corresponding work is work i.

[0103] In one embodiment of the present application, the process of querying the work version mapping table for the pending version identifier and the target work corresponding to the pending version identifier in step S810 includes the following steps:

[0104] Check whether there is a new version in the version information table;

[0105] When there is a new version in the version information table, the pending version identifier and the target work corresponding to the pending version identifier are queried from the work version mapping table.

[0106] Specifically, this embodiment detects a new version in the version information table by checking the version information table. Upon detecting a new version in the version information table, the system queries the work version mapping table for the pending version identifier and the target work corresponding to the pending version identifier. This method automatically detects the lowest version in the system upon detecting the latest version in the system, thereby automatically triggering a work version update. This improves the intelligence and efficiency of work version updates in the system.

[0107] In one embodiment of the present application, the process of querying the work version mapping table for the pending version identifier and the target work corresponding to the pending version identifier in step S810 includes the following steps:

[0108] Get the set version update cycle;

[0109] Based on the version update cycle, check whether there is a new version in the version information table;

[0110] When there is a new version in the version information table, the pending version identifier and the target work corresponding to the pending version identifier are queried from the work version mapping table.

[0111] Specifically, this embodiment automatically detects new versions based on a set version update cycle. When a new version is detected in the version information table, the work version mapping table is searched for the pending version identifier and the target work corresponding to the pending version identifier. This periodic, automatic triggering of version updates improves the intelligence of version updates while eliminating the need to constantly detect new versions in the system, thereby reducing the amount of data processed and alleviating the system's data processing burden.

[0112] In step S820, a target version identifier greater than the version identifier to be processed and target version information corresponding to the target version identifier are obtained from the version information table, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier.

[0113] In one embodiment of the present application, after querying the target work corresponding to the version identifier to be processed from the work version mapping table, the target version identifier greater than the version identifier to be processed and the target version information corresponding to the target version identifier are obtained from the version information table to revise the target work based on the target version information.

[0114] Please continue to refer to Figure 6 As shown, in Figure 6 In step 7.1, obtain detailed information of versions greater than the minimum version m from the content structure version history table; in step 7.2, obtain the returned version information as the target version information, so as to revise the target work based on the target version information.

[0115] For example, if the minimum version number recorded in the current mapping table is 2, a version identifier greater than version 2 is obtained as the target version identifier, that is, version 3 is obtained as the target version identifier, and the version information corresponding to version 3 is used as the target version information to revise the target work based on the version information of the target version 3.

[0116] In step S830, the target work is revised based on the target version information to obtain a revised work corresponding to the target version identifier.

[0117] In one embodiment of the present application, after obtaining the target version information, the target work is revised based on the target version information to obtain a revised work corresponding to the target version identifier, that is, a new work after the revision.

[0118] Please continue to refer to Figure 6 As shown, in Figure 6 In step 8.1, for each version returned in 7.2, that is, a version greater than the minimum version m, data conversion processing is performed on work i and then written to the actual data storage; the storage result is returned in step 8.2.

[0119] For example, if the current minimum version is version 2 corresponding to work 1, and the version identifier obtained that is greater than the minimum version 2 is version 3, then data conversion processing is performed on work 1 based on the version information of version 3, and work 1 corresponds to the revised work with target version identifier 3.

[0120] In one embodiment of the present application, Figure 10 As shown, in step S830, the target work is revised based on the target version information to obtain a revised version of the target work corresponding to the target version identifier, including steps S1010 to S1020, which are described in detail as follows:

[0121] In step S1010, the revision rules between the version identifier to be processed and the target version identifier are obtained.

[0122] In one embodiment of the present application, a revision rule exists between the pending version identifier and the target version identifier, and is used to convert the pending version identifier to the target version identifier based on the revision rule. For example, in this embodiment, the target work includes video data, and the revised work includes audio data; the target version information includes mapping information for the audio data corresponding to the target work.

[0123] In step S1020, based on the target version information and the revision rule, the target work is revised to obtain a revised work corresponding to the target version identifier.

[0124] In one embodiment of the present application, a target work is subjected to revision processing such as data conversion based on target version information and revision rules, thereby obtaining a revised work corresponding to the target version identifier. For example, audio data from a video work is extracted based on revision rules for converting a video work into an audio work; the audio data is then processed based on the target version information to generate audio data corresponding to the target version identifier.

[0125] In step S840, the current version identifier corresponding to the target work in the work version mapping table is updated according to the version of the revised work.

[0126] In one embodiment of the present application, the work version mapping table is used to record the work and the latest version identifier corresponding to the work. Therefore, after the work is revised to obtain a new revised work and its corresponding target version identifier, the identifier corresponding to the work in the work version mapping table is updated, and the version of the revised work is updated with the current version identifier corresponding to the target work in the work version mapping table.

[0127] Please continue to refer to Figure 6 As shown, in Figure 6 After storing the revised version data in steps 8.1 and 8.2, the mapping record is updated in step 9.1 to the current version identifier corresponding to the target work, i.e., (work i, version max). By updating the current version identifier corresponding to the target work in the work version mapping table, the latest version corresponding to the work can be directly determined based on the work version mapping table, facilitating the search and reading of work data.

[0128] In one embodiment of the present application, the method for adjusting the version further includes the following steps:

[0129] After each update of the work version mapping table, the pending version identifier is obtained from the work version mapping table; if the current version identifier is smaller than the pending version identifier, the current version identifier is updated to the pending version identifier.

[0130] Specifically, the current version identifier in this embodiment represents the pending version identifier in the work version mapping table. After the work version mapping table is updated, the pending version identifier may also change. Therefore, the current version identifier is updated by comparing the current version identifier with the pending version identifier. Specifically, if the current version identifier is less than the pending version identifier, the current version identifier is updated to the pending version identifier.

[0131] Please continue to refer to Figure 6 As shown, in Figure 6 After obtaining the minimum version number in step 5.1, in step 6.1, if the current version is smaller than the minimum version, the version identifier of the minimum version is assigned to the current version. In this way, the version identifier of the current version is updated to make the current version the latest.

[0132] In one embodiment of the present application, the method for adjusting the version further includes the following steps:

[0133] Get the new version information, including the new version identifier and its corresponding version information;

[0134] Add the new version identifier and its corresponding version information to the version information table.

[0135] Please continue to refer to Figure 4 As shown, in this embodiment, the administrator can manage the version information table, for example, add a new version and its corresponding time, version information, etc., that is, add a new version identifier and its corresponding version information, and add the new version identifier and its corresponding version information to the version information table to realize version updates.

[0136] Figure 9 A schematic diagram of writing data after adding version 2 provided in an embodiment of the present application.

[0137] like Figure 9 As shown, in one embodiment of the present application, when the publishing server obtains a write request for Work 2, the write request for Work 2 is sent to the elasticsearch write proxy server. When writing Work 2, the following steps are performed through the elasticsearch write proxy server:

[0138] 1.1 Get the current version identifier from the current content structure version information, that is, version 1;

[0139] 1.2 The current version identifier is returned from the current content structure version information, that is, version 1;

[0140] 2.1 Obtain the version information that is greater than or equal to the current version identifier from the content structure version history table;

[0141] 2.2 Return detailed information of version 1 and version 2;

[0142] 3.1 Since the current version is version 1, for each content version greater than or equal to the current version, write it to the corresponding data storage, including content structure version 1 elasticsearch and content structure version 2 elasticsearch;

[0143] 3.2 Return the stored results;

[0144] 4.1 Update the mapping record in the work version mapping table to (work 2, version 2);

[0145] 4.2 Return the updated result.

[0146] Please continue to refer to Figure 9 As shown in the figure, after adding the new work 2, the works in the system are updated through the timer trigger. The specific processing method is as follows:

[0147] The first trigger update process includes the following steps:

[0148] 5.1 Get the minimum version number of all records from the mapping table and take 1 record;

[0149] 5.2 Return (Work 1, Version 1). This means that as of now, among all the records in the Work Version Mapping Table, the smallest version number is Version 1, and the corresponding work is Work 1;

[0150] 6.1 At this time, the current version and the minimum version are both version 1. If the current version is not less than the minimum version, the current version will not be updated.

[0151] 6.2 Return the update result;

[0152] 7.1 Obtain detailed information of versions greater than the minimum version 1 from the content structure version history table, i.e., version 2;

[0153] 7.2 Get the returned version information as the target version information;

[0154] 8.1 For each version returned by 7.2, that is, each version greater than the minimum version 1, perform data conversion processing on work 1 and then write it to the actual data storage, that is, content structure version 2 elasticsearch;

[0155] 8.2 Return the stored results;

[0156] 9.1 Update the mapping record to the current version identifier of the target work, i.e. (Work 1, Version 2);

[0157] 9.2 Return the updated results.

[0158] The second trigger update process includes the following steps:

[0159] 5.1'Get the minimum version number of all records from the mapping table and take 1 record;

[0160] 5.2' As of now, all records in the work version mapping table have been updated to version 2. Therefore, if the current minimum version number is version 2, then return (work 1, version 2) or (work 2, version 2);

[0161] 6.1' At this time, the current version is version 1, and the minimum version is version 2. If the current version is less than the minimum version, then the current version is updated to equal the minimum version, that is, the current version identifier is set to version 2;

[0162] 6.2'Return the updated result;

[0163] 7.1'Get the version details greater than the minimum version 2 from the content structure version history table;

[0164] 7.2'If there is no version greater than version 2, return null;

[0165] 8.1'Since 7.2 is empty, it is not executed here;

[0166] 8.2'Return the stored result;

[0167] 9.1'Since 7.2 is empty, it is not executed here;

[0168] 9.2'Return the updated result.

[0169] Figure 11 A schematic diagram of a work data storage provided in an embodiment of the present application.

[0170] Please refer to Figure 4 and Figure 11 As shown, after the work is revised, the work data is stored based on the storage location corresponding to each version in this embodiment. Figure 4 480, for each content structure version, there is a corresponding storage method and storage location. Specifically, Figure 11 In the example, various storage methods are included, such as 1 elasticsearch storage 1110, 2 elasticsearch storage 1120, and x elasticsearch storage 1130, each of which corresponds to a different version structure. For example, the mapping relationship between the works and data included in 1 elasticsearch storage 1110 is:

[0171] "Work": {"Title":"string","Main Text":"string","Cover Image":"string"}; 2The mapping relationship between the works and data included in elasticsearch storage 1120 is: mapping mapping relationship "Work": {"Title":"string","Main Text":"string","Cover Image":"string""Work Type":"int"} and so on.

[0172] In this embodiment, works corresponding to various version types are stored in the above-mentioned storage method, so that when searching, classifying or reading the works, the storage location of the works can be efficiently determined and corresponding processing can be performed. In this way, the efficiency of data management can be greatly improved.

[0173] Figure 12A flowchart of a method for reading content according to an embodiment of the present application is shown. The method for adjusting the content version can be executed by a server, which can be Figure 1 The server shown in can also be a terminal device. Figure 12 As shown, the method for reading content includes at least steps S1210 to S1240, which are described in detail as follows:

[0174] In step S1210 , a read request for a specified work is obtained.

[0175] In one embodiment of the present application, the read request may be sent via a server or a terminal device, and may include the name, author, keywords, etc. of the specified work, and may also include a work identifier, etc.

[0176] Figure 13 A schematic diagram of reading a work provided in an embodiment of the present application.

[0177] In one embodiment of the present application, Figure 13 As shown, in step S1310, the publishing server obtains the read request of work x; in step S1320, the read request of work x is forwarded to the Elasticsearch read proxy server.

[0178] Figure 14 A schematic diagram of reading work 1 provided in an embodiment of the present application.

[0179] In one embodiment of the present application, Figure 14 As shown, in step S1410, the publishing server obtains the read request of work 1; in step S1420, the read request of work 1 is forwarded to the Elasticsearch read proxy server.

[0180] Figure 15 A schematic diagram of reading work 2 provided in an embodiment of the present application.

[0181] In one embodiment of the present application, Figure 15 As shown, in step S1310, the publishing server obtains the read request of work 2; in step S1320, the read request of work 2 is forwarded to the Elasticsearch read proxy server.

[0182] In step S1220, based on the read request, the current version identifier is obtained from the work version mapping table, wherein the work version mapping table is used to record the current version identifier corresponding to each work, and the current version identifier is the pending version identifier in the work version mapping table.

[0183] In one embodiment of the present application, a work version mapping table is set to record the current version identifier corresponding to each work, and the current version identifier is the pending version identifier in the work version mapping table. In this embodiment, after obtaining a read request, the pending version identifier in the version mapping table is determined to be the current version identifier.

[0184] In one embodiment of this application, please continue to refer to Figure 13 As shown, in step S1330, the current version is obtained through the current content structure version; in step S1340, the current content structure version returns the current version identifier.

[0185] In one embodiment of this application, please continue to refer to Figure 14 As shown, in step S1430, the current version 1 is obtained through the current content structure version; in step S1440, the current content structure version returns the current version identifier 1.

[0186] In one embodiment of this application, please continue to refer to Figure 15 As shown, in step S1530, the current version 2 is obtained through the current content structure version; in step S1540, the current content structure version returns the current version identifier 2.

[0187] In step S1230, the version information corresponding to the current version identifier is obtained from the version information table, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier.

[0188] In one embodiment of the present application, the version information table is used to record each version identifier and the version information corresponding to each version identifier, and the version information corresponding to the current version identifier is obtained from the version information table, wherein the version information includes information such as the actual data storage location and the data storage location.

[0189] In one embodiment of this application, please continue to refer to Figure 13 As shown, in step S1350, detailed information of the current version is obtained from the content structure version history table; in step S1360, detailed information of the current version is returned.

[0190] In one embodiment of this application, please continue to refer to Figure 14 As shown, in step S1450, detailed information of the current version 1 is obtained from the content structure version history table; in step S1460, detailed information of the current version 1 is returned.

[0191] In one embodiment of this application, please continue to refer to Figure 15As shown, in step S1550, detailed information of the current version 2 is obtained from the content structure version history table; in step S1560, detailed information of the current version 2 is returned.

[0192] In step S1240, based on the version information, the version data corresponding to the specified work is read.

[0193] In one embodiment of the present application, after obtaining the version information corresponding to the current version, the version data corresponding to the specified work is read based on information such as the data storage location in the version information.

[0194] In one embodiment of this application, please continue to refer to Figure 13 As shown, in step S1370, the corresponding data storage is read through the actual data storage content structure version x elasticsearch.

[0195] In one embodiment of this application, please continue to refer to Figure 14 As shown, in step S1470, the corresponding data storage is read through the actual data storage content structure version 1 elasticsearch.

[0196] In one embodiment of this application, please continue to refer to Figure 15 As shown, in step S1570, the corresponding data storage is read through the actual data storage content structure version 2 elasticsearch.

[0197] It should be noted that Figure 12 The specific implementation method of the corresponding embodiment corresponds to the implementation method in the above embodiment. Please refer to the description in the above embodiment for details, and no further details will be given here.

[0198] The following describes an embodiment of the device of the present application, which can be used to execute the adjusted version of the method in the above-mentioned embodiment of the present application. It is understood that the device can be a computer program (including program code) running on a computer device, for example, the device is an application software; the device can be used to execute the corresponding steps in the method provided in the embodiment of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the adjusted version of the method in the above-mentioned embodiment of the present application.

[0199] Figure 16 A block diagram of a device for reading content according to an embodiment of the present application is shown.

[0200] Reference Figure 16 As shown, an adjusted version of the apparatus 1600 according to one embodiment of the present application includes:

[0201] The query unit 1610 is used to query the pending version identifier and the target work corresponding to the pending version identifier from the work version mapping table, wherein the work version mapping table is used to record the current version identifier corresponding to each work; the first acquisition unit 1620 is used to obtain the target version identifier greater than the pending version identifier and the target version information corresponding to the target version identifier from the version information table, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier; the revision unit 1630 is used to revise the target work based on the target version information to obtain the revised work of the target work corresponding to the target version identifier; the update unit 1640 is used to update the current version identifier corresponding to the target work in the work version mapping table according to the version of the revised work.

[0202] In some embodiments of the present application, based on the aforementioned scheme, the query unit 1610 includes: a first detection unit, used to detect whether there is a new version in the version information table; a first query unit, used to query the version identifier to be processed and the target work corresponding to the version identifier to be processed from the work version mapping table when there is a new version in the version information table.

[0203] In some embodiments of the present application, based on the aforementioned scheme, the version adjustment device 1600 also includes: a fifth acquisition unit, used to obtain the current version identifier when a new work is detected, the current version identifier being the pending version identifier in the work version mapping table; a sixth acquisition unit, used to obtain a target entry version identifier that is higher than or equal to the current version identifier from the version information table based on the current version identifier, and the target entry version information corresponding to the target entry version identifier; an entry unit, used to enter the new work based on the target entry version information.

[0204] In some embodiments of the present application, based on the aforementioned scheme, the version adjustment device 1600 also includes: a minimum version acquisition unit, which is used to obtain the pending version identifier from the work version mapping table after each update of the work version mapping table; and a current version update unit, which is used to update the current version identifier to the pending version identifier if the current version identifier is smaller than the pending version identifier.

[0205] In some embodiments of the present application, based on the aforementioned scheme, the device 1600 for adjusting the version also includes: a read request acquisition unit, used to obtain a read request for a specified work; a version identification acquisition unit, used to obtain a current version identification based on the read request; a version information acquisition unit, used to obtain version information corresponding to the current version identification based on the current version identification; and a version data reading unit, used to read the current version data corresponding to the specified work based on the data storage location in the version information.

[0206] In some embodiments of the present application, based on the aforementioned scheme, the revision unit 1630 includes: a rule acquisition unit, used to obtain the revision rules between the version identifier to be processed and the target version identifier; a revision processing unit, used to perform revision processing on the target work based on the target version information and the revision rules, and obtain a revised work of the target work corresponding to the target version identifier.

[0207] In some embodiments of the present application, based on the aforementioned scheme, the target work includes video data, and the revised work includes audio data; the target version information includes mapping information for representing the audio data corresponding to the target work; the revision processing unit is used to: extract the audio data in the video work based on the revision rules for converting the video work into the audio work; process the audio data based on the target version information to generate video data corresponding to the audio data corresponding to the target version identifier.

[0208] In some embodiments of the present application, based on the aforementioned scheme, the device 1600 for adjusting the version also includes: a storage location acquisition unit, used to obtain the data storage location corresponding to the target version identifier based on the version information corresponding to the target version identifier in the version information table; and a work storage unit, used to store the revised work based on the data storage location.

[0209] In some embodiments of the present application, based on the aforementioned scheme, the device 1600 for adjusting the version also includes: a new information acquisition unit, used to obtain new version information, the new version information includes a new version identifier and its corresponding version information; a new information adding unit, used to add the new version identifier and its corresponding version information to the version information table.

[0210] In some embodiments of the present application, based on the aforementioned scheme, the query unit is configured to: obtain the set version update cycle; based on the version update cycle, detect whether there is a new version in the version information table; when there is a new version in the version information table, query the pending version identifier and the target work corresponding to the pending version identifier from the work version mapping table.

[0211] Figure 17 A block diagram of a device for reading content according to an embodiment of the present application is shown.

[0212] Reference Figure 17As shown, according to an embodiment of the present application, the device 1700 for reading content includes: a second acquisition unit 1710, used to obtain a read request for a specified work; a third acquisition unit 1720, used to obtain a current version identifier from a work version mapping table based on the read request, wherein the work version mapping table is used to record the current version identifier corresponding to each work; a fourth acquisition unit 1730, used to obtain version information corresponding to the current version identifier from a version information table, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier; a reading unit 1740, used to read version data corresponding to the specified work based on the version information.

[0213] Figure 18 A schematic diagram of the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application is shown.

[0214] It should be noted that Figure 18 The computer system 1800 of the electronic device shown is only an example and should not limit the functions and scope of use of the embodiments of the present application.

[0215] like Figure 18 As shown, computer system 1800 includes a central processing unit (CPU) 1801, which can perform various appropriate actions and processes according to the program stored in read-only memory (ROM) 1802 or the program loaded from storage portion 1808 into random access memory (RAM) 1803, such as executing the method described in the above embodiment. Various programs and data required for system operation are also stored in RAM 1803. CPU 1801, ROM 1802 and RAM 1803 are connected to each other via bus 1804. Input / output (I / O) interface 1805 is also connected to bus 1804.

[0216] The following components are connected to the I / O interface 1805: an input section 1806 including a keyboard, a mouse, and the like; an output section 1807 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and speakers; a storage section 1808 including a hard disk; and a communication section 1809 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 1809 performs communication processing via a network such as the Internet. A drive 1810 is also connected to the I / O interface 1805 as needed. Removable media 1811, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 1810 as needed, so that computer programs read from the removable media can be installed in the storage section 1808 as needed.

[0217] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1809, and / or installed from a removable medium 1811. When the computer program is executed by the central processing unit (CPU) 1801, the various functions defined in the system of the present application are executed.

[0218] It should be noted that the computer-readable medium shown in the embodiments of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable computer program. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0219] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0220] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. In some cases, the names of these units do not constitute limitations on the units themselves.

[0221] According to one aspect of the present application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations described above.

[0222] As another aspect, the present application further provides a computer-readable medium, which may be included in the electronic device described in the above embodiments, or may exist independently without being incorporated into the electronic device. The computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device implements the method described in the above embodiments.

[0223] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiment of the application, the features and functions of two or more modules or units described above can be concretized in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0224] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

[0225] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art that are not disclosed herein.

[0226] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for adjusting a version, characterized in that: include: Querying a pending version identifier and a target work corresponding to the pending version identifier from a work version mapping table, wherein the work version mapping table is used to record the current version identifier of each work, and the pending version identifier is less than or equal to the set version identifier; Obtaining from a version information table a target version identifier greater than the version identifier to be processed, target version information corresponding to the target version identifier, and a target revision rule corresponding to the target version information, wherein the version information table is used to record each version identifier and the version information corresponding to each version identifier, and the version information includes revision rules for performing cross-media format conversion on the work; Based on the target version information and the target revision rule, performing revision processing on the target work for the cross-media format conversion to obtain a revised work of the target work corresponding to the target version identifier; The current version identifier corresponding to the target work in the work version mapping table is updated according to the version of the revised work.

2. The method according to claim 1, characterized in that Querying the work version mapping table for the version identifier to be processed and the target work corresponding to the version identifier to be processed includes: Check whether there is a new version in the version information table; When there is a new version in the version information table, the to-be-processed version identifier and the target work corresponding to the to-be-processed version identifier are queried from the work version mapping table.

3. The method according to claim 1, characterized in that The method comprises: When a new work is detected, a current version identifier is obtained, where the current version identifier is the pending version identifier in the work version mapping table; Based on the current version identifier, obtaining from the version information table a target entry version identifier that is greater than or equal to the current version identifier, and target entry version information corresponding to the target entry version identifier; The newly added work is entered based on the target entry version information.

4. The method according to claim 3, characterized in that The method further comprises: After each update of the work version mapping table, obtaining a to-be-processed version identifier from the work version mapping table; If the current version identifier is smaller than the version identifier to be processed, the current version identifier is updated to the version identifier to be processed.

5. The method according to claim 3, characterized in that The method further comprises: Get the read request for the specified work; Based on the read request, obtain a current version identifier; Based on the current version identifier, obtaining version information corresponding to the current version identifier; Based on the data storage location in the version information, the current version data corresponding to the specified work is read.

6. The method according to claim 1, characterized in that The target work includes video data, the modified work includes audio data, and the target modification rules include modification rules for converting the video work into the audio work; Based on the target version information and the target revision rule, the target work is revised to obtain a revised work of the target work corresponding to the target version identifier, including: extracting audio data from the video work based on the modification rules for converting the video work into an audio work; The audio data is processed based on the target version information to generate audio data corresponding to the target version identifier of the video data.

7. The method according to claim 1, characterized in that Based on the target version information and the target revision rule, after performing revision processing on the target work for the cross-media format conversion to obtain a revised work of the target work corresponding to the target version identifier, the method further includes: Based on the version information corresponding to the target version identifier in the version information table, obtaining the data storage location corresponding to the target version identifier; Based on the data storage location, the revised work is stored.

8. The method according to claim 1, characterized in that The method further comprises: Obtaining new version information, including a new version identifier and its corresponding version information; The newly added version identifier and its corresponding version information are added to the version information table.

9. The method according to claim 1, characterized in that Querying the work version mapping table for the version identifier to be processed and the target work corresponding to the version identifier to be processed includes: Get the set version update cycle; Based on the version update cycle, detecting whether there is a new version in the version information table; When there is a new version in the version information table, the to-be-processed version identifier and the target work corresponding to the to-be-processed version identifier are queried from the work version mapping table.

10. A method for reading content, characterized in that: include: Get the read request for the specified work; Based on the read request, obtaining a current version identifier from a work version mapping table updated by the method according to any one of claims 1 to 9; Obtain the version information corresponding to the current version identifier from the version information table; Based on the obtained version information, the version data corresponding to the specified work is read.

11. A device for adjusting the version, characterized in that include: a query unit, configured to query a work version mapping table for a pending version identifier and a target work corresponding to the pending version identifier, wherein the work version mapping table is configured to record the current version identifier of each work, and the pending version identifier is less than or equal to a set version identifier; A first obtaining unit is configured to obtain, from a version information table, a target version identifier that is greater than the version identifier to be processed, target version information corresponding to the target version identifier, and a target revision rule corresponding to the target version information, wherein the version information table is configured to record each version identifier and the version information corresponding to each version identifier, and the version information includes revision rules for performing cross-media format conversion on the work; a revision unit configured to perform revision processing on the target work for the cross-media format conversion based on the target version information and the target revision rule, to obtain a revised work of the target work corresponding to the target version identifier; An updating unit is configured to update a current version identifier corresponding to the target work in the work version mapping table according to the version of the revised work.

12. A device for reading content, characterized in that: include: A second acquiring unit is used to acquire a read request for a specified work; a third acquiring unit, configured to acquire, based on the read request, a current version identifier from a work version mapping table updated by the method according to any one of claims 1 to 9; A fourth acquiring unit, configured to acquire version information corresponding to the current version identifier from the version information table; The reading unit is used to read the version data corresponding to the specified work based on the obtained version information.

13. A computer-readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the adjusted version method according to any one of claims 1 to 9 or the method for reading content according to claim 10 is implemented.

14. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the adjusted version method as described in any one of claims 1 to 9, or the method for reading content as described in claim 10.

15. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the adjusted version method as described in any one of claims 1 to 9, or the method for reading content as described in claim 10.

Images