CN114943040A

CN114943040A - Object sorting method, device, equipment, medium and product

Info

Publication number: CN114943040A
Application number: CN202210459510.XA
Authority: CN
Inventors: 张哲�
Original assignee: Amusement Starcraft Beijing Technology Co ltd
Current assignee: Amusement Starcraft Beijing Technology Co ltd
Priority date: 2022-04-27
Filing date: 2022-04-27
Publication date: 2022-08-26

Abstract

The application discloses an object sorting method, device, equipment, medium and product, which are applied to the technical field of computers. According to the technical scheme provided by the embodiment of the application, after a request for carrying out sequencing display on the associated object account numbers is received, the database is inquired by using the unique key, and a plurality of associated object account numbers which accord with the request are output to the terminal according to the sequencing sequence. The unique key comprises a target business index and a self-increment global unique identifier in the database, so that when the target business indexes are equal, the value of the unique key is ensured to be globally unique by utilizing the self-increment property of the global unique identifier, the value of the unique key at the initial point of inquiry in the requests of different batches cannot be repeated, the inquired associated object account is complete, the condition of missing cannot exist, and the accuracy of the sequencing display result of the terminal is ensured.

Description

Object sorting method, device, equipment, medium and product

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, a medium, and a product for object sorting.

Background

In network social contact, a scene that a plurality of friend accounts of an object need to be displayed in a sequencing mode often exists, and the sequencing display is generally performed on the basis of a target service index for measuring interaction conditions between the object and the friend accounts.

In the related technology, when a terminal displays a plurality of friend account numbers in a sorted manner, because the number of account numbers that can be displayed on each page is limited, page display may be performed, and each time the account number on the current page is displayed, the terminal needs to query again from a database based on target service indexes of the displayed account number and the like so as to further obtain the friend account number displayed on the next page.

However, in the above scheme, when a large number of accounts with the same target service index exist in the plurality of friend accounts, and when a next batch of friend accounts are obtained based on the target service index of the displayed accounts, it is likely that the obtained friend accounts are less than the friend accounts which should be actually displayed, so that the sequencing display result of the terminal is inaccurate.

Disclosure of Invention

The embodiment of the application provides an object sorting method, an object sorting device, equipment, a medium and a product, which can avoid the condition that the inquired associated object account number is missing and ensure the accuracy of the sorting display result of a terminal. The technical scheme is as follows:

in one aspect, an object sorting method is provided, and the method includes:

receiving a related object account display request of a terminal aiming at an object account, wherein the related object account display request indicates that the related object account of the object account is subjected to sequencing display of a target sequencing mode according to a target service index;

based on the associated object account number display request, acquiring a unique key serving as a query starting point, wherein the unique key comprises a target service index of the associated object account number and a self-added global unique identifier in a database;

taking the target service index in the unique key as a query starting point as a starting point, and acquiring a plurality of associated object account numbers which accord with the associated object account number display request from the database;

and outputting the plurality of associated object accounts to the terminal according to the sequencing order of the plurality of associated object accounts.

In some embodiments, the obtaining the unique key as the query starting point based on the related object account number exposure request includes any one of the following cases:

responding to the unique key not carried by the associated object account number display request, and acquiring the unique key which accords with the target sorting mode from the database;

and responding to the unique key carried by the associated object account number display request, and acquiring the unique key from the associated object account number display request.

In some embodiments, the obtaining, from the database, a plurality of associated object accounts meeting the associated object account presentation request with the target service indicator in the unique key as the query starting point includes:

acquiring a plurality of associated object account numbers from the database based on the target service index in the unique key as the query starting point, wherein the numerical relationship between the target service index in the unique key of the associated object account number and the target service index in the unique key as the query starting point conforms to the associated account number display request;

and if the plurality of associated object account numbers have associated object account numbers with the same target service index, determining the sequencing sequence of the plurality of associated object account numbers based on the global unique identification in the unique key.

In some embodiments, if there is an associated object account with an equal target service indicator in the plurality of associated object accounts, determining the sorting order of the plurality of associated object accounts based on the globally unique identifier in the unique key includes:

if the associated object account numbers with the same target service index exist in the associated object account numbers, comparing global unique identifications in the unique keys of the associated object account numbers from high order to low order, and determining the sequencing order of the associated object account numbers based on the comparison result.

In some embodiments, the method further comprises:

creating a unique key of the associated object account for the associated object account of the object account;

and updating the unique key of the associated object account based on the target behavior between the object account and the associated object account, wherein the target behavior is associated with the target service index.

In some embodiments, the global unique identifier that is self-added to the database includes: at least one of a time increment representing a difference between the creation time of the unique key and a reference time, a machine node identification representing a machine node that created the unique key, and a serial number representing a task request to create the unique key.

In some embodiments, the creating a unique key of the associated object account for the associated object account of the object account includes:

responding to a task request for creating a unique key of the associated object account, acquiring the time increment based on the receiving time of the task request for creating the unique key and the reference time, acquiring the machine node identifier, and acquiring a serial number of the task request;

and carrying out bit operation on the target service index, the time increment, the machine node identification and the serial number of the associated object account to obtain a unique key of the associated object account.

In some embodiments, the obtaining the machine node identification comprises:

and acquiring the maximum machine node identifier in the local cache of the server as the machine node identifier.

In some embodiments, the obtaining the sequence number of the task request includes:

locally acquiring the receiving time and the current time of the last task request and the sequence number of the last task request from the server;

if the receiving time of the last task request is the same as the current time, setting the sequence number of the task request as the last sequence number plus 1;

and if the receiving time of the last task request is different from the current time, setting the sequence number of the task request to be 0.

In some embodiments, the target behavior includes any kind of interaction behavior between object accounts, and the target service index is used for measuring interaction conditions between object accounts.

In some embodiments, the updating the unique key of the associated object account based on the target behavior between the object account and the associated object account comprises:

responding to a task request for updating the unique key of the associated object account, and acquiring the unique key of the associated object account in the database;

and updating the target service index in the unique key of the associated object account in the database based on the target service index of the associated object account.

In one aspect, an apparatus for object sorting is provided, the apparatus comprising:

the system comprises a receiving unit, a processing unit and a display unit, wherein the receiving unit is configured to execute a related object account display request of a receiving terminal for an object account, and the related object account display request indicates that the related object account of the object account is subjected to sequencing display in a target sequencing mode according to a target service index;

a first obtaining unit, configured to execute a presentation request based on the associated object account, and obtain a unique key as a query starting point, where the unique key includes a target service index of the associated object account and a self-added global unique identifier in a database;

a second obtaining unit, configured to obtain, from the database, a plurality of related object accounts meeting the related object account display request, starting from the target service index in the unique key serving as the query starting point;

an output unit configured to perform output of the plurality of associated object accounts to the terminal in an order of the plurality of associated object accounts.

In some embodiments, the first obtaining unit is configured to perform any one of the following steps:

In some embodiments, the second obtaining unit comprises:

a first obtaining subunit, configured to perform obtaining, from the database, a plurality of associated object account numbers based on the target service index in the unique key serving as the query starting point, where a numerical relationship between the target service index in the unique key of the associated object account number and the target service index in the unique key serving as the query starting point conforms to the associated account number display request;

and the second acquisition subunit is configured to execute, if the plurality of associated object accounts have associated object accounts with the same target service index, determining a sorting order of the plurality of associated object accounts based on the global unique identifier in the unique key.

In some embodiments, the second obtaining subunit is configured to perform:

In some embodiments, the apparatus further comprises:

a creating unit configured to execute creating a unique key of an associated object account for the object account;

and the updating unit is configured to execute a target behavior based on the object account and the associated object account, and update the unique key of the associated object account, wherein the target behavior is associated with the target service index.

In some embodiments, the creating unit includes:

a third acquisition subunit configured to execute a task request in response to creating a unique key of the associated object account;

a fourth acquiring subunit configured to execute acquiring the time increment based on the reception time of the task request for creating the unique key and the reference time;

a fifth obtaining subunit configured to perform obtaining the machine node identifier;

a sixth obtaining subunit configured to perform obtaining the serial number of the task request;

and the operation subunit is configured to perform bit operation on the target service index of the associated object account, the time increment, the machine node identifier and the serial number to obtain a unique key of the associated object account.

In some embodiments, the fifth obtaining subunit is configured to perform obtaining the largest machine node identifier in the server local cache as the machine node identifier.

In some embodiments, the sixth obtaining subunit is configured to perform:

In some embodiments, the update unit is configured to perform:

In one aspect, a computer device is provided, the computer device comprising: one or more processors; a memory for storing the processor executable program code; wherein the processor is configured to execute the program code to implement the object sorting method described above.

In one aspect, a computer-readable storage medium is provided, in which program code is enabled, when executed by a processor of a server, to perform an object sorting method as described above.

In one aspect, a computer program product is provided, which when executed by a processor implements the object ordering method described above.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

Fig. 1 is a schematic diagram of an implementation environment of an object sorting method according to an embodiment of the present application;

FIG. 2 is a flowchart of an object sorting method according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of an object sorting method according to an embodiment of the present application;

FIG. 4 is a flow chart of creating and updating a unique key according to an embodiment of the present application;

FIG. 5 is a logic flow diagram for creating a unique key according to an embodiment of the present application;

FIG. 6 is a flowchart for creating and updating a unique key according to an embodiment of the present application

Fig. 7 is a schematic structural diagram of an object sorting apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

In this application, the terms "first," "second," and the like are used for distinguishing identical or similar items with substantially identical functions and functionalities, and it should be understood that "first," "second," and "n" have no logical or temporal dependency, and no limitation on the number or execution order. It will be further understood that, although the following description uses the terms first, second, etc. to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, the first acquisition unit can be referred to as a second acquisition unit, and similarly, the second acquisition unit can be referred to as a first acquisition unit, without departing from the scope of various such examples. The first acquisition unit and the second acquisition unit can both be acquisition units, and in some cases, can be separate and distinct acquisition units.

The term "at least one" in the present application means one or more, and the term "a plurality" in the present application means two or more, for example, a plurality of associated object account numbers means two or more associated object account numbers.

It is to be understood that the terminology used in the description of the various examples herein is for the purpose of describing particular examples only and is not intended to be limiting. As used in the description of the various examples and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The term "and/or" is an associative relationship that describes an associated object, meaning that three relationships can exist, e.g., a and/or B, can mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in the present application generally indicates that the former and latter related objects are in an "or" relationship.

It should also be understood that, in the embodiments of the present application, the sequence numbers of the respective processes do not mean the execution sequence, and the execution sequence of the respective processes should be determined by the functions and the inherent logic thereof, and should not constitute any limitation to the implementation process of the embodiments of the present application.

It should also be understood that determining B from a does not mean determining B from a alone, but can also determine B from a and/or other information.

It will be further understood that the terms "Comprises," "Comprising," "inCludes" and/or "inCluding," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "if" may be interpreted to mean "when" ("while" or "upon") or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined." or "if [ a stated condition or event ] is detected" may be interpreted to mean "upon determining.. or" in response to determining. "or" upon detecting [ a stated condition or event ] or "in response to detecting [ a stated condition or event ]" depending on the context.

It should be noted that information (including but not limited to user equipment information, user personal information, etc.), data (including but not limited to data for analysis, stored data, presented data, etc.), and signals referred to in this application are authorized by the user or sufficiently authorized by various parties, and the collection, use, and processing of the relevant data is required to comply with relevant laws and regulations and standards in relevant countries and regions. For example, the object account and related information referred to in this application are obtained under sufficient authorization.

Fig. 1 is a schematic diagram of an implementation environment of an object ranking method according to an embodiment of the present application, and referring to fig. 1, the implementation environment may include a terminal 101 and a server 102.

The terminal 101 is connected to the server 102 through a wireless network or a wired network. Optionally, the terminal 101 is a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart television, and the like, but is not limited thereto. The terminal 101 is installed and running with an application that supports object ranking, for example, a social-class application, a short-video-class application, or other type of application.

The server 102 is a server cluster or a distributed system formed by a plurality of physical servers, or is a cloud server that provides basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, a cloud storage, a web service, cloud communication, a middleware service, a domain name service, a security service, a Content Delivery Network (CDN), a big data and artificial intelligence platform, and the like. The server 102 provides background services for applications running on the terminal 101.

Also included in the implementation environment is a database 103. The database 103 stores data related to objects, for example, related object accounts of the object accounts and information between objects.

Those skilled in the art will appreciate that the number of the terminals 101 and the servers 102 can be greater or smaller. For example, there can be only one terminal 101 or one server 102, or several tens or hundreds of terminals 101 or servers 102, or more, and the number of terminals or servers and the type of the device are not limited in the embodiment of the present application.

After the implementation environment of the embodiment of the present application is described, an application scenario of the embodiment of the present application will be described below with reference to the implementation environment, and in the following description, the terminal is the terminal 101 in the implementation environment, and the server is the server 102 in the implementation environment.

The technical scheme provided by the embodiment of the application can be applied to any scene needing object account display, for example, under the condition that the associated object account is a friend account, the object account can click and view a friend list on a terminal to trigger the server to sort the friend accounts of the object account, and the server carries out sort display based on the received friend accounts, at the moment, the target service index according to which the display is carried out can be used for expressing the bidirectional behavior between objects; for another example, when the associated object account is an attention account, the object account may click and view an attention list on the terminal to trigger the server to sort the attention account of the object account, and perform sorting display based on the received attention account, at this time, a target service index according to which the display is performed may be used to represent an attention behavior of the object account with respect to the attention account, such as a unidirectional behavior of browsing and the like, which is not limited in this embodiment of the present application.

Of course, the technical solution provided in the embodiment of the present application can be applied to other scenes in which objects are sorted besides the above-mentioned several scenes, and the embodiment of the present application does not limit this.

The technical solutions provided by the present disclosure are described next. Fig. 2 is a flowchart of an object sorting method provided in an embodiment of the present application, and referring to fig. 2, taking the execution of the method by the server 102 as an example, the method includes the following steps:

in step 201, a related object account display request of the terminal for the object account is received, where the related object account display request indicates that a target ranking manner is performed on the related object account of the object account according to the target service index.

In step 202, based on the related object account number display request, a unique key serving as a query starting point is obtained, where the unique key includes a target service index of the related object account number and a self-added global unique identifier in the database.

In step 203, a plurality of related object accounts meeting the related object account display request are obtained from the database with the target service index in the unique key as the query starting point as the starting point.

In step 204, the plurality of association object accounts are output to the terminal in the order of the plurality of association object accounts.

According to the technical scheme provided by the embodiment of the application, after a request for carrying out sequencing display on the associated object account numbers is received, the database is inquired by using the unique key, and a plurality of associated object account numbers which accord with the request are output to the terminal according to the sequencing sequence. The unique key comprises a target business index and a self-increment global unique identifier in the database, so that when the target business indexes are equal, the value of the unique key is ensured to be globally unique by utilizing the self-increment property of the global unique identifier, the value of the unique key at the initial point of inquiry in the requests of different batches cannot be repeated, the inquired associated object account is complete, the condition of missing cannot exist, and the accuracy of the sequencing display result of the terminal is ensured.

In the embodiment of the application, in the sequencing display process, the sequencing display process may be performed based on a cursor mechanism, a position of an adopted cursor may be represented by a unique key of an associated object account, for the associated object account of the object account, a unique key is created for the associated object account to uniquely identify the associated object account, and the unique key includes a target service index of the associated object account and an incremental global unique identifier in a database. In order to more clearly illustrate the components of the unique key, table 1 is a composition manner of the unique key of the associated object account provided in the embodiment of the present application, as shown in table 1, the unique key is composed of five parts, the components in the unique key are, from left to right, a fixed symbol identifier, a target service index of the associated object account, and a self-added global unique identifier in a database, where the self-added global unique identifier in the database includes: time increment, machine node identification, and sequence number. The fixed symbol identifier is used for indicating that the unique key is a positive number, the target service index of the associated object account is used for measuring the interaction condition between the object account and the associated object account, the time increment is used for indicating the time when the unique key is applied, namely the difference value between the creation time of the unique key and the reference time, the machine node identifier is used for indicating a machine node for creating the unique key, and the serial number is used for indicating a task request for creating the unique key. The component presses in the unique key from left to right can be viewed as going from high to low.

In some embodiments, each component is represented by a binary number, the fixed symbol identifier occupies 1 bit, and the target traffic indicator occupies 20 bits.

In some embodiments, the number of bits of the time increment determines the time limit to which the unique key can be applied, and the technician can set the number of bits of the time increment as desired. In some embodiments, this time increment takes 28 bits and can support applications for up to about 8.7 years.

In some embodiments, the machine node is associated with the number of server starts, the number of bits of the machine node identifier determines the number of server starts supported by the unique key, and a technician can set the number of bits of the machine node identifier according to requirements. In some embodiments, the machine node identification takes 22 bits and can support up to about 420 ten thousand server boots.

In some embodiments, the number of bits of the serial number determines the number of concurrent requests that can be processed by the server per second, and the technician can set the number of bits of the serial number according to the requirement. In some embodiments, the sequence number occupies 13 bits and can support up to 8129 concurrent requests per second.

TABLE 1

It is understood that the unique key may be stored in a database in a list of associated object account numbers of the object account number, and the specific storage form of the unique key may be an attribute of the associated object account number, and the associated object account number further has other attributes, such as a target service index, a nickname of the associated object account number, interaction history of the object account number and the associated object account number, and other related information.

After the implementation environment and the application scenario of the embodiment of the present application are introduced, an execution subject is taken as an example, and a technical solution provided by the embodiment of the present application is introduced below. Fig. 3 is a flowchart of an object sorting method provided in an embodiment of the present application, and as shown in fig. 3, a technical solution provided in the embodiment of the present application includes the following steps:

in step 300, the terminal responds to a related object account display instruction of the object account, and sends a related object account display request to the server, where the related object account display request indicates that a target sorting manner is performed on the related object account of the object account according to a target service index.

The target service index is used for measuring the interaction condition between the object accounts based on the target behavior. For example, the target service index may be used to measure a bidirectional behavior between the object account and the friend account when the associated object account is the friend account, and the target service index may be used to measure an attention behavior of the object account with respect to the attention account when the associated object account is the attention account, which is not limited in this embodiment of the present application. The target behavior includes any one of interaction behaviors between the object account numbers, which may be positive behaviors such as praise, concern, comment, and browse, or negative behaviors such as canceling concern, pulling in a blacklist, and deleting an account number between the object account number and the associated object account number, and this is not limited in the embodiment of the present application.

The target sorting mode is used for indicating the sequence according to which the associated object account numbers are sorted and displayed. For example, the target ranking mode may be a ranking display according to a target service index from high to low, or a ranking display according to a target service index from low to high, which is not limited in this embodiment of the application. The target sorting mode may be a default sorting mode of the terminal, or may also be a sorting mode set by the object, which is not limited in the embodiment of the present application.

In some embodiments, the related object account display request further indicates to display related information of the related object account, such as a target service index of the related object account, a time of a last interaction with the object account, and the like, so as to provide more reference information for the object and enrich the displayed content.

Under the condition that paging display is needed, the number of objects which can be displayed on each page of the terminal is limited, and the terminal can request a certain number of related object accounts to display each time. Therefore, the terminal triggers a related object account displaying instruction of the object account when a page needs to be displayed each time based on the operation of the object on the terminal, so as to send a request to the server for multiple times, and request the related object account to be displayed in the page in batches. In step 300, the related object account displaying instruction may be a displaying instruction for a first page, or may be a displaying instruction for another page, which is not limited herein.

In step 301, the server receives a request for displaying an associated object account of the terminal with respect to the object account.

In some embodiments, the display request of the associated object account is triggered based on the display of the first page, and the request does not carry a unique key used as a starting point of the query. In some embodiments, the display request of the associated object account is triggered based on the display of a page other than the first page, where the request carries a unique key serving as a query starting point, and the unique key is a unique key of the last associated object account received by the terminal based on the last request.

In step 302, in response to the unique key not carrying as a query starting point in the associated object account number display request, the server obtains the unique key conforming to the target sorting manner from the database.

It can be understood that, when the associated object account number display request does not carry a unique key serving as a query starting point, the server can determine the unique key corresponding to the current display according to a target sorting mode. And if the target sorting mode is displayed in a descending order according to the target service index, the server compares the unique keys of the associated object account of the object account from the high order to the low order in the associated object account list of the object account in the database to determine the unique key with the maximum value, and the unique key with the maximum value is used as the unique key of the query starting point. If the target sorting mode is displayed according to the ascending order of the target service index, the server compares the unique keys of the associated object account of the object account from the high order to the low order in the associated object account list of the object account in the database to determine the unique key with the minimum value, and the unique key with the minimum value is used as the unique key of the query starting point.

In step 303, in response to the associated object account number display request carrying a unique key as a starting point of the query, the server obtains the unique key from the associated object account number display request.

It can be understood that, when the associated object account number display request carries a unique key serving as a query starting point, the server can parse the unique key from a target field of the associated object account number display request to serve as the query starting point.

The

above steps

302 and 303 are two possible implementation scenarios in which the server obtains a unique key as a starting point of the query based on the associated object account number presentation request.

In step 304, the server obtains a plurality of associated object account numbers from the database based on the target service index in the unique key as the query starting point, wherein the numerical relationship between the target service index in the unique key of the associated object account number and the target service index in the unique key as the query starting point conforms to the associated account number display request.

In the embodiment of the application, if the terminal requests descending display, the server sends a query instruction to the database according to the unique key serving as a query starting point, the query instruction is used for querying the associated object account numbers of which the unique key is smaller than the unique key, when querying is carried out according to the query instruction, the associated object account numbers are preferentially sorted in descending order from big to small according to the target service indexes in the unique key, and the server obtains a plurality of associated object account numbers of which the target service indexes are sorted in the front target digit number based on the sorting result. And the target digit is more than or equal to the number of the object accounts which can be displayed on each page. If the terminal requests ascending display, the server sends a query instruction to the database according to the unique key serving as a query starting point, the query instruction is used for querying the associated object account numbers of which the unique key is larger than the unique key, when the query is carried out according to the query instruction, the associated object account numbers are preferentially sorted in ascending order from small to large according to the target service indexes in the unique key, and the server obtains a plurality of associated object account numbers of which the target service indexes are sorted in the front target digit number based on the sorting result.

Referring to table 1, for the unique key, the target service index is located at a higher position of the unique key than the global unique identifier, in this embodiment of the application, the target service index located at the higher position is preferentially compared, when the target service index cannot meet the requirement of sorting, that is, when the target service indexes are equal, the size sorting cannot be implemented, and the global unique identifier located at the lower position is continuously compared to perform further sorting.

In step 305, if there are associated object accounts with the same target service index in the plurality of associated object accounts, the server determines a sorting order of the plurality of associated object accounts based on the globally unique identifier in the unique key.

In this embodiment of the present application, if there are associated object accounts with the same target service index in the plurality of associated object accounts, for the associated object accounts with the same target service index, the server compares global unique identifiers at a low level in the unique keys thereof from a high level to a low level, and determines a sorting order of the plurality of associated object accounts based on a comparison result.

In some embodiments, if the terminal requests descending presentation, after obtaining the multiple associated object accounts based on step 304, the server sorts the associated object accounts with equal target service indexes in descending order according to the descending order of the global unique identifiers in the unique keys, where, referring to table 1, the global unique identifiers include time increments, machine node identifiers, and serial numbers from high order to low order, preferentially sort the associated object accounts according to the descending order of the time increments in the global unique identifiers, sort the associated object accounts according to the descending order of the machine node identifiers when the time increments are equal, and sort the associated object accounts according to the descending order of the serial numbers when the machine node identifiers are equal, to obtain the comparison result.

In some embodiments, if the terminal requests ascending presentation, after the server obtains the plurality of associated object accounts based on step 304, for the associated object accounts with the same target service index, the associated object accounts are sorted in ascending order from small to large according to the global unique identifier in the unique key, so as to obtain a comparison result. The sorting process is the same as the descending sorting process, and is not described herein.

Steps 304 to 305 are an implementation manner of the server obtaining a plurality of associated object accounts meeting the associated object account display request from the database with the target service index in the unique key as the query starting point as the starting point.

In step 306, the server outputs the plurality of associated object accounts to the terminal according to the sorted order of the plurality of associated object accounts.

In some embodiments, the server outputs the associated object accounts in a sorted order using a cursor mechanism. The specific process of the cursor mechanism is that for each associated object account number in the associated object account numbers, when the cursor points to the associated object account number, the server acquires the associated object account number and the position of the cursor at the moment, assigns an acquired result to a main variable, wherein the main variable is a variable parameter in an operating program of the server, and the server transmits the acquired result to the terminal by using the operating program. Here, the position of the cursor is also the position of the associated object account, and can be represented by a unique key of the associated object account.

In some embodiments, the associated object account display request further indicates to display related information of the associated object account, and the server outputs the associated object account and related information thereof in a sorting order by using a cursor mechanism.

In step 307, the terminal receives the multiple related object accounts transmitted by the server, and displays the multiple related object accounts in a display interface according to a sorting order.

In some embodiments, the terminal stores the last cursor position of the query, that is, the position of the last associated object account of the query, and when the terminal needs to continue page display based on the display result, the terminal carries the stored cursor position in a new request and sends the new request to the server, and the server can determine the unique key serving as the starting point of the query in the query according to the cursor position in the request.

In some embodiments, when the terminal needs to display the target service index of the associated object account, the terminal analyzes the unique key of the associated object account through bit operation to obtain the target service index of the associated object account, displays the associated object account and the corresponding target service index on a display interface, and performs analysis based on the unique key, so that multiple interactions with a server can be avoided, and the interaction pressure between the terminal and the server is reduced. In addition, the database can also store the target service index in a unique key mode instead of storing the target service index separately, so that the storage data volume is reduced, and the storage pressure is reduced.

According to the technical scheme provided by the embodiment of the application, after a request for sequencing and displaying the associated object accounts is received, the database is inquired by using the unique key, and a plurality of associated object accounts which accord with the request are output to the terminal according to the sequencing sequence. The unique key comprises a target business index and a self-increasing global unique identifier in the database, so that when the target business indexes are equal, the value of the unique key is guaranteed to be globally unique by utilizing the self-increasing property of the global unique identifier, the value of the unique key at the initial point of query in requests of different batches cannot be repeated, the account number of the queried associated object is complete, the condition of loss cannot exist, and the accuracy of the sequencing display result of the terminal is guaranteed.

Fig. 4 is a flowchart of a process for creating and updating a unique key according to an embodiment of the present application, fig. 5 is a flowchart of a logic for creating a unique key according to an embodiment of the present application, and fig. 6 is a flowchart of a process for creating and updating a unique key according to an embodiment of the present application. In order to more clearly illustrate the process of creating and updating the unique key of the associated object account, referring to fig. 4, 5 and 6, the technical solution regarding the unique key includes the following steps:

in step 401, the server receives a task request to create a unique key for the associated object account.

In some embodiments, after the object account and the associated object account establish a social relationship for the first time, the terminal sends a task request for creating a unique key of the associated object account to the server. The social relationship may be a friend relationship, an attention relationship, and the like, which is not limited in the embodiment of the present application.

In step 402, the server obtains a target service index of the associated account.

In some embodiments, for an associated object account for which the server does not already store a target behavior, a target business indicator can be initialized. Optionally, the initialization process is to configure a default value for the target service index, and optionally, the initialization process is performed based on target behaviors of the object account and the associated object account before the social relationship is not established, for example, comment behaviors have occurred between two object accounts when the social relationship is not established, and the target service index may be obtained based on such comment behaviors. In some embodiments, when the target business index is obtained based on the target behavior occurring when the social relationship is not established, the conversion manner may be different from the conversion manner after the social relationship is established, for example, the configured score is lower, and the like.

In step 403, the server acquires a time increment based on the reception time of the task request for creating the unique key and the reference time.

The server obtains the receiving time of the task request from the local, and obtains the time increment by making a difference between the receiving time and a reference time, wherein the reference time is a certain past time point set by a technician. The reference time is determined, so that along with time change, the numerical value of the time increment acquired when the unique key of the associated object account is created is continuously increased, the time increment of the unique key of the associated object account created at different times cannot be repeated, and the time increment acquired in the way can be used for measuring the sequence of the time for establishing the relationship between the object account and different associated object accounts.

In step 404, the server obtains the machine node identification.

And the server acquires the maximum machine node identifier in the local cache as the machine node identifier. The machine node mark is a numerical value which is automatically distributed by the database and stored in a local cache after the server is started every time. Due to the self-increment of the main key of the database, the database can be ensured to distribute different machine node identifiers to each server, and the numerical values of the machine node identifiers are automatically increased, so that the situation that the machine node identifiers are repeated cannot occur.

In step 405, the server obtains the serial number of the task request.

The server receives a plurality of task requests within one second, and in order to identify the plurality of task requests which are concurrent within the one second, the server assigns a serial number to each task request in the plurality of task requests within the one second, and the serial number automatically increases according to the sequence of the receiving time of the task requests within the one second, so that the serial number of the task requests received within the one second by the server cannot be repeated.

In the embodiment of the present application, the plurality of task requests refer to task requests for creating a unique key for an associated object account of any object account in the database, and are not limited to the associated object account of the object account.

Wherein, the step of obtaining the serial number is as follows: the server obtains the receiving time of the last task request, the current time and the sequence number of the last task request from the local, if the receiving time of the last task request is the same as the current time, the sequence number of the last task request is set to be the sequence number of the last task request plus 1, and if the receiving time of the last task request is different from the current time, the sequence number of the last task request is set to be 0. The server locally saves the current time as the time of receipt of the task request.

By executing the above steps 401 to 405, the server may obtain, in response to a task request for creating a unique key of the associated object account, the time increment based on the receiving time of the task request for creating the unique key and the reference time, obtain the machine node identifier, and obtain the serial number of the task request.

In step 406, the server performs bit operation on the target service indicator of the associated object account, the time increment, the machine node identifier, and the serial number to obtain a unique key of the associated object account.

After obtaining the unique key of the associated object account, the server inserts the unique key of the associated object account into an associated object account list of the object account in the database.

In some embodiments, the database opens a binary log, and after the unique key of the associated object account is inserted into the database, the database records the change condition of data in the binary log, so as to facilitate data recovery when the database is stopped unexpectedly.

To describe the logic of creating the unique key of the associated object account for the associated object account of the object account in more detail in steps 401 to 406, referring to fig. 5, after receiving a task request for creating the unique key of the associated object account, the server obtains a target service index of the associated object account, obtains a time increment based on the receiving time of the task request for creating the unique key and the reference time, obtains a machine node identifier based on the maximum machine node identifier in the local cache of the server, obtains a serial number based on the receiving time of the previous task request, the current time and the serial number of the previous task request, and then obtains the unique key by performing a bit operation in step 406.

In some embodiments, for all associated object accounts of the object account, the steps 402 to 406 in the process of creating the unique key of the associated object account are processed by one server separately, so as to avoid the uniqueness of the unique key due to non-uniform time among a plurality of servers.

In step 407, the server receives a task request to update the unique key of the associated object account.

In step 408, the server obtains the unique key of the associated object account in the database.

In this embodiment, the server obtains the unique key from the list of the associated object account of the object account in the database according to the account id of the associated object account.

In step 409, the server updates the target service index in the unique key of the associated object account in the database based on the target service index of the associated object account.

When the server updates the target service index in the unique key, the server may recalculate the current latest value of the target service index, or update the existing target service index based on the amplitude, that is, calculate an index value that needs to be increased or decreased for the target service index each time, which is not limited in the embodiment of the present application. Next, the step 409 will be described based on these two update methods.

In one implementation, the step 409 process includes the following steps a1 through a 2:

in step a1, the server obtains an update amplitude of the target service index of the associated object account based on the target behavior corresponding to the current update.

In some embodiments, updating the target service indicator may refer to updating immediately after the target behavior is detected, or may refer to updating based on a certain update period; accordingly, the target behavior corresponding to the current update in step a refers to the target behavior occurring this time in the case of immediate update, and refers to the target behavior occurring in the current cycle in the case of update based on the update cycle.

In some embodiments, the target behavior may be stored in the form of a message queue, the process comprising: after the target behaviors of the object account and the associated object account occur, the server writes the behavior record based on the target behaviors into a message queue for the associated object account, and the server can read the object account and the target behaviors of the associated object account from the message queue.

In some embodiments, for some interaction situations having a negative effect on the target service index, the target service index may be negatively updated based on the interaction situation, so that the index more accurately reflects an actual interaction situation between the objects, and accordingly, when the server detects that no target behavior occurs between the account numbers of the objects within the target duration, the update amplitude of the target service index is configured as a negative number, so that the target service index is negatively updated based on the update amplitude of the negative number in the following.

It can be understood that, for a plurality of different target behaviors between objects, corresponding weights may be configured, so that when the target business index or the update amplitude of the target business index is calculated, the relationship between the objects can be accurately reflected based on the influence of the different target behaviors on the overall interaction condition.

In some embodiments, the server calculates the update amplitude of the target service index by stepwise applying different algorithms according to the retention time of the relationship between the object accounts. For example, taking two updates of the retention durations T1 and T2 as an example, the magnitudes of the updates calculated based on different algorithms may be different for the same target behavior. If T1 is greater than T2, the calculated update magnitude for T1 is greater than the update magnitude for T2 for the same target behavior. By applying different algorithms in a stepwise manner for the calculation, the contributions of the service indicators of different retention durations of the relationship can be distinguished.

In step a2, the server updates the target service index in the unique key based on the updated amplitude of the target service index to obtain an updated unique key.

When updating based on the update amplitude, the server may perform bit operations based on the target service index and the update amplitude existing in the database to obtain an updated unique key.

In one implementation, the step 409 process includes the following steps B1 through B2:

in step B1, the server obtains the latest value of the target service index of the associated object account based on the historical target behaviors and the target behaviors corresponding to the current update.

The historical target behaviors and the latest target behaviors can be stored in a message queue form, which is not described herein any further.

In some embodiments, the server calculates the target service index by stepwise applying different algorithms according to the duration of the relationship between the object accounts. For example, taking the two updates of the retention time durations T1 and T2 as an example, the target service indicator sizes calculated based on different algorithms may be different for the same target behavior. If T1 is greater than T2, the calculated target service index corresponding to T1 is greater than the target service index corresponding to T2 for the same target behavior. By applying different algorithms in a stepwise manner for the calculation, the contributions of the service indicators of different holding durations of the relationship can be distinguished.

In step B2, the server updates the target business index in the unique key based on the latest value of the target business index to obtain an updated unique key.

In some embodiments, after the server obtains the latest value of the target service index of the associated object account, the server sets the target service index in the unique key to zero, and performs bit operation based on the latest value and the processed unique key to obtain an updated unique key.

In some embodiments, the database opens a binary log, and after the unique key of the associated object account in the database is updated, the database records the change condition of data in the binary log, so as to facilitate data recovery when the database is stopped unexpectedly.

To illustrate the flow of creating and updating unique keys in more detail, see FIG. 6. After the object account and the associated object account establish a social relationship for the first time, the server obtains a target service index of the associated object account, then creates a unique key of the associated object account through a service logic for creating the unique key, inserts the unique key into a database, and the database records data change in a binary log. After the target account and the associated object account are interacted based on the target behavior, the server acquires a target service index based on the target behavior between the object accounts, then updates the unique key of the associated object account through the service logic of the updated unique key, updates the unique key of the associated object account in the database into the updated unique key, and records data change in a binary log by the database.

By applying the technical scheme of creating and updating the unique key, a unique key can be configured for each associated object account of the object account, and the unique key can embody the target service index of the associated object account and cannot be repeated. The unique key may be used to rank the associated object account of the object account, and according to the property that the unique key is not repeated, it may be determined that the result of the ranking is unique.

Fig. 7 is a schematic structural diagram of an object sorting apparatus according to an embodiment of the present application. Referring to fig. 7, the apparatus includes a receiving unit 701, a first acquiring unit 702, a second acquiring unit 703, and an output unit 704.

A receiving unit 701, configured to execute a related object account display request of a receiving terminal for an object account, where the related object account display request indicates that a target ordering manner is performed on a related object account of the object account according to a target service index;

a first obtaining unit 702, configured to execute obtaining, based on the associated object account number display request, a unique key serving as a query starting point, where the unique key includes a target service index of the associated object account number and a global unique identifier added in a database;

a second obtaining unit 703 configured to perform obtaining, from the database, a plurality of related object accounts meeting the related object account display request, with the target service indicator in the unique key as the query starting point as a starting point;

an output unit 704 configured to perform outputting the plurality of association object accounts to the terminal in the order of the plurality of association object accounts.

In some embodiments, the first obtaining unit 702 is configured to perform any one of the following steps:

In some embodiments, based on the apparatus composition of fig. 7, the second obtaining unit 703 includes:

and the second acquisition subunit is configured to execute, if the plurality of associated object accounts have associated object accounts with the same target service index, determining the ordering order of the plurality of associated object accounts based on the global unique identifier in the unique key.

In some embodiments, the second acquisition subunit is configured to perform:

In some embodiments, based on the apparatus composition of fig. 7, the apparatus further comprises:

a creating unit configured to perform creating a unique key of an associated object account for the object account;

In some embodiments, based on the apparatus composition of fig. 7, the creating unit includes:

In some embodiments, the sixth obtaining subunit is configured to perform:

In some embodiments, the updating unit is configured to perform:

It should be noted that: in the object sorting apparatus provided in the above embodiments, only the division of the function modules is illustrated when performing object sorting, and in practical applications, the function distribution may be completed by different function modules according to needs, that is, the internal structure of the computer device is divided into different function modules to complete all or part of the functions described above. In addition, the object sorting method provided by the above embodiment and the object sorting apparatus embodiment belong to the same concept, and specific implementation processes thereof are detailed in the object sorting method embodiment and are not described herein again.

An embodiment of the present application provides a computer device, configured to perform the foregoing method, where the computer device may be implemented as a server, and a structure of the server is described below:

fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application, where the server 800 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs 8 Units) 801 and one or more memories 802, where the one or more memories 802 store at least one computer program, and the at least one computer program is loaded and executed by the one or more processors 801 to implement the object sorting method provided by the foregoing method embodiments. Certainly, the server 800 may further have a wired or wireless network interface, a keyboard, an input/output interface, and other components to facilitate input and output, and the server 800 may further include other components for implementing functions of the device, which are not described herein again.

In an exemplary embodiment, there is also provided a computer-readable storage medium having at least one computer program stored therein, the computer program being loaded and executed by a processor to implement the object sorting method in the above-described embodiments. For example, the computer readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, a computer program product is also provided, comprising a computer program which, when executed by a processor, implements the above object ordering method.

In some embodiments, the computer program according to the embodiments of the present application may be deployed to be executed on one computer device or on multiple computer devices located at one site, or may be executed on multiple computer devices distributed at multiple sites and interconnected by a communication network, and the multiple computer devices distributed at the multiple sites and interconnected by the communication network may constitute a block chain system.

It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be implemented by hardware, or may be implemented by a program controlling the relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method of object ordering, the method comprising:

acquiring a unique key serving as a query starting point based on the associated object account number display request, wherein the unique key comprises a target service index of the associated object account number and a self-added global unique identifier in a database;

and outputting the plurality of associated object accounts to the terminal according to the sequencing sequence of the plurality of associated object accounts.

2. The object sorting method according to claim 1, wherein the obtaining of the unique key as the starting point of the query based on the associated object account number presentation request includes any one of the following cases:

responding to a correlated object account number display request without carrying the unique key, and acquiring the unique key which accords with the target sorting mode from the database;

3. The method according to claim 1, wherein the obtaining a plurality of associated object accounts meeting the associated object account display request from the database with the target business index in the unique key as a query starting point as a starting point comprises:

acquiring a plurality of associated object account numbers from the database based on the target service index in the unique key serving as the query starting point, wherein the numerical relationship between the target service index in the unique key of the associated object account numbers and the target service index in the unique key serving as the query starting point conforms to the associated account number display request;

4. The object sorting method according to claim 3, wherein if there is an associated object account with an equal target service index among the associated object accounts, determining the sorting order of the associated object accounts based on the globally unique identifier in the unique key comprises:

5. The method of object ranking according to claim 1, the method further comprising:

and updating the unique key of the associated object account based on a target behavior between the object account and the associated object account, wherein the target behavior is associated with the target service index.

6. The object ranking method according to claim 1, wherein the global unique identifier of the respective increment in the database comprises: at least one of a time increment representing a difference between the creation time of the unique key and a reference time, a machine node identification representing a machine node creating the unique key, and a serial number representing a task request to create the unique key.

7. An apparatus for object ranking, the apparatus comprising:

a first obtaining unit, configured to execute a display request based on the associated object account, and obtain a unique key serving as a query starting point, where the unique key includes a target service index of the associated object account and a self-added global unique identifier in a database;

a second obtaining unit, configured to perform obtaining, from the database, a plurality of associated object account numbers that meet the associated object account number display request, starting from the target service index in the unique key that is the starting point of the query;

8. A computer device, characterized in that the computer device comprises:

one or more processors;

a memory for storing the processor executable program code;

wherein the processor is configured to execute the program code to implement the object ordering method of any one of claims 1 to 6.

9. A computer-readable storage medium, wherein program code in the computer-readable storage medium, when executed by a processor of a server, enables the server to perform the object ranking method of any of claims 1 to 6.

10. A computer program product comprising a computer program which, when executed by a processor, implements the object ranking method of any of claims 1 to 6.