為克服相關技術中存在的問題，本說明書提供了業務處理方法、裝置及設備。
根據本說明書實施例的第一方面，提供一種業務處理方法，包括：
針對主用戶的業務訂單，根據預設資料結構創建綁定所述業務訂單的主用戶資料，其中，所述預設資料結構至少指定用戶資料具有資產字段，所述主用戶資料的資產字段指示資產所有人包括所述主用戶；
若透過所述業務訂單確定所述主用戶將資產共享給關聯用戶，根據所述預設資料結構創建綁定所述業務訂單的關聯用戶資料，其中，所述關聯用戶資料的資產字段指示資產所有人包括所述關聯用戶。
可選的，所述預設資料結構還指定有資料創建者字段，所述主用戶資料的資料創建者字段指示所述主用戶，所述關聯用戶資料的資料創建者字段指示所述主用戶。
可選的，所述方法還包括：
基於用戶的用戶資料，創建對應用戶的資料庫視圖，所述資料庫視圖對應有利用所述用戶資料查詢展示資料的查詢語句；
若接收到用戶發起的攜帶有用戶標識的資料查閱請求，透過所述用戶標識查找對應所述用戶的資料庫視圖，利用所述資料庫視圖中的查詢語句獲取展示資料後返回。
可選的，所述用戶的資料庫視圖包括一個或多個對應不同業務場景的資料庫視圖，所述資料查閱請求還攜帶有對應業務場景的請求觸發入口資訊，所述透過所述用戶標識查找對應所述用戶的資料庫視圖，包括：
透過所述用戶標識和請求觸發入口資訊查找對應所述用戶及業務場景的資料庫視圖。
可選的，所述展示資料包括如下一種或多種：所述資產所有人資訊、所述業務訂單資訊或資料創建者資訊。
可選的，所述方法還包括：
獲取登錄用戶資訊，透過登錄用戶資訊查找登錄用戶資料，獲取所述登錄用戶資料中的資產字段和資料創建者字段，進而確定所述登錄用戶對所述登錄用戶資料關聯的業務訂單的操作權限。
根據本說明書實施例的第二方面，提供另一種業務處理方法，包括：
針對主用戶的保險訂單，根據預設資料結構創建綁定所述業務訂單的主用戶資料，其中，所述預設資料結構至少指定用戶資料具有資產字段，所述主用戶資料的資產字段指示資產所有者包括所述主用戶；
若透過所述保險訂單確定所述主用戶將保險保額共享給關聯用戶，根據所述預設資料結構創建綁定所述業務訂單的關聯用戶資料，其中，所述關聯用戶資料的資產字段指示資產所有者包括所述關聯用戶。
可選的，所述預設資料結構還指定有資料創建者字段，所述主用戶資料的資料創建者字段指示所述主用戶，所述關聯用戶資料的資料創建者字段指示所述主用戶。
可選的，所述方法還包括：
基於用戶的用戶資料，創建對應用戶的資料庫視圖，所述資料庫視圖對應有利用所述用戶資料查詢展示資料的查詢語句；
若接收到用戶發起的攜帶有用戶標識的資料查閱請求，透過所述用戶標識查找對應所述用戶的資料庫視圖，利用所述資料庫視圖中的查詢語句獲取展示資料後返回。
可選的，所述用戶的資料庫視圖包括一個或多個對應不同業務場景的資料庫視圖，所述資料查閱請求還攜帶有對應業務場景的請求觸發入口資訊，所述透過所述用戶標識查找對應所述用戶的資料庫視圖，包括：
透過所述用戶標識和請求觸發入口資訊查找對應所述用戶及業務場景的資料庫視圖。
可選的，所述展示資料包括如下一種或多種：所述資產所有人資訊、所述保險訂單資訊或資料創建者資訊。
可選的，所述方法還包括：
獲取登錄用戶資訊，透過登錄用戶資訊查找登錄用戶資料，獲取所述登錄用戶資料中的資產字段和資料創建者字段，進而確定所述登錄用戶對所述登錄用戶資料關聯的保險訂單的操作權限。
根據本說明書實施例的第三方面，提供一種業務處理裝置，所述裝置包括：
主用戶資料創建模組，用於：針對主用戶的業務訂單，根據預設資料結構創建綁定所述業務訂單的主用戶資料，其中，所述預設資料結構至少指定用戶資料具有資產字段，所述主用戶資料的資產字段指示資產所有人包括所述主用戶；
關聯用戶資料創建模組，用於：若透過所述業務訂單確定所述主用戶將資產共享給關聯用戶，根據所述預設資料結構創建綁定所述業務訂單的關聯用戶資料，其中，所述關聯用戶資料的資產字段指示資產所有人包括所述關聯用戶。
可選的，所述預設資料結構還指定有資料創建者字段，所述主用戶資料的資料創建者字段指示所述主用戶，所述關聯用戶資料的資料創建者字段指示所述主用戶。
可選的，所述裝置還包括資料庫視圖創建模組，用於：基於用戶的用戶資料，創建對應用戶的資料庫視圖，所述資料庫視圖對應有利用所述用戶資料查詢展示資料的查詢語句；
資料查閱模組，用於：若接收到用戶發起的攜帶有用戶標識的資料查閱請求，透過所述用戶標識查找對應所述用戶的資料庫視圖，利用所述資料庫視圖中的查詢語句獲取展示資料後返回。
可選的，所述用戶的資料庫視圖包括一個或多個對應不同業務場景的資料庫視圖，所述資料查閱請求還攜帶有對應業務場景的請求觸發入口資訊，所述資料查閱模組，還用於：
透過所述用戶標識和請求觸發入口資訊查找對應所述用戶及業務場景的資料庫視圖。
可選的，所述展示資料包括如下一種或多種：所述資產所有人資訊、所述業務訂單資訊或資料創建者資訊。
可選的，所述裝置還包括權限確定模組，用於：
獲取登錄用戶資訊，透過登錄用戶資訊查找登錄用戶資料，獲取所述登錄用戶資料中的資產字段和資料創建者字段，進而確定所述登錄用戶對所述登錄用戶資料關聯的業務訂單的操作權限。
根據本說明書實施例的第四方面，提供一種電腦設備，包括儲存器、處理器及儲存在儲存器上並可在處理器上運行的電腦程式，其中，所述處理器執行所述程式時實現如下方法：
針對主用戶的業務訂單，根據預設資料結構創建綁定所述業務訂單的主用戶資料，其中，所述預設資料結構至少指定用戶資料具有資產字段，所述主用戶資料的資產字段指示資產所有人包括所述主用戶；
若透過所述業務訂單確定所述主用戶將資產共享給關聯用戶，根據所述預設資料結構創建綁定所述業務訂單的關聯用戶資料，其中，所述關聯用戶資料的資產字段指示資產所有人包括所述關聯用戶。
本說明書的實施例提供的技術方案可以包括以下有益效果：
本說明書實施例中，對於主用戶向關聯用戶分享的業務訂單的資產，可以對應創建有綁定業務訂單的關聯用戶資料，利用該關聯用戶資料的資產字段記錄該關聯用戶所擁有的資產。因此可以有效記錄業務訂單中主用戶與共享者的關係，可以支援共享者對業務訂單的查閱，可以便於業務提供方進行資料的維護。
應當理解的是，以上的一般描述和後文的細節描述僅是示例性和解釋性的，並不能限制本說明書。In order to overcome the problems in related technologies, this specification provides business processing methods, devices and equipment.
According to the first aspect of the embodiments of this specification, a service processing method is provided, including:
For the business order of the master user, the master user profile bound to the business order is created according to a preset profile structure, wherein the preset profile structure at least specifies that the user profile has an asset field, and the asset field of the master user profile indicates an asset The owner includes the main user;
If it is determined through the business order that the main user shares the asset with the associated user, the associated user profile bound to the business order is created according to the preset data structure, wherein the asset field of the associated user profile indicates that the asset is owned The person includes the associated user.
Optionally, the preset profile structure further specifies a profile creator field, the profile creator field of the master user profile indicates the master user, and the profile creator field of the associated user profile indicates the master user.
Optionally, the method further includes:
Based on the user profile of the user, creating a database view corresponding to the user, the database view corresponding to a query sentence for querying and displaying data using the user profile;
If a user-initiated data query request carrying a user identification is received, the database view corresponding to the user is searched through the user identification, and the display data is obtained by using the query sentence in the database view and returned.
Optionally, 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, and the search is performed through the user identifier The database view corresponding to the user includes:
Search for the database view corresponding to the user and business scenario through the user identification and request trigger entry information.
Optionally, the display data includes one or more of the following: the asset owner information, the business order information, or the data creator information.
Optionally, the method further includes:
Obtain log-in user information, search log-in user information through log-in user information, obtain the asset field and data creator field in the log-in user profile, and then determine the operation authority of the log-in user on the business order associated with the log-in user profile.
According to the second aspect of the embodiments of this specification, another service processing method is provided, including:
For the main user’s insurance order, create a master user profile bound to the business order according to a preset profile structure, wherein the preset profile structure at least specifies that the user profile has an asset field, and the asset field of the master profile indicates an asset The owner includes the main user;
If it is determined through the insurance order that the main user shares the insurance coverage with the associated users, 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.
Optionally, the preset profile structure further specifies a profile creator field, the profile creator field of the master user profile indicates the master user, and the profile creator field of the associated user profile indicates the master user.
Optionally, the method further includes:
Based on the user profile of the user, creating a database view corresponding to the user, the database view corresponding to a query sentence for querying and displaying data using the user profile;
If a user-initiated data query request carrying a user identification is received, the database view corresponding to the user is searched through the user identification, and the display data is obtained by using the query sentence in the database view and returned.
Optionally, 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, and the search is performed through the user identifier The database view corresponding to the user includes:
Search for the database view corresponding to the user and business scenario through the user identification and request trigger entry information.
Optionally, the display data includes one or more of the following: the asset owner information, the insurance order information, or the data creator information.
Optionally, the method further includes:
Obtain log-in user information, search log-in user information through log-in user information, obtain asset fields and data creator fields in said log-in user information, and then determine said log-in user's operation authority on insurance orders associated with said log-in user information.
According to a third aspect of the embodiments of this specification, there is provided a service processing apparatus, the apparatus including:
The master user profile creation module is used to create a master user profile bound to the business order based on the master user’s business order according to a preset profile structure, wherein the preset profile structure at least specifies that the user profile has an asset field, The asset field of the master user profile indicates that the asset owner includes the master user;
The associated user data creation module is used for: if it is determined through the business order that the main user shares assets with the associated user, create the associated user data bound to the business order according to the preset data structure, where all The asset field of the associated user profile indicates that the asset owner includes the associated user.
Optionally, the preset profile structure further specifies a profile creator field, the profile creator field of the master user profile indicates the master user, and the profile creator field of the associated user profile indicates the master user.
Optionally, the device further includes a database view creation module, which is used to create a database view corresponding to the user based on the user profile of the user, and the database view corresponds to a query for querying and displaying data using the user profile. Statement
The data retrieval module is used for: if a data retrieval request carrying a user identification is received from a user, the database view corresponding to the user is searched through the user identification, and the query statement in the database view is used to obtain the display Return after the information.
Optionally, 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, and the data query module further Used for:
Search for the database view corresponding to the user and business scenario through the user identification and request trigger entry information.
Optionally, the display data includes one or more of the following: the asset owner information, the business order information, or the data creator information.
Optionally, the device further includes a permission determination module for:
Obtain log-in user information, search log-in user information through log-in user information, obtain the asset field and data creator field in the log-in user profile, and then determine the operation authority of the log-in user on the business order associated with the log-in user profile.
According to a fourth aspect of the embodiments of this specification, a computer device is provided, including a storage, a processor, and a computer program stored on the storage and running on the processor, wherein the processor executes the program when the program is executed The following method:
For the business order of the master user, the master user profile bound to the business order is created according to a preset profile structure, wherein the preset profile structure at least specifies that the user profile has an asset field, and the asset field of the master user profile indicates an asset The owner includes the main user;
If it is determined through the business order that the main user shares the asset with the associated user, the associated user profile bound to the business order is created according to the preset data structure, wherein the asset field of the associated user profile indicates that the asset is owned The person includes the associated user.
The technical solutions provided by the embodiments of this specification may include the following beneficial effects:
In the embodiment of this specification, for the asset of the business order shared by the master user with the associated user, the associated user profile with the bound business order can be created correspondingly, and the asset field of the associated user profile is used to record the assets owned by the associated user. Therefore, the relationship between the main user and the sharer in the business order can be effectively recorded, and the sharer can support the review of the business order, which can facilitate the maintenance of data by the service provider.
It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit this specification.
這裡將詳細地對示例性實施例進行說明，其示例表示在圖式中。下面的描述涉及圖式時，除非另有表示，不同圖式中的相同數字表示相同或相似的要素。以下示例性實施例中所描述的實施方式並不代表與本說明書相一致的所有實施方式。相反，它們僅是與如所附申請專利範圍中所詳述的、本說明書的一些方面相一致的裝置和方法的例子。
在本說明書使用的術語是僅僅出於描述特定實施例的目的，而非旨在限制本說明書。在本說明書和所附申請專利範圍中所使用的單數形式的“一種”、“所述”和“該”也旨在包括多數形式，除非上下文清楚地表示其他含義。還應當理解，本文中使用的術語“及/或”是指並包含一個或多個相關聯的列出項目的任何或所有可能組合。
應當理解，儘管在本說明書可能採用術語第一、第二、第三等來描述各種資訊，但這些資訊不應限於這些術語。這些術語僅用來將同一類型的資訊彼此區分開。例如，在不脫離本說明書範圍的情況下，第一資訊也可以被稱為第二資訊，類似地，第二資訊也可以被稱為第一資訊。取決於語境，如在此所使用的詞語“如果”可以被解釋成為“在……時”或“當……時”或“響應於確定”。
在一些業務場景中，可能會涉及資產共享的情況。例如，以保險業務場景為例，用戶可以將保險保額共享給子女等其他人。首先對保險業務涉及的詞語進行說明：
保險人，保險人又稱“承保人”，是指與投保人訂立保險合同，並承擔賠償或者給付保險金責任的保險主體。
投保人，是指與保險人訂立保險合同，並按照保險合同負有支付保險費義務的人。
被保人，是指根據保險合同，其財產利益或人身受保險合同保障，在保險事故發生後，享有保額請求權的人。
保額，保險金額的簡稱，指保險人承擔賠償或者給付保險金責任的最高限額。
向用戶提供保險業務時，用戶會有相應的協議簽約動作，之後該用戶會獲得一份保單。其中，保額可能是固定不變的，也有可能發生變動。
作為例子，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是本說明書根據一示例性實施例示出的一種業務處理裝置的方塊圖，所述裝置包括：
主用戶資料創建模組41，用於：針對主用戶的業務訂單，根據預設資料結構創建綁定所述業務訂單的主用戶資料，其中，所述預設資料結構至少指定用戶資料具有資產字段，所述主用戶資料的資產字段指示資產所有人包括所述主用戶；
關聯用戶資料創建模組42，用於：若透過所述業務訂單確定所述主用戶將資產共享給關聯用戶，根據所述預設資料結構創建綁定所述業務訂單的關聯用戶資料，其中，所述關聯用戶資料的資產字段指示資產所有人包括所述關聯用戶。
可選的，所述預設資料結構還指定有資料創建者字段，所述主用戶資料的資料創建者字段指示所述主用戶，所述關聯用戶資料的資料創建者字段指示所述主用戶。
可選的，所述裝置還包括資料庫視圖創建模組，用於：基於用戶的用戶資料，創建對應用戶的資料庫視圖，所述資料庫視圖對應有利用所述用戶資料查詢展示資料的查詢語句；
資料查閱模組，用於：若接收到用戶發起的攜帶有用戶標識的資料查閱請求，透過所述用戶標識查找對應所述用戶的資料庫視圖，利用所述資料庫視圖中的查詢語句獲取展示資料後返回。
可選的，所述用戶的資料庫視圖包括一個或多個對應不同業務場景的資料庫視圖，所述資料查閱請求還攜帶有對應業務場景的請求觸發入口資訊，所述資料查閱模組，還用於：
透過所述用戶標識和請求觸發入口資訊查找對應所述用戶及業務場景的資料庫視圖。
可選的，所述展示資料包括如下一種或多種：所述資產所有人資訊、所述業務訂單資訊或資料創建者資訊。
可選的，所述裝置還包括權限確定模組，用於：
獲取登錄用戶資訊，透過登錄用戶資訊查找登錄用戶資料，獲取所述登錄用戶資料中的資產字段和資料創建者字段，進而確定所述登錄用戶對所述登錄用戶資料關聯的業務訂單的操作權限。
相應的，本說明書還提供一種電腦設備，包括儲存器、處理器及儲存在儲存器上並可在處理器上運行的電腦程式，其中，所述處理器執行所述程式時實現如下方法：
針對主用戶的業務訂單，根據預設資料結構創建綁定所述業務訂單的主用戶資料，其中，所述預設資料結構至少指定用戶資料具有資產字段，所述主用戶資料的資產字段指示資產所有人包括所述主用戶；
若透過所述業務訂單確定所述主用戶將資產共享給關聯用戶，根據所述預設資料結構創建綁定所述業務訂單的關聯用戶資料，其中，所述關聯用戶資料的資產字段指示資產所有人包括所述關聯用戶。
上述業務處理裝置中各個模組的功能和作用的實現過程具體詳見上述業務處理方法中對應步驟的實現過程，在此不再贅述。
對於裝置實施例而言，由於其基本對應於方法實施例，所以相關之處參見方法實施例的部分說明即可。以上所描述的裝置實施例僅僅是示意性的，其中所述作為分離部件說明的模組可以是或者也可以不是實體上分開的，作為模組顯示的部件可以是或者也可以不是實體模組，即可以位於一個地方，或者也可以分佈到多個網路模組上。可以根據實際的需要選擇其中的部分或者全部模組來實現本說明書方案的目的。本領域普通技術人員在不付出進步性勞動的情況下，即可以理解並實施。
上述對本說明書特定實施例進行了描述。其它實施例在所附申請專利範圍的範圍內。在一些情況下，在申請專利範圍中記載的動作或步驟可以按照不同於實施例中的順序來執行並且仍然可以實現期望的結果。另外，在圖式中描繪的過程不一定要求示出的特定順序或者連續順序才能實現期望的結果。在某些實施方式中，多任務處理和並行處理也是可以的或者可能是有利的。
本領域技術人員在考慮說明書及實踐這裡申請的發明後，將容易想到本說明書的其它實施方案。本說明書旨在涵蓋本說明書的任何變形、用途或者適應性變化，這些變形、用途或者適應性變化遵循本說明書的一般性原理並包括本說明書未申請的本技術領域中的公知常識或慣用技術手段。說明書和實施例僅被視為示例性的，本說明書的真正範圍和精神由下面的請求項指出。
應當理解的是，本說明書並不局限於上面已經描述並在圖式中示出的精確結構，並且可以在不脫離其範圍進行各種修改和改變。本說明書的範圍僅由所附的請求項來限制。
以上所述僅為本說明書的較佳實施例而已，並不用以限制本說明書，凡在本說明書的精神和原則之內，所做的任何修改、等同替換、改進等，均應包含在本說明書保護的範圍之內。The exemplary embodiments will be described in detail here, and examples thereof are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with this specification. On the contrary, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the scope of the appended application.
The terms used in this specification are only for the purpose of describing specific embodiments, and are not intended to limit the specification. The singular forms of "a", "the" and "the" used in this specification and the scope of the appended applications are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and/or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.
It should be understood that although the terms 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. For example, without departing from the scope of this specification, the first information can also be referred to as second information, and similarly, the second information can also be referred to as first information. Depending on the context, the word "if" as used herein can be interpreted as "when" or "when" or "in response to determination".
In some business scenarios, asset sharing may be involved. For example, taking an insurance business scenario as an example, users can share the insurance coverage with other people such as their children. First, explain the terms involved in insurance business:
The insurer, the insurer, also known as the "underwriter", refers to the insurance subject that has concluded an insurance contract with the insured and is liable for compensation or payment of insurance money.
An insured person refers to a person who has concluded an insurance contract with an insurer and is obligated to pay insurance premiums in accordance with the insurance contract.
The insured refers to a person whose property or personal interests are protected by the insurance contract under the insurance contract, and who enjoy the right to claim the amount of insurance after an insured incident occurs.
Insured amount, short for insured amount, refers to the maximum limit of the insurer's liability for compensation or payment of insurance money.
When providing a user with insurance services, the user will have a corresponding contract signing action, and then the user will get an insurance policy. Among them, the insured amount may be fixed or change.
As an example, Lulu purchases an insurance product from an insurance company. Lulu is the insured person, and the insurer is the insurance company. Lulu can designate the insured person for the insurance amount as himself or another person.
In other cases, with the innovation of Internet services, other types of insurance have emerged. For example, a third-party payment platform party purchases an insurance product for a user from an insurance company, where 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. This business data can record user information and various related information about the insurance order.
In other insurance businesses, there may also be a situation where the insured amount is shared, and the user shares the insured amount with other people, such as the user's family members (own children or spouse, etc.). In response to this situation, business processing will face some problems, such as how to record the relationship between the user and the sharer in the insurance order, and how to record the sharer’s information in the user profile so that the sharer can also check the user’s share Other people’s insurance policies, etc.
Based on this, this manual 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 review of the insurance order, and facilitate the maintenance of data by the business provider. Next, the embodiments of this specification are described in detail.
As shown in Fig. 1A, Fig. 1A is a flowchart of a service processing method according to an exemplary embodiment of this specification, including the following steps:
In step 102, for the insurance order of the master user, create a master user profile bound to the business order according to a preset profile structure, wherein the preset profile structure at least specifies that the user profile has an asset field, and the profile of the master user profile The asset field indicates that the asset owner includes the master user.
In step 104, if it is determined through the insurance order that the primary user shares the insurance coverage with the associated users, create associated user data bound to the business order according to the preset data structure, wherein the associated user data The asset field of indicates that the asset owner includes the associated user.
As shown in FIG. 1B, it is a business processing scene diagram shown in this specification according to an exemplary embodiment. In the embodiment of this specification, two types of users are involved. In order to facilitate the distinction, this embodiment refers to one of the types as primary users, that is, insurance orders. The owner is the user who is the insured; the other is called the associated user, that is, the main user shares the insurance coverage of his own insurance order.
The business processing method of this embodiment can be applied to the business side. The business side can be a service side, specifically, a service side that provides insurance products. In other examples, the business side can also be an insurance platform business side. Party can access multiple insurance product service providers to provide users with various insurance products.
For the main user, the service provider will create a user profile for the insurance order. The embodiment of this specification can propose a solution based on the data structure of the user profile. In this embodiment, the insurance coverage can be used as the user’s asset. For the main user, its assets include the insurance coverage. The main user shares the insurance coverage with the associated users, that is, the asset is shared, and the associated user also owns the insurance. assets. Therefore, in this embodiment, a data structure can be set in advance. The data structure at least specifies that the user profile has an asset field, and the asset field is used to indicate the asset owner. It is understandable that the asset field of the master user profile indicates that the asset owner includes the master user . Based on this, the master user profile 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 user profile is the master user. It can be understood that in practical applications, 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., to record in detail Information about the business order of the user.
Among them, if the user purchases insurance through the business side for the first time to complete an insurance-related business order, the business side can create an account for the main user based on the business order, and the user information of the main user belongs to the data under the user’s account ; It is understandable that if the user has other business orders in the future, there can be more user information under the account.
Further, for an insurance order in which the main user shares the insurance coverage with the associated user, this embodiment will also create an associated user profile for the associated user according to the preset profile structure, because at least the designated user profile in the profile structure has an asset field , The asset field is used to indicate the owner of the asset. It can be understood that the asset field of the associated user profile indicates that the asset owner includes the associated user. Based on this, the associated user profile created with the preset data structure contains assets. The asset field can determine that the asset owner in the associated user profile includes the associated user.
Among them, if the associated user is sharing assets by the master user for the first time, an account can be created for the associated user, and the user information of the associated user belongs to the information under the user’s account; it is understandable that if the associated user subsequently returns If the main user shares the assets of other business orders, the account can have more information; optionally, if the associated user is subsequently shared by other main users with the assets of other business orders, it can be in the associated user’s account Create other information under the link, or create another account for the associated user to create information under the other account.
In practical applications, a user can also be the primary user and the associated user at the same time. For example, user Lulu has a business order A, and the assets of business order B are shared by user Tony. You can create a Lulu master account for business order A. The master account has the main user profile of business order A, and at the same time, another Lulu account is created for user Tony's business order B. This account is an associated account associated with business order B, and the associated account is associated with business order B user information. In other scenarios, it is also possible to create only one account for Lulu, under which there are both the main user profile of business order A and the associated user profile of business order B.
Among them, the main user data and the related user data are bound to the main user’s business order. The binding can be implemented in multiple ways. As an example, the default data structure can be specified with a business order information field. Write information such as the identification of the business order in the information field. It can also record the correspondence between user data and business orders in other data tables.
It can be seen from the above embodiment that the main user also creates user information for the associated user shared by the insurance coverage, and uses the asset field of the associated user information to record the insurance coverage owned by the associated user, so the main user in the business order can be effectively recorded The relationship with the sharer can support the sharer's access to insurance orders and facilitate the maintenance of data by the business provider.
In order to provide users with clearer access to asset sources and other information, and to facilitate data maintenance by business parties, optionally, the default data structure also specifies a data creator field. The data creator field of the master user profile indicates the master For the user, the data creator field of the associated user profile indicates the primary user; for example, through the data creator field, the service party can determine which user's insurance order created the user profile. For example, from the profile creator field of the master user profile, it can be determined that the profile creator of the user profile is the master user, and the profile creator field of the associated user profile can determine that the profile creator of the associated user profile is the associated user. , Based on this, the business party, the main user or the associated user, etc. can provide user information to the data creator and know the source of the asset.
In actual applications, for the business party, due to business needs, the created user profile may contain a lot of information about the user and the business order, such as the order ID, order serial number, or payment flow created by the business party for the order Number and so on. But for the user, the user may only care about some of the information, and the user still needs to check some of the information, such as checking the insurance protection period, the amount of insurance, the time of insurance purchase, or the insurance contract. The information the user queries may only be a small number of fields in the user data, such as insurance contracts and other data may not be in the same database table as the user data, and the query process may involve multiple database tables. Based on this, the following solutions are also provided in this embodiment, which can facilitate the processing of the user's data access requirements. Optionally, in this embodiment, a database view corresponding to the user can be created based on the user data of the user, and the database view corresponds to a query sentence that uses the user data to query and display data; The user-identified data lookup request searches for the database view corresponding to the user through the user identification, uses the query sentence in the database view to obtain the display data and returns.
Among them, the database view (view) is a virtual table that does not store data itself, and its content is defined by a query, and can be queried in a specified manner. For complex query events, the need to write query statements for each query is bound to be inefficient. This embodiment uses the view function of the database to solve this problem. Optionally, this embodiment can 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, and is based on user data. Storage location and other conditions, you can pre-write query statements that can use the user data to query the display data to complete the creation of the view. Among them, the database view of each user corresponds to the user. Optionally, the user ID can be used to combine the views Make a distinction. When a user needs to consult (for example, the user logs in to a personal page using APP, etc., which provides a data display function), a data query request with a user ID can be initiated, and the user ID can be used to find the data corresponding to the user The database view uses the query statement in the database view to obtain the display data and return.
Optionally, the user account may also involve multiple business orders and have multiple user profiles. Different business orders may be initiated based on different business scenarios. In different business scenarios, users pay attention to different materials. Based on this, in this embodiment , The database view of the user includes one or more database views corresponding to different business scenarios, the data look-up request also carries request trigger entry information corresponding to the business scenario, and the search corresponding to the The database view of the user includes: searching the database view corresponding to the user and business scenario through the user identification and request trigger entry information. Through the above method, the effect of providing different data under different business scenarios can be achieved.
As an example, the business side provides two types of insurance products. The first type of insurance product is for users to share the insurance coverage with their family members, and the second type of insurance product is for users to participate in the business side’s marketing activities, which are purchased and shared by the business side The sum assured to the user. Assume that user A is involved in a business order generated after purchasing the first type of insurance product, and user A also shares the insurance coverage with his family; after user A participates in the marketing activities of the business side, as an associated user, he obtains the information shared by the business side Insurance coverage. Among them, user A can use the client or login service page provided by the business party to check the relevant information of the two types of insurance products. For the first type of insurance products, user A’s demand is to be able to view the first type of insurance products and share with his family; for the second type of insurance products, user A’s need is to view the insurance coverage shared by the business side That is, there is no need to involve a lot of information such as business parties.
Based on the different business scenarios corresponding to these two types of insurance products, the business party can pre-configure the database views of these two business scenarios to provide different business data. Taking the client as an example, user A can log in to the server with a user ID such as UID and/or ID card. Optionally, the client provides a request trigger entry, and the user can trigger the request trigger entry, so that the client initiates a data query request. Optionally, the request trigger entry may include a data lookup request for viewing two types of insurance products, and the business party may respectively obtain the display data of the two types of insurance products through the database views of the foregoing two business scenarios and return. In some other examples, there may be two request trigger entrances, one is for the first type of insurance product, and the other is for the second type of insurance product. The user can trigger any of them to view information. As shown in Fig. 1C, this specification shows a schematic diagram of displaying data in two different business scenarios according to an exemplary embodiment. In business scenario 1, a user in the role of "father" shares assets with the child and the child’s mother. The corresponding database view can obtain the relevant display materials shared with the child and the child’s mother; in business scenario 2, the user is an associated user who shares the insurance coverage by the business party, and the corresponding database view can be obtained To the information related to its own insurance coverage.
Next, the business processing scheme of this specification will be described in detail through an embodiment.
This embodiment takes the insurance scenario as an example. If the user purchases insurance through the business side to complete a business order related to insurance, the business side can create an account for the user based on the business order. This embodiment is called a health account and is based on This account generates user profile. In actual applications, the business party does not limit whether it is a service party of insurance products, but can be a platform that provides services for insurance product service parties.
For health accounts, the service party can pre-configure the data structure to specify which fields are included in the account data. Optionally, the data primary key that can be specified by the preset data structure includes: user identification, which can be the user's ID number and/or UserID (User, Identification, UID for short). This embodiment takes the UID and ID number of the user as an example. Through the index based on the user's UID and ID number, it can be ensured that the user can support multi-dimensional query when querying data later.
Since the user has completed the insurance order, the user as the main user can generate corresponding user information according to the preset data structure. Among them, 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, the main user himself. In other words, the rights and interests of the policy can only be enjoyed by the main user. Wherein, the preset material structure at least specifies that the user profile has an asset field, and the asset field of the master user profile indicates that the asset owner includes the master user.
In this embodiment, user A (primary user) can also share the insured rights with associated users (user B). specific:
The service party can create a health account for user A. For a certain insurance order of the user, the service party will create the main user profile corresponding to the insurance order under the health account. Among them, based on the provisions of the preset data structure, the data creator field of the master user data indicates user A, and the asset field indicates user A. The insurance order can be used as a health asset to be bound to the health account of the user A.
Optionally, you can create a health account group view for user A, that is, after user A logs in to the server, the data can be obtained through this view and displayed to the user for review. Optionally, user A can log in with his own UID and ID number Server and access your own health account.
Since user A shares the insured amount with user B, if user B does not have a health account on the server side, he can create a health account for user B. If user B has already 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. Correspondingly, a user profile corresponding to the insurance order shared by user A is created under the health account of user B. In the user profile of user B, the asset field indicates that the asset owner includes the user B and is related to the insurance order of the main user. Binding. Therefore, user B's health account has A's insurance policy. When user B accesses the health account through his ID card or UID, he can check that the insurance policy under the account was shared by A with himself through the user information , And the owner of the asset is himself.
It can be seen from the above embodiment that through the above user data, the asset information between the main user and the associated user will not experience information loss. In addition, if user A has his own insurance order, he can have user information in which he is the creator and the owner of the asset. In some business scenarios, user A may have multiple business orders and pay attention to his own insurance policy. For example, user B will have an insurance policy. If user B only needs to pay attention to his own account, he can filter data through the relationship between the data creator and the asset owner. , Solve the problem of business isolation from different business perspectives.
In the scenario of policy sharing, the type of health asset is an insurance policy. In other scenarios, different types can also be expanded, such as other types such as physical examination reports or fitness monitoring reports, so as to realize the sharing of other types of assets.
For the service provider, the above solution can also solve the problem of authority isolation, obtain login user information, search for login user information through login user information, obtain the asset field and data creator field in the login user information, and then determine the The operation authority of the login user on the business order associated with the login user profile. As an example, after a user logs in, the UID of the currently logged-in user can be obtained. The logged-in user corresponds to user information. The asset field in the user information indicates the UID of the asset owner, and the data creator field indicates the UID of the data creator. These three UID relationship to determine the user's authority. For example, the login UID is the same as the asset owner UID, but is different from the data creator UID, indicating that the corresponding asset under this account is shared by others, and you cannot surrender the insurance policy asset associated with the user data. Therefore, the problem of authority isolation is also solved.
In addition to insurance business scenarios, the business processing solutions in 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, etc., as an example of business orders involving purchasing members , You can share the purchased membership to other associated users, etc.
As shown in FIG. 2, it is another service processing method according to an exemplary embodiment, which includes the following steps:
In step 202, for the business order of the master user, a master user profile bound to the business order is created according to a preset profile structure, wherein the preset profile structure at least specifies that the user profile has an asset field, and the master profile profile The asset field of indicates that the asset owner includes the master user;
In step 204, if it is determined through the service order that the main user shares assets with the associated users, the associated user data bound to the service order is created according to the preset data structure, wherein the data of the associated user data The asset field indicates that the asset owner includes the associated user.
Optionally, the preset profile structure further specifies a profile creator field, the profile creator field of the master user profile indicates the master user, and the profile creator field of the associated user profile indicates the master user.
Optionally, the method further includes:
Based on the user profile of the user, creating a database view corresponding to the user, the database view corresponding to a query sentence for querying and displaying data using the user profile;
If a user-initiated data query request carrying a user identification is received, the database view corresponding to the user is searched through the user identification, and the display data is obtained by using the query sentence in the database view and returned.
Optionally, 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, and the search is performed through the user identifier The database view corresponding to the user includes:
Search for the database view corresponding to the user and business scenario through the user identification and request trigger entry information.
Optionally, the display data includes one or more of the following: the asset owner information, the business order information, or the data creator information.
Optionally, the method further includes:
Obtain log-in user information, search log-in user information through log-in user information, obtain the asset field and data creator field in the log-in user profile, and then determine the operation authority of the log-in user on the business order associated with the log-in user profile.
Corresponding to the foregoing embodiment of the service processing method, this specification also provides an embodiment of the service processing apparatus and the equipment applied thereto.
The embodiments of the business processing device in this specification can be applied to computer equipment, such as servers or terminal equipment. The device embodiments can be implemented through software, or through hardware or a combination of software and hardware. Take software implementation as an example. As a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the internal memory through the processor where the file is processed. From the perspective of hardware, as shown in FIG. 3, it is a hardware structure diagram of the computer equipment where the business processing device of the embodiment of this specification is located, except for the processor 310, internal memory 330, and network interface 320 shown in FIG. In addition to the non-volatile storage 340, the server or electronic device where the device 331 is located in the embodiment may also include other hardware generally according to the actual function of the computer device, which will not be repeated here.
As shown in FIG. 4, FIG. 4 is a block diagram of a service processing apparatus according to an exemplary embodiment of this specification, and the apparatus includes:
The master user profile creation module 41 is used for: for the master user’s business order, create master user profile bound to the business order according to a preset profile structure, wherein the preset profile structure at least specifies that the user profile has an asset field , The asset field of the master user profile indicates that the asset owner includes the master user;
The associated user data creation module 42 is configured to: if it is determined through the business order that the main user shares assets with the associated users, create the associated user data bound to the business order according to the preset data structure, wherein: The asset field of the associated user profile indicates that the asset owner includes the associated user.
Optionally, the preset profile structure further specifies a profile creator field, the profile creator field of the master user profile indicates the master user, and the profile creator field of the associated user profile indicates the master user.
Optionally, the device further includes a database view creation module, which is used to create a database view corresponding to the user based on the user profile of the user, and the database view corresponds to a query for querying and displaying data using the user profile. Statement
The data retrieval module is used for: if a data retrieval request carrying a user identification is received from a user, the database view corresponding to the user is searched through the user identification, and the query statement in the database view is used to obtain the display Return after the information.
Optionally, 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, and the data query module further Used for:
Search for the database view corresponding to the user and business scenario through the user identification and request trigger entry information.
Optionally, the display data includes one or more of the following: the asset owner information, the business order information, or the data creator information.
Optionally, the device further includes a permission determination module for:
Obtain log-in user information, search log-in user information through log-in user information, obtain the asset field and data creator field in the log-in user profile, and then determine the operation authority of the log-in user on the business order associated with the log-in user profile.
Correspondingly, this specification also provides a computer device, including a storage, a processor, and a computer program stored on the storage and capable of running on the processor, wherein the processor implements the following method when the program is executed:
For the business order of the master user, the master user profile bound to the business order is created according to a preset profile structure, wherein the preset profile structure at least specifies that the user profile has an asset field, and the asset field of the master user profile indicates an asset The owner includes the main user;
If it is determined through the business order that the main user shares the asset with the associated user, the associated user profile bound to the business order is created according to the preset data structure, wherein the asset field of the associated user profile indicates that the asset is owned The person includes the associated user.
For the implementation process of the functions and roles of each module in the above-mentioned service processing device, please refer to the implementation process of the corresponding steps in the above-mentioned service processing method, which will not be repeated here.
As for the device embodiment, since it basically corresponds to the method embodiment, the relevant part can refer to the part of the description of the method embodiment. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components displayed as modules may or may not be physical modules. It can 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 purpose of the solution in this specification. Those of ordinary skill in the art can understand and implement it without making progressive work.
The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the attached patent application. In some cases, the actions or steps described in the scope of the patent application may be performed in a different order from the embodiment and still achieve desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown in order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Those skilled in the art will easily think of other embodiments of this specification after considering the specification and practicing the invention applied here. This specification is intended to cover any modification, use, or adaptive change of this specification. These modifications, uses or adaptive changes follow the general principles of this specification and include common knowledge or conventional technical means in the technical field not applied for in this specification. . The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the specification are pointed out by the following claims.
It should be understood that this specification is not limited to the precise structure described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of this specification is only limited by the attached claims.
The above descriptions are only the preferred embodiments of this specification, and are not intended to limit this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in this specification Within the scope of protection.
