Data processing method, device and equipment and readable storage medium

By generating and sending an entity sequence list, the receiving server performs reverse parsing based on the orchestration location, which solves the problems of low efficiency and poor timeliness in traditional entity migration, and realizes efficient and complete migration and rapid recovery of entity data.

CN119003481APending Publication Date: 2024-11-22TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310572076.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-19
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In traditional seamless large-scale entity migration solutions, the sending server cannot determine the relationships between entities in a timely manner, which means that the receiving server needs to wait for all relationships to be determined before it can restore the entities, thus reducing migration efficiency and timeliness.

Method used

By obtaining the object entity that triggered the migration event and its associated entities, an entity sequence table is generated and sent to the receiving server. The receiving server performs reverse parsing based on the orchestration position to ensure that the serialized packets in the entity sequence table are processed sequentially, thereby achieving entity integrity and rapid recovery.

Benefits of technology

It improves the efficiency of entity migration and the timeliness of entity recovery on the receiving server, reduces the processing complexity of the receiving server, and ensures the integrity and order of entity data during the migration process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119003481A_ABST
    Figure CN119003481A_ABST
Patent Text Reader

Abstract

The invention discloses a data processing method and device, equipment and a readable storage medium. The method comprises the steps that an object entity triggering a migration event is obtained, M associated entities associated with the object entity are obtained, and the object entity and the M associated entities are determined as to-be-migrated entities added to an entity association table in sequence; obtaining business data of each entity to be migrated in the first environment, generating a serialized packet corresponding to each business data, and forming M + 1 serialized packets containing the business data into an entity sequence table; and sending the entity sequence table to an immigration server, so that the immigration server sequentially carries out inverse analysis on the serialized packets in the entity sequence table based on the arrangement position to obtain immigrated entities. By adopting the method and the device, the entity migration efficiency can be improved, and the timeliness of recovering the immigrated entity by the immigration server is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method, device, equipment and readable storage medium. Background Art

[0002] In the traditional seamless big world entity migration solution, when multiple entity data (for example, entity data can be virtual characters or virtual props, etc.) are migrated, the outgoing server queues and waits for the previous entity to complete the migration before migrating the next entity. Therefore, the incoming server cannot determine the relationship between entities after receiving the entity, and therefore cannot immediately restore the entity. After the entire migration task is completed, the outgoing server needs to spend a lot of time to determine the relationship between all entities, and the incoming server can restore the migrated entity based on the relationship. It can be seen that the upper-level business module consumes a lot of time to determine the relationship between all entities, which will lead to low entity migration efficiency, and the incoming server needs to wait until the relationship between all entities is determined before it can restore the entity, which in turn reduces the timeliness of the incoming server to restore the migrated entity. Summary of the invention

[0003] The embodiments of the present application provide a data processing method, apparatus, device and readable storage medium, which can improve the efficiency of entity migration and improve the timeliness of recovery of the migrated entity by the migrated server.

[0004] On the one hand, an embodiment of the present application provides a data processing method, including:

[0005] Acquire an object entity that triggers a migration event, acquire M associated entities associated with the object entity, and determine the object entity and the M associated entities as entities to be migrated that are sequentially added to an entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in a first environment of the virtual world;

[0006] Obtain business data of each entity to be migrated in the first environment, generate serialized packages corresponding to each business data, and group M+1 serialized packages containing business data into an entity sequence table; the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table;

[0007] The entity sequence list is sent to the migration server so that the migration server can reverse parse the serialized packages in the entity sequence list in sequence based on the arrangement position to obtain the migrated entities; the migrated entities include object entities and M associated entities; the migrated entities stored in the migration server are virtual objects in the second environment of the virtual world.

[0008] The M associated entities associated with the object entity are obtained, including:

[0009] Taking the object entity as the root node, in the entity set belonging to the first environment of the virtual world, recursively query the entities that have a child node relationship with the root node and the entities that have a leaf node relationship with the root node, and determine the recursively queried entities as M associated entities associated with the object entity.

[0010] The business data of each entity to be migrated in the first environment is obtained, a serialized package corresponding to each business data is generated, and M+1 serialized packages containing business data are grouped into an entity sequence table, including:

[0011] Obtaining entity attribute location information corresponding to M+1 entities to be migrated, and obtaining business data of the M+1 entities to be migrated in the first environment according to the entity attribute location information; the entity attribute location information includes environment information where the virtual object is located and role type information;

[0012] Serialized packages corresponding to the entity attribute location information are generated respectively through M+1 business data, and the M+1 serialized packages containing business data are combined into an entity sequence table.

[0013] Among them, it also includes:

[0014] Obtain the distributed entities corresponding to the M+1 entities to be migrated, and perform authorization downgrade on the entities to be migrated in the entity association table; the distributed entity is used to record the entity attribute location information of the entity to be migrated each time a migration event is triggered, and the authorization downgrade status of the entity to be migrated is used to indicate that the entity attribute location information associated with the entity to be migrated is solidified;

[0015] Write the M+1 solidified entity attribute location information into the distributed entity corresponding to the associated entity to be migrated; one distributed entity contains one solidified entity attribute location information;

[0016] If a migration exception occurs during the process of sending the entity sequence list to the migration server, the distributed entity associated with the entity sequence list is obtained, the business data is re-obtained through the entity attribute location information recorded by the distributed entity, and the serialized packages corresponding to each business data are generated again, and the step of combining M+1 serialized packages containing business data into an entity sequence list is performed.

[0017] Among them, the M+1 entities to be migrated include the entity to be migrated S i , M+1 entity attribute location information includes the entity to be migrated S i The corresponding entity attribute location information P i; i is a positive integer less than or equal to M+1; obtaining the business data of M+1 entities to be migrated in the first environment according to the entity attribute location information, including:

[0018] If the entity to be migrated S i The corresponding entity attribute location information P i If there is an attribute identifier for the migration server in the entity attribute location information P i The entity information indicated by the attribute identifier in the first environment is obtained. i Corresponding business data; the attribute identifier is used to record entity attribute location information P in the first environment i The identifier of the entity information that has been modified;

[0019] If the entity to be migrated S i The corresponding entity attribute location information P i If there is no attribute identifier for the migration server in the entity attribute location information P i Each entity information in the first environment is obtained to migrate the entity S i The corresponding business data.

[0020] Among them, the M+1 entities to be migrated include the entity to be migrated S j , M+1 entity attribute location information includes the entity to be migrated S j The corresponding entity attribute location information P j ; j is a positive integer less than or equal to M+1; obtaining the business data of M+1 entities to be migrated in the first environment according to the entity attribute location information, including:

[0021] Get entity location attribute information P j Entities to be migrated S j role type information; role types include authoritative roles and proxy roles, the authoritative role is a virtual object that acts freely in the first environment, and the proxy role is a virtual object used to synchronize the actions of the authoritative role in the first environment;

[0022] If the entity location attribute information P j Indicates the entity to be migrated S j If it is an authoritative role, then obtain the entity to be migrated S j The private and public data of the entity S to be migrated j The private data and public data of the entity S to be migrated j Corresponding business data;

[0023] If the entity location attribute information P j Indicates the entity to be migrated S j For the proxy role, get the entity to be migrated Sj Public data of the entity to be migrated S j The public data of the entity S to be migrated j The corresponding business data.

[0024] Among them, the M+1 entities to be migrated include the entity to be migrated S t , t is a positive integer less than or equal to M+1; a serialized package corresponding to the entity attribute location information is generated through M+1 business data, including:

[0025] If the entity to be migrated S t The entity attribute location information indicates the entity to be migrated S t If it is an authoritative role, then obtain the entity to be migrated S t Private data in business data;

[0026] Get the entity S to be migrated. t The data package of public data in the business data is treated as the migration entity S t Serialize the private data in the business data to obtain the serialized private data, and add the serialized private data to the entity S to be migrated t At the end of the corresponding data packet, the entity to be migrated S is obtained t The serialized package corresponding to the entity attribute location information.

[0027] Among them, M+1 serialized packages containing business data are grouped into an entity sequence table, including:

[0028] According to the arrangement position of the entity to be migrated in the entity association table, M+1 position identifiers representing the arrangement position of M+1 serialized packages are generated, the M+1 serialized packages are sorted by the M+1 position identifiers, and the M+1 serialized packages are grouped into an entity sequence list.

[0029] The step of sending the entity sequence list to the migration server includes:

[0030] The entity sequence list is divided to obtain a plurality of unit data packets; the unit data packets include unit labels, and the unit labels are used to verify the position of the unit data packets in the entity sequence list;

[0031] The multiple unit data packets are sent to the migration server, so that the migration server reorganizes the multiple unit data packets into an entity sequence list in sequence according to the unit labels, and reversely parses the entity sequence list to obtain the migrated entity.

[0032] On the one hand, an embodiment of the present application provides another data processing method, including:

[0033] Obtaining an entity sequence list sent by a migration server; the entity sequence list includes M+1 serialized packages, the serialized packages include business data of entities to be migrated, and the entities to be migrated stored in the migration server are virtual objects in a first environment of a virtual world; the M+1 entities to be migrated associated with the M+1 serialized packages include an object entity that triggers a migration event and M associated entities associated with the object entity;

[0034] Based on the arrangement position, the serialized packages in the entity sequence table are reverse parsed in turn to obtain the migrated entities; the arrangement position refers to the arrangement position of the entity to be migrated in the entity association table generated by the migration server, and the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; the entity association table is used to store M+1 entities to be migrated in sequence when the object entity that triggers the migration event is obtained; the migrated entities include the object entity and M associated entities; the migrated entities are virtual objects in the second environment of the virtual world.

[0035] Among them, based on the arrangement position, the serialized packages in the entity sequence table are reverse parsed in turn to obtain the migrated entities, including:

[0036] Based on the arrangement position, the serialized packages in the entity sequence list are reverse parsed in turn to obtain the parsed entities corresponding to M+1 serialized packages respectively; the M+1 parsed entities include the parsed entity Q i , i is a positive integer less than or equal to M+1;

[0037] will be combined with the resolved entity Q i The business data in the corresponding serialized package is written into the parsed entity Q i , get the intermediate parsed entity;

[0038] If the intermediate resolution entity has an attribute identifier, obtain the local entity associated with the intermediate resolution entity in the second environment of the virtual world, perform attribute callback on the data indicated by the attribute identifier in the local business data associated with the local entity, write the callback data into the intermediate resolution entity, and obtain the data associated with the resolved entity Q. i The corresponding migrated entity.

[0039] An embodiment of the present application provides a data processing device, including:

[0040] An entity acquisition module is used to acquire an object entity that triggers a migration event, acquire M associated entities associated with the object entity, and determine the object entity and the M associated entities as entities to be migrated that are sequentially added to the entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in the first environment of the virtual world;

[0041] A sequence table generation module is used to obtain the business data of each entity to be migrated in the first environment, generate a serialized package corresponding to each business data, and group M+1 serialized packages containing business data into an entity sequence table; the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table;

[0042] The sending module is used to send the entity sequence list to the migration server, so that the migration server can reversely parse the serialized packages in the entity sequence list in turn based on the arrangement position to obtain the migrated entities; the migrated entities include object entities and M associated entities; the migrated entities stored in the migration server are virtual objects in the second environment of the virtual world.

[0043] Among them, the entity acquisition module is specifically used to take the object entity as the root node, and recursively query the entities that have a child node relationship with the root node and the entities that have a leaf node relationship with the root node in the entity set belonging to the first environment of the virtual world, and determine the recursively queried entities as M associated entities associated with the object entity.

[0044] Wherein, the sequence table generation module includes:

[0045] A business data acquisition unit is used to acquire entity attribute location information corresponding to M+1 entities to be migrated, and acquire business data of the M+1 entities to be migrated in the first environment according to the entity attribute location information; the entity attribute location information includes environment information where the virtual object is located and role type information;

[0046] The serialization package generation unit is used to generate serialization packages corresponding to the entity attribute location information through M+1 business data respectively, and group the M+1 serialization packages containing business data into an entity sequence table.

[0047] Wherein, the sequence table generation module also includes:

[0048] The distributed entity acquisition unit is used to acquire the distributed entities corresponding to the M+1 entities to be migrated, and perform authorization downgrade on the entities to be migrated in the entity association table; the distributed entity is used to record the entity attribute location information of the entity to be migrated each time a migration event is triggered, and the authorization downgrade state of the entity to be migrated is used to indicate that the entity attribute location information associated with the entity to be migrated is solidified;

[0049] The information solidification unit is used to write M+1 solidified entity attribute location information into the distributed entities corresponding to the associated entities to be migrated; one distributed entity contains one solidified entity attribute location information;

[0050] The exception handling unit is used to obtain the distributed entity associated with the entity sequence list if a migration exception occurs during the process of sending the entity sequence list to the migration server, re-acquire the business data through the entity attribute location information recorded by the distributed entity, re-execute the generation of serialized packages corresponding to each business data, and combine M+1 serialized packages containing business data into an entity sequence list.

[0051] The M+1 entities to be migrated include the entity to be migrated S i The M+1 entity attribute location information includes the entity to be migrated S i The corresponding entity attribute location information P i ; i is a positive integer less than or equal to M+1; the business data acquisition unit comprises:

[0052] The first processing subunit is used to: i The corresponding entity attribute location information P i If there is an attribute identifier for the migration server in the entity attribute location information P i The entity information indicated by the attribute identifier in the first environment is obtained. i Corresponding business data; the attribute identifier is used to record entity attribute location information P in the first environment i The identifier of the entity information that has been modified;

[0053] The second processing subunit is used to: i The corresponding entity attribute location information P i If there is no attribute identifier for the migration server in the entity attribute location information P i Each entity information in the first environment is obtained to migrate the entity S i The corresponding business data.

[0054] The M+1 entities to be migrated include the entity to be migrated S j The M+1 entity attribute location information includes the entity to be migrated S j The corresponding entity attribute location information P j ; j is a positive integer less than or equal to M+1; the business data acquisition unit comprises:

[0055] Role type acquisition subunit, used to obtain entity location attribute information P j Entities to be migrated S j role type information; role types include authoritative roles and proxy roles, the authoritative role is a virtual object that acts freely in the first environment, and the proxy role is a virtual object used to synchronize the actions of the authoritative role in the first environment;

[0056] The first determination subunit is used to determine if the entity location attribute information P j Indicates the entity to be migrated S j If it is an authoritative role, then obtain the entity to be migrated S j The private and public data of the entity S to be migrated j The private data and public data of the entity S to be migrated j Corresponding business data;

[0057] The second determination subunit is used to determine if the entity location attribute information P j Indicates the entity to be migrated S j For the proxy role, get the entity to be migrated S j Public data of the entity to be migrated S j The public data of the entity S to be migrated j The corresponding business data.

[0058] The M+1 entities to be migrated include the entity to be migrated S t , t is a positive integer less than or equal to M+1; the serialization packet generation unit includes:

[0059] Private data acquisition subunit, used for the entity S to be migrated t The entity attribute location information indicates the entity to be migrated S t If it is an authoritative role, then obtain the entity to be migrated S t Private data in business data;

[0060] Private data serialization subunit, used to obtain the entity S to be migrated t The data package of public data in the business data is treated as the migration entity S t Serialize the private data in the business data to obtain the serialized private data, and add the serialized private data to the entity S to be migrated t At the end of the corresponding data packet, the entity to be migrated S is obtained t The serialized package corresponding to the entity attribute location information.

[0061] Among them, the sequence table generation module is specifically used to generate M+1 position identifiers representing the arrangement positions of M+1 serialized packages according to the arrangement positions of the entities to be migrated in the entity association table, sort the M+1 serialized packages through the M+1 position identifiers, and form the M+1 serialized packages into an entity sequence table.

[0062] The sending module includes:

[0063] A division unit, used for dividing the entity sequence list to obtain a plurality of unit data packets; the unit data packets include unit labels, and the unit labels are used for verifying the position of the unit data packets in the entity sequence list;

[0064] The reorganization unit is used to send multiple unit data packets to the migration server, so that the migration server reorganizes the multiple unit data packets into an entity sequence list in sequence through the unit labels, and reversely parses the entity sequence list to obtain the migrated entity.

[0065] On the one hand, an embodiment of the present application provides another data processing device, including:

[0066] The sequence list acquisition module is used to acquire the entity sequence list sent by the migration server; the entity sequence list includes M+1 serialization packages, the serialization packages include the business data of the entity to be migrated, and the entity to be migrated stored in the migration server is a virtual object in the first environment of the virtual world; the M+1 entities to be migrated associated with the M+1 serialization packages include the object entity that triggers the migration event and M associated entities associated with the object entity;

[0067] The reverse parsing module is used to reversely parse the serialized packages in the entity sequence table in turn based on the arrangement position to obtain the migrated entity; the arrangement position refers to the arrangement position of the entity to be migrated in the entity association table generated by the migration server, and the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; the entity association table is used to store M+1 entities to be migrated in sequence when the object entity that triggers the migration event is obtained; the migrated entity includes the object entity and M associated entities; the migrated entity is a virtual object in the second environment of the virtual world.

[0068] Among them, the inverse analysis module includes:

[0069] The parsed entity generation unit is used to reverse parse the serialized packages in the entity sequence table in turn based on the arrangement position to obtain parsed entities corresponding to M+1 serialized packages respectively; the M+1 parsed entities include the parsed entity Q i , i is a positive integer less than or equal to M+1;

[0070] Business data writing unit, used to write data related to the resolved entity Q i The business data in the corresponding serialized package is written into the parsed entity Q i , get the intermediate parsed entity;

[0071] The attribute callback unit is used to obtain the local entity associated with the intermediate resolution entity in the second environment of the virtual world if the intermediate resolution entity has an attribute identifier, perform attribute callback on the data indicated by the attribute identifier in the local business data associated with the local entity, write the callback data into the intermediate resolution entity, and obtain the data associated with the resolved entity Q. i The corresponding migrated entity.

[0072] On the one hand, an embodiment of the present application provides a computer device, including: a processor, a memory, and a network interface;

[0073] The processor is connected to the memory and the network interface, wherein the network interface is used to provide a data communication function, and the memory is used to store a computer program. When the computer program is executed by the processor, the computer device executes the method provided in the embodiment of the present application.

[0074] On the one hand, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. The computer program is suitable for being loaded and executed by a processor so that a computer device having the processor executes the method provided by the embodiment of the present application.

[0075] In one aspect, an embodiment of the present application provides a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, so that the computer device executes the method provided in the embodiment of the present application.

[0076] The embodiment of the present application obtains the object entity that triggers the migration event, obtains M associated entities associated with the object entity, determines the object entity and the M associated entities as entities to be migrated that are sequentially added to the entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in the first environment of the virtual world; obtains the business data of each entity to be migrated in the first environment, generates a serialized package corresponding to each business data, and groups the M+1 serialized packages containing the business data into an entity sequence table; the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; the entity sequence table is sent to the migration server, so that the migration server reversely parses the serialized packages in the entity sequence table based on the arrangement position to obtain the migrated entity; the migrated entity includes the object entity and the M associated entities; the migrated entity stored in the migration server is the virtual object in the second environment of the virtual world. It can be seen that the embodiment of the present application can ensure the integrity of multiple associated entities to be migrated (object entities and associated entities) during migration by adding the object entities to be migrated and the associated entities of the object entities to the same entity association table. The migration-out server can freely define the data arrival and processing order after the migration of multiple associated entities, which greatly reduces the processing complexity of the migration-in server after the disorderly migration of entity data, and can improve the efficiency of entity migration. Since the entity association table can reflect the association relationship between the entities to be migrated, the entity sequence table generated based on the entity association table also has the above-mentioned association relationship. Therefore, the migration-in server can restore the entity based on the association relationship in the entity sequence table after the migration of a single entity sequence table is completed, which improves the timeliness of the migration-in server to restore the migrated entity. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0078] Figure 1 This is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0079] Figure 2 This is a schematic diagram of a data processing scenario provided by an embodiment of the present application;

[0080] Figure 3 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 1 ;

[0081] Figure 4 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 2 ;

[0082] Figure 5 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 3 ;

[0083] Figure 6 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 4 ;

[0084] Figure 7 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 5 ;

[0085] Figure 8 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 6 ;

[0086] Fig. 9 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. Figure 1 ;

[0087] Fig.10 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. Figure 2 ;

[0088] Fig.11 It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0089] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0090] See also Figure 1 , Figure 1 This is a schematic diagram of a network architecture provided by an embodiment of the present application. The schematic diagram of the network architecture may include an outgoing server 100 and an incoming server 200, and the outgoing server 100 may be in communication connection with the incoming server 200. The above communication connection does not limit the connection mode, and may be directly or indirectly connected through a wired communication mode, directly or indirectly connected through a wireless communication mode, or through other modes, which are not limited by the present application.

[0091] Among them, the migration server 100 can be a server that provides data services for the first environment of the virtual world, and the migration server 200 can be a server that provides data services for the second environment of the virtual world. The virtual world can be a virtual social scene adapted to the seamless world (Seamless World), including but not limited to the consumer shopping world scene, the cultural tourism world scene, the game entertainment world scene, the education learning world scene, etc. The first environment and the second environment are different scenes in the virtual world, such as the first environment and the second environment can be different virtual geographical areas in the virtual world. Among them, the virtual social scene refers to a 3D (short for Three Dimensions) virtual space with link perception and sharing characteristics based on the future Internet, which is enhanced by virtual physical reality and presents convergence and physical persistence characteristics, or an interactive, immersive and collaborative world. Just as the physical universe is a series of worlds interconnected in space, the virtual social scene can also be regarded as a collection of many worlds.

[0092] Specifically, the migration server 100 may respond to the migration event and obtain the object entity (also referred to as entity) that triggers the migration event. The object entity may be a virtual object in the first environment of the virtual world, such as a character, environmental item, equipment prop, etc. The migration event may be an event in which the object entity affects the stage state of the virtual world in the virtual world, for example, a virtual object in the virtual world is about to move from the first environment to the second environment.

[0093] The migration server 100 can obtain the associated entities (AssociatedEntity) associated with each object entity. For example, if virtual character 1 holds virtual equipment 2, the migration server 100 can determine virtual equipment 2 as the associated entity of virtual character 1. The migration server 100 can determine the object entity and the associated entity of the object entity as the entity to be migrated, that is, the virtual object in the first environment of the virtual world, and add the above-mentioned entity to be migrated to the same entity association table.

[0094] The outgoing server 100 can transfer the mutually related entities to be migrated to the incoming server in a package. Since the associations are clear, the incoming server can directly restore the entities to be migrated based on the associations in the entity association table to obtain the migrated entities. The migrated entities can include object entities and their associated entities.

[0095] The embodiment of the present application can ensure the integrity of multiple associated entities to be migrated (object entities and associated entities) during migration by adding the object entities to be migrated and the associated entities of the object entities to the same entity association table. Therefore, the outgoing server can freely define the data arrival and processing order after the migration of multiple associated entities, which greatly reduces the processing complexity of the incoming server after the disorderly migration of entity data, and can improve the efficiency of entity migration. Since the entity association table can reflect the association relationship between the entities to be migrated, the entity sequence table generated based on the entity association table also has the above-mentioned association relationship. Therefore, the incoming server can restore the entity based on the association relationship in the entity sequence table after the migration of a single entity sequence table is completed, which improves the timeliness of the incoming server to restore the migrated entity.

[0096] See also Figure 2 , Figure 2 This is a schematic diagram of a data processing scenario provided by an embodiment of the present application, taking the virtual world as a game entertainment world scenario as an example.

[0097] like Figure 2 As shown, the migration server 100 may be a server that provides data services for the first environment 101 of the virtual world, and the migration server 200 may be a server that provides data services for the second environment 201 of the virtual world. A migration event may be an event in which an object entity in the virtual world affects the stage state of the virtual world, for example, a virtual object in the virtual world is about to move from the first environment to the second environment.

[0098] The virtual vehicle 102 may be a virtual object in the first environment 101 . When the vehicle 102 travels to a predetermined position in the first environment 101 and is about to travel to the second environment 201 , the migration server 100 may be triggered to generate a migration event.

[0099] The migration server 100 may obtain the associated entities of the virtual vehicle 102 (i.e., the object entity that triggers the migration event), for example, the vehicle 102 has a virtual character 103 and a virtual item 104. Then, the migration server 100 may determine that the virtual character 103 and the virtual item 104 are the associated entities of the virtual vehicle 102. The migration server 100 may determine that the virtual vehicle 102, the virtual character 103, and the virtual item 104 are the entities to be migrated, and add the entities to be migrated to the entity association table 105.

[0100] Among them, the object entity representing the virtual vehicle 102 can be at the head position of the entity association table, and the position of the associated entity in the entity association table 105 can be further sorted based on the association relationship between the associated entities. For example, the association relationship between the virtual character 103 and the virtual item 104 is that the virtual character 103 holds the virtual item 104, then the order of the arrangement position of the virtual vehicle 102, the virtual character 103, and the virtual item 104 in the entity association table can be virtual vehicle 102, virtual character 103, virtual item 104 in sequence. The position of the associated entity in the entity association table can also be determined by the migration server 100 according to business needs, and the embodiment of the present application does not limit this.

[0101] The migration server 100 can obtain entity attribute location information corresponding to the entities to be migrated. The entity attribute location information can be the environment or role information of the entities to be migrated in the virtual world, which can include the environment where the virtual object is located (which can be a scene in the virtual world such as the first environment, the second environment, etc.), the role type it has, and the environment where the virtual object owner is located and the role type he has.

[0102] The role types include simulated proxy and authority. An authority refers to an entity that can act on its own and synchronize its behavior to the proxy. For example, the role type of the virtual character 103 can be an authority. A proxy refers to an entity that can only passively synchronize the behavior of the entity associated with the authority on the server and cannot act on its own. For example, the role type of the virtual vehicle 102 and the virtual item 104 can be a proxy.

[0103] The migration server 100 can obtain the business data of the entity to be migrated in the first environment 101 of the virtual world through the entity attribute location information. The business data may include public data (Public Attribute) and private data (Private Attribute). Public data is data that any entity will carry away when triggering a migration event. Private data refers to data that an entity whose role type is an authoritative role will carry away when triggering a migration event. For example, public data can be the coordinate data of a virtual vehicle 102, a virtual character 103, and a virtual item 104, and private data can be the action data of the virtual character 103.

[0104] The migration server 100 may obtain public data and private data of the virtual character 103 as business data of the virtual character 103 , obtain public data of the virtual vehicle 102 as business data of the virtual vehicle 102 , and obtain public data of the virtual item 104 as business data of the virtual item 104 .

[0105] The outgoing server 100 can generate a serialized package (Entity Bunch) corresponding to the attribute location information of the entity to which it belongs through each business data, and obtain several serialized packages (i.e. one serialized package for one entity to be migrated), that is, the serialized package can store the business data corresponding to the entity to be migrated, and the outgoing server 100 can combine several serialized packages into an entity sequence table in order according to the arrangement position of the entity to be migrated in the entity association table, so that the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table. Therefore, the incoming server can determine the association relationship between the entities to be migrated based on the arrangement position in the entity sequence table.

[0106] The migration-out server 100 may send the entity sequence list to the migration-in server 200, and the migration-in server 200 reversely parses the serialized package in the entity sequence list to obtain the virtual vehicle 102, the virtual character 103, and the virtual item 104 in the second environment 201. The migration-in server 200 may present the virtual vehicle 102, the virtual character 103, and the virtual item 104 in the second environment 201 to achieve the display effect of the virtual character 103 driving the virtual vehicle 102 from the first environment 101 to the second environment 201.

[0107] The embodiment of the present application can ensure the integrity of multiple associated entities to be migrated (object entities and associated entities) during migration by adding the object entities to be migrated and the associated entities of the object entities to the same entity association table. The outgoing server can freely define the data arrival and processing order after the migration of multiple associated entities, which greatly reduces the processing complexity of the incoming server after the disorderly migration of entity data, and can improve the efficiency of entity migration. Since the entity association table can reflect the association relationship between the entities to be migrated, the entity sequence table generated based on the entity association table also has the above-mentioned association relationship. Therefore, the incoming server can restore the entity based on the association relationship in the entity sequence table after the migration of a single entity sequence table is completed, which improves the timeliness of the incoming server to restore the migrated entity.

[0108] See also Figure 3 , Figure 3 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 1 The data processing method may be executed by a migration server, which may be Figure 1 The migration server 100 is shown. Figure 3 As shown, the method may include:

[0109] Step S101, obtaining an object entity that triggers a migration event, obtaining M associated entities associated with the object entity, and determining the object entity and the M associated entities as entities to be migrated that are sequentially added to an entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in a first environment of the virtual world;

[0110] Specifically, the migration server may obtain an object entity that triggers a migration event. The object entity may be a virtual object in the virtual world, such as a character, an environmental item, an equipment item, etc. The migration event may be an event in which the object entity in the virtual world affects the virtual world process, such as a virtual object in the virtual world is about to move from a first environment to a second environment.

[0111] The migration server may be a server that provides data services for the first environment of the virtual world, and the server that provides data services for the second environment of the virtual world may be called the migration server. The virtual world may be a virtual social scene adapted to the seamless world, including but not limited to the consumption shopping world scene, the cultural tourism world scene, the game entertainment world scene, the education learning world scene, etc.

[0112] The migration server can obtain the associated entity associated with the object entity. The associated entity refers to an entity (virtual object) with a calling relationship in the virtual world. The calling relationship can be a relationship between entities of ownership and being owned. For example, if virtual character 1 holds virtual equipment 2, the migration server can determine virtual equipment 2 as the associated entity of virtual character 1. The calling relationship can also be a dependency relationship between entities. For example, if virtual equipment 1 contains virtual item 2, the migration server can determine virtual equipment 1 as the associated entity of virtual item 2. The specific manner in which the migration server determines the association relationship between entities is not limited in the embodiments of the present application.

[0113] The migration-out server may determine the object entity and entities associated with the object entity as entities to be migrated, and the entities to be migrated are virtual objects in the first environment of the virtual world.

[0114] The migration server can add the mutually related entities to be migrated to the same entity association table, wherein the object entity can be at the header position of the entity association table, and the position of the related entity in the entity association table can be further sorted based on the association relationship between the related entities. For example, the association relationship between a virtual vehicle and a virtual character is that a virtual vehicle has a virtual character riding in it, and the association relationship between a virtual character and a virtual item is that a virtual character holds a virtual item. Then the order of arrangement of the virtual vehicle, virtual character, and virtual item in the entity association table can be virtual vehicle, virtual character, and virtual item, respectively. The position of the related entity in the entity association table can also be determined by the migration server according to business needs, and the embodiments of the present application are not limited here.

[0115] Step S102, obtaining the business data of each entity to be migrated in the first environment, generating a serialized package corresponding to each business data, and grouping M+1 serialized packages containing the business data into an entity sequence table; the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table;

[0116] Specifically, the migration server can obtain entity attribute location information corresponding to the entities to be migrated. The entity attribute location information can be the environment or role information of the entities to be migrated in the virtual world, which can include the environment where the virtual object is located (which can be a scene in the virtual world such as the first environment and the second environment), the role type it has, and the environment where the virtual object owner is located and the role type he has.

[0117] Among them, the role types include proxy roles and authoritative roles. The authoritative role refers to an entity that can act on its own and synchronize its behavior to the proxy role. The proxy role refers to an entity that can only passively synchronize the behavior of the entity associated with the authoritative role on the server and cannot act on its own.

[0118] The migration server can obtain the business data of the entity to be migrated in the virtual world through the entity attribute location information. The business data may include public data and private data. Public data refers to the data that any entity will carry away when triggering a migration event. Private data refers to the data that an entity with the role type of an authoritative role will carry away when triggering a migration event.

[0119] The outgoing server can generate serialized packages corresponding to the attribute location information of the entities through the business data, and obtain several serialized packages (i.e. one serialized package for one entity to be migrated), that is, the serialized package can store the business data corresponding to the entity to be migrated. The outgoing server can combine several serialized packages into an entity sequence table according to the arrangement position of the entity to be migrated in the entity association table, so that the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table. Therefore, the incoming server can determine the association relationship between the entities to be migrated based on the arrangement position in the entity sequence table.

[0120] Step S103, sending the entity sequence list to the migration server, so that the migration server sequentially reversely parses the serialized packages in the entity sequence list based on the arrangement position to obtain the migrated entity; the migrated entity includes the object entity and M associated entities; the migrated entity stored in the migration server is a virtual object in the second environment of the virtual world;

[0121] Specifically, the outgoing server may send the entity sequence list to the outgoing server, and the outgoing server may reverse parse the serialized packages in turn according to the arrangement position of the serialized packages in the entity sequence list, obtain the migrated entities (which may include object entities and associated entities of the object entities), and complete the migration of the object entities and the associated entities corresponding to the object entities. The migrated entities are virtual objects in the second environment of the virtual world stored in the ingoing server.

[0122] The embodiment of the present application obtains the object entity that triggers the migration event, obtains M associated entities associated with the object entity, determines the object entity and the M associated entities as entities to be migrated that are sequentially added to the entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in the first environment of the virtual world; obtains the business data of each entity to be migrated in the first environment, generates a serialized package corresponding to each business data, and groups the M+1 serialized packages containing the business data into an entity sequence table; the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; the entity sequence table is sent to the migration server, so that the migration server reversely parses the serialized packages in the entity sequence table based on the arrangement position to obtain the migrated entity; the migrated entity includes the object entity and the M associated entities; the migrated entity stored in the migration server is the virtual object in the second environment of the virtual world. It can be seen that the embodiment of the present application can ensure the integrity of multiple associated entities to be migrated (object entities and associated entities) during migration by adding the object entities to be migrated and the associated entities of the object entities to the same entity association table. The migration-out server can freely define the data arrival and processing order after the migration of multiple associated entities, which greatly reduces the processing complexity of the migration-in server after the disorderly migration of entity data, and can improve the efficiency of entity migration. Since the entity association table can reflect the association relationship between the entities to be migrated, the entity sequence table generated based on the entity association table also has the above-mentioned association relationship. Therefore, the migration-in server can restore the entity based on the association relationship in the entity sequence table after the migration of a single entity sequence table is completed, which improves the timeliness of the migration-in server to restore the migrated entity.

[0123] See also Figure 4 , Figure 4 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 2 The data processing method may be executed by a migration server, which may be Figure 1 The migration server 100 is shown. Figure 4 As shown, the method may include:

[0124] Step S201, obtaining an object entity that triggers a migration event, obtaining M associated entities associated with the object entity, and determining the object entity and the M associated entities as entities to be migrated that are sequentially added to an entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in a first environment of the virtual world;

[0125] For details, please refer to Figure 5 , Figure 5 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 3 ,like Figure 5 As shown, the migration server can obtain the object entity that triggers the migration event. The object entity can be a virtual object in the virtual world, such as a character, an environmental item, an equipment item, etc. The migration event can be an event in which the object entity affects the virtual world process in the virtual world, for example, a virtual object in the virtual world is about to move from a first environment to a second environment.

[0126] The migration server may be a server that provides data services for the first environment of the virtual world, and the server that provides data services for the second environment of the virtual world may be a migration server. The virtual world may be a virtual social scene adapted to the seamless world, including but not limited to a consumption shopping world scene, a cultural tourism world scene, a game entertainment world scene, an education learning world scene, etc.

[0127] The migration server can obtain the associated entities associated with the object entity. The associated entities refer to entities (virtual objects) that have a calling relationship in the virtual world. The migration server can use the object entity as a tree root node to query its associated associated entities.

[0128] Among them, the specific method of migrating out of the server to query related entities can be: taking the object entity as the root node, recursively querying the entities that have a child node relationship with the root node and the entities that have a leaf node relationship with the root node in the entity set belonging to the first environment of the virtual world, and determining the recursively queried entities as M related entities associated with the object entity.

[0129] Specifically, the migration server may use the object entity as a tree root node for querying associated entities, and the tree root node is also the starting node of the query.

[0130] The migration server can recursively query the entities that are in a child node relationship with the tree root node and the entities that are in a leaf node relationship with the tree root node in the entity set belonging to the first environment of the virtual world.

[0131] Among them, the child node relationship may refer to the entity of the child node being the next layer entity that has an association relationship with the parent node in the entity set. The leaf node relationship may refer to the last layer entity that has an association relationship with the parent node in the entity set. The association relationship may be a calling relationship between entities in the virtual world, and the calling relationship may be a relationship of ownership and being owned between entities. For example, if character 1 holds equipment 2, then the migration server may determine equipment 2 as the associated entity of character 1; the calling relationship may also be a dependency relationship between entities. For example, if prop 2 exists in equipment 1, then the migration server may determine equipment 1 as the associated entity of prop 2. The specific method of determining the association between entities and the calling relationship is not limited in the embodiments of the present application.

[0132] like Figure 5 As shown, virtual character 1 holds virtual equipment 2, and virtual prop 3 exists in virtual equipment 2. Then the migration server can start querying with object entity 1 represented by virtual character 1 as the root node of the tree, query virtual equipment 2 that has a child node relationship with object entity 1, and use virtual equipment 2 as associated entity 1. The migration server can continue querying with associated entity 2 as the parent node until virtual prop 3, which is the leaf node of associated entity 1, is queried, and virtual prop 3 is used as associated entity 2.

[0133] The migration-out server may determine the entity obtained by the recursive query as an associated entity of the object entity, and determine the object entity and the associated entity of the object entity as entities to be migrated, where the entities to be migrated are virtual objects in the first environment of the virtual world.

[0134] like Figure 5 As shown, if the object entity has associated entities, the migration server can add the mutually associated entities to be migrated to the same entity association table, and can set the arrangement position between the associated entities, for example, Figure 5 The object entity 1 in can be used as the header of the entity association table, and the associated entity 1 and the associated entity 2 are added to the entity association table in the order of associated entity 1 to associated entity 2.

[0135] If the object entity has no associated entity, the migration server may determine the object entity as an entity association table alone. For example, the object entity 2 that has no associated entity may be determined as an entity association table alone.

[0136] Step S202, obtaining entity attribute location information corresponding to M+1 entities to be migrated respectively, and obtaining business data of the M+1 entities to be migrated respectively in the first environment according to the entity attribute location information;

[0137] Specifically, the migration server can obtain entity attribute location information corresponding to the entities to be migrated. The entity attribute location information can be the environment or role information of the entities to be migrated in the virtual world, which can include the environment where the virtual object is located (which can be a scene in the virtual world such as the first environment and the second environment), the role type it has, and the environment where the virtual object owner is located and the role type he has.

[0138] The entity attribute location information may also include the entity name (entity ID), the entity local environment identifier (the environment where the virtual object is located), the entity owner environment identifier (the environment where the virtual object owner is located), the local role type (the role type possessed), and the owner role type (the role type possessed by the virtual object owner). For example, the virtual objects are virtual character 1 and virtual equipment 2, and virtual character 1 owns virtual equipment 2, so virtual character 1 can be called the virtual object owner of virtual equipment 2.

[0139] Optionally, the migration server may first solidify the entity attribute location information of the entity to be migrated. After solidification, the entity attribute location information in the entity to be migrated no longer changes. The migration server may obtain the solidified entity attribute location information, and then store the entity attribute location information through the distributed entity. When an entity migration exception occurs in the above-mentioned entity to be migrated, the entity attribute location information of the entity to be migrated can be determined again.

[0140] Among them, the entity attribute location information of the entity to be migrated is solidified, and the specific process of storing the entity attribute location information through the distributed entity can be: obtaining the distributed entities corresponding to M+1 entities to be migrated respectively, and downgrading the authorization of the entities to be migrated in the entity association table; the distributed entity is used to record the entity attribute location information of the entity to be migrated each time a migration event is triggered, and the authorization downgrade status of the entity to be migrated is used to indicate that the entity attribute location information associated with the entity to be migrated is solidified; the M+1 solidified entity attribute location information are respectively written into the distributed entities corresponding to the associated entities to be migrated; one distributed entity contains one solidified entity attribute location information.

[0141] Specifically, the migration server can obtain the distributed entities corresponding to the entities to be migrated, that is, when the entity is established, it is used to store the environment and role type of the entity. One entity corresponds to one distributed entity in the first environment.

[0142] The structure of the distributed entity can be shown in Table 1:

[0143] Table 1

[0144]

[0145] The entity ID is the unique identifier of the entity, and the environment ID is the environment where the entity is located. A distributed entity can be uniquely identified by combining the entity ID and the environment ID. The owner ID is the environment where the entity is located. The local role is the role type of the entity, and the owner role is the role type of the owner of the entity.

[0146] The role type of an entity can be divided into a proxy role and an authoritative role based on the entity's ability to change its own state, the environment in which the entity is located, and the relationship between the owner's environment. An authoritative role refers to an entity that can act on its own and synchronize its actions to the proxy role. A proxy role refers to an entity that can only passively synchronize the actions of its authoritative role entity on the server and cannot act on its own.

[0147] Please also refer to Figure 6 , Figure 6 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 4 ,like Figure 6 As shown, the migration server can downgrade the authorization of the entity to be migrated, that is, adjust the role type of the entity to be migrated from the authoritative role to the proxy role, so as to solidify the entity attribute location information in the entity to be migrated. The role types of the object entity 1, the associated entity 1 and the associated entity 2 can be adjusted from the authoritative role to the proxy role, so that the entity attribute location information of the object entity 1, the associated entity 1 and the associated entity 2 will no longer change.

[0148] The migration-out server may write the solidified entity information into a distributed entity associated with the entity information, and store the entity attribute location information of this migration task through the distributed entity.

[0149] The migration server can obtain the business data of the entity to be migrated through the entity attribute location information in the entity to be migrated, or can obtain the business data through the entity attribute location information in the distributed entity.

[0150] Optionally, the migration server may also obtain the business data through the attribute identifier in the entity attribute location information. The attribute identifier refers to an identifier used to record the entity information modified in the entity attribute location information in the first environment.

[0151] Among them, the specific process of the migrating server obtaining the business data through the attribute identifier in the entity attribute location information can be: if there is an attribute identifier for the migrating server in the entity attribute location information Pi corresponding to the entity Si to be migrated, then the business data corresponding to the entity Si to be migrated is obtained in the first environment according to the entity information indicated by the attribute identifier in the entity attribute location information Pi; the attribute identifier is an identifier used to record the entity information that has been modified in the entity attribute location information Pi in the first environment; if there is no attribute identifier for the migrating server in the entity attribute location information Pi corresponding to the entity Si to be migrated, then the business data corresponding to the entity Si to be migrated is obtained in the first environment according to each entity information in the entity attribute location information Pi.

[0152] Specifically, the outgoing server may obtain the attribute identifier of the incoming server in the entity attribute location information, and the attribute identifier may record whether the entity has changed compared with the last migration task.

[0153] If the attribute identifier of the migration-in server exists in the entity attribute location information of the entity to be migrated, the migration-out server may obtain the business data in the first environment of the virtual world according to the entity information indicated by the attribute identifier.

[0154] If the attribute identifier of the migration-in server does not exist in the entity attribute location information of the entity to be migrated, the migration-out server may obtain the business data in the first environment of the virtual world according to the entity attribute location information.

[0155] For example, in the first migration task, the outgoing server migrates entity 1 to the incoming server. After the migration is completed, the entity information 2 corresponding to entity 1 of the outgoing server is modified, so the attribute identifier 3 for entity information 2 can record the modified information of entity information 2. In the second migration task that is still the outgoing server migrating entity 1 to the incoming server, the outgoing server can obtain the data corresponding to the modified information of entity information 2 through attribute identifier 3, instead of using the data corresponding to the entire entity attribute location information as business data.

[0156] The embodiment of the present application can compare the data corresponding to the entities in the outgoing server and the incoming server through the attribute identifier in the entity attribute location information, which can reduce the amount of data transmission in the migration task and improve the efficiency of the outgoing server transmitting entities and the incoming server parsing entities.

[0157] The business data obtained by the migration server may include public data and private data. Public data refers to the data that an entity will carry away when a migration event is triggered, and private data refers to the data that an entity with a role type of an authoritative role will carry away when a migration event is triggered.

[0158] The migration server can determine the data carried by the entity in the migration task according to the role type of the entity to be migrated. Different role types carry different data.

[0159] The specific process of determining the data carried by the entity in the migration task by the role type may be: obtaining the entity location attribute information P j Entities to be migrated S j The role type information includes the authoritative role and the proxy role, the authoritative role is a virtual object that moves freely in the first environment, and the proxy role is a virtual object used to synchronize the actions of the authoritative role in the first environment; if the entity position attribute information P j Indicates the entity to be migrated S j If it is an authoritative role, then obtain the entity to be migrated S j The private and public data of the entity S to be migrated j The private data and public data of the entity S to be migrated j Corresponding business data; if the entity location attribute information P j Indicates the entity to be migrated S j For the proxy role, get the entity to be migrated S j Public data of the entity to be migrated S j The public data of the entity to be migrated is S j The corresponding business data.

[0160] Specifically, the migration server can obtain the role type of the entity to be migrated. If the entity location attribute information indicates that the entity to be migrated is an authoritative role, the migration server can obtain the private data and public data of the entity to be migrated and use the private data and public data as the business data corresponding to the entity to be migrated.

[0161] If the entity location attribute information indicates that the entity to be migrated is a proxy role, public data of the entity to be migrated is obtained, and the public data is determined to be business data corresponding to the entity to be migrated.

[0162] For example, the virtual character is the entity of the authoritative role, and the virtual vehicle and virtual item are the entities of the agent role. Then, the migration server can obtain the public data and private data of the virtual character as the business data of the virtual character, obtain the public data of the virtual vehicle as the business data of the virtual vehicle, and obtain the public data of the virtual item as the business data of the virtual item.

[0163] The embodiment of the present application can obtain the required private data of the entity through the divided role type, so that the entity can carry the deep copy data at the memory level when migrating, avoiding the situation of not carrying or carrying all data due to unclassified, resulting in uncontrollable amount of data transmitted by the migration task. The private data required by some entities in the migration task is determined by the role type, making the amount of data transmitted by the migration task more controllable.

[0164] Step S203: If the entity to be migrated S t The entity attribute location information indicates the entity to be migrated S t If it is an authoritative role, then obtain the entity to be migrated S t Get the private data in the business data of the entity to be migrated S t The data package of public data in the business data is treated as the migration entity S t Serialize the private data in the business data to obtain the serialized private data, and add the serialized private data to the entity S to be migrated t At the end of the corresponding data packet, the entity to be migrated S is obtained t The serialized package corresponding to the entity attribute location information;

[0165] Specifically, if the entity attribute location information of the entity to be migrated indicates that the entity to be migrated is an authoritative role, the migration server can obtain private data in the business data of the entity to be migrated and obtain a data packet containing public data in the business data of the entity to be migrated.

[0166] The migration server can serialize the private data in the business data of the entity to be migrated to obtain the serialized private data, and add the serialized private data to the end of the data packet corresponding to the entity to be migrated to obtain a serialized package corresponding to the entity attribute location information of the entity to be migrated.

[0167] The embodiment of the present application provides additional classification of private data by serializing private data to the end of the data packet corresponding to the entity to be migrated, thereby improving the processing capability of the migration service parsing entity and improving convenience and compatibility.

[0168] Step S204, generating M+1 position identifiers representing the arrangement positions of M+1 serialized packages according to the arrangement positions of the entities to be migrated in the entity association table, sorting the M+1 serialized packages according to the M+1 position identifiers, and grouping the M+1 serialized packages into an entity sequence table;

[0169] Specifically, the migration server can generate serialized packages corresponding to the attribute location information of the entity through the business data, and obtain several serialized packages (ie, one serialized package for each entity to be migrated), that is, the serialized package can store the business data corresponding to the entity to be migrated.

[0170] The migration server can generate a position identifier representing the arrangement position of the serialized package according to the arrangement position of the entity to be migrated in the entity association table, sort the serialized packages according to the position identifier, and group several serialized packages into an entity sequence table in order, so as to achieve that the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table.

[0171] The entity sequence table may be shown in Table 2:

[0172] Table 2

[0173]

[0174] Among them, TransEntity1, TransEntity2, and TransEntity3 are the labels determined by the migration server for the entities to be migrated; Entity indicates that the type of migration is entity; Entity1-ID, Entity2-ID, and Entity3-ID are entity IDs, that is, unique ID identifiers of entities; Entity-Bunch, Associate1-Bunch, and Associate2-Bunch are types of serialization packages, Entity-Bunch is the serialization package of the object entity, and Associate1-Bunch and Associate2-Bunch are the serialization packages of the associated entities.

[0175] Step S205, sending the entity sequence list to the migration server, so that the migration server sequentially reversely parses the serialized packages in the entity sequence list based on the arrangement position to obtain the migrated entity; the migrated entity includes the object entity and M associated entities; the migrated entity stored in the migration server is a virtual object in the second environment of the virtual world;

[0176] Specifically, the outgoing server may divide the entity sequence list including multiple serialized packets to obtain multiple unit data packets, and the outgoing server may send the multiple unit data packets to the incoming server.

[0177] The specific process of the outgoing server dividing the entity sequence list including the plurality of serialized packets and sending the divided entity sequence list to the incoming server may be: dividing the entity sequence list to obtain a plurality of unit data packets; the unit data packets include unit labels, and the unit labels are used to verify the position of the unit data packets in the entity sequence list; sending the plurality of unit data packets to the incoming server, so that the incoming server reorganizes the plurality of unit data packets into the entity sequence list in order according to the unit labels, and reversely parses the entity sequence list to obtain the migrated entity;

[0178] Specifically, the migration server may divide the entity sequence list to obtain a plurality of unit data packets. The unit data packets may include unit labels, and the unit labels are used to verify the position of the unit data packets in the entity sequence list.

[0179] Optionally, the migration server may continue to serialize the entity sequence list into a larger entity group package, and then divide the entity group package.

[0180] The migration server may determine a plurality of entity sequence lists as an entity group package, and the entity group package may be as shown in Table 3:

[0181] Table 3

[0182] Entity Group Package Entity1-ID Entity-Bunch Associate1-Bunch Associate2-Bunch

[0183] The migration-out server may record the entity ID of the migrated object entity and the serialization bundle (Entity-Bunch, Associate1-Bunch and Associate2-Bunch) of the object entity through the entity group bundle.

[0184] It can be understood that, through the above processing at the communication layer, the migration server does not need to consider the size of the entity group packet when sending the entity group packet, but the communication layer takes care of it instead.

[0185] The outgoing server can record the unit number corresponding to the unit data packet, and the incoming server can also record the unit number corresponding to the unit data packet, until the incoming server receives all the unit data packets, and the incoming server sorts the unit data packets according to the unit number corresponding to the unit data packet, and when the corresponding entity sequence list is obtained, the outgoing server can clear the unit mark. Through the above method, it can be seen that the out-of-order transmission and asynchronous transmission of the outgoing server do not affect the entity sequence list composed of the unit data packets received by the incoming server, and the incoming server can also obtain a complete, organized and ordered entity after parsing the entity sequence list.

[0186] The migration server can reverse parse the serialized packages in turn according to the arrangement position of the serialized packages in the entity sequence table to obtain the migrated entities (which may include object entities and associated entities of the object entities) and complete the migration of the object entities and the associated entities of the object entities. The migrated entities are virtual objects stored in the second environment of the virtual world of the migration server.

[0187] Optionally, if a migration exception occurs during the entity migration process, the outgoing server can regenerate the entity sequence list to complete the migration task. The specific process of regenerating the entity sequence list may be: if a migration exception occurs during the process of sending the entity sequence list to the incoming server, the distributed entity associated with the entity sequence list is obtained, the business data is re-obtained through the entity attribute location information recorded by the distributed entity, and the serialized packages corresponding to each business data are generated again, and M+1 serialized packages containing business data are combined into an entity sequence list.

[0188] Specifically, if a migration anomaly occurs during the entity migration process, the out-migration server can redetermine the entity to be migrated based on the entity association table, and determine the corresponding distributed entity based on the entity to be migrated. The entity attribute location information stored in the distributed entity is the entity attribute location information fixed by the authorization downgrade when the migration task occurs. The out-migration server can obtain the business data of the entity to be migrated through the entity attribute location information fixed in the distributed entity, and can regenerate the entity sequence list required by the migration task.

[0189] For example, during the migration process, if the role type (authorization downgrade) switch initiated by the outgoing server is completed, and the incoming server crashes during the migration process, when the set timeout period is reached, or after receiving a problem notification returned by the incoming server, the incoming server can determine the entity to be migrated through the entity sequence list, obtain the corresponding distributed entity through the entity to be migrated, obtain business data based on the entity attribute location information stored in the distributed entity, and regenerate the entity sequence list of the pre-migration state to complete the migration task.

[0190] The manner in which the migration server generates the entity sequence list through the entity attribute location information may refer to the specific process from step S202 to step S204.

[0191] It can be understood that the present invention can store the entity attribute location information that changes in each migration task through distributed entities, and perform good fault detection on hardware failures and network fluctuations that may occur during the migration process. When the above-mentioned migration anomalies occur, the entity to be migrated can still be re-determined through the entity association table, and the entity sequence table can be regenerated to complete the migration task, which fully improves the timeliness and robustness of large-scale distributed systems such as virtual worlds.

[0192] The embodiment of the present application can ensure the integrity of multiple associated entities to be migrated (object entities and associated entities) during migration by adding the object entities to be migrated and the associated entities of the object entities to the same entity association table. The outgoing server can freely define the data arrival and processing order after the migration of multiple associated entities, which greatly reduces the processing complexity of the incoming server after the disorderly migration of entity data, and can improve the efficiency of entity migration. Since the entity association table can reflect the association relationship between the entities to be migrated, the entity sequence table generated based on the entity association table also has the above-mentioned association relationship. Therefore, the incoming server can restore the entity based on the association relationship in the entity sequence table after the migration of a single entity sequence table is completed, which improves the timeliness of the incoming server to restore the migrated entity.

[0193] See also Figure 7 , Figure 7 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 5 The data processing method may be executed by a migration server, which may be Figure 1 The migration server 200 shown in FIG. Figure 7 As shown, the method may include:

[0194] Step S301, obtaining an entity sequence list sent by a migration server; the entity sequence list includes M+1 serialization packages, the serialization packages include business data of entities to be migrated, and the entities to be migrated stored in the migration server are virtual objects in a first environment of a virtual world; the M+1 entities to be migrated associated with the M+1 serialization packages include an object entity that triggers a migration event and M associated entities associated with the object entity;

[0195] Specifically, the migration server reorganizes the multiple unit data packets into an entity sequence table in order through unit labels. The entity sequence table includes multiple serialized packages, and the serialized packages include business data of the entity to be migrated.

[0196] The entity to be migrated may be stored in the migration server and is a virtual object in the first environment of the virtual world. The multiple entities to be migrated associated with the multiple serialization packages may be the object entity that triggers the migration event and the associated entity associated with the object entity.

[0197] For details about entity sequence table, serialization package and business data, please refer to the above Figure 4 The description of the entity sequence table, serialization package and business data in step S202 of the corresponding embodiment will not be repeated here.

[0198] Please also refer to Figure 8 , Figure 8 This is a flow diagram of a data processing method provided in an embodiment of the present application. Figure 6 ,like Figure 8 As shown, the migration server can receive data sent by the migration server, and reassemble multiple unit data packets into an entity sequence list according to the corresponding unit labels (or assemble entity packets and then split them into entity sequence lists).

[0199] The migration server can determine the arrangement position of the entity in the entity sequence list according to the position identifier of the serialization package in the entity sequence list.

[0200] The location identifier may be an identifier representing the arrangement position of the serialized package generated by the arrangement position of the entity to be migrated in the entity association table. The entity association table may be used to store multiple entities to be migrated in order when the object entity that triggers the migration event is obtained. The entities to be migrated include the object entity and the associated entities of the object entity.

[0201] For details about the entity association table, please refer to the above Figure 4 The description of the entity association table in step S201 of the corresponding embodiment will not be repeated here.

[0202] The migration server can reverse parse the serialized packages in the entity sequence table according to the arrangement position. For example, if the arrangement positions in the entity sequence table are virtual vehicle 1, virtual character 2, and virtual item 3, the migration server can parse the data packets corresponding to virtual vehicle 1, virtual character 2, and virtual item 3 in sequence. In this way, the migration server can better determine the association relationship between entities in the entity sequence table during the parsing process.

[0203] Step S302, based on the arrangement position, the serialized packages in the entity sequence table are reverse parsed in turn to obtain the migrated entities; the arrangement position refers to the arrangement position of the entity to be migrated in the entity association table generated by the migration server, and the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; the entity association table is used to store M+1 entities to be migrated in sequence when the object entity that triggers the migration event is obtained; the migrated entities include the object entity and M associated entities; the migrated entities are virtual objects in the second environment of the virtual world.

[0204] Specifically, the migration server may parse the entity sequence list to obtain parsed entities, and the parsed entities may include: Figure 8The object entity 1, associated entity 1 and associated entity 2 are shown. The migration server can read the business data corresponding to the resolved entity to obtain the migrated entity (which can include the object entity 1, associated entity 1 and associated entity 2 that have been written with the business data). The migrated entity can include the object entity and the associated entities associated with each object entity. The migrated entity stored in the migration server can be a virtual object in the second environment of the virtual world.

[0205] Optionally, the migration server may perform attribute callback on the local entity according to the attribute identifier to obtain the migrated entity. The specific process of attribute callback may be: based on the arrangement position, the serialized packages in the entity sequence list are reversely parsed in turn to obtain the parsed entities corresponding to M+1 serialized packages respectively; the M+1 parsed entities include the parsed entity Q i , i is a positive integer less than or equal to M+1; will be combined with the parsed entity Q i The business data in the corresponding serialized package is written into the parsed entity Q i , get the intermediate parsed entity; if the intermediate parsed entity has an attribute identifier, then obtain the local entity associated with the intermediate parsed entity in the second environment of the virtual world, perform attribute callback on the data indicated by the attribute identifier in the local business data associated with the local entity, write the callback data into the intermediate parsed entity, and get the data associated with the resolved entity Q i The corresponding migrated entity.

[0206] Specifically, the migration server may write the business data in the serialized package corresponding to the resolved entity into the resolved entity to obtain the intermediate resolved entity.

[0207] If there is an attribute identifier in the intermediate parsed entity, the migration server can obtain the local entity and perform attribute callback on the local business data associated with the local entity according to the data indicated by the attribute identifier. For example, the local entity corresponding to object entity 1 is local entity 1, and the migration server can adjust the local business data associated with local entity 1, for example, it can automatically execute the bound function on attributes such as health value and level according to the data indicated by the attribute identifier.

[0208] The local entity may be an entity associated with the intermediate resolution entity in the second environment of the virtual world. The attribute identifier is an identifier in the entity for recording the entity information modified in the entity attribute location information.

[0209] For details about attribute identification and entity attribute location information, please refer to the above Figure 4 The description of the attribute identification and entity attribute location information in step S202 of the corresponding embodiment will not be repeated here.

[0210] The migration server may write the callback data into the intermediate parsed entity to obtain a migrated entity corresponding to the parsed entity.

[0211] It can be understood that the present invention provides an orchestration migration capability for entity roaming in a virtual world. By migrating entities through an entity sequence list, the timing and integrity issues of multi-entity migration caused by network fluctuations or other software and hardware anomalies when an entity in the virtual world itself is associated with multiple entities are resolved. The idempotence of entity recovery processing after entity migration is guaranteed by the orchestration position of the entity. By comparing the data corresponding to the entities in the outgoing server and the incoming server through the attribute identification of the entity attribute location information, the amount of data transmission in the migration task can be reduced, and the overall time of entity migration can be controlled within a smaller clock cycle, thereby improving the timeliness of entity migration.

[0212] The embodiment of the present application obtains an entity sequence list sent by a migration server; the entity sequence list includes M+1 serialized packages, the serialized packages include business data of the entity to be migrated, and the entity to be migrated stored in the migration server is a virtual object in a first environment of a virtual world; the M+1 entities to be migrated associated with the M+1 serialized packages include an object entity that triggers a migration event and M associated entities associated with the object entity; the serialized packages in the entity sequence list are reversely parsed in turn based on the arrangement position to obtain the migrated entity; the arrangement position refers to the arrangement position of the entity to be migrated in the entity association table generated by the migration server, and the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence list is the same as the arrangement position of the entity to be migrated in the entity association table; the entity association table is used to store the M+1 entities to be migrated in sequence when the object entity that triggers the migration event is obtained; the migrated entity includes the object entity and M associated entities; the migrated entity is a virtual object in a second environment of the virtual world. It can be seen from this that the present application can add the object entities that need to be migrated and the associated entities of the object entities to the same entity association table, which can ensure the integrity of multiple entities to be migrated (object entities and associated entities) during the migration. The upper-level business module can freely define the data arrival and processing order after the migration of multiple associated entities, which greatly reduces the processing complexity of the upper-level business module caused by the disorderly migration of entity data, and can improve the efficiency of entity migration. The entity can be restored after the migration of a single entity sequence table is completed, thereby improving the timeliness of the migrating server to parse the migrated entity.

[0213] See also Fig. 9 , Fig. 9 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. Figure 1 .like Fig. 9As shown, the data processing device 1 includes an entity acquisition module 810, a sequence table generation module 880, and a sending module 870. The sequence table generation module 880 includes a business data acquisition unit 820, a serialization package generation unit 830, a distributed entity acquisition unit 840, an information solidification unit 850, and an exception handling unit 860. The sending module 870 includes a division unit 871 and a reorganization unit 872. The business data acquisition unit 820 includes a first processing subunit 821, a second processing subunit 822, a role type acquisition subunit 823, a first determination subunit 824, and a second determination subunit 825. The serialization package generation unit 830 includes a private data acquisition subunit 831 and a private data serialization subunit 832.

[0214] The entity acquisition module 810 is used to acquire the object entity that triggers the migration event, acquire M associated entities associated with the object entity, and determine the object entity and the M associated entities as entities to be migrated that are sequentially added to the entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in the first environment of the virtual world; the specific functional implementation of the entity acquisition module 810 can be found in Figure 3 The description of step S101 in the corresponding embodiment will not be repeated here.

[0215] The entity acquisition module 810 is specifically used to use the object entity as the root node, and recursively query the entities that are child nodes of the root node and the entities that are leaf nodes of the root node in the entity set of the first environment of the virtual world, and determine the recursively queried entities as M associated entities associated with the object entity. The specific functional implementation of the entity acquisition module 810 can be found in Figure 4 The description of step S201 in the corresponding embodiment will not be repeated here.

[0216] The sequence table generation module 880 is used to obtain the business data of each entity to be migrated in the first environment, generate a serialized package corresponding to each business data, and form an entity sequence table by combining M+1 serialized packages containing business data; the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; the specific function implementation method of the sequence table generation module 880 can be found in Figure 3 The description of step S102 in the corresponding embodiment will not be repeated here.

[0217] The business data acquisition unit 820 is used to acquire entity attribute location information corresponding to the M+1 entities to be migrated, and acquire business data of the M+1 entities to be migrated in the first environment according to the entity attribute location information; the entity attribute location information includes the environment information where the virtual object is located and the role type information it has;

[0218] The first processing subunit 821 is used to: i The corresponding entity attribute location information P i If there is an attribute identifier for the migration server in the entity attribute location information P i The entity information indicated by the attribute identifier in the first environment is obtained. i Corresponding business data; the attribute identifier is used to record entity attribute location information P in the first environment i The identifier of the entity information that has been modified;

[0219] The second processing subunit 822 is used to: i The corresponding entity attribute location information P i If there is no attribute identifier for the migration server in the entity attribute location information P i Each entity information in the first environment is obtained to migrate the entity S i The corresponding business data.

[0220] The role type acquisition subunit 823 is used to obtain the entity location attribute information P j Entities to be migrated S j role type information; role types include authoritative roles and proxy roles, the authoritative role is a virtual object that acts freely in the first environment, and the proxy role is a virtual object used to synchronize the actions of the authoritative role in the first environment;

[0221] The first determining subunit 824 is used to determine the entity location attribute information P j Indicates the entity to be migrated S j If it is an authoritative role, then obtain the entity to be migrated S j The private and public data of the entity S to be migrated j The private data and public data of the entity S to be migrated j Corresponding business data;

[0222] The second determining subunit 825 is used to determine the entity location attribute information P j Indicates the entity to be migrated S j For the proxy role, get the entity to be migrated S j Public data of the entity to be migrated S j The public data of the entity to be migrated is S j The corresponding business data.

[0223] The specific functional implementation of the first processing subunit 821, the second processing subunit 822, the role type acquisition subunit 823, the first determination subunit 824 and the second determination subunit 825 can be found in Figure 4 The description of step S202 in the corresponding embodiment will not be repeated here.

[0224] The serialization package generation unit 830 is used to generate serialization packages corresponding to the corresponding entity attribute location information through M+1 business data, and group the M+1 serialization packages containing business data into an entity sequence table.

[0225] The private data acquisition subunit 831 is used to obtain the private data of the entity S to be migrated. t The entity attribute location information indicates the entity to be migrated S t If it is an authoritative role, then obtain the entity to be migrated S t Private data in business data;

[0226] The private data serialization subunit 832 is used to obtain the data containing the entity S to be migrated. t The data package of public data in the business data is treated as the migration entity S t Serialize the private data in the business data to obtain the serialized private data, and add the serialized private data to the entity S to be migrated t At the end of the corresponding data packet, the entity to be migrated S is obtained t The serialized package corresponding to the entity attribute location information.

[0227] The specific functional implementation of the private data acquisition subunit 831 and the private data serialization subunit 832 can be found in Figure 4 The description of step S203 in the corresponding embodiment will not be repeated here.

[0228] The distributed entity acquisition unit 840 is used to acquire the distributed entities corresponding to the M+1 entities to be migrated, and perform authorization downgrade on the entities to be migrated in the entity association table; the distributed entity is used to record the entity attribute location information of the entity to be migrated each time a migration event is triggered, and the authorization downgrade status of the entity to be migrated is used to indicate that the entity attribute location information associated with the entity to be migrated is solidified;

[0229] The information solidification unit 850 is used to write the M+1 solidified entity attribute location information into the distributed entities corresponding to the associated entities to be migrated; one distributed entity contains one solidified entity attribute location information;

[0230] The exception handling unit 860 is used to obtain the distributed entity associated with the entity sequence list if a migration exception occurs during the process of sending the entity sequence list to the migration server, re-acquire the business data through the entity attribute location information recorded by the distributed entity, re-execute the step of generating a serialized package corresponding to each business data, and combine M+1 serialized packages containing business data into an entity sequence list.

[0231] The specific functional implementation of the distributed entity acquisition unit 840, the information solidification unit 850 and the exception handling unit 860 can be found in Figure 4 The description of step S204 in the corresponding embodiment will not be repeated here.

[0232] The sending module 870 is used to send the entity sequence list to the migration server, so that the migration server can reversely parse the serialized packages in the entity sequence list based on the arrangement position to obtain the migrated entity; the migrated entity includes the object entity and M associated entities; the migrated entity stored in the migration server is a virtual object in the second environment of the virtual world. The specific functional implementation of the sending module 870 can be found in Figure 3 The description of step S103 in the corresponding embodiment will not be repeated here.

[0233] The division unit 871 is used to divide the entity sequence list to obtain a plurality of unit data packets; the unit data packets include unit labels, and the unit labels are used to verify the position of the unit data packets in the entity sequence list;

[0234] The reassembly unit 872 is used to send multiple unit data packets to the migration server, so that the migration server reassembles the multiple unit data packets into an entity sequence list in sequence according to the unit labels, and reversely parses the entity sequence list to obtain the migrated entity.

[0235] The specific functional implementation of the division unit 871 and the reorganization unit 872 can be found in Figure 4 The description of step S205 in the corresponding embodiment will not be repeated here.

[0236] See also Fig.10 , Fig.10 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. Figure 2 .like Fig.10 As shown, the data processing device 2 includes a sequence table acquisition module 600 and a reverse parsing module 700. The reverse parsing module 700 includes a parsed entity generation unit 710, a business data writing unit 720 and an attribute callback unit 730.

[0237] The sequence list acquisition module 600 is used to acquire the entity sequence list sent by the migration server; the entity sequence list includes M+1 serialization packages, the serialization packages include the business data of the entity to be migrated, and the entity to be migrated stored in the migration server is a virtual object in the first environment of the virtual world; the M+1 entities to be migrated associated with the M+1 serialization packages include the object entity that triggers the migration event and M associated entities associated with the object entity; the specific functional implementation method of the sequence list acquisition module 600 can be found in Figure 7 The description of step S301 in the corresponding embodiment will not be repeated here.

[0238] The reverse parsing module 700 is used to reverse parse the serialized packages in the entity sequence table in sequence based on the arrangement position to obtain the migrated entity; the arrangement position refers to the arrangement position of the entity to be migrated in the entity association table generated by the migration server, and the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; the entity association table is used to store M+1 entities to be migrated in sequence when the object entity that triggers the migration event is obtained; the migrated entity includes the object entity and M associated entities; the migrated entity is a virtual object in the second environment of the virtual world.

[0239] The specific functional implementation of the inverse analysis module 700 can be found in Figure 7 The description of step S302 in the corresponding embodiment will not be repeated here.

[0240] The inverse analysis module 700 includes:

[0241] The parsed entity generation unit 710 is used to reverse parse the serialized packages in the entity sequence table in turn based on the arrangement position to obtain parsed entities corresponding to M+1 serialized packages respectively; the M+1 parsed entities include the parsed entity Q i , i is a positive integer less than or equal to M+1;

[0242] The business data writing unit 720 is used to write the business data to the parsed entity Q i The business data in the corresponding serialized package is written into the parsed entity Q i , get the intermediate parsed entity;

[0243] The attribute callback unit 730 is used to obtain the local entity associated with the intermediate resolution entity in the second environment of the virtual world if the intermediate resolution entity has an attribute identifier, perform attribute callback on the data indicated by the attribute identifier in the local business data associated with the local entity, write the callback data into the intermediate resolution entity, and obtain the data associated with the resolved entity Q. i The corresponding migrated entity.

[0244] See also Fig.11 , Fig.11 Schematic diagram of the structure of a computer device provided in an embodiment of the present application. Fig.11 As shown, the computer device 1000 may include: a processor 1001, a network interface 1004 and a memory 1005. The computer device 1000 may be the above Figure 1 The migration-out server 100 or the migration-in server 200 in the embodiment. In addition, the above-mentioned computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. Among them, the user interface 1003 may include a display screen (Display), a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or it may be a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 1005 may optionally also be at least one storage device located away from the aforementioned processor 1001. As Fig.11 As shown, the memory 1005 as a computer-readable storage medium may include an operating system, a network communication module, a user interface module, and a device control application program.

[0245] In such Fig.11 In the computer device 1000 shown, the network interface 1004 can provide a network communication element; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005. When the computer device 1000 is a migration server ( Figure 1 When migrating out of the server 100 in the embodiment, the processor 1001 may implement:

[0246] Acquire the object entity that triggers the migration event, acquire M associated entities associated with the object entity, determine the object entity and the M associated entities as entities to be migrated, and add M+1 entities to be migrated to the entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in the first environment of the virtual world;

[0247] Obtain business data of each entity to be migrated in the first environment, generate serialized packages corresponding to each business data, and group M+1 serialized packages containing business data into an entity sequence table; the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table;

[0248] The entity sequence list is sent to the migration server so that the migration server can reverse parse the serialized packages in the entity sequence list in sequence based on the arrangement position to obtain the migrated entities; the migrated entities include object entities and M associated entities; the migrated entities stored in the migration server are virtual objects in the second environment of the virtual world.

[0249] When the computer device 1000 is a migration server ( Figure 1 When migrating to the server 200 in the embodiment, the processor 1001 may implement:

[0250] Obtaining an entity sequence list sent by a migration server; the entity sequence list includes M+1 serialized packages, the serialized packages include business data of entities to be migrated, and the entities to be migrated stored in the migration server are virtual objects in a first environment of a virtual world; the M+1 entities to be migrated associated with the M+1 serialized packages include an object entity that triggers a migration event and M associated entities associated with the object entity;

[0251] Based on the arrangement position, the serialized packages in the entity sequence table are reverse parsed in turn to obtain the migrated entities; the arrangement position refers to the arrangement position of the entity to be migrated in the entity association table generated by the migration server, and the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; the entity association table is used to store M+1 entities to be migrated in sequence when the object entity that triggers the migration event is obtained; the migrated entities include the object entity and M associated entities; the migrated entities are virtual objects in the second environment of the virtual world.

[0252] It should be understood that the computer device 1000 described in the embodiment of the present application can execute the above Figure 3 , Figure 4 and Figure 7 The description of the data processing method in any corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated here.

[0253] In addition, it should be pointed out here that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program, and when the processor executes the computer program, it can execute the above Figure 3 , Figure 4 and Figure 7 The description of the above data processing method in any corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0254] The computer-readable storage medium may be the data processing device provided in any of the aforementioned embodiments or the internal storage unit of the computer device, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (smart media ard, SMC), a secure digital (secure digitala l, SD) card, a flash card (flash card), etc. equipped on the computer device. Further, the computer-readable storage medium may also include both the internal storage unit of the computer device and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium may also be used to temporarily store data that has been displayed or is to be displayed.

[0255] In addition, it should be noted that: the embodiment of the present application also provides a computer program product, the computer program product includes a computer program, the computer program is stored in a computer-readable storage medium. The processor of the computer device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, so that the computer device executes the above Figure 3 , Figure 4 and Figure 7 Any method provided by the corresponding embodiment.

[0256] The terms "first", "second", etc. in the description, claims, and drawings of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, device, product, or equipment that includes a series of steps or units is not limited to the listed steps or modules, but optionally includes steps or modules that are not listed, or optionally includes other step units inherent to these processes, methods, devices, products, or equipment.

[0257] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of network elements in the above description. Whether these network elements are executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described network elements for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0258] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A data processing method, characterized in that: include: Acquire an object entity that triggers a migration event, acquire M associated entities associated with the object entity, and determine the object entity and the M associated entities as entities to be migrated that are sequentially added to an entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in a first environment of a virtual world; Obtaining business data of each entity to be migrated in the first environment, generating a serialized package corresponding to each business data, and forming an entity sequence table with M+1 serialized packages containing the business data; the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; The entity sequence list is sent to the migration server, so that the migration server reversely parses the serialized packages in the entity sequence list in turn based on the arrangement position to obtain the migrated entity; the migrated entity includes the object entity and M associated entities; the migrated entity stored in the migration server is a virtual object in the second environment of the virtual world.

2. The method according to claim 1, characterized in that The acquiring M associated entities associated with the object entity includes: Taking the object entity as a tree root node, recursively query entities that have a child node relationship with the tree root node and entities that have a leaf node relationship with the tree root node in an entity set belonging to the first environment of the virtual world, and determine the entities obtained by the recursive query as M associated entities associated with the object entity.

3. The method according to claim 1, characterized in that The acquiring of the business data of each entity to be migrated in the first environment, generating a serialized package corresponding to each business data, and forming M+1 serialized packages containing the business data into an entity sequence table includes: Obtaining entity attribute location information corresponding to the M+1 entities to be migrated, and obtaining business data of the M+1 entities to be migrated in the first environment according to the entity attribute location information; the entity attribute location information includes environment information where the virtual object is located and role type information; Serialized packages corresponding to the entity attribute location information are generated respectively through the M+1 business data, and the M+1 serialized packages containing the business data are grouped into an entity sequence table.

4. The method according to claim 3, characterized in that Also includes: Obtaining distributed entities corresponding to M+1 entities to be migrated respectively, and performing authorization downgrade on the entities to be migrated in the entity association table; The distributed entity is used to record the entity attribute location information of the entity to be migrated each time a migration event is triggered, and the authorization downgrade state of the entity to be migrated is used to indicate that the entity attribute location information associated with the entity to be migrated is solidified; Write the M+1 solidified entity attribute location information into the distributed entities corresponding to the associated entities to be migrated respectively; one of the distributed entities contains one solidified entity attribute location information; If a migration exception occurs during the process of sending the entity sequence list to the migration server, the distributed entity associated with the entity sequence list is obtained, the business data is re-obtained through the entity attribute location information recorded by the distributed entity, and the serialized packages corresponding to each of the business data are generated again, and M+1 serialized packages containing the business data are combined into an entity sequence list.

5. The method according to claim 3, characterized in that: The M+1 entities to be migrated include entity S to be migrated i The M+1 entity attribute location information includes the entity to be migrated S i The corresponding entity attribute location information P i ; i is a positive integer less than or equal to M+1; the acquiring of the business data of the M+1 entities to be migrated in the first environment respectively according to the entity attribute location information includes: If the entity to be migrated S i The corresponding entity attribute location information P i There is an attribute identifier for the migration server in the entity attribute location information P i and the entity information indicated by the attribute identifier, and obtaining the entity to be migrated S in the first environment. i Corresponding business data; the attribute identifier is used to record the entity attribute location information P in the first environment i The identifier of the entity information that has been modified; If the entity to be migrated S i The corresponding entity attribute location information P i If there is no attribute identifier for the migration server in the entity attribute location information P i Each entity information in the first environment is obtained, and the entity to be migrated S is obtained in the first environment i The corresponding business data.

6. The method according to claim 3, characterized in that: The M+1 entities to be migrated include entity S to be migrated j The M+1 entity attribute location information includes the entity to be migrated S j The corresponding entity attribute location information P j ; j is a positive integer less than or equal to M+1; the acquiring of the business data of the M+1 entities to be migrated in the first environment respectively according to the entity attribute location information includes: Get the entity location attribute information P j The entity S to be migrated j The role type information includes an authoritative role and an agent role, the authoritative role is a virtual object that moves freely in the first environment, and the agent role is a virtual object used to synchronize the actions of the authoritative role in the first environment; If the entity location attribute information P j Indicate the entity to be migrated S j is an authoritative role, then obtain the entity to be migrated S j The private data and public data of the entity to be migrated S j The private data and public data of the entity to be migrated S j Corresponding business data; If the entity location attribute information P j Indicate the entity to be migrated S j is a proxy role, then obtain the entity to be migrated S j The public data of the entity to be migrated S j The public data of the entity to be migrated is j The corresponding business data.

7. The method according to claim 6, characterized in that The M+1 entities to be migrated include entity S to be migrated t , t is a positive integer less than or equal to M+1; The generating of serialized packages corresponding to the entity attribute location information respectively through the M+1 business data includes: If the entity to be migrated S t The entity attribute location information indicates the entity to be migrated S t is an authoritative role, then obtain the entity to be migrated S t Private data in business data; Get the entity S to be migrated t The data packet of the public data in the business data of the entity to be migrated S t The private data in the business data is serialized to obtain the serialized private data, and the serialized private data is added to the entity to be migrated S t At the end of the corresponding data packet, the entity to be migrated S is obtained. t The serialized package corresponding to the entity attribute location information.

8. The method according to claim 1, characterized in that The step of forming the M+1 serialized packages containing the business data into an entity sequence list includes: According to the arrangement position of the entity to be migrated in the entity association table, M+1 position identifiers representing the arrangement position of the M+1 serialized packages are generated, the M+1 serialized packages are sorted according to the M+1 position identifiers, and the M+1 serialized packages are grouped into an entity sequence list.

9. The method according to claim 1, characterized in that: The sending of the entity sequence list to the migration server comprises: Dividing the entity sequence list to obtain a plurality of unit data packets; the unit data packets include unit labels, and the unit labels are used to verify the position of the unit data packets in the entity sequence list; The multiple unit data packets are sent to a migration server, so that the migration server reorganizes the multiple unit data packets into the entity sequence list in sequence according to the unit labels, and reversely parses the entity sequence list to obtain the migrated entity.

10. A data processing method, characterized in that: include: Get the entity sequence list sent by the migration server; The entity sequence table includes M+1 serialized packages, the serialized packages include business data of the entity to be migrated, the entity to be migrated stored in the migration server is a virtual object in the first environment of the virtual world; the M+1 entities to be migrated associated with the M+1 serialized packages include the object entity that triggers the migration event and M associated entities associated with the object entity; The serialized packages in the entity sequence table are reverse parsed in sequence based on the arrangement position to obtain the migrated entities; the arrangement position refers to the arrangement position of the entity to be migrated in the entity association table generated by the migration server, and the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; the entity association table is used to store M+1 entities to be migrated in sequence when the object entity that triggers the migration event is obtained; the migrated entities include the object entity and M associated entities; the migrated entities are virtual objects in the second environment of the virtual world.

11. The method according to claim 10, characterized in that The step of sequentially reversing the serialized packages in the entity sequence table based on the arrangement position to obtain the migrated entity includes: Based on the arrangement position, the serialized packages in the entity sequence table are reverse parsed in sequence to obtain M+1 parsed entities corresponding to the serialized packages; the M+1 parsed entities include the parsed entity Q i , i is a positive integer less than or equal to M+1; will be combined with the resolved entity Q i The business data in the corresponding serialized package is written into the parsed entity Q i , get the intermediate parsed entity; If the intermediate parsed entity has an attribute identifier, obtain the local entity associated with the intermediate parsed entity in the second environment of the virtual world, perform attribute callback on the data indicated by the attribute identifier in the local business data associated with the local entity, write the callback data into the intermediate parsed entity, and obtain the data associated with the resolved entity Q. i The corresponding migrated entity.

12. A data processing device, characterized in that: include: An entity acquisition module is used to acquire an object entity that triggers a migration event, acquire M associated entities associated with the object entity, and determine the object entity and the M associated entities as entities to be migrated that are sequentially added to an entity association table; M is a positive integer, and the M+1 entities to be migrated are all virtual objects in a first environment of a virtual world; A sequence table generation module is used to obtain the business data of each entity to be migrated in the first environment, generate a serialized package corresponding to each business data, and form an entity sequence table by combining M+1 serialized packages containing the business data; the arrangement position of the entity to be migrated associated with the serialized package in the entity sequence table is the same as the arrangement position of the entity to be migrated in the entity association table; A sending module is used to send the entity sequence list to a migration server, so that the migration server can reversely parse the serialized packages in the entity sequence list in turn based on the arrangement position to obtain the migrated entity; the migrated entity includes the object entity and M associated entities; the migrated entity stored in the migration server is a virtual object in the second environment of the virtual world.

13. A computer device, characterized in that: include: Processor, memory, and network interface; The processor is connected to the memory and the network interface, wherein the network interface is used to provide a data communication function, the memory is used to store a computer program, and the processor is used to call the program code so that the computer device executes the method described in any one of claims 1-11.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is suitable for being loaded and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 11.

15. A computer program product, characterized in that The computer program product comprises a computer program, which is stored in a computer-readable storage medium and is suitable for being read and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 11.