WO2020134701A1 - 业务处理方法、装置及设备 - Google Patents

业务处理方法、装置及设备 Download PDF

Info

Publication number
WO2020134701A1
WO2020134701A1 PCT/CN2019/119191 CN2019119191W WO2020134701A1 WO 2020134701 A1 WO2020134701 A1 WO 2020134701A1 CN 2019119191 W CN2019119191 W CN 2019119191W WO 2020134701 A1 WO2020134701 A1 WO 2020134701A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
data
business
asset
master
Prior art date
Application number
PCT/CN2019/119191
Other languages
English (en)
French (fr)
Inventor
邓霄
郭耕辰
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2020134701A1 publication Critical patent/WO2020134701A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635—Processing of requisition or of purchase orders
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Definitions

  • This specification relates to the field of Internet technology, and in particular to business processing methods, devices and equipment.
  • business providers provide users with more and more types of services, which brings great convenience to people's work and life.
  • business providers can create business data to record various relevant information of the business, which is convenient for users to query and manage. It can be understood that there are many ways for business providers to perform business processing and create business data, and it is undoubtedly of great significance to provide a more efficient business processing solution.
  • this specification provides business processing methods, devices and equipment.
  • a business processing method including:
  • master user data bound to the business order according to a preset data structure wherein the preset data structure at least specifies that the user data has an asset field, and the asset field of the master user data indicates an asset everyone includes the primary user;
  • the associated user data bound to the business order is created according to the preset data structure, wherein the asset field of the associated user data indicates that the asset owns The person includes the associated user.
  • the preset data structure further specifies a data creator field, the data creator field of the master user data indicates the master user, and the data creator field of the associated user data indicates the master user.
  • the method further includes:
  • a database view corresponding to the user is searched through the user ID, and query data in the database view is used to obtain display data and return.
  • the database view of the user includes one or more database views corresponding to different business scenarios
  • the data query request also carries request trigger entry information corresponding to the business scenario
  • the corresponding user is searched for by the user ID Database views, including:
  • the database view corresponding to the user and the business scene is searched through the user identification and request trigger entry information.
  • the presentation data includes one or more of the following: the asset owner information, the business order information, or the data creator information.
  • the method further includes:
  • another service processing method including:
  • master user data bound to the business order is created according to a preset data structure, wherein the preset data structure at least specifies that the user data has an asset field, and the asset field of the master user data indicates an asset
  • the owner includes the primary user
  • the associated user data bound to the business order is created according to the preset data structure, wherein the asset field of the associated user data indicates The asset owner includes the associated user.
  • the preset data structure further specifies a data creator field, the data creator field of the master user data indicates the master user, and the data creator field of the associated user data indicates the master user.
  • the method further includes:
  • a database view corresponding to the user is searched through the user ID, and query data in the database view is used to obtain display data and return.
  • the database view of the user includes one or more database views corresponding to different business scenarios
  • the data query request also carries request trigger entry information corresponding to the business scenario
  • the corresponding user is searched for by the user ID Database views, including:
  • the database view corresponding to the user and the business scene is searched through the user identification and request trigger entry information.
  • the presentation data includes one or more of the following: the asset owner information, the insurance order information, or the data creator information.
  • the method further includes:
  • a service processing device including:
  • the master user data creation module is used to create master user data bound to the business order according to a preset data structure for the business order of the master user, wherein the preset data structure at least specifies that the user data has an asset field.
  • the asset field of the master user data indicates that the asset owner includes the master user;
  • the associated user data creation module is configured to: if it is determined through the business order that the main user shares assets with the associated user, create associated user data bound to the business order according to the preset data structure, wherein, the The asset field of the associated user data indicates that the asset owner includes the associated user.
  • the preset data structure further specifies a data creator field, the data creator field of the master user data indicates the master user, and the data creator field of the associated user data indicates the master user.
  • the device further includes a database view creation module, configured to: create a database view corresponding to the user based on the user data of the user, and the database view corresponds to a query statement that uses the user data to query and display data;
  • a database view creation module configured to: create a database view corresponding to the user based on the user data of the user, and the database view corresponds to a query statement that uses the user data to query and display data;
  • the data search module is used to: if a data search request carrying a user ID initiated by the user is received, search the database view corresponding to the user by using the user ID, use the query statement in the database view to obtain the display data, and then return .
  • the user's database view includes one or more database views corresponding to different business scenarios
  • the data query request also carries request trigger entry information corresponding to the business scenario
  • the data query module is also used to:
  • the database view corresponding to the user and the business scene is searched through the user identification and request trigger entry information.
  • the presentation data includes one or more of the following: the asset owner information, the business order information, or the data creator information.
  • the device further includes a permission determination module for:
  • a computer device including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the program as follows method:
  • master user data bound to the business order according to a preset data structure wherein the preset data structure at least specifies that the user data has an asset field, and the asset field of the master user data indicates an asset everyone includes the primary user;
  • the associated user data bound to the business order is created according to the preset data structure, wherein the asset field of the associated user data indicates that the asset owns The person includes the associated user.
  • the associated user data with which the business order is bound can be created, and the asset field of the associated user data is used to record the asset owned by the associated user. Therefore, the relationship between the main user and the sharer in the business order can be effectively recorded, the sharer can be supported to check the business order, and the service provider can facilitate data maintenance.
  • Fig. 1A is a flowchart of a business processing method according to an exemplary embodiment of this specification.
  • Fig. 1B is a schematic diagram of a business processing scenario according to an exemplary embodiment of this specification.
  • Fig. 1C is a schematic diagram of data display in a different business scenario according to an exemplary embodiment of this specification.
  • Fig. 2 is a flowchart of another business processing method according to an exemplary embodiment of this specification.
  • FIG. 3 is a hardware structure diagram of computer equipment where the business processing apparatus of the embodiment of the present specification is located.
  • Fig. 4 is a block diagram of a service processing device according to an exemplary embodiment of this specification.
  • first, second, third, etc. may be used in this specification to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as second information, and similarly, the second information may also be referred to as first information.
  • word “if” as used herein may be interpreted as "when” or “when” or “in response to a determination”.
  • An insurer also known as an “insurer” refers to an insurance entity that concludes an insurance contract with an insurer and assumes responsibility for compensation or payment of insurance money.
  • An insurance applicant refers to a person who concludes an insurance contract with an insurer and has the obligation to pay insurance premiums in accordance with the insurance contract.
  • the insured refers to a person whose property interests or person are protected by the insurance contract according to the insurance contract and who have the right to claim the sum insured after the insurance accident.
  • Sum insured, short for insured amount, refers to the maximum limit of the insurer’s liability for compensation or payment of insurance money.
  • the user When providing insurance services to a user, the user will have a corresponding contract signing action, after which the user will get a policy. Among them, the sum assured may be fixed or may change.
  • Lulu buys an insurance product from an insurance company.
  • Lulu is the insured, and the insurer is the insurance company.
  • Lulu can designate the insured person of the insurance amount as himself or someone else.
  • the third-party payment platform party purchases an insurance product from an insurance company for the user.
  • the third-party payment platform party is the insured and the user is the insured.
  • the third-party payment platform can create business data for the user's insurance order, and this piece of business data can record the user information and various related information of the insurance order.
  • this specification provides a business processing solution that can effectively record the relationship between the user and the sharer in the insurance order, can support the sharer's inspection of the insurance order, and can facilitate the service provider to maintain the data.
  • FIG. 1A is a flowchart of a business processing method according to an exemplary embodiment of this specification, including the following steps:
  • step 102 for the insurance order of the master user, master user data bound to the business order is created according to a preset data structure, wherein the preset data structure at least specifies that the user data has an asset field, and that the master user data The asset field indicates that the asset owner includes the master user.
  • step 104 if it is determined through the insurance order that the main user shares the insurance sum to the associated user, the associated user data bound to the business order is created according to the preset data structure, wherein the associated user data
  • the asset field of indicates that the asset owner includes the associated user.
  • FIG. 1B it is a business process scenario diagram shown in this specification according to an exemplary embodiment.
  • this embodiment refers to one type as the main user, that is, insurance The order owner and the user as the insured; the other type is called the associated user, that is, the party that the main user shares the insurance sum of his own insurance order.
  • the business processing method of this embodiment may be applied to the business side.
  • the business side may be a service side, which may specifically be a service side that provides insurance products.
  • the business side may specifically be an insurance platform business side.
  • the party can access multiple service providers of insurance products to provide users with various insurance products.
  • the service provider will create user data for the insurance order.
  • the embodiment of this specification can propose a solution from the data structure of the user data.
  • the insurance sum assured can be used as the user’s asset.
  • the asset includes the insurance sum insured.
  • the main user shares the insurance sum insured to the associated user, that is, the asset is shared, and the associated user also owns the assets. Therefore, in this embodiment, a data structure may be preset, and at least the user data in the data structure has an asset field, and the asset field is used to indicate the asset owner. It can be understood that the asset field of the master user data indicates that the asset owner includes the master user .
  • the master user data created using the preset data structure has assets, and by reading the asset field, it can be determined that the owner of the asset in the piece of user data is the master user.
  • the preset data structure can also specify other fields in the user data, such as user ID, business order ID, order completion time, guarantee duration, payment method or user personal information, etc. Information about the user's business order.
  • the business party may establish an account for the master user based on the business order, and the user data of the master user belongs to the user’s account. Data; understandably, if the user has other business orders in the future, there can be more user data under the account.
  • this embodiment will also create associated user data for the associated user according to the preset data structure, because at least the specified user data in the data structure has an asset field ,
  • the asset field is used to indicate the asset owner. It can be understood that the asset field of the associated user data indicates that the asset owner includes the associated user.
  • the associated user data created using the preset data structure has assets, which can be read by reading In the asset field, it can be determined that the owner of the asset in the piece of associated user data includes the associated user.
  • an account can be established for the associated user, and the user data of the associated user belongs to the data under the user's account; it is understandable that if the associated user subsequently returns If the master user shares the assets of other business orders, the account can have more data; optionally, if the associated user is subsequently shared by other master users with assets of other business orders, it can be in the account of the associated user Other data can be created below, or another account can be created for the associated user to create data under the other account.
  • a user can also be the main user and an associated user at the same time.
  • user Lulu has a business order A
  • user Tony shares the assets of business order B.
  • another Lulu account is created for the business order B of the user Tony.
  • the account is an associated account associated with the business order B.
  • the associated account is associated with the business order B User data.
  • the master user data and associated user data are bound to the master user’s business order.
  • the preset data structure can specify the business order information field. Information such as the identification of the business order is written in the order information field. It can also record the correspondence between user data and business orders in other data tables.
  • the master user also creates user data for the associated user shared by the insurance sum insured, and uses the asset field of the associated user data to record the insured amount owned by the associated user, so the master user in the business order can be effectively recorded
  • the relationship with the sharer can support the sharer's inspection of insurance orders, and can facilitate the maintenance of data by the service provider.
  • the preset data structure also specifies a data creator field, and the data creator field of the master user data indicates the master
  • the data creator field of the associated user data indicates the master user; for example, through the data creator field, the server can determine which user's insurance order created the piece of user data.
  • the data creator field of the master user data may determine that the data creator of the piece of user data is the master user
  • the data creator field of the associated user data may determine that the data creator of the piece of associated user data is the associated user Based on this, business parties, primary users, or associated users can provide user data to the data creator to understand the source of the asset.
  • the user data created may contain a lot of information about users and business orders due to business needs, such as the order ID, order serial number or payment serial number created by the business party for the order. No. etc. But for the user, the user may only care about some of the information, and the user also needs to check some of the information, for example, to check the duration of the insurance, the amount of the insurance amount, the time of insurance purchase or the insurance contract, etc.
  • the information queried by the user may be only a small number of fields in the user data. Data such as insurance contracts may not be in the same database table as the user data.
  • the query process may involve multiple database tables. Based on this, the following solution is also provided in this embodiment, which can facilitate the processing of the user's query request for data.
  • a database view corresponding to the user may be created based on the user data of the user, and the database view corresponds to a query statement that uses the user data to query and display data; Data query request, search the database view corresponding to the user through the user ID, and use the query statement in the database view to obtain the display data and return.
  • the database view is a virtual table, does not store data itself, its content is defined by the query, you can query in a specified manner. For complex query events, it is inefficient to write query statements for each query.
  • This embodiment uses the view function of the database to solve the problem.
  • this embodiment may create a corresponding database view for each user in advance, where the data that can be queried by the database view is the data returned to the user for reference.
  • This embodiment is called display data, based on the storage location of the user data
  • a query statement that can use the user data to query and display data can be pre-written to complete the creation of the view, where each user's database view corresponds to the user, and optionally, the user ID can be used to distinguish each view.
  • a data search request carrying the user ID can be initiated, and the database corresponding to the user can be searched through the user ID View, use the query statement in the database view to obtain the display data and return.
  • multiple business orders and multiple user data may be involved in the user account.
  • Different business orders may be initiated based on different business scenarios.
  • the data concerned by the user is different.
  • the database view of the user includes one or more database views corresponding to different business scenarios
  • the data query request also carries request trigger entry information corresponding to the business scenario
  • the database view corresponding to the user is searched for by the user identifier Including: searching the database view corresponding to the user and the business scene through the user identification and the request trigger entry information. In this way, the effect of providing different data under different business scenarios can be achieved.
  • the business party provides two types of insurance products.
  • the first type of insurance product is for users to share the insurance coverage to their families
  • the second type of insurance product is for users to purchase and share after the user participates in the business party's marketing activities. Sum assured to users.
  • user A is involved in a business order generated after purchasing the first type of insurance product, and user A also shares the insurance sum to his family; after user A participates in the marketing activities of the business party, as an associated user, he obtains business party sharing Insurance coverage.
  • user A can use the client provided by the business party or log in to the service page to check the relevant data of these two types of insurance products.
  • user A's demand is to be able to check the first type of insurance products and share the situation with family members; for the second type of insurance products, user A's demand is to check the insurance coverage shared by the business party That is, there is no need to involve a lot of information such as business parties.
  • business parties can pre-configure database views of these two business scenarios to provide different business data.
  • client can log in to the server using a user ID such as a UID and/or ID card.
  • the client provides a request triggering portal, and the user can trigger the request triggering portal, so that the client initiates a data query request.
  • the request triggering entry may be a data query request that includes consulting two types of insurance products, and then the business party may separately obtain the display data of the two types of insurance products through the database views of the foregoing two business scenarios, and then return.
  • this specification shows a schematic diagram of display data in two different business scenarios according to an exemplary embodiment.
  • a user in the role of "father" shares assets to children and mothers of children, Corresponding database views can obtain the relevant display data shared with the child and the child’s mother; in business scenario two, the user is an associated user who shares insurance coverage by the business party, and the corresponding database view can obtain the corresponding Data related to your sum assured.
  • an insurance scenario is used as an example. If a user completes a business order related to insurance through the purchase of insurance on the business side for the first time, the business side may establish an account for the user based on the business order. This embodiment is called a health account and Generate user data based on the account.
  • the business party does not limit whether it is a service party of insurance products, but may be a platform for providing services to insurance product service parties.
  • the service side can pre-configure the data structure to specify which fields are included in the account data.
  • the data primary key that can be specified in the preset data structure includes: a user identification, which may be the user's ID number and/or UserID (User, Identification, user identification, UID for short).
  • a user identification which may be the user's ID number and/or UserID (User, Identification, user identification, UID for short).
  • This embodiment takes the user's UID and ID number as an example. Through the index based on the user UID and ID number, it can ensure that the user can support multi-dimensional queries when performing subsequent data queries.
  • the user as the master user can generate corresponding user data according to the preset data structure.
  • the insurance order involves stakeholders, such as the insured and the insured. If the main user does not share the sum assured, there is only one insured, namely the main user himself. In other words, the benefits of the policy can only be enjoyed by the main user.
  • the preset data structure at least specifies that the user data has an asset field, and the asset field of the master user data indicates that the asset owner includes the master user.
  • user A may also share the insured rights and interests to the associated user (user B). specific:
  • the service party can create a health account for user A.
  • the service party will create master user data corresponding to the insurance order under the health account.
  • the data creator field of the piece of master user data indicates user A
  • the asset field indicates user A.
  • the insurance order can be bound to the health account with the user A as a health asset.
  • user A can log in using his own UID and ID number Server and access your own health account.
  • a health account can be created for user B. If user B has created a health account, there is no need to create it again. Similarly, User B can also use his UID and ID number to access his health account. Accordingly, user data corresponding to the insurance order shared by user A is created under the health account of user B.
  • the asset field indicates that the asset owner includes the user B, and the insurance order with the main user Binding. Therefore, user B has a policy of A under his health account.
  • the user data can be used to check that the policy under the account is shared by A. The asset owner is himself.
  • the asset information between the main user and the associated user will not cause the problem of information loss.
  • user A has his own insurance order, he can have user data that is the creator and the owner of the asset.
  • user A may have multiple business orders, and pay attention to his own insurance policy.
  • user B will apply the insurance policy. If user B only needs to pay attention to his own account, data can be filtered through the relationship between the data creator and the asset owner. , Solve the problem of business isolation from different business perspectives.
  • the type of health asset is a policy.
  • different types can also be extended, such as physical examination reports or physical fitness monitoring reports and other types, to achieve the sharing of other types of assets.
  • the above solution can also solve the problem of permission isolation, obtain login user information, search for login user data through login user information, obtain the asset field and data creator field in the login user data, and then determine the The operation authority of the login user to the business order associated with the login user data.
  • the user can obtain the UID of the currently logged-in user after logging in.
  • the logged-in user corresponds to user data.
  • the asset field in the user data indicates the asset owner UID
  • the data creator field indicates the data creator UID. UID relationship to determine the user's permissions.
  • the UID of the login state is the same as the UID of the asset owner, but it is different from the UID of the data creator, indicating that the corresponding asset under this account is shared by others, and the policy asset associated with the user data cannot be surrendered. Therefore, the problem of permission isolation is also solved.
  • the business processing solutions of the embodiments of this specification can also be applied to other business scenarios that require asset sharing, such as red envelope sharing scenarios or business order equity sharing scenarios. , You can share the purchased membership to other associated users.
  • FIG. 2 it is another business processing method shown according to an exemplary embodiment, including the following steps:
  • step 202 for the business order of the master user, master user data bound to the business order is created according to a preset data structure, wherein the preset data structure at least specifies that the user data has an asset field, and the master user data The asset field of indicates that the asset owner includes the primary user;
  • step 204 if it is determined through the business order that the main user shares the asset to the associated user, the associated user data bound to the business order is created according to the preset data structure, wherein the associated user data
  • the asset field indicates that the asset owner includes the associated user.
  • the preset data structure further specifies a data creator field, the data creator field of the master user data indicates the master user, and the data creator field of the associated user data indicates the master user.
  • the method further includes:
  • a database view corresponding to the user is searched through the user ID, and query data in the database view is used to obtain display data and return.
  • the database view of the user includes one or more database views corresponding to different business scenarios
  • the data query request also carries request trigger entry information corresponding to the business scenario
  • the corresponding user is searched for by the user ID Database views, including:
  • the database view corresponding to the user and the business scene is searched through the user identification and request trigger entry information.
  • the presentation data includes one or more of the following: the asset owner information, the business order information, or the data creator information.
  • the method further includes:
  • this specification also provides an embodiment of the business processing apparatus and the equipment to which it is applied.
  • the embodiment of the service processing apparatus in this specification can be applied to a computer device, such as a server or a terminal device.
  • the device embodiments may be implemented by software, or by hardware or a combination of hardware and software. Taking software implementation as an example, as a device in a logical sense, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory through the processor of the file processing where it is located. From the hardware level, as shown in FIG.
  • the server or the electronic device where the device 331 is located may generally include other hardware according to the actual function of the computer device, which will not be repeated here.
  • FIG. 4 is a block diagram of a service processing apparatus according to an exemplary embodiment of the present specification.
  • the apparatus includes:
  • the master user data creation module 410 is configured to: for the business order of the master user, create master user data bound to the business order according to a preset data structure, wherein the preset data structure at least specifies that the user data has an asset field, The asset field of the master user data indicates that the asset owner includes the master user;
  • the associated user data creation module 420 is configured to: if it is determined through the business order that the primary user shares assets with the associated user, create associated user data bound to the business order according to the preset data structure, wherein The asset field of the associated user data indicates that the asset owner includes the associated user.
  • the preset data structure further specifies a data creator field, the data creator field of the master user data indicates the master user, and the data creator field of the associated user data indicates the master user.
  • the device further includes a database view creation module, configured to: create a database view corresponding to the user based on the user data of the user, and the database view corresponds to a query statement that uses the user data to query and display data;
  • a database view creation module configured to: create a database view corresponding to the user based on the user data of the user, and the database view corresponds to a query statement that uses the user data to query and display data;
  • the data search module is used to: if a data search request carrying a user ID initiated by the user is received, search the database view corresponding to the user by using the user ID, use the query statement in the database view to obtain the display data, and then return .
  • the user's database view includes one or more database views corresponding to different business scenarios
  • the data query request also carries request trigger entry information corresponding to the business scenario
  • the data query module is also used to:
  • the database view corresponding to the user and the business scene is searched through the user identification and request trigger entry information.
  • the presentation data includes one or more of the following: the asset owner information, the business order information, or the data creator information.
  • the device further includes a permission determination module for:
  • this specification also provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the program to implement the following method:
  • master user data bound to the business order according to a preset data structure wherein the preset data structure at least specifies that the user data has an asset field, and the asset field of the master user data indicates an asset everyone includes the primary user;
  • the associated user data bound to the business order is created according to the preset data structure, wherein the asset field of the associated user data indicates that the asset owns The person includes the associated user.
  • the relevant part can be referred to the description of the method embodiment.
  • the device embodiments described above are only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, may be located in one place Or, it can be distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solution in this specification. Those of ordinary skill in the art can understand and implement without paying creative labor.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种业务处理方法、装置及设备，对于主用户向关联用户分享的业务订单的资产，可以对应创建有绑定业务订单的关联用户数据，利用该关联用户数据的资产字段记录该关联用户所拥有的资产。因此可以有效记录业务订单中主用户与共享者的关系，可以支持共享者对业务订单的查阅，可以便于业务提供方进行数据的维护。

Description

业务处理方法、装置及设备 技术领域
本说明书涉及互联网技术领域，尤其涉及业务处理方法、装置及设备。
背景技术
随着互联网技术的持续发展，业务提供方为用户提供的业务类型越来越多，给人们工作生活带来了极大便利。业务提供方为用户提供业务的过程中，可以创建业务数据，以记录该笔业务的各种相关信息，方便用户查询管理等。可以理解，业务提供方进行业务处理、创建业务数据的方式多种多样，提供一种更高效的业务处理方案，无疑具有重要意义。
发明内容
为克服相关技术中存在的问题，本说明书提供了业务处理方法、装置及设备。
根据本说明书实施例的第一方面，提供一种业务处理方法，包括：
针对主用户的业务订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有人包括所述主用户；
若通过所述业务订单确定所述主用户将资产共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有人包括所述关联用户。
可选的，所述预设数据结构还指定有数据创建者字段，所述主用户数据的数据创建者字段指示所述主用户，所述关联用户数据的数据创建者字段指示所述主用户。
可选的，所述方法还包括：
基于用户的用户数据，创建对应用户的数据库视图，所述数据库视图对应有利用所述用户数据查询展示数据的查询语句；
若接收到用户发起的携带有用户标识的数据查阅请求，通过所述用户标识查找对应所述用户的数据库视图，利用所述数据库视图中的查询语句获取展示数据后返回。
可选的，所述用户的数据库视图包括一个或多个对应不同业务场景的数据库视图，所述数据查阅请求还携带有对应业务场景的请求触发入口信息，通过所述用户标识查找对应所述用户的数据库视图，包括：
通过所述用户标识和请求触发入口信息查找对应所述用户及业务场景的数据库视图。
可选的，所述展示数据包括如下一种或多种：所述资产所有人信息、所述业务订单信息或数据创建者信息。
可选的，所述方法还包括：
获取登录用户信息，通过登录用户信息查找登录用户数据，获取所述登录用户数据中的资产字段和数据创建者字段，进而确定所述登录用户对所述登录用户数据关联的业务订单的操作权限。
根据本说明书实施例的第二方面，提供另一种业务处理方法，包括：
针对主用户的保险订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有者包括所述主用户；
若通过所述保险订单确定所述主用户将保险保额共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有者包括所述关联用户。
可选的，所述预设数据结构还指定有数据创建者字段，所述主用户数据的数据创建者字段指示所述主用户，所述关联用户数据的数据创建者字段指示所述主用户。
可选的，所述方法还包括：
基于用户的用户数据，创建对应用户的数据库视图，所述数据库视图对应有利用所述用户数据查询展示数据的查询语句；
若接收到用户发起的携带有用户标识的数据查阅请求，通过所述用户标识查找对应所述用户的数据库视图，利用所述数据库视图中的查询语句获取展示数据后返回。
可选的，所述用户的数据库视图包括一个或多个对应不同业务场景的数据库视图，所述数据查阅请求还携带有对应业务场景的请求触发入口信息，通过所述用户标识查找对应所述用户的数据库视图，包括：
通过所述用户标识和请求触发入口信息查找对应所述用户及业务场景的数据库视图。
可选的，所述展示数据包括如下一种或多种：所述资产所有人信息、所述保险订单信息或数据创建者信息。
可选的，所述方法还包括：
获取登录用户信息，通过登录用户信息查找登录用户数据，获取所述登录用户数据中的资产字段和数据创建者字段，进而确定所述登录用户对所述登录用户数据关联的保险订单的操作权限。
根据本说明书实施例的第三方面，提供一种业务处理装置，所述装置包括：
主用户数据创建模块，用于：针对主用户的业务订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有人包括所述主用户；
关联用户数据创建模块，用于：若通过所述业务订单确定所述主用户将资产共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有人包括所述关联用户。
可选的，所述预设数据结构还指定有数据创建者字段，所述主用户数据的数据创建者字段指示所述主用户，所述关联用户数据的数据创建者字段指示所述主用户。
可选的，所述装置还包括数据库视图创建模块，用于：基于用户的用户数据，创建对应用户的数据库视图，所述数据库视图对应有利用所述用户数据查询展示数据的查询语句；
数据查阅模块，用于：若接收到用户发起的携带有用户标识的数据查阅请求，通过所述用户标识查找对应所述用户的数据库视图，利用所述数据库视图中的查询语句获取展示数据后返回。
可选的，所述用户的数据库视图包括一个或多个对应不同业务场景的数据库视图，所述数据查阅请求还携带有对应业务场景的请求触发入口信息，所述数据查阅模块，还用于：
通过所述用户标识和请求触发入口信息查找对应所述用户及业务场景的数据库视图。
可选的，所述展示数据包括如下一种或多种：所述资产所有人信息、所述业务订单信息或数据创建者信息。
可选的，所述装置还包括权限确定模块，用于：
获取登录用户信息，通过登录用户信息查找登录用户数据，获取所述登录用户数据中的资产字段和数据创建者字段，进而确定所述登录用户对所述登录用户数据关联的业务订单的操作权限。
根据本说明书实施例的第四方面，提供一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如下方法：
针对主用户的业务订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有人包括所述主用户；
若通过所述业务订单确定所述主用户将资产共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有人包括所述关联用户。
本说明书的实施例提供的技术方案可以包括以下有益效果：
本说明书实施例中，对于主用户向关联用户分享的业务订单的资产，可以对应创建有绑定业务订单的关联用户数据，利用该关联用户数据的资产字段记录该关联用户所拥有的资产。因此可以有效记录业务订单中主用户与共享者的关系，可以支持共享者对业务订单的查阅，可以便于业务提供方进行数据的维护。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本说明书。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本说明书的实施例，并与说明书一起用于解释本说明书的原理。
图1A是本说明书根据一示例性实施例示出的一种业务处理方法的流程图。
图1B是本说明书根据一示例性实施例示出的一种业务处理场景示意图。
图1C是本说明书根据一示例性实施例示出的一种不同业务场景下的数据展示示意图。
图2是本说明书根据一示例性实施例示出的另一种业务处理方法的流程图。
图3是本说明书实施例业务处理装置所在计算机设备的一种硬件结构图。
图4是本说明书根据一示例性实施例示出的一种业务处理装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本说明书相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本说明书的一些方面相一致的装置和方法的例子。
在本说明书使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书。在本说明书和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
在一些业务场景中，可能会涉及资产共享的情况。例如，以保险业务场景为例，用户可以将保险保额共享给子女等其他人。首先对保险业务涉及的词语进行说明：
保险人，保险人又称“承保人”，是指与投保人订立保险合同，并承担赔偿或者给付保险金责任的保险主体。
投保人，是指与保险人订立保险合同，并按照保险合同负有支付保险费义务的人。
被保人，是指根据保险合同，其财产利益或人身受保险合同保障，在保险事故发生后，享有保额请求权的人。
保额，保险金额的简称，指保险人承担赔偿或者给付保险金责任的最高限额。
向用户提供保险业务时，用户会有相应的协议签约动作，之后该用户会获得一份保单。其中，保额可能是固定不变的，也有可能发生变动。
作为例子，Lulu在保险公司购买一款保险产品，Lulu即投保人，保险人即保险公司，Lulu可以将保险金额的被保人指定为自己，或者是其他人。
在另一些例子中，随着互联网业务的创新，也出现了其他保险类型。例如，第三方支付平台方为用户从保险公司购买了一款保险产品，其中，第三方支付平台方即投保人，用户为被保人。第三方支付平台可以针对用户的保险订单创建业务数据，该条业务数据可以记录有用户信息、该笔保险订单的各种相关信息等。
在另一些保险业务中，还可能出现保额共享的情况，用户将保额共享给其他人，例如用户的家庭成员(自己的子女或配偶等)。针对这种情况，业务处理会面临一些问题，例如，如何记录该笔保险订单中用户与共享者的关系，如何在用户数据中记录共享者的信息，以方便共享者也可以查阅到用户分享给他人的保单等等。
基于此，本说明书提供一种业务处理方案，该方案可以有效记录保险订单中用户与共享者的关系，可以支持共享者对保险订单的查阅，可以便于业务提供方进行数据的维护。接下来对本说明书实施例进行详细说明。
如图1A所示，图1A是本说明书根据一示例性实施例示出的一种业务处理方法的流程图，包括以下步骤：
在步骤102、针对主用户的保险订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有人包括所述主用户。
在步骤104、若通过所述保险订单确定所述主用户将保险保额共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有人包括所述关联用户。
如图1B所示，是本说明书根据一示例性实施例示出的业务处理场景图，本说明书实施例中涉及两类用户，为了便于区分，本实施例将其中一类称为主用户，即保险订单所有者、作为被保人的用户；另一类称为关联用户，即主用户将自身保险订单的保险保额所共享的一方。
本实施例的业务处理方法可应用于业务方侧，该业务方可以是服务方具体可以是提供保险产品的服务方，在另一些例子中，业务方具体也可以是保险平台业务方，该业 务方可以接入多家保险产品的服务方，向用户提供各种保险产品。
对于主用户，业务提供方会针对该笔保险订单创建用户数据，本说明书实施例可以从用户数据的数据结构上提出解决方案。本实施例中可以将保险保额作为用户的资产，对于主用户，其资产包括该保险保额，主用户将保险保额共享给关联用户，也即是将资产共享，关联用户也拥有了该资产。因此，本实施例可以预先设置数据结构，该数据结构中至少指定用户数据具有资产字段，利用该资产字段指示资产所有人，可以理解，主用户数据的资产字段指示资产所有者包括所述主用户。基于此，利用该预设数据结构创建的主用户数据中具有资产，通过读取该资产字段，即可确定该条用户数据中资产所有人是该主用户。可以理解，实际应用中，该预设数据结构还可指定用户数据中的其他字段，例如用户标识、业务订单标识、订单完成时间、保障时长、付款方式或用户个人信息等等，以详细记录有关该用户的该笔业务订单的相关信息。
其中，若用户第一次通过业务方侧购买保险完成一笔有关保险的业务订单，业务方可以基于该笔业务订单为该主用户建立账户，该主用户的用户数据属于该用户的账户下的数据；可以理解，若该用户后续还有其他业务订单，则在该账户下还可以有更多的用户数据。
进一步的，对于主用户将保险保额共享给关联用户的保险订单，本实施例同样会根据该预设数据结构为该关联用户创建关联用户数据，由于该数据结构中至少指定用户数据具有资产字段，利用该资产字段指示资产所有人，可以理解，关联用户数据的资产字段指示资产所有者包括所述关联用户，基于此，利用该预设数据结构创建的关联用户数据中具有资产，通过读取该资产字段，即可确定该条关联用户数据中资产所有人包括该关联用户。
其中，若该关联用户是第一次被该主用户分享资产，则可以为该关联用户建立账户，该关联用户的用户数据属于该用户的账户下的数据；可以理解，若该关联用户后续还被该主用户分享其他业务订单的资产，则该账户下可以有更多的数据；可选的，若该关联用户后续被其他主用户分享其他业务订单的资产，可以是在该关联用户的账户下创建其他数据，也可以是针对该关联用户创建其他账户，以在该其他账户下创建数据。
实际应用中，某个用户还可以同时作为主用户和关联用户，例如用户Lulu有一笔业务订单A，并且被用户Tony分享有业务订单B的资产，可以针对业务订单A创建Lulu的主账户，该主账户下有业务订单A的主用户数据，同时，针对用户Tony的业务订单B创建Lulu的另一账户，该账户是与业务订单B关联的关联账户，该关联账户下 有业务订单B的关联用户数据。在另一些场景中，也可以是针对Lulu只创建一个账户，在该账户下既有业务订单A的主用户数据，也有业务订单B的关联用户数据。
其中，主用户数据和关联用户数据都与主用户的业务订单进行绑定，绑定的实现方式可以有多种，作为例子，可以是预设数据结构指定有业务订单信息字段，通过在该业务订单信息字段中写入业务订单的标识等信息。也可以是在其他数据表中记录用户数据与业务订单的对应关系。
由上述实施例可见，主用户将保险保额所共享的关联用户也创建有用户数据，利用该关联用户数据的资产字段记录该关联用户所拥有的保额，因此可以有效记录业务订单中主用户与共享者的关系，可以支持共享者对保险订单的查阅，可以便于业务提供方进行数据的维护。
为了更为清晰地供用户查阅资产来源等信息、便于业务方进行数据维护，可选的，预设数据结构还指定有数据创建者字段，所述主用户数据的数据创建者字段指示所述主用户，所述关联用户数据的数据创建者字段指示所述主用户；例如，通过数据创建者字段，服务方可以确定该条用户数据是由哪个用户的保险订单创建的。例如，从主用户数据的数据创建者字段可以确定该条用户数据的数据创建者是该主用户，从关联用户数据的数据创建者字段可以确定该条关联用户数据的数据创建者是该关联用户，基于此，业务方、主用户或关联用户等可以提供用户数据查阅到数据创建者，清楚资产的来源。
实际应用中，对于业务方来说，可能由于业务需要，创建的用户数据中可能包含有有关用户及业务订单的诸多信息，例如业务方为该笔订单创建的订单标识、订单流水号或付款流水号等等。但对于用户来说，用户可能只关心其中的部分信息，用户还有查阅其中部分信息的需求，例如查看保险的保障时长、保额有多少、保险购买时间或保险合同等等。用户查询的信息可能只是用户数据中的少量字段，诸如保险合同等数据可能与用户数据不在同一张数据库表中，查询的过程可能涉及多张数据库表。基于此，本实施例中还提供了如下方案，可以便于处理用户对数据的查阅需求。可选的，本实施例中可以基于用户的用户数据，创建对应用户的数据库视图，所述数据库视图对应有利用所述用户数据查询展示数据的查询语句；若接收到用户发起的携带有用户标识的数据查阅请求，通过所述用户标识查找对应所述用户的数据库视图，利用所述数据库视图中的查询语句获取展示数据后返回。
其中，数据库视图(view)是一个虚拟表，本身不存储数据，其内容由查询定义，可以按照指定的方式进行查询。对于复杂的查询事件，每次查询都需要编写查询语句必 然效率低下，本实施例利用数据库的视图功能解决该问题。可选的，本实施例可以为每个用户预先创建对应的数据库视图，其中，数据库视图所能查询的数据是返回给用户查阅的数据，本实施例称为展示数据，基于用户数据的存储位置等条件，可以预先编写能利用所述用户数据查询展示数据的查询语句以完成视图的创建，其中，每个用户的数据库视图与用户对应，可选的，可以采用用户标识将各个视图进行区分。当用户需要查阅时(例如用户利用APP等方式登录个人页面，该个人页面中提供有数据展示功能)，可以发起携带有用户标识的数据查阅请求，通过该用户标识可以查找对应所述用户的数据库视图，利用所述数据库视图中的查询语句获取展示数据后返回。
可选的，用户账户下可能还涉及多笔业务订单、具有多条用户数据，不同业务订单可能基于不同业务场景发起，在不同业务场景下用户所关注的数据不同，基于此，本实施例中，所述用户的数据库视图包括一个或多个对应不同业务场景的数据库视图，所述数据查阅请求还携带有对应业务场景的请求触发入口信息，通过所述用户标识查找对应所述用户的数据库视图，包括：通过所述用户标识和请求触发入口信息查找对应所述用户及业务场景的数据库视图。通过上述方式，可以达到不同业务场景下提供不同数据的效果。
作为例子，业务方提供有两类保险产品，第一类保险产品是可供用户将保险保额分享给家人，第二类保险产品是用户参与业务方的营销活动后，由业务方购买并分享保额给用户的。假设用户A涉及一笔购买第一类保险产品后产生的业务订单，并且用户A还将保险保额分享给家人；用户A参与了业务方的营销活动后，作为关联用户，获得了业务方分享的保险保额。其中，用户A可以使用业务方提供的客户端或登录服务页面查阅这两类保险产品的相关数据。针对第一类保险产品，用户A的需求是希望能够查阅到该第一类保险产品以及分享给家人的情况；针对第二类保险产品，用户A的需求是查阅到业务方分享的保险保额即可，并不需要涉及到业务方等诸多信息。
基于这两类保险产品所对应的不同业务场景，业务方可以预先配置这两种业务场景的数据库视图，以提供不同的业务数据。以使用客户端为例，用户A可以采用UID和/或身份证等用户标识登录服务器。可选的，客户端提供有请求触发入口，用户可以触发该请求触发入口，以使客户端发起数据查阅请求。可选的，该请求触发入口可以是包括查阅两类保险产品的数据查阅请求，则业务方可以分别通过前述两种业务场景的数据库视图，对应获取到两类保险产品的展示数据后返回。在另一些例子中，请求触发入口可以有两个，一个是针对第一类保险产品的触发入口，一个是针对第二类保险产品的触 发入口，用户可以触发其中任一入口，以查阅数据。如图1C所示，是本说明书根据一示例性实施例示出了两种不同业务场景下的展示数据示意图，在业务场景一中，作为“父亲”角色的用户将资产分享给孩子和孩子母亲，相对应的数据库视图可以获取到分享给孩子和孩子母亲的相关展示数据；在在业务场景二中，该用户是作为被业务方分享保险保额的关联用户，相对应的数据库视图可以获取到与其自身保额相关的数据。
接下来再通过一实施例对本说明书的业务处理方案进行详细说明。
本实施例以保险场景为例，若用户第一次通过业务方侧购买保险完成一笔有关保险的业务订单，业务方可以基于该笔业务订单为用户建立账户，本实施例称为健康账户并基于该账户生成用户数据。实际应用中，该业务方不限定是否是保险产品的服务方，可以是为保险产品服务方提供服务的平台。
针对健康账户，服务方可以预先配置数据结构，以规定账户数据中包含哪些字段。可选的，预设数据结构可以指定的数据主键包括：用户标识，可以是用户的身份证号码和/或UserID(User，Identification，用户身份证明，简称UID)。本实施例以用户的UID和身份证号码为例。通过基于用户UID和身份证号的索引，可以保证用户后续进行数据查询的时候，能支持多维度的查询。
由于该用户完成了保险订单，该用户作为主用户可以按照预设数据结构生成相应的用户数据。其中，保险订单涉及有干系人，如投保人和被保人。若主用户未分享保额，则被保人只有一个，即主用户自己。也就是说该保单的权益，只能主用户自己享用。其中，预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有人包括所述主用户。
本实施例中，用户A(主用户)也可以将保额权益分享给关联用户(用户B)。具体的：
服务方可以为用户A创建健康账户，对于用户的某一个保险订单，服务方会在该健康账户下创建对应该保险订单的主用户数据。其中，基于预设数据结构的规定，该条主用户数据的数据创建者字段指示用户A，资产字段指示用户A。该保险订单可以作为健康资产与该用户A绑定到健康账户上。
可选的，可以为用户A创建健康账户组视图，即用户A登录服务端后，通过该视图可以获得数据后展示给用户查阅，可选的，用户A可以使用自己的UID和身份证号码登录服务端并访问自己的健康账户。
由于用户A将保额分享给用户B，若用户B未在服务端有健康账户，则可以为用户B创建一健康账户。如果用户B已创建有健康账户，则不需要重复创建。同样，用户B也可以使用自己的UID和身份证号码来访问自己的健康账户。相应地，在用户B的健康账户下创建对应用户A所分享的保险订单的用户数据，用户B的用户数据中，资产字段指示资产所有者包括该用户B，并且与所述主用户的保险订单绑定。因此，用户B的健康账户下就拥有了A的保单，用户B通过自己的身份证或UID来访问健康账户的时候，通过该用户数据，可以查阅到账户下的保单是A分享给自己的，而资产所有人是自己。
由上述实施例可见，通过上述用户数据，主用户和关联用户之间的资产信息不会发生信息丢失的问题。另外，如果用户A有自己的保险订单，可以拥有自己是创建人，同时自己是资产所有人的用户数据。在一些业务场景中，用户A可能有多笔业务订单，关注自己的保单例如用户B将保单如果用户B只需要关注自己的账户，则可以通过数据创建者和资产所有者的关系来进行数据筛选，解决了不同业务视角业务隔离的问题。
在保单分享的场景下，健康资产的类型是保单。在其他场景中，还可以扩展不同的类型，例如体检报告或体质监测报告等其他类型，从而实现其他类型资产的分享。
对服务方来说，上述方案还可以解决权限隔离的问题，获取登录用户信息，通过登录用户信息查找登录用户数据，获取所述登录用户数据中的资产字段和数据创建者字段，进而确定所述登录用户对所述登录用户数据关联的业务订单的操作权限。作为例子，用户登录后可以获得当前登录用户的UID，该登录用户对应有用户数据，用户数据中资产字段指示有资产所有人UID，数据创建者字段指示有数据创建者UID，可以通过这三个UID的关系来确定用户的权限。例如登录态UID和资产所有人UID相同，但与数据创建者UID不同，说明这个账户下对应的资产是别人分享给自己的，则不能对该条用户数据关联的保单资产进行退保等操作，因此也解决了权限隔离的问题。
除了保险业务场景之外，本说明书实施例的业务处理方案也可以应用在其他涉及需要资产分享的业务场景中，例如红包分享场景或业务订单权益分享场景等，作为例子涉及购买会员的业务订单中，可以将所购买的会员资格分享给其他关联用户等。
如图2所示，是根据一示例性实施例示出的另一种业务处理方法，包括如下步骤：
在步骤202中，针对主用户的业务订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用 户数据的资产字段指示资产所有人包括所述主用户；
在步骤204中，若通过所述业务订单确定所述主用户将资产共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有人包括所述关联用户。
可选的，所述预设数据结构还指定有数据创建者字段，所述主用户数据的数据创建者字段指示所述主用户，所述关联用户数据的数据创建者字段指示所述主用户。
可选的，所述方法还包括：
基于用户的用户数据，创建对应用户的数据库视图，所述数据库视图对应有利用所述用户数据查询展示数据的查询语句；
若接收到用户发起的携带有用户标识的数据查阅请求，通过所述用户标识查找对应所述用户的数据库视图，利用所述数据库视图中的查询语句获取展示数据后返回。
可选的，所述用户的数据库视图包括一个或多个对应不同业务场景的数据库视图，所述数据查阅请求还携带有对应业务场景的请求触发入口信息，通过所述用户标识查找对应所述用户的数据库视图，包括：
通过所述用户标识和请求触发入口信息查找对应所述用户及业务场景的数据库视图。
可选的，所述展示数据包括如下一种或多种：所述资产所有人信息、所述业务订单信息或数据创建者信息。
可选的，所述方法还包括：
获取登录用户信息，通过登录用户信息查找登录用户数据，获取所述登录用户数据中的资产字段和数据创建者字段，进而确定所述登录用户对所述登录用户数据关联的业务订单的操作权限。
与前述业务处理方法的实施例相对应，本说明书还提供了业务处理装置及其所应用的设备的实施例。
本说明书业务处理装置的实施例可以应用在计算机设备上，例如服务器或终端设备。装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在文件处理的处理器将非易失性存储器中对应的计算机程序指令读取到内存中运行形成的。从硬件层面而言，如图3所 示，为本说明书实施例业务处理装置所在计算机设备的一种硬件结构图，除了图3所示的处理器310、内存330、网络接口320、以及非易失性存储器340之外，实施例中装置331所在的服务器或电子设备，通常根据该计算机设备的实际功能，还可以包括其他硬件，对此不再赘述。
如图4所示，图4是本说明书根据一示例性实施例示出的一种业务处理装置的框图，所述装置包括：
主用户数据创建模块410，用于：针对主用户的业务订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有人包括所述主用户；
关联用户数据创建模块420，用于：若通过所述业务订单确定所述主用户将资产共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有人包括所述关联用户。
可选的，所述预设数据结构还指定有数据创建者字段，所述主用户数据的数据创建者字段指示所述主用户，所述关联用户数据的数据创建者字段指示所述主用户。
可选的，所述装置还包括数据库视图创建模块，用于：基于用户的用户数据，创建对应用户的数据库视图，所述数据库视图对应有利用所述用户数据查询展示数据的查询语句；
数据查阅模块，用于：若接收到用户发起的携带有用户标识的数据查阅请求，通过所述用户标识查找对应所述用户的数据库视图，利用所述数据库视图中的查询语句获取展示数据后返回。
可选的，所述用户的数据库视图包括一个或多个对应不同业务场景的数据库视图，所述数据查阅请求还携带有对应业务场景的请求触发入口信息，所述数据查阅模块，还用于：
通过所述用户标识和请求触发入口信息查找对应所述用户及业务场景的数据库视图。
可选的，所述展示数据包括如下一种或多种：所述资产所有人信息、所述业务订单信息或数据创建者信息。
可选的，所述装置还包括权限确定模块，用于：
获取登录用户信息，通过登录用户信息查找登录用户数据，获取所述登录用户数据中的资产字段和数据创建者字段，进而确定所述登录用户对所述登录用户数据关联的业务订单的操作权限。
相应的，本说明书还提供一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如下方法：
针对主用户的业务订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有人包括所述主用户；
若通过所述业务订单确定所述主用户将资产共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有人包括所述关联用户。
上述业务处理装置中各个模块的功能和作用的实现过程具体详见上述业务处理方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本说明书方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
本领域技术人员在考虑说明书及实践这里的申请后，将容易想到本说明书的其它实施方案。本说明书旨在涵盖本说明书的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本说明书的一般性原理并包括本说明书未申请的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本说明书的真正范围和精神由下面的权利要求指出。
应当理解的是，本说明书并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本说明书的范围仅由所附的权利要求来限制。
以上所述仅为本说明书的较佳实施例而已，并不用以限制本说明书，凡在本说明书的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本说明书保护的范围之内。

Claims (10)

  1. 一种业务处理方法，包括：
    针对主用户的业务订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有人包括所述主用户；
    若通过所述业务订单确定所述主用户将资产共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有人包括所述关联用户。
  2. 根据权利要求1所述的方法，所述预设数据结构还指定有数据创建者字段，所述主用户数据的数据创建者字段指示所述主用户，所述关联用户数据的数据创建者字段指示所述主用户。
  3. 根据权利要求1或2所述的方法，所述方法还包括：
    基于用户的用户数据，创建对应用户的数据库视图，所述数据库视图对应有利用所述用户数据查询展示数据的查询语句；
    若接收到用户发起的携带有用户标识的数据查阅请求，通过所述用户标识查找对应所述用户的数据库视图，利用所述数据库视图中的查询语句获取展示数据后返回。
  4. 根据权利要求3所述的方法，所述用户的数据库视图包括一个或多个对应不同业务场景的数据库视图，所述数据查阅请求还携带有对应业务场景的请求触发入口信息，所述通过所述用户标识查找对应所述用户的数据库视图，包括：
    通过所述用户标识和请求触发入口信息查找对应所述用户及业务场景的数据库视图。
  5. 根据权利要求3或4所述的方法，所述展示数据包括如下一种或多种：所述资产所有人信息、所述业务订单信息或数据创建者信息。
  6. 根据权利要求1所述的方法，所述方法还包括：
    获取登录用户信息，通过登录用户信息查找登录用户数据，获取所述登录用户数据中的资产字段和数据创建者字段，进而确定所述登录用户对所述登录用户数据关联的业务订单的操作权限。
  7. 一种业务处理方法，包括：
    针对主用户的保险订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有者包括所述主用户；
    若通过所述保险订单确定所述主用户将保险保额共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有者包括所述关联用户。
  8. 根据权利要求7所述的方法，所述预设数据结构还指定有数据创建者字段，所述主用户数据的数据创建者字段指示所述主用户，所述关联用户数据的数据创建者字段指示所述主用户。
  9. 一种业务处理装置，所述装置包括：
    主用户数据创建模块，用于：针对主用户的业务订单，根据预设数据结构创建绑定所述业务订单的主用户数据，其中，所述预设数据结构至少指定用户数据具有资产字段，所述主用户数据的资产字段指示资产所有人包括所述主用户；
    关联用户数据创建模块，用于：若通过所述业务订单确定所述主用户将资产共享给关联用户，根据所述预设数据结构创建绑定所述业务订单的关联用户数据，其中，所述关联用户数据的资产字段指示资产所有人包括所述关联用户。
  10. 一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求1至8任一所述的方法。
PCT/CN2019/119191 2018-12-25 2019-11-18 业务处理方法、装置及设备 WO2020134701A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811593751.3 2018-12-25
CN201811593751.3A CN110046950A (zh) 2018-12-25 2018-12-25 业务处理方法、装置及设备

Publications (1)

Publication Number Publication Date
WO2020134701A1 true WO2020134701A1 (zh) 2020-07-02

Family

ID=67274042

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/119191 WO2020134701A1 (zh) 2018-12-25 2019-11-18 业务处理方法、装置及设备

Country Status (3)

Country Link
CN (1) CN110046950A (zh)
TW (1) TW202025007A (zh)
WO (1) WO2020134701A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110046950A (zh) * 2018-12-25 2019-07-23 阿里巴巴集团控股有限公司 业务处理方法、装置及设备
CN111161088A (zh) * 2019-12-31 2020-05-15 上海亿保健康管理有限公司 票据处理方法、装置和设备
CN112486955B (zh) * 2020-12-04 2021-07-27 北京神州慧安科技有限公司 基于大数据和人工智能的数据维护方法及大数据服务器
CN112416966B (zh) * 2020-12-11 2024-01-26 北京顺达同行科技有限公司 即席查询方法、装置、计算机设备和存储介质
CN115564356B (zh) * 2022-10-28 2024-04-12 上海东普信息科技有限公司 亲友物流订单信息实时共享方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020174061A1 (en) * 2000-12-04 2002-11-21 Venkatesan Srinivasan Method and apparatus for intelligent, scalable communications in a multi-asset financial fulfillment network
CN106022908A (zh) * 2016-05-17 2016-10-12 中国建设银行股份有限公司 一种资产负债信息的查询方法及系统
CN107066457A (zh) * 2016-08-23 2017-08-18 平安科技（深圳）有限公司 用户信息视图构建方法和系统
CN107506658A (zh) * 2017-07-10 2017-12-22 上海最会保网络科技有限公司 一种用户权限管理系统及方法
CN110046950A (zh) * 2018-12-25 2019-07-23 阿里巴巴集团控股有限公司 业务处理方法、装置及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020174061A1 (en) * 2000-12-04 2002-11-21 Venkatesan Srinivasan Method and apparatus for intelligent, scalable communications in a multi-asset financial fulfillment network
CN106022908A (zh) * 2016-05-17 2016-10-12 中国建设银行股份有限公司 一种资产负债信息的查询方法及系统
CN107066457A (zh) * 2016-08-23 2017-08-18 平安科技（深圳）有限公司 用户信息视图构建方法和系统
CN107506658A (zh) * 2017-07-10 2017-12-22 上海最会保网络科技有限公司 一种用户权限管理系统及方法
CN110046950A (zh) * 2018-12-25 2019-07-23 阿里巴巴集团控股有限公司 业务处理方法、装置及设备

Also Published As

Publication number Publication date
TW202025007A (zh) 2020-07-01
CN110046950A (zh) 2019-07-23

Similar Documents

Publication Publication Date Title
WO2020134701A1 (zh) 业务处理方法、装置及设备
US11463508B1 (en) System and method for global data sharing
US11620404B2 (en) System and method of permission-based data sharing
US11810089B2 (en) Data exchange-based platform
CN104866513B (zh) 用于跨租户数据访问的系统和方法
CN112424766A (zh) 数据交换
WO2019084922A1 (zh) 信息处理方法和系统、服务器、终端、计算机存储介质
CN109937420A (zh) 去识别化分布式桥接网络平台
CN112789616A (zh) 私有数据交换
US9262792B2 (en) Rights management for content aggregators
US10453091B2 (en) System and method to build external facing information platform to generate target list of entities
US10192250B1 (en) Systems and methods for providing access to data sets owned by different entities
AU2016215472A1 (en) Universal business procurement
US9525687B2 (en) Template for customer attributes
US11790470B1 (en) Storage service for sensitive customer data
JP7465472B2 (ja) コンサルティング導入システム
US20160154841A1 (en) Methods and apparatus for administering a mutually owned secure email and file repository for family members
US20240095442A1 (en) Automated document processing
Harfoush Data Ethics: Facts and Fiction
Dhar et al. Comments on'Protecting Consumer Privacy in an Era of Rapid Change: Aproposed Framework for Businesses and Policymakers'
Ameh DESIGN AND IMPLEMENTATION OF A WEB BASED SHOPPING MANAGEMENT SYSTEM
CA2755688C (en) Systems and methods for generating data feeds

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19906554

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19906554

Country of ref document: EP

Kind code of ref document: A1