WO2016061762A1 - 移动终端软件的多渠道sdk接入系统及方法 - Google Patents

移动终端软件的多渠道sdk接入系统及方法 Download PDF

Info

Publication number
WO2016061762A1
WO2016061762A1 PCT/CN2014/089165 CN2014089165W WO2016061762A1 WO 2016061762 A1 WO2016061762 A1 WO 2016061762A1 CN 2014089165 W CN2014089165 W CN 2014089165W WO 2016061762 A1 WO2016061762 A1 WO 2016061762A1
Authority
WO
WIPO (PCT)
Prior art keywords
channel
sdk
file
apk
module
Prior art date
Application number
PCT/CN2014/089165
Other languages
English (en)
French (fr)
Inventor
刘大澎
孙智勇
Original Assignee
刘大澎
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 刘大澎 filed Critical 刘大澎
Priority to PCT/CN2014/089165 priority Critical patent/WO2016061762A1/zh
Publication of WO2016061762A1 publication Critical patent/WO2016061762A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present invention relates to an SDK access system, and more particularly to a system and method for multi-channel SDK access of a mobile terminal software.
  • the SDK the Software Development Kit
  • the SDK is a collection of development tools used by software engineers to build application software for specific software packages, software frameworks, hardware platforms, operating systems, and the like.
  • content developers can develop corresponding mobile terminal programs based on the SDK provided by the channel and upload them to the channel for promotion and distribution.
  • a mobile terminal application based on a mobile operating system (such as Android system) (for example, in the form of an APK file format application)
  • a mobile operating system such as Android system
  • APK file format application for example, in the form of an APK file format application
  • Channel vendors often work with content developers to embed user account systems, payment systems, ad systems, and more in the APK source file to enable revenue sharing between channel providers and content developers.
  • the channel provider will release its own SDK library for content developers to download and use.
  • Content developers need to modify their APK files according to the channel's SDK library to meet the channel's customization requirements.
  • the object of the present invention is to provide a multi-channel SDK access system, which includes a central console, a universal SDK, a CP interface module, a third-party SDK, a channel interface module, a channel parameter configuration, a file packaging module, and a file management system.
  • a module wherein the central console is configured to schedule and control other modules; the universal SDK is configured to store SDKs common to different multiple channels, which encapsulates the same as third-party SDKs provided by all channels.
  • the client interface is connected to the server; the CP interface module provides an interface for the at least one CP to access the system, and is used for the CP to download or upload a file or configure the file; the third-party SDK is used for storing a respective SDK provided by different channels; the channel interface module provides an interface for at least one channel provider to access the system, is used to obtain SDKs of different channels, and configures and files through the channel parameters
  • the file generated by the packaging module is uploaded to each of the corresponding channels; the channel parameter configuration and the file packaging module are configured to receive the configuration provided by the CP,
  • the program developed by the CP based on the universal SDK is configured and packaged to be able to access different channels; the file management module is used for storage and management in the system operation. And the transmission of various types of files.
  • the multi-channel SDK access system according to the present invention can help developers reduce the workload and maintenance of SDKs accessing different channels, and can realize multi-channel development and management on one platform.
  • FIG. 1 is a block diagram schematically showing an architecture of a multi-channel SDK access system according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart showing a channel parameter configuration and an SDK packing according to an embodiment of the present invention
  • FIG. 3 is a flow chart schematically showing an inspection update function according to an embodiment of the present invention.
  • FIG. 4 is a flow chart showing the interaction between a CP end, a general purpose SDK server, and a third party SDK server according to an embodiment of the present invention
  • FIG. 5(a) is a schematic diagram showing a user login verification interaction flowchart according to an embodiment of the present invention.
  • FIG. 5(b) schematically shows a flow chart of user refill interaction according to an embodiment of the present invention.
  • FIG. 1 is a schematic block diagram showing a system architecture of a mobile terminal software multi-channel SDK access system according to an embodiment of the present invention.
  • module refers to computer program logic and/or data used to provide a particular function. Modules can be implemented in hardware or in firmware and/or software. In order to clarify and highlight the gist of the present invention, some conventional components such as a network interface, a security mechanism, a load balancer, and the like are not shown in FIG.
  • the mobile terminal software multi-channel SDK access system 100 interacts with at least one content provider (CP), such as CP_1, CP_2, ..., CP_m, through a network, and communicates with at least one channel through the network, for example, A channel, a second channel, ..., the nth channel to interact.
  • the network is a communication path between the multi-channel SDK access system 100, content providers, and channels.
  • the content provider provides content that contains specific content A software product that is accessed or distributed by a multi-channel SDK access system 100 in accordance with the present invention.
  • the specific content includes, but is not limited to, games, application software, tool software, educational software, and the like.
  • the network is the Internet.
  • the network can be any communication path such as a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a mobile wired or wireless network, a private network, or a virtual private network.
  • LAN local area network
  • MAN metropolitan area network
  • WAN wide area network
  • mobile wired or wireless network a private network
  • private network or a virtual private network.
  • the network uses standard communication techniques and/or protocols.
  • protocols used on the network include: Transmission Control Protocol/Internet Protocol (TCP/IP), Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), and the like.
  • Techniques and/or formats available for data exchanged over the network include Hypertext Markup Language (HTML), Extensible Markup Language (XML), and the like.
  • data may also be transmitted over a network using a customized and/or dedicated, and/or encrypted data communication technology over a network.
  • the system 100 of the present invention includes a central console 101, a universal SDK 102, a CP interface module 103, a third party SDK 104, a channel interface module 105, a channel parameter configuration and file packaging module 106, a file management module 107, and a CP statistics and management module 108. And check the update module 109.
  • the central console 101 is a central control terminal for scheduling and controlling other various modules, preferably in a web interface.
  • the central console 101 contains entries for various other functional modules.
  • a generic SDK 102 for storing the system 100 of the present invention provides SDKs that are common to different multiple channels.
  • the Generic SDK 102 encapsulates the same client interface and server interface as the third-party SDK 104 provided by all channels, in the form of a downloadable software development kit.
  • the CP downloads the universal SDK 102 from the system 100 through the CP interface module 103, debugs and verifies the APK or Android project file developed by the CP, and finally accesses the third-party SDK 104 by using the universal SDK 102.
  • the project file here is the intermediate version of the file during the Android program development process.
  • the CP interface module 103 provides an interface for the at least one CP to access the system 100 for the CP to download or upload files or configure the files.
  • the CP downloads the universal SDK 102 through the CP interface module 103, and the CP accesses the APK or Android project file developed by the CP to the universal SDK 102, accesses the debugging and verification until the correct access, and forms a general-purpose The APK 102 or Android project file of the SDK 102, and finally the APK or Android project file based on the generic SDK 102 is uploaded to the system 100 of the present invention through the CP interface module 103.
  • the third-party SDK 104 integrates SDKs dedicated to certain function channels, such as user login, recharge channels, community functions, social sharing, and data background statistics.
  • the third party SDK 104 of different channels is packaged into the universal SDK 102 by configuration.
  • the CP For the specific functions of the third-party SDK 104, the CP must embed it into its own APK or Android project file, so that the channel provider will allow the CP to publish its product to the channel platform of the channel and finally go online.
  • the channel interface module 105 provides an interface for the at least one channel provider to access the system 100, and is used to obtain the SDKs of different channels, and the APKs configured by the channel parameter configuration and the file packaging module 106 are packaged and generated for downloading by the user. Upload to the respective different channels.
  • the channel parameter configuration and file packaging module 106 is configured to receive the configuration provided by the CP, and configure and package the APK program based on the universal SDK 102 or the Android project file according to the configuration of the CP and the requirements of the third-party SDK, to access In different channels.
  • the CP uploads its APK or Android project file developed based on the universal SDK
  • the CP interface module 103 of the system performs configuration of relevant parameters (for example, filling in private keys of different channels), and then these parameters and project files are in the channel parameters.
  • the configuration and file packaging module 106 performs packaging, and finally generates respective APK files that are applied to different channels.
  • the APK is also tested. After the test is passed, it is submitted to different channels through the channel interface module 105. After the channel check is passed, the channel can be officially launched for distribution.
  • the specific channel parameter configuration and packing algorithm will be described later with reference to FIG. 2.
  • the file management module 107 is configured to store and manage various types of files generated and transmitted in the system 100, including but not limited to the different versions of the common SDK files, third-party SDK files, CP developed APK or Android project described above. Files and packaged APK files, etc.
  • the CP statistics and management module 108 is configured for the CP to count the operation of the program products connected to each channel, and manage the operation of different versions of the products on different channels.
  • system 100 may further include an inspection update module 109, The version management function for providing different APKs for the CP, and checking the update of the version of the APK file uploaded by the CP for accessing the channel.
  • the CP may update the version (such as modifying bugs, adding new functions, etc.) to the system 100 frequently.
  • the check update module 109 checks whether the CP has provided the updated version each time the terminal user allows the program.
  • the check update module 109 also provides the terminal user with the function of incremental update.
  • the incremental update feature allows users to upload or download larger files using smaller network traffic.
  • the check update module 109 generates a unique identifier for each version of the APK file uploaded to the distributor to distinguish between different versions.
  • FIG. 2 is a flow chart schematically showing channel parameter configuration and file packing module 106 performing channel parameter configuration and SDK packaging according to an embodiment of the present invention. As shown in Figure 2, taking a channel as an example, the specific steps are as follows:
  • Step 210 Acquire an APK file developed by the CP based on the universal SDK, and unpack the APK file to generate a CP temporary file.
  • the CP may upload an APK file developed based on the universal SDK through the CP interface module and store it in the file management module.
  • Step 220 Acquire a channel selected by the CP to be published, and apply configuration information of the APK file to the channel;
  • the configuration information includes, but is not limited to, configuration information related to channel payment, Debug mode configuration, landscape configuration, update configuration, user account settings, and the like.
  • Step 230 Obtain an SDK file of the channel, generate a project SDK development project file based on the SDK file, and then generate a channel APK package for the project file;
  • the SDK file for obtaining the channel may be obtained by the third-party SDK 104 or directly obtained from the channel by the channel interface module 105.
  • Step 240 Unpack the channel APK package to generate a system SDK temporary file.
  • Step 250 adding the configuration information acquired in step 220 to the SDK temporary file generated in step 240;
  • the addition of the configuration information may be to replace the configuration information.
  • the original configuration information in the SDK temporary file can also add information items that are not originally in the SDK temporary file.
  • Step 260 Combine the system SDK temporary file that has updated the configuration information with the CP temporary file generated in step 210, and generate a channel APK temporary file corresponding to the channel;
  • Step 270 packaging the channel APK temporary file to generate a channel APK package
  • step 280 the channel APK package is signed to generate a signed channel APK package.
  • the signed channel APK package can be directly uploaded to the corresponding channel for publishing.
  • the rules of the signature may be obtained in the configuration information in step 220.
  • FIG. 2 is only a schematic diagram showing the flow of channel parameter configuration and packaging for one channel.
  • the method flow of FIG. 2 can be synchronized for each channel.
  • FIG. 3 is a flow chart schematically showing a function of checking and updating a file version by the check update module 109 according to an embodiment of the present invention, and the specific steps are as follows:
  • Step 310 Obtain an APK file version identifier (ChecksumA) sent by the terminal user.
  • the APK file obtained by the end user through the channel provider carries a version identifier added to the APK file by the check update module 109, the version identifier being used to uniquely identify the version of the APK file.
  • Step 320 Compare the obtained APK file version identifier with the latest APK file version identifier (ChecksumB) existing in the system 100. If the same, the terminal user installs the latest version, and the method ends; if different Go to step 330;
  • Step 330 Determine whether a request for consent update sent by the terminal user is received, and if yes, proceed to step 340; otherwise, the method ends;
  • Step 340 Generate a difference file patch between the obtained version of the APK file and the latest APK file version, and add a unique identifier (ChecksumPatch) to the difference file.
  • ChecksumPatch a unique identifier
  • Step 350 Acquire an address of the difference file and send it to the terminal user, and at the same time The new APK file version identifier (ChecksumB) is sent to the end user.
  • ChecksumB The new APK file version identifier
  • Step 360 The terminal user accesses the address of the difference file, the client starts the downloading process, downloads the difference file and installs, and then records the latest APK file version identifier (ChecksumB) received.
  • the latest version APK file is synthesized with the original version APK in the client, and the client launches the application installation program, prompting the installation to complete.
  • the latest APK file version identifier (ChecksumB) received is recorded in the installed version as an identifier for the version.
  • FIG. 4 shows a flow diagram of the interaction between the CP end 401, the multi-channel SDK access system 402 (i.e., the system 100 in FIG. 1) and the channel provider 403.
  • FIG. 4 only schematically illustrates the interaction between a CP end 401 and a channel provider 403 through the multi-channel SDK access system 402. It can be understood that the interaction method is suitable for interaction between multiple CPs and multiple channels.
  • the multi-channel SDK access system 402 acquires third-party SDKs 104 of different channels (step 405) and stores them in the multi-channel SDK access system 402.
  • the CP terminal 401 sends a request universal SDK to the server 402 (step 410), and the server 402 presents the generic SDK 102 (step 415) and is used for downloading by the CP 401 (step 420).
  • the CP end 401 accesses the APK developed by the CP to the downloaded universal SDK 102, debugs and verifies the access to the correct access, and forms an APK based on the universal SDK 102, and finally uploads the APK based on the universal SDK 102 to the multi-channel SDK.
  • Access system 402 (step 425).
  • the CP side selects the channel and performs parameter configuration.
  • the channel and the configured parameters are sent to the universal multi-channel SDK access system 402 (step 430).
  • the multi-channel SDK access system 402 packs the APK developed by the CP into a channel APK according to the channel selected by the CP and the configured parameters (step 435).
  • the CP may download the packaged channel APK (step 440) and perform a related test (step 445). If the test finds it needs to be modified
  • the APK file returns to step 425, and steps 425-440 are repeated to repackage.
  • the CP issues an instruction to upload to the channel (step 450), and the multi-channel SDK access system 402 receives the command and uploads the tested APK to the corresponding channel (step 455).
  • the terminal user can download the corresponding APK file from various channels and install and use the terminal device (for example, a smart phone or a tablet). .
  • the system according to the present invention can further manage and collect the use of subsequent end users, so as to facilitate the CP to better implement the multi-channel APK management of one platform. Management and statistical data can also be provided to the CP via the CP Statistics and Management Module 108.
  • FIG. 5(a) and 5(b) respectively show two examples of interactions with the system 100 when an end user uses a program generated by the multi-channel SDK access system 100 in accordance with the present invention.
  • FIG. 5(a) shows an interaction flow chart of terminal user login verification
  • FIG. 5(b) shows an interaction flow chart of end user payment verification.
  • the terminal user can download the corresponding program. After downloading, the terminal user runs the corresponding program to perform a series of operations, such as a game program, a game, a tool program, a related function, a social program, and the like.
  • the nodes of the interaction process between the end user and the system 00 include an end user client 501, a universal SDK client 502, a channel SDK client 503, a channel SDK server 505, and a terminal.
  • the terminal user client 501 is a program (for example, an APK file) generated by the multi-channel SDK access system 100 of the present invention that is downloaded, installed, and used by the terminal user through the client terminal device, and the client terminal device, such as a smart phone, A smart terminal with computing functions, such as a tablet or a computer.
  • the universal SDK client 502 is embedded in the final program, that is, the client embedded in the end user client 501, in the form of a generic SDK when the CP accesses the multi-channel SDK access system 100 of the present invention.
  • the channel SDK client 503 is an interface for enabling an end user to access a third party channel. Preferably, it is presented in the form of a user interaction interface of the client terminal device of the end user. When the user logs in, the interface presented by the channel SDK client 503 can provide the terminal user with the functions of inputting the user name, password, and additional information. .
  • Channel SDK client 503 then sends the information to the channel SDK server 505 for login authentication and authorization operations.
  • the terminal program server 504 is a server that provides a series of services for the end user client 501 program, such as a game server, a social forum server, and the like.
  • Figure 5(a) shows an interactive flow diagram for user login verification.
  • channel registration verification is first performed, that is, login to the channel server that distributes the terminal program.
  • the user launches a program of the end user client 501, such as game or utility software, and the end user client 501 issues a request to invoke the login to the universal SDK client 502 (step 506), thereby forwarding the request to the channel SDK via the generic SDK client 502.
  • the client 503 requests to invoke the channel login (step 508).
  • the terminal user client 501 requests the server 505 of the login channel SDK according to the channel login information (such as the username and password, the channel identifier, and the like) sent by the request (step 510).
  • the channel login information such as the username and password, the channel identifier, and the like
  • the channel SDK server 505 performs verification to verify whether the client 501 of the end user is a terminal program that is legally downloaded through the channel server, and to verify the information of the client user.
  • a prompt is returned to the channel SDK client 503 for successful login (step 514), and the user UID identifier is returned to the universal SDK client 502 (step 516); the universal SDK client 502 then identifies the user UID and The channel identifier is returned to the end user client 501 (step 518), and the login verification process of the channel SDK server is completed.
  • the channel SDK server is used to log in the successfully obtained information (user UID, channel identifier, etc.), and the terminal program server is verified for login.
  • the end user client 501 requests the login terminal program server 504 using the user UID identification and the channel identification to obtain the user's information (step 520); and then authenticates the login to the multi-channel SDK access system 100 (step 522).
  • the multi-channel SDK access system 100 performs verification.
  • the user information is sent by the multi-channel SDK access system 100 to the channel SDK server 505 for verification (step 526).
  • verification of the user identity is performed by the channel SDK server 505.
  • the user who is operating the multi-channel SDK access system 100 is notified that the user is a valid user (step 530); then, the multi-channel SDK access system 100 notifies the terminal program server 504 that the user being operated is a valid user ( Step 532), thereby returning information to the end user client 501 that the user successfully logged in (step 534), completing the login verification.
  • channel SDK server Through the above end users, channel SDK server, terminal program server and multiple channels
  • the interaction verification between the SDK access systems can ensure the accuracy and security of the user information, so that the programs downloaded by the end users through different channels can be correctly verified and used, which ensures the interests of the channel provider and the CP.
  • Figure 5(b) shows an interactive flow diagram of user refill.
  • the multi-channel SDK access system and the channel SDK of the present invention are required.
  • the server and the terminal program server work together to ensure the security and reliability of the user's recharge.
  • the refill operation can be initiated. Specifically, the user's refill request first initiates a call refill request to the universal SDK client 502 (step 550).
  • the generic SDK client 502 initiates a request to the multi-channel SDK access system 100, creates an order with callback information, and submits it to the multi-channel SDK access system 100 (step 552).
  • Callback information can be responsive based on the occurrence of a particular event or condition, such as a result notification of a refill.
  • the multi-channel SDK access system 402 creates an order with callback information, it returns an order ID and other relevant information to the generic SDK client 502 (step 554).
  • the SDK client 502 uses the returned order ID to request the channel SDK client 503 to initiate a refill request, requesting payment of the order ID (step 556), and the channel SDK client sends the refill request to the channel SDK server 505 (step 558).
  • the channel SDK server 505 verifies whether the refill is successful. If the recharge is successful, the recharge prompt is returned to the universal SDK client 502 (step 560), and the universal SDK client 502 returns the recharge prompt to the end user.
  • Client 501
  • the user's recharge behavior usually needs to be divided into the channel SDK server and the server end of the terminal program, that is, the channel provider and the CP are jointly divided into recharges, therefore, the user recharge information needs to be provided to the user.
  • Terminal program server 504. As shown in FIG. 5(b), after the channel SDK server 505 verifies that the refilling is successful, the multi-channel SDK access system 100 is also notified of the successful refilling result (step 564). Preferably, the notification can be sent in an asynchronous communication manner.
  • the multi-channel SDK access system 402 After receiving the message of the refill result, the multi-channel SDK access system 402 sends a refill result notification with the callback information to the terminal program server 504 (step 566), and finally returns the notification of the recharge result to the terminal through the terminal program server 504.
  • the user client 501 (step 568) completes the user refill.
  • the multi-channel SDK access system 100 can also directly provide the configuration of the related application of the universal SDK access channel SDK by providing more functions for different channels and providing the API to the third-party SDK through the channel.
  • the CP may be required to provide its user identifier (usually a username or user ID) on the channel.
  • the CP needs to access the channel's oAuth authentication system through the system 100 of the present invention, log in and obtain its configuration information on the channel.
  • the system 100 of the present invention may further have a recommendation engine that recommends different channels to the CP based on the big data analysis of the statistical module or recommends a bidirectional recommendation mode of the CP to the channel.
  • the system automatically recommends channels to the CP.
  • the channel recommendation CP, the background providing CP of the system 100 of the present invention may choose to open the function of recommending its application to some or all of the channels.
  • the system 100 of the present invention automatically recommends the application of the CP to the channel through a set of algorithms based on the results of the CP development and the analysis results of the application and the channel.
  • the system 100 of the present invention can also deeply integrate with third-party service companies according to the needs of users and the needs of the industry chain, and provide the following related services to users: cloud services (including cloud data, cloud storage), application reinforcement, application statistics, Application testing, application push, advertising SDK, game engine plugin, payment SDK, etc.
  • cloud services including cloud data, cloud storage
  • application reinforcement including cloud data, cloud storage
  • application statistics including cloud data, cloud storage
  • Application testing application push
  • advertising SDK application push
  • advertising SDK game engine plugin
  • payment SDK etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明提供了一种移动终端软件多渠道SDK接入系统，所述系统包括中央控制台、通用SDK、CP接口模块、第三方SDK、渠道接口模块、渠道参数配置及文件打包模块和文件管理模块，其中通用SDK用于存储对于不同的多个渠道通用的SDK；CP接口模块为至少一个CP提供接入到系统的接口，用于CP下载或上传文件或进行配置；第三方SDK用于存储由不同的渠道商提供的各自的SDK；渠道接口模块为至少一个渠道商提供接入到系统的接口，用于获取不同渠道的SDK并将通过渠道参数配置及文件打包模块生成的文件上传至各个渠道；渠道参数配置及文件打包模块，用于接收CP提供的配置，并根据CP的配置和第三方SDK，将CP上传的基于通用SDK开发的程序进行配置与打包，以便接入到不同渠道中。

Description

移动终端软件的多渠道SDK接入系统及方法 技术领域
本发明涉及一种SDK接入系统，特别涉及一种移动终端软件多渠道SDK接入的系统及方法。
背景技术
SDK，即软件开发工具包(Software Development Kit)是指被软件工程师用于为特定的软件包、软件框架、硬件平台、操作系统等建立应用软件的开发工具的集合。在移动终端领域，内容开发者可以基于渠道商提供的SDK来开发相应的移动终端程序，并上传到渠道商进行推广和分发。
通常，内容开发者开发完一个基于移动操作系统(例如Android系统)的移动终端应用(例如以APK文件格式的应用程序形式)后，由于内容开发者个人的推广能力有限，因此需要接入到不同的渠道商进行推广。渠道商通常会与内容开发者合作，以便在APK源文件中嵌入用户账户系统、付费系统、广告系统等功能，从而实现渠道商与内容开发者的收益共享。为了实现上述嵌入功能，渠道商会发布自己的SDK库供内容开发者下载使用。内容开发者需要将自己的APK文件根据渠道商的SDK库进行修改，以便符合渠道商的定制化要求。
然而，内容开发者为了更好地推广自己的应用，通常会接入不同的渠道。而每个渠道都会发布自己独特的SDK库给开发者进行修改。因此，当开发者面对当前成百上千的渠道的SDK，开发者需要花费大量的人力物力将APK应用接入到不同的渠道的SDK，且接入到不同的渠道的SDK后会带来后续的维护问题。但是为了将APK应用更广泛的推送给用户，开发者不得不接入少则几个多则数十个的渠道的SDK。纷繁的渠道SDK接入过程耗时耗力，不仅会给内容开发者增加很多没有必要的成本，更可能延误APK应用的最佳上线时间，进而带来一定的损失。
因此，如何帮助开发者降低接入到不同渠道的SDK的工作量和维护量是当前亟需解决的问题。
发明内容
本发明的目的在于提供一种用于多渠道SDK接入系统，所述系统包括中央控制台、通用SDK、CP接口模块、第三方SDK、渠道接口模块、渠道参数配置及文件打包模块和文件管理模块，其中，所述中央控制台，用于调度和控制其他各个模块；所述通用SDK，用于存储对于不同的多个渠道通用的SDK，其封装了与所有渠道提供的第三方SDK同样的客户端接口与服务端接口；所述CP接口模块，为至少一个CP提供接入到所述系统的接口，用于CP下载或上传文件或对文件进行配置；所述第三方SDK，用于存储由不同的渠道商提供的各自的SDK；所述渠道接口模块，为至少一个渠道商提供接入到所述系统的接口，用于获取不同渠道的SDK，并将通过所述渠道参数配置及文件打包模块生成的文件上传至所述各个相应的渠道；所述渠道参数配置及文件打包模块，用于接收CP提供的配置，并根据CP的配置和第三方SDK，将CP上传的基于通用SDK开发的程序进行配置与打包，以便能够接入到不同渠道中；所述文件管理模块，用于存储和管理在系统运行中产生和传输的各类文件。
根据本发明的多渠道SDK接入系统可以帮助开发者降低接入到不同渠道的SDK的工作量和维护量，在一个平台上即可以实现多渠道的开发和管理。
应当理解，前述大体的描述和后续详尽的描述均为示例性说明和解释，并不应当用作对本发明所要求保护内容的限制。
附图说明
参考随附的附图，本发明更多的目的、功能和优点将通过本发明实施方式的如下描述得以阐明，其中：
图1示意性示出根据本发明实施方式的多渠道SDK接入系统的架构图；
图2示意性示出根据本发明实施方式的渠道参数配置及SDK打包流程图；
图3示意性示出根据本发明实施方式的检查更新功能的流程图；
图4示意性示出根据本发明实施方式的CP端、通用SDK服务器和第三方SDK服务器之间的交互流程图；
图5(a)示意性示出根据本发明实施方式的用户登录验证交互流程图；
图5(b)示意性示出根据本发明实施方式的用户充值交互流程图。
具体实施方式
通过参考示范性实施例，本发明的目的和功能以及用于实现这些目的和功能的方法将得以阐明。然而，本发明并不受限于以下所公开的示范性实施例；可以通过不同形式来对其加以实现。说明书的实质仅仅是帮助相关领域技术人员综合理解本发明的具体细节。
在下文中，将参考附图描述本发明的实施例。在附图中，相同的附图标记代表相同或类似的部件，或者相同或类似的步骤。
系统概述
图1示意性示出根据本发明实施方式的一种移动终端软件多渠道SDK接入系统的系统架构图。如本文所使用的，术语“模块”是指用于提供特定功能的计算机程序逻辑和/或数据。模块可以在硬件中实现，也可以在固件和/或软件中实现。为了明确和突出本发明的要点，例如网络接口、安全机制、负载均衡器等一些常规部件在图1中未示出。
此外，尽管实施例在这里描述了基于安卓(Android)系统的APK文件的SDK移动终端软件开发工具包，本领域普通技术人员将会认识到，本发明所描述的系统和架构功能可以适用于其它任何类型的软件开发平台和软件开发工具包。
根据本发明的移动终端软件多渠道SDK接入系统100分别通过网络与至少一个内容提供方(CP)，例如CP_1、CP_2、……、CP_m进行交互，并通过网络与至少一个渠道商，例如第一渠道商、第二渠道商、……、第n渠道商进行交互。该网络是在多渠道SDK接入系统100、内容提供方和渠道商之间的通信通路。内容提供方提供包含特定内容的 软件产品，所述软件产品需通过根据本发明的多渠道SDK接入系统100接入到渠道商进行分发或发行。所述特定内容包括但不限于游戏、应用软件、工具软件、教育软件等。
在一个实施例中，该网络是因特网。然而，该网络可以是任何通信路径，诸如局域网(LAN)，城域网(MAN)，广域网(WAN)，移动有线或无线网络、专用网络，或虚拟专用网络。
在一个实施例中，网络使用标准通信技术和/或协议。在网络上使用的协议的例子包括：传输控制协议/因特网协议(TCP/IP)，超文本传输协议(HTTP)，文件传输协议(FTP)等。通过网络交换的数据可利用的技术和/或格式包括超文本标记语言(HTML)，可扩展标记语言(XML)等。
在一些实施例中，除了上述技术和/或格式，数据也可以被通过网络使用定制和/或专用、和/或加密的数据通信技术通过网络进行传输。
本发明的系统100包括中央控制台101、通用SDK 102、CP接口模块103、第三方SDK 104、渠道接口模块105、渠道参数配置及文件打包模块106、文件管理模块107、CP统计与管理模块108和检查更新模块109。
中央控制台101，是用于调度和控制其他各个模块的中央控制端，优选地呈现方式为web界面。中央控制台101中包含了其他各个功能模块的入口。
通用SDK 102，用于存储为本发明的系统100提供对于不同的多个渠道通用的SDK。通用SDK 102封装了与所有渠道商提供的第三方SDK 104同样的客户端接口与服务端接口，以可下载的软件开发工具包的形式存在。CP通过CP接口模块103从系统100中下载该通用SDK102，对其开发的APK或Android工程文件进行调试、验证，并最终利用通用SDK 102接入到第三方SDK 104。这里的工程文件即在Android程序开发过程中中间版本的文件。
CP接口模块103，为至少一个CP提供接入到系统100的接口，用于CP下载或上传文件或对文件进行配置。CP通过CP接口模块103下载通用SDK 102，且CP将其开发的APK或Android工程文件接入到通用SDK 102，接入进行调试和验证直至正确接入，并形成基于通用 SDK 102的APK或Android工程文件，最后将基于通用SDK 102的APK或Android工程文件通过CP接口模块103上传到本发明的系统100。
第三方SDK 104，用于存储由不同的渠道商提供的各自的软件开发工具包。第三方SDK 104集成了一定功能渠道专用的SDK，例如用户登录、充值通道、社区功能、社交分享、数据后台统计等功能。不同渠道的第三方SDK 104通过配置均封装到通用SDK 102中。
对于第三方SDK 104的特定功能，CP必须将其植入到自己的APK或Android工程文件中，只有这样渠道商才会允许CP将其产品发布到渠道商的平台上并最终实现上线。
渠道接口模块105，为至少一个渠道商提供接入到系统100的接口，用于获取不同渠道的SDK，并将通过渠道参数配置与文件打包模块106处理后并打包生成的供用户下载使用的APK上传至相应的各个不同渠道。
渠道参数配置与文件打包模块106，用于接收CP提供的配置，并根据CP的配置和第三方SDK的要求，将基于通用SDK 102的APK程序或Android工程文件进行配置与打包，以接入到不同渠道中。CP在上传了其基于通用SDK开发的APK或Android工程文件后，通过本系统的CP接口模块103进行相关参数的配置(例如填写不同渠道的私钥)，然后将这些参数与工程文件在渠道参数配置与文件打包模块106中进行打包，并最终分别生成应用于不同渠道的各自的APK文件。打包生成APK文件后还需进行相关测试，测试通过后通过渠道接口模块105提交给不同的渠道，渠道检查通过后即可正式上线进行分发。具体的渠道参数配置与打包算法在后文参照图2进行描述。
文件管理模块107，用于存储和管理在系统100运行中产生和传输的各类文件，包括但不限于以上所述的不同版本的通用SDK文件、第三方SDK文件、CP开发的APK或Android工程文件以及打包生成的APK文件等。
CP统计和管理模块108，用于CP统计接入到各个渠道的程序产品运营情况，以及管理自己不同版本的产品在不同渠道上的运行情况。
根据本发明的一个实施例，系统100还可以包括检查更新模块109， 用于为CP提供不同APK的版本管理功能，检查CP上传的用于接入渠道的APK文件版本的更新情况。在CP根据通用SDK制作适用于各个渠道的APK文件过程中，可能会经常更新版本(例如修改bug，增加新功能等)上传至系统100。当终端用户通过渠道商下载了APK文件并在终端安装后，检查更新模块109用来每次终端用户允许该程序时是否CP已经提供了更新的版本。当判断出有更新的版本后，检查更新模块109还为终端用户提供增量更新的功能。增量更新功能可以让用户使用较小的网络流量上传或下载比较大的文件。具体的检查更新实现算法在后文参照图3进行描述。
根据本发明的一个实施例，检查更新模块109为每个上传至渠道商的APK文件版本生成唯一的标识符，以在不同版本之间进行区分。
图2示意性示出根据本发明实施方式的渠道参数配置与文件打包模块106进行渠道参数配置及SDK打包的流程图。如图2所示，以一个渠道为例，具体步骤如下：
步骤210，获取CP提供的基于通用SDK开发的APK文件，将该APK文件进行解包，生成CP临时文件；
根据本发明的一个实施例，CP可以通过CP接口模块将基于通用SDK开发的APK文件进行上传，存储在文件管理模块中。
步骤220，获取CP所选择的要发布的渠道，以及对所述APK文件应用于该渠道的配置信息；
根据本发明的一个实施例，所述配置信息包括但不限于涉及渠道支付的配置信息、Debug模式配置、横屏配置、更新配置、用户帐号设置等。
步骤230，获取该渠道的SDK文件，基于该SDK文件生成渠道SDK开发工程文件，然后将该工程文件生成渠道APK包；
根据本发明的一个实施例，获取该渠道的SDK文件可以通过第三方SDK 104中获取，或通过渠道接口模块105直接从渠道商获取。
步骤240，对所述渠道APK包进行解包，生成系统SDK临时文件；
步骤250，将步骤220获取的配置信息添加到步骤240生成的SDK临时文件中；
根据本发明的一个实施例，配置信息的添加可以是将配置信息替换 SDK临时文件中的原有配置信息，也可以添加SDK临时文件中原来没有的信息条目。
步骤260，将更新了配置信息的系统SDK临时文件和步骤210中生成的CP临时文件合并，生成对应于该渠道的渠道APK临时文件；
步骤270，将该渠道APK临时文件进行打包，生成渠道APK包；
步骤280，对该渠道APK包进行签名，生成签名的渠道APK包。签名后的渠道APK包即可以直接上传至相应的渠道商进行发布。
根据本发明的一个实施例，签名的规则可以在步骤220中的配置信息中获取。
本领域技术人员可以理解的是，上述步骤210和220的组合以及步骤230和240的组合的执行顺序可以任意交换，例如可以同时进行，也可以按顺序依次进行，只要在步骤250执行之前生成了相应的文件和配置信息即可。
图2仅示意性地示出了针对一个渠道的渠道参数配置与打包的流程，当CP同时配置了多个渠道时，图2的方法流程可以针对各个渠道同步进行。
图3示意性示出根据本发明实施方式的检查更新模块109对文件版本进行检查更新功能的流程图，具体步骤如下：
步骤310，获取终端用户发来的APK文件版本标识符(ChecksumA)。根据本发明的一个实施例，终端用户通过渠道商获取的APK文件带有通过检查更新模块109为该APK文件添加的版本标识符，该版本标识符用来唯一地标识该APK文件的版本。
步骤320，将所获取的APK文件版本标识符与系统100中已有的最新APK文件版本标识符(ChecksumB)进行比较，若相同，则终端用户安装的已经是最新版本，本方法结束；若不同，则进入步骤330；
步骤330，判断是否接收到终端用户发来的同意更新的请求，若收到，则进入步骤340，否则，本方法结束；
步骤340，生成所获取的APK文件版本与最新APK文件版本之间的差值文件Patch，为所述差值文件添加唯一的标识(ChecksumPatch)；
步骤350，获取所述差值文件的地址，发送给终端用户，同时将最 新APK文件版本标识符(ChecksumB)发送给终端用户。
步骤360，终端用户访问该差值文件的地址，客户端启动下载程序，下载该差值文件并安装，然后记录收到的最新APK文件版本标识符(ChecksumB)。差值文件下载完成以后，与客户端中原有的版本APK合成最新的版本APK文件，客户端启动应用安装程序，提示安装完毕。之后，将收到的最新APK文件版本标识符(ChecksumB)记录在该安装的版本中，作为该版本的标识符。
通过上述增量更新的功能，可以让用户使用较小的网络流量上传或下载比较大的文件，提高用户的体验，同时便于CP更好地管理上传至系统的多个版本。
交互方式
图4示出了CP端401、多渠道SDK接入系统402(即图1中的系统100)和渠道商403之间的交互流程图。图4仅示意性地示出了一个CP端401和一个渠道商403通过多渠道SDK接入系统402之间进行的交互。可以理解的是，该交互方法适用于多个CP和多个渠道商之间进行交互。
如图4所示，交互流程的具体步骤如下：
多渠道SDK接入系统402获取不同渠道的第三方SDK 104(步骤405)并存储在多渠道SDK接入系统402中。CP端401向服务器端402发送请求通用SDK(步骤410)，服务器端402呈现出通用SDK102(步骤415)并供CP端401下载使用(步骤420)。
CP端401将其开发的APK接入到下载的通用SDK 102，接入后进行调试和验证直至正确接入，并形成基于通用SDK 102的APK，最后上传基于通用SDK 102的APK到多渠道SDK接入系统402(步骤425)。
CP端选择渠道并进行参数配置，完成后将渠道和配置的参数发送到通用多渠道SDK接入系统402(步骤430)。多渠道SDK接入系统402会根据CP端选择的渠道和配置的参数将CP端开发的APK打包成渠道APK(步骤435)。可选地，CP可以下载打包的渠道APK(步骤440)并进行相关测试(步骤445)。如果测试发现需要修改 APK文件，则返回步骤425，重复步骤425-步骤440，重新进行打包。在测试完成之后，CP发出上传至渠道的指令(步骤450)，多渠道SDK接入系统402接到指令后将测试后的APK上传至相应的渠道(步骤455)。
当CP通过上述方法利用本发明的系统100完成了APK文件上传至不同的渠道后，终端用户就可以从各个渠道下载相应的APK文件，在终端设备(例如智能手机、平板电脑)上安装并使用。根据本发明的系统还可以进一步对后续终端用户的使用进行管理和统计，以方便CP更好地实现一个平台多渠道的APK管理。管理和统计的数据还可以通过CP统计和管理模块108提供给CP。
图5(a)和图5(b)分别示出了终端用户在使用根据本发明的多渠道SDK接入系统100生成的程序时与系统100进行交互的两个示例。其中图5(a)示出了终端用户登录验证的交互流程图，图5(b)示出了终端用户付费验证的交互流程图。CP通过根据本发明的多渠道SDK接入系统100生成的程序(例如APK文件)，经不同的渠道分发后，终端用户可以下载相应的程序。下载后终端用户运行相应的程序进行一系列的操作，如游戏类程序则进行游戏、工具类程序则使用相关功能、社交类程序则进行聊天等活动。
在图5(a)和图5(b)中，终端用户与系统00之间交互流程的节点包括终端用户客户端501、通用SDK客户端502、渠道SDK客户端503、渠道SDK服务器505、终端程序服务器504和多渠道SDK接入系统402。其中，终端用户客户端501是终端用户通过客户端终端设备下载、安装并使用的经过了本发明的多渠道SDK接入系统100生成的程序(例如APK文件)，客户端终端设备例如智能手机、平板电脑、电脑等带有计算功能的智能终端。通用SDK客户端502是在CP利用本发明的多渠道SDK接入系统100进行接入时，以通用SDK形式嵌入到最终程序，即嵌入到终端用户客户端501中的客户端。渠道SDK客户端503是用于使终端用户接入到第三方渠道的接口。优选地，呈现为在终端用户的客户端终端设备的用户交互界面形式，当用户登录时，通过渠道SDK客户端503呈现的界面，可以为终端用户提供输入用户名、密码以及附加信息等的功能。渠道SDK客户端 503再将信息发送到渠道SDK服务器505端进行登陆鉴权和授权操作。终端程序服务器504是为终端用户客户端501程序提供一系列服务的服务器，例如游戏服务器、社交论坛服务器等。
图5(a)示出了用户登录验证的交互流程图。如图5(a)所示，在登录到终端程序服务器之前，首先进行渠道登录验证，即登录到分发该终端程序的渠道服务器。用户启动终端用户客户端501的程序，例如游戏或工具类软件，终端用户客户端501发出调用登录的请求到通用SDK客户端502(步骤506)，进而通过通用SDK客户端502转发请求到渠道SDK客户端503，请求调用渠道登录(步骤508)；接着，通过终端用户客户端501随请求发送过来的渠道登录信息(例如用户名和密码、渠道标识等信息)请求登录渠道SDK的服务器505(步骤510)。在步骤512，渠道SDK服务器505进行验证，以验证终端用户的客户端501是否是合法通过渠道服务器下载的终端程序，以及验证客户端用户的信息。当渠道验证成功后，返回给渠道SDK客户端503登录成功的提示(步骤514)，并将用户UID标识返回至通用SDK客户端502(步骤516)；通用SDK客户端502再将用户UID标识和渠道标识返回终端用户客户端501(步骤518)，完成了渠道SDK服务器的登录验证过程。
接着利用渠道SDK服务器登录成功获取的信息(用户UID，渠道标识等)，进行终端程序服务器的登录验证。终端用户客户端501利用用户UID标识和渠道标识请求登录终端程序服务器504，获取用户的信息(步骤520)；进而验证登录到多渠道SDK接入系统100(步骤522)。在步骤524，多渠道SDK接入系统100进行验证。当验证通过后，由多渠道SDK接入系统100将用户信息发送至渠道SDK服务器505进行验证(步骤526)。在步骤528，由渠道SDK服务器505进行用户身份的验证。若验证成功，则通知多渠道SDK接入系统100正在操作的用户为有效的用户(步骤530)；接着，多渠道SDK接入系统100再通知终端程序服务器504正在操作的用户为有效的用户(步骤532)，从而返回给终端用户客户端501用户成功登录的信息(步骤534)，完成登录验证。
通过上述终端用户、渠道SDK服务器、终端程序服务器和多渠 道SDK接入系统之间的交互验证，可以确保用户信息的准确与安全，使终端用户通过不同渠道下载的程序都可以正确的验证和使用，保障了渠道商和CP的利益。
图5(b)示出了用户充值的交互流程图。如图5(b)所示，在用户运行终端程序的过程中进行充值操作时(例如游戏的付费充值，或使用软件工具的付费充值)，需要本发明的多渠道SDK接入系统、渠道SDK服务器和终端程序服务器协同操作，以确保用户充值的安全性和可靠性。用户登陆终端用户客户端501后即可发起充值操作，具体地，用户的充值请求首先是向通用SDK客户端502发起调用充值请求(步骤550)。通用SDK客户端502向多渠道SDK接入系统100发起请求，创建带有回调信息的订单，提交给多渠道SDK接入系统100(步骤552)。回调信息可以基于特定的事件或条件发生时做出响应，例如充值的结果通知。多渠道SDK接入系统402创建了带有回调信息的订单后，返回订单ID和其他相关信息至通用SDK客户端502(步骤554)。接着，通过SDK客户端502利用返回的订单ID想渠道SDK客户端503发起充值的请求，请求支付订单ID(步骤556)，进而渠道SDK客户端将该充值请求发送到渠道SDK服务器505(步骤558)，由渠道SDK服务器505验证充值是否成功，如果充值成功，则将充值成功的提示返回到通用SDK客户端502(步骤560)，进而通用SDK客户端502再将充值成功的提示返回到终端用户客户端501(步骤562)。
根据本发明的一个实施例，由于用户的充值行为通常需要在渠道SDK服务器端和终端程序的服务器端进行分成，即由渠道商和CP共同分成充值，因此，还需要将用户充值的信息提供给终端程序服务器504。如图5(b)所示，在渠道SDK服务器505验证充值成功后，还将充值成功的结果通知给多渠道SDK接入系统100(步骤564)。优选地，该通知可以以异步通信的方式发送。多渠道SDK接入系统402接收到充值结果的消息后，再将带有回调信息的充值结果通知发送给终端程序服务器504(步骤566)，最后通过终端程序服务器504将充值结果的通知返回给终端用户客户端501(步骤568)，从而完成用户充值。
根据本发明的多渠道SDK接入系统100也可以与为不同渠道提供更多的功能，通过渠道提供给第三方SDK的API，则可直接获取通用SDK接入渠道SDK的相关应用的配置，过程中可能需要CP提供其在渠道上的用户标示符(通常是用户名或用户ID)。CP需要通过本发明的系统100接入到渠道的oAuth认证系统，登录并获取其在渠道上的配置信息。
此外，本发明的系统100还可以具有推荐引擎，基于统计模块的大数据分析向CP推荐不同的渠道或者向渠道推荐CP的双向推荐模式。CP推荐渠道，根据cp在棱镜后台填写的APK相关信息，以及CP统计和管理模块108基于大数据对CP的应用分析结果，结合CP统计和管理模块108基于大数据对渠道的数据特性的分析结果，通过一套算法，系统自动向CP推荐渠道。渠道推荐CP，本发明的系统100的后台提供CP可选择向部分或全部渠道开放推荐其应用的功能。本发明的系统100根据CP开发的结果，以及对应用和渠道的分析结果，通过一套算法，自动向渠道推荐CP的应用。
本发明的系统100还可将根据用户的需求和产业链的需求与第三方服务公司进行深度整合，给用户提供以下相关服务：云服务(包括云数据、云存储)、应用加固、应用统计、应用测试、应用推送、广告SDK、游戏引擎插件、支付SDK等。
所述附图仅为示意性的并且未按比例画出。虽然已经结合优选实施例对本发明进行了描述，但应当理解本发明的保护范围并不局限于这里所描述的实施例。
结合这里披露的本发明的说明和实践，本发明的其他实施例对于本领域技术人员都是易于想到和理解的。说明和实施例仅被认为是示例性的，本发明的真正范围和主旨均由权利要求所限定。

Claims (10)

  1. 一种用于移动终端软件的多渠道SDK接入系统，所述系统包括中央控制台、通用SDK、CP接口模块、第三方SDK、渠道接口模块、渠道参数配置及文件打包模块和文件管理模块，其中，
    所述中央控制台，用于调度和控制其他各个模块；
    所述通用SDK，用于存储对于不同的多个渠道通用的SDK，其封装了与所有渠道提供的第三方SDK同样的客户端接口与服务端接口；
    所述CP接口模块，为至少一个CP提供接入到所述系统的接口，用于CP下载或上传文件或对文件进行配置；
    所述第三方SDK，用于存储由不同的渠道商提供的各自的SDK；
    所述渠道接口模块，为至少一个渠道商提供接入到所述系统的接口，用于获取不同渠道的SDK，并将通过所述渠道参数配置及文件打包模块生成的文件上传至所述各个相应的渠道；
    所述渠道参数配置及文件打包模块，用于接收CP提供的配置，并根据CP的配置和第三方SDK，将CP上传的基于通用SDK开发的程序进行配置与打包，以便能够接入到不同渠道中；
    所述文件管理模块，用于存储和管理在系统运行中产生和传输的各类文件。
  2. 根据权利要求1所述的系统，还包括CP统计与管理模块，用于CP统计接入到各个渠道的程序产品运营情况，以及管理不同版本的产品在不同渠道上的运行情况。
  3. 根据权利要求1所述的系统，还包括检查更新模块，用于为CP提供不同APK的版本管理功能，并检查CP上传的用于接入渠道的APK文件版本的更新情况。
  4. 根据权利要求1所述的系统，其中所述中央控制台的呈现方式为web界面。
  5. 根据权利要求1所述的系统，其中所述渠道参数配置及文件打包模块通过下列步骤进行打包：
    步骤a，获取CP提供的基于通用SDK开发的APK文件，将该APK 文件进行解包，生成CP临时文件；
    步骤b，获取CP所选择的要发布的渠道，以及对所述APK文件应用于该渠道的配置信息；
    步骤c，获取该渠道的SDK文件，基于该SDK文件生成渠道SDK开发工程文件，将该工程文件生成渠道APK包；
    步骤d，对所述渠道APK包进行解包，生成系统SDK临时文件；
    步骤e，将步骤b获取的配置信息添加到步骤240生成的SDK临时文件中；
    步骤f，将更新了配置信息的系统SDK临时文件和步骤a中生成的CP临时文件合并，生成对应于该渠道的渠道APK临时文件；
    步骤g，将该渠道APK临时文件进行打包，生成渠道APK包；
    步骤h，对该渠道APK包进行签名，生成签名的渠道APK包。
  6. 根据权利要求1所述的系统，其中所述配置信息选自涉及渠道支付的配置信息、Debug模式配置、横屏配置、更新配置、用户帐号设置。
  7. 根据权利要求5所述的系统，其中所述步骤a和b、所述步骤c和d互换或同时进行。
  8. 根据权利要求3所述的系统，其中所述检查更新模块为每个上传至渠道商的文件版本生成唯一的标识符。
  9. 根据权利要求3所述的系统，其中所述检查更新模块进行的更新为增量更新。
  10. 根据权利要求1所述的系统，其中所述系统还包括推荐引擎，基于所述CP统计与管理模块的大数据分析向CP推荐不同的渠道或者向渠道推荐CP。
PCT/CN2014/089165 2014-10-22 2014-10-22 移动终端软件的多渠道sdk接入系统及方法 WO2016061762A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/089165 WO2016061762A1 (zh) 2014-10-22 2014-10-22 移动终端软件的多渠道sdk接入系统及方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/089165 WO2016061762A1 (zh) 2014-10-22 2014-10-22 移动终端软件的多渠道sdk接入系统及方法

Publications (1)

Publication Number Publication Date
WO2016061762A1 true WO2016061762A1 (zh) 2016-04-28

Family

ID=55760054

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/089165 WO2016061762A1 (zh) 2014-10-22 2014-10-22 移动终端软件的多渠道sdk接入系统及方法

Country Status (1)

Country Link
WO (1) WO2016061762A1 (zh)

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107493198A (zh) * 2017-08-29 2017-12-19 北纬通信科技南京有限责任公司 基于sdk接入的蜂巢游戏打包系统及sdk接入方法
CN108008959A (zh) * 2017-12-28 2018-05-08 北京奇虎科技有限公司 一种软件开发工具包sdk接入方法、系统及装置
CN108108161A (zh) * 2016-11-23 2018-06-01 上海冰穹网络科技有限公司 支持多渠道sdk的接入系统及方法
CN108132808A (zh) * 2016-12-01 2018-06-08 北京金山云网络技术有限公司 一种渠道包生成方法及装置
CN109522030A (zh) * 2018-11-29 2019-03-26 北纬通信科技南京有限责任公司 基于一键生成多个游戏渠道包的平台出包方法
CN109784982A (zh) * 2018-12-20 2019-05-21 长沙聚丰网络科技有限公司 应用程序的推广方法、装置及计算机可读存储介质
CN110377333A (zh) * 2019-07-24 2019-10-25 上海游民网络科技有限公司 一种应用安装包文件处理方法及系统
CN110417860A (zh) * 2019-06-21 2019-11-05 深圳壹账通智能科技有限公司 文件传输管理方法、装置、设备及存储介质
CN110688095A (zh) * 2018-07-04 2020-01-14 深圳市科比特航空科技有限公司 一种无人机sdk开发平台的构建方法及装置
CN111309407A (zh) * 2020-02-21 2020-06-19 咪咕文化科技有限公司 集成第三方库的处理方法及装置
CN111596931A (zh) * 2020-05-27 2020-08-28 北京学之途网络科技有限公司 应用程序封装方法、装置、电子设备及可读存储介质
CN111610984A (zh) * 2020-05-09 2020-09-01 上海万间信息技术有限公司 基于插件的安卓应用打包分发方法、系统及应用终端
CN111866087A (zh) * 2020-06-29 2020-10-30 深圳壹账通智能科技有限公司 文件处理方法、装置、存储介质及计算机设备
CN112148330A (zh) * 2020-09-23 2020-12-29 南京爱奇艺智能科技有限公司 一种目标设备系统的升级方法和装置
CN112272211A (zh) * 2020-09-29 2021-01-26 京东数字科技控股股份有限公司 业务请求处理方法、装置及系统
CN112988177A (zh) * 2021-04-16 2021-06-18 腾讯科技（深圳）有限公司 应用安装包的发布、应用程序的运行方法、服务器及终端
CN114399065A (zh) * 2022-01-10 2022-04-26 厦门点触科技股份有限公司 面向多渠道的游戏后台配置管理系统
CN114461226A (zh) * 2022-04-07 2022-05-10 广州易方信息科技股份有限公司 解决强制依赖的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102509038A (zh) * 2011-10-11 2012-06-20 深圳市融创天下科技股份有限公司 一种塞班平台单签名多渠道发布软件的方法、装置、系统
CN103019708A (zh) * 2012-11-30 2013-04-03 北京奇虎科技有限公司 用于发布软件的方法和系统
CN103064666A (zh) * 2012-11-30 2013-04-24 北京奇虎科技有限公司 一种多渠道软件发布方法和系统
CN103338121A (zh) * 2013-06-13 2013-10-02 北京奇虎科技有限公司 一种系统管理服务器、方法及其系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102509038A (zh) * 2011-10-11 2012-06-20 深圳市融创天下科技股份有限公司 一种塞班平台单签名多渠道发布软件的方法、装置、系统
CN103019708A (zh) * 2012-11-30 2013-04-03 北京奇虎科技有限公司 用于发布软件的方法和系统
CN103064666A (zh) * 2012-11-30 2013-04-24 北京奇虎科技有限公司 一种多渠道软件发布方法和系统
CN103338121A (zh) * 2013-06-13 2013-10-02 北京奇虎科技有限公司 一种系统管理服务器、方法及其系统

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108108161A (zh) * 2016-11-23 2018-06-01 上海冰穹网络科技有限公司 支持多渠道sdk的接入系统及方法
CN108132808A (zh) * 2016-12-01 2018-06-08 北京金山云网络技术有限公司 一种渠道包生成方法及装置
CN107493198B (zh) * 2017-08-29 2020-08-04 北纬通信科技南京有限责任公司 基于sdk接入的蜂巢游戏打包系统及sdk接入方法
CN107493198A (zh) * 2017-08-29 2017-12-19 北纬通信科技南京有限责任公司 基于sdk接入的蜂巢游戏打包系统及sdk接入方法
CN108008959A (zh) * 2017-12-28 2018-05-08 北京奇虎科技有限公司 一种软件开发工具包sdk接入方法、系统及装置
CN110688095B (zh) * 2018-07-04 2023-08-25 深圳市科比特航空科技有限公司 一种无人机sdk开发平台的构建方法及装置
CN110688095A (zh) * 2018-07-04 2020-01-14 深圳市科比特航空科技有限公司 一种无人机sdk开发平台的构建方法及装置
CN109522030A (zh) * 2018-11-29 2019-03-26 北纬通信科技南京有限责任公司 基于一键生成多个游戏渠道包的平台出包方法
CN109522030B (zh) * 2018-11-29 2021-07-30 北纬通信科技南京有限责任公司 基于一键生成多个游戏渠道包的平台出包方法
CN109784982A (zh) * 2018-12-20 2019-05-21 长沙聚丰网络科技有限公司 应用程序的推广方法、装置及计算机可读存储介质
CN110417860A (zh) * 2019-06-21 2019-11-05 深圳壹账通智能科技有限公司 文件传输管理方法、装置、设备及存储介质
CN110377333A (zh) * 2019-07-24 2019-10-25 上海游民网络科技有限公司 一种应用安装包文件处理方法及系统
CN111309407A (zh) * 2020-02-21 2020-06-19 咪咕文化科技有限公司 集成第三方库的处理方法及装置
CN111610984A (zh) * 2020-05-09 2020-09-01 上海万间信息技术有限公司 基于插件的安卓应用打包分发方法、系统及应用终端
CN111610984B (zh) * 2020-05-09 2023-10-27 上海万间信息技术有限公司 基于插件的安卓应用打包分发方法、系统及应用终端
CN111596931A (zh) * 2020-05-27 2020-08-28 北京学之途网络科技有限公司 应用程序封装方法、装置、电子设备及可读存储介质
CN111866087A (zh) * 2020-06-29 2020-10-30 深圳壹账通智能科技有限公司 文件处理方法、装置、存储介质及计算机设备
CN112148330A (zh) * 2020-09-23 2020-12-29 南京爱奇艺智能科技有限公司 一种目标设备系统的升级方法和装置
CN112272211A (zh) * 2020-09-29 2021-01-26 京东数字科技控股股份有限公司 业务请求处理方法、装置及系统
CN112988177A (zh) * 2021-04-16 2021-06-18 腾讯科技（深圳）有限公司 应用安装包的发布、应用程序的运行方法、服务器及终端
CN112988177B (zh) * 2021-04-16 2023-08-01 腾讯科技（深圳）有限公司 应用安装包的发布、应用程序的运行方法、服务器及终端
CN114399065A (zh) * 2022-01-10 2022-04-26 厦门点触科技股份有限公司 面向多渠道的游戏后台配置管理系统
CN114461226A (zh) * 2022-04-07 2022-05-10 广州易方信息科技股份有限公司 解决强制依赖的方法及装置

Similar Documents

Publication Publication Date Title
WO2016061762A1 (zh) 移动终端软件的多渠道sdk接入系统及方法
EP3688594B1 (en) Api repository enabling microservices configuration and management
US10140205B1 (en) Systems and methods for infrastructure validation
CN104363264B (zh) 移动终端软件的多渠道sdk接入系统
US9798881B2 (en) Dynamic feature enhancement in client server applications and high volume server deployment with dynamic app store integration
US8819638B2 (en) Application protoyping suite
US8612947B2 (en) System and method for remotely compiling multi-platform native applications for mobile devices
US20150128103A1 (en) System and method for automating application programming interface integration
US20110154441A1 (en) Online development environment server, online marketplace server, online development environment constituting method, and developed application providing method
WO2016173199A1 (zh) 一种移动应用单点登录方法及装置
WO2023045849A1 (zh) 软件包处理方法、装置、系统、设备及介质
KR20210151926A (ko) 블록체인을 사용한 버전 이력 관리
WO2018033094A1 (zh) 富通信套件发布平台、版本更新方法及系统、移动终端
WO2020046981A1 (en) Automated code verification service and infrastructure therefor
US9760472B2 (en) Tenant code debugging in multi-tenant systems
US11113357B2 (en) Method and system for onboarding a virtual network function package utilized by one or more network services
JP2023525576A (ja) ソフトウェア更新のための認証キーの制御範囲
US20150121517A1 (en) Bundle-to-bundle authentication in modular systems
CN110493234B (zh) 证书处理方法、证书处理装置和电子设备
TWI506451B (zh) Support multi-service version of the service system and its methods
TWI813962B (zh) 企業雲網整合監控之建置與演進系統、方法及電腦可讀媒介
KR102435357B1 (ko) 블록체인 네트워크 트윈을 이용한 블록체인 통합 개발 및 관리 방법 및 시스템
EP4235437A1 (en) A test system and method for testing of apis
KR20180078764A (ko) 차량 단말기에서 실행 가능한 애플리케이션의 테스트를 통한 검증 절차를 제공하고 상기 애플리케이션이 마켓 포털 서버에 등록되도록 지원하는 방법, 이를 이용하는 개발자 포털 서버 및 애플리케이션 관리 서버
Rivera-Dourado DebAuthn: a Relying Party Implementation as a WebAuthn Authenticator Debugging Tool

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14904490

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16/08/2017)

122 Ep: pct application non-entry in european phase

Ref document number: 14904490

Country of ref document: EP

Kind code of ref document: A1