CN117728964A

CN117728964A - Service request processing method and device

Info

Publication number: CN117728964A
Application number: CN202211100134.1A
Authority: CN
Inventors: 秦亦然; 孙秉乾; 苗高升; 穆永俊; 杨丽
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2022-09-09
Filing date: 2022-09-09
Publication date: 2024-03-19

Abstract

The invention discloses a service request processing method and device, and relates to the technical field of big data. The specific implementation mode of the method comprises the following steps: receiving a first service request of one or more field terminals; the first service request comprises a first user account, a first field end identifier and first data to be processed; searching a local scene database, and determining first login state information according to a first user account and a first field end identifier; analyzing the first login state information, determining a first field end account number in the first login state information, and sending the first field end account number to a first field end server corresponding to the first field end identifier, so that the first field end server processes first data to be processed under the first field end account number. The embodiment can accurately distinguish the service data of each field end and each entity and realize smooth use experience of the user.

Description

Service request processing method and device

Technical Field

The present invention relates to the field of account data technologies, and in particular, to a method and an apparatus for processing a service request.

Background

When the existing platform processes service requests, because of the multiple service scenes under the platform, one service scene comprises one or more approximate function field terminals, in order to improve user experience and improve user use convenience, a user is usually allowed to switch all the field terminals under the platform through one account.

In the existing service request processing process, because all the field terminals use the same account number, user data cannot be accurately split according to each field terminal in a service scene, and further requirements of data processing (for example, single field terminal data analysis), supervision (for example, single field terminal account number cancellation) and the like cannot be met. Therefore, a method for distinguishing account numbers based on service scenes is proposed to distinguish service data.

In the process of implementing the present invention, the inventor finds that at least the following problems exist in the prior art:

when the accounts are distinguished in the existing business scenes, users need to register respectively in different business scenes, and when the scene-crossing calling field terminal service is performed, the corresponding registered accounts need to be logged in again, on one hand, the operation of frequently registering/replacing the accounts leads to extremely bad use experience of the users; on the other hand, when the user is an enterprise party, a plurality of accounts may exist under one enterprise, and the business data is too scattered to accurately analyze the business data of the enterprise.

Disclosure of Invention

In view of this, the embodiments of the present invention provide a method and an apparatus for processing a service request, which can accurately distinguish service data of each field terminal and each entity, and meanwhile, realize smooth use experience of a user, without frequent operations such as registration and account switching of the user, so as to improve user satisfaction, and can realize accurate splitting of field terminal data, so as to analyze service data of individuals and enterprises in detail, and promote service promotion of a platform.

In order to achieve the above object, according to an aspect of the embodiments of the present invention, there is provided a method for processing a service request, where the method is used in a service scenario server, and one service scenario corresponds to one or more sites, and the service scenario server stores a correspondence between a user account number, a site identifier, a site account number, and login status information; the method comprises the following steps:

receiving a first service request of the one or more field terminals; the first service request comprises a first user account, a first field end identifier and first data to be processed;

searching a local scene database, and determining first login state information according to the first user account and the first field end identifier;

analyzing the first login state information, determining a first field end account number in the first login state information, and sending the first field end account number to a first field end server corresponding to the first field end identifier, so that the first field end server processes first data to be processed under the first field end account number.

Optionally, the service scenario server further includes a correspondence between a user entity identifier and a user account and a field end account, and further includes:

Under each service scene, one user entity identifier corresponds to one or more user accounts;

in each service scene, one user entity identifier corresponds to one or more field end accounts.

Optionally, the method further comprises:

when the user entity identifier is a personal entity, one user entity identifier corresponds to one user account number, and one user entity identifier corresponds to one or more field end account numbers;

when the user entity identifier is a business entity, one user entity identifier corresponds to one or more user accounts, and one user entity identifier corresponds to one or more field end accounts.

Optionally, the method further comprises:

receiving one or more second service requests; the second service request comprises a second field end account number, a second field end identifier and second data to be processed;

determining whether the second field end identifier belongs to a service scene corresponding to the service scene server;

responding to the service scene which the second field terminal identifier does not belong to the service scene corresponding to the service scene server, sending the second field terminal account number and the second field terminal identifier to the account middle server, and receiving second login state information returned by the account middle server; the account middle server stores corresponding relations among user entity identifications, field end accounts and login state information under different service scenes, and the second login state information is obtained by inquiring the account middle server according to the second field end account, the second user entity identifications and the second field end identifications;

And sending the second login state information and the second data to be processed to a service scene server corresponding to the second field end identifier.

Optionally, the method further comprises:

under the condition that the second field end identifier is determined to belong to a service scene corresponding to the service scene server, inquiring the scene database, and determining third login state information corresponding to the second field end account;

analyzing the third login state information, determining a third field end account number in the third login state information, and sending the third field end account number to a second field end server corresponding to the second field end identifier, so that the second field end server processes second data to be processed under the third field end account number.

Optionally, the method further comprises:

for the same user account, one user entity identifier in one service scene corresponds to one user entity identifier in another service scene among different service scenes.

Optionally, the method further comprises:

and the service scene server extracts service data of each user account under each field terminal by using the field terminal account.

Optionally, before the receiving one or more first service requests, the method further includes:

Receiving one or more user account registration requests; the user account registration request comprises a user account to be registered and user entity information corresponding to the user account to be registered;

inquiring the scene database, and determining whether user entity information of the user account to be registered exists or not in response to the fact that the user account to be registered does not exist;

and responding to the existence of the user entity information of the user account to be registered, and determining a target user account of the user account to be registered according to the category of the user entity information of the user account to be registered.

Optionally, the determining the target user account of the user account to be registered according to the category of the user entity information of the user account to be registered includes:

returning a user account registration failure reminder under the condition that the category of the user entity information of the user account to be registered is personal entity information; otherwise, generating a target user account corresponding to the user account to be registered, and binding the target user account with a user entity identifier corresponding to the existing user entity information.

Optionally, the method further comprises:

inquiring a local scene database, and determining whether the request user account has field terminal accounts of other field terminals under the service scene server;

Responding to the field terminal accounts of other field terminals under the service scene server, sending an authorization prompt to the field terminal server, receiving an authorization result returned by the field terminal server, generating a target field terminal account corresponding to a field terminal identifier of the field terminal to be registered under the condition that the authorization result is permission authorization, and binding the request user account, a user entity identifier corresponding to the request user account, the field terminal identifier and the target field terminal account.

According to still another aspect of the embodiment of the present invention, there is provided a service request processing apparatus, where the apparatus is used in a service scenario server, where a service scenario corresponds to one or more sites, and the service scenario server stores a correspondence between a user account, a site identifier, a site account and login state information; the device comprises:

the receiving module is used for receiving the first service requests of the one or more field terminals; the first service request comprises a first user account, a first field end identifier and first data to be processed;

the searching module is used for searching a local scene database and determining first login state information according to the first user account number and the first field end identifier;

The analysis module is used for analyzing the first login state information, determining a first field end account number in the first login state information, and sending the first field end account number to a first field end server corresponding to the first field end identifier, so that the first field end server processes first data to be processed under the first field end account number.

According to another aspect of an embodiment of the present invention, there is provided an electronic device for processing a service request, including:

one or more processors;

storage means for storing one or more programs,

when the one or more programs are executed by the one or more processors, the one or more processors are enabled to implement the method for processing service requests provided by the present invention.

According to still another aspect of the embodiments of the present invention, there is provided a computer readable medium having stored thereon a computer program which when executed by a processor implements the method for processing a service request provided by the present invention.

One embodiment of the above invention has the following advantages or benefits: because the service scene server is adopted to construct the corresponding relation of the user account, the user entity identifier, the field terminal account and the login state information, the account middle server constructs the corresponding relation of the user account, the user entity identifier, the field terminal account and the login state information under different service scenes, and when a subsequent user initiates a service request in the service scene, the service scene server inquires the corresponding relation verification and sends the verification to the corresponding field terminal server for processing; when a subsequent user initiates a service request of a cross-service scene, a server in an account inquires a corresponding relation check and sends the check to a corresponding field server for processing; one user entity identifier corresponds to one or more user accounts, and one user entity identifier corresponds to one or more field end accounts, so that the operation of frequently registering/replacing the accounts is overcome, and the use experience of the user is extremely poor; the service data is too scattered, so that the technical problem that the service data of enterprises cannot be accurately analyzed is solved, smooth use experience of users is achieved while the service data of each site and each entity can be accurately distinguished, frequent registration, account switching and other operations are not needed by the users, user satisfaction is improved, accurate splitting of the site data can be achieved, the service data of individuals and enterprises are analyzed in detail, and the technical effect of service promotion of a platform is promoted.

Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

fig. 1 is a schematic diagram of the main flow of a service request processing method according to a first embodiment of the present invention;

fig. 2 (a) is a schematic diagram of a main flow of a registration method of a user account according to a first embodiment of the present invention;

fig. 2 (b) is a schematic diagram of a correspondence between a user account of a personal entity and a user entity identifier and a field account in each service scenario according to an embodiment of the present invention;

fig. 2 (c) is a schematic diagram of a correspondence between a user account-user entity identifier and a field account of a business entity in each business scenario according to an embodiment of the present invention;

fig. 3 (a) is a schematic diagram of a main flow of a registration method of a user account according to a second embodiment of the present invention;

fig. 3 (b) is a schematic diagram of a correspondence between a user account-user entity identifier and a field account in each service scenario stored by the account platform server according to an embodiment of the present invention;

fig. 4 is a schematic diagram of a main flow of a method for registering a field account according to a first embodiment of the present invention;

Fig. 5 is a schematic diagram of a main flow of a method for registering a field account according to a second embodiment of the present invention;

fig. 6 (a) is a schematic diagram of main flow of a service request processing method according to a second embodiment of the present invention;

fig. 6 (b) is a schematic diagram of correspondence between user entity identifiers among various service scenarios stored by the account platform server according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of the main modules of a service request processing apparatus according to an embodiment of the present invention;

FIG. 8 illustrates an exemplary system architecture diagram of a service request processing method or service request processing apparatus suitable for application to embodiments of the present invention;

fig. 9 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.

Detailed Description

Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

When the existing platform processes a service request, a user is allowed to switch all field terminals through one account, so that user data cannot be split according to the field terminals and the increasingly-increased supervision requirements cannot be met; although the account system based on the service scene is not intercommunicable between accounts, the service data can be split, but the user experience is poor because the account system needs to be frequently switched when the account system is required to be registered and used under each service scene.

By the service request processing method, the corresponding relation between the user account number and the user entity identifier and the field terminal account number in each service scene is constructed by using the account number center server, so that an account number system based on the concept of an entity is realized, and user data can be distinguished according to the field terminal account numbers; and the user account intercommunication under a plurality of business scenes corresponding to the same entity can be realized based on the entity through the non-sense authorization of the user account, so that the use experience of the user is improved and the development of enterprise services is met. For example, there may be multiple branch user accounts, multiple departments 'user accounts, multiple employees' user accounts, etc. under an enterprise, and since multiple user accounts are bound with a unique enterprise entity, enterprise service data sets may be implemented, and all enterprise service data is extracted by the enterprise entity, so as to promote benign development of enterprise service.

Fig. 1 is a schematic diagram of main flow of a service request processing method according to a first embodiment of the present invention, and as shown in fig. 1, the service request processing method according to the first embodiment of the present invention includes the following steps:

in the embodiment of the present invention, the method for processing a service request according to the first embodiment of the present invention is executed by a service scenario server, and a service scenario is described as an example. It should be noted that one service scenario may include one or more field terminals, where the definitions of the service scenario and the field terminal are selectively set according to actual needs. For example, different business scenes may be distinguished according to the region to which the site belongs, each business scene may include a plurality of terminals, accordingly, the domestic station is a business scene, the Thailand station is a business scene, the Indonesia station is a business scene, the domestic station includes a plurality of terminals such as domestic mall, domestic health, domestic finance, domestic retail cloud, domestic logistics cloud, domestic seven-delicacy, etc., the Thailand station includes a plurality of terminals such as Thailand mall, thailand health, thailand finance, thailand retail cloud, thailand logistics cloud, thailand seven-delicacy, etc., and the Indonesia station includes a plurality of terminals such as Indonesia mall, indonesia health, indonesia financial, indonesia retail cloud, indonesia logistics cloud, indonesia seven-deliy, etc. For example, different business scenes can be distinguished according to different specific transactions, and accordingly, the business scenes can comprise scenes such as a mall, a health, a finance and the like, the mall comprises a plurality of sites such as an APP mode, an applet mode, a webpage mode and the like, the health comprises a plurality of sites such as an APP mode, an applet mode, a webpage mode and the like, and the finance comprises a plurality of sites such as an APP mode, an applet mode, a webpage mode and the like.

Furthermore, the market terminals such as malls, health, finance, APP modes, applet modes, webpage modes and the like can be integrated into one business scene, and the business scene can be selectively set according to the needs.

In the embodiment of the invention, the service scene server stores the corresponding relation among the user account, the field terminal identifier, the field terminal account and the login state information.

Step S101, receiving a first service request of one or more field terminals; the first service request comprises a first user account, a first field end identifier and first data to be processed.

In the embodiment of the invention, the service request is generally initiated by a user to a field end server through a terminal, and the first service request comprises a first user account number, a first field end identifier and first data to be processed. For example, the service request may be a purchase request sent by a user through a shopping cart of the indonesia station, a purchase request sent by a user through a purchase order page of the thailand station, etc., the first user account is an account registered by the user at the indonesia station or the thailand station, the first field end identifier may be a shopping cart of the indonesia station or a purchase order page of the thailand station, and the first data to be processed may be one or more commodities in the shopping cart of the indonesia station or one or more commodities in the purchase order page of the thailand station.

In the embodiment of the invention, before a user initiates a service request to a field terminal server through a terminal, the user needs to register the corresponding field terminal service, and after successful registration and login, the user can initiate the service request. Specifically, a user initiates a registration request through each field end server, a service scene server generates a user account number under each service scene, a user entity identification account number and field end account numbers under different field ends of each service scene according to user entity information, and the corresponding relation of the user account number-the user entity identification account number-the field end account numbers is bound and stored.

In the embodiment of the present invention, as shown in fig. 2 (a), the method for registering a user account in the first embodiment of the present invention includes the following steps:

in the embodiment of the present invention, the user usually generates the requirement of registering the user account when using the specific field service in each service scenario, so the registration method of the user account in the first embodiment of the present invention is executed by the field server, and the field server receives the registration request initiated by the user through the terminal via each field service.

Step S201, receiving one or more user account registration requests; the user account registration request comprises a user account to be registered and user entity information corresponding to the user account to be registered.

In the embodiment of the invention, each field end server receives a user account registration request initiated by a user through a terminal, and the user account to be registered can be a mobile phone number, a mailbox and the like and is used for uniquely positioning one user under the service scene corresponding to the field end, namely, the user account is unique in each service scene.

Further, when the user modifies the user account information, the uniqueness in the service scene needs to be checked.

Further, the user account may be associated with a communication account of the user to improve the convenience of use of the user. For example, the communication account number is a micro signal, QQ number, etc.

Step S202, inquiring a local field database, determining whether the user account to be registered exists or not, and if so, turning to step S203; if not, go to step S204.

Step S203, a registered reminder is sent.

In the embodiment of the invention, under the condition that the account number of the user to be registered exists, the field end server sends a registered prompt of 'the account number is registered and please directly log in' to the terminal of the user, so that the user can directly log in.

Step S204, the user account to be registered is sent to a service scene server corresponding to a field server, and a first processing result returned by the service scene server is received.

In the embodiment of the invention, one or more field terminals can be included in one service scene, so when the field terminal server queries a local field terminal database and does not query the user account to be registered, the user account to be registered is possibly registered in other field terminals in the service scene corresponding to the field terminal server, and therefore the service scene server is required to search the local scene database to determine whether the user account to be registered exists or not for further processing.

In the embodiment of the invention, the business scene server stores the user account numbers of the field terminal services under the business scene server and the user entity identifications corresponding to the user account numbers. The user entity may be a person or a business, and a person entity is usually used by a person, so that the user entity identifier of the person corresponds to a user account, as shown in fig. 2 (b); one business entity may correspond to multiple employees, branches, departments, etc., so that the user entity identification of the business may correspond to one or more user accounts, as shown in fig. 2 (c), accordingly:

the user entity information of the personal entity can be an identity mark of the individual, for example, an identity card number, and correspondingly, the user account to be registered can be a mobile phone number, a mailbox and the like of the individual; the user entity information of the enterprise entity may be an identity of the enterprise, for example, a tax payer identifier, and accordingly, the user account to be registered may be a mobile phone number of a company employee, a company mailbox of the company employee, a personal mailbox of the company employee, a public mailbox of the company corporation, a public mailbox of the sub corporation, a public mailbox of the corporation, and the like.

In an embodiment of the present invention, as shown in fig. 3 (a), a method for registering a user account in a second embodiment of the present invention includes the following steps:

in the embodiment of the present invention, the method for registering the user account in the second embodiment of the present invention is executed by the service scene server, and the service scene server receives the user account to be registered and the user entity information corresponding to the user account to be registered, which are sent by the client server.

Step S301, query a local scene database.

Step S302, determining whether the user account to be registered exists, and if so, turning to step S303; if not, go to step S304.

In the embodiment of the invention, the service scene server queries a local database of the account center to judge whether the user account to be registered exists or not.

Step S303, the historical login state information corresponding to the user account to be registered is sent to the field server.

In the embodiment of the invention, as the service scene server stores the user account numbers, the user entity identifications and the historical login state information of each field service in the scene, the historical login state information comprises the user account numbers, the login time, the login failure time and the like. Therefore, under the condition that the user account to be registered exists in the local scene database, the fact that the user account to be registered is successful in logging in through other field terminals in the service scene is indicated, and the service scene server directly sends the historical login state information corresponding to the user account to be registered to the field terminal server.

Step S304, determining whether the user entity information of the user account to be registered exists, if so, turning to step S305; if not, go to step S309.

In the embodiment of the invention, when the user entity is a person, one personal entity corresponds to one user account; when the user entity is a corporation, one corporation entity can correspond to a plurality of user accounts, therefore, even if the user account to be registered does not exist, the user entity information of the user account to be registered may already be registered, and therefore, the service scene server needs to perform different operations according to whether the user entity information exists.

Step S305, judging whether the user entity information of the user account to be registered is personal entity information, if so, turning to step S306; if not, go to step S307.

Step S306, returning a user account registration failure reminder.

In the embodiment of the invention, under the conditions that the user account to be registered does not exist, the user entity information of the user account to be registered exists and the user entity information is the entity information of the individual, because one individual entity corresponds to one user account, the entity information of the individual is bound with one user account necessarily and only one user account can be bound, that is, as long as the entity information of the individual exists, the user account to be registered is bound with one user account necessarily, so the user account to be registered cannot be registered, the service scene server returns a user account registration failure reminding of 'the identity is registered', the user entity information of the user account to be registered is the entity information of the individual, and the entity information of the individual is bound with other user accounts, so that the user is required to send an entity binding request to the manual service.

Further, since the business entity corresponds to one or more user accounts, the business entity is free to unbind from the user accounts, but must be guaranteed to have at least one bound user account.

Step S307, generating a target user account corresponding to the user account to be registered.

In the embodiment of the invention, the service scene server generates the target user account (or called UserName) corresponding to the user account to be registered under the condition that the user account to be registered does not exist, the user entity information of the user account to be registered exists and the user entity information is the entity information of a corporation.

Further, the service scene server can directly take a mobile phone number, a mailbox and the like corresponding to the user account to be registered as the target user account; alternatively, a unique identification corresponding to the user account to be registered may be generated as the target user account.

Step S308, binding the target user account with the user entity identifier corresponding to the existing user entity information, and going to step S311.

In the embodiment of the invention, the service scene server binds the target user account of the user account to be registered to the user entity identifier corresponding to the existing user entity information, namely, the user entity identifier of the existing enterprise entity.

Step S309, generating a target user account corresponding to the user account to be registered, and a target user entity identifier corresponding to the user entity information of the user account to be registered.

In the embodiment of the invention, under the condition that the user account to be registered does not exist and the user Entity information of the user account to be registered does not exist, the service scene server generates a target user account corresponding to the user account to be registered and a target user Entity identifier corresponding to the user Entity information of the user account to be registered, wherein the target user Entity identifier comprises a Personal Entity (or Personal Entity) and a business Entity (or Enterprise Entity).

Further, when the user entity is a person, the service scene server can directly use the personal identification card number as a target user entity identifier, so that one user entity is uniquely calibrated as the personal entity of the person; when the user entity is a business, the business scenario server can directly use the tax payer identification number of the business as a target user entity identification, so that one user entity is uniquely calibrated as the business entity of the business. Alternatively, the service context server may generate a unique identifier corresponding to the user entity information of the user account to be registered as the target user entity identifier.

Step S310, binding the target user account and the target user entity identifier.

In the embodiment of the invention, the service scene server binds the target user account of the user account to be registered and the target user entity identifier, and builds a binding relationship between the target user account and the target user entity identifier.

Step S311, the target user account is sent to the field server.

In the embodiment of the present invention, or in step S311, the service scenario server may further send the binding relationship between the target user account and the target user account identifier to the in-account server for storage, so as to provide services subsequently.

In the embodiment of the invention, the service scene server judges the user account through the registration method of the second embodiment of the invention, and if the user account is registered/logged in under other scene ends of the service scene, the history login state information is returned to the scene end server; if the user account is never registered, judging the user entity information, and if the user account is a personal entity and exists, reporting errors; if the user account is a business entity and exists, generating a target user account and binding a user entity identifier of the existing business entity; if the user entity information does not exist, generating a target user account corresponding to the user account to be registered and a target user account identifier, and returning the target user account to the field server so that the user can use the field service.

In the embodiment of the invention, when the user modifies the user entity identifier, the uniqueness in the service scene needs to be checked.

In the embodiment of the invention, when a user modifies the inheritable personalized information such as nicknames, head portraits and the like, the modified personalized information can be directly inherited when logging in other field terminals again after finishing modification in one field terminal.

Step 205, determining a target user account of the user account to be registered according to a first processing result returned by the service scene server.

In the embodiment of the invention, the field server determines the target user account corresponding to the user account to be registered according to the first processing result returned by the service scene server. Or sending a registration failure prompt of the user account number to the terminal, so that the user searches the manual service for processing.

In the embodiment of the invention, by the user account registration method in the first embodiment of the invention, a field server processes a user account registration request, and if the user account is registered/logged in by the current field, a registered reminder is returned; and if not, the target user account is sent to the service scene server for processing, and the target user account is determined according to the first processing result returned by the service scene server, so that the correct registration of the user account is ensured to ensure the user service.

In the embodiment of the present invention, as shown in fig. 4, the method for registering a field end account in the first embodiment of the present invention includes the following steps:

in the embodiment of the present invention, the method for registering the field terminal account in the first embodiment of the present invention is executed by the field terminal server. It should be noted that, the generation of the field terminal account is usually performed on the basis that the user account has been generated to provide each field terminal service, so the method for generating the field terminal account of the present invention does not judge the user account any more, and directly processes the field terminal account registration request generated when the user initiates the field terminal service through the terminal.

Step S401, receiving one or more field end account registration requests; the field terminal account registration request comprises a request user account and a field terminal identifier of a field terminal to be registered.

In the embodiment of the invention, each field terminal server receives a field terminal account registration request initiated by a user through a terminal. The field end server stores user account numbers and field end account numbers using its field end service.

Step S402, inquiring a local field terminal database, determining whether the field terminal account corresponding to the field terminal identifier of the field terminal to be registered exists in the request user account, and if so, turning to step S403; if not, go to step S404.

Step S403, a login prompt is sent.

In the embodiment of the invention, under the condition that the user account is requested to have the field terminal account corresponding to the field terminal identification of the field terminal to be registered, the field terminal server sends a login prompt of whether the field terminal is registered or not and enables the user to directly log in.

Step S404, the request user account and the field end identifier to be registered are sent to a service scene server corresponding to a field end server, and a second processing result returned by the service scene server is received.

In the embodiment of the invention, one or more field ends can be included in one service scene, so that when the field end database corresponding to the request user account is not queried by the field end server, the field end account of other field ends in the same service scene can be possibly queried by the request user account, and therefore the service scene server is required to search the local scene database to determine whether the request user account is the field end account of other field ends in the same service scene or not so as to further process.

In the embodiment of the invention, the business scene server stores the user account numbers of the field terminal services under the business scene server, the user entity identifications corresponding to the user account numbers, the corresponding relations of the field terminal identifications and the field terminal account numbers. The user entity can be a person or an enterprise, one person entity can correspond to a plurality of field ends, so that the user entity identification of the person can correspond to one or a plurality of field end account numbers, as shown in fig. 2 (b); one business entity may also correspond to multiple sites, so that the user entity identification of the business person may correspond to one or more site account numbers, as shown in fig. 2 (c).

Further, since one or more farm ends may be included in one service scenario, as shown in fig. 3 (b), in each service scenario, one user entity identifier corresponds to one or more user accounts, one user entity identifier corresponds to one or more farm end accounts, and service services of each farm end server can be accessed by using the farm end accounts. For example, under the service scenario M, one user entity identifier corresponds to one user account, and one user entity identifier corresponds to one field end account; for another example, in the service scenario N, one user entity identifier corresponds to one or more user accounts, and one user entity identifier corresponds to one or more field end accounts. Specifically:

as shown in fig. 2 (b), when the user entity identifier is a personal entity, one user entity identifier corresponds to one user account, and one user entity identifier corresponds to one or more field end accounts; as shown in fig. 2 (c), when the user entity identifier is a business entity, one user entity identifier corresponds to one or more user accounts, and one user entity identifier corresponds to one or more field accounts.

In the embodiment of the invention, for each user entity identifier, one field end account corresponds to one field end identifier.

In the embodiment of the present invention, as shown in fig. 5, the method for registering a field end account according to the second embodiment of the present invention includes the following steps:

in the embodiment of the invention, the registration method of the field terminal account number in the second embodiment of the invention is executed by the service scene server, the condition that the field terminal account number of other field terminals in the same service scene possibly exists in the request user account number is judged, and the service scene server receives the request user account number and the field terminal identification of the field terminal to be registered, which are sent by the field terminal server of the request field terminal.

Step S501, query a local scene database.

Step S502, determining whether the user account is requested to have field end accounts of other field ends under the service scene server, if so, turning to step S503; if not, go to step S505.

Step S503, sending an authorization alert to the field server, and receiving an authorization result returned by the field server.

In the embodiment of the invention, under the condition that the user account is requested to exist on the site account of other sites under the service scene server, an authorization prompt of 'the other sites are registered under the scene and authorization is requested' is returned to the site server. After the user sees the authorization prompt, the user selects whether to directly authorize by one key, so that the user's noninductive operation is realized, and under the condition of the user's one-key authorization, a corresponding target field end account is directly generated.

Step S504, determining whether the authorization result returned by the field server is permission authorization, if so, going to step S505; if not, go to step S508.

Step S505, generating a target field terminal account number corresponding to the field terminal identifier of the field terminal to be registered.

In the embodiment of the invention, a service scene server generates a target field end account number (or AppAccount) corresponding to a field end identifier of a field end to be registered.

Step S506, binding the requested user account, a user entity identifier corresponding to the requested user account, the field end identifier, and the target field end account.

Step S507, the target field terminal account number is sent to a target field terminal server of the field terminal to be registered.

In the embodiment of the present invention, or in step S507, the service scenario server may further send the binding relationship among the target user account, the target user account identifier, the field end identifier, and the target field end account to the in-account server for storage, so as to provide the service subsequently.

Step S508, a field terminal account registration failure prompt is sent to the field terminal server.

In the embodiment of the invention, through the registration method of the field terminal account number in the second embodiment of the invention, the service scene server judges that if the user account number is registered/logged in the field terminal account number under other field terminals of the service scene, an authorization prompt is returned to the field terminal server, and a target field terminal account number corresponding to the field terminal identifier to be registered is generated according to the authorization result of the user; if the user account is not registered/logged in the terminal account under other terminals of the service scene, directly generating a target terminal account corresponding to the terminal identification to be registered, and returning the target user account to the terminal server so as to enable the user to use the terminal service.

Step S405, determining a target field end account corresponding to the field end identifier to be registered according to a second processing result returned by the service scene server.

In the embodiment of the invention, the field terminal server determines the target field terminal account corresponding to the field terminal identifier to be registered under the request user account according to the second processing result returned by the service scene server. Or sending a field end account registration failure prompt to the terminal, so that the user searches for the manual service for processing.

In the embodiment of the invention, by the method for registering the terminal account in the first embodiment of the invention, a field server processes a terminal account registration request, and if the terminal account is a user account registered/logged in by the current field, a login prompt is returned; and if not, the target field terminal account number is sent to the service scene server for processing, and the target field terminal account number is determined according to a second processing result returned by the service scene server, so that the user is ensured to share the field terminal service.

In the embodiment of the invention, after the user is successfully registered, the service scene server stores the first login state information of the user, so that the user does not need to frequently input information such as an account number, a password and the like to repeatedly log in the subsequent use process of the user, and only needs to initiate a service request, namely, the service scene server determines whether the user has a presence account number or not according to the information in the service request, namely, whether the user has the authority to access the presence service or not, and only needs to respond to the service request of the user through the presence server, so that the whole process of using the presence service by the user is noninductive, the use experience is greatly improved, and the user satisfaction is greatly improved.

Step S102, searching a local scene database, and determining whether first login state information exists according to the first user account and the first field end identifier; the business scene server stores the corresponding relation among the user account number, the field terminal identification, the field terminal account number and the login state information.

In the embodiment of the invention, a service scene server searches a local scene database according to a first user account number and a first field end identifier and locates first login state information. For example, the service request is a purchase request sent by a user through a shopping cart of the indonesian station, and the service scene server of the indonesian station searches a local scene database according to a first user account number of the purchase request and the shopping cart of the indonesian station, and locates first login state information of the user.

In an embodiment of the present invention, the login state information may be in the form of a cookie.

In the embodiment of the invention, the service scene server can store the corresponding relation between the user account number and the user Entity identification account number and the field end account number by using a scene account number system model (UEA model) so as to process the user information required by registration, login, inquiry, service request and the like.

Step S103, if yes, analyzing the first login state information, determining a first field end account number in the first login state information, and sending the first field end account number to a first field end server corresponding to the first field end identifier, so that the first field end server processes first data to be processed under the first field end account number.

In the embodiment of the invention, the service scene server field end server analyzes the first login state information, determines a first field end account number in the first login state information, sends the first field end account number to the first field end server corresponding to the first field end identifier, and the presence of the first field end account number indicates that the user is logged in, so that the first field end server can directly respond to a first service request of the user and process the first data to be processed. For example, adding merchandise to a shopping cart; and rejecting the first service request under the condition that the verification result is that the verification fails.

In the embodiment of the invention, a first service request of one or more field terminals is received; the first service request comprises a first user account, a first field end identifier and first data to be processed; searching a local scene database, and determining whether first login state information exists according to the first user account and the first field end identifier; the service scene server stores the corresponding relation among the user account number, the field terminal identifier, the field terminal account number and the login state information; if yes, the first login state information is analyzed, a first field end account number in the first login state information is determined, the first field end account number is sent to a first field end server corresponding to the first field end identification, so that the first field end server processes first data to be processed under the first field end account number, smooth use experience of a user can be achieved while service data of each field end and each entity are accurately distinguished, operations such as frequent registration and account number switching are not needed by the user, user satisfaction is improved, accurate splitting of the field end data can be achieved, service data of individuals and enterprises are analyzed in detail, and service promotion of a platform is promoted.

In an embodiment of the present invention, as shown in fig. 6 (a), a service request processing method according to a second embodiment of the present invention includes the following steps:

step S601, receiving one or more second service requests; the second service request comprises a second field end account number, a second field end identifier and second data to be processed.

In the embodiment of the present invention, the method for processing a service request according to the first embodiment of the present invention is applicable to each field terminal in a service scenario corresponding to a current service scenario server, unlike the method for processing a service request according to the first embodiment of the present invention, the method for processing a service request according to the second embodiment of the present invention is applicable to a jump request of other field terminals in a service scenario corresponding to a current service scenario server, or a jump request of each field terminal in a service scenario corresponding to other service scenario servers. Accordingly, the second field end account number may be the same as or different from the first field end account number, but the second field end identification is different from the first field end identification.

Step S602, determining whether the second field identifier belongs to a service scenario corresponding to the service scenario server, and if not, turning to step S603; if so, go to step S605.

In the embodiment of the invention, for example, the second service request is that the user jumps from the shopping cart of the domestic station to the shopping cart of the indonesian station, the second site is identified as the shopping cart of the indonesian station, and the service scene server is still the service scene of the domestic station, so that the shopping cart of the indonesian station does not belong to the domestic station.

Step S603, sending the second field end account number and the second field end identifier to a server in the account number, and receiving second login state information returned by the server in the account number; the second login state information is obtained by inquiring the account middle server according to the second field terminal account number and the second field terminal identification, and the account middle server stores the corresponding relation among the user account number, the field terminal identification, the field terminal account number and the login state information under different service scenes.

In the embodiment of the invention, aiming at the same user account, one user entity identifier in one service scene can only correspond to one user entity identifier in another service scene among different service scenes, namely, one user entity in one service scene can only be bound with one user entity in another service scene, and one user entity in one service scene is not allowed to be bound with a plurality of user entities in another service scene. For example, as shown in fig. 6 (b), the user entity identifier P1 in the service scenario P is bound to the user entity identifier Q1 in the service scenario Q, and cannot be bound to the user entity identifier Q2 or Q3 in the service scenario Q.

In the embodiment of the invention, before the account middle server issues login state information, whether the state of the field terminal account is valid or not needs to be confirmed, if the field terminal account is frozen, a failure reason (such as account freezing) is returned to the service scene server, and the service scene server transmits the failure reason to the corresponding field terminal server, so that a user can perform manual processing.

Further, if the login state information is not queried by the account middle server, returning a failure reason (for example, the account is not logged in) to the service scene server, and transmitting the failure reason to the corresponding field terminal server by the service scene server, so that the user performs login authorization, and the corresponding field terminal can be switched in a non-sensing manner when the user uses the corresponding field terminal next time after the user is authorized.

In the embodiment of the invention, the account middle server can store the corresponding relation of the user entities under different service scenes by using a middle account system model (namely a UEAP model).

Step S604, sending the second login state information and the second data to be processed to a service scene server corresponding to the second field identifier.

Step S605, query the scene database, and determine third login state information corresponding to the second field identifier.

In the embodiment of the invention, under the condition that the second field end identifier is determined to belong to the service scene corresponding to the service scene server, the service scene server queries a scene database and determines the third login state information corresponding to the second field end account.

Step S606, analyzing the third login state information, determining a third field end account in the third login state information, and sending the third field end account to a second field end server corresponding to the second field end identifier, so that the second field end server processes second data to be processed under the third field end account.

In the embodiment of the invention, by the service request processing method in the second embodiment of the invention, the service requests of jumping between different field terminals in one service scene or the service requests of jumping between each field terminal in different service scenes can be processed, and if the service requests are the field terminal jumping in one service scene, the field terminal account number of the jumping field terminal can be determined only by inquiring a local scene database by the service scene server; if the jump is among the field terminals of different service scenes, a query request is required to be sent to the account center server, a corresponding field terminal account is determined to send data to be processed, and a second service processing request is responded. The whole processing process is free of perception of users, the service scene server can extract service data of the users at each field end according to the field end account numbers, and the account center server can extract service data of each user entity according to the user entity identifications for independent analysis, so that smooth use experience of the users is realized while the service data of each field end and each entity are accurately distinguished, frequent registration, account number switching and other operations are not needed, user satisfaction is improved, and service promotion of a platform is promoted.

In the embodiment of the invention, the service scene server supports a login state deleting request (such as a wind control risk requirement) for deleting the login state information of each field end by a user, and the account center server supports a login state deleting request (such as a security risk requirement) for deleting the login state information of all service scenes by the user.

In the embodiment of the invention, the service scene server supports the user to log out, delete and prohibit logging in the field terminal account number of the corresponding field terminal, and when the user uses the corresponding field terminal again after logging out the field terminal account number, the field terminal account number needs to be regenerated.

Fig. 7 is a schematic diagram of main modules of a service request processing apparatus according to an embodiment of the present invention, and as shown in fig. 7, a service request processing apparatus 700 of the present invention includes:

a receiving module 701, configured to receive a first service request of the one or more field terminals; the first service request comprises a first user account, a first field end identifier and first data to be processed.

The searching module 702 is configured to search a local scene database, and determine whether first login state information exists according to the first user account and the first field identifier; the business scene server stores the corresponding relation among the user account number, the field terminal identification, the field terminal account number and the login state information.

And the parsing module 703 is configured to parse the first login state information, determine a first field end account in the first login state information, and send the first field end account to a first field end server corresponding to the first field end identifier, so that the first field end server processes first data to be processed under the first field end account.

In the embodiment of the invention, through the modules such as the receiving module, the searching module and the analyzing module, the service data of each field end and each entity can be accurately distinguished, the smooth use experience of the user is realized, the user is not required to perform operations such as frequent registration and account switching, the user satisfaction degree is improved, the accurate splitting of the field end data can be realized, the service data of individuals and enterprises can be analyzed in detail, and the service promotion of a platform is promoted.

Fig. 8 shows an exemplary system architecture diagram of a processing method of a service request or a processing apparatus of a service request suitable for application to an embodiment of the present invention, and as shown in fig. 8, an exemplary system architecture of a processing method of a service request or a processing apparatus of a service request of an embodiment of the present invention includes:

as shown in fig. 8, a system architecture 800 may include terminal devices 801, 802, 803, a network 804, and a server 805. The network 804 serves as a medium for providing communication links between the terminal devices 801, 802, 803 and the server 105. The network 804 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

A user may interact with the server 805 through the network 804 using the terminal devices 801, 802, 803 to receive or send messages or the like. Various communication client applications such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 801, 802, 803.

The terminal devices 801, 802, 803 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 805 may be a server providing various services, such as a background management server providing support for shopping-type websites browsed by the user using the terminal devices 801, 802, 803. The background management server may analyze and process the received data such as the shopping cart request, and feed back the processing result (for example, the processing result of the field end server) to the terminal devices 801, 802, 803.

It should be noted that, the method for processing a service request provided in the embodiment of the present invention is generally executed by the server 805, and accordingly, the processing device for the service request is generally disposed in the server 805.

It should be understood that the number of terminal devices, networks and servers in fig. 8 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Fig. 9 is a schematic diagram of a computer system suitable for use in implementing a terminal device or a server according to an embodiment of the present invention, and as shown in fig. 9, a computer system 900 of a terminal device or a server according to an embodiment of the present invention includes:

a Central Processing Unit (CPU) 901 which can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM903, various programs and data necessary for the operation of the system 900 are also stored. The CPU901, ROM902, and RAM903 are connected to each other through a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.

The following components are connected to the I/O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output portion 907 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 908 including a hard disk or the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 901.

The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor includes a receiving module, a lookup module, and an parsing module. The names of these modules do not limit the module itself in some cases, for example, the lookup module may also be described as "a module for looking up a local scene database, and determining whether the first login state information exists according to the first user account number and the first field identifier".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: receiving a first service request of the one or more field terminals; the first service request comprises a first user account, a first field end identifier and first data to be processed; searching a local scene database, and determining whether first login state information exists according to the first user account and the first field end identifier; the service scene server stores the corresponding relation among the user account number, the field terminal identifier, the field terminal account number and the login state information; if so, analyzing the first login state information, determining a first field end account number in the first login state information, and sending the first field end account number to a first field end server corresponding to the first field end identifier, so that the first field end server processes first data to be processed under the first field end account number.

According to the technical scheme of the embodiment of the invention, the account service abstraction is divided into mapping, association and authorization relations among different layers of UserName (user account), entity (user Entity identifier) and AppAccount (field end account), so that the service data of the user can be independent and the field end service can be enjoyed without sense. Namely, when the user account is distinguished from the field end, the user account is not required to be frequently registered and replaced for logging in, the front end experience of system bottom separation and smoothness is realized, and the development direction of adaptation to later supervision and business is supported.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. A processing method of service request is characterized in that the method is used for a service scene server, one service scene corresponds to one or more field terminals, and the service scene server stores the corresponding relation of user account numbers, field terminal identifiers, field terminal account numbers and login state information; the method comprises the following steps:

2. The method according to claim 1, wherein the service scenario server further stores a correspondence between a user entity identifier and a user account and a field account, and the user entity identifier is used for uniquely identifying an individual entity or a business entity;

under each service scene, one user entity identifier corresponds to one or more user accounts; in each service scene, one user entity identifier corresponds to one or more field end accounts.

3. The method as recited in claim 2, further comprising:

4. The method as recited in claim 1, further comprising:

5. The method as recited in claim 4, further comprising:

6. The method as recited in claim 4, further comprising:

7. The method as recited in claim 1, further comprising:

8. The method of claim 1, further comprising, prior to said receiving one or more first service requests:

9. The method according to claim 8, wherein the determining the target user account of the user account to be registered according to the category of the user entity information of the user account to be registered includes:

10. The method as recited in claim 8, further comprising:

11. The service request processing device is characterized in that the device is used for a service scene server, one service scene corresponds to one or more field terminals, and the service scene server stores the corresponding relation among a user account number, a field terminal identifier, a field terminal account number and login state information; the device comprises:

12. An electronic device for processing a service request, comprising:

one or more processors;

storage means for storing one or more programs,

when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-10.

13. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-10.