CN109710418B - Object processing method and device - Google Patents
Object processing method and device Download PDFInfo
- Publication number
- CN109710418B CN109710418B CN201711015142.5A CN201711015142A CN109710418B CN 109710418 B CN109710418 B CN 109710418B CN 201711015142 A CN201711015142 A CN 201711015142A CN 109710418 B CN109710418 B CN 109710418B
- Authority
- CN
- China
- Prior art keywords
- attribute
- attribute information
- condition
- requested
- prohibition condition
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses an object processing method and device. The method comprises the following steps: receiving an object processing request sent by client equipment, acquiring attribute information according to the object processing request, determining whether to allow the execution of specified service logic on the object requested to be processed according to the object processing strategy and the attribute information, and performing corresponding processing according to a determination result. Wherein the object handling policy includes a decision condition for determining whether execution of a specified business logic is allowed for the requested object.
Description
Technical Field
The present application relates to the field of computer and internet application technologies, and in particular, to an object processing method and apparatus.
Background
With the development of internet technology and wireless communication technology, internet applications are widely used in Personal Computers (PCs) and wireless terminals.
Taking online transactions (such as online shopping) as an example, the application can be implemented on various types of terminals at present, such as a PC, a tablet computer, a mobile phone and a smart terminal. For some reasons, when some internet applications are implemented on different terminals, the business logic may be different, taking online shopping as an example:
(1) for example, the PC-side online shopping application is loaded and presented in a web page form, and the mobile-side online shopping application is loaded and presented in an application program (App) form, so that the same commodity in the online shopping application is only allowed to be purchased through the application on the PC (i.e., the application loaded and presented in the web page form).
(2) Because different versions of the online shopping application program exist on the mobile terminal, the different versions of the application program can support different business logics, for example, for a certain type of goods in the online shopping application, the low-version online shopping application does not support the purchasing operation.
(3) Because host mobile terminals of the online application have different types, the online shopping application of the mobile terminal also has different types, such as a mobile phone terminal application, a tablet computer terminal application, an application on an intelligent terminal, and the like. Different types may support different business logic, for example, an online shopping application on an intelligent refrigerator supports only purchasing fresh goods.
Therefore, how to determine the appropriate business logic is a technical problem to be solved at present.
Disclosure of Invention
The embodiment of the application discloses an object processing method and device.
In a first aspect, an object processing method is provided, the method including:
receiving an object processing request sent by client equipment;
acquiring attribute information according to the object processing request;
determining whether to allow the execution of a specified service logic on the object requested to be processed according to the object processing policy and the attribute information;
performing corresponding processing according to the determination result of whether the object requested to be processed is allowed to execute the designated service logic;
wherein the object handling policy includes a decision condition for determining whether execution of a specified business logic is allowed for the requested object.
Optionally, the attribute information includes attribute information of a first attribute and attribute information of a second attribute, the decision condition includes a single attribute prohibition condition corresponding to the first attribute and an open condition corresponding to the prohibition condition, the single attribute prohibition condition is set according to the first attribute, and the open condition is set according to the second attribute;
the determining whether to allow the specified service logic to be executed on the object requested to be processed according to the object processing policy and the attribute information includes:
and determining whether the attribute information of the first attribute meets the single attribute prohibition condition according to the single attribute prohibition condition corresponding to the first attribute, if so, determining whether the attribute information of the second attribute meets the open condition, and if not, prohibiting the execution of the specified service logic on the object requested to be processed.
Optionally, the decision condition further includes a multi-attribute prohibition condition, where the multi-attribute prohibition condition is set according to a plurality of attributes, where the plurality of attributes at least include the first attribute;
the method further comprises the following steps:
after determining that the specified service logic is allowed to be executed on the requested object according to the single attribute prohibition condition and the opening condition, determining whether the multi-attribute prohibition condition is met according to the acquired attribute information; if yes, forbidding executing the specified service logic to the requested object, otherwise, allowing executing the specified service logic to the requested object.
Optionally, the decision condition further includes a multi-attribute prohibition condition, where the multi-attribute prohibition condition is set according to a plurality of attributes, where the plurality of attributes at least include the first attribute;
the method further comprises the following steps:
determining whether the multi-attribute prohibition condition is satisfied according to the acquired attribute information before determining that the specified service logic is allowed to be executed on the requested object according to the single-attribute prohibition condition and the opening condition; if yes, forbidding to execute the appointed service logic to the requested object;
the determining to allow execution of the specified business logic for the requested object according to the single attribute prohibition condition and the open condition includes:
if the multi-attribute prohibition condition is not met, determining whether the attribute information of the first attribute meets the single-attribute prohibition condition according to the single-attribute prohibition condition corresponding to the first attribute, if so, determining whether the attribute information of the second attribute meets the open condition, if not, prohibiting executing the specified service logic on the object requested to be processed, otherwise, allowing the specified service logic to be executed on the object requested to be processed.
Optionally, the obtaining attribute information according to the object processing request includes:
and acquiring attribute information carried by the object processing request as first part of attribute information according to the object processing request, acquiring second part of attribute information according to the object processing request, and using the first part of attribute information and the second part of attribute information as attribute information for determining whether to allow the execution of specified service logic on the object requested to be processed.
Optionally, the object handling policy is stored as configuration information, and the method further includes: and updating the configuration information.
Optionally, the attribute information includes attribute information of one or more of the following attributes:
object properties, the object properties including properties of at least one dimension;
a client attribute comprising an attribute of at least one dimension;
user attributes including attributes of at least one dimension;
attributes associated with object handling requests, the attributes associated with object handling requests including attributes of at least one dimension.
Optionally, the client attributes include attributes of one or more of the following dimensions:
the type of the client application is used for indicating the bearing and display mode of the application program;
the type of the host terminal of the client application is used for indicating the type of the host terminal equipment of the client;
a version of the client application.
Optionally, the client device is a client device for implementing an online transaction application; the object is an online transaction object provided by the online transaction application; the business logic includes business logic for transaction operations provided by the online transaction application.
In a second aspect, there is provided an object processing apparatus comprising:
a policy configuration module storing an object processing policy, the object processing policy including decision conditions for determining whether to allow execution of a specified business logic for a requested object;
the receiving module is used for receiving an object processing request sent by the client equipment;
the acquisition module acquires attribute information according to the object processing request;
the determining module is used for determining whether to allow the specified service logic to be executed on the object requested to be processed according to the object processing strategy and the attribute information;
and the processing module is used for carrying out corresponding processing according to the determination result of whether the object requested to be processed is allowed to execute the specified business logic.
Optionally, the attribute information includes attribute information of a first attribute and attribute information of a second attribute, the decision condition includes a single attribute prohibition condition corresponding to the first attribute and an open condition corresponding to the prohibition condition, the single attribute prohibition condition is set according to the first attribute, and the open condition is set according to the second attribute;
the determining module is specifically configured to:
and determining whether the attribute information of the first attribute meets the single attribute prohibition condition according to the single attribute prohibition condition corresponding to the first attribute, if so, determining whether the attribute information of the second attribute meets the open condition, and if not, prohibiting the execution of the specified service logic on the object requested to be processed.
In a third aspect, one or more computer-readable media are provided, the readable media having instructions stored thereon, which when executed by one or more processors, cause a communication device to perform the method of any of the first aspects above.
In a fourth aspect, there is provided an apparatus comprising: one or more processors; and one or more computer-readable media having instructions stored thereon, which, when executed by the one or more processors, cause the apparatus to perform the method of any of the first aspects described above.
In the embodiments of the present application, after receiving an object processing request sent by a client, attribute information may be obtained according to the request, and according to the object processing policy and the attribute information, it is determined whether to allow execution of a specified service logic on the object requested to be processed, and corresponding processing is performed according to a determination result, so that a suitable service execution logic may be determined according to the attribute information.
Drawings
Embodiments of the present application are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements.
Fig. 1 schematically illustrates a system architecture provided by an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating an object processing flow provided by an embodiment of the present application;
fig. 3 and fig. 4 respectively illustrate a schematic flow chart of determining whether to allow execution of a specified business logic on an object according to an embodiment of the present application;
FIG. 5 is a schematic diagram illustrating an example of a server structure provided by an embodiment of the present application;
fig. 6 schematically shows a structural diagram of an apparatus provided in an embodiment of the present application.
Detailed Description
While the concepts of the present application are susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the concepts of the present application to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives consistent with the present application and the appended claims.
References in the specification to "one embodiment," "an illustrative embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may or may not include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, it is believed to be within the knowledge of one skilled in the art when a particular feature, structure or characteristic is described in connection with an embodiment, it is submitted that such feature, structure or characteristic is affected in connection with other embodiments whether or not explicitly described. In addition, it should be understood that an item included in the list in the form of "at least one of a, B, and C" may represent (a); (B) (ii) a (C) (ii) a (A and B); (A and C); (B and C); or (A, B and C). Similarly, an item listed in the form of "at least one of a, B, or C" may represent (a); (B) (ii) a (C) (ii) a (A and B); (A and C); (B and C) or (A, B and C).
In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored by one or more transitory or non-transitory machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. A machine-readable storage medium may be embodied as any storage device, mechanism, or other physical structure for storing or transmitting information in a form readable by a machine (e.g., volatile or non-volatile memory, media disk, or other medium).
In the drawings, some structural or methodical features may be shown in a particular arrangement and/or order. However, it is to be understood that such specific arrangement and/or ordering may not be required. Rather, in some embodiments, the features may be arranged in a different manner and/or order than shown in the illustrative figures. In addition, the inclusion of a structural or methodical feature in a particular figure is not meant to imply that such feature is required in all embodiments and may not be included or may be combined with other features in some embodiments.
The embodiments of the present application will be described in detail below with reference to the accompanying drawings.
Referring to fig. 1, a system architecture applicable to the embodiments of the present application is shown. As shown, the system architecture may include a server 101 and client devices 102a and 102 b. The number of the client devices may be multiple, and only 2 client devices are described as an example in fig. 1.
The server 101 and the client devices 102a and 102b may be connected via a network 103.
The client devices (102a, 102b) may be any suitable computing or mobile device, such as may include: a smart phone, a smart terminal (such as a smart home device), a tablet computer, a notebook computer, a Personal Digital Assistant (PDA), or the like. The terminal may comprise a display and may comprise a suitable input device, such as a keyboard, mouse or touch pad. The display may include a touch sensitive screen for input functions.
The client devices (102a, 102b) are provided with client application programs, the server 101 is provided with a server application program, and the client application program and the server application program can be matched to realize the display and processing of the objects. For example, the application may be an online transaction program, and more particularly, an online shopping application.
In the embodiment of the present application, an object processing policy is configured on the server 101, where the object processing policy includes a decision condition, and the decision condition is used to determine whether to allow execution of a specified business logic on a requested object.
The object refers to an object processed by the application program, and the business logic refers to business logic which can be provided by the application program aiming at the object. Taking an online shopping application as an example, the object refers to a commodity provided by the online shopping application, and the online shopping application can provide an online display business logic of the commodity (for example, provide a service for a user to view details of the commodity), and provide an online purchase business logic of the commodity (that is, allow the user to perform online transaction on the commodity). The object handling policy may define whether a certain class or a certain good is allowed to be presented online or whether it is allowed to be purchased online.
In the embodiment of the present application, the object processing policy may be stored as configuration information. When the object processing strategy needs to be updated, the corresponding configuration information can be updated. The configuration information may be independent of the application program, so that when only the object handling policy needs to be updated, only the configuration information indicating the object handling policy needs to be updated, and the application program using the object handling policy does not need to be updated, thereby facilitating the update of the object handling policy.
In the embodiment of the application, the decision conditions in the object processing strategy can be set from different dimensions based on different attributes, so that the determination of whether the object requested to be processed is allowed to execute the specified business logic or not based on multiple dimensions can be supported.
Wherein the attributes may include:
-an object property. The object attribute can be further subdivided into attributes of different dimensions, such as divisible; object categories, object characteristics, object identifications, etc. The object category can classify the object from the point of view of the object, taking the commodity in online transaction application as an example, the object category can be used for commodity subject classification, for example, the classification can include clothing for men and women, shoes and bags, articles for mother and baby, skin care color cosmetics, home decoration and building materials, home textiles, home appliances and office, automotive articles, mobile phone digital products, life services and the like. The object class may be identified by an object class identification, such as an object class number. The object features can classify the objects from the perspective of common features, and the object features can be further subdivided into features of multiple dimensions. Still taking the commodities in online transaction application as an example, commodities belonging to the same industry or the same buying and selling process can be classified as commodities with the same object characteristics, or commodities can be classified according to the use population, the popularity degree, the use purpose and the like. The object feature may be identified by an object feature identifier (e.g., an object feature number), for example, the value of the product feature identifier is 13183, which indicates that the product uses one sales process, and the value of the product feature identifier is 3395, which indicates that the product uses another sales process.
-a client property. The client attributes may be further subdivided into attributes of different dimensions, such as version of the client application, type of hosting terminal of the client application, and the like. The type of the client application may specifically include a type of carrying and presenting an application in the form of a web page (such as a PC client type), a type of carrying and presenting an application in the form of an application program (such as a mobile phone client type), or may include a type of web page access of a personal computer (such as a web access type), and a type of web page access of a mobile terminal (such as a mobile phone client access type). The type of hosting terminal of the client application may be used to categorize the type of hosting terminal of the client application, such as the type of operating system used by the hosting handset terminal.
-a user attribute. User attributes may be further subdivided into attributes of different dimensions. Still taking the online transaction application as an example, the user attributes may include a product seller attribute and a product seller attribute, and the product seller attribute may further include a product seller characteristic and a product seller identifier (such as a product seller number), for example, the product seller characteristic may be categorized according to product preference activities participated in by the product seller. The buyer attributes may include buyer characteristics and buyer identifiers (e.g., buyer numbers), for example, the buyer characteristics may be categorized according to the registration time of the buyer.
-an attribute associated with the object handling request. The attribute may be further subdivided into attributes of different dimensions, such as the time or date of initiation of the object handling request, the location (e.g., region or city) where the user initiated the object handling request is located.
The above listed attributes are only examples, and the embodiments of the present application do not limit the present application. For example, whether to allow the specified business logic to be executed on the object may be defined according to other attributes, for example, a decision condition may be set according to personalized information (such as age, etc.) of the user.
In this embodiment of the present application, the decision condition in the object processing policy may include a single attribute prohibition condition. The single attribute prohibition condition may also be referred to as a single attribute blacklist. The single attribute prohibition condition may be set according to a single attribute, and one attribute may correspond to one single attribute prohibition condition. A single attribute disable condition is used to set a condition for disabling execution of a specified business logic for a requested object based on an attribute. For example, an object class corresponds to a single attribute prohibition condition that specifies which objects of the object class are prohibited from executing the specified business logic, or that specifies which objects of the object class meet which conditions are prohibited from executing the specified business logic. For example, the single attribute prohibition condition corresponding to the object category may specify that the object whose value is 1 and 2 is identified by the object category, and is prohibited from executing the specified service logic.
The single attribute prohibition condition may be in the form of a list (e.g., a black list), where the list includes one or more attribute information (attribute values) prohibited from executing the specified service logic, such as object category identification values 1 and 2, indicating that the object having the object category identification values 1 and 2 is prohibited from executing the specified service logic. The single attribute prohibition condition may also be in the form of an expression, such as an object category identifier value <3, which may also indicate that objects with values of 1 and 2 of the object category identifier are prohibited from executing the specified service logic.
In the embodiment of the application, in the object processing policy, an open condition may be set for a single attribute prohibition condition. The open condition corresponding to a single attribute prohibition condition is used to specify an exceptional case of the single attribute prohibition condition, that is, in the case where it is determined that the object is prohibited from executing the specified business logic according to the single attribute prohibition condition, if the open condition is satisfied, it is still possible to allow the object to be executed with the specified business logic.
The open condition may be in the form of a list (e.g., a white list) including one or more attribute information (attribute values) that are allowed to execute the specified business logic, where the attribute information (attribute values) corresponds to an attribute different from an attribute corresponding to the corresponding single attribute prohibition condition. For example, if the single attribute prohibition condition specifies that the objects whose values of the object category identifier are 1 and 2 are prohibited from executing the designated service logic, the open condition corresponding to the single attribute prohibition condition may specify that the version number of the client application is greater than 4.0, and may not be restricted by the single attribute prohibition condition, that is, when the version number of the client application is greater than 4.0, the objects whose values of the object category identifier are 1 and 2 may still be permitted to execute the designated service logic.
Alternatively, the open condition may be set based on one attribute or a plurality of attributes. For example, if a single attribute prohibition condition corresponding to one open condition specifies that objects whose object category identifiers take values of 1 and 2 are prohibited from executing the specified service logic, the open condition corresponding to the single attribute prohibition condition may specify: the version number of the client application is not restricted by the single attribute prohibition condition when the version number is above 4.0, or the open condition may also specify: and when the version number of the client application is more than 4.0 and the host terminal type of the client application is an intelligent terminal, the client application is not restricted by the single attribute prohibition condition.
Optionally, a multi-attribute prohibition condition may be further included in the object processing policy. The multi-attribute prohibition condition may be set according to a plurality of attributes, and more complicated judgment may be realized compared to a single-attribute prohibition condition. For example, the multi-attribute prohibition condition may specify: and if the value of the object category identification is 1 and 2, and the host terminal type of the client application is the intelligent refrigerator, prohibiting the object category identification from executing the specified service logic (such as online purchase).
In the embodiment of the present application, the object processing policy may be stored as configuration information (such as a configuration file) and/or a script. For example, the single attribute prohibition condition and the corresponding open condition in the object processing logic may be stored as a configuration file, and the multiple attribute prohibition condition may be stored as a script. For example, a Groovy script may be employed, which supports dynamic loading. Therefore, the modified script can be directly configured without restarting the server, and can be immediately applied to an online environment. As another example, the open condition may be stored as a script to handle complex decision logic (e.g., open conditions set based on various attributes).
In the case that the object processing logic includes a single attribute prohibition condition and a corresponding opening condition, but does not include a multi-attribute prohibition condition, in one implementation, the object processing logic may sequentially perform a judgment according to the single attribute prohibition condition and the corresponding opening condition, and if it is judged that the requested object is prohibited from executing the specified service logic according to one of the single attribute prohibition conditions and the corresponding opening condition, output the judgment result as a final judgment result; if the requested object is allowed to execute the specified service logic according to a certain single attribute prohibition condition and a corresponding opening condition, the judgment can be carried out according to the next single attribute prohibition condition and the corresponding opening condition, and so on. And if the specified service logic is allowed to be executed for the requested object according to all the single attribute forbidden conditions and the corresponding open conditions, outputting the result as a final judgment result.
In the case where the single-attribute prohibition condition and the corresponding open condition are included in the object processing logic, and the multiple-attribute prohibition condition is included, the determination may be made based on each single-attribute prohibition condition and the corresponding open condition in the manner described above. And if the specified service logic is allowed to be executed for the requested object according to all the single attribute prohibition conditions and the corresponding opening conditions, judging according to the multi-attribute prohibition conditions, and taking the result of judgment according to the multi-attribute prohibition conditions as a final output result. Of course, the determination may be performed according to the multi-attribute prohibition condition, and if the determination result is that the execution of the designated service logic is prohibited, the determination result is output as a final determination result, otherwise, the determination may be performed according to the single-attribute prohibition condition and the corresponding open condition in sequence according to the above method.
Referring to fig. 2, an object processing flow provided in the embodiment of the present application is shown. The execution subject of the flow may be an object processing apparatus, which may be provided on a server or refers to the server itself.
As shown, the process may include the following steps:
s201: and receiving an object processing request sent by the client equipment.
In one implementation scenario, a user may send a processing request for an object provided by an application in a client device through the application, which may be sent to a server side of the application. For example, taking the application as an online transaction application as an example, the user may send a query request, a viewing request, a purchasing request, or the like for one or some (e.g., a certain type) of goods through the client device.
For example, after a user browses a user interface of an online transaction application, selects a commodity, and clicks a "view details" command button, the application generates a view details request for the commodity, and sends the request to a server through a PC where the application is located.
For another example, after the user browses the user interface of the online transaction application, selects a commodity and clicks the "purchase" command button, the application generates a purchase request for the commodity, and sends the request to the server through the mobile terminal where the application is located.
S202: and acquiring attribute information according to the object processing request.
The description of the attribute and the attribute information can be referred to the foregoing description, and is not repeated here.
The attribute information may be obtained from the object processing request (that is, all the attribute information is carried in the object processing request), or may be obtained from part of the attribute information (that is, part of the attribute information is carried in the object processing request), and the other part of the attribute information is obtained by the server according to the object processing request. All attribute information may also be obtained by the server in response to the object processing request. Several specific scenarios are exemplarily listed below:
scene 1: the object processing request carries attribute information, and the server can directly acquire the attribute information carried in the object processing request as a basis for judging whether to allow the execution of the specified service logic on the object requested to be processed.
As an example of the scenario 1, the object processing request may carry version information (e.g., a version number) of the client application, type information (e.g., a type identifier) to which a host terminal of the client application belongs, and category information (e.g., a category identifier) to which the object belongs. The server can directly acquire the attribute information carried in the request as a basis for judging whether to allow the specified business logic to be executed on the commodity.
As another example of scenario 1, the object processing request may carry version information (e.g., version number) of the client application, type information (e.g., type identifier) of a host terminal of the client application, location information of the user, and user personalization information (e.g., age, which may be obtained by the client device from a locally stored cookie). The server can directly acquire the attribute information carried in the request as a basis for judging whether to allow the specified business logic to be executed on the commodity.
Scene 2: the object processing request may carry attribute information, and the server may obtain the attribute information carried by the object processing request, obtain other attribute information according to the object request, and use the attribute information obtained from the request and the obtained other attribute information as a basis for determining whether to allow execution of a specified service logic for the commodity.
As an example of the scenario 2, the object processing request may carry version information (such as a version number) of the client application, type information (such as a type identifier) to which a host terminal of the client application belongs, and may also carry the following identifier information: and (5) identifying the commodity. The server may query the product database according to the product identifier to obtain category information (such as a category identifier) to which the product belongs, and obtain version information of the client application and type information to which the host terminal of the client application belongs from the request, where these attribute information may be used as a basis for determining whether to allow execution of a specified service logic for the product.
As another example of the scenario 2, the object processing request may carry version information (e.g., a version number) of the client application and type information (e.g., a type identifier) to which a host terminal of the client application belongs. The server can obtain the version information of the client application and the type information of the host terminal of the client application from the request, obtain the initiation time of the request, and obtain the position of the user according to the IP address of the user initiating the request, wherein the attribute information can be used as a basis for judging whether to allow the specified business logic to be executed on the commodity.
Scene 3: the server may obtain the attribute information according to the object processing request as a basis for deciding whether to allow execution of the specified business logic for the commodity.
As an example of scenario 3 above, the object processing request may carry the following identification information: and (5) identifying the commodity. The server may query the product database according to the product identifier to obtain category information (such as a category identifier) to which the product belongs and feature information (such as a product feature identifier) of the product, and these attribute information may be used as a basis for determining whether to allow a specific service logic to be performed on the product.
As another example of scenario 3 above, the object handling request may carry the following identification information: the server can query the commodity database according to the commodity identification to obtain the category information (such as the category identification) to which the commodity belongs, query the user database according to the user identification to obtain the user characteristic information (such as the characteristic identification) to which the user belongs, obtain the initiation date of the request, and obtain the position of the user according to the IP address of the user initiating the request, wherein the attribute information can be used as a basis for judging whether to allow the specified service logic to be executed on the commodity.
S203: according to the object processing policy and the attribute information acquired in S202, it is determined whether or not to allow execution of the specified service logic on the object requested to be processed.
In this step, optionally, when determining whether or not to allow the specified business logic to be executed on the object requested to be processed, if it is determined that the specified business logic is prohibited from being executed according to one attribute information acquired in S202, a result of prohibiting the specified business logic from being executed on the requested object may be obtained regardless of a determination result obtained according to other attribute information.
S204: and performing corresponding processing according to the determination result of the S203.
In this step, if the determination result of S203 is that the execution of the specified business logic on the requested object is prohibited, the present flow may be ended, or prompt information that prohibits the execution of the specified business logic on the requested object may be output. If the determination of S203 is that the specified business logic is allowed to be executed on the requested object, the business logic may be executed with respect to the requested object.
In one scenario, in the object processing policy, a single attribute prohibition condition (e.g., a black list) is set for each attribute, and optionally, a corresponding open condition (e.g., a white list) may also be set. Taking the example of acquiring the attribute information of the first attribute and the attribute information of the second attribute in S202, the object processing policy includes a single attribute prohibition condition (blacklist) corresponding to the first attribute and a corresponding open condition (whitelist). One implementation method of S203 may include:
and determining whether the attribute information of the first attribute meets the single attribute prohibition condition or not according to the single attribute prohibition condition corresponding to the first attribute, if so, determining whether the attribute information of the second attribute meets the opening condition or not, and if not, prohibiting the execution of the specified service logic on the object requested to be processed.
For each attribute information, whether to execute the specified business logic on the requested object can be determined according to the above process. If the determination result for each attribute information is that the specified business logic is allowed to be performed on the object of the requested processing, it may be determined that the specified business logic is allowed to be performed on the object of the requested processing.
Referring to fig. 3, a schematic flowchart of a process for determining whether to allow execution of a specific business logic on an object of a requested process according to an embodiment of the present application may include:
s300: traversing the attribute information acquired in the step S202, and determining the current attribute and the attribute information;
s301: determining whether the attribute information of the current attribute meets the single attribute prohibition condition or not according to the single prohibition condition corresponding to the current attribute, and executing S302 if the attribute information of the current attribute meets the single attribute prohibition condition; otherwise, S305 is executed;
s302: judging whether an open condition is set for the current attribute, if so, executing S303, otherwise, determining to forbid the execution of the specified service logic on the object requested to be processed, and ending the process;
s303: judging whether the opening condition is met or not according to the attribute information acquired in the S202, if not, determining to prohibit the execution of the specified service logic on the object requested to be processed, and ending the process, otherwise, executing the S304;
s304: if yes, executing S305, otherwise, determining to allow to execute the specified service logic to the object requested to be processed, and ending the process;
s305: and acquiring next attribute information, taking the acquired next attribute information as current attribute information, and returning to the step S301.
Referring to fig. 4, a schematic flow chart of determining whether to allow execution of a specified business logic on an object of a requested process provided by the embodiment of the present application is shown by taking an online transaction application as an example. In the application scenario, in the object processing logic, a black list and a white list are respectively set for the following attributes: a commodity category, a first-dimension commodity characteristic, a second-dimension commodity characteristic, a buyer characteristic, a type of the client application, and a version of the client application. And the first-dimension commodity features and the second-dimension commodity features are commodity features with different dimensions. In this flow, if attribute information (attribute value) of a certain attribute is in a blacklist corresponding to the attribute, it is called to hit the blacklist, and if the attribute information (attribute value) of a certain attribute satisfies an open condition in a whitelist, it is called to hit the whitelist.
As shown in fig. 4, the process includes:
s401: judging whether the commodity category identification hits a blacklist corresponding to the commodity category according to the identification of the commodity category to which the commodity requested to be processed belongs, and if not, switching to S402; otherwise, judging whether the white list corresponding to the blacklist is hit according to the obtained other attribute information, if so, switching to S402, otherwise, switching to S408;
s402: judging whether the first-dimension commodity feature identifier hits a blacklist corresponding to the first-dimension commodity feature according to the first-dimension commodity feature identifier of the commodity requested to be processed, and if the first-dimension commodity feature identifier does not hit the blacklist, turning to S403; otherwise, judging whether the white list corresponding to the blacklist is hit according to the obtained other attribute information, if so, switching to S403, otherwise, switching to S408;
s403: according to the second dimension commodity feature identification of the commodity requested to be processed, judging whether the second dimension commodity feature identification hits a blacklist corresponding to the second dimension commodity feature, and if the blacklist is not hit, turning to S404; otherwise, judging whether the white list corresponding to the blacklist is hit according to the obtained other attribute information, if so, switching to S404, otherwise, switching to S408;
s404: judging whether the buyer feature identifier hits a blacklist corresponding to the buyer feature according to the buyer feature identifier of the commodity requested to be processed, and turning to S405 if the buyer feature identifier does not hit the blacklist; otherwise, judging whether the white list corresponding to the blacklist is hit according to the obtained other attribute information, if so, switching to S405, otherwise, switching to S408;
s405: judging whether the application type identifier hits a blacklist corresponding to the type of the client application according to the type identifier of the client application, and if the application type identifier does not hit the blacklist, switching to S406; otherwise, judging whether the white list corresponding to the blacklist is hit according to the obtained other attribute information, if so, switching to S406, otherwise, switching to S408;
s406: judging whether the version number hits a blacklist corresponding to the version of the client application according to the version number of the client application, and turning to S407 if the version number does not hit the blacklist; otherwise, judging whether the white list corresponding to the blacklist is hit according to the obtained other attribute information, if so, switching to S407, otherwise, switching to S408;
s407: determining to permit execution of a specified business logic for the requested commodity;
s408: it is determined that the designated business logic is prohibited from being performed on the requested merchandise.
An example according to the above process is: the object processing strategy comprises a first-dimension commodity feature blacklist and a version white list corresponding to the first-dimension commodity feature blacklist, wherein the blacklist comprises a first-dimension commodity feature identification value 4889, and the white list comprises an opening condition: version >5.6.0 of the client application. In one example, if the first-dimension product feature identification value is 4889 in S402, the blacklist is hit, but the version number of the client application is 5.5.0, and the whitelist is not hit, indicating that the identification value of the first-dimension product feature is in the blacklist but satisfies the open condition, the process proceeds to S403. In another example, if the first-dimension product feature identification value is 4889 in S402, the blacklist is hit, the version number of the client application is 5.6.2, and the whitelist is also hit, indicating that the identification value of the first-dimension product feature is in the blacklist and does not satisfy the open condition, so the process goes to S408, and the specified service logic is prohibited from being executed on the requested product.
Based on the same technical concept, the embodiment of the present application further provides an object processing apparatus, which can implement the object processing method described in the foregoing embodiment.
Fig. 5 is a schematic structural diagram of an object processing apparatus according to an embodiment of the present application. The apparatus may include: the system comprises a policy configuration module 501, a receiving module 502, an obtaining module 503, a determining module 504 and a processing module 505.
The policy configuration module 501 may store an object handling policy that includes decision conditions for determining whether to allow execution of specified business logic for a requested object.
The receiving module 502 may be configured to receive an object handling request sent by a client device.
The obtaining module 503 may be configured to obtain the attribute information according to the object processing request.
The determining module 504 may be configured to determine whether to allow execution of the specified business logic for the object requested to be processed based on the object processing policy and the attribute information.
The processing module 505 may be configured to perform corresponding processing according to a determination result of whether to allow execution of a specified business logic on the object requested to be processed.
Optionally, the attribute information includes attribute information of a first attribute and attribute information of a second attribute, the decision condition includes a single attribute prohibition condition corresponding to the first attribute and an open condition corresponding to the prohibition condition, the single attribute prohibition condition is set according to the first attribute, and the open condition is set according to the second attribute. The determining module 504 may be specifically configured to: and determining whether the attribute information of the first attribute meets the single attribute prohibition condition according to the single attribute prohibition condition corresponding to the first attribute, if so, determining whether the attribute information of the second attribute meets the open condition, and if not, prohibiting the execution of the specified service logic on the object requested to be processed.
Optionally, the decision condition further includes a multi-attribute prohibition condition, the multi-attribute prohibition condition is set according to a plurality of attributes, and the plurality of attributes at least include the first attribute. The determining module 504 may also be configured to: after determining that the specified service logic is allowed to be executed on the requested object according to the single attribute prohibition condition and the opening condition, determining whether the multi-attribute prohibition condition is met according to the acquired attribute information; if yes, forbidding executing the specified service logic to the requested object, otherwise, allowing executing the specified service logic to the requested object.
Optionally, the decision condition further includes a multi-attribute prohibition condition, the multi-attribute prohibition condition is set according to a plurality of attributes, and the plurality of attributes at least include the first attribute. The determination module 504 may also be configured to: determining whether the multi-attribute prohibition condition is satisfied according to the acquired attribute information before determining that the specified service logic is allowed to be executed on the requested object according to the single-attribute prohibition condition and the opening condition; if so, the execution of the specified business logic on the requested object is prohibited. The determining module 504, when determining that the specified service logic is allowed to be executed on the requested object according to the single attribute prohibition condition and the open condition, may specifically be configured to: if the multi-attribute prohibition condition is not met, determining whether the attribute information of the first attribute meets the single-attribute prohibition condition according to the single-attribute prohibition condition corresponding to the first attribute, if so, determining whether the attribute information of the second attribute meets the open condition, if not, prohibiting the execution of the specified service logic on the object requested to be processed, otherwise, allowing the execution of the specified service logic on the object requested to be processed.
Optionally, the obtaining module 503 may be specifically configured to: and acquiring attribute information carried by the object processing request as first part of attribute information according to the object processing request, acquiring second part of attribute information according to the object processing request, and using the first part of attribute information and the second part of attribute information as attribute information for determining whether to allow the execution of specified service logic on the object requested to be processed.
Optionally, the object handling policy is stored as configuration information; the policy configuration module 501 may also be configured to: and updating the configuration information.
Optionally, the configuration information includes: configuration files and/or scripts.
Optionally, the attribute information includes attribute information of one or more of the following attributes:
object properties, the object properties including properties of at least one dimension;
a client attribute comprising an attribute of at least one dimension;
user attributes including attributes of at least one dimension;
attributes associated with object handling requests, the attributes associated with object handling requests including attributes for at least one dimension.
Optionally, the client attributes include attributes of one or more of the following dimensions:
the type of the client application is used for indicating the bearing and display mode of the application program;
the type of the host terminal of the client application is used for indicating the type of the host terminal equipment of the client;
a version of the client application.
Optionally, the client device is a client device for implementing an online transaction application; the object is an online transaction object provided by the online transaction application; the business logic includes business logic of transaction operations provided by the online transaction application.
Based on the same technical concept, the embodiment of the present application further provides an apparatus 600, and the apparatus 600 may implement the object processing flow described in the foregoing embodiment.
Fig. 6 illustrates an example apparatus 600 according to various embodiments, the apparatus 600 may include one or more processors 602, system control logic 601 coupled to at least one processor 602, non-volatile memory (NMV)/memory 604 coupled to the system control logic 601, and a network interface 606 coupled to the system control logic 601.
The system control logic 601 in one embodiment may include one or more memory controllers to provide an interface to the system memory 603. The system memory 603 is used to load and store data and/or instructions. For example, corresponding to apparatus 600, in one embodiment, system memory 603 may include any suitable volatile memory.
NVM/memory 604 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions. For example, NVM/memory 604 may include any suitable non-volatile storage device, such as one or more Hard Disk Drives (HDDs), one or more Compact Disks (CDs), and/or one or more Digital Versatile Disks (DVDs).
NVM/memory 604 may include storage resources that are physically part of a device on which the system is installed or may be accessed, but not necessarily part of a device. For example, NVM/memory 604 may be network accessible via network interface 606.
In one embodiment, at least one of the processors 602 may be packaged together with logic for one or more controllers of system control logic. In one embodiment, at least one of the processors may be packaged together with logic for one or more controllers of system control logic to form a system in a package. In one embodiment, at least one of the processors may be integrated on the same die with logic for one or more controllers of system control logic. In one embodiment, at least one of the processors may be integrated on the same die with logic for one or more controllers of system control logic to form a system chip.
The device 600 may further include an input/output device 605. Input/output devices 605 may include a user interface intended to enable a user to interact with device 600, may include a peripheral component interface designed to enable peripheral components to interact with the system, and/or may include sensors intended to determine environmental conditions and/or location information about device 600.
Based on the same technical concept, the present application also provides one or more computer-readable media, where instructions are stored on the readable media, and when the instructions are executed by one or more processors, the instructions cause a communication device to execute the object processing method described in the foregoing embodiments.
Claims (11)
1. An object processing method, characterized in that the method comprises:
receiving an object processing request sent by client equipment;
acquiring attribute information according to the object processing request, wherein the attribute information comprises attribute information of a first attribute and attribute information of a second attribute;
determining whether to allow the execution of a specified service logic on the object requested to be processed according to the object processing policy and the attribute information;
performing corresponding processing according to the determination result of whether the object requested to be processed is allowed to execute the designated service logic;
the object processing policy comprises a decision condition, the decision condition is used for determining whether to allow a specified service logic to be executed on the requested object, the decision condition comprises a single attribute prohibition condition corresponding to the first attribute and an open condition corresponding to the prohibition condition, the single attribute prohibition condition is set according to the first attribute, and the open condition is set according to the second attribute;
the determining whether to allow the specified service logic to be executed on the object requested to be processed according to the object processing policy and the attribute information includes:
and determining whether the attribute information of the first attribute meets the single attribute prohibition condition according to the single attribute prohibition condition corresponding to the first attribute, if so, determining whether the attribute information of the second attribute meets the open condition, and if not, prohibiting the execution of the specified service logic on the object requested to be processed.
2. The method of claim 1,
the judgment condition further comprises a multi-attribute prohibition condition, the multi-attribute prohibition condition is set according to a plurality of attributes, and the plurality of attributes at least comprise the first attribute;
the method further comprises the following steps:
after determining that the specified service logic is allowed to be executed on the requested object according to the single attribute prohibition condition and the opening condition, determining whether the multi-attribute prohibition condition is met according to the acquired attribute information; if yes, forbidding executing the specified service logic to the requested object, otherwise, allowing executing the specified service logic to the requested object.
3. The method of claim 1,
the judgment condition further comprises a multi-attribute prohibition condition, the multi-attribute prohibition condition is set according to a plurality of attributes, and the plurality of attributes at least comprise the first attribute;
the method further comprises the following steps:
determining whether the multi-attribute prohibition condition is satisfied according to the acquired attribute information before determining that the specified service logic is allowed to be executed on the requested object according to the single-attribute prohibition condition and the opening condition; if yes, forbidding executing the specified service logic to the requested object;
the determining to allow the execution of the specified business logic on the requested object according to the single attribute prohibition condition and the opening condition includes:
if the multi-attribute prohibition condition is not met, determining whether the attribute information of the first attribute meets the single-attribute prohibition condition according to the single-attribute prohibition condition corresponding to the first attribute, if so, determining whether the attribute information of the second attribute meets the open condition, if not, prohibiting executing the specified service logic on the object requested to be processed, otherwise, allowing the specified service logic to be executed on the object requested to be processed.
4. The method of claim 1, wherein the obtaining attribute information based on the object handling request comprises:
and acquiring attribute information carried by the object processing request as first part of attribute information according to the object processing request, acquiring second part of attribute information according to the object processing request, and using the first part of attribute information and the second part of attribute information as attribute information for determining whether to allow the execution of specified service logic on the object requested to be processed.
5. The method of claim 1,
the object handling policy is stored as configuration information;
the method further comprises the following steps:
and updating the configuration information.
6. The method of any of claims 1 to 5, wherein the attribute information comprises attribute information for one or more of:
object properties, the object properties including properties of at least one dimension;
a client attribute comprising an attribute of at least one dimension;
user attributes including attributes of at least one dimension;
attributes associated with object handling requests, the attributes associated with object handling requests including attributes of at least one dimension.
7. The method of claim 6, wherein the client attributes comprise attributes for one or more of the following dimensions:
the type of the client application is used for indicating the bearing and display mode of the application program;
the type of the host terminal of the client application is used for indicating the type of the host terminal equipment of the client;
a version of the client application.
8. The method of any of claims 1 to 5, wherein:
the client device is used for realizing online transaction application;
the object is an online transaction object provided by the online transaction application;
the business logic includes business logic of transaction operations provided by the online transaction application.
9. An object processing apparatus, comprising:
a policy configuration module storing an object processing policy, the object processing policy including decision conditions for determining whether to allow execution of a specified business logic for a requested object;
the receiving module is used for receiving an object processing request sent by the client equipment;
the acquisition module acquires attribute information according to the object processing request, wherein the attribute information comprises attribute information of a first attribute and attribute information of a second attribute;
the determining module is used for determining whether to allow the execution of the specified service logic on the object requested to be processed according to the object processing strategy and the attribute information;
the processing module is used for carrying out corresponding processing according to the determination result of whether the object requested to be processed is allowed to execute the specified service logic;
the judgment condition comprises a single attribute prohibition condition corresponding to the first attribute and an open condition corresponding to the prohibition condition, the single attribute prohibition condition is set according to the first attribute, and the open condition is set according to the second attribute;
the determining module is specifically configured to: and determining whether the attribute information of the first attribute meets the single attribute prohibition condition according to the single attribute prohibition condition corresponding to the first attribute, if so, determining whether the attribute information of the second attribute meets the open condition, and if not, prohibiting the execution of the specified service logic on the object requested to be processed.
10. One or more computer-readable media having instructions stored thereon, which when executed by one or more processors, cause a communication device to perform the method of any of claims 1-8.
11. An apparatus, comprising:
one or more processors; and
one or more computer-readable media having instructions stored thereon that, when executed by the one or more processors, cause the apparatus to perform the method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711015142.5A CN109710418B (en) | 2017-10-25 | 2017-10-25 | Object processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711015142.5A CN109710418B (en) | 2017-10-25 | 2017-10-25 | Object processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109710418A CN109710418A (en) | 2019-05-03 |
| CN109710418B true CN109710418B (en) | 2022-09-27 |
Family
ID=66252207
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711015142.5A Active CN109710418B (en) | 2017-10-25 | 2017-10-25 | Object processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109710418B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112241866A (en) * | 2019-07-18 | 2021-01-19 | 腾讯科技（深圳）有限公司 | Service processing method and device, computer readable medium and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH09265398A (en) * | 1996-03-28 | 1997-10-07 | Fujitsu Ltd | Object orientated processing system and object orientated case device |
| US5819279A (en) * | 1995-04-27 | 1998-10-06 | Fujitsu Limited | Object data processing apparatus |
| CN105828110A (en) * | 2016-03-09 | 2016-08-03 | 乐视网信息技术（北京）股份有限公司 | Business object putting method and device and server |
| CN106296329A (en) * | 2015-06-09 | 2017-01-04 | 阿里巴巴集团控股有限公司 | Business object information processing, credential information processing method and processing device |
| CN106878043A (en) * | 2016-07-05 | 2017-06-20 | 阿里巴巴集团控股有限公司 | A kind of method and device for business processing |
-
2017
- 2017-10-25 CN CN201711015142.5A patent/CN109710418B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5819279A (en) * | 1995-04-27 | 1998-10-06 | Fujitsu Limited | Object data processing apparatus |
| JPH09265398A (en) * | 1996-03-28 | 1997-10-07 | Fujitsu Ltd | Object orientated processing system and object orientated case device |
| CN106296329A (en) * | 2015-06-09 | 2017-01-04 | 阿里巴巴集团控股有限公司 | Business object information processing, credential information processing method and processing device |
| CN105828110A (en) * | 2016-03-09 | 2016-08-03 | 乐视网信息技术（北京）股份有限公司 | Business object putting method and device and server |
| CN106878043A (en) * | 2016-07-05 | 2017-06-20 | 阿里巴巴集团控股有限公司 | A kind of method and device for business processing |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109710418A (en) | 2019-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200342338A1 (en) | Method for preloading application, storage medium, and terminal | |
| US9215074B2 (en) | Expressing intent to control behavior of application components | |
| US20230092579A1 (en) | Identifying product metadata from an item image | |
| CN104350497B (en) | User task completion via open actions and/or provider market | |
| KR102277087B1 (en) | Method of classifying contents and electronic device | |
| JP6585832B2 (en) | Smart card read / write method and apparatus | |
| US10423471B2 (en) | Virtualizing integrated calls to provide access to resources in a virtual namespace | |
| US20220092625A1 (en) | Electronic apparatus and operation method thereof | |
| CN104516885A (en) | Implementation method and device of browse program double-kernel assembly | |
| CN107329991A (en) | A kind of list access to web page and methods of exhibiting and its system | |
| Liu et al. | Understanding mobile users’ privacy expectations: A recommendation-based method through crowdsourcing | |
| CN112085567A (en) | Commodity recommendation method and device, electronic equipment and readable medium | |
| US20220309546A1 (en) | Ad Simulator Browser Extension | |
| CN104050001A (en) | Resource processing method, device and equipment based on Android system | |
| CN111274516B (en) | Page display method, page configuration method and device | |
| CN109710418B (en) | Object processing method and device | |
| US20170046756A1 (en) | Social network-based inventory management | |
| US20230153328A1 (en) | System and method for real-time customer classification | |
| CN113434063A (en) | Information display method, device and equipment | |
| US11243867B1 (en) | System for federated generation of user interfaces from a set of rules | |
| US11348163B1 (en) | System for presenting simplified user interface | |
| CN111881148A (en) | Object combination attribute determination method and device and electronic equipment | |
| US20200201498A1 (en) | Dynamic auxiliary user interface | |
| US11496605B1 (en) | Management of network resource transfers via network portals and physical portals | |
| US11972465B2 (en) | Social network-based inventory management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |