Term processing method, system and storage medium

Abstract

Embodiments of the present application provide a term processing method and system and a storage medium. The method is applied to a business end, the business end comprising a business front end and a business back end, the business back end establishing a long connection with the business front end and a unified term platform, and comprising: detecting, by the business back end, whether a term included in a term asset matched with an identifier of the business end in the unified term platform is updated, the unified term platform being configured to generate a term asset of the business end, the term asset comprising a plurality of term groups used by the business end, each term group comprising all terms of the business end in any language that can be supported, and each term corresponding to a term identifier; obtaining, by the business back end, an updated term in a case where it is detected that there is an update, and returning the updated term to the business front end, the updated term carrying the term identifier; determining, by the business front end, a functional module to which the updated term belongs according to the term identifier; and updating, by the business front end, a corresponding term in the determined functional module using the updated term.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a method, system, and storage medium for processing terms. Background Technology

[0002] In a software platform, text descriptions and prompts are ubiquitous; these are called terms. Some terms are hardcoded into the front-end, while others are prompts returned from the back-end. When a term is found to have a problem and needs modification, the front-end or back-end software needs to be redeployed. Modifying terms is very cumbersome, especially regarding multilingual (internationalization) support. When a new language needs to be supported, finding the corresponding term and configuring the new language term is extremely time-consuming.

[0003] In existing technologies, the common approach is to extract the translated terminology files from each application module and compress them into resource file archives with package names corresponding to each application module. All these resource file archives are then compressed into a single theme package. The resulting theme package is copied to the mobile terminal and decompressed into a custom directory. When the mobile terminal's system uses an ID to look up the terminology for the corresponding application module, it parses the passed-in resource ID and checks if a resource file archive corresponding to the current application module's package name exists in the custom directory. If such an archive exists, the terminology file within it is loaded into memory, and the terminology with the corresponding resource ID is returned as the final terminology. However, modifying terms using this method is cumbersome. Each application's terms are stored in a separate terminology file. When a term needs modification, it must be searched within that file, modified, and then the application repackaged and republished. This process only takes effect after the user downloads the new application, resulting in a lengthy period from terminology modification to final terminology effectiveness. At the same time, because the target term is being searched in a file, it is easy to make mistakes. Summary of the Invention

[0004] The purpose of this application is to provide a method, system, and storage medium for processing terms, in order to solve the technical defects in the prior art that cannot achieve accurate dynamic updates of terms.

[0005] To achieve the above objectives, the first aspect of this application provides a method for processing terms, applied to a business end, which includes a business front-end and a business back-end. The business back-end establishes a long connection with the business front-end and a unified term platform. The processing method includes:

[0006] The business backend checks whether the terms included in the term assets that match the business identifier in the unified term platform have been updated. The unified term platform is used to generate term assets for the business. The term assets include multiple term groups used by the business. Each term group includes all terms of the business in any supported language. Each term corresponds to a term identifier.

[0007] When the business backend detects an update, it retrieves the updated term and returns it to the business frontend. The updated term carries a term identifier.

[0008] The business front-end determines the functional module to which the updated term belongs based on the term identifier;

[0009] The business front-end uses the updated terms to update the corresponding terms in the identified functional modules.

[0010] In embodiments of this application, the processing method further includes: a business backend receiving a first SSE long connection request initiated by a business frontend, wherein the first SSE long connection request carries at least one language parameter; the business backend responding to the first SSE long connection request to establish a long connection with the business frontend; the business backend initiating a second SSE long connection request to the unified term platform, and establishing a long connection with the unified term platform if it is determined that the unified term platform responds to the second SSE long connection request.

[0011] In embodiments of this application, the processing method further includes updating at least one of term modification, term deletion, and term addition.

[0012] In embodiments of this application, the processing method further includes: upon receiving a term query request triggered by a user carrying a term to be queried, the business frontend obtains the user's address; the business frontend determines the language type corresponding to the user address, generates an interface call request corresponding to the language type, and sends the interface call request to the business backend; the business backend searches for term assets matching the business identifier of the business end in the unified term platform based on the interface call request, determines a term group matching the language type based on the term assets, and obtains multiple terms of the business end under the language type; the business backend returns multiple terms to the business frontend; the business frontend searches for a target term matching the term identifier of the term to be queried from the multiple terms, and displays the target term.

[0013] In the embodiments of this application, the business side further includes a first local cache library, and the processing method further includes: after receiving multiple terms, the business front end caches the multiple terms in a hash format to the first local cache library for any functional module of the business front end to call.

[0014] In the embodiments of this application, the business side further includes a second local cache library, and the processing method further includes: after receiving the interface call request, the business backend determines whether there is a term under the language category in the second local cache library; if it is determined that there is a term under the language category in the second local cache library, the term is returned to the business frontend.

[0015] In the embodiments of this application, the business side further includes a second local cache library, and the processing method further includes: after the business backend obtains multiple entries, it caches the multiple entries in dictionary format to the second local cache library.

[0016] A second aspect of this application provides a term processing system, characterized in that it includes:

[0017] The business side and the unified entry platform are connected. The business side includes the business front-end and the business back-end. The business back-end establishes a long connection with the business front-end and the unified entry platform.

[0018] The business backend is configured as follows:

[0019] Detect whether the terms included in the term assets that match the business-side identifier in the unified term platform have been updated;

[0020] If an update is detected, the updated term is retrieved and returned to the business front end, where the updated term carries a term identifier;

[0021] The business frontend is configured as follows:

[0022] The updated term belongs to a specific functional module based on its identifier.

[0023] Update the corresponding entries in the identified functional modules using the updated entries;

[0024] The unified term platform is configured to generate term assets for the business side. The term assets include multiple term groups used by the business side. Each term group includes all terms of the business side in any supported language. Each term corresponds to a term identifier.

[0025] In embodiments of this application, the unified terminology platform is further configured to: obtain the language types supported by each business terminal and the multiple terms used in each language, and assign a corresponding business identifier to each business terminal; define the terminology identifier corresponding to each term; generate terminology groups for each language based on the multiple terms used in each language; and generate terminology assets for each business terminal based on the business identifier and terminology groups of each business terminal.

[0026] A third aspect of this application provides a machine-readable storage medium storing instructions that, when executed by a processor, configure the processor to perform the aforementioned processing method for the term.

[0027] The above technical solution involves a backend business system detecting whether there are updates to the terms in the unified term platform that match the business-side identifier. The unified term platform generates the business-side term assets, which include multiple term groups used by the business. Each term group includes all terms used by the business in any supported language, and each term corresponds to a term identifier. Upon detecting an update, the backend retrieves the updated term and returns it to the frontend, carrying the term identifier. The frontend determines the functional module to which the updated term belongs based on the term identifier. The frontend then uses the updated term to update the corresponding terms in the determined functional modules, thus achieving accurate and dynamic term updates.

[0028] Other features and advantages of the embodiments of this application will be described in detail in the following detailed description section. Attached Figure Description

[0029] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings:

[0030] Figure 1 The illustration shows an application environment diagram of a term processing method according to an embodiment of this application;

[0031] Figure 2 The illustration shows a flowchart of a term processing method according to an embodiment of this application;

[0032] Figure 3 The diagram illustrates the internal structure of a computer device according to an embodiment of this application. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for illustration and explanation of the embodiments of this application and are not intended to limit the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0034] Furthermore, if the embodiments of this application involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0035] The term processing method provided in this application can be applied to, for example... Figure 1 The application environment shown. Among them, such as... Figure 1 As shown, a term processing system is provided, including:

[0036] The business side and the unified entry platform are connected. The business side includes the business front-end and the business back-end. The business back-end establishes a long connection with the business front-end and the unified entry platform.

[0037] The business backend is configured as follows:

[0038] Detect whether the terms included in the term assets that match the business-side identifier in the unified term platform have been updated;

[0039] If an update is detected, the updated term is retrieved and returned to the business front end, where the updated term carries a term identifier;

[0040] The business frontend is configured as follows:

[0041] The updated term belongs to a specific functional module based on its identifier.

[0042] Update the corresponding entries in the identified functional modules using the updated entries;

[0043] The unified term platform is configured to generate term assets for the business side. The term assets include multiple term groups used by the business side. Each term group includes all terms of the business side in any supported language. Each term corresponds to a term identifier.

[0044] In this embodiment, it should be noted that a unified terminology platform is constructed specifically for managing all business-side terms. During business operation, the business frontend can establish a long-lived connection with the business backend. When the business backend detects changes in terms on the unified terminology platform, it proactively pushes the new terms to the business frontend. The business frontend updates the terminology content based on the term identifier. Furthermore, when the business frontend initiates a long-lived connection request to the business backend, it can carry language parameters. Subsequently, the business backend will only proactively push updated terms in that language to the business frontend. When the business backend starts, it retrieves all terms for that business's languages ​​from the unified terminology platform using the business identifier and caches them in local memory. Upon startup, the business backend also sends a long-lived connection request to the unified terminology platform. Subsequently, when changes occur in terms for that business on the unified terminology platform, it can proactively push the terms to the business backend. After receiving the updated term data pushed by the unified term platform, the backend updates the locally cached terms and pushes the new term information to the business frontend. If the language of the business frontend is the same as the language of this term update, it will be pushed; otherwise, it will not be pushed to the business frontend.

[0045] In this embodiment of the application, it also includes:

[0046] The unified terminology platform is configured as follows:

[0047] Obtain the number of languages ​​supported by each business unit and the multiple terms used in each language, and assign a corresponding business identifier to each business unit;

[0048] Define the term identifier corresponding to each term;

[0049] Generate word groups for each language based on multiple words used in each language;

[0050] Generate term assets for each business unit based on the business identifier and term group for each business unit.

[0051] In this embodiment, it should be noted that the unified terminology platform can be used to manage terms from all business units. The platform first provides a page for adding terms. Each term contains the following main information: Platform_id (the identifier of the business unit), language, id (terminology identifier), and content (terminology content). When saving terms, to speed up subsequent term queries, the unified terminology platform also stores terminology information in a remote dictionary service, Redis. The terminology storage format in Redis can be: hash format, with the key being the business unit identifier (platform_id) and the value being a hash format (where the key is the language and the value is the corresponding term list (including id and content)). The business unit identifier (platform_id) is assigned to each business unit when the unified terminology platform is created. The business unit configures this id in its own configuration, and the business unit id needs to be specified when querying terms from the unified terminology platform.

[0052] Figure 2 The illustration shows a flowchart of a term processing method according to an embodiment of this application. Figure 2 As shown in the embodiments of this application, a method for processing terms is provided, which can be applied to, for example... Figure 1 The business end shown includes a business front-end and a business back-end. The business back-end establishes a long connection with the business front-end and the unified entry platform. The processing method may include the following steps.

[0053] Step 201: The business backend checks whether there are any updates to the terms included in the term assets that match the business identifier in the unified term platform. The unified term platform is used to generate term assets for the business. The term assets include multiple term groups used by the business. Each term group includes all terms of the business in any supported language. Each term corresponds to a term identifier.

[0054] In this embodiment, it should be noted that the business identifier can refer to a business ID, and the term identifier can refer to a term ID. Each business terminal can support multiple languages, including but not limited to Chinese, English, and Japanese. The unified term platform can be used to manage all terms that can be used by all business terminals, and these terms involve any language supported by the business terminal. Since the unified term platform needs to manage terms from all business terminals, in order to distinguish different business terminals, the unified term platform can assign a specific business ID to each business terminal. In this way, when different business terminals access the unified term platform, the specific business terminal can be identified by the business ID carried. At the same time, after collecting all terms that can be used by each business terminal, the unified term platform can assign a term ID to each term based on the term ID corresponding to each term, and group all terms according to the language type corresponding to each term. Termlets of the same language type are grouped together, thereby obtaining multiple term groups, each term group corresponding to a language supported by a business terminal. After obtaining all term groups, these term groups are bound to the business ID of the business terminal to generate term assets unique to each business terminal.

[0055] It should be noted that, since the business backend establishes long connections with both the business frontend and the unified term platform, the business backend can detect whether there are any updates to the terms included in the term assets in the unified term platform that match the business frontend identifier.

[0056] In this embodiment of the application, the processing method further includes updating at least one of term modification, term deletion, and term addition.

[0057] In this embodiment, it should be noted that the business backend, based on a long connection, can detect whether there are updates to the terms included in the term assets matching the business terminal identifier in the unified term platform. Updates can include term modification, term deletion, and term addition. It should also be noted that when a term is added, the term ID can be manually set or dynamically generated, such as using a UUID or an auto-incrementing field from the database. When the business frontend uses this, for example, if a functional module needs to add a term, it can add the new term on the unified term platform, then save the new term ID, and subsequently retrieve the corresponding term content using this ID and display it on the functional module.

[0058] In this embodiment of the application, the processing method further includes: the business backend receiving a first SSE long connection request initiated by the business frontend, wherein the first SSE long connection request carries at least one language parameter; the business backend responding to the first SSE long connection request to establish a long connection with the business frontend; the business backend initiating a second SSE long connection request to the unified term platform, and establishing a long connection with the unified term platform if it is determined that the unified term platform responds to the second SSE long connection request.

[0059] In this embodiment, it should be noted that the long connection refers to an SSE long connection, which is an HTTP-based long connection technology that allows the server to proactively push real-time updates to the client. SSE creates a persistent HTTP connection over which the server can continuously send new data blocks, referred to as "events." The client initiates a request by creating an EventSource object and pointing it to a URL on the server. This request remains open, allowing the server to continuously send new data blocks over this single TCP connection. Each event includes a type (optional), data, and some metadata (such as event ID, reconnection time interval, etc.). Specifically, in this technical solution, to enable the business backend to push updated terms to the business frontend in real time when terms are updated, the business frontend can initiate an SSE long connection request to the business backend. The business backend responds to this SSE long connection request by proactively pushing updated terms to the business frontend. The SSE long connection request initiated by the business frontend to the business backend can carry a language parameter, so that the business backend will only push updated terms in the specified language to the business frontend. Meanwhile, the business backend can initiate an SSE long connection request to the unified term platform. When the unified term platform responds to the SSE long connection request, it can proactively push the term to the business backend when the term is updated.

[0060] Step 202: When the business backend detects an update, it retrieves the updated term and returns the updated term to the business frontend, wherein the updated term carries a term identifier.

[0061] In this embodiment of the application, it should be noted that each term in the unified term platform corresponds to a term ID. When the business backend detects an update in the unified term platform based on the SSE long connection, it obtains the updated term and can return the updated term to the business frontend based on the SSE long connection.

[0062] Step 203: The business front end determines the functional module to which the updated term belongs based on the term identifier.

[0063] In this embodiment, it should be noted that the business front-end may include multiple functional modules, each module can use multiple terms, and each term in each functional module corresponds to a term ID. For any given term, the term ID in the functional module should be the same as the term ID in the unified term platform. Therefore, after the business front-end receives the updated term returned by the business back-end, it can find the functional module to which the updated term belongs based on the term identifier.

[0064] Step 204: The business front-end uses the updated terms to update the corresponding terms in the determined functional modules.

[0065] In this embodiment of the application, it should be noted that after the business front end finds the functional module to which the updated term belongs based on the term identifier, it can push the updated term to the functional module so that the updated term can be used to update the corresponding term in the functional module.

[0066] The above technical solution detects whether there are any updates to the terms included in the term assets that match the business terminal identifier in the unified term platform through the business backend. When an update is detected, the business backend obtains the updated term and returns it to the business frontend. The business frontend determines the functional module to which the updated term belongs based on the term identifier and uses the updated term to update the corresponding term in the determined functional module, thereby achieving accurate and dynamic updates of terms.

[0067] In this embodiment, the processing method further includes: when the business front-end receives a term query request triggered by a user carrying a term to be queried, it obtains the user's address; the business front-end determines the language type corresponding to the user address, generates an interface call request corresponding to the language type, and sends the interface call request to the business back-end; the business back-end searches for term assets matching the business identifier of the business end in the unified term platform based on the interface call request, determines the term group matching the language type based on the term assets, and obtains multiple terms of the business end under the language type; the business back-end returns multiple terms to the business front-end; the business front-end searches for the target term matching the term identifier of the term to be queried from the multiple terms, and displays the target term.

[0068] In this embodiment, it should be noted that the user address can refer to the user's IP address. When a user accesses the service, they can interact through the service front-end to trigger a query request carrying the term to be queried. After receiving the query request, the service front-end can identify the language used by the user's location by obtaining the user's current IP address. For example, if the user's IP address is located in Hunan, the language used by the Hunan IP address can be identified as Chinese.

[0069] After determining the language type, the business frontend can generate an API call request corresponding to that language type and send it to the business backend. The business backend responds to this API call request by first searching the unified terminology platform for term assets that match the business ID of the business. These term assets include term groups built for each language supported by the business. Therefore, through further language matching, a term group matching that language type can be obtained. The multiple terms included in this term group are the terms belonging to that language type. The business backend can then return these multiple terms to the business frontend. Upon receiving these terms, the business frontend, based on the term ID, searches through the multiple terms to find the target term that matches the term ID of the term the user is querying, and then displays the target term to the user.

[0070] In this embodiment of the application, the business side also includes a first local cache library, and the processing method further includes: after receiving multiple terms, the business front end caches the multiple terms in a hash format to the first local cache library for any functional module of the business front end to call.

[0071] In this embodiment, it should be noted that the hash format can refer to a hash format, which is a set of key-value pairs. In this technical solution, the key is the term ID, and the value is the term content. The business side also includes a first local cache library for data calls by the business frontend. All terms received by the business frontend can be cached in this first local cache library to improve the response speed of the business frontend. Specifically, after receiving multiple terms returned by the business backend, the business frontend can cache the multiple terms in hash format in the first local cache library for quick access by any functional module of the business frontend.

[0072] In this embodiment of the application, the business side also includes a second local cache library, and the processing method further includes: after receiving the interface call request, the business backend determines whether there is a term under the language category in the second local cache library; if it is determined that there is a term under the language category in the second local cache library, the term is returned to the business frontend.

[0073] In this embodiment, it should be noted that the business side also includes a second local cache library for data calls by the business backend. All terms received by the business backend can be cached in this second local cache library to improve the response speed of the business backend. Specifically, after receiving an interface call request sent by the business frontend, the business backend can first determine whether there are terms in the second local cache library that belong to the language type used by the user's IP address. If there are terms in the second local cache library that belong to that language type, these terms can be returned to the business frontend first. If there are no terms in the second local cache library that belong to that language type, then they are retrieved from the unified term platform.

[0074] In this embodiment of the application, the business side also includes a second local cache library, and the processing method further includes: after the business backend obtains multiple entries, it caches the multiple entries in dictionary format to the second local cache library.

[0075] In this embodiment, it should be noted that the dictionary format can refer to a set of key-value pairs. In this technical solution, the key is the term ID, and the value is the term content. Specifically, after the business backend obtains multiple terms from the unified term platform, it can cache the multiple term key-value pairs in a second local cache library for the business frontend to quickly access.

[0076] This technical solution uses a unified term management platform to manage terms, eliminating the need for each business system to develop its own term management page, reducing code development workload, and facilitating term management and modification by product managers. It leverages SSE technology to achieve real-time term updates; when a term needs modification, there's no need to redeploy the backend and frontend services, ensuring the term takes effect immediately. For example, adding support for a new language doesn't require redeploying services or software; the language can be added directly to the term management platform, taking effect instantly. Finally, it features dynamic frontend term updates. Unlike traditional methods that require redeploying the frontend or developing multi-language pages, this solution eliminates the need for frontend redeployment, supporting dynamic real-time updates of frontend terms.

[0077] This application provides a machine-readable storage medium storing instructions that, when executed by a processor, configure the processor to perform the aforementioned term processing method.

[0078] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 3As shown. The computer device includes a processor A01, a network interface A02, memory (not shown), and a database (not shown) connected via a system bus. The processor A01 provides computing and control capabilities. The memory includes internal memory A03 and a non-volatile storage medium A04. The non-volatile storage medium A04 stores an operating system B01, a computer program B02, and a database (not shown). The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 stored in the non-volatile storage medium A04. The database stores data on term processing methods. The network interface A02 communicates with external terminals via a network connection. When the computer program B02 is executed by the processor A01, it implements a term processing method.

[0079] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0080] This application provides an apparatus, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps of a term processing method.

[0081] This application also provides a computer program product, which, when executed on a data processing device, is adapted to perform the processing method steps for initializing entries.

[0082] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can 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, etc.) containing computer-usable program code.

[0083] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can 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, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0084] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0085] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0087] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

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

[0089] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0090] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for processing entries, characterized in that, Applied to the business side, the business side includes a business front-end and a business back-end, the business back-end establishes a long connection with the business front-end and the unified terminology platform, and the processing method includes: The business backend detects whether the terms included in the term assets that match the business end identifier in the unified term platform have been updated. The unified term platform is used to generate term assets for the business end. The term assets include multiple term groups used by the business end. Each term group includes all terms of the business end in any supported language. Each term corresponds to a term identifier. When the business backend detects an update, it retrieves the updated term and returns the updated term to the business frontend, wherein the updated term carries a term identifier; The business front-end determines the functional module to which the updated term belongs based on the term identifier; The business front-end uses the updated terms to update the corresponding terms in the determined functional modules.

2. The processing method according to claim 1, characterized in that, The processing method further includes: The business backend receives a first SSE long connection request initiated by the business frontend, wherein the first SSE long connection request carries at least one language parameter. The business backend responds to the first SSE long connection request to establish a long connection with the business frontend; The business backend initiates a second SSE long connection request to the unified term platform, and establishes a long connection with the unified term platform if the unified term platform responds to the second SSE long connection request.

3. The processing method according to claim 1, characterized in that, The processing method further includes: The update includes at least one of the following: entry modification, entry deletion, and entry addition.

4. The processing method according to claim 1, characterized in that, The processing method further includes: When the business front-end receives a term query request triggered by a user, carrying the term to be queried, it obtains the user's address. The business front end determines the language type corresponding to the user address, generates an interface call request corresponding to the language type, and sends the interface call request to the business back end; The business backend searches for term assets that match the business identifier of the business end in the unified term platform based on the interface call request, so as to determine the term group that matches the language type based on the term assets, and obtain multiple terms of the business end under the language type; The business backend returns the multiple terms to the business frontend; The business front end searches for target terms that match the term identifier of the term to be queried from the multiple terms, and then displays the target terms.

5. The processing method according to claim 4, characterized in that, The business unit also includes a first local cache library, and the processing method further includes: After receiving the multiple terms, the business front-end caches the multiple terms in a hash format in the first local cache library for use by any functional module of the business front-end.

6. The processing method according to claim 4, characterized in that, The business unit also includes a second local cache library, and the processing method further includes: After receiving the interface call request, the business backend determines whether there is a term in the second local cache library that belongs to the language category; If it is determined that a term belonging to the specified language exists in the second local cache library, the term is returned to the business front end.

7. The processing method according to claim 4, characterized in that, The business unit also includes a second local cache library, and the processing method further includes: After obtaining the multiple terms, the business backend caches the multiple terms in dictionary format to the second local cache library.

8. A term processing system, characterized in that, include: The business side and the unified term platform, wherein the business side includes a business front-end and a business back-end, and the business back-end establishes a long connection with the business front-end and the unified term platform; The business backend is configured as follows: Detect whether the terms included in the term assets that match the business terminal identifier in the unified term platform have been updated; If an update is detected, the updated term is retrieved and returned to the business front end, wherein the updated term carries a term identifier; The business front-end is configured as follows: The updated term belongs to a specific functional module based on the term identifier. The updated terms are used to update the corresponding terms in the determined functional modules; the unified term platform is configured to generate term assets for the business side, the term assets include multiple term groups used by the business side, each term group includes all terms of the business side in any supported language, and each term corresponds to a term identifier.

9. The term processing system according to claim 8, characterized in that, Also includes: The unified terminology platform is configured as follows: Obtain the number of languages ​​supported by each business unit and the multiple terms used in each language, and assign a corresponding business identifier to each business unit; Define the term identifier corresponding to each term; Generate word groups for each language based on multiple words used in each language; Generate term assets for each business unit based on the business identifier and term group for each business unit.

10. A machine-readable storage medium storing instructions thereon, characterized in that, When executed by a processor, this instruction causes the processor to be configured to perform the processing method for the term according to any one of claims 1 to 8.

Images