Resource bit configuration information storage method and resource bit information configuration system

By receiving and verifying resource bit configuration information and storing it in the database using a resource bit extension point table, the problem of long development cycles and resource waste caused by resource bit construction schemes is solved, and efficient resource bit construction is achieved.

CN115687832BActive Publication Date: 2026-11-17BEIJING WODONG TIANJUN INFORMATION TECH CO LTD +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202211145577.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-09-20
Publication Date
2026-11-17
Estimated Expiration
2042-09-20

AI Technical Summary

Technical Problem

In existing technologies, resource allocation solutions require continuous research and testing by developers, resulting in long development cycles and wasted resources.

Method used

By receiving resource bit configuration requests, verifying and storing resource bit configuration information, and using the resource bit extension point table to perform field verification to ensure that the information meets the construction requirements, the information is directly stored in the resource bit database.

Benefits of technology

It shortened the R&D cycle for resource slot construction, reduced the waste of R&D resources, and improved the efficiency of resource slot construction.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115687832B_ABST
    Figure CN115687832B_ABST
Patent Text Reader

Abstract

This disclosure presents a method and system for storing resource bit configuration information. One specific implementation of the method includes: in response to receiving a resource bit configuration request from a service terminal, receiving resource bit configuration information and a resource bit extension point table corresponding to the request, wherein the resource bit configuration information includes a service identifier, and the resource bit configuration request carries a service terminal identifier; in response to determining that the service identifier matches the service terminal identifier, performing field validation processing on the resource bit configuration information according to the resource bit extension point table to generate a field validation result; and in response to determining that the field validation result indicates that the field validation passed, storing the resource bit configuration information and the resource bit extension point table in a resource bit database. This implementation is related to digital marketing, saving R&D personnel's development time, shortening the development cycle, and reducing the waste of R&D resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments disclosed herein relate to the field of computers, and specifically to a method for storing resource bit configuration information and a system for configuring resource bit information. Background Technology

[0002] Display ad placements are typically locations on a webpage provided by applications (apps), websites, online platforms, or other channels to display information. Types of display ad placements generally include: exposure ad placements and reach ad placements. For example, exposure ad placements could be an app's splash screen or splash page, or a website's banner ad or interstitial ad. Reach ad placements could be online platform announcements or push notifications, SMS messages, etc. Currently, when developing ad placements, the common approach is for dedicated developers to provide different implementation plans for different ad placements, including data storage, business logic processing, backend configuration, frontend update mechanisms, and canary rollout.

[0003] However, the above approach usually has the following technical problems: providing different construction schemes for different resource slots requires R&D personnel to continuously develop and test the resource slots, resulting in a long development cycle and a waste of R&D resources.

[0004] The information disclosed in this background section is only intended to enhance the understanding of the background of the inventive concept, and therefore may contain information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] The summary portion of this disclosure is intended to provide a brief overview of the concepts, which will be described in detail in the detailed description portion. This summary portion is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0006] Some embodiments of this disclosure provide a method for storing resource bit configuration information, a system for configuring resource bit information, an apparatus, an electronic device, a computer-readable medium, and a program product to solve one or more of the technical problems mentioned in the background section above.

[0007] In a first aspect, some embodiments of this disclosure provide a method for storing resource bit configuration information. The method includes: in response to receiving a resource bit configuration request sent by a service terminal, receiving resource bit configuration information and a resource bit extension point table corresponding to the resource bit configuration request, wherein the resource bit configuration information includes a service identifier, and the resource bit configuration request carries a service terminal identifier; in response to determining that the service identifier matches the service terminal identifier, performing field validation processing on the resource bit configuration information according to the resource bit extension point table to generate a field validation result; and in response to determining that the field validation result indicates that the field validation passed, storing the resource bit configuration information and the resource bit extension point table in a resource bit database.

[0008] Optionally, the resource bit configuration information includes at least one configuration field, and the at least one configuration field includes a target parameter field; and the above-mentioned field validation processing of the resource bit configuration information according to the resource bit extension point table to generate a field validation result includes: in response to determining that the resource bit extension point table includes an enumeration object, determining whether the at least one configuration field satisfies a first condition, wherein the first condition is: the field length of each configuration field in the at least one configuration field is less than or equal to the preset length of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the first condition, determining whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, generating a field validation result indicating that the field validation has passed.

[0009] Optionally, the resource bit configuration information includes at least one configuration field, and the at least one configuration field includes a target parameter field; and the above-mentioned field validation processing of the resource bit configuration information according to the resource bit extension point table to generate a field validation result includes: in response to determining that the resource bit extension point table does not contain an enumeration object, determining whether the at least one configuration field satisfies a first condition; in response to determining that the at least one configuration field satisfies the first condition, determining whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, determining whether the at least one configuration field satisfies a second condition, wherein the second condition is: the field format of each configuration field in the at least one configuration field is the same as the preset format of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the second condition, generating a field validation result indicating that the field validation has passed.

[0010] Optionally, before receiving the resource bit configuration information and resource bit extension point table corresponding to the resource bit configuration request sent by the service terminal, the method further includes: generating a service identifier and a service terminal token in response to receiving a service access request sent by the service terminal; and associating the service identifier and the service terminal token with a preset service user group.

[0011] Optionally, the above method further includes: in response to determining that the above service identifier is inconsistent with the above service terminal identifier, generating a prompt message indicating that the above service terminal has no permission, and sending the prompt message to the above service terminal.

[0012] Optionally, the above method further includes: in response to determining that at least one configuration field does not meet the first condition, generating field length exception information representing the at least one configuration field, and sending the field length exception information to the service terminal.

[0013] Secondly, some embodiments of this disclosure provide a resource bit information configuration system, including: a general resource bit configuration subsystem configured to store at least one general resource bit configuration information; an extensible resource bit configuration subsystem configured with at least one calling interface, each calling interface being configured with a resource bit extension point, configured to receive resource bit configuration information and a resource bit extension point table through the at least one calling interface; and a personalized resource bit configuration subsystem configured to receive personalized resource bit configuration information.

[0014] Thirdly, some embodiments of this disclosure provide a resource bit configuration information storage device, the device comprising: a receiving unit configured to, in response to receiving a resource bit configuration request sent by a service terminal, receive resource bit configuration information and a resource bit extension point table corresponding to the resource bit configuration request, wherein the resource bit configuration information includes a service identifier, and the resource bit configuration request carries a service terminal identifier; a verification unit configured to, in response to determining that the service identifier and the service terminal identifier are consistent, perform field verification processing on the resource bit configuration information according to the resource bit extension point table to generate a field verification result; and a storage unit configured to, in response to determining that the field verification result indicates that the field verification has passed, store the resource bit configuration information and the resource bit extension point table in a resource bit database.

[0015] Optionally, the resource bit configuration information mentioned above includes at least one configuration field, and the at least one configuration field includes a target parameter field.

[0016] Optionally, the verification unit is further configured to: in response to determining that the resource bit extension point table includes an enumeration object, determine whether the at least one configuration field satisfies a first condition, wherein the first condition is: the field length of each configuration field in the at least one configuration field is less than or equal to the preset length of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the first condition, determine whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, generate a field verification result indicating that the field verification has passed.

[0017] Optionally, the resource bit configuration information mentioned above includes at least one configuration field, and the at least one configuration field includes a target parameter field.

[0018] Optionally, the verification unit is further configured to: in response to determining that the resource bit extension point table does not include an enumerated object, determine whether the at least one configuration field satisfies a first condition; in response to determining that the at least one configuration field satisfies the first condition, determine whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, determine whether the at least one configuration field satisfies a second condition, wherein the second condition is: the field format of each configuration field in the at least one configuration field is the same as the preset format of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the second condition, generate a field verification result indicating that the field verification has passed.

[0019] Optionally, prior to the receiving unit, the apparatus further includes: a generating unit configured to generate a service identifier and a service token in response to receiving a service access request sent by a service terminal; and an associating unit configured to associate the service identifier and the service token with a preset service user group.

[0020] Optionally, the apparatus further includes: a first sending unit configured to, in response to determining that the service identifier is inconsistent with the service terminal identifier, generate a prompt message indicating that the service terminal has no permission, and send the prompt message to the service terminal.

[0021] Optionally, the apparatus further includes: a second sending unit configured to, in response to determining that at least one configuration field does not satisfy the first condition, generate field length anomaly information representing the at least one configuration field, and send the field length anomaly information to the service terminal.

[0022] Fourthly, some embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation of the first aspect above.

[0023] Fifthly, some embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method described in any of the implementations of the first aspect.

[0024] Sixthly, some embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0025] The above embodiments of this disclosure have the following beneficial effects: The resource bit configuration information storage method of some embodiments of this disclosure shortens the development cycle of resource bits for R&D personnel and reduces the waste of R&D resources. Specifically, the reason for the waste of R&D resources is that providing different construction schemes for different resource bits requires R&D personnel to continuously develop and test resource bits, resulting in a long development cycle. Based on this, the resource bit configuration information storage method of some embodiments of this disclosure firstly receives resource bit configuration information and a resource bit extension point table corresponding to the resource bit configuration request sent by the business terminal in response to receiving the resource bit configuration request. Therefore, resource bits can be directly constructed based on the resource bit information configured by the business terminal. This allows R&D personnel to construct resource bits with less R&D time based on the configured resource bit information. Then, in response to determining that the business identifier is consistent with the business terminal identifier, the resource bit configuration information is subjected to field validation processing according to the resource bit extension point table to generate a field validation result. This verifies whether the resource bit configuration information provided by the business terminal meets the construction requirements, preventing subsequent resource bit construction failures. Finally, in response to the confirmation that the above field validation results indicate that the field validation has passed, the above resource bit configuration information and the above resource bit extension point table are stored in the resource bit database. This allows developers to directly construct resource bits based on the resource bit configuration information and the resource bit extension point table. This saves developers' development time, shortens the development cycle, and reduces the waste of development resources. Attached Figure Description

[0026] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.

[0027] Figure 1 This is an architectural diagram of an exemplary system to which some embodiments of this disclosure can be applied;

[0028] Figure 2This is a flowchart of some embodiments of the resource bit configuration information storage method of this disclosure;

[0029] Figure 3 This is a schematic diagram of an application scenario of the resource bit in the resource bit configuration information storage method according to this disclosure;

[0030] Figure 4 This is a schematic diagram of the structure of some embodiments of the resource bit information configuration system according to this disclosure;

[0031] Figure 5 This is a schematic diagram of the structure of some embodiments of the resource bit configuration information storage device according to the present disclosure;

[0032] Figure 6 This is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed Implementation

[0033] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0034] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0035] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0036] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0037] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0038] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0039] Figure 1An exemplary system architecture 100 is shown for a resource bit configuration information storage method or resource bit configuration information storage device to which some embodiments of the present disclosure may be applied.

[0040] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0041] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as web browser applications, search applications, instant messaging tools, email clients, and social media platform software.

[0042] Terminal devices 101, 102, and 103 can be either hardware or software. When terminal devices 101, 102, and 103 are hardware, they can be various electronic devices with displays that support information display, including but not limited to smartphones, tablets, e-book readers, laptops, and desktop computers. When terminal devices 101, 102, and 103 are software, they can be installed in the aforementioned electronic devices. They can be implemented as, for example, multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are imposed here.

[0043] Server 105 can be a server that provides various services, such as a backend server that supports the information displayed on terminal devices 101, 102, and 103. The backend server can analyze and process received requests and other data, and then feed the processing results back to the terminal devices.

[0044] It should be noted that the resource bit configuration information storage method provided in the embodiments of this disclosure can be executed by terminal devices 101, 102, and 103, or by server 105. Accordingly, the resource bit configuration information storage device can be located in terminal devices 101, 102, and 103, or in server 105. No specific limitation is made here.

[0045] It should be noted that a server can be either hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the server is software, it can be implemented as multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are made here.

[0046] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0047] Continue to refer to Figure 2 The diagram illustrates a flow 200 of some embodiments of a resource bit configuration information storage method according to the present disclosure. This resource bit configuration information storage method includes the following steps:

[0048] Step 201: In response to receiving a resource bit configuration request sent by the service terminal, receive the resource bit configuration information and resource bit extension point table corresponding to the above resource bit configuration request.

[0049] In some embodiments, the execution entity of the resource bit configuration information storage method (e.g. Figure 1 The server shown can respond to a resource configuration request sent by a business terminal, receiving resource configuration information and a resource extension point table corresponding to the request. The resource configuration information includes a business identifier, and the resource configuration request carries a business terminal identifier. The business terminal can be a user terminal requesting the display of resource bits in the application interface. The resource configuration request can be an instruction from the execution entity requesting the configuration of resource bits on the business terminal. The resource configuration information can be parameter information submitted by the business terminal to configure resource bits. For example, the resource configuration information may include: resource bit title and resource bit display time. The resource extension point table can be a list containing various expansion joints of resource bits developed by the business terminal. Both the business identifier and the business terminal identifier can uniquely identify the business terminal. Here, the execution entity of the resource configuration information storage method can be a terminal device used to configure resource bits. Here, the resource extension points in the resource extension point table can be pre-configured resource bit interfaces provided by the business terminal.

[0050] Optionally, before step 201, the above method further includes:

[0051] The first step, in response to receiving a service access request from the service provider, is to generate a service identifier and a service provider token. The service access request can be a request to access service provider information. The service identifier uniquely identifies the service provider. The service provider token is a token used to verify the service provider's identity.

[0052] The second step is to associate the aforementioned business identifier and business terminal token with a preset business user group. Here, the preset business user group can refer to the various business personnel responsible for managing the resource bits information of the aforementioned business terminal. Association means binding the aforementioned business identifier and business terminal token to the preset business user group.

[0053] Step 202: In response to determining that the above-mentioned service identifier is consistent with the above-mentioned service terminal identifier, the above-mentioned resource bit configuration information is subjected to field verification processing according to the above-mentioned resource bit extension point table to generate field verification results.

[0054] In some embodiments, the execution entity may, in response to determining that the service identifier is consistent with the service terminal identifier, perform field validation processing on the resource bit configuration information according to the resource bit extension point table to generate a field validation result. Determining that the service identifier is consistent with the service terminal identifier means determining that the service identifier is the same as the service terminal identifier.

[0055] In practice, based on the aforementioned resource bit extension point table, the executing entity can perform field validation processing on the aforementioned resource bit configuration information through the following steps to generate field validation results:

[0056] The first step is to determine whether the above resource bit extension point table is empty.

[0057] The second step is to determine whether any of the fields included in the resource bit extension point table are empty, in response to the determination that the above resource bit configuration information is an empty table.

[0058] The third step is to generate a field validation result indicating that the field validation has passed, in response to the determination that none of the fields included in the above resource bit configuration information are empty.

[0059] Optionally, the resource bit configuration information mentioned above includes at least one configuration field, which includes a target parameter field. Here, the at least one configuration field can refer to a parameter field used to configure the resource bit. For example, the at least one configuration field may also include: a business category field and an extended field. The target parameter field can refer to a field representing the resource bit's affiliation. For example, the target parameter field can represent a business-side identifier. The business category field can refer to a field configuring the resource bit. For example, the business category field may include: resource bit title, resource bit status, resource bit image format, etc. The extended field can represent the type of text displayed in the resource bit set by the business side.

[0060] In some optional implementations of certain embodiments, based on the aforementioned resource bit extension point table, the execution entity may further perform field validation processing on the aforementioned resource bit configuration information through the following steps to generate field validation results:

[0061] The first step, in response to determining that the resource bit extension point table includes an enumeration object, is to determine whether the at least one configuration field satisfies a first condition. The first condition is that the length of each configuration field in the at least one configuration field is less than or equal to the preset length of the corresponding configuration field. Here, the enumeration object can refer to an enumeration class. For example, the length of a business class field is less than or equal to the preset length of a business class field.

[0062] The second step is to determine whether the target parameter field is an empty field in response to determining that at least one of the above configuration fields satisfies the above first condition.

[0063] The third step is to generate a field validation result indicating that the above target parameter field is not empty, in response to the determination that the field validation has passed.

[0064] In some alternative implementations of certain embodiments, based on the aforementioned resource bit extension point table, the execution entity may further perform field validation processing on the aforementioned resource bit configuration information through the following steps to generate field validation results:

[0065] The first step, in response to determining that the resource bit extension point table does not contain an enumeration object, is to determine whether the at least one configuration field satisfies a first condition. The first condition is that the length of each configuration field in the at least one configuration field is less than or equal to the preset length of the corresponding configuration field. Here, an enumeration object can refer to an enumeration class.

[0066] The second step is to determine whether the target parameter field is an empty field in response to determining that at least one of the above configuration fields satisfies the above first condition.

[0067] The third step, in response to determining that the aforementioned target parameter field is not an empty field, is to determine whether the aforementioned at least one configuration field satisfies the second condition. The second condition is that the field format of each of the aforementioned at least one configuration field is the same as the preset format of the corresponding configuration field. For example, whether the image format included in the business category field is PNG (Portable Network Graphics). Another example is whether the address format of the image address included in the business category field is a preset address format (HTTP format).

[0068] Fourth step: In response to determining that at least one of the above configuration fields meets the above second condition, generate a field validation result indicating that the field validation has passed.

[0069] Step 203: In response to determining that the above field verification result indicates that the field verification has passed, the above resource bit configuration information and the above resource bit extension point table are stored in the resource bit database.

[0070] In some embodiments, the execution entity may, in response to determining that the field validation result indicates that the field validation has passed, store the resource bit configuration information and the resource bit extension point table in the resource bit database. Here, the resource bit database may refer to a database used to store resource bit configuration information provided by the service terminal.

[0071] Optionally, in response to determining that the above-mentioned service identifier is inconsistent with the above-mentioned service terminal identifier, a prompt message indicating that the above-mentioned service terminal has no permission is generated, and the above-mentioned prompt message is sent to the above-mentioned service terminal.

[0072] In some embodiments, the executing entity may, in response to determining that the service identifier and the service terminal identifier are inconsistent, generate a prompt message indicating that the service terminal lacks authorization, and send the prompt message to the service terminal. Here, the prompt message may be a message indicating that the service terminal has not registered with the executing entity. For example, the prompt message may be "Service terminal A has not registered; please register at the XX registration portal."

[0073] Optionally, in response to determining that at least one configuration field does not meet the first condition, field length exception information representing the at least one configuration field is generated, and the field length exception information is sent to the service terminal.

[0074] In some embodiments, the execution entity may, in response to determining that at least one configuration field does not meet the first condition, generate field length exception information representing the at least one configuration field, and send the field length exception information to the service terminal. The field length exception information may indicate that the field length of one or more of the at least one configuration field is abnormal. For example, the field length exception information may be "The field length of the business class field is too long and does not meet the requirements."

[0075] like Figure 3 As shown, Figure 3 The display shows resource slots 301, 302, and 303. Resource slot 301 displays the message "Strawberry clearance sale!" Resource slot 302 displays the message "Company A's watermelon special offer". Resource slot 303 displays the message "XX pineapple, sweet and delicious, 5 yuan / each".

[0076] It should be noted that resource slots 301, 302, and 303 are merely one display format for resource slots. Resource slots can also be displayed as carousels, splash screens, floating pages, etc.

[0077] The above embodiments of this disclosure have the following beneficial effects: The resource bit configuration information storage method of some embodiments of this disclosure shortens the development cycle of resource bits for R&D personnel and reduces the waste of R&D resources. Specifically, the reason for the waste of R&D resources is that providing different construction schemes for different resource bits requires R&D personnel to continuously develop and test resource bits, resulting in a long development cycle. Based on this, the resource bit configuration information storage method of some embodiments of this disclosure firstly receives resource bit configuration information and a resource bit extension point table corresponding to the resource bit configuration request sent by the business terminal in response to receiving the resource bit configuration request. Therefore, resource bits can be directly constructed based on the resource bit information configured by the business terminal. This allows R&D personnel to construct resource bits with less R&D time based on the configured resource bit information. Then, in response to determining that the business identifier is consistent with the business terminal identifier, the resource bit configuration information is subjected to field validation processing according to the resource bit extension point table to generate a field validation result. This verifies whether the resource bit configuration information provided by the business terminal meets the construction requirements, preventing subsequent resource bit construction failures. Finally, in response to the confirmation that the above field validation results indicate that the field validation has passed, the above resource bit configuration information and the above resource bit extension point table are stored in the resource bit database. This allows developers to directly construct resource bits based on the resource bit configuration information and the resource bit extension point table. This saves developers' development time, shortens the development cycle, and reduces the waste of development resources.

[0078] Further reference Figure 4 As an implementation of the methods shown in the above figures, this disclosure provides some embodiments of the resource bit information configuration system 400 according to this disclosure. These system embodiments are similar to... Figure 2 Corresponding to the method embodiments shown, the above-mentioned resource bit information configuration system 400 includes: a general resource bit configuration subsystem 401, an expandable resource bit configuration subsystem 402, and a personalized resource bit configuration subsystem 403.

[0079] In some embodiments, the general resource bit configuration subsystem 401 is configured to store at least one general resource bit configuration information. Here, the general resource bit configuration subsystem may be a pre-built system for building and storing various general resource bit configuration information. The general resource bit configuration information may be resource bit configuration information that is not extensible or modifiable.

[0080] In some embodiments, the extensible resource bit configuration subsystem 402 is configured with at least one calling interface, each calling interface being configured with resource bit extension points, and is configured to receive resource bit configuration information and a resource bit extension point table through the at least one calling interface. Here, the calling interface may refer to an interface (Application Programming Interface) provided to the business side for extending resource bit configuration information.

[0081] In some embodiments, the personalized resource bit configuration subsystem 403 is configured to receive personalized resource bit configuration information. Here, the personalized resource bit configuration information may be resource bit configuration information configured by the service itself.

[0082] It should be noted that the general resource bit configuration subsystem 401, the expandable resource bit configuration subsystem 402, and the personalized resource bit configuration subsystem 403 can communicate with each other or not; this is not limited here.

[0083] It is understandable that the devices and references described in the resource bit information configuration system 400 Figure 2 The steps in the described method correspond to each other. Therefore, the operations, features, and beneficial effects described above for the method also apply to the resource bit information configuration system 400 and the devices contained therein, and will not be repeated here.

[0084] Further reference Figure 5 As an implementation of the methods shown in the above figures, this disclosure provides some embodiments of a resource bit configuration information storage device, which are similar to... Figure 2 Corresponding to the method embodiments shown, the device can be specifically applied to various electronic devices.

[0085] like Figure 5 As shown, a resource bit configuration information storage device 500 in some embodiments includes: a receiving unit 501, a verification unit 502, and a storage unit 503. The receiving unit 501 is configured to, in response to receiving a resource bit configuration request sent by a service terminal, receive resource bit configuration information and a resource bit extension point table corresponding to the resource bit configuration request, wherein the resource bit configuration information includes a service identifier, and the resource bit configuration request carries a service terminal identifier; the verification unit 502 is configured to, in response to determining that the service identifier matches the service terminal identifier, perform field verification processing on the resource bit configuration information according to the resource bit extension point table to generate a field verification result; the storage unit 503 is configured to, in response to determining that the field verification result indicates that the field verification passed, store the resource bit configuration information and the resource bit extension point table in a resource bit database.

[0086] Optionally, the resource bit configuration information mentioned above includes at least one configuration field, and the at least one configuration field includes a target parameter field.

[0087] Optionally, the verification unit 502 is further configured to: in response to determining that the resource bit extension point table includes an enumeration object, determine whether the at least one configuration field satisfies a first condition, wherein the first condition is: the field length of each configuration field in the at least one configuration field is less than or equal to the preset length of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the first condition, determine whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, generate a field verification result indicating that the field verification has passed.

[0088] Optionally, the resource bit configuration information mentioned above includes at least one configuration field, and the at least one configuration field includes a target parameter field.

[0089] Optionally, the verification unit 502 is further configured to: in response to determining that the resource bit extension point table does not include an enumerated object, determine whether the at least one configuration field satisfies a first condition; in response to determining that the at least one configuration field satisfies the first condition, determine whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, determine whether the at least one configuration field satisfies a second condition, wherein the second condition is: the field format of each configuration field in the at least one configuration field is the same as the preset format of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the second condition, generate a field verification result indicating that the field verification has passed.

[0090] Optionally, before the receiving unit 501, the device 500 further includes: a generation unit configured to generate a service identifier and a service token in response to receiving a service access request sent by a service terminal; and an association unit configured to associate the service identifier and the service token with a preset service user group.

[0091] Optionally, the apparatus 500 further includes: a first sending unit configured to, in response to determining that the service identifier is inconsistent with the service terminal identifier, generate a prompt message indicating that the service terminal has no permission, and send the prompt message to the service terminal.

[0092] Optionally, the apparatus 500 further includes: a second sending unit configured to, in response to determining that at least one configuration field does not satisfy the first condition, generate field length abnormality information representing the at least one configuration field, and send the field length abnormality information to the service terminal.

[0093] It is understandable that the units described in the device 500 are related to the reference. Figure 2 The steps in the described method correspond accordingly. Therefore, the operations, features, and beneficial effects described above for the method also apply to the device 500 and the units contained therein, and will not be repeated here.

[0094] The following is for reference. Figure 6 It illustrates electronic devices suitable for implementing some embodiments of this disclosure (e.g., Figure 1 The diagram shows the structure of the server (600) in this disclosure. Electronic devices in some embodiments of this disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this disclosure.

[0095] like Figure 6 As shown, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. Processing device 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0096] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 6 Each box shown can represent a device or multiple devices as needed.

[0097] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, it performs the functions defined above in the methods of some embodiments of this disclosure.

[0098] It should be noted that, in some embodiments of this disclosure, the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In some embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0099] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0100] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: in response to receiving a resource bit configuration request sent by a service terminal, receive resource bit configuration information and a resource bit extension point table corresponding to the resource bit configuration request, wherein the resource bit configuration information includes a service identifier, and the resource bit configuration request carries a service terminal identifier; in response to determining that the service identifier matches the service terminal identifier, perform field validation processing on the resource bit configuration information according to the resource bit extension point table to generate a field validation result; and in response to determining that the field validation result indicates that the field validation passed, store the resource bit configuration information and the resource bit extension point table in a resource bit database.

[0101] Computer program code for performing operations of some embodiments of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0102] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0103] The units described in some embodiments of this disclosure can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor may be described as including a receiving unit, a verification unit, and a storage unit. The names of these units do not necessarily limit the unit itself; for example, a verification unit may be described as "a unit that, in response to determining that the service identifier matches the service terminal identifier, performs field verification processing on the resource bit configuration information according to the resource bit extension point table to generate a field verification result."

[0104] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0105] Some embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements any of the resource bit configuration information storage methods described above.

[0106] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. A method for storing resource bit configuration information, comprising: In response to receiving a resource bit configuration request sent by the service terminal, the system receives resource bit configuration information and a resource bit extension point table corresponding to the resource bit configuration request. The resource bit configuration information includes a service identifier and at least one configuration field, the at least one configuration field including a target parameter field. The resource bit configuration request carries a service terminal identifier, the service identifier and the service terminal identifier are used to represent the service terminal. The resource bit configuration information includes resource bit information configured by the service terminal for building resource bits. The resource bit extension point table contains each extension point of the resource bit developed by the service terminal, and each extension point is a pre-configured interface of the resource bit provided by the service terminal. In response to determining that the service identifier is consistent with the service terminal identifier, the resource bit configuration information is subjected to field validation processing according to the resource bit extension point table to generate a field validation result, wherein the validation result indicates whether the resource bit configuration information meets the construction requirements; In response to determining that the field validation result indicates that the field validation has passed, the resource bit configuration information and the resource bit extension point table are stored in the resource bit database, wherein the resource bit database is used by R&D personnel to build the resource bits of the business terminal; The step of performing field validation processing on the resource bit configuration information based on the resource bit extension point table to generate field validation results includes: In response to determining that the resource bit extension point table includes an enumeration object, it is determined whether the at least one configuration field satisfies a first condition, wherein the first condition is: the field length of each configuration field in the at least one configuration field is less than or equal to the preset length of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the first condition, it is determined whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, a field verification result indicating that the field verification has passed is generated; In response to determining that the resource bit extension point table does not contain an enumerated object, determine whether the at least one configuration field satisfies the first condition; in response to determining that the at least one configuration field satisfies the first condition, determine whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, determine whether the at least one configuration field satisfies the second condition, wherein the second condition is: the field format of each configuration field in the at least one configuration field is the same as the preset format of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the second condition, generate a field verification result indicating that the field verification has passed.

2. The method of claim 1, wherein, Before receiving the resource bit configuration request sent by the service terminal, and receiving the resource bit configuration information and resource bit extension point table corresponding to the resource bit configuration request, the method further includes: In response to receiving a service access request from the service provider, a service identifier and a service provider token are generated. The service identifier and the service terminal token are associated with a preset service user group.

3. The method of claim 1, wherein, The method further includes: In response to determining that the service identifier is inconsistent with the service terminal identifier, a prompt message indicating that the service terminal has no permission is generated, and the prompt message is sent to the service terminal.

4. The method of claim 2, wherein, The method further includes: In response to determining that the at least one configuration field does not meet the first condition, a field length exception information representing the at least one configuration field is generated, and the field length exception information is sent to the service terminal.

5. A resource bit information configuration system, comprising: The general resource bit configuration subsystem is configured to store at least one general resource bit configuration information. An expandable resource bit configuration subsystem is configured with at least one calling interface, each calling interface being configured with a resource bit extension point, and is configured to receive resource bit configuration information and a resource bit extension point table through the at least one calling interface; The personalized resource bit configuration subsystem is configured to receive personalized resource bit configuration information; The resource bit information configuration system utilizes the general resource bit configuration subsystem, the scalable resource bit configuration subsystem, and the personalized resource bit configuration subsystem to execute the method described in any one of claims 1-4.

6. A resource bit configuration information storage device, comprising: The receiving unit is configured to, in response to receiving a resource bit configuration request sent by a service terminal, receive resource bit configuration information and a resource bit extension point table corresponding to the resource bit configuration request. The resource bit configuration information includes a service identifier and at least one configuration field, the at least one configuration field including a target parameter field. The resource bit configuration request carries a service terminal identifier, which, along with the service terminal identifier, represents the service terminal. The resource bit configuration information includes resource bit information configured by the service terminal for building resource bits. The resource bit extension point table contains extension points for resource bits developed by the service terminal, each extension point being a pre-configured interface for a resource bit provided by the service terminal. The verification unit is configured to, in response to determining that the service identifier is consistent with the service terminal identifier, perform field verification processing on the resource bit configuration information according to the resource bit extension point table to generate a field verification result, wherein the verification result indicates whether the resource bit configuration information meets the construction requirements; The storage unit is configured to, in response to determining that the field validation result indicates that the field validation has passed, store the resource bit configuration information and the resource bit extension point table in the resource bit database, wherein the resource bit database is used by R&D personnel to build the resource bits of the business terminal; The verification unit is further configured to: in response to determining that the resource bit extension point table includes an enumeration object, determine whether the at least one configuration field satisfies a first condition, wherein the first condition is: the field length of each configuration field in the at least one configuration field is less than or equal to the preset length of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the first condition, determine whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, generate a field verification result indicating that the field verification has passed. In response to determining that the resource bit extension point table does not contain an enumerated object, determine whether the at least one configuration field satisfies the first condition; in response to determining that the at least one configuration field satisfies the first condition, determine whether the target parameter field is an empty field; in response to determining that the target parameter field is not an empty field, determine whether the at least one configuration field satisfies the second condition, wherein the second condition is: the field format of each configuration field in the at least one configuration field is the same as the preset format of the corresponding configuration field; in response to determining that the at least one configuration field satisfies the second condition, generate a field verification result indicating that the field verification has passed.

7. An electronic device, comprising: One or more processors; A storage device on which one or more programs are stored; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-4.

8. A computer readable medium having stored thereon a computer program, wherein, When the program is executed by the processor, it implements the method as described in any one of claims 1-4.

9. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-4.

Citation Information

Patent Citations

  • Method and device for generating dynamic page

    CN110020358A

  • Login method and device, storage medium and processor

    CN114726632A