Skip to content

APP Migration SOP ​

After the Runtime authorization service is upgraded to the OpenPaaS service, the original Runtime authorization service will stop granting authorization. The new OpenPaaS service will adopt a new game package format, involving changes to how the game user account system is obtained, the payment flow, the ad flow, and other changes, as well as a new settlement method. This document aims to help partners quickly migrate from the original service to the new service, ensuring their business runs safely and in an orderly manner.

Overview of the Overall Migration Work ​

  1. Register an account in the OpenPaaS console and complete enterprise verification.
  2. Integrate the OpenPaaS SDK on both the front end and back end.
  3. Implement APP-specific capabilities through the extended API capabilities of the JS API provided by OpenPaaS.
  4. Handle the current stock of existing games.
    • Game package compatibility handling
    • Game package upgrade handling
  5. Data synchronization handling
    • Synchronizing game developer data between the APP's original open platform and OpenPaaS game developers
    • Synchronizing game data between the OpenPaaS platform and the APP's original open platform

1. OpenPaaS Account Preparation ​

  • Account registration
  • Complete the relevant verification: you need to prepare the company's business license, legal representative information, bank account, etc.
  • Obtain the public/private key pair required to access the service.

2. OpenPaaS SDK Integration ​

2.1 Front-End Integration ​

OpenPaaS provides SDKs for different system versions for the APP. The APP can choose the SDK to integrate based on its own system.

The SDK has encapsulated the vast majority of capabilities, but there are still a very small number of APP-specific capabilities that the APP needs to inject into the SDK via the JS API.

2.2 Back-End Integration ​

3. Compatibility for Legacy Games ​

APPs with legacy games can choose to load and run them by loading from a local game file directory.

3.1 Support for Loading Games via a Local Path ​

The APP calls startGameByDirectoryPath to load and run a local game package directory. The file directory passed in here is the directory of files that have already been signature-verified, decrypted, and installed, and the relevant parameters must also be passed in. The SDK will report the relevant parameters as the basis for billing. To avoid billing the same game multiple times for the same user, the APP must synchronize the full data of legacy games to SUD in advance.

4. Upgrading and Migrating Legacy Games to the New Version ​

Updating legacy games requires developers to package them in the new package format supported by OpenPaaS. The new package's loading method, user login, etc. differ from the original logic.

4.1 New Version Game Package Format ​

The new game package uses the .sp suffix and requires calling startGameBySignature to load and run the game.

4.2 Package Migration After a Game Update ​

4.2.1 Publishing the Game Package from the SUD OpenPaaS Platform ​

  • After the CP packages the game into the new version, publish the new version of the mini game on the OpenPaaS platform.
  • The APP selects the mini game on the OpenPaaS platform to publish it.
  • Pull the mini game's GameSignature.
  • Load the mini game via the GameSignture.
  • The publishing flow follows the APP's original flow.
  • The game package is loaded via a local path or URL.
  • Because the game package's file hash value changes, if the user logs in on both versions, it will result in duplicate billing.

4.3 User Data Mapping in the New Version of the Game ​

4.3.1 Mapping Data for Existing Users ​

  • When a user logs into a game with a new game package, because OpenPaaS provides a brand-new login solution, the resulting user identity differs from the identity issued by the APP. Therefore, the APP needs to return the user's original identity to OpenPaaS at login. OpenPaaS then processes it to form a new identifier and a mapping between the new and old identifiers, and returns it to the game side.
  • User Account Data