Secure communication method between mobile SDK and native application based on open platform

By integrating the open platform mobile SDK in native applications, providing registration services, loading product services and data transmission service interfaces, building data transmission channels, solving the problem of high access and maintenance costs in the existing technology, and achieving functional richness and improve security.

CN114338151BActive Publication Date: 2024-11-08CHINA CONSTRUCTION BANK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111624918.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-28
Publication Date
2024-11-08
Estimated Expiration
2041-12-28

AI Technical Summary

Technical Problem

The access method of existing open platform mobile terminals usually adopts a single SDK method, resulting in a single function, high access and maintenance costs, and large SDK packages, which affect performance optimization.

Method used

Using a secure communication method based on the open platform mobile SDK and native applications, encapsulate the SDK through the core area, provides registration services, load product services and data transmission service interfaces, and builds a data transmission channel. Native applications can call the core area interface to use open platform services , the products are provided in the form of H5.

Benefits of technology

Reduces the volume of the program package, improves the security of the open platform, reduces third-party access and maintenance costs, and improves feature richness and performance optimization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114338151B_ABST
    Figure CN114338151B_ABST
Patent Text Reader

Abstract

The present disclosure provides a method, system, device, medium and product for secure communication between an open platform mobile terminal SDK and a native application. The method is applied to a native area, a core area and an extended area. The native area is a native application of the access party. The core area encapsulates the open platform mobile terminal SDK. The extended area provides a variety of products h5. The open platform mobile terminal SDK provides a registration service interface, a loading product service interface and a data transmission service interface. The method comprises: the core area obtains the registration information and product parameters transmitted by the native area through the registration service interface and the loading product service interface; the native area is authenticated according to the registration information and the product parameters and the contracted product is loaded, and the contracted product provides services in the form of h5; the contracted product requests services from the open platform through the core area; and the native area obtains the return information of the open platform through the core area.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of mobile communication technology, and in particular to a secure communication method, system, device, medium and product based on an open platform mobile terminal SDK and a native application. Background Art

[0002] Currently, the mobile access method provided by the open platform is generally a single software development kit (SDK). The access party integrates the SDK into the project according to the integration document and calls the SDK interface to use a certain function. The internal implementation of the SDK generally requests the platform background service or implements a certain function within the SDK. This access method provides relatively simple functions. If the functions provided are richer, the access and maintenance costs of the access party will increase to a certain extent. In addition, if the platform provides too many interfaces, it will also increase the maintenance and update costs of subsequent versions, the platform application promotion and support costs, and increase the size of the SDK package. Summary of the invention

[0003] In view of the above technical problems, the present disclosure provides a secure communication method, system, device, medium and product based on an open platform mobile SDK and native applications, provides an access method for mobile SDK plus product H5, reduces the size of the program package while ensuring product services, and improves the security of the open platform.

[0004] A first aspect of the present disclosure provides a secure communication method based on an open platform mobile terminal SDK and a native application, the method is applied to a native area, a core area and an extended area, the native area is a native application of the access party, the core area encapsulates the open platform mobile terminal SDK, the extended area provides a variety of products h5, the open platform mobile terminal SDK provides a registration service interface, a loading product service interface and a data transmission service interface, the method includes:

[0005] The core area obtains the registration information and product parameters passed in by the native area through the registration service interface and the loading product service interface;

[0006] Authenticate the native zone according to the registration information and the product parameters and load the contracted product, the contracted product providing services in the form of h5;

[0007] The contracted product requests services from the open platform through the core area; and

[0008] The native area obtains the feedback information of the open platform through the core area.

[0009] According to an embodiment of the present disclosure, the contracted product calls the native area SDK through the components provided by the core area to perform native method operations.

[0010] According to an embodiment of the present disclosure, authenticating the native zone according to the registration information and the product parameters and loading the contracted product includes:

[0011] Performing an authentication operation on the native zone according to the registration information; and

[0012] The contracted product is loaded through the loading product service interface according to the product parameters.

[0013] According to an embodiment of the present disclosure, the contracted product requests a service from the open platform through the core area, including:

[0014] The contracted product obtains the product parameters through the data transmission service interface;

[0015] The service request information is sent to the open platform through the data transmission service interface according to the product parameters.

[0016] According to an embodiment of the present disclosure, the native area obtains the return information of the open platform through the core area, including:

[0017] The native area obtains the feedback information through the data transmission service interface, wherein the feedback information includes transmission parameters, product ID and event ID.

[0018] According to an embodiment of the present disclosure, the core area uses full message encryption and decryption to transmit data.

[0019] The second aspect of the present disclosure provides a secure communication system based on an open platform mobile terminal SDK and a native application, the secure communication system comprising a native area, a core area and an extended area, the native area is a native application of the access party, the core area encapsulates the open platform mobile terminal SDK, the extended area provides a variety of products h5, the open platform mobile terminal SDK provides a registration service interface, a loading product service interface and a data transmission service interface, including:

[0020] An acquisition module, used for the core area to acquire the registration information and product parameters passed in by the native area through the registration service interface and the loading product service interface;

[0021] A loading module, used to authenticate the native area and load the contracted product according to the registration information and the product parameters, wherein the contracted product provides services in the form of h5;

[0022] A service request module, used for the contracted product to request services from the open platform through the core area; and

[0023] The data feedback module is used for the native area to obtain the feedback information of the open platform through the core area.

[0024] The third aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein, when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned secure communication method based on an open platform mobile SDK and a native application.

[0025] The fourth aspect of the present disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the above-mentioned secure communication method based on an open platform mobile SDK and a native application.

[0026] The fifth aspect of the present disclosure further provides a computer program product, including a computer program, which, when executed by a processor, implements the above-mentioned secure communication method based on an open platform mobile terminal SDK and a native application.

[0027] Compared with the related art, the present invention provides a secure communication method, system, device, medium and product based on an open platform mobile SDK and native applications, which integrates the open platform mobile SDK into the native application. The mobile SDK exposes a registration service interface, a loading product service interface and a data transmission service interface. The mobile SDK builds a data transmission channel. Native applications can use the open platform services by calling the core area interface. The open platform provides services in the form of product h5, which is conducive to upgrades and maintenance and reduces third-party access costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0029] Figure 1 An application scenario diagram schematically illustrates a secure communication method between an open platform mobile terminal SDK and a native application according to an embodiment of the present disclosure;

[0030] Figure 2 A flowchart schematically shows a secure communication method between an open platform mobile terminal SDK and a native application according to an embodiment of the present disclosure;

[0031] Figure 3 A structural block diagram of a secure communication system based on an open platform mobile terminal SDK and native applications according to an embodiment of the present disclosure is schematically shown; and

[0032] Figure 4 A block diagram of an electronic device suitable for implementing a secure communication method between an open platform mobile terminal SDK and a native application according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0033] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0034] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0035] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0036] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0037] Currently, the mobile access method provided by open platforms is generally a single SDK method. The access party calls the SDK interface to use a certain function. The internal implementation of the SDK generally requests the platform background service, or implements a certain function within the SDK.

[0038] In one example, if the functions provided are to be enriched, the integrator's project must integrate the full SDK package internally, which increases the package size and is not conducive to mobile performance optimization. If the SDK is integrated on demand, multiple SDK packages may need to be integrated, which will also increase the access cost and maintenance cost of the access party. Secondly, if only interfaces are provided, the access party needs to implement the function page by itself, which will require a certain amount of design, development, testing, bug modification and other workload for the access party. Furthermore, if the mobile SDK provides richer functions, the access party needs to view the access documents and debug multiple interfaces, which increases the access cost and maintenance cost. For open platforms, because it is necessary to assist the access party in access, the upgrade, maintenance and promotion costs will also increase accordingly. In addition, the mobile SDK upgrade is more complicated, and the SDK integrated in the project needs to be updated.

[0039] To solve the above technical problems, the embodiments of the present disclosure provide a secure communication method based on an open platform mobile SDK and a native application, which is applied to the open platform mobile SDK. The native application is integrated with the open platform mobile SDK. The open platform mobile SDK provides a registration service interface, a loading product service interface and a data transmission service interface. The method includes: responding to an access request of the native application, obtaining configuration parameters, the configuration parameters are pre-configured by the native application through the registration service interface; initializing the configuration of the native application according to the configuration parameters; receiving the response parameters of the native application; and loading the product H5 through the loading product service interface according to the response parameters, and the product H5 prevents access to the open platform service through the data transmission service interface.

[0040] Figure 1 The application scenario diagram of the secure communication method between the open platform mobile terminal SDK and the native application according to the embodiment of the present disclosure is schematically shown. Figure 1 The application scenarios shown are only examples of application scenarios that can be used in the embodiments of the present disclosure, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios. It should be noted that the secure communication method and system based on the open platform mobile terminal SDK and native applications provided by the embodiments of the present disclosure can be used in the field of secure communication technology and related aspects of the financial field, and can also be used in any field other than the financial field. The application field of the secure communication method and system based on the open platform mobile terminal SDK and native applications provided by the embodiments of the present disclosure is not limited.

[0041] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a scenario where a native application accesses an open platform. The network 104 is used as a medium for providing a communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0042] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0043] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0044] The server 105 may be a server that provides various services, such as a background management server (only an example) that provides support for websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0045] It should be noted that the secure communication method based on the open platform mobile terminal SDK and the native application provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the secure communication system based on the open platform mobile terminal SDK and the native application provided in the embodiment of the present disclosure can generally be set in the server 105. The secure communication method based on the open platform mobile terminal SDK and the native application provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Correspondingly, the secure communication system based on the open platform mobile terminal SDK and the native application provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0046] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0047] The following will be based on Figure 1 The scene described by Figure 2 to Figure 4 The secure communication method between the open platform mobile terminal SDK and the native application based on the disclosed embodiment is described in detail.

[0048] Figure 2The flowchart schematically shows a secure communication method between an open platform mobile terminal SDK and a native application according to an embodiment of the present disclosure.

[0049] like Figure 2 As shown, the secure communication method based on the open platform mobile terminal SDK and the native application in this embodiment includes operations S210 to S230. The open platform in this embodiment can be an open platform of a banking system or other open platforms. The native area is integrated with the open platform mobile terminal SDK. The extended area provides a variety of open platform products, which are provided in the form of h5. The core area open platform mobile terminal SDK provides service interfaces, including: a registration service interface, which is used for native applications to configure parameters and register products; a loading product service interface, which is used to load registered products; a data transmission service interface, which is used to establish a data transmission channel between the native area and the core area, and between the core area and the extended area. The native area interacts with the core area through the data transmission channel, and the extended area accesses the open platform service through the core area, and calls the native area SDK through the components provided by the core area to perform native method operations.

[0050] In the disclosed embodiment, the open platform mobile SDK + product H5 is used to provide services to native applications. For native applications, it is equivalent to introducing an independent functional module, including page display and function implementation. Native applications only need to register and use it. For native applications (access parties), the SDK size is reduced while ensuring rich functions. For open platforms, a unified interface is exposed to the outside world, security is improved, and the product H5 form is flexible to upgrade, reducing the cost of later upgrades and maintenance.

[0051] In operation S210, the core area obtains the registration information and product parameters transmitted by the native area through the registration service interface and the loading product service interface.

[0052] In one example, the registration information includes configuration parameters and product registration information, and the configuration parameters include access environment configuration parameters, public key configuration parameters, and page style configuration parameters. The access environment is determined according to the access environment configuration parameters; the native application is authenticated according to the public key configuration parameters; and the control page display style is determined according to the page style configuration parameters.

[0053] When receiving a user's request to operate a native application to access the open platform, the core area (open platform mobile SDK) obtains the registration information and product parameters passed in by the native area, and determines the configuration parameters based on the registration information. The configuration parameters are pre-configured by the native application when registering in the project startup completion callback using the interface provided by the open platform mobile SDK. The configuration parameters include: access environment configuration parameters, public key configuration parameters, and page style configuration parameters. Native applications can configure the access environment, such as using a sandbox environment for testing and a formal environment for going online. The public key configuration parameters are used by the open platform to authenticate native applications and ensure the security of open platform product services. The page style configuration parameters are used to determine whether the control page displays a close button. In this embodiment, the configuration parameters may also include face-related parameters to identify the user's identity and further enhance the security of product services.

[0054] In operation S220, the native area is authenticated according to the registration information and product parameters and the contracted product is loaded, and the contracted product provides services in the form of h5.

[0055] According to the embodiment of the present disclosure, the native area is authenticated according to the registration information; and the contracted product is loaded through the loading product service interface according to the product parameters.

[0056] In one example, from a security perspective, authentication is performed each time a product is loaded. After the page is closed, there is no coupling between the core area and the native area. Specifically, the native area is authenticated based on the public key information configured in the core area. After authentication, the contracted product ID is determined based on the product parameters; the product loading service interface is called based on the contracted product ID to load the product H5.

[0057] In one example, the product parameters are sent by the native application to the open platform mobile SDK according to the access document. According to the product parameters, the contracted product ID to be loaded by the native application can be determined, and the product service interface is called according to the product ID to load the product and provide services to the native application. The product in this embodiment is provided to the native application in the form of H5, which is equivalent to a hot update solution, so that the native application only needs to register for product usage rights, without having to worry about the specific implementation of the product, thereby reducing the access cost of the native application. It should be noted that in order to ensure the security of data communication, the open platform mobile SDK adopts a unified message format and a unified encryption and decryption method for data transmission, such as AES full message encryption and RSA encryption key, or other encryption methods for data encryption.

[0058] In operation S230, the contracted product requests services from the open platform through the core area.

[0059] Operation S230 mainly includes operations S231 to S232, which are the interaction process between the mobile SDK of the core area open platform and the extended area product H5.

[0060] In operation S231, the contracted product obtains product parameters through the data transmission service interface. In operation S232, service request information is sent to the open platform through the data transmission service interface according to the product parameters.

[0061] In one example, the contracted product obtains the product parameters sent by the native application through the interface provided by the mobile SDK, requests services from the open platform based on the product parameters, and receives callback results from the open platform, which are displayed in the form of a page.

[0062] According to the embodiment of the present disclosure, the contracted product calls the native area SDK through the components provided by the core area to perform native method operations.

[0063] In an example, product H5 can also complete some operations that h5 cannot complete through the core area. Specifically, it calls the native area SDK through the components provided by the core area to perform some native method operations. For example, product H5 calls the SDK camera function to get the picture and display it on the H5 page. It can also realize opening another contracted product, obtaining the version number, album interface, screenshot, screen recording notification, prohibiting copying, calling up the address book and other functions.

[0064] According to the disclosed embodiment, the core area and the extended area define a communication method and communication standard. The communication method is described as follows: when the mobile phone loads a web page, it loads a section of application logic and establishes a secure communication channel, so that different programming languages ​​can interact with each other with the help of internal application standards (API). The channel uses AES encryption and RSA signature mechanisms to protect the integrity of data security. The channel uses a circular queue data structure and an asynchronous non-blocking communication method to achieve asynchronous execution and asynchronous response of transactions in the page, improve interaction efficiency, and reduce page jams.

[0065] In operation S240 , the native area obtains the return information of the open platform through the core area.

[0066] Operation S240 specifically includes operations S241 to S244, which is the interaction process between the mobile SDK of the core area development platform and the native area.

[0067] In operation S241, register and use the open platform mobile SDK interface in the project startup completion callback to configure initialization parameters.

[0068] In one example, after the native application is started, it calls back to register the mobile SDK interface and configures some parameter information, including loading page style information, face recognition function parameter information, public key information parameters, etc. to complete the initial registration. Native applications can configure the access environment, use the sandbox environment for testing, and use the formal environment for online. Configure public key information for authentication. Configure the signature server header field for native application signature. Configure the style to control whether the page displays a close button. Configure face-related parameters and use the face recognition function to enhance product and service security.

[0069] In operation S242, response parameters are passed to the open platform mobile SDK according to the access document. In operation S243, product h5 is loaded and product parameters are sent to the open platform mobile SDK. In operation S244, the return information of the open platform is received, where the return information includes transmission parameters, product ID and event ID.

[0070] In one example, the native application calls the interface in the controller and passes in the response parameters to load the contracted product. The format requirements of the response parameters have been pre-set in the access document. The native application can pass in relevant parameters, load the registered product, and send back information when the product is stopped. From a security perspective, each time a product is loaded, authentication is performed. After closing the page, there is no coupling between the open platform mobile SDK and the native application.

[0071] Native applications can establish data interaction channels with open platforms through mobile SDKs. The platform can send information back to native applications at any time and can also call other mobile SDKs connected to native applications. Because different contracted products and different events of the same product share the same data transmission channel, the callback design will carry product information and event ID in addition to transmission parameters.

[0072] According to the disclosed embodiment, a communication method and communication standard are defined for the native area and the core area. The communication method description provides an interface for the core area to use in the native area. Native applications can regard the core area as a black box system and can use the service by simply passing in the response parameters according to the access document instructions. The communication standard is that the core area uses AES full message encryption and RSA encryption key to ensure data communication security, and the callback information is output in a unified message format. Because the core area involves a transaction that depends on the result of another transaction, it is implemented in a sub-thread using a serial queue method, which does not affect the main thread and other thread operations. Therefore, the function can be guaranteed without affecting the performance. Even if it is violently clicked, the transaction dependency can be guaranteed to prevent the APP from getting stuck.

[0073] Through the method provided by the embodiment of the present disclosure, under the access mode of the open platform mobile terminal SDK + product h5, the mobile terminal provides a unified interactive interface for each product h5, standardizes message encapsulation and parsing, and provides functions that are difficult for h5 to achieve, which simplifies product development to a certain extent. The mobile terminal SDK adopts a unified message format and a unified encryption and decryption method for data transmission, which allows native applications to use the services of the open platform conveniently and safely.

[0074] Based on the above-mentioned secure communication method based on the open platform mobile terminal SDK and the native application, the present disclosure also provides a secure communication system based on the open platform mobile terminal SDK and the native application. Figure 3 The device is described in detail.

[0075] Figure 3 The structural block diagram of a secure communication system based on an open platform mobile terminal SDK and native applications according to an embodiment of the present disclosure is schematically shown.

[0076] like Figure 3 As shown, the secure communication system 400 based on the open platform mobile terminal SDK and the native application of this embodiment includes an acquisition module 410, a loading module 420, a service request module 430 and a data return module 440. The secure communication system includes a native area, a core area and an extended area. The native area is the native application of the access party, the core area is encapsulated with the open platform mobile terminal SDK, and the extended area provides a variety of products h5. The open platform mobile terminal SDK provides a registration service interface, a loading product service interface and a data transmission service interface.

[0077] The acquisition module 410 is used for the core area to acquire the registration information and product parameters passed in by the native area through the registration service interface and the loading product service interface. In one embodiment, the acquisition module 410 can be used to perform the operation S210 described above, which will not be repeated here.

[0078] The configuration module 420 is used to authenticate the native area and load the contracted product according to the registration information and product parameters, and the contracted product provides services in the form of h5. In one embodiment, the configuration module 420 can be used to perform the operation S220 described above, which will not be repeated here.

[0079] The service request module 430 is used for the contracted product to request services from the open platform through the core area. In one embodiment, the service request module 430 can be used to perform the operation S230 described above, which will not be repeated here.

[0080] The data return module 440 is used for the native area to obtain the return information of the open platform through the core area. In one embodiment, the data return module 440 can be used to perform the operation S240 described above, which will not be repeated here.

[0081] According to an embodiment of the present disclosure, any multiple modules among the acquisition module 410, the loading module 420, the service request module 430 and the data return module 440 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the acquisition module 410, the loading module 420, the service request module 430 and the data return module 440 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the acquisition module 410 , the loading module 420 , the service request module 430 and the data return module 440 may be at least partially implemented as a computer program module, and when the computer program module is executed, a corresponding function may be executed.

[0082] Figure 4 A block diagram of an electronic device suitable for implementing a secure communication method between an open platform mobile terminal SDK and a native application according to an embodiment of the present disclosure is schematically shown.

[0083] like Figure 4 As shown, the electronic device 500 according to an embodiment of the present disclosure includes a processor 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage part 508 into a random access memory (RAM) 503. The processor 501 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 501 may also include an onboard memory for caching purposes. The processor 501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0084] In RAM 503, various programs and data required for the operation of electronic device 500 are stored. Processor 501, ROM 502 and RAM 503 are connected to each other via bus 504. Processor 501 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 502 and / or RAM 503. It should be noted that the program can also be stored in one or more memories other than ROM 502 and RAM 503. Processor 501 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in one or more memories.

[0085] According to an embodiment of the present disclosure, the electronic device 500 may further include an input / output (I / O) interface 505, which is also connected to the bus 504. The electronic device 500 may further include one or more of the following components connected to the I / O interface 505: an input portion 506 including a keyboard, a mouse, etc.; an output portion 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 508 including a hard disk, etc.; and a communication portion 509 including a network interface card such as a LAN card, a modem, etc. The communication portion 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed, so that a computer program read therefrom is installed into the storage portion 508 as needed.

[0086] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0087] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 502 and / or RAM 503 described above and / or one or more memories other than ROM 502 and RAM 503.

[0088] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program includes a program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the secure communication method based on the open platform mobile terminal SDK and the native application provided by the embodiment of the present disclosure.

[0089] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 501. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0090] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 509, and / or installed from the removable medium 511. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0091] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the processor 501, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0092] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0093] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0094] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0095] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A secure communication method based on an open platform mobile terminal SDK and a native application, the method is applied to the native area, the core area and the extended area, the native area is the native application of the access party, the core area encapsulates the open platform mobile terminal SDK, the extended area provides a variety of products h5, the open platform mobile terminal SDK provides a registration service interface, a loading product service interface and a data transmission service interface, characterized in that: The method comprises: The core area obtains the registration information and product parameters passed in by the native area through the registration service interface and the loading product service interface; Authenticate the native zone according to the registration information and the product parameters and load the contracted product, the contracted product providing services in the form of h5; The contracted product requests services from the open platform through the core area; and The native area obtains the feedback information of the open platform through the core area; The contracted product calls the native area SDK to perform native method operations through the components provided by the core area.

2. The method according to claim 1, characterized in that: The authenticating the native area and loading the contracted product according to the registration information and the product parameters includes: Performing an authentication operation on the native zone according to the registration information; and The contracted product is loaded through the loading product service interface according to the product parameters.

3. The method according to claim 1, characterized in that The contracted product requests services from the open platform through the core area, including: The contracted product obtains the product parameters through the data transmission service interface; The service request information is sent to the open platform through the data transmission service interface according to the product parameters.

4. The method according to claim 1, characterized in that: The native area obtains the return information of the open platform through the core area, including: The native area obtains the feedback information through the data transmission service interface, wherein the feedback information includes transmission parameters, product ID and event ID.

5. The method according to any one of claims 1 to 4, characterized in that: The core area uses full message encryption and decryption to transmit data.

6. A secure communication system based on an open platform mobile terminal SDK and native applications, the secure communication system comprising a native area, a core area and an extended area, the native area being the native application of the access party, the core area encapsulating the open platform mobile terminal SDK, the extended area providing a variety of products h5, the open platform mobile terminal SDK providing a registration service interface, a product loading service interface and a data transmission service interface, including: An acquisition module, used for the core area to acquire the registration information and product parameters passed in by the native area through the registration service interface and the loading product service interface; A loading module, used to authenticate the native area and load the contracted product according to the registration information and the product parameters, wherein the contracted product provides services in the form of h5; A service request module, used for the contracted product to request services from the open platform through the core area; as well as A data feedback module, used for the native area to obtain feedback information of the open platform through the core area; The calling module is used for the contracted product to call the native area SDK through the components provided by the core area to perform native method operations.

7. An electronic device comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 5.

9. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.