Access access method, device and equipment of external platform, storage medium and program product

Abstract

This application provides a method, apparatus, device, storage medium, and program product for accessing an external platform. The method includes: receiving an access request sent by an external platform; parsing the access request to obtain account data of the accessing account on the external platform; if the account data includes account information and authentication information, performing a first authentication on the accessing account based on the authentication information; wherein the authentication information is generated by the external platform's access interface after authenticating the account information during the accessing account's first access; and responding to the result of the first authentication being successful by calling the function interface corresponding to the target function requested by the access request to respond to the access request. This application can improve the access efficiency of external platform access requests.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a method, apparatus, device, storage medium, and program product for accessing external platforms. Background Technology

[0002] Many popular platform products provide developers with methods to integrate with their platforms. This allows developers to easily access their products to a large user base of these popular platforms without needing to download additional applications. The conventional approach to integration involves customizing a dedicated integration logic code library based on the official documentation of each platform. Different functional modules in the business load and execute these specific code libraries according to their needs for platform user information. Thus, a new code library needs to be built for each new platform integration. Due to the unique characteristics of different platforms, even implementing the same functionality or logic requires separate coding for each platform's specific requirements. This necessitates rewriting the corresponding functional code for each platform, making integration difficult and inefficient. Summary of the Invention

[0003] This application provides an external platform access method, apparatus, device, storage medium, and program product, which can improve the access efficiency of external platform access requests.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides a method for accessing an external platform. The method includes: receiving an access request sent by an external platform; parsing the access request to obtain account data of an access account on the external platform; if the account data includes account information and authentication information, performing a first authentication on the access account based on the authentication information; wherein the authentication information is generated by the external platform's access interface after authenticating the account information when the access account first accesses the platform; and responding to the first authentication result being successful by calling the function interface corresponding to the target function requested by the access request to respond to the access request.

[0006] This application provides an access device for an external platform, comprising: a receiving module for receiving an access request sent by an external platform; a parsing module for parsing the access request to obtain account data of the access account on the external platform; a first authentication module for performing a first authentication on the access account based on the authentication information when the account data includes account information and authentication information; wherein the authentication information is generated by the external platform access interface after authenticating the account information when the access account accesses the platform for the first time; and a response module for responding to the first authentication result being successful by calling the function interface corresponding to the target function requested by the access request to respond to the access request.

[0007] In the above scheme, the first authentication module is further configured to: when the account data includes account information and authentication information, call the external platform access interface to perform a second authentication on the account information; in response to the result of the second authentication being successful, perform the first authentication on the access account based on the authentication information.

[0008] In the above scheme, the device further includes a first mapping module, which is used to: when the account data includes account information, call the external platform access interface to perform a second authentication on the account information; in response to the second authentication result being successful, determine whether the access request is the first access of the accessing account based on the account identifier in the account information; in response to the access request being the first access of the accessing account, assign a platform account identifier to the accessing account; establish a first mapping relationship between the platform account identifier and the account identifier, and store the first mapping relationship.

[0009] In the above scheme, the device further includes a second mapping module, which is used to: generate authentication information corresponding to the platform account identifier; send the authentication information to the access account of the external platform; establish a second mapping relationship between the authentication information, the platform account identifier and the account identifier, and store the second mapping relationship.

[0010] In the above scheme, the first mapping module is further configured to: query the database for a platform account identifier that has the first mapping relationship with the account identifier in the account information; in response to not finding a platform account identifier with the first mapping relationship with the account identifier in the database, determine that the access request is the first access of the accessing account; in response to finding a platform account identifier with the first mapping relationship with the account identifier in the database, determine that the access request is not the first access of the accessing account.

[0011] In the above scheme, the first authentication module is further configured to: obtain authentication information from the database that has the second mapping relationship with the account identifier; and perform first authentication on the access account based on the authentication information in the account data and the authentication information obtained from the database.

[0012] In the above scheme, the receiving module is further configured to: display the sharing information on the client of the external platform; generate the access request in response to the external platform receiving a trigger operation for the sharing information, and receive the access request sent by the external platform.

[0013] In the above scheme, the configuration module is further configured to: create a platform access program on the client of the external platform; and configure at least one functional component of the current application in the platform access program.

[0014] In the above scheme, the receiving module is further configured to: generate the access request in response to the external platform receiving a trigger operation for any functional component, and receive the access request sent by the external platform.

[0015] In the above scheme, the response module is further configured to: in response to the first authentication result being authentication passed, determine the interface identifier of the functional interface corresponding to the target function requested by the access request; in response to querying the service network address corresponding to the interface identifier from a preset routing information file, initiate an interface call request to the server corresponding to the service network address; the interface call request carries the account data; receive the request response result returned by the server corresponding to the service network address after responding to the interface call request; and send the request response result to the access account of the external platform.

[0016] In the above scheme, the device further includes a generation module, which is used to: generate an error response result in response to the failure to find a service network address corresponding to the interface identifier in a preset routing information file; and send the error response result to the access account of the external platform.

[0017] This application provides an electronic device, including: a memory for storing computer-executable instructions; and a processor for executing the computer-executable instructions stored in the memory to implement the external platform access method provided in this application.

[0018] This application provides a computer-readable storage medium storing computer-executable instructions for implementing the external platform access method provided in this application when executed by a processor.

[0019] This application provides a computer program product, which includes computer-executable instructions stored in a computer-readable storage medium. When the processor of an electronic device reads and executes the computer-executable instructions from the computer-readable storage medium, it implements the external platform access method provided in this application.

[0020] The embodiments of this application have the following beneficial effects:

[0021] When accessing an external platform, the process begins by parsing the access request sent by the external platform to obtain the account data of the accessing account. This account data includes account information and authentication information. The authentication information is generated by the external platform's access interface after authenticating the account information upon the account's first access. In other words, the external platform's access interface authenticates the account information upon the first access. After successful authentication, this authentication information is generated and returned to the external platform. This ensures that the external platform includes this authentication information in its access requests, guaranteeing the authenticity and legitimacy of the accessing account. Then, given the account data includes both account information and authentication information, the accessing account undergoes initial authentication based on the authentication information. Finally, if the initial authentication is successful, the function interface corresponding to the target function requested in the access request is invoked to respond to the access request. Thus, when the first authentication passes, the access account on the external platform gains permission to access the target function requested in the access request, and can respond to the access request from the external platform through the function's interface. This greatly simplifies the access process to the external platform and improves the efficiency of access requests. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the architecture of the external platform access system provided in the embodiments of this application;

[0023] Figure 2 This is a schematic diagram of the structure of the external platform access device provided in the embodiments of this application;

[0024] Figure 3 This is an optional flowchart illustrating the external platform access method provided in this application embodiment;

[0025] Figure 4 This is another optional flowchart illustrating the external platform access method provided in the embodiments of this application;

[0026] Figure 5This is a schematic diagram of the execution flow provided in an embodiment of this application when account data includes account information;

[0027] Figure 6 This is a schematic diagram of the implementation process for determining whether it is the first access, provided in an embodiment of this application;

[0028] Figure 7 This is a schematic diagram of the execution flow after assigning a platform account identifier to an access account, provided in an embodiment of this application.

[0029] Figure 8 This is a schematic diagram of the process for implementing the first authentication provided in an embodiment of this application;

[0030] Figure 9 This is a schematic diagram of an HTML5 page for a specific platform accessed according to an embodiment of this application;

[0031] Figure 10 This is a functional example diagram of a test robot on an external platform A provided in this application embodiment;

[0032] Figure 11 This is another functional example diagram of a test robot on an external platform A provided in this application embodiment;

[0033] Figure 12 This is a schematic diagram of the overall process for accessing multiple external platforms provided in an embodiment of this application. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0035] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments, but it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0036] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0037] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0038] Unless otherwise defined, all technical and scientific terms used in the embodiments of this application have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in the embodiments of this application is for the purpose of describing the embodiments of this application only and is not intended to limit this application.

[0039] In the implementation of this application, the collection and processing of relevant data should strictly comply with the requirements of relevant laws and regulations, obtain the informed consent or separate consent of the personal information subject, and carry out subsequent data use and processing within the scope of laws and regulations and the authorization of the personal information subject.

[0040] In related technologies, the conventional approach to integration is to customize and develop dedicated integration logic code libraries based on the official documentation of each integration platform. Different functional modules in the business load and execute these specific code libraries according to their needs for platform user information. Thus, a new code library needs to be built for each new platform integration. Due to the unique characteristics of different platforms, even implementing the same function or logic requires separate coding for each platform's specific requirements, resulting in the need to rewrite the corresponding functional code for each platform. For example, a game live streaming platform has a wealth of functions, including hundreds of individual functional modules such as live streaming, bullet comments, lotteries, interaction, subscriptions, and mini-games. When this game live streaming platform integrates with a specific platform, all these hundreds of functional modules need to be modified simultaneously. This is equivalent to each functional module integrating with that specific platform, and subsequent additions of functional modules also need to consider the logic of the integrated platform. If multiple platforms need to be integrated, the workload of modification increases exponentially. Furthermore, each functional module only reuses the logic code library of the integrated platform; if the platform integration logic changes and needs updating, the services of all these hundreds of functional modules need to be updated simultaneously, which will greatly affect the user experience. For example, updates to mini-game services can impact the online user experience.

[0041] To address at least one of the problems in the aforementioned related technologies, this application proposes a method for accessing multiple external platforms. This method applies the mapping between user identifiers on different external platforms and user login identifiers on a specific platform, as well as the verification between user status information on different external platforms and user login status on a specific platform. This method significantly reduces the platform access cost: when a user accesses a specific platform page from any external platform, all requests are processed through the specific platform's backend gateway. Through the method proposed in this application, these external platform users are converted and initialized as independent users of the specific platform, including setting user nicknames, avatars, genders, and birthdays. Thus, various functional modules on the specific platform will treat this user as a standard specific platform user, enabling all specific platform functions to be seamlessly used on different access platforms without additional custom development.

[0042] The following describes exemplary applications of the external platform access device (i.e., electronic device) provided in the embodiments of this application. The external platform access device provided in the embodiments of this application can be implemented as various types of user terminals capable of accessing external platforms, such as laptops, tablets, desktop computers, set-top boxes, mobile devices (e.g., mobile phones, portable music players, personal digital assistants, dedicated messaging devices, portable gaming devices), smartphones, smart speakers, smartwatches, smart TVs, and in-vehicle terminals. It can also be implemented as a server. The following describes exemplary applications when the external platform access device is implemented as a server.

[0043] See Figure 1 , Figure 1 This is a schematic diagram of the architecture of the external platform access system 100 provided in this application embodiment. In order to support the access application of an external platform, the client 400 of the external platform connects to the server 200 through the network 300. The network 300 can be a wide area network or a local area network, or a combination of the two.

[0044] The client 400 of the external platform sends an access request to the server 200. The server 200 constitutes the access device for the external platform in this embodiment of the application. The server 200 responds to the access request from the external platform by receiving the access request sent by the external platform; parsing the access request to obtain the account data of the access account in the external platform; if the account data includes account information and authentication information, performing a first authentication on the access account based on the authentication information; wherein, the authentication information is generated by the external platform access interface after authenticating the account information when the access account first accesses; in response to the result of the first authentication being successful, calling the function interface corresponding to the target function requested by the access request to respond to the access request and obtain the request response result. The request response result is then returned to the client 400 of the external platform so that the client 400 of the external platform can output the request response result.

[0045] In some embodiments, server 200 may be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. Client 400 of the external platform may be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, in-vehicle terminal, etc., but is not limited to these. Clients and servers of the external platform can be connected directly or indirectly via wired or wireless communication, which is not limited in this embodiment.

[0046] See Figure 2 , Figure 2 This is a schematic diagram of the structure of the electronic device 40 provided in the embodiment of this application. Figure 2 The illustrated electronic device 40 can be an access device for an external platform, which includes at least one processor 410, a memory 450, at least one network interface 420, and a user interface 430. The various components in the external platform access device are coupled together via a bus system 440. It is understood that the bus system 440 is used to implement communication between these components. In addition to a data bus, the bus system 440 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 2 The general labeled all buses as Bus System 440.

[0047] The processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0048] User interface 430 includes one or more output devices 431 that enable the presentation of media content, including one or more speakers and one or more visual displays. User interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0049] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 450 may optionally include one or more storage devices physically located away from the processor 410.

[0050] The memory 450 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 450 described in this application embodiment is intended to include any suitable type of memory.

[0051] In some embodiments, memory 450 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0052] Operating system 451 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;

[0053] The network communication module 452 is used to reach other electronic devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including Bluetooth, WiFi, and Universal Serial Bus (USB); the presentation module 453 is used to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431 associated with the user interface 430 (e.g., a display screen, a speaker, etc.); the input processing module 454 is used to detect and translate one or more user inputs or interactions from one or more input devices 432.

[0054] In some embodiments, the apparatus provided in this application can be implemented in software. Figure 2 An access device 455 for an external platform, stored in memory 450, is shown. This device can be software in the form of programs and plug-ins, and includes the following software modules: a receiving module 4551, a parsing module 4552, a first authentication module 4553, and a response module 4554. These modules are logically connected and can therefore be arbitrarily combined or further separated according to their implemented functions. The functions of each module will be described below.

[0055] In some other embodiments, the apparatus provided in this application can be implemented in hardware. As an example, the apparatus provided in this application can be a processor in the form of a hardware decoding processor, which is programmed to execute the access method of the external platform provided in this application. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0056] In some embodiments, the client or server of an external platform can implement the external platform access method provided in this application by running various computer-executable instructions or computer programs. For example, computer-executable instructions can be microprogram-level commands, machine instructions, or software instructions. Computer programs can be native programs or software modules in an operating system; they can be native applications (APPs), i.e., programs that need to be installed in the operating system to run, or they can be applets that can be embedded in any APP, i.e., programs that only need to be downloaded to a browser environment to run. In summary, the aforementioned computer-executable instructions can be any form of instruction, and the aforementioned computer programs can be any form of application, module, or plugin.

[0057] The external platform access methods provided in the embodiments of this application can be executed by an electronic device, which can be a server or a client of the external platform. That is, the external platform access methods in the embodiments of this application can be executed by a server, by a client of the external platform, or by interaction between the server and the client of the external platform.

[0058] See Figure 3 , Figure 3 This is an optional flowchart illustrating an external platform access method provided in an embodiment of this application, which will be combined with... Figure 3 The steps shown will be explained, taking the execution subject of the external platform access method as the server as an example. The method includes the following steps S101 to S104:

[0059] Step S101: Receive an access request sent by an external platform.

[0060] In this embodiment, an external platform refers to a third-party platform belonging to a different region and independent of the specific platform (i.e., the current application). The external platform may provide different services or content but desires to integrate or interoperate with the specific platform in some way. In internet applications, an external platform can be any system capable of initiating an access request, such as another website, mobile application, or server-side program. An access request is a request initiated by the external platform to the server. This access request can be used to obtain data, trigger operations, or perform certain functions on the specific platform. This access request is typically made via HTTP or HTTPS protocols and includes information required to execute the request, such as user authentication data, the type of operation requested, or any necessary parameters. For example, suppose a user wants to watch a live stream on another live streaming platform (i.e., the specific platform) through a shared content link on a social media platform (i.e., the external platform). When the user clicks the shared content link on the social media platform, the social media platform sends an access request to the server, requesting access to the live streaming platform to watch its live stream content.

[0061] In some embodiments, a specific platform may provide a server-side Application Programming Interface (API) to an external platform. This API is specifically designed to receive access requests from the external platform. This API also needs to be pre-configured. The server on the specific platform can detect this API and wait for access requests from external platforms. When an external platform sends an access request, the server on the specific platform can detect that it has received the access request through the API, and can then perform subsequent request processing operations based on the access request.

[0062] In some embodiments, the server can also simultaneously receive multiple access requests from multiple external platforms, each requesting different content. For example, the multiple external platforms could be external platform A, external platform B, and external platform C. External platform A might send an access request to register as a user on a specific platform, external platform B might send an access request to watch live stream content on a specific platform, and external platform C might send an access request to retrieve data from a specific platform. When the server receives multiple access requests from multiple external platforms simultaneously, it can perform subsequent request processing operations on each request separately.

[0063] Step S102: Parse the access request to obtain the account data of the accessing account in the external platform.

[0064] In this embodiment, an access account refers to an account owned by a user on an external platform. Account data refers to all data information related to the access account on the external platform, which can be used to verify the user's identity and permissions. Account data may include account information and authentication information of the access account on the external platform. Account information refers to identification information used to identify the user, such as a user ID, username, or email address. Authentication information refers to additional information used to verify the user's identity and permissions, such as the user's platform-specific user identification (UID), access token, OpenID, session ID, or signature. This authentication information is typically used to ensure that the access request is initiated by a legitimate user and that the user has the authority to perform the operation requested by the access request.

[0065] When a user sends an access request to the server through a client on an external platform, the account data of the accessing account on the external platform can be encapsulated in the access request. When the server receives the access request, it parses the request and extracts the account data of the accessing account from the external platform.

[0066] Step S103: If the account data includes account information and authentication information, perform first authentication on the accessing account based on the authentication information.

[0067] In this embodiment, the authentication information is generated by the external platform access interface after authenticating the account information upon the first access by the account. That is, when an account accesses a specific platform for the first time, it first needs to authenticate the account information through the external platform access interface. After successful authentication, the authentication information is generated. The external platform access interface is the aforementioned API interface, which allows the server of a specific platform to verify the account information of the accessing account on the external platform. The authentication process for account information refers to verifying whether the accessing account on the external platform is a genuine and legitimate user account. That is, the external platform access interface checks and verifies the received account information to ensure that the user corresponding to the account information is a genuine and legitimate user on the external platform.

[0068] When an account accesses an external platform for the first time, the external platform's access interface authenticates the account information and generates authentication information, which is then returned to the external platform's access account. This authentication information is then included in the access request for subsequent accesses, and the access account undergoes initial authentication based on this information. Initial authentication refers to the process of verifying whether the access account on the external platform has the permission to access the target function on the specific platform (i.e., the target function requested in the access request). For example, this can be achieved by verifying whether the access account is logged in from multiple locations or on multiple devices, whether the device and IP address used to log in to the access account are abnormal, whether the client on the external platform corresponding to the access account is a legitimate client, whether secondary verification such as CAPTCHA is required, whether the login cookie information is a valid credential issued by the specific platform's server when the access account logs in, and whether the credential is still valid. These verifications effectively implement the initial authentication of the access account.

[0069] Step S104: In response to the first authentication result being successful, the function interface corresponding to the target function requested by the access request is invoked to respond to the access request.

[0070] In this embodiment, the target function refers to the specific operation or service that a user wishes to perform through an access request. This target function is part of various services provided by a specific platform, such as playing a video from the specific platform on an external platform, viewing product details on the specific platform, or initiating a payment service on the specific platform. The function interface is the programming interface corresponding to the target function provided by the specific platform. This function interface allows the target function in the specific platform to be called through a client of the external platform. This function interface may exist in the form of an API interface, defining how to send requests, pass parameters, and respond to access requests sent by the external platform.

[0071] When the first authentication pass is detected, the access account on the external platform has permission to access the target function requested in the access request. It can respond to the access request sent by the external platform through the corresponding function's interface. After the response is completed, the result is returned to the access account on the external platform. Conversely, when the first authentication fails, the access account on the external platform does not have permission to access the target function requested in the access request and cannot respond to the access request sent by the external platform through the corresponding function's interface. In this case, the server will reject the access request from the external platform, generate an error message, and return the error message to the access account on the external platform.

[0072] The external platform access method provided in this application first obtains the account data of the accessing account on the external platform by parsing the access request sent by the external platform. The account data includes account information and authentication information. The authentication information is generated by the external platform's access interface after authenticating the account information during the first access by the accessing account. That is, the external platform's access interface authenticates the account information of the accessing account during the first access on the external platform. After successful authentication, the authentication information is generated and returned to the external platform, so that the external platform carries the authentication information in the access request to ensure the authenticity and legitimacy of the accessing account on the external platform. Then, when the account data includes account information and authentication information, the accessing account is directly authenticated based on the authentication information. Finally, if the first authentication result is successful, the function interface corresponding to the target function requested by the access request is called to respond to the access request. Thus, when the first authentication passes, the access account on the external platform gains permission to access the target function requested in the access request, and can respond to the access request from the external platform through the function's interface. This greatly simplifies the access process to the external platform and improves the efficiency of access requests.

[0073] The following will describe the external platform access method in this application embodiment, focusing on the interaction between the client and server of the external platform in the external platform access system. It should be noted that the external platform access method here is implemented through interaction between the external platform client and the server, and is essentially the same as the external platform access method executed by the server in the above embodiments. The only difference is that this application embodiment also describes the actions performed by the external platform client during the execution of the external platform access method. Furthermore, some steps can be executed by either the external platform client or the server. Therefore, for steps in this embodiment that are the same as those in the above embodiments but have different execution subjects, this embodiment is merely illustrative. In the implementation process, any execution subject can perform these steps, and this application embodiment does not limit this.

[0074] Figure 4 This is another optional flowchart illustrating the external platform access method provided in the embodiments of this application, such as... Figure 4 As shown, the method includes the following steps S201 to S212:

[0075] In step S201, the client of the external platform receives the access operation input by the user.

[0076] In this embodiment of the application, an external platform access application can run on the client side of the external platform. Users can input access operations on the client side of the external platform access application. The external platform access application can provide external platform access functions. Users can input access operations on the external platform access function page to trigger access requests.

[0077] In some embodiments, when a user inputs an access operation, they can also simultaneously input account data for the access account on the external platform. When the client of the external platform receives this account data, a confirmation window for external platform access will pop up on the external platform's access access function page. After the client of the external platform detects that the user has clicked the confirmation button for external platform access, it will further process the account data to achieve access to the external platform. Alternatively, in other embodiments, the user can directly input the account data on the external platform's access access function page. Upon receiving the account data, the client of the external platform can directly trigger the external platform's access access function to further process the account data and achieve access to the external platform.

[0078] In step S202, the client of the external platform generates an access request in response to the access operation.

[0079] In this embodiment, user-inputted data can be encapsulated into an access request. For example, on the display interface of an external platform's access application, account data is displayed. Users can select or confirm data on this display interface according to their actual needs, and then the user-inputted account data can be encapsulated into an access request.

[0080] In step S203, the client on the external platform sends an access request to the server.

[0081] Step S204: The server receives an access request sent by an external platform.

[0082] In this embodiment of the application, the specific meaning and implementation of the step of receiving access requests sent by external platforms can be found in the description of step S101 above, and will not be repeated here.

[0083] In some embodiments, receiving an access request sent by an external platform can be achieved in the following ways: Method 1, the sharing information can be displayed on the client of the external platform; in response to the external platform receiving a trigger operation for the sharing information, an access request is generated, and the access request sent by the external platform is received.

[0084] An external platform client refers to the front-end interface or device used by a user to interact with the external platform. This client can be a webpage in a web browser, a mobile application, or a desktop application. Through the external platform client, users can browse content, perform operations, and access the specific platform. Shared information refers to information or links displayed by the external platform client that can be used to interact with the specific platform. A triggering action for shared information refers to an action performed by the user on the external platform client that triggers an access request sent to the specific platform to enable access from the external platform to the specific platform. This triggering action can be a click, touch, or swipe. For example, suppose the external platform is a social media website, and the specific platform is a live streaming platform. The shared information is a live stream link on the live streaming platform, and the user clicks the live stream link on the social media website. At this time, the external platform client detects the triggering action for the live stream link, calls an API to generate an access request, and sends the access request to the server of the specific platform to request to watch the live stream on the live streaming platform on the external platform.

[0085] This process enables data and functionality integration between external platforms and specific platforms, providing users with a seamless cross-platform experience.

[0086] Here, by displaying shared information on the client side of an external platform and responding to user-triggered actions, rapid access between the external platform and a specific platform is achieved, providing users with a more convenient and richer experience. At the same time, through access, multiple platforms can share user resources, increasing multiple channels for dissemination and user acquisition, and increasing user stickiness.

[0087] Alternatively, a platform access program can be created on the client side of an external platform. This program can then be configured with at least one functional component of the current application. Finally, in response to a trigger operation received by the external platform for any functional component, an access request can be generated, and the program can receive access requests sent by the external platform.

[0088] A platform access program is a software module or application designed to integrate into the client of an external platform. The purpose of creating a platform access program is to establish an interface between a specific platform (i.e., the current application) and the external platform, allowing the external platform to access the functions and services of the specific platform. This platform access program may include necessary API interfaces, authentication mechanisms, and data processing logic. A functional component refers to a specific function provided by a specific platform, which can be encapsulated as a module or service for external platforms to call. This functional component can be provided in the form of an API or Software Development Kit (SDK) and can be used by the client of the external platform to enhance its own functionality. Based on the number of functions that can be implemented in the current application, at least one functional component of the current application can be configured in the platform access program. For example, in a map service, a location search functional component is provided. By creating a platform access program on the client of the external platform and configuring this location search functional component in the platform access program, the location search function in the map service can be integrated into the external platform, allowing users to directly search and display location information on the external platform. A trigger operation for any functional component refers to an action performed by the user on the client of the external platform, which can be invoked by the platform access program to call the functional component of the specific platform. No specific limitations are set for this triggering operation.

[0089] Here, by creating a platform access program on the client side of an external platform and configuring specific platform functional components within it, user-triggered operations on the external platform client can be correctly identified and transformed into access requests for specific platform services. This not only improves the user experience but also expands the functional scope of the external platform.

[0090] In step S205, the server parses the access request and obtains the account data of the accessing account on the external platform.

[0091] In this embodiment of the application, after receiving an access request sent by an external platform, if the access request encapsulates account data of the accessing account on the external platform, the account data of the accessing account on the external platform can be directly parsed to obtain the account data of the accessing account on the external platform. For the specific meaning and implementation method of parsing the access request to obtain the account data of the accessing account on the external platform, please refer to the description of step S102 above, which will not be repeated here.

[0092] In step S206, if the account data includes account information and authentication information, the server calls the external platform access interface to perform a second authentication of the account information.

[0093] In this embodiment of the application, the second authentication refers to the process of verifying the security of the access account on the external platform and verifying the authenticity of the user identity corresponding to the access account.

[0094] In some embodiments, see Figure 5 , Figure 5 This demonstrates that when the server includes account information in the account data, the following steps S501 to S504 can be performed:

[0095] Step S501: If the account data includes account information, call the external platform access interface to perform a second authentication of the account information.

[0096] In this embodiment, the account data includes account information but not authentication information, which can be categorized into three scenarios. First, the server of the specific platform is receiving an access request from an external platform for the first time; that is, the account on the external platform is accessing the server for the first time, and the account information has not yet been authenticated by the external platform's access interface. Second, when the account on the external platform accesses the server for the first time, the authentication of the account information by the external platform's access interface fails, and no authentication information is generated. Third, the account on the external platform is not accessing the server for the first time; when the account on the external platform accesses the server for the first time, the external platform's access interface authenticates the account information and generates authentication information, but this authentication information is not included in the access request.

[0097] In the first scenario, upon the initial access of the account, the external platform's access interface is invoked to authenticate the account information (i.e., secondary authentication). Upon successful authentication, authentication information is generated. In both the second and third scenarios, the external platform's access interface can re-authenticate the account information (i.e., secondary authentication), and the result determines whether to generate authentication information.

[0098] In step S502, in response to the second authentication result being successful, the system determines whether the access request is the first access to the account based on the account identifier in the account information.

[0099] In this embodiment of the application, the result of the second authentication is divided into authentication successful and authentication unsuccessful. The account identifier is an identifier in the account information used to uniquely identify the account accessing the external platform. The account identifier can be a string or number generated by the external platform, that is, the account identifier in the account information belongs to the account identifier in the external platform.

[0100] In some embodiments, see Figure 6 , Figure 6The following steps illustrate how, in step S502, the server determines whether the access request is the first access by the accessing account based on the account identifier in the account information. This can be achieved through the following steps S5021 to S5023:

[0101] Step S5021: Query the database for platform account identifiers that have a first mapping relationship with the account identifiers in the account information.

[0102] In this embodiment, the platform account identifier is a unique identifier assigned by a specific platform to an access account on an external platform. This platform account identifier is typically generated when a user first accesses the specific platform through an external platform and is used to identify the user in subsequent accesses. This platform account identifier is controlled and managed by the specific platform and differs from the account identifier on the external platform. A certain mapping relationship (i.e., a first mapping relationship) exists between the account identifier in the account information and the platform account identifier; that is, the account on the specific platform corresponding to the platform account identifier and the access account on the external platform are the same user's accounts on two different platforms. Furthermore, when a user first accesses the specific platform through an external platform and a platform account identifier is generated, the first mapping relationship between the account identifier in the account information and the platform account identifier needs to be established and recorded in the database. The first mapping relationship ensures the consistency of identification for the same user across different platforms, allowing the user to create an account on the specific platform corresponding to the access account on the external platform.

[0103] When the second authentication result is successful, the system queries the database for the platform account identifier that has a first mapping relationship with the account identifier in the account information to determine whether the access request sent by the external platform is the first access for that account.

[0104] Step S5022: In response to the fact that no platform account identifier with a first mapping relationship with the account identifier is found in the database, it is determined that the access request is the first access to the account.

[0105] In this embodiment of the application, when no platform account identifier with a first mapping relationship with the account identifier is found in the database, it means that the access request sent by the external platform is the first access of the access account in the external platform, that is, the access account in the external platform is accessing the server of a specific platform for the first time, and the platform account identifier has not yet been generated, nor has the first mapping relationship between the account identifier and the platform account identifier been established.

[0106] Step S5023: In response to finding a platform account identifier with a first mapping relationship to the account identifier in the database, it is determined that the access request is not the first access to the account.

[0107] In this embodiment of the application, when a platform account identifier with a first mapping relationship with an account identifier is found in the database, it means that the access request sent by the external platform is not the first access of the access account in the external platform. That is, the access account in the external platform has accessed the server of the specific platform and has generated a platform account identifier and established a first mapping relationship between the account identifier and the platform account identifier during the previous first access.

[0108] Here, by querying the database to see if there is a platform account identifier that has a first mapping relationship with the account identifier in the account information, it is possible to quickly determine whether the access request sent by the external platform is the first access to the account, thereby improving the access speed of the external platform.

[0109] Step S503: In response to the access request being the first access by the access account, a platform account identifier is assigned to the access account.

[0110] In this embodiment, when it is determined that the access request sent by the external platform is the first access by the accessing account, a platform account identifier is assigned to the accessing account on the external platform through the server of the specific platform, so that the account identifier of the accessing account corresponds to the platform account identifier. Then, a platform account corresponding to the platform account identifier is created on the specific platform, and the account information of the accessing account on the external platform is synchronized to the platform account, so that the user's account information is the same on multiple different platforms, including the specific platform and the external platform.

[0111] In some embodiments, see Figure 7 , Figure 7 The steps S701 to S703 are shown to be performed after a platform account identifier is assigned to an access account:

[0112] Step S701: Generate authentication information corresponding to the platform account identifier.

[0113] In this embodiment, various authentication information corresponding to the platform account identifier can be generated based on different information. For example, when assigning a platform account identifier to an access account, after a user completes registration on a specific platform, the server can automatically generate a unique user identifier (UID) using an auto-incrementing field in the database or a Universally Unique Identifier (UUID). An access token can also be generated using an authentication protocol (e.g., OAuth 2.0) or a specific algorithm (e.g., JWT). This access token can be a randomly generated string containing a payload and a signature. Alternatively, a unique OpenID identifier can be generated for the user based on information such as their email address or username. A session can also be created, and a randomly generated unique session ID can be assigned to that session and stored in the user's cookie or passed as a URL parameter. Furthermore, the user's private key can be used to sign certain parts of the access request using various encryption algorithms (e.g., HMAC, RSA, or ECDSA). The specific limitations on the authentication information corresponding to the platform account identifier and the methods for generating such authentication information are not described here.

[0114] Step S702: Send the authentication information to the access account of the external platform.

[0115] In this embodiment of the application, after obtaining the authentication information corresponding to the platform account identifier, the authentication information is sent to the access account of the external platform so that when the access account sends an access request through the external platform, the authentication information is encapsulated in the access request, and then the access account is authenticated for the first time based on the authentication information.

[0116] Step S703: Establish a second mapping relationship between authentication information, platform account identifier and account identifier, and store the second mapping relationship.

[0117] In this embodiment of the application, the second mapping relationship refers to the mapping relationship between authentication information, platform account identifier and account identifier. Based on the second mapping relationship, the authentication information corresponding to the platform account identifier, the platform account identifier and the account identifier correspond to each other, and the other two items can be obtained by querying one of the items in the second mapping relationship.

[0118] In some embodiments, the method for establishing the second mapping relationship may be: creating a dedicated database table to store the second mapping relationship, the database table containing at least three fields: authentication information, platform account identifier, and account identifier.

[0119] Here, through the generation process of authentication information, the sending process of authentication information, and the establishment and storage process of the second mapping relationship, it is possible to quickly determine whether the user has a corresponding platform account on the specific platform based on the authentication information carried in the access request or the account identifier of the access account corresponding to the access request when the user sends an access request through an external platform to request a target function on a specific platform, so as to realize the rapid access of the access request sent by the external platform.

[0120] Step S504: Establish a first mapping relationship between platform account identifiers and account identifiers, and store the first mapping relationship.

[0121] In this embodiment of the application, the first mapping relationship refers to the mapping relationship between platform account identifiers and account identifiers. Based on the first mapping relationship, the authentication information corresponding to the platform account identifier, the platform account identifier and the account identifier correspond to each other, and the platform account identifier can be queried according to the account identifier in the first mapping relationship.

[0122] In some embodiments, the method for establishing the first mapping relationship may be: creating a dedicated database table to store the first mapping relationship, the database table containing at least two fields: platform account identifier and account identifier.

[0123] Here, when it's determined that the access request is the first time, the specific platform creates a mapping relationship to associate the external platform's account identifier with the specific platform's platform account identifier, and stores this mapping relationship in the database. In subsequent accesses, the specific platform's server can use this initial mapping relationship stored in the database to identify and authenticate the user, ensuring that the user can seamlessly use the specific platform's functions or services on the external platform, thus maintaining a consistent user experience across different platforms.

[0124] In step S207, the server responds to the second authentication result as authentication passed, and performs the first authentication on the access account based on the authentication information.

[0125] In this embodiment of the application, if the second authentication result is successful, it indicates that the user corresponding to the access account on the external platform is a real and legitimate user. When the second authentication result is detected as successful, the access account is subjected to first authentication based on the authentication information.

[0126] In some embodiments, see Figure 8 , Figure 8 The step S207, in which the server performs the first authentication of the access account based on the authentication information, can be achieved through the following steps S2071 to S2072:

[0127] Step S2071: Obtain authentication information from the database that has a second mapping relationship with the account identifier.

[0128] In this embodiment, when a user sends an access request through an external platform, the account information of the accessing account on the external platform is obtained by parsing the access request. This account information includes the account identifier of the accessing account, and a second mapping relationship exists between the account identifier, authentication information, and the platform account identifier, and is stored in a database. If the account identifier is known, authentication information with the second mapping relationship to the account identifier is retrieved from the database.

[0129] Step S2072: Based on the authentication information in the account data and the authentication information obtained from the database, perform the first authentication on the access account.

[0130] In this embodiment, the authentication information in the account data is the same as the authentication information carried in the access request. The authentication information carried in the access request is compared with the authentication information obtained from the database. If the authentication information carried in the access request is the same as the authentication information obtained from the database, the accessing account is first authenticated according to the authentication method in step S103 above. Conversely, if the authentication information carried in the access request is different from the authentication information obtained from the database, the access request is rejected, and the accessing account does not need to undergo first authentication.

[0131] Here, by comparing the authentication information carried in the access request with the authentication information obtained from the database, it is possible to quickly determine whether to perform the first authentication on the access account, that is, to quickly determine whether to process the access request sent by the external platform.

[0132] Here, when the access request sent by the external platform carries account information and authentication information, the two authentication processes of second authentication and first authentication can be passed in sequence to quickly determine whether the user corresponding to the access account is a real and legitimate user on both the external platform and the specific platform. This allows for a rapid response to the access request on the specific platform after subsequent authentication is passed, thereby improving the access efficiency of the external platform to the specific platform.

[0133] In step S208, the server responds to the first authentication result as authentication passed and determines the interface identifier of the functional interface corresponding to the target function requested by the access request.

[0134] In step S209, the server responds by querying the service network address corresponding to the interface identifier from the preset routing information file and initiating an interface call request to the server corresponding to the service network address.

[0135] In this embodiment, the target function requested by the access request can be any function that can be implemented on a specific platform. The target function requested by the access request corresponds to a functional interface, and this functional interface corresponds to a unique interface identifier. The preset routing information file is a configuration file that defines the mapping relationship between the access request and the backend server (i.e., the server corresponding to the service network address). This configuration file typically contains the correspondence between the interface identifier and the service network address, enabling the server on a specific platform to determine which specific backend server to route the access request to. The service network address refers to the network location of the server corresponding to the service network address. The service network address can be an IP address or a domain name, and may also include a port number. This service network address is used to indicate that the access request should be forwarded to the backend server corresponding to the interface identifier, initiating an interface call request to that server.

[0136] Step S210: The server receives the request response result returned by the server in response to the interface call request corresponding to the service network address.

[0137] In this embodiment, the request-response result is the data returned by the server corresponding to the service network address after processing the access request. For example, suppose a user initiates a request on an external platform to access book details on a specific platform. After authentication, the server identifies that the target function requested by the access request is to obtain book details and determines the interface identifier corresponding to the target function as / books / {bookID}. The server queries the preset routing information file and finds that the service network address corresponding to the interface identifier / books / {bookID} is http: / / book-service:8080. The user's access request is forwarded to the server corresponding to the service network address http: / / book-service:8080. An interface call request is sent to this server to invoke the function interface requested by the access request. After responding to the interface call request, the server responds to the access request sent by the external platform through the function interface and returns the book details data from the specific platform.

[0138] In step S211, the server sends the request response result to the access account of the external platform.

[0139] Here, using a pre-defined routing information file, access requests can be dynamically routed to different service instances, improving the system's flexibility and scalability. By identifying the server corresponding to the service's network address, effective request processing can be achieved, ensuring the accuracy of the request response results.

[0140] In some embodiments, in response to the failure to find a service network address corresponding to the interface identifier in a preset routing information file, an error response result is generated and sent to the access account of an external platform.

[0141] In this embodiment, the error response result is the response returned by the server of a specific platform to the client of an external platform when it cannot successfully process an access request. This error response result can be an error code, an error message, and a possible error description, and can be used to indicate the reason for the request failure. When the service network address corresponding to the interface identifier is not found in the preset routing information file, the server of the specific platform generates an error response result for the access request and sends it to the access account of the external platform so that the error response result can be displayed on the client of the external platform.

[0142] Here, the generation and sending of error responses allows for quick notification to users that access requests cannot be processed, reducing user wait time and improving user experience. Detailed error information in the response helps users understand the reason for the failure and guides them on how to resolve the issue or retry. Furthermore, it avoids sending access requests to non-existent service network addresses, conserving network and server resources.

[0143] In step S212, the client of the external platform outputs the request response result.

[0144] In this embodiment, when accessing an external platform, the account data of the accessing account on the external platform is obtained by parsing the access request sent by the external platform. The account data includes account information and authentication information. The authentication information is generated by the external platform's access interface after authenticating the account information during the account's first access. In other words, the external platform's access interface authenticates the account information of the accessing account during its first access. After successful authentication, the authentication information is generated and returned to the external platform. This ensures that the external platform includes the authentication information in its access requests, guaranteeing the authenticity and legitimacy of the accessing account. Furthermore, the specific platform creates a mapping relationship to associate the external platform's account identifier with the specific platform's platform account identifier, and stores this mapping relationship in a database. In subsequent accesses, the specific platform's server can use the first mapping relationship stored in the database to identify and authenticate users, ensuring that users can seamlessly use the specific platform's functions or services on the external platform, resulting in a consistent user experience across different platforms. Then, assuming the account data includes account information and authentication information, the accessing account is directly authenticated based on the authentication information. Finally, if the first authentication passes, the function interface corresponding to the target function requested by the access request is invoked to respond to the access request. Thus, when the first authentication passes, the accessing account on the external platform has permission to access the target function requested by the access request and can respond to access requests from the external platform through the function interface of that target function. This greatly simplifies the access process to the external platform and improves the efficiency of external platform access.

[0145] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0146] This application provides a method for accessing multiple external platforms. This method centralizes the access logic of multiple external platforms at the backend gateway level for unified management and processing. It maps users from different external platforms to users of a specific platform, while authenticating user status information to ensure user legitimacy and security. User information (e.g., nickname, avatar, gender, and birthday) is stored and available for business function modules to access. The entire process is transparent to the business modules and requires no awareness, greatly simplifying the complexity and workload of access. Through the unified access logic of the backend gateway, existing business modules and future added function modules do not need to make any adjustments for different external platforms; they can continue to treat mapped users as ordinary platform users. This method not only saves a significant amount of development and maintenance work, but also allows for a smooth rollout of all business functions after a single platform access, requiring only an update at the gateway service level when the access logic needs to be updated. Standardizing the access process for all external platforms accelerates the access of each specific platform. Furthermore, each accessing platform only interfaces with the gateway service and does not expose the network addresses of other server-side functional services, improving server security.

[0147] With the development of HTML5 technology, most popular applications now support web pages that can run across various terminal platforms. The functions of a specific platform are not only supported on PC desktop browsers, but also on Android and iOS mobile applications and browsers. Furthermore, popular external platform products typically have hundreds of millions of users and support the integration of HTML5 pages from these external platforms. This allows specific platforms to seamlessly integrate their functions into these external platforms, greatly facilitating use for external users and significantly increasing the user reach of the specific platform. For example... Figure 9 As shown, Figure 9 This refers to the HTML5 page of a specific platform that can be integrated. For example, users of any external platform can open the HTML5 page of that specific platform within a group via a shared message, allowing them to watch live streams or play mini-games. Furthermore, during use, the payment page of the external platform can be directly accessed for top-ups. After paying using various payment methods, users can still obtain more live stream benefits and game items, enjoying the same experience as within the specific platform's own application. This eliminates the need to enter account passwords and create a user account for the specific platform before logging in. This integration method not only adds multiple channels for dissemination and user acquisition for the specific platform but also significantly improves user engagement.

[0148] Therefore, it is necessary to migrate all existing and new features of a specific platform to an external platform as quickly and smoothly as possible. Taking external platform A as an example, the conventional approach is to first create a bot on external platform A. Based on the developer documentation of external platform A, the addresses of various functional pages on the specific platform are configured and trigger callbacks to become part of this bot mini-program. This way, users who follow the bot from external platform A can trigger the opening of these functional page addresses through the bot's menu or dialog box, thus using the functions provided by these pages. However, after each functional page is opened from external platform A, it needs to process various information from external platform A according to the developer documentation. For example, it needs to authenticate user information on external platform A, and use the user identification (UID) and avatar of external platform A users to identify a user. This process usually requires writing an SDK library so that each functional page can manage its access to external platform A by integrating this SDK. This particular platform has hundreds of functional modules, each requiring this processing. Furthermore, each module needs detailed testing to ensure compatibility with external platform A, and any new functional modules must also consider compatibility with external platform A. Extending this process to accessing multiple other external platforms would significantly delay the deployment of the platform's business functions on those platforms. Moreover, the mixed user information across different platforms for this function is prone to errors and makes it difficult to locate and troubleshoot problems.

[0149] When using the method proposed in this application, when a user accesses the address of these functional pages and requests a backend interface, the user first accesses a unified external platform gateway. This gateway is responsible for authenticating user information from the corresponding platform and initializing and registering the user as a platform-specific user upon their first access. During this process, the gateway also synchronizes and stores the user's information. Next, the gateway returns a set of authentication information for the platform-specific user, including UID, openID, and token. Subsequent calls to the backend interface through this functional page only require carrying this platform-specific user authentication information to make the request, just like a normal interface call.

[0150] On external platform A, all third-party developers need to first register a robot with the official website of platform A. The registration process requires filling in basic robot information and developer details, and configuring the robot's response to commands or shortcuts through pre-configuration and callbacks. For example... Figure 10 and Figure 11The image shows a functional example of a test robot on external platform A. After registration, the robot can interact with users like a regular user. The robot can proactively send a message to users daily, guiding them to activate a specific function on the platform. Users can also actively enter a start command in the interaction box to activate a specific function. The robot can also use shortcuts in the interaction box area to open designated functions. Users can also join the robot in an interactive group and interact with it by entering commands using @BotName. Activating a function is equivalent to opening the HTML5 page for that function on the platform. Since this HTML5 page is accessed through external platform A, the corresponding JavaScript code can be configured according to the developer documentation of external platform A to enable the HTML5 page to carry and process interactive information from users on external platform A. This is the process of a developer on external platform A developing a robot mini-program.

[0151] It's important to note that regardless of whether it's external platform A or any other external platform, although the specific methods for opening a particular platform's feature page may differ, the overall process is similar. Users need to first register for the feature component, and then activate a specific component to ultimately open the feature page for that platform. This process simply requires following the configuration instructions in the developer documentation for each external platform.

[0152] like Figure 12 As shown, Figure 12This is a schematic diagram of the overall process for accessing multiple external platforms proposed in this application embodiment. Step S301: User triggers opening. The user triggers the opening of a specific platform's function page on an external platform. Step S302: Initial request to the backend gateway's external platform login and registration interface. Unlike traditional solutions where the function page directly calls various server-side function interfaces after opening, the function page sends a request to the backend gateway to access the specific platform's backend gateway's external platform login and registration interface (ExternPlatLoginWithCode). This request carries the external platform's user information. Step S303: Authentication of the external platform's user information to ensure the authenticity of the external platform's user. When the function page accesses this interface, the backend gateway first authenticates the external platform's user information carried in the request. Each external platform has its own specifications; some use OAuth authentication, while others use platform-custom encrypted authentication. The authentication logic can be completed by referring to the developer documentation of each external platform. Step S304: If the external platform user's UID does not exist on the specific platform, the external platform user is initialized. After successful authentication, it is checked whether the external platform user's UID has a corresponding user UID on the specific platform. If not, it means that the user from the external platform does not exist on the specific platform. Therefore, according to the user UID allocation rules of the specific platform, a specific platform UID is assigned to the user, and the bidirectional mapping relationship between the external platform user UID and the assigned specific platform UID is stored. Finally, the user information of the external platform user is synchronized and associated with the specific platform UID. After user initialization, the user from the external platform has a legitimate identity on the specific platform. Step S305: Generate authentication information for the specific platform user. Authentication information for the specific platform is generated for the user on that specific platform. Step S306: The backend gateway's external platform login and registration interface returns the authentication information for the specific platform. The backend gateway's external platform login and registration interface returns the authentication information for the specific platform to the function page and stores it. Step S307: Access the backend gateway's business function interface. When a functional page needs to access a specific business function interface of the backend gateway, it needs to directly access the backend gateway by carrying the authentication information of the specific platform returned by the external platform login and registration interface. Step S308: Authenticate the authentication information of the specific platform user to ensure the authenticity of the specific platform user. The backend gateway first performs authentication based on the authentication information, checking whether the UID exists, whether the token is correct, or whether the token has expired, etc. Step S309: Implement security protection for users, devices, and external platforms. By implementing security protection for users, devices, and external platforms, it determines whether the user is a banned user, whether they possess fingerprint information of a malicious device, or whether they are a malicious user of an external platform, etc.Step S310: Access the specified business function interface in the backend, obtain the interface information, and forward the interface response information to the function page upon successful acquisition. Accessing the corresponding business function interface in the backend through the backend gateway, obtaining the interface response information, and then returning it to the function page completes this access to a specific business function interface in the backend. Step S311: The business function interface returns the interface response information.

[0153] As you can see, the access process here standardizes the access interaction between specific platforms and external platforms. Using this access process framework, each external platform only needs to process the external platform login and registration interface once in the backend. After that, all business function interface accesses will be as convenient and efficient as accessing the backend interface within the specific platform itself.

[0154] The specific process of this method is described as follows: A user triggers the opening of a specific function page on an external platform. The function page first requests the backend's external platform login and registration interface, hoping to obtain the corresponding specific platform UID and authentication information. The request field needs to include the external platform type (ExternPlatType), the external platform user information, and the authentication information. This information is encoded in a JSON format according to the specifications of each external platform and then sent to the backend gateway. After receiving the external platform login and registration interface request, the backend gateway parses the request field according to the external platform specification corresponding to the external platform type and authenticates the external platform user's authentication information in the request field. After successful authentication, based on the mapping relationship between the external platform user's UID and the specific platform UID stored in the backend, it determines whether the user from the external platform exists on the specific platform. If not, the external platform user is initialized. First, a specific platform UID is assigned. The specific platform UID can be an unsigned 64-bit integer, and a corresponding rule can be established. The allocation is as follows: 100-100 billion is allocated to users of the specific platform itself; 10-200 billion is allocated to users of external platform A with their corresponding specific platform UIDs; and 20-300 billion is allocated to users of external platform B with their corresponding specific platform UIDs. This allows for simple identification of users on a specific external platform using their specific platform UIDs. A two-way mapping relationship is then established between external platform UIDs and specific platform UIDs. User information from the external platform is synchronized to the corresponding user information for the specific platform UID. If this exists, authentication information corresponding to the specific platform UID is generated, and the interface response information for the specified business function is sent back to the function page for storage. It's worth noting that this authentication information includes user information, IP information, device fingerprint, and custom encryption information from the external platform. After receiving the interface response information, the function page stores it locally. When making subsequent interface requests to the backend gateway, this information is appended to the request via cookies or headers. If the interface returns successfully, the function page obtains the corresponding response information; if it fails, a failure message is displayed directly.

[0155] When the backend gateway receives a request from a function page, it first authenticates the platform's authorization information. This primarily involves user identity verification, security, and risk control processing. Specifically, it verifies whether the user has logged in from multiple locations and devices, whether the user's login device and IP are abnormal, whether the client is legitimate, whether secondary verification such as CAPTCHA is required, and whether the login cookie information is a valid credential issued by the server during user login and whether the credential is still valid. If these identity verifications and security checks pass, the Remote Procedure Call Protocol (RPC) is considered a legitimate call. If they fail, the backend gateway directly returns an error to the function page for processing. For external platform authentication information, it also verifies the existence of the platform's UID mapping relationship and whether the platform user has been banned, among other security protection checks.

[0156] After successful authentication, the backend gateway queries its local routing information file based on the requested API name to find the corresponding internal service network address. If not found, it directly returns an error response to the functional page. If found, it initiates an API call to that internal service network address, including the functional page's request information. Upon receiving the response from the internal service, the gateway forwards it to the functional page. In this process, the backend gateway acts as a request proxy.

[0157] During the integration process, external platform login and registration API requests or regular page requests may encounter exceptions. If the server crashes or experiences other exceptions, it will promptly return exception information to the client, and the API request will be interrupted. If the server remains unresponsive for an extended period, the function page can set a timeout for this merged request. If no response data is received from the backend after the timeout expires, the page request fails, and the user can be prompted to retry.

[0158] When an error occurs between the backend gateway and the regular server interface, whether it is a real-time error or a timeout due to prolonged lack of response, the error message will always be forwarded directly to the page as response data, and the page can simply display the error message.

[0159] The method proposed in this application provides a standardized process for multiple external platforms to access a specific platform, greatly simplifying the access process. It avoids the complexity of handling user information on each external platform separately for each business function, with unified processing and authentication handled by the backend gateway. It enables transparent processing of all accessed platforms for both existing and new business functions, treating each platform as its own logic without any awareness of the accessing platform. It also unifies the access method for function pages: function pages uniformly access the login and registration interfaces of external platforms through the backend gateway, without exposing the network addresses of other server-side functional service programs, thus improving server security.

[0160] It is understood that in the embodiments of this application, if the content involves user information, such as account data and authentication information, and if it involves data related to user information or enterprise information, when the embodiments of this application are applied to specific products or technologies, it is necessary to obtain user permission or consent, or to obfuscate this information to eliminate the correspondence between this information and the user; and the collection and processing of related data should strictly comply with the requirements of relevant national laws and regulations when applied in practice, obtain the informed consent or separate consent of the personal information subject, and carry out subsequent data use and processing within the scope of laws and regulations and the authorization of the personal information subject.

[0161] The following description continues to illustrate the exemplary structure of the external platform access device 455 provided in the embodiments of this application as a software module. In some embodiments, such as... Figure 2 As shown, the software modules stored in the external platform access device 455 in the memory 450 may include: a receiving module 4551, used to receive an access request sent by the external platform; a parsing module 4552, used to parse the access request to obtain account data of the access account in the external platform; a first authentication module 4553, used to perform a first authentication on the access account based on the authentication information when the account data includes account information and authentication information; wherein, the authentication information is generated by the external platform access interface after authenticating the account information when the access account accesses for the first time; and a response module 4554, used to respond to the first authentication result being authentication passed by calling the function interface corresponding to the target function requested by the access request to respond to the access request.

[0162] In some embodiments, the first authentication module 4553 is further configured to: when the account data includes account information and authentication information, call the external platform access interface to perform a second authentication on the account information; and in response to the result of the second authentication being successful, perform the first authentication on the access account based on the authentication information.

[0163] In some embodiments, the device 455 further includes a first mapping module, which is configured to: when the account data includes account information, invoke the external platform access interface to perform a second authentication on the account information; in response to the second authentication result being successful, determine whether the access request is the first access of the accessing account based on the account identifier in the account information; in response to the access request being the first access of the accessing account, assign a platform account identifier to the accessing account; establish a first mapping relationship between the platform account identifier and the account identifier, and store the first mapping relationship.

[0164] In some embodiments, the device 455 further includes a second mapping module, which is configured to: generate authentication information corresponding to the platform account identifier; send the authentication information to the access account of the external platform; establish a second mapping relationship between the authentication information, the platform account identifier, and the account identifier, and store the second mapping relationship.

[0165] In some embodiments, the first mapping module is further configured to: query a database for a platform account identifier that has the first mapping relationship with the account identifier in the account information; determine that the access request is the first access of the accessing account if no platform account identifier with the first mapping relationship is found in the database; and determine that the access request is not the first access of the accessing account if a platform account identifier with the first mapping relationship is found in the database.

[0166] In some embodiments, the first authentication module 4553 is further configured to: obtain authentication information from the database that has the second mapping relationship with the account identifier; and perform first authentication on the access account based on the authentication information in the account data and the authentication information obtained from the database.

[0167] In some embodiments, the receiving module 4551 is further configured to: display sharing information on the client of the external platform; generate the access request in response to the external platform receiving a trigger operation for the sharing information; and receive the access request sent by the external platform.

[0168] In some embodiments, the apparatus 455 further includes a configuration module, which is configured to: create a platform access program on the client of the external platform; and configure functional components of at least one function of the current application in the platform access program.

[0169] In some embodiments, the receiving module 4551 is further configured to: generate the access request in response to the external platform receiving a trigger operation for any functional component, and receive the access request sent by the external platform.

[0170] In some embodiments, the response module 4554 is further configured to: in response to the first authentication result being authentication passed, determine the interface identifier of the functional interface corresponding to the target function requested by the access request; in response to querying the service network address corresponding to the interface identifier from a preset routing information file, initiate an interface call request to the server corresponding to the service network address; the interface call request carries the account data; receive the request response result returned by the server corresponding to the service network address after responding to the interface call request; and send the request response result to the access account of the external platform.

[0171] In some embodiments, the apparatus 455 further includes a generation module, which is configured to: generate an error response result in response to not finding a service network address corresponding to the interface identifier in a preset routing information file; and send the error response result to the access account of the external platform.

[0172] It should be noted that the description of the apparatus in this application embodiment is similar to the description of the method embodiment described above, and has similar beneficial effects as the method embodiment; therefore, it will not be repeated. For technical details not disclosed in this apparatus embodiment, please refer to the description of the method embodiment of this application for understanding.

[0173] This application provides a computer-readable storage medium storing computer-executable instructions. When these instructions are executed by a processor, they cause the processor to execute the external platform access method provided in this application. For example, ... Figure 3 The method for accessing external platforms is shown.

[0174] This application provides a computer program product including computer-executable instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer-executable instructions from the computer-readable storage medium and executes the computer-executable instructions, causing the electronic device to perform the external platform access method described above in this application.

[0175] In some embodiments, the computer-readable storage medium may be a memory such as RAM, ROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a variety of devices including one or any combination of the above-mentioned memories.

[0176] In some embodiments, computer-executable instructions may take the form of programs, software, software modules, scripts, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as stand-alone programs or as modules, components, subroutines, or other units suitable for use in a computing environment.

[0177] As an example, computer-executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple co-located files (e.g., files that store one or more modules, subroutines, or code sections).

[0178] As an example, computer-executable instructions can be deployed to execute on a single electronic device, or on multiple electronic devices located at one location, or on multiple electronic devices distributed across multiple locations and interconnected via a communication network.

[0179] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A method for accessing an external platform, characterized in that, The method includes: Receive access requests sent by external platforms; The access request is parsed to obtain the account data of the accessing account in the external platform; When the account data includes account information and authentication information, the accessing account is first authenticated based on the authentication information; wherein, the authentication information is generated by the external platform access interface after authenticating the account information when the accessing account first accesses the platform. In response to the first authentication result being successful, the function interface corresponding to the target function requested by the access request is invoked to respond to the access request.

2. The method according to claim 1, characterized in that, When the account data includes account information and authentication information, the first authentication of the accessing account based on the authentication information includes: If the account data includes account information and authentication information, the external platform access interface is invoked to perform a second authentication on the account information. In response to the second authentication result being successful, the first authentication is performed on the access account based on the authentication information.

3. The method according to claim 1, characterized in that, The method further includes: If the account data includes account information, the external platform access interface is invoked to perform a second authentication on the account information. If the second authentication result is successful, it is determined whether the access request is the first access by the accessing account based on the account identifier in the account information; In response to the access request being the first access by the accessing account, a platform account identifier is assigned to the accessing account; Establish a first mapping relationship between the platform account identifier and the account identifier, and store the first mapping relationship.

4. The method according to claim 3, characterized in that, After assigning a platform account identifier to the access account, the method further includes: Generate authentication information corresponding to the platform account identifier; Send the authentication information to the access account of the external platform; Establish a second mapping relationship between the authentication information, the platform account identifier, and the account identifier, and store the second mapping relationship.

5. The method according to claim 3, characterized in that, Determining whether the access request is the first access by the accessing account based on the account identifier in the account information includes: Retrieve from the database the platform account identifier that has the first mapping relationship with the account identifier in the account information; In response to the fact that no platform account identifier with the first mapping relationship with the account identifier is found in the database, it is determined that the access request is the first access of the access account; In response to finding a platform account identifier in the database that has the first mapping relationship with the account identifier, it is determined that the access request is not the first access by the accessing account.

6. The method according to claim 4, characterized in that, The first authentication of the access account based on the authentication information includes: Retrieve authentication information from the database that has the second mapping relationship with the account identifier; The access account is first authenticated based on the authentication information in the account data and the authentication information obtained from the database.

7. The method according to any one of claims 1 to 6, characterized in that, The receiving of access requests sent by external platforms includes: The sharing information is displayed on the client side of the external platform; In response to the external platform receiving a trigger operation for the shared information, the system generates the access request and receives the access request sent by the external platform.

8. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Create a platform access program on the client side of the external platform; Configure at least one functional component of the current application in the platform access program; The receiving of access requests sent by external platforms includes: The system generates the access request in response to the external platform receiving a trigger operation for any functional component, and receives the access request sent by the external platform.

9. The method according to any one of claims 1 to 6, characterized in that, The response to the first authentication result being authentication passed involves invoking the function interface corresponding to the target function requested by the access request, and providing a request-response mechanism for the access request, including: In response to the first authentication result being successful, the interface identifier of the functional interface corresponding to the target function requested by the access request is determined. In response to finding the service network address corresponding to the interface identifier from a preset routing information file, an interface call request is initiated to the server corresponding to the service network address; the interface call request carries the account data. Receive the request response result returned by the server corresponding to the service network address after responding to the interface call request; The request response result is sent to the access account of the external platform.

10. The method according to claim 9, characterized in that, The method further includes: If no service network address corresponding to the interface identifier is found in the preset routing information file, an error response result is generated; The error response result is sent to the access account of the external platform.

11. An access device for an external platform, characterized in that, include: The receiving module is used to receive access requests sent by external platforms; The parsing module is used to parse the access request and obtain the account data of the accessing account in the external platform; The first authentication module is used to perform a first authentication on the accessing account based on the authentication information when the account data includes account information and authentication information; wherein, the authentication information is generated by the external platform access interface after authenticating the account information when the accessing account accesses the account for the first time; The response module is used to respond to the first authentication result being that authentication is successful by calling the function interface corresponding to the target function requested by the access request and responding to the access request.

12. An electronic device, characterized in that, include: Memory is used to store executable instructions for a computer; A processor, when executing computer-executable instructions stored in the memory, implements the external platform access method according to any one of claims 1 to 10.

13. A computer-readable storage medium, characterized in that, The device stores computer-executable instructions, which, when executed by a processor, implement the external platform access method according to any one of claims 1 to 10.

14. A computer program product, characterized in that, The computer program product includes computer-executable instructions, which are stored in a computer-readable storage medium. When the processor of the electronic device reads the computer-executable instructions from the computer-readable storage medium and executes the computer-executable instructions, it implements the external platform access method according to any one of claims 1 to 10.

Images