Method and device for processing attribute of object, electronic equipment and storage medium

Abstract

The invention provides an object attribute processing method and device, electronic equipment and a storage medium. A conversion request is obtained, the conversion request at least carries a target attribute, the target attribute is at least one attribute in multiple attributes of the object of the target type, the target attribute comprises a scene attribute, coupled with the service scene, of the object of the target type or a public attribute, decoupled with the service scene, of the object of the target type, and the object of the target type is converted according to the conversion request. And converting the recorded attribute value of the target attribute of each first object of the target type between the public attribute value of the public attribute decoupled with the business scene and the scene attribute value of the scene attribute coupled with the business scene. By means of the method and device, in the process that the attribute value of each attribute of the object of the target type is used for providing service externally, it is supported that the attribute value of the target attribute of the recorded object of the target type is converted between the scene attribute value of the scene attribute and the public attribute value of the public attribute in real time according to actual requirements.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for processing attributes of an object. Background Art

[0002] A property often has multiple attributes, such as price, price unit, orientation, number of bedrooms, number of halls, area, number of bathrooms, and decoration. The attributes of a property have attribute values, and the attribute values ​​of the attributes of the property are used to represent the specific conditions of the attributes of the property. Sometimes it is necessary to store the attributes of the property and the attribute values ​​of the attributes in the database for later use. Summary of the invention

[0003] The present application illustrates a method, device, electronic device and storage medium for processing attributes of an object.

[0004] In a first aspect, a method for processing attributes of an object is shown, including: obtaining a conversion request, the conversion request carrying at least a target attribute, the target attribute being at least one of a plurality of attributes possessed by an object of a target type, the target attribute comprising a scenario attribute of the object of the target type coupled with a business scenario or a public attribute decoupled from the business scenario, wherein the attribute value of the scenario attribute coupled with the business scenario is different according to the business scenario of the object of the target type, and the attribute value of the public attribute decoupled from the business scenario is the same in a plurality of business scenarios of the object of the target type; in a case where the target attribute is a scenario attribute of the object of the target type coupled with a business scenario, according to the conversion request, the attribute value of the target attribute of each first object of the target type that has been recorded is converted from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario; or, in a case where the target attribute is a public attribute of the object of the target type decoupled from the business scenario, according to the conversion request, the attribute value of the target attribute of each first object of the target type that has been recorded is converted from the public attribute value of the public attribute decoupled from the business scenario to the scenario attribute value of the scenario attribute coupled with the business scenario.

[0005] In a second aspect, a device for processing attributes of an object is shown, including: an acquisition module, used to acquire a conversion request, the conversion request at least carries a target attribute, the target attribute is at least one attribute among multiple attributes possessed by an object of the target type, the target attribute includes a scenario attribute of the object of the target type coupled with a business scenario or a public attribute decoupled from the business scenario, wherein the attribute value of the scenario attribute coupled with the business scenario varies according to the business scenario of the object of the target type, and the attribute value of the public attribute decoupled from the business scenario is the same in multiple business scenarios of the object of the target type; a first conversion module, used to convert the target attribute into a target attribute when the target attribute is In the case of a scenario attribute of an object of the target type coupled with a business scenario, the attribute value of the target attribute of each first object of the target type that has been recorded is converted from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario according to the conversion request; or, a second conversion module is used to convert the attribute value of the target attribute of each first object of the target type that has been recorded from the public attribute value of the public attribute decoupled from the business scenario to the scenario attribute value of the scenario attribute coupled with the business scenario according to the conversion request when the target attribute is a public attribute of an object of the target type decoupled from the business scenario.

[0006] In a third aspect, an electronic device is shown, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the method described in any of the above aspects.

[0007] In a fourth aspect, a non-transitory computer-readable storage medium is shown. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method described above.

[0008] In a fifth aspect, a computer program product is shown. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to perform the method described above.

[0009] The technical solution provided by this application may have the following beneficial effects:

[0010] In the present application, a conversion request is obtained, and the conversion request carries at least a target attribute. The target attribute is at least one of multiple attributes possessed by an object of the target type, and the target attribute includes a scenario attribute of the object of the target type that is coupled to a business scenario or a public attribute that is decoupled from the business scenario; wherein the attribute value of the scenario attribute coupled to the business scenario is different according to the business scenario of the object of the target type, and the attribute value of the public attribute that is decoupled from the business scenario is the same in multiple business scenarios of the object of the target type; in the case where the target attribute is a scenario attribute of the object of the target type that is coupled to the business scenario, according to the conversion request, the attribute value of the target attribute of each first object of the target type that has been recorded is converted from the scenario attribute value of the scenario attribute coupled to the business scenario to the public attribute value of the public attribute that is decoupled from the business scenario; or, in the case where the target attribute is a public attribute of the object of the target type that is decoupled from the business scenario, according to the conversion request, the attribute value of the target attribute of each first object of the target type that has been recorded is converted from the public attribute value of the public attribute that is decoupled from the business scenario to the scenario attribute value of the scenario attribute that is coupled to the business scenario.

[0011] Through the present application, in the process of using the attribute values ​​of each attribute of an object of the target type to provide external services, it is supported to convert the attribute values ​​of the target attributes of the object of the target type between the scene attribute values ​​of the scene attributes and the public attribute values ​​of the public attributes in real time according to actual needs. For example, it is supported to convert the attribute values ​​of the target attributes of each first object of the target type that have been recorded in real time according to actual needs from the scene attribute values ​​of the scene attributes coupled with the business scenario to the public attribute values ​​of the public attributes decoupled from the business scenario. It is supported to convert the attribute values ​​of the target attributes of each first object of the target type that have been recorded in real time according to actual needs from the public attribute values ​​of the public attributes decoupled from the business scenario to the scene attribute values ​​of the scene attributes coupled with the business scenario.

[0012] For example, in the case where a certain target attribute is a scenario attribute of the first object of the target type that is coupled with a business scenario, the scenario attribute value of the scenario attribute of the first object of the target type that is respectively coupled with each business scenario can be converted into a public attribute value of a public attribute of the first object of the target type that is decoupled from the business scenario, so that the attributes stored for the first object of the target type are changed from multiple scenario attributes to one public attribute, thereby reducing the number of attributes stored for the first object of the target type, and the attribute value of the attribute stored for the first object of the target type is changed from multiple scenario attribute values ​​to one public attribute value, thereby reducing the number of attribute values ​​stored for the first object of the target type. In this way, the number of attributes and attribute values ​​stored for the first object of the target type is reduced, and storage space can be further saved.

[0013] Alternatively, in the case where a certain target attribute is a public attribute of the first object of the target type that is decoupled from the business scenario, the public attribute value of the public attribute of the first object of the target type that is decoupled from the business scenario can be converted into a scene attribute value of the scene attribute of the first object of the target type that is respectively coupled to each business scenario, so that the attribute value of the attribute of the first object of the target type can meet the personalized needs of the corresponding business scenario, thereby improving the service quality of services provided externally using the attribute value of the attribute of the first object of the target type.

[0014] Secondly, in the present application, a conversion request is used to convert the attribute values ​​of an object of one type. Thus, a staff member can submit a conversion request once to enable the server to convert the attribute values ​​of the target attributes of multiple objects of one type between the scene attribute values ​​of the scene attributes and the public attribute values ​​of the public attributes, thereby achieving the effect of converting multiple objects with one request. The conversion has a high degree of automation and efficiency, and the staff member does not need to submit conversion requests separately for each object of a type, thus reducing labor costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a flowchart of the steps of a method for processing attributes of an object in the present application.

[0016] Figure 2 It is a structural block diagram of a device for processing attributes of an object in the present application.

[0017] Figure 3 It is a block diagram of an electronic device of the present application. DETAILED DESCRIPTION

[0018] The following will be combined with the drawings in this application to clearly and completely describe the technical solutions in this application. Obviously, the described embodiments are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0019] Sometimes, the same property may be used in multiple business scenarios, including leasing scenarios and buying and selling scenarios. For example, the same property may be used in both leasing scenarios and second-hand housing scenarios.

[0020] At present, various business scenarios are often highly independent. Therefore, for the same property, a copy of the property's attribute-related data (including the property's attributes and the attribute values ​​of the property's attributes) is stored separately for each business scenario. In this way, a copy of the property's attribute-related data stored separately for it can be used in each business scenario.

[0021] However, the inventors have discovered that storing a copy of property-related data for each business scenario would take up a large amount of storage space.

[0022] Thus, there is a need to save storage space.

[0023] In order to save storage space, the inventor analyzed the attribute-related data of the house and found that the attributes of the same house in each business scenario are the same. For example, the same house has the price, price unit, orientation, number of bedrooms, number of halls, area, number of bathrooms and decoration conditions in each business scenario. The attribute values ​​of the same attribute of the same house in each business scenario may be the same or different.

[0024] For example, the attribute values ​​of some attributes of the same house in various business scenarios are the same. For example, the attribute values ​​of the house's orientation, the number of bedrooms, the number of halls, the area, and the number of bathrooms are the same in both the rental and sale scenarios.

[0025] Secondly, the attribute values ​​of other attributes of the same property in various business scenarios are different. For example, the attribute values ​​of the price, the unit of price, and the decoration condition of the property in the rental scenario are different from those of the price, the unit of price, and the decoration condition of the property in the buying and selling scenarios.

[0026] For example, the attribute value of the price of a house in a rental scenario is 3000, the attribute value of the price unit is thousand, and the attribute value of the decoration condition is yes or no. The attribute value of the price of a house in a buying and selling scenario is 400, the attribute value of the price unit is ten thousand, and the attribute value of the decoration condition is fine decoration, simple decoration, or undecorated.

[0027] In view of the above findings, the inventors proposed the concept of the present invention.

[0028] The concept of the present invention includes: firstly reusing the attribute values ​​of the attributes for each business scenario to save storage space.

[0029] For example, for each business scenario, instead of storing the properties and their attribute values ​​separately, only one copy of "the properties and their attribute values" is stored for each business scenario. The "properties and their attribute values ​​of the property" can be shared and used as public attributes and their public attribute values ​​in various business scenarios, thereby reducing the number of copies of stored "properties and their attribute values ​​of the property", thus saving time.

[0030] In addition, for the other attributes, the other attributes of the property and the attribute values ​​of the other attributes are stored separately for each business scenario. The "other attributes of the property and the attribute values ​​of the other attributes" can be used in the corresponding business scenarios as scene attributes coupled with the business scenarios and the scene attribute values ​​of the scene attributes.

[0031] Furthermore, a certain attribute of a property and the attribute value stored separately for each business scenario can be reused for each business scenario. That is, it is no longer necessary to store the certain attribute of a property and the attribute value of the certain attribute separately for each business scenario, but only store one copy of "the certain attribute of a property and the attribute value of the certain attribute" for each business scenario.

[0032] Also, sometimes, in some business scenarios, a certain attribute of a property and the attribute value of the attribute need to be changed. For example, the attribute value needs to be more refined, etc., to meet the actual needs in these business scenarios. In this way, for the property and the attribute value of the attribute that are stored for reuse, it is necessary to store them separately for each business scenario. That is, it is no longer necessary to reuse the property and the attribute value of the attribute for each business scenario, and the property and the attribute value of the attribute of the property can be stored separately for each business scenario.

[0033] The concept of the present invention also includes: converting the attribute value of a certain attribute of the house source between the scene attribute value of the scene attribute and the public attribute value of the public attribute.

[0034] Specifically, refer to Figure 1 , shows a flowchart of the steps of a method for processing attributes of an object of the present application, the method can be applied to a server, etc., wherein the method can specifically include the following steps:

[0035] In step S101, a conversion request is obtained, and the conversion request carries at least a target attribute. The target attribute is at least one of multiple attributes possessed by an object of the target type. The target attribute includes a scenario attribute of the object of the target type that is coupled with a business scenario or a public attribute that is decoupled from the business scenario. The attribute value of the scenario attribute coupled with the business scenario varies according to the business scenario of the object of the target type, and the attribute value of the public attribute that is decoupled from the business scenario is the same in multiple business scenarios of the object of the target type.

[0036] In this application, an attribute has an attribute value, and thus, the attribute value is attribute-dependent.

[0037] A target attribute of an object of the target type may be converted between a scene attribute and a common attribute, and an attribute value of a target attribute of an object of the target type may be converted between a scene attribute value of a scene attribute and a common attribute value of a common attribute.

[0038] Objects may include commodities, and commodities may include vehicles or houses.

[0039] The types of objects include vehicle types, house types, or electronic product types, etc. Vehicle type objects generally refer to vehicles, house type objects generally refer to houses, and electronic product type objects generally refer to electronic products.

[0040] The target type object may include all objects of the target type, for example, the target type object corresponds to all objects of the target type that the server has involved in. The objects that the server has involved in include: objects that have stored attributes and attribute values ​​of the attributes in the server.

[0041] Objects often have multiple attributes, each of which has an attribute value, which can reflect the specific situation of the attribute.

[0042] Objects of the same type have the same attributes, and the attribute values ​​of the same attributes of two different objects of the same type may be the same or different.

[0043] For example, when the target type is a house type, the object of the target type is a house, and the attributes of the house include price, price unit, orientation, number of bedrooms, number of bathrooms, number of halls, area, decoration, name of the community, building number, floor, door number, etc. The target attribute of the house may be at least one of price, price unit, orientation, number of bedrooms, number of bathrooms, number of halls, area, decoration, name of the community, building number, floor, door number, etc.

[0044] The attribute values ​​of the attributes of a house are used to indicate the specific circumstances of the attributes of the house. For example, the number of bathrooms (attribute) of the house is 2 (attribute value), the number of halls (attribute) of the house is 1 (attribute value), the building number (attribute) of the house is 9# (attribute value), etc.

[0045] Business scenarios include business scenarios to which the object can be applied.

[0046] For example, when the object is a house, the house can be bought and sold, or rented, and the buying and selling business scenarios also include second-hand house buying and selling scenarios or new house buying and selling scenarios.

[0047] In this way, for houses, business scenarios may include rental scenarios, second-hand house sales scenarios, and new house sales scenarios, etc.

[0048] Among the multiple attributes of an object, some attributes are scenario attributes coupled with business scenarios, and some attributes are public attributes decoupled from business scenarios.

[0049] For example, for a house, the price, price unit, and decoration condition are scenario attributes coupled with the business scenario.

[0050] For example, the price of a house in a rental scenario is different from that in a sale and purchase scenario, and the price units are different. For example, the unit of the house price in a rental scenario may be thousands, and the unit of the house price in a sale and purchase scenario may be ten thousand, one hundred thousand, one million, or ten million, etc. It can be seen that the price may change with the change of the business scenario, and the price unit may change with the change of the business scenario.

[0051] For another example, in a rental scenario, the decoration condition of a house can be simple or fine, etc., and in a sale scenario, the decoration condition of a house can be rough, undecorated or decorated, etc. It can be seen that the decoration condition can change with the changes in the business scenario.

[0052] The attribute values ​​of the orientation, number of bedrooms, number of bathrooms, number of halls, area, name of the community, building number, floor, door number, etc. of the house in the rental scenario and the sale scenario can be the same, that is, they can be unchanged by the change of the business scenario.

[0053] In this way, if a certain attribute of an object is a scenario attribute of the object coupled with a business scenario, the scenario attribute value of the scenario attribute of the object coupled with the business scenario may be different depending on the business scenario. For example, the scenario attribute values ​​of the same scenario attribute of the same object coupled with different business scenarios may be different.

[0054] Alternatively, if a property of an object is a public property of the object that is decoupled from a business scenario, the property value of the public property of the object that is decoupled from a business scenario may not be different with different business scenarios, that is, the public property value of the public property of the same object that is decoupled from a business scenario may be the same in all business scenarios. For example, in any business scenario, the public property value of the same public property of the same object that is decoupled from a business scenario may be the same.

[0055] The target attribute may be a scenario attribute of an object of the target type coupled with a business scenario, and the attribute value of the target attribute may be a scenario attribute value of the scenario attribute of the object of the target type coupled with a business scenario.

[0056] Alternatively, the target attribute may be a common attribute of an object of the target type that is decoupled from the business scenario, and the attribute value of the target attribute may be a common attribute value of the common attribute of the object of the target type that is decoupled from the business scenario.

[0057] According to actual needs, sometimes it may be necessary to convert the attribute value of the target attribute of the target type object between the public attribute value of the public attribute decoupled from the business scenario and the scenario attribute value of the scenario attribute coupled with the business scenario. In this way, the staff can submit a conversion request to the server, and the conversion request is used to convert the attribute value of the target attribute of the target type object between the scenario attribute value of the scenario attribute and the public attribute value of the public attribute.

[0058] For example, according to actual needs, it is necessary to convert the attribute value of the target attribute of the target type object from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario. In this way, the staff can submit a conversion request to the server. The conversion request is used to convert the attribute value of the target attribute of the target type object from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario.

[0059] Alternatively, according to actual needs, it is necessary to convert the attribute value of the target attribute of the target type object from the public attribute value of the public attribute decoupled from the business scenario to the scene attribute value of the scene attribute coupled with the business scenario. In this way, the staff can submit a conversion request to the server, and the conversion request is used to convert the attribute value of the target attribute of the target type object from the public attribute value of the public attribute decoupled from the business scenario to the scene attribute value of the scene attribute coupled with the business scenario.

[0060] In step S102, in the case where the target attribute is a scenario attribute of an object of the target type coupled with the business scenario, the attribute values ​​of the recorded target attributes of each first object of the target type are converted from the scenario attribute values ​​of the scenario attribute coupled with the business scenario to the public attribute values ​​of the public attributes decoupled from the business scenario according to the conversion request.

[0061] In the present application, the target attribute of the first object of the target type and the attribute value of the target attribute have been recorded in a database or other storage form. In the following, the present application is described by taking the storage form of the database as an example.

[0062] It should be noted that the target type object is a general reference, for example, a general reference to multiple objects of the target type (for example, all objects of the target type, etc.). The first object of the target type is a specific reference, for example, a specific reference to an object of the target type whose target attributes and attribute values ​​of the target attributes have been stored in the database.

[0063] In one embodiment, when a conversion request is used to convert the attribute value of a target attribute of an object of a target type from the attribute value of a scenario attribute coupled to a business scenario to the public attribute value of a public attribute decoupled from the business scenario, the attribute value of the target attribute of a first object of the target type can be converted in a database from the scenario attribute value of the scenario attribute coupled to the business scenario to the public attribute value of the public attribute decoupled from the business scenario.

[0064] Afterwards, the target attribute of the first object of the target type is a public attribute decoupled from the business scenario, and is no longer a scenario attribute coupled to the business scenario.

[0065] Furthermore, the attribute value of the target attribute of the first object of the target type is the public attribute value of the public attribute decoupled from the business scenario, and is no longer the scenario attribute value of the scenario attribute coupled with the business scenario.

[0066] In this way, what is stored in the database are the target attributes (in this case, the public attributes) of the first object of the target type that are decoupled from the business scenario and the public attribute values ​​of the target attributes.

[0067] Afterwards, in any business scenario, the target attribute (in this case, a public attribute) decoupled from the business scenario and the public attribute value of the target attribute of the first object using the target type can be shared.

[0068] Furthermore, for any business scenario, the target attribute of the first object of the target type coupled to the business scenario and the scenario attribute value of the target attribute of the first object of the target type coupled to the business scenario are no longer stored separately in the database. The same is true for each other business scenario.

[0069] For details, please refer to the embodiments shown below, which will not be described in detail here.

[0070] In step S103, when the target attribute is a common attribute of an object of the target type that is decoupled from the business scenario, the attribute values ​​of the recorded target attributes of each first object of the target type are converted from the common attribute values ​​of the common attributes decoupled from the business scenario to the scenario attribute values ​​of the scenario attributes coupled to the business scenario according to the conversion request.

[0071] In one embodiment, when a conversion request is used to convert the attribute value of a target attribute of an object of a target type from a public attribute value of a public attribute decoupled from a business scenario to a scenario attribute value of a scenario attribute coupled to a business scenario, the attribute value of the target attribute of a first object of the target type can be converted in a database from the public attribute value of the public attribute decoupled from the business scenario to the scenario attribute value of the scenario attribute coupled to the business scenario.

[0072] Afterwards, the target attribute of the first object of the target type is a scenario attribute coupled with the business scenario, and is no longer a public attribute decoupled from the business scenario.

[0073] Furthermore, the attribute value of the target attribute of the first object of the target type is the scenario attribute value of the scenario attribute coupled with the business scenario, and is no longer the public attribute value of the public attribute decoupled from the business scenario.

[0074] Afterwards, the target attribute of the first object of the target type that is decoupled from the business scenario and the common attribute value of the target attribute are no longer stored in the database.

[0075] Afterwards, for any business scenario, the target attribute (in this case, the scenario attribute) of the first object of the target type coupled with the business scenario and the scenario attribute value of the target attribute of the first object of the target type coupled with the business scenario are separately stored in the database (the scenario attribute values ​​of the same scenario attribute of the first object of the target type coupled with each business scenario may be the same, may not be completely the same, or may be completely different). The same is true for each other business scenario.

[0076] In this way, in any business scenario, the target attribute (in this case, the scenario attribute) of the first object of the target type coupled with the business scenario and the scenario attribute value of the target attribute can be used.

[0077] For details, please refer to the embodiments shown below, which will not be described in detail here.

[0078] Through the present application, in the process of using the attribute values ​​of each attribute of an object of the target type to provide external services, it is supported to convert the attribute values ​​of the target attributes of the object of the target type between the scene attribute values ​​of the scene attributes and the public attribute values ​​of the public attributes in real time according to actual needs. For example, it is supported to convert the attribute values ​​of the target attributes of each first object of the target type that have been recorded in real time according to actual needs from the scene attribute values ​​of the scene attributes coupled with the business scenario to the public attribute values ​​of the public attributes decoupled from the business scenario. It is supported to convert the attribute values ​​of the target attributes of each first object of the target type that have been recorded in real time according to actual needs from the public attribute values ​​of the public attributes decoupled from the business scenario to the scene attribute values ​​of the scene attributes coupled with the business scenario.

[0079] For example, in the case where a certain target attribute is a scenario attribute of the first object of the target type that is coupled with a business scenario, the scenario attribute value of the scenario attribute of the first object of the target type that is respectively coupled with each business scenario can be converted into a public attribute value of a public attribute of the first object of the target type that is decoupled from the business scenario, so that the attributes stored for the first object of the target type are changed from multiple scenario attributes to one public attribute, thereby reducing the number of attributes stored for the first object of the target type, and the attribute value of the attribute stored for the first object of the target type is changed from multiple scenario attribute values ​​to one public attribute value, thereby reducing the number of attribute values ​​stored for the first object of the target type. In this way, the number of attributes and attribute values ​​stored for the first object of the target type is reduced, and storage space can be further saved.

[0080] Alternatively, in the case where a certain target attribute is a public attribute of the first object of the target type that is decoupled from the business scenario, the public attribute value of the public attribute of the first object of the target type that is decoupled from the business scenario can be converted into a scene attribute value of the scene attribute of the first object of the target type that is respectively coupled to each business scenario, so that the attribute value of the attribute of the first object of the target type can meet the personalized needs of the corresponding business scenario, thereby improving the service quality of services provided externally using the attribute value of the attribute of the first object of the target type.

[0081] Secondly, in the present application, a conversion request is used to convert the attribute values ​​of an object of one type. Thus, a staff member can submit a conversion request once to enable the server to convert the attribute values ​​of the target attributes of multiple objects of one type between the scene attribute values ​​of the scene attributes and the public attribute values ​​of the public attributes, thereby achieving the effect of converting multiple objects with one request. The conversion has a high degree of automation and efficiency, and the staff member does not need to submit conversion requests separately for each object of a type, thus reducing labor costs.

[0082] In one embodiment, when a conversion request is used to convert the attribute value of a target attribute of an object of a target type from a scenario attribute value of a scenario attribute coupled to a business scenario to a public attribute value of a public attribute decoupled from the business scenario, it is explained that the target attribute of the first object of the target type is currently the scenario attribute of the first object of the target type coupled to the business scenario, and that the attribute value of the target attribute of the first object of the target type is currently the scenario attribute value of the scenario attribute of the first object of the target type coupled to the business scenario. Secondly, the scenario attribute values ​​of the target attributes (scenario attributes) of the first object of the target type that are respectively coupled to various business scenarios may be the same, may not be completely the same, or may be completely different.

[0083] In this embodiment, step S102 may include:

[0084] In step S201, a common attribute value of a target attribute of a first object of a target type that is decoupled from a business scenario is obtained.

[0085] In one embodiment, the public attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario may be submitted in real time by the staff, etc. In this way, the public attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario and submitted in real time by the staff can be obtained.

[0086] For example, when a conversion request is received from a staff member, a submission page can be provided to the staff member. The submission page is used to submit the common attribute values ​​of the target attributes of the target type object that are decoupled from the business scenario, so that the staff member can submit the common attribute values ​​of the target attributes of the first object of the target type that are decoupled from the business scenario to the server according to the submission page. In this way, the server can obtain the common attribute values ​​of the target attributes of the first object of the target type that are decoupled from the business scenario submitted by the staff according to the submission page.

[0087] Alternatively, in one embodiment, this step may be implemented by the following process, including:

[0088] 2011. Obtain scenario attribute values ​​of target attributes of a first object of a target type that are respectively coupled to each business scenario.

[0089] In one embodiment, for any object of the target type, a public attribute set corresponding to the object and a scenario attribute set of the object coupled to each business scenario (different from scenario attribute sets coupled to different business scenarios) are stored in the database.

[0090] The public attribute set corresponding to the object and the scenario attribute set of the object coupled with each business scenario can be identified using the ID (Identity Document) of the object.

[0091] The public attribute set corresponding to the object is used to store the public attributes of the object that are decoupled from the business scenario and the public attribute values ​​of the public attributes of the object that are decoupled from the business scenario.

[0092] Among them, the public attributes of the object that are decoupled from the business scenario and the public attribute values ​​of the public attributes of the object that are decoupled from the business scenario can be stored in the public attribute set corresponding to the object in the form of "key-value".

[0093] For the scene attribute set of the object coupled with any business scenario, the scene attribute set of the object coupled with the business scenario is used to store the scene attributes of the object coupled with the business scenario and the scene attribute values ​​of the scene attributes of the object coupled with the business scenario. For example, the scene attributes of the object coupled with the business scenario and the scene attribute values ​​of the scene attributes of the object coupled with the business scenario can be stored in the scene attribute set of the object coupled with the business scenario in the form of "key-value". The same is true for the scene attribute set of the object coupled with each other business scenario.

[0094] Additionally, the same is true for every other object of the target type.

[0095] In this way, the scenario attribute set of the first object of the target type, which is respectively coupled with each business scenario, can be searched in the database according to the ID of the first object of the target type.

[0096] Then, the scenario attribute value of the target attribute is searched in the scenario attribute set of the first object of the target type respectively coupled with each business scenario, and the found target attribute value is used as the scenario attribute value of the target attribute of the first object of the target type respectively coupled with each business scenario.

[0097] 2012. Obtain a common attribute value of a target attribute of the first object of the target type that is decoupled from the business scenario according to the scenario attribute value of the target attribute of the first object of the target type that is respectively coupled to each business scenario.

[0098] In one embodiment, this step can be implemented through the following process, including:

[0099] 11) Determine whether the scenario attribute values ​​of the target attributes of the first object of the target type, which are respectively coupled to each business scenario, are all the same.

[0100] 12) When the scenario attribute values ​​of the target attributes of the first object of the target type that are coupled to each business scenario are the same, the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario is obtained according to the scenario attribute value of the target attribute of the first object of the target type that is coupled to any business scenario.

[0101] For example, when the scenario attribute values ​​of the target attributes of the first object of the target type that are coupled to various business scenarios are the same, the scenario attribute value of the target attribute of the first object of the target type that is coupled to any business scenario can be determined as the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario.

[0102] 13) When the scenario attribute values ​​of the target attributes of the first object of the target type that are coupled to each business scenario are not all the same or all different, obtain the specified business scenario, and obtain the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario based on the scenario attribute value of the target attribute coupled to the specified business scenario.

[0103] In one embodiment, the specified business scenario may be specified by the staff in advance according to the actual situation. For example, for a house, the staff may specify a rental scenario or a sale scenario in advance according to the actual situation. In this way, the server may obtain the business scenario specified in advance by the staff.

[0104] Alternatively, in another embodiment, the specified business scenario can be specified by the staff in real time according to actual conditions. For example, when the scenario attribute values ​​of the target attributes of the first object of the target type that are respectively coupled to each business scenario are not all the same or completely different, a scenario specification page can be provided to the staff. The scenario specification page is used to specify a business scenario among multiple business scenarios, so that the staff can submit the specified business scenario to the server according to the scenario instruction page. In this way, the server can obtain the specified business scenario submitted by the staff according to the scenario specification page.

[0105] Afterwards, the scenario attribute value of the target attribute of the first object of the target type coupled with the specified business scenario may be determined as the common attribute value of the target attribute of the first object of the target type decoupled from the business scenario.

[0106] In step S202, the target attributes and the common attribute values ​​of the target attributes of the first object of the target type decoupled from the business scenario are stored in a common attribute set corresponding to each first object of the target type; and, for any business scenario, in the scenario attribute set coupled to the business scenario of each first object of the target type, the target attributes and the scenario attribute values ​​of the target attributes of the first objects of the target type coupled to the business scenario are deleted; wherein, the scenario attributes and the scenario attribute values ​​of the target attributes coupled to the business scenario of the object of the target type correspond to different scenario attribute sets according to different business scenarios, and the common attributes and the common attribute values ​​of the target attributes decoupled from the business scenario of the object of the target type correspond to the same common attribute set for multiple business scenarios.

[0107] The same is true for every other business scenario.

[0108] In one embodiment, for any object, a public attribute set corresponding to the object and a scenario attribute set of the object coupled to each business scenario are stored in the database. The public attribute set and the scenario attribute set can be found in the above description and will not be described in detail here.

[0109] In view of this, for the first object of the target type, the target attributes and the common attribute values ​​of the target attributes of the first object of the target type that are decoupled from the business scenario may be stored in a common attribute set corresponding to the first object of the target type.

[0110] For example, the target attribute and the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario are stored in the common attribute set corresponding to the first object of the target type in the form of "key-value".

[0111] For any business scenario, in the scenario attribute set coupled to the business scenario of the first object of the target type, the target attribute coupled to the business scenario and the scenario attribute value of the target attribute can be deleted. The same is true for each other business scenario.

[0112] In this way, the attribute value of the target attribute of the object of the target type is converted from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario.

[0113] Furthermore, subsequent staff may also need to upload the attributes of the second object of the target type and the attribute values ​​of the attributes to the server.

[0114] Objects of the same type have the same attributes. The attribute values ​​of the same attributes of two different objects of the same type may be the same or different.

[0115] The second object is of the same type as the first object, so the server may store the attributes and attribute values ​​of the second object of the target type in the same manner as the server stores the attributes and attribute values ​​of the first object of the target type.

[0116] Since in the aforementioned embodiment, the attribute value of the target attribute of the first object of the target type has been converted from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario according to the conversion request, the target attribute of the second object of the target type is the public attribute decoupled from the business scenario, and the attribute value of the target attribute of the second object of the target type is the public attribute value of the public attribute decoupled from the business scenario.

[0117] Therefore, in order to facilitate the staff to subsequently upload the target attribute and the attribute value of the second object of the target type, in another embodiment of the present application, the method may further include:

[0118] In step S301, for any business scenario, a first upload page corresponding to the business scenario is obtained, and the first upload page is at least used to upload the scenario attribute value of the target attribute of the target type object coupled with the business scenario. The first upload page has at least a selection control of the target attribute, and the selection control of the target attribute includes a plurality of scenario attribute values ​​for selection of the target attribute of the target type object coupled with the business scenario.

[0119] For objects of the target type, different business scenarios correspond to different upload pages. The upload page corresponding to a certain business scenario is used to upload various scenario attributes of the target type object that are coupled with the business scenario and the attribute values ​​of each scenario attribute, and is used to upload various public attributes of the target type object that are decoupled from the business scenario and the attribute values ​​of each public attribute. Each scenario attribute includes the target attribute.

[0120] In order to facilitate staff to upload the attributes and attribute values ​​of the target type object under a business scenario through the upload page corresponding to the business scenario, for any business scenario of the target type object and for any scenario attribute coupled with the task scenario, the selection control on the upload page corresponding to the business scenario can have multiple selectable scenario attribute values ​​of the scenario attribute of the target type object coupled with the business scenario (for direct selection by staff), and the same is true for each other scenario attribute coupled with each other business scenario.

[0121] Secondly, for any public attribute of the target type of object that is decoupled from the business scenario, the selection control on the upload page corresponding to the business scenario can have multiple public attribute values ​​for selection of the public attribute of the target type of object that is decoupled from the business scenario (for direct selection by the staff), and the same is true for each other public attribute of the target type of object that is decoupled from the business scenario.

[0122] The same is true for every other business scenario that an object of the target type has.

[0123] The first upload page is applicable to the situation before: "converting the attribute value of the target attribute of the target type object from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario according to the conversion request."

[0124] That is, the "multiple selectable scenario attribute values ​​of the target attribute of the target type object coupled with the business scenario" in the selection control in the first upload page is for the situation before "converting the attribute value of the target attribute of the target type object from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario according to the conversion request."

[0125] However, after "converting the attribute value of the target attribute of the target type object from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario according to the conversion request", the "multiple selectable scenario attribute values ​​of the target attribute of the target type object coupled with the business scenario" in the selection control in the first upload page is no longer applicable, and the first upload page needs to be adjusted to make it applicable to the situation after "converting the attribute value of the target attribute of the target type object from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario according to the conversion request".

[0126] So that the selection control on it includes multiple selectable common attribute values ​​of the target attribute of the target type object that is decoupled from the business scenario, so that the staff can choose.

[0127] In step S302, a plurality of selectable common attribute values ​​of a target attribute of an object of a target type that is decoupled from a business scenario are obtained.

[0128] In the present application, when the staff has previously submitted a conversion request for converting the attribute value of the target attribute of an object of the target type from the scenario attribute value of the scenario attribute coupled to the business scenario to the public attribute value of the public attribute decoupled from the business scenario, the staff can also set multiple selectable public attribute values ​​of the target attribute of the object of the target type that are decoupled from the business scenario, and form corresponding table items of the target type, the target attribute, and the multiple selectable public attribute values ​​of the target attribute of the set target type that are decoupled from the business scenario, and store them in the first correspondence between the type, the attribute, and the multiple selectable public attribute values ​​of the attribute.

[0129] Thus, in this step, multiple public attribute values ​​corresponding to the target type and target attribute can be found in the first correspondence between the type, attribute and multiple public attribute values ​​for selection, and used as multiple public attribute values ​​for selection of the target attribute of the target type object decoupled from the business scenario.

[0130] In step S303, when the multiple selectable public attribute values ​​are different from the multiple selectable scenario attribute values ​​in the selection control, the multiple selectable scenario attribute values ​​in the selection control are replaced with the multiple selectable public attribute values ​​to obtain a second upload page corresponding to the business scenario. The second upload page is at least used to upload the public attribute values ​​of the target attributes of the target type of object that are decoupled from the business scenario.

[0131] In this way, when the staff needs to upload the target attribute of the second object of the target type and the attribute value of the target attribute of the second object of the target type in the business scenario, the staff can send a page acquisition request to the server using the terminal, and the page acquisition request is used to request to obtain the second upload page corresponding to the business scenario. The server can receive the page acquisition request sent by the terminal, and obtain the second upload page corresponding to the business scenario according to the acquisition request. And provide the second upload page corresponding to the business scenario to the terminal.

[0132] This allows staff to conveniently select the public attribute value of the target attribute of the second object of the target type according to a plurality of selectable public attribute values ​​in the selection control in the second upload page, and upload the target attribute of the second object of the target type and the public attribute value of the target attribute of the second object of the target type through the second upload page, thereby facilitating the server to store the uploaded target attribute of the second object of the target type and the public attribute value of the target attribute of the second object of the target type in the form of "key-value" in the public attribute set corresponding to the second object of the target type.

[0133] In one embodiment, when a conversion request is used to convert the attribute value of a target attribute of an object of a target type from a public attribute value of a public attribute decoupled from a business scenario to a scene attribute value of a scene attribute coupled to a business scenario, it is described that the target attribute of the first object of the target type is currently a public attribute of the first object of the target type that is decoupled from the business scenario, and that the attribute value of the target attribute of the first object of the target type is currently a public attribute value of the public attribute of the first object of the target type that is decoupled from the business scenario. Secondly, the scene attribute values ​​of the target attributes (scene attributes) of the first object of the target type that are respectively coupled to various business scenarios may be the same, may not be completely the same, or may be completely different.

[0134] In this embodiment, step S103 may include:

[0135] In step S401, for each business scenario, a scenario attribute value of a target attribute of each first object of a target type coupled with the business scenario is obtained.

[0136] In one embodiment, the scenario attribute value of the target attribute of the first object of the target type coupled with the business scenario may be submitted in real time by the staff. In this way, the scenario attribute value of the target attribute of the first object of the target type coupled with the business scenario submitted in real time by the staff may be obtained.

[0137] For example, when a conversion request is received from a staff member, a submission page can be provided to the staff member, and the submission page is used to submit the scenario attribute value of the target attribute of the first object of the target type coupled with the business scenario, so that the staff member can submit the scenario attribute value of the target attribute of the first object of the target type coupled with the business scenario to the server according to the submission page. In this way, the server can obtain the scenario attribute value of the target attribute of the first object of the target type coupled with the business scenario submitted by the staff according to the submission page.

[0138] Alternatively, in one embodiment, this step may be implemented by the following process, including:

[0139] 4011. Obtain a common attribute value of a target attribute of each first object of the target type that is decoupled from the business scenario.

[0140] In one embodiment, for any object of the target type, a public attribute set corresponding to the object and a scenario attribute set of the object coupled to each business scenario (different from scenario attribute sets coupled to different business scenarios) are stored in the database.

[0141] The public attribute set corresponding to the object and the scenario attribute set of the object coupled with each business scenario can be identified using the ID (Identity Document) of the object.

[0142] The public attribute set corresponding to the object is used to store the public attributes of the object that are decoupled from the business scenario and the public attribute values ​​of the public attributes of the object that are decoupled from the business scenario.

[0143] Among them, the public attributes of the object that are decoupled from the business scenario and the public attribute values ​​of the public attributes of the object that are decoupled from the business scenario can be stored in the public attribute set corresponding to the object in the form of "key-value".

[0144] For the scene attribute set of the object coupled with any business scenario, the scene attribute set of the object coupled with the business scenario is used to store the scene attributes of the object coupled with the business scenario and the scene attribute values ​​of the scene attributes of the object coupled with the business scenario. For example, the scene attributes of the object coupled with the business scenario and the scene attribute values ​​of the scene attributes of the object coupled with the business scenario can be stored in the scene attribute set of the object coupled with the business scenario in the form of "key-value". The same is true for the scene attribute set of the object coupled with each other business scenario.

[0145] Additionally, the same is true for every other object of the target type.

[0146] In this way, the public attribute set corresponding to the first object of the target type may be searched in the database according to the ID of the first object of the target type.

[0147] Then, the public attribute value of the target attribute is searched in the public attribute set corresponding to the first object of the target type, and the found public attribute value is used as the public attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario.

[0148] 4012. According to the common attribute value of the target attribute decoupled from the business scenario of each first object of the target type and the business scenario, respectively obtain the scenario attribute value of the target attribute coupled to the business scenario of each first object of the target type.

[0149] In one embodiment, for each first object of the target type, the public attribute value of the target attribute decoupled from the business scenario of the first object of the target type and the scene attribute value corresponding to the business scenario can be searched in the second correspondence between the public attribute value of the target attribute decoupled from the business scenario of the target type object, the business scenario, and the scene attribute value of the target attribute coupled to the business scenario of the target type object, and used as the scene attribute value of the target attribute of the first object of the target type coupled to the business scenario.

[0150] The second corresponding relationship is manually set in advance, and each corresponding table entry represents: the scenario attribute value to which the public attribute value of the object of the target type needs to be switched in a business scenario.

[0151] In step S402, in the scenario attribute set corresponding to the business scenario of each first object of the target type, the target attribute and the scenario attribute value of the target attribute of each first object of the target type coupled with the business scenario are stored, and, in the public attribute set corresponding to the first object of the target type, the public attribute value of the target attribute and the target attribute of each first object of the target type decoupled from the business scenario is deleted.

[0152] In one embodiment, for any object, a public attribute set corresponding to the object and a scenario attribute set of the object coupled to each business scenario are stored in the database. The public attribute set and the scenario attribute set can be found in the above description and will not be described in detail here.

[0153] In view of this, for the first object of the target type, the target attribute and the scenario attribute value of the target attribute of the first object of the target type coupled with the business scenario can be stored in a scenario attribute set of the first object of the target type coupled with the business scenario.

[0154] For example, the target attribute and the scenario attribute value of the target attribute of the first object of the target type coupled with the business scenario are stored in the scenario attribute set of the first object of the target type coupled with the business scenario in the form of "key-value".

[0155] The same is true for every other business scenario.

[0156] Furthermore, in the public attribute set corresponding to the first object of the target type, the target attribute and the public attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario may be deleted.

[0157] In this way, the attribute value of the target attribute of the object of the target type is converted from the public attribute value of the public attribute decoupled from the business scenario to the scenario attribute value of the scenario attribute coupled to the business scenario.

[0158] Furthermore, subsequent staff may also need to upload the attributes of the second object of the target type and the attribute values ​​of the attributes to the server.

[0159] Objects of the same type have the same attributes. The attribute values ​​of the same attributes of two different objects of the same type may be the same or different.

[0160] The second object is of the same type as the first object, so the server may store the attributes and attribute values ​​of the second object of the target type in the same manner as the server stores the attributes and attribute values ​​of the first object of the target type.

[0161] Since in the aforementioned embodiment, the attribute value of the target attribute of the object of the target type has been converted from the public attribute value of the public attribute decoupled from the business scenario to the scene attribute value of the scene attribute coupled to the business scenario according to the conversion request, the target attribute of the second object of the target type is the scene attribute coupled to the business scenario, and the attribute value of the target attribute of the second object of the target type is the scene attribute value of the scene attribute coupled to the business scenario.

[0162] Therefore, in order to facilitate the staff to subsequently upload the target attribute and the attribute value of the second object of the target type, in another embodiment of the present application, the method may further include:

[0163] In step S501, for any business scenario, a third upload page corresponding to the business scenario is obtained, and the third upload page is at least used to upload the public attribute value of the target attribute of the target type object decoupled from the business scenario. The third upload page has at least a selection control for the target attribute, and the selection control for the target attribute includes multiple public attribute values ​​for selection of the target attribute of the target type object decoupled from the business scenario.

[0164] For objects of the target type, different business scenarios correspond to different upload pages. The upload page corresponding to a certain business scenario is used to upload various scenario attributes of the target type object that are coupled with the business scenario and the attribute values ​​of each scenario attribute, and is used to upload various public attributes of the target type object that are decoupled from the business scenario and the attribute values ​​of each public attribute. Each scenario attribute includes the target attribute.

[0165] In order to facilitate staff to upload the attributes and attribute values ​​of the target type object under a business scenario through the upload page corresponding to the business scenario, for any business scenario of the target type object and for any scenario attribute coupled with the task scenario, the selection control on the upload page corresponding to the business scenario can have multiple selectable scenario attribute values ​​of the scenario attribute of the target type object coupled with the business scenario (for direct selection by staff), and the same is true for each other scenario attribute coupled with each other business scenario.

[0166] Secondly, for any public attribute of the target type of object that is decoupled from the business scenario, the selection control on the upload page corresponding to the business scenario can have multiple public attribute values ​​for selection of the public attribute of the target type of object that is decoupled from the business scenario (for direct selection by the staff), and the same is true for each other public attribute of the target type of object that is decoupled from the business scenario.

[0167] The same is true for every other business scenario that an object of the target type has.

[0168] The third upload page is applicable to the situation before: "Converting the attribute value of the target attribute of the target type object from the public attribute value of the public attribute decoupled from the business scenario to the scenario attribute value of the scenario attribute coupled to the business scenario according to the conversion request."

[0169] That is, the "multiple selectable common attribute values ​​of the target attribute of the target type object decoupled from the business scenario" in the selection control in the third upload page is for the situation before "converting the attribute value of the target attribute of the target type object from the public attribute value of the public attribute decoupled from the business scenario to the scenario attribute value of the scenario attribute coupled with the business scenario according to the conversion request."

[0170] However, after "converting the attribute value of the target attribute of the target type object from the public attribute value of the public attribute decoupled from the business scenario to the scenario attribute value of the scenario attribute coupled with the business scenario", the "multiple public attribute values ​​for selection of the target attribute of the target type object decoupled from the business scenario" in the selection control in the third upload page is no longer applicable, and the third upload page needs to be adjusted to make it applicable to the situation after "converting the attribute value of the target attribute of the target type object from the public attribute value of the public attribute decoupled from the business scenario to the scenario attribute value of the scenario attribute coupled with the business scenario according to the conversion request".

[0171] So that the selection control thereon includes multiple selectable scenario attribute values ​​of the target attribute of the target type object coupled with the business scenario, so that the staff can select.

[0172] In step S502, a plurality of selectable scenario attribute values ​​of a target attribute of an object of a target type coupled with the business scenario are obtained.

[0173] In the case where the staff has previously submitted a conversion request for converting the attribute value of the target attribute of the target type object from the public attribute value of the public attribute decoupled from the business scenario to the scene attribute value of the scene attribute coupled with the business scenario, for any business scenario, the staff can also set multiple scene attribute values ​​for the target attribute of the target type object coupled with the business scenario for selection, and form corresponding table items with the target type, the business scenario, the target attribute, and the multiple scene attribute values ​​for the target attribute of the set target type object coupled with the business scenario, and store them in the third correspondence between the type, the business scenario, the attribute, and the multiple scene attribute values ​​for selection of the attribute. For each other business scenario, the same is provided.

[0174] Thus, in this step, in the third correspondence between the type, business scenario, attribute and multiple optional scenario attribute values ​​of the attribute, multiple optional scenario attribute values ​​corresponding to the target type, the business scenario and the target attribute can be found, and multiple optional scenario attribute values ​​of the target attribute coupled with the business scenario of the object of the target type can be used as the values.

[0175] In step S503, when the multiple selectable scene attribute values ​​are different from the multiple selectable public attribute values ​​in the selection control, the multiple selectable scene attribute values ​​are used to replace the multiple selectable public attribute values ​​in the selection control to obtain a fourth upload page corresponding to the business scenario. The fourth upload page is used to upload the scene attribute values ​​of the target attributes of the target type of object coupled with the business scenario.

[0176] In this way, when the staff needs to upload the target attribute of the second object of the target type and the attribute value of the target attribute of the second object of the target type in the business scenario, the terminal can send a page acquisition request to the server, and the page acquisition request is used to request to obtain the fourth upload page corresponding to the business scenario. The server can receive the page acquisition request sent by the terminal, and obtain the fourth upload page corresponding to the business scenario according to the acquisition request. And provide the fourth upload page corresponding to the business scenario to the terminal.

[0177] This allows staff to conveniently select the scenario attribute value of the target attribute of the second object of the target type according to a plurality of selectable scenario attribute values ​​of the target attribute coupled with the business scenario in the selection control in the fourth upload page, and upload the target attribute of the second object of the target type and the scenario attribute value of the target attribute of the second object of the target type coupled with the business scenario through the fourth upload page, thereby facilitating the server to store the uploaded target attribute of the second object of the target type and the scenario attribute value of the target attribute of the second object of the target type coupled with the business scenario in the form of "key-value" in the scenario attribute set of the second object of the target type coupled with the business scenario.

[0178] It should be noted that, for the method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the order of the actions described, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions involved are not necessarily required by the present application.

[0179] Reference Figure 2, shows a structural block diagram of a device for processing attributes of an object, including: an acquisition module 11, used to acquire a conversion request, the conversion request at least carries a target attribute, the target attribute is at least one attribute among multiple attributes of the target type object, the target attribute includes a scenario attribute of the target type object coupled with a business scenario or a public attribute decoupled from the business scenario, wherein the attribute value of the scenario attribute coupled with the business scenario varies according to the business scenario of the target type object, and the attribute value of the public attribute decoupled from the business scenario is the same in multiple business scenarios of the target type object; a first conversion module 12, used to convert the target attribute into a scenario attribute of the target type object; In the case where the target attribute is a scenario attribute of an object of the target type coupled with the business scenario, the attribute value of the target attribute of each first object of the target type that has been recorded is converted from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario according to the conversion request; or, a second conversion module 13 is used to convert the attribute value of the target attribute of each first object of the target type that has been recorded from the public attribute value of the public attribute decoupled from the business scenario to the scenario attribute value of the scenario attribute coupled with the business scenario according to the conversion request when the target attribute is a public attribute of an object of the target type decoupled from the business scenario.

[0180] Optionally, the first conversion module includes: a first acquisition unit, used to acquire the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario; a first storage unit, used to store the target attribute and the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario in a common attribute set corresponding to each first object of the target type; and, for any business scenario, in the scenario attribute set coupled to the business scenario of each first object of the target type, deleting the target attribute and the scenario attribute value of the target attribute of each first object of the target type that is coupled to the business scenario; wherein the scenario attributes and the scenario attribute values ​​of the target attribute coupled to the business scenario of the object of the target type correspond to different scenario attribute sets according to different business scenarios, and the common attributes and the common attribute values ​​of the target attribute of the object of the target type that are decoupled from the business scenario correspond to the same common attribute set for multiple business scenarios.

[0181] Optionally, the first acquisition unit includes: a first acquisition sub-unit, used to obtain scenario attribute values ​​of target attributes of the first object of the target type that are respectively coupled to various business scenarios; and a second acquisition sub-unit, used to obtain common attribute values ​​of target attributes of the first object of the target type that are decoupled from business scenarios based on the scenario attribute values ​​of the target attributes of the first object of the target type that are respectively coupled to various business scenarios.

[0182] Optionally, the second acquisition sub-unit is specifically used to: determine whether the scenario attribute values ​​of the target attributes of the first object of the target type that are respectively coupled to various business scenarios are all the same; when the scenario attribute values ​​of the target attributes of the first object of the target type that are respectively coupled to various business scenarios are all the same, obtain the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario according to the scenario attribute value of the target attribute of the first object of the target type that is coupled to any business scenario; or, when the scenario attribute values ​​of the target attributes of the first object of the target type that are respectively coupled to various business scenarios are not all the same or completely different, obtain a specified business scenario, and obtain the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario according to the scenario attribute value of the target attribute of the first object of the target type that is coupled to the specified business scenario.

[0183] Optionally, the first conversion module also includes: a second acquisition unit, used to acquire a first upload page corresponding to a business scenario for any business scenario, the first upload page being at least used to upload scenario attribute values ​​of target attributes of a target type of object coupled with the business scenario, the first upload page having at least a target attribute selection control, the target attribute selection control including a plurality of selectable scenario attribute values ​​of the target attribute of the target type of object coupled with the business scenario; a third acquisition unit, used to acquire a plurality of selectable common attribute values ​​of a target attribute of the target type of object decoupled from the business scenario; a first replacement unit, used to replace a plurality of selectable scenario attribute values ​​in the selection control with a plurality of selectable common attribute values ​​when the plurality of selectable common attribute values ​​are different from a plurality of selectable scenario attribute values ​​in the selection control, so as to obtain a second upload page corresponding to the business scenario, the second upload page being at least used to upload a plurality of selectable common attribute values ​​of the target attribute of the target type of object decoupled from the business scenario.

[0184] Optionally, the third acquisition unit includes: a first search sub-unit, used to search for multiple selectable public attribute values ​​corresponding to the target type and the target attribute in a first correspondence between the type, the attribute and the multiple selectable public attribute values ​​of the attribute, and to use the multiple selectable public attribute values ​​of the target attribute of the object of the target type as decoupled from the business scenario.

[0185] Optionally, the first conversion module also includes: a first receiving unit, used to receive a page acquisition request sent by the terminal, the page acquisition request is used to request to obtain a second upload page corresponding to the business scenario; a fourth acquisition unit, used to obtain the second upload page corresponding to the business scenario according to the acquisition request; and a first providing unit, used to provide the second upload page corresponding to the business scenario to the terminal.

[0186] Optionally, the second conversion module includes: a fifth acquisition unit, used to obtain, for each business scenario, the scenario attribute value of the target attribute of each first object of the target type coupled with the business scenario; a second storage unit, used to store the target attribute and the scenario attribute value of the target attribute of each first object of the target type coupled with the business scenario in a scenario attribute set corresponding to the business scenario of each first object of the target type, and to delete the target attribute and the public attribute value of the target attribute of each first object of the target type decoupled from the business scenario in a public attribute set corresponding to the first object of the target type.

[0187] Optionally, the fifth acquisition unit includes: a third acquisition sub-unit, used to obtain the common attribute value of the target attribute decoupled from the business scenario of each first object of the target type; and a fourth acquisition sub-unit, used to obtain the scenario attribute value of the target attribute coupled to the business scenario of each first object of the target type according to the common attribute value of the target attribute decoupled from the business scenario and the business scenario.

[0188] Optionally, the fourth acquisition sub-unit is specifically used to: for each first object of the target type, in the second correspondence between the common attribute value of the target attribute decoupled from the business scenario of the target type object, the business scenario, and the scenario attribute value of the target attribute coupled to the business scenario of the target type object, search for the common attribute value of the target attribute decoupled from the business scenario of the first object of the target type and the scenario attribute value corresponding to the business scenario, and use them as the scenario attribute value of the target attribute coupled to the business scenario of the first object of the target type.

[0189] Optionally, the second conversion module also includes: a sixth acquisition unit, used to obtain a third upload page corresponding to any business scenario, the third upload page is at least used to upload the common attribute value of the target attribute of the target type object decoupled from the business scenario, the third upload page has at least a selection control for the target attribute, the selection control for the target attribute includes a plurality of selectable common attribute values ​​of the target attribute of the target type object decoupled from the business scenario; a seventh acquisition unit, used to obtain a plurality of selectable scenario attribute values ​​of the target attribute of the target type object coupled with the business scenario; a second replacement unit, used to replace the plurality of selectable common attribute values ​​in the selection control with the plurality of selectable scenario attribute values ​​when the plurality of selectable scenario attribute values ​​are different from the plurality of selectable common attribute values ​​in the selection control, so as to obtain a fourth upload page corresponding to the business scenario, the fourth upload page is used to upload the scenario attribute value of the target attribute of the target type object coupled with the business scenario.

[0190] Optionally, the seventh acquisition unit includes: a second search sub-unit, used to search for multiple selectable scenario attribute values ​​corresponding to the target type, business scenario and target attribute in the third correspondence between the type, business scenario, attribute and multiple selectable scenario attribute values ​​of the attribute, and use them as multiple selectable scenario attribute values ​​of the target attribute coupled with the business scenario of the object of the target type.

[0191] Optionally, the second conversion module also includes: a second receiving unit, used to receive a page acquisition request sent by the terminal, the page acquisition request is used to request to obtain the fourth upload page corresponding to the business scenario; an eighth acquisition unit, used to obtain the fourth upload page corresponding to the business scenario according to the acquisition request; and a second providing unit, used to provide the fourth upload page corresponding to the business scenario to the terminal.

[0192] Through the present application, in the process of using the attribute values ​​of each attribute of an object of the target type to provide external services, it is supported to convert the attribute values ​​of the target attributes of the object of the target type between the scene attribute values ​​of the scene attributes and the public attribute values ​​of the public attributes in real time according to actual needs. For example, it is supported to convert the attribute values ​​of the target attributes of each first object of the target type that have been recorded in real time according to actual needs from the scene attribute values ​​of the scene attributes coupled with the business scenario to the public attribute values ​​of the public attributes decoupled from the business scenario. It is supported to convert the attribute values ​​of the target attributes of each first object of the target type that have been recorded in real time according to actual needs from the public attribute values ​​of the public attributes decoupled from the business scenario to the scene attribute values ​​of the scene attributes coupled with the business scenario.

[0193] For example, in the case where a certain target attribute is a scenario attribute of the first object of the target type that is coupled with a business scenario, the scenario attribute value of the scenario attribute of the first object of the target type that is respectively coupled with each business scenario can be converted into a public attribute value of a public attribute of the first object of the target type that is decoupled from the business scenario, so that the attributes stored for the first object of the target type are changed from multiple scenario attributes to one public attribute, thereby reducing the number of attributes stored for the first object of the target type, and the attribute value of the attribute stored for the first object of the target type is changed from multiple scenario attribute values ​​to one public attribute value, thereby reducing the number of attribute values ​​stored for the first object of the target type. In this way, the number of attributes and attribute values ​​stored for the first object of the target type is reduced, and storage space can be further saved.

[0194] Alternatively, in the case where a certain target attribute is a public attribute of the first object of the target type that is decoupled from the business scenario, the public attribute value of the public attribute of the first object of the target type that is decoupled from the business scenario can be converted into a scene attribute value of the scene attribute of the first object of the target type that is respectively coupled to each business scenario, so that the attribute value of the attribute of the first object of the target type can meet the personalized needs of the corresponding business scenario, thereby improving the service quality of services provided externally using the attribute value of the attribute of the first object of the target type.

[0195] Secondly, in the present application, a conversion request is used to convert the attribute values ​​of an object of one type. Thus, a staff member can submit a conversion request once to enable the server to convert the attribute values ​​of the target attributes of multiple objects of one type between the scene attribute values ​​of the scene attributes and the public attribute values ​​of the public attributes, thereby achieving the effect of converting multiple objects with one request. The conversion has a high degree of automation and efficiency, and the staff member does not need to submit conversion requests separately for each object of a type, thus reducing labor costs.

[0196] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0197] Optionally, the present application also provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the various processes of the above-mentioned method embodiments are implemented and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0198] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, each process of the above method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0199] Figure 3 1 is a block diagram of an electronic device 1900 shown in the present application. For example, the electronic device 1900 may be provided as a server.

[0200] Reference Figure 3, the electronic device 1900 includes a processing component 1922, which further includes one or more processors, and a memory resource represented by a memory 1932 for storing instructions executable by the processing component 1922, such as an application. The application stored in the memory 1932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1922 is configured to execute instructions to perform the above method.

[0201] The electronic device 1900 may also include a power supply component 1926 configured to perform power management of the electronic device 1900, a wired or wireless network interface 1950 configured to connect the electronic device 1900 to a network, and an input / output (I / O) interface 1958. The electronic device 1900 may operate based on an operating system stored in the memory 1932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

[0202] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0203] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0204] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

[0205] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0206] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

[0209] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0210] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0211] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for processing attributes of an object, characterized in that The method comprises: Obtaining a conversion request, the conversion request at least carries a target attribute, the target attribute being at least one of a plurality of attributes possessed by an object of the target type, the target attribute comprising a scenario attribute of the object of the target type coupled with a business scenario or a public attribute decoupled from the business scenario; wherein the attribute value of the scenario attribute coupled with the business scenario is different according to different business scenarios of the object of the target type, and the attribute value of the public attribute decoupled from the business scenario is the same in multiple business scenarios of the object of the target type; In a case where the target attribute is a scenario attribute of an object of the target type coupled with the business scenario, converting the recorded attribute value of the target attribute of each first object of the target type from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario according to the conversion request; or, In the case where the target attribute is a common attribute of an object of the target type that is decoupled from the business scenario, the attribute values ​​of the recorded target attributes of each first object of the target type are converted from the common attribute values ​​of the common attributes decoupled from the business scenario to the scenario attribute values ​​of the scenario attributes coupled to the business scenario according to the conversion request.

2. The method according to claim 1, characterized in that The step of converting the recorded attribute values ​​of the target attributes of each first object of the target type from the scenario attribute values ​​of the scenario attributes coupled with the business scenario to the public attribute values ​​of the public attributes decoupled from the business scenario according to the conversion request includes: Obtain a common attribute value of a target attribute of a first object of a target type that is decoupled from a business scenario; The target attributes and the common attribute values ​​of the target attributes of the first object of the target type decoupled from the business scenario are stored in the common attribute set corresponding to the first objects of the target type; and, for any business scenario, in the scenario attribute set coupled to the business scenario of the first objects of the target type, the target attributes and the scenario attribute values ​​of the target attributes of the first objects of the target type coupled to the business scenario are deleted; wherein the scenario attributes and the scenario attribute values ​​of the objects of the target type coupled to the business scenario correspond to different scenario attribute sets according to different business scenarios, and the common attributes and the common attribute values ​​of the objects of the target type decoupled from the business scenario correspond to the same common attribute set for multiple business scenarios.

3. The method according to claim 2, characterized in that The step of obtaining a common attribute value of a target attribute of a first object of a target type that is decoupled from a business scenario includes: Obtaining scenario attribute values ​​of target attributes of a first object of a target type that are respectively coupled to each business scenario; According to the scenario attribute values ​​of the target attributes of the first object of the target type that are respectively coupled to the respective business scenarios, the common attribute values ​​of the target attributes of the first object of the target type that are decoupled from the business scenarios are acquired.

4. The method according to claim 3, characterized in that The acquiring, according to the scenario attribute values ​​of the target attributes of the first object of the target type respectively coupled with each business scenario, the common attribute value of the target attribute of the first object of the target type decoupled from the business scenario comprises: Determine whether the scenario attribute values ​​of the target attributes of the first object of the target type, which are respectively coupled to the various business scenarios, are all the same; When the scenario attribute values ​​of the target attributes of the first object of the target type that are respectively coupled to the various business scenarios are the same, obtaining the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario according to the scenario attribute value of the target attribute of the first object of the target type that is coupled to any business scenario; or, When the scenario attribute values ​​of the target attributes of the first object of the target type that are coupled to each business scenario are not all the same or all different, obtain the specified business scenario, and obtain the common attribute value of the target attribute of the first object of the target type that is decoupled from the business scenario based on the scenario attribute value of the target attribute coupled to the specified business scenario.

5. The method according to claim 1, characterized in that The step of converting the recorded attribute values ​​of the target attributes of each first object of the target type from the public attribute values ​​of the public attributes decoupled from the business scenario to the scenario attribute values ​​of the scenario attributes coupled to the business scenario according to the conversion request includes: For each business scenario, obtaining a scenario attribute value of a target attribute of each first object of a target type coupled with the business scenario; In the scenario attribute set corresponding to the business scenario of each first object of the target type, the target attribute and the scenario attribute value of the target attribute of each first object of the target type coupled with the business scenario are stored; and, in the public attribute set corresponding to the first object of the target type, the public attribute value of the target attribute and the target attribute of each first object of the target type decoupled from the business scenario is deleted.

6. The method according to claim 5, characterized in that The acquiring the scenario attribute value of the target attribute of each first object of the target type coupled with the business scenario includes: Obtaining a common attribute value of a target attribute of each first object of the target type that is decoupled from the business scenario; According to the common attribute value of the target attribute decoupled from the business scenario of each first object of the target type and the business scenario, the scenario attribute value of the target attribute coupled to the business scenario of each first object of the target type is respectively obtained.

7. The method according to claim 6, characterized in that The acquiring, according to the common attribute value of the target attribute decoupled from the business scenario of each first object of the target type and the business scenario, the scenario attribute value of the target attribute coupled to the business scenario of each first object of the target type respectively includes: For each first object of the target type, in the second correspondence between the public attribute value of the target attribute decoupled from the business scenario of the target type object, the business scenario, and the scenario attribute value of the target attribute coupled to the business scenario of the target type object, the public attribute value of the target attribute decoupled from the business scenario of the first object of the target type and the scenario attribute value corresponding to the business scenario are searched and used as the scenario attribute value of the target attribute coupled to the business scenario of the first object of the target type.

8. A device for processing attributes of an object, characterized in that The device comprises: An acquisition module is used to acquire a conversion request, where the conversion request carries at least a target attribute, where the target attribute is at least one of multiple attributes possessed by an object of the target type, and the target attribute includes a scenario attribute of the object of the target type coupled with a business scenario or a public attribute decoupled from the business scenario, wherein the attribute value of the scenario attribute coupled with the business scenario is different according to different business scenarios of the object of the target type, and the attribute value of the public attribute decoupled from the business scenario is the same in multiple business scenarios of the object of the target type; A first conversion module is used for converting the recorded attribute value of the target attribute of each first object of the target type from the scenario attribute value of the scenario attribute coupled with the business scenario to the public attribute value of the public attribute decoupled from the business scenario according to the conversion request when the target attribute is a scenario attribute of an object of the target type coupled with the business scenario; or, A second conversion module is used to convert the recorded attribute values ​​of the target attributes of each first object of the target type from the public attribute values ​​of the public attributes decoupled from the business scenario to the scenario attribute values ​​of the scenario attributes coupled to the business scenario according to a conversion request, when the target attribute is a public attribute of an object of the target type decoupled from the business scenario.

9. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the method according to any one of claims 1 to 7 when executed by the processor.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images