Data calling method and device for target platform, equipment and storage medium

The functional data of the target platform is obtained through the combination interface, which solves the problem of inconsistent interface languages ​​in game SDK docking, improves efficiency and reduces costs, and realizes functional data transmission consistent with the development-side programming language.

CN119025232APending Publication Date: 2024-11-26广州三七极创网络科技有限公司
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202410901831.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-05
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

During the game SDK docking process, due to the inconsistent interface languages ​​of each platform or system, R&D personnel need to conduct sufficient communication and learning, which affects the docking efficiency and increases costs.

Method used

通过获取客户端发送的游戏代码、目标平台标识和调用事件,确定代码语言和接口类型,组合第一和第二调用接口以形成目标转调接口,直接获取目标平台的功能数据,避免语言转换和实例代码学习。

Benefits of technology

It improves the docking efficiency and data call efficiency of the game SDK, reduces the docking cost, and avoids communication and learning needs between R&D personnel.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025232A_ABST
    Figure CN119025232A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a data calling method and device for a target platform, equipment and a storage medium, and the method comprises the steps: obtaining a game code, a target platform identifier and a calling event sent by a client, and determining a code language of the game code and an interface type corresponding to the calling event; determining a first calling interface according to the interface type and the code language, and determining a second calling interface according to the target platform identifier and the interface type; and performing interface combination on the first calling interface and the second calling interface to obtain a target modulation interface, obtaining function data corresponding to the target modulation interface in a target platform through the target modulation interface, and sending the function data to the client. The docking efficiency of the game SDKs is improved, and the docking cost of the game SDKs is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a method, device, equipment and storage medium for calling data on a target platform. Background Art

[0002] Game development docking refers to the process of connecting and interacting games with other systems or platforms. It may involve docking the game development platform with third-party platforms and docking between systems of multiple business departments. The purpose of game development docking is to increase the functionality and entertainment of the game, improve the user experience, and expand the audience of the game. Game SDK (Software Development Kit) is an integrated development environment that allows developers to dock and integrate games more easily during the game development docking process. Game SDK usually contains game API, sample code and development tools. Developers can use these tools and resources to speed up the development process.

[0003] In the related technologies, whether it is the game SDK docking with a third-party platform or the game SDK docking between business departments, there will be inconsistencies in the interface languages ​​of the docking interfaces of each platform or system. Therefore, in the process of game SDK docking, sufficient communication and learning are required between R&D personnel, which affects the docking efficiency and R&D efficiency of the game SDK and increases the cost of game SDK docking. Summary of the invention

[0004] The embodiments of the present application provide a data calling method, device, equipment and storage medium for a target platform, which solves the problem that during the game SDK docking process, sufficient communication and learning between R&D personnel are required, thereby affecting the docking efficiency of the game SDK and increasing the docking cost of the game SDK. The docking efficiency of the game SDK is improved and the docking cost of the game SDK is reduced.

[0005] In a first aspect, an embodiment of the present application provides a data calling method of a target platform, comprising:

[0006] Obtain the game code, target platform identifier and call event sent by the client, and determine the code language of the game code and the interface type corresponding to the call event;

[0007] Determine a first calling interface according to the interface type and the code language, and determine a second calling interface according to the target platform identifier and the interface type;

[0008] The first calling interface and the second calling interface are combined to obtain a target transfer interface, and functional data corresponding to the target transfer interface in the target platform is obtained through the target transfer interface, and the functional data is sent to the client.

[0009] Optionally, combining the first calling interface and the second calling interface comprises:

[0010] The interface address of the second calling interface is queried, and the service address parameter of the first calling interface is set to the interface address to implement interface combination.

[0011] Optionally, acquiring function data corresponding to the target transfer interface in the target platform through the target transfer interface, and sending the function data to the client includes:

[0012] A target call instruction is sent to the target platform through the target transfer interface to obtain function data associated with the target call instruction in the target platform, the function data is called back to the target engine through the monitoring module, and the function data is sent to the client through the target engine.

[0013] Optionally, the calling instruction includes a layer identifier and a calling module identifier, and the step of sending the target calling instruction to the target platform through the target transfer interface to obtain function data associated with the target calling instruction in the target platform includes:

[0014] A target calling instruction is sent to the target platform through the target transfer interface, so that the target platform determines the service line to be called based on the layer identifier and the calling module identifier, and returns the function data associated with the service line to be called.

[0015] Optionally, after returning the function data associated with the to-be-called business line, the method further includes:

[0016] Determine the data volume of the functional data, compare the data volume with a preset target data volume, and if the data volume is different from the preset target data volume, perform interface expansion based on the target platform identifier to obtain a target platform extension interface, and obtain the newly added functional data of the target platform based on the target platform extension interface.

[0017] Optionally, after obtaining the target transfer interface, the method further includes:

[0018] According to the interface type and the preset input parameter rule, the target transfer interface is processed with input parameter specification to obtain a standardized input parameter interface, and according to the interface type and the preset output parameter rule, the target transfer interface is processed with output parameter specification to obtain a standardized output parameter interface;

[0019] The function data corresponding to the target transfer interface in the target platform is obtained through the standard input parameter interface and the standard output parameter interface.

[0020] Optionally, the acquiring, through the standard input parameter interface and the standard output parameter interface, function data corresponding to the target transfer interface in the target platform includes:

[0021] Sending a target call instruction to the target platform through the standard input parameter interface to obtain function data associated with the target call instruction in the target platform;

[0022] The function data is monitored through the monitoring module, and the monitored function data is called back to the target engine through the standard output parameter interface.

[0023] In a second aspect, an embodiment of the present application provides a data calling device for a target platform, including:

[0024] The data acquisition module is used to obtain the game code, target platform identifier and call event sent by the client;

[0025] A type determination module, used to determine the code language of the game code and the interface type corresponding to the call event;

[0026] An interface determination module, used to determine a first calling interface according to the interface type and the code language, and to determine a second calling interface according to the target platform identifier and the interface type;

[0027] An interface combination module, used for combining the first calling interface and the second calling interface to obtain a target transfer interface;

[0028] The data acquisition module is further used to acquire the function data corresponding to the target transfer interface in the target platform through the target transfer interface;

[0029] A data sending module is used to send the functional data to the client.

[0030] In a third aspect, an embodiment of the present application provides a data calling device for a target platform, the device comprising: one or more processors; a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the data calling method for the target platform described in the first aspect.

[0031] In a fourth aspect, an embodiment of the present application provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to execute the data calling method of the target platform as described in the first aspect.

[0032] The embodiment of the present application determines the code language of the game code and the interface type corresponding to the call event by obtaining the game code, target platform identification and call event sent by the client; determines the first call interface according to the interface type and code language, and determines the second call interface according to the target platform identification and interface type; combines the first call interface and the second call interface to obtain a target transfer interface, obtains the functional data of the corresponding target transfer interface in the target platform through the target transfer interface, and sends the functional data to the client. During the data docking process, the client does not need to consider learning the programming language of the target platform, and does not need to consider the specific content of the instance code in the game SDK. The corresponding target transfer interface is directly determined based on the demand data sent by the client, so that the functional data consistent with the programming language of the development end will be obtained based on the target transfer interface, avoiding the communication and learning between the game developers and the developers of the target platform during the game SDK docking process. The calling efficiency of data is improved, and the docking efficiency of data in the research and development process is correspondingly improved, and the docking cost of the game SDK is reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 It is a flow chart of a data calling method of a target platform provided in an embodiment of the present application;

[0034] Figure 2 is a flow chart of a method for acquiring functional data provided by an embodiment of the present application;

[0035] Figure 3 It is a layered architecture diagram of an Android platform provided in an embodiment of the present application;

[0036] Figure 4 It is a flow chart of a standard processing method of a target transfer interface provided by an embodiment of the present application;

[0037] Figure 5 It is a structural schematic diagram of a data calling device for a target platform provided in an embodiment of the present application;

[0038] Figure 6 It is a structural diagram of a data calling device for a target platform provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical scheme and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for the convenience of description, only the part related to the present application but not all the contents are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow chart describes each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.

[0040] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

[0041] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0042] The data calling method, device, equipment and medium of the target platform provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings through specific embodiments and their application scenarios.

[0043] The target platform data calling method provided in the embodiment of the present application can be applied to the scenario where developers connect to SDKs of different target platforms. It aims to determine the corresponding transfer interface and implement data calling of different programming languages ​​through the transfer interface, thereby avoiding the inconsistency between the code language used by the development terminal and the code language used by the target platform, and the need for corresponding communication during the SDK docking process, resulting in the problem of high SDK docking costs. Based on the above application scenarios, it can be understood that the execution subject of this solution can be a server.

[0044] Figure 1 is a flow chart of a data calling method for a target platform provided in an embodiment of the present application, such as Figure 1 As shown, including:

[0045] Step S101: Obtain the game code, target platform identifier and call event sent by the client, and determine the code language of the game code and the interface type corresponding to the call event.

[0046] Among them, the target platform identifier can be the platform name of the SDK docking platform, such as the Android platform and the IOS platform. The call event can be used to represent the call behavior of the data, and the call event is determined by the user's selection operation on the client's page, such as login, payment, account switching, and character upgrade. The code language can be the programming language of the game code, such as c# language, java language, etc. The interface type is determined according to the pre-set call event, and one call event corresponds to one interface type. If the pre-set call event is a login event, the corresponding interface type is a login interface. Correspondingly, if the call event is a payment event, the corresponding interface type is a payment interface. In one embodiment, the game code, target platform identifier and call event sent by the client are obtained, and the code language of the game code and the interface type corresponding to the call event are determined.

[0047] Step S102: determining a first calling interface according to the interface type and the code language, and determining a second calling interface according to the target platform identifier and the interface type.

[0048] The first calling interface may be a data interface of the server, and the second calling interface may be a data interface of the target platform. In one embodiment, the data interface of the server to be called is determined according to the determined interface type and code language, and the data interface of the target platform to be called is determined according to the determined target platform identifier and interface type. Exemplarily, if the interface type is a login interface, the code language is C#, and the target platform identifier is an Android platform, then the first calling interface is determined to be a login interface of the server in C# language, and the second calling interface is determined to be a login interface of the Android platform.

[0049] Step S103: Combine the first calling interface and the second calling interface to obtain a target transfer interface, obtain function data corresponding to the target transfer interface in the target platform through the target transfer interface, and send the function data to the client.

[0050] The interface combination may refer to a combined call of interfaces, such as calling the first calling interface first and then calling the second calling interface. The first calling interface and the second calling interface may also be connected in series to generate a bidirectional interface that includes both an input parameter interface and an output parameter interface, namely, a target transfer interface. Functional data is used to represent the specific implementation data of the SDK (Software Development Kit). In one embodiment, the calling process of the functional data of the target platform is the docking process of the target platform SDK. The types of functional data obtained in different interfaces are different. If the interface type is a payment type interface, the functional data obtained from the payment interface may include product ID, product name, service ID, service name, character name, and character level, etc. In one embodiment, the first calling interface and the second calling interface are connected in series to obtain a target transfer interface, and the functional data corresponding to the target transfer interface is obtained through the target transfer interface, and the obtained functional data is sent to the client. Exemplarily, if the first calling interface is the server's C# language login interface, and the second calling interface is the Android platform's login interface, the login function data in the Android platform is obtained through the target conversion interface. If the programming language of the Android platform is Java, the target conversion interface can be used to implement C# language calling the Java language's login function data, so that the acquired Android platform's login function data is C# language data, and the C# language function data is sent to the client, so that the code language of the function data received by the client is consistent with the client's game development language.

[0051] As described above, by obtaining the game code, target platform identifier and call event sent by the client, the code language of the game code and the interface type corresponding to the call event are determined; the first call interface is determined according to the interface type and code language, and the second call interface is determined according to the target platform identifier and interface type; the first call interface and the second call interface are combined to obtain a target transfer interface, and the functional data of the corresponding target transfer interface in the target platform is obtained through the target transfer interface, and the functional data is sent to the client. During the data docking process, the client does not need to consider learning the programming language of the target platform, and does not need to consider the specific content of the instance code in the game SDK. The corresponding target transfer interface is directly determined based on the demand data sent by the client, so that the functional data consistent with the programming language of the development end is obtained based on the target transfer interface, which avoids the communication and learning between the game developers and the developers of the target platform during the game SDK docking process. The efficiency of data calling is improved, and the efficiency of data docking in the development process is correspondingly improved, and the docking cost of the game SDK is reduced.

[0052] In one embodiment, combining the first calling interface and the second calling interface comprises:

[0053] The interface address of the second calling interface is queried, and the service address parameter of the first calling interface is set to the interface address to implement interface combination.

[0054] Among them, the interface address is the IP configured on the network device interface, which is to be associated with the port. The service address truly represents the logical IP address of the service, such as the DNS service address, NTP service address, MME's S6a service address, etc., and a certain service or function can be obtained by accessing this address. The first calling interface and the second calling interface both contain corresponding control information, address information and data information. The address information may include the interface address and the service address. After determining the second calling interface, query the interface address of the second calling interface and the service address of the first calling interface, and set the service address parameter of the first calling interface to the interface address of the second calling interface, thereby realizing the series connection of the first calling interface and the second calling interface.

[0055] In the above, by querying the interface address of the second calling interface, the service address parameter of the first calling interface is set to the interface address to realize interface combination. Functional data that meets the client development requirements can be directly output through interface combination, avoiding language conversion of functional data during transmission, and improving data calling efficiency.

[0056] Figure 2 is a flow chart of a method for obtaining functional data provided by an embodiment of the present application, such as Figure 2 As shown, including:

[0057] Step S201: Obtain the game code, target platform identifier and call event sent by the client, and determine the code language of the game code and the interface type corresponding to the call event.

[0058] Step S202: determine a first calling interface according to the interface type and the code language, and determine a second calling interface according to the target platform identifier and the interface type.

[0059] Step S203: Combine the first calling interface and the second calling interface to obtain a target transfer interface.

[0060] Step S204: sending a target call instruction to the target platform through the target transfer interface to obtain function data associated with the target call instruction in the target platform, calling back the function data to the target engine through the monitoring module, and sending the function data to the client through the target engine.

[0061] Among them, the target call instruction is used to represent the call instruction for the target data in the target platform, that is, the instruction to start calling the target data. In one embodiment, the function data associated with the method name can be determined according to the method name in the target call instruction. The method name is determined according to the type of interface or the type of function data. For example, if the target call instruction is ".Call("login", "")", then the login function data associated with the target call instruction is called. The monitoring module is a component for monitoring specific events and performing corresponding operations, which can realize communication between pages, between users and servers, and within applications. The target engine can be a unity engine, which is a cross-platform game development engine developed by Unity Technologies, which can provide a comprehensive development platform for creating high-quality games and interactive virtual experiences. The Unity engine supports multiple platforms, including Windows, Mac, Linux, iOS, Android, etc. It enables developers to publish games to multiple platforms with less workload and expand the audience range of the game. In one embodiment, a target call instruction is sent to a target platform through a target transfer interface, thereby obtaining function data associated with the target call instruction, monitoring the function data through a monitoring module, and sending the monitored function data to the target engine for callback, so that the target engine sends the function data to the client for display through a unified interface, so that the client receives the function data in a unified language. In another possible embodiment, after the monitoring module monitors the corresponding function data, the corresponding function data obtained from each target platform is stored in a callback file, the callback file is sent to the target engine through the target transfer interface, and then the callback file is sent to the client through the target engine.

[0062] In the above, the target call instruction is sent to the target platform through the target transfer interface to obtain the function data associated with the target call instruction in the target platform, the function data is called back to the target engine through the monitoring module, and the function data is sent to the client through the target engine. The monitoring module can obtain the function data associated with the target call instruction in real time, and the obtained function data can be uniformly stored in the callback file, and the callback file can be sent to the client, so that the client can receive function data from different target platforms or different types at the same time, thereby further improving the efficiency of data calling.

[0063] In one embodiment, the calling instruction includes a hierarchical identifier and a calling module identifier, and the step of sending the target calling instruction to the target platform through the target transfer interface to obtain function data associated with the target calling instruction in the target platform includes:

[0064] A target calling instruction is sent to the target platform through the target transfer interface, so that the target platform determines the service line to be called based on the layer identifier and the calling module identifier, and returns the function data associated with the service line to be called.

[0065] The hierarchical identifier can be used to represent the hierarchical architecture of the target platform, and the hierarchical identifier can include a display layer identifier and a specific implementation layer identifier. The calling module identifier is used to represent different business systems in the target platform, and different business systems respectively include a business display layer and a specific implementation layer. For example, Figure 3 is a layered architecture diagram of an Android platform provided in an embodiment of the present application, such as Figure 3 As shown, if the target platform is an Android platform, which may include online game Android, mobile game Android and Games Android systems, correspondingly, the calling module identifier can identify the online game Android module, the mobile game Android module and the Games Android module respectively, wherein the online game Android module includes the display layer identifier of the online game Android and the specific implementation layer identifier of the online game Android, correspondingly, the mobile game Android module includes the display layer identifier of the mobile game Android and the specific implementation layer identifier of the mobile game Android, and the Games Android module includes the display layer identifier of the Games Android and the specific implementation layer identifier of the Games Android. The business line to be called is used to represent the calling path of the function in the module to be called, such as calling the business display layer in the online game Android to retrieve the function data of the specific implementation layer, which can be expressed as online game Android-online game display layer-online game specific implementation layer. In one embodiment, a target call instruction is sent to the target platform through the target transfer interface, so that the target platform determines the business line to be called, that is, the business module to be called, based on the layer identifier and the calling module identifier in the target call instruction, and obtains the function data associated with each business line to be called respectively, and returns the function data of the business line to be called to the server respectively. Exemplarily, if the target calling instruction includes the online game display layer and the online game specific implementation layer of the online game Android module and the mobile game display layer and the mobile game business specific display layer of the mobile game Android module, it can be determined that the business lines to be called are online game Android-online game display layer-online game specific implementation layer and mobile game Android-mobile game display layer-mobile game specific implementation layer, respectively, and according to the above business lines, the Android online game function data of the online game specific implementation layer and the Android mobile game function data of the mobile game specific implementation layer are respectively obtained, thereby returning the Android online game function data and the Android mobile game function data to the target engine respectively.

[0066] As described above, a target call instruction is sent to the target platform through the target transfer interface, so that the target platform determines the business line to be called based on the hierarchical identifier and the calling module identifier, and returns the functional data associated with the business line to be called. The location of the functional data to be called in the target platform can be accurately determined through the hierarchical identifier and the calling module identifier, thereby improving the accuracy of the target data call, and correspondingly improving the efficiency of game development.

[0067] In one embodiment, after returning the function data associated with the to-be-called service line, the method further includes:

[0068] Determine the data volume of the functional data, compare the data volume with a preset target data volume, and if the data volume is different from the preset target data volume, perform interface expansion based on the target platform identifier to obtain a target platform extension interface, and obtain the newly added functional data of the target platform based on the target platform extension interface.

[0069] For example, after obtaining the functional data, the data volume of the functional data is determined, and the data volume of the functional data is compared with the target data volume. If the data volume of the functional data is different from the preset target data volume, it means that the obtained functional data is incomplete or does not meet the R&D needs of the R&D personnel. There may be other business lines to be called, and the business lines to be called are determined, so it is necessary to expand the interface of the target platform. Optionally, during the interface expansion process, the expansion can be performed based on the target platform identifier to obtain the target platform expansion interface, thereby obtaining the newly added functional data of the target platform based on the target platform expansion interface, so that the received functional data meets the R&D needs of the R&D personnel.

[0070] In the above, by determining the data volume of the functional data, the data volume is compared with the preset target data volume. When the data volume is different from the preset target data volume, the interface is extended based on the target platform identifier to obtain the target platform extension interface, and the newly added functional data of the target platform is obtained based on the target platform extension interface. The functional data can be verified by comparing the data volume of the functional data with the preset target data volume, thereby obtaining complete R&D data based on the extended interface, thereby ensuring the integrity of the data and the R&D effect.

[0071] Figure 4 is a flowchart of a standard processing method for a target transfer interface provided by an embodiment of the present application, such as Figure 4 As shown, including:

[0072] Step S401, perform input parameter specification processing on the target transfer interface according to the interface type and preset input parameter rules to obtain a standardized input parameter interface, and perform output parameter specification processing on the target transfer interface according to the interface type and preset output parameter rules to obtain a standardized output parameter interface.

[0073] The preset input parameter rule may be a preset unified input parameter naming specification, and correspondingly, the input parameter specification processing is the standard processing of interface naming of the input parameter interface. The preset output parameter rule may be a preset unified output parameter naming specification, and correspondingly, the output parameter specification processing is the standard processing of interface naming of the output parameter interface. In one embodiment, the input parameter interface and the output parameter interface may be the same data interface, that is, both are target transfer interfaces, and the difference is that the interface name used when inputting parameters is different from the interface name used when outputting parameters. In another embodiment, the target transfer interface is subjected to input parameter specification processing according to the interface type and the preset input parameter rule. Exemplarily, the naming rule of the input parameter interface is XXXInfo, such as representing the input parameter specification class name is ˋMaxSDKLoginInfoˋ. The naming rule of the output parameter interface is XXXBean, such as representing the return parameter specification class name is ˋMaxSDKBeanˋ. Optionally, the parameters returned by multiple different interfaces can be uniformly encapsulated in the ˋMaxSDKBean.csˋ file.

[0074] Step S402: Acquire the function data corresponding to the target transfer interface in the target platform through the standard input parameter interface and the standard output parameter interface.

[0075] In one embodiment, a target call instruction is sent to the target platform by calling a standard input parameter interface, and function data from the target platform is received by using a substitute standard output parameter interface, thereby avoiding inconsistent naming of the input parameter interfaces and affecting the efficiency of the target platform in determining the corresponding function data. It can also avoid inconsistent naming of the output parameter interfaces and affecting the efficiency of developers in using the corresponding function data, thereby affecting development efficiency.

[0076] In one embodiment, the acquiring the function data corresponding to the target transfer interface in the target platform through the standard input parameter interface and the standard output parameter interface includes:

[0077] Sending a target call instruction to the target platform through the standard input parameter interface to obtain function data associated with the target call instruction in the target platform;

[0078] The function data is monitored through the monitoring module, and the monitored function data is called back to the target engine through the standard output parameter interface.

[0079] The specific method of obtaining the function data associated with the target call instruction in the target platform based on the standard input parameter interface and the standard output parameter interface, monitoring the function data through the monitoring module, and calling back the monitored function data to the target engine through the standard output parameter interface can be referred to step S204, which will not be repeated here. This method of obtaining the corresponding function data can not only ensure the efficiency of calling the function data by monitoring the function data through the monitoring module, but also avoid the interface parameters of the target transfer interface being non-standard, affecting the calling efficiency of the function data, and further improving the docking efficiency of the function data.

[0080] Figure 5 is a structural diagram of a data calling device for a target platform provided in an embodiment of the present application, such as Figure 5 As shown, including:

[0081] The data acquisition module 51 is used to acquire the game code, target platform identifier and call event sent by the client;

[0082] A type determination module 52, used to determine the code language of the game code and the interface type corresponding to the call event;

[0083] An interface determination module 53, configured to determine a first calling interface according to the interface type and the code language, and to determine a second calling interface according to the target platform identifier and the interface type;

[0084] An interface combining module 54, used for combining the first calling interface and the second calling interface to obtain a target transfer interface;

[0085] The data acquisition module 55 is further used to acquire the function data corresponding to the target transfer interface in the target platform through the target transfer interface;

[0086] The data sending module 56 is used to send the functional data to the client.

[0087] The embodiment of the present application determines the code language of the game code and the interface type corresponding to the call event by obtaining the game code, target platform identification and call event sent by the client; determines the first call interface according to the interface type and code language, and determines the second call interface according to the target platform identification and interface type; combines the first call interface and the second call interface to obtain a target transfer interface, obtains the functional data of the corresponding target transfer interface in the target platform through the target transfer interface, and sends the functional data to the client. During the data docking process, the client does not need to consider learning the programming language of the target platform, and does not need to consider the specific content of the instance code in the game SDK. The corresponding target transfer interface is directly determined based on the demand data sent by the client, so that the functional data consistent with the programming language of the development end will be obtained based on the target transfer interface, avoiding the communication and learning between the game developers and the developers of the target platform during the game SDK docking process. The calling efficiency of data is improved, and the docking efficiency of data in the research and development process is correspondingly improved, and the docking cost of the game SDK is reduced.

[0088] In a possible embodiment, the interface combination module 54 is specifically used for:

[0089] The interface address of the second calling interface is queried, and the service address parameter of the first calling interface is set to the interface address to implement interface combination.

[0090] In a possible embodiment, the data acquisition module 55 is specifically used for:

[0091] Sending a target calling instruction to a target platform through the target transfer interface to obtain function data associated with the target calling instruction in the target platform;

[0092] The data sending module 56 is specifically used for:

[0093] The function data is called back to the target engine through the monitoring module, and the function data is sent to the client through the target engine.

[0094] In a possible embodiment, the data acquisition module 55 is further configured to:

[0095] A target calling instruction is sent to the target platform through the target transfer interface, so that the target platform determines the service line to be called based on the layer identifier and the calling module identifier, and returns the function data associated with the service line to be called.

[0096] In a possible embodiment, the data calling device of the target platform further includes an interface expansion module, and the interface expansion module is used to:

[0097] Determine the data volume of the functional data, compare the data volume with the total data volume of the target transfer interface, and if the data volume is different from the total data volume, perform interface extension based on the target platform identifier to obtain a target platform extension interface;

[0098] The data acquisition module 55 is also used for:

[0099] Newly added function data of the target platform is acquired based on the target platform extension interface.

[0100] In a possible embodiment, the data calling device of the target platform further includes an interface specification module, and the interface specification module is used to:

[0101] The target transfer interface is processed for input parameters in a standardized manner according to the interface type and preset input parameter rules to obtain a standardized input parameter interface, and the target transfer interface is processed for output parameters in a standardized manner according to the interface type and preset output parameter rules to obtain a standardized output parameter interface.

[0102] The data acquisition module 55 is also specifically used for:

[0103] The function data corresponding to the target transfer interface in the target platform is obtained through the standard input parameter interface and the standard output parameter interface.

[0104] In a possible embodiment, the data acquisition module 55 is further used to:

[0105] Sending a target call instruction to the target platform through the standard input parameter interface to obtain function data associated with the target call instruction in the target platform;

[0106] The function data is monitored through the monitoring module, and the monitored function data is called back to the target engine through the standard output parameter interface.

[0107] The embodiment of the present application also provides a data calling device for a target platform, and the data calling device for the target platform can be integrated with a data calling apparatus for a target platform provided in the embodiment of the present application. Figure 6 Schematic diagram of a data calling device for a target platform provided in an embodiment of the present application. Figure 6 The target platform data calling device includes: an input device 63, an output device 64, a memory 62 and one or more processors 61; the memory 62 is used to store one or more programs; when one or more programs are executed by one or more processors 61, the one or more processors 61 implement the target platform data calling method provided by the above embodiment. The input device 63, the output device 64, the memory 62 and the processor 61 can be connected by a bus or other means. Figure 6 The example of connecting through bus is taken in the following.

[0108] The memory 62, as a computing device readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the data calling method of the target platform provided in any embodiment of the present application. The memory 62 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the device, etc. In addition, the memory 62 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 62 may further include a memory remotely arranged relative to the processor 61, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0109] The input device 63 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the device. The output device 64 may include a display device such as a display screen.

[0110] The processor 61 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 62, that is, realizes the data calling method of the above-mentioned target platform.

[0111] The target platform data calling device, equipment and computer provided above can be used to execute the target platform data calling method provided in any of the above embodiments, and have corresponding functions and beneficial effects.

[0112] The present application also provides a storage medium storing computer executable instructions. When the computer executable instructions are executed by a computer processor, they are used to execute the data calling method of the target platform provided in the above embodiment. The data calling method based on the target platform includes:

[0113] Obtain the game code, target platform identifier and call event sent by the client, and determine the code language of the game code and the interface type corresponding to the call event;

[0114] Determine a first calling interface according to the interface type and the code language, and determine a second calling interface according to the target platform identifier and the interface type;

[0115] The first calling interface and the second calling interface are combined to obtain a target transfer interface, and functional data corresponding to the target transfer interface in the target platform is obtained through the target transfer interface, and the functional data is sent to the client.

[0116] Storage medium - any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROM, floppy disk or tape device; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements, etc. Storage media may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system, which is connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations (for example, in different computer systems connected by a network). The storage medium may store program instructions (for example, embodied as a computer program) that can be executed by one or more processors.

[0117] Of course, the storage medium containing computer executable instructions provided in an embodiment of the present application is not limited to the data calling method of the target platform as described above, and can also execute related operations in the data calling method of the target platform provided in any embodiment of the present application.

[0118] The target platform-based data calling apparatus, device and storage medium provided in the above embodiments can execute the target platform data calling method provided in any embodiment of the present application. For technical details not described in detail in the above embodiments, please refer to the target platform data calling method provided in any embodiment of the present application.

[0119] The above are only preferred embodiments of the present application and the technical principles used. The present application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not deviate from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the claims.

Claims

1. A data calling method for a target platform, characterized in that: include: Obtain the game code, target platform identifier and call event sent by the client, and determine the code language of the game code and the interface type corresponding to the call event; Determine a first calling interface according to the interface type and the code language, and determine a second calling interface according to the target platform identifier and the interface type; The first calling interface and the second calling interface are combined to obtain a target transfer interface, and functional data corresponding to the target transfer interface in the target platform is obtained through the target transfer interface, and the functional data is sent to the client.

2. The target platform data calling method according to claim 1, characterized in that: The combining the first calling interface and the second calling interface comprises: The interface address of the second calling interface is queried, and the service address parameter of the first calling interface is set to the interface address to implement interface combination.

3. The target platform data calling method according to claim 1, characterized in that: The step of acquiring function data corresponding to the target transfer interface in the target platform through the target transfer interface and sending the function data to the client comprises: A target call instruction is sent to the target platform through the target transfer interface to obtain function data associated with the target call instruction in the target platform, the function data is called back to the target engine through the monitoring module, and the function data is sent to the client through the target engine.

4. The target platform data calling method according to claim 3, characterized in that: The calling instruction includes a hierarchical identifier and a calling module identifier, and the step of sending the target calling instruction to the target platform through the target transfer interface to obtain function data associated with the target calling instruction in the target platform includes: A target calling instruction is sent to the target platform through the target transfer interface, so that the target platform determines the service line to be called based on the layer identifier and the calling module identifier, and returns the function data associated with the service line to be called.

5. The target platform data calling method according to claim 4, characterized in that: After returning the function data associated with the to-be-called business line, the method further includes: Determine the data volume of the functional data, compare the data volume with a preset target data volume, and if the data volume is different from the preset target data volume, perform interface expansion based on the target platform identifier to obtain a target platform extension interface, and obtain the newly added functional data of the target platform based on the target platform extension interface.

6. The target platform data calling method according to claim 1, characterized in that: After obtaining the target transfer interface, the method further includes: According to the interface type and the preset input parameter rule, the target transfer interface is processed with input parameter specification to obtain a standardized input parameter interface, and according to the interface type and the preset output parameter rule, the target transfer interface is processed with output parameter specification to obtain a standardized output parameter interface; The function data corresponding to the target transfer interface in the target platform is obtained through the standard input parameter interface and the standard output parameter interface.

7. The target platform data calling method according to claim 6, characterized in that: The obtaining, through the standard input parameter interface and the standard output parameter interface, function data corresponding to the target transfer interface in the target platform includes: Sending a target call instruction to the target platform through the standard input parameter interface to obtain function data associated with the target call instruction in the target platform; The function data is monitored through the monitoring module, and the monitored function data is called back to the target engine through the standard output parameter interface.

8. A data calling device for a target platform, characterized in that: include: The data acquisition module is used to obtain the game code, target platform identifier and call event sent by the client; A type determination module, used to determine the code language of the game code and the interface type corresponding to the call event; An interface determination module, used to determine a first calling interface according to the interface type and the code language, and to determine a second calling interface according to the target platform identifier and the interface type; An interface combination module, used for combining the first calling interface and the second calling interface to obtain a target transfer interface; The data acquisition module is further used to acquire the function data corresponding to the target transfer interface in the target platform through the target transfer interface; A data sending module is used to send the functional data to the client.

9. A data calling device for a target platform, the 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 implement the data calling method of the target platform as described in any one of claims 1-7.

10. A storage medium storing computer executable instructions, wherein the computer executable instructions are used to execute the data calling method for a target platform according to any one of claims 1 to 7 when executed by a computer processor.

Citation Information

Cited By

  • Data processing method and game engine framework

    CN121534395A