KR20100042681A - Method for supporting game playing in multi-devices and apparatus thereof - Google Patents

Abstract

PURPOSE: A method for supporting a game playing in a multi-devices and an apparatus thereof are provided to execute the same game in different devices continuously. CONSTITUTION: A storage unit(46) stores game data corresponding to an identifier of a first terminal, and a user authentication unit(44) receives the connection signal of the second terminal. The user authentication unit authenticates the identifier of the user. The request signal reception unit receives the transmission request signal of the game data corresponding to the identifier of the user from the second terminal. A transmission unit(48) transmits the game data to the second terminal.

Description

Method for supporting game playing in multi-devices and Apparatus

The present invention relates to a multi-device game play support method and apparatus therefor.

With the development of mobile communication technology, most people own a mobile communication terminal such as a mobile phone. The mobile phone is not used only as a communication device, but serves as various devices such as an information storage device, a game machine, a schedule management device, and a video player.

Among them, the game of the mobile communication terminal has a problem that the user does not enjoy the game continuously because the platform on which the execution is different from other devices, for example, a PC. That is, a user enjoys a game enjoyed by a mobile communication terminal and a game enjoyed by a PC, and these games have a problem in that they cannot execute the same game continuously anytime and anywhere because of different game data.

Accordingly, there is a need for game data that is a result of a game program executed in a mobile communication terminal to be executed on another device, for example, a PC.

The present invention is to provide a multi-device game play support method and apparatus capable of continuously executing the same game on different devices.

Technical problems other than the present invention will be easily understood through the following description.

According to an aspect of the present invention, in a method for supporting a multi-device game play support apparatus to play a game on a multi-device, receiving the game data generated corresponding to the game executed in the first terminal, the game data Storing in the storage unit corresponding to the identifier of the user of the first terminal, authenticating the identifier of the user after receiving the access signal of the second terminal, and after the authentication of the game data corresponding to the identifier of the user from the second terminal. Provided is a multi-device game play support method comprising receiving a transmission request signal and transmitting game data to a second terminal.

Here, the second game program executed in the second terminal may be generated from the first game program executed in the first terminal.

Here, the step of storing and assigning an index to each function included in the target API of the first game program, calling the index corresponding to the function of the target API of the second game program required for generating the target API of the first game program Step, generating the target API by using a function of the target API corresponding to the index may proceed to generate a second game program.

The storing step may further include extracting code required for a platform on which the target API is executed from the target API and storing the code in a memory.

The step of calling the index may further include calling a code corresponding to the index.

According to another aspect of the present invention, an apparatus for supporting a game on a multi-device, comprising: a data receiving unit for receiving game data generated corresponding to a game executed in a first terminal, the game data of the user of the first terminal A storage unit for storing the identifier, the user authentication unit for authenticating the identifier of the user after receiving the access signal of the second terminal, and receiving the transmission request signal of the game data corresponding to the identifier of the user from the second terminal after authentication Provided is a multi-device game play support apparatus including a request signal receiver and a transmitter for transmitting game data to a second terminal.

Here, the second game program executed in the second terminal may be generated from the first game program executed in the first terminal.

In addition, an index is assigned to each function included in the target API of the first game program and stored, and the index corresponding to the function of the target API of the second game program required for generating the target API of the first game program is called. The second game program can be generated by generating the target API using the function of the target API corresponding to the index.

The first terminal or the second terminal may be any one of a mobile phone, a smart phone, a wireless Internet terminal, a PMP, a PDA, an MP4 player, a PC, an IP-TV, a D-TV, and a UMPC.

Other aspects, features, and advantages other than those described above will become apparent from the following drawings, claims, and detailed description of the invention.

The multi-device game play support method and apparatus thereof according to the present invention have the effect of continuously executing the same game on different devices.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all changes, equivalents, and substitutes included in the spirit and scope of the present invention.

Terms including ordinal numbers such as first and second may be used to describe various components, but the components are not limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes any item of a plurality of related items or a combination of a plurality of related items.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. As used herein, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described on the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

In the following description of the present invention with reference to the accompanying drawings, the same components are denoted by the same reference numerals regardless of the reference numerals, and redundant explanations thereof will be omitted. In the following description of the present invention, if it is determined that the detailed description of the related known technology may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

1 is a block diagram of a multi-device game play system according to an exemplary embodiment of the present invention. Referring to FIG. 1, a first terminal 10, 13, 15, 17, a second terminal 20, 23, 25, 27, a network 30, and a multi-device game support apparatus 40 are illustrated.

The first terminals 10, 13, 15, and 17 and the second terminals 20, 23, 25, and 27 are classified for convenience of description and may be of the same terminal type. That is, the first terminal 10, 13, 15, 17 and / or the second terminal 20, 23, 25, 27 may be a mobile phone, a smartphone, a wireless Internet terminal, a PMP, a PDA, an MP4 player, a PC, an IP. It may be any one of -TV, D-TV and UMPC. It has different platforms, and according to the present embodiment, it is possible to execute 2D, 3D games using the same game data on different platforms.

The network 30 may be a wired or wireless communication network, for example, an internet communication network. The first terminal 10, 13, 15, 17 and the second terminal 20, 23, 25, 27 are connected to the multi-device game support apparatus 40 by the network 30.

The multi-device game support apparatus 40 may receive game data that is result data of a game program executed by the first terminal 10, 13, 15, or 17 and transmit the game data to the second terminal 20, 23, 25, 27. have. The second terminals 20, 23, 25, and 27 may continuously execute the game by using the received game data. For example, the game data may be an item acquired on a game program executed by the first terminal 10, 13, 15, or 17, and the acquired item may be recorded and stored as game data so that the second terminal 20 may be another device. , 23, 25, 27) can be applied to the game program. Here, the game program executed in the second terminal 20, 23, 25, 27 may be generated using the game program executed in the first terminal 10, 13, 15, or 17. Details thereof will be described with reference to FIGS. 4 to 12.

2 is a block diagram of a multi-device game play support apparatus according to an embodiment of the present invention. Referring to FIG. 2, the multi-device game play support apparatus 40 includes a receiver 42, a user authenticator 44, a storage 46, and a transmitter 48.

The receiver 42 may be divided into a data receiver and a request signal receiver. The data receiver receives game data generated corresponding to a game executed in the first terminal 10. The request signal receiving unit receives a transmission request signal for game data corresponding to the identifier of the user from the second terminal 20 after the authentication.

The storage unit 46 stores game data corresponding to the identifier of the user of the first terminal 10. The user authenticator 44 authenticates the identifier of the user after receiving the access signal of the second terminal 20. The transmitter 48 transmits the game data to the second terminal 20 requesting reception.

3 is a flowchart of a multi-device game play supporting method according to an embodiment of the present invention.

In step S31, the game is executed in the first terminal 10. Game data is generated when the game is run. In operation S32, the first terminal 10 accesses the multi-device game play support apparatus 40 and undergoes a user authentication process. In operation S33, the generated game data is transmitted to the multi-device game play support apparatus 40. . In operation S34, the multi-device game play support apparatus 40 stores the received game data.

Subsequently, in step S35, the second terminal 20 having a different platform from the first terminal 10 accesses the multi-device game play supporting apparatus 40 and undergoes a user authentication process. In step S36, the stored game data is requested. Receive. Thereafter, in step S37, the second terminal 20 executes the game program using the received game data.

In operation S38, the second terminal 20 generates the modified game data after the game is terminated, accesses the multi-device game play support apparatus 40, and undergoes a user authentication process. In operation S39, the second terminal 20 generates the modified game data. The multi-device game play support apparatus 40 transmits the data.

In the above, the block configuration diagram of the multi-device game play supporting apparatus and the method of using the same according to an embodiment of the present invention have been described. Hereinafter, an apparatus and method for interworking a game program executed in each terminal will be described. . According to the present invention, there is an advantage in that it is possible to generate a game program running on another platform from a game program running on one platform.

4 is a block diagram of a heterogeneous device including a heterogeneous interlocking program generating device according to an exemplary embodiment of the present invention. Referring to FIG. 4, the application 110, the middleware adaptation layer 120, the library 130, the framework 140, the middleware platform engine 150, the heterogeneous run-time engine 160, the handset adaptation layer HAL Handset Adaptation Layer (170), handset hardware and native system software 180, and required API 190 are shown.

The application 110 is a program of the highest layer of a program to be executed heterogeneously, and may be, for example, a game program. In the following, a detailed description will be given focusing on the game program. In addition, for convenience of explanation, a description will be given of a case where a program executed in a PC environment is changed to a program executed in a mobile environment (for example, an environment such as a mobile phone, a game phone, a post PC, etc.). Of course, the present invention can also be implemented in the reverse process.

The middleware adaptation layer 120 is a layer provided for interworking heterogeneous programs and is a heterogeneous program interworking device. The middleware adaptation layer 120 may include an API extracting unit extracting a target API corresponding to the target API based on a preset function, and extracting the target API number and the target API number corresponding to the corresponding function. In addition, the game middleware adaptation layer 120 may include an API mapping unit for mapping the target API to the target API by matching the target API number with the target API number. Here, the target API is a pre-modification API, and the target API is an API generated using the target API. The target API or the target API may be any one of functions such as DirectX, Open GL, Open GL ES, and Renderware.

The middleware adaptation layer 120 supports Direct X modules to easily port general PC games designed based on Windows when mapping Direct x to Open GL ES. Most of the mobile 3D is Open GL ES, which can be converted.

In addition, when mapping Open GL to Open Gl ES, the middleware adaptation layer 120 supports porting of games and content developed in Linux and other Open GL games. Open GL ES supports only some of the features of Open GL, so you can add unsupported features.

In addition, when mapping Renderware to Open GL ES, the middleware adaptation layer 120 is a console device such as PS2, PS3, X-BOX, GameCube, and Renderware which is a cross-platform development environment such as PC, PSP, and N-Gage. It supports easy porting of developed games. The middleware adaptation layer 120 may support for easy conversion of PlayStation games and other platform games.

In addition, if the Open GL ES-based extension library is supported, the middleware adaptation layer 120 may provide a development library for mobile phones and mobile terminals in which the Open GL ES chip is embedded based on basic APIs for improved functions and performance. have.

The library 130 is a set of libraries to be executed in the program after the change. For example, the library 130 may be a game library optimized for a mobile communication terminal and a post PC platform. The library 130 may be a graphic, animation, sound, physics, AI, Ext, or the like.

The framework 140 refers to a framework of a mobile environment, that is, a platform, H / W, I / F, and the like.

The middleware platform engine 150 includes a middleware engine and an engine selector for selecting an engine of a mobile environment. Here, the middleware engine uses a storage module unit which assigns an index to a plurality of target APIs and stores them in a memory, an index caller that calls an index corresponding to a target API required to generate a target API, and a target API corresponding to the index. It may include an API generator for generating a target API.

Here, the storage module unit may extract the code required for the platform on which the target API is executed from the target API and store it in a memory. In this case, the index caller may further call a code corresponding to the index, and the API generator may generate the target API by combining the code of the target API.

That is, the middleware platform engine 150 may generate the target API from the respective functions selected for each API, function, and structure in the middleware adaptation layer 120.

The heterogeneous run-time engine 160, the handset adaptation layer 170, and the handset hardware and the native system software 180 are each layers previously implemented in a mobile environment. That is, they are H / W and S / W prepared for the implementation of the mobile environment, they are linked with the necessary API (190) 2D API, 3D API, M & U API, Eglx API, extension API.

5 is a block diagram showing the operation of the heterogeneous interlocking program generating device according to an embodiment of the present invention. Referring to FIG. 5, the target API 210, the second platform structure 220, is shown. The second platform structure 220 includes a middleware adaptation layer 225, an engine structure 230 for the middleware adaptation layer, a middleware platform engine 240, a software 3D engine 250, and a destination API 260. The differences from the above will be explained mainly.

The target API 210 may be DirectX 213, Open GL / Open GL ES 215, and Renderware 217. The function structure and memory structure used in the target API 210 are different from the function structure and memory structure used in the target API 260. Accordingly, by changing the structure of the function in the middleware adaptation layer 225, the engine structure 230 for the middleware adaptation layer, and the middleware platform engine 240, the target API 210 is adapted to the second platform structure 220. Generate 260.

The engine structure 230 for the middleware adaptation layer changes each function of the target API 210 extracted according to the target API 260 in the middleware adaptation layer 225 into a structure for the middleware platform engine 240.

The middleware platform engine 240 may include a middleware engine 243 and an engine selector 245. The middleware engine 243 generates a target API using each function of the target API as described above. The generated destination API enables execution by the engine selector 245 in the corresponding software 3D engine 250. H / W acceleration engine and S / W renderer engine can be applied to the present invention.

The software 3D engine 250 receives the corresponding API from the engine selector 245 and executes the target API 260. Here, the software 3D engine 250 is an engine to be executed in the case of 3D, and it is natural that the present invention is not limited to 3D.

FIG. 6 is a block diagram of a heterogeneous device on which a heterogeneous interlocking program generating device according to an embodiment of the present invention is driven. The differences from the above will be explained mainly.

The destination API generated by the middleware platform engine 150 is executed on the second platform structure 350. The second platform structure 350 may be driven by selectively adopting HAL or handset hardware and native system software 353, PDA or mobile set 356, and OS (Window / Linux / Unix / Mac).

Accordingly, the destination API may be changed corresponding to the second platform structure 350 by the middleware platform engine 150.

In the above description, a block diagram showing a heterogeneous interlocking program generating device has been described in general. Let's explain. It is obvious that the present invention is not limited to these examples.

7 is a diagram illustrating a method for generating an API function by a heterogeneous interlocking program generating device according to a first embodiment of the present invention.

According to the first embodiment of the present invention, when one target API 210 corresponds to one target API, the middleware platform engine 240 needs the factor 420 required for one target API as described above. Extracting from 410 generates one destination API. Here, the argument 410 may be a component necessary to extract the function or code of the target API 210 to form the target API. The factor 420 necessary for the target API may be used by the middleware platform engine 240 to generate the target API.

When one target API 210 corresponds to one target API, the target API may be simply generated by analyzing a function or code of one API and extracting only necessary arguments.

In addition, in order to extract these factors, the API extractor or middleware platform engine 240 may compare the structure of the target API and the structure of the target API. When the comparison results in the same structure, the middleware platform engine 240 may directly convert the target API into the target API. Also, as a result of the comparison, the structures are not identical to each other, and if similar, the API extractor or the middleware platform engine 240 may extract a similar factor and generate the target API using the same factor.

In addition, the extracted factors 410 and 420 may be stored in a memory and called and used from the memory when necessary. The extracted factors 410 and 420 may be entirely stored in a memory, or an index or a memory address may be stored in a memory and called by a corresponding index or memory address if necessary.

8 is a diagram illustrating a method for generating an API function by a heterogeneous interlocking program generating device according to a second embodiment of the present invention.

According to the second embodiment of the present invention, when one target API 210 corresponds to a plurality of target APIs, a plurality of targets are extracted by extracting the factors 520 and 525 necessary for the plurality of target APIs from the targets 510 of the target API. When creating an API. Here, the factor 510 may be extracted from a function or code of the target API 210 and used as the factors 520 and 525 which are components necessary to form the target API.

Here, although the case in which the factor 510 extracted from one target API 210 corresponds to a plurality of target APIs has been described, the plurality of factors 520 and 525 may form one target API.

9 is a diagram illustrating a method for generating an API function by a heterogeneous interlocking program generating device according to a third embodiment of the present invention.

According to the third embodiment of the present invention, when the plurality of target APIs 210 correspond to one target API, the necessary factors 520 for one target API are extracted from the factors 610 and 615 of the plurality of target APIs. This is the case when the purpose API is created.

In addition, in FIG. 10, when the plurality of target APIs 210 correspond to a plurality of target APIs, the plurality of target APIs 210 extracts the factors 720 and 725 necessary for the plurality of target APIs from the plurality of target APIs 710 and 715. When creating the destination API. Of course, as described above, the plurality of factors 720 and 725 necessary for the target API may form one target API.

11 is a block diagram of a program development tool of a heterogeneous interlocking program generation device according to an exemplary embodiment of the present invention. Referring to FIG. 11, source data resources 810, 850, resource converter 820, tools 830, source converter 840, exporter 860, API connection list 870, and program source 880 Shown. The case where the program is a game program will be described mainly.

The program development tool according to an embodiment of the present invention comprises a function extraction unit for extracting a function corresponding to a predetermined function from a target API, a memory address generator for generating a memory address corresponding to the function, and a memory address by calling It may include an API conversion unit for extracting a function of the target API required when generating the API and using this to generate the target API.

Here, the necessary functions for generating the target API are separately determined in the form of blocks and stored in the memory. You can then create the destination API by calling the memory address of the stored function and extracting the required function.

The source data resources 810 and 850 may be 3D objects, images, sounds, 3D max / light waves, etc. as data before being changed.

The resource converter 820 converts a resource of a function of the target API into a platform format to which the target API is applied. The resource converter 820 stores resources such as 2D, 3D, animation, moving picture, sound, and the like of a program (eg, a game) operating in heterogeneous devices in a second platform format (eg, a mobile format). To convert and optimize.

Tool 830 transforms data associated with animations, maps, effects, and UIs as appropriate for the second platform format. For example, the animation tool of the tool 830 combines animations produced in 3D Max, Lightwave, etc. for each mesh.

The mapping tool of the tool 830 may designate a Map Tile Pattern setting on the tool with respect to the background, and automatically assigns the specified Map Tile on the map and designates it in Cel units. In addition, the mapping tool sets the size of the map to be produced in units of n powers of 2, and uses the RGB value of the bitmap pixel and the height of each cell by using a brush supported on the tool. Can be set. The mapping tool also supports vertex color settings for each cell of the terrain, which can affect the character. In addition, the mapping tool may have a fog and light setting function (a function of specifying the brightness and the color of the light for each map and the color depth of the fog). In this case, the mapping tool may allocate and configure objects constituting the map in units of cells. In addition, the mapping tool can designate attributes (non-moveable, mobile, safe zone) in units of cells. By this function, a moving path can be specified for each object object. For example, independent movement paths may be designated for each object of AHQ, NPC, and character.

The UI tool of the tool 830 minimizes the programmer's involvement in making the interface and optimizes the use of graphic data. Among these, the resource tool supports TGA, BMP, and various files, and cuts the resources needed in the bitmap into the desired size and gives an ID. In addition, the resource tool specifies an action of generating a button for generating an automatic combination pattern of resources required for the interface.

In addition, among the UI tools, the interface tool manages the interface constituting the game by folder and configures the interface. In addition, the interface tool creates a desired interface by using the ID and pattern specified in the above-described resource tool. The interface tool can assign the initial open position of the interface, assign shortcut keys, manage all the text included in the interface in a separate file, and set the degree of Alpha Blend for each interface.

The source converter 840 converts a library of the target API into a platform format to which the target API is applied. The source converter 840 provides a function of automatically converting the Direct X, Open GL, and Renderware Graphic libraries according to the game middleware platform structure for mobile. The source converter 840 converts libraries of Direct X, Renderware, and Open GL into libraries of the middleware platform. (For example, DirectX-> Open GLes / Renderware-> Open GLes)

The exporter 860 converts the content of the target API into a platform format to which the target API is applied. The exporter 860 provides a function of converting graphics, such as 2D graphics, 3D graphics, and video used in a mobile 3D game, into a format provided by a mobile environment to be ported. For example, the exporter 860 converts 3D graphics into a 3D format for mobile use in 3Max, and provides an Explorer program for converting various contents such as Photoshop and AVI into a mobile format.

The API connection list 870 may be an API connection list value for connecting a library of Direct X, Renderware, and Open GL to a library of a middleware platform.

Program sources 880 are program sources before being changed. For example, the program source 880 may be a game program source, a content program source, or the like. In this case, the program source 880 may be data before change generated at compile time by the compiler of FIG. 11. The API connection list 870 and the program source 880 may be selectively provided with each other.

12 is a diagram illustrating a program development environment by a program development tool among heterogeneous interlocked program generation devices according to an exemplary embodiment of the present invention. Referring to FIG. 12, a configuration of participating functions of the planner 910, the programmer 920, and the designer 930 according to an embodiment of the present invention is illustrated.

The organizer 910 is responsible for text input, menu frame construction, key event processing, simulation testing, data loading, and memory management 915.

The programmer 920 develops a game engine and performs a phone test.

The designer 930 performs key event processing, menu / screen composition, image modification, screen layout, and simulation test 935.

The planner 910, the programmer 920, and the designer 930 may efficiently develop a game program through the program development tool, which is the UI tool & game editor 940 described above. The game developed in the UI tool & game editor 940 is generated into the game program 960 by the game play engine 950.

Those skilled in the art will appreciate that various modifications and changes can be made in the present invention without departing from the spirit and scope of the invention as set forth in the claims below.

1 is a block diagram of a multi-device game play system according to an embodiment of the present invention.

Figure 2 is a block diagram of a multi-device game play support apparatus according to an embodiment of the present invention.

3 is a flowchart of a multi-device game play support method according to an embodiment of the present invention.

Figure 4 is a block diagram of a heterogeneous device including a heterogeneous interlocking program generating device according to an embodiment of the present invention.

5 is a block diagram showing the operation of the heterogeneous interlocking program generating device according to an embodiment of the present invention.

6 is a block diagram of a heterogeneous device in which the heterogeneous interlocking program generating device is driven according to an embodiment of the present invention.

7 is a diagram illustrating a method for generating an API function by a heterogeneous interlocking program generating device according to a first embodiment of the present invention.

8 is a diagram illustrating a method for generating an API function by a heterogeneous interlocking program generating device according to a second embodiment of the present invention.

9 is a diagram illustrating a method for generating an API function by a heterogeneous interlocking program generating device according to a third embodiment of the present invention.

10 is a diagram illustrating a method for generating an API function by a heterogeneous interlocking program generating device according to a fourth embodiment of the present invention.

11 is a block diagram of a program development tool of the heterogeneous interlocking program generating device according to an embodiment of the present invention.

12 is a diagram illustrating a program development environment by a program development tool among heterogeneous interlocked program generation devices according to an embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

10, 13, 15, 17: first terminal 20, 23, 25, 27: second terminal

30: network 40: multi-device game support device

42: receiver 44: user authentication unit

46: storage unit 48: transmission unit

110: application 120: middleware adaptation layer

130: library 140: framework

150: middleware platform engine 160: heterogeneous run-time engine

170: handset adaptation layer

180: Handset Hardware and Native System Software

190: required API

Claims (10)

In the method of supporting a multi-device game play support device to play a game on a multi-device, Receiving game data generated corresponding to a game executed in the first terminal; Storing the game data in a storage unit corresponding to the identifier of the user of the first terminal; Authenticating the identifier of the user after receiving the access signal of the second terminal; Receiving a transmission request signal of game data corresponding to the identifier of the user from the second terminal after the authentication; And And transmitting the game data to the second terminal. The method of claim 1, And a second game program executed in the second terminal is generated from a first game program executed in the first terminal. The method of claim 2, Storing and assigning an index to each function included in the target API of the first game program; Calling an index corresponding to a function of a target API of the second game program required for generating the target API of the first game program; Generating the target API by using a function of the target API corresponding to the index. The method of claim 3, The storing step, And extracting the code necessary for the platform on which the target API is executed from the target API and storing the code in the memory. The method of claim 4, wherein The index call step, And further calling a code corresponding to the index. The method of claim 1, The first terminal or the second terminal is a multi-device game play, characterized in that any one of a mobile phone, smart phone, wireless Internet terminal, PMP, PDA, MP4 player, PC, IP-TV, D-TV and UMPC How to apply. In a device that supports playing a game on a multi-device, A data receiver configured to receive game data generated corresponding to a game executed in the first terminal; A storage unit to store the game data corresponding to the identifier of the user of the first terminal; A user authentication unit which authenticates an identifier of the user after receiving a connection signal of a second terminal; A request signal receiving unit which receives a transmission request signal for game data corresponding to the identifier of the user from the second terminal after the authentication; And And a transmitter configured to transmit the game data to the second terminal. The method of claim 7, wherein And a second game program executed in the second terminal is generated from a first game program executed in the first terminal. The method of claim 8, Assign and store an index to each function included in the target API of the first game program, and call an index corresponding to a function of the target API of the second game program required for generating the target API of the first game program; By generating the destination API by using a function of the target API corresponding to the index, And the second game program is generated. The method of claim 7, wherein The first terminal or the second terminal is a multi-device game play, characterized in that any one of a mobile phone, smart phone, wireless Internet terminal, PMP, PDA, MP4 player, PC, IP-TV, D-TV and UMPC Support device.

Images