CN110781375A

CN110781375A - User state identification determining method and device

Info

Publication number: CN110781375A
Application number: CN201810856553.5A
Authority: CN
Inventors: 李伟杰
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Singapore Holdings Pte Ltd
Priority date: 2018-07-31
Filing date: 2018-07-31
Publication date: 2020-02-11
Anticipated expiration: 2038-07-31
Also published as: WO2020024824A1; CN110781375B

Abstract

The application provides a method and a device for determining a user state identifier, which comprise the following steps: providing a plurality of first state identifications, wherein the plurality of first state identifications respectively correspond to a plurality of second state identifications and conversion conditions among the plurality of second state identifications; receiving a user request; acquiring a current first state identifier, a current second state identifier and user attribute information of a user according to a user request; and determining a target second state identifier of the user according to the current first state identifier, the current second state identifier, the user attribute information and conversion conditions among the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers. The purpose of verifying the state identifiers in multiple dimensions is achieved, the data structure of the conversion conditions between the second state identifiers corresponding to the first state identifiers and the second state identifiers is simple, the code amount is small, and the response speed determined by the user state identifiers is high.

Description

User state identification determining method and device

Technical Field

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

Background

Under the background of large-scale application of wireless application, the state of a user is generally required to be identified aiming at multi-country and multi-market services, so that the service is provided for the user in a targeted manner according to the state of the user, and the effect of optimizing user experience is achieved.

At present, there are two specific implementation methods for performing state identification on a user, the first method is to directly update the state of the user to a state matched with a grouping attribute according to the grouping attribute corresponding to the user, and if the user is a first login, the user is marked with a state tag for the first login. Secondly, a user identification system with at least three dimensions of market, condition and state is established, logic for identifying the state of the user is realized through a large number of code statements such as if and if-else based on a script language (JavaScript), the market where the user is located is determined according to the geographical position information of the user, the state of the user is further determined according to the user behavior information of the user, and the state is bound with the user, so that the state of the user is determined.

However, the inventor finds in the research process that: in the first scheme at present, the judgment condition based on the user state is too few, and the usable condition dimensionality is too low, so that the determination precision of the user state is low, and in the second scheme, the implementation of multi-dimensional user state identification through a large number of JavaScript code sentences can cause the problems of excessive code quantity, complex processing logic and low processing efficiency.

Disclosure of Invention

In view of the foregoing problems, an embodiment of the present application provides a method for determining a user status identifier, where a plurality of first status identifiers are provided, and the plurality of first status identifiers correspond to a plurality of second status identifiers and a transition condition between the plurality of second status identifiers, respectively; receiving a user request; acquiring a current first state identifier, a current second state identifier and user attribute information of a user according to a user request; and determining a target second state identifier of the user according to the current first state identifier, the current second state identifier, the user attribute information and conversion conditions among the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers. The purpose of state identification verification under multiple dimensions is achieved, the data structure of conversion conditions among multiple second state identifications corresponding to the first state identification and the multiple second state identifications is simple, the code amount is small, the response speed determined by the user state identification is high, and the problems that processing logic is complex and processing efficiency is low in the prior art are solved.

Correspondingly, the embodiment of the application also provides a user state identifier determining device, which is used for ensuring the realization and the application of the 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 a plurality of first state identifications, wherein the plurality of first state identifications respectively correspond to a plurality of second state identifications and conversion conditions among the plurality of second state identifications;

receiving a user request;

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

and determining a target second state identifier of the user according to the current first state identifier, the current second state identifier, the user attribute information, and conversion conditions among the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers.

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

the device comprises a providing module, a judging module and a judging module, wherein the providing module is used for providing a plurality of first state identifications, and the first state identifications respectively correspond to a plurality of second state identifications and conversion conditions among the second state identifications;

the receiving module is used for receiving a user request;

the acquisition module is used for acquiring the current first state identification, the current second state identification and the user attribute information of the user according to the user request;

and the determining module is used for determining the target second state identifier 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 conversion conditions among the plurality of second state identifiers corresponding to the plurality of first state identifiers.

Correspondingly, the embodiment of the application also discloses a device, which comprises:

one or more processors; and

one or more machine-readable media having instructions stored thereon, which when executed by the one or more processors, cause the apparatus to perform a user state identification determination method.

Accordingly, one or more machine-readable media having instructions stored thereon, which when executed by one or more processors, cause an apparatus to perform a method for user status indicator determination are also disclosed.

The embodiment of the application has the following advantages:

the embodiment of the application comprises the following steps: the method comprises the following steps: providing a plurality of first state identifications, wherein the plurality of first state identifications respectively correspond to a plurality of second state identifications and conversion conditions among the plurality of second state identifications; receiving a user request; acquiring a current first state identifier, a current second state identifier and user attribute information of a user according to a user request; and determining a target second state identifier of the user according to the current first state identifier, the current second state identifier, the user attribute information and conversion conditions among the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers. The purpose of state identification verification under multiple dimensions is achieved, the data structure of conversion conditions among multiple second state identifications corresponding to the first state identification and the multiple second state identifications is simple, the code amount is small, the response speed determined by the user state identification is high, and the problems that processing logic is complex and processing efficiency is low in the prior art are solved.

Drawings

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

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

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

FIG. 4 is a diagram illustrating a state condition lookup table of a state machine according to an embodiment of the present application;

fig. 5 is a flowchart illustrating specific steps of a system-level user status identifier determining method according to an embodiment of the present application;

fig. 6 is a flowchart illustrating specific steps of another system-level user status identifier determination method according to an embodiment of the present application;

fig. 7 is a configuration file data structure diagram under a two-dimensional precondition according to an embodiment of the present application;

fig. 8 is a block diagram of a user status identifier determining apparatus according to an embodiment of the present application;

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

fig. 10 is a schematic structural diagram of an apparatus according to another embodiment of the present application.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.

Referring to fig. 1, a system architecture of an embodiment of the present application is shown, which may include at least:

a service server 10, a configuration center 20, a user attribute data server 30 and a client 40, wherein the service server 10 comprises: an identification engine 101 and a local data store 102.

In the embodiment of the present application, in order to distinguish and group massive users facing the service server 10, corresponding state identifiers may be set for the users, so as to group the users according to different market attributes and grouping attributes, so that the service server 10 may provide services corresponding to the state identifiers for the client 40 according to the state identifiers of the users, thereby achieving the purpose of meeting the requirements of different users.

It should be noted that, when a user logs in the service server 10 for the first time to perform service access, a related user account may be established, and a status identifier corresponding to the user account is generated to indicate the current status of the user, where the status identifier may be a status label, for example, when the user logs in the account for the first time, a status label of "new person" may be displayed near the user avatar to indicate the "new person identity" of the user, and the status identifier may be changed, for example, as the number of user logins increases, the status label of "new person" may be updated to "faithful user".

Specifically, the service server 10 is provided with an identification Engine 101(Mark Engine) and a Local Data store 102(Local Data). The local data storage 102 may store a state configuration file 201 related to a user state identifier, which is obtained from the configuration center 20, in the state configuration file 201, a plurality of first state identifiers, a plurality of second state identifiers, and a conversion condition between the plurality of second state identifiers may be stored, the identifier engine 101 is an independent thread used for parsing the state configuration file 201 in the local data storage 102, and under a current application architecture, the identifier engine may often be a service plug-in the service server 10, and the service plug-in may load the state configuration file 201 pushed by the configuration center 20 to update a state of a user.

The configuration center 20(Config Server) often stores various state configuration files 201 used in the service in a form of key value pairs, and the configuration center 20 may update the state configuration files 201 or push the state configuration files 201 to the service Server 10, where at least one first state identifier, a plurality of second state identifiers corresponding to the first state identifier, and a conversion condition between the plurality of second state identifiers are stored in the state configuration files 201, and a correspondence relationship between the first state identifier, the second state identifier, and the conversion condition between the plurality of second state identifiers may be written in a form of key value pairs.

The user attribute data server 30 stores user attribute information and current second state identifiers of each user, the user attribute data is an effective tool for delineating a target user and contacting user appeal and design direction, the user attribute data can enable a service object of an application product to be more focused and concentrated, a data source established by the user attribute data server is data related to user behaviors generated when the user uses the application product, such as name, sex, age, geographical location, etc. filled in by the user registration account, browsing history information, behavior information, etc. generated by the user in the application, and by collecting these information, a user attribute data server 30 may be established that includes the user, and using data in the user attribute data server 30, the corresponding market attributes of the user and the grouping attributes in the market may be determined.

It should be noted that, for the first state identifier, the second state identifier, the transition condition, and the user attribute information in the present application, the first state identifier may be a state label to indicate an attribute of one dimension of the user, such as an attribute that the nationality, the region, the gender, and the like of the user do not change in the first time period, and the second state identifier may also be a state label to indicate an attribute of another dimension of the user, such as an attribute that a new/old user of the user changes in the second time period. The dimension corresponding to the first state identifier and the dimension corresponding to the second state identifier can be different dimensions; of course, the dimension attributes specifically corresponding to the first state identifier and the second state identifier may be set as needed, and are not limited in this embodiment of the application. The conversion condition is a parameter set for triggering the corresponding target second state identifier according to the execution logic of the finite state machine, and the corresponding relationship between the second state identifier + the trigger condition + the target second state identifier may be preset, so that the corresponding target second state identifier is obtained according to the relationship between the second state identifier + the trigger condition; the user attribute information is information generated according to user behavior, such as a user browsing record, a user behavior record, and the like.

It should be noted that the current first state identifier of the user may correspond to a market dimension, may be used to partition a market, determine a market attribute of the user, and may generally be a nationality of the user or a current geographic location of the user, such as the united states, china, north china, and the like, and the current first state identifier of the user may be obtained according to positioning of an Internet Protocol (IP) of the user, or may be obtained according to registration information input by the user when registering an account. The previous second state identifier of the user may correspond to a grouping dimension, and may be used to divide the grouping, and determine a grouping attribute of the user, which is generally the current state of the user, for example, tags such as "new person" and "faithful user" of the user, or tags associated with services such as "may participate in XX big promotion", "consume 8 discount", and the like, the user attribute information may be obtained by using some user behavior data or user identity data before the user, for example, the first login time of the user is within one month and has already made a bill, the user has participated in XX big promotion, and the like, and the current second state identifier of the user may be generally bound with a user Identifier (ID) so as to query the corresponding current second state identifier of the user by using the user ID.

The current second state identifier of the user may change continuously with the increase of the user behavior, and because the market attribute of the user is usually fixed, the probability of the change is small, therefore, the current first state identifier of the user may not change within a certain time range, for example, the country and the region where the user is located usually do not change, or the probability of the change is small, the user attribute data may be regarded as data related to the user behavior, and the user attribute data may only increase with the increase of the user behavior, which indicates that the nature of the user behavior may not change.

Under the trend of business service global deployment, aiming at the business of multi-country and multi-market, at least three dimensions of market, condition and state are faced when the user state is identified, the market dimension is used for dividing the user into specific countries or markets, if the user accesses Russian business, the user is divided into Russian markets, the condition dimension is used for further grouping the users divided into specific markets, the specific implementation is similar to the logic of a finite state machine, and the method comprises the following steps: the current state + condition is the next state, and the user is assigned to the market by dividing the user into specific markets, and updating the state in the market, therefore, in the present application, the update of the current second state identifier of the user can be completed by using a Finite-state machine (FSM), which is also called a Finite-state automata, abbreviated as a state machine, and is a mathematical model representing behaviors such as Finite states and transitions and actions between the states, wherein the first state identifier in the state configuration file 201 may correspond to a market dimension, and may be used to partition a market and determine a market attribute of a user, the finite state machine is used to obtain a corresponding target second state identifier based on a current second state identifier of the user and user attribute data, and updating the target second state identification with the current second state identification of the user in the specific market group, namely further establishing the group attribute of the user.

Specifically, referring to fig. 2, the system architecture interaction diagram shown based on fig. 2 includes:

and step S1, the configuration center pushes the state configuration file to the service server.

In this step, the configuration center pushes the state configuration file to the service server, where the state configuration file may include a plurality of first state identifiers, and a plurality of second state identifiers corresponding to the plurality of first state identifiers, respectively, and a conversion condition between the plurality of second state identifiers, so that the service server may update the corresponding state identifier for the user by using the state configuration file, and in addition, the configuration center may also update the state configuration file and push the updated state configuration file to the service server.

Step S2, the service server receives the user request sent by the client.

When a client user needs to access a service server, the client sends a user request to the service server, wherein a user Identifier (ID) of a corresponding user may be bound in the user request, a current second state identifier of the user, a current first state identifier of the user, and user attribute information may be queried through the user ID, and the current first state identifier is used for matching with the first state identifier in a state configuration file.

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

The current first state identifier, the current second state identifier and the user attribute information of the user are obtained by querying according to the user ID in the user request, and specifically, the current first state identifier and the user attribute information are obtained by querying in the user attribute data server according to the user ID and are used for subsequently updating the user state.

Step S4, the service server determines a target second state identifier of the user according to the current first state identifier, the current second state identifier, the user attribute information, and the transition condition between the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers.

In this step, the current first state identifier is used as a query KEY to match with the first state identifier KEY in the state configuration file, so as to determine a Value corresponding to the first state identifier KEY, where the Value may be a conversion condition between a plurality of second state identifiers and a plurality of second state identifiers, and a corresponding relationship between the current first state identifier, a plurality of second state identifiers and a conversion condition between the first state identifier and the plurality of second state identifiers may be obtained through matching. For example, when the user establishes an account, the input nationality is russia, and the information may be imported into the user attribute information of the user and exists as the current first state identifier, and by matching the current first state identifier with the russia-related first state identifier, the conversion conditions between the plurality of second state identifiers and the plurality of second state identifiers corresponding to the russia market may be determined quickly.

Further, the state identifier is updated through a plurality of second state identifiers and a plurality of conversion conditions between the second state identifiers, and a specific implementation of the state identifier may be implemented by a finite state machine, where an implementation logic of the finite state machine is: specifically, referring to fig. 1, the logic of the finite state machine may be embodied in a form of a condition lookup table, the service server may use the user attribute information as a condition, the current second state identifier as a current state, obtain a target second state identifier as a next state, and update the current second state identifier of the user, for example, the user attribute information may be a login record of the user, and assuming that the user may be divided into a group of loyalty users after the user logs in 100 times, when a certain user accesses the service 100 th time, the current second state identifier may be updated from a "new person" state to a "loyalty user" according to the logic of the state machine.

And S5, the service server provides corresponding service to the client of the user according to the target second state identification.

In the embodiment of the application, after the service server identifies/verifies the state of the user based on three dimensions of market, condition and state, the service server can provide the service corresponding to the updated target second state identification for the user, for example, the user is a loyalty user group in a russian market, the service server can provide member handling recommendation in the russian market for the user so that the loyalty user can know member rights and interests, and the probability of the loyalty user handling members is greatly improved compared with that of a new user.

Therefore, the application can provide a plurality of first state identifiers, and the plurality of first state identifiers respectively correspond to a plurality of second state identifiers and conversion conditions among the plurality of second state identifiers; receiving a user request; acquiring a current first state identifier, a current second state identifier and user attribute information of a user according to a user request; and determining a target second state identifier of the user according to the current first state identifier, the current second state identifier, the user attribute information and conversion conditions among the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers. The purpose of state identification verification under multiple dimensions is achieved, the data structure of conversion conditions among multiple second state identifications corresponding to the first state identification and the multiple second state identifications is simple, the code amount is small, the response speed determined by the user state identification is high, and the problems that processing logic is complex and processing efficiency is low in the prior art are solved.

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

step 301, providing a plurality of first state identifiers, where the plurality of first state identifiers respectively correspond to a plurality of second state identifiers and a transition condition between the plurality of second state identifiers.

In this embodiment of the application, the plurality of first state identifiers, the plurality of second state identifiers corresponding to the plurality of first state identifiers, respectively, and the conversion condition between the plurality of second state identifiers may be written into a state configuration file, and stored in the form of the configuration file, the state configuration file may be pushed by a configuration center, and the configuration center may push the configuration file to any one service server for use.

Specifically, based on the current operation of verifying the current second state identifier of the user, the requirement of three dimensions of the market, condition and state is provided, that is, the state of the identified user may determine a market attribute first, and then further determine a group attribute in the market, where the group attribute is the changed target second state identifier of the user, and based on the current market rule, the market attribute may generally be a specific market, such as country, region, operation type, and the like, and the group attribute may generally be obtained by using some user behavior data or user identity data before the user, for example, if the first login time of the user is within one month and has passed, the group attribute may be a "non-new user", and the state of the user is updated from neW to first.

Further, the determining of the market attribute may be implemented by a first state identifier in the state configuration file, and the determining of the 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, for example, tags of multiple countries are established, different countries may correspond to different first state identifiers, and a correspondence between the corresponding second state identifier and the transition condition between the second state identifiers is established for each country, so as to update the user state in the market of this country. The specific implementation of the conversion condition between the first state identifier and the corresponding second state identifier in the state configuration file and the second state identifier can be in a key-value form, so that the purposes of reducing the code amount and improving the corresponding speed can be achieved.

Step 302, a user request is received.

When a user client needs to access a service server, the client sends a user request to the service server, wherein the user request may store a user ID of a corresponding user, and a current second state identifier of the user, a current first state identifier of the user, and user attribute information may be queried through the user ID, and the current first state identifier is used for matching with the first state identifier in a state configuration file.

Step 303, obtaining the current first state identifier, the current second state identifier and the 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 current first state identifier and the user attribute information of the user under the user ID may be called by accessing the user attribute data server, where the data source established by the user attribute data server is data related to user behavior generated when the user uses the application, for example, data such as identity information input when the user establishes an account, the current first state identifier may generally correspond to a market attribute, such as nationality, a local area, and the like of the user, and the user attribute information may correspond to a group attribute, such as a historical browsing record, a user behavior record, and the like of the user.

Further, the state identifier of the user may also be bound to the user ID, and the current second state identifier of the user may also be obtained by querying in the state management thread through the corresponding user ID.

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

The identification engine of the service server matches the current first state identification with the first state identification in the state configuration file, can determine the conversion conditions between a plurality of second state identifications corresponding to the first state identification and the plurality of second state identifications, and obtains the corresponding relation of the conversion conditions between the current first state identification, the plurality of second state identifications and the plurality of second state identifications. For example, when the user establishes an account, the input nationality is russia, and the state machine corresponding to the russian market can be determined by matching the input nationality with the first state identifier of which the content is russia.

When a plurality of second state identifiers corresponding to a specific market attribute and a conversion condition between the plurality of second state identifiers are determined, at this time, an identifier engine of a service server retrieves user attribute information whether the user attribute information meets a state machine triggering condition, if the user attribute information exists, a target second state identifier is triggered to update a current second state identifier of a user, and if the user attribute information does not exist, when updated user attribute information is acquired next time, whether the state machine triggering condition is met when the updated user attribute information is retrieved until the current second state identifier of the user is updated.

Referring to fig. 4, a schematic diagram of a state condition lookup table of a state machine is shown, where the state machine is a mathematical model representing a finite number of states and behaviors such as transitions and actions between the states, where the state machine establishes a trigger logic lookup table of a current state/condition according to business logic, in fig. 4, three trigger states of a state a, a state B, and a state C are shown, and three trigger conditions of a condition 1, a condition 2, and a condition 3 are shown, and the trigger logic may include a state C + a condition 1 ═ a state B, and may be represented as a new person state + a login number greater than or equal to 100 ═ a true user state by combining with a business logic example.

Through the current first state identification and the user attribute information, the identification engine of the business server can update the current second state identification of the corresponding user in the state machine, the business server can provide business service corresponding to the updated target second state identification for the user, for example, the user is a loyalty user group in a Russian market, the business server can provide member handling recommendation in the Russian market for the user so that the loyalty user can know member rights and interests, and the probability of the loyalty user handling members is greatly improved compared with that of a new user.

To sum up, a method for determining a user status identifier provided by an embodiment of the present application includes: providing a plurality of first state identifications, wherein the plurality of first state identifications respectively correspond to a plurality of second state identifications and conversion conditions among the plurality of second state identifications; receiving a user request; acquiring a current first state identifier, a current second state identifier and user attribute information of a user according to a user request; and determining a target second state identifier of the user according to the current first state identifier, the current second state identifier, the user attribute information and conversion conditions among the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers. The purpose of state identification verification under multiple dimensions is achieved, the data structure of conversion conditions among multiple second state identifications corresponding to the first state identification and the multiple second state identifications is simple, the code amount is small, the response speed determined by the user state identification is high, and the problems that processing logic is complex and processing efficiency is low in the prior art are solved.

Referring to fig. 5, a flowchart illustrating specific steps of a system-level user status identifier determining method provided in the present application is shown, which specifically includes the following steps:

step 501, providing a state configuration file; in the state configuration file, the first state identifier is used as a key, and a plurality of second state identifiers corresponding to the first state identifier and a conversion condition between the plurality of second state identifiers are used as key values.

In the embodiment of the present application, generating the state configuration file first requires creating an empty state configuration file document for writing configuration data.

Furthermore, KEY (a first state identifier) and Value (a transition condition between a plurality of second state identifiers and a plurality of second state identifiers corresponding to the first state identifier) may be written in the state configuration file, and by using the current first state identifier as the query KEY and matching the query KEY with the first state identifier KEY in the state configuration file, the Value corresponding to the first state identifier KEY may be determined, and a correspondence relationship between the current first state identifier, the plurality of second state identifiers, and the transition condition between the second state identifiers is obtained.

Optionally, sub-step 501 may further include sub-step a 1.

Substep a1, using the first state identifier as a key, using the plurality of second state identifiers corresponding to the first state identifier and the conversion conditions between the plurality of second state identifiers as key values in the format of the object numbered musical notation, and generating the state configuration file in a key-value pair manner.

In the embodiment of the application, the state machine corresponding to the first state identifier takes the format of a JavaScriptObject Notation (JSON) as a value, so that the code amount and the code logic complexity can be effectively reduced, the JSON is a lightweight data exchange format, data is stored and represented by adopting a text format completely independent of a programming language, and a simple and clear hierarchical structure enables the JSON to become an ideal data exchange language, is easy to read and write by people, is easy to analyze and generate by a machine, and effectively improves the network transmission efficiency.

In a specific example, the set of key-value pairs in the state profile may be as follows in table 1:

TABLE 1

In table 1, KEY is shown as corresponding Value in russia and spanish markets, where the Value of the state machine is implemented in JSON format, and Value is implemented by state machine logic of transition conditions between a plurality of second state identifiers, where capital letters such as a represent states and lower case letters such as a represent conditions, and trigger logic thereof includes russia: state a + condition a is state B. Spain: state a + condition B state B, etc.

Table 1 shows key-value pairs of state machines corresponding to only one-dimensional first state identifiers, where the first state identifiers only represent dimensions of the market.

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

In this step, the identification engine of the service server, upon acquiring the state profile, may store the state profile in a local data store, for further use next time, in addition, the state configuration file may also be stored in the cache data store by the marking engine, and further, the state configuration file may also be stored in both the cache data store and the local data store, and the speed of extracting the state configuration file from the cache data store is faster than that of the local data store, but the cache data store is generally used for running threads, it is unstable and the cache data storage will affect the normal use of the service when the resources occupied by the state configuration file are excessive, therefore, the state configuration file can be stored in the local data storage, the storage space of the local data storage is larger, and the storage performance is more stable.

Optionally, step 502 may include sub-step 5021.

Substep 5021, when a state configuration update file aiming at the state configuration file is obtained, storing the state configuration update file in a local data storage to replace the state configuration file; or storing the state configuration update file in a cache data storage to replace the state configuration file.

In the embodiment of the application, based on the timeliness of data when a business is developed by a merchant, the state configuration file needs to be updated frequently to meet the timeliness requirement of the business, at the moment, the configuration center can acquire the state configuration update file and push the state configuration update file to the business server, and the business server can automatically store the state configuration update file in corresponding storage to replace the original state configuration file.

Step 503, receiving a user request.

This step can refer to step 302 described above, and is not described here.

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

This step can refer to step 303 above, and is not described here.

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

In the embodiment of the present application, based on the determination of the corresponding transition conditions between the plurality of second state identifiers and the plurality of second state identifiers by the current first state identifier, in the correspondence relationship between the plurality of second state identifiers and the transition conditions between the plurality of second state identifiers, the service logic that performs state update by using the user attribute information may determine that the priority of the current first state identifier is greater than the priority of the user attribute information.

For example, the priority may be embodied in the time sequence of occurrence of user behavior, when a user accesses a web application, the user clicks the tag in the united states first, enters the united states page for service access, and executes a corresponding operation, so that the tag in the united states may determine the market attribute of the user and may be correspondingly generated as the current first state identifier, and the user may determine the group attribute of the user and may be correspondingly generated as the user attribute information if the user enters the corresponding operation executed by the united states page.

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

The identification engine of the service server can determine a plurality of matched second state identifications and a target conversion condition between the plurality of matched second state identifications by matching the current first state identifications with the plurality of first state identifications, and obtain a corresponding relation of the current first state identifications, the plurality of matched second state identifications and the target conversion condition between the plurality of matched second state identifications. For example, when the user establishes the account, the input nationality is russia, and by matching with the first state identifier whose content is russia, a plurality of matched second state identifiers corresponding to the russian market and a target conversion condition between the plurality of matched second state identifiers can be determined.

Optionally, step 505 may further include:

in the status configuration file, the current first status identifier is used as a query key, and the key of the corresponding first status identifier, the plurality of matching second status identifiers corresponding to the key of the first status identifier, and the key value of the target transition condition between the plurality of matching second status identifiers are determined.

In the embodiment of the application, the current first state identifier is used as a query KEY and is matched with the first state identifier KEY in the state configuration file, so that Value (Value) corresponding to the first state identifier KEY can be determined, and the corresponding relation of the conversion conditions between the current first state identifier, the plurality of second state identifiers and the plurality of second state identifiers is obtained.

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

When a state machine corresponding to a specific market attribute is determined, the identification engine of the service server searches whether a current second state identification and user attribute information meeting the trigger condition of the state machine exist or not, if yes, a target second state identification is triggered to update the current second state identification, and if not, when updated user attribute information is obtained next time, the updated user attribute information is searched whether the trigger condition of the state machine is met or not until the current second state identification of the user is updated.

Through the current second state identification and the user attribute information, the identification engine of the business server can update the current second state identification of the corresponding user in the state machine, the business server can provide business service corresponding to the updated target second state identification for the user, for example, the user is a loyalty user group in a Russian market, the business server can provide member handling recommendation in the Russian market for the user so that the loyalty user can know member rights and interests, and the member handling probability of the loyalty user is greatly improved compared with that of a new user.

Optionally, step 506 may further include:

sub-step 5061, in the key assignment of the target transition condition between the plurality of matching second state identifiers and the plurality of matching second state identifiers, matching the current second state identifier with the plurality of determined second state identifiers, and matching the user attribute information 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 a query KEY to match with the first state identifier KEY in the state configuration file, a Value corresponding to the first state identifier KEY may be determined, a corresponding relationship of a conversion condition between the current first state identifier and the first state identifier and between the plurality of second state identifiers is obtained, and then in the corresponding relationship of the conversion condition between the plurality of second state identifiers and between the plurality of second state identifiers, a trigger logic of the state machine is utilized to perform state update through the current second state identifier of the user and the user attribute information, so as to obtain an updated target second state identifier. The matching mode has the advantages of simple logic, small code amount and high response speed.

To sum up, the method for determining a user status identifier provided by the embodiment of the present application includes providing a plurality of first status identifiers, where the plurality of first status identifiers correspond to a plurality of second status identifiers and a transition condition between the plurality of second status identifiers, respectively; receiving a user request; acquiring a current first state identifier, a current second state identifier and user attribute information of a user according to a user request; determining a target second state identifier of the user according to the current first state identifier, the current second state identifier, the user attribute information and conversion conditions among a plurality of second state identifiers corresponding to the plurality of first state identifiers and the plurality of first state identifiers; the method comprises the steps of taking a first state identifier as a key, enabling the first state identifier to correspond to a plurality of second state identifiers and a conversion condition between the plurality of second state identifiers to serve as values, generating a corresponding state configuration file in a key value pair mode, utilizing the first state identifier stored in the state configuration file to be matched with the current first state identifier, determining a corresponding relation between the plurality of second state identifiers corresponding to state updating and the conversion condition between the plurality of second state identifiers, and updating the current second state identifier of a user in the corresponding relation through the current second state identifier and user attribute information.

Referring to fig. 6, a flowchart illustrating specific steps of another system-level user status identifier determining method provided in the present application is shown, which specifically includes the following steps:

step 601, providing a state configuration file; in the state configuration file, the first state identifier serves as a key, the plurality of second state identifiers corresponding to the first state identifier and the conversion conditions among the plurality of second state identifiers serve as key values, wherein the first state identifier includes a plurality of first state sub-identifiers, and each first state sub-identifier corresponds to the plurality of second state sub-identifiers and the conversion conditions among the plurality of second state sub-identifiers respectively.

Fig. 5 shows a one-dimensional first precondition scheme, which may be extended to a two-dimensional first precondition scheme in another implementation manner of the embodiment of the present application, for example, the condition for selecting a corresponding state machine is not only one precondition dimension of a country, but also needs a service mode in which a user is located, such as a self-service mode or a platform service mode, so that the determination of the market attribute may be more accurate, and a more accurate service may be provided for the user.

Therefore, the first state identifier may include a plurality of first state sub-identifiers, each first state sub-identifier corresponds to a plurality of second state sub-identifiers and a transition sub-condition between the plurality of second state sub-identifiers, and the plurality of second state sub-identifiers and the transition sub-condition between the plurality of second state sub-identifiers may be implemented in the form of a sub-state machine, for example, for a market dimension of each country, a business mode of the country market is further subdivided into a self-operation mode or a platform business mode.

Referring to fig. 7, a configuration file data structure diagram under a two-dimensional precondition is shown, where the first state identifiers a and b may include nationality, such as russia, spain, and the like, each first state identifier may include two first state sub-identifiers a ', b', a 'may represent a self-operation mode, b' may represent a platform operation mode, each first state identifier may correspond to a state machine set, two sub-state machines respectively corresponding to the first state sub-identifiers a ', b' are disposed in the state machine set, and a data structure of the first state identifier, the first state sub-identifier, and the sub-state machines in the state configuration file under the two-dimensional precondition may be implemented in a form of key value pairs.

In a specific example, the set of key-value pairs in the state profile under the two-dimensional precondition may be as follows in table 2:

TABLE 2

In table 2, KEY is shown as a set Value of corresponding state machines in russia and spanish markets, where the set Value of state machines is implemented in JSON format, capital letters such as a in Value represent state, small letters such as a represent condition, and its trigger logic includes russia: state a + condition a is state B. Spain: state a + condition B state B, etc.

Specifically, table 2 shows key value pairs of state machines corresponding to only two-dimensional first state identifiers, where 1ST represents a self-service mode, that is, one first state sub-identifier, and 3RD represents a platform service mode, that is, another first state sub-identifier, and different service modes correspond to different sub-state machines.

Step 602, storing the state configuration file in a local data storage; or, storing the state configuration file in a cache data store.

This step may refer to step 502 described above, and will not be described herein.

Optionally, step 602 may include sub-step 6021.

Substep 6021, when acquiring the state configuration update file for the state configuration file, storing the state configuration update file in a local data storage, and replacing the state configuration file; or storing the state configuration update file in a cache data storage to replace the state configuration file.

This step can refer to step 5021, which is not described herein.

Step 603, receiving a user request.

This step can refer to step 302 described above, and is not described here.

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

This step can refer to step 303 above, and is not described here.

Step 605, obtaining the service mode data corresponding to the current first state identifier, where the service mode data includes a service mode identifier matched with the first state sub-identifier.

In this embodiment, the database of the service server may store service pattern data, where the service pattern data is established according to service logic, and the service pattern data includes a service pattern identifier matched with the first state sub-identifier, and represents a correspondence between conversion sub-conditions between the first state identifier, the first state sub-identifier, the service pattern identifier, the plurality of second state sub-identifiers, and the plurality of second state sub-identifiers, for example, a russian market is currently a self-operating mode, and a U.S. market is currently a platform operating mode.

Step 606, matching the current first state identifier with the plurality of first state identifiers, and determining a plurality of target first state sub-identifiers.

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

Step 607, matching the service mode identifier with the target first state sub identifier, and determining a plurality of corresponding target second state sub identifiers and target conversion sub conditions among the plurality of target second state sub identifiers.

In table 2, the current first state identifier is matched with the first state identifier, so that a corresponding state machine can be determined, the state machine includes a plurality of sub-state machines, and at this time, the service mode identifier is matched with the first state sub-identifier, so that the sub-state machines in the state machine set can be determined for performing state updating through the sub-state machines, where the sub-state machines are specific implementations of the plurality of target second state sub-identifiers and the target transition sub-conditions between the plurality of target second state sub-identifiers.

For example, if the user is russian and has service access, and the russian market is currently in the self-supporting operation mode by querying, the sub-state machine in Value with KEY being russia is found in table 2: 1 ST: { "A": { "a": "B", "B": "C", "C": "a" } and makes state changes according to the logic therein.

Step 608, in the target transition sub-condition between the plurality of target second state sub-identifiers and the plurality of target second state sub-identifiers, matching the current second state identifier with the target second state sub-identifier, matching the user attribute information with the target transition sub-condition, and determining the target second state identifier.

In this step, the running 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, and is not described herein again.

To sum up, a method for determining a user status identifier provided by an embodiment of the present application includes: and matching the provided first state identification with the current first state identification of the user acquired according to the user request, determining a plurality of corresponding matched second state identifications and conversion conditions among the plurality of matched second state identifications, and then matching the current second state identification of the user acquired according to the user request and the user attribute information with the second state identification and the conversion conditions among the plurality of second state identifications to obtain the target second state identification of the user. The method comprises the steps of using a first state identifier as a key, using a sub-state machine set corresponding to the first state sub-identifier as a value, generating a corresponding state configuration file in a key-value pair mode, further using the first state identifier stored in the state configuration file to match with a current first state identifier, using a plurality of target first state sub-identifiers, matching a service mode identifier with the target first state sub-identifiers, determining a plurality of corresponding target second state sub-identifiers and a target conversion sub-condition between the plurality of target second state sub-identifiers, matching the current second state identifier with the target second state sub-identifiers, matching user attribute information with the target conversion sub-condition, determining a target second state identifier, updating the current second state identifier of a user object with the target second state identifier, and realizing the purpose of state identifier verification under multiple dimensions, the scheme under the two-dimensional market dimension can enable the market attribute to be determined more accurately, provide more accurate service for users, and enable the response speed of state identification verification to be high due to the fact that the data structure of key value pairs in the state configuration file is simple and the code amount is small.

Referring to fig. 8, a block diagram of a user status identifier determining apparatus at a system level in a specific example of the present application is shown, including:

a providing module 701, configured to provide a plurality of first state identifiers, where the plurality of first state identifiers respectively correspond to a plurality of second state identifiers and a transition condition between the plurality of second state identifiers;

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

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

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

To sum up, a user status identifier determining apparatus provided in an embodiment of the present application includes: providing a plurality of first state identifications, wherein the plurality of first state identifications respectively correspond to a plurality of second state identifications and conversion conditions among the plurality of second state identifications; receiving a user request; acquiring a current first state identifier, a current second state identifier and user attribute information of a user according to a user request; and determining a target second state identifier of the user according to the current first state identifier, the current second state identifier, the user attribute information and conversion conditions among the plurality of first state identifiers and the plurality of second state identifiers corresponding to the plurality of first state identifiers. The purpose of verifying the state identifiers in multiple dimensions is achieved, the data structure of the conversion conditions between the second state identifiers corresponding to the first state identifiers and the second state identifiers is simple, the code amount is small, and the response speed determined by the user state identifiers is high.

Referring to fig. 9, a specific structure diagram of a user status identifier determining apparatus at a system level in a specific example of the present application is shown, including:

a providing module 801, configured to provide a plurality of first state identifiers, where the plurality of first state identifiers respectively correspond to a plurality of second state identifiers and a transition condition between the plurality of second state identifiers;

optionally, a module 801 is provided, including:

providing sub-module 8011 for providing a status profile; in the state configuration file, the first state identifier is used as a key, a plurality of second state identifiers corresponding to the first state identifier and a conversion condition between the plurality of second state identifiers are used as key values

Optionally, providing a sub-module comprising:

and the providing unit is used for generating the state configuration file by taking the first state identifier as a key, taking a plurality of second state identifiers corresponding to the first state identifier and conversion conditions among the plurality of second state identifiers as key values in the form of object numbered musical notation and in a key-value pair mode.

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

A configuration update sub-module 8013, configured to, when a state configuration update file for the state configuration file is obtained, store the state configuration update file in a local data store, instead of the state configuration file;

or storing the state configuration update file in a cache data storage to replace the state configuration file.

A receiving module 802, configured to receive a user request.

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

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

Optionally, the determining module 804 includes:

a first matching submodule 8041, configured to match the current first state identifier with the multiple first state identifiers, and determine multiple matched second state identifiers and a target transition condition between the multiple matched second state identifiers;

a first matching submodule comprising:

a first determining unit, configured to determine, in the state configuration file, a key of the corresponding first state identifier, a plurality of matched 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, with the current first state identifier as a query key.

An obtaining unit, configured to obtain service mode data corresponding to the current first state identifier, where the service mode data includes a service mode identifier matched with the first state sub-identifier;

the first matching unit is used for matching the current first state identifier with the plurality of first state identifiers to determine a plurality of target first state sub-identifiers;

and the second matching unit is used for matching the service mode identifier with the target first state sub-identifier and determining a plurality of corresponding target second state sub-identifiers and target conversion sub-conditions among the plurality of target second state sub-identifiers.

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

A second matching submodule comprising:

a second determining unit, configured to match, in the multiple matched second state identifiers and key values of target transition conditions between the multiple matched second state identifiers, the current second state identifier with the multiple determined second state identifiers, match the user attribute information with the target transition conditions, and determine the target second state identifier.

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

To sum up, a user status identifier determining apparatus provided in an embodiment of the present application includes: the provided first state identification is matched with the current first state identification of the user acquired according to the user request, a plurality of corresponding matched second state identifications and conversion conditions among the plurality of matched second state identifications are determined, and then the current second state identification of the user and user attribute information acquired according to the user request are matched with the second state identification and the conversion conditions among the plurality of second state identifications to obtain the target second state identification of the user. The method comprises the steps of determining a plurality of corresponding target second state sub-identifications and a plurality of target conversion sub-conditions among the target second state sub-identifications, matching the current second state identification with the target second state sub-identifications, matching user attribute information with the target conversion sub-conditions, determining the target second state identification, and updating the current second state identification of a user object with the target second state identification, so that the aim of performing state identification verification in multiple dimensions is fulfilled.

For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.

Fig. 10 is a schematic structural diagram of an apparatus according to an embodiment of the present disclosure. Referring to fig. 10, a server 900 may be used to implement the user status identification determination method provided in the above-described embodiment. The server 900 may vary widely in configuration or performance and may include one or more Central Processing Units (CPUs) 922 (e.g., one or more processors) and memory 932, one or more storage media 930 (e.g., one or more mass storage devices) storing applications 942 or data 944. Memory 932 and storage media 930 may be, for example, transitory or persistent. The program stored on the storage medium 930 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, a central processor 922 may be provided in communication with the storage medium 930 to 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 supplies 926, one or more wired or wireless network interfaces 950, one or more input-output interfaces 958, one or more keyboards 956, and/or one or more operating systems 941, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc. Central processor 922 may execute the following instructions on server 900:

receiving a user request;

One or more machine-readable media having instructions stored thereon, which when executed by one or more processors, cause an apparatus to perform a method for user state identity determination.

An apparatus, one or more machine-readable media having instructions stored thereon, which when executed by the one or more processors, cause the apparatus to perform a business process demonstration method.

One or more machine-readable media having instructions stored thereon, which when executed by one or more processors, cause an apparatus to perform a business process demonstration method are also provided.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

As will be appreciated by one of skill in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, 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. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. The term "comprising" is used to specify the presence of stated elements, but not necessarily the presence of stated elements, unless otherwise specified.

The method and the device for determining the user state identifier provided by the application are introduced in detail, a specific example is applied in the text to explain the principle and the implementation of the application, and the description of the embodiment is only used for helping to understand the method and the core idea of the application; to sum up, the content of the present specification should not be construed as limiting the present application, since the scope of the present application may vary with the embodiments and applications of the present application.

Claims

1. A method for determining user status identifier, comprising:

receiving a user request;

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

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

and matching the current second state identifier with the plurality of determined second state identifiers, and matching the user attribute information with the target conversion condition to determine the target second state identifier.

3. The method of claim 2, wherein the step of providing a plurality of first state identifiers corresponding to a plurality of second state identifiers and transition conditions between the plurality of second state identifiers comprises:

providing a state configuration file; in the state configuration file, the first state identifier is used as a key, and a plurality of second state identifiers corresponding to the first state identifier and a conversion condition between the plurality of second state identifiers are used as key values.

4. The method of claim 3, wherein the step of providing a state profile comprises:

and generating the state configuration file by taking the first state identifier as a key, taking a plurality of second state identifiers corresponding to the first state identifier and conversion conditions among the plurality of second state identifiers as key values in an object numbered musical notation format and in a key value pair mode.

5. The method of claim 3, wherein the step of matching the current first state identifier with the plurality of first state identifiers, determining a plurality of matching second state identifiers and a target transition condition between the plurality of matching second state identifiers comprises:

and in the state configuration file, taking the current first state identifier as a query key, and determining a corresponding key of the first state identifier, a plurality of matched second state identifiers corresponding to the key of the first state identifier and key values of target conversion conditions among the plurality of matched second state identifiers.

6. The method of claim 5, wherein the step of determining the target second state identifier by 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 comprises:

and matching the current second state identifier with the plurality of determined second state identifiers in the plurality of matched second state identifiers and key values of target conversion conditions among the plurality of matched second state identifiers, matching the user attribute information with the target conversion conditions, and determining the target second state identifiers.

7. The method of 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 a transition sub-condition between the plurality of second state sub identifiers.

8. The method of claim 7, wherein the step of matching the current first state identifier with the plurality of first state identifiers, determining a plurality of matching second state identifiers and a target transition condition between the plurality of matching second state identifiers comprises:

acquiring service mode data corresponding to the current first state identifier, wherein the service mode data comprises a service mode identifier matched with 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;

and matching the service mode identifier with the target first state sub-identifier, and determining a plurality of corresponding target second state sub-identifiers and target conversion sub-conditions among the plurality of target second state sub-identifiers.

9. The method of claim 8, wherein the step of determining the target second state identifier by 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 comprises:

and in the target conversion sub-condition among the plurality of target second state sub-identifications and the plurality of target second state sub-identifications, matching the current second state identification with the target second state sub-identification, matching the user attribute information with the target conversion sub-condition, and determining the target second state identification.

10. The method of claim 3, after the step of providing a state profile, further comprising:

storing the state configuration file in a local data store;

or, storing the state configuration file in a cache data store.

11. The method of claim 10, further comprising:

when a state configuration update file aiming at the state configuration file is acquired, storing the state configuration update file in a local data storage to replace the state configuration file;

12. The method of claim 1, wherein the current first state identifier is generated by a user behavior of a user corresponding to a first priority level, and wherein the user attribute information is generated by a user behavior of the user corresponding to a second priority level;

the priority of the first priority level is greater than the priority of the second priority level.

13. An apparatus for determining a status indicator of a user, comprising:

the receiving module is used for receiving a user request;

14. The apparatus of claim 13, wherein the determining module comprises:

the first matching submodule is used for matching the current first state identifier with the plurality of first state identifiers and determining a plurality of matched second state identifiers and target conversion conditions among the plurality of matched second state identifiers;

and the second matching submodule is used for matching the current second state identifier with the plurality of determined second state identifiers, matching the user attribute information with the target conversion condition and determining the target second state identifier.

15. The apparatus of claim 14, wherein the providing module comprises:

providing a submodule for providing a state configuration file; in the state configuration file, the first state identifier is used as a key, and a plurality of second state identifiers corresponding to the first state identifier and a conversion condition between the plurality of second state identifiers are used as key values.

16. The apparatus of claim 15, wherein the providing sub-module comprises:

17. The apparatus of claim 15, wherein the first matching sub-module comprises:

18. The apparatus of claim 17, wherein the second matching sub-module comprises:

19. The apparatus of claim 14, wherein the first matching sub-module comprises:

20. The apparatus of claim 19, wherein the second matching sub-module comprises:

21. The apparatus of claim 15, further comprising:

and the storage submodule is used for storing the state configuration file in a local data storage or storing the state configuration file in a cache data storage.

22. The apparatus of claim 21, further comprising:

the configuration updating submodule is used for storing the state configuration updating file in a local data storage to replace the state configuration file when the state configuration updating file aiming at the state configuration file is obtained;

23. An apparatus, comprising:

one or more processors; and

one or more machine-readable media having instructions stored thereon that, when executed by the one or more processors, cause the apparatus to perform the methods of claims 1-12.

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