CN112560076B

CN112560076B - Program page display method and device, computer equipment and readable storage medium

Info

Publication number: CN112560076B
Application number: CN202110199267.8A
Authority: CN
Inventors: 方思维
Original assignee: Zhejiang Koubei Network Technology Co Ltd
Current assignee: Zhejiang Koubei Network Technology Co Ltd
Priority date: 2021-02-23
Filing date: 2021-02-23
Publication date: 2021-05-18
Anticipated expiration: 2041-02-23
Also published as: CN112560076A

Abstract

The application discloses a program page display method, a program page display device, computer equipment and a readable storage medium, which relate to the technical field of Internet and are used for converting login session information of a third-party platform into data in a service system domain, so that a service system determines a target service system brand which has a binding relationship with an account to be logged in the data in the service system domain according to the account to be logged in, displays a target program, can authenticate the account to be logged in the service system, and ensures the universality and compatibility of the small program. The method comprises the following steps: responding to the program login request, and determining an account to be logged in which the program login request is issued; acquiring data in a service system domain; inquiring a target third-party platform to which an account to be logged belongs, and extracting account information of the account to be logged from login session information of the target third-party platform; determining a target service system brand in the data in the service system domain; and determining a target program signed by the brand of the target service system, and displaying the signed program page of the target program.

Description

Program page display method and device, computer equipment and readable storage medium

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for displaying a program page, a computer device, and a readable storage medium.

Background

With the continuous development of the internet technology, more and more programs are supported and run by the terminal, and people can efficiently and accurately complete the processing of data through the programs, so that great convenience is brought to life and work. The traditional program is not convenient to use only by downloading and installing in a terminal, so that a small program is derived at present. The applet is a program which can be used without downloading and installing, can save the use time cost and the storage space of the terminal for people, and is widely applied to online shopping at present. And more third party platforms providing online shopping functions are provided, and the third party platforms are uniformly deployed on the service system and provide online shopping services for users based on the functions of the service system. The small program can be used universally in the third-party platforms, so that a user can purchase commodities in the small programs provided by the third-party platforms, meanwhile, the third-party platforms can also provide the login function of the small programs for the merchant, and after the merchant successfully logs in, the third-party platforms can display program pages related to the running conditions of the small programs for the merchant, so that the merchant can know the small programs conveniently.

Because the applet is common to a plurality of third-party platforms, based on the characteristic, a scene that a plurality of third-party platform channels log in the applet exists, each third-party platform can perform authentication on an account number requesting for logging, authentication logics of account numbers with the same identity of different platforms are different, and in order to guarantee the universality and compatibility of the applet and enable the applet to adapt to the authentication difference between the platforms, a method for authenticating a merchant and displaying a program page to the merchant is urgently needed.

Disclosure of Invention

In view of this, the present application provides a program page display method, apparatus, computer device and readable storage medium, and mainly aims to solve the problem of ensuring the universality and compatibility of an applet and enabling the applet to adapt to the difference of authority between platforms.

According to a first aspect of the present application, there is provided a program page display method, including:

responding to a program login request, and determining an account to be logged in for issuing the program login request;

acquiring data in a service system domain, wherein the data in the service system domain is obtained by performing information conversion on login session information of a plurality of third-party platforms accessed to a service system, and data fields in the data in the service system domain accord with the domain processing logic of the service system;

inquiring a target third-party platform to which the account to be logged belongs, and extracting account information of the account to be logged from login session information of the target third-party platform;

determining a target service system brand in the data in the service system domain, wherein the target service system brand and the account information have a direct or indirect binding relationship;

and determining a target program signed by the brand of the target service system, and displaying a signed program page of the target program.

Optionally, the acquiring data in the service system domain includes:

acquiring a plurality of login session information of the plurality of third party platforms based on the gateway system of each of the plurality of third party platforms;

for login session information of each third-party platform in the plurality of third-party platforms, splitting the login session information into a plurality of information items;

querying a data field corresponding to a character included in each of the plurality of information items in a third-party mapping relation table of the service system to obtain a plurality of data fields, using the plurality of data fields as data of the login session information in a platform domain of the service system, wherein the third-party mapping relation table includes a mapping relation between the character and the data field established based on the in-domain processing logic;

respectively determining platform domain data of each third-party platform in the plurality of third-party platforms to obtain a plurality of platform domain data;

and taking the plurality of platform domain data as the service system domain data.

Optionally, the determining a target service system brand in the service system domain data includes:

responding to the account information to indicate that the account to be logged in is the account with the highest control authority, and inquiring whether the account to be logged in has a bound service system brand in data in the service system domain;

if the account to be logged in has the bound service system brand, taking the service system brand bound by the account to be logged in as the target service system brand;

and if the account to be logged in does not have the bound service system brand, displaying a registration page and ending the current process.

responding to the account information to indicate that the account to be logged in is an employee account, determining the highest control authority account to which the account to be logged in belongs, and inquiring whether the highest control authority account has a bound service system brand in the data in the service system domain;

if the highest control authority account number has the bound service system brand, acquiring a first service system brand bound by the highest control authority account number, inquiring whether the account number to be logged in and the first service account number of the first service system brand have a binding relationship in data in the service system domain, outputting a first inquiry result, and determining the target service system brand according to the first inquiry result;

and if the highest control authority account number does not have the bound service system brand, displaying login failure prompt and ending the current process.

Optionally, the determining the target service system brand according to the first query result includes:

if the first query result indicates that the account to be logged in and the first service account do not have a binding relationship, displaying a binding page, acquiring an identifier to be bound input based on the binding page, querying whether the identifier to be bound is included in an identifier list provided based on the account with the highest control authority in the service system domain data, outputting a second query result, and acquiring the target service system brand according to the second query result;

and if the first query result indicates that the account to be logged in and the first service account have a binding relationship, querying employee permission corresponding to the account to be logged in data in the service system domain, and determining the brand of the target service system according to the employee permission.

Optionally, the obtaining the target service system brand according to the second query result includes:

if the second query result indicates that the identifier to be bound is included in the identifier list, binding the identifier to be bound with the account to be logged in, and taking the first service system brand bound by the account with the highest control authority as the target service system brand;

and if the second query result indicates that the identifier to be bound is not included in the identifier list, displaying a binding failure prompt and ending the current process.

Optionally, the querying, in the data in the service system domain, the employee authority corresponding to the account to be logged in, and determining the target service system brand according to the employee authority includes:

acquiring the employee authority corresponding to the account to be logged in from the data in the service system domain, and inquiring whether the employee authority comprises program access authority;

if the employee authority comprises the program access authority, taking the first service system brand bound by the highest control authority account as the target service system brand;

and if the employee authority does not include the program access authority, displaying an authority configuration prompt and ending the current process.

responding to the account information to indicate that the account to be logged in is a partner account, and inquiring whether the account to be logged in has a bound service system brand in data in the service system domain;

if the account to be logged in does not have the bound service system brand, displaying login failure prompt and ending the current process;

if the account to be logged in has the bound service system brand, acquiring a second service system brand bound to the account to be logged in, inquiring whether a binding relationship exists between the account to be logged in and the second service account of the second service system brand in the data in the service system domain, outputting a third inquiry result, and determining the target service system brand according to the third inquiry result.

Optionally, the determining the target service system brand according to the third query result includes:

if the third query result indicates that the account to be logged in and the second service account do not have a binding relationship, taking the second service system brand bound by the account to be logged in as the target service system brand, and completely forbidding the operation authority of the account to be logged in on the target service system brand;

and if the third query result indicates that the account to be logged in and the second service account have a binding relationship, querying management information corresponding to the second service account in the data in the service system domain, and determining the target service system brand according to the management information.

Optionally, the determining the target service system brand according to the management information includes:

if the management information indicates that the account identity of the account to be logged in does not have the management authority, taking the second service system brand bound by the account to be logged in as the target service system brand, and completely forbidding the operation authority of the account to be logged in on the target service system brand;

if the management information indicates that the account identity of the account to be logged in has management authority, taking the second service system brand bound by the account to be logged in as the target service system brand, and opening all operation authorities of the account to be logged in to the target service system brand.

Optionally, the method further comprises:

when the target program is determined to fail in the data in the service system domain, acquiring a preset un-signed page for indicating an un-signed program;

and displaying the preset non-signed page.

According to a second aspect of the present application, there is provided a program page presentation apparatus, comprising:

the first determination module is used for responding to a program login request and determining an account to be logged in for issuing the program login request;

the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring data in a service system domain, the data in the service system domain is obtained by carrying out information conversion on login session information of a plurality of third party platforms accessed to the service system, and data fields in the data in the service system domain accord with the domain processing logic of the service system;

the query module is used for querying a target third-party platform to which the account to be logged belongs and extracting account information of the account to be logged from login session information of the target third-party platform;

the second determination module is used for determining a target service system brand in the data in the service system domain, and the target service system brand and the account information have a direct or indirect binding relationship;

and the display module is used for determining the target program signed by the target service system brand and displaying the signed program page of the target program.

Optionally, the first obtaining module is configured to obtain, based on a gateway system of each of the plurality of third-party platforms, a plurality of login session information of the plurality of third-party platforms; for login session information of each third-party platform in the plurality of third-party platforms, splitting the login session information into a plurality of information items; querying a data field corresponding to a character included in each of the plurality of information items in a third-party mapping relation table of the service system to obtain a plurality of data fields, using the plurality of data fields as data of the login session information in a platform domain of the service system, wherein the third-party mapping relation table includes a mapping relation between the character and the data field established based on the in-domain processing logic; respectively determining platform domain data of each third-party platform in the plurality of third-party platforms to obtain a plurality of platform domain data; and taking the plurality of platform domain data as the service system domain data.

Optionally, the second determining module is configured to, in response to that the account information indicates that the account to be logged in is the highest control authority account, query, in data in the service system domain, whether the account to be logged in has a bound brand of the service system; if the account to be logged in has the bound service system brand, taking the service system brand bound by the account to be logged in as the target service system brand; and if the account to be logged in does not have the bound service system brand, displaying a registration page and ending the current process.

Optionally, the second determining module is configured to determine, in response to that the account information indicates that the account to be logged in is an employee account, a highest control authority account to which the account to be logged in belongs, and query, in data in the service system domain, whether the highest control authority account has a bound service system brand; if the highest control authority account number has the bound service system brand, acquiring a first service system brand bound by the highest control authority account number, inquiring whether the account number to be logged in and the first service account number of the first service system brand have a binding relationship in data in the service system domain, outputting a first inquiry result, and determining the target service system brand according to the first inquiry result; and if the highest control authority account number does not have the bound service system brand, displaying login failure prompt and ending the current process.

Optionally, the second determining module is configured to, if the first query result indicates that the account to be logged in and the first service account do not have a binding relationship, display a binding page, obtain an identifier to be bound, which is input based on the binding page, query, in data in the service system domain, whether the identifier to be bound is included in an identifier list provided based on the account with the highest control authority, output a second query result, and obtain the target service system brand according to the second query result; and if the first query result indicates that the account to be logged in and the first service account have a binding relationship, querying employee permission corresponding to the account to be logged in data in the service system domain, and determining the brand of the target service system according to the employee permission.

Optionally, the second determining module is configured to, if the second query result indicates that the identifier to be bound is included in the identifier list, bind the identifier to be bound with the account to be logged in, and use the first service system brand bound by the account with the highest control authority as the target service system brand; and if the second query result indicates that the identifier to be bound is not included in the identifier list, displaying a binding failure prompt and ending the current process.

Optionally, the second determining module is configured to acquire the employee permission corresponding to the account to be logged in from data in the service system domain, and query whether the employee permission includes a program access permission; if the employee authority comprises the program access authority, taking the first service system brand bound by the highest control authority account as the target service system brand; and if the employee authority does not include the program access authority, displaying an authority configuration prompt and ending the current process.

Optionally, the second determining module is configured to, in response to the account information indicating that the account to be logged in is a partner account, query, in data in the service system domain, whether the account to be logged in has a bound brand of the service system; if the account to be logged in does not have the bound service system brand, displaying login failure prompt and ending the current process; if the account to be logged in has the bound service system brand, acquiring a second service system brand bound to the account to be logged in, inquiring whether a binding relationship exists between the account to be logged in and the second service account of the second service system brand in the data in the service system domain, outputting a third inquiry result, and determining the target service system brand according to the third inquiry result.

Optionally, the second determining module is configured to, if the third query result indicates that the account to be logged in and the second service account do not have a binding relationship, take the second service system brand bound to the account to be logged in as the target service system brand, and disable all operation permissions of the account to be logged in on the target service system brand; and if the third query result indicates that the account to be logged in and the second service account have a binding relationship, querying management information corresponding to the second service account in the data in the service system domain, and determining the target service system brand according to the management information.

Optionally, the second determining module is configured to, if the management information indicates that the account identity of the account to be logged in does not have the management authority, use the second service system brand bound to the account to be logged in as the target service system brand, and disable all the operation authorities of the account to be logged in on the target service system brand; if the management information indicates that the account identity of the account to be logged in has management authority, taking the second service system brand bound by the account to be logged in as the target service system brand, and opening all operation authorities of the account to be logged in to the target service system brand.

Optionally, the apparatus further comprises:

a second obtaining module, configured to obtain a preset un-signed page used for indicating an un-signed program when it is determined that the target program fails in the data in the service system domain;

and the display module is used for displaying the preset non-signed page.

According to a third aspect of the present application, there is provided a computer device comprising a memory storing a computer program and a processor implementing the steps of the method of the first aspect when the processor executes the computer program.

According to a fourth aspect of the present application, there is provided a readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the method of the first aspect described above.

By the technical scheme, the program page display method, the device, the computer equipment and the readable storage medium provided by the application convert login session information related to program login in a plurality of third party platforms accessed into a service system into service system domain data conforming to domain processing logic of the service system, so that the service system directly inquires and determines a target service system brand in binding relationship with the account to be logged in from integrated service system domain data according to the account identity of the account to be logged in when receiving a program login request, displays signed program pages of a target program signed by the target service system brand, directly adopts service system domain data to realize the right of account login by converting the login session information of the third party platforms into the service system domain data of the service system, the method can not be influenced by the authority logic of different third-party platforms, and the applet can adapt to the difference of the authority of different third-party platforms, so that the universality and compatibility of the applet are guaranteed.

The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 shows a flowchart of a program page display method provided in an embodiment of the present application;

fig. 2A is a schematic flowchart illustrating a program page display method according to an embodiment of the present application;

FIG. 2B is a diagram illustrating a program page display method according to an embodiment of the present disclosure;

fig. 2C is a schematic flowchart illustrating a program page display method according to an embodiment of the present application;

fig. 3A is a schematic structural diagram illustrating a program page display device according to an embodiment of the present application;

FIG. 3B is a schematic structural diagram illustrating a program page display apparatus according to an embodiment of the present disclosure;

fig. 4 shows a schematic device structure diagram of a computer apparatus according to an embodiment of the present application.

Detailed Description

Exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

An embodiment of the present application provides a program page display method, as shown in fig. 1, the method includes:

101. and responding to the program login request, and determining the account to be logged in which the program login request is issued.

102. Obtaining data in the service system domain, wherein the data in the service system domain is obtained by performing information conversion on login session information of a plurality of third-party platforms accessed to the service system, and data fields in the data in the service system domain conform to the domain processing logic of the service system.

103. And inquiring a target third-party platform to which the account to be logged belongs, and extracting account information of the account to be logged from the login session information of the target third-party platform.

104. And determining a target service system brand in the data in the service system domain, wherein the target service system brand and the account information have a direct or indirect binding relationship.

105. And determining a target program signed by the brand of the target service system, and displaying the signed program page of the target program.

The method provided by the embodiment of the application converts login session information related to program login in a plurality of third party platforms accessed into a service system into service system domain data which accords with domain processing logic of the service system, so that the service system directly extracts account information from the login session information of a target third party platform to which an account to be logged belongs when receiving a program login request, inquires and determines a target service system brand which has direct or indirect binding relationship with the account to be logged in integrated service system domain data, displays a signed program page of a target program signed by the target service system brand, and realizes authentication of the account to be logged in the service system by directly adopting service system domain data through converting the login session information of the third party platforms into the service system domain data of the service system, the method can not be influenced by the authority logic of different third-party platforms, and the applet can adapt to the difference of the authority of different third-party platforms, so that the universality and compatibility of the applet are guaranteed.

An embodiment of the present application provides a program page display method, as shown in fig. 2A, the method includes:

201. and responding to the program login request, and determining the account to be logged in which the program login request is issued.

In recent years, with the favor of people to the applets, more and more merchants create the applets of their stores, and increase popularity for the stores while meeting the daily shopping demands of people. The applet is provided by the terminal application and depends on a third party platform of the terminal application during running, and the third party platform is deployed on a Service system, such as a Software-as-a-Service (SaaS a Service) Service system, and provides a Service for online shopping for a user based on the function of the Service system. With the increase of the number of third-party platforms uniformly deployed on a service system, some applets are two-code applets at present, grow in a plurality of third-party platforms and are universal in the plurality of third-party platforms, and thus merchants are prevented from repeatedly creating the same applets in different third-party platforms. However, applicants have recognized that based on the feature that a two-code applet grows in multiple different third party platforms, there may be scenarios where multiple third party platform channels log on the applet. Actually, each third-party platform performs authentication on the merchant requesting for login, the authentication scheme of each third-party platform is logically different, but actually, the data used for account authentication of different identities are the same, so in order to ensure the universality and compatibility of the applet and enable the applet to adapt to the difference of the authentication between the platforms, a method for authenticating the merchant and displaying a program page to the merchant is urgently needed. Therefore, the application provides a program page display method, which converts login session information related to program login in a plurality of third party platforms accessed into a service system into service system domain data conforming to domain processing logic of the service system, so that the service system directly extracts account information from login session information of a target third party platform to which an account to be logged in belongs when receiving a program login request, inquires and determines a target service system brand which has direct or indirect binding relationship with the account to be logged in the integrated service system domain data, displays a signed program page of a target program signed by the target service system brand, and directly adopts service system domain data to realize the right identification of the account to be logged in the service system by converting the login session information of the third party platform into the service system domain data of the service system, the method can not be influenced by the authority logic of different third-party platforms, and the applet can adapt to the difference of the authority of different third-party platforms, so that the universality and compatibility of the applet are guaranteed.

Therefore, when a user requests to log in an applet, the service system receives a program login request of the user, determines an account to be logged in which the program login request is issued, further determines a target service brand which has a binding relationship with the account to be logged in according to the account identity of the account to be logged in the following, and determines a corresponding target program through the target service brand.

202. And acquiring data in the service system domain.

In the embodiment of the application, since the main basis for authenticating the right of the account to be logged in is service system domain data obtained based on the login session information of the plurality of third party platforms, the service system acquires the service system domain data, and then determines the target service brand for the account to be logged in according to the record of the service system domain data in the follow-up process. The data in the service system domain is obtained by performing information conversion on login session information of a plurality of third party platforms accessing the service system according to the domain processing logic of the service system, wherein the login session information is recorded with data which needs to be verified when accounts with different account identities log in, and the specific conversion process is as follows:

firstly, the service system acquires a plurality of login session information of a plurality of third-party platforms based on a gateway system of each of the plurality of third-party platforms. The service system is provided with a third-party mapping relation table which comprises a mapping relation between characters and data fields established based on intra-domain processing logic. Therefore, for the login session information of each third-party platform in the plurality of third-party platforms, the service system divides the login session information into a plurality of information items, inquires a data field corresponding to a character included in each information item in the plurality of information items in the third-party relational mapping table to obtain a plurality of data fields, uses the plurality of data fields as platform preparation data of the login session information in the service system, respectively determines platform intra-domain data of each third-party platform in the plurality of third-party platforms to obtain a plurality of platform intra-domain data, and uses the plurality of platform intra-domain data as service system intra-domain data. In a specific application scenario, for the SaaS service system, the third-party mapping relationship table may be an out _ relationship database table, and a mapping relationship between information in the SaaS domain and information of an organization account of a third-party platform ISV (Independent Software developers) and the like is recorded in the table. Therefore, the login session information of each third-party platform can be converted into corresponding information data in the SaaS domain through matching the login session information of the third-party platforms in the table, and information data fields of different third-party platforms are converted into information fields corresponding to the SaaS platforms, so that the subsequent logic processing of related information in the SaaS domain is facilitated.

Referring to fig. 2B, assuming that the service system is a SaaS system, the SaaS system may be provided with the gateway system shown in fig. 2B, and based on the docking of the gateway system with the third party platforms A, B, C and D, login session information of the third party platforms A, B, C and D is obtained respectively. And then, a session adaptation tool layer of the SaaS system performs data conversion on the login session information of the third-party platform according to the set third-party mapping relation table to obtain the data in the service system domain, and further applies the data in the service system domain to each service in the SaaS system.

It should be noted that, in the embodiment of the present invention, an example of acquiring data in the service system domain when a program login request is received is taken as an example for description. In the process of practical application, data in the service system domain can be prepared in advance, and a target service brand which has a binding relationship with an account to be logged of a issued program login request is directly determined in the data in the service system domain when the program login request is received. The present application does not specifically limit the timing of acquiring data in the service system domain.

203. And inquiring a target third-party platform to which the account to be logged belongs, and extracting account information of the account to be logged from the login session information of the target third-party platform.

In the embodiment of the application, since the service system is interfaced with a plurality of third party platforms, each third party platform is provided with a plurality of accounts with different account identities, for example, the account identity is a merchant or an employee or a partner of a gate in an area, etc., the accounts with different account identities have different rights, which page is displayed after logging in is also related to the account identity, and the data used by different third party platforms for authorizing accounts with different account identities are the same, therefore, in order to adapt to the difference of authentication of the account numbers by different third-party platforms, the service system queries the target third-party platform to which the account number to be logged in belongs, extracting account information of the account to be logged in from the login session information of the target third-party platform, and then, determining a target service system brand which has a binding relationship with the account to be logged in the data in the service system domain according to the account information. The small programs are marked in the service system according to the service brands, so that the small programs to be logged in can be determined by determining the target service brands which have binding relations with the account numbers to be logged in, whether the target programs related to the target service system brands are displayed or not is further determined according to the account number information, and the right identification is carried out on the account numbers to be logged in according to the account number information.

When the account information is acquired, because the login session information of the third-party platform is stored in the service system, the target third-party platform to which the account to be logged in belongs can be directly inquired, and the account information of the account to be logged in is extracted from the login session information of the target third-party platform. Specifically, the account information may include an account ID, a login mobile phone number, a login third party ID, and the like, and the content of the account information is not specifically limited in the present application.

204. And determining a target service system brand in the service system domain data.

In the embodiment of the application, after the account information is determined, the service system determines the brand of the target service system in the data in the service system domain. The account identities of the accounts to be logged in are three conditions, namely a merchant, an employee and a partner, the merchant usually has the highest control authority and is the account with the highest control authority, and the accounts of the employee and the partner have an association relationship with the corresponding account with the highest control authority. Therefore, for the account with different account identities, the service system determines the target service brand by using different information and processes, the target service system brand and the account information have a direct or indirect binding relationship, and the following describes the process of determining the target service brand by using the three account identities respectively:

the account information indicates that the account to be logged in is the highest control authority account.

The account with the highest control authority is actually an account with a higher authority in an area or a store, has a larger management authority, and is usually provided with an account identity of an employee or a partner, and such an account may directly have a binding relationship with a service brand in a service system, such as an ID of a company, an ID of a merchant, and the like. Therefore, in response to the account information indicating that the account to be logged in is the highest control authority account, considering the characteristic that the account can be bound with the service brand, the service system can directly inquire whether the account to be logged in has the bound service system brand in the data in the service system domain. And if the account to be logged in has the bound service system brand, taking the service system brand bound by the account to be logged in as a target service system brand, and further taking the applet signed by the target service system brand as the applet to be logged in later. If the account to be logged in does not have the bound service system brand, the account identity indicates that the account to be logged in of the merchant does not complete the registration in the service system, so the service system displays a registration page, prompts a registration operation based on the account to be logged in, performs a registration process according to the operation, and ends the current process of determining the target service system brand.

And secondly, the account information indicates that the account to be logged in is an employee account.

The employee account is actually an account under a certain highest control authority account, so that the target system brand needs to be determined according to the highest control authority account to which the account to be logged in belongs. Therefore, when the account information indicates that the account to be logged in is an employee account, the service system determines the highest control authority account to which the account to be logged in belongs, and queries whether the highest control authority account has a bound service system brand in data in the service system domain. And if the highest control authority account number has the bound service system brand, acquiring the first service system brand bound by the highest control authority account number. Actually, the employee account authenticated by the merchant and the first service system brand also have a binding relationship, and the binding relationship is embodied between the employee account and the service account of the first service system brand, so that after the first service system brand bound by the highest control authority account is determined, the service system further queries whether the account to be logged in and the first service account of the first service system brand have the binding relationship in data in the service system domain, outputs a first query result, and further determines the target service system brand according to the first query result. If the highest control authority account does not have a bound service system brand, the account identity indicates that a merchant to which the account to be logged in of the employee belongs is not bound with the service brand in the service system, and at present, subsequent login operation cannot be executed, so that the service system displays login failure prompt and ends the current process.

Further, when the brand of the target service system is further determined according to the first query result, on one hand, if the first query result indicates that the account to be logged in does not have a binding relationship with the first service account, a binding operation needs to be provided for the account to be logged in, so that the account to be logged in enters a binding process, and the account to be logged in is bound with the first service account. However, the binding is premised on that a merchant to which the account to be logged in belongs is allowed to bind, and when the merchant sets the employee, the contact manner of the employee is usually arranged into an identification list to be provided for the service system, and the identification included in the identification list indicates the employee allowed to be bound by the merchant, so that the service system displays a binding page, acquires the identifier to be bound input based on the binding page, and the identifier to be bound is also the contact manner input by the user who currently requests to log in, further queries whether the identifier to be bound is included in the identification list provided based on the account with the highest control authority in the data in the service system domain, outputs a second query result, and continues to acquire the brand of the target service system according to the second query result. And if the second query result indicates that the to-be-bound identifier is included in the identifier list, the to-be-bound identifier currently input is authenticated by the merchant, so that the service system can bind the to-be-bound identifier and the to-be-registered account in order to facilitate next login of the to-be-registered account, and the first service system brand bound by the account with the highest control authority is used as the target service system brand. And if the second query result indicates that the to-be-bound identifier is not included in the identifier list, the currently input to-be-bound identifier is not authenticated by the merchant, so that a binding failure prompt is displayed, and the current login process is ended.

On the other hand, if the first query result indicates that the account to be logged in and the first service account have a binding relationship, the service system needs to further query employee permissions corresponding to the account to be logged in data in the service system domain, and continue to determine the target service system brand according to the employee permissions. Therefore, the service system can acquire the employee authority corresponding to the account to be logged in from the data in the service system domain, and inquire whether the employee authority includes the program access authority. After the employee authority is inquired, if the employee authority comprises program access authority, the account to be logged in is indicated to be allowed to be logged in the program, therefore, the service system takes the first service system brand bound by the account with the highest control authority as a target service system brand, and then program login and page jump are realized according to the target service system brand in the follow-up process. If the employee authority does not include the program access authority, the current account to be logged in cannot be logged in by the program, so the service system can display the authority configuration prompt, remind the businessman to configure the authority of the employee, and end the current login process. It should be noted that, when the employee authority is actually verified, a reverse verification mode may also be adopted. During reverse verification, the program page can be directly displayed to the staff, and different authorities are needed for accessing different modules in the program page. For example, entering a function module for viewing applet data requires that the employee have the corresponding authority a. In this way, when the functional module for viewing the applet data of the program page is detected to be triggered, whether the authority of the employee comprises the authority A is inquired; if the authority A is included, continuously displaying related data and information; and if the authority A is not included, displaying an authority configuration prompt, reminding the businessman to configure the authority of the employee, and ending the current login process. The manner in which the employee permissions are verified is not specifically limited.

And thirdly, the account information indicates that the account to be logged in is a partner account.

The account of the partner is actually an account having a cooperative relationship with a certain service system brand, and a plurality of accounts with the identity of the partner may exist in a certain service brand, so the account with the identity of the partner is generally managed integrally based on the service system brand and the service account of the service system brand. Therefore, when the account information indicates that the account to be logged in is a partner account, the service system firstly queries whether the account to be logged in has a bound service system brand in data in the service system domain. If the account to be logged in does not have the bound service system brand, the account to be logged in can be directly determined to have no related service system brand, the login request of the account to be logged in is blocked, therefore, the login failure prompt is displayed, and the current process is ended. And if the account to be logged in has the bound service system brand, acquiring a second service system brand bound by the account to be logged in, inquiring whether the account to be logged in has a binding relationship with a second service account of the second service system brand in data in a service system domain, outputting a third inquiry result, and determining a target service system brand according to the third inquiry result.

If the third query result indicates that the account to be logged in and the second service account are not in the binding relationship, the second service system brand bound by the account to be logged in is used as the target service system brand, and the operation permission of the account to be logged in on the target service system brand is completely disabled, that is, the account to be logged in can be logged in a target program signed by the target service system brand, but any operation cannot be performed. And if the third query result indicates that the account to be logged in and the second service account have the binding relationship, the service system queries management information corresponding to the second service account in the data in the service system domain, and determines the brand of the target service system according to the management information.

Further, if the management information indicates that the account identity of the account to be logged in does not have the management authority, the second service system brand bound to the account to be logged in is used as the target service system brand, and the operation authority of the account to be logged in on the target service system brand is completely disabled, that is, the account to be logged in can be subsequently logged in a target program signed by the target service system brand, but any operation cannot be performed. And if the management information indicates that the account identity of the account to be logged in has the management authority, taking the second service system brand bound by the account to be logged in as the target service system brand, and opening all the operation authorities of the account to be logged in on the target service system brand, that is, after the subsequent account to be logged in logs in a target program signed by the target service system brand, the functions in the target program can be normally used.

Therefore, the target service system brand which determines the binding relationship of the account to be logged in is completed, the binding relationship does not limit the direct binding relationship between the target service system brand and the account to be logged in, and the indirect binding relationship between the account to be logged in and the target service system brand is also involved.

205. Determining a target program signed by a target service system brand in the data in the service system domain, and executing the following step 206 when the target program is determined to be successful in the data in the service system domain; when it is determined that the target program fails in the data within the service system domain, the following step 207 is performed.

In this embodiment of the present application, after the brand of the target service system is determined, it can be determined in which program the login operation of the account to be logged in needs to be performed, so that the service system determines the target program signed by the brand of the target service system in the data in the service system domain, and when the target program is determined to be successful in the data in the service system domain, it indicates that the brand of the target service system has signed the applet, so that the signed program page of the target program is displayed, the account to be logged in is controlled to be successfully logged in the target program, and the account to be logged in is normally logged in the target program for use, that is, the following step 206 is performed. When it is determined that the target program fails in the data in the service system domain, it indicates that the target service system brand has not signed the applet yet, and the login of the account to be logged in the applet cannot be realized, and it is necessary to remind the user that the target service system brand has not been signed yet, so that a preset un-signed page indicating an un-signed program is obtained, and the preset un-signed page is displayed, that is, the following step 207 is performed.

206. And when the target program is determined to be successful in the data in the service system domain, displaying the signed program page of the target program.

In the embodiment of the application, when the target program is determined to be successful in the data in the service system domain, the target service system brand is indicated to have signed the applet, so that the signed program page of the target program is displayed, the account to be logged in is controlled to be logged in the target program successfully, and the account to be logged in is normally logged in and used in the target program.

207. And when the target program is determined to fail in the data in the service system domain, acquiring a preset non-signed page for indicating a non-signed program, and displaying the preset non-signed page.

In the embodiment of the application, when it is determined that the target program fails in the data in the service system domain, it indicates that the target service system brand has not signed the applet yet, and the login of the account to be logged in the applet cannot be realized, and it is necessary to remind a user that the target service system brand has not signed yet, so that a preset un-signed page used for indicating an un-signed program is obtained, and the preset un-signed page is displayed.

In summary, the whole process of authenticating the account to be logged in and displaying the corresponding program page is summarized as follows:

referring to fig. 2C, the account to be logged in to which the program login request is issued is determined. And when the account information indicates that the account to be logged in is the highest control authority account, inquiring whether the account to be logged in is bound with the brand of the service system in the data in the domain of the service system. And if the service system brand is determined to be bound, checking whether the service system brand signs a target program or not, if the service system brand signs a signature, directly jumping to a signed program page of the target program, and if the service system brand does not sign a signature, displaying a preset unsigned page. And if the service system brand is determined not to be bound, entering a registration process of the account to be logged in.

And when the account information indicates that the account to be logged in is an employee account, inquiring whether the highest control authority account to which the account to be logged in belongs is bound with a service system brand or not in data in a service system domain. And if the brand of the service system is not bound, blocking the current login process and displaying login failure prompt. And if the service system brand is bound, continuously inquiring whether the account to be logged in and the service account of the bound service system brand have a binding relationship. On one hand, if the binding relationship exists, whether the employee authority corresponding to the account to be logged in includes the program access authority is inquired in the data in the service system domain. And if the program does not contain the program access authority, blocking the current login process and prompting to carry out authority configuration. And if the program access authority is included, checking whether the service system brand has a signed target program or not, if the service system brand has the signed target program, directly jumping to a signed program page of the target program, and if the service system brand has no signed target program, displaying a preset unsigned page. And if the service system brand is determined not to be bound, entering a registration process of the account to be logged in. On the other hand, if the binding relationship does not exist, jumping to a binding page, acquiring an identifier to be bound (namely a contact way such as a mobile phone number) input based on the binding page, and inquiring whether the identifier to be bound is included in an identifier list provided based on the account with the highest control authority in data in the service system domain. And if the identifier list does not comprise the identifier to be bound, blocking the current login process and prompting that the identifier to be bound does not create an account. And if the identifier list comprises the identifier to be bound, directly jumping to the signed program page of the target program.

And when the account information indicates that the account to be logged in is a partner account, inquiring whether the account to be logged in is bound with a service system brand in data in the service system domain. On one hand, if the service system brand is bound, whether a binding relationship exists between the account to be logged in and the service account of the bound service system brand is inquired. If the binding relationship exists, whether the management information of the account to be logged in exists is inquired through the service account, and if so, the account to be logged in is controlled to be logged in the applet, so that the account to be logged in has all the authority of operating the applet. If the operation is not performed, only the account to be logged in is controlled to log in the applet, and all the authority of the account to be logged in on the operation of the applet is forbidden. On the other hand, if the brand of the service system is not bound or the account to be logged in and the service account of the bound brand of the service system do not have a binding relationship, the current login process is blocked, and login failure is prompted.

Further, as a specific implementation of the method shown in fig. 1, an embodiment of the present application provides a program page display apparatus, and as shown in fig. 3A, the apparatus includes: a first determining module 301, a first obtaining module 302, a querying module 303, a second determining module 304 and a presenting module 305.

The first determining module 301 is configured to determine, in response to a program login request, an account to be logged in for issuing the program login request;

the first obtaining module 302 is configured to obtain data in a service system domain, where the data in the service system domain is obtained by performing information conversion on login session information of multiple third party platforms accessing a service system, and a data field in the data in the service system domain conforms to an intra-domain processing logic of the service system;

the query module 303 is configured to query a target third-party platform to which the account to be logged belongs, and extract account information of the account to be logged from login session information of the target third-party platform;

the second determining module 304 is configured to determine a target service system brand in the data in the service system domain, where the target service system brand and the account information have a direct or indirect binding relationship;

the display module 305 is configured to determine a target program signed by the target service system brand, and display a signed program page of the target program.

In a specific application scenario, the first obtaining module 302 is configured to obtain, based on a gateway system of each of the third party platforms, multiple login session information of the third party platforms; for login session information of each third-party platform in the plurality of third-party platforms, splitting the login session information into a plurality of information items; querying a data field corresponding to a character included in each of the plurality of information items in a third-party mapping relation table of the service system to obtain a plurality of data fields, using the plurality of data fields as data of the login session information in a platform domain of the service system, wherein the third-party mapping relation table includes a mapping relation between the character and the data field established based on the in-domain processing logic; respectively determining platform domain data of each third-party platform in the plurality of third-party platforms to obtain a plurality of platform domain data; and taking the plurality of platform domain data as the service system domain data.

In a specific application scenario, the second determining module 304 is configured to, in response to that the account information indicates that the account to be logged in is the highest control authority account, query, in data in the service system domain, whether the account to be logged in has a bound service system brand; if the account to be logged in has the bound service system brand, taking the service system brand bound by the account to be logged in as the target service system brand; and if the account to be logged in does not have the bound service system brand, displaying a registration page and ending the current process.

In a specific application scenario, the second determining module 304 is configured to determine, in response to that the account information indicates that the account to be logged in is an employee account, a highest control authority account to which the account to be logged in belongs, and query, in data in the service system domain, whether the highest control authority account has a bound service system brand; if the highest control authority account number has the bound service system brand, acquiring a first service system brand bound by the highest control authority account number, inquiring whether the account number to be logged in and the first service account number of the first service system brand have a binding relationship in data in the service system domain, outputting a first inquiry result, and determining the target service system brand according to the first inquiry result; and if the highest control authority account number does not have the bound service system brand, displaying login failure prompt and ending the current process.

In a specific application scenario, the second determining module 304 is configured to, if the first query result indicates that the account to be logged in and the first service account do not have a binding relationship, display a binding page, obtain an identifier to be bound that is input based on the binding page, query, in data in the service system domain, whether the identifier to be bound is included in an identifier list that is provided based on the account with the highest control authority, output a second query result, and obtain the target service system brand according to the second query result; and if the first query result indicates that the account to be logged in and the first service account have a binding relationship, querying employee permission corresponding to the account to be logged in data in the service system domain, and determining the brand of the target service system according to the employee permission.

In a specific application scenario, the second determining module 304 is configured to, if the second query result indicates that the identifier to be bound is included in the identifier list, bind the identifier to be bound with the account to be logged in, and use the first service system brand bound by the account with the highest control authority as the target service system brand; and if the second query result indicates that the identifier to be bound is not included in the identifier list, displaying a binding failure prompt and ending the current process.

In a specific application scenario, the second determining module 304 is configured to obtain the employee permission corresponding to the account to be logged in from data in the service system domain, and query whether the employee permission includes a program access permission; if the employee authority comprises the program access authority, taking the first service system brand bound by the highest control authority account as the target service system brand; and if the employee authority does not include the program access authority, displaying an authority configuration prompt and ending the current process.

In a specific application scenario, the second determining module 304 is configured to, in response to that the account information indicates that the account to be logged in is a partner account, query, in data in the service system domain, whether the account to be logged in has a bound service system brand; if the account to be logged in does not have the bound service system brand, displaying login failure prompt and ending the current process; if the account to be logged in has the bound service system brand, acquiring a second service system brand bound to the account to be logged in, inquiring whether a binding relationship exists between the account to be logged in and the second service account of the second service system brand in the data in the service system domain, outputting a third inquiry result, and determining the target service system brand according to the third inquiry result.

In a specific application scenario, the second determining module 304 is configured to, if the third query result indicates that the account to be logged in and the second service account do not have a binding relationship, use the second service system brand bound by the account to be logged in as the target service system brand, and disable all operation permissions of the account to be logged in on the target service system brand; and if the third query result indicates that the account to be logged in and the second service account have a binding relationship, querying management information corresponding to the second service account in the data in the service system domain, and determining the target service system brand according to the management information.

In a specific application scenario, the second determining module 304 is configured to, if the management information indicates that the account identity of the account to be logged in does not have the management authority, use the second service system brand bound to the account to be logged in as the target service system brand, and disable all the operation authorities of the account to be logged in on the target service system brand; if the management information indicates that the account identity of the account to be logged in has management authority, taking the second service system brand bound by the account to be logged in as the target service system brand, and opening all operation authorities of the account to be logged in to the target service system brand.

In a specific application scenario, as shown in fig. 3B, the apparatus further includes: a second acquisition module 306.

The second obtaining module 306 is configured to, when it is determined that the target program fails in the data in the service system domain, obtain a preset unsigned page indicating an unsigned program;

the displaying module 305 is configured to display the preset unsigned page.

The device provided by the embodiment of the application converts login session information related to program login in a plurality of third party platforms accessed into a service system into service system domain data which accords with domain processing logic of the service system, so that the service system directly extracts account information from the login session information of a target third party platform to which an account to be logged belongs when receiving a program login request, inquires and determines a target service system brand which has direct or indirect binding relationship with the account to be logged in integrated service system domain data, displays a signed program page of a target program signed by the target service system brand, and realizes authentication of the account to be logged in the service system by directly adopting service system domain data through converting the login session information of the third party platforms into the service system domain data of the service system, the method can not be influenced by the authority logic of different third-party platforms, and the applet can adapt to the difference of the authority of different third-party platforms, so that the universality and compatibility of the applet are guaranteed.

It should be noted that other corresponding descriptions of the functional units related to the program page display device provided in the embodiment of the present application may refer to the corresponding descriptions in fig. 1 and fig. 2A, and are not described herein again.

In an exemplary embodiment, referring to fig. 4, there is further provided a device including a communication bus, a processor, a memory, and a communication interface, and further including an input/output interface and a display device, wherein the functional units may communicate with each other through the bus. The memory stores computer programs, and the processor is used for executing the programs stored in the memory and executing the program page display method in the embodiment.

A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the program page presentation method.

Through the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented by hardware, and also by software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.), and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the implementation scenarios of the present application.

Those skilled in the art will appreciate that the figures are merely schematic representations of one preferred implementation scenario and that the blocks or flow diagrams in the figures are not necessarily required to practice the present application.

Those skilled in the art will appreciate that the modules in the devices in the implementation scenario may be distributed in the devices in the implementation scenario according to the description of the implementation scenario, or may be located in one or more devices different from the present implementation scenario with corresponding changes. The modules of the implementation scenario may be combined into one module, or may be further split into a plurality of sub-modules.

The above application serial numbers are for description purposes only and do not represent the superiority or inferiority of the implementation scenarios.

The above disclosure is only a few specific implementation scenarios of the present application, but the present application is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present application.

Claims

1. A program page display method is characterized by comprising the following steps:

acquiring data in a service system domain, wherein the data in the service system domain is obtained by performing information conversion on login session information of a plurality of third-party platforms accessing a service system, data fields in the data in the service system domain conform to the domain processing logic of the service system, and the login session information of each third-party platform in the plurality of third-party platforms is recorded with data which needs to be verified when an account number logs in the corresponding third-party platform;

and determining a target program signed by the brand of the target service system, and displaying a signed program page of the target program, wherein the target program is commonly used in the plurality of third-party platforms.

2. The method of claim 1, wherein the obtaining data within the service system domain comprises:

3. The method of claim 1, wherein determining a target service system brand in the service system domain data comprises:

4. The method of claim 1, wherein determining a target service system brand in the service system domain data comprises:

5. The method of claim 4, wherein determining the target service system brand from the first query result comprises:

6. The method of claim 5, wherein obtaining the target service system brand according to the second query result comprises:

7. The method according to claim 5, wherein the step of querying employee permissions corresponding to the account to be logged in the data in the service system domain and determining the target service system brand according to the employee permissions comprises:

8. The method of claim 1, wherein determining a target service system brand in the service system domain data comprises:

9. The method of claim 8, wherein determining the target service system brand from the third query result comprises:

10. The method of claim 9, wherein said determining the target service system brand according to the management information comprises:

11. A program page presentation apparatus, comprising:

the system comprises a first acquisition module, a second acquisition module and a third party platform, wherein the first acquisition module is used for acquiring data in a service system domain, the data in the service system domain is obtained by carrying out information conversion on login session information of a plurality of third party platforms accessed to the service system, data fields in the data in the service system domain accord with the domain processing logic of the service system, and the login session information of each third party platform in the plurality of third party platforms is recorded with data which needs to be verified when an account number logs in the corresponding third party platform;

and the display module is used for determining a target program signed by the target service system brand, and displaying the signed program page of the target program, wherein the target program is universal in the third-party platforms.