Development framework generation method and application method

Abstract

The application discloses a development framework generation method and application method. The method comprises the following steps: determining component requirement information corresponding to application requirement information of a specified service, service logic and compatibility requirement information; determining a general basic component and a component access interface for original basic component access according to the compatibility requirement information and the component requirement information; determining key logic indicating a key service based on the service logic, and configuring a corresponding calling interface for the key logic; and generating a development framework for the specified service based on the general basic component, the component access interface, the service logic and the calling interface. The application provides a development framework with good compatibility, improves the reusability of related logic code, and reduces the code maintenance difficulty and workload. On this basis, the universality of a related software development kit can be ensured, and the development efficiency of related software is improved. The application embodiments can be applied to various scenes such as cloud technology, AI, intelligent transportation and vehicle-mounted devices.

Description

Technical Field

[0001] This application relates to the field of Internet communication technology, and in particular to a method for generating and applying a development framework. Background Technology

[0002] With the development of internet communication technology, various software applications are emerging in large numbers, their application areas are becoming increasingly widespread, and the functions they can perform are also increasing. Different software programs may share the same functional requirements, such as implementing payment services. In related technologies, the platform providing the payment service typically provides the relevant software development code, and software developers then use this code to enable payment functionality in their software. However, considering platform differences, software development code is often provided based on the platform, such as code for Android and code for other console platforms. When there are logical changes in the payment process, the software development code needs to be adjusted accordingly, meaning adjustments are required for the code on each platform. This leads to significant maintenance difficulties and workload, thus impacting the development efficiency of the software. Therefore, it is necessary to provide software development code with good platform compatibility. Summary of the Invention

[0003] To address the lack of compatible software development code in existing technologies for software development, this application provides a development framework generation method and application method:

[0004] According to a first aspect of this application, a method for generating a development framework is provided, the method comprising:

[0005] In response to the application requirements information of a specified business, the corresponding component requirements information, business logic, and compatibility requirements information are determined; wherein, the compatibility objects indicated by the compatibility requirements information include at least one of the following: at least two types of devices, at least two types of operating systems, and at least two types of programming languages;

[0006] Based on the compatibility requirement information and the component requirement information, determine the general basic components and the component access interfaces for native basic component access;

[0007] Based on the aforementioned business logic, the key logic indicating the key business is determined, and the corresponding calling interface is configured for the key logic;

[0008] A development framework for the specified business is generated based on the general basic components, the component access interface, the business logic, and the calling interface.

[0009] According to a second aspect of this application, a method for developing a framework application is provided, the method comprising:

[0010] Obtain target framework data, wherein the target framework data indicates the development framework of a specified business, and the development framework indicating the specified business is generated using the development framework generation method described in the first aspect;

[0011] Obtain server information that supports the implementation of the specified service;

[0012] Based on the target framework data and the server information, a software development kit (SDK) file corresponding to the specified business is generated.

[0013] According to a third aspect of this application, a method for developing a framework application is provided, the method comprising:

[0014] Obtain functional requirements information for a specified software;

[0015] When the functional requirement information indicates that a specified business is to be implemented, the target software development kit file is obtained. The target software development kit file is the software development kit file corresponding to the specified business generated in the development framework application method as described in the second aspect.

[0016] The specified software is updated based on its code files and the target software development kit files.

[0017] According to a fourth aspect of this application, a business processing method is provided, applied to a client, the client having installed specified software updated in the development framework application method as described in the third aspect, the specified software including a target software development kit file indicating specified business, the method comprising:

[0018] In response to a specified business request indicating a critical business, the specified business request is processed based on a call interface; wherein the critical business belongs to the specified business, the call interface indicates the business logic settings information of the development framework in the target software development kit file, and the call interface is configured for the critical business.

[0019] According to a fifth aspect of this application, a development framework generation apparatus is provided, the apparatus comprising:

[0020] Response module: Used to respond to application requirement information of a specified business and determine the corresponding component requirement information, business logic and compatibility requirement information; wherein, the compatibility objects indicated by the compatibility requirement information include at least one of the following: at least two types of devices, at least two types of operating systems and at least two types of programming languages;

[0021] Determining module: used to determine the general basic components and the component access interfaces for native basic component access based on the compatibility requirement information and the component requirement information;

[0022] Call interface configuration module: used to determine the key logic indicating key business based on the business logic, and to configure the corresponding call interface for the key logic;

[0023] Framework generation module: used to generate a development framework for the specified business based on the general basic components, the component access interface, the business logic, and the calling interface.

[0024] According to a sixth aspect of this application, a development framework application apparatus is provided, the apparatus comprising:

[0025] Framework acquisition module: used to acquire target framework data, wherein the target framework data indicates the development framework of a specified business, and the development framework indicating the specified business is generated using the development framework generation method described in the first aspect;

[0026] Server information acquisition module: used to acquire server information that supports the implementation of the specified business;

[0027] Toolkit generation module: Used to generate software development kit files corresponding to the specified business based on the target framework data and the server information.

[0028] According to a seventh aspect of this application, a development framework application apparatus is provided, the apparatus comprising:

[0029] Requirements information acquisition module: used to acquire functional requirements information for a specified software;

[0030] Toolkit Acquisition Module: Used to acquire a target software development kit file when the functional requirement information indicates the implementation of a specified business, wherein the target software development kit file is the software development kit file corresponding to the specified business generated in the development framework application method as described in the second aspect;

[0031] Update module: Used to update the functionality of the specified software based on the code files of the specified software and the target software development kit files.

[0032] According to an eighth aspect of this application, a business processing apparatus is provided, configured on a client, the client having installed specified software updated in the development framework application method as described in the third aspect, the specified software including a target software development kit file indicating a specified business, the apparatus comprising:

[0033] Business processing module: used to respond to a specified business request indicating a key business, and process the specified business request based on the calling interface; wherein, the key business belongs to the specified business, the calling interface indicates the business logic setting information of the development framework in the target software development kit file, and the calling interface is configured for the key business.

[0034] According to a ninth aspect of this application, an electronic device is provided, the electronic device including a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the development framework generation method as described in the first aspect, the development framework application method as described in the second aspect, the development framework application method as described in the third aspect, or the business processing method as described in the fourth aspect.

[0035] According to a tenth aspect of this application, a computer-readable storage medium is provided, wherein at least one instruction or at least one program is stored therein, the at least one instruction or the at least one program being loaded and executed by a processor to implement the development framework generation method as described in the first aspect, the development framework application method as described in the second aspect, the development framework application method as described in the third aspect, or the business processing method as described in the fourth aspect.

[0036] According to the eleventh aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the development framework generation method as described in the first aspect, the development framework application method as described in the second aspect, the development framework application method as described in the third aspect, or the business processing method as described in the fourth aspect.

[0037] This application provides a development framework generation method and application method, which have the following technical effects:

[0038] This application determines the component requirements, business logic, and compatibility requirements corresponding to the application requirements of a specified business. Then, based on the compatibility and component requirements, it determines general-purpose basic components and component access interfaces for native basic component integration. Furthermore, based on the business logic, it identifies key logic indicating critical business operations and configures corresponding call interfaces for this key logic. Thus, based on the general-purpose basic components, component access interfaces, business logic, and call interfaces, it generates a development framework for the specified business. This application provides a development framework with good compatibility, improves the reusability of related logic code, and reduces the difficulty and workload of code maintenance. It ensures applicability across different platforms at the level of basic components and overcomes incompatibility issues between some platforms and general-purpose basic components due to their own characteristics by utilizing component access interfaces. Configuring corresponding call interfaces for key logic improves the response to core business calls and reduces its coupling with the platform, user interface, etc. Based on this, the generated development framework for the specified business ensures the universality of related software development kits and improves the development efficiency of related software. Attached Figure Description

[0039] To more clearly illustrate the technical solutions and advantages in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 This is a schematic diagram of an application environment provided in an embodiment of this application;

[0041] Figure 2 This is a flowchart illustrating a development framework generation method provided in an embodiment of this application;

[0042] Figure 3 This is a flowchart illustrating a development framework application method provided in an embodiment of this application;

[0043] Figure 4 This is also a flowchart illustrating a development framework application method provided in an embodiment of this application;

[0044] Figure 5-10 This is a schematic diagram of the layered design of the development framework provided in the embodiments of this application;

[0045] Figure 11 This is a schematic diagram of the application of the calling interface provided in the embodiments of this application;

[0046] Figure 12 This is a schematic diagram illustrating the invocation method and invocation principle of the access layer provided in the embodiments of this application;

[0047] Figure 13 This is a block diagram of a development framework generation device provided in an embodiment of this application;

[0048] Figure 14 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0049] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0050] It should be noted that the terms "comprising" and "having" and any variations thereof in the specification, claims and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such processes, methods, products or devices.

[0051] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0052] DB (Database): A database can be viewed as an electronic filing cabinet—a place to store electronic files, where users can perform operations such as adding, querying, updating, and deleting data. A "database" is a collection of data stored together in a certain way, capable of being shared by multiple users, with minimal redundancy, and independent of application programs.

[0053] PS4 (PlayStation 4): A home video game console developed by Sony Corporation.

[0054] PS5 (PlayStation 5): A home video game console launched by Sony Corporation.

[0055] NS (Nintendo Switch): A console released by Nintendo in March 2017, featuring a hybrid design that combines home console and handheld functionality.

[0056] Xbox One: A home video game console released by Microsoft.

[0057] Steam: A digital game software distribution platform.

[0058] PC (Personal Computer): A personal computer.

[0059] Console platform: In this application, the embodiments refer to console game platforms such as Switch, PS4, PS5, and Xbox.

[0060] PC game platform: In this application embodiment, it refers to a PC game platform, such as the Steam platform.

[0061] SDK (Software Development Kit): A software development toolkit. In this application embodiment, it refers to a functional module integrated into the client application to complete a specific independent function; for example, the MiMaster SDK completes the payment function.

[0062] IDL (Interface Description Language): An interface description language specifically designed to describe interfaces and can be used for cross-platform development.

[0063] C is a procedural, abstract, general-purpose programming language widely used in low-level development.

[0064] C++ is an extension of the C language. It can perform procedural programming like C, object-based programming with abstract data types, and object-oriented programming with inheritance and polymorphism.

[0065] Kotlin: A statically typed programming language for modern multi-platform applications.

[0066] OC (Objective-C): It is an object-oriented programming language that extends C.

[0067] Swift: A computer programming language.

[0068] Java: An object-oriented programming language.

[0069] JNI (Java Native Interface): A Java native interface that ensures code portability across different platforms. It can be used as a way for native Java code in Android to access C++.

[0070] Please see Figure 1 , Figure 1This is a schematic diagram of an application environment provided in an embodiment of this application. This application environment may include a client 10 and a server 20. The client 10 and the server 20 can be directly or indirectly connected via wired or wireless communication. The client 10 sends a service request triggered by a user, indicating a specified service, to the server 20, and the server 20 processes the received service request. It should be noted that... Figure 1 This is just one example.

[0071] Client 10 can be a physical device such as a smartphone, computer (e.g., desktop computer, tablet, laptop), augmented reality (AR) / virtual reality (VR) device, digital assistant, smart wearable device, smart voice interaction device (e.g., smart speaker), smart home appliance, or in-vehicle terminal. It can also be software running on the physical device, such as a computer program. The operating system corresponding to the client can include Android, iOS (a mobile operating system developed by Apple), Linux, Microsoft Windows, etc. When client 10 is software running on a physical device, this software can be developed by software developer A based on an SDK provided by a designated business service provider B. This SDK is generated based on a development framework that instructs the designated business.

[0072] Server 20 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The server may include network communication units, processors, and memory, etc. Server 20, belonging to the designated business service provider B, can provide background services related to the designated business to client 10.

[0073] In practical applications, the software developed by software developer A can be a game application. It can be understood that implementing game-related services is the primary functional requirement of the game application, while implementing specific services is a secondary functional requirement. The specific service provided by service provider B can be a payment service, supporting payment channels such as virtual currency, third-party payment platforms, online payment platform balances, online payment platform quick payments, mobile phone recharge cards, and mobile phone bills. Of course, the software developed by software developer A can also be a vehicle-to-everything (V2X) application or a map application. The functions of a V2X application can include vehicle information (such as energy consumption information and speed information) maintenance functions, music playback functions, etc.

[0074] The following describes a specific embodiment of a development framework generation method according to this application. Figure 2 This is a flowchart illustrating a development framework generation method provided in this application. This application provides the operational steps described in the embodiments or flowchart, but based on conventional or non-inventive labor, it may include more or fewer operational steps. The order of steps listed in the embodiments is merely one possible execution order among many, and does not represent the only execution order. In actual system or product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment). Specifically, as shown... Figure 2 As shown, the method may include:

[0075] S201: In response to the application requirement information of the specified business, determine the corresponding component requirement information, business logic and compatibility requirement information; wherein, the compatibility objects indicated by the compatibility requirement information include at least one of the following: at least two types of devices, at least two types of operating systems and at least two types of programming languages;

[0076] In this embodiment, the server responds to the application requirement information of a specified business and determines the corresponding component requirement information, business logic, and compatibility requirement information. The application requirement information of the specified business refers to the server's requirements for providing the specified business service externally. The component requirement information describes the requirements at the component level, such as requirements for basic components and user interface (UI) components. The business logic describes the relevant processes for implementing the specified business. The compatibility requirement information describes the objects that need to be compatible. The compatible objects indicated by the compatibility requirement information may include at least one of the following: at least two types of devices, at least two types of operating systems, and at least two types of programming languages. For example, at least two types of devices include mobile phones, PCs, and host computers. At least two types of operating systems include Android, iOS, and Windows. At least two types of programming languages ​​include Java, C, C++, Kotlin, Objective-C, and Swift.

[0077] S202: Determine the general basic components and the component access interfaces for native basic component access based on the compatibility requirement information and the component requirement information;

[0078] In this embodiment, the server determines general basic components and component access interfaces for native basic component access based on compatibility requirement information and component requirement information. The component requirement information can determine the requirements for basic components, resulting in a candidate basic component set, which can be determined based on historical experience. The compatible objects indicated by the compatibility requirement information can be considered as consisting of at least two conflicting sub-objects. For the candidate basic component set, the basic components supported by each conflicting sub-object are determined, and the union of these basic components becomes the general basic component. For basic components not supported by the conflicting sub-objects in the candidate basic component set, a component access interface is introduced to access the native basic components supported by the conflicting sub-objects. It should be noted that the basic components in the candidate basic component set can be adaptively adjusted by combining historical experience and compatible objects. The basic components in the candidate basic component set can include network libraries, log libraries, databases, thread libraries, etc. Alternatively, the requirements for basic components can be determined by the component requirement information, and based on these requirements, the basic components supported by each conflicting sub-object can be determined. For each conflicting sub-object's supported basic components, determine the support frequency of each basic component, and include basic components with a support frequency equal to or higher than the threshold into the category of general basic components. If a conflicting sub-object's supported basic component is excluded from the general basic components due to a support frequency lower than the threshold, then the conflicting sub-object can retain the right to use the basic components it supports through the component access interface.

[0079] Generally, Android platforms use Java, Kotlin, and C for software development, iOS platforms use Objective-C, Swift, or C, and console platforms use C. PC game platforms often support Windows systems. Since basic components such as networking and threading require system support from the platform, compatibility issues are common. Therefore, this application provides both general-purpose basic components and component access interfaces for native basic components. If a specific platform (such as PS4 / 5) is incompatible with the general version of the basic components, native basic components can be developed separately through the component access interfaces for adaptation. For PS4 and PS5 platforms, due to different component dependencies, native basic components are required. Compared to software development code that integrates component requirements and business logic, the development framework provided in this application separates business logic from component access interfaces, allowing business logic to remain cross-platform, and enabling basic components to use the dependencies of PS4 and PS5 platforms when needed.

[0080] See Figure 7-8The standard component interface corresponds to the component access interface mentioned above. After this adaptation, channels on Android, iOS, Windows (Steam), Switch, and Windows (Xbox) platforms can uniformly reuse the same universal basic component version. PS4 and PS5 platforms use the native platform component version.

[0081] S203: Based on the business logic, determine the key logic that indicates the key business, and configure the corresponding calling interface for the key logic;

[0082] In this embodiment, the server determines the key logic indicating key business operations based on business logic, and configures corresponding calling interfaces for the key logic. Taking payment business as an example, the key (core) business is the business strongly related to payment, such as purchasing a target game skin. Conversely, there are ordinary businesses weakly related to payment, such as changing avatars or wallpapers. The business logic consists of logic code, which indicates logic related to page redirection, user interaction responses, order number construction, order request placement, parameter encapsulation, etc. See also... Figure 11 The API calls correspond to standard payment process APIs. This can be understood as defining a standard payment process for a user's purchase scenario, including initialization, querying product information, querying marketing activities, user payment, and delivery. Based on this process, the relevant APIs are standardized, unifying the required parameters. Defining standard payment process APIs decouples key logic calls from the platform and UI, allowing all platforms to reuse the same version of key logic and even business logic, minimizing maintenance costs. The main defined standard payment process APIs are shown below:

[0083] (1) Initialization

[0084] init(const InitRequest&request,const std::shared_ptr <initcallback>&callback)

[0085] Includes: the passed-in initialization parameter object request, and the initialization callback object callback;

[0086] (2) Query

[0087] query(const QueryRequest&request,const std::shared_ptr <querycallback>&callback)

[0088] Includes: the request object (the passed query parameter) and the callback object (the query callback object);

[0089] (3) Payment

[0090] pay(const PayRequest&request,const std::shared_ptr <paycallback>&callback)

[0091] Includes: the incoming payment parameter object `request`, and the payment callback object `callback`;

[0092] (4) Shipping

[0093] provide(const ProvideRequest&request,const std::shared_ptr <providecallback>&callback)

[0094] It includes: the incoming shipping parameter object `request`, and the shipping callback object `callback`.

[0095] S204: Generate a development framework for the specified business based on the general basic components, the component access interface, the business logic, and the calling interface.

[0096] In this embodiment, the server generates a development framework for a specific business based on the aforementioned general basic components, component access interfaces, business logic, and calling interfaces. Compared to software development code that integrates component requirement information and business logic, the development framework provided in this embodiment is more granular, enabling maximum cross-platform reuse of business logic, while being compatible with platforms such as Android, iOS, Windows (Steam), Switch, Windows (Xbox), and PS4 / 5.

[0097] In one exemplary embodiment, before generating a development framework for the specified business based on the general basic components, the component access interface, the business logic, and the calling interface, the method further includes: determining the corresponding user interface component based on the component requirement information;

[0098] Accordingly, a development framework for the specified business is generated based on the general basic components, the component access interface, the business logic, and the calling interface, including: first, determining the hierarchy information; wherein the hierarchy information indicates that the user interface component is set at the level closer to the user, and that the general basic components, the component access interface, the business logic, and the calling interface are set at the level closer to the machine; then, a development framework for the specified business is obtained based on the hierarchy information, the user interface component, the general basic components, the component access interface, the business logic, and the calling interface.

[0099] The requirements for UI components can be determined from the component requirement information. UI components are used to implement the representation of the user interface, including buttons, pop-ups, lists, labels, etc. The hierarchy information indicates that user interface components should be placed at a level closer to the user, while common basic components, component access interfaces, business logic, and calling interfaces should be placed at a level closer to the machine. The resulting development framework can be found in [reference needed]. Figure 6-10 User interface components are located in the native layer, while general-purpose basic components, component access interfaces, business logic, and calling interfaces are located in the C / C++ layer. This means that UI components utilize native components from various platforms, providing users with a better interface experience. This hierarchical information helps users more intuitively understand the design philosophy of the development framework and predict the performance of the resulting software product. For example... Figure 6-10 As shown, apart from platform differences in the UI, the overall business process, such as page navigation and network request initiation, can be controlled in C++. The business process that mainly involves modifications (such as adjustments needed when there are logical changes in a specified business) has achieved cross-platform uniformity.

[0100] In an exemplary embodiment, before generating a development framework for the specified business based on the general basic components, the component access interface, the business logic, and the calling interface, the method further includes: when the compatibility object indicated by the compatibility requirement information includes at least two types of programming languages ​​that are conflicting programming languages, creating an access layer for programming language conversion; wherein, the access layer is used to convert and adapt business requests using conflicting programming languages ​​based on preset calling rules;

[0101] Accordingly, generating a development framework for the specified business based on the general basic components, the component access interface, the business logic, and the calling interface includes: obtaining a development framework for the specified business based on the access layer, the general basic components, the component access interface, the business logic, and the calling interface.

[0102] The compatibility criteria include at least two types of programming languages, which can be a first type and a second type, where the first and second types are conflicting languages. For example, the first type might be Java, and the second type might be C or C++. Since compatibility with both types is required, one type of programming language can be chosen as the default programming language for the business request. Using a specially designed access layer for programming language conversion, when a request is received in a language other than the default, it can be converted and adapted to achieve compatibility between the two types of programming languages. The same principle applies when at least three types of programming languages ​​are conflicting. The default invocation rule, which serves as the basis for the access layer's conversion and adaptation of business requests using conflicting programming languages, can be based on the concept of object invocation.

[0103] A development framework for a specific business is derived based on the access layer, general basic components, component access interfaces, business logic, and API calls. See also... Figure 9-10 The access layer corresponds to the "object conversion and adaptation layer". The access layer, common basic components, component access interfaces, business logic, and calling interfaces can be set in the C / C++ layer.

[0104] In practical applications, this application provides a cross-platform SDK development framework that supports the reuse of the same core payment process code across platforms such as Android, iOS, Windows (Steam), Switch, Windows (Xbox), and PS4 / 5. It also allows for extensible adaptation of the basic component library for specific platforms. This unifies the previous separate development versions for each platform into a single core codebase plus multiple specific dependency libraries, significantly reducing development and maintenance costs and improving development efficiency. Regardless of whether it's Android, iOS, or a console platform (such as Switch, PS4 / 5), the general payment process remains largely the same. However, the differences in platform languages ​​and supporting libraries are significant. This application solves the problem of using the same payment business logic code to support applications on different platforms to complete payments.

[0105] As can be seen from the technical solutions provided in the embodiments of this application above, the embodiments of this application determine the component requirement information, business logic, and compatibility requirement information corresponding to the application requirement information of a specified business. Then, based on the compatibility requirement information and component requirement information, general basic components and component access interfaces for native basic component access are determined. Furthermore, based on the business logic, the key logic indicating the key business is determined, and corresponding call interfaces are configured for the key logic. Thus, a development framework for a specified business is generated based on general basic components, component access interfaces, business logic, and call interfaces. The embodiments of this application provide a development framework with good compatibility, improve the reusability of related logic code, and reduce maintenance difficulty and workload. It can ensure the applicability of different platforms at the level of basic components and overcome the incompatibility problem of some platforms with general basic components due to their own characteristics by using component access interfaces. Configuring corresponding call interfaces for key logic can improve the call response to core business and reduce its coupling with the platform, user interface, etc. Compared with software development code that integrates component requirement information and business logic, the embodiments of this application can be regarded as splitting the software development code into four main parts: general basic components, component access interfaces, business logic, and call interfaces.

[0106] The following describes a specific embodiment of a development framework application method according to this application. Figure 3 This is a flowchart illustrating a development framework application method provided in an embodiment of this application. This application provides the operational steps described in the embodiments or flowchart, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only execution order. In actual system or product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment). Specifically, as shown... Figure 3 As shown, the method may include:

[0107] S301: Obtain target framework data, wherein the target framework data indicates the development framework of a specified business, and the development framework indicating the specified business is generated using the development framework generation method described in steps S201-S204 above.

[0108] S302: Obtain server information that supports the implementation of the specified service;

[0109] S303: Based on the target framework data and the server information, generate the software development kit file corresponding to the specified business.

[0110] Based on the aforementioned steps S201-S204, the target framework data can be considered as a development template for implementing a specified business function across multiple platforms. On this basis, the server can obtain server information supporting the implementation of the specified business function, and then generate a software development kit (SDK) file corresponding to the specified business function based on the target framework data and server information. This establishes a connection between the development template and the backend machines supporting the implementation of the specified business function. The generated SDK file can be used by software developers to endow related software with the functionality to implement the specified business function.

[0111] As can be seen from the technical solutions provided in the embodiments of this application above, the embodiments of this application utilize target framework data and server information to generate software development kit (SDK) files corresponding to a specified business. The good compatibility of the development framework based on the specified business ensures the universality of the generated SSD, creating the possibility of providing empowerment for more software. Software developers use this SSD to conduct related software development, improving the convenience and efficiency of software development.

[0112] The following describes a specific embodiment of a development framework application method according to this application. Figure 4 This is a flowchart illustrating a development framework application method provided in an embodiment of this application. This application provides the operational steps described in the embodiments or flowchart, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only execution order. In actual system or product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment). Specifically, as shown... Figure 4 As shown, the method may include:

[0113] S401: Obtain functional requirements information for the specified software;

[0114] S402: When the functional requirement information indicates that a specified business is to be implemented, obtain the target software development kit file. The target software development kit file is the software development kit file corresponding to the specified business generated in the development framework application method described in steps S301-S303 above.

[0115] S403: Update the functionality of the specified software based on the code file of the specified software and the target software development kit file.

[0116] The executing entity here can be the software development platform of the software developer. The specified software can be software under development or software that has already been developed. The functional requirements information indicates what functions the specified software needs to be assigned. When the function to be assigned is to implement a specified business, the specified software's code files and target software development kit files (see the relevant descriptions in steps S301-S303 above) can be used to update the functions of the specified software. It can be understood that the function update here means: adding a function to implement the specified business based on the existing functions of the specified software; or replacing a similar or even identical function in the original functions with the function to implement the specified business. Of course, the specified software can also be software that is yet to be developed, and can be developed based on the target software development kit files.

[0117] In one exemplary embodiment, updating the functionality of the specified software based on the code file of the specified software and the target software development kit (SDK) file may include the following steps: First, determining the component compatibility information of the running device corresponding to the specified software; then, determining the setting information of the basic components in the development framework based on the target SSD file; wherein the setting information of the basic components indicates general basic components and component access interfaces for native basic components; furthermore, when the component compatibility information indicates that the running device rejects the general basic components, a target native basic component adapted to the running device is accessed based on the component access interface; next, the setting information of the basic components is updated based on the access relationship between the component access interface and the target native basic component to obtain an updated target SSD file; finally, updating the functionality of the specified software based on the code file of the specified software and the updated target SSD file.

[0118] The specified operating device is the device on which the specified software needs to be installed and run, such as a mobile phone, PC, or host. Based on the target software development kit file, the configuration information of the basic components in the development framework is determined; the configuration information of the basic components indicates the general basic components and the component access interfaces used for native basic component access. This can be referred to in the relevant description of "general basic components and component access interfaces used for native basic component access" in the aforementioned step S202.

[0119] When component compatibility information indicates that the running device rejects general-purpose basic components, the target native basic component adapted to the running device is accessed through the component access interface. Taking PS4 / 5 as an example, if the running device is incompatible with the general version of the basic component, a native basic component can be developed separately to adapt it through the component access interface.

[0120] Based on the connection relationship between the component access interface and the target native basic component, the configuration information of the basic component is updated to obtain the updated target software development kit (SDK) file. This allows for functional updates to the specified software based on the code files of the specified software and the updated target SSD file. For example... Figure 6 As shown, "General Basic Components" and "Component Access Interfaces for Native Basic Component Access" can be considered as two options provided by the development framework. Here, "Component Access Interfaces for Native Basic Component Access" is selectively enabled and the relevant configuration is saved. Compared to the settings for "General Basic Components" and "Component Access Interfaces for Native Basic Component Access" in the development framework in step S202 above, this provides a specific software development example to ensure the effective compatibility of the running device corresponding to the specified software with the basic components involved in the development framework, thereby improving the effectiveness of giving the specified software the function of implementing the specified business.

[0121] As can be seen from the technical solutions provided in the embodiments of this application above, the embodiments of this application utilize the code files of the specified software and the target software development kit (SDK) files to update the functions of the specified software. Based on the universality of the SSD, this saves the software developer the development workload and cost of assigning specified business functions to the specified software.

[0122] The following describes a specific embodiment of a business processing method according to this application. This application provides the method operation steps as shown in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operation steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only execution order. In actual system or product execution, the method can be executed sequentially according to the embodiments or accompanying drawings, or in parallel (e.g., in a parallel processor or multi-threaded processing environment). The method may include:

[0123] In response to a specified business request indicating a critical business function, the specified business request is processed based on the invoked interface and business logic.

[0124] In this embodiment, the business processing method is applied to a client. The client has the specified software updated in the development framework application method described in steps S401-S403 above installed. The specified software includes a target software development kit file indicating a specified business. The client receives a specified business request indicating a key business and processes the specified business request using a calling interface and business logic. This specified business request may be triggered by a target object (such as a tester, simulator, or online user). The key business belongs to the specified business. The calling interface and business logic indicate the business logic settings information of the development framework in the target software development kit file. The calling interface is configured for the key business. This can be combined with the relevant descriptions of "business logic," "key business," and "calling interface" in step S203 above. For example, the specified business request indicates a "query" business, a "shipping" business, etc. The specified business request is processed using the calling interface and business logic, that is, related operations are performed based on the information carried by the specified business request.

[0125] In practical applications, such as Figure 9-11 As shown, when the specified software integrates the payment function, it initiates the payment by calling the platform version's payment entry point. Then, the native layer entry point forwards the call directly to the standard payment process interfaces in Java, Objective-C, and C++, directly entering the cross-platform business logic layer. In this way, the implementation of key business processes is triggered by calling the standard payment process interface, placing control in the C++ layer and achieving the goal of unifying the business processes across various platforms.

[0126] In an exemplary embodiment, before processing the specified business request based on the calling interface and business logic, the method further includes the following steps: First, using an access layer to determine the programming language used by the specified business request; wherein, the access layer indicates the interface setting information of the development framework in the target software development kit file, and the access layer is used to convert and adapt the business request using the conflicting programming language based on preset calling rules; then, when the programming language used does not match the preset programming language, the access layer is used to convert and adapt the specified business request to obtain a target object, so as to send the target object to the calling interface.

[0127] This can be referenced in the relevant description of "access layer" in step S204 above, and will not be repeated here.

[0128] For example, platforms like the Switch and Xbox, which are developed in C, naturally support calling standard C++ payment process interfaces. However, accessing native C++ JNI methods on the Android platform is more complicated. See also... Figure 12 Based on the concept of object invocation, the access layer transforms and adapts the specified business requests from Java and Objective-C to obtain the target object (C++ object) to ensure the smooth implementation of critical business logic. This process may involve using IDL and leveraging proxy tools to automatically generate access layer code in Java, Objective-C, and C++. This unifies cross-language method calls into object invocation (scheduling), avoiding the redundancy of JNI and unifying the interface between Java and Objective-C.

[0129] Furthermore, such as Figure 5 As shown, the process of converting and adapting the specified business request to obtain the target object includes:

[0130] S501: Extract the specified service object and operation information from the specified service request; wherein, the operation information indicates the operation for the specified service object;

[0131] S502: Determine the target operation function using the preset programming language based on the operation information;

[0132] S503: Bind the specified business object and the target operation function to obtain the target object.

[0133] Based on the information carried in the specified business request, the specified business object and operation information are determined. Since the operation information comes from the specified business request, it can be regarded as an operation method that indicates behavior A using a non-preset programming language. The target operation function, which also indicates behavior A, is determined from this operation information. The specified business object and the target operation function are then bound together to obtain the target object. See also... Figure 12 This is equivalent to injecting and rebinding the upper-level object at the access layer. For example, by injecting the upper-level object into the C++ layer, calls to a specific C++ method can be made in both the Java and Objective-C layers. To maintain consistency in the interface parameters of the external layers, an object conversion and adaptation layer is introduced on top of the standard payment process interface, specifically responsible for object conversion and adaptation for the Android and iOS platforms.

[0134] As can be seen from the technical solutions provided in the embodiments of this application above, the embodiments of this application utilize API calls to process specified business requests indicating key business operations. Due to the definition of the API call, processes involving key business operations on different platforms can be managed and maintained in a unified manner, and the corresponding key logic (even business logic) can be unified into one, providing a reliable guarantee for the smooth implementation of key business operations.

[0135] This application also provides a development framework generation apparatus, such as... Figure 13 As shown, the development framework generation device 1300 includes:

[0136] Response module 1301: used to respond to application requirement information of a specified business and determine the corresponding component requirement information, business logic and compatibility requirement information; wherein, the compatibility objects indicated by the compatibility requirement information include at least one of the following: at least two types of devices, at least two types of operating systems and at least two types of programming languages;

[0137] Determining module 1302: used to determine the general basic components and the component access interfaces for native basic component access based on the compatibility requirement information and the component requirement information;

[0138] Call interface configuration module 1303: used to determine the key logic indicating the key business based on the business logic, and to configure the corresponding call interface for the key logic;

[0139] Framework generation module 1304: used to generate a development framework for the specified business based on the general basic components, the component access interface, the business logic and the calling interface.

[0140] It should be noted that the apparatus in the device embodiments and the related method embodiments are based on the same inventive concept.

[0141] This application embodiment also provides a development framework application apparatus, the apparatus comprising:

[0142] Framework acquisition module: used to acquire target framework data, wherein the target framework data indicates the development framework of a specified business, and the development framework indicating the specified business is generated using the development framework generation method described in steps S201-S204 above;

[0143] Server information acquisition module: used to acquire server information that supports the implementation of the specified business;

[0144] Toolkit generation module: Used to generate software development kit files corresponding to the specified business based on the target framework data and the server information.

[0145] It should be noted that the apparatus in the device embodiments and the related method embodiments are based on the same inventive concept.

[0146] This application embodiment also provides a development framework application apparatus, the apparatus comprising:

[0147] Requirements information acquisition module: used to acquire functional requirements information for a specified software;

[0148] Toolkit Acquisition Module: Used to acquire a target software development kit file when the functional requirement information indicates the implementation of a specified business. The target software development kit file is the software development kit file corresponding to the specified business generated in the development framework application method described in steps S301-S303 above.

[0149] Update module: Used to update the functionality of the specified software based on the code files of the specified software and the target software development kit files.

[0150] It should be noted that the apparatus in the device embodiments and the related method embodiments are based on the same inventive concept.

[0151] This application embodiment also provides a business processing device configured on a client, wherein the client has installed specified software updated as described in the development framework application method of steps S401-S403 above, the specified software including a target software development kit file indicating a specified business, and the device includes:

[0152] Business processing module: used to respond to a specified business request indicating a key business, and process the specified business request based on the calling interface and business logic; wherein, the key business belongs to the specified business, the calling interface and the business logic indicate the business logic setting information of the development framework in the target software development kit file, and the calling interface is configured for the key business.

[0153] It should be noted that the apparatus in the device embodiments and the related method embodiments are based on the same inventive concept.

[0154] This application provides an electronic device including a processor and a memory. The memory stores at least one instruction or at least one program segment. The at least one instruction or at least one program segment is loaded and executed by the processor to implement the development framework generation method, development framework application method, or business processing method provided in the above method embodiments.

[0155] Furthermore, Figure 14 A schematic diagram of the hardware structure of an electronic device for implementing the development framework generation method, development framework application method, or business processing method provided in the embodiments of this application is shown. The electronic device may participate in or include the development framework generation device, development framework application device, or business processing device provided in the embodiments of this application. Figure 14 As shown, the electronic device 100 may include one or more processors 1002 (shown as 1002a, 1002b, ..., 1002n in the figure) (processor 1002 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 1004 for storing data, and a transmission device 1006 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 14 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the electronic device 100 may also include... Figure 14 The more or fewer components shown, or having the same Figure 14 The different configurations shown.

[0156] It should be noted that the aforementioned one or more processors 1002 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be wholly or partially integrated into any other element within the electronic device 100 (or mobile device). As involved in the embodiments of this application, the data processing circuit serves as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0157] The memory 1004 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the development framework generation method, the development framework application method, or the business processing method described in the embodiments of this application. The processor 1002 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby implementing one of the aforementioned development framework generation methods, development framework application methods, or business processing methods. The memory 1004 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1004 may further include memory remotely located relative to the processor 1002, and these remote memories can be connected to the electronic device 100 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0158] The transmission device 1006 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the electronic device 100. In one example, the transmission device 1006 includes a network interface controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In one embodiment, the transmission device 1006 may be a radio frequency (RF) module for wireless communication with the Internet.

[0159] The display can be, for example, a touchscreen liquid crystal display (LCD) that allows a user to interact with the user interface of the electronic device 100 (or mobile device).

[0160] Embodiments of this application also provide a computer-readable storage medium, which can be disposed in an electronic device to store at least one instruction or at least one program related to implementing a development framework generation method, development framework application method or business processing method in the method embodiments. The at least one instruction or the at least one program is loaded and executed by the processor to implement the development framework generation method, development framework application method or business processing method provided in the above method embodiments.

[0161] Optionally, in this embodiment, the storage medium may be located in at least one of the multiple network servers in a computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0162] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, the above description focuses on specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired results. In some implementations, multitasking and parallel processing are also possible or may be advantageous.

[0163] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and electronic device embodiments are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0164] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0165] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.< / providecallback> < / paycallback> < / querycallback> < / initcallback>

Claims

1. A method for generating a development framework, characterized in that, The method includes: In response to the application requirement information of a specified business, the corresponding component requirement information, business logic and compatibility requirement information are determined. The compatibility object indicated by the compatibility requirement information consists of at least two conflicting sub-objects. The combination of the at least two conflicting sub-objects includes at least one of the following: at least two types of devices, at least two types of operating systems and at least two types of programming languages. Based on the component requirement information, determine the user interface components and the set of candidate basic components; Based on the basic components supported by each of the conflicting sub-objects, the support frequency of each basic component in the candidate basic component set is determined, and basic components with a support frequency equal to or higher than a threshold are determined as general basic components, and basic components with a support frequency lower than the threshold are determined as native basic components. The component access interface for accessing the native basic components is also determined. Based on the aforementioned business logic, the key logic indicating the key business is determined, and the corresponding calling interface is configured for the key logic; Guided by the hierarchical information, a development framework for the specified business is generated based on the user interface components, the general basic components, the component access interface, the business logic, and the calling interface. The hierarchical information indicates that the user interface components should be placed at a level closer to the user, and that the general basic components, the component access interface, the business logic, and the calling interface should be placed at a level closer to the machine.

2. The method according to claim 1, characterized in that: Before generating a development framework for the specified business based on the user interface components, the general basic components, the component access interface, the business logic, and the calling interface under the guidance of hierarchical information, the method further includes: When the at least two conflicting sub-objects are at least two types of programming languages, an access layer for programming language conversion is created. The access layer is used to convert and adapt business requests using conflicting programming languages ​​based on preset calling rules. Guided by hierarchical information, the process of generating a development framework for the specified business based on the user interface components, the general basic components, the component access interfaces, the business logic, and the calling interfaces includes: Guided by the hierarchical information, a development framework for the specified business is obtained based on the access layer, the user interface components, the general basic components, the component access interface, the business logic, and the calling interface. The hierarchical information also indicates that the access layer should be set at a level closer to the machine.

3. A development framework application method, characterized in that, The method includes: Obtain target framework data, wherein the target framework data indicates the development framework of a specified business, and the development framework indicating the specified business is generated using the development framework generation method as described in claim 1 or 2; Obtain server information that supports the implementation of the specified service; Based on the target framework data and the server information, a software development kit (SDK) file corresponding to the specified business is generated.

4. A development framework application method, characterized in that, The method includes: Obtain functional requirements information for a specified software; When the functional requirement information indicates that a specified business is to be implemented, the target software development kit file is obtained. The target software development kit file is the software development kit file corresponding to the specified business generated in the development framework application method as described in claim 3. The specified software is updated based on its code files and the target software development kit files.

5. The method according to claim 4, characterized in that, The function update of the specified software based on the code file of the specified software and the target software development kit file includes: Determine the component compatibility information of the running device corresponding to the specified software; Based on the target software development kit file, the configuration information of the basic components in the development framework is determined. The configuration information of the basic components indicates the general basic components and the component access interface for native basic component access. When the component compatibility information indicates that the operating device rejects the general basic component, the target native basic component adapted to the operating device is accessed based on the component access interface. Based on the access relationship between the component access interface and the target native basic component, the setting information of the basic component is updated to obtain the updated target software development kit file; The specified software is updated based on its code files and the updated target software development kit files.

6. A business processing method, characterized in that, Applied to a client, the client having installed the specified software updated in the development framework application method as described in claim 4 or 5, the specified software including a target software development kit file indicating a specified business, the method comprising: In response to a specified business request indicating a critical business, the specified business request is processed based on a calling interface and business logic. The critical business belongs to the specified business. The calling interface and the business logic indicate the business logic settings information of the development framework in the target software development kit file. The calling interface is configured for the critical business.

7. The method according to claim 6, characterized in that, Before processing the specified business request based on the API call and business logic, the method further includes: The access layer determines the programming language used by the specified business request. The access layer indicates the interface setting information of the development framework in the target software development kit file. The access layer is used to convert and adapt business requests using conflicting programming languages ​​based on preset calling rules. When the programming language used does not match the preset programming language, the access layer is used to convert and adapt the specified business request to obtain the target object, and then the target object is sent to the calling interface.

8. The method according to claim 7, characterized in that, The process of converting and adapting the specified business request to obtain the target object includes: Extract a specified business object and operation information from the specified business request, wherein the operation information indicates the operation for the specified business object; Based on the operation information, determine the target operation function using the preset programming language; The target object is obtained by binding the specified business object and the target operation function.

9. A development framework generation device, characterized in that, The device includes: Response module: Used to respond to application requirement information of a specified business, determine the corresponding component requirement information, business logic and compatibility requirement information. The compatibility object indicated by the compatibility requirement information consists of at least two conflicting sub-objects. The combination of the at least two conflicting sub-objects includes at least one of the following: at least two types of devices, at least two types of operating systems and at least two types of programming languages. Determination module: used to determine user interface components and candidate basic component sets based on the component requirement information; based on the basic components supported by each conflicting sub-object, determine the support frequency of each basic component in the candidate basic component set, and determine that basic components with a support frequency equal to or higher than a threshold are general basic components, and basic components with a support frequency lower than the threshold are native basic components, and determine the component access interface for the access of the native basic components; Call interface configuration module: used to determine the key logic indicating key business based on the business logic, and to configure the corresponding call interface for the key logic; Framework generation module: Guided by hierarchical information, it generates a development framework for the specified business based on the user interface components, the general basic components, the component access interface, the business logic, and the calling interface. The hierarchical information indicates that the user interface components should be placed at a level closer to the user, and that the general basic components, the component access interface, the business logic, and the calling interface should be placed at a level closer to the machine.

10. The apparatus according to claim 9, characterized in that: The device also includes an access layer creation module; The access layer creation module is used to create an access layer for programming language conversion when the at least two conflicting sub-objects are at least two types of programming languages. The access layer is used to convert and adapt business requests using conflicting programming languages ​​based on preset calling rules. The framework generation module is further configured to, under the guidance of hierarchical information, obtain a development framework for the specified business based on the access layer, the user interface components, the general basic components, the component access interface, the business logic, and the calling interface. The hierarchical information also indicates that the access layer should be set at a level closer to the machine.

11. A development framework application device, characterized in that, The device includes: Framework acquisition module: used to acquire target framework data, wherein the target framework data indicates the development framework of a specified business, and the development framework indicating the specified business is generated using the development framework generation method as described in claim 1 or 2; Server information acquisition module: used to acquire server information that supports the implementation of the specified business; Toolkit generation module: Used to generate software development kit files corresponding to the specified business based on the target framework data and the server information.

12. A development framework application device, characterized in that, The device includes: Requirements information acquisition module: used to acquire functional requirements information for a specified software; Toolkit Acquisition Module: Used to acquire a target software development kit file when the functional requirement information indicates the implementation of a specified business, wherein the target software development kit file is the software development kit file corresponding to the specified business generated in the development framework application method as described in claim 3; Update module: Used to update the functionality of the specified software based on the code files of the specified software and the target software development kit files.

13. The apparatus according to claim 12, characterized in that, The update module is further configured to: determine the component compatibility information of the running device corresponding to the specified software; and, based on the target software development kit file, determine the setting information of the basic components in the development framework, wherein the setting information of the basic components indicates the general basic components and the component access interface for native basic component access; When the component compatibility information indicates that the operating device rejects the general basic component, the target native basic component adapted to the operating device is accessed based on the component access interface. Based on the access relationship between the component access interface and the target native basic component, the setting information of the basic component is updated to obtain the updated target software development kit file; The specified software is updated based on its code files and the updated target software development kit files.

14. A business processing apparatus, characterized in that, Configured on a client, the client having installed the specified software updated in the development framework application method as described in claim 4 or 5, the specified software including a target software development kit file indicating a specified business, the apparatus comprising: Business processing module: Used to respond to a specified business request that indicates a key business, process the specified business request based on the calling interface and business logic, wherein the key business belongs to the specified business, the calling interface and the business logic indicate the business logic setting information of the development framework in the target software development kit file, and the calling interface is configured for the key business.

15. The apparatus according to claim 14, characterized in that, The device also includes a conversion and adaptation module; The conversion and adaptation module is used to determine the programming language used by the specified business request using the access layer. The access layer indicates the interface setting information of the development framework in the target software development kit file. The access layer is used to convert and adapt business requests using conflicting programming languages ​​based on preset calling rules. When the programming language used does not match the preset programming language, the access layer is used to convert and adapt the specified business request to obtain a target object, and the target object is sent to the calling interface.

16. The apparatus according to claim 15, characterized in that, The step of converting and adapting the specified business request to obtain the target object includes: extracting a specified business object and operation information from the specified business request, wherein the operation information indicates an operation for the specified business object; determining a target operation function using the preset programming language based on the operation information; and binding the specified business object and the target operation function to obtain the target object.

17. An electronic device, characterized in that, The electronic device includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the development framework generation method as described in any one of claims 1-2, the development framework application method as described in claim 3, the development framework application method as described in any one of claims 4-5, or the business processing method as described in any one of claims 6-8.

18. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction or at least one program segment, which is loaded and executed by a processor to implement the development framework generation method as described in any one of claims 1-2, the development framework application method as described in claim 3, the development framework application method as described in any one of claims 4-5, or the business processing method as described in any one of claims 6-8.

19. A computer program product, characterized in that, The computer program product includes at least one instruction or at least one program segment, which is loaded and executed by a processor to implement the development framework generation method as described in any one of claims 1-2, the development framework application method as described in claim 3, the development framework application method as described in any one of claims 4-5, or the business processing method as described in any one of claims 6-8.

Images