WO2020024824A1

WO2020024824A1 - Method and device for determining user status identifier

Info

Publication number: WO2020024824A1
Application number: PCT/CN2019/097002
Authority: WO
Inventors: 李伟杰
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2018-07-31
Filing date: 2019-07-22
Publication date: 2020-02-06
Also published as: CN110781375A; CN110781375B

Abstract

The present application provides a method and a device for determining a user status identifier, comprising: providing a plurality of first status identifiers, wherein the plurality of first status identifiers respectively correspond to a plurality of second status identifiers and conversion conditions between the plurality of second status identifiers; receiving a user request; obtaining, according to the user request, a current first status identifier, a current second status identifier, and user attribute information of a user; and determining a target second status identifier of the user according to the current first status identifier, the current second status identifier, the user attribute information, the plurality of first status identifiers, and the conversion conditions between the plurality of second status identifiers corresponding to the plurality of first status identifiers. The invention performs status identifier authorization in multiple dimensions, data structures of the plurality of second status identifiers and the conversion conditions between the plurality of second status identifiers corresponding to the first status identifiers are simple, and the amount of codes thereof are small, increasing the response speed of user status identifier determination.

Description

Method and device for determining user status identifier

This application claims priority from a Chinese patent application filed on July 31, 2018 with an application number of 201810856553.5 and an invention name of "a method and device for determining user status identification", the entire contents of which are incorporated herein by reference.

Technical field

The present application relates to the field of information technology, and in particular, to a method and device for determining a user status identifier.

Background technique

In the context of large-scale application of wireless applications, for multi-country and multi-market services, it is usually necessary to identify the status of users in order to provide targeted services to users based on the status of users to achieve the effect of optimizing the user experience.

At present, there are two specific implementation methods for identifying the status of a user. The first method is to directly update the status of the user to a status that matches the grouping property according to the grouping attribute corresponding to the user. If the user is logging in for the first time, the user is updated. Label the status of the first login. The second is to establish a user identification system with at least three dimensions of market, condition, and status, and implement a logic of user status identification through a large number of if, if-else and other script statements based on JavaScript. The geographic location information of the user determines the market in which the user is located, further determines the status of the user based on the user behavior information of the user, and binds the status to the user to determine the status of the user.

However, during the research process, the inventors found that in the first solution, there are too few judgment conditions based on the user status, and the available condition dimension is too low, which makes the determination of the user status inaccurate. In the second solution, A large number of JavaScript code statements to implement multi-dimensional user state identification will cause too much code, tedious processing logic, and low processing efficiency.

Summary of the invention

In view of the above problems, an embodiment of the present application provides a method for determining a user status identifier. This application provides multiple first status identifiers, and the multiple first status identifiers correspond to multiple second status identifiers and multiple second status identifiers, respectively. Conversion conditions between; receiving a user request; obtaining the user ’s current first state identifier, current second state identifier, and user attribute information according to the user request; according to the current first state identifier, current second state identifier, and user attribute information, And transition conditions between the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers to determine a target second state identifier of the user. The purpose of verifying the status identifier in multiple dimensions is achieved, and the data structure of the transition conditions between the multiple second status identifiers corresponding to the first status identifier and the multiple second status identifiers is simple, and the amount of code is small, making the user status The response speed of the identification is relatively fast, which solves the problems of cumbersome processing logic and low processing efficiency in the prior art.

Correspondingly, an embodiment of the present application further provides a user status identifier determining device, which is used to ensure the implementation and application of the foregoing method.

In order to solve the above problem, an embodiment of the present application discloses a method for determining a user status identifier, including:

Providing multiple first status identifiers, the multiple first status identifiers corresponding to multiple second status identifiers and transition conditions between the multiple second status identifiers, respectively;

Receiving user requests;

Acquiring, according to the user request, a current first state identifier, a current second state identifier, and user attribute information of the user;

According to the current first state identifier, the current second state identifier, the user attribute information, and the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers A transition condition between determining a target second state identifier of the user.

Correspondingly, an embodiment of the present application further discloses a device for determining a user status identifier, including:

A providing module, configured to provide multiple first status identifiers, where the multiple first status identifiers correspond to multiple second status identifiers and transition conditions between the multiple second status identifiers;

A receiving module for receiving a user request;

An obtaining module, configured to obtain a current first state identifier, a current second state identifier, and user attribute information of the user according to the user request;

A determining module, configured to: according to the current first state identifier, the current second state identifier, the user attribute information, and multiple corresponding ones of the multiple first state identifiers and the multiple first state identifiers A transition condition between the second state identifiers determines a target second state identifier of the user.

Correspondingly, an embodiment of the present application further discloses a device, including:

One or more processors; and

One or more machine-readable media having instructions stored thereon, when executed by the one or more processors, cause the device to execute a method for determining a user status identifier.

Correspondingly, the embodiment of the present application also discloses one or more machine-readable media having instructions stored thereon, which when executed by one or more processors, cause the device to execute a method for determining a user status identifier.

The embodiments of the present application include the following advantages:

The embodiment of the present application includes: providing a plurality of first status identifiers, each of which corresponds to a plurality of second status identifiers and a transition condition between a plurality of second status identifiers; receiving a user request; Request to obtain the user ’s current first state identifier, current second state identifier, and user attribute information; according to the current first state identifier, current second state identifier, user attribute information, and multiple first state identifiers, multiple first A transition condition between a plurality of second state identifiers corresponding to the state identifiers determines a target second state identifier of the user. The purpose of verifying the status identifier in multiple dimensions is achieved, and the data structure of the transition conditions between the multiple second status identifiers corresponding to the first status identifier and the multiple second status identifiers is simple, and the amount of code is small, making the user status The response speed of the identification is relatively fast, which solves the problems of cumbersome processing logic and low processing efficiency in the prior art.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system architecture diagram of a method for determining a user status identifier according to an embodiment of the present application; FIG.

2 is a system interaction diagram of a method for determining a user status identifier according to an embodiment of the present application;

3 is a flowchart of steps of a method for determining a user status identifier at a system level according to an embodiment of the present application;

4 is a schematic diagram of a state condition query table of a state machine according to an embodiment of the present application;

5 is a flowchart of specific steps of a method for determining a user status identifier at a system level according to an embodiment of the present application;

FIG. 6 is a flowchart of specific steps of another method for determining a user status identifier at a system level according to an embodiment of the present application; FIG.

7 is a configuration file data structure diagram under a two-dimensional precondition provided by an embodiment of the present application;

FIG. 8 is a structural diagram of an apparatus for determining a user status identifier according to an embodiment of the present application; FIG.

FIG. 9 is a specific structural diagram of an apparatus for determining a user status identifier according to an embodiment of the present application; FIG.

FIG. 10 is a schematic structural diagram of a device according to another embodiment of the present application.

detailed description

In order to make the above-mentioned objects, features, and advantages of this application more comprehensible, the following further describes this application in detail with reference to the accompanying drawings and specific embodiments.

Referring to FIG. 1, which illustrates a system architecture according to an embodiment of the present application, which may include at least:

The business server 10, the configuration center 20, the user attribute data server 30, and the client 40. The business server 10 includes an identification engine 101 and a local data storage 102.

The service server 10 is a server that provides a corresponding personalized service for the client 40 of the user based on the user request. For example, the service server 10 can provide a personalized recommendation to the user and the details of the personalized recommendation. In the embodiment of the present application, In order to distinguish and group the large number of users faced by the business server 10, corresponding status identifiers can be set for the users to group users according to different market attributes and grouping attributes, so that the business server 10 can identify according to the user's status. The client 40 is provided with a service corresponding to the status identification, so as to meet the needs of different users.

It should be noted that when a user logs in to the service server 10 for business access for the first time, a related user account can be established, and a status identifier corresponding to the user account is generated to indicate the current status of the user. The status identifier can be a Status labels, for example, when a user first signs up for an account, a status label of "newcomer" can be displayed near the user's avatar to indicate the "newcomer identity" of the user, and the status identifier can be changed. Updated "newcomer" status label to "loyal users".

Specifically, the service server 10 is provided with a mark engine 101 (Mark Engine) and a local data storage 102 (Local Data). The local data storage 102 may store a status configuration file 201 related to a user status identifier obtained from the configuration center 20, and the status configuration file 201 may store multiple first status identifiers, multiple second status identifiers, and multiple first status identifiers. The transition conditions between the two state identifiers. The identifier engine 101 is an independent thread used to parse the state profile 201 in the local data store 102. Under the current application architecture, it can often be a business plug-in in the business server 10. The service plug-in can load the status configuration file 201 pushed down by the configuration center 20 to update the status of the user.

Configuration Center 20 (Config Server), which often stores various status configuration files 201 used in business services in the form of key-value pairs. The configuration center 20 can update the status configuration file 201 or push the status configuration file 201 to the business. The server 10, wherein the state configuration file 201 stores at least one first state identifier, a plurality of second state identifiers corresponding to the first state identifier, and transition conditions between the plurality of second state identifiers, the first state identifier and The correspondence between the second state identifier and the transition conditions between the plurality of second state identifiers may be written in the form of key-value pairs.

The user attribute data server 30 stores user attribute information and the current second status identifier of each user. The user attribute data is an effective tool for sketching target users, contacting user demands and design directions. User attribute data can enable application products The service object is more focused and more focused. The data source established by the user attribute data server is data related to user behavior generated by the user when using the application product, such as the name, gender, and age filled in by the user's registered account. Information such as location information, geographic location, and browsing history information and behavior information generated by the user in the application. By collecting this information, a user attribute data server 30 including the user can be established. Using the data in the user attribute data server 30, the Determine the user's corresponding market attributes and grouping attributes in the market.

It should be noted that, for the first state identifier, the second state identifier, the transition condition, and the user attribute information in this application, the first state identifier may be a state label used to indicate a dimension attribute of the user. For example, the attributes of the user ’s nationality, region, gender, etc. that do not change during the first time period, the second status identifier can also be a status label, which indicates the attributes of the user in another dimension, such as the user's new / old users, etc. Properties that change during the second time period. The dimensions corresponding to the first status identifier and the dimensions corresponding to the second status identifier may be different dimensions; of course, the specific dimension attributes corresponding to the first status identifier and the second status identifier may be set according to needs, and this embodiment does not change them. Be restricted. The transition condition is a parameter set according to the execution logic of the finite state machine for the purpose of triggering the corresponding second state identifier of the target. The corresponding relationship of the second state identifier + trigger condition = target second state identifier can be set in advance. The subsequent second status identifier is obtained according to the relationship between the second status identifier + the trigger condition; the user attribute information is a type of information generated based on user behavior, such as user browsing records, user behavior records, and the like.

It should be noted that the current first status identifier of the user can correspond to the market dimension, and can be used to divide the market and determine the user's market attributes. Usually, it can be the user ’s nationality or the current geographic location, such as the United States, China, and North China. Region, etc., the user's current first status identifier can be obtained according to the positioning of the user's Internet Protocol (IP, Internet Protocol), or can be obtained according to the registration information entered by the user when registering an account. The user ’s first and second status identifiers can correspond to the grouping dimension, which can be used to divide the grouping and determine the grouping attributes of the user, which is usually the current state of the user. For example, the user ’s "newcomer", "loyal user" and other tags, or XX big promotion "," 20% off consumption "and other service-related tags. User attribute information can be obtained by using some previous user behavior data or user identity data of the user. For example, the user's first login time is within one month and The order has been placed, the user has participated in the XX big promotion, etc., and the current second status identifier of the user can usually be bound to the user identification (ID, identification) to facilitate the use of the user ID to query the corresponding second current status identifier of the user .

Among them, the user's current second state identifier can change continuously as the user's behavior increases, and because the user's market attributes are usually fixed, the chance of change is small, so the user's current first state identifier can be It will not change within a certain time range. For example, the country and region where the user is located usually does not change, or the chance of change is small. User attribute data can be considered as data related to user behavior. User attribute data It will only increase as user behavior increases, which indicates that the nature of user behavior will not change.

Under the trend of global deployment of business services, for multi-country and multi-market businesses, when identifying user status, they will face at least three dimensions: market, condition, and status. The market dimension is used to divide users into specific countries or markets. For example, if a user accesses Russian business, the user will be divided into the Russian market. The condition dimension is used to further group users that are divided into specific markets. The specific implementation is similar to the logic of the finite state machine, including: current state + Condition = next state, by dividing the user into a specific market and updating the state in that market, therefore, the update of the user's current second state identifier in this application can be done using a finite state machine, Finite State Machine (Finite -state machine (FSM), also known as a finite state automaton, or state machine for short, is a mathematical model representing a finite number of states and behaviors such as transitions and actions between these states. Among them, the first state in the state configuration file 201 Identification can correspond to market dimensions, can be used to divide the market, determine the user's market attributes, limited status The state machine is used to obtain the corresponding target second state identifier based on the user's current second state identifier and user attribute data, and to update the target second state identifier to the user's current second state identifier in a specific market group, that is, to further establish User grouping attributes.

Specifically, referring to FIG. 2, a system architecture interaction diagram based on FIG. 2 includes:

Step S1. The configuration center pushes a status configuration file to the service server.

In this step, the configuration center pushes the status configuration file to the service server. The status configuration file may include multiple first status identifiers, multiple second status identifiers corresponding to the multiple first status identifiers, and multiple second status identifiers. The transition conditions between them enable the business server to use the status configuration file to update the corresponding status identifier for the user. In addition, the configuration center can also update the status configuration file and push the updated status configuration file to the business server.

Step S2: The service server receives a user request sent by the client.

When a client user needs to access the business server, the client sends a user request to the business server. The user request can be bound to the user ID (identification) of the corresponding user, and the user ID can be used to query the service server. The current second status identifier of the user, and the current first status identifier and user attribute information of the user. The current first status identifier is used to match the first status identifier in the status configuration file.

Step S3: The service server obtains the current first state identifier, the current second state identifier, and user attribute information of the user according to the user request.

The user ’s current first state identifier, current second state identifier, and user attribute information are obtained by querying the user ID in the user request. Specifically, the current first state identifier and user attribute information are obtained from the user attribute data server according to the user ID. The query is used to update the user status.

Step S4: The service server according to the current first state identifier, the current second state identifier, the user attribute information, and the transition conditions between the multiple first state identifiers and the multiple second state identifiers corresponding to the multiple first state identifiers. To determine the user's target second status identifier.

In this step, by using the current first state identifier as the query KEY and matching the first state identifier KEY in the state configuration file, a value corresponding to the first state identifier KEY can be determined, and the Value can be For the transition conditions between multiple second status identifiers and multiple second status identifiers, the current first status identifier—first status identifier—multiple second status identifiers and multiple second status identifiers can be obtained by matching. Corresponding relationship between conversion conditions, this matching method has the beneficial effects of simple logic, small amount of code, and fast response speed. For example, when a user establishes an account and the nationality entered is Russian, the information can be imported into the user's user attribute information and exists as the current first state identifier. By matching with the first state identifier whose content is Russian, it can quickly Determine a plurality of second state identifiers corresponding to the Russian market and transition conditions between the plurality of second state identifiers.

Further, the status identifier is updated through multiple second state identifiers and transition conditions between multiple second state identifiers. The specific implementation can be implemented by a finite state machine. The implementation logic of the finite state machine is: current state + Condition = next state. For details, refer to Figure 1. The logic of the finite state machine can be embodied in the form of a condition query table. The service server can use the user attribute information as the condition, and the current second state identifier can be used as the current state. The second status identifier is used as the next status to update the current second status identifier of the user. For example, the user attribute information can be the user's login record. Assuming that the user can be divided into loyal user groups after the user logs in 100 times, then when When a user makes a business visit for the 100th time, according to the logic of the state machine, the current second state identifier can be updated from the "newcomer" state to the "loyal user".

S5. The service server provides a corresponding service to the client of the user according to the target second state identifier.

In the embodiment of the present application, after the service server performs status identification / verification on the user based on the three dimensions of market, condition, and status, the service server may provide the user with a business service corresponding to the updated target second status identifier, for example, Users are grouped into loyal users in the Russian market. The service server can provide users with recommendations for members in the Russian market for loyal users to understand the rights and interests of members, and the probability of loyal users to apply for membership is greatly improved compared to new users.

Therefore, this application can provide multiple first status identifiers, and multiple first status identifiers respectively correspond to multiple second status identifiers and transition conditions between multiple second status identifiers; receive user requests; and obtain according to user requests The user's current first state identifier, current second state identifier, and user attribute information; according to the current first state identifier, current second state identifier, user attribute information, and multiple first state identifiers, multiple first state identifiers The transition conditions between the corresponding second state identifiers determine the target second state identifier of the user. The purpose of verifying the status identifier in multiple dimensions is achieved, and the data structure of the transition conditions between the multiple second status identifiers corresponding to the first status identifier and the multiple second status identifiers is simple, and the amount of code is small, making the user status The response speed of the identification is relatively fast, which solves the problems of cumbersome processing logic and low processing efficiency in the prior art.

Referring to FIG. 3, a flowchart of a method for determining a user status identifier at a system level provided in the present application is shown, which may specifically include the following steps:

Step 301: Provide a plurality of first state identifiers, where the plurality of first state identifiers respectively correspond to a plurality of second state identifiers and transition conditions between the plurality of second state identifiers.

In the embodiment of the present application, a plurality of first state identifiers, a plurality of second state identifiers corresponding to the plurality of first state identifiers, and transition conditions between the plurality of second state identifiers may be written into the state configuration file to The configuration file is stored, and the status configuration file can be pushed by the configuration center, and the configuration center can push the configuration file to any business server for its use.

Specifically, based on the current operation of verifying the user ’s current second status identification, there are three dimensions of market, condition, and status. That is, to identify the user status, the market attribute can be determined first, and then the grouping attribute in the market can be further determined. This grouping attribute It is the user ’s changed target second state identifier. Based on the current market rules, market attributes can usually be specific markets, such as country, region, operation type, etc. Grouping attributes can usually use some previous user behavior data of the user. Or obtained from user identity data. For example, if the user's first login time is within one month and an order has been placed, its grouping attribute can be "non-newcomer user", and its status is updated from new to first.

Further, determining a market attribute may be implemented by a first state identifier in a state configuration file, and determining a grouping attribute may be implemented by a second state identifier corresponding to the first state identifier and a transition condition between the second state identifiers, such as establishing Tags of multiple countries, different countries can correspond to different first state identifiers, and establish a corresponding relationship between the corresponding second state identifier and the transition conditions between the second state identifiers for each country to update this country User status in the market. The specific implementation of the transition condition between the first state identifier, the corresponding second state identifier, and the second state identifier in the state configuration file can be achieved through the form of key-value, which can reduce the amount of code and increase the corresponding speed.

Step 302: Receive a user request.

When the user client needs to access the service server, the client sends a user request to the service server. The user request may store the user ID of the corresponding user, and the current second state of the user can be queried by the user ID. The identifier, and the current first state identifier and user attribute information of the user. The current first state identifier is used to match the first state identifier in the state configuration file.

Step 303: Acquire the current first state identifier, the current second state identifier, and user attribute information of the user according to the user request.

In this step, according to the user ID of the corresponding user stored in the user request, the user's current first state identifier and user attribute information of the user under the user ID can be called by accessing the user attribute data server, and the data source established by the user attribute data server It is data related to user behavior generated by the user when using the application, such as data such as identity information entered by the user when establishing an account. The current first state identifier can generally correspond to market attributes, such as the user's nationality, region, etc. The user attribute information can correspond to grouping attributes, such as the user's historical browsing records, user behavior records, and so on.

Further, the user's status identifier can also be bound to the user ID, and the current second status identifier of the user can also be obtained by querying in the status management thread through the corresponding user ID.

Step 304: According to the current first state identifier, the current second state identifier, the user attribute information, and the plurality of first state identifiers and the plurality of first state identifiers corresponding to the plurality of first state identifiers. A transition condition between the two state identifiers determines a target second state identifier of the user.

The identification engine of the service server can determine the transition between multiple second status identifiers corresponding to the first status identifier and multiple second status identifiers by matching the current first status identifier with the first status identifier in the status configuration file. Conditions to obtain the corresponding relationship between the current first state identifier—first state identifier—multiple second state identifiers and multiple second state identifiers. This matching method has simple logic, small amount of code, and response speed Quick beneficial effects. For example, when the user establishes an account, the nationality entered is Russia, and by matching with the first state identifier whose content is Russia, the state machine corresponding to the Russian market can be determined.

When determining a plurality of second state identifiers corresponding to a specific market attribute and a transition condition between the plurality of second state identifiers, at this time, the identification engine of the service server retrieves user attribute information whether the state machine trigger condition is met. If it exists, the target second state identifier is triggered to update the current second state identifier of the user. If it does not exist, when the updated user attribute information is obtained next time, whether the state machine trigger condition is satisfied when retrieving the updated user attribute information, Until the user's current second status identifier is updated.

Referring to FIG. 4, a schematic diagram of a state condition query table of a state machine is shown. The state machine is a mathematical model representing a finite number of states and behaviors such as transitions and actions between the states. The state machine is based on business logic. A trigger logic lookup table of the current state / condition is established. In FIG. 4, three trigger states of state A, state B, and state C, and three trigger conditions of condition 1, condition 2, and condition 3 are shown. It can include state C + condition 1 = state B, which can be expressed as a newcomer state + login times greater than or equal to 100 = loyal user state in combination with business logic.

Based on the current first state identifier and user attribute information, the identification engine of the service server can update the current second state identifier of the corresponding user in the state machine, and the service server can provide the user with the business service corresponding to the updated target second state identifier. For example, if the user is a group of loyal users in the Russian market, the business server can provide users with recommendations for members in the Russian market for loyal users to understand the rights and interests of members, and the probability of loyal users to apply for membership is greatly improved compared to new users. .

In summary, a method for determining a user status identifier provided in an embodiment of the present application includes: providing a plurality of first status identifiers, the multiple first status identifiers corresponding to multiple second status identifiers and multiple second statuses, respectively. Conversion conditions between identities; receiving user requests; obtaining the user's current first state identifier, current second state identifier, and user attribute information according to the user request; according to the current first state identifier, current second state identifier, and user attribute information And transition conditions between multiple first state identifiers and multiple second state identifiers corresponding to the multiple first state identifiers to determine a user's target second state identifier. The purpose of verifying the status identifier in multiple dimensions is achieved, and the data structure of the transition conditions between the multiple second status identifiers corresponding to the first status identifier and the multiple second status identifiers is simple, and the amount of code is small, making the user status The response speed of the identification is relatively fast, which solves the problems of cumbersome processing logic and low processing efficiency in the prior art.

Referring to FIG. 5, a flowchart of specific steps of a system-level user status identifier determination method provided in the present application is shown, which may specifically include the following steps:

Step 501: Provide a status configuration file; in the status configuration file, the first status identifier serves as a key, between a plurality of second status identifiers corresponding to the first status identifier and the plurality of second status identifiers. As the key value.

In the embodiment of the present application, to generate a status configuration file, first, an empty status configuration file file needs to be established for writing configuration data.

Further, KEY = (first state identifier) and Value = (multiple second state identifiers corresponding to the first state identifier and transition conditions between multiple second state identifiers) may be written in the state configuration file, By using the current first state identifier as the query KEY and matching the first state identifier KEY in the state configuration file, the value corresponding to the first state identifier KEY can be determined, and the current first state identifier—first state identifier—multiple The correspondence between the second state identifier and the transition conditions between multiple second state identifiers. This matching method has the beneficial effects of simple logic, small amount of code, and fast response speed.

Optionally, the sub-step 501 may further include a sub-step A1.

Sub-step A1, using the first state identifier as a key, and using a plurality of second state identifiers corresponding to the first state identifier and transition conditions between the plurality of second state identifiers as a key in a notation format of the object Value, the state configuration file is generated as a key-value pair.

In the embodiment of the present application, using the state machine corresponding to the first state identifier in the format of object notation (JSON, JavaScript, Object Notation) as the value can effectively reduce the amount of code and the complexity of the code logic. JSON is a lightweight Data exchange format, which uses a text format that is completely independent of the programming language to store and represent data. The concise and clear hierarchical structure makes JSON an ideal data exchange language that is easy for humans to read and write, and also easy for machines to parse and generate, and is effective To improve network transmission efficiency.

In a specific example, the set of key-value pairs in the state configuration file can be as follows:

Table 1

In Table 1, it is shown that KEY is the corresponding Value in the Russian and Spanish markets, where the state machine Value is implemented in JSON format, and the value is a transition condition between multiple second state identifiers and multiple second state identifiers. The state machine logic is implemented. In the value, capital letters such as A represent states, and lowercase letters such as a represent conditions. The trigger logic includes Russia: state A + condition a = state B. Spain: State A + condition b = state B, etc.

Table 1 shows only the key-value pairs of the state machine corresponding to the one-dimensional first state identifier, and the first state identifier only represents the dimension of the market.

Step 502: Store the state configuration file in a local data store; or, and store the state configuration file in a cache data store.

In this step, when the identification server of the business server obtains the status configuration file, it can store the status configuration file in the local data store for further use next time. In addition, the identification engine can also store the status configuration file in the cache data store. In addition, the identification engine can also store the state configuration file in both the cache data store and the local data store. Compared with the local data store, the speed of extracting the state configuration file from the cache data store is faster, but Cache data storage is usually used to run threads. It is relatively unstable, and when the cache data storage is occupied by too many resources in the state configuration file, it will affect the normal use of business services. Therefore, the state configuration file can also be stored in the local data storage. The local data storage has a larger storage space and more stable storage performance.

Optionally, step 502 may include sub-step 5021.

Sub-step 5021: When a status configuration update file for the status configuration file is obtained, store the status configuration update file in a local data store instead of the status configuration file; or and, update the status configuration The file is stored in a cache data store, replacing the state configuration file.

In the embodiment of the present application, based on the timeliness of the data when the business is conducted by the merchant, the status configuration file needs to be frequently updated to meet its timeliness requirements. At this time, the configuration center can obtain the status configuration update file and push the status configuration update file to Business server, the business server will automatically store the status configuration update file in the corresponding storage, replacing the original status configuration file.

Step 503: Receive a user request.

This step may refer to the above step 302, which is not repeated here.

Step 504: Acquire the current first state identifier, the current second state identifier, and user attribute information of the user according to the user request.

This step may refer to the above step 303, which is not repeated here.

Optionally, the current first state identifier is generated by a user behavior corresponding to a first priority level of the user object, and the user attribute information is generated by a user behavior corresponding to a second priority level of the user object; the first priority level The priority of is greater than the priority of the second priority level.

In the embodiment of the present application, based on determining the corresponding plurality of second state identifiers and the transition conditions between the plurality of second state identifiers through the current first state identifier, the plurality of second state identifiers and the plurality of second state identifiers In the corresponding relationship between the conversion conditions, and then using the business logic of the user attribute information to update the status, it can be determined that the priority of the current first state identifier is greater than the priority of the user attribute information.

For example, this priority can be reflected in the sequence in which user behavior occurs. When a user accesses a web application, he first clicks on the US tab, enters the US page for business access, and performs the corresponding operation. Therefore, the US The tag can determine the user's market attributes, and can be correspondingly generated as the current first state identifier. The corresponding operation performed by the user when entering the US page can determine the user's grouping attribute, and can be correspondingly generated as the user attribute information.

Step 505: Match the current first state identifier with the plurality of first state identifiers, and determine a target transition condition between the plurality of matched second state identifiers and the plurality of matched second state identifiers.

The identification engine of the service server can determine the target transition conditions between multiple matching second status identifiers and multiple matching second status identifiers by matching the current first status identifier with multiple first status identifiers. The first state identifier—the first state identifier—the corresponding relationship of the target transition conditions between the multiple matching second state identifiers and the multiple matching second state identifiers. This matching method has a simple logic, a small amount of code, and a response Fast speed benefits. For example, when the user creates an account, the nationality entered is Russia, and by matching with the first state identifier whose content is Russia, one of the multiple matching second state identifiers and the multiple matching second state identifiers in the Russian market can be determined. Between target transitions.

Optionally, step 505 may further include:

Sub-step 5051: In the state configuration file, use the current first state identifier as a query key, determine a key corresponding to the first state identifier, and a plurality of matching first key corresponding to the first state identifier key. A key value of a target transition condition between the two state identifiers and the plurality of matching second state identifiers.

In the embodiment of the present application, by using the current first state identifier as the query KEY and matching the first state identifier KEY in the state configuration file, the Value corresponding to the first state identifier KEY can be determined and obtained The current first state identifier—the first state identifier—the correspondence between multiple second state identifiers and the transition conditions between multiple second state identifiers. This matching method has the advantages of simple logic, small amount of code, and fast response speed. effect.

Step 506: Match the current second state identifier with the determined plurality of second state identifiers, and match the user attribute information with the target transition condition to determine the target second state identifier.

When determining the state machine corresponding to a specific market attribute, at this time, the identification engine of the business server retrieves whether there is a current second state identifier and user attribute information that meet the trigger conditions of the state machine. If it exists, the target second state identifier is triggered to update If the current second state identifier does not exist, the next time the updated user attribute information is obtained, it is retrieved whether the updated user attribute information satisfies the triggering condition of the state machine until the user's current second state identifier is updated.

Based on the current second state identifier and the user attribute information, the identification engine of the service server can update the current second state identifier of the corresponding user in the state machine, and the business server can provide the user with a business service corresponding to the updated target second state identifier. For example, if the user is a group of loyal users in the Russian market, the business server can provide users with recommendations for members in the Russian market for loyal users to understand the rights and interests of members, and the probability of loyal users to apply for membership is greatly improved compared to new users. .

Optionally, step 506 may further include:

Sub-step 5061, in the key value of the target transition condition between the plurality of matched second state identifiers and the plurality of matched second state identifiers, the current second state identifier and the determined Multiple second state identifiers are matched, and the user attribute information is matched with the target transition condition to determine the target second state identifier.

In the embodiment of the present application, by using the current first state identifier as the query KEY and matching the first state identifier KEY in the state configuration file, the Value corresponding to the first state identifier KEY can be determined and obtained The corresponding relationship between the current first state identifier—first state identifier—multiple second state identifiers and multiple second state identifiers, and then between multiple second state identifiers and multiple second state identifiers In the corresponding relationship of the transition conditions, the state logic is used to update the state by using the trigger logic of the state machine to obtain the updated target second state identifier. This matching method has the beneficial effects of simple logic, small amount of code, and fast response speed.

In summary, a method for determining a user status identifier provided in an embodiment of the present application includes providing a plurality of first status identifiers, and the multiple first status identifiers correspond to multiple second status identifiers and multiple second status identifiers, respectively. Conversion conditions between; receiving a user request; obtaining the user ’s current first state identifier, current second state identifier, and user attribute information according to the user request; according to the current first state identifier, current second state identifier, and user attribute information, And the transition conditions between multiple first status identifiers and multiple second status identifiers corresponding to multiple first status identifiers to determine a user's target second status identifier; this application uses the first status identifier as a key, A state identifier corresponds to a plurality of second state identifiers and a transition condition between the plurality of second state identifiers as values, and a corresponding state configuration file is generated in the form of a key-value pair. A status identifier is matched with the current first status identifier to determine a plurality of second status identifiers corresponding to the status update, and The corresponding relationship of the transition conditions between the plurality of second state identifiers, and then the current second state identifier of the user is updated in the correspondence relationship through the current second state identifier and the user attribute information, thereby implementing in multiple dimensions. The purpose of state identification verification, and the data structure of key-value pairs in the state configuration file is simple, and the amount of code is small, making the state identification verification response faster.

Referring to FIG. 6, there is shown a flowchart of specific steps of another method for determining a user status identifier provided at the system level, which may specifically include the following steps:

In step 601, a state configuration file is provided; in the state configuration file, the first state identifier is used as a key, between a plurality of second state identifiers corresponding to the first state identifier and the plurality of second state identifiers. The transition conditions are used as key values, where the first state identifier includes multiple first state sub-identifiers, and each first state sub-identifier corresponds to a plurality of second state sub-identifiers and between the plurality of second state sub-identifiers, respectively. The condition of the converter.

FIG. 5 shows a one-dimensional first precondition scheme. In another implementation manner of the embodiment of the present application, it can also be extended to a two-dimensional first precondition scheme, such as selecting a condition of a corresponding state machine. It is not only a precondition dimension of the country, but also the business model in which the user is located, such as a self-employed model or a platform business model. This can make the determination of market attributes more accurate and provide users with more accurate services.

Therefore, the first state identifier may include multiple first state sub-identifiers, and each first state sub-identifier corresponds to multiple second state sub-identifiers and transition sub-conditions between the multiple second state sub-identifiers, respectively. The second state sub-identifier and the transition sub-conditions between the plurality of second state sub-identifiers can be implemented in the form of a sub-state machine. For example, for the market dimension of each country, the business model of this country market is further subdivided. Is it a self-employed model or a platform business model.

Referring to FIG. 7, there is shown a configuration file data structure diagram under a two-dimensional precondition, wherein the first state identifiers a, b may include nationalities, such as Russia, Spain, etc., each of the first state identifiers may be Including two first state sub-identifiers a ', b', a 'can represent the self-employed mode, b' can represent the platform business model, each first state identifier can correspond to a state machine set, set in the state machine set There are two sub-state machines corresponding to the first state sub-identities a 'and b', respectively. The first state identifier, the first state sub-identity, and the data structure of the sub-state machine in the state configuration file under the two-dimensional precondition can be Implemented as key-value pairs.

In a specific example, the set of key-value pairs in the state configuration file under the two-dimensional precondition can be as shown in Table 2:

Table 2

In Table 2, it is shown that KEY is a set of corresponding state machines Value in the Russian and Spanish markets, where the set of state machines Value is implemented in JSON format, where capital letters such as A represent states and lowercase letters such as a represent Conditions, whose trigger logic includes Russia: state A + condition a = state B. Spain: State A + condition b = state B, etc.

Specifically, Table 2 shows only the key-value pairs of the state machine corresponding to the two-dimensional first state identifier. 1ST represents the self-operating business model, that is, a first state sub-identifier, and 3RD represents the platform business model, that is, another first A state sub-identifier, and different business models correspond to different sub-state machines.

Step 602: Store the state configuration file in a local data storage; or, and store the state configuration file in a cached data storage.

This step may refer to the above step 502, which is not repeated here.

Optionally, step 602 may include sub-step 6021.

Sub-step 6021, when a status configuration update file for the status configuration file is obtained, store the status configuration update file in a local data store instead of the status configuration file; or, and update the status configuration The file is stored in a cache data store, replacing the state configuration file.

This step may refer to the above step 5021, which is not repeated here.

Step 603: Receive a user request.

This step may refer to the above step 302, which is not repeated here.

Step 604: Acquire the current first state identifier, the current second state identifier, and user attribute information of the user according to the user request.

This step may refer to the above step 303, which is not repeated here.

Step 605: Obtain business mode data corresponding to the current first state identifier, where the business mode data includes a business mode identifier that matches the first state sub-identifier.

In the embodiment of the present application, business database data may be stored in the database of the business server. The business model data is established according to business logic. The business model data includes a business model identifier that matches the first state sub-identifier, indicating the first State ID-first state sub-identity-business model ID-correspondence between multiple second state sub-identities and transition sub-conditions between multiple second state sub-identities, such as the Russian market is currently self-operating mode, The US market is currently a platform business model.

Step 606: Match the current first state identifier with the plurality of first state identifiers to determine a plurality of target first state sub-identities.

In this step, by matching the current first state identifier with the plurality of first state identifiers, multiple target first state sub-identifiers corresponding to the matched first state identifiers can be further determined.

Step 607: Match the business mode identifier with the target first state sub-identifier, and determine corresponding target second state sub-identifiers and target transition sub-conditions between the multiple target second state sub-identifiers. .

In Table 2 above, the current first state identifier is matched with the first state identifier to determine the corresponding state machine. The state machine includes multiple sub-state machines. At this time, the business mode identifier and the first state sub-identifier are used. By matching, the sub-state machine in the state machine set can be determined for status update through the sub-state machine. The sub-state machine is between multiple target second-state sub-identifiers and the multiple target second-state sub-identifiers. The specific realization of the target transition condition.

For example, if the user is a Russian and has made a business visit, it is known through the query that the Russian market is currently a self-employed business model. Then, in Table 2, find the sub-state machine in the Value whose KEY is Russia: 1ST: {"A": { "a": "B", "b": "C", "c": "A"}}, and make state changes based on the logic in them.

Step 608: In the plurality of target second-state sub-identifiers and the target transition sub-condition between the plurality of target second-state sub-identifiers, combine the current second state identifier and the target second-state sub-condition. Matching the identifier, and matching the user attribute information with the target conversion sub-condition to determine the target second state identifier.

In this step, the operation logic of the sub-state machine under the two-dimensional precondition is the same as that of the state machine under the one-dimensional precondition, which will not be repeated here.

In summary, a method for determining a user status identifier provided by an embodiment of the present application includes: matching a provided first status identifier with a current first status identifier of a user obtained according to a user request, and determining a plurality of corresponding matches. The second state identifier and the transition conditions between the plurality of matching second state identifiers, and the second state identifier and the plurality of second states are obtained through the user ’s current second state identifier and user attribute information obtained according to the user request The transition conditions between the identifiers are matched to obtain the target second state identifier of the user. This application uses a first state identifier as a key, a substate machine set corresponding to the first state sub-identifier as a value, and generates a corresponding state configuration file in the form of a key-value pair. Further, the first state stored in the state configuration file is used. The state identifier matches the current first state identifier, multiple target first state sub-identifiers, the business model identifier is matched with the target first state sub-identifier, and the corresponding multiple target second state sub-identifiers and multiple target first The target transition sub-condition between the two state sub-identifiers, matching the current second state identifier with the target second state sub-identifier, and matching the user attribute information with the target transition sub-condition, determining the target second state identifier, and the target The second state identifier is used to update the current second state identifier of the user object, which achieves the purpose of verifying the state identifier in multiple dimensions. The solution in the two-dimensional market dimension can make the determination of market attributes more accurate and provide users with more accurate Service, and the data structure of the key-value pairs in the state configuration file is simple, the amount of code is small, so that State identification verification response speed.

Referring to FIG. 8, a structure diagram of a system for determining a user status identifier in a specific example of the present application is shown, including:

A providing module 701 is configured to provide multiple first status identifiers, where the multiple first status identifiers respectively correspond to multiple second status identifiers and transition conditions between the multiple second status identifiers;

A receiving module 702, configured to receive a user request;

An obtaining module 703, configured to obtain a current first state identifier, a current second state identifier, and user attribute information of the user according to the user request;

A determining module 704, configured to: according to the current first state identifier, the current second state identifier, the user attribute information, and the multiple first state identifiers and the multiple first state identifiers corresponding to A transition condition between a plurality of second state identifiers determines a target second state identifier of the user.

In summary, an apparatus for determining a user status identifier provided in an embodiment of the present application includes: providing multiple first status identifiers, the multiple first status identifiers corresponding to multiple second status identifiers and multiple second statuses, respectively. Conversion conditions between identities; receiving user requests; obtaining the user's current first state identifier, current second state identifier, and user attribute information according to the user request; according to the current first state identifier, current second state identifier, and user attribute information And transition conditions between multiple first state identifiers and multiple second state identifiers corresponding to the multiple first state identifiers to determine a target second state identifier for the user. The purpose of verifying the status identifier in multiple dimensions is achieved, and the data structure of the transition conditions between the multiple second status identifiers corresponding to the first status identifier and the multiple second status identifiers is simple, and the amount of code is small, making the user status The response of the identification is fast.

Referring to FIG. 9, a specific structural diagram of a system-level user state identification determining device in a specific example of the present application is shown, including:

A providing module 801 is configured to provide multiple first status identifiers, where the multiple first status identifiers correspond to multiple second status identifiers and transition conditions between the multiple second status identifiers, respectively;

Optionally, a module 801 is provided, including:

Provide a sub-module 8011 for providing a status configuration file; in the status configuration file, the first status identifier serves as a key, a plurality of second status identifiers corresponding to the first status identifier, and the plurality of second status identifiers The transition conditions between the state identifiers are used as key values.

Optionally, provide submodules, including:

A providing unit, configured to use the first state identifier as a key, and use a plurality of second state identifiers corresponding to the first state identifier and transition conditions between the plurality of second state identifiers as a notation format The key value is used to generate the state configuration file in the form of a key value pair.

The storage sub-module 8012 is configured to store the status configuration file in a local data storage, or and, store the status configuration file in a cache data storage.

A configuration update submodule 8013, configured to store the status configuration update file in a local data store when the status configuration update file for the status configuration file is obtained, instead of the status configuration file;

Or, and the state configuration update file is stored in a cache data storage, replacing the state configuration file.

The receiving module 802 is configured to receive a user request.

The obtaining module 803 is configured to obtain a current first state identifier, a current second state identifier, and user attribute information of the user according to the user request.

A determining module 804, configured to: according to the current first state identifier, the current second state identifier, the user attribute information, and the multiple first state identifiers and the multiple first state identifiers corresponding to A transition condition between a plurality of second state identifiers determines a target second state identifier of the user.

Optionally, the determining module 804 includes:

A first matching sub-module 8041, configured to match the current first state identifier with the plurality of first state identifiers, determine a plurality of matching second state identifiers, and the plurality of matching second state identifiers; Between target conversion conditions;

The first matching sub-module includes:

A first determining unit, configured to use the current first state identifier as a query key in the state configuration file, determine a key corresponding to the first state identifier, and a plurality of keys corresponding to the first state identifier key A key value of a target transition condition between the matched second state identifiers and the plurality of matched second state identifiers.

An obtaining unit, configured to obtain business mode data corresponding to the current first state identifier, where the business mode data includes a business mode identifier that matches the first state sub-identifier;

A first matching unit, configured to match the current first state identifier with the plurality of first state identifiers, and determine multiple target first state sub-identifiers;

A second matching unit, configured to match the business mode identifier with the target first-state sub-identifier, and determine the correspondence between the corresponding multiple target second-state sub-identifiers and the multiple target second-state sub-identifiers Target transition subcondition.

A second matching submodule 8042, configured to match the current second state identifier with the determined plurality of second state identifiers, and match the user attribute information with the target transition condition to determine the Target second status identification.

The second matching sub-module includes:

A second determining unit, configured to: among the key values of the target transition condition between the plurality of matched second state identifiers and the plurality of matched second state identifiers, compare the current second state identifier with all Matching the determined plurality of second state identifiers, and matching the user attribute information with the target conversion condition to determine the target second state identifier.

A third determining unit, configured to: in the target transition sub-condition between the multiple target second-state sub-identifiers and the target second-state sub-identifiers, associate the current second status identifier with the target Match the second status sub-identifier, and match the user attribute information with the target transition sub-condition to determine the target second status id.

In summary, an apparatus for determining a user status identifier provided in an embodiment of the present application includes: matching a first status identifier provided with a current first status identifier of a user obtained according to a user request to determine a plurality of corresponding matches; The second state identifier and the transition conditions between the plurality of matching second state identifiers, and the second state identifier and the plurality of second states are obtained through the user ’s current second state identifier and user attribute information obtained according to the user request The conversion conditions between the identifiers are matched to obtain the target second state identifier of the user. This application uses the first state identifier as the key, and the substate machine set corresponding to the first state sub-identifier as the value, and is generated in the form of key-value pairs. The corresponding state configuration file further uses the first state identifier stored in the state configuration file to match the current first state identifier, and multiple target first state sub-identities to match the business mode identifier with the target first state sub-identity. Match to determine the corresponding multiple target second state sub-identifiers and multiple target second state sub-identifiers Between target transition sub-conditions, matching the current second state identifier with the target second state sub-identifier, and matching user attribute information with target transition sub-conditions, determining the target second state identifier, and Update the current second status identifier of the user object to achieve the purpose of verifying the status identifier in multiple dimensions. The solution in the two-dimensional market dimension can make the determination of market attributes more accurate, provide users with more accurate services, and configure the status. The data structure of the key-value pairs in the file is simple, and the amount of code is small, which makes the response of the status identification verification faster.

As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For the related parts, refer to the description of the method embodiment.

FIG. 10 is a schematic structural diagram of a device according to an embodiment of the present application. Referring to FIG. 10, the server 900 may be configured to implement the user state identifier determination method provided in the foregoing embodiment. The server 900 may have relatively large differences due to different configurations or performance, and may include one or more central processing units (CPUs) 922 (for example, one or more processors) and memory 932, one or one The above storage medium 930 (for example, one or one storage device) storing application programs 942 or data 944. The memory 932 and the storage medium 930 may be temporarily stored or persistently stored. The program stored in the storage medium 930 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server. Furthermore, the central processing unit 922 may be configured to communicate with the storage medium 930, and execute a series of instruction operations in the storage medium 930 on the server 900.

The server 900 may also include one or more power sources 926, one or more wired or wireless network interfaces 950, one or more input-output interfaces 958, one or more keyboards 956, and / or and, one or more operating systems. 941, such as Windows ServerTM, Mac OSXTM, UnixTM, LinuxTM, FreeBSDTM and so on. The central processing unit 922 may execute the following operations on the server 900:

Receiving user requests;

This application also provides one or more machine-readable media having instructions stored thereon that, when executed by one or more processors, cause the device to execute a method for determining a user status identifier.

The present application provides a device having one or more machine-readable media having instructions stored thereon, which when executed by the one or more processors, causes the device to execute a method for displaying business progress.

This application also provides one or more machine-readable media having instructions stored thereon that, when executed by one or more processors, cause the device to execute a method for displaying business progress.

Each embodiment in this specification is described in a progressive manner. Each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments may refer to each other.

Those skilled in the art should understand that the embodiments of the embodiments of the present application may be provided as a method, an apparatus, or a computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

The embodiments of the present application are described with reference to flowcharts and / or block diagrams of the method, the terminal device (system), and the computer program product according to the embodiments of the present application. It should be understood that each process and / or block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing terminal device Means are generated for implementing the functions specified in one or more of the flowcharts and / or one or more of the block diagrams.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufactured article including the instruction means, the The instruction device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device, so that a series of operating steps can be performed on the computer or other programmable terminal device to produce a computer-implemented process, so that the computer or other programmable terminal device can The instructions executed on the steps provide steps for implementing the functions specified in one or more of the flowcharts and / or one or more of the block diagrams.

Although the preferred embodiments of the embodiments of the present application have been described, those skilled in the art can make other changes and modifications to these embodiments once they know the basic inventive concepts. Therefore, the appended claims are intended to be construed to include the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present application.

Finally, it should be noted that in this article, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities. There is any such actual relationship or order between OR operations. Moreover, the terms "including", "comprising", or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or end device that includes a series of elements includes not only those elements but also those that are not explicitly listed Other elements, or elements inherent to such a process, method, article, or terminal. Without more restrictions, the elements defined by the sentence "including one ..." do not exclude that there are other identical elements in the process, method, article, or terminal device including the elements.

The method and device for determining a user status identifier provided in the present application have been described in detail above. Specific examples are used in this document to explain the principle and implementation of the present application. The description of the above embodiments is only used to help understand the present invention. The method of application and its core ideas; for those of ordinary skill in the art, according to the ideas of this application, there will be changes in the specific implementation and the scope of application. In summary, the contents of this specification should not be interpreted as Application restrictions.

Claims

A method for determining a user status identifier, comprising:

Providing multiple first status identifiers, the multiple first status identifiers corresponding to multiple second status identifiers and transition conditions between the multiple second status identifiers, respectively;

Receiving user requests;

Acquiring, according to the user request, a current first state identifier, a current second state identifier, and user attribute information of the user;

According to the current first state identifier, the current second state identifier, the user attribute information, and the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers A transition condition between determining a target second state identifier of the user.
The method according to claim 1, wherein, according to the current first state identifier, the current second state identifier, the user attribute information, and the plurality of first state identifiers, the The step of determining a transition condition between the plurality of second state identifiers corresponding to the plurality of first state identifiers and the target second state identifier of the user includes:

Matching the current first state identifier with the plurality of first state identifiers, and determining a target transition condition between the plurality of matched second state identifiers and the plurality of matched second state identifiers;

Matching the current second state identifier with the determined plurality of second state identifiers, and matching the user attribute information with the target transition condition to determine the target second state identifier.
The method according to claim 2, wherein said providing a plurality of first state identifiers, said plurality of first state identifiers respectively corresponding to a plurality of second state identifiers and said plurality of second state identifiers Steps between transition conditions, including:

Provide a state configuration file; in the state configuration file, the first state identifier serves as a key, a plurality of second state identifiers corresponding to the first state identifier, and transition conditions between the plurality of second state identifiers As the key value.
The method according to claim 3, wherein the step of providing a status configuration file comprises:

Using the first state identifier as a key, and using a plurality of second state identifiers corresponding to the first state identifier and transition conditions between the plurality of second state identifiers as a key value in a notation format of the object, and Value-wise manner, generating the state configuration file.
The method according to claim 3, wherein the matching the current first state identifier with the plurality of first state identifiers, determining a plurality of matching second state identifiers, and the plurality of matching The step of identifying a target transition condition between the second state includes:

In the state configuration file, using the current first state identifier as a query key, determining a key corresponding to the first state identifier, and a plurality of matching second state identifiers corresponding to the key of the first state identifier, and A key value of a target transition condition between the plurality of matched second state identifiers.
The method according to claim 5, wherein the matching the current second state identifier with the determined plurality of second state identifiers, and the user attribute information and the target transition condition The step of performing matching to determine the target second state identifier includes:

And among the key values of the target transition conditions between the plurality of matching second state identifiers and the plurality of matching second state identifiers, the current second state identifier and the determined plurality of second Match the status identifier, and match the user attribute information with the target transition condition to determine the target second status identifier.
The method according to claim 2, wherein the first state identifier comprises a plurality of first state sub-identifiers, and each first state sub-identifier corresponds to a plurality of second state sub-identifiers and the plurality of first state sub-identifiers, respectively. Transition sub-conditions between two state sub-identifiers.
The method according to claim 7, wherein the matching the current first state identifier with the plurality of first state identifiers, determining a plurality of matching second state identifiers, and the plurality of matching The step of identifying a target transition condition between the second state includes:

Acquiring business mode data corresponding to the current first state identifier, where the business mode data includes a business mode identifier that matches the first state sub-identifier;

Matching the current first state identifier with the plurality of first state identifiers to determine a plurality of target first state sub-identifiers;

Matching the business mode identifier with the target first state sub-identifier, and determining a corresponding plurality of target second state sub-identifiers and target transition sub-conditions between the plurality of target second state sub-identifiers.
The method according to claim 8, wherein the matching the current second state identifier with the determined plurality of second state identifiers, and the user attribute information and the target transition condition The step of performing matching to determine the target second state identifier includes:

Match the current second state identifier with the target second state sub-identifier in the plurality of target second state sub-identities and the target transition sub-condition between the plurality of target second state sub-identifiers And matching the user attribute information with the target conversion sub-condition to determine the target second state identifier.
The method according to claim 3, after the step of providing a status configuration file, further comprising:

Storing the status configuration file in a local data store;

Or, and the state configuration file is stored in a cache data storage.
The method according to claim 10, further comprising:

When a status configuration update file for the status configuration file is obtained, storing the status configuration update file in a local data store instead of the status configuration file;

Or, and the state configuration update file is stored in a cache data storage, replacing the state configuration file.
The method according to claim 1, wherein the current first state identifier is generated by a user behavior corresponding to a first priority level of the user, and the user attribute information is generated by a user behavior corresponding to a second priority level of the user ;

The priority of the first priority level is greater than the priority of the second priority level.
A device for determining a user status identifier, comprising:

A providing module, configured to provide multiple first status identifiers, where the multiple first status identifiers correspond to multiple second status identifiers and transition conditions between the multiple second status identifiers;

A receiving module for receiving a user request;

An obtaining module, configured to obtain a current first state identifier, a current second state identifier, and user attribute information of the user according to the user request;

A determining module, configured to: according to the current first state identifier, the current second state identifier, the user attribute information, and multiple corresponding ones of the multiple first state identifiers and the multiple first state identifiers A transition condition between the second state identifiers determines a target second state identifier of the user.
The apparatus according to claim 13, wherein the determining module comprises:

A first matching submodule, configured to match the current first state identifier with the plurality of first state identifiers, and determine between a plurality of matched second state identifiers and the plurality of matched second state identifiers Target conversion conditions

A second matching submodule, configured to match the current second state identifier with the determined plurality of second state identifiers, and match the user attribute information with the target transition condition to determine the target The second status identifier.
The apparatus according to claim 14, wherein the providing module comprises:

Provide a sub-module for providing a state configuration file; in the state configuration file, the first state identifier serves as a key, a plurality of second state identifiers corresponding to the first state identifier, and the plurality of second states The transition conditions between the IDs are used as key values.
The apparatus according to claim 15, wherein the providing submodule comprises:

A providing unit, configured to use the first state identifier as a key, and use a plurality of second state identifiers corresponding to the first state identifier and transition conditions between the plurality of second state identifiers as a format of an object notation The key value is used to generate the state configuration file in the form of a key value pair.
The apparatus according to claim 15, wherein the first matching sub-module comprises:

A first determining unit, configured to use the current first state identifier as a query key in the state configuration file, determine a key corresponding to the first state identifier, and a plurality of keys corresponding to the first state identifier key A key value of a target transition condition between the matched second state identifiers and the plurality of matched second state identifiers.
The apparatus according to claim 17, wherein the second matching sub-module comprises:

A second determining unit, configured to: among the key values of the target transition condition between the plurality of matched second state identifiers and the plurality of matched second state identifiers, compare the current second state identifier with all Matching the determined plurality of second state identifiers, and matching the user attribute information with the target conversion condition to determine the target second state identifier.
The apparatus according to claim 14, wherein the first matching sub-module comprises:

An obtaining unit, configured to obtain business mode data corresponding to the current first state identifier, where the business mode data includes a business mode identifier that matches the first state sub-identifier;

A first matching unit, configured to match the current first state identifier with the plurality of first state identifiers, and determine multiple target first state sub-identifiers;

A second matching unit, configured to match the business mode identifier with the target first-state sub-identifier, and determine the correspondence between the corresponding multiple target second-state sub-identifiers and the multiple target second-state sub-identifiers Target transition subcondition.
The apparatus according to claim 19, wherein the second matching sub-module comprises:

A third determining unit, configured to: in the target transition sub-condition between the multiple target second-state sub-identifiers and the target second-state sub-identifiers, associate the current second status identifier with the target Match the second status sub-identifier, and match the user attribute information with the target transition sub-condition to determine the target second status id.
The apparatus according to claim 15, further comprising:

A storage submodule, configured to store the status configuration file in a local data storage, or and, store the status configuration file in a cached data storage.
The apparatus according to claim 21, further comprising:

A configuration update submodule, configured to store the status configuration update file in a local data store when the status configuration update file for the status configuration file is obtained, replacing the status configuration file;

Or, and the state configuration update file is stored in a cache data storage, replacing the state configuration file.
A device for determining a user status identifier, comprising:

One or more processors; and

One or more machine-readable media having instructions stored thereon, which when executed by the one or more processors, causes the apparatus to perform the method of any one of claims 1 to 12 .
One or more machine-readable media having stored thereon instructions which, when executed by one or more processors, perform the method of any one of claims 1 to 12.