Platform integration methods, systems, equipment, and storage media based on online sandboxes

Abstract

This invention provides a platform integration method, system, device, and storage medium based on an online sandbox. The method includes: configuring an application testing environment and an application production environment within the same container; generating at least one test user account within the container; and providing application editing and interactive display in the application testing environment based on the test user account. During the application testing phase, when a user account accessing the container is detected to meet a preset test account whitelist, the user account is allowed to access the container's test user account. After testing is completed and the application is published to the container, the container generates at least one display user account. During the application publishing phase, the application is displayed in the container based on the display user account, which is visible to all accessing users. This invention can improve the efficiency of supplier platform integration and reduce the manpower and time costs incurred by both the platform and the supplier in achieving satisfactory results after the supplier's final integration.

Description

Technical Field

[0001] This invention relates to the field of tourism products, and more specifically, to a platform integration method, system, device, and storage medium based on an online sandbox. Background Technology

[0002] Currently, car rental platforms all use a test environment integration model when connecting with external suppliers. The pain points of existing solutions include:

[0003] Pain Point 1: It is not possible for external suppliers to intuitively see how their data content is displayed on the platform. This is not supplier-friendly and may result in the desired effect only after deployment to the production environment, requiring further time and effort for adjustments.

[0004] Pain Point 2: After the test environment is connected, the production environment still needs to undergo a full-function regression test (considering the possible differences between the test environment and the production environment), which is time-consuming and labor-intensive, and the efficiency of supplier integration is low.

[0005] Based on the two pain points mentioned above, an online sandbox solution was developed and implemented.

[0006] For example, a supplier wants to connect to a car rental platform to receive user car rental orders. The technical integration process with Fliggy includes the following steps:

[0007] 1. Obtain the interface documentation

[0008] 2. Development code

[0009] 3. Both parties will conduct joint debugging, testing, and acceptance in the test environment.

[0010] 4. The vendor releases the code to the production environment.

[0011] 5. Feizhu implements access control for Feizhu in the production environment.

[0012] 6. Suppliers see the display effect on channels such as the Fliggy app downloaded from app stores.

[0013] During steps 3 through 5, suppliers cannot see how their vehicle, pricing, and policy information is displayed. They may only discover in step 6 that some of the effects are not what they wanted, leading to a series of problems such as temporary removal from the platform, reduced user experience, and wasted technical resources for redevelopment and re-testing. It could even result in misunderstandings with customers, harm to users, and damage to the supplier's brand image.

[0014] It's clear that the supplier integration and deployment process doesn't provide a direct view of the customer's experience. Furthermore, differences between production and testing environments can lead to various issues being discovered after deployment, necessitating secondary development, wasting manpower and time, and damaging the brand image of both users and suppliers. Therefore, directly integrating with suppliers in the production environment becomes a problem that needs to be addressed.

[0015] Therefore, the present invention provides a platform docking method, system, device and storage medium based on an online sandbox. Summary of the Invention

[0016] In view of the problems in the prior art, the purpose of this invention is to provide a platform docking method, system, device and storage medium based on online sandbox, which overcomes the difficulties of the prior art, can improve the efficiency of supplier docking with the platform, and reduce the human and time costs incurred by both the platform and the supplier in the process of achieving satisfactory results after the supplier finally connects to the platform.

[0017] Embodiments of the present invention provide a platform integration method based on an online sandbox, comprising the following steps:

[0018] An application testing environment and an application production environment are configured based on the same container. The container generates at least one test user account, and the application testing environment provides the editing and interactive display of the application based on the test user account.

[0019] During the application testing phase, when it is detected that a user account accessing the container meets the preset test account whitelist, the user account is allowed to access the container.

[0020] Upon completion of the test, the application is published to the container, which generates at least one user account for display; and

[0021] During the application deployment phase, the container displays applications based on user accounts, which are visible to all accessing users.

[0022] Preferably, the step of configuring an application testing environment and an application production environment based on the same container, wherein the container generates at least one test user account, and the application testing environment provides editing and interactive display of the application based on the test user account, further includes:

[0023] The test user account is associated with a preset test account whitelist, which includes the accounts of application developers.

[0024] Preferably, the step of configuring an application testing environment and an application production environment based on the same container, wherein the container generates at least one test user account, and the application testing environment provides editing and interactive display of the application based on the test user account, further includes:

[0025] The test user account is configured to interface in both the application testing environment and the application production environment.

[0026] Preferably, during the application testing phase, when it is detected that a user account accessing the container meets the preset test account whitelist, allowing the user account to access the container includes:

[0027] The system checks whether the user account accessing the container meets the preset test account whitelist. If so, the user account is allowed to access the test user account in the container, and the application is downloaded on the terminal based on the test user account to obtain data content that meets the permissions of the test user account. If not, the user account is not allowed to access the test user account in the container.

[0028] Preferably, the step of allowing the test user account to access the container during the application testing phase, when it is detected that the user account accessing the container meets the preset test account whitelist, further includes:

[0029] The user account performs integration testing, verification, and acceptance testing of the application's development code in the test environment.

[0030] Preferably, when the test is completed and the application is published to the container, the container generates at least one display user account, including:

[0031] Once the testing is complete, the application's development code will be deployed to the container.

[0032] The container generates at least one user account for display; and

[0033] The production environment for the application is generated based on the displayed user account and development code.

[0034] Preferably, in the production environment where the application is generated based on the displayed user account and development code, the production environment has multiple interfaces, and each interface collects supplier access data, interface integration success rate, and error logs.

[0035] Embodiments of the present invention also provide a platform docking system based on an online sandbox, used to implement the above-described platform docking method based on an online sandbox, wherein the platform docking system based on an online sandbox includes:

[0036] The testing environment module configures an application testing environment and an application production environment based on the same container. The container generates at least one test user account, and the application testing environment provides the editing and interactive display of the application based on the test user account.

[0037] The categorized access module, during the application testing phase, allows user accounts accessing the container to access the container if the detected user account meets the preset test account whitelist.

[0038] The user display module, once testing is complete, is published to the container, and the container generates at least one user display account; and

[0039] In the application publishing module, during the application publishing phase, the container displays applications based on user accounts, and these user accounts are visible to all accessing users.

[0040] Embodiments of the present invention also provide a platform docking device based on an online sandbox, comprising:

[0041] processor;

[0042] A memory in which executable instructions of the processor are stored;

[0043] The processor is configured to execute the steps of the above-described platform docking method based on an online sandbox by executing the executable instructions.

[0044] Embodiments of the present invention also provide a computer-readable storage medium for storing a program that, when executed, implements the steps of the above-described platform docking method based on an online sandbox.

[0045] The purpose of this invention is to provide a platform integration method, system, device and storage medium based on an online sandbox, which can improve the efficiency of supplier integration with the platform and reduce the manpower and time costs incurred by both the platform and the supplier in the process of achieving satisfactory results after the supplier finally connects to the platform. Attached Figure Description

[0046] Other features, objects, and advantages of the invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings.

[0047] Figure 1 This is a flowchart of the platform integration method based on an online sandbox according to the present invention.

[0048] Figure 2 A schematic diagram illustrating the implementation process of the platform docking method based on an online sandbox according to the present invention.

[0049] Figure 3This is a schematic diagram of the platform docking system based on an online sandbox according to the present invention.

[0050] Figure 4 This is a schematic diagram of the platform docking device based on an online sandbox according to the present invention.

[0051] Figure 5 This is a schematic diagram of the structure of a computer-readable storage medium according to an embodiment of the present invention. Detailed Implementation

[0052] The following specific examples illustrate the implementation methods of this application. Those skilled in the art can easily understand the other advantages and effects of this application from the content disclosed herein. This application can also be implemented or applied through other different specific embodiments, and various details in this application can be modified or changed according to different viewpoints and application systems without departing from the spirit of this application. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be combined with each other.

[0053] The embodiments of this application will now be described in detail with reference to the accompanying drawings, so that those skilled in the art can easily implement the application. This application may be embodied in many different forms and is not limited to the embodiments described herein.

[0054] In this application, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics represented in connection with that embodiment or example, which are included in at least one embodiment or example of this application. Furthermore, the specific features, structures, materials, or characteristics represented may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate different embodiments or examples represented in this application, as well as features of different embodiments or examples.

[0055] Furthermore, the terms "first" and "second" are used for illustrative purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the representation of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0056] To clearly illustrate this application, devices unrelated to the description are omitted, and the same or similar constituent elements throughout the specification are given the same reference numerals.

[0057] Throughout this specification, when it is said that a device is "connected" to another device, this includes not only "direct connection" but also "indirect connection" by placing other components in between. Furthermore, when it is said that a device "comprises" a certain constituent element, unless otherwise stated otherwise, this does not exclude other constituent elements, but rather implies that other constituent elements may be included.

[0058] When we say that a device is "above" another device, this can mean that it is directly above the other device, or it can mean that other devices are present in between. Conversely, when we say that a device is "directly" "above" another device, there are no other devices present in between.

[0059] Although the terms first, second, etc., are used in some instances herein to refer to various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, first interface and second interface, etc., are used. Furthermore, as used herein, the singular forms “a,” “an,” and “the” are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms “comprising,” “including,” indicate the presence of features, steps, operations, elements, components, items, kinds, and / or groups, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms “or” and “and / or” as used herein are interpreted as inclusive, or mean any one or any combination thereof. Thus, “A, B, or C” or “A, B, and / or C” means “any one of: A; B; C; A and B; A and C; B and C; A, B, and C.” Exceptions to this definition will only occur if the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0060] The technical terms used herein are for reference only to specific embodiments and are not intended to limit the scope of this application. The singular form used herein includes the plural form unless the statement explicitly indicates otherwise. The word "comprising" as used in the specification means to specify a particular characteristic, region, integer, step, operation, element, and / or component, and does not exclude the presence or addition of other characteristics, regions, integers, steps, operations, elements, and / or components.

[0061] Although not explicitly defined, all terms, including technical and scientific terms used herein, shall have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. Terms defined in commonly used dictionaries shall be further interpreted as having a meaning consistent with the relevant technical literature and the content of this present application, and shall not be over-interpreted as having an ideal or overly formulaic meaning unless otherwise defined.

[0062] Figure 1This is a flowchart of the platform integration method based on an online sandbox according to the present invention. Figure 1 As shown, an embodiment of the present invention provides a platform integration method based on an online sandbox, including the following steps:

[0063] S110. Configure an application test environment and an application production environment based on the same container. The container generates at least one test user account. The application test environment provides application editing and interactive display based on the test user account.

[0064] S120. During the application testing phase, when it is detected that the user account accessing the container meets the preset test account whitelist, the test user account that allows the user account to access the container is allowed.

[0065] S130. After testing is complete, the system is deployed to a container, and the container generates at least one user account to display.

[0066] S140. During the application deployment phase, the container displays the application based on the user account, and the user account is visible to all accessing users.

[0067] The problem this invention aims to solve is: enabling supplier integration within a production environment while ensuring that the integration process is only visible to relevant personnel and not to actual customers, thereby improving the efficiency of the supplier integration platform and reducing labor and time costs. The core of this invention is that the platform uses a production environment to simultaneously support integration with both the supplier's testing and production environments. Two supplier accounts, A and B, are created for each supplier. Account A is used for the integration process between the platform's production and supplier testing environments, including full-process debugging, testing, and verification of the production environment app (downloadable directly from the app store). This account is only visible to relevant personnel involved in supplier integration and not to official users. Account B is used to publish the product to customers after Account A has completed integration, testing, and acceptance.

[0068] In a preferred embodiment, step S110 further includes:

[0069] Test user accounts are associated with a preset test account whitelist, which includes, but is not limited to, the accounts of application developers.

[0070] In a preferred embodiment, step S110 further includes:

[0071] Test user accounts are configured to interface with both application testing and application production environments, but are not limited to this.

[0072] In a preferred embodiment, step S120 includes:

[0073] S121. Check whether the user account accessing the container meets the preset test account whitelist. If yes, proceed to step S123; otherwise, proceed to step S122.

[0074] S122. Do not allow test user accounts to access the container;

[0075] S123, Allowing test user accounts to access the container; and

[0076] S124. Download the application on the terminal based on the test user account and obtain data content that conforms to the test user account's permissions, but not limited to this.

[0077] In a preferred embodiment, step S120 further includes:

[0078] S125. User accounts may conduct integration testing, verification, and acceptance testing of application development code in the test environment, but this is not a limitation.

[0079] In a preferred embodiment, step S130 includes:

[0080] S131. After the test is completed, deploy the application's development code to the container;

[0081] S132, The container generates at least one user account for display; and

[0082] S133. Based on a production environment that displays user accounts and develops code to generate applications, but not limited to this.

[0083] In a preferred embodiment, in step S133, the production environment has multiple interfaces, and each interface collects supplier access data, interface connection success rate and error logs, but is not limited to this.

[0084] This invention enables a one-time self-service connection in the production environment, and allows customers to intuitively see information such as vehicles, prices, and policies during the connection process without being visible to online users, thus achieving the desired effect for suppliers in one go.

[0085] To reduce the manpower and time costs of platform integration with suppliers, this solution breaks away from the conventional platform integration solution's characteristic of not being able to intuitively see the customer display effect; it ensures that suppliers see what they get during the integration phase, greatly avoiding the manpower and time costs of conventional platform integration solutions that require rework, redevelopment, integration testing, acceptance, and release after discovering problems after release. Figure 2 A schematic diagram illustrating the implementation process of the platform docking method based on an online sandbox according to the present invention.

[0086] like Figure 2As shown, the specific implementation process of this invention is as follows: During the implementation of this invention, a judgment can be made in the platform search interface to specify that users can only see a specified supplier and not other suppliers. Log points are added to each interface provided by the platform for suppliers to track supplier access status. A supplier access progress backend is built, using the data from step two to track and display supplier access progress. The platform creates two backend accounts, A and B, for the supplier. The platform configures account A to point to the supplier's test environment; the platform configures account B to point to the supplier's production environment; the platform sets account A to be visible only to personnel related to supplier access.

[0087] This invention first breaks away from conventional platform integration solutions that only perform interface data integration in the testing environment, and instead performs full-process, full-function integration verification; secondly, it solves the problem of potential inconsistencies between the testing environment and the production environment, thus avoiding additional manpower and time costs.

[0088] The most fundamental feature of this invention is user isolation, ensuring that in the production environment app, supplier account A is only visible to personnel involved in supplier interactions and not to actual customers. After account A is deployed to the production environment, account B becomes visible to actual customers. For example:

[0089] The supplier's technical staff uses account A to connect to the platform. After development, they directly download the platform's production environment APP from the app store. Only this technical staff member can see the data content under account A, and real customers cannot see the data content under account A.

[0090] After the integration process, including Account A development, integration debugging, testing, acceptance, and release, is completed, the platform will activate the supplier's Account B. Subsequently, real customers will be able to see the data content under the supplier's Account B, thus completing the integration process.

[0091] The commonality between this invention and conventional solutions is that they both adopt a standard process of development > integration > testing > acceptance > release. The difference is that this invention uses multiple accounts in the production environment to connect to the supplier's testing and production environments separately, which solves the problem of the lack of intuitiveness in the supplier integration process.

[0092] This invention provides a self-service integration backend to further improve supplier integration efficiency. It records the logs of each interface during the integration and testing process, indicating the success rate of each interface integration and displaying error logs. This helps suppliers complete the integration process independently, significantly reducing the platform's technical manpower and time costs and decreasing the frequency of communication during supplier integration.

[0093] This invention provides the platform with end-to-end integration, testing, and acceptance capabilities across multiple dimensions, including interfaces, logs, backend functions, and app performance for customers, during the supplier integration process. It supports suppliers directly using the production app downloaded from the app store for integration testing, without disclosing it to customers, significantly improving supplier integration efficiency and reducing the manpower and time costs for both the platform and suppliers.

[0094] Figure 3 This is a schematic diagram of the platform docking system based on an online sandbox according to the present invention. For example... Figure 3 As shown, embodiments of the present invention also provide a platform docking system based on an online sandbox, used to implement the above-described platform docking method based on an online sandbox. The platform docking system based on an online sandbox includes:

[0095] Test environment module 51 configures an application test environment and an application production environment based on the same container. The container generates at least one test user account, and the application test environment provides application editing and interactive display based on the test user account.

[0096] The categorized access module 52, during the application testing phase, when it is detected that the user account accessing the container meets the preset test account whitelist, allows the user account to access the test user account of the container.

[0097] Display user module 53, after testing is completed and it is deployed to the container, the container generates at least one display user account; and

[0098] Application publishing module 54: During the application publishing phase, the container displays applications based on user accounts, and these user accounts are visible to all accessing users.

[0099] In a preferred embodiment, the test environment module 51 is configured to associate test user accounts with a preset test account whitelist, which includes application developer accounts.

[0100] In a preferred embodiment, the test environment module 51 is further configured such that test user accounts are configured to interface in the application test environment and the application production environment.

[0101] In a preferred embodiment, the classification access module 52 is configured to detect whether the user account accessing the container meets the preset test account whitelist. If so, the user account is allowed to access the test user account of the container, and the application is downloaded on the terminal based on the test user account to obtain data content that meets the permissions of the test user account. If not, the user account is not allowed to access the test user account of the container.

[0102] In a preferred embodiment, the categorized access module 52 is also configured to perform integration, testing, and acceptance of the application development code for user accounts in the test environment.

[0103] In a preferred embodiment, the user display module 53 is configured to publish the application's development code to a container after testing is completed; the container generates at least one user display account; and a production environment for the application is generated based on the user display account and the development code.

[0104] In a preferred embodiment, the user module 53 is further configured to provide the production environment with multiple interfaces, each of which collects vendor access data, interface connection success rate, and error logs.

[0105] The online sandbox-based platform docking system of the present invention can improve the efficiency of supplier docking with the platform and reduce the manpower and time costs incurred by both the platform and the supplier in the process of achieving satisfactory results after the supplier finally connects to the platform.

[0106] This invention also provides a platform docking device based on an online sandbox, including a processor and a memory storing executable instructions for the processor. The processor is configured to execute steps of a platform docking method based on an online sandbox by executing the executable instructions.

[0107] As shown above, the online sandbox-based platform docking system of this invention can improve the efficiency of supplier docking with the platform and reduce the manpower and time costs incurred by both the platform and the supplier in the process of achieving satisfactory results after the supplier finally connects to the platform.

[0108] Those skilled in the art will understand that various aspects of the present invention can be implemented as systems, methods, or program products. Therefore, various aspects of the present invention can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "platform."

[0109] Figure 4 This is a schematic diagram of the platform docking device based on an online sandbox according to the present invention. See below for reference. Figure 4 To describe an electronic device 600 according to this embodiment of the present invention. Figure 4 The electronic device 600 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0110] like Figure 4 As shown, the electronic device 600 is presented in the form of a general-purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 connecting different platform components (including storage unit 620 and processing unit 610), a display unit 640, etc.

[0111] The storage unit stores program code, which can be executed by the processing unit 610 to perform the steps described in the above-described section on the electronic prescription transfer processing method according to various exemplary embodiments of the present invention. For example, the processing unit 610 can perform actions such as... Figure 1 The steps are shown in the figure.

[0112] Storage unit 620 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 6201 and / or cache memory 6202, and may further include a read-only memory (ROM) 6203.

[0113] Storage unit 620 may also include a program / utility 6204 having a set (at least one) program module 6205, such program module 6205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0114] Bus 630 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the multiple bus structures.

[0115] Electronic device 600 can also communicate with one or more external devices 700 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 600, and / or with any device that enables electronic device 600 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 650. Furthermore, electronic device 600 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 660. Network adapter 660 can communicate with other modules of electronic device 600 via bus 630. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage platforms.

[0116] This invention also provides a computer-readable storage medium for storing a program, which, when executed, implements the steps of a platform integration method based on an online sandbox. In some possible implementations, various aspects of this invention can also be implemented as a program product comprising program code that, when run on a terminal device, causes the terminal device to perform the steps described in the above-described electronic prescription processing method section of this specification according to various exemplary embodiments of the invention.

[0117] As shown above, the online sandbox-based platform docking system of this invention can improve the efficiency of supplier docking with the platform and reduce the manpower and time costs incurred by both the platform and the supplier in the process of achieving satisfactory results after the supplier finally connects to the platform.

[0118] Figure 5 This is a schematic diagram of the structure of the computer-readable storage medium of the present invention. (Reference) Figure 5 As shown, a program product 800 for implementing the above-described method according to an embodiment of the present invention is described. This product may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0119] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0120] Computer-readable storage media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable storage medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0121] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0122] In summary, the purpose of this invention is to provide a platform integration method, system, device, and storage medium based on an online sandbox, which can improve the efficiency of supplier integration with the platform and reduce the manpower and time costs incurred by both the platform and the supplier in the process of achieving satisfactory results after the supplier finally connects to the platform.

[0123] The above description, in conjunction with specific preferred embodiments, provides a further detailed explanation of the present invention. It should not be construed that the specific implementation of the present invention is limited to these descriptions. For those skilled in the art, various simple deductions or substitutions can be made without departing from the concept of the present invention, and all such modifications and substitutions should be considered within the scope of protection of the present invention.

Claims

1. A platform integration method based on an online sandbox, characterized in that, Includes the following steps: An application testing environment and an application production environment are configured based on the same container. The container generates at least one test user account, and the application testing environment provides the editing and interactive display of the application based on the test user account. During the application testing phase, when it is detected that a user account accessing the container meets the preset test account whitelist, the user account is allowed to access the container. Once the test is completed and published to the container, the container generates at least one display user account. as well as During the application deployment phase, the container displays applications based on user accounts, which are visible to all accessing users.

2. The platform integration method based on an online sandbox as described in claim 1, characterized in that, The method of configuring an application testing environment and an application production environment based on the same container, wherein the container generates at least one test user account, and the application testing environment provides editing and interactive display of the application based on the test user account, further includes: The test user account is associated with a preset test account whitelist, which includes the accounts of application developers.

3. The platform integration method based on an online sandbox as described in claim 1, characterized in that, The method of configuring an application testing environment and an application production environment based on the same container, wherein the container generates at least one test user account, and the application testing environment provides editing and interactive display of the application based on the test user account, further includes: The test user account is configured to interface in both the application testing environment and the application production environment.

4. The platform integration method based on online sandbox as described in claim 1, characterized in that, During the application testing phase, when a user account accessing the container is detected to meet the preset test account whitelist, the test user account is allowed to access the container, including: The system checks whether the user account accessing the container meets the preset test account whitelist. If so, the user account is allowed to access the test user account in the container, and the application is downloaded on the terminal based on the test user account to obtain data content that meets the permissions of the test user account. If not, the user account is not allowed to access the test user account in the container.

5. The platform integration method based on an online sandbox as described in claim 4, characterized in that, The provision that, during the application testing phase, when a user account accessing the container is detected to meet the preset test account whitelist, the test user account is allowed to access the container, further includes: The user account performs integration testing, verification, and acceptance testing of the application's development code in the test environment.

6. The platform integration method based on an online sandbox as described in claim 1, characterized in that, Upon completion of the test, the application is published to the container, which generates at least one user account for display, including: Once the testing is complete, the application's development code will be deployed to the container. The container generates at least one user account for display; and The production environment for the application is generated based on the displayed user account and development code.

7. The platform integration method based on an online sandbox as described in claim 6, characterized in that, In the production environment where the application is generated based on the displayed user account and development code, the production environment has multiple interfaces, and each interface collects supplier access data, interface integration success rate, and error logs.

8. A platform docking system based on an online sandbox, used to implement the platform docking method based on an online sandbox as described in claim 1, characterized in that, include: The testing environment module configures an application testing environment and an application production environment based on the same container. The container generates at least one test user account, and the application testing environment provides the editing and interactive display of the application based on the test user account. The categorized access module, during the application testing phase, allows user accounts accessing the container to access the container if the detected user account meets the preset test account whitelist. The user module is displayed, and after testing is completed, it is published to the container, which generates at least one user account for display. as well as In the application publishing module, during the application publishing phase, the container displays applications based on user accounts, and these user accounts are visible to all accessing users.

9. A platform docking device based on an online sandbox, characterized in that, include: processor; A memory in which executable instructions of the processor are stored; The processor is configured to execute the steps of the platform docking method based on any one of claims 1 to 7 by executing the executable instructions.

10. A computer-readable storage medium for storing a program, characterized in that, When the program is executed by the processor, it implements the steps of the platform docking method based on the online sandbox as described in any one of claims 1 to 7.

Images