CN104166820B - A kind of data managing method and system - Google Patents

Abstract

The embodiment of the invention discloses a data management method and system to solve the problem that offline user data of a client platform cannot be managed. The method includes loading offline user data satisfying storage conditions in advance into a fixed-capacity memory pool; receiving an online user's management application for offline user data during the running of the server application; verifying whether the online user and the management application both have management authority; When both the online user and the management application have management authority, query whether there is offline user data corresponding to the management application in the memory pool; if there is, send the offline user data corresponding to the management application to the online user terminal, and save it with the management application The corresponding offline user data is in the memory pool. High-frequency offline user data is loaded in advance, low-frequency offline user data is stored and released, and high-frequency offline user data is kept in the memory pool, reducing the storage pressure on the database side.

Description

A data management method and system

technical field

The embodiments of the present invention relate to the field of computer technology, and in particular to a data management method and system.

Background technique

The data stored in the database may include online user data and offline user data. An online user is a user who is connected to the server, and an offline user is a user who is disconnected from the server.

When the user is online, the data of the online user will be temporarily retrieved from the database by the server and temporarily stored in the running server. The online user data is modified in real time by the server and written back to the database at a specific time.

When a user goes offline, the offline user's data is removed from the running server. At this time, the running server will not be able to obtain any information of offline users.

The method for the online user to manage the offline user data stored in the database is as follows: the online user directly connects to the database, performs operations such as reading, modifying, and deleting the offline user data in the database, and then saves the offline user data in the database.

Taking games as an example, there are currently two types of client platform games and web platform games. In web platform games, online users can manage offline user data through the above methods. However, since the user data of client platform games is more interactive, The amount of user data is larger, and the offline user data stored in the database is also larger. Accessing offline user data from the database requires a high-performance server and database, and transmitting large-capacity offline user data also requires higher network bandwidth; Moreover, the data information and attributes of offline user data on the client platform are richer, and there may be various correlations between different offline user data, so the data management of offline user data on the client platform is more complicated. There is no offline user data management method for client platform games.

Contents of the invention

The embodiment of the present invention discloses a data management method and system to solve the problem that offline user data of a client platform cannot be managed.

In order to solve the above problems, the embodiment of the present invention discloses a data management method, including:

When the server application starts, offline user data that meets the storage conditions is loaded in advance to the created fixed-capacity memory pool;

During the running process of the server application, a management application for offline user data is received from an online user, and the management application has a mapping relationship with the offline user data;

Verifying whether the online user and the management application both have the authority to manage offline user data;

When both the online user and the management application have the authority to manage offline user data, query whether there is offline user data corresponding to the management application in the memory pool;

When there is offline user data corresponding to the management application in the memory pool, send the offline user data corresponding to the management application to the online user terminal, and keep the offline user data corresponding to the management application in the in the memory pool.

Preferably, after querying whether there is offline user data corresponding to the management application in the memory pool, the method further includes:

When the offline user data corresponding to the management application does not exist in the memory pool, the offline user data corresponding to the management application is read from the database and stored in the memory pool.

Preferably, the verifying whether the online user and the management application both have the authority to manage offline user data includes:

judging whether the online user belongs to a user with authority to manage offline user data corresponding to the management application;

When the online user belongs to a user with authority to manage the offline user data corresponding to the management application, determine whether the management application meets the management conditions of the offline user data corresponding to the management application, and the management conditions include Whether the data in the offline user data is allowed to be read, modified and deleted;

When the online user belongs to a user with authority to manage the offline user data corresponding to the management application, and the management application meets the management conditions of the offline user data corresponding to the management application, determine the online user and The management applications all have the authority to manage offline user data;

When the online user does not belong to the user with the authority to manage the offline user data corresponding to the management application, it is determined that the online user does not have the authority to manage the offline user data; When determining the management conditions of the offline user data corresponding to the management application, it is determined that none of the management applications has the authority to manage the offline user data.

Preferably: the storage condition is that the access frequency of offline user data is greater than or equal to a predetermined threshold.

Preferably, the method also includes:

Querying the offline user data in the memory pool in turn;

If the offline user data in the memory pool has not been accessed within the first preset time period, the offline user data that has not been accessed within the first preset time period will be stored in the database, and stored in the memory pool pool delete;

If the offline user data in the memory pool has been accessed within a second preset time period, retain the offline user data accessed within the second preset time period in the memory pool.

The embodiment of the present invention also discloses a data management system, including:

The loading module is used to pre-load offline user data that meets the storage conditions into the created fixed-capacity memory pool when the server application starts;

The receiving module is configured to receive a management application for offline user data from an online user during the running process of the server application, and the management application has a mapping relationship with the offline user data;

A verification module, configured to verify whether both the online user and the management application have the authority to manage offline user data;

A query module, configured to query whether there is offline user data corresponding to the management application in the memory pool when both the online user and the management application have the authority to manage offline user data;

A sending and retaining module, configured to send the offline user data corresponding to the management application to an online user terminal when there is offline user data corresponding to the management application in the memory pool, and retain the data corresponding to the management application Offline user data is in the memory pool.

Preferably, the system also includes:

The reading storage module is used to, after the query module inquires whether there is offline user data corresponding to the management application in the memory pool, when there is no offline user data corresponding to the management application in the memory pool , the offline user data corresponding to the management application is read from the database and stored in the memory pool.

Preferably, the verification module includes:

An online user judging submodule, configured to judge whether the online user belongs to a user with authority to manage offline user data corresponding to the management application;

The management application judging sub-module is used to judge whether the management application conforms to the requirements of the offline user data corresponding to the management application when the online user belongs to a user with authority to manage the offline user data corresponding to the management application Management conditions, the management conditions include whether each data in the offline user data is allowed to be read, modified and deleted;

A determining submodule, configured to: when the online user belongs to a user with authority to manage the offline user data corresponding to the management application, and the management application meets the management conditions of the offline user data corresponding to the management application, determining that both the online user and the management application have the authority to manage offline user data; when the online user does not belong to a user with authority to manage offline user data corresponding to the management application, determine that the The user does not have the right to manage offline user data; when the management application does not meet the management conditions for offline user data corresponding to the management application, it is determined that none of the management applications has the right to manage offline user data .

Preferably: the storage condition is that the access frequency of offline user data is greater than or equal to a predetermined threshold.

Preferably, the system also includes:

A query management module, configured to sequentially query the offline user data in the memory pool; if the offline user data in the memory pool is not accessed within a first preset time period, it will Store the offline user data that has not been accessed within the database and delete it in the memory pool; if the offline user data in the memory pool has been accessed within the second preset time period, it will be kept in the second Offline user data accessed within a preset time period is stored in the memory pool.

Compared with the background technology, the embodiments of the present invention include the following advantages:

In the data management method and system disclosed in the embodiments of the present invention, a fixed-capacity memory pool is created in the server of the client platform, and frequently accessed offline user data is loaded into the memory pool in advance each time the server application is started. During the running of the server application, when an online user's application for offline user data management is received, it will query whether there is offline user data to be managed in the memory pool. If it exists, the offline user data to be managed (high-frequency access offline user data) to the online user terminal, and keep the offline user data to be managed (offline user data with high frequency access) in the memory pool; if it does not exist, read the offline user data to be managed from the database (low frequency access Offline user data accessed by users), loaded into the memory pool, and then the offline user data to be managed (offline user data with infrequent access) is sent from the memory pool to the online user terminal, and the managed offline user data (offline user data with infrequent access) User data) is stored in the database, and the offline user data is deleted in the memory pool. Load and cache frequently accessed offline user data in the memory pool in advance, store infrequently accessed offline user data in the memory pool and release it from the memory pool, and frequently access offline user data remain in the memory pool , only save offline user data accessed infrequently to the database, reducing the storage pressure on the database side.

Moreover, a memory pool with a fixed capacity is used to load and cache offline user data. The capacity of the memory pool is fixed. Clearing the offline user data therein and loading and caching the offline user data into the memory pool results in less memory fragmentation. If you use a memory pool with dynamic capacity to load and cache offline user data, the more offline user data you load and cache, the larger the capacity of the memory pool will be, and a memory pool with a relatively large capacity will generate more memory fragments.

Use a fixed-capacity memory pool to load and cache offline user data, and the capacity of the remaining memory on the server side is also fixed, so that the remaining memory on the server side will not decrease because the memory pool for loading and caching offline user data is getting larger and larger. The memory capacity used by the server side for application running.

Because less memory fragments are generated, the running risk of the server is reduced (the more memory fragments, the higher the risk of abnormal server downtime).

At the same time, the offline user data in the memory pool is dynamically adjusted. When high-frequency access to offline user data becomes low-frequency access to offline user data, these offline user data can be cleaned up in time, which improves the utilization rate of the memory pool.

Furthermore, since the offline user data is cached in the memory pool, when the connection between the server and the database is disconnected, the offline user data can be safely stored in the memory pool, and when the connection is re-established, the offline user data can continue to be stored in the database, reducing the The risk of offline user data loss is reduced.

Description of drawings

Fig. 1 is a flow chart of a data management method in an embodiment of the present invention;

Fig. 2 is a schematic diagram of a data management method in an embodiment of the present invention;

Fig. 3 is a schematic diagram of offline player data cleaning in an embodiment of the present invention;

FIG. 4 is an overall structural diagram of the combination of the client game and the web game in the embodiment of the present invention;

5 is a structural diagram of a data management system in an embodiment of the present invention;

Fig. 6 is a schematic structural diagram of managing offline user data in a client game according to an embodiment of the present invention.

detailed description

In order to make the above objects, features and advantages of the present invention more comprehensible, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

Embodiment one

A data management method disclosed in the embodiment of the present invention is introduced in detail.

Referring to FIG. 1 , it shows a flowchart of a data management method in an embodiment of the present invention.

Step 100, when the server application is started, offline user data meeting storage conditions is loaded in advance into the created memory pool with fixed capacity.

The server may refer to a server for running applications.

The storage condition may be that the access frequency of offline user data is greater than or equal to a predetermined threshold.

For example: if an offline user data is accessed 60 times within a month (calculated as 30 days), then the offline user data access frequency is 2 times/day. If the predetermined threshold is 1 time/day, then the offline user data meets the storage condition.

The fixed-capacity memory pool may be a part of the server memory, the memory pool is used to store offline user data, and the memory pool may not be used to participate in the running of the server application.

Step 102: During the running process of the server application, an online user's application for managing offline user data is received.

The management application has a mapping relationship with offline user data.

For example, an online user submits a management application for offline user data, and the management application may access, modify, or delete certain offline user data.

Step 104, verify whether the online user and the management application both have the authority to manage offline user data.

The step 104 may include two-step verification operations, one step is to verify whether the online user has management authority to a certain offline user data, and the offline user data is the offline user data corresponding to the management application; the other step is to verify whether the management application meets its corresponding The management conditions of offline user data.

Preferably, said step 104 may include:

Sub-step 1041, judging whether the online user belongs to a user who has the authority to manage offline user data corresponding to the management application.

For example, online users who have the right to manage offline user data D1 include A, B, and C. If online user A applies for management of offline user data D1, online user A belongs to the online user who has the right to manage offline user data D1 ; If the online user D puts forward a management application for the offline user data D1, the online user D does not belong to the online user with the authority to manage the offline user data D1.

Sub-step 1042, when the online user belongs to a user with authority to manage the offline user data corresponding to the management application, determine whether the management application meets the management conditions of the offline user data corresponding to the management application.

The management conditions may include whether each item of data in the offline user data is allowed to be read, modified and deleted.

For example, the management condition of offline user data D1 is that it is allowed to be read, not allowed to be modified and deleted. When online user A belongs to the online user with the authority to manage offline user data D1, if the management application submitted by online user A is to modify offline user data D1, the management application submitted by online user A does not meet the management conditions of offline user data D1 ; If the management application made by the online user A is to read the offline user data D1, then the management application made by the online user A meets the management conditions of the offline user data D1.

When the online user belongs to a user with authority to manage the offline user data corresponding to the management application, and the management application meets the management conditions of the offline user data corresponding to the management application, determine the online user and The management applications all have the authority to manage offline user data.

When the online user does not belong to the user with the authority to manage the offline user data corresponding to the management application, it is determined that the online user does not have the authority to manage the offline user data; When determining the management conditions of the offline user data corresponding to the management application, it is determined that none of the management applications has the authority to manage the offline user data.

Step 106, when both the online user and the management application have the authority to manage offline user data, query whether there is offline user data corresponding to the management application in the memory pool.

For example, when both the online user A and the management application submitted by the online user A have the management authority on the offline user data D1, query whether the offline user data D1 exists in the memory pool. And the management application submitted by the online user A is to manage the offline user data D1.

Step 108, when there is no offline user data corresponding to the management application in the memory pool, read the offline user data corresponding to the management application from the database, and store it in the memory pool.

After the step 108, the offline user data stored in the memory pool may be sent to the online user terminal for management operations. And after the management operation is finished, the managed offline user data can be saved in the database and deleted from the memory pool. It is also possible to save the managed offline user data in the database after the management operation ends, and keep it in the memory pool.

Step 110, when there is offline user data corresponding to the management application in the memory pool, sending the offline user data corresponding to the management application to an online user terminal, and retaining the offline user data corresponding to the management application in the memory pool.

The important execution operations in the step 110 can be understood as:

After the offline user data is managed, the managed offline user data is kept in the memory pool, which can facilitate subsequent online users to manage the offline user data.

Step 112, perform a cleaning operation on the offline user data in the memory pool.

Since the capacity of the memory pool is fixed, it is impossible to store offline user data without limit, so it is necessary to periodically or continuously clean up the offline user data in the memory pool.

The purpose of cleaning is to keep the frequently accessed offline user data in the memory pool, store the infrequently accessed offline user data back into the database, and delete them from the memory pool, so that enough memory pool space can be left for loading and caching other offline user data.

Preferably, said step 112 may include:

The offline user data in the memory pool is queried sequentially. If the offline user data in the memory pool has not been accessed within the first preset time period, the offline user data that has not been accessed within the first preset time period will be stored in the database, and stored in the memory pool Deleting from the pool; if the offline user data in the memory pool has been accessed within the second preset time period, keep the offline user data accessed within the second preset time period in the memory pool .

For example, the memory pool includes 3 offline user data, namely D1, D2 and D3. If D1 has not been accessed within 2 days, store D1 in the database and delete D1 from the memory pool; if D2 and D3 have been accessed within 1 day, keep D2 and D3 in the memory pool.

The first preset time period and the second preset time period can be set according to actual conditions.

It should be noted that the step 112 may be performed at any time after the step 100, may be performed periodically one or more times, or may be continuously performed.

In the following, the game is mainly taken as an example to introduce the data management method when the game is running.

Referring to FIG. 2 , it shows a schematic diagram of a data management method in an embodiment of the present invention.

Step 200, receiving a player's application for managing offline player data.

In step 202, the offline player data manager inquires whether there is offline player data corresponding to the management application in the memory pool.

Among them, the offline player data manager can be used to manage the memory pool, and control access to offline player data that has been put into the memory pool.

If offline player data corresponding to the management application exists in the memory pool, step 204 is performed.

Step 204, feeding back the offline player data corresponding to the management application to the player.

If there is no offline player data corresponding to the management application in the memory pool, step 206 is performed.

Step 206, read offline player data corresponding to the management application from the database.

Step 208, storing the offline player data corresponding to the management application in the memory pool, and feeding it back to the player.

Moreover, the above-mentioned offline player data manager can also clean up the offline player data in the memory pool. Referring to FIG. 3 , it shows a schematic diagram of offline player data cleaning in an embodiment of the present invention.

Step 300, the offline player data manager polls the offline player data in the memory pool.

If the offline player data in the memory pool has not been accessed within a period of time, step 302 is executed. The aforementioned time period may be set according to actual conditions, for example, one week or one month.

Step 302: Store the offline player data that has not been accessed within a period of time into the database, and delete it from the memory pool.

If some offline player data in the memory pool has been accessed within a period of time, step 304 is executed. The aforementioned time period can be set according to actual conditions, for example, one day or one hour.

Step 304, keep the offline player data accessed within a period of time in the memory pool.

It should be noted that the above two time periods may be the same or different, and may be set according to actual conditions.

In the following, a data management method is introduced mainly by taking a game as an example.

Firstly, the overall structure of data management by applying the data management method described in the embodiment of the present invention is introduced.

Client game refers to an online game in which the official server is set up, and the user downloads the installation file to install the client and connects to the server through the Internet for multiplayer interaction. Web games (WEB games) refer to games that can be played by opening a web page through a browser, and can be completed with only a few clicks.

Duration-based online games (referred to as "duration games") refer to online games that players need to spend a long time continuously experiencing, such as most client games. Fragmented time-based online games (referred to as "fragmented time games") refer to online games in which players can enjoy a rich experience in a small amount of time, such as community web games.

In the embodiment of the present invention, the time continuation of client games and the time fragmentation of web games can be combined, so that players can make full use of these fragmented times, and obtain fragmented time online games in the fragmented time of continuous online games gaming experience.

Among them, the client game is called the duration game, the corresponding server is called the duration server, the corresponding client is called the duration client, and the data in the game is called the duration data; the web game is called the fragmented time game , the corresponding client is called fragment time client, and the data in the game is called fragment time data.

First of all, a fragmented time game can be developed in the duration game, and the fragmented time game can be developed in the way of developing a web game (thus, the embodiment of the present invention can consider the developed fragmented time game as a webpage game, in essence its Not really a browser game). These two types of games can use the same set of data for different game experiences, and fragmented time games can be a new scene different from continuous time games. For example, if the player’s scene in the duration game is A, the character is a, and the character data is b, then the player’s scene in the fragmented time game can be B, the character is also a, and the character data is also b, so that Through these two types of games, the development of characters is carried out simultaneously.

Specifically, as shown in FIG. 4 , it is an overall structural diagram of the combination of the client game and the browser game in the embodiment of the present invention.

As can be seen from Figure 4, after the duration game and the fragment time game are combined, the fragment time game can be played during the duration game. A fragmented time client can be developed on the basis of the original duration server and duration client, and a fragmented time data processing module can be developed on the original duration server to process the fragmented time data in the fragmented time game .

Wherein, the duration client and the fragment time client can be implemented by the same client software, and after the user downloads the client software, he can have the duration client and the fragment time client at the same time. Fragment time clients can be some plug-ins, which can be temporarily stored, for example, if the player can delete them after loading them, of course, they can also be saved, which is not limited in the embodiment of the present invention.

A subprocess for hosting the fragmented time client can be developed. When the player is playing the duration game, the host sub-process can be triggered in some way in the duration client to start, and the fragment time client can be displayed through this sub-process; then the fragment time client can be used for the duration client The terminal is an intermediary (the way of inter-process communication), which interacts with the duration server for data, and processes the fragment time data of the fragment time client through the fragment time data processing module in the duration server.

The above-mentioned duration server in FIG. 4 may include a duration data processing module and a fragment time data processing module. The client game mentioned in the embodiment of the present invention can be the above-mentioned duration game, and the webpage game can be the above-mentioned fragmented time game; the client (ie web client) of the webpage game can be the above-mentioned fragmented time client, and the client The client of the client game can be the above-mentioned duration client; the server of the web game (that is, the web server) can be the above-mentioned fragment time data processing module, the server of the client game can be the above-mentioned duration data processing module, and the central server can be the above-mentioned Duration server; the client data can be the data in the Duration game, the webpage data can be the data in the fragment time game, and the shared data can be the character data (account data) running the game.

In summary, a data management method disclosed in the embodiment of the present invention has the following advantages:

Create a fixed-capacity memory pool in the server of the client platform, and load frequently accessed offline user data into the memory pool in advance each time the server application is started. During the running of the server application, when an online user's application for offline user data management is received, it will query whether there is offline user data to be managed in the memory pool. If it exists, the offline user data to be managed (high-frequency access offline user data) to the online user terminal, and keep the offline user data to be managed (offline user data with high frequency access) in the memory pool; if it does not exist, read the offline user data to be managed from the database (low frequency access Offline user data accessed by users), loaded into the memory pool, and then the offline user data to be managed (offline user data with infrequent access) is sent from the memory pool to the online user terminal, and the managed offline user data (offline user data with infrequent access) User data) is stored in the database, and the offline user data is deleted in the memory pool. Load and cache frequently accessed offline user data in the memory pool in advance, store infrequently accessed offline user data in the memory pool and release it from the memory pool, and frequently access offline user data remain in the memory pool , only save offline user data accessed infrequently to the database, reducing the storage pressure on the database side.

Moreover, a memory pool with a fixed capacity is used to load and cache offline user data. The capacity of the memory pool is fixed. Clearing the offline user data therein and loading and caching the offline user data into the memory pool results in less memory fragmentation. If you use a memory pool with dynamic capacity to load and cache offline user data, the more offline user data you load and cache, the larger the capacity of the memory pool will be, and a memory pool with a relatively large capacity will generate more memory fragments.

Use a fixed-capacity memory pool to load and cache offline user data, and the capacity of the remaining memory on the server side is also fixed, so that the remaining memory on the server side will not decrease because the memory pool for loading and caching offline user data is getting larger and larger. The memory capacity used by the server side for application running.

Because less memory fragments are generated, the running risk of the server is reduced (the more memory fragments, the higher the risk of abnormal server downtime).

At the same time, the offline user data in the memory pool is dynamically adjusted. When high-frequency access to offline user data becomes low-frequency access to offline user data, these offline user data can be cleaned up in time, which improves the utilization rate of the memory pool.

Furthermore, since the offline user data is cached in the memory pool, when the connection between the server and the database is disconnected, the offline user data can be safely stored in the memory pool, and when the connection is re-established, the offline user data can continue to be stored in the database, reducing the The risk of offline user data loss is reduced.

Embodiment two

A data management system disclosed in the embodiment of the present invention is introduced in detail.

Referring to FIG. 5 , it shows a structural diagram of a data management system in an embodiment of the present invention.

The data management system may include:

Loading module 200 , receiving module 202 , verifying module 204 , querying module 206 , reading storage module 208 , sending and saving module 210 , and querying management module 212 .

Wherein, the verification module 204 may include:

An online user judging submodule 2041 , a management application judging submodule 2042 , and a determining submodule 2043 .

The functions of each module and each sub-module and the relationship between each module and each sub-module are introduced in detail below.

The loading module 200 is configured to load offline user data satisfying storage conditions into the created memory pool with fixed capacity in advance when the server application is started.

The storage condition is that the access frequency of offline user data is greater than or equal to a predetermined threshold.

The receiving module 202 is configured to receive an online user's application for managing offline user data during the running of the server application.

The management application has a mapping relationship with offline user data.

A verification module 204, configured to verify whether both the online user and the management application have the authority to manage offline user data.

Preferably, the verification module 204 may include:

The online user judging sub-module 2041 is configured to judge whether the online user belongs to a user with authority to manage offline user data corresponding to the management application.

The management application judging sub-module 2042 is used for judging whether the management application conforms to the offline user data corresponding to the management application when the online user belongs to a user with authority to manage the offline user data corresponding to the management application management conditions.

The management conditions include whether each data in the offline user data is allowed to be read, modified and deleted.

A determining submodule 2043, configured to be used when the online user belongs to a user with authority to manage the offline user data corresponding to the management application, and the management application meets the management conditions of the offline user data corresponding to the management application , determining that both the online user and the management application have the authority to manage offline user data; when the online user does not belong to a user with authority to manage offline user data corresponding to the management application, determine that Online users do not have the right to manage offline user data; when the management application does not meet the management conditions for offline user data corresponding to the management application, it is determined that none of the management applications has the right to manage offline user data authority.

The query module 206 is configured to query whether the offline user data corresponding to the management application exists in the memory pool when the online user and the management application both have the authority to manage offline user data.

The reading storage module 208 is configured to, after the query module 206 inquires whether there is offline user data corresponding to the management application in the memory pool, when there is no offline user data corresponding to the management application in the memory pool For user data, offline user data corresponding to the management application is read from the database and stored in the memory pool.

Sending and retaining module 210, configured to send the offline user data corresponding to the management application to an online user terminal when there is offline user data corresponding to the management application in the memory pool, and reserve the data corresponding to the management application The offline user data is in the mempool.

The query management module 212 is configured to sequentially query the offline user data in the memory pool; if the offline user data in the memory pool is not accessed within a first preset time period, it will The offline user data that has not been accessed in the segment is stored in the database and deleted in the memory pool; if the offline user data in the memory pool has been accessed within the second preset time period, it is retained in the first The offline user data that has been accessed within a preset period of time is stored in the memory pool.

In the following, the game is mainly used as an example to introduce the data management system when the game is running.

Firstly, the overall structure of data management using the data management system described in the embodiment of the present invention is introduced.

Client game refers to an online game in which the official server is set up, and the user downloads the installation file to install the client and connects to the server through the Internet for multiplayer interaction.

Duration-based online games (referred to as "duration games") refer to online games that players need to spend a long time continuously experiencing, such as most client games.

Wherein, the client game is called the duration game, the corresponding server is called the duration server, the corresponding client is called the duration client, and the data in the game is called the duration data.

Specifically, as shown in FIG. 6 , it is a schematic structural diagram of managing offline user data in a client game in an embodiment of the present invention.

It can be seen from FIG. 6 that the duration server may include a fragment time data processing module. The client game mentioned in the embodiment of the present invention may be the above-mentioned duration game, and the client of the client game may be the above-mentioned duration client; the server of the client game may be the above-mentioned duration server. Wherein, the fragment time data processing module may be a combination of the above-mentioned loading module 200 , query module 206 , read storage module 208 , sending reservation module 210 and query management module 212 .

To sum up, the data management system disclosed in the embodiment of the present invention has the following advantages:

Create a fixed-capacity memory pool in the server of the client platform, and load frequently accessed offline user data into the memory pool in advance each time the server application is started. During the running of the server application, when an online user's application for offline user data management is received, it will query whether there is offline user data to be managed in the memory pool. If it exists, the offline user data to be managed (high-frequency access offline user data) to the online user terminal, and keep the offline user data to be managed (offline user data with high frequency access) in the memory pool; if it does not exist, read the offline user data to be managed from the database (low frequency access Offline user data accessed by users), loaded into the memory pool, and then the offline user data to be managed (offline user data with infrequent access) is sent from the memory pool to the online user terminal, and the managed offline user data (offline user data with infrequent access) User data) is stored in the database, and the offline user data is deleted in the memory pool. Load and cache frequently accessed offline user data in the memory pool in advance, store infrequently accessed offline user data in the memory pool and release it from the memory pool, and frequently access offline user data remain in the memory pool , only save offline user data accessed infrequently to the database, reducing the storage pressure on the database side.

Moreover, a memory pool with a fixed capacity is used to load and cache offline user data. The capacity of the memory pool is fixed. Clearing the offline user data therein and loading and caching the offline user data into the memory pool results in less memory fragmentation. If you use a memory pool with dynamic capacity to load and cache offline user data, the more offline user data you load and cache, the larger the capacity of the memory pool will be, and a memory pool with a relatively large capacity will generate more memory fragments.

Use a fixed-capacity memory pool to load and cache offline user data, and the capacity of the remaining memory on the server side is also fixed, so that the remaining memory on the server side will not decrease because the memory pool for loading and caching offline user data is getting larger and larger. The memory capacity used by the server side for application running.

Because less memory fragments are generated, the running risk of the server is reduced (the more memory fragments, the higher the risk of abnormal server downtime).

At the same time, the offline user data in the memory pool is dynamically adjusted. When high-frequency access to offline user data becomes low-frequency access to offline user data, these offline user data can be cleaned up in time, which improves the utilization rate of the memory pool.

Furthermore, since the offline user data is cached in the memory pool, when the connection between the server and the database is disconnected, the offline user data can be safely stored in the memory pool, and when the connection is re-established, the offline user data can continue to be stored in the database, reducing the The risk of offline user data loss is reduced.

As for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the related parts, please refer to the part of the description of the method embodiment.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other.

The data management method and system disclosed in the embodiments of the present invention have been introduced in detail above. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The descriptions of the above embodiments are only used to help understand the present invention. The method of the invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, the content of this specification should not be understood To limit the present invention.

Claims (10)

1. a kind of data managing method, it is characterised in that including：

When server application starts, loading in advance meets the offline user data of storage condition to the fixed capacity created In memory pool, the memory pool of the fixed capacity is a part for the server memory；

In server application running, management application of the online user to offline user data, the management application are received There are mapping relations with offline user data；

Verify whether the online user and the management application are respectively provided with the authority being managed to offline user data；

When the online user and the management application are respectively provided with the authority being managed to offline user data, inquiry is described It whether there is offline user data corresponding with the management application in memory pool；

When existing in the memory pool with the management corresponding offline user data of application, send and the management application pair The offline user data answered retain offline user data corresponding with the management application described interior to online user's terminal Deposit in pond.

2. according to the method described in claim 1, it is characterised in that whether there is and the pipe in the inquiry memory pool After the corresponding offline user data of reason application, methods described also includes：

When in the memory pool be not present with it is described management apply corresponding offline user data when, read out from database and Corresponding offline user data are applied in the management, and are stored into the memory pool.

3. according to the method described in claim 1, it is characterised in that the checking online user and the management application are It is no to be respectively provided with the authority being managed to offline user data, including：

Judge whether the online user belongs to the authority with management offline user data corresponding with the management application User；

When the online user belongs to the user of the authority with management offline user data corresponding with the management application, Judge whether the management application meets the management condition of offline user data corresponding with the management application, the management bar Whether each item data that part is included in offline user data allows to be read, change and delete；

When the online user belongs to the user with management with the authority for managing the corresponding offline user data of application, and When the management application meets the management condition of offline user data corresponding with the management application, the online user is determined The authority being managed to offline user data is respectively provided with the management application；

When the online user is not belonging to the user of the authority with management offline user data corresponding with the management application When, determine that the online user does not have the authority being managed to offline user data；When it is described management application do not meet with When the management condition of corresponding offline user data is applied in the management, determine that the management application does not have to offline user The authority that data are managed.

4. according to the method described in claim 1, it is characterised in that：

The storage condition is more than or equal to predetermined threshold for the access frequency of offline user data.

5. according to the method described in claim 1, it is characterised in that methods described also includes：

The offline user data inquired about successively in the memory pool；

, will be preset described first if the offline user data in the memory pool are not accessed within the first preset time period Accessed offline user data storage is not deleted into database, and in the memory pool in period；

If the offline user data in the memory pool are accessed within the second preset time period, described second is retained in pre- The offline user data being accessed in the period are put into the memory pool；Wherein, first preset time period is more than institute Stated for the second preset time period.

6. a kind of data management system, it is characterised in that including：

Load-on module, for when server application starts, loading in advance meets the offline user data of storage condition to having created In the memory pool for the fixed capacity built, the memory pool of the fixed capacity is a part for the server memory；

Receiving module, in server application running, receiving management application of the online user to offline user data, The management application has mapping relations with offline user data；

Authentication module, for verifying whether the online user and the management application are respectively provided with and are managed to offline user data The authority of reason；

Enquiry module, for being respectively provided with the power being managed to offline user data when the online user and the management application In limited time, inquire about in the memory pool and whether there is offline user data corresponding with the management application；

Reservation module is sent, for when existing in the memory pool with the management corresponding offline user data of application, sending out Send with the corresponding offline user data of the management apply to online user's terminal, and retain with it is described manage application it is corresponding from Line user data is in the memory pool.

7. system according to claim 6, it is characterised in that the system also includes：

Memory module is read, for being inquired about in the enquiry module in the memory pool with the presence or absence of corresponding with the management application Offline user data after, when in the memory pool be not present with it is described management application corresponding offline user data when, from Offline user data corresponding with the management application are read out in database, and are stored into the memory pool.

8. system according to claim 6, it is characterised in that the authentication module, including：

Online user's judging submodule, for judging whether the online user belongs to corresponding with the management application with management Offline user data authority user；

Management application judging submodule, for belonging to corresponding offline with management and the management application as the online user During the user of the authority of user data, judge whether the management application meets offline user number corresponding with the management application According to management condition, the management condition include offline user data in each item data whether allow to be read, change and delete Remove；

Determination sub-module, for belonging to as the online user with management offline user data corresponding with the management application Authority user, and the management application is when meeting the management condition with the corresponding offline user data of the management application, Determine that the online user and the management application are respectively provided with the authority being managed to offline user data；When the online use When family is not belonging to the user of the authority with management offline user data corresponding with the management application, the online use is determined Family does not have the authority being managed to offline user data；When it is described management application do not meet with it is described management application it is corresponding During the management condition of offline user data, determine the management application without the power being managed to offline user data Limit.

9. system according to claim 6, it is characterised in that：

The storage condition is more than or equal to predetermined threshold for the access frequency of offline user data.

10. system according to claim 6, it is characterised in that the system also includes：

Searching and managing module, for inquiring about the offline user data in the memory pool successively；If in the memory pool from Line user data is not accessed within the first preset time period, the offline use not being accessed within first preset time period User data is stored into database, and is deleted in the memory pool；If the offline user data in the memory pool are It is accessed in two preset time periods, is retained in the offline user data that are accessed in second preset time period to described In memory pool；Wherein, first preset time period is more than second preset time period.