CN107180030B - Method and device for generating relational data on network - Google Patents
Method and device for generating relational data on network Download PDFInfo
- Publication number
- CN107180030B CN107180030B CN201610133030.9A CN201610133030A CN107180030B CN 107180030 B CN107180030 B CN 107180030B CN 201610133030 A CN201610133030 A CN 201610133030A CN 107180030 B CN107180030 B CN 107180030B
- Authority
- CN
- China
- Prior art keywords
- service
- data
- node
- service node
- users
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
-
- 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]
Abstract
The application discloses a method and a device for generating relational data on a network, which are used for solving the problem that in the prior art, the actual operator of a current service node is difficult to know, so that risks are brought to service interaction of the current service node. The method comprises the following steps: acquiring service data of each designated service node on a network, wherein the service data is generated after service interaction is carried out between users through each service node; determining service interaction conditions carried out between users through the service nodes according to the acquired service data, wherein the service interaction conditions comprise specific contents of services and/or transfer conditions of service resources related to the services; presume the responsibility of the user related to each service node in the service nodes to the service node according to the determined service interaction condition; and generating the relationship data of each service node and each user according to the presumed responsibility.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method and an apparatus for generating relational data on a network.
Background
With the rapid development of the internet and computer technologies, many services can be performed through service nodes on the internet. For different types of services, the types of the corresponding service nodes may also be different. For example, for an e-commerce service, the corresponding service node may be an online store, for a network storage service, the corresponding service node may be a data storage node, for a financial service, the corresponding service node may be an online bank, and so on.
The users can perform service interaction through the service node, and correspondingly, the service node can generate and store corresponding service data so as to be convenient for the users to inquire and use. A user may refer to a customer obtaining service from a service node, an actual operator providing service to the customer through the service node, and so on.
In practical application, a customer can freely select a service node for providing service for the customer, and at this time, from the safety perspective, the customer may need to know the actual operator of the current service node; similarly, not only the customer, but also possibly other service nodes or service systems may need to know the actual operator of the current service node to serve the current service node.
However, in the prior art, due to the problems of the hanging name, the false information, and the like, it is difficult for a client, other service nodes, or a service system to know the actual operator of the current service node, and thus, a risk is brought to service interaction with the current service node.
Disclosure of Invention
The embodiment of the application provides a method and a device for generating relational data on a network, which are used for solving the problem that in the prior art, due to the existence of the problems of name hanging, false information and the like, a client, other service nodes or a service system cannot easily know the actual operator of a current service node, so that risks are brought to service interaction with the current service node.
The method for generating the relational data on the network provided by the embodiment of the application comprises the following steps:
acquiring service data of each designated service node on a network, wherein the service data is generated after service interaction is carried out between users through each service node;
determining service interaction conditions carried out between users through the service nodes according to the acquired service data, wherein the service interaction conditions comprise specific contents of services and/or transfer conditions of service resources related to the services;
presume the responsibility of the user related to each service node in the service nodes to the service node according to the determined service interaction condition;
and generating the relationship data of each service node and each user according to the presumed responsibility.
An embodiment of the present application provides an apparatus for generating relational data on a network, including:
the system comprises an acquisition module, a service node selection module and a service node selection module, wherein the acquisition module is used for acquiring service data of each service node appointed on a network, and the service data is generated after service interaction is carried out between users through each service node;
a determining module, configured to determine, according to the service data acquired by the acquiring module, a service interaction situation performed between users through the service nodes, where the service interaction situation includes specific content of a service and/or a transfer situation of a service resource related to the service;
the presumption module is used for presuming the responsibility of the user related to each service node in each service node to the service node according to the service interaction condition determined by the determination module;
and the generating module is used for generating the relationship data between each service node and each user according to the responsibility presumed by the presumption module.
According to the embodiment of the application, through at least one technical scheme, the responsibility of the user related to the current service node can be presumed, and the corresponding relationship data is generated, so that the embodiment of the application is helpful for helping the client, other service nodes or a service system to further know the current service node according to the generated relationship data, such as the actual operator of the current service node, and the like, thereby solving the problems in the prior art.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a process of a method for generating relationship data on a network according to an embodiment of the present application;
FIG. 2 is a flow of funds related to a portion of an online store according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram illustrating user responsibility estimation based on business data of a online store according to an embodiment of the present application;
fig. 4 is a schematic diagram of query on generated relational data in practical application according to the embodiment of the present application;
fig. 5 is a schematic diagram of access to generated relationship data in practical application according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a relationship data generation apparatus on a network according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the background art, due to the problems of hanging names and false information, it is difficult for clients, other service nodes or service systems (a service system may refer to a system of a service platform where a service node is located, or may refer to a system of another service platform) to know about the actual operator of the current service node, in order to solve the problem, the scheme of the application considers that the service data of the current service node and other service nodes are analyzed, based on the specific content of the service which can be reflected by the service data and the transfer condition of the service resource related to the service, relationship data of each service node and each user is generated by mining, the relationship data can reflect more real information of the service node and the user, rather than information about the service node and user (typically self-disclosed by the service node and user) as acquired in the prior art, can be spurious.
Moreover, a special character attribute management system can be established for the user and/or a special service node attribute management system can be established for the service node based on the mined relationship data, wherein the data in the character attribute management system and the data in the service node attribute management system can be correlated. Therefore, the user, the service node or other service systems can acquire certain information which is not disclosed by any user or service node through the established systems, and the fair and transparent service interaction is facilitated.
The following describes the scheme of the present application.
Fig. 1 is a process of a method for generating relationship data on a network according to an embodiment of the present application, where an execution subject of the process may be a terminal or a server. The terminal includes but is not limited to: personal computers, cell phones, tablet computers, smart watches, vehicle-mounted mobile stations, and the like; the server includes but is not limited to: personal computers, large and medium sized computers, computer clusters, etc. as servers. The execution subject is not limited to the present application, and for convenience of description, the execution subject is exemplified as a server in the embodiments of the present application.
S101: acquiring service data of each designated service node on a network, wherein the service data is generated after service interaction is carried out between users through each service node.
In the embodiments of the present application, the specific scope of the network is not limited. In general, different types of service nodes may be managed by different types of service platforms, each service platform may manage multiple service nodes, and provide a certain type of service through the multiple service nodes. For example, the online shopping platform can manage a plurality of online shops, and can provide e-commerce business services such as selling commodities and purchasing commodities through the online shops; the network storage platform can manage a plurality of data storage nodes (which can be logic nodes or physical nodes), and network storage service such as cloud storage and cloud backup can be provided through the data storage nodes.
Because different service platforms are independent of each other and are generally provided by different service providers, the scheme to be implemented may need to directly interact with the service providers, and therefore, in practical application, the scheme of the application may be implemented by taking the service platform as a unit, which is not only beneficial to improving the implementation efficiency, but also can prevent redundant data from being excessive.
In the embodiment of the application, users can perform service interaction through service nodes, and during the service interaction, the responsibilities (or roles) of different users are different. Some users belong to the service node side and have the management authority to the service node, and other users are opposite to the service node side and can initiate service requests to the service node but do not have the management authority to the service node. The responsibility of the user can be further subdivided for the service nodes of different service platforms based on these two categories. For example, for a web store, the user's duties may include: a certifier (which can be a user applying for registering the online shop), an actual operator, a partner, an employee and the like; for a data storage node, the responsibilities of the user may include: database administrators, developers, storage device maintainers, and the like.
The service node may be used as a bridge for service interaction between users, and the service may be processed directly by the service node, or may be processed by other software or hardware modules besides the service node, which is not limited in this application. For convenience of description, for any service node, the service data generated by service interaction through the service node is referred to as: traffic data for the traffic node.
S102: and determining the service interaction condition between the users through the service nodes according to the acquired service data, wherein the service interaction condition comprises the specific content of the service and/or the transfer condition of the service resources related to the service.
In the embodiment of the present application, the service resource may be a resource, such as funds, goods, computing resources, storage resources, and the like, transferred between different users and/or different service nodes and between users and service nodes due to service interaction. In general, each service may involve at least one service node and two or more users, and each service may result in at least one transfer of a certain amount of service resources.
For example, for a business node such as a web store, users involved in a business of the web store may be a buyer (e.g., a customer) and a seller (e.g., a clerk, a physical proprietor, etc. of the web store), and a business of the web store may cause a product sold in the business to be transferred from the seller to the seller via the web store, and cause funds for the buyer to purchase the product to be transferred from the buyer to the buyer via the web store.
In this embodiment, the service data acquired in step S102 may include service data generated by service interaction of multiple services, and then the service interaction condition between multiple users may be determined according to the acquired service data. Accordingly, the transfer situation of the past service resources between each user and each service node, such as information of transfer direction, transfer quantity and the like, can be determined.
The service interaction condition may include, in addition to the specific content of the service and/or the transfer condition of the service resource related to the service, a message in the service interaction process, a service interaction result, and other contents.
In the embodiment of the present application, generally, the specific content of the service is recorded in the service data, and therefore, the specific content can be directly obtained from the service data, while the transfer condition of the service resource may need to be indirectly obtained according to the service data or according to the specific content of the service.
S103: and according to the determined service interaction condition, presuming the responsibility of the user related to each service node in the service nodes to the service node.
In the embodiment of the present application, generally, according to a service interaction situation, it may be determined whether a user involved in a service is located on a service node side involved in the service or on an opposite side of the service node side. However, in order to solve the problems in the background art, it is necessary to know the relationship between the user and the service node more deeply.
The service interaction condition can reflect the behavior and information related to the user and the service, and the result caused by the service, such as the business behavior, the consumption behavior, the user personal information, the user social information, the fund flow direction (i.e. the transfer condition of the service resource, fund) and the like, so that the relationship between the user and the service node can be better understood by analyzing and mining the service interaction condition. The following respectively exemplifies the service interaction situation as the specific content of the service and the transfer situation of the service resource related to the service.
For some services, the responsibility of the user involved in the service node for the service node (simply referred to as user responsibility) can be inferred through the specific content of the service. For example, assuming that many businesses in one online store are commodity transactions of a certain commodity with a large volume lower than the market price, and a buyer of the commodity transaction belongs to another online store, and the other online store sells the commodity at the market price, the buyer can be presumed to be a buyer (and possibly an actual operator) of the other online store.
The user responsibility can be presumed not only based on the concrete content of the business, but also based on the transfer condition of the business resources related to the business, and the latter scheme has wider applicability. For example, assuming that many services cause the transfer of the service resource to a service node, and the transaction is collected to a user at the service node side, for example, for the fund, the fund may be collected to a fund account (such as a bank account or a third party payment account) of the user, for the commodity, the fund may be collected to a real estate held by the user, such as a residence of the user, a company of the user, and the like, and assuming that the service resource of the user is transferred to one or more other service nodes, it may be assumed that the user is an actual operator of the service node, because: as can be seen from the transition of the service resource, the user is the main receiver and the received dominator of the service resource related to the service node, and generally, the actual operator of the service node has such a large processing right. Further, assuming that the business resource is funded, and that funding is transferred from the user to a plurality of other users on the business node side periodically (e.g., once a month) (the amount of transfer is relatively fixed), it can be presumed that the user is funded to the plurality of other users, and thus, the plurality of other users may be employees of the business node.
It should be noted that the actual operator and employee in the above two examples are only examples of the "responsibility for the service node" described in this application, and the responsibility may further include: authenticator, partner, agent, upstream and downstream, splicer, etc. Moreover, the types and names of the above responsibilities may vary for different types of services, and the application does not limit the types and names of the responsibilities. For example, for one type of service, the user registering the service node may be referred to as an authenticator, while for another type of service, the user registering the service node may be referred to as a registrar, and so on.
In the embodiment of the application, according to the service interaction condition, the personal information, the social information, the service node information and the like of the user can be further presumed.
S104: and generating the relationship data of each service node and each user according to the presumed responsibility.
In the embodiment of the present application, the expression form and data format of the relational data are not limited, and the meaning of the relational data is mainly described here. The relationship data of each service node and each user may include three types:
the first type, relationship data between the service node and the user. For example, the meaning of a first type of relational data may be: user a is the actual operator of service node a, user B is an employee of service node a, and so on.
And the second type is the relationship data among users. For example, the meaning of a second type of relational data may be: user C is a partner of user D, user E is a subscriber to user D (e.g., a web shop is originally operated by user D, and later user D transfers the web shop to user E), and so on.
And the third type is relationship data among all service nodes. For example, the meaning of some third type of relational data may be: service node a is an upstream node of service node b, service node c is a downstream node of service node b, the actual operators of service node d and service node e are the same, and so on.
By the method, the responsibility of the user related to the current service node can be inferred, and corresponding relationship data is generated, so that the method is helpful for helping a client, other service nodes or a service system to further know the current service node according to the generated relationship data, such as the actual operator of the current service node, and the like, and the problems in the prior art are solved.
In practical applications, based on the above method, the embodiments of the present application also provide some specific embodiments of the above method and the extension of the above method, and for convenience of description, the specific embodiments and the extension are mainly described below by taking the service platform as an online shopping platform and the service node as an online store as an example.
In this embodiment of the application, for step S102, determining, according to the obtained service data, a service interaction condition performed between the users through the service nodes may specifically include: determining each service occurring on each service node in the service nodes and a user related to each service according to the acquired service data; and determining the specific content of each service and/or the transfer condition of the service resources related to each service between each service node and each user according to each service and the user related to each service, wherein the transfer condition is used as the service interaction condition between the determined users through each service node.
For example, the business data of the online shop may be a transaction record of each transaction that occurred in the online shop. The transaction record may generally include, but is not limited to, information: transaction number, transaction time, information on the goods being transacted, transaction amount, user account numbers of both or more parties to the transaction, etc.; the user account itself may be used as a fund account for collecting or paying money, or may be a fund account bound to the user account for collecting or paying money.
In practical application, in order to ensure the fund security of a user, the fund account of the user is bound with the real identity of the user (represented by the identity card number or the biometric information of the user, and the like), so that the transfer condition of the fund between the fund accounts of the users (which can be called as fund flow direction) can relatively truly reflect the behavior of the user on the service platform.
Further, according to the descriptions of steps S102 and S103, the user responsibility can be inferred according to the specific content of the service or the transfer condition of the service resource related to the service, which has been described in the foregoing by way of example; and the user responsibility can also be conjectured according to the specific content of the service and the transfer condition of the service resource involved in the service. In practical applications, the latter scheme can be generally adopted in order to improve the accuracy of the estimation.
Specifically, for step S103, according to the determined service interaction condition, presuming the responsibility of the user related to each service node in the service nodes for the service node, may include: according to the determined service interaction condition, aiming at each service node in each service node, executing the following steps: determining each service occurring at the service node and causing the transfer of service resources to the service node; determining users related to the service node according to the determined services, and determining the condition that the service resources caused by the services are transferred to the service node and then transferred to the users; and according to the determined services and the situations, presuming the responsibility of the user related to the service node for the service node.
For example, FIG. 2 illustrates the flow of portions of funds involved in a particular online store.
The flow of funds into and out of the account number can involve a plurality of fund account numbers, and the purpose of the fund account number and the responsibility of a user of the fund account number on the service node can be presumed through the fund flow. The fund obtained by sale is often transferred to the own fund account of the actual operator, and when the funds of a plurality of fund sources are collected into one fund account through the service node and the action is frequently carried out, the possibility that the owner of the fund account is the actual operator of the service node is high. Further, when funds are diverted from the funding account to multiple other funding accounts, the owners of the funding accounts may be associated and relationships between the users may be located.
In fig. 2, the capital accounts primarily used by the actual operator are the collection points and the diversion points of the capital. The fund accounts 1 and 2 … … are collected to the fund account mainly used by the actual operator, and it can be presumed that all the persons in the fund accounts 1 and 2 … … are clients of the online shop operated by the actual operator, and the actual operator can distribute part of the collected fund to other fund accounts and can presume the use of other fund accounts according to the services related to other fund. For ease of understanding, the use of other fund accounts that have been presumed is shown in FIG. 2, and it will be seen that other fund accounts may include: a funding account for incoming goods, a funding account for sales, a funding account for shopping, a funding account for management, and the like. The owner of the other fund account and the actual operator can be the same user or different users, and when the owner of the other fund account is different, the owner of the other fund account can be responsible for the online shop.
Fig. 3 is a diagram showing a process of inferring user responsibility based on business data of a cyber shop. As already mentioned above, the business data of the online store may be a transaction record, and more specifically, the data contained in the transaction record includes, but is not limited to: business data, transaction data, payment data, customer information, and the like. The roles of each user involved in the online store that can be inferred include, but are not limited to: actual operators, partners, employees, operations on behalf of, upstream and downstream, splicers, and the like.
It should be noted that the above-mentioned responsibilities may overlap with each other. For example, when there are a plurality of actual operators in a certain online store, it may be assumed that the plurality of actual operators are in a partner relationship with each other, or when there is only one actual operator in a certain online store, but the actual operator often shares interests with other users, it may be assumed that other users are in a partner relationship with the actual operator.
In the embodiment of the present application, an association relationship may also exist between different service nodes (such an association relationship may be hidden), for example, different service nodes may be operated by the same actual operator, and the embodiment of the present application also provides a scheme for mining the relationship between each service node and each other.
Specifically, based on the service data of each service node, similarity comparison and cross comparison can be performed on the services occurring on each service node; according to the similarity comparison result and the cross comparison result, the correlation between the service nodes is presumed; and generating the relationship data among the service nodes according to the association.
For example, when a user or a team operates a plurality of online stores, based on business data of the online stores, it is possible to find: these online stores have similarities and intersections in terms of sources of goods, decoration of stores, marketing operation, business work, receipt, shipment, customer maintenance, and the like, and by integrating and matching these similar or intersecting behavior data, the correlations between the online stores, the correlations between users (such as actual operators, certifiers, and the like) involved in the online stores, and the like can be found.
In the embodiment of the application, based on the service data of the service node, the information of each user and the relationship between each user can be mined.
Specifically, the business participated by the user can reflect the business behavior, consumption behavior and the like of the user, and the behaviors can directly or indirectly reflect the information of the user. Therefore, according to each service of the service node and the user involved in each service, the personal information and the social information of each user can be obtained, and the association between each user can be presumed; and generating the relationship data of the users according to the acquired personal information and the presumed association.
The information of the user includes but is not limited to: name, age, gender, identification number, mobile phone number, household registration, frequent residence, spouse, family, network management, life and study, interpersonal relationship, etc.; the relationship between users includes but is not limited to: relationships in the context of consanguinity (e.g., relatives), relationships in the context of business (e.g., partners), and relationships in the context of life and study (e.g., friends, classmates).
In addition, in practical application, for the online shopping platform, besides the buying and selling functions, a plurality of tools and services are derived, in the using process of the tools and services, the information of the user can be recorded, and the information recorded in different scenes and different times can be used for more comprehensively and truly describing the user and assisting in judging the change of the user.
In the embodiment of the application, the relationship data generated by the scheme of the application can be provided for users, service nodes, service systems and the like. The method for providing the relationship data is not limited in the present application, and generally, a person attribute management system, a service node attribute management system, and a person and service node attribute management system including the relationship data may be established, and a user may query and acquire the required relationship data in the established systems.
Fig. 4 shows a schematic diagram of a query on the generated relational data in practical application.
In fig. 4, the query may be performed based on the user or based on the service node. When a query is made based on a user, information of the user, such as an identity card number, can be used as a query key word, as shown in the left sub-graph in fig. 4, the user "zhang bi" can be queried according to the identity card number "141723 xxxxxxxx 1001", and relationship data of zhang bi, including a present partner of zhang bi, a previous partner, a spouse, a father, a mother, a sister and the like; when the query is made based on the service node, information of the service node such as the online store name can be used as a query key, and as shown in the right sub-graph in fig. 4, the online store "store X" can be queried according to the online store name "store X", and relationship data of the store X including an actual operator, an authenticator, a partner, an employee, a downstream store Y, a proxy operation, and the like of the store X.
In the embodiment of the present application, in order to facilitate the business system to use the generated relationship data, the relationship data may be accessed to the business system through the above-mentioned person attribute management system and other systems.
Specifically, after the relational data is generated by executing the scheme of the present application, the generated relational data may be accessed to a specified business system, so that the business system queries the required data in the relational data; and correcting and/or supplementing the relation data according to a feedback result of the service system after the queried data is used.
Fig. 5 shows a schematic diagram of access to generated relationship data in practical application.
In fig. 5, the system in which the character attribute management system is connected to the online shopping platform, "basic information of online store", "basic information of person", "contact information", and "management information" may be modules in the system of the online shopping platform. Furthermore, the relationship data contained in the person attribute management system can be displayed in the modules, so that the information integrity and accuracy of the system of the online shopping platform are improved. In the using process, the information input by the user can be reflowed to the character attribute management system, the result which is not matched with the actual situation is processed again and output, and the operation is repeated in such a way, so that the integrity and the accuracy of the relation data in the task attribute management system can be improved.
It should be noted that, in practical applications, in order to prevent misuse of the privacy information of the user and the service node, the usage right of the generated relationship data may be limited, and the usage process of the generated relationship data may be supervised.
The scheme of the application can be used in many scenes. For example, in the network loan business related to the network shopping platform, in the business links of loan approval, post-loan supervision, collection with the loan, and the like, through the scheme of the application, the actual operator of the online shop (generally, the actual operator is the actual user of the loan) can be known, the actual operating condition of the actual operator on the network shopping platform is mastered, the social activity condition of the borrower is known, and the changes of the conditions are known in time, so that the network loan business can be reasonably credited, timely monitored, effectively collected, and business risks caused by reasons of information asymmetry, information loss, and the like are avoided.
Based on the same idea, the method for generating relational data on a network provided in the embodiment of the present application further provides a corresponding apparatus for generating relational data on a network, as shown in fig. 6.
Fig. 6 is a schematic structural diagram of a relationship data generation apparatus on a network according to an embodiment of the present application, which specifically includes:
an obtaining module 601, configured to obtain service data of each service node specified on a network, where the service data is generated after service interaction is performed between users through each service node;
a determining module 602, configured to determine, according to the service data acquired by the acquiring module 601, a service interaction situation performed between users through each service node, where the service interaction situation includes specific content of a service and/or a transfer situation of a service resource related to the service;
a presumption module 603, configured to presume, according to the service interaction condition determined by the determination module 602, a role of a user related to each service node in the service nodes for the service node;
a generating module 604, configured to generate relationship data between each service node and each user according to the responsibility presumed by the presumption module 603.
Through the device, the responsibility of the user related to the current service node can be inferred, and corresponding relationship data is generated, so that the device is helpful for helping a client, other service nodes or a service system to further know the current service node according to the generated relationship data, such as the actual operator of the current service node, and the like, and the problems in the prior art are solved.
Optionally, the determining module 602 is specifically configured to: determining each service occurring on each service node of the service nodes and a user related to each service according to the service data acquired by the acquisition module 601; and determining the specific content of each service and/or the transfer condition of the service resources related to each service between each service node and each user according to each service and the user related to each service, wherein the transfer condition is used as the service interaction condition between the determined users through each service node.
Optionally, the inference module 603 is specifically configured to, according to the service interaction condition determined by the determination module 602, execute the following steps for each service node in the service nodes: determining each service occurring at the service node and causing the transfer of service resources to the service node; determining users related to the service node according to the determined services, and determining the condition that the service resources caused by the services are transferred to the service node and then transferred to the users; and according to the determined services and the situations, presuming the responsibility of the user related to the service node for the service node.
Optionally, the apparatus further comprises:
a node relation module 605, configured to perform similarity comparison and cross comparison on the services occurring on the service nodes; according to the similarity comparison result and the cross comparison result, the correlation between the service nodes is presumed; and generating the relationship data among the service nodes according to the association.
Optionally, the apparatus further comprises:
a user relationship module 606, configured to obtain personal information and social information of each user according to each service and the user related to each service, and infer an association between the users; and generating the relationship data of the users according to the acquired personal information and the presumed association.
Optionally, the apparatus further comprises:
a data access module 607, configured to access the generated relationship data to a specified business system, so that the business system queries required data in the relationship data; and correcting and/or supplementing the relation data according to a feedback result of the service system after the queried data is used.
Optionally, the business node comprises an online store, the business resource comprises funds, and the responsibility comprises at least an actual operator
The apparatus shown in fig. 6 may be located in a terminal or a server.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (14)
1. A method for generating relational data on a network, comprising:
acquiring service data of each designated service node on a network, wherein the service nodes are used for performing service interaction, and the service data is generated after service interaction is performed between users through the service nodes;
determining service interaction conditions carried out between users through the service nodes according to the acquired service data, wherein the service interaction conditions comprise specific contents of services and/or transfer conditions of service resources related to the services;
presuming the responsibility of a user related to each service node in the service nodes to the service node according to the determined service interaction condition, wherein the responsibility comprises a seller and a buyer;
generating relationship data between each service node and each user according to the presumed responsibility;
the relation data between each service node and each user comprises the relation data between the service nodes and the users, and the relation data between the service nodes and the users comprises actual operators of which the users are the service nodes or employees of which the users are the service nodes; or the relationship data between each service node and each user comprises relationship data between each service node, and the relationship data between each service node comprises actual operators of any two service nodes.
2. The method of claim 1, wherein determining the service interaction between the users through the service nodes according to the obtained service data specifically comprises:
determining each service occurring on each service node in the service nodes and a user related to each service according to the acquired service data;
and determining the specific content of each service and/or the transfer condition of the service resources related to each service between each service node and each user according to each service and the user related to each service, wherein the transfer condition is used as the service interaction condition between the determined users through each service node.
3. The method of claim 2, wherein inferring responsibilities of users involved in each of the service nodes to the service node based on the determined service interaction conditions comprises:
according to the determined service interaction condition, aiming at each service node in each service node, executing the following steps:
determining each service occurring at the service node and causing the transfer of service resources to the service node;
determining users related to the service node according to the determined services, and determining the condition that the service resources caused by the services are transferred to the service node and then transferred to the users;
and according to the determined services and the situations, presuming the responsibility of the user related to the service node for the service node.
4. The method of claim 2, wherein the method further comprises:
carrying out similarity comparison and cross comparison on the services occurring on each service node;
according to the similarity comparison result and the cross comparison result, the correlation between the service nodes is presumed;
and generating the relationship data among the service nodes according to the association.
5. The method of claim 2, wherein the method further comprises:
according to each service and the users involved in each service, acquiring personal information and social information of each user, and presuming the association between each user;
and generating the relationship data of the users according to the acquired personal information and the presumed association.
6. The method of any one of claims 1 to 5, further comprising:
accessing the generated relational data into a designated service system so that the service system can inquire required data in the relational data;
and correcting and/or supplementing the relation data according to a feedback result of the service system after the queried data is used.
7. A method according to any of claims 1 to 5, wherein the business node comprises a store on the Internet, the business resource comprises funds, and the obligations comprise at least the actual operator.
8. An apparatus for generating relational data on a network, comprising:
the system comprises an acquisition module, a service node selection module and a service data processing module, wherein the acquisition module is used for acquiring service data of each designated service node on a network, the service nodes are used for carrying out service interaction, and the service data is generated after service interaction is carried out between users through each service node;
a determining module, configured to determine, according to the service data acquired by the acquiring module, a service interaction situation performed between users through the service nodes, where the service interaction situation includes specific content of a service and/or a transfer situation of a service resource related to the service;
the presumption module is used for presuming the responsibility of the user related to each service node in the service nodes to the service node according to the service interaction condition determined by the determination module, wherein the responsibility comprises a seller and a buyer;
the generating module is used for generating the relationship data of each service node and each user according to the role presumed by the presumption module; the relation data between each service node and each user comprises the relation data between the service nodes and the users, and the relation data between the service nodes and the users comprises actual operators of which the users are the service nodes or employees of which the users are the service nodes; or the relationship data between each service node and each user comprises relationship data between each service node, and the relationship data between each service node comprises actual operators of any two service nodes.
9. The apparatus of claim 8, wherein the determination module is specifically configured to: determining each service occurring on each service node in the service nodes and a user related to each service according to the service data acquired by the acquisition module; and determining the specific content of each service and/or the transfer condition of the service resources related to each service between each service node and each user according to each service and the user related to each service, wherein the transfer condition is used as the service interaction condition between the determined users through each service node.
10. The apparatus according to claim 9, wherein the inference module is specifically configured to, for each of the service nodes, perform the following steps according to the service interaction condition determined by the determination module: determining each service occurring at the service node and causing the transfer of service resources to the service node; determining users related to the service node according to the determined services, and determining the condition that the service resources caused by the services are transferred to the service node and then transferred to the users; and according to the determined services and the situations, presuming the responsibility of the user related to the service node for the service node.
11. The apparatus of claim 9, wherein the apparatus further comprises:
the node relation module is used for carrying out similarity comparison and cross comparison on the services generated on the service nodes; according to the similarity comparison result and the cross comparison result, the correlation between the service nodes is presumed; and generating the relationship data among the service nodes according to the association.
12. The apparatus of claim 9, wherein the apparatus further comprises:
the user relation module is used for acquiring personal information and social information of each user according to each service and the users related to each service, and presuming the association between the users; and generating the relationship data of the users according to the acquired personal information and the presumed association.
13. The apparatus of any of claims 8 to 12, further comprising:
the data access module is used for accessing the generated relational data into a specified business system so as to facilitate the business system to inquire required data in the relational data; and correcting and/or supplementing the relation data according to a feedback result of the service system after the queried data is used.
14. An arrangement according to any of claims 8 to 12, wherein the service node comprises a store on the internet, the service resource comprises funds, and the responsibility comprises at least the actual operator.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610133030.9A CN107180030B (en) | 2016-03-09 | 2016-03-09 | Method and device for generating relational data on network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610133030.9A CN107180030B (en) | 2016-03-09 | 2016-03-09 | Method and device for generating relational data on network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107180030A CN107180030A (en) | 2017-09-19 |
| CN107180030B true CN107180030B (en) | 2020-11-17 |
Family
ID=59829692
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610133030.9A Active CN107180030B (en) | 2016-03-09 | 2016-03-09 | Method and device for generating relational data on network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107180030B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109784013A (en) * | 2017-11-14 | 2019-05-21 | 阿里巴巴集团控股有限公司 | A kind of method, apparatus and equipment of information identification |
| CN108122163A (en) * | 2017-11-14 | 2018-06-05 | 阿里巴巴集团控股有限公司 | Risk monitoring and control method, apparatus and equipment based on internet credit |
| CN111125269B (en) * | 2019-12-31 | 2023-05-02 | 腾讯科技（深圳）有限公司 | Data management method, blood relationship display method and related device |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101308493B (en) * | 2007-05-18 | 2010-12-08 | 亿览在线网络技术（北京）有限公司 | Entity relation exhibition method and system |
| CN101425065B (en) * | 2007-10-31 | 2013-01-09 | 日电（中国）有限公司 | Entity relation excavating method and device |
| CN102339445A (en) * | 2010-07-23 | 2012-02-01 | 阿里巴巴集团控股有限公司 | Method and system for evaluating credibility of network trade user |
| CN103164416B (en) * | 2011-12-12 | 2016-08-03 | 阿里巴巴集团控股有限公司 | The recognition methods of a kind of customer relationship and equipment |
| US20130332450A1 (en) * | 2012-06-11 | 2013-12-12 | International Business Machines Corporation | System and Method for Automatically Detecting and Interactively Displaying Information About Entities, Activities, and Events from Multiple-Modality Natural Language Sources |
| CN110009372B (en) * | 2012-08-03 | 2023-08-18 | 创新先进技术有限公司 | User risk identification method and device |
| CN103854193B (en) * | 2012-12-06 | 2017-10-10 | 腾讯科技（深圳）有限公司 | Virtual resource transaction monitoring method and device is applied on line |
| CN104933570A (en) * | 2014-03-20 | 2015-09-23 | 阿里巴巴集团控股有限公司 | User detection method and device |
| CN103955833B (en) * | 2014-03-31 | 2017-08-15 | 浙江工商大学 | Waterborne troops's indentity identifying method based on wash sale and social networks matrix analysis |
| CN104376491A (en) * | 2014-10-29 | 2015-02-25 | 中国建设银行股份有限公司 | Virtual resource monitoring method, device and system |
| CN104836701B (en) * | 2015-05-04 | 2019-03-15 | 北京京东尚科信息技术有限公司 | Order monitoring method and device |
| CN104867032A (en) * | 2015-05-16 | 2015-08-26 | 成都数联铭品科技有限公司 | Electronic commerce client evaluation identification system |
-
2016
- 2016-03-09 CN CN201610133030.9A patent/CN107180030B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107180030A (en) | 2017-09-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11153256B2 (en) | Systems and methods for recommending merchant discussion groups based on settings in an e-commerce platform | |
| US10318546B2 (en) | System and method for test data management | |
| US10878405B2 (en) | Smart redundant pairing of a card reader | |
| EP3757932A1 (en) | Systems and methods for facilitating e-commerce product returns using orders for returned items | |
| EP3799401B1 (en) | Systems and methods for facilitating authentication of emails sent by 3rd parties | |
| US20230262043A1 (en) | Hidden line property of online content to inhibit bot activity | |
| CN115809871A (en) | Business attributes based on non-homogeneous tokens | |
| CN113205402A (en) | Account checking method and device, electronic equipment and computer readable medium | |
| CN107180030B (en) | Method and device for generating relational data on network | |
| TW202312068A (en) | Systems and methods for blockchain network congestion-adaptive digital asset event handling | |
| US20220398572A1 (en) | Systems and methods for controlling transfers of digital assets | |
| Islam et al. | A review on E-commerce system in Bangladesh: an empirical study | |
| US11403646B2 (en) | Secure pin entry via mobile device | |
| Garg et al. | Issues and challenges with fake reviews in Digital Marketing | |
| EP3945484A1 (en) | Systems and methods for obtaining information from a digital message | |
| CN109310916B (en) | System and method for resolving conflicts in ordering data products | |
| US20220198036A1 (en) | Systems and methods for facilitating protecting recipient privacy | |
| US20220230178A1 (en) | Computer-implemented systems and methods for detecting fraudulent activity | |
| CN115099967A (en) | Supply chain-based enterprise owner social recommendation method and device and storage medium | |
| CN115049448A (en) | System and method for optimizing performance of online services | |
| US20210279774A1 (en) | Systems and methods for dynamic campaign engine | |
| US11522862B2 (en) | Systems and methods for a trusted entity to facilitate authentication of emails sent by 3rd parties | |
| CN112036941A (en) | Block chain-based store consumption evaluation method, equipment and medium | |
| US20130332316A1 (en) | Systems and Methods for Facilitating Business to Business Commerce | |
| Driessen et al. | Validated Data Quality Assessment with “Skin in the Game”: A Smart Contract Approach |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |