CN110865827B

CN110865827B - Data updating method, device and system

Info

Publication number: CN110865827B
Application number: CN201810982508.4A
Authority: CN
Inventors: 张斌
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Singapore Holdings Pte Ltd
Priority date: 2018-08-27
Filing date: 2018-08-27
Publication date: 2023-04-25
Anticipated expiration: 2038-08-27
Also published as: CN110865827A

Abstract

The embodiment of the application provides a data updating method, device and system, wherein the method comprises the following steps: in response to an update triggering event, determining a key identifier of a design unit to be updated as a target key identifier; obtaining a design unit to be updated corresponding to the target key identification from a design unit library; determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each design unit contained in at least one design file; updating the design unit to be updated into at least one design file to be updated. In the embodiment of the application, batch updating of a plurality of design files can be realized, so that the updating efficiency of the design files is effectively improved, and the updating accuracy and the updating comprehensiveness can be ensured.

Description

Data updating method, device and system

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a method, an apparatus, and a system for updating data.

Background

In the process of project development, technicians use design software to generate design files, for example, a mobile phone interface can be used as a design file. The design file includes a number of design elements, such as documents, generic design components, and the like. The update of design files may be very frequent for various reasons, such as project upgrades.

Current design file updating schemes typically make manual modifications to the design elements that need to be updated in a single design file by design software. The number of design files involved is large for each project, which results in the update of the design files requiring a lot of manpower and material resources and being prone to error. Especially for large projects, the required update costs and effort are enormous.

Thus, there is a need for a more efficient, lower cost design file update scheme.

Disclosure of Invention

Aspects of the present application provide a data updating method, apparatus and system for providing a new, more efficient, and less costly design file updating scheme.

The embodiment of the application provides a data updating method, which comprises the following steps:

in response to an update triggering event, determining a key identifier of a design unit to be updated as a target key identifier;

obtaining a design unit to be updated corresponding to the target key identification from a design unit library;

determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each design unit contained in at least one design file;

and updating the design unit to be updated into the at least one design file to be updated.

The embodiment of the application also provides a data updating method, which comprises the following steps:

responding to an operation interface access request, displaying an operation interface, wherein the operation interface comprises an update trigger control;

responding to the triggering operation of updating the triggering control, and displaying an information input interface;

and responding to the information input operation on the information input interface, acquiring a key identifier of a design unit to be updated as a target key identifier, wherein the target key identifier is used for determining at least one design file to be updated.

The embodiment of the application also provides a server, which comprises a memory and a processor;

the memory is used for storing one or more computer instructions;

the processor, coupled to the memory, is configured to execute one or more computer instructions for:

The embodiment of the application also provides a client, which comprises a memory, a processor, a display and a communication component;

the memory is used for storing one or more computer instructions;

responding to an operation interface access request, displaying an operation interface through the display, wherein the operation interface comprises an update trigger control;

responding to the triggering operation of updating the triggering control, and displaying an information input interface through the display;

The embodiment of the application also provides a data updating system, which comprises: a client, a server and a design unit library;

the client is used for sending an update request to the server, wherein the update request carries a target key identifier, and the target key identifier is a key identifier of a design unit which needs to be updated;

the design unit library is used for storing at least one design unit and the key identification of each of the at least one design unit;

The server is used for acquiring a design unit to be updated corresponding to the target key identifier from the design unit library according to the update request sent by the client; and determining at least one design file to be updated corresponding to the target key identification according to the key identification of each design unit contained in the at least one design file, and updating the design units to be updated into the at least one design file to be updated.

In the embodiment of the application, based on the key identifier of each design unit, an association relationship between each design unit contained in at least one design file and each design unit in the design unit library is formed. When the update triggering event occurs, the required design unit to be updated can be obtained from the design unit library according to the key identification of the design unit to be updated, at least one design file to be updated is determined according to the key identification of the design unit to be updated, and the design unit to be updated is updated to the at least one design file to be updated in batches. Therefore, in the embodiment of the application, batch updating of a plurality of design files can be realized, so that the updating efficiency of the design files is effectively improved, and the updating accuracy and the updating comprehensiveness can be ensured.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

FIG. 1 is a schematic diagram of a data update system according to an embodiment of the present disclosure;

FIG. 1a is a schematic diagram of an interactive interface of a client according to an embodiment of the present application;

FIG. 2 is a schematic diagram of another data update system according to an embodiment of the present application

FIG. 3 is a flowchart illustrating a method for updating data according to another embodiment of the present disclosure;

FIG. 4 is a flowchart illustrating another data updating method according to another embodiment of the present application;

fig. 5 is a flowchart of a data updating method according to another embodiment of the present application;

FIG. 6 is a flowchart illustrating another method for updating data according to another embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a server according to another embodiment of the present application;

fig. 8 is a schematic structural diagram of a client according to another embodiment of the present application.

Detailed Description

For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

In the prior art, a design file updating scheme is generally that design units needing updating in a single design file are manually modified through design software. The number of design files involved is large for each project, which results in the update of the design files requiring a lot of manpower and material resources and being prone to error. Especially for large projects, the required update costs and effort are enormous. Aiming at the problems existing in the prior art, in some embodiments of the present application, based on the key identifier of each design unit, an association relationship between each design unit contained in at least one design file and each design unit in the design unit library is formed. When the update triggering event occurs, the required design unit to be updated can be obtained from the design unit library according to the key identification of the design unit to be updated, at least one design file to be updated is determined according to the key identification of the design unit to be updated, and the design unit to be updated is updated to the at least one design file to be updated in batches. Therefore, in the embodiment of the application, batch updating of a plurality of design files can be realized, so that the updating efficiency of the design files is effectively improved, and the updating accuracy and the updating comprehensiveness can be ensured.

The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.

Fig. 1 is a schematic structural diagram of a data updating system according to an embodiment of the present application. As shown in fig. 1, the data updating system includes: a client 11, a server 12 and a library 13 of design elements.

The client 11, the server 12 and the design unit library 13 are communicatively connected to each other. The client 11, server 12 and design element library 13 may be connected by a wireless or wired network. In this embodiment, if the three are connected through mobile network communication, the network system of the mobile network may be any one of 2G (GSM), 2.5G (GPRS), 3G (WCDMA, TD-SCDMA, CDMA2000, UTMS), 4G (LTE), 4g+ (lte+), wiMax, or even new network systems that will be forthcoming in the future.

In physical implementation, the client 11 may be a terminal device such as a personal computer, a smart phone, or a tablet computer, the server 12 may be a server device such as a conventional server, a cloud host, or a virtual center, and the design unit library 13 may be a storage device such as a local memory, a cloud memory, or a network hard disk. The server device mainly comprises a processor, a hard disk, a memory, a system bus and the like, and is similar to a general computer architecture.

In the present embodiment, the design unit library 13 is used to store design units and key identifications of the design units. The design unit library 13 may provide a data interface to the outside, and different technicians may store a plurality of design units related to different projects into the design unit library 13. Moreover, a technician or project manager may make modifications to a plurality of design units in the design unit library 13, and thus, each design unit in the design unit library 13 may maintain a high freshness. In one possible scenario, the latest design elements may be stored in the design element library 13.

The technician may use design software to generate the design file 17 as the project is developed. An item may correspond to a plurality of design files 17, each design file 17 may contain a number of design elements, such as documents, generic design components, etc. After the design files 17 are completed, they may be stored in a local storage location corresponding to the technician, or may be stored in a public storage location, for example, different technicians may store all the design files 17 related to different projects in the same material library, for example, the technician may store the design files 17 related to the same project in a local computer used by the technician, which is not limited in this embodiment. Regardless of the storage location where the design file 17 is stored, when a batch update of the design file 17 is required, the data update method provided in this embodiment may be used. That is, at least one design file 17 determined based on other storage locations, other storage quantities, or other storage rules may be the subject of batch updates performed in embodiments of the present application.

In this embodiment, the client 11 is configured to provide a user interaction function and can notify the server 12 of the user's needs. An application or program code or the like may be installed on the client 11 and execution of such application or program code or the like by the client 11 may provide a user interaction interface and generate an update request.

Fig. 1a is a schematic diagram of an interactive interface of a client according to an embodiment of the present application. As shown in fig. 1a, the client 11 may respond to an operation interface access request to display an operation interface (the left view in fig. 1 a), where the operation interface includes an update trigger control. Depending on the usage requirement, there may be multiple update trigger controls, for example, 2 update trigger controls in fig. 1a are respectively a document synchronization control 111 and a universal design component synchronization control 112. In other scenarios, the update trigger control may also be 1, e.g., the update trigger control may be a design element synchronization control. Of course, the update trigger control may be set to other numbers, which is not limited in this embodiment.

Next, the client 11 may respond to the triggering operation of the update triggering control, and expose an information input interface (the right view in fig. 1 a), where the information input interface includes an information input control 113; and acquiring key identification of the design unit to be updated in response to the information input operation on the information input interface. The information input interface may provide an information input area or provide a list of information that may be selected by a technician, and may also provide other input forms, which are not limited in this embodiment. The technician may type or click in the information input interface information about the design unit that needs to be updated, e.g., directly key the key identification of the design unit that needs to be updated, or by typing in information such as content keywords of the design unit that needs to be updated, retrieving an information list and ultimately selecting the design unit that needs to be updated, etc. According to the information input operation by the technician, the client 11 can acquire the key identification of the design unit that needs to be updated. For convenience of description, hereinafter, the key identification of the design unit that needs to be updated is described as the target key identification.

It should be noted that fig. 1a is only an illustration of an interactive interface of the client 11, and should not be taken as a specific limitation on the interactive interface of the client 11 in the present embodiment. According to different use requirements, the interactive interface of the client 11 can be changed, the display layout of the update trigger control in the interactive interface can be adjusted according to the use requirements, the display sequence of the information input interface and the operation interface can be adjusted, and other elements in the interactive interface can be adjusted according to the use requirements.

The client 11, after acquiring the target key identification according to the information input operation of the technician, may send the target key identification to the server 12 with the update request.

For the server 12, when receiving the update request sent by the client 11, the design unit to be updated corresponding to the target key identifier may be obtained from the design unit library 13 according to the target key identifier carried in the update request; according to the key identification of each design unit contained in the at least one design file 17, at least one design file to be updated corresponding to the target key identification is determined, and the design unit to be updated is updated to the at least one design file to be updated.

As previously described, at least one design file 17 may be stored in the material library 14, or may be stored in other storage locations. Hereinafter, the technical solution of the present embodiment will be described by taking the material library 14 as an example. It should be understood that the storage location of at least one design file 17 in this embodiment is not limited to the library 14.

Fig. 2 is a schematic structural diagram of another data updating system according to an embodiment of the present application. In fig. 2, a schematic diagram of a data updating system is shown, taking as an example that at least one design file 17 is stored in the material library 14. Accordingly, the server 12 will communicate with the client 11, the design unit library 13, and the materials library 14, respectively.

After receiving the update request sent by the client 11, the server 12 may, on the one hand, search for the design unit to be updated corresponding to the target key identifier in the design unit library 13 according to the target key identifier carried in the update request, and obtain the design unit to be updated corresponding to the target key identifier from the design unit library 13. On the other hand, the server 12 may update the design units to be updated acquired from the design unit library 13 to at least one design file to be updated in the material library 14 in batch.

The server 12 may determine, according to the target key identifier and the key identifier of each design unit included in each design file 17 in the material library 14, the design unit corresponding to the target key identifier, and determine the design file 17 including the design unit corresponding to the target key identifier as the design file to be updated, where the number of design files to be updated may be multiple.

In the process of updating the design units to be updated to at least one design file to be updated in batches by the server 12, the design units to be updated can be written into the design file to be updated by the server 12, or a plug-in unit can be arranged at a storage position of the design file to be updated or the design file to be updated is loaded in the design software, and the plug-in unit or the design software is triggered by the server 12 to execute the operation of writing the design units to be updated into the design file to be updated. This embodiment is not limited thereto.

In the embodiment of the present application, based on the key identifier of each design unit, an association relationship between each design unit included in at least one design file and each design unit in the design unit library may be formed. When the update triggering event occurs, the required design unit to be updated can be obtained from the design unit library according to the key identification of the design unit to be updated, at least one design file to be updated is determined according to the key identification of the design unit to be updated, and the design unit to be updated is updated to the at least one design file to be updated in batches. Therefore, in the embodiment of the application, batch updating of a plurality of design files can be realized, so that the updating efficiency of the design files is effectively improved, and the updating accuracy and the updating comprehensiveness can be ensured.

In the above or the following embodiments, for each design file to be updated, the server 12 may determine, according to the position identifier of each design unit included in the design file to be updated, the position of the design unit corresponding to the target key identifier in the design file to be updated as the position of the design unit to be updated in the design file to be updated; and updating the design unit to be updated into the design file to be updated according to the position of the design unit to be updated in the design file to be updated.

In this embodiment, each design unit in the design file to be updated has a key identifier and a location identifier. The design units corresponding to the target key identifiers in the design file to be updated can be used as the design units to be updated according to the key identifiers of the design units in the design file to be updated, the positions of the design units in the design file to be updated can be determined according to the position identifiers of the design units contained in the design file to be updated, and the positions of the design units to be updated are used as the positions of the design units to be updated in the design file to be updated. Accordingly, when updating the design file to be updated, the server 12 can update the design unit to be updated to the position directly according to the position of the design unit to be updated in the design file to be updated.

For the server 12, after determining each design file to be updated, the position of the design unit to be updated in each design file to be updated can be quickly determined based on the position identification of each design unit in each design file to be updated, and each design file to be updated can be accurately updated in batches according to the position of the design unit to be updated in each design file to be updated, so that the updating efficiency is effectively improved.

It should be noted that the server 12 may update each design file to be updated in other manners. For example, each design unit in the design file to be updated may be traversed according to the target key identifier, and when traversing to the design file corresponding to the target key identifier in the design file to be updated, the operation of updating the design unit to be updated to the design file to be updated is performed. This embodiment is not limited thereto.

In the above or the following embodiments, in order to facilitate the server 12 to determine at least one design file to be updated corresponding to the target key identifier and a location of a design unit to be updated in the at least one design file to be updated, the server 12 may perform identifier initialization on at least one design file 17 in the material library 14.

In this embodiment, the server 12 may add a key identifier to each design unit included in each design file 17 based on the key identifier of each design unit in the design unit library 13, and may also add a location identifier to each design unit according to the location of each design unit included in each design file 17. Wherein the key identification is used to identify the content of the design unit and the location identification is used to identify the location of the design unit in the design file 17.

As described above, the design unit library 13 stores at least one design unit and the key identifications of the design units, and the server 12 may add the key identifications for the design units included in each design file 17 in the material library 14 based on the key identifications of the design units in the design unit library 13, so that the key identifications of the design units included in each design file 17 in the material library 14 are consistent with the key identifications of the design units in the design unit library 13. Accordingly, on the one hand, the server 12 can quickly locate the design unit to be updated corresponding to the target key identifier in the design unit library 13 according to the target key identifier, and on the other hand, the server 12 can determine the design unit corresponding to the target key identifier according to the target key identifier and the key identifier of each design unit included in each design file 17 in the material library 14, and determine the design file 17 including the design unit corresponding to the target key identifier as the design file to be updated.

Based on the file structure of the design files 17, the server 12 may add location identifiers to the design units according to the locations of the design units contained in each design file 17. For example, when the design file 17 is a sketch file, because of the hierarchical file structure of the sketch file, there is a correspondence between the design units and the layers, for example, when the design unit a included in the sketch file X is located on the layer 1, the server 12 may add the location identifier "add-layer 1" to the design unit a according to the layer on which the design unit a is located. Of course, the design files 17 may also adopt other file structures, and the server 12 may add location identifiers to the design units according to the locations of the design units included in each design file 17 in different file structures.

In the present embodiment, by initializing the identification of at least one design file 17 in the material library 14, the correspondence between the at least one design file 17 in the material library 14 and each design unit in the design unit library 13 can be formed based on the key identification and the position identification of each design unit. The server 12 may obtain the design unit to be updated corresponding to the target key identifier according to the invisible correspondence, determine at least one design file to be updated corresponding to the target key identifier in the material library 14, and locate a position of the design unit to be updated in the at least one design file to be updated. Thereby, the synchronous updating of at least one design file to be updated can be realized.

In the above or the following embodiments, the server 12 may further add a grouping identifier to each design file 17 according to the grouping to which each design file 17 belongs when initializing the identifier of at least one design file 17 in the material library 14. Wherein the design files 17 may be grouped by business, project, etc. dimensions. One design file 17 may belong to different groups, i.e. each design file 17 may carry multiple group identifications. For example, when grouped according to business dimension, design file a belongs to business 1 group; in the service 1 group range, when grouping according to project dimensions, the design file A is used for the project 2 group, meanwhile, the design file 17A is also used for the project 3 group, at this time, the grouping identifications carried by the design file A can be 3, namely a service 1 group, a service 1-project 2 group and a service 1-project 3 group; when grouping according to service dimension, the design file B belongs to the service 1 group; within the service 1 group, when the design files B are grouped according to the project dimension, the design files B are used for the project 1 group, and meanwhile, the design files B are also used for the project 2 group, at the moment, the grouping identifications carried by the design files A can be 3, namely, a service 1 group, a service 1-project 1 group and a service 1-project 2 group "

Accordingly, the server 12 may determine the design file group corresponding to the group identifier according to the group identifier corresponding to the target key identifier, where the group identifier corresponding to the target key identifier may be carried in the update request sent by the client 11. When the grouping identifier corresponding to the target key identifier is "service 1-item 2 group", the design file group formed by all the design files 17 carrying the grouping identifier can be determined, wherein the design files A and B in the previous example belong to the design file group.

After determining the design file group corresponding to the grouping identifier, the server 12 may determine the design file to be updated from the design file group according to the target key identifier. That is, the server 12 picks at least one design file to be updated corresponding to the target key identification from the design file group.

In this embodiment, design files belonging to different groups are isolated by the group identifier, and when the design files are updated, the update range can be flexibly selected according to different update requirements, so that the update efficiency of the design files can be further improved. Especially, when the updating scene of the design unit in the specific group is required to be updated, the updating mode provided by the embodiment can effectively meet the updating requirement and avoid unnecessary updating of the design file outside the specific group.

In the above or below embodiments, the design unit may include a document and/or a general-purpose design component. The text refers to the text portion in the design file 17. The generic design components refer to some generic design elements in the design file 17, such as colors, fonts, font sizes, and the like. Each design file 17 may include at least one document and/or at least one generic design component. For ease of management, as shown in FIG. 2, the design unit library 13 may include a document library 15 and a component library 16, wherein the document library 15 is used to store at least one document and key identifications of the document, and the component library 16 is used to store at least one generic design component and key identifications of the generic design component.

In this embodiment, the server 12 may obtain the document to be updated corresponding to the target key identifier from the document library 15; and/or obtain the generic design component to be updated corresponding to the target key identification from the component library 16. In some update scenarios, only a certain document/documents need to be updated, and in such scenarios, the server 12 may only interact with the document library 15 and obtain the document to be updated corresponding to the target key identifier. In other update scenarios, the server 12 may also interact with only the component library 16, or may also interact with both the document library 15 and the component library 16.

In some update scenarios, there may be multiple language versions for each document. Accordingly, the document library 15 stores therein documents corresponding to the key identifiers of the documents, at least one language value associated with the key identifiers of the documents, and at least one language value associated with the key identifiers of the documents. For example, for case a, there are three language versions corresponding to chinese, english and french, the key identifier of case a will be associated with three language values corresponding to three languages of chinese, english and french, respectively, and accordingly, case a of three language versions, i.e. case a, case a and case a, are stored in case library 15, and case a, case a and case a correspond to the three language values associated with the key identifier of case a, respectively.

For such an update scenario, the server 12 may obtain, from the document library 15, the documents to be updated corresponding to the at least one language value associated with the target key identifier, respectively, according to the at least one language value associated with the target key identifier. Accordingly, for the target key identifier, the server 12 may obtain, from the document library 15, a plurality of language versions corresponding to the documents to be updated. In the above example, when the target key identifier is the key identifier of the document a, the server 12 may obtain three language versions of the document a, the english document a and the french document a from the documents to be updated.

The patterns of the documents will be different in different languages, for example, the lengths of the documents in different languages may be different, and the lengths of the documents converted according to the currency exchange rate in the same amount may be different in different languages, which may cause different visual effects of the documents in different languages in the design file 17, and may cause problems such as line feed, cut, broken pages or sky light.

In an alternative implementation, to improve the effect of the pattern differences between the documents of different language versions on the visual effect of the design file 17, the server 12 may determine whether the at least one language value associated with the target key identifier includes a preset language value before updating the design unit to be updated into the at least one design file to be updated according to the location of the design unit to be updated in the at least one design file to be updated. The preset language value can be one or more, and the preset language value can be modified according to different updating scenes. The server 12 may perform different operations according to different judgment results.

When the at least one language value associated with the target key identifier does not include the preset language value, the server 12 may perform an operation of updating the to-be-updated document to the at least one to-be-updated design document according to the location of the to-be-updated design unit in the at least one to-be-updated design document.

When at least one language value associated with the target key identifier includes a preset language value, the server 12 may send, to the client 11, a document to be updated corresponding to the preset language value; for the to-be-updated document corresponding to the non-preset language value, the server 12 may perform an operation of updating the to-be-updated document corresponding to the non-preset language value into at least one to-be-updated design file.

In addition, in this implementation, the server may perform the operation of updating the universal design component to be updated into the at least one design file to be updated, regardless of whether the at least one language value associated with the target key identifier includes the preset language value.

In this implementation manner, for the client 11, the to-be-updated document corresponding to the preset language value associated with the target key identifier sent by the server 12 may be received; displaying the document to be updated through a preview interface; and in response to the modification operation of the file to be updated, updating the modified file to be updated into at least one design file to be updated corresponding to the target key identifier.

For each to-be-updated document corresponding to each preset language value associated with the target key identifier, when the to-be-updated document is displayed through a preview interface, the client 11 may display the to-be-updated document in an effect diagram of the to-be-updated design document corresponding to the target key identifier. The client 11 may adjust the language variable value of the document corresponding to the target key identifier in the design document to be displayed to be consistent with the preset language value according to the preset language value corresponding to the document to be updated. Accordingly, when the client 11 displays the effect diagram of the design file to be updated through the preview interface, the to-be-updated file corresponding to the language variable value can be called according to the adjusted language variable value of the related file in the design file to be updated, that is, the to-be-updated file corresponding to the preset language value can be called, and the to-be-updated file is displayed in the effect diagram of the design file to be updated.

The designer can modify the document to be updated in the preview interface until the document meets the design effect requirement, and the client 11 can save the modified document to be updated and update the modified document to the corresponding document to be updated.

It should be noted that, the to-be-updated document corresponding to each preset language value associated with the target key identifier may correspond to at least one to-be-updated design file, and when the to-be-updated design files are plural, the client 11 may display the plural to-be-updated design files in sequence through the preview interface. In one display mode, after the designer modifies the document to be updated corresponding to the preset language value in the currently displayed document to be updated, the next document to be updated can be continuously displayed. In another display manner, the client 11 may also display a plurality of design files to be updated at the same time. Of course, the client 11 also uses other orders or other rules to display a plurality of design files to be updated, which is not limited in this embodiment.

In this implementation manner, for the to-be-updated document corresponding to the non-preset language value, the server 12 may still perform batch update operation on the related to-be-updated document, for the to-be-updated document corresponding to the preset language value, the client 11 may preview and modify the to-be-updated document corresponding to the preset language value, and perform personalized update on at least one to-be-updated design document related to the to-be-updated document corresponding to the preset language value, so as to solve the problems of line changing, cutting, page breaking, or skylight caused by the style difference between documents of different language versions, and effectively improve the display effect of the documents of various language versions in the design document 17.

In the above or the following embodiments, the implementation manner in which the server 12 determines the key identifier of the design unit that needs to be updated as the target key identifier may be adopted, and other implementation manners may be adopted in addition to the implementation manner in which the client 11 generates the update request in the foregoing embodiments, and the server 12 obtains the key identifier of the design unit that needs to be updated from the update request as the target key identifier.

In an alternative implementation, the server 12 may receive the update notification sent by the design unit library 13, and obtain, from the update notification, the key identifier of the design unit in which the update has occurred as the target key identifier.

In the present implementation, the design unit library 13 may generate an update notification according to the update condition of the design unit stored thereon. For various reasons such as project upgrades, a designer or a user such as a project manager who has access to a library of design elements may modify the design elements in the library of design elements, which may result in an update of the design elements in the library of design elements. When the design unit stored in the design unit library is updated, the design unit library 13 may send the key identifier corresponding to the updated design unit to the server 12 in an update notification, and the server 12 may obtain the key identifier of the updated design unit from the update notification sent by the design unit library 13 as the target key identifier. And the server 12 may obtain the design unit to be updated corresponding to the target key identifier from the design unit library according to the trigger of the update notification, and update the design unit to be updated to at least one design file to be updated corresponding to the target key identifier.

In another alternative implementation, the server 12 may also periodically compare the version information of each design unit included in each design file 17 with the version information of the design units included in the design unit library 13, and obtain, as the target key identifier, the key identifier of the design unit whose version information is inconsistent.

In the present implementation, the server 12 may add version information for each design unit included in each design file 17 during the initialization process, and when updating occurs for each design file 17, the server 12 may update each design unit added version information included in each design file 17. Each design unit in the design unit library 13 also carries version information. The version information of each design unit included in each design file 17 matches the definition rule of the version information of each design unit in the design unit library 13. Thus, the version information may reflect differences between each design unit in each design file 17 and each design unit in the design unit library. Accordingly, the server can judge whether each design unit in each design file needs to be updated according to the version information.

In order to automatically determine whether each design unit in each design file needs to be updated, the server 12 may periodically compare version information of each design unit included in each design file 17 with version information of each design unit included in the design unit library 13, and when the comparison result is inconsistent with the version information for the same design unit, indicate that the design unit included in each design file 17 is a design unit that needs to be updated. The server 12 may take the key identifier of the design unit as the target key identifier, then obtain the design unit to be updated corresponding to the target key identifier from the design unit library, and update the design unit to be updated into at least one design file to be updated corresponding to the target key identifier. In this way, the server can automatically update the at least one design file 17 without requiring the designer to manually trigger the update.

In the present embodiment, batch automatic updating of the design file 17 can be achieved by an implementation in which the design unit library 13 transmits an update notification or the server 12 periodically polls version information of the design units in the design unit library 13. So that the freshness of each design file 17 can be effectively ensured.

It should be noted that, the implementation manner of determining, by the above-mentioned several servers 12, the key identifier of the design unit that needs to be updated as the target key identifier may be implemented alone or in combination. For example, the server 12 may initiate a periodic polling implementation to determine the key identifier of the design element that needs to be updated as the target key identifier when the interval duration from the last update request sent by the client 11 reaches a predetermined duration, although other possible combinations may be used, and are not exhaustive.

Fig. 3 is a flowchart of a data updating method according to another embodiment of the present application. The method is applicable to a server in a data updating system, as shown in fig. 3, and comprises the following steps:

300. in response to an update triggering event, determining a key identifier of a design unit to be updated as a target key identifier;

301. obtaining a design unit to be updated corresponding to the target key identification from a design unit library;

302. Determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each design unit contained in at least one design file;

303. updating the design unit to be updated into at least one design file to be updated.

In this embodiment, according to the update trigger event, the design unit that needs to be updated may be determined, and the key identifier of the design unit that needs to be updated is used as the target key identifier. The method comprises the steps of determining the key identifier of a design unit needing to be updated as a target key identifier, wherein in one optional implementation mode, an update request sent by a client can be received, the key identifier of the design unit needing to be updated is obtained from the update request as the target key identifier, and in another optional implementation mode, an update notification sent by a design unit library can be received, and the key identifier of the design unit with the update is obtained from the update notification as the target key identifier; in another alternative implementation manner, the version information of each design unit included in each design file may be compared with the version information of each design unit included in the design unit library periodically, so as to obtain the key identifier of the design unit with inconsistent version information as the target key identifier.

It should be noted that, the above-mentioned several implementations of determining the key identifier of the design unit that needs to be updated as the target key identifier may be implemented separately or in combination. For example, when the interval duration of the update request sent by the last client reaches a predetermined duration, the implementation of periodic polling may be started to determine the key identifier of the design unit that needs to be updated as the target key identifier, and other possible combination embodiments may be adopted, which are not exhaustive herein.

Based on the determined target key identification, a design unit to be updated corresponding to the target key identification can be obtained from the design unit library. The design unit library is used for storing the design units and the key identifiers of the design units. The library of design units may provide a data interface to the outside, and different technicians may store a plurality of design units related to different projects into the library of design units. Moreover, a technician or project manager may modify a plurality of design units in the library of design units, and thus each design unit in the library of design units may remain relatively fresh. In one possible scenario, the latest design elements may be stored in a library of design elements.

After the design units to be updated corresponding to the target key identifiers are obtained, the design units corresponding to the target key identifiers can be determined according to the target key identifiers and the key identifiers of the design units contained in each design file in the material library, the design files containing the design units corresponding to the target key identifiers are determined as the design files to be updated, and the number of the design files to be updated may be multiple.

In the above or below embodiments, step 303 includes: for each design file to be updated, determining the position of the design unit corresponding to the target key identifier in the design file to be updated as the position of the design unit to be updated in the design file to be updated according to the position identifiers of the design units contained in the design file to be updated; and updating the design unit to be updated into the design file to be updated according to the position of the design unit to be updated in the design file to be updated.

In this embodiment, each design unit in the design file to be updated has a key identifier and a location identifier. The design units corresponding to the target key identifiers in the design file to be updated can be used as the design units to be updated according to the key identifiers of the design units in the design file to be updated, the positions of the design units in the design file to be updated can be determined according to the position identifiers of the design units contained in the design file to be updated, and the positions of the design units to be updated are used as the positions of the design units to be updated in the design file to be updated. Accordingly, when the design file to be updated is updated, the design unit to be updated can be updated to the position directly according to the position of the design unit to be updated in the design file to be updated. The design files to be updated can be updated accurately in batches, and the updating efficiency is effectively improved.

It should be noted that, other ways may be used to update each design file to be updated. For example, each design unit in the design file to be updated may be traversed according to the target key identifier, and when traversing to the design file corresponding to the target key identifier in the design file to be updated, the operation of updating the design unit to be updated to the design file to be updated is performed. This embodiment is not limited thereto.

In the above or below embodiments, before step 302, further includes:

based on the key identification of each design unit in the design unit library, the key identification is added for each design unit contained in each design file, and the position identification can be added for each design unit according to the position of each design unit contained in each design file.

In this embodiment, the key identifier may be added to each design unit included in each design file based on the key identifier of each design unit in the design unit library, and the position identifier may be added to each design unit according to the position of each design unit included in each design file. Wherein the key identification is used for identifying the content of the design unit and the position identification is used for identifying the position of the design unit in the design file.

As described above, at least one design unit and the key identifier of the design unit are stored in the design unit library, and in this embodiment, the key identifier may be added to each design unit included in each design file in the material library based on the key identifier of each design unit in the design unit library, so that the key identifier of each design unit included in each design file in the material library is consistent with the key identifier of each design unit in the design unit library. Accordingly, on one hand, the design unit to be updated corresponding to the target key identifier in the design unit library can be rapidly positioned according to the target key identifier, on the other hand, the design unit corresponding to the target key identifier can be determined according to the target key identifier and the key identifier of each design unit contained in each design file in the material library, and the design file containing the design unit corresponding to the target key identifier is determined as the design file to be updated.

Based on the file structure of the design files, position identifiers can be respectively added for the design units according to the positions of the design units contained in each design file. For example, when the design file is a sketch file, because of the hierarchical file structure of the sketch file, there is a correspondence between the design unit and the layer, for example, when the design unit a included in the sketch file X is located on the layer 1, the position identifier "add-layer 1" may be added to the design unit a according to the layer on which the design unit a is located. Of course, the design files can also adopt other file structures, and position identifiers can be respectively added for the design units according to the positions of the design units contained in each design file in different file structures.

In this embodiment, by initializing at least one design file in the material library, a correspondence between the at least one design file in the material library and each design unit in the design unit library may be formed based on the key identifier and the position identifier of each design unit. According to the invisible corresponding relation, a design unit to be updated corresponding to the target key identification can be obtained, at least one design file to be updated corresponding to the target key identification is determined in the material library, and the position of the design unit to be updated in the at least one design file to be updated is located. Thereby, the synchronous updating of at least one design file to be updated can be realized.

In the above or below embodiments, step 302 may include:

determining a design file group corresponding to the grouping identification according to the grouping identification corresponding to the target key identification;

and determining at least one design file to be updated corresponding to the target key identifier from the design file group according to the target key identifier and the key identifiers of all design units in the design file group.

In this embodiment, when initializing the identifier of at least one design file, a group identifier may be added to each design file according to the group to which each design file belongs. The design files can be grouped according to dimensions of business, project and the like. One design file may be belonging to different groups, i.e. each design file may carry multiple group identifications. For example, when grouped according to business dimension, design file a belongs to business 1 group; in the service 1 group range, when grouping according to project dimensions, the design file A is used for the project 2 group, meanwhile, the design file A is also used for the project 3 group, at this time, the grouping identifications carried by the design file A can be 3, namely a service 1 group, a service 1-project 2 group and a service 1-project 3 group; when grouping according to service dimension, the design file B belongs to the service 1 group; within the service 1 group, when the design files B are grouped according to the project dimension, the design files B are used for the project 1 group, and meanwhile, the design files B are also used for the project 2 group, at the moment, the grouping identifications carried by the design files A can be 3, namely, a service 1 group, a service 1-project 1 group and a service 1-project 2 group "

Accordingly, the design file group corresponding to the grouping identification can be determined according to the grouping identification corresponding to the target key identification, wherein the grouping identification corresponding to the target key identification can be carried in the update request sent by the client. When the grouping identifier corresponding to the target key identifier is the service 1-item 2 group, the design file group formed by all the design files carrying the grouping identifier can be determined, wherein the design files A and B in the previous example belong to the design file group.

After the design file group corresponding to the grouping identification is determined, the design file to be updated can be determined from the design file group according to the target key identification and the key identification of each design unit in the design file group. That is, at least one design file to be updated corresponding to the target key identifier may be selected from the design file group.

In the above or below embodiments, the design unit may include a document and/or a general-purpose design component. The text refers to the text portion of the design file. A generic design component refers to some generic design elements in a design file, e.g., color, font size, etc. Each design file may include at least one document and/or at least one generic design component. For ease of management, as shown in fig. 2, the design unit library may include a document library and a component library, wherein at least one document and a key identifier of the document are stored in the document library, and the component library is used for at least one general design component and a key identifier of the general design component.

In this embodiment, step 301 may include:

the document to be updated corresponding to the target key identification can be obtained from the document library; and/or acquiring the to-be-updated universal design component corresponding to the target key identification from the component library.

The steps in the foregoing embodiments will be further described below by taking the design unit that needs to be updated as an example.

In some update scenarios, each document may correspond to multiple language versions, and the patterns of the documents will be different in different languages, for example, the lengths of the documents in different languages may be different, and the lengths of the documents converted according to currency exchange rates in the same amount may be different in different languages, which will cause the visual effects of the documents in different languages in the design file to be different. For example, problems such as line feed, truncation, page break, or empty skylights may occur.

Fig. 4 is a flowchart of another data updating method according to another embodiment of the present application. For convenience of description, each step in fig. 4 only relates to the update process of the document. It should be understood that the updating process of the generic design component may be implemented as described in the foregoing embodiments for the updating process of the design element. As shown in fig. 4, the method includes:

400. in response to an update triggering event, determining a key identifier of a document to be updated as a target key identifier;

401. according to the at least one language value associated with the target key identification, acquiring the to-be-updated document corresponding to the at least one language value associated with the target key identification from a document library;

402. determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each document contained in the at least one design file;

403. judging whether at least one language value associated with the target key identification contains a preset language value, if not, executing step 404; if yes, go to step 405;

404. updating the file to be updated into at least one design file to be updated;

405. judging whether the current file to be updated is a file to be updated corresponding to a preset language value, if so, executing step 406; if not, go to step 407;

406. The method comprises the steps of sending a current to-be-updated file to a client so that a designer can modify the current to-be-updated file through the client, and updating at least one to-be-updated design file corresponding to a target key identifier of the modified to-be-updated file through the client;

407. and updating the current to-be-updated file to the at least one to-be-updated design file according to the position of the to-be-updated design unit in the at least one to-be-updated design file.

Steps 400-402 may refer to the descriptions in the foregoing embodiments, and are not repeated here.

In this embodiment, a step of determining whether at least one language value associated with the target key identifier includes a preset language value is added to screen a file to be updated corresponding to the preset language value. The preset language value can be one or more, and the preset language value can be modified according to different updating scenes. According to different judging results, the server can execute different operations.

In this embodiment, for a document to be updated corresponding to a non-preset language value, batch update operation may be performed on related documents to be updated directly, and for a document to be updated corresponding to a preset language value, previewing and modifying the document to be updated corresponding to the preset language value may be performed through a client, and at least one design document to be updated related to the document to be updated corresponding to the preset language value may be individually updated, so as to solve the problems of line feed, cutoff, page breaking, or blank window caused by pattern differences between documents of different language versions, and effectively improve the display effect of documents of various language versions in the design document.

Fig. 5 is a flowchart of a data updating method according to another embodiment of the present application. The method is applied to a client in a data updating system, as shown in fig. 5, and comprises the following steps:

500. responding to an operation interface access request, displaying an operation interface, wherein the operation interface comprises an update trigger control;

501. responding to the triggering operation of updating the triggering control, and displaying an information input interface;

502. and responding to the information input operation on the information input interface, acquiring a key identifier of a design unit to be updated as a target key identifier, wherein the target key identifier is used for determining at least one design file to be updated.

In this embodiment, an operation interface may be displayed in response to an operation interface access request, where the operation interface includes an update trigger control. The number of update trigger controls may be multiple, for example, 2 update trigger controls in fig. 2 are respectively a document synchronization control and a universal design component synchronization control. In other scenarios, the update trigger control may also be 1, e.g., the update trigger control may be a design element synchronization control. Of course, the update trigger control may be set to other numbers, which is not limited in this embodiment.

Next, an information input interface can be presented in response to a trigger operation to update the trigger control; and acquiring key identification of the design unit to be updated in response to the information input operation on the information input interface. The information input interface may provide an information input area or provide a list of information that may be selected by a technician, and may also provide other input forms, which are not limited in this embodiment. The technician may type or click in the information input interface information about the design unit that needs to be updated, e.g., directly key the key identification of the design unit that needs to be updated, or by typing in information such as content keywords of the design unit that needs to be updated, retrieving an information list and ultimately selecting the design unit that needs to be updated, etc. According to the information input operation of the technician, the key identification of the design unit to be updated can be obtained. For convenience of description, hereinafter, the key identification of the design unit that needs to be updated is described as the target key identification.

It should be noted that fig. 2 is merely an illustration of an interactive interface of the client, and should not be taken as a specific limitation on the interactive interface of the client in this embodiment. According to different use requirements, the interactive interface in the embodiment can be changed, the display layout of the update trigger control in the interactive interface can be adjusted according to the use requirements, the display sequence of the information input interface and the operation interface can be adjusted, and other elements in the interactive interface can be adjusted according to the use requirements.

After the target key identification is obtained according to the information input operation of the technician, the target key identification can be carried in the update request and sent to the server.

Fig. 6 is a flowchart of another data updating method according to another embodiment of the present application. As shown in fig. 6, the method includes:

600. responding to an operation interface access request, displaying an operation interface, wherein the operation interface comprises an update trigger control;

601. responding to the triggering operation of updating the triggering control, and displaying an information input interface;

602. responding to information input operation on an information input interface, acquiring a key identifier of a design unit to be updated as a target key identifier, carrying the target key identifier in an update request, and sending the update request to a server so that the server updates the corresponding design unit in at least one design file to be updated containing the target key identifier;

603. receiving a document to be updated corresponding to a preset language value associated with a target key identifier, which is sent by a server;

604. displaying the document to be updated through a preview interface;

605. and in response to the modification operation of the file to be updated, updating the modified file to be updated into at least one design file to be updated corresponding to the target key identifier.

Steps 600-602 may refer to the descriptions in the foregoing embodiments, and are not repeated here.

In this embodiment, when the design unit to be updated includes a document corresponding to a preset language value, the document to be updated corresponding to the preset language value can be displayed through a preview interface. Optionally, the file to be updated is displayed in an effect diagram of the design file to be updated corresponding to the target key identifier. According to the preset language value corresponding to the to-be-updated document, the language variable value of the document corresponding to the target key identification in the to-be-updated design document to be displayed can be adjusted to be consistent with the preset language value. Accordingly, when the effect diagram of the design file to be updated is displayed through the preview interface, the language variable value corresponding to the language variable value can be called according to the adjusted language variable value of the related language in the design file to be updated, that is, the language to be updated corresponding to the preset language value can be called, and the language to be updated is displayed in the effect diagram of the design file to be updated.

The designer can modify the document to be updated in the preview interface until the design effect requirement is met. In this embodiment, the modified file to be updated may be saved, and the modified file to be updated may be updated into the corresponding file to be updated.

It should be noted that, the to-be-updated document corresponding to each preset language value associated with the target key identifier may correspond to at least one to-be-updated design file, and when there are multiple to-be-updated design files, the multiple to-be-updated design files may be displayed in sequence through the preview interface. In one display mode, after the designer modifies the document to be updated corresponding to the preset language value in the currently displayed document to be updated, the next document to be updated can be continuously displayed. In another display mode, the client may also display a plurality of design files to be updated at the same time. Of course, other orders or other rules are also used to present the plurality of design files to be updated, which is not limited in this embodiment.

In this implementation manner, for the to-be-updated document corresponding to the non-preset language value, the server may still execute batch update operation on the related to-be-updated document, and for the to-be-updated document corresponding to the preset language value, preview and modification of the to-be-updated document corresponding to the preset language value may be performed through the technical solution provided in this embodiment, and at least one to-be-updated design document related to the to-be-updated document corresponding to the preset language value may be individually updated, so as to solve the problems of line feed, cutoff, page breaking or sky window caused by style differences between documents of different language versions, and effectively improve the display effect of documents of various language versions in the design document.

Fig. 7 is a schematic structural diagram of a server according to another embodiment of the present application. As shown in fig. 7, the server includes: a memory 70 and a processor 71.

Memory 70 is used to store computer programs and may be configured to store various other data to support operations on the master node. Examples of such data include instructions for any application or method operating at the host node, contact data, phonebook data, messages, pictures, video, and the like.

The memory 70 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

A processor 71 coupled to the memory 70 for executing a computer program in the memory 70 for:

updating the design unit to be updated into at least one design file to be updated.

In an alternative embodiment, the processor 71 is configured to, when updating the design unit to be updated into at least one design file to be updated:

for each design file to be updated, determining the position of the design unit corresponding to the target key identifier in the design file to be updated as the position of the design unit to be updated in the design file to be updated according to the position identifiers of the design units contained in the design file to be updated;

and updating the design unit to be updated into the design file to be updated according to the position of the design unit to be updated in the design file to be updated.

In an alternative embodiment, before determining, according to the location identifier of each design unit included in the design file to be updated, the location of the design unit corresponding to the target key identifier in the design file to be updated as the location of the design unit to be updated in the design file to be updated, the processor 71 is further configured to:

and adding position identifiers for the design units according to the positions of the design units contained in each design file.

In an alternative embodiment, before determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each design unit included in the at least one design file, the processor 71 is further configured to:

and adding a key identifier for each design unit contained in each design file based on the key identifier of each design unit in the design unit library.

In an alternative embodiment, when determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each design unit included in the at least one design file, the processor 71 is configured to:

In an alternative embodiment, the processor 71 is configured to, when acquiring the design unit to be updated corresponding to the target key identifier from the design unit library:

acquiring a document to be updated corresponding to the target key identification from a document library; and/or the number of the groups of groups,

and acquiring the universal design component to be updated corresponding to the target key identification from the component library.

In an alternative embodiment, the processor 71, when acquiring the document to be updated corresponding to the target key identifier from the document library, is further configured to:

and acquiring the to-be-updated file corresponding to the at least one language value associated with the target key identifier from the file library according to the at least one language value associated with the target key identifier.

In an alternative embodiment, the processor 71 is further configured to, before updating the design unit to be updated into the at least one design file to be updated according to the location of the design unit to be updated in the at least one design file to be updated:

judging whether at least one language value associated with the target key identification contains a preset language value or not;

and when the at least one language value associated with the target key identification does not contain the preset language value, executing the operation of updating the document to be updated into the at least one design file to be updated according to the position of the design unit to be updated in the at least one design file to be updated.

In an alternative embodiment, processor 71 is further configured to:

when at least one language value associated with the target key identification contains a preset language value, sending a document to be updated corresponding to the preset language value to a client for a designer to modify the document to be updated corresponding to the preset language value through the client, and updating at least one design file to be updated corresponding to the target key identification by the modified document to be updated corresponding to the preset language value through the client;

And aiming at the to-be-updated file corresponding to the non-preset language value, executing the operation of updating the to-be-updated file corresponding to the non-preset language value into at least one to-be-updated design file according to the position of the to-be-updated design unit in at least one to-be-updated design file.

In an alternative embodiment, the server further comprises: the communication component 72 is primarily responsible for communication between the server and other devices. Based on this, the processor 71, in response to the update trigger event, when determining the key identification of the design unit that needs to be updated as the target key identification, is configured to:

receiving an update request sent by a client through a communication component 72, and acquiring a key identifier of a design unit needing to be updated from the update request as a target key identifier; or alternatively

Receiving an update notification sent by the design unit library through the communication component 72, and acquiring a key identifier of the design unit in which the update occurs from the update notification as a target key identifier; or alternatively

And comparing the version information of each design unit contained in each design file with the version information of each design unit contained in the design unit library at regular intervals, and obtaining the key identification of the design unit with inconsistent version information as a target key identification.

Further, as shown in fig. 7, the server may further include: power supply assembly 73, and the like. Only some of the components are schematically shown in fig. 7, which does not mean that the server only comprises the components shown in fig. 7.

Accordingly, the present application further provides a computer readable storage medium storing a computer program, where the computer program is executed to implement the steps executable by the server in the above method embodiments.

Fig. 8 is a schematic structural diagram of a client according to another embodiment of the present application. The client comprises: memory 80, processor 81, display 82, and communication component 83.

Memory 80 is used to store computer programs and may be configured to store various other data to support operations on the management device. Examples of such data include instructions for any application or method operating at the host node, contact data, phonebook data, messages, pictures, video, and the like.

The memory 80 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

A processor 81 coupled to the memory 80 for executing a computer program in the memory 80 for:

In response to the operation interface access request, an operation interface is displayed through the display 82, wherein the operation interface comprises an update trigger control;

in response to a trigger operation to update the trigger control, an information input interface is presented via the display 82;

In an alternative embodiment, the design unit to be updated includes a document corresponding to a preset language value; the processor 81 is further configured to:

receiving a document to be updated corresponding to a preset language value associated with the target key identification sent by a server through a communication component 83;

displaying the document to be updated through a preview interface;

and in response to the modification operation of the file to be updated, updating the modified file to be updated into at least one design file to be updated corresponding to the target key identifier.

Further, as shown in fig. 8, the client may further include: power supply assembly 84, audio assembly 85, and the like. Only some of the components are schematically shown in fig. 8, which does not mean that the client only comprises the components shown in fig. 8.

Accordingly, the embodiments of the present application also provide a computer readable storage medium storing a computer program, where the computer program can implement the steps executable by the client in the above method embodiments when executed.

Wherein the communication assembly of fig. 7 and 8 may be configured to facilitate wired or wireless communication between the device in which the communication assembly is located and other devices. The device in which the communication component is located may access a wireless network based on a communication standard, such as WiFi,2G or 3G, or a combination thereof. In one embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one embodiment, the communication component further comprises a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

Among them, the display in fig. 8 includes a screen, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation.

The power supply assembly in fig. 7 and 8 provides power for various components of the device in which the power supply assembly is located. The power components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the devices in which the power components are located.

Wherein the audio component of fig. 8 may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive external audio signals when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a speech recognition mode. The received audio signal may be further stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer 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 disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises an element.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. A method of updating data, comprising:

updating the design unit to be updated into the at least one design file to be updated;

wherein the updating the design to be updated unit to the at least one design to be updated file includes:

for each design file to be updated, determining the position of the design unit corresponding to the target key identifier in the design file to be updated as the position of the design unit to be updated in the design file to be updated according to the position identifier of each design unit contained in the design file to be updated;

2. The method according to claim 1, wherein before determining, for each design file to be updated, a position of a design unit corresponding to the target key identifier in the design file to be updated as a position of a design unit to be updated in the design file to be updated according to the position identifier of each design unit included in the design file to be updated, the method further includes:

3. The method according to claim 1, further comprising, before determining at least one design file to be updated corresponding to the target key identification according to the key identification of each design unit included in the at least one design file:

and adding key identifiers for the design units contained in each design file based on the key identifiers of the design units in the design unit library.

4. The method according to claim 1, wherein the determining, according to the key identifier of each design unit included in the at least one design file, the at least one design file to be updated corresponding to the target key identifier includes:

5. The method of claim 1, wherein the obtaining, from the design unit library, the design unit to be updated corresponding to the target key identifier includes:

Acquiring a document to be updated corresponding to the target key identifier from a document library; and/or the number of the groups of groups,

6. The method of claim 5, wherein the obtaining the document to be updated corresponding to the target key identifier from the document library further comprises:

and acquiring the to-be-updated document corresponding to the at least one language value associated with the target key identifier from the document library according to the at least one language value associated with the target key identifier.

7. The method of claim 6, wherein before updating the design unit to be updated into the at least one design file to be updated, further comprising:

and when the at least one language value associated with the target key identifier does not contain the preset language value, executing the operation of updating the design unit to be updated into at least one design file to be updated.

8. The method of claim 7, further comprising:

when at least one language value associated with the target key identification contains a preset language value, sending a to-be-updated document corresponding to the preset language value to a client for a designer to modify the to-be-updated document corresponding to the preset language value through the client, and updating the modified to-be-updated document corresponding to the preset language value to at least one to-be-updated design document corresponding to the target key identification through the client;

And aiming at the to-be-updated file corresponding to the non-preset language value, executing the operation of updating the to-be-updated file corresponding to the non-preset language value into the at least one to-be-updated design file.

9. The method of claim 1, wherein determining, in response to the update triggering event, a key identification of a design element that needs to be updated as the target key identification comprises:

receiving an update request sent by a client, and acquiring a key identifier of a design unit to be updated from the update request as a target key identifier; or alternatively

Receiving an update notification sent by the design unit library, and acquiring a key identifier of the design unit updated from the update notification as a target key identifier; or alternatively

10. A method of updating data, comprising:

Responding to information input operation on an information input interface, and acquiring a key identifier of a design unit to be updated as a target key identifier, wherein the target key identifier is used for determining at least one design file to be updated;

the design unit to be updated comprises a document corresponding to a preset language value; the method further comprises the steps of:

receiving a document to be updated corresponding to a preset language value associated with the target key identification, which is sent by a server;

displaying the file to be updated through a preview interface;

and in response to the modification operation of the file to be updated, updating the modified file to be updated into the at least one design file to be updated corresponding to the target key identifier.

11. A server comprising a memory and a processor;

the memory is used for storing one or more computer instructions;

the processor is specifically configured to, when updating the design to be updated unit to the at least one design to be updated file:

12. A client comprising a memory, a processor, a display, and a communication component;

the memory is used for storing one or more computer instructions;

the design unit to be updated comprises a document corresponding to a preset language value; the processor is further configured to:

displaying the file to be updated through a preview interface;

13. A data updating system, comprising: a client, a server and a design unit library;

the server is used for acquiring a design unit to be updated corresponding to the target key identifier from the design unit library according to the update request sent by the client; determining at least one design file to be updated corresponding to the target key identifier according to the key identifier of each design unit contained in at least one design file, and determining the position of the design unit corresponding to the target key identifier in the design file to be updated as the position of the design unit to be updated in the design file to be updated according to the position identifier of each design unit contained in the design file to be updated aiming at each design file to be updated; and updating the design unit to be updated into the design file to be updated according to the position of the design unit to be updated in the design file to be updated.

14. A computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform the data updating method of any of claims 1-9.

15. A computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform the data updating method of claim 10.