WO2016095738A1 - Relationship network data maintenance method, off-line server and real-time server - Google Patents

Abstract

Provided are a relationship network data maintenance method, an off-line server and a real-time server. The method comprises: an off-line server acquiring a user operation record before a pre-set time node; the off-line server conducting calculation to obtain sub-network data before the pre-set time node; and a real-time server supplementing a user operation record after the pre-set time node, and updating the supplemented relationship network data into an on-line server. The relationship network data maintenance method, off-line server and real-time server provided in the embodiments of the present application enable a network platform to access relationship network data after a pre-set time node in time after the off-line server completely processes a user operation record.

Description

Maintenance method for relational network data, offline server and real-time server Technical field

The present application relates to the field of network information processing, and in particular, to a method for maintaining network data, an offline server, and a real-time server.

Background technique

A network diagram structure composed of associations between interacting entities in a network platform may be referred to as a relational network.

Relationship-based network services can be provided in the network platform. The relationship may be an association relationship between a network social subject or a network transaction subject. For example, the relationship between social social subjects, friends, etc.; the relationship between payment and transfer between online transaction entities. With the relationship, a network structure diagram can be constructed from the perspective of the figure. From the perspective of the graph, the subject in the relational network can be a graph node, and the association relationship between the subjects can be the edge of the graph. Such a network structure diagram can intuitively and clearly indicate the network of subjects and relationships.

For example, in a network structure diagram composed of a network social platform, a user may be a graph node, and a relationship between a user and a user such as a friend and/or a concern may be used as an edge of the graph. For example, in a network transaction platform, a user, a credit card, a device, or the like can be regarded as a graph node, and the user can use the credit card to pay, the user to use the device to log in, the user to pay the valuable object to other users, and the like can be regarded as the edge of the graph.

Typically, network platform systems need to maintain a relational network in conjunction with user action records. In the prior art, the maintenance of the relational network generally involves an offline server and an online server. The offline server can read the user operation record in the network platform in a certain period of time, and calculate the user operation record before the preset time node in each time period to construct the relationship network data. The offline server then updates the calculated relational network data directly to the online server. The relational network data in the online server can be provided to the network platform for access. In general, the online server and the network platform can be located in the same network environment, and the offline server and the online server can be in different network environments.

In the process of implementing the present application, the inventors found that the prior art has at least the following problems:

Since the amount of user operation record data before the preset time node read by the offline server is relatively large, the calculation takes a long time. This causes the user operation record generated from the preset time node to the offline server to be updated to the online server only after the calculation of the next cycle, resulting in the network platform not being able to access the relationship in time. Network data.

Summary of the invention

The purpose of the embodiment of the present application is to provide a method for maintaining network data, an offline server, and a real-time server, so that the network platform can access the relationship after the preset time node in time after the offline server processes the user operation record. Network data.

A method for maintaining relationship network data, an offline server, and a real-time server provided by the embodiments of the present application are implemented as follows:

A method for maintaining network data, including:

The offline server obtains a user operation record before the preset time node;

The offline server calculates the user operation record before the preset time node, and obtains the first sub-network data before the preset time node;

The offline server synchronizes the first sub-network data into the real-time server and sends the preset time node to the real-time server;

The real-time server stores the first sub-network data and acquires a user operation record after the preset time node;

The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data with the first sub-network data into the third sub-network data, and merges the combined The third subnet data is updated to the online server.

A method for maintaining network data, including:

The offline server obtains a user operation record before the preset time node;

The offline server calculates the user operation record before the preset time node, and obtains the first sub-network data before the preset time node;

The offline server synchronizes the first sub-network data into the online server and sends the preset time node to the real-time server;

The real-time server acquires a user operation record after the preset time node;

The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data into the online server.

A method for maintaining network data, including:

The offline server obtains a user operation record before the preset time node;

The offline server calculates the user operation record before the preset time node, and obtains the first sub-network data before the preset time node;

The offline server synchronizes the first sub-network data to the real-time server or the online server, and sends the preset time node to the real-time server.

A method for maintaining network data, including:

The real-time server stores the first sub-network data synchronized from the offline server and receives the preset time node;

The real-time server acquires a user operation record after the preset time node;

The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data with the first sub-network data into the third sub-network data, and merges the combined The third subnet data is updated to the online server.

A method for maintaining network data, including:

The real-time server receives the preset time node and acquires a user operation record after the preset time node;

The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data into the online server.

An offline server that includes:

a user operation record obtaining unit, configured to acquire a user operation record before the preset time node;

a calculating unit, configured to calculate a user operation record before the preset time node, to obtain a first sub-network data before the preset time node;

The sub-network data synchronization unit is configured to synchronize the first sub-network data into the real-time server and send the preset time node to the real-time server.

An offline server that includes:

a user operation record obtaining unit, configured to acquire a user operation record before the preset time node;

a calculating unit, configured to calculate a user operation record before the preset time node, to obtain a first sub-network data before the preset time node;

The sub-network data update unit is configured to synchronize the first sub-network data into the online server and send the preset time node to the real-time server.

A real-time server that includes:

a storage unit, configured to store first sub-network data synchronized by the offline server;

The user operation record reading unit is configured to obtain a user operation record after the preset time node;

a calculating unit, configured to calculate a user operation record after the preset time node, to obtain second sub-network data;

a merging unit, configured to merge the second sub-network data with the first sub-network data into the third sub-network data;

The update unit is configured to update the merged third sub-network data to the online server.

A real-time server that includes:

The user operation record reading unit is configured to obtain a user operation record after the preset time node;

a calculating unit, configured to calculate a user operation record after the preset time node, to obtain second sub-network data;

The merging unit is used to merge the second sub-network data into the online server.

According to the embodiment of the present application, after the offline server calculates the user operation record before the preset time node, the real-time server can supplement the user operation record after the preset time node in time, so that the network platform can be enabled. After the offline server processes the user operation record, it accesses the relational network data after the preset time node in time.

DRAWINGS

1 is a flowchart of a first embodiment of a method for maintaining relationship network data according to the present application;

2 is a functional diagram of a module of an offline server in an embodiment of the present application;

3 is a functional block diagram of an offline server in another embodiment of the present application;

4 is a functional block diagram of a computing unit in an offline server in an embodiment of the present application;

FIG. 5 is a functional diagram of a module of a real-time server in an embodiment of the present application; FIG.

6 is a functional diagram of a module of a real-time server in another embodiment of the present application;

7 is a functional diagram of a module of a computing unit in a real-time server according to an embodiment of the present application;

8 is a flowchart of an embodiment of a method for maintaining relationship network data that is mainly an offline server according to the present application;

FIG. 9 is a flowchart of another embodiment of a method for maintaining relationship network data that is mainly composed of an offline server;

10 is a flowchart of an embodiment of a method for maintaining relationship network data mainly composed of a real-time server;

11 is a flow chart of another embodiment of a method for maintaining relationship network data mainly based on a real-time server in the present application.

detailed description

The embodiment of the present application provides a method for maintaining network data, an offline server, and a real-time server. The technical solutions in the embodiments of the present application are clearly and completely described in the following, in which the technical solutions in the embodiments of the present application are clearly and completely described. The embodiments are only a part of the embodiments of the present application, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope shall fall within the scope of the application.

The method for maintaining relationship network data provided by the present application relates to an offline server, a real-time server, and an online server. The offline server can be responsible for the calculation of large amounts of data in an offline environment; the real-time server and the online server can be located in the same network environment. In addition, the real-time server can also be integrated into the online server as a software module or hardware module. 1 is a flow chart of a first embodiment of a method for maintaining network data in the present application. As shown in FIG. 1, the method for maintaining the relationship network data includes the following steps:

S1: The offline server obtains a user operation record before the preset time node.

In the network platform system, operations in the user's online environment, such as "add, delete, change", can be recorded in the user operation record. There are various software systems for storing user operation records, including: file system, MySQL database, HBase database, and so on.

The offline server can synchronize the user actions recorded by the platform system in a fixed cycle. For example, the offline server synchronizes daily user action records for the day in the online production environment on a daily basis. Further, the offline server can set a specific time node, for example, 23:59:59 every day. In this way, the offline server can synchronize the user operation records before the time node at 23:59:59 every day. The above-mentioned daily time node can be used as the preset time node described in step 1. In addition, the offline server can also perform the above synchronization operation on user operations recorded by the platform system in a non-fixed cycle.

The offline server can use incremental synchronization when performing synchronization operations. Specifically, in each synchronization after the first synchronization, only the data of the last cycle can be synchronized. Based on the above example, when the offline server synchronizes the user operation records at 23:59:59 on September 24, 2014, it only needs to be 23:59:59 on September 23, 2014 to September 24, 2014. The user operation record of 23:59:59 on the day can be synchronized, because the user operation record before 23:59:59 on September 23, 2014 has been processed in the previous synchronization process. Specifically, assuming that the online production environment uses the file system to implement the user operation record storage, the online production environment can scroll to generate a user operation record file every day, for example, the user operation data of September 24, 2014 is stored in the " User operation record - 2014.09.24.log" file. Then, when the offline server synchronizes at 23:59:59 on September 24, 2014, the "user operation record-2014.09.24.log" file can be read or copied incrementally. Assume that the online production environment uses the HBase database to implement the user operation record storage. Then the online production environment can use the data backup tool provided by the HBase database to store the last cycle of data to the offline server. You can also use the HBase database scan. Operation, the data in the last cycle time period is read into the offline server. The common methods of the scan class in HBase are described as follows:

//scan.setTimeRange();//Specify the maximum timestamp and the smallest timestamp, only cells in this range can be obtained.

//scan.setTimeStamp();//Specify the timestamp

//scan.setFilter();//Specify Filter to filter out unwanted information

//scan.setStartRow();//Specify the starting line. If not called, start from the header;

//scan.setStopRow();//Specify the end of the line (without this line);

//scan.setBatch();//Specifies the maximum number of cells returned. Used to prevent excessive data in a row, resulting in an OutOfMemory error.

Of course, when the offline server performs the synchronization operation, it can also be processed in a synchronous manner as needed, which is not limited herein.

During each of the preset time periods, the processing of steps S2 to S5 may be performed:

S2: The offline server calculates a user operation record before the preset time node, and obtains the preset time. The first subnet data before the node.

After the offline server reads the user operation record before the preset time node, it can be processed as follows:

S201: The offline server disassembles each user operation record before the preset time node into data including a sub-network body and a sub-network edge.

The sub-network body disassembled in step S201 may include a start body and a terminating body.

As an example, there is a user operation record for user 1 to pay by using credit card 1 on device 1. After the offline server disassembles this operation record, the sub-network body is obtained as user 1, device 1, and credit card 1; the sub-network side is paid. According to the operation record, the offline server can determine the starting body and the terminating body, and save the starting body, the terminating body, and the sub-network side into the sub-network table, as shown in Table 1:

Table 1: Subnet Table

Starting subject	Termination of the subject	Subnetwork side
User 1	Equipment 1	Pay
User 1	Credit card 1	Pay
Equipment 1	Credit card 1	Pay

After the offline server processes the user operation record, it will continue to process the subsequent user operation records in the same way, and finally obtain a subnet table composed of several subnetwork data, as shown in Table 2:

Table 2: Subnet Table

Starting subject	Termination of the subject	Subnetwork side
User 1	Equipment 1	Pay
User 1	Credit card 1	Pay
Equipment 1	Credit card 1	Pay
User 2	Device 2	Pay
User 2	Credit card 2	Pay
Device 2	Credit card 2	Pay
User 1	Device 2	Pay
...	...	...

As can be seen from Table 2, the offline server disassembles the user operation data in the preset time period into the starting body one by one, terminates the body and the sub-network side, and terminates the starting body, the terminating body, and the sub-network side. Save in the subnet table.

The subject and sub-network edges involved in the user action record may be accompanied by an initial identifier that distinguishes between different subjects and different sub-network edges. In addition, the sub-network side involved in the user operation record can also be accompanied by an initial time letter. Information, used to record the exact time point generated by the subnetwork. After the offline server determines the starting body and the terminating body and the sub-network side between them, the identifiers of the starting body, the terminating body, and the sub-network edge can be emptied.

S202: The offline server performs the merge processing on the disassembled data according to the sub-network body and the sub-network edge according to a preset rule, to obtain the first sub-network data before the preset time node.

The offline server may perform a merge process on the sub-network body in the sub-network table to obtain a correspondence between the main body and the sub-network. The offline server can follow the following rules when merging sub-network bodies in the sub-network table:

If neither the starting body nor the terminating body has an identifier, the offline server generates an identifier assigned to the starting body and the terminating body;

If the starting body has an identifier and the terminating body has no identifier, the identifier of the starting body is assigned to the terminating body;

If the starting body has no identity and the terminating body has an identity, the identity of the terminating body is assigned to the starting body;

If the identifiers of the start body and the terminating body are different, the identifier of the terminating body is cleared, then the identifier of the starting body is assigned to the terminating body, and the identifiers of all the subjects associated with the terminating body are modified to Terminate the identity of the subject;

If the start and stop bodies have the same identity, no processing is done.

The identifier generated by the offline server is a unique identifier.

The rules followed in the above-mentioned merge processing can be preset rules.

Continue with the example of step S201 to illustrate:

First, the above processing is performed on the first item in Table 2. The starting entity is user 1, the terminating body is device 1, wherein user 1 has no identifier, and device 1 has no identifier. According to the above-mentioned merge principle, the offline server generates an identifier A, and sets the identifiers of user 1 and device 1 to A. ;

The above processing is performed on the second item in Table 2. The starting body is the user 1, the terminating body is the credit card 1, wherein the user 1 has the identifier A, the credit card 1 has no identification, and according to the above-mentioned merge principle, the identification of the credit card 1 is set to A;

The above processing is performed on the third item in Table 2. The starting entity is the device 1, and the terminating body is the credit card 1, wherein the identifier of the device 1 is A, and the identifier of the credit card 1 is also A. According to the above-mentioned merge principle, no processing is performed.

The above processing is performed on the fourth item in Table 2. The starting entity is user 2, the terminating body is device 2, wherein user 2 has no identity, and device 2 has no identity. According to the above-mentioned merge principle, the offline server generates a different identifier B from the identifier A, and the user 2 and the device 2 The identity is set to B.

By analogy, the subject identifiers in Articles 5 and 6 of Table 2 are both set to B; for the seventh clause in Table 2, the starting subject is User 1, and the terminating subject is Device 2, where User 1's logo is A. The identifier of the device 2 is B. According to the above-mentioned merge principle, the identifier of the device 2 is cleared, then the identifier A of the user 1 is assigned to the device 2, and the identifiers of all the subjects associated with the device 2 are modified to A. , that is, the identification of both user 2 and credit card 2 is changed from B to A.

Finally, the starting body and the terminating body in the same subnet have the same identity; the subjects in different subnetworks have different identities.

The offline server can continue to assign the identifier of the subject in the same sub-network to the sub-network side, so that the subject and the edge in the same sub-network can have the same identifier, and the same identifier can be defined as the sub-network identifier. The subnet table after the merge processing is shown in Table 3:

Table 3: Subnet Tables after Identification and Merging

In this way, the start body, the termination body, the sub-network side, the time information of the sub-network side, and the sub-network identifier in the sub-network can be the first sub-network data before the preset time node.

S3: The offline server synchronizes the first sub-network data into the real-time server and sends the preset time node to the real-time server.

The offline server may synchronize the first sub-network data before the preset time node to the real-time server. The specific implementation manner can use the data backup tool provided by the HBase database to save the sub-network data to the real-time server; or use the scan operation of the HBase database to read the sub-network data in the preset time period to the real-time server.

The offline server may send the preset time node to the real-time server after the synchronization of the first sub-network data before the preset time node is completed. For example, the offline server processes the user operation record before 23:59:59 on September 24, 2014. After the synchronization of the sub-network data before this time node is completed, it can be September 24, 2014. At 59 minutes and 59 seconds, this time node is sent to the real-time server. In this way, the real-time server can start processing the subsequent user operation records from 23:59:59 on September 24, 2014.

S4: The real-time server stores the first sub-network data and acquires a user operation record after the preset time node.

After receiving the preset time node sent by the offline server, the real-time server may store the sub-network data before the preset time node synchronized by the offline server, and perform subsequent processing. Step S1 mentioned that the user generated by the platform system The record can be stored in the software system. The software system storing the user operation record can be located in a separate data server, which can be located in the online environment where the platform system is located; the software system storing the user operation record can also be integrated into the real-time server as a software module. Facilitate faster access to real-time servers. The real-time server may determine the user operation record after the preset time node: if the user operation record is not generated, the real-time server waits for the user record to be generated; if the user operation record is generated, after reading the preset time node User action record.

S5: The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data with the first sub-network data into the third sub-network data.

For the user operation record after each preset time node, the real-time server may first disassemble each user operation record after the preset time node into data including the sub-network body and the sub-network edge. Then, the real-time server may perform the merge processing on the disassembled data based on the sub-network body and the sub-network edge according to a preset rule to obtain the second sub-network data. The merging process is similar to step S202, and will not be described again here. The real-time server may then merge the second sub-network data with the first sub-network data into the third sub-network data based on the sub-network body and the sub-network side in the second sub-network data. The specific process is as follows:

The real-time server searches for the sub-network and the sub-network identifier corresponding to the disassembled main body in the stored first sub-network data according to the disassembled main body. If the discovered subnet identifiers are the same, the disassembled entities are located in the same subnet. Further, whether the disassembled user operation record already exists in the stored first sub-network data may be determined by the time information of the disassembled sub-network side. If the disassembled user operation record already exists in the stored first sub-network data, skip the user operation record directly, and perform processing of the next user operation record; if the disassembled user operation record is not The first sub-network data stored in the storage may be directly set to the sub-network identifier of the disassembled sub-network identifier and merged into the stored first sub-network data.

As an example, a user operation record is that the user 1 is performing a payment operation using the credit card 1. After the real-time server obtains the user operation record, the user operation record can be disassembled into: user 1, credit card 1 and the payment of the sub-network side, and the payment is assumed to be at 9:24 on September 24, 2014. In 38 seconds, the payment operation in the user operation record has a time information, which is assumed to be 0020140924092438. The real-time server can then find the identifier corresponding to the user 1 and the credit card 1 in the stored first sub-network data. Assuming that the identified IDs of both User 1 and Credit Card 1 are A1, it indicates that User 1 and Credit Card 1 are in the same sub-network. At this time, the real-time server can continue to compare the time information of the payment operation between the user 1 and the credit card 1, assuming that there is also a payment operation between the user 1 and the credit card 1 in the stored first sub-network data, and the payment The time information of the operation is also 0020140924092438, which indicates that the current user operation record processed by the real-time server actually exists in the stored A subnet of the network data. In order not to process the data repeatedly, the real-time server can directly skip the user operation record and perform the processing of the next user operation record. If the time information corresponding to the payment operation between the user 1 and the credit card 1 in the stored first sub-network data is different from the time information corresponding to the payment operation between the user 1 and the credit card 1 in the user operation record, it indicates that The user operation record and the stored first sub-network data are not duplicated, and then the user 1, the credit card 1 and the payment identifier in the user operation record can be set to A1 and merged into the stored first sub-network data.

If the discovered sub-network identifiers are different, indicating that the disassembled entities are in different sub-networks, the sub-networks that are found may be merged first. The method of merging may be: randomly selecting one sub-network identifier in the discovered sub-network, and setting the subject identifier, the sub-network edge identifier, and the sub-network identifier in the found sub-network to the The selected sub-network identifiers, so that the discovered sub-networks can be merged into one sub-network; the identifiers of the disassembled main body and sub-network edges can be set as the selected sub-network identifiers and merged into the In the first subnet data stored.

The following is explained by a specific example. For example, a user operation record read by the real-time server after the preset time node is: User 1 performs a payment operation on the device 2. Then the real-time server can disassemble the user operation record into the main user 1 and the main device 2 and the sub-network side payment. The real-time server can then find the sub-network corresponding to user 1 and device 2 from the stored first sub-network data. It is assumed that the sub-network corresponding to user 1 is A, the sub-network identifier is A1, the sub-network corresponding to device 2 is B, and the sub-network identifier is B1. It can be seen that the user 1 and the device 2 are not in the same sub-network, but the sub-network A and the sub-network B are connected through the payment relationship between the user 1 and the device 2, so the sub-network A and the sub-network need to be Network B is merged into one subnet. The specific merge method is as follows: the real-time server randomly selects one sub-network identifier in the sub-network A and the sub-network B, for example, A1, and the subject identifier, the sub-network edge identifier, and the sub-network identifier in the sub-network A and the sub-network B are both Set to A1. In this way, sub-network A and sub-network B can be combined into one sub-network. The user 1 and the device 2 and the payment identifier can then be set to A1 and merged into the stored first sub-network data. When the real-time server is looking for the sub-network corresponding to the disassembled main body, there may be another case: the disassembled main body does not have a corresponding sub-network in the stored first sub-network data. This situation indicates that the disassembled body appears for the first time. The real-time server may form the disassembled main body into a new sub-network, and merge the constructed new sub-network data into the stored first sub-network data. After the real-time server processes the user operation record, the subsequent user operation record processing can be continued. The process is as described above, and will not be described here.

S6: The real-time server updates the merged third sub-network data to the online server.

Since the amount of user operation record data after the preset time node is relatively small, and the user operation record can be stored in the real-time server or stored in a separate server in the same network environment as the real-time server, the real-time server The time for data reading and data processing is very short; on the other hand, the real-time server can be located in the same network environment as the online server, and can also be integrated into the online server as a software module or hardware module, so the real-time server and online The information exchange between the servers is very fast, and the time for the real-time server to update the data to the online server is also very short, so that the online server can timely access the user operation records after the preset time node.

In this embodiment, the offline server performs data acquisition and calculation processing according to a preset time period, and can flexibly respond to the access requirements of the network platform system. For example, in a network trading platform system, an online trading platform wants to access the number of credit card usages of a user in the most recent year. In the solution provided by the embodiment, the offline server may continue to process the user operation record of the latest year for processing in the time period after the user operation record before the preset time node is acquired. In this way, the data in the online server will only contain the user operation data of the last year, which can meet the access requirements of the network transaction platform.

In the second embodiment of the present application, the offline server may also not read the user operation record for a certain period of time, but only read the user operation record before the preset time node once and perform calculation processing. For example, if the preset time node is 23:59:59 on September 24, 2014, the offline server can read the user operation record before 23:59:59 on September 24, 2014, and calculate after reading. deal with. After the offline server calculates the user operation record before the preset time node, the first sub-network data before the preset time node can be obtained. The offline server synchronizes the first sub-network data before the preset time node to the real-time server and sends the preset time node to the real-time server. The real-time server stores the first sub-network data before the preset time node and acquires a user operation record after the preset time node. The real-time server calculates a user operation record after the preset time node, and merges the calculated sub-network data into the stored first sub-network data, and updates the merged sub-network data to the online server. Continuing with the above example, the offline server can calculate the sub-network data before 23:59:59 on September 24, 2014 after calculating the user operation record before 23:59:59 on September 24, 2014. . The offline server synchronizes the subnet data to the real-time server and sends the time node at 23:59:59 on September 24, 2014 to the real-time server. After the real-time server stores the sub-network data before 23:59:59 on September 24, 2014, it can calculate all the user operation records after 23:59:59 on September 24, 2014, and The calculated sub-network data is merged into the stored sub-network data, and the merged sub-network data can be further updated to the online server. The calculation process of the offline server and the data calculation and merge process of the real-time server are as described in the first embodiment of the present application, and are not described herein again.

In this embodiment, the offline server only reads the user operation record before the preset time node, avoids repeated calculation of part of the large data amount, and can improve the efficiency of the maintenance of the entire relationship network.

In the third embodiment of the present application, the offline server may acquire the preset time node according to the preset time period. User action record. The following processing can be performed during each preset time period:

The offline server calculates the user operation record before the preset time node, and obtains the first sub-network data before the preset time node;

The offline server synchronizes the first sub-network data into the online server and sends the preset time node to the real-time server;

The real-time server acquires a user operation record after the preset time node;

The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data into the online server.

The calculation process of the offline server and the data calculation and merge process of the real-time server are as described in the first embodiment of the present application, and are not described herein again.

In this embodiment, the offline server directly updates the sub-network data before the preset time node to the online server, avoiding the process of performing data synchronization to the real-time server and data storage by the real-time server. The real-time server can directly merge the user operation records after the preset time node into the online server, thereby avoiding the process of updating the large data volume to the online server, so the whole process is more efficient. In addition, the offline server performs data acquisition and calculation processing according to a preset time period, and can flexibly respond to the access requirements of the network platform system. For example, in a network trading platform system, an online trading platform wants to access the number of credit card usages of a user in the most recent year. In the solution provided by the embodiment, the offline server may continue to process the user operation record of the latest year for processing in the time period after the user operation record before the preset time node is acquired. In this way, the data in the online server will only contain the user operation data of the last year, which can meet the access requirements of the network transaction platform.

In the fourth embodiment of the present application, the offline server may not read the user operation record for a certain period of time, but only read the user operation record before the preset time node once and perform calculation processing. For example, if the preset time node is 23:59:59 on September 24, 2014, the offline server can read the user operation record before 23:59:59 on September 24, 2014, and calculate after reading. deal with. After the offline server calculates the user operation record before the preset time node, the first sub-network data before the preset time node is obtained. The offline server may directly synchronize the first sub-network data before the preset time node to the online server, and simultaneously send the preset time node to the real-time server. After obtaining the user operation record after the preset time node, the real-time server calculates a user operation record after the preset time node, and merges the calculated sub-network data into the online server.

In this embodiment, the offline server directly updates the first sub-network data before the preset time node to the online server, avoiding the process of performing data synchronization to the real-time server and data storage by the real-time server. The real-time server can directly merge the user operation records after the preset time node into the online server, avoiding the entry to the online server. The process of updating large amounts of data is so efficient that the entire process is more efficient. In addition, the offline server only reads the user operation record before the preset time node, avoids the repeated calculation of part of the large data amount, and can also improve the efficiency of the maintenance of the entire relationship network. Through the foregoing embodiment of the present application, the offline server calculates a user operation record of a large amount of data before the preset time node, and obtains sub-network data before the preset time node; the real-time server can timely access the user after the preset time node. The operation record is supplemented, so that the network platform can access the relational network data after the preset time node in time after the offline server processes the user operation record.

The following describes an embodiment of the maintenance method of the relational network with the offline server as the main body of the present application. FIG. 8 is a flowchart of an embodiment of a method for maintaining relationship network data with an offline server as the main body of the present application. As shown in FIG. 8, the method for maintaining relationship network data that is mainly composed of an offline server includes the following steps:

S110: The offline server acquires a user operation record before the preset time node.

In a preferred embodiment of the present application, the offline server may acquire a user operation record before the preset time node according to a preset time period, where the preset time period includes a preset fixed time period and a preset non-fixed time period. The offline server can obtain the user operation record before the preset time node in the incremental synchronization mode or can obtain the user operation record before the preset time node in all synchronization modes.

S120: The offline server calculates a user operation record before the preset time node, and obtains the first sub-network data before the preset time node.

Step S120 can be specifically implemented by the following two steps:

The offline server disassembles each user operation record before the preset time node into data including the sub-network body and the sub-network edge;

The offline server performs the merging process on the disassembled data based on the sub-network body and the sub-network edge according to a preset rule to obtain the first sub-network data before the preset time node.

S130: The offline server synchronizes the first sub-network data into the real-time server and sends the preset time node to the real-time server.

Another embodiment of the maintenance method of the relational network with the offline server as the main body of the present application is described below. FIG. 9 is a flowchart of another embodiment of a method for maintaining relationship network data that is mainly an offline server according to the present application. As shown in FIG. 9, the method for maintaining relationship network data that is based on an offline server includes:

S210: The offline server acquires a user operation record before the preset time node.

In a preferred embodiment of the present application, the offline server may acquire a user operation record before the preset time node according to a preset time period, where the preset time period includes a preset fixed time period and a preset non-fixed time period. The offline server can obtain the user operation record before the preset time node in the incremental synchronization mode or can obtain the user operation record before the preset time node in all synchronization modes.

S220: The offline server calculates a user operation record before the preset time node, and obtains the first sub-network data before the preset time node.

Step S220 can be specifically implemented by the following two steps:

The offline server disassembles each user operation record before the preset time node into data including the sub-network body and the sub-network edge;

The offline server performs the merging process on the disassembled data based on the sub-network body and the sub-network edge according to a preset rule to obtain the first sub-network data before the preset time node.

S230: The offline server synchronizes the first sub-network data into the online server and sends the preset time node to the real-time server.

The following describes an embodiment of the maintenance method of the relational network in which the real-time server is the main body of the present application. FIG. 10 is a flowchart of an embodiment of a method for maintaining relationship network data that is based on a real-time server. As shown in FIG. 10, the method for maintaining relationship network data that is based on a real-time server includes the following steps:

S310: The real-time server stores the first sub-network data synchronized from the offline server and receives the preset time node;

S320: The real-time server acquires a user operation record after the preset time node;

S330: The real-time server calculates a user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data with the first sub-network data into the third sub-network data, and merges The third sub-network data is updated to the online server. The obtaining the third sub-network data may be specifically implemented by the following three steps:

The real-time server disassembles each user operation record after the preset time node into data including the sub-network body and the sub-network edge;

The real-time server merges the disassembled data according to the preset rule based on the sub-network body and the sub-network edge to obtain the second sub-network data;

The real-time server merges the second sub-network data and the first sub-network data into the third sub-network data based on the sub-network body and the sub-network side in the second sub-network data.

Further, after the foregoing steps, the method may further include:

The real-time server obtains the fourth sub-network data, and the start time point of the fourth sub-network data is not earlier than the end time point of the third sub-network data;

The real-time server merges the fourth sub-network data and the third sub-network data into the fifth sub-network data, and updates the merged fifth sub-network data to the online server.

Another embodiment of the maintenance method of the relational network with the real-time server as the main body of the present application is described below. FIG. 11 is a flowchart of another embodiment of a method for maintaining relationship network data that is based on a real-time server. As shown in FIG. 11, the method for maintaining relationship network data that is based on a real-time server includes the following steps:

S410: The real-time server receives the preset time node and acquires a user operation record after the preset time node;

S420: The real-time server calculates a user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data into the online server.

Step S420 may specifically include the following three steps:

The real-time server disassembles each user operation record after the preset time node into data including the sub-network body and the sub-network edge;

The real-time server merges the disassembled data according to the preset rule based on the sub-network body and the sub-network edge to obtain the second sub-network data;

The real-time server merges the second sub-network data into the online server based on the sub-network body and the sub-network side in the second sub-network data.

Further, after the foregoing steps, the method may further include:

The real-time server obtains the third sub-network data, and the start time point of the third sub-network data is not earlier than the end time point of the second sub-network data;

The real-time server merges the third subnet data into the online server.

2 is a functional diagram of a module of an offline server in an embodiment of the present application. As shown in FIG. 2, the offline server includes:

The user operation record obtaining unit 101 is configured to acquire a user operation record before the preset time node;

The calculating unit 102 is configured to calculate a user operation record before the preset time node, and obtain a first sub-network data before the preset time node;

The sub-network data synchronization unit 103 is configured to synchronize the first sub-network data into the real-time server and send the preset time node to the real-time server.

FIG. 3 is a functional block diagram of an offline server in another embodiment of the present application. As shown in FIG. 3, the offline server specifically includes:

The user operation record obtaining unit 101 is configured to acquire a user operation record before the preset time node;

The calculating unit 102 is configured to calculate a user operation record before the preset time node, and obtain a first sub-network data before the preset time node;

The sub-network data updating unit 104 is configured to synchronize the first sub-network data into the online server and send the preset time node to the real-time server.

4 is a functional block diagram of a computing unit in an offline server in an embodiment of the present application. As shown in FIG. 4, the computing unit 102 in the offline server specifically includes:

The disassembling unit 1021 is configured to disassemble each user operation record before the preset time node to include a sub-network body and Data on the side of the subnetwork;

The merging unit 1022 is configured to perform merging processing on the disassembled data based on the sub-network body and the sub-network edge according to a preset rule to obtain first sub-network data before the preset time node.

FIG. 5 is a functional diagram of a module of a real-time server in an embodiment of the present application. As shown in FIG. 5, the real-time server includes:

The storage unit 201 is configured to store first sub-network data synchronized by the offline server;

The user operation record reading unit 202 is configured to acquire a user operation record after the preset time node;

The calculating unit 203 is configured to calculate a user operation record after the preset time node to obtain second sub-network data;

The merging unit 204 is configured to merge the second sub-network data with the first sub-network data into the third sub-network data;

The updating unit 205 is configured to update the merged third sub-network data into the online server.

6 is a block diagram of a real-time server in another embodiment of the present application. As shown in FIG. 6, the real-time server includes:

The user operation record reading unit 202 is configured to acquire a user operation record after the preset time node;

The calculating unit 203 is configured to calculate a user operation record after the preset time node to obtain second sub-network data;

The merging unit 303 is configured to merge the second sub-network data into the online server.

FIG. 7 is a functional diagram of a module of a computing unit in a real-time server according to an embodiment of the present application. As shown in FIG. 7, the calculating unit 203 includes:

The disassembling unit 2031 is configured to disassemble each user operation record after the preset time node into data including a sub-network body and a sub-network side;

The merging unit 2032 is configured to perform merging and processing the disassembled data based on the sub-network body and the sub-network edge according to a preset rule to obtain second sub-network data.

In the 1990s, improvements to a technology could clearly distinguish between hardware improvements (eg, improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (for process flow improvements). However, as technology advances, many of today's method flow improvements can be seen as direct improvements in hardware circuit architecture. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented by hardware entity modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is an integrated circuit whose logic function is determined by the user programming the device. Designed by the designer to "integrate" a digital system on a PLD without the need for a chip manufacturer to design and manufacture A dedicated integrated circuit chip 2 is used. Moreover, today, instead of manually making integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in programming development, but before compiling The original code has to be written in a specific programming language. This is called the Hardware Description Language (HDL). HDL is not the only one, but there are many kinds, such as ABEL (Advanced Boolean Expression Language). AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., are currently the most commonly used VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog2. It should also be apparent to those skilled in the art that the hardware flow for implementing the logic method flow can be easily obtained by simply programming the method flow into the integrated circuit with a few hardware description languages.

The controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. In the form of logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers, examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.

Those skilled in the art will also appreciate that in addition to implementing the controller in purely computer readable program code, the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding. The form of a microcontroller or the like to achieve the same function. Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component. Or even a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.

The system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.

For the convenience of description, the above devices are described separately by function into various units. Of course, the functions of each unit may be implemented in the same software or software and/or hardware when implementing the present application.

It will be apparent to those skilled in the art from the above description of the embodiments that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM or a disk. , CD, etc., including a number of instructions to make a computer device (can It is a personal computer, server, or network device, etc.) that performs the methods described in various embodiments of the present application or portions of the embodiments.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

This application can be used in a variety of general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor based systems, set-top boxes, programmable consumer electronics devices, network PCs, small computers, mainframe computers, including A distributed computing environment of any of the above systems or devices, and the like.

The application can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. The present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including storage devices.

While the present invention has been described by the embodiments of the present invention, it will be understood by those skilled in the art

Claims (29)

1. A method for maintaining relationship network data, comprising:

   The offline server obtains a user operation record before the preset time node;

   The offline server calculates the user operation record before the preset time node, and obtains the first sub-network data before the preset time node;

   The offline server synchronizes the first sub-network data into the real-time server and sends the preset time node to the real-time server;

   The real-time server stores the first sub-network data and acquires a user operation record after the preset time node;

   The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data with the first sub-network data into the third sub-network data, and merges the combined The third subnet data is updated to the online server.
2. A method for maintaining relationship network data, comprising:

   The offline server obtains a user operation record before the preset time node;

   The offline server calculates the user operation record before the preset time node, and obtains the first sub-network data before the preset time node;

   The offline server synchronizes the first sub-network data into the online server and sends the preset time node to the real-time server;

   The real-time server acquires a user operation record after the preset time node;

   The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data into the online server.
3. The method for maintaining the relationship network data according to claim 1 or 2, wherein the user operation record before the offline server acquires the preset time node comprises:

   The offline server obtains the user operation record before the preset time node according to the preset time period.
4. The method for maintaining relationship network data according to claim 3, wherein the preset time period comprises a preset fixed time period and a preset non-fixed time period.
5. The method for maintaining the relationship network data according to claim 3, wherein the offline server obtains the user operation record before the preset time node according to the preset time period, including:

   The offline server acquires a user operation record before the preset time node by using an incremental synchronization manner;

   or,

   The offline server acquires the user operation record before the preset time node in all synchronization manners.
6. A method for maintaining relationship network data according to claim 1 or 2, wherein said offline service The server calculates the user operation record before the preset time node, and the first sub-network data before the preset time node is specifically included:

   The offline server disassembles each user operation record before the preset time node into data including the sub-network body and the sub-network edge;

   The offline server performs the merging process on the disassembled data based on the sub-network body and the sub-network edge according to a preset rule to obtain the first sub-network data before the preset time node.
7. The method for maintaining relationship network data according to claim 1, wherein the real-time server calculates a user operation record after the preset time node to obtain a second sub-network data, and the second The merging of the sub-network data with the first sub-network data into the third sub-network data includes:

   The real-time server disassembles each user operation record after the preset time node into data including the sub-network body and the sub-network edge;

   The real-time server merges the disassembled data according to the preset rule based on the sub-network body and the sub-network edge to obtain the second sub-network data;

   The real-time server merges the second sub-network data and the first sub-network data into the third sub-network data based on the sub-network body and the sub-network side in the second sub-network data.
8. The method for maintaining relationship network data according to claim 2, wherein the real-time server calculates a user operation record after the preset time node to obtain a second sub-network data, and the second The subnet data is merged into the online server including:

   The real-time server disassembles each user operation record after the preset time node into data including the sub-network body and the sub-network edge;

   The real-time server merges the disassembled data according to the preset rule based on the sub-network body and the sub-network edge to obtain the second sub-network data;

   The real-time server merges the second sub-network data into the online server based on the sub-network body and the sub-network side in the second sub-network data.
9. The method for maintaining the relationship network data according to claim 1, wherein the method further comprises:

   The real-time server obtains the fourth sub-network data, and the start time point of the fourth sub-network data is not earlier than the end time point of the third sub-network data;

   The real-time server merges the fourth sub-network data and the third sub-network data into the fifth sub-network data, and updates the merged fifth sub-network data to the online server.
10. A method for maintaining relationship network data as claimed in claim 2, characterized in that after the method Also includes:

    The real-time server obtains the third sub-network data, and the start time point of the third sub-network data is not earlier than the end time point of the second sub-network data;

    The real-time server merges the third subnet data into the online server.
11. The method for maintaining relationship network data according to claim 1 or 2, wherein the user operation record is stored in an independent data server, and the data server is in the same network environment as the real-time server;

    or,

    The user operation record is stored in a real-time server.
12. The method for maintaining relationship network data according to claim 1 or 2, wherein the real-time server and the online server are located in the same network environment;

    or,

    The real-time server is integrated into the online server as a software module or hardware module.
13. A method for maintaining relationship network data, comprising:

    The offline server obtains a user operation record before the preset time node;

    The offline server calculates the user operation record before the preset time node, and obtains the first sub-network data before the preset time node;

    The offline server synchronizes the first sub-network data to the real-time server or the online server, and sends the preset time node to the real-time server.
14. The method for maintaining the relationship network data according to claim 13, wherein the user operation record before the offline server acquires the preset time node comprises:

    The offline server obtains the user operation record before the preset time node according to the preset time period.
15. The method for maintaining relationship network data according to claim 14, wherein the preset time period comprises a preset fixed time period and a preset non-fixed time period.
16. The method for maintaining the relationship network data according to claim 14, wherein the offline server obtains the user operation record before the preset time node according to the preset time period, including:

    The offline server acquires a user operation record before the preset time node by using an incremental synchronization manner;

    or,

    The offline server acquires the user operation record before the preset time node in all synchronization manners.
17. The method for maintaining the relationship network data according to claim 13, wherein the offline server calculates a user operation record before the preset time node, and obtains the first before the preset time node. The subnet data specifically includes:

    The offline server disassembles each user operation record before the preset time node into data including the sub-network body and the sub-network edge;

    The offline server performs the merging process on the disassembled data based on the sub-network body and the sub-network edge according to a preset rule to obtain the first sub-network data before the preset time node.
18. A method for maintaining relationship network data, comprising:

    The real-time server stores the first sub-network data synchronized from the offline server and receives the preset time node;

    The real-time server acquires a user operation record after the preset time node;

    The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data with the first sub-network data into the third sub-network data, and merges the combined The third subnet data is updated to the online server.
19. The method for maintaining relationship network data according to claim 18, wherein the real-time server calculates a user operation record after the preset time node to obtain a second sub-network data, and the second The merging of the sub-network data with the first sub-network data into the third sub-network data includes:

    The real-time server disassembles each user operation record after the preset time node into data including the sub-network body and the sub-network edge;

    The real-time server merges the disassembled data according to the preset rule based on the sub-network body and the sub-network edge to obtain the second sub-network data;

    The real-time server merges the second sub-network data and the first sub-network data into the third sub-network data based on the sub-network body and the sub-network side in the second sub-network data.
20. The method for maintaining the relationship network data according to claim 18, further comprising:

    The real-time server obtains the fourth sub-network data, and the start time point of the fourth sub-network data is not earlier than the end time point of the third sub-network data;

    The real-time server merges the fourth sub-network data and the third sub-network data into the fifth sub-network data, and updates the merged fifth sub-network data to the online server.
21. A method for maintaining relationship network data, comprising:

    The real-time server receives the preset time node and acquires a user operation record after the preset time node;

    The real-time server calculates the user operation record after the preset time node, obtains the second sub-network data, and merges the second sub-network data into the online server.
22. The method for maintaining relationship network data according to claim 21, wherein the real-time server calculates a user operation record after the preset time node to obtain a second sub-network data, and the second Subnet The consolidation of the data into the online server includes:

    The real-time server disassembles each user operation record after the preset time node into data including the sub-network body and the sub-network edge;

    The real-time server merges the disassembled data according to the preset rule based on the sub-network body and the sub-network edge to obtain the second sub-network data;

    The real-time server merges the second sub-network data into the online server based on the sub-network body and the sub-network side in the second sub-network data.
23. The method for maintaining the relationship network data according to claim 21, wherein the method further comprises:

    The real-time server obtains the third sub-network data, and the start time point of the third sub-network data is not earlier than the end time point of the second sub-network data;

    The real-time server merges the third subnet data into the online server.
24. An offline server, comprising:

    a user operation record obtaining unit, configured to acquire a user operation record before the preset time node;

    a calculating unit, configured to calculate a user operation record before the preset time node, to obtain a first sub-network data before the preset time node;

    The sub-network data synchronization unit is configured to synchronize the first sub-network data into the real-time server and send the preset time node to the real-time server.
25. An offline server, comprising:

    a user operation record obtaining unit, configured to acquire a user operation record before the preset time node;

    a calculating unit, configured to calculate a user operation record before the preset time node, to obtain a first sub-network data before the preset time node;

    The sub-network data update unit is configured to synchronize the first sub-network data into the online server and send the preset time node to the real-time server.
26. The offline server according to claim 24 or 25, wherein the calculating unit specifically comprises:

    a disassembling unit, configured to disassemble each user operation record before the preset time node into data including a sub-network body and a sub-network edge;

    The merging unit is configured to perform the merging processing on the disassembled data according to the preset rule based on the sub-network body and the sub-network edge to obtain the first sub-network data before the preset time node.
27. A real-time server, comprising:

    a storage unit, configured to store first sub-network data synchronized by the offline server;

    The user operation record reading unit is configured to obtain a user operation record after the preset time node;

    a calculating unit, configured to calculate a user operation record after the preset time node, to obtain second sub-network data;

    a merging unit, configured to merge the second sub-network data with the first sub-network data into the third sub-network data;

    The update unit is configured to update the merged third sub-network data to the online server.
28. A real-time server, comprising:

    The user operation record reading unit is configured to obtain a user operation record after the preset time node;

    a calculating unit, configured to calculate a user operation record after the preset time node, to obtain second sub-network data;

    The merging unit is used to merge the second sub-network data into the online server.
29. A real-time server according to claim 27 or 28, wherein said calculating unit comprises:

    a disassembling unit, configured to disassemble each user operation record after the preset time node into data including a sub-network body and a sub-network edge;

    The merging unit is configured to perform merging and processing the disassembled data based on the sub-network body and the sub-network edge according to a preset rule to obtain second sub-network data.

Images