CN113542429B

CN113542429B - Platform residence processing method, device, equipment and medium

Info

Publication number: CN113542429B
Application number: CN202110866845.9A
Authority: CN
Inventors: 朱文飞
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2021-07-29
Filing date: 2021-07-29
Publication date: 2023-09-01
Anticipated expiration: 2041-07-29
Also published as: CN113542429A

Abstract

The disclosure provides a platform residence processing method, relates to the technical field of Internet, and particularly relates to a cloud platform or cloud service. The implementation scheme is as follows: acquiring a first source channel of an account number which applies for residence to a target platform, wherein the first source channel has corresponding service characteristics; according to a first source channel, configuring a residence management background, the residence management background configured to: based on the corresponding service characteristics, the account number residence service is disassembled into a plurality of minimum sub-capability services, and based on the plurality of minimum sub-capability services, an information interaction page is provided for the account number, wherein the plurality of minimum sub-capability services can be multiplexed when being configured into a residence management background according to a second source channel different from the first source channel; verifying information input to the information interaction page based on at least part of the minimum sub-capability services in the plurality of minimum sub-capability services; and opening the account number to the target platform in response to the information passing the verification.

Description

Platform residence processing method, device, equipment and medium

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a cloud platform or a cloud service, and in particular, to a method, an apparatus, an electronic device, a computer readable storage medium, and a computer program product for platform residence processing.

Background

The internet technology is an information technology developed and established on the basis of computer technology. The internet technology connects different devices with each other through a computer network, accelerates the transmission speed of information, widens the acquisition channel of information, and promotes the development of various different software applications, network platforms and the like.

With the development of internet technology, more and more users enter in-line platforms. Because the account numbers applied for residence may originate from various channels, require different products, or require different businesses. Therefore, systematic processing and management and control of the resident services of various accounts are the needs to be solved.

The approaches described in this section are not necessarily approaches that have been previously conceived or pursued. Unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section. Similarly, the problems mentioned in this section should not be considered as having been recognized in any prior art unless otherwise indicated.

Disclosure of Invention

The present disclosure provides a method, apparatus, electronic device, computer readable storage medium and computer program product for platform hosting processing.

According to an aspect of the present disclosure, there is provided a platform residence processing method, including: acquiring a first source channel of an account number which applies for residence to a target platform, wherein the first source channel has corresponding service characteristics; according to a first source channel, configuring a residence management background, the residence management background configured to: based on the corresponding service characteristics, the account number residence service is disassembled into a plurality of minimum sub-capability services, and based on the plurality of minimum sub-capability services, an information interaction page is provided for the account number, wherein the plurality of minimum sub-capability services can be multiplexed when being configured into a residence management background according to a second source channel different from the first source channel; verifying information input to the information interaction page based on at least part of the minimum sub-capability services in the plurality of minimum sub-capability services; and responding to the information passing the verification, and opening the account number to a target platform.

According to another aspect of the present disclosure, there is provided a platform entry management apparatus, including: the acquisition module is configured to acquire a first source channel of an account number which is applied to a target platform for residence, wherein the first source channel has corresponding service characteristics; a configuration module configured to configure a residence management background according to the first source channel, the residence management background configured to: based on the corresponding service characteristics, the account number residence service is disassembled into a plurality of minimum sub-capability services, and based on the plurality of minimum sub-capability services, an information interaction page is provided for the account number, wherein the plurality of minimum sub-capability services can be multiplexed when being configured into a residence management background according to a second source channel different from the first source channel; the verification module is configured to verify the information input to the information interaction page based on at least part of the minimum sub-capability services in the plurality of minimum sub-capability services; and the opening module is configured to open the account number to the target platform in response to the information passing the verification.

According to another aspect of the present disclosure, there is provided an electronic device including: at least one processor and a memory communicatively coupled to the processor; the memory stores commands executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform the steps of the method described above.

According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the steps of the above-described method.

According to another aspect of the present disclosure, a computer program product is provided, including a computer program. The computer program realizes the steps of the above method when executed by a processor.

According to one or more embodiments of the present disclosure, platform residence processing methods may be utilized to uniformly manage residence traffic for accounts from different channels.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

The accompanying drawings illustrate exemplary embodiments and, together with the description, serve to explain exemplary implementations of the embodiments. The illustrated embodiments are for exemplary purposes only and do not limit the scope of the claims. Throughout the drawings, identical reference numerals designate similar, but not necessarily identical, elements.

FIG. 1 illustrates a schematic diagram of an exemplary system in which various methods described herein may be implemented, in accordance with an embodiment of the present disclosure;

FIG. 2 illustrates a flow chart of a platform residence processing method according to an embodiment of the present disclosure;

3A-3C illustrate schematic diagrams of an inbound service of account numbers of different source channels according to embodiments of the present disclosure;

FIG. 4 illustrates a flowchart of example operations of configuring a residence management background in the method of FIG. 2, according to embodiments of the present disclosure;

FIG. 5 illustrates a schematic diagram of example operations of a configuration admission management background in the method of FIG. 4, in accordance with embodiments of the present disclosure;

FIG. 6 illustrates a schematic diagram of example operations for verifying information in the method of FIG. 2, in accordance with an embodiment of the present disclosure;

FIG. 7 illustrates a block diagram of a platform resident processing device according to an embodiment of the present disclosure;

fig. 8 illustrates a block diagram of an exemplary electronic device that can be used to implement embodiments of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one 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 of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

In the present disclosure, the use of the terms "first," "second," and the like to describe various elements is not intended to limit the positional relationship, timing relationship, or importance relationship of the elements, unless otherwise indicated, and such terms are merely used to distinguish one element from another. In some examples, a first element and a second element may refer to the same instance of the element, and in some cases, they may also refer to different instances based on the description of the context.

The terminology used in the description of the various illustrated examples in this disclosure is for the purpose of describing particular examples only and is not intended to be limiting. Unless the context clearly indicates otherwise, the elements may be one or more if the number of the elements is not specifically limited. Furthermore, the term "and/or" as used in this disclosure encompasses any and all possible combinations of the listed items.

In the related technology, due to the complexity of account numbers/user identity characteristics of the resident platforms, account numbers introduced by different platforms are different in qualification materials, rules of the same materials are different, and interaction flows of product inlets are different. For example, the self-media account number has multiple sets of identities on the platform, which may be resident with the content and service provider from the media, applet, etc. Also, for example, the types of residence from media department numbers include individual and institution, star introduction, official media account introduction, filling base material introduced by applet developers, etc., qualification materials, rules and procedures of residence, and audit standards are highly diverse.

In the related art, when a new account channel is introduced, the history scheme replicates the existing product code for customized modification. For example, a doctor opens an account number in an invitation code mode and needs to open a number to access the demand, and the customized support enters an opening page in the invitation code mode. Medical material filling and auditing services are also required for doctor accounts, as opposed to code packages provided for residence to common personal account numbers. Because the existing product codes can be duplicated during customization and transformation, when a plurality of channels are accessed, a plurality of code packages and a plurality of auditing pages exist. In the face of multiple types of channel account numbers, the portal guide needs to be compatible with multiple pages. And when the basic rule is modified, a plurality of code packages need to be changed, and the iteration cost is high.

In addition, in the related art, the workload is repeated when a new channel is introduced, and the customized rule iterates with the channel. For each channel's policy rules, the product level is not readable. Aiming at different channels, the related technology can copy a multi-sleeved standing-flow system and a multi-sleeved standing-check background, so that the code coupling degree is high, for example, the iteration of the same logic needs to be repeated at a plurality of positions. The front end codes of the material filling entries are chaotic, and the access modes and rules have no readability. When each product is not compatible with the entry rules, different channel accounts are not communicated with each other, so that the user side may need to fill in materials repeatedly. In addition, when intervention rules are carried out on multiple types of channels, the modification is needed more, and careless mistakes are easy to occur.

Therefore, how to build a set of account introduction systems with different qualification requirements, users with different product forms can be quickly accessed, and unified management and control is a need to be solved.

According to the embodiment of the disclosure, the account number residence service is disassembled and multiplexed by introducing the platform residence processing method, so that unified management and control of the account number residence service from different channels is realized.

Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

Fig. 1 illustrates a schematic diagram of an exemplary system 100 in which various methods and apparatus described herein may be implemented, in accordance with an embodiment of the present disclosure. Referring to fig. 1, the system 100 includes one or more client devices 101, 102, 103, 104, 105, and 106, a server 120, and one or more communication networks 110 coupling the one or more client devices to the server 120. Client devices 101, 102, 103, 104, 105, and 106 may be configured to execute one or more applications.

In an embodiment of the present disclosure, the server 120 may run one or more services or software applications that enable execution of the platform hosting method.

In some embodiments, server 120 may also provide other services or software applications that may include non-virtual environments and virtual environments. In some embodiments, these services may be provided as web-based services or cloud services, for example, provided to users of client devices 101, 102, 103, 104, 105, and/or 106 under a software as a service (SaaS) model.

In the configuration shown in fig. 1, server 120 may include one or more components that implement the functions performed by server 120. These components may include software components, hardware components, or a combination thereof that are executable by one or more processors. A user operating client devices 101, 102, 103, 104, 105, and/or 106 may in turn utilize one or more client applications to interact with server 120 to utilize the services provided by these components. It should be appreciated that a variety of different system configurations are possible, which may differ from system 100. Accordingly, FIG. 1 is one example of a system for implementing the various methods described herein and is not intended to be limiting.

The user may apply for platform hosting using client devices 101, 102, 103, 104, 105, and/or 106. The client device may provide an interface that enables a user of the client device to interact with the client device. The client device may also output information to the user via the interface. Although fig. 1 depicts only six client devices, those skilled in the art will appreciate that the present disclosure may support any number of client devices.

Client devices 101, 102, 103, 104, 105, and/or 106 may include various types of computer devices, such as portable handheld devices, general purpose computers (such as personal computers and laptop computers), workstation computers, wearable devices, gaming systems, thin clients, various messaging devices, sensors or other sensing devices, and the like. These computer devices may run various types and versions of software applications and operating systems, such as Microsoft Windows, apple iOS, UNIX-like operating systems, linux, or Linux-like operating systems (e.g., google Chrome OS); or include various mobile operating systems such as Microsoft Windows Mobile OS, iOS, windows Phone, android. Portable handheld devices may include cellular telephones, smart phones, tablet computers, personal Digital Assistants (PDAs), and the like. Wearable devices may include head mounted displays and other devices. The gaming system may include various handheld gaming devices, internet-enabled gaming devices, and the like. The client device is capable of executing a variety of different applications, such as various Internet-related applications, communication applications (e.g., email applications), short Message Service (SMS) applications, and may use a variety of communication protocols.

Network 110 may be any type of network known to those skilled in the art that may support data communications using any of a number of available protocols, including but not limited to TCP/IP, SNA, IPX, etc. For example only, the one or more networks 110 may be a Local Area Network (LAN), an ethernet-based network, a token ring, a Wide Area Network (WAN), the internet, a virtual network, a Virtual Private Network (VPN), an intranet, an extranet, a Public Switched Telephone Network (PSTN), an infrared network, a wireless network (e.g., bluetooth, WIFI), and/or any combination of these and/or other networks.

The server 120 may include one or more general purpose computers, special purpose server computers (e.g., PC (personal computer) servers, UNIX servers, mid-end servers), blade servers, mainframe computers, server clusters, or any other suitable arrangement and/or combination. The server 120 may include one or more virtual machines running a virtual operating system, or other computing architecture that involves virtualization (e.g., one or more flexible pools of logical storage devices that may be virtualized to maintain virtual storage devices of the server). In various embodiments, server 120 may run one or more services or software applications that provide the functionality described below.

The computing units in server 120 may run one or more operating systems including any of the operating systems described above as well as any commercially available server operating systems. Server 120 may also run any of a variety of additional server applications and/or middle tier applications, including HTTP servers, FTP servers, CGI servers, JAVA servers, database servers, etc.

In some implementations, server 120 may include one or more applications to analyze and consolidate data feeds and/or event updates received from users of client devices 101, 102, 103, 104, 105, and 106. Server 120 may also include one or more applications to display data feeds and/or real-time events via one or more display devices of client devices 101, 102, 103, 104, 105, and 106.

In some implementations, the server 120 may be a server of a distributed system or a server that incorporates a blockchain. The server 120 may also be a cloud server, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology. The cloud server is a host product in a cloud computing service system, so as to solve the defects of large management difficulty and weak service expansibility in the traditional physical host and virtual private server (VPS, virtual Private Server) service.

The system 100 may also include one or more databases 130. In some embodiments, these databases may be used to store data and other information. For example, one or more of databases 130 may be used to store information such as audio files and video files. The data store 130 may reside in a variety of locations. For example, the data store used by the server 120 may be local to the server 120, or may be remote from the server 120 and may communicate with the server 120 via a network-based or dedicated connection. The data store 130 may be of different types. In some embodiments, the data store used by server 120 may be a database, such as a relational database. One or more of these databases may store, update, and retrieve the databases and data from the databases in response to the commands.

In some embodiments, one or more of databases 130 may also be used by applications to store application data. The databases used by the application may be different types of databases, such as key value stores, object stores, or conventional stores supported by the file system.

The system 100 of fig. 1 may be configured and operated in various ways to enable application of the various methods and apparatus described in accordance with the present disclosure.

Fig. 2 illustrates a flow chart of a platform hosting method 200 according to an embodiment of the present disclosure. As shown in fig. 2, the platform docking processing method 200 includes steps 210 through 240.

In step 210, a first source channel of an account number for residence applied to a target platform is obtained, where the first source channel has corresponding service features. In one example, the first source channel may be, for example, from a media department number, medical class public number, and the like. In one example, the business feature corresponding to the self-media hundred-family number is a media-class business, and the business feature corresponding to the medical-class public number is a doctor-class business, a hospital-class business, a medical-class business, or the like.

In step 220, according to the first source channel, a residence management background is configured to: based on the corresponding service characteristics, the account number residence service is disassembled into a plurality of minimum sub-capability services, and based on the plurality of minimum sub-capability services, an information interaction page is provided for the account number, wherein the plurality of minimum sub-capability services can be multiplexed when configured into a residence management background according to a second source channel different from the first source channel. In one example, the inbound traffic hosting the account may be broken down into multiple minimum sub-capability traffic based on traffic characteristics of different source channels. For example, the minimum sub-capability service may be auditing the compliance of the user name, ID assignment, or auditing partition, etc. Meanwhile, the minimum sub-capability service has reusability. For example, when an account from the media applies for residence, the minimum sub-capability service may include checking a user name, ID assignment, human-machine auditing, and the like. When a residence is applied from an account other than self-media, such as a medical type account, the minimum sub-capability service may be repeatedly invoked in the residence service of the type account.

At step 230, information entered into the information interaction page is verified based on at least some of the plurality of minimum sub-capability services. In one example, the minimum sub-capability services may include a sub-capability service that provides an information interaction page and a minimum sub-capability service that verifies information filled in by a user through the information interaction page. In one example, the check-class traffic may be divided into multiple phases of checks, such as attribute checks, account submission checks, and account audit checks, and each phase of check may be broken down into a minimum sub-capability traffic with reusability.

In step 240, in response to the information passing the verification, the account number is opened to the target platform. In one example, when the information filled in by the user passes all the verification, an account number is opened to the target platform, so that the user can stay on the target platform.

In some exemplary embodiments, at least one minimum sub-capability service of the plurality of minimum sub-capability services may be adjusted through the presence management background to achieve unified regulation of different service features.

In summary, the method 200 may disassemble the resident service into a plurality of services with minimum sub-capabilities according to the service types corresponding to the account numbers from different channels. Since the minimum sub-capability service has reusability, the same minimum sub-capability service can be invoked in combination for the resident services of account numbers from other channels. In addition, when intervention is carried out on a certain minimum sub-capability service, all resident services comprising the minimum sub-capability service can be effective, so that unified regulation and control of account resident from each channel is realized.

Fig. 3A-3C illustrate schematic diagrams of an inbound service of account numbers of different source channels according to embodiments of the present disclosure. As shown in fig. 3A, 300A represents a resident service derived from an account number in, for example, the medical field. The inbound service 300A includes information fill-in 370, verification 380, audit 360, and open account number 390.

The information fill 370 includes the minimum sub-capability services 310 through 350. For example, the minimum sub-capability service 310 may represent a number ID assignment, 320 may represent a nickname/user name, 330 may represent an avatar, 340 may represent a signature, and 350 may represent a medical qualification.

Check 380 includes minimum sub-capability services 322 through 328 and may check nickname/user name 320. The minimum sub-capability service 322 may be an enterprise end number bank uniqueness check, 324 may be a consumer end number bank uniqueness check, 326 may be an anti-cheating check, and 328 may be a medical protection word check. Here, the term "guard word" is a specific word, such as a sensitive word, which is excluded from being used as an account number.

Fig. 3B shows a resident service 300B originating from an account number of a channel other than the medical field. Like reference numerals in fig. 3B denote like elements as in fig. 3A, and a detailed description thereof will be omitted. As shown in fig. 3B, the scheduling and configuration of each minimum sub-capability also changes because the account number source is different from the medical domain in fig. 3A. In one example, the minimum sub-capabilities 310-340 may be multiplexed into the inbound traffic 300B. However, since 300B does not involve medical services, the information fill-in 370 'need not include medical qualification 350 and the verification 380' need not include medical protection word verification 328.

Fig. 3C shows a inbound service 300C originating from a channel different from fig. 3A and 3B. In one example, the account in 300C may have been opened by the account on other platforms, so the account may be opened only by multiplexing the ID assignment 310 without repeated invocation of various information fills and checks.

In some exemplary embodiments, at least a portion of the minimum sub-capability services include at least one of the group consisting of: the minimum sub-capability service can be customized based on the service characteristics of the account; minimum sub-capability services that can be executed in parallel; and a minimum sub-capability service that can be retried for execution. In one example, depending on the execution time and core level of different minimum sub-capability services, the corresponding minimum sub-capability services may be scheduled for parallel execution or retried execution. For example, when the minimum sub-capability service of verifying an identity card is the core service, the service may be retried until the identity card verification passes. In one example, the minimum sub-capability service for user name verification may include a vocabulary query and a uniqueness check, so that individual vocabularies may be queried in parallel to achieve user name verification. In some exemplary embodiments, the partial minimum sub-capability service may also have a customized capability. For example, if an account from the self-media requires additional verification at the time of account verification, the minimum sub-capability service may be customized for the self-media class account.

In summary, according to different account services, different execution orders of the minimum sub-capability services and customized minimum sub-capability services can be adopted, so that stability and flexibility of account residence processing of different sources are improved.

Fig. 4 illustrates a flowchart of example operations of configuring a residence management background in the method of fig. 2, according to embodiments of the present disclosure. As shown in fig. 4, the configuration residence management background (step 220) further includes steps 410 to 440.

At step 410, portal guidance is configured, including providing a plurality of jump links. In some example embodiments, configuring the portal guidance may further include providing a portal document. In one example, the portal document may prompt the user for the current account open status, the stage that has been completed, the fill-in stage that needs to be jumped, and so forth. In one example, a jump link is a jump that can be made from a current information interaction page to other information interaction pages. In one example, the user may jump to the next phase through the jump link through various human-machine interaction means, such as click-to-jump.

At step 420, a plurality of attribute verification phases are configured, each attribute verification phase including a first subset of a plurality of minimum sub-capability services, the first subset including the minimum sub-capability services for verifying account number entered information in real-time, each attribute verification phase corresponding to one of the plurality of jump links and providing a corresponding information interaction page to the account number. In one example, the attribute verification stage may provide an information interaction page for the user to fill in the material, and verify the filled-in information in real time as the user fills in the corresponding material. For example, when the user needs to provide the identity card information, the attribute verification stage can verify in real time whether the identity card information filled by the user meets the specification, for example, meets the word length specification. In one example, the first subset may also include customization capabilities.

At step 430, an account submission stage is configured, the account submission stage including a second subset of the plurality of minimum sub-capability services, the second subset including minimum sub-capability services for performing a submission-type verification of information entered by the account. In some exemplary embodiments, the second subset further comprises at least one of the group consisting of: minimum sub-capability service capable of carrying out ID allocation on the account; minimum sub-capability service capable of transmitting and checking information input by the account; and the minimum sub-capability service which can be uniformly stored according to the source channel corresponding to the account. In one example, the second subset may also include customization capabilities.

After the user has filled out the information, the user may submit the filled-in information by performing a man-machine interaction operation such as click-to-jump. In one example, the account submission phase can further process information submitted by the user, such as data processing, ID assignment, unified storage, and submission class verification. In one example, the account submission stage is also capable of submitting submitted information for review based on the requirements of the account. For example, when a platform is docked from another sub-account subordinate to the media account or a user of the account, the sub-account or information submitted by the user of the media account may be issued to the self-media account for review during the account submission phase.

In step 440, an account auditing phase is configured, the account auditing phase including a third subset of the plurality of minimum sub-capability services, the third subset including minimum sub-capability services for audit-like verification of information entered by the account. In some exemplary embodiments, the third subset further comprises at least one of the group consisting of: the minimum sub-capability service of the information input by the account can be checked by a machine; and a minimum sub-capability service that can be used to manually review information entered by the account. In one example, the third subset may also include customization capabilities.

In one example, the account auditing phase can perform machine audits on submitted information, such as linking to an information repository external to the platform to further audit the submitted information of the account. Furthermore, the account auditing stage can also audit and partition the information and allocate corresponding auditing authorities for manually auditing the submitted information of the account.

In some exemplary embodiments, at least a portion of the minimum sub-capability traffic includes a first subset, a second subset, and a third subset.

Fig. 5 illustrates a schematic diagram of example operations 500 of configuring a residence management background in the method of fig. 4, according to embodiments of the present disclosure. As shown in fig. 5, an example operation 500 of the configuration residence management background includes a configuration portal guide 510, a plurality of attribute verification phases 520, an account submission phase 530, and an account auditing phase 540.

The plurality of attribute verification phases 520 includes a first subset: minimum sub-capability traffic 521 through 528. The minimum sub-capability services 521 through 529 may be user names, avatars, personal introductions, invitation codes, identification cards, institution codes, business licenses, account types, and customization capabilities, respectively. Multiple attribute verification phases 520 may be provided to the user corresponding information interaction pages according to the minimum sub-capability services 521-529. In one example, each attribute verification stage may display one or more information interaction pages corresponding to the smallest sub-capability service.

The account submission stage 530 includes a second subset: minimum sub-capability traffic 531 to 536. The minimum sub-capability services 531 to 536 may be data processing, commit class checking, message issuing, ID allocation, unified storage and customisation capabilities, respectively.

The account auditing stage 540 includes a third subset: minimum sub-capability services 541 through 544. The minimum sub-capability services 541 through 544 may be an audit rules engine, audit partition, audit rights, and customization capability, respectively.

In summary, embodiments of the present disclosure may configure the presence management background as distinct phases, each phase including a portion of a respective minimum sub-capability service. By hierarchically configuring the stages, the logicality and readability of the resident management background can be enhanced. Meanwhile, customization capability is configured at each stage, so that the flexibility of configuration of the portal management background can be improved.

In some exemplary embodiments, the plurality of attribute verification phases includes an execution order, and verifying information input to the information interaction page includes: in response to a real-time verification confirmation of information input to the information interaction page corresponding to the current attribute verification stage, jumping to an attribute verification stage immediately following the current attribute verification stage in the execution order or an attribute verification stage parallel to the current attribute verification stage in the execution order. In one example, for multiple attribute verification phases, the order of execution of a portion of the attribute verification phases may be configured in parallel, e.g., the attribute verification phases provided to the user input identification card material may be parallel in order of execution with the attribute verification phases provided to the user input mechanism operational material. That is, the user can select any one of the stages to fill in the material. In other exemplary embodiments, one portion of the attribute verification phase needs to be performed sequentially earlier than another portion of the attribute verification phase. For example, the filling of the user's base material (user name, etc.) needs to be performed earlier in order than the filling of other materials. That is, the user needs to complete filling of the base material before proceeding to the next stage. Therefore, the embodiment of the disclosure can adjust the execution sequence of different attribute verification stages according to different source channels, thereby improving the flexibility of the residence management background for the management of the residence business of different channel accounts.

In some exemplary embodiments, verifying the information input to the information interaction page further comprises: performing commit class verification in response to the real-time verification validation of the plurality of attribute verification phases; and performing an audit class check in response to the validation of the commit class check.

In some example embodiments, configuring the portal boot further comprises providing a portal document, and configuring the residence management background further comprises: and adjusting the entry text and the jump link of the entry guide in response to verifying the information input to the information interaction page. In one example, based on the completion of the information filling and the passing of each verification stage, an entry-directed entry document may be provided to indicate the user's next action and adjust the jump links accordingly. Therefore, only the minimum sub-capability service or the scheduling sequence of each stage needs to be configured for account number residence services where different channels reside. And the entrance guide can be correspondingly adjusted according to the completion state of each stage, so that the method brings convenience guidance and similar page interaction experience to users without channels. The execution order of the various stages configured in the method of fig. 4 and the adjusted entry guide are schematically shown in table 1.

TABLE 1

As can be seen from table 1, the information interaction pages to be provided may be different according to account sources, so that the required attribute verification stages may be different, and the execution order of the attribute verification stages may be different. Furthermore, the portal guidance can adjust the portal document and the jump link according to the completion condition of each stage, so that the user can conveniently fill in information.

Fig. 6 illustrates a schematic diagram of an example operation 600 for verifying information in the method of fig. 2, according to an embodiment of the disclosure. As shown in fig. 6, when checking information input by a user, the inbound traffic may be classified into a serial traffic 610, a parallel traffic 620, an asynchronous traffic 630, and a retry traffic 640 according to time consumption and core degree of each minimum sub-capability traffic. For example, when a certain minimum sub-capability service belongs to a core service, such as medical qualification belongs to the core service for an account number derived from a medical service, the core service may be added to the retry service 640 after the execution of the core service fails to ensure the completion rate. Parallel service 620 may include tasks 622, 624, 626, etc. that can be performed in parallel. In one example, the verification service of the user name needs to check the vocabulary and determine the uniqueness, wherein checking the vocabulary may be performed in parallel to check multiple vocabularies, such as a star protection list, a city class vocabulary, a yellow counter vocabulary, an industry domain vocabulary, and the like. The memory 650 may be uniformly stored for accounts of different sources. In addition, if execution of the core tasks 632, 634, 636 and the like in the retry service 640 still fails, it is determined to be abnormal and log 660 is imported. Service Level Agreements (SLAs) for monitoring traffic may also be added to improve stability of the inbound traffic.

Fig. 7 shows a block diagram of a platform entry handling device 700 according to an embodiment of the disclosure. As shown in fig. 7, platform resident processing device 700 includes an acquisition module 710, a configuration module 720, a verification module 730, and an provisioning module 740.

The acquisition module 710 is configured to acquire a first source channel of an account number that applies for residence to a target platform, the first source channel having corresponding business characteristics.

A configuration module 720 configured to configure a residence management background according to the first source channel, the residence management background configured to: based on the corresponding service characteristics, the account number residence service is disassembled into a plurality of minimum sub-capability services, and based on the plurality of minimum sub-capability services, an information interaction page is provided for the account number, wherein the plurality of minimum sub-capability services can be multiplexed when the residence management background is configured according to a second source channel different from the first source channel.

And a verification module 730 configured to verify information input to the information interaction page based on at least a part of the minimum sub-capability services of the plurality of minimum sub-capability services.

And the opening module 740 is configured to open the account number to the target platform in response to the information passing the verification.

In some exemplary embodiments, the configuration module 720 includes a first configuration sub-module 721, a second configuration sub-module 722, a third configuration sub-module 723, and a fourth configuration sub-module 724.

A first configuration sub-module 721 configured to perform configuration entry guidance, including providing a plurality of jump links;

a second configuration sub-module 722 configured to configure a plurality of attribute verification phases, each attribute verification phase including a first subset of the plurality of minimum sub-capability services, the first subset including minimum sub-capability services for verifying information entered by the account in real time, wherein each attribute verification phase corresponds to one of the plurality of jump links and provides a corresponding information interaction page to the account;

a third configuration sub-module 723 configured to configure an account submission stage, the account submission stage including a second subset of the plurality of minimum sub-capability services, the second subset including minimum sub-capability services for submission-type verification of information entered by the account; and

a fourth configuration sub-module 724 configured to configure an account auditing phase, the account auditing phase including a third subset of the plurality of minimum sub-capability services, the third subset including minimum sub-capability services for auditing-like verification of information entered by the account.

In some exemplary embodiments, the plurality of attribute verification phases includes an execution order, and the verification module 730 includes: a skip rotor module 731 configured to skip to one of the group consisting of: an attribute verification stage immediately following the current attribute verification stage in execution order; and an attribute verification phase that is concurrent in execution order with the current attribute verification phase.

In some exemplary embodiments, the verification module 730 further includes a first execution sub-module 732 and a second execution sub-module 733.

A first execution sub-module 732 configured to execute a commit class check in response to the real-time check validation of the plurality of attribute check phases; and

the second execution sub-module 733 is configured to execute an audit class check in response to a validation of the commit class check.

In some exemplary embodiments, the first configuration sub-module 721 further includes a providing sub-module configured to provide an entry document, and the configuration module 720 further includes: an adjustment sub-module 725 configured to adjust the portal context and the jump link of the portal guidance in response to verifying the information input to the information interaction page.

In some exemplary embodiments, the platform residence processing device 700 further includes an adjustment module 750 configured to adjust at least one of the plurality of minimum sub-capability services to achieve unified regulation of different service features through the residence management background.

Fig. 8 illustrates a block diagram of an exemplary electronic device 800 that can be used to implement embodiments of the present disclosure. Referring to fig. 8, a block diagram of an electronic device 800 that may be a server or a client of the present disclosure, which is an example of a hardware device that may be applied to aspects of the present disclosure, will now be described. Electronic devices are intended to represent various forms of digital electronic computer devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 8, the apparatus 800 includes a computing unit 801 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 802 or a computer program loaded from a storage unit 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the device 800 can also be stored. The computing unit 801, the ROM 802, and the RAM 803 are connected to each other via a bus 1204. An input/output (I/O) interface 805 is also connected to the bus 804.

Various components in device 800 are connected to I/O interface 805, including: an input unit 806, an output unit 807, a storage unit 808, and a communication unit 809. The input unit 1206 may be any type of device capable of inputting information to the device 800, the input unit 806 may receive input numeric or character information, and generate key signal inputs related to user settings and/or function control of the electronic device, and may include, but is not limited to, a mouse, a keyboard, a touch screen, a trackpad, a trackball, a joystick, a microphone, and/or a remote control. The output unit 807 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers. The storage unit 808 may include, but is not limited to, magnetic disks, optical disks. The communication unit 809 allows the device 800 to exchange information/data with other devices over computer networks, such as the internet, and/or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and/or chipsets, such as bluetooth (TM) devices, 1302.11 devices, wiFi devices, wiMax devices, cellular communication devices, and/or the like.

The computing unit 801 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 801 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as method 200. For example, in some embodiments, the method 200 may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as the storage unit 808. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 800 via ROM 802 and/or communication unit 809. When a computer program is loaded into RAM 803 and executed by computing unit 801, one or more steps of method 200 described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the method 200 by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on 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.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.

The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel, sequentially or in a different order, provided that the desired results of the disclosed aspects are achieved, and are not limited herein.

Although embodiments or examples of the present disclosure have been described with reference to the accompanying drawings, it is to be understood that the foregoing methods, systems, and apparatus are merely exemplary embodiments or examples, and that the scope of the present invention is not limited by these embodiments or examples but only by the claims following the grant and their equivalents. Various elements of the embodiments or examples may be omitted or replaced with equivalent elements thereof. Furthermore, the steps may be performed in a different order than described in the present disclosure. Further, various elements of the embodiments or examples may be combined in various ways. It is important that as technology evolves, many of the elements described herein may be replaced by equivalent elements that appear after the disclosure.

Claims

1. A platform hosting method, comprising:

acquiring a first source channel of an account number which applies for residence to a target platform, wherein the first source channel has corresponding service characteristics;

configuring a residence management background according to the first source channel, wherein the residence management background is configured to: based on the corresponding service characteristics, disassembling an account number residence service into a plurality of minimum sub-capability services, and providing an information interaction page for the account number based on the plurality of minimum sub-capability services, wherein the plurality of minimum sub-capability services can be multiplexed when configuring the residence management background according to a second source channel different from the first source channel;

Verifying information input to the information interaction page based on at least part of the minimum sub-capability services in the plurality of minimum sub-capability services; and

and responding to the information passing the verification, and opening the account number to the target platform.

2. The method of claim 1, wherein the configuration enqueue management background comprises:

configuring an entry guide including providing a plurality of jump links;

configuring a plurality of attribute verification stages, wherein each attribute verification stage comprises a first subset of the plurality of minimum sub-capability services, the first subset comprises the minimum sub-capability services for verifying information input by the account in real time, each attribute verification stage corresponds to one of the plurality of jump links and provides a corresponding information interaction page for the account;

configuring an account number submitting stage, wherein the account number submitting stage comprises a second subset of the plurality of minimum sub-capability services, and the second subset comprises minimum sub-capability services for performing submitting class verification on information input by the account number; and

an account auditing stage is configured, wherein the account auditing stage comprises a third subset of the plurality of minimum sub-capability services, and the third subset comprises the minimum sub-capability services for auditing-type verification of information input by the account.

3. The method of claim 2, wherein the at least a portion of minimum sub-capability traffic comprises the first subset, the second subset, and the third subset.

4. A method as claimed in claim 3, wherein the plurality of attribute verification phases comprises an execution order, and wherein the verifying information entered into the information interaction page comprises:

in response to a real-time verification validation of information entered into the information interaction page corresponding to the current attribute verification stage, jumping to one of the group consisting of:

an attribute verification stage following the current attribute verification stage in the execution order; and

and an attribute verification stage parallel to the current attribute verification stage in the execution order.

5. The method of claim 4, wherein the verifying the information entered into the information interaction page further comprises:

performing the commit class check in response to real-time check validation of the plurality of attribute check phases; and

and executing the audit class verification in response to the confirmation of the commit class verification.

6. The method of claim 4 or 5, wherein the configuration portal bootstrap further comprises providing a portal document, and wherein the configuration residence management background further comprises: and adjusting the entry text and jump link of the entry guide in response to the verification of the information input to the information interaction page.

7. The method of claim 1, further comprising: and adjusting at least one minimum sub-capability service in the plurality of minimum sub-capability services through the residence management background so as to realize unified regulation and control of account residence services with different service characteristics.

8. The method of claim 1, wherein the at least a portion of minimum sub-capability traffic comprises at least one of the group consisting of:

the minimum sub-capability service can be customized based on the service characteristics of the account;

minimum sub-capability services that can be executed in parallel; and

the minimum sub-capability service performed can be retried.

9. The method of claim 2, wherein the second subset further comprises at least one of the group consisting of:

minimum sub-capability service capable of carrying out ID allocation on the account;

minimum sub-capability service capable of transmitting and checking information input by the account; and

and the minimum sub-capability service which is uniformly stored according to the source channel corresponding to the account number can be performed.

10. The method of claim 2, wherein the third subset further comprises at least one of the group consisting of:

The minimum sub-capability service of the information input by the account can be checked by a machine; and

and the minimum sub-capability service can be used for manually checking the information input by the account.

11. A platform residence management device, comprising:

the acquisition module is configured to acquire a first source channel of an account number which is applied to a target platform for residence, wherein the first source channel has corresponding service characteristics;

a configuration module configured to configure a residence management background according to the first source channel, wherein the residence management background is configured to: based on the corresponding service characteristics, disassembling an account number residence service into a plurality of minimum sub-capability services, and providing an information interaction page for the account number based on the plurality of minimum sub-capability services, wherein the plurality of minimum sub-capability services can be multiplexed when configuring the residence management background according to a second source channel different from the first source channel;

the verification module is configured to verify the information input to the information interaction page based on at least part of the minimum sub-capability services in the plurality of minimum sub-capability services; and

and the opening module is configured to open the account number to the target platform in response to the information passing the verification.

12. The apparatus of claim 11, wherein the configuration module comprises:

a first configuration sub-module configured to perform configuration entry guidance, including providing a plurality of jump links;

a second configuration sub-module configured to configure a plurality of attribute verification phases, each attribute verification phase including a first subset of the plurality of minimum sub-capability services, the first subset including minimum sub-capability services for verifying information input by the account in real time, wherein each attribute verification phase corresponds to one of the plurality of jump links and provides a corresponding information interaction page to the account;

a third configuration sub-module configured to configure an account submission stage, the account submission stage including a second subset of the plurality of minimum sub-capability services, the second subset including minimum sub-capability services for performing a submission-type verification of information entered by the account; and

and a fourth configuration sub-module configured to configure an account auditing stage, wherein the account auditing stage comprises a third subset of the plurality of minimum sub-capability services, and the third subset comprises minimum sub-capability services for auditing-type verification of information input by the account.

13. The apparatus of claim 12, wherein the at least a portion of minimum sub-capability traffic comprises the first subset, the second subset, and the third subset.

14. The apparatus of claim 13, wherein the plurality of attribute verification phases comprises an execution order, and wherein the verification module comprises:

a skip rotor module configured to skip to one of the group consisting of:

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

a first execution sub-module configured to execute the commit class check in response to real-time check validation of the plurality of attribute check phases; and

and a second execution sub-module configured to execute the audit class check in response to a validation of the commit class check.

16. The apparatus of claim 14 or 15, wherein the first configuration submodule further comprises a provision submodule configured to provide an entry document, and wherein the configuration module further comprises: and the adjustment sub-module is configured to adjust the entry text and the jump link of the entry guide in response to the verification of the information input to the information interaction page.

17. The apparatus of claim 11, further comprising: and the adjusting module is configured to adjust at least one minimum sub-capability service in the plurality of minimum sub-capability services through the residence management background so as to realize unified regulation and control of different service characteristics.

18. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the method comprises the steps of

The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-10.

19. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-10.