Grayscale resource rendering method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a gray resource rendering method and device, electronic equipment and a storage medium, and is applied to the technical field of resource processing, the method comprises the following steps: receiving starting information of an application sent by a client, the starting information carrying a user identifier of a user; when the user identifier is in a preset user identifier set, sending gray resource standard template construction information to the client; when it is detected that the application meets a preset gray resource rendering condition, obtaining a target gray resource corresponding to the user identifier; and controlling the client to construct a gray-scale resource standard template according to the gray-scale resource standard template construction information, and performing gray-scale resource rendering in the gray-scale resource standard template according to the target gray-scale resource. By uniformly sending the gray resource standard template construction information to the client, the client is guided to construct the gray resource standard template specially used for the gray test, so that the gray function abnormality is avoided, and the adaptability of the gray resource at the client is improved.

Description

Technical Field

[0001] The present application relates to the field of resource processing technology, and in particular to a grayscale resource rendering method, device, electronic device and storage medium. Background Art

[0002] With the rapid development of society, the iteration and update of applications are becoming more and more frequent. To ensure the running stability of applications, before releasing the official version of the update, it is necessary to use grayscale release to allow a small number of users to use the new version of the application in advance to facilitate version testing.

[0003] In the related technology, there is a lack of perception mechanism for front-end cache resources, and it is impossible to accurately identify which resources are cached in the front-end application. As a result, it is difficult to determine which front-end resources need to be updated to adapt to the grayscale version during grayscale release. It is also difficult to control the timing and method of updating cached resources, resulting in abnormalities in certain grayscale functions. Therefore, it is urgent to provide a grayscale resource rendering method to solve the above technical problems. Summary of the invention

[0004] The main purpose of the embodiments of the present application is to propose a grayscale resource rendering method, device, electronic device and storage medium, which uniformly sends grayscale resource standard template construction information to the client to guide the client to construct a grayscale resource standard template specifically for grayscale testing, instead of using the resources cached by the client to render the grayscale resources, thereby avoiding grayscale function abnormalities and improving the adaptability of grayscale resources on the client.

[0005] To achieve the above object, a first aspect of an embodiment of the present application provides a grayscale resource rendering method, the method comprising:

[0006] Receiving application startup information sent by a client, wherein the startup information carries a user identifier of a user;

[0007] When the user identifier is in a preset user identifier set, sending grayscale resource standard template construction information to the client;

[0008] When it is detected that the application meets the preset grayscale resource rendering condition, obtaining the target grayscale resource corresponding to the user identifier;

[0009] The client is controlled to construct a grayscale resource standard template according to the grayscale resource standard template construction information, and grayscale resource rendering is performed in the grayscale resource standard template according to the target grayscale resource.

[0010] In some embodiments, when it is detected that the application meets a preset grayscale resource rendering condition, obtaining the target grayscale resource corresponding to the user identifier includes:

[0011] Receiving a page access request for the application sent by the client, and determining a target access page requested by the page access request;

[0012] When the target access page is a preset access page, determining that the application meets a preset grayscale resource rendering condition;

[0013] Obtain the target grayscale resource corresponding to the user identifier.

[0014] In some embodiments, the method further comprises:

[0015] Receiving a function control request for the application sent by the client, and determining a target function requested to be controlled by the function control request;

[0016] When the target function is a preset function, determining that the application meets a preset grayscale resource rendering condition;

[0017] Obtain the target grayscale resource corresponding to the user identifier.

[0018] In some embodiments, after performing grayscale resource rendering in the grayscale resource standard template according to the target grayscale resource, the method further includes:

[0019] receiving a function implementation request sent by the client, wherein the function implementation request carries a target grayscale version identifier, and the function implementation request is a request generated by the client in response to a control operation on a rendered target grayscale resource;

[0020] Determine the target function implementation interface corresponding to the target gray version identifier based on a preset mapping relationship between the gray version identifier and the function implementation interface;

[0021] The target function implementation interface is called to process the function implementation request.

[0022] In some embodiments, after controlling the client to construct the grayscale resource standard template according to the grayscale resource standard template construction information, the method further includes:

[0023] Receive build exception information, where the build exception information carries an exception code, the user identifier, and a system identifier of the client;

[0024] Determine the grayscale code missing from the client according to the abnormal code and the system identifier;

[0025] A mapping relationship between the grayscale code and the user identifier is established.

[0026] In some embodiments, when the user identifier is in a preset user identifier set, sending grayscale resource standard template construction information to the client includes:

[0027] When the user identifier is in a preset user identifier set and it is not the first time to receive the startup information carrying the user identifier, determining whether a target grayscale code having a preset mapping relationship with the user identifier is stored;

[0028] When a target grayscale code having a preset mapping relationship with the user identifier is stored, sending the target grayscale code to the client;

[0029] The controlling the client to construct a grayscale resource standard template according to the grayscale resource standard template construction information includes:

[0030] The client is controlled to construct a grayscale resource standard template according to the saved grayscale code and the target grayscale code.

[0031] In some embodiments, when the user identifier is in a preset user identifier set, sending grayscale resource standard template construction information to the client includes:

[0032] When the user identifier is in a preset user identifier set and when the startup information carrying the user identifier is received for the first time, grayscale resource standard template construction information is sent to the client.

[0033] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application proposes a grayscale resource rendering device, comprising:

[0034] A receiving unit, configured to receive application startup information sent by a client, wherein the startup information carries a user identifier of a user;

[0035] A sending unit, configured to send grayscale resource standard template construction information to the client when the user identifier is in a preset user identifier set;

[0036] An acquisition unit, configured to acquire a target grayscale resource corresponding to the user identifier when it is detected that the application meets a preset grayscale resource rendering condition;

[0037] A rendering unit is used to control the client to construct a grayscale resource standard template according to the grayscale resource standard template construction information, and to render grayscale resources in the grayscale resource standard template according to the target grayscale resource.

[0038] In some embodiments, the acquisition unit includes:

[0039] A first determining subunit is used to receive a page access request for the application sent by the client, and determine a target access page requested by the page access request;

[0040] A second determining subunit is used to determine that the application meets a preset grayscale resource rendering condition when the target access page is a preset access page;

[0041] The first acquisition subunit is used to acquire the target grayscale resource corresponding to the user identifier.

[0042] In some embodiments, the acquisition unit includes:

[0043] A third determining subunit is configured to receive a function control request for the application sent by the client, and determine a target function requested to be controlled by the function control request;

[0044] A fourth determining subunit, configured to determine, when the target function is a preset function, whether the application satisfies a preset grayscale resource rendering condition;

[0045] The second acquisition subunit is used to acquire the target grayscale resource corresponding to the user identifier.

[0046] In some embodiments, the apparatus is further configured to:

[0047] receiving a function implementation request sent by the client, wherein the function implementation request carries a target grayscale version identifier, and the function implementation request is a request generated by the client in response to a control operation on a rendered target grayscale resource;

[0048] Determine the target function implementation interface corresponding to the target gray version identifier based on a preset mapping relationship between the gray version identifier and the function implementation interface;

[0049] The target function implementation interface is called to process the function implementation request.

[0050] In some embodiments, the apparatus is further configured to:

[0051] Receive build exception information, where the build exception information carries an exception code, the user identifier, and a system identifier of the client;

[0052] Determine the grayscale code missing from the client according to the abnormal code and the system identifier;

[0053] A mapping relationship between the grayscale code and the user identifier is established.

[0054] In some embodiments, the sending unit includes:

[0055] A third determination subunit is used to determine whether a target grayscale code having a preset mapping relationship with the user identifier is stored when the user identifier is in a preset user identifier set and it is not the first time that the startup information carrying the user identifier is received;

[0056] A first sending subunit is used to send the target grayscale code to the client when a target grayscale code having a preset mapping relationship with the user identifier is stored;

[0057] Rendering units, used to:

[0058] The client is controlled to construct a grayscale resource standard template according to the saved grayscale code and the target grayscale code.

[0059] In some embodiments, the sending unit includes:

[0060] The second sending subunit is used to send grayscale resource standard template construction information to the client when the user identifier is in a preset user identifier set and the startup information carrying the user identifier is received for the first time.

[0061] To achieve the above objectives, a third aspect of an embodiment of the present application proposes an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the method described in the first aspect is implemented.

[0062] To achieve the above-mentioned purpose, the fourth aspect of an embodiment of the present application proposes a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in the first aspect is implemented.

[0063] The grayscale resource rendering method, device, electronic device and storage medium proposed in the present application receive the startup information of the application sent by the client, and the startup information carries the user ID of the user; when the user ID is in the preset user ID set, the grayscale resource standard template construction information is sent to the client; when it is detected that the application meets the preset grayscale resource rendering conditions, the target grayscale resource corresponding to the user ID is obtained; the client is controlled to construct a grayscale resource standard template according to the grayscale resource standard template construction information, and grayscale resource rendering is performed in the grayscale resource standard template according to the target grayscale resource. In this way, by uniformly sending the grayscale resource standard template construction information to the client, the client is guided to construct a grayscale resource standard template specifically for grayscale testing, instead of using the client cached resources to render grayscale resources, thereby avoiding grayscale function abnormalities and improving the adaptability of grayscale resources on the client. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Figure 1 is a flowchart of a grayscale resource rendering method provided in an embodiment of the present application;

[0065] Figure 2 yes Figure 1 Flow chart of step S103 in FIG.

[0066] Figure 3 yes Figure 1 Flow chart of step S103 in FIG.

[0067] Figure 4 is another flow chart of the grayscale resource rendering method provided in an embodiment of the present application;

[0068] Figure 5 is another flow chart of the grayscale resource rendering method provided in an embodiment of the present application;

[0069] Figure 6 yes Figure 1 Flowchart of step S102 and step S104 in FIG. 1 ;

[0070] Figure 7 yes Figure 1 Flow chart of step S102 in FIG.

[0071] Figure 8 is a structural diagram of a grayscale resource rendering device provided in an embodiment of the present application;

[0072] Fig. 9 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0073] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0074] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0075] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0076] First, some nouns involved in this application are analyzed:

[0077] Grayscale resources: refers to the specific resources involved in the grayscale release process of the software system. In grayscale release, in order to reduce risks and gradually verify the effects of new functions or changes, the new version will not be pushed to all users, but some users will be selected for trial first. These resources displayed to specific user groups are grayscale resources. Grayscale resources are a collection of resources specially prepared for specific user groups during the grayscale release process to display and test new functions or changes. It includes both the front-end user interface and interactive elements, as well as the back-end data and service configuration.

[0078] 1. Front-end:

[0079] User interface elements: may include specific page layouts, new function buttons, unique visual styles, etc. For example, in a grayscale release of an e-commerce application, the grayscale resource may be a newly designed product details page with clearer image display and more convenient purchase process buttons.

[0080] The purpose of these front-end resources is to provide users participating in the grayscale test with a different user experience from the old version, while collecting their feedback for further optimization.

[0081] Scripts and interactive logic: Grayscale resources can contain specific JavaScript scripts to implement new interactive features. For example, when a social platform releases a new message reminder function in grayscale, there may be a dedicated script responsible for processing and displaying the new reminder method. These scripts ensure that users can trigger and experience new features when interacting with the application, while not affecting the normal use of non-grayscale users.

[0082] 2. Backend

[0083] Data and APIs:

[0084] Backend grayscale resources may include specific data sets or API interfaces. For example, when an online education platform is grayscale testing a new course recommendation algorithm, it will provide course recommendation data generated based on the new algorithm to users participating in the grayscale test, and return it to the frontend for display through a specific API interface.

[0085] These data and APIs are designed to support the implementation of new features while ensuring that they can be effectively monitored and adjusted during the grayscale testing phase.

[0086] Service Configuration:

[0087] Backend grayscale resources may also involve adjusting service configuration parameters. For example, in order to improve the response speed of grayscale users, you can adjust the server's load balancing strategy or database query optimization parameters.

[0088] These configuration adjustments are intended to provide better performance and experience for grayscale users without affecting the overall system stability.

[0089] Grayscale resource standard template construction information: including HTML templates for display pages within the application, CSS style sheets for beautifying the interface, and JavaScript scripts for processing user interactions. Grayscale resources may be additional HTML fragments for specific functions, specific CSS style adjustments, or new JavaScript function modules.

[0090] Based on this, the embodiments of the present application provide a grayscale resource rendering method, device, electronic device and storage medium, aiming to avoid grayscale function abnormalities and improve the adaptability of grayscale resources on the client.

[0091] The grayscale resource rendering method, device, electronic device and storage medium provided in the embodiments of the present application are specifically described through the following embodiments. First, the grayscale resource rendering method in the embodiments of the present application is described.

[0092] The grayscale resource rendering method provided in the embodiment of the present application relates to the field of data processing technology. The grayscale resource rendering method provided in the embodiment of the present application can be applied to a terminal, can be applied to a server side, or can be software running in a terminal or a server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or can be configured as a server cluster or a distributed system composed of multiple physical servers, or can be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the grayscale resource rendering method, etc., but is not limited to the above forms.

[0093] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0094] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0095] Figure 1 is an optional flowchart of the grayscale resource rendering method provided in an embodiment of the present application. Figure 1 The method may include but is not limited to steps S101 to S104.

[0096] Step S101: receiving application startup information sent by a client, where the startup information carries a user ID of a user.

[0097] The startup information is information generated when the user touches and starts the application in the client and the application is initialized. The front-end module in the client triggers the relevant interface of the server and sends the startup information to the server.

[0098] Specifically, the client sends a startup message to the server to indicate that the application is about to start running. This message usually contains some basic context information, such as the application version number, device information, etc., and the most important of which is the user ID of the user. The startup message carries the user ID of the user, which is information used to uniquely identify the user, such as the user name, user ID, etc.

[0099] During the startup process, the client obtains the user ID in various ways. If the user has logged in, the user ID can be obtained from local storage or the verification response of the server; if the user has not logged in, the unique identifier of the device can be used or a temporary user ID can be generated.

[0100] The client includes the collected user ID in the startup information and sends it to the server through a network request. This request can use the HTTP protocol or other suitable communication protocols.

[0101] Step S102: When the user identifier is in the preset user identifier set, grayscale resource standard template construction information is sent to the client.

[0102] Among them, in the grayscale resource preparation and release stage, the developer will set at least one user identification set in the server in advance. The user corresponding to each user identification in these user identification sets is selected to participate in the grayscale release. The selection strategy can be determined based on a specific strategy and target user group. After the server receives the startup information from the client, it extracts the user identification therein and compares it with the preset user identification set. If the user identification is in the set, it means that the user is selected to participate in the grayscale release.

[0103] Specifically, if the user is in the preset user identification set, the server prepares grayscale resource standard template construction information. The grayscale resource standard template construction information may include generating a JSON object or other data format containing information such as a template file address, a style sheet link, and a script file reference. The server sends the prepared grayscale resource standard template construction information back to the client as a response. After receiving this information, the client can first save the constructed grayscale resource standard template for subsequent rendering of grayscale resources.

[0104] Step S103, when it is detected that the application meets the preset grayscale resource rendering condition, the target grayscale resource corresponding to the user identifier is obtained.

[0105] The preset grayscale resource rendering conditions are specific trigger conditions. When the application meets these conditions, the server will obtain and send the target grayscale resources to the client. These conditions can be specific operations of the user, page loading events, time points, etc. The target grayscale resources are grayscale resources specific to the user determined according to the user identifier, and can include new functional modules, data sets, interface layouts, etc.

[0106] Specifically, the server continuously monitors the status of the application to determine whether the preset grayscale resource rendering conditions are met. For example, the server can monitor the user's page browsing events, button click events, etc., or check according to time intervals. When it is detected that the rendering conditions are met, the server obtains the target grayscale resources corresponding to the user from the database or other storage according to the user ID. This may involve querying a specific data set, calling a specific API, or reading a configuration file. The server organizes and packages the acquired target grayscale resources so that they can be easily sent to the client. If the resources are large, you can consider sending them in batches or using compression technology to reduce the amount of data transmitted.

[0107] Step S104 , controlling the client to construct a grayscale resource standard template according to the grayscale resource standard template construction information, and performing grayscale resource rendering in the grayscale resource standard template according to the target grayscale resource.

[0108] The grayscale resource standard template is a template for displaying grayscale resources that is constructed based on the construction information provided by the server. It has a specific structure and style, and can accommodate the target grayscale resource and display it to the user.

[0109] Specifically, the server controls the client to download the required resource files (such as template files, style sheets, script files, etc.) according to the instructions in the build information, and use the front-end development framework (such as React, Vue.js, etc.) to build the grayscale resource standard template. This may involve operations such as creating an HTML structure, applying CSS styles, and loading JavaScript scripts. The server fills the acquired target grayscale resources into the constructed grayscale resource standard template for rendering. This can be achieved by binding data to specific elements in the template, calling script functions for dynamic updates, etc. In the end, the user sees the rendered grayscale resources on the client and experiences new functions or interface changes.

[0110] Steps S101 to S104 shown in the embodiment of the present application are as follows: receiving the startup information of the application sent by the client, wherein the startup information carries the user ID of the user; when the user ID is in the preset user ID set, sending the grayscale resource standard template construction information to the client; when it is detected that the application meets the preset grayscale resource rendering conditions, obtaining the target grayscale resource corresponding to the user ID; controlling the client to construct the grayscale resource standard template according to the grayscale resource standard template construction information, and rendering the grayscale resource in the grayscale resource standard template according to the target grayscale resource. In this way, by uniformly sending the grayscale resource standard template construction information to the client, the client is guided to construct a grayscale resource standard template specifically for grayscale testing, without using the client cached resources to render the grayscale resources, thereby avoiding grayscale function abnormalities and improving the adaptability of grayscale resources on the client.

[0111] See also Figure 2 In some embodiments, step S103 may include but is not limited to steps S201 to S203:

[0112] Step S201: receiving a page access request for the application sent by the client, and determining a target access page requested by the page access request.

[0113] When a user operates an application on a client (which can be a mobile application, web browser, etc.), such as clicking a link, entering a URL, or selecting a page through a navigation menu, the client sends a page access request to the server. This request usually contains some information, such as the requested URL, request method (such as GET, POST, etc.), user session information (if any), etc.

[0114] For example, when a user clicks a link to a "product details" page in an e-commerce application, the client sends a request to the server for the product details page.

[0115] Specifically, after receiving the page access request sent by the client, the server will parse the request. The server software (such as a Web server, an application server, etc.) will read the information in the request and determine the target page of the request.

[0116] For example, by parsing the requested URL, the server can determine which specific page the user is requesting to access. If the URL is " / product / detail / 123", the server can determine that the user is requesting to access the product details page with product number 123.

[0117] Step S202: When the target access page is a preset access page, it is determined that the application meets a preset grayscale resource rendering condition.

[0118] Among them, developers will pre-set some specific pages on the server side as pages that may trigger grayscale resource rendering. These preset access pages are usually pages related to new features, changes or tests.

[0119] For example, in a grayscale release of an online education platform, a new course learning page, a homework submission page for a specific course, etc. may be set as the preset access page.

[0120] Specifically, when the server determines the target access page requested by the client, it will compare it with the preset access page. If the target access page matches the preset access page, it is considered that the application meets the preset grayscale resource rendering conditions.

[0121] For example, if the page requested by the user is a new course learning page, and this page happens to be one of the preset access pages, the server will determine that the application meets the preset grayscale resource rendering conditions.

[0122] Step S203, obtaining the target grayscale resource corresponding to the user identifier.

[0123] In the process of processing page access requests, the server can extract user identification information from the request. If the user is logged in, the user identification may be obtained through session information or the authentication token in the request header; if the user is not logged in, a temporary user identification may be generated based on the client's IP address, device information, etc.

[0124] For example, the server may read the user ID from the requested session information as the user identifier.

[0125] Specifically, after determining the user identifier, the server can query the corresponding target grayscale resource based on this identifier. This usually involves obtaining grayscale resource data specific to the user from a database, cache, or other storage. The server organizes and prepares the obtained target grayscale resources so that they can be sent to the client for rendering. If the resources are large, you can consider sending them in batches or using compression technology to reduce the amount of data transmitted.

[0126] For example, the server can query the database for target grayscale resources such as specific course content and personalized interface layout that the user should see during the grayscale release period based on the user ID. The server packages the target grayscale resources into a suitable data format (such as JSON, XML, etc.) and returns them to the client as a response. After receiving these resources, the client can render them on the page and display them to the user.

[0127] In this way, developers can accurately select specific pages as preset access pages based on business needs and test objectives. This ensures that grayscale resource rendering is triggered only on key pages related to new features, changes, or tests, avoiding unnecessary resource waste and excessive interference with user experience. And by determining the target grayscale resources through user identification, grayscale releases can be personalized for different user groups. Not only can more sophisticated traffic control be achieved, but also a customized grayscale experience can be provided based on specific user attributes (such as user behavior, preferences, levels, etc.).

[0128] See also Figure 3 In some embodiments, step S103 may include but is not limited to steps S301 to S303:

[0129] Step S301: receiving a function control request for the application sent by the client, and determining a target function to be controlled by the function control request.

[0130] When a user interacts with an application on a client (such as a mobile app or web browser), a control request for a specific function may be triggered. For example, a user clicks a button to activate a specific function module, or starts a specific service through a menu selection. The client sends this function control request to the server. The request usually contains some information, such as the type of request (for example, whether to turn the function on or off), related parameters (if any), and the user's session information.

[0131] Specifically, after receiving the function control request sent by the client, the server will parse the request. The server software will read the information in the request to determine the target function requested by the user.

[0132] For example, if the request is for a "collaborative editing" function in an online document editing application, the server can determine that the target function is "collaborative editing" by parsing a specific identifier or parameter in the request. Step S302: When the target function is a preset function, determine that the application meets the preset grayscale resource rendering condition.

[0133] Among them, developers pre-set some specific functions on the server side as functions that may trigger grayscale resource rendering. These preset functions are usually newly launched functions, functions that are being tested or optimized.

[0134] For example, in the grayscale release of an online music platform, the function of "personalized recommendation algorithm upgrade" may be set as a preset function.

[0135] Specifically, when the server determines the target function requested by the client, it will compare it with the preset function. If the target function matches the preset function, it is considered that the application meets the preset grayscale resource rendering conditions.

[0136] For example, if the function requested by the user is "personalized recommendation algorithm upgrade", and this function happens to be one of the preset functions, the server will determine that the application meets the preset grayscale resource rendering conditions.

[0137] Step S303, obtaining the target grayscale resource corresponding to the user identifier.

[0138] In the process of processing the function control request, the server can extract the user identification information from the request. If the user is logged in, the user identification may be obtained through the session information or the authentication token in the request header; if the user is not logged in, a temporary user identification may be generated based on the client's IP address, device information, etc.

[0139] For example, the server may read the user ID from the requested session information as the user identifier.

[0140] After determining the user ID, the server can query the corresponding target grayscale resource based on this ID. This usually involves obtaining grayscale resource data specific to the user from a database, cache, or other storage. The server organizes and prepares the obtained target grayscale resources so that they can be sent to the client for rendering. If the resources are large, you can consider sending them in batches or using compression technology to reduce the amount of data transmitted.

[0141] For example, if the target function is "personalized recommendation algorithm upgrade", the server can query the database for target grayscale resources such as the personalized recommendation list that the user should see during the grayscale release based on the user ID. The server packages the target grayscale resources into a suitable data format (such as JSON, XML, etc.) and returns it to the client as a response. After the client receives these resources, it can display the corresponding grayscale resources in the application so that users can experience new functions or changes.

[0142] In this way, by presetting specific functions as conditions for triggering grayscale resource rendering, you can focus on testing newly launched or optimized functions. This allows the development team to more accurately evaluate the performance, stability, and user acceptance of new functions without affecting other parts of the entire application. Obtaining target grayscale resources based on user identification can provide different users with personalized new function experiences. This helps meet the needs and preferences of different users and improve user satisfaction.

[0143] See also Figure 4In some embodiments, the grayscale resource rendering method may also include but is not limited to steps S401 to S403:

[0144] Step S401 : receiving a function implementation request sent by the client, wherein the function implementation request carries a target grayscale version identifier and is a request generated by the client in response to a control operation on a rendered target grayscale resource.

[0145] When the user performs a control operation on the rendered target grayscale resource on the client, the client generates a function implementation request. This control operation can be various behaviors of interacting with the target grayscale resource, such as clicking a button, sliding the screen, and entering text.

[0146] For example, in an image editing application with a new grayscale version function, when a user applies a filter effect newly added to the grayscale version, the client will respond to this operation by generating a function implementation request. This request carries the target grayscale version identifier, which is used by the server to identify the grayscale version corresponding to the request.

[0147] Specifically, the client sends the generated function implementation request to the server. This request can be sent over a network connection, usually using HTTP or other suitable communication protocols. After receiving the function implementation request sent by the client, the server prepares to process it. The server will first parse the request and extract key information such as the target grayscale version identifier.

[0148] For example, the client uses a POST request to send a function implementation request to a specific interface address of the server. For example, the server software reads the content of the request, identifies the target grayscale version identifier carried in the request, and prepares for subsequent processing steps.

[0149] Step S402: determining a target function implementation interface corresponding to the target gray version identifier based on a preset mapping relationship between the gray version identifier and the function implementation interface.

[0150] On the server side, developers pre-set the mapping relationship between the gray version identifier and the function implementation interface. This mapping relationship can be stored in a database, configuration file, or server memory.

[0151] For example, for a grayscale version of an online shopping application, there may be different grayscale version identifiers corresponding to different new functions, such as "grayscale version A" corresponding to "new payment interface", "grayscale version B" corresponding to "personalized recommendation interface upgrade", etc.

[0152] When the server receives a function implementation request and extracts the target grayscale version identifier, it searches for the corresponding function implementation interface based on the preset mapping relationship.

[0153] For example, if the target grayscale version identifier in the received function implementation request is "grayscale version A", the server will determine that the corresponding target function implementation interface is "new payment interface" according to the mapping relationship.

[0154] Step S403: calling the target function implementation interface to process the function implementation request.

[0155] After determining the target function implementation interface, the server will call this interface to process the function implementation request. This calling process can be implemented through the programming language and framework of the server side.

[0156] For example, in a server using the Java programming language, a method call may be used to trigger the execution of a target function implementation interface.

[0157] Specifically, the target function implementation interface will perform corresponding processing according to the specific content of the function implementation request. This may involve operations such as interacting with the database, calling other services, and executing specific business logic. After the target function implementation interface processes the function implementation request, it will return the processing result to the server. The server can further process this result and return it to the client, or perform other operations as needed.

[0158] For example, the target function implementation interface is an interface for processing new payment functions. It may communicate with the payment gateway, verify payment information, complete the payment transaction, and return the processing result to the server. If the payment is successful, the interface will return a successful status code and related payment confirmation information. The server returns this information to the client, and the client can display a prompt of successful payment, update the user interface, etc.

[0159] In this way, developers can set different function implementation interface mapping relationships according to different grayscale version requirements. This provides great flexibility for application function expansion and customization. The function implementation methods of different grayscale versions can be adjusted at any time based on user feedback and test results without affecting the stability of the entire system. By carrying the target grayscale version identifier in the function implementation request, the server can accurately identify the grayscale version corresponding to the request. This allows the server to provide specific function implementation interfaces for different grayscale versions, ensuring that new functions of each grayscale version can be processed correctly.

[0160] See also Figure 5 In some embodiments, the grayscale resource rendering method may also include but is not limited to steps S501 to S503:

[0161] Step S501: receiving construction exception information, wherein the construction exception information carries an exception code, the user identifier, and a system identifier of the client.

[0162] When an exception occurs during the process of building grayscale resources, the client generates a build exception message. This exception may be caused by a variety of reasons, such as network problems that cause some resources to fail to download, the client system is incompatible with specific grayscale codes, or a logical error occurs during the build process. The client sends the build exception message to the server. This sending process can be achieved through a network request, usually using HTTP or other communication protocols. The server receives the exception message and prepares to process it.

[0163] For example, the client uses a POST request to send construction exception information to a specific interface address of the server. After receiving the request, the network monitoring module of the server passes it to the corresponding processing module.

[0164] The exception information will carry an exception code, which is usually a specific identifier used to indicate the type of exception that occurred. For example, "resource download failure" may correspond to code "001", "system incompatibility" may correspond to code "002", etc. At the same time, the exception information will also include the user ID and the client's system ID. The user ID is used to uniquely identify the user who has the exception, and the system ID is used to describe the client's operating system, browser type, and other information.

[0165] For example, in a grayscale release of an online learning platform, if a resource loading error occurs when the client attempts to build a new learning module, the client will generate a build exception message, where the exception code may be the code corresponding to "resource loading failure", the user identifier may be the user's account ID, and the system identifier may be a combination of "Windows 10+Chrome".

[0166] Step S502: Determine the grayscale code missing from the client according to the abnormal code and the system identifier.

[0167] After receiving the build exception information, the server will analyze it based on the exception code and system identifier to determine the cause of the client exception. Different combinations of exception codes and system identifiers may correspond to different problems and require different solutions. By analyzing the exception information, the server can determine the grayscale code that the client is missing. These missing codes may be specific functional modules, resource files, or configuration parameters, etc., which need to be sent to the client to solve the build exception problem.

[0168] For example, if the exception code indicates "failed to download resource" and the system identifier is "iOS+Safari", it may be due to some network settings of the Safari browser on the iOS system that caused a problem with the resource download. The server will further analyze this information to determine the grayscale code that may be missing. If the analysis results show that the client is missing a specific JavaScript script file during the build process, the server will determine the grayscale code corresponding to this script file and prepare to send it to the client.

[0169] Step S503: establishing a mapping relationship between the grayscale code and the user identifier.

[0170] After determining the grayscale code missing from the client, the server will establish a mapping relationship between the grayscale code and the user ID of the abnormal user. This mapping relationship can be stored in a database, cache, or server memory so that the specific grayscale code required by the user can be quickly identified later.

[0171] For example, the server can create a record in the database to associate the user ID with the missing grayscale code. In this way, when the user requests to build grayscale resources again, the server can quickly provide the required grayscale code based on this mapping relationship.

[0172] In this way, by receiving the build exception information carrying the exception code and system identifier, the server can quickly determine the specific cause of the client exception. The combination of the exception code and the system identifier provides rich information, enabling the server to conduct targeted analysis for different problems. The server establishes a mapping relationship between the grayscale code and the user identifier, so that when the user requests to build the grayscale resource again, the specific grayscale code required by the user can be quickly identified. This personalized processing method can provide more accurate services for each user and improve the user experience.

[0173] See also Figure 6 In some embodiments, step S102 may include but is not limited to steps S601 to S602, and step S104 may include but is not limited to step S603:

[0174] Step S601: when the user identification is in a preset user identification set and it is not the first time to receive the startup information carrying the user identification, it is determined whether a target grayscale code having a preset mapping relationship with the user identification is stored.

[0175] Among them, if the user identifier is in the preset user identifier set, and it is not the first time to receive the startup information carrying the user identifier, it means that the user is a gray test user, but it is not the first time to start the application. This may involve the user's second or multiple startups caused by an exception in the process of building gray resources, so it is determined whether a target gray code with a preset mapping relationship established with the user identifier is stored. If the target gray code with a preset mapping relationship established with the user identifier is not stored, it means that the user is using the application normally again; if the target gray code with a preset mapping relationship established with the user identifier is stored, it means that the user has started the application twice or multiple times due to an exception in the process of building gray resources.

[0176] Step S602: When a target grayscale code having a preset mapping relationship with the user identifier is stored, the target grayscale code is sent to the client.

[0177] Among them, if a target grayscale code with a preset mapping relationship established with the user identifier is stored, it means that the user has started the program a second or multiple times due to an exception occurring in the process of building grayscale resources, so the pre-stored target grayscale code is sent to the client. The target grayscale code is used to repair the missing grayscale code that caused the exception in the process of building grayscale resources.

[0178] Step S603, controlling the client to construct a grayscale resource standard template according to the saved grayscale code and the target grayscale code.

[0179] After receiving the target grayscale code sent by the server, the client first needs to obtain the saved grayscale code. If the client has saved some grayscale codes in the previous use process, such as in local storage or memory, these saved grayscale codes can be used together with the newly received target grayscale code to construct the grayscale resource standard template. The client can read the saved grayscale code from the local storage and merge or integrate it with the newly received target grayscale code.

[0180] Specifically, the client builds a grayscale resource standard template based on the saved grayscale code and the newly received target grayscale code. This process may involve using a front-end development framework or tool to convert the grayscale code into actual page elements, styles, and functions.

[0181] For example, if the grayscale code represents a specific page layout, style sheet or script file, the client can use these codes to build the corresponding HTML structure, apply CSS styles and load JavaScript scripts, thereby creating a complete grayscale resource standard template. This template will be used to display the grayscale version of the application interface and functions on the client.

[0182] In this way, when an exception occurs during the construction of grayscale resources, resulting in a second or multiple restarts, the system can identify this situation and take appropriate measures. By checking whether a target grayscale code with a preset mapping relationship established with the user identifier is stored, it is possible to quickly determine whether the user restarted due to an exception. Storing a target grayscale code with a preset mapping relationship established with the user identifier can quickly provide the required partial code when the user starts again, improve information transmission efficiency, and avoid repeated construction exceptions. This helps to improve the reliability of grayscale testing and reduce user dissatisfaction with testing due to frequent problems.

[0183] See also Figure 7 In some embodiments, step S102 may also include but is not limited to step S701:

[0184] Step S701: When the user identifier is in a preset user identifier set and when the startup information carrying the user identifier is received for the first time, grayscale resource standard template construction information is sent to the client.

[0185] Among them, if the user identifier is in the preset user identifier set and the startup information carrying the user identifier is received for the first time, it means that the user is a grayscale user who uses the grayscale function of the application for the first time, and the complete grayscale resource standard template construction information is sent to the client.

[0186] In this way, by checking whether the user ID is in the preset set and whether it is the first time to receive the user's startup information, users who use the application's grayscale function for the first time can be accurately identified. This enables the system to provide these new grayscale test users with complete grayscale resource standard template construction information, ensuring that they can fully experience new features and improvements.

[0187] See also Figure 8 The embodiment of the present application further provides a grayscale resource rendering device, which can implement the above-mentioned grayscale resource rendering method, and the device includes:

[0188] A receiving unit, configured to receive application startup information sent by a client, wherein the startup information carries a user identifier of a user;

[0189] A sending unit, configured to send grayscale resource standard template construction information to the client when the user identifier is in a preset user identifier set;

[0190] An acquisition unit, configured to acquire a target grayscale resource corresponding to the user identifier when it is detected that the application meets a preset grayscale resource rendering condition;

[0191] A rendering unit is used to control the client to construct a grayscale resource standard template according to the grayscale resource standard template construction information, and to render grayscale resources in the grayscale resource standard template according to the target grayscale resource.

[0192] In some embodiments, the acquisition unit includes:

[0193] A first determining subunit is used to receive a page access request for the application sent by the client, and determine a target access page requested by the page access request;

[0194] A second determining subunit is used to determine that the application meets a preset grayscale resource rendering condition when the target access page is a preset access page;

[0195] The first acquisition subunit is used to acquire the target grayscale resource corresponding to the user identifier.

[0196] In some embodiments, the acquisition unit includes:

[0197] A third determining subunit is configured to receive a function control request for the application sent by the client, and determine a target function requested to be controlled by the function control request;

[0198] A fourth determining subunit, configured to determine, when the target function is a preset function, whether the application satisfies a preset grayscale resource rendering condition;

[0199] The second acquisition subunit is used to acquire the target grayscale resource corresponding to the user identifier.

[0200] In some embodiments, the apparatus is further configured to:

[0201] receiving a function implementation request sent by the client, wherein the function implementation request carries a target grayscale version identifier, and the function implementation request is a request generated by the client in response to a control operation on a rendered target grayscale resource;

[0202] Determine the target function implementation interface corresponding to the target gray version identifier based on a preset mapping relationship between the gray version identifier and the function implementation interface;

[0203] The target function implementation interface is called to process the function implementation request.

[0204] In some embodiments, the apparatus is further configured to:

[0205] Receive build exception information, where the build exception information carries an exception code, the user identifier, and a system identifier of the client;

[0206] Determine the grayscale code missing from the client according to the abnormal code and the system identifier;

[0207] A mapping relationship between the grayscale code and the user identifier is established.

[0208] In some embodiments, the sending unit includes:

[0209] A third determination subunit is used to determine whether a target grayscale code having a preset mapping relationship with the user identifier is stored when the user identifier is in a preset user identifier set and it is not the first time that the startup information carrying the user identifier is received;

[0210] A first sending subunit is used to send the target grayscale code to the client when a target grayscale code having a preset mapping relationship with the user identifier is stored;

[0211] Rendering units, used to:

[0212] The client is controlled to construct a grayscale resource standard template according to the saved grayscale code and the target grayscale code.

[0213] In some embodiments, the sending unit includes:

[0214] The second sending subunit is used to send grayscale resource standard template construction information to the client when the user identifier is in a preset user identifier set and the startup information carrying the user identifier is received for the first time.

[0215] The grayscale resource rendering device provided in the embodiment of the present application receives the startup information of the application sent by the client through the receiving unit, and the startup information carries the user identification of the user; the sending unit sends the grayscale resource standard template construction information to the client when the user identification is in the preset user identification set; the acquiring unit acquires the target grayscale resource corresponding to the user identification when detecting that the application meets the preset grayscale resource rendering condition; the rendering unit controls the client to construct the grayscale resource standard template according to the grayscale resource standard template construction information, and renders the grayscale resource in the grayscale resource standard template according to the target grayscale resource. In this way, by uniformly sending the grayscale resource standard template construction information to the client, the client is guided to construct a grayscale resource standard template specifically for grayscale testing, and the grayscale resource is not rendered using the resources cached by the client, thereby avoiding grayscale function abnormalities and improving the adaptability of grayscale resources on the client. Developers can accurately select specific pages as preset access pages according to business needs and test objectives. This ensures that grayscale resource rendering is triggered only on key pages related to new functions, changes or tests, avoiding unnecessary waste of resources and excessive interference with user experience. And the target grayscale resources are determined by the user identifier, so that the grayscale release can be personalized for different user groups. Not only can more sophisticated traffic control be achieved, but also a customized grayscale experience can be provided based on the specific attributes of the user (such as user behavior, preferences, levels, etc.). By presetting specific functions as conditions for triggering grayscale resource rendering, targeted testing can be concentrated on newly launched or optimized functions. This enables the development team to more accurately evaluate the performance, stability, and user acceptance of new functions without affecting other parts of the entire application. Obtaining target grayscale resources based on user identifiers can provide personalized new function experiences for different users. This helps to meet the needs and preferences of different users and improve user satisfaction. Developers can set different function implementation interface mapping relationships based on different grayscale version requirements. This provides great flexibility for application function expansion and customization. The function implementation methods of different grayscale versions can be adjusted at any time based on user feedback and test results without affecting the stability of the entire system. By carrying the target grayscale version identifier in the function implementation request, the server can accurately identify the grayscale version corresponding to the request. This allows the server to provide specific function implementation interfaces for different grayscale versions, ensuring that new functions of each grayscale version are properly processed. By receiving build exception information with exception codes and system identifiers, the server can quickly determine the specific cause of the client exception. The combination of exception codes and system identifiers provides rich information, allowing the server to perform targeted analysis on different issues.The mapping relationship between the grayscale code and the user identifier is established through the server, so that when the user requests to build the grayscale resource again, the specific grayscale code required by the user can be quickly identified. This personalized processing method can provide more accurate services for each user and improve the user experience. When an exception occurs in the process of building grayscale resources, resulting in secondary or multiple startups, the system can identify this situation and take corresponding measures. By checking whether the target grayscale code with a preset mapping relationship established with the user identifier is stored, it can be quickly determined whether the user restarted due to an exception. Storing the target grayscale code with a preset mapping relationship established with the user identifier can quickly provide the required part of the code when the user starts again, improve the efficiency of information transmission, and avoid repeated construction exceptions. This helps to improve the reliability of grayscale testing and reduce user dissatisfaction with testing due to frequent problems. By checking whether the user identifier is in the preset set and whether the user's startup information is received for the first time, users who use the grayscale function of the application for the first time can be accurately identified. This enables the system to provide complete grayscale resource standard template construction information for these new grayscale test users, ensuring that they can fully experience new features and improvements.

[0216] The specific implementation of the grayscale resource rendering device is substantially the same as the specific implementation of the grayscale resource rendering method described above, and will not be described in detail herein.

[0217] The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the grayscale resource rendering method when executing the computer program. The electronic device can be any smart terminal including a tablet computer, a car computer, etc.

[0218] See also Fig. 9 , Fig. 9 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0219] The processor 901 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0220] The memory 902 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 902 can store an operating system and other applications. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 902, and the processor 901 calls and executes the grayscale resource rendering method of the embodiment of this application;

[0221] Input / output interface 903, used to implement information input and output;

[0222] Communication interface 904, used to realize communication interaction between the device and other devices, which can be realized by wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0223] A bus 905 that transmits information between the various components of the device (e.g., the processor 901, the memory 902, the input / output interface 903, and the communication interface 904);

[0224] The processor 901 , the memory 902 , the input / output interface 903 and the communication interface 904 are connected to each other in communication within the device via a bus 905 .

[0225] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned grayscale resource rendering method is implemented.

[0226] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0227] The grayscale resource rendering method, grayscale resource rendering device, electronic device and storage medium provided in the embodiments of the present application receive the startup information of the application sent by the client, wherein the startup information carries the user identification of the user; when the user identification is in the preset user identification set, grayscale resource standard template construction information is sent to the client; when it is detected that the application meets the preset grayscale resource rendering conditions, the target grayscale resource corresponding to the user identification is obtained; the client is controlled to construct a grayscale resource standard template according to the grayscale resource standard template construction information, and grayscale resource rendering is performed in the grayscale resource standard template according to the target grayscale resource. In this way, the grayscale resource standard template construction information is uniformly sent to the client to guide the client to construct a grayscale resource standard template specifically for grayscale testing, without using the resources cached by the client to render the grayscale resources, thereby avoiding grayscale function abnormalities and improving the adaptability of grayscale resources on the client.

[0228] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0229] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0230] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0231] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0232] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0233] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0234] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0235] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0236] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0237] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0238] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A grayscale resource rendering method, characterized in that: include: Receiving application startup information sent by a client, wherein the startup information carries a user identifier of a user; When the user identifier is in a preset user identifier set, sending grayscale resource standard template construction information to the client; When it is detected that the application meets the preset grayscale resource rendering condition, obtaining the target grayscale resource corresponding to the user identifier; The client is controlled to construct a grayscale resource standard template according to the grayscale resource standard template construction information, and grayscale resource rendering is performed in the grayscale resource standard template according to the target grayscale resource.

2. The grayscale resource rendering method according to claim 1, characterized in that: When it is detected that the application meets the preset grayscale resource rendering condition, obtaining the target grayscale resource corresponding to the user identifier includes: Receiving a page access request for the application sent by the client, and determining a target access page requested by the page access request; When the target access page is a preset access page, determining that the application meets a preset grayscale resource rendering condition; Obtain the target grayscale resource corresponding to the user identifier.

3. The grayscale resource rendering method according to claim 2, characterized in that: The method further comprises: Receiving a function control request for the application sent by the client, and determining a target function requested to be controlled by the function control request; When the target function is a preset function, determining that the application meets a preset grayscale resource rendering condition; Obtain the target grayscale resource corresponding to the user identifier.

4. The grayscale resource rendering method according to claim 1, characterized in that: After performing grayscale resource rendering in the grayscale resource standard template according to the target grayscale resource, the method further includes: receiving a function implementation request sent by the client, wherein the function implementation request carries a target grayscale version identifier, and the function implementation request is a request generated by the client in response to a control operation on a rendered target grayscale resource; Determine the target function implementation interface corresponding to the target gray version identifier based on a preset mapping relationship between the gray version identifier and the function implementation interface; The target function implementation interface is called to process the function implementation request.

5. The grayscale resource rendering method according to claim 1, characterized in that: After controlling the client to construct the grayscale resource standard template according to the grayscale resource standard template construction information, the method further includes: Receive build exception information, where the build exception information carries an exception code, the user identifier, and a system identifier of the client; Determine the grayscale code missing from the client according to the abnormal code and the system identifier; A mapping relationship between the grayscale code and the user identifier is established.

6. The grayscale resource rendering method according to claim 5, characterized in that: When the user identifier is in a preset user identifier set, sending grayscale resource standard template construction information to the client includes: When the user identifier is in a preset user identifier set and it is not the first time to receive the startup information carrying the user identifier, determining whether a target grayscale code having a preset mapping relationship with the user identifier is stored; When a target grayscale code having a preset mapping relationship with the user identifier is stored, sending the target grayscale code to the client; The controlling the client to construct a grayscale resource standard template according to the grayscale resource standard template construction information includes: The client is controlled to construct a grayscale resource standard template according to the saved grayscale code and the target grayscale code.

7. The grayscale resource rendering method according to claim 1, characterized in that: When the user identifier is in a preset user identifier set, sending grayscale resource standard template construction information to the client includes: When the user identifier is in a preset user identifier set and when the startup information carrying the user identifier is received for the first time, grayscale resource standard template construction information is sent to the client.

8. A grayscale resource rendering device, characterized in that: include: A receiving unit, configured to receive application startup information sent by a client, wherein the startup information carries a user identifier of a user; A sending unit, configured to send grayscale resource standard template construction information to the client when the user identifier is in a preset user identifier set; An acquisition unit, configured to acquire a target grayscale resource corresponding to the user identifier when it is detected that the application meets a preset grayscale resource rendering condition; A rendering unit is used to control the client to construct a grayscale resource standard template according to the grayscale resource standard template construction information, and to render grayscale resources in the grayscale resource standard template according to the target grayscale resource.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the grayscale resource rendering method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the grayscale resource rendering method according to any one of claims 1 to 7 is implemented.

Images