A method and system for delivering mini-programs across sites

Abstract

The embodiments of this specification disclose a method and system for cross-site delivery of mini-programs. The method includes: obtaining a cross-site delivery request of a mini-program through a cross-site delivery platform, the delivery request including a mini-program to be delivered across sites, and at least two site clients for cross-site delivery; based on the delivery request, performing cross-site delivery capability authentication on the mini-program to be delivered across sites and the site clients for cross-site delivery; when both the mini-program to be delivered across sites and the site clients for cross-site delivery pass the cross-site delivery capability authentication, delivering the mini-program to be delivered across sites to the site clients for cross-site delivery.

Description

Technical Field

[0001] The present invention relates to the field of computer applications, and in particular to a method and system for delivering mini-programs across sites. Background Art

[0002] Mini Program refers to an application developed based on a specific programming language that can be used without downloading and installing. It can run on cross-platform (i.e. cross-site) clients. The biggest feature of Mini Program is its ease of use. Users can open the application by scanning or searching, without having to download and install it in the operating system, so users do not have to worry about installing too many applications. When Mini Programs are delivered across sites, due to the different client capabilities between multiple sites, the Mini Programs to be delivered across sites and the site clients for cross-site delivery need to meet certain delivery conditions to ensure that the Mini Programs can run normally on the site clients after cross-site delivery.

[0003] Therefore, it is hoped to provide a method for cross-site delivery of mini-programs. Summary of the invention

[0004] One of the embodiments of the present specification provides a method for cross-site delivery of mini-programs, which is applied to a cross-site delivery platform for mini-programs, the method comprising: obtaining a cross-site delivery request for the mini-program through the cross-site delivery platform for the mini-program, the delivery request comprising the mini-program to be delivered across sites, and at least two site clients for cross-site delivery; based on the delivery request, performing cross-site delivery capability authentication on the mini-program to be delivered across sites and the site clients for cross-site delivery; when the mini-program to be delivered across sites and the site clients for cross-site delivery both pass the cross-site delivery capability authentication, delivering the mini-program to be delivered across sites to the site clients for cross-site delivery.

[0005] In some embodiments, the cross-site delivery capability authentication includes application program interface capability authentication.

[0006] In some embodiments, the cross-site delivery capability certification of the mini-program to be cross-site delivered and the site client for the cross-site delivery includes: obtaining the capability standard for the cross-site delivery of the mini-program, and determining whether the capability of the site client for the cross-site delivery meets the capability standard for the cross-site delivery of the mini-program; when the capability standard for the cross-site delivery of the mini-program is met, determining whether the capabilities of the mini-program to be cross-site delivered and the site client for the cross-site delivery match; when the two match, determining that both the mini-program to be cross-site delivered and the site client for the cross-site delivery have passed the cross-site delivery capability certification.

[0007] In some embodiments, the method further includes: when the capability of the site client for cross-site delivery does not meet the capability standard of the mini-program cross-site delivery, returning the site client for cross-site delivery to its corresponding site so that the site can update the client.

[0008] In some embodiments, the method also includes: when the capabilities of the mini-program to be cross-site delivered and the site client of the cross-site delivery do not match, returning the site client of the cross-site delivery and the judgment result to its corresponding site so that the site can update the client; and updating the capability standard of the mini-program cross-site delivery according to the judgment result, and storing the updated capability standard of the mini-program cross-site delivery in the database.

[0009] In some embodiments, the method further includes: when the site client for cross-site delivery passes the cross-site delivery capability authentication, sending it to at least one terminal device so that the at least one terminal device performs real machine testing on the site client for cross-site delivery.

[0010] In some embodiments, the method further includes: when the version of the cross-site delivery site client is updated, performing the cross-site delivery capability authentication on the updated cross-site delivery site client.

[0011] In some embodiments, the method also includes: before the site client for cross-site delivery enters the mini-program cross-site delivery platform, authenticating the site client's ability to be delivered before entering the site client; the delivery ability authentication process includes: obtaining the mini-program cross-site delivery capability standard; based on the mini-program cross-site delivery capability standard, generating a mini-program that has the mini-program cross-site delivery capability standard, and running the mini-program on the site client before entering the site; based on the running result, judging whether the site client before entering the site has the ability to be delivered across sites; when the site client before entering the site has the ability to be delivered across sites, allowing it to enter the mini-program cross-site delivery platform.

[0012] One of the embodiments of the present specification provides a mini-program cross-site delivery system, which is applied to a mini-program cross-site delivery platform, and the system includes: a first acquisition module, used to obtain the mini-program cross-site delivery request, the delivery request includes the mini-program to be cross-site delivered, and at least two site clients for cross-site delivery; a first capability authentication module, used to perform cross-site delivery capability authentication on the mini-program to be cross-site delivered and the site client for cross-site delivery based on the delivery request; a delivery module, used to deliver the mini-program to be cross-site delivered to the site client for cross-site delivery when both the mini-program to be cross-site delivered and the site client for cross-site delivery pass the cross-site delivery capability authentication.

[0013] In some embodiments, the cross-site delivery capability authentication includes application program interface capability authentication.

[0014] In some embodiments, the first capability authentication module is used to: obtain the capability standard for cross-site delivery of the mini-program, and determine whether the capability of the site client for cross-site delivery meets the capability standard for cross-site delivery of the mini-program; when the capability standard for cross-site delivery of the mini-program is met, determine whether the capabilities of the mini-program to be cross-site delivered and the site client for cross-site delivery match; when the two match, determine that both the mini-program to be cross-site delivered and the site client for cross-site delivery have passed the cross-site delivery capability authentication.

[0015] In some embodiments, the first capability authentication module is used to: when the capability of the site client for cross-site delivery does not meet the capability standard of the mini-program cross-site delivery, return the site client for cross-site delivery to its corresponding site so that the site can update the client.

[0016] In some embodiments, the first capability authentication module is used to: when the capabilities of the mini-program to be cross-site delivered and the site client of the cross-site delivery do not match, return the site client of the cross-site delivery and the judgment result to its corresponding site so that the site can update the client; and update the capability standard of the mini-program cross-site delivery according to the judgment result, and store the updated capability standard of the mini-program cross-site delivery in the database.

[0017] In some embodiments, the system also includes a testing module, which is used to: when the site client for cross-site delivery passes the cross-site delivery capability authentication, send it to at least one terminal device so that the at least one terminal device can perform real machine testing on the site client for cross-site delivery.

[0018] In some embodiments, the first capability authentication module is further used to: when the version of the cross-site delivery site client is updated, perform the cross-site delivery capability authentication on the updated cross-site delivery site client.

[0019] In some embodiments, the system includes a second capability authentication module, which is used to: before the site client of the cross-site delivery enters the mini-program cross-site delivery platform, perform delivery capability authentication on the site client before entering. The delivery capability authentication process includes: obtaining the capability standard of the mini-program cross-site delivery; based on the capability standard of the mini-program cross-site delivery, generating a mini-program that meets the capability standard of the mini-program cross-site delivery, and running the mini-program on the site client before entering; based on the running result, judging whether the site client before entering has the ability to be delivered across sites; when the site client before entering has the ability to be delivered across sites, allowing it to enter the mini-program cross-site delivery platform.

[0020] One of the embodiments of the present specification provides a computer-readable storage medium, wherein the storage medium stores computer instructions. When a computer reads the computer instructions in the storage medium, the computer executes the method described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] This specification will be further described in the form of exemplary embodiments, which will be described in detail by the accompanying drawings. These embodiments are not restrictive, and in these embodiments, the same number represents the same structure, wherein:

[0022] Figure 1 This is a schematic diagram of an application scenario of cross-site delivery of a mini-program according to some embodiments of this specification;

[0023] Figure 2 is an exemplary block diagram of a mini-program cross-site delivery system according to some embodiments of this specification;

[0024] Figure 3 is an exemplary block diagram of a mini-program cross-site delivery system according to other embodiments of this specification;

[0025] Figure 4 is an exemplary flow chart of a method for delivering a mini-program across sites according to some embodiments of this specification;

[0026] Figure 5 It is an exemplary flowchart of the method for cross-site delivery of mini-programs shown in other embodiments of this specification. DETAILED DESCRIPTION

[0027] In order to more clearly illustrate the technical solutions of the embodiments of this specification, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of this specification. For ordinary technicians in this field, this specification can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0028] It should be understood that the "system", "device", "unit" and / or "module" used herein are a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.

[0029] As shown in this specification, unless the context clearly indicates an exception, the words "a", "an", "a kind" and / or "the" do not refer to the singular, but also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0030] Although this specification makes various references to certain modules or units in the system according to the embodiments of this specification, any number of different modules or units can be used and run on the client and / or server. The modules are illustrative only, and different aspects of the system and method can use different modules.

[0031] Flowcharts are used in this specification to illustrate the operations performed by the system according to the embodiments of this specification. It should be understood that the preceding or following operations are not necessarily performed precisely in order. Instead, the steps may be processed in reverse order or simultaneously. At the same time, other operations may also be added to these processes, or one or more operations may be removed from these processes.

[0032] The embodiments of this specification provide a method for cross-site delivery of mini-programs. When a mini-program is delivered across sites, the mini-program to be delivered across sites, the site client for cross-site delivery, and the capability standards for cross-site delivery of the mini-program need to maintain capability alignment so that the mini-program can operate normally on the delivered site client. In some embodiments, before delivering the mini-program, the delivery capability of the mini-program to be delivered across sites and the site client for cross-site delivery can be authenticated. When both the mini-program to be delivered across sites and the site client for cross-site delivery pass the delivery capability authentication, the mini-program is delivered across sites to the corresponding site client. In some embodiments, before the site client is stationed on the mini-program cross-site delivery platform, the capabilities of the site client can be tested based on the capability standards for cross-site delivery of the mini-program. When the capabilities of the site client meet the capability standards for cross-site delivery of the mini-program, the site client is stationed on the mini-program cross-site delivery platform.

[0033] Figure 1 This is a schematic diagram of an application scenario of cross-site delivery of a mini-program according to some embodiments of this specification.

[0034] like Figure 1 As shown, scenario 100 may include a first server 110, a second server 120, a terminal device 130, a database 140, and a network 150. The mini-program cross-site delivery method may be applied to various scenarios where mini-programs need to be delivered across sites. For example, the first server 110 may deliver the mini-program across sites to site client A, or deliver the mini-program across sites to site client A and site client B at the same time. In some embodiments, the site may be a merchant that has a demand for delivery and is stationed in the mini-program cross-site delivery platform, such as merchants such as Alipay.

[0035] The first server 110 can be used to perform capability authentication on the mini program to be delivered across the site and the site client to be delivered across the site. For example, the first server 110 can perform cross-site delivery capability authentication on the mini program to be delivered across the site and the site client to be delivered across the site. For another example, the first server 110 can perform delivery capability authentication on the site client before entering the mini program cross-site delivery platform. In some embodiments, the first server 110 can be a server corresponding to the mini program cross-site delivery platform. In some embodiments, the second server 120 can be used to perform capability authentication on the site client before entering the mini program cross-site delivery platform. For example, the second server 120 can be a server corresponding to the site terminal, which can perform delivery capability authentication on the site client before entering the mini program cross-site delivery platform. In some embodiments, the first server 110 and the second server 120 can communicate with each other. For example, the first server 110 can obtain the site client from the second server 120. For another example, the second server 120 can obtain the capability authentication result of the site client and / or the mini program from the first server 110.

[0036] In some embodiments, the server (e.g., the first server 110, the second server 120) can be a single server or a server group. In some embodiments, the server group can be centralized or distributed (e.g., the first server 110 can be a distributed system, the second server 120 can be a centralized system, etc.). In some embodiments, the server can be local or remote. For example, the first server 110 and / or the second server 120 can access the information and / or data stored in the terminal device 130 and / or the database 140 through the network 150. For another example, the first server 110 and / or the second server 120 can be directly connected to the terminal device 130 and / or the database 140 to access the stored information and / or data. In some embodiments, the server can be implemented on a cloud platform. As an example only, the cloud platform can include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, a cross-cloud, a multi-cloud, etc., or any combination of the above examples. In some embodiments, the server can be implemented on a computing device, such as a computer, a mobile device, or any device with a computing and processing function.

[0037] In some embodiments, the server may include a processing device (for example, the first server 110 may include a processing device 112, and the second server 120 may include a processing device 122). The processing device may process various information and / or data related to the cross-site delivery of mini-programs to perform one or more functions described in this specification. For example, the processing device 112 may obtain information about the mini-program from the terminal device 130. In some embodiments, the processing device may include one or more processors (for example, a single-chip processor or a multi-chip processor). By way of example only, the processing device may include one or more hardware processors, such as a central processing unit (CPU), an application-specific integrated circuit (ASIC), an application-specific instruction set processor (ASIP), a graphics processing unit (GPU), a physical processing unit (PPU), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a controller, a microcontroller unit, a reduced instruction set computer (RISC), a microprocessor, etc., or any combination of the above examples.

[0038] The terminal device 130 can be any device that can provide applet and client operation. For example, the terminal device 130 may include a mobile device, etc. In some embodiments, the mobile device may include a smart home device, a wearable device, a smart mobile device, a virtual reality device, an augmented reality device, etc., or any combination of the above examples. In some embodiments, the smart home device may include smart lighting equipment, control equipment for smart appliances, smart monitoring equipment, smart TVs, smart cameras, intercoms, etc., or any combination of the above examples. In some embodiments, wearable devices may include bracelets, shoes and socks, glasses, helmets, watches, clothing, backpacks, smart accessories, etc., or any combination of the above examples. In some embodiments, the smart mobile device may include a mobile phone, a personal digital assistant, a gaming device, a navigation device, a POS machine, a laptop computer, a desktop computer, etc., or any combination of the above examples.

[0039] In some embodiments, the terminal device 130 can be used to perform real machine testing on the mini program and / or client. For example, the mini program can be run on the terminal device 130 to test whether the functions of the mini program can be normally implemented on the terminal device. For another example, the client of the mini program can be run on the terminal device 130 to test whether the capabilities between the client and the mini program match. In some embodiments, the terminal device 130 may include a smart phone 130-1, a tablet computer 130-2, a laptop computer, a desktop computer, etc. In some embodiments, the user can use the functions of the mini program and / or client through the terminal device 130. In some embodiments, the terminal device 130 can obtain the running data of the mini program and the client, and transmit the running data of the mini program and the client to the first server 110 or the second server 120. For example, the terminal device 130 can send the real machine test results of the mini program and / or the client to the first server 110, and the first server 110 can determine whether to perform cross-site delivery of the mini program based on the test results. For another example, the terminal device 130 may send the real machine test result of the client to the second server 120 so that the second server 120 can update or modify the data of the client.

[0040] The database 140 may store data and / or instructions. In some embodiments, the database 140 may store data obtained from the terminal device 130 and / or the network 150. In some embodiments, the storage device 140 may store data and / or instructions for execution or use by the server (e.g., the first server 110, the second server 120), and the server may implement the exemplary method described in this specification by executing or using these data and / or instructions. In some embodiments, the database 140 may include a large capacity memory, a removable memory, a volatile read-write memory, a read-only memory (ROM), etc., or any combination of the above examples. An exemplary large capacity memory may include a disk, an optical disk, a solid-state disk, etc. An exemplary removable memory may include a flash drive, a floppy disk, an optical disk, a memory card, a compressed disk, a magnetic tape, etc. In some embodiments, the database 140 may be implemented on a cloud platform. As an example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, a cross-cloud, a multi-cloud, etc., or any combination of the above examples.

[0041] In some embodiments, the database 140 may be connected to the network 150 to communicate with one or more components in the scene 100 (e.g., the first server 110, the second server 120, the terminal device 130). One or more components in the scene 100 may access data or instructions stored in the database 140 through the network 150. In some embodiments, the database 140 may be directly connected or communicated with one or more components in the scene 100 (e.g., the first server 110, the second server 120, the terminal device 130). In some embodiments, the database 140 may be part of the first server 110 and / or the second server 120.

[0042] The network 150 can facilitate the exchange of information and / or data. In some embodiments, one or more components in the scene 100 (e.g., the first server 110, the second server 120, the terminal device 130, the database 140) can send information and / or data to other components in the scene 100 through the network 150. For example, the first server 110 can obtain the data of the site client from the second server 120 through the network 150. For another example, the second server 120 can obtain the real machine test results of the client from the terminal device 130 through the network 150. In some embodiments, the network 150 can be any one or a combination of a wired network or a wireless network. As an example only, the network 150 may include a cable network, a wired network, an optical fiber network, a remote communication network, an intranet, the Internet, a local area network (LAN), a wide area network (WAN), a wireless local area network (WLAN), a metropolitan area network (MAN), a wide area network (WAN), a public switched telephone network (PSTN), a Bluetooth network, a ZigBee network, a near field communication (NFC) network, etc. or any combination of the above examples. In some embodiments, the network 150 may include one or more network exchange points. For example, network 150 may include wired or wireless network exchange points, such as base stations and / or Internet exchange points 150-1, 150-2, ..., through which one or more components of scene 100 may be connected to network 150 to exchange data and / or information.

[0043] In some alternative embodiments, scenario 100 may also include other components for implementing cross-site delivery of the mini-program, for example, it may include a third server for mini-program development, modification, and update, which is not limited in this specification.

[0044] Figure 2 It is an exemplary block diagram of a mini-program cross-site delivery system according to some embodiments of this specification.

[0045] like Figure 2As shown, the system 200 may include a first acquisition module 210 , a first capability authentication module 220 , a delivery module 230 , a testing module 240 , and a second capability authentication module 250 .

[0046] The first acquisition module 210 can be used to obtain a cross-site delivery request for a mini program. In some embodiments, the delivery request can include a mini program to be delivered across sites, and at least two site clients for cross-site delivery. For more information about the mini program cross-site delivery request, see Figure 4 And the related description will not be repeated here.

[0047] The first capability authentication module 220 can be used to perform cross-site delivery capability authentication on the mini program to be delivered across sites and the site client of the cross-site delivery based on the delivery request. In some embodiments, the cross-site delivery capability authentication may include application interface capability authentication. In some embodiments, the first capability authentication module 220 can obtain the capability standard of the mini program's cross-site delivery, and determine whether the capability of the site client of the cross-site delivery meets the capability standard of the mini program's cross-site delivery; when the capability standard of the mini program's cross-site delivery is met, determine whether the capabilities between the mini program to be delivered across sites and the site client of the cross-site delivery match; when the two match, determine that the mini program to be delivered across sites and the site client of the cross-site delivery have passed the cross-site delivery capability authentication. In some embodiments, the first capability authentication module 220 can return the site client of the cross-site delivery to its corresponding site when the capability of the site client of the cross-site delivery does not meet the capability standard of the mini program's cross-site delivery, so that the site can update the client. In some embodiments, when the capabilities of the mini-program to be cross-site delivered do not match those of the site client for cross-site delivery, the first capability authentication module 220 can return the site client for cross-site delivery and the judgment result to its corresponding site so that the site can update the client. In some embodiments, the first capability authentication module 220 can update the capability standard of the mini-program for cross-site delivery based on the judgment result, and store the updated capability standard of the mini-program for cross-site delivery in the database. In some embodiments, the first capability authentication module 220 can perform the cross-site delivery capability authentication on the updated site client for cross-site delivery when the version of the site client for cross-site delivery is updated. For more information on cross-site delivery capability authentication, please refer to Figure 4 And the related description will not be repeated here.

[0048] The delivery module 230 can be used to deliver the mini program to be delivered across sites to the corresponding cross-site delivery site client. In some embodiments, the delivery module 230 can deliver the mini program to be delivered across sites to the cross-site delivery site client when both the mini program to be delivered across sites and the cross-site delivery site client pass the cross-site delivery capability certification. For more information about delivering the mini program to be delivered across sites to the cross-site delivery site client, please refer to Figure 4 And the related description will not be repeated here.

[0049] The test module 240 can be used to perform real machine testing on the mini program and / or client. In some embodiments, the test module 240 can send the site client of the cross-site delivery to at least one terminal device when it passes the cross-site delivery capability certification, so that the at least one terminal device can perform real machine testing on the site client of the cross-site delivery. In some embodiments, the test module 240 can send the mini program to be delivered across sites to the terminal device so as to perform real machine testing on the mini program. For more information about real machine testing of mini programs / site clients, please refer to Figure 4 And the related description will not be repeated here.

[0050] The second capability authentication module 250 can be used to authenticate the site client's ability to be delivered before the site client for cross-site delivery enters the mini-program cross-site delivery platform. Specifically, the second capability authentication module 250 can obtain the capability standard for the mini-program cross-site delivery; based on the capability standard for the mini-program cross-site delivery, generate a mini-program that meets the capability standard for the mini-program cross-site delivery, and run the mini-program on the site client; based on the running result, determine whether the site client has the ability to be delivered across sites; when the site client has the ability to be delivered across sites, allow it to enter the mini-program cross-site delivery platform.

[0051] It should be understood that Figure 2The system and its modules shown can be implemented in various ways. For example, the system 200 and its modules can be implemented by hardware, software or a combination of software and hardware. Among them, the hardware part can be implemented by dedicated logic; the software part can be stored in a memory and executed by an appropriate instruction execution system, such as a microprocessor or a dedicated design hardware. Those skilled in the art will understand that the above methods and systems can be implemented using computer executable instructions and / or included in a processor control code, such as a carrier medium such as a disk, CD or DVD-ROM, a programmable memory such as a read-only memory (firmware), or a data carrier such as an optical or electronic signal carrier. Such code is provided on the device and its modules of this specification. Not only can the hardware circuits such as ultra-large-scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, etc., or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc. be implemented, it can also be implemented by software such as executed by various types of processors, and it can also be implemented by a combination of the above hardware circuits and software (for example, firmware).

[0052] It should be noted that the above description of system 200 is only for convenience of description and does not limit this specification to the scope of the embodiments. It is understandable that for those skilled in the art, after understanding the principle of the system, it is possible to arbitrarily combine the modules or form a subsystem connected to other modules without deviating from this principle. For example, system 200 may also include a communication module for communicating with other components. For another example, the modules in system 200 may share a storage module, or each module may have its own storage module. Such variations are all within the scope of protection of this specification.

[0053] Figure 3 It is an exemplary block diagram of a mini-program cross-site delivery system according to other embodiments of this specification.

[0054] In some embodiments, the site terminal can authenticate the client's ability to be delivered before placing the site client on the mini-program cross-site delivery platform. Figure 3 As shown, the system 300 may be applied to a site terminal. In some embodiments, the system 300 may include a second acquisition module 310 , an operation module 320 , a determination module 330 , and a sending module 340 .

[0055] The second acquisition module 310 can be used to obtain the capability standard of cross-site delivery of the mini program.

[0056] The running module 320 can be used to generate a mini-program that meets the mini-program cross-site delivery capability standard based on the mini-program cross-site delivery capability standard, and run the mini-program on the site client.

[0057] The determination module 330 may be used to determine whether the site client has the ability to be delivered across sites based on the operation result.

[0058] The sending module 340 can be used to send the site client to the mini program cross-site delivery platform when the site client has the ability to be delivered across sites, so as to enter the mini program cross-site delivery platform. For more information about the system 300, please refer to other parts of this specification (for example, Figure 4 , Figure 5 and its related description), which will not be repeated here.

[0059] It should be understood that Figure 3 The system and its modules shown can be implemented in various ways. For example, the system and its modules can be implemented by hardware, software or a combination of software and hardware. Among them, the hardware part can be implemented by dedicated logic; the software part can be stored in a memory and executed by an appropriate instruction execution system, such as a microprocessor or a dedicated design hardware. Those skilled in the art will understand that the above methods and systems can be implemented using computer executable instructions and / or included in a processor control code, such as a carrier medium such as a disk, CD or DVD-ROM, a programmable memory such as a read-only memory (firmware), or a data carrier such as an optical or electronic signal carrier. Such code is provided on the device and its modules of this specification. Not only can the hardware circuits such as ultra-large-scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc. be implemented, it can also be implemented by software such as executed by various types of processors, and it can also be implemented by a combination of the above hardware circuits and software (for example, firmware).

[0060] It should be noted that the above description of system 300 is only for convenience of description and does not limit this specification to the scope of the embodiments. It is understandable that for those skilled in the art, after understanding the principle of the system, it is possible to arbitrarily combine the various modules or form a subsystem connected to other modules without deviating from this principle. For example, system 300 may also include a communication module for communicating with other components. For another example, each module in system 300 may share a storage module, or each module may have its own storage module. Such variations are all within the scope of protection of this specification. For another example, each module in system 300 may be the same as the submodule or unit contained in the second capability authentication module 250 in system 200.

[0061] Figure 4 is an exemplary flow chart of a method for delivering a mini-program across sites according to some embodiments of this specification. Figure 4 As shown, in some embodiments, the process 400 may be executed by the processing device 112 (eg, the first server 110) or the applet cross-site delivery system 200. It includes:

[0062] Step 410 , obtaining a mini program cross-site delivery request. In some embodiments, step 410 may be performed by the first acquisition module 210 .

[0063] Mini-program cross-site delivery refers to running the mini-program on different site clients. For example, a mini-program that can provide takeaway services can be delivered to the client of Alipay across sites. Users can open the mini-program on the page of the Alipay client without downloading and installing the takeaway service mini-program, and initiate a request for takeaway. Sites refer to merchants that have joined the mini-program cross-site delivery platform, such as merchants such as Alipay. The mini-program cross-site delivery platform refers to a one-stop platform that can provide mini-program release processes and corresponding operating capabilities. For example, a newly developed mini-program can be released through the mini-program cross-site delivery platform so that it can be delivered on different sites. In some embodiments, the mini-program cross-site delivery platform may include one or more mini-programs with delivery requirements, and one or more sites and / or site clients with delivery requirements. In some embodiments, the mini-program cross-site delivery platform can perform risk assessment, performance audit, security scanning, capability certification, real machine testing, and one or more combinations of tests on the mini-program and / or site client.

[0064] In some embodiments, the mini-program cross-site delivery platform can authenticate the site client's ability to be delivered before the site client with the demand for delivery enters the platform. Specifically, the ability standard for mini-program cross-site delivery can be obtained, and based on the ability standard for mini-program cross-site delivery, a mini-program with the ability standard for mini-program cross-site delivery can be generated, and the mini-program can be run on the site client; based on the running result, it is determined whether the site client has the ability to be delivered across sites; when the site client has the ability to be delivered across sites, it is allowed to enter the mini-program cross-site delivery platform. In some embodiments, the mini-program cross-site delivery platform can obtain the mini-program on the platform that has the mini-program cross-site delivery ability standard, and authenticate the site client's ability to be delivered based on the mini-program. In some embodiments, the mini-program cross-site delivery platform can authenticate the site client's ability to be delivered before entering the platform through other methods. The delivery ability authentication may include but is not limited to risk ability authentication, application interface ability authentication, etc., and this specification does not limit this.

[0065] In some embodiments, a mini-program cross-site delivery request can be obtained through the mini-program cross-site delivery platform. In some embodiments, a mini-program can be delivered to one or more site clients across sites. In some embodiments, a site client can be delivered with one or more mini-programs. Multiple mini-programs can be mini-programs with different functional attributes. Functional attributes refer to the service characteristics of the mini-program itself, which may include but are not limited to the service type of the mini-program, industry information, service feature data that can characterize the mini-program, etc. For example, a site client can be delivered with multiple mini-programs with different functional attributes such as takeout, ride-hailing, music, and city services at the same time.

[0066] In some embodiments, the delivery request may include the mini-program to be delivered across sites, and at least two site clients for the cross-site delivery. In some embodiments, the site may update, install, run, and uninstall the client through a protocol with the mini-program cross-site delivery platform. For example, the protocol may include, but is not limited to, a platform service protocol, a security protocol, and the like.

[0067] In some embodiments, the cross-site delivery request of the mini-program can be obtained by other means. For example, the cross-site delivery request of the mini-program can be obtained by the site client. The delivery request may include other information, such as the functional attributes of the mini-program, the running size of the mini-program, the running memory of the client, etc. This manual does not limit this.

[0068] Step 420 , based on the delivery request, performs cross-site delivery capability authentication on the mini program to be delivered across sites and the site client of the cross-site delivery. In some embodiments, step 420 may be performed by the first capability authentication module 220 .

[0069] In some embodiments, cross-site delivery capability authentication may include application program interface (API) capability authentication. API, also known as application programming interface, is a set of definitions, programs and protocols. Through the API interface, mutual communication between computer software can be realized. For example, the application program interface can be coupled to the first server 110 and / or the second server 120 and provide programmatic and Web interfaces to them respectively. For another example, the application program interface can also access the network 150 and the database 140. In some embodiments, the application program interface capability authentication may include but is not limited to the authentication of the number, function, and consistency of the protocol of the application program interface. For example, the number of standard APIs for cross-site delivery of mini programs is 100. If the site client API does not meet the 100 quantity requirements, it is considered that the site client does not meet the capability authentication, that is, it has not passed the cross-site delivery capability authentication. For another example, if the functional version of the application program interface allowed by the site client is version 2.0, the capability authentication can be realized by detecting whether the functional version of the application program interface of the mini program to be delivered across the site is version 2.0. For another example, it can be detected whether the standard application program interface security protocol allowed by the site client is consistent with the application program interface security protocol of the mini program to achieve capability authentication. In some embodiments, when the mini program to be delivered across sites and / or the site client to be delivered across sites fails to pass the cross-site delivery capability certification, the mini program to be delivered across sites and / or the site client to be delivered across sites may be returned to the corresponding uploading user. For example, the site client that has not passed the cross-site delivery capability certification may be returned to the corresponding site so that the site can update or adjust its client. For another example, the mini program that has not passed the cross-site delivery capability certification may be returned to its developer so that the developer can modify or update the mini program.

[0070] In some embodiments, the mini-program cross-site delivery platform can directly deliver the mini-program to the corresponding site client after obtaining the mini-program cross-site delivery request. In this case, since the mini-program and the site client have not been authenticated for cross-site delivery, the delivered mini-program and the site client may not match their capabilities, resulting in the mini-program failing to run normally on the site client or some of the mini-program's functions failing to be implemented through the site client.

[0071] In some embodiments of the present invention, the processing device 112 can implement cross-site delivery capability authentication of the mini program to be delivered across sites and the site client to be delivered across sites by detecting whether the capability standard of the mini program to be delivered across sites, the mini program to be delivered across sites, and the site client to be delivered across sites match. Specifically:

[0072] Step 423, determine whether the capability of the site client for cross-site delivery meets the capability standard for cross-site delivery of the mini program.

[0073] In some embodiments, the capability standards for cross-site delivery of mini-programs may include the capability standards for the application program interface of the mini-program. For example, the number, functions, and consistency of protocols of the mini-program application program interface. In some embodiments, the capability standards for cross-site delivery of mini-programs can be determined based on user needs. For example, data such as user feedback on the functions of the mini-programs and the demand for the functional characteristics of the mini-programs can be obtained to determine the capability standards for cross-site delivery of mini-programs. In some embodiments, the capability standards for cross-site delivery of mini-programs can be determined based on the capabilities of the mini-programs to be delivered across sites. For example, if the API function version of the mini-program is version 2.1, the capability standard for cross-site delivery of the mini-program can be determined as the API function version is version 2.1. In some alternative embodiments, the capability standards for cross-site delivery of mini-programs may include but are not limited to security standards, delivery protocols, etc., and this specification does not limit this.

[0074] In some embodiments, the capability standard of the mini-program cross-site delivery may be obtained from a database (eg, database 140). In some embodiments, the capability standard of the mini-program cross-site delivery may be obtained from a terminal device (eg, terminal device 130).

[0075] In some embodiments, by comparing the data of the capability standard of the mini-program cross-site delivery with the data of the site client of the cross-site delivery, it can be judged whether the capability of the site client of the cross-site delivery meets the capability standard of the mini-program cross-site delivery. For example, if the capability standard of the mini-program cross-site delivery is that the API function version is version 1.9, if the API function version of the site client is version 2.1, it can be judged to meet the capability standard of the mini-program cross-site delivery. Since the function version of the application program interface of the site client of the cross-site delivery can be compatible with a lower version, it can be judged to be satisfied. For another example, if the capability standard of the mini-program cross-site delivery is that the number of APIs is 100, then when the number of APIs of the site client is 100, it is judged to meet the capability standard of the mini-program cross-site delivery.

[0076] In some embodiments, when the capability of the site client for cross-site delivery does not meet the capability standard for cross-site delivery of the mini-program, the processing device 112 may return the site client to its corresponding site so that the site can update the client. For example, the processing device 112 may return the site client that does not meet the capability standard to its corresponding site terminal, and the second server 120 (e.g., the processing device 122) corresponding to the site terminal may change the number of APIs of its client to 100 based on the capability standard for cross-site delivery of the mini-program that the number of APIs is 100, and send it to the first server 110 again for delivery capability certification.

[0077] When the capability of the site client for cross-site delivery meets the capability standard of the mini-program cross-site delivery, step 425 is executed.

[0078] Step 425, determine whether the capabilities of the mini program to be delivered across sites match those of the site client to be delivered across sites.

[0079] In some embodiments, the processing device 112 can determine whether the capabilities of the two match by comparing the data between the small program to be delivered across sites and the site client for cross-site delivery. For example, the number of APIs of the site client is 50, and the number of APIs of the small program to be delivered across sites is 50, then it is determined that the capabilities of the small program to be delivered across sites and the site client for cross-site delivery match. For another example, the API function version of the site client is version 2.0, and the API function version of the small program to be delivered across sites is version 2.0, then it is determined that the capabilities of the small program to be delivered across sites and the site client for cross-site delivery match. It should be noted that only when all the capability data (for example, API quantity, version, security protocol, etc.) between the small program to be delivered across sites and the site client for cross-site delivery match, the two are considered to match, otherwise it is considered that the capabilities of the small program to be delivered across sites and the site client for cross-site delivery do not match.

[0080] In some embodiments, when the capabilities of the mini program to be delivered across sites do not match those of the site client to be delivered across sites, the processing device 112 may return the site client to its corresponding site so that the site can update the client. For example, the processing device 112 may return the site client to its corresponding site terminal when the two do not match, and the second server 120 (e.g., the processing device 122) corresponding to the site terminal may change the capabilities of its client to be consistent with the capabilities of the mini program to be delivered across sites, and send it to the first server 110 again for delivery capability authentication. In some embodiments, the mini program is developed based on the latest delivery capability standards, and updating the site client capabilities based on the capabilities of the mini program can make the delivered site client more compatible with the mini program to be delivered across sites and meet user needs.

[0081] In some embodiments, the processing device 112 may update the capability standard for the mini-program cross-site delivery according to the judgment result in step 425, and store the updated capability standard for the mini-program cross-site delivery in the database. For example, when the capabilities of the mini-program to be delivered across sites do not match those of the site client for cross-site delivery, the capability of the mini-program to be delivered across sites may be determined as the updated capability standard for the mini-program cross-site delivery, and stored in the database. In some embodiments, the processing device 112 may update the capability standard for the mini-program cross-site delivery in real time or periodically based on user needs.

[0082] In some embodiments, the processing device 112 can directly match and authenticate the capabilities between the mini program to be delivered across sites and the site client for cross-site delivery. When the capabilities of the two match, it is determined that the mini program to be delivered across sites and the site client for cross-site delivery have both passed the cross-site delivery capability certification. In other embodiments, the processing device 112 can determine the capability standard for the mini program's cross-site delivery based on the mini program to be delivered across sites, and perform capability authentication on the site client for cross-site delivery based on the capability standard. When the site client for cross-site delivery matches the capability standard, it is determined that the mini program to be delivered across sites and the site client for cross-site delivery have both passed the cross-site delivery capability authentication.

[0083] When the mini program to be cross-site delivered and the site client for cross-site delivery both pass the cross-site delivery capability certification, step 430 is executed.

[0084] Step 430 , determine that the mini program to be delivered across sites and the site client for cross-site delivery have passed the cross-site delivery capability certification, and deliver the mini program to be delivered across sites to the site client for cross-site delivery. In some embodiments, step 430 may be performed by delivery module 230 .

[0085] In some embodiments, when the mini program to be delivered across sites and the site client for cross-site delivery pass the cross-site delivery capability authentication, the processing device 112 can send the information of the mini program that has passed the cross-site delivery capability authentication to the site terminal that has passed the cross-site delivery capability authentication, and the site terminal can run the mini program on its client. In some embodiments, the information of the mini program may include, but is not limited to, a combination of one or more of the attribute information of the mini program, the qualification information of the user, the security protocol of the mini program, the mini program delivery capability authentication information, the URL information of the mini program, etc. In some embodiments, the processing device 112 can obtain the information of the mini program from the mini program developer. In some embodiments, the processing device 112 can obtain the information of the mini program from the database 140. In some embodiments, when the mini program to be delivered across sites and the site client for cross-site delivery pass the cross-site delivery capability authentication, the processing device 112 can directly run the mini program to be delivered across sites on one or more site clients based on the cross-site delivery request of the mini program after obtaining site authorization.

[0086] Step 440 , sending the site client that has passed the cross-site delivery capability certification to the terminal device so that the terminal device can perform a real machine test on it. In some embodiments, step 440 can be performed by the test module 240 .

[0087] In some embodiments, the processing device 112 can send the site client for cross-site delivery to at least one terminal device when it passes the cross-site delivery capability authentication, so that the at least one terminal device can perform real machine testing on the site client for cross-site delivery. Real machine testing refers to running the client on the user's terminal device. For example, the user can download and install the corresponding site client through the terminal device 130 to test the relevant functions of the site client on the terminal device 130. In some embodiments, real machine testing may include remote real machine testing and local real machine testing. Local real machine testing can be performed on real machine testing through local electronic devices. For example, local mobile phones, tablet computers, computers and other real machines. Remote real machine testing can be performed on real machine testing through network 150 connection. For example, the user does not need a local electronic device, does not use a simulator, but uses the network to remotely access the real machine and perform remote testing on the real machine.

[0088] In some embodiments, the processing device 112 may send the mini program to be delivered across sites to at least one terminal device (e.g., terminal device 130) for real machine testing when the mini program to be delivered across sites passes the delivery capability certification. In some embodiments, the processing device 112 may send both the mini program to be delivered across sites and the site client for cross-site delivery to at least one terminal device for real machine testing when both pass the cross-site delivery capability certification. By performing real machine testing on the mini program and / or site client, it can be ensured that the mini program and / or site client run normally on the user's terminal device to execute the functions of the mini program and / or site client.

[0089] It should be noted that the above description of process 400 is only for example and explanation, and does not limit the scope of application of this specification. For those skilled in the art, various modifications and changes can be made to process 400 under the guidance of this specification. However, these modifications and changes are still within the scope of this specification. For example, in step 420, the data of the site client can be obtained from the site terminal in order to authenticate its ability to be delivered across sites. For another example, in step 430, when the mini program to be delivered across sites is delivered to the site client for cross-site delivery, the site client can detect the security, risk level, etc. of the mini program.

[0090] Figure 5 It is an exemplary flowchart of the method for cross-site delivery of mini-programs shown in some embodiments of this specification.

[0091] In some embodiments, a site with a demand for delivery can perform a capability test on its client before placing the client on the mini-program cross-site delivery platform. If the test is qualified, the site client can be placed on the mini-program cross-site delivery platform to deliver the mini-program on the client. Figure 5As shown, the mini-program cross-site delivery method 500 can be applied to a site terminal, which can be implemented by a processing device 122 (eg, the second server 120 ) or a mini-program cross-site delivery system 300 .

[0092] Step 510 , obtaining the capability standard of the mini program cross-site delivery. In some embodiments, step 510 may be performed by the second acquisition module 310 .

[0093] In some embodiments, the processing device 122 can determine the capability standard for cross-site delivery of the mini-program based on user needs. For example, data such as user feedback on the mini-program functions and the demand for mini-program functional characteristics can be obtained to determine the capability standard for cross-site delivery of the mini-program. In some embodiments, the processing device 122 can determine the capability standard for cross-site delivery of the mini-program based on the capabilities of the mini-program delivered across sites. For example, if the API function version of the mini-program is version 2.1, it can be determined that the capability standard for cross-site delivery of the mini-program is that the API function version is version 2.1. In some alternative embodiments, the capability standard for cross-site delivery of mini-programs may include but is not limited to security standards, delivery protocols, etc., and this specification does not limit this.

[0094] Step 520 , based on the capability standard of mini-program cross-site delivery, generate a mini-program that meets the capability standard of mini-program cross-site delivery, and run the mini-program on the site client. In some embodiments, step 520 may be performed by the running module 320 .

[0095] In some embodiments, the processing device 122 can write a mini program with the capability standard of mini program cross-site delivery based on the capability standard of mini program cross-site delivery. The processing device 122 can run the generated mini program in full on the client to determine whether the client has the ability to execute the mini program. For example, whether the number of APIs on the client matches the number of APIs on the generated mini program.

[0096] Step 530 , based on the operation result, determine whether the site client has the ability to be delivered across sites. In some embodiments, step 530 may be performed by the determination module 330 .

[0097] In some embodiments, the operation results may include program errors, successful program operation, successful function implementation, unachievable function, data errors, etc. Program errors may include language program errors in the code itself. Successful program operation may mean that the code can run safely and stably. Function implementation may include normal or abnormal execution of the service functions of the mini-program, etc. Data errors may include page display errors that occur when the client runs the mini-program, the inability to jump to the page, etc. Based on the results of the mini-program running on the client with the ability standard of mini-program cross-site delivery, it can be judged whether the site client has the ability to be delivered across sites. In some embodiments, the processing device 122 can adjust the data of the client to match the ability of the mini-program when the mini-program cannot run successfully on the client or there is an operation error. When the mini-program can run successfully on the client, it is considered that the client has the ability to be delivered across sites.

[0098] Step 540 , when the site client has the ability to be delivered across sites, it is sent to the mini program cross-site delivery platform so as to be delivered across sites by the mini program. In some embodiments, step 540 may be performed by the sending module 340 .

[0099] In some embodiments, when the site client has the ability to be delivered across sites, the processing device 122 can send it to the mini-program cross-site delivery platform (for example, the first server 110), that is, enter the mini-program cross-site delivery platform, so that the mini-program cross-site delivery platform can deliver the mini-program to the site client.

[0100] It should be noted that the above description of method 500 is only for example and explanation, and does not limit the scope of application of this specification. For those skilled in the art, various modifications and changes can be made to method 500 under the guidance of this specification. However, these modifications and changes are still within the scope of this specification. For example, in step 510, the capability standard of cross-site delivery of mini-programs can be obtained from the mini-program cross-site delivery platform. For another example, in step 540, it is sent to the mini-program cross-site delivery platform, and the mini-program cross-site delivery platform can detect the site client based on security protocols, platform service protocols, etc. to determine whether it meets the platform requirements.

[0101] The beneficial effects that may be brought about by the embodiments of this specification include but are not limited to: (1) Before the mini-program is delivered, the delivery capability of the mini-program to be delivered and the delivery client are authenticated to ensure the capability matching between the mini-program and the delivery client; (2) By matching the capability standards of the mini-program to be delivered, the site client to be delivered, and the mini-program cross-site delivery, the delivery capability alignment can be guaranteed to ensure the quality of the mini-program cross-site delivery; (3) Before the site client enters the mini-program cross-site delivery platform, the capability of the delivered party (site client) is checked in advance to increase the online speed. It should be noted that different embodiments may produce different beneficial effects. In different embodiments, the beneficial effects that may be produced may be any one or a combination of the above, or any other possible beneficial effects.

[0102] The basic concepts have been described above. Obviously, for those skilled in the art, the above detailed disclosure is only for example and does not constitute a limitation on the embodiments of this specification. Although not explicitly stated here, those skilled in the art may make various modifications, improvements and corrections to the embodiments of this specification. Such modifications, improvements and corrections are suggested in the embodiments of this specification, so such modifications, improvements and corrections still belong to the spirit and scope of the exemplary embodiments of this specification.

[0103] At the same time, this specification uses specific words to describe the embodiments of this specification. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures or characteristics in one or more embodiments of this specification can be appropriately combined.

[0104] In addition, it will be appreciated by those skilled in the art that the various aspects of the embodiments of this specification may be illustrated and described by a number of patentable categories or situations, including any new and useful process, machine, product or combination of substances, or any new and useful improvements thereto. Accordingly, the various aspects of the embodiments of this specification may be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software may all be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". In addition, the various aspects of the embodiments of this specification may be represented as a computer product located in one or more computer-readable media, the product including computer-readable program code.

[0105] A computer storage medium may include a propagated data signal containing computer program code, for example, in baseband or as part of a carrier wave. The propagated signal may be in a variety of forms, including electromagnetic, optical, etc., or a suitable combination. A computer storage medium may be any computer-readable medium other than a computer-readable storage medium, which can be connected to an instruction execution system, device or apparatus to communicate, propagate or transmit the program for use. The program code on the computer storage medium may be transmitted via any suitable medium, including radio, cable, fiber optic cable, RF, or similar media, or any combination of the above media.

[0106] The computer program coding required for the operation of each part of the embodiment of this specification can be written in any one or more programming languages, including object-oriented programming languages ​​such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python, etc., conventional procedural programming languages ​​such as C language, VisualBasic, Fortran2003, Perl, COBOL2002, PHP, ABAP, dynamic programming languages ​​such as Python, Ruby and Groovy, or other programming languages, etc. The program coding can be run completely on the user's computer, or run on the user's computer as an independent software package, or partly run on the user's computer and partly run on the remote computer, or run completely on the remote computer or processing equipment. In the latter case, the remote computer can be connected to the user's computer by any network form, such as a local area network (LAN) or a wide area network (WAN), or connected to an external computer (e.g., by the Internet), or in a cloud computing environment, or used as a service such as software as a service (SaaS).

[0107] In addition, unless explicitly stated in the claims, the order of the processing elements and sequences described in the embodiments of this specification, the use of alphanumeric characters, or the use of other names are not intended to limit the order of the processes and methods of the embodiments of this specification. Although the above disclosure discusses some invention embodiments that are currently considered useful through various examples, it should be understood that such details are only for illustrative purposes, and the attached claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that are consistent with the essence and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing processing device or mobile device.

[0108] Similarly, it should be noted that in order to simplify the description of the embodiments disclosed in this specification, thereby helping to understand one or more embodiments of the invention, in the above description of the embodiments of this specification, multiple features are sometimes combined into one embodiment, figure or description thereof. However, this disclosure method does not mean that the features required by the objects of the embodiments of this specification are more than the features mentioned in the claims. In fact, the features of the embodiments are less than all the features of the single embodiment disclosed above.

[0109] Each patent, patent application, patent application publication, and other materials, such as articles, books, specifications, publications, documents, etc., cited in this specification are hereby incorporated by reference in their entirety. Except for application history documents that are inconsistent with or conflicting with the contents of this specification, documents that limit the broadest scope of the claims of this specification (currently or later attached to this specification) are also excluded. It should be noted that if the descriptions, definitions, and / or use of terms in the materials attached to this specification are inconsistent or conflicting with the contents described in this specification, the descriptions, definitions, and / or use of terms in this specification shall prevail.

[0110] Finally, it should be understood that the embodiments described in this specification are only used to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of the embodiments of this specification. Therefore, as an example and not a limitation, alternative configurations of the embodiments of this specification may be considered consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly introduced and described in this specification.

Claims

1. A method for delivering mini-programs across sites, applied to a mini-programs across site delivery platform, wherein a site client stationed in the mini-programs across site delivery platform has passed delivery capability certification, wherein the delivery capability certification is achieved by running a mini-program that meets the mini-programs across site delivery capability standards on the site client, and the method comprises: Obtaining a mini-program cross-site delivery request through the mini-program cross-site delivery platform, wherein the delivery request includes the mini-program to be delivered across sites and at least two site clients for the cross-site delivery; Based on the delivery request, cross-site delivery capability authentication is performed on the mini program to be delivered across sites and the site client of the cross-site delivery, including: Obtaining the capability standard of the mini program cross-site delivery, and determining whether the capability of the site client for the cross-site delivery meets the capability standard of the mini program cross-site delivery; When the capability standard of the mini program cross-site delivery is met, determining whether the capabilities of the mini program to be cross-site delivered and the site client of the cross-site delivery match; When the two match, it is determined that the mini program to be delivered across sites and the site client for the cross-site delivery have both passed the cross-site delivery capability certification; The capability standards for the mini program to be delivered across sites include the number, functions, and protocol consistency of the mini program application programming interfaces; When the mini-program to be delivered across sites and the site client for the cross-site delivery both pass the cross-site delivery capability authentication, the mini-program to be delivered across sites is delivered to the site client for the cross-site delivery.

2. The method according to claim 1, further comprising: When the capability of the site client for cross-site delivery does not meet the capability standard of the mini-program cross-site delivery, the site client for cross-site delivery is returned to its corresponding site so that the site can update the client.

3. The method according to claim 1, further comprising: When the capabilities of the mini program to be cross-site delivered do not match those of the site client for cross-site delivery, the site client for cross-site delivery and the judgment result are returned to the corresponding site so that the site can update the client; as well as The capability standard for cross-site delivery of the mini-program is updated according to the judgment result, and the updated capability standard for cross-site delivery of the mini-program is stored in a database.

4. The method according to claim 1, further comprising: When the site client for cross-site delivery passes the cross-site delivery capability authentication, it is sent to at least one terminal device so that the at least one terminal device performs a real machine test on the site client for cross-site delivery.

5. The method according to claim 1, further comprising: When the version of the site client for cross-site delivery is updated, the cross-site delivery capability authentication is performed on the updated site client for cross-site delivery.

6. According to the method of claim 1, the specific process of performing the delivery capability authentication on the site client before entering the mini program cross-site delivery platform comprises: Obtain the capability standard for cross-site delivery of the Mini Program; Based on the capability standard of the mini program cross-site delivery, generate a mini program that meets the capability standard of the mini program cross-site delivery, and run the mini program on the site client before entry; Based on the operation result, determining whether the site client before entry has the ability to be delivered across sites; When the site client before entry has the ability to be delivered across sites, it is allowed to enter the mini-program cross-site delivery platform.

7. A mini program cross-site delivery system, applied to a mini program cross-site delivery platform, wherein a site client stationed in the mini program cross-site delivery platform has passed the delivery capability certification, and the delivery capability certification is achieved by running a mini program with the mini program cross-site delivery capability standard on the site client, and the system comprises: A first acquisition module is used to acquire a cross-site delivery request of a mini program, wherein the delivery request includes a mini program to be delivered across sites and at least two site clients for the cross-site delivery; The first capability authentication module is used to perform cross-site delivery capability authentication on the mini program to be delivered across sites and the site client of the cross-site delivery based on the delivery request, including: Obtaining the capability standard of the mini program cross-site delivery, and determining whether the capability of the site client for the cross-site delivery meets the capability standard of the mini program cross-site delivery; When the capability standard of the mini program cross-site delivery is met, determining whether the capabilities of the mini program to be cross-site delivered and the site client of the cross-site delivery match; When the two match, it is determined that the mini program to be delivered across sites and the site client for the cross-site delivery have both passed the cross-site delivery capability certification; The capability standards for the mini program to be delivered across sites include the number, functions, and protocol consistency of the mini program application programming interfaces; The delivery module is used to deliver the mini program to be delivered across sites to the site client for cross-site delivery when both the mini program to be delivered across sites and the site client for cross-site delivery pass the cross-site delivery capability authentication.

8. The system according to claim 7, wherein the first capability authentication module is used for: When the capability of the site client for cross-site delivery does not meet the capability standard of the mini-program cross-site delivery, the site client for cross-site delivery is returned to its corresponding site so that the site can update the client.

9. The system according to claim 7, wherein the first capability authentication module is used for: When the capabilities of the mini program to be cross-site delivered do not match those of the site client for cross-site delivery, returning the site client for cross-site delivery and the judgment result to its corresponding site so that the site can update the client; and The capability standard for cross-site delivery of the mini-program is updated according to the judgment result, and the updated capability standard for cross-site delivery of the mini-program is stored in a database.

10. The system according to claim 7, further comprising a testing module, wherein the testing module is configured to: When the site client for cross-site delivery passes the cross-site delivery capability authentication, it is sent to at least one terminal device so that the at least one terminal device performs a real machine test on the site client for cross-site delivery.

11. The system according to claim 7, wherein the first capability authentication module is further configured to: When the version of the site client for cross-site delivery is updated, the cross-site delivery capability authentication is performed on the updated site client for cross-site delivery.

12. The system according to claim 7, further comprising a second capability authentication module, the second capability authentication module being used to: before the site client of the cross-site delivery is settled in the mini-program cross-site delivery platform, perform delivery capability authentication on the site client before settling in; The process of authenticating the deployed capability includes: Obtain the capability standard for cross-site delivery of the Mini Program; Based on the capability standard of the mini program for cross-site delivery, generate a mini program that meets the capability standard of the mini program for cross-site delivery, and run the mini program on the site client before entry; Based on the operation result, determining whether the site client before entry has the ability to be delivered across sites; When the site client before entry has the ability to be delivered across sites, it is allowed to enter the mini-program cross-site delivery platform.

13. A computer-readable storage medium, wherein the storage medium stores computer instructions, and when a computer reads the computer instructions in the storage medium, the computer executes the method according to any one of claims 1 to 6.

Images