CN117081762A

CN117081762A - Data processing method and related equipment

Info

Publication number: CN117081762A
Application number: CN202210503864.XA
Authority: CN
Inventors: 雍雅心; 何芬
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-05-10
Filing date: 2022-05-10
Publication date: 2023-11-17

Abstract

The embodiment of the application provides a data processing method and related equipment, wherein the method comprises the following steps: displaying N parts of object roles allowed to be used by a target object under a login account; n split object roles are all subordinate to one main object role under a login account, and the N split object roles are mutually independent; n is a positive integer; responsive to selection of a first object role of the N split object roles, displaying a service interface for the first object role; the service interface of the first object character supports the target object to perform data processing by using the first object character and supports independent management of the character data of the first object character. The embodiment of the application can flexibly select the roles of the split objects in the client to process the data, and can independently manage the role data of the split objects.

Description

Data processing method and related equipment

Technical Field

The present application relates to the field of computer technology, and in particular, to a data processing method, a data processing apparatus, a computer device, a computer readable storage medium, and a computer program product.

Background

With the development of computer technology, an object can log in a certain client (such as a social client, a game client and the like) through an account number and a password, and data processing is performed on a service interface under the account number in a fixed object role, for example, the object performs social expression in the service interface under the social account number, such as comment making, online state updating and the like. Practice finds that the data processing process of the current object in the client is too limited, is not flexible enough, has the problem of being incapable of adapting to the requirements of different data processing scenes, and cannot effectively manage the data.

Disclosure of Invention

The embodiment of the application provides a data processing method and related equipment, which can flexibly select a split object role in a client to process data and can realize independent and effective management of the data of the split object role.

In one aspect, an embodiment of the present application provides a data processing method, where the method includes:

displaying N parts of object roles allowed to be used by a target object under a login account; n split object roles are all subordinate to one main object role under a login account, and the N split object roles are mutually independent; n is a positive integer;

responsive to selection of a first object role of the N split object roles, displaying a service interface for the first object role; the service interface of the first object character supports the target object to perform data processing by using the first object character and supports independent management of the character data of the first object character.

In one aspect, an embodiment of the present application provides a data processing apparatus, including:

the display unit is used for displaying N body-divided object roles which are allowed to be used by the target object under the login account; n split object roles are all subordinate to one main object role under a login account, and the N split object roles are mutually independent; n is a positive integer;

A processing unit for displaying a service interface of a first object character among the N split object characters in response to a selection of the first object character; the service interface of the first object character supports the target object to perform data processing by using the first object character and supports independent management of the character data of the first object character.

In one embodiment, n+1 object roles under the login account are each used to represent a target object; the n+1 object roles include a main object role and N individual object roles;

the login account is used as a main account and is bound with a main object role, and N split object roles respectively correspond to one split account; the N split accounts are all subordinate to the primary account, and after the primary account successfully logs in the client, the N split accounts successfully log in the client;

n parts of the body are independent, including: the character data of each of the N individual object characters are mutually independent, and the character data of each individual object character is independently managed by adopting the individual account numbers corresponding to each individual object character;

wherein the character data includes any one or more of: basic material data, interaction dynamic data, relationship chain data, function data, attribute data, role state data, cross-identity sharing relationship data, and application data associated with a third party application.

In one embodiment, the processing unit is further configured to:

setting character states for the n+1 object characters respectively, the character states including any one of the following: online status, away status, stealth status, busy status, application status.

In one embodiment, the display unit is further configured to display N number of individual object roles and role data of the N number of individual object roles in a service interface of the main object roles; the method comprises the steps of,

and the processing unit is also used for uniformly managing the character data of the N individual object characters in the service interface of the main object character.

In one embodiment, the role data includes relationship chain data; when the processing unit performs unified management on the character data of the N individual object characters in the service interface of the master object character, the processing unit may be specifically configured to:

displaying object management lists of N individual object roles in a service interface of the main object role;

in response to the object migration operation, selecting one or more relationship objects from the object management list of the first object role;

and migrating the selected relation object to an object management list of a second object role, wherein the second object role is any one of N separated object roles, and the first object role and the second object role are different.

In one embodiment, the character data comprises interactive dynamic data, the interactive dynamic data comprising interactive messages; when the processing unit performs unified management on the data under the N split object roles in the service interface of the main object role, the processing unit is further used for:

and if the migrated relation object has the interactive message in the service interface of the first object role, migrating the existing interactive message to the service interface of the second object role.

In one embodiment, the role data includes cross-identity sharing relationship data; when the processing unit performs unified management on data under the N split object roles in the service interface of the main object role, the processing unit can be specifically used for:

setting cross-identity sharing relations among N split object roles in a service interface of a main object role;

the method comprises the step of allowing data sharing across identities between the individual object roles with the across-identity sharing relationship.

In one embodiment, the display unit is further configured to, if a cross-identity sharing relationship is provided between the first object role and the second object role, display a data list to be shared in response to a sharing request received in a service interface of the first object role, where the data list includes role data of the first object role to be shared and role data of the second object role to be shared;

The processing unit is also used for executing sharing operation on the selected data to be shared in the data list; the sharing operation is used for sharing the data to be shared to any relation object in the object management list of the first object role; or the sharing operation is used for sharing the data to be shared to any relation object in the object management list of the second object role; the method comprises the steps of,

the display unit is also used for displaying the sharing record in the service interface of the first object role; wherein,

in one embodiment, the character data comprises interactive dynamic data, the interactive dynamic data comprising interactive messages; when the processing unit performs unified management on data under the N split object roles in the service interface of the main object role, the processing unit can be specifically used for:

displaying the interactive messages under the N split object roles in the service interface of the main object role;

responding to the reply operation of the target interaction message under the first object role, and sending a reply message of the target interaction message by using the first object role; the method comprises the steps of,

a reply record for the target interaction message is displayed in a service interface of the first object role.

In one embodiment, the role data of the first object role is independently managed, including any one of the following:

The character data of the first object character is visible only to the relationship objects in the object management list of the first object character; or,

after the primary account number is successfully logged in the third party application, if the target object selects to use the first object role in the third party application for application processing, application data associated with the third party application in the role data of the first object role is only visible to the relationship objects in the object management list of the first object role.

In one embodiment, the first object role is any one of the N split object roles; the display unit is also used for displaying a service interface of the main object role, wherein the service interface of the main object role comprises an account management interface of the main object role, and a split creation inlet is arranged in the account management interface of the main object role;

the processing unit is further configured to create a first object role in response to a trigger to create an entry to the partition.

In one embodiment, in response to a trigger of the split creation portal, creating a first object character, a display unit for displaying a split creation interface in which a split data configuration function interface is provided in response to a trigger operation performed by the split creation portal;

The processing unit is used for setting character data for a first object character to be created in the splitting data configuration function interface and creating the first object character after the setting is completed;

In one embodiment, after the first object character is created in response to the triggering of the split creation portal, the display unit is further configured to display a service interface of the created first object character, where the service interface of the first object character includes a split data setting interface;

the processing unit is also used for setting character data for the created first object character in the separation data setting interface; wherein the character data includes any one or more of: basic material data, interaction dynamic data, relationship chain data, function data, attribute data, role state data, cross-identity sharing relationship data, and application data associated with a third party application.

In one embodiment, the character data includes base material data; when setting character data for a first object character, a display unit for displaying a knock-down material editing interface;

The processing unit is used for automatically filling basic data of the main object roles in the split data editing interface; and generating the basic data of the first object role in response to the editing operation of the filled data in the split data editing interface.

In one embodiment, the role data includes any one or more of the following: interaction dynamic data, functional data and attribute data; when character data is set for the first object character, the display unit is used for displaying a data synchronization interface, and the data synchronization interface comprises a synchronization switch control;

the processing unit is used for setting the character data of the first object character to be null if the synchronous switch control is always in the closed state in the setting process; and if the synchronous switch control is triggered to be started in the setting process, synchronizing the role data of the main object role into the role data of the first object role.

In one embodiment, synchronizing the role data of the master object role into the role data of the first object role includes one or more of the following synchronization:

synchronizing existing character data of the master object character to the first object character;

synchronizing the existing character data of the master object character to the first object character, and synchronizing the updated data to the first object character when the character data of the master object character is updated;

And synchronizing the role data of the main object role in the preset time period to the first object role.

In one embodiment, the role data includes relationship chain data; when setting character data for a first object character, a display unit is used for displaying an object management list of a main object character, wherein the object management list of the main object character comprises all relation objects with interactive relation with a target object;

a processing unit for selecting one or more relationship objects from an object management list of the master object role; the selected relationship object is migrated to the object management list of the first object role.

In one embodiment, the relationship objects in the object management list of the master object role are partitioned into multiple relationship groups; the processing unit is further configured to, when setting character data for the first object character:

when one or more relation groups in the object management list of the main object role are selected, all relation objects in the selected relation groups are integrally migrated to the object management list of the first object role.

In one embodiment, the processing unit, when migrating all the relationship objects in the selected relationship group as a whole into the object management list of the first object role, may be specifically configured to:

If the object management list of the first object role already has the target relation group which is the same as the identification of the selected relation group, combining the selected relation group with the existing target relation group;

if the object management list of the first object role does not have the relationship group which is the same as the identification of the selected relationship group, a target relationship group is newly built in the object management list of the first object role based on the identification of the selected relationship group, and all relationship objects in the selected relationship group are migrated to the newly built target relationship group.

In one embodiment, the processing unit is further configured to:

and prompting the migrated relationship object or relationship group in the object management list of the main object role, wherein the prompting is used for indicating that the corresponding relationship object or relationship group is migrated to the first object role.

In one embodiment, the processing unit is further configured to: and if the migrated relation object has the interactive message in the service interface of the main object role, migrating the existing interactive message to the service interface of the first object role.

In an embodiment, the display unit is further configured to: after the first object role is created, displaying the created first object role in a service interface of the main object role;

The processing unit is further used for closing the split creation inlet when the number of the created split object roles is larger than a number threshold; wherein closing the split creation portal includes any one of: hiding the split creation portal, and setting the split creation portal to an inoperable state.

In one embodiment, the first object role is any one of the N split object roles; the processing unit is also used for responding to the role switching operation and switching from the first object role of the target object to the third object role of the target object; the method comprises the steps of,

the display unit is also used for displaying a service interface of a third object role, and the service interface of the third object role supports the target object to use the third object role for data processing;

wherein the third object character comprises a master object character or any one of the N split object characters other than the first object character.

In one embodiment, the service interface of the first object role includes an account management interface of the first object role; the identification of the first object role and the identification of the third object role are displayed in an account management interface of the first object role; the processing unit, in response to the role switch operation, is operable to, in particular, switch from the first object role of the target object to the third object role of the target object:

And switching from the first object role of the target object to the third object role of the target object in response to a triggering operation of the identification of the third object role displayed in the account management interface of the first object role.

In one embodiment, the processing unit is further configured to: in the account management interface of any object role, the object role currently being used by the target object is prompted.

In one embodiment, the display unit is further configured to display an object addition interface of the master object role in response to the object addition request received by the login account, where the object addition interface includes n+1 object roles;

the processing unit is also used for selecting the n+1 object roles in the object adding interface; the object requested by the object addition request is added to the object management list of the selected object character among the n+1 object characters.

In one aspect, an embodiment of the present application provides a computer apparatus, including:

a processor adapted to execute a computer program;

a computer readable storage medium having a computer program stored therein, which when executed by a processor, implements a data processing method as described above.

In one aspect, embodiments of the present application provide a computer readable storage medium storing a computer program loaded by a processor and performing a data processing method as described above.

In one aspect, embodiments of the present application provide a computer program product comprising a computer program stored in a computer readable storage medium. A processor of a computer device reads the computer program from a computer-readable storage medium, and the processor executes the computer program so that the computer device performs the above-described data processing method.

In the embodiment of the application, N body-divided object roles which are allowed to be used by a target object under a login account are displayed; n split object roles are all subordinate to one main object role under a login account, and the N split object roles are mutually independent; n is a positive integer; responsive to selection of a first object role of the N split object roles, displaying a service interface for the first object role; the service interface of the first object character supports the target object to perform data processing by using the first object character and supports independent management of the character data of the first object character. On one hand, the embodiment of the application provides different body-separated object roles under the same login account, so that the target object can flexibly select the object roles to deal with the data processing scene in the client, the object adaptation degree in different data processing scenes is improved, and the flexibility and the intelligence of data processing are improved; on the other hand, after the individual object roles are selected, the individual object roles can independently manage own role data, so that flexible management of data is realized, and the data privacy and safety of each individual object role can be protected to a certain extent.

Drawings

In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a block diagram of a data processing system in accordance with an illustrative embodiment of the present application;

FIG. 2 is a flow chart of a method for processing data according to an exemplary embodiment of the present application;

FIG. 3a is a schematic diagram of a service interface provided by an exemplary embodiment of the present application;

FIG. 3b is a schematic illustration of a service interface provided by another exemplary embodiment of the present application;

FIG. 3c is a schematic illustration of a service interface provided by yet another exemplary embodiment of the present application;

FIG. 3d is a schematic diagram of an object role switch provided by an exemplary embodiment of the present application;

FIG. 3e is a schematic diagram of an entry account management interface provided by an exemplary embodiment of the present application;

FIG. 3f is a schematic diagram of a prompt for an object role currently in use provided by an exemplary embodiment of the present application;

FIG. 4a is a schematic illustration of an add object provided by an exemplary embodiment of the present application;

FIG. 4b is a schematic diagram of a relational object migration provided by an exemplary embodiment of the application;

FIG. 4c is a schematic diagram of an interactive message migration provided by an exemplary embodiment of the present application;

FIG. 4d is a schematic diagram of a cross-identity sharing relationship setup between a type of split object roles provided by an exemplary embodiment of the present application;

FIG. 4e is a diagram illustrating data sharing between different individual object roles provided by an exemplary embodiment of the present application;

FIG. 5 is a flow chart of a method for creating a split object character according to an exemplary embodiment of the present application;

FIG. 6a is a flow chart of a creation of a split object character according to another exemplary embodiment of the present application;

FIG. 6b is a diagram of setting profile data for a knock-out object character according to an exemplary embodiment of the present application;

FIG. 6c is a schematic diagram of a data synchronization interface provided by an exemplary embodiment of the present application;

FIG. 6d is a schematic diagram of an object management list of a master object role provided in accordance with an exemplary embodiment of the present application;

FIG. 6e is a schematic diagram of relationship chain data under different object roles provided by an exemplary embodiment of the present application;

FIG. 6f is a diagram of interactive message migration of a relationship object provided by an exemplary embodiment of the present application;

FIG. 7a is a flow chart of setting character data for a knock-over object character according to an exemplary embodiment of the present application;

FIG. 7b is a schematic diagram of an object management list of another master object role provided in accordance with an exemplary embodiment of the present application;

FIG. 8 is a flow chart of a method of data processing according to an exemplary embodiment of the present application;

FIG. 9 is a schematic diagram of a data processing apparatus according to an exemplary embodiment of the present application;

fig. 10 is a schematic structural diagram of a computer device according to an exemplary embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The following terms are presented in relation to embodiments of the present application:

1. client terminal

A client may refer to a social APP (Application) corresponding to a server that provides local services to a client, which may include, but is not limited to: social clients, game clients (e.g., cloud game clients, etc.), content interaction platform clients, and so forth. Wherein the social client may include, but is not limited to: instant messaging APP, map social APP, content interaction APP, game social APP, installation-free APP (an application that can be used without download installation, e.g., applet), and so forth. The game client may include, but is not limited to: a multi-object online game APP constructed with cloud games, a role playing game APP, and so on. A client may also refer to a website corresponding to a server that provides local services to a client, such as a social networking site that provides local social session functionality to a client, a game forum that provides game services to a client, and so on. Among them, cloud game (Cloud game) may also be called game on demand (game on demand), which is an online game technology based on Cloud computing technology. Cloud gaming technology enables lightweight devices (thin clients) with relatively limited graphics processing and data computing capabilities to run high quality games. In a cloud game scene, the game is not run in a player game terminal, but is run in a cloud server, the cloud server renders the game scene into a video and audio stream, and the video and audio stream is transmitted to the player game terminal through a network. The player game terminal does not need to have strong graphic operation and data processing capability, and only needs to have basic streaming media playing capability and the capability of acquiring player input instructions and sending the player input instructions to the cloud server.

2. Object and object role

An object may refer to a user of a client, for example: a user logs in through the social account number and uses the social client, and the user is a social object. And the following steps: a certain user logs in through the game account number and uses the game client, and the user is a game object. In the subsequent embodiments of the present application, the target object is taken as an example for illustration, and the target object may be any object in the client.

The object role refers to a setting for representing the identity of an object in a client. An object may correspond to multiple object roles that belong to the same account and that each represent the same object. That is, after the target object logs in to the client by using the account number, a plurality of object roles can be created and used to represent different identities of the target object by using different object roles under different data processing scenes in the client; for example: a certain object role of the target object may be identified as "student of XX class", another object role of the target object may be identified as "staff member of XX company", and yet another object role of the target object may be identified as "dad of yy"; etc.

3. Service interface

The client provides pages, windows, etc. for data processing (e.g., data display, data interaction, etc.) for the target object of the logged-in account. In the embodiment of the application, the target object can have a plurality of object roles under the same login account, so the target object can correspond to the same or different service interfaces under each object role and is used for supporting the target object to perform data processing under different object roles and independently manage the role data of the object roles, wherein the independent management of the role data of the object roles comprises any one of the following steps: the role data for the object role is visible only to the relationship objects in the object management list for the object role; or after the primary account number is successfully logged in the third party application, if the target object selects to use a certain object role in the third party application for application processing, application data associated with the third party application in the role data of the object role is only visible to the relationship objects in the object management list of the object role. By visible is meant: the relationship objects in the object management list of the object roles may access (or view) the role data for the object roles or the application data associated with the third party application in the role data for the object roles.

4. Character data of object characters

Character data refers to some data set for an object at a client under a corresponding object character, which may include, but is not limited to: basic data describing the object under the object role, interactive dynamic data describing the object under the object role, and relationship chain data (namely an object management list) formed by relationship objects with interactive relationship with the object; functional data which can be used by the object under the object roles, attribute data of a service interface, role state data describing the object roles, cross-identity sharing relation data which can share data among the split object roles in a cross-identity manner, and application data associated with third-party applications. The character data of the individual character can be bound with the individual account of the corresponding individual character, so that the character data of the corresponding individual character can be acquired according to the individual account.

Wherein the base data may include, but is not limited to: nicknames, IDs, hobbies, etc. of the target object under the object character; the interactive dynamic data may include, but is not limited to: interactive messages, dynamic comment data, etc.; the relationship chain data may include, but is not limited to: a relationship object having an interactive relationship with the target object, and object information of the relationship object; the functional data may include, but is not limited to: reading, cartoon, live broadcast, etc.; attribute data may include, but is not limited to: font setting data, night mode data, sound setting data; character status data may include, but is not limited to: the individual object character is in an online state, a leaving state, a stealth state, a busy state, and an application state (such as listening to songs, playing games, viewing today's weather, etc.) that the target object uses the application under the individual object character; sharing relationship data across identities may include, but is not limited to: various video data and various file data; application data associated with the third party application may include, but is not limited to: application data associated with the applet in the service interface of the object character (e.g., number of games of the game applet, current game level, etc.), application data associated with the plugin in the service interface of the object character.

It will be appreciated that in embodiments of the present application, various types of data related to an object, such as an object role, role data of the object role, account numbers, etc., are involved, and when the above embodiments of the present application are applied to a specific product or technology, permission or consent of the object needs to be obtained, and collection, use and processing of related data needs to comply with related laws and regulations and standards of related countries and regions.

The embodiment of the application provides a data processing scheme which is at least provided with the following mechanism:

(1) The target object allows creation of multiple (n+1) object roles under the same client account, each of the n+1 object roles being used to represent the target object. One main object role and N individual object roles can be contained in the n+1 objects; n individual object roles are all subordinate to the main object role, and the N individual object roles are mutually independent. The assignment of the individual object character to the master object character means that: the separate object role can be created only if the master object role already exists.

In one embodiment, the master object role may be an object role created when the target object is registered in the client, the client allocates a client account for the registered target object, the target object may log into the client using the allocated client account, for example, the target object may obtain a social account when registered in the social client, and the target object may log into the social client using the social account; the target object obtains a game account number when the game client registers, and the target object can log in to the game client by using the game account number. For convenience of description, in the embodiment of the present application, a client account obtained by registration and distribution of a target object is referred to as a primary account, and after the target object successfully logs in to the client by using the primary account, the primary account is also referred to as a login account.

The primary object role is bound to the primary account number, i.e., the primary object role's ID is equal to the primary account number. The target object logs in the client by using the main account and requests to create a body-separated object role under the main account, the client allocates a body-separated account (namely the ID of the body-separated object role) to the created body-separated object role, and the body-separated account belongs to the main account; by subordinate it is meant to include the following aspects: (1) the individual account number is valid only if the primary account number is valid; (2) only allowing the use of the sub-individual account of the main account under the condition that the main account logs in; (3) after the primary account number successfully logs in the client, the separate account number also successfully logs in the client; and after the primary account number logs out from the client, the separate account number also logs out from the client. The target object may uniformly manage the character data of the N individual object characters using the master object character, for example, an object management list of the N individual object characters and interactive messages under each individual object character may be uniformly managed.

The N individual characters are independent of each other, which means that the character data corresponding to each individual character is independent of each other, and the character data of each individual character is independently managed by using the individual account numbers corresponding to each individual character. The managing of the character data using the separate account may include: the role data of each individual object role is associated with each individual object role and stored; the target object uses the character data under a certain split object character (for example, a split object character A) to only exist under the split account corresponding to the split object character, and only allows independent management (for example, inquiry, editing and display) to be performed by using the split account corresponding to the split object character; the target object cannot query and display the character data of the separate object character (i.e., separate object character a) using separate account numbers corresponding to other separate object characters (e.g., separate object character B).

(2) The target object allows to use a plurality of (n+1) object roles under the same login account, and supports the mutual switching among the plurality of object roles, so that the target object is used for representing different identities of the target object under different data processing scenes in the client, and further data processing is performed based on the different identities. The data processing herein may include, but is not limited to: sending or receiving interactive messages, modifying character data of the corresponding object character, etc.

(3) The target object can set a cross-identity sharing relationship between the individual object roles, wherein the cross-identity sharing relationship is a relationship used for indicating whether data sharing can be performed between the individual object roles or not, and the data sharing can be performed between the individual object roles with the cross-identity sharing relationship. Here, the data sharing across identities may include the following two types: (1) data sharing can be performed by using one individual object role to a relationship object under another individual object role; for example, the individual object character a and the individual object character B have a cross-identity sharing relationship, and the target object can share file data, video data and the like belonging to the individual object character a with the individual object character a to a relationship object (e.g., friend c) in the object management list of the individual object character B. (2) The character data under one body-divided object character can be used in the process of data sharing of the other body-divided object character; for example, the individual object character a and the individual object character B have a cross-identity sharing relationship, and when the target object can use the individual object character a to share data with a relationship object (such as a friend d) in the object management list of the individual object character a, file data, video data, and the like belonging to the individual object character B can be selected. That is, if the individual object roles do not have a cross-identity sharing relationship, the individual object roles are independent of each other, and the role data under the individual object roles are independent of each other, and cannot be shared, viewed or invoked. And if the inter-identity sharing relationship is provided between the individual object roles, the inter-identity data sharing is allowed between the individual object roles having the inter-identity sharing relationship.

Through the mechanism, the embodiment of the application can allow the target object to create different object roles under the same login account, and enriches the identity setting of the target object when the target object performs data processing in the client. And meanwhile, different split object roles are provided under the same login account, so that the target object can flexibly select the object roles to cope with the data processing scene in the client, and the independent and effective management of the data of the split object roles is realized. In addition, flexible switching among a plurality of object roles can be allowed under the same login account, so that different identity settings can be flexibly switched by a target object to adapt to different data processing scenes in a client, the object adaptation degree under different data processing scenes is improved, and the data processing efficiency and the intelligence are improved; in addition, the main object roles can be used for uniformly managing each subordinate individual object role, so that the uniformity and effectiveness of management can be improved; the individual object roles can be managed independently, so that certain data isolation can be achieved among the individual object roles, and the data privacy and safety among the individual object roles are ensured. The embodiment of the application can also set a cross-identity sharing relationship to establish a cross-identity data sharing channel between the individual object roles, so that the data sharing of the individual object roles can be realized rapidly.

Next, a related description will be given of the data processing system provided by the present application. Referring to fig. 1, fig. 1 is a schematic diagram of a data processing system according to an embodiment of the present application. As shown in fig. 1, the data processing system may include a terminal device 101, a terminal device 102, … …, and a server 103, which is not limited by the number of terminal devices, but of course, the number of servers may also be plural, which is not limited by the present application. The terminal device 101 and the terminal device 102 in the data processing system may be directly or indirectly connected to the server 103 through wired or wireless communication, and the terminal device 101 and the terminal device 102 may perform information interaction through the server 103. Wherein:

the terminal device 101 has a client running thereon, which may be a social client, a game client, or the like. The object in the embodiment of the application can refer to a user using the client, any one object can have one or more login accounts for logging in the client, and a plurality of object roles can be created under each login account. The terminal device 101 and the terminal device 102 may be used to display service interfaces in different object roles and set different role data for the different object roles. Any one of the terminal devices may include, but is not limited to, a smart phone, tablet, notebook, desktop computer, smart speaker, smart watch, vehicle terminal, smart wearable device, etc.

The server 103 may correspond to a client, and provide technical support for a service provided by the client. For example, when the client is a social client, the server 103 may correspond to the social client, and provide technical support for a social service provided by the social client; for another example, when the client is a game client, the server 103 may correspond to the game client and provide technical support for a game service provided by the game client.

The server 103 may create a master object role when registering a target object in the client, and when creating a split object role for the target object, allocate a split account for each split object role, and bind and store the split account with the role data set by the split object role. Meanwhile, the server 103 may pull corresponding character data according to the splitting account of the splitting object character, and send the pulled character data to the client in the terminal device 101.

At this time, data associated with the target object may also be stored in the server 103, and may include, but is not limited to: the login account and account password of the object, the individual account of the individual object role, the account login state, the common login equipment, and the role data (such as relationship chain data, basic data of the target object, etc.) bound with the individual account of the individual object role.

The server 103 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or may be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (content delivery network), basic cloud computing services such as big data and an artificial intelligence platform. Cloud computing refers to a delivery and use mode of an IT infrastructure, namely that required resources are obtained in an on-demand and easily-expandable manner through a network; generalized cloud computing refers to the delivery and usage patterns of services, meaning that the required services are obtained in an on-demand, easily scalable manner over a network. Such services may be IT, software, internet related, or other services. Cloud Computing is a product of fusion of traditional computer and network technology developments such as Grid Computing (Grid Computing), distributed Computing (distributed Computing), parallel Computing (Parallel Computing), utility Computing (Utility Computing), network storage (Network Storage Technologies), virtualization (Virtualization), load balancing (Load balancing), and the like. With the development of the internet, real-time data flow and diversification of connected devices, and the promotion of demands of search services, social networks, mobile commerce, open collaboration and the like, cloud computing is rapidly developed. Unlike the previous parallel distributed computing, the generation of cloud computing will promote the revolutionary transformation of the whole internet mode and enterprise management mode in concept.

Cloud storage (cloud storage) is a new concept that extends and develops in the concept of cloud computing, and a distributed cloud storage system (hereinafter referred to as a storage system for short) refers to a storage system that can combine a large number of different types of storage devices (storage devices are also referred to as storage nodes) in a network through application software or an application interface to cooperatively work together through functions such as cluster application, grid technology, and a distributed storage file system, so as to provide data storage and service access functions for the outside. At present, the storage method of the storage system is as follows: when creating logical volumes, each logical volume is allocated a physical storage space, which may be a disk composition of a certain storage device or of several storage devices. The client stores data on a logical volume (e.g., in embodiments of the application, role data for the object roles). That is, the data is stored on the file system, the file system divides the data into a plurality of parts, each part is an object, the object not only contains the data but also contains additional information such as a data Identification (ID) and the like, the file system writes each object into the physical storage space of the logical volume, and the file system records the storage location information of each object, so that when the client requests to access the data, the file system can enable the client to access the data according to the storage location information of each object.

In one embodiment, a data processing flow is described by taking as an example between any one of the terminal apparatuses 101 and the server 103, the data processing flow including:

(1) The target object may log in the client through inputting the primary account number and the account number password in the client in the terminal device 101, and after successful log-in, display a service interface of a primary object role of the target object, where the service interface of the primary object role may include an account management interface, where a split creation portal may be set in the account management interface, the target object may trigger the split creation portal, and when the client in the terminal device 101 is triggered in response to the split creation portal, may generate a split creation request, and send a split creation request to the server 103, where the split creation request carries the primary account number, and the split creation request is used to instruct the server 103 to create a split object role that can be used under the primary account number.

(2) After receiving the split creation request, the server 103 may assign a split account to the to-be-created split object character, the split account subordinate to the main account (i.e., the login account), and return the split account of the split object character to the client.

(3) The client in the terminal apparatus 101 can create the split object character after receiving the information such as the split account assigned to the split object character.

In one embodiment, after N number of the split object roles are created, the data processing flow may further include:

(1) The target object can log in the client through inputting the primary account number and the account number password through the client in the terminal equipment 101; specifically: the client may generate a login request according to the primary account, and send the login request to the server 103, where the login request carries the primary account and the account password, and the login request is used to request to login to the client.

(2) When receiving the login request, the server 103 obtains the individual accounts of the individual object roles belonging to the main object role based on the account, and returns the individual accounts of the individual object roles to the client;

(3) After receiving the individual accounts of the plurality of individual roles, the terminal device 101 may successfully log in the client based on the primary account and the account password, and at the same time, the N individual accounts are all successfully logged in to the client. The client in the terminal device 101 may display N individual object roles that the target object is allowed to use under the login account.

(4) The target object may select a desired one of the N individual object roles (i.e., the first object role), and the client of the terminal apparatus 101 may transmit, in response to the selection of the first object role, a first data acquisition request carrying the individual account number of the first object role to the server 103.

(5) The server 103 receives the first data acquisition request, pulls a service interface bound with the splitting account of the first object role according to the splitting account of the first object role, and returns the service interface of the first object role to the client in the terminal equipment 101; in some embodiments, the server 103 may further obtain the role data of the first object role based on the body account of the first object role, and return the role data to the client in the terminal device 101 together with the interface data of the service interface of the first object role.

(6) The client in the terminal device 101 receives the service interface of the first object character and displays the service interface of the first object character.

(7) The target object may perform data processing using the first object role in the service interface of the first object role, and independently manage the role data of the first object role. For example, the dynamic data is published in the service interface of the first object role of the target object, the terminal device 101 responds to the publishing operation of the dynamic data, displays the dynamic data in the service interface of the first object role, sends the dynamic data to the server 103, and the server 103 stores the dynamic data in association with the splitting account of the first object role, so as to facilitate the subsequent independent management of the role data of the first object role by using the splitting account of the first object role, for example: the server 103 sends the dynamic data to the terminal device (e.g., terminal device 102) where the relationship object in the object management list of the first object character is located, so that the relationship object can view the dynamic data, i.e., the character data of the first object character is visible only to the relationship object in the object management list of the first object character.

(8) When the target object wants to switch to the second object role for data processing, the target object can be switched from the first object role to the second object role through certain role switching operations (such as clicking a separate account of the second object role, clicking a switching button and the like), the second object role is any separate object role in the N separate object roles, and the first object role and the second object role are different. The client in the terminal apparatus 101 transmits, in response to the character switching operation, a second data acquisition request carrying the individual account number of the second object character to the server 103.

(9) After receiving the second data acquisition request, the server 103 pulls a service interface bound with the individual account of the second object role; then returning a service interface of the second object role to the client in the terminal equipment 101; in some embodiments, the server 103 may also obtain the role data of the second object role based on the body account of the second object role, and return the role data to the client in the terminal device 101 together with the service interface of the second object role.

(10) And after receiving the service interface of the second object role, the client displays the service interface of the second object role of the target object.

(11) The target object may perform data processing using the second object character in the service interface of the second object character, and independently manage character data of the second object character. For example, the target object issues dynamic data in the service interface of the second object role, the terminal device 101 responds to the issue operation of the dynamic data, displays the dynamic data in the service interface of the second object role, and sends the dynamic data to the server 103, and the server 103 stores the dynamic data in association with the splitting account of the second object role, so as to facilitate the subsequent independent management of the role data of the second object role by using the splitting account of the second object role, for example: the server 103 transmits the dynamic data to the terminal device (except the terminal device 102) where the relationship object in the object management list included in the character data of the second object character is located, so that the relationship object can view the dynamic data, that is, the character data of the second object character is visible only to the relationship object in the object management list of the second object character.

In the embodiment of the present application, the client in the terminal device 101 may include three important modules, namely, a network layer, a data layer and a presentation layer, and the functions of the modules are as follows:

1) Network layer: the module responsible for communication between the client 101 and the server 103 may send the login account of the object, the splitting account of the splitting object role, the role data of the splitting object role, the expansion information of the splitting account based on the splitting object role, and the like to the server 103, meanwhile, the network layer may receive the data (or information) sent or pushed by the server 103, the client may update the received data to the data layer after receiving the data, and the underlying communication protocol is udp (user datagram protocol ). When the network is not connectable, the network layer outputs a prompt message indicating failure.

2) Data layer: primarily storing data associated with the object in the client, the data associated with the object may include: a login account for the object, a separate account for the separate object role, role data for the separate object role (e.g., base data: user nickname, avatar, object management list, etc.), etc. The data associated with the object is stored in a memory cache (a cache memory) and a local Database (Database), and when the memory cache does not have the data yet, the corresponding data is loaded to the local Database and cached in the memory cache, so that the data acquisition speed is improved. And after receiving the data sent by the server, the client side simultaneously updates the memory cache and the database. The database can be considered as an electronic filing cabinet, namely a place for storing electronic files, and a user can perform operations such as adding, inquiring, updating, deleting and the like on data in the files. A "database" is a collection of data stored together in a manner that can be shared with multiple users, with as little redundancy as possible, independent of the application.

3) Display layer: the UI (User Interface) display part responsible for the client mainly comprises two major parts, wherein the first part is basic information display of the split object character and setting of the split creation entry display of the split object character and character data of the split object character, and the setting of the character data can include but is not limited to: migration of relationship chain data (e.g., relationship objects in an object management list), editing of underlying material data, interactive dynamic data (e.g., spatial dynamic data, dynamic data of a small world, video data, etc.), synchronization of functional data, attribute data, and so forth. All the above are responsible for presentation by standard system controls; the second part is a display icon, and the corresponding icon is displayed on the currently displayed interface. The presentation layer is also responsible for responding to the user interaction operation and calling back to the corresponding function processing, and the capability support is provided by the system control.

Through the data processing system, the embodiment of the application can allow the target object to create different object roles (comprising the main object role and N split object roles) under the same login account, thereby enriching the identity setting of the target object when the target object performs data processing in the client. Meanwhile, the method allows the user to flexibly select the split object roles to perform data processing under the same login account, can independently manage the role data of the split object roles, and can flexibly switch among a plurality of object roles, so that different identity settings can be flexibly switched by a target object to adapt to different data processing scenes in a client, the object adaptation degree under different processing scenes is improved, the data processing efficiency and intelligence are improved, and the pressure of using the same object role to perform data processing is reduced. In addition, the client adopts the network layer and the data layer in the three modules to rapidly acquire the required data under different object roles, and the service interface is displayed through the display layer, so that the client can be better assisted to rapidly acquire the data, and flexible switching between the object roles is completed.

Based on the data processing system, the embodiment of the application provides a data processing method. Fig. 2 is a flow chart of a data processing method according to an exemplary embodiment of the present application. In this embodiment, the data processing method may be executed by a computer device, and more specifically, may be executed by a client in the computer device; the computer device may be a terminal device 101 or a terminal device 102 in the system shown in fig. 1 described above. Referring to fig. 2, the data processing method may include the following steps S201 to S202:

s201, displaying N parts of the object roles allowed to be used by the target object under the login account.

The target object refers to any one object in the client. The target object can have one or more login accounts for logging in a certain client, the number of object roles allowed to be used under each login account can be n+1, the n+1 object roles can represent the target object, and the target object can use different object roles for data processing under different data processing scenes; wherein N is a positive integer. The n+1 object roles may include a main object role and N split object roles, where the N split object roles are all subordinate to the main object role and independent from each other.

The target object can perform unified management on the role data of the N split object roles by using the master object roles, that is, the role data of the split object roles (such as relationship chain data of the split object roles and interactive messages) can be managed in a unified manner by using the master object roles. However, the character data of each individual character is independent of each other, and the target object cannot access the character data of other individual characters by using one individual character. In a social scenario, an object typically has multiple social identities, such as school scenario as students, work scenario as staff, family scenario as children/parents, stranger friend-making scenario as an up-stream person, etc. These different social scenarios correspond to the identity settings of the object in the different scenarios. The object role in the embodiment of the present application can also be understood as the identity setting of the target object in the client.

Each object character may correspond to character data, an account of the object character (the account may be a primary account or a separate account), and so on. The character data may include any one or more of the following: basic data, interaction dynamic data, relationship chain data, function data, attribute data, character state data, cross-identity sharing relationship data and application data associated with a third party application, wherein the character data of each individual object character are mutually independent, and the character data of each individual object character is managed by adopting an individual account corresponding to each individual object character.

In one embodiment, the target object may input the primary account number and the account number password in the client to successfully log in the client, and after the primary account number is successfully logged in the client, the N individual accounts are all successfully logged in to the client. At the moment, the primary account and the split account are both logged in the client side at the same time, so that the simultaneous login of the primary object roles and the multiple split object roles is realized, the message can be timely received and transmitted, the problem that the split object roles can receive the message but are not on-line in an intermediate state is avoided, and the message receiving and transmitting efficiency and the intelligence are improved.

In one embodiment, after the primary account number successfully logs in to the client, N individual object roles allowed to be used by the target object under the login account number may be displayed in a service interface under the primary account number. The service interface of the primary account number may be any interface provided by the client after the primary account number is logged into the client. When the client is a social client, the service interface may include, but is not limited to: the present embodiments are not limited in this regard as to interfaces for a service interface for displaying a list of social session messages, a social session message interface for conducting a social session and displaying a stream of session messages for the social session, a functional interface, a setup interface (for setting account security, setting contact), an account management interface, and so forth. For example, the service interface is a social session interface for displaying a social session message list, which may be displayed in area 311 of the service interface as shown in fig. 3a with a master object role 3111 and a split object role 3112 allowed to be used under the same login account, a social session message list in area 312 of the service interface, and a series of options (i.e., message option, channel option, contact option, point of view option, dynamic option, etc.) in area 313 of the service interface. As another example, the service interface may be a functional interface, which may be as shown in fig. 3b, in which a plurality of functional options (e.g., live, member, wallet, personality, etc.) may be displayed in an area 314 of the service interface, and a setup option 32 is displayed in an area 315 of the service interface; two split object roles, split 1 and split 2, respectively, are displayed in region 324 of the service interface, and the master object role is displayed in region 325 of the service interface.

When the client is a game client, the service interface may include, but is not limited to: the embodiments of the present application are not limited to these examples, and the examples include a service interface for displaying game interactions, a social session message interface for conducting a social session and displaying a session message stream of the social session, a function interface, a setting interface (for setting account security, setting a game sound size, and game image quality definition), and the like. For example, the service interface may display game interactions (i.e., two game objects are chased) in an area 316 of the service interface as shown in FIG. 3 c; the master object character and the 3 split object characters (i.e., split a, split B, split C) allowed to be used under the same login account are displayed in area 326 of the service interface.

The display positions of the main object role and the individual object role in the service interface can be flexibly set, and the embodiment of the application is not limited. In one embodiment, the master object role and the split object role may be displayed in any area in the service interface; for example, the main object character and the separate object character shown in fig. 3a are displayed in an upper area (i.e., area 311) of the service interface; and the following steps: the master object roles and the split object roles may also be displayed in the right region (e.g., master object roles and split object roles are displayed in region 326 in fig. 3 c), left region, lower region, etc. of the service interface, as embodiments of the application are not limited in this regard.

The main object character and the separate object character may be displayed in any area of the service interface in a fixed manner, in a floating manner, in a preset period, etc., and the present application is not limited thereto, and the main object character and the separate object character may be displayed in different areas, for example, as shown in fig. 3b, the separate object character may be displayed in an area 324 of the service interface, and the main object character may be displayed in an area 325 of the service interface.

The above service interfaces of N individual object roles allowed to be used by the target object under the display login account may be understood as service interfaces of the master object roles, and in this case, the target object may use the master object roles to perform data processing in the service interfaces of the master object roles.

The above data processing is somewhat different for different service interfaces. Taking the service interface as any interface in the social client as an example, when the service interface of the first object role is a service interface for displaying a social session message list, the data processing may include, but is not limited to: receive and send social session messages, post dynamic messages (i.e., enter dynamic message post through dynamic options of region 313), view contacts (i.e., view contacts through contact options of region 313), select a split object role, and so forth. When the service interface of the first object role is a functional interface, the data processing may include, but is not limited to: live, persona, view collection data, select a split object role, etc.

The target object can respectively set different role states for each object role according to actual requirements, and the role states of each object role can be the same or different; wherein the character status may include any of the following: online status, away status, stealth status, busy status, application status. The target object may click on the avatar information of any object character, and in response to a click operation of the avatar information of any object character (e.g., clicking on the avatar information 31 of the master object character 3111 in fig. 3 a), a character state selection window may be displayed, the character state selection window including one or more of an on-line state, an off-state, a stealth state, a busy state, an application state, and setting the selected character state as the character state of the object character.

S202, responding to selection of a first object role in the N split object roles, and displaying a service interface of the first object role; the service interface of the first object character supports the target object to perform data processing by using the first object character and supports independent management of the character data of the first object character.

When the target object wants to select a first object character of the N individual object characters for data processing, the first object character of the N individual object characters may be clicked or double clicked, a service interface of the first object character is displayed in response to the selection of the first object character, and the target object may use the first object character for data processing and independently manage the data of the first object character in the service interface of the first object character. For example, the target object may click on the split object character 3112 as in fig. 3a, and in response to selection of the split object character 3112, a service interface for the split object character 3112 is displayed.

The service interface of the first object role may refer to any interface provided by the client when the target object uses the first object role. When the client is a social client, the service interface may be any interface provided by the social client under the first object role, for example, the service interface of the first object role may include, but is not limited to: the present embodiments are not limited in this regard as to interfaces for displaying a list of social session messages, a service interface for conducting a social session and displaying a stream of session messages for the social session, a function interface, a setup interface (for setting account security, setting contact details), etc.

When the client is a game client, the service interface of the first object role may be any interface provided by the game client, for example, the service interface of the first object role may be a service interface for displaying game interaction, a social session message interface for performing a social session and displaying a session message stream of the social session, a function interface, a setting interface (for setting account security, setting a playing sound size, and playing image definition), and the like.

Wherein independently managing the character data of the first object character may include any one of: the character data for the first object character is visible only to the relationship objects in the object management list for the first object character; or after the primary account number is successfully logged in the third party application, if the target object selects to use the first object role in the third party application for application processing, application data associated with the third party application in the role data of the first object role is only visible to the relationship objects in the object management list of the first object role. For example, the role data for the first object role includes interaction dynamics data (e.g., posting comments) that are all visible to the relationship objects in the object management list for the first object role. The interactive dynamic data is invisible to the relationship objects in the object management list of other object roles. For another example, the target object selection plays a game using the split object character a in the game applet, and application data (e.g., game state) associated with the game applet among the character data of the split object character a is visible only to the relationship objects in the object relationship list of the split object character a.

In the embodiment of the application, the flexible switching among a plurality of object roles can be performed on the same login account, so that different identity settings can be flexibly switched by a target object to adapt to different data processing scenes in a client, the adaptation degree of the object under the different data processing scenes is improved, and the efficiency and the intelligence of data processing are improved. When the target object wants to switch from the first object role to the other object roles, role switching can be triggered, and responding to the role switching operation, the first object role of the target object is switched to the third object role of the target object; and displaying a service interface of a third object role of the target object, wherein the service interface of the third object role supports the target object to process data by using the third object role and supports independent management of the role data of the third object role.

The first object role and the third object role refer to different object roles which are allowed to be used by the target object under the same login account, and the third object role can comprise a main object role or any one of the N split object roles except the first object role. The service interface of the third object role may refer to any interface provided by the client when the target object uses the third object role. When the client is a social client, the service interface of the third object role may be any interface provided by the social client under the third object role, for example, the service interface of the third object role includes, but is not limited to: a service interface for displaying a list of social session messages, a social session message interface for conducting a social session and displaying a stream of session messages for the social session, a functional interface, a setup interface (for setting account security, setting contact addresses)), and so forth. When the client is a game client, the service interface of the third object role may be any interface provided by the game client under the third object role, for example, the service interface of the third object role may be a service interface for displaying game interaction, a social session message interface for performing a social session and displaying a session message stream of the social session, a function interface, a setting interface (for setting account security, setting a playing sound size, and playing image quality definition), and the like.

The above-described character switching operation may be a trigger operation of a voice input character switching, for example, the target object may input "switch to third object character" by voice, the computer device may perform voice recognition on the voice "switch to third object character" and recognize the resultant "third object character", and the computer device may switch from the first object character of the target object to the third object character of the target object based on the recognized "third object character".

The service interface of the first object role includes one or more switching options, each switching option corresponds to one object role, and the role switching operation may be: triggering operation of the switching option corresponding to the third object role can be clicking operation, double-clicking operation and the like. At this time, the computer device switches from the first object role to the third object role in response to a trigger operation of a switching option corresponding to the third object role. Any switching option may be displayed in suspension in the service interface, or fixedly displayed in a certain area of the service interface, or displayed in the service interface for a period of time, which is not limited by the implementation of the present application.

The service interface of the first object role comprises an account management interface of the first object role, and the account management interface of the first object role can display identifications of the n+1 object roles. The identification herein may refer to nicknames, avatar information, etc. of the object character; as shown in fig. 3d, an identification 317 of the first object role and an identification 318 of the third object role may be displayed in the account management interface 301. The target object may directly select the third object role to be switched in the account management interface under the first object role, where the role switching operation may be a triggering operation of the identifier of the third object role (for example, the triggering operation may be an operation of clicking the identifier of the third object role), and the computer device switching from the first object role of the target object to the third object role of the target object in response to the role switching operation may include: in response to a triggering operation of the identification of the third object role displayed in the account management interface of the first object role, switching from the first object role of the target object to the third object role of the target object, and displaying a service interface of the third object role of the target object, i.e. displaying the service interface 302 of the third object role as in fig. 3d, a social session message list is displayed in an area 320 of the service interface of the third object role.

It should be understood that the identification of n+1 object roles that can be used under the same login account may be displayed in the account management interface of any object role.

When the service interface of the first object role includes a service interface for displaying a social session message list, an account management interface of the first object role needs to be entered first. The manner of entering the account management interface of the first object role may be: the service interface of the first object role comprises the head portrait information of the first object role, the function interface of the first object role is entered in response to the triggering operation of the head portrait information of the first object role, the function interface comprises a setting option, when the setting option is triggered, the function interface is entered, the setting interface comprises an account management option, and the account management interface under the first object role is displayed in response to the triggering operation of the account management option (such as clicking the account management option). For example, referring to fig. 3e, fig. 3e is a schematic diagram of an entering account management interface, in fig. 3e, a service interface includes avatar information 31 of a first object character, a target object may trigger the avatar information 31 of the first object character (e.g. click on the avatar information 31), and a computer device displays a function interface in response to a click operation of the avatar information of the first object character, where the function interface includes a setting option 32; the target object may click on the setting option 32, that is, the setting option 32 is triggered, the computer device displays a setting interface, where the setting interface includes an account management option 33, the target object triggers the account management option 33 (that is, clicks on the account management option 33), and in response to a triggering operation of the account management option 33, the account management interface 301 of the first object role is displayed.

In addition, in the account management interface of any object role, besides displaying n+1 object roles, the object role currently being used by the target object can be prompted, so that the object can conveniently and quickly know the object role currently being used. For example, in the account management interface 301 in fig. 3d, in addition to displaying the identifier 317 of the first object role and the identifier 318 of the third object role, in the account management interface 301, the identifier 317 of the first object role correspondingly displays a prompt 319 of "current use", and the prompt 319 prompts that the object role currently being used by the target object is the first object role.

Meanwhile, after the computer equipment responds to the role switching operation and is switched from the first object role to the third object role, the object role currently being used by the target object is prompted in the account management interface of the first object role, and the prompt is used for prompting that the object role currently being used by the target object is the third object role. As shown in fig. 3f, in the account management interface 301, after switching from the first object role to the third object role in response to the role switching operation, a prompt 321 for prompting that the object role currently being used by the target object is the third object role is correspondingly displayed on the identifier of the third object role in the account management interface 301.

In one embodiment, any one object (e.g., a target object) may add different objects under different object roles, where the object to be added may be understood as adding friends. By adding objects, the target object may establish an interactive relationship with the object to be added. Wherein, there are two cases in which the target object adds the object:

(1) The target object actively adds an object, and in this case, the target object performs data processing using a target object character of n+1 object characters, and thus an object to be added can be added to the object management list of the target object character. Wherein the target object role is any one of n+1 object roles. For example, when the target object performs data processing using the object character 1, and the target object wants to add the object 1, the target object may add the object 1 to the object management list of the object character 1; for another example, when the target object is performing data processing using the object character 2 and the target object wants to actively add the object 1, the object 1 may be added to the object management list of the object character 2.

(2) The target object adds an object according to an object addition request transmitted by the object, in which case the target object may choose to add the object requested by the object addition request to the object management list of any one of the n+1 object roles. The computer equipment responds to the object adding request received by the login account, and displays an object adding interface under the role of the main object. The object addition interface may include n+1 object roles; and selecting the n+1 object roles in the object adding interface, and adding the object requested by the object adding request to an object management list under the selected object role in the n+1 object roles. The selection operation may be an operation of clicking or double-clicking any one of n+1 object characters; alternatively, the selecting operation may further include: the target object clicks, double clicks on any one of the n+1 object roles and triggers the operation of the object to add a confirmation option in the interface.

Wherein, after the login account receives the object adding request, an object notification interface may be displayed, where the object notification interface includes the object adding request, where the object adding request includes a nickname of the requested object, object description information, and the like, and adding options. For example, as shown in fig. 4a, an object addition request 41 is included in the object notification interface 401, and a nickname "deer-horn", object description information "i am XXXX … …", and an addition option 42 are included in the object addition request 41. When the target object triggers the add option 42, the computer device may display an object add interface 402 under the master object role in response to the object add request received by the login account, where 2 object roles are displayed in the area 43 of the object add interface, the master object role and the individual object role respectively. When the target object performs a selection operation on 2 object roles in the object addition interface (e.g., selects the master object role and clicks on the confirm option 44 "ok"), the computer device may add the object requested by the object addition request to the object management list of the master object role.

In one embodiment, all of the individual object roles may be managed identically using the master object role. The service interface of the main object role can display the N split object roles and the role data of the N split object roles, and the service interface of the main object role uniformly manages the role data of the N split object roles. The unified management here may include: the main object roles can be used for checking the role data of each individual object role, and data migration is carried out on the role data of N individual object roles; setting a cross-identity sharing relationship between the individual object roles, and the like. The service interface of the main object role can be any interface provided by the client when the main object role is used, and the service interface of the main object role can be the same as or different from the service interface of the first object role.

(1) When the character data includes relationship chain data, performing the same management on the character data of the N individual object characters in the service interface of the master object character may include: the method may include displaying an object management list of N split object roles in a service interface of a master object role, selecting one or more relationship objects from the object management list of a first object role in response to an object migration operation, and migrating the selected relationship objects into an object management list of a second object role, which may be any one of the N split object roles, the first object role and the second object role being different. The object migration operation may be an operation of clicking a relationship object in an object management list of a selected first object character, dragging a relationship object in the object management list of the first object character, and the like.

For example, as shown in fig. 4b, an object management list 45 of the split object character 1 (i.e., the split 1) and an object management list 46 of the split object character 2 (i.e., the split 2) are displayed in the service interface 403 of the master object character; when the target object clicks the relationship objects "small four" and "small none" in the selected object management list 45, the relationship objects "small four" and "small none" are migrated to the object management list 46 of the second object character in response to the click operation for the relationship objects in the object management list 45, and at this time, the relationship objects "small four" and "small none" are migrated to the "nearest attention" in the object management list 46.

(2) When the character data includes interactive dynamic data, the interactive dynamic data includes an interactive message; the unified management of the data under the N individual object roles in the service interface of the master object role may further include: and if the migrated relation object has the interactive message in the service interface of the first object role, migrating the existing interactive message to the service interface of the second object role. For example, as shown in fig. 4c, the first object role is a split object role a, the second object role is a split object role B, the migrated relationship object "listown" has an interactive message "ait" in the service interface of the split object role a, and the interactive message "ait" is migrated to the service interface of the split object role B. At this time, the service interface is a session message interface, where the session message interface includes a message list, and the interactive message may be migrated to the message list of the body-separated object role B. For another example, when the interactive dynamic data includes dynamic data (e.g., a spatial comment), the dynamic data in the service interface of the first object persona is migrated into the service interface of the second object persona in response to a migration operation of the dynamic data.

The target object can use the main object role to check the interaction information under all the split object roles, and when a certain interaction information is replied, the default use of the split object roles corresponding to the interaction information is replied, and at this time, unified management of the data under the N split object roles in the service interface of the main object role can be as follows: displaying the interactive messages under the N split object roles in the service interface of the main object role; responding to the reply operation of the target interaction message under the first object role, and sending a reply message of the target interaction message by using the first object role; and displaying a reply record for the target interaction message in the service interface of the first object role. The reply operation may be an operation of clicking on the target interactive message and inputting a reply message, or the reply operation may be an operation of inputting a reply message through voice. When clicking the target interactive message, a reply window can be directly displayed on the service interface of the main object role, the target object can directly input the reply message in the reply window, and the reply message of the target interactive message is sent by using the first object role in response to the reply operation of the target interactive message under the first object role. By uniformly managing the interactive messages under each split object role, all the interactive messages can be intensively checked, so that corresponding interactive messages can be quickly replied.

In addition, the target object may use the split object roles to view interactive messages under the corresponding split object roles. At this time, only the interactive messages of the relation objects in the object management list of the first object role are displayed, and the problem of finding important messages in the advertisement messages can be solved by the mode, so that the important messages can be quickly obtained.

In the embodiment of the application, in order to realize quick data calling under each individual object role and realize data sharing among the individual object roles, a cross-identity sharing relationship among the individual object roles can be set. When the role data includes cross-identity sharing relationship data, unified management of data under N individual object roles in the service interface of the master object role may include: setting cross-identity sharing relations among N split object roles in a service interface of a main object role; the method comprises the steps that data sharing across identities is allowed between the individual object roles with the across-identity sharing relationship, and data sharing across identities is not allowed between the individual object roles without the across-identity sharing relationship. As shown in fig. 4d, the service interface of the main object role may be a relationship setting interface 404, and in the relationship setting interface 404, a part object role having a cross-identity sharing relationship with part 1, a part object role having a cross-identity sharing relationship with part 2, and a part object role having a cross-identity sharing relationship with part 3 may be set. The relationship setting interface 404 includes a creation option 47 corresponding to each of the individual object roles (e.g., the individual 1 corresponds to the creation option 47 and the individual 2 corresponds to one of the creation options in fig. 4 d), the target object may trigger the creation option 47 corresponding to a certain individual object role (e.g., the individual 1), and in response to the triggering operation of the creation option, a plurality of individual object roles may be displayed, a individual object role (e.g., the individual 2) that is to establish a cross-identity sharing relationship is selected from the plurality of individual object roles, and a cross-identity sharing relationship between the selected individual object role and the individual object role is established (i.e., the cross-identity sharing relationship between the individual 1 and the individual 2 is created). In addition, a delete option 48 is further provided in the relationship setting interface 404, and the delete option 48 can delete the corresponding cross-identity sharing relationship. For example, the target object clicks the delete option 48 corresponding to the part 2, and in response to the clicking operation for the delete option 48, the cross-identity sharing relationship between the part 1 and the part 2 is deleted.

Taking a first object role and a second object role as an example, if a cross-identity sharing relationship is provided between the first object role and the second object role, a data list (such as a collection list) to be shared is displayed in response to a sharing request received in a service interface of the first object role, wherein the data list contains role data of the first object role to be shared and role data of the second object role to be shared; and executing sharing operation on the selected data to be shared in the data list; and displaying the sharing record in the service interface of the first object role. For example, as shown in fig. 4e, a cross-identity sharing relationship is provided between a first object role and a second object role, a data list 405 to be shared is displayed in response to a sharing request received in a service interface of the first object role, the data list 405 includes role data 49 of the first object role to be shared and role data 50 of the second object role to be shared, a target object may select data to be shared (such as the role data 49 of the selected first object role) in the data list, and a sharing operation is performed on the selected data to be shared in the data list; and displaying the sharing record 51 "successfully sharing the picture DDDDDDD to the second object role" in the service interface 406 of the first object role. The sharing operation performed on the selected data to be shared in the data list may be, but is not limited to: the method comprises the steps of sharing data to be shared to any relation object in an object management list of a first object role; or the sharing operation is used for sharing the data to be shared to any relation object in the object management list of the second object role.

In the embodiment of the application, the computer equipment displays N parts of object roles which are allowed to be used by the target object under the login account; n split object roles are all subordinate to one main object role under a login account, and the N split object roles are mutually independent; n is a positive integer; responsive to selection of a first object role of the N split object roles, displaying a service interface for the first object role; the service interface of the first object character supports the target object to perform data processing by using the first object character and supports independent management of the character data of the first object character. On one hand, different body-separated object roles are provided under the same login account, so that a target object can flexibly select the object roles to deal with different data processing scenes in a client, the object adaptation degree under the different data processing scenes is improved, and the data processing efficiency and the intelligence are improved; on the other hand, after the individual object roles are selected, the individual object roles can independently manage own role data, so that flexible management of data is realized. In addition, the cross-identity sharing relationship can be established between the individual roles, so that the flexible and efficient cross-identity data sharing can be realized.

Referring to fig. 5, fig. 5 is a flowchart of a method for creating a split object role according to an embodiment of the present application, where the method for creating a split object role may be executed by a computer device, and the method for creating a split object role according to the embodiment of the present application may include the following steps S501 to S502:

s501, displaying a service interface of a target object in a main object role, wherein the service interface of the main object role comprises an account management interface of the main object role, and a split creation entry is arranged in the account management interface.

As shown in fig. 5, the account management interface of the master object role included in the service interface of the master object role may be provided with a split creation portal 51 in the account management interface 501 of the master object role, and the split object role may be quickly created through the split creation portal 51.

Wherein the parts-up creation portal may be "+ create parts-up" as shown in fig. 5, which may be one parts-up creation option, a parts-up creation button, a parts-up creation prompt, or the like. Of course, the parts-in-parts creation portal in the embodiment of the present application may be displayed at the position shown in fig. 5, or may be displayed at other positions in the account management interface of the main object character, or may be displayed in a hidden manner (i.e. the parts-in-parts creation portal needs to be displayed by a certain triggering operation), which is not limited in the embodiment of the present application.

In one embodiment, the login account (i.e., the primary account) is bound to the primary object role, the target object may input the login account and the account password in the client, and the computer device may verify the input login account and account password, and display a service interface of the primary object role of the target object after the verification is successful.

S502, responding to the trigger of creating an entry for the segmentation, and creating a first object role.

When the target object wants to create the split object role, the split creation portal can be triggered, the computer equipment responds to the triggering of the split creation portal, a split creation request is generated and sent to the server, the split creation request carries a login account, the server receives the split creation request, a split account can be allocated to the split object role to be created according to the login account, the split account is returned to the computer equipment, and the computer equipment creates the first object role according to the split account. Wherein the trigger to create an entry to the partition may be: clicking or double clicking on the parts creates an entry.

In the process of creating the body-divided object roles, the target object can set role data for the body-divided object roles to be created; or after the creation of the completed individual object character, setting character data for the created individual object character can enrich the individual object character by setting character data for the individual object character. The computer equipment can send the character data set for the body-divided object character to the server, and after receiving the character data set for the body-divided object character, the server can bind the character data with the body-divided account corresponding to the body-divided object character, so that the subsequent inquiry of the character data of the body-divided object character based on the body-divided account is facilitated. Wherein the character data may include any one or more of the following: basic material data, interaction dynamic data, relationship chain data, function data, attribute data, role state data, cross-identity sharing relationship data, and application data associated with a third party application.

(1) The target object may set character data for the first object character in creating the first object character. In response to a trigger to create an entry for the partition, creating the first object role may include: the computer equipment responds to the triggering operation executed by the split creation portal, displays a split creation interface, wherein a split data configuration function interface is arranged in the split creation interface, sets character data for a first object character to be created in the split data configuration function interface, and creates the first object character after the setting is completed. The method comprises the steps that a creation option is included in a displayed separation creation interface, and a separation data configuration function interface arranged in the separation creation interface can be accessed through the creation option. For example, in fig. 6a, in response to a trigger operation of the knock creation portal 51, a knock creation interface 602 is displayed, a creation key 62 is included in the knock creation interface 602, when the creation key 62 is triggered, the knock data configuration function interface 603 may be displayed, and character data that may be set in the knock data configuration function interface 603 may include: basic material data, function data, relationship chain data, and attribute data, character data is set for a first object character to be created in the knock-down data configuration function interface 603, and after the configuration is completed and a trigger operation for the confirmation option 63 is detected, the first object character is created.

Optionally, a prompt message is further included in the part creation interface, and as shown in fig. 6a, the part creation interface 602 further includes a prompt message 61. The hint information 61 is used to indicate that the character data configured for the individual object character can be re-edited independently of the character data of the master object character, and that the relationship link data in the master object character can be migrated, which facilitates management of the relationship link data.

(2) The target object may configure the character data for the first object character after the first object character is created. The computer device may display a service interface of the first object character, which includes a knock-over data setting interface in which character data may be set for the created first object character.

In one embodiment, the above-mentioned configuration interface of the knock-out data and the knock-out data setting interface may each include a knock-out data editing interface, and when the character data includes basic data, setting the character data for the first object character may be: displaying a separate data editing interface, automatically filling basic data of a main object role in the separate data editing interface, editing the filled data in the separate data editing interface by a target object, and generating basic data of a first object role by computer equipment in response to the editing operation of the filled data in the separate data editing interface. The editing here may be confirmation of the filled data or modification of the filled data. Accordingly, the editing operation may be a confirmation operation for the filled data or a modification operation for the filled data. When the editing operation is a confirmation operation of the filled data, the base data of the first object character may multiplex the base data of the main object character. For example, as shown in fig. 6b, a profile editing interface is displayed, in which basic profile data of a main object character is filled, the target object can edit the data filled in the profile editing interface (e.g., modify the avatar 64), and the computer device generates basic profile data of the first object character in response to the modification operation of the avatar in the profile editing interface, at which time the avatar 64 of the basic profile data has been modified into the avatar 65.

In another embodiment, the above-mentioned configuration function interface and configuration setting interface may further include a data synchronization interface, when the character data includes any one or more of the following: when the dynamic data, the functional data and the attribute data are interacted, the target object can select whether to synchronize the role data of the main object role in the data synchronization interface, so that the role data authority under the split object role is set, and the target object can conveniently and efficiently manage the corresponding dynamic data, the functional data and the attribute data and the viewing authority of the role data under the split object role. At this time, setting character data for the first object character may be: the computer device may display a data synchronization interface including a synchronization switch control, and if the synchronization switch control is in an off state during the setting process, set the character data of the first object character to be null, that is, not synchronize the character data of any main object character at this time. If the synchronous switch control is triggered to be turned on in the setting process, the role data of the main object role can be synchronized into the role data of the first object role. When the character data includes at least two of interactive dynamic data, functional data and attribute data, the data synchronization interface may only include one synchronization switch control, and if the synchronization switch control is triggered to be turned on, at least two of the interactive dynamic data, the functional data and the attribute data may be synchronized into the character data of the first object character. Of course, the data synchronization interface may include multiple synchronization switch controls, one of which may control synchronization of one character data.

For example, as shown in fig. 6c, in the data synchronization interface, the interactive dynamic data corresponds to one synchronization switch control 66, the functional data corresponds to one synchronization switch control 66, and the attribute data may correspond to one synchronization switch control 66. If any one of the synchronous switch controls is triggered to be turned on in the setting process, the role data corresponding to the triggered synchronous switch control is synchronized into the role data of the first object role, for example, the function data corresponding to the triggered synchronous switch control can be synchronized into the role data of the first object role by the computer equipment. For example, the interactive dynamic data includes comment data, and when a synchronous switch control corresponding to the interactive dynamic data is triggered to be turned on, the comment data is synchronized into character data of the first object character.

The above-mentioned synchronization of the role data of the main object role into the role data of the first object role includes one or more of the following synchronization modes: synchronizing existing character data of the master object character to the first object character; synchronizing the existing character data of the main object character to the first object character, and synchronizing the updated data to the first object character when the character data of the main object character is updated, namely synchronizing the character data of the main object character to the first object character in real time; and synchronizing the role data of the main object role in the preset time period to the first object role. The preset time period may be set according to the need, for example, character data of the master object character in the preset time period "2022/4/21-2022/4/22" may be synchronized to the first object character.

In still another embodiment, the above-mentioned interface for configuration of the splitting data and the interface for setting of the splitting data may further include a splitting object selection interface, where the splitting object selection interface includes: when the role data comprises the relationship chain data, the relationship objects in the object management list of the main object role can be migrated to the first object role, the corresponding object management list is managed under the split object role, the relationship objects and the viewing authority of the relationship objects can be efficiently managed through the migration of the relationship objects, and when the target object is used for data processing (comment making, mood making and game playing) by using the split object role, only the relationship objects in the object management list of the split object role can view the data processing result, namely, view comments, mood making, game progress and the like issued by the target object, so that the user content sharing cost and risk are reduced. At this time, setting character data for the first object character may include: displaying an object management list of a main object role, wherein the object management list of the main object role can be as shown in fig. 6d, and the object management list of the main object role comprises all relationship objects with interaction relationship with a target object, and the interaction relationship is a relationship that the relationship objects in the object management list can interact with the target object or can access data of the other party mutually; one or more relationship objects are then selected from the object management list of the master object role and the selected relationship objects are migrated to the object management list of the first object role. As in fig. 6d, the object management list 67 of the master object character is included in the separate object selection interface, the relationship object "small four", the relationship object "small none", and the relationship object "small six" are selected from the object management list 67 of the master object character, and the selected relationship object "small four", relationship object "small none", and relationship object "small six" are added to the object management list of the first object character.

Wherein the relationships in the object management list of the master object character may be divided into a plurality of relationship groups, as in fig. 6d, 6 relationship groups, i.e., special interest group, my friend group, senior citizen group, and others, are included in the object management list of the master object character. Alternatively, each relationship group may display a corresponding number of relationship objects, such as 3 in a particular relationship group, 10 in my friends group, and 40 in friends group. In the object management list that migrates the selected relationship object to the first object role may be: and based on the identification of the relation group to which the selected relation object belongs, migrating the selected relation object to the relation group with the same identification in the object management list of the first object role. For example, the identification of the relationship group to which the selected relationship object belongs is "other", and the selected relationship object may be migrated to the relationship group identified as "other" in the object management list of the first object role. Of course, the selected relationship object may be randomly migrated to any relationship group in the object management list of the first object role, which is not limited in the present application.

In addition to migrating one or more relationship objects, the embodiment of the present application may migrate a relationship object included in a whole group, where setting role data for a first object role further includes: when one or more relationship groups in the object management list of the master object character are selected, all relationship objects in the selected relationship groups are integrally migrated to the object management list of the first object character. For example, if the relationship group "my friends" in the object management list of the master object role is selected, all relationship objects in the selected relationship group "my friends" are migrated to the object management list of the first object role as a whole. At this time, as shown in fig. 6e, after the entire group is migrated to the object management list of the first object character, the service interface of the first object character includes a contact option 68, through which a group list of the main object corners can be entered, at which time the migrated relationship group "colleague" is not shown in the group list of the main object character, the service interface of the first object character includes a contact option 69, through which the group list of the first object character is entered, and then "colleague" is shown in the group list of the first object character.

Wherein, the whole migration of all the relationship objects in the selected relationship group to the object management list of the first object role may include: if the object management list of the first object role has the target relationship group which is the same as the identification of the selected relationship group, the selected relationship group is combined with the existing target relationship group, and at the moment, all relationship objects in the selected relationship group can be added into the target relationship group, or a new relationship group is created again, and all relationship objects in the selected relationship group and all relationship objects in the target relationship group are added into the new relationship group. If the object management list of the first object role does not have the relationship group which is the same as the identification of the selected relationship group, a target relationship group is newly built in the object management list of the first object role based on the identification of the selected relationship group, and all relationship objects of the selected relationship group are migrated to the newly built target relationship group. At this time, the identification of the target relationship group is the same as the identification of the selected relationship group.

The object management list of the master object role may further include a relationship group in the object management list of the created individual object role, and if the relationship group in the object management list of the created individual object role is selected, the selected relationship group in the object management list of the created individual object role may be migrated to the object management list of the first object role.

In the process of migrating the relation object or the relation group to the object management list of the first object role, if the migrated relation object has an interactive message in the service interface of the main object role, migrating the existing interactive message to the service interface of the first object role. For example, in fig. 6f, in migrating the relationship object "mins" to the object management list of the individual object character, the relationship object "mins" may have an interaction message "how long you are found" in the service interface of the master object character, and the computer device may migrate the interaction message "how long you are found" to the service interface of the individual object character, at this time, the interaction message "how long you are found" may not be displayed in the service interface of the master object character.

In one embodiment, a hint may be provided in the object management list of the master object role for the migrated relationship object or relationship group that indicates that the corresponding relationship object and relationship group has been migrated to the first object role.

The above-mentioned interface of the configuration function of the data of the devising and devising data set up interface can include the following multiple kinds: an object management list of the main object roles, a body data editing interface and a data synchronization interface; the system comprises a grouping data configuration function interface and a grouping data setting interface, wherein the grouping data configuration function interface and the grouping data setting interface comprise a grouping data editing interface, a data synchronization interface and an object management list of a main object role; the computer device may set character data for the first object character in the object management list of the parts-of-body material editing interface, the data synchronization interface, and the master object character in this order. Referring to fig. 7a, the computer device displays a separate data editing interface, basic data of a main object character is automatically filled in the separate data editing interface, the target object can edit the data filled in the separate data editing interface, the computer device responds to the editing operation of the filled data in the separate data editing interface (that is, the editing operation can also trigger the interface switching option 70 in the separate data editing interface), and displays a data synchronization interface, if the synchronization switch control is always in the off state in the setting process, the character data of the first object character is set to be empty, that is, the character data of any main object character is not synchronized at the moment. If the synchronous switch control is triggered to be started in the setting process, the role data of the main object role can be synchronized into the role data of the first object role; then, by triggering an operation (e.g., triggering interface switching option 71 in the synchronous data interface), an object management list of the primary object character is displayed, one or more relationship objects are selected from the object management list of the primary object character, and the selected relationship objects are added to the object management list of the first object character.

It should be understood that, in the embodiment of the present application, the role data may be set for the individual object roles according to the requirements, that is, only the basic data of the individual object roles may be set, and only the relationship chain data of the individual object roles may be set. Of course, at least two of basic data, interactive dynamic data, relationship chain data, functional data and attribute data may be set, and at this time, the corresponding interface setting may be sequentially entered, and the setting sequence is not limited by the present application. Any one of the N split object roles may be created according to a split creation flow for creating the first object role.

In one embodiment, after the first object role is created, the first object role may be displayed on a service interface of the master object role, which may include, but is not limited to: the account management interface, the interface where the object management list is located, the setting interface, and the service interface are not limited in this embodiment of the present application. For example, in fig. 6a, after the split object character is created, the created split object character "split 1" may be displayed in the account management interface 601. In addition, after the first object role is created, the first object role may be further managed in a service interface of the master object role, where the managing may include: the created first object character is deleted and marked in the object management list of the master object character. For example, in FIG. 7b, the object management list 72 of the master object role marks the created split object role 1 (i.e., split 1 in FIG. 7 b) to the relationship group "My friends (3 people)" that has migrated under the split object role 1; the created split object character 2, i.e. the split 2 in fig. 7b, is marked to the relationship group "my friends (23 people)" that has migrated under the split object character 2.

When the number of created individual object characters is N, the name of each individual object character may be named as individual object character 1, individual object character 2 … …, individual object character N in the order of creation. Of course, the name of each of the individual characters may be generated as required.

In one embodiment, when the number of the created individual object roles is multiple, the server may acquire the role data of the created individual object roles, and perform independent deduplication processing on the role data of the created individual object roles, so as to ensure that the role data under each individual object role is independent of each other, and does not appear in other individual object roles, thereby ensuring the security of data processing to a certain extent. The character data of each individual character mainly includes: the relationship chain data is independent (namely, the relationship objects in the management object list of the created body-part object roles are not appeared in the object management lists of other body-part object roles), the interaction dynamic data is independent (the interaction dynamic data of the body-part object roles of the created body-part object roles are not checked by the relationship objects in the object management lists of other body-part object roles), and the interaction message is independent (namely, the social messages sent by the target objects and the corresponding relationship objects under the created body-part object roles are not acquired by other body-part object roles).

In one embodiment, to facilitate managing the number of the split object roles of the target object and prevent the target object from creating too many split object roles, the number of the created split object roles may be counted, and it may be determined whether the number of the created split object roles is greater than a number threshold, and when the number of the created split object roles is greater than the number threshold, the split creation portal may be closed, wherein closing the split creation portal may include any one of: concealing the split creation portal, placing the split creation portal in an inoperable state. The number threshold may be set according to requirements, for example, the number threshold may be 3, 4, 5; the application is not limited in this regard. When the number of the created split object roles (such as deleting a part of the split object roles) is less than or equal to the number threshold, the split creation portal can be opened again in the account management interface under the main object roles, and the opening of the split creation portal can include any one of the following: displaying the split creation portal and placing the split creation portal in an operable state.

In the embodiment of the application, a service interface of a target object in a main object role is displayed, wherein the service interface of the main object role comprises an account management interface, and a split creation inlet is arranged in the account management interface; and responding to the triggering operation of the split creation portal, creating a first object role, and allowing the target object to create different object roles under the same login account according to the split creation portal, so that the identity setting of the target object in the client during data processing is enriched, and the social pressure is relieved.

Next, in conjunction with the creation flow of the split object role, the embodiment of the present application further provides a data processing method, where the data processing method may be as shown in fig. 8, and the data processing method may include:

(1) The social client displays a service interface of a target object in a main object role, wherein the service interface of the main object role comprises an account management interface of the main object role, and a split creation entry is arranged in the account management interface. When the target object wants to create a split object role under the login account, the split creation portal may be triggered, and the social client may generate a split creation request in response to a triggering operation performed by the split creation portal, where the split creation request carries the login account (i.e., the primary account) and the account name, and the split creation request is used to instruct the server to create the split object role under the login account.

(2) After receiving the split creation request, the server responds to the split creation request, and creates a split account for the split object role according to the login account, wherein the split account can be a split object role ID, and the split account can also be: the login account is obtained by splicing the login account with the role ID of the splitting object. The follow-up server can conveniently search the role data and the like of the roles corresponding to the splitting objects through the splitting account. In fig. 8, after receiving the login account and the account name a, the server may allocate a split ID1 to the split object character 1 according to the login account and the account name a, and splice the login account and the split ID1 to obtain a split account (i.e., an account index) of the split object character 1, and similarly, may subsequently obtain a split account of the split object character 2 and a split account of the split object character 3.

(3) The social client may send the role data (e.g., space dynamic data) set for the created split role to the server, and the server may bind the role data (space dynamic data) with the split account of the split object role, so that the corresponding role data may be obtained based on the split account of the split object role sent by the client.

(4) After binding the role data of the split object roles with the corresponding split account numbers, the server can perform independent duplicate removal processing on the created split object roles according to the creation time of the split object roles. Specifically, according to the creation time of the individual object roles, the relationship chain data, the interactive dynamic data and the like in the role data of each individual object role are subjected to de-duplication cutting processing, so that the individual object roles are mutually independent. Taking two split object roles as an example, by performing the deduplication cutting process on the relationship link data and the interactive dynamic data in the role data of the split object role 1 and the split object role 2, the friend "xiao Li" exists in the object management list included in the relationship link data of the split object role 1, and the friend "xiao Li" does not exist in the object management list included in the relationship link data of the split object role 2. For another example, the target object sends interactive dynamic data (e.g., posting a comment) using the split object character 1, which can be viewed by the relationship objects in the object management list of the split object character 1, but not by the relationship objects in the object management list of the split object character 2.

(5) After the deduplication processing is performed, a login account, a splitting account of the splitting object role, role data (such as nickname, head portrait and other basic data) and the like can be returned to the social client, the social client receives the login account, the splitting account of the splitting object role, the role data and the like, and the social client creates the splitting object role.

Referring to fig. 9, fig. 9 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application; the data processing means may be a computer program (comprising program code) running in the computer device, for example the data processing means may be an application software in the computer device; the data processing device may be used to perform some or all of the steps in the method embodiments shown in fig. 2 and 5. Referring to fig. 9, the data processing apparatus includes the following units:

the display unit 901 is used for displaying N body-divided object roles allowed to be used by a target object under a login account; n split object roles are all subordinate to one main object role under the login account, and the N split object roles are mutually independent; n is a positive integer;

a processing unit 902 for displaying a service interface of a first object character among the N split object characters in response to a selection of the first object character; the service interface of the first object character supports the target object to perform data processing by using the first object character and supports independent management of the character data of the first object character.

In one embodiment, the processing unit 902 is further configured to:

In one embodiment, the display unit 901 is further configured to display N number of split object roles and role data of the N number of split object roles in a service interface of the main object roles; the method comprises the steps of,

the processing unit 902 is further configured to perform unified management on the role data of the N individual object roles in the service interface of the master object role.

In one embodiment, the role data includes relationship chain data; when the processing sheet 902 performs unified management on the role data of the N split object roles in the service interface of the master object role, the processing sheet may be specifically used for:

In one embodiment, the character data comprises interactive dynamic data, the interactive dynamic data comprising interactive messages; when the processing unit 902 performs unified management on data under N split object roles in the service interface of the master object role, the processing unit is further configured to:

In one embodiment, the role data includes cross-identity sharing relationship data; when the processing unit 902 performs unified management on data under N split object roles in the service interface of the master object role, it may be specifically used to:

In an embodiment, the display unit 901 is further configured to, if a cross-identity sharing relationship is provided between the first object role and the second object role, display a data list to be shared in response to a sharing request received in a service interface of the first object role, where the data list includes role data of the first object role to be shared and role data of the second object role to be shared;

the processing unit 902 is further configured to perform a sharing operation on the selected data to be shared in the data list; the sharing operation is used for sharing the data to be shared to any relation object in the object management list of the first object role; or the sharing operation is used for sharing the data to be shared to any relation object in the object management list of the second object role; the method comprises the steps of,

The display unit 901 is further configured to display a sharing record in a service interface of the first object role.

In one embodiment, the character data comprises interactive dynamic data, the interactive dynamic data comprising interactive messages; when the processing unit 902 performs unified management on data under N split object roles in the service interface of the master object role, it may be specifically used to:

In one embodiment, the first object role is any one of the N split object roles; the display unit 901 is further configured to display a service interface of a master object role, where the service interface of the master object role includes an account management interface of the master object role, and a split creation entry is set in the account management interface of the master object role;

the processing unit 902 is further configured to create a first object role in response to a trigger to create an entry to the partition.

In one embodiment, in response to a trigger of creating an entry for the split, after creating the first object character, the display unit 901 is further configured to display a service interface of the first object character, where the service interface of the first object character includes a split data setting interface;

a processing unit 902, configured to set character data for the created first object character in the knock-over data setting interface; wherein the character data includes any one or more of: basic material data, interaction dynamic data, relationship chain data, function data, attribute data, role state data, cross-identity sharing relationship data, and application data associated with a third party application.

In one embodiment, the character data includes base material data; a display unit 901 for displaying a knock-down material editing interface when setting character data for a first object character;

a processing unit 902, configured to automatically fill basic data of the main object role in the profile editing interface; and generating the basic data of the first object role in response to the editing operation of the filled data in the split data editing interface.

A processing unit 902, configured to set the character data of the first object character to be null if the synchronous switch control is always in the off state in the setting process; and if the synchronous switch control is triggered to be started in the setting process, synchronizing the role data of the main object role into the role data of the first object role.

In one embodiment, the processing unit 902 synchronizes the role data of the master object role to the role data of the first object role, including one or more of the following synchronization:

In one embodiment, the role data includes relationship chain data; when setting character data for a first object character, a display unit 901 is configured to display an object management list of a master object character, where the object management list of the master object character includes all relationship objects having an interaction relationship with a target object;

A processing unit 902 configured to select one or more relationship objects from the object management list; the selected relationship object is migrated to the object management list of the first object role.

In one embodiment, the relationship objects in the object management list of the master object role are partitioned into multiple relationship groups; in setting character data for the first object character, the processing unit 902 is further configured to:

In one embodiment, the processing unit 902, when migrating all the relationship objects in the selected relationship group as a whole into the object management list of the first object role, may be specifically configured to:

In one embodiment, the processing unit 902 is further configured to:

In one embodiment, the processing unit 902 is further configured to: and if the migrated relation object has the interactive message in the service interface of the main object role, migrating the existing interactive message to the service interface of the first object role.

In one embodiment, the display unit 901 is further configured to: after the first object role is created, displaying the created first object role in a service interface of the main object role;

closing the split creation portal when the number of the created split object roles is greater than a number threshold;

wherein closing the split creation portal includes any one of: hiding the split creation portal, and setting the split creation portal to an inoperable state.

In one embodiment, the first object role is any one of the N split object roles; a processing unit 902 further configured to switch from a first object role of the target object to a third object role of the target object in response to a role switch operation; the method comprises the steps of,

The display unit 901 is further configured to display a service interface of a third object role, where the service interface of the third object role supports the target object to perform data processing by using the third object role;

In one embodiment, the service interface of the first object role includes an account management interface of the first object role; the identification of the first object role and the identification of the third object role are displayed in an account management interface of the first object role; the processing unit 902, in response to the role switch operation, is operable to switch from the first object role of the target object to the third object role of the target object, in particular:

In one embodiment, the processing unit 902 is further configured to: in the account management interface of any object role, the object role currently being used by the target object is prompted.

In one embodiment, the display unit 901 is further configured to display an object addition interface of the master object role in response to the object addition request received by the login account, where the object addition interface includes n+1 object roles;

the processing unit 902 is further configured to perform a selection operation on n+1 object roles in the object addition interface; the object requested by the object addition request is added to the object management list of the selected object character among the n+1 object characters.

Further, the embodiment of the application also provides a schematic structural diagram of the computer device, and the schematic structural diagram of the computer device can be seen in fig. 10. The computer device runs a client; the computer device may include: a processor 1001, an input device 1002, an output device 1003, and a memory 1004. The processor 1001, the input device 1002, the output device 1003, and the memory 1004 are connected by buses. The memory 1004 is used for storing a computer program comprising program instructions, and the processor 1001 is used for executing the program instructions stored in the memory 1004.

In an embodiment of the present application, the processor 1001 performs the following operations by executing executable program code in the memory 1004:

In one embodiment, the processor 1001 is further configured to:

displaying the character data of the N individual object characters in the service interface of the main object character; the method comprises the steps of,

and uniformly managing the character data of the N individual object characters in the service interface of the main object character.

In one embodiment, the role data includes relationship chain data; when the processor 1001 performs unified management on the character data of the N split object characters in the service interface of the master object character, it may be specifically used to:

In one embodiment, the character data comprises interactive dynamic data, the interactive dynamic data comprising interactive messages; when the processor 1001 performs unified management on data under N split object roles in the service interface of the master object role, it is further configured to:

In one embodiment, the role data includes cross-identity sharing relationship data; when the processor 1001 performs unified management on data under N split object roles in the service interface of the master object role, it may be specifically used to:

In one embodiment, the processor 1001 is further configured to:

if the first object role and the second object role have a cross-identity sharing relationship, responding to a sharing request received in a service interface of the first object role, and displaying a data list to be shared, wherein the data list comprises role data of the first object role to be shared and role data of the second object role to be shared;

executing sharing operation on the selected data to be shared in the data list; the sharing operation is used for sharing the data to be shared to any relation object in the object management list of the first object role; or the sharing operation is used for sharing the data to be shared to any relation object in the object management list of the second object role; and displaying the sharing record in the service interface of the first object role.

In one embodiment, the character data comprises interactive dynamic data, the interactive dynamic data comprising interactive messages; when the processor 1001 performs unified management on data under N split object roles in the service interface of the master object role, it may be specifically used to:

In one embodiment, the first object role is any one of N split object roles, and the processor 1001 is further configured to:

displaying a service interface of a main object role, wherein the service interface of the main object role comprises an account management interface of the main object role, and a body-splitting creation inlet is arranged in the account management interface of the main object role;

in response to a trigger to create a portal to the segment, a first object role is created.

In one embodiment, in response to a trigger to create an entry to a split, the processor 1001 may be configured to:

responding to a triggering operation executed by the split creation inlet, displaying a split creation interface, wherein a split data configuration function interface is arranged in the split creation interface;

setting character data for a first object character to be created in a separate data configuration function interface, and creating the first object character after the setting is completed;

In one embodiment, after creating the first object role in response to a trigger to create an entry for the split, the processor 1001 is further configured to:

Displaying a service interface of a first object role, wherein the service interface of the first object role comprises a body-separated data setting interface;

setting character data for the created first object character in a knock-over data setting interface;

In one embodiment, the character data includes base material data; the processor 1001, when setting character data for a first object character, may be specifically configured to:

displaying a separate data editing interface;

automatically filling basic data of the main object roles in the separate data editing interface;

and generating the basic data of the first object role in response to the editing operation of the filled data in the split data editing interface.

In one embodiment, the role data includes any one or more of the following: interaction dynamic data, functional data and attribute data; the processor 1001, when setting character data for a first object character, may be specifically configured to:

displaying a data synchronization interface, wherein the data synchronization interface comprises a synchronization switch control;

If the synchronous switch control is always in the off state in the setting process, setting the character data of the first object character to be null;

and if the synchronous switch control is triggered to be started in the setting process, synchronizing the role data of the main object role into the role data of the first object role.

In one embodiment, the role data includes relationship chain data; the processor 1001 is further configured, when setting character data for a first object character, to:

displaying an object management list of a main object role, wherein the object management list of the main object role comprises all relation objects with interactive relation with a target object;

selecting one or more relationship objects from an object management list of the master object role;

The selected relationship object is migrated to the object management list of the first object role.

In one embodiment, the relationship objects in the object management list of the master object role are partitioned into multiple relationship groups; the processor 1001 is further configured, when setting character data for a first object character, to:

In one embodiment, the processor 1001, when migrating all the relationship objects in the selected relationship group as a whole into the object management list of the first object role, may be specifically configured to:

In one embodiment, the processor 1001 is further configured to:

and if the migrated relation object has the interactive message in the service interface of the main object role, migrating the existing interactive message to the service interface of the first object role.

In one embodiment, the processor 1001 is further configured to:

after the first object role is created, displaying the created first object role in a service interface of the main object role;

In one embodiment, the first object role is any one of the N split object roles; the processor 1001 is further configured to:

switching from the first object role of the target object to the third object role of the target object in response to the role switching operation; the method comprises the steps of,

Displaying a service interface of a third object role, wherein the service interface of the third object role supports the target object to process data by using the third object role;

In one embodiment, the service interface of the first object role includes an account management interface of the first object role; the identification of the first object role and the identification of the third object role are displayed in an account management interface of the first object role; the processor 1001 may be specifically configured to, in response to a character switching operation, switch from a first object character of a target object to a third object character of the target object:

In one embodiment, the processor 1001 is further configured to:

in the account management interface of any object role, the object role currently being used by the target object is prompted.

In one embodiment, the processor 1001 is further configured to:

Responding to an object adding request received by a login account, displaying an object adding interface of a main object role, wherein the object adding interface comprises N+1 object roles;

selecting N+1 object roles in an object adding interface;

the object requested by the object addition request is added to the object management list of the selected object character among the n+1 object characters.

Furthermore, it should be noted here that: the embodiment of the present application further provides a computer readable storage medium, and the computer readable storage medium stores a computer program, where the computer program includes program instructions, when executed by a processor, can perform the method in the embodiment corresponding to fig. 2 and fig. 5, and therefore, a detailed description will not be given here. For technical details not disclosed in the embodiments of the computer-readable storage medium according to the present application, please refer to the description of the method embodiments of the present application. As an example, the program instructions may be deployed on one computer device or executed on multiple computer devices at one site or distributed across multiple sites and interconnected by a communication network.

According to one aspect of the present application, there is provided a computer program product comprising a computer program 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 can perform the method in the corresponding embodiment of fig. 2 and 5, and thus, a detailed description will not be given here.

Those skilled in the art will appreciate that the processes implementing all or part of the methods of the above embodiments may be implemented by a computer program for instructing relevant hardware, and the program may be stored in a computer readable storage medium, and the program may include the processes of the embodiments of the methods as above when executed. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random-access Memory (Random Access Memory, RAM), or the like.

The above disclosure is only a preferred embodiment of the present invention, and it should be understood that the scope of the invention is not limited thereto, and those skilled in the art will appreciate that all or part of the procedures described above can be performed according to the equivalent changes of the claims, and still fall within the scope of the present invention.

Claims

1. A method of data processing, comprising:

displaying N parts of object roles allowed to be used by a target object under a login account; the N split object roles are all subordinate to one main object role under the login account, and the N split object roles are mutually independent; n is a positive integer;

Responsive to selection of a first object role of the N split object roles, displaying a service interface of the first object role; the service interface of the first object role supports the target object to process data by using the first object role, and supports independent management of role data of the first object role.

2. The method of claim 1, wherein n+1 object roles under the login account are each used to represent the target object; the n+1 object roles include the master object role and the N individual object roles;

the login account is used as a main account and is bound with the main object role, and the N split object roles respectively correspond to one split account; n split accounts are all subordinate to the primary account, and after the primary account is successfully logged in a client, the N split accounts are all successfully logged in the client; after successful login, the n+1 object roles respectively correspond to respective role states, wherein the role states comprise any one of the following: an online state, an away state, a stealth state, a busy state, and an application state;

the N parts of the body-separated object roles are mutually independent and comprise: the character data of each of the N split object characters are mutually independent, and the character data of each split object character is independently managed by adopting a split account corresponding to each split object character;

3. The method of claim 2, wherein the method further comprises:

displaying the N split object roles and the role data of the N split object roles in a service interface of the master object role; the method comprises the steps of,

4. The method of claim 3, wherein the role data includes relationship chain data and interaction dynamic data, the interaction dynamic data including interaction messages; the unified management of the character data of the N individual object characters in the service interface of the master object character includes:

displaying object management lists of the N individual object roles in a service interface of the main object role;

in response to an object migration operation, selecting one or more relationship objects from an object management list of the first object role;

Migrating the selected relation object to an object management list of a second object role, wherein the second object role is any one of N separated object roles, and the first object role and the second object role are different;

and if the migrated relation object has the interactive information in the service interface of the first object role, migrating the existing interactive information to the service interface of the second object role.

5. The method of claim 3, wherein the role data includes sharing relationship data across identities; the unified management of the data under the N individual object roles in the service interface of the master object role includes:

setting a cross-identity sharing relationship among the N split object roles in a service interface of the main object role;

and allowing cross-identity data sharing among the individual object roles with the cross-identity sharing relationship.

6. The method of claim 5, wherein the method further comprises:

if the first object role and the second object role have a cross-identity sharing relationship, a data list to be shared is displayed in response to a sharing request received in a service interface of the first object role, wherein the data list comprises role data of the first object role to be shared and role data of the second object role to be shared;

Executing sharing operation on the selected data to be shared in the data list; the method comprises the steps of,

displaying a sharing record in a service interface of the first object role;

the sharing operation is used for sharing the data to be shared to any relation object in the object management list of the first object role; or the sharing operation is used for sharing the data to be shared to any relation object in the object management list of the second object role.

7. The method of claim 3, wherein the character data comprises interactive dynamic data, the interactive dynamic data comprising interactive messages; the unified management of the data under the N individual object roles in the service interface of the master object role includes:

and displaying a reply record aiming at the target interaction message in the service interface of the first object role.

8. The method of claim 2, wherein the independently managing the character data of the first object character comprises any one of:

and after the primary account number is successfully logged in the third-party application, if the target object selects to use the first object role in the third-party application for application processing, application data associated with the third-party application in the role data of the first object role is only visible to the relation object in the object management list of the first object role.

9. The method of claim 1, wherein the first object role is any one of the N split object roles; the method further comprises the steps of:

displaying a service interface of the main object role, wherein the service interface of the main object role comprises an account management interface of the main object role, and a split creation inlet is arranged in the account management interface of the main object role;

creating the first object role in response to a trigger to the split creation portal;

closing the split creation entry when the number of the created split object roles is greater than a number threshold;

wherein said closing said split creation portal comprises any one of: hiding the split creation portal, and setting the split creation portal into an inoperable state.

10. The method of claim 9, wherein the creating the first object role in response to a trigger to create an entry for the split comprises:

responding to a triggering operation executed on the split creation inlet, displaying a split creation interface, wherein a split data configuration function interface is arranged in the split creation interface;

setting character data for a first object character to be created in the splitting data configuration function interface, and creating the first object character after the setting is completed;

11. The method of claim 9, wherein after creating the first object role in response to a trigger to create an entry for the split, further comprising:

displaying the created service interface of the first object role, wherein the service interface of the first object role comprises a split data setting interface;

setting character data for the created first object character in the knock-over data setting interface;

12. A method as claimed in claim 10 or 11, wherein said character data comprises base data; setting character data for the first object character includes:

displaying a separate data editing interface;

automatically filling basic data of the main object roles in the splitting data editing interface;

and responding to the editing operation of the filled data in the body part data editing interface, and generating the basic data of the first object role.

13. A method as claimed in claim 10 or 11, wherein the character data comprises any one or more of: interaction dynamic data, functional data and attribute data; setting character data for the first object character includes:

if the synchronous switch control is triggered to be started in the setting process, the role data of the main object role is synchronized into the role data of the first object role;

the step of synchronizing the role data of the main object role into the role data of the first object role comprises one or more of the following synchronization modes: synchronizing existing character data of the master object character to the first object character; synchronizing the existing character data of the master object character to the first object character, and synchronizing the update data to the first object character when the character data of the master object character is updated; and synchronizing the role data of the master object role in a preset time period to the first object role.

14. A method as claimed in claim 10 or 11, wherein the role data comprises relationship chain data; setting character data for the first object character includes:

displaying an object management list of the main object role, wherein the object management list of the main object role comprises all relation objects with interactive relation with the target object;

and migrating the selected relation object to an object management list of the first object role.

15. The method of claim 14, wherein relationship objects in the object management list of the master object role are partitioned into a plurality of relationship groups; the setting of the character data for the first object character further includes:

and when one or more relation groups in the object management list of the main object role are selected, all relation objects in the selected relation groups are integrally migrated to the object management list of the first object role.

16. The method of claim 15, wherein the integrally migrating all relationship objects in the selected relationship group into the object management list of the first object role comprises:

If the object management list of the first object role already has the target relation group which is the same as the identification of the selected relation group, merging the selected relation group with the existing target relation group;

if the object management list of the first object role does not have the relationship group which is the same as the identifier of the selected relationship group, a target relationship group is newly built in the object management list of the first object role based on the identifier of the selected relationship group, and all relationship objects in the selected relationship group are migrated to the newly built target relationship group.

17. The method of claim 16, wherein the method further comprises:

prompting the migrated relationship object or relationship group in the object management list of the main object role, wherein the prompting is used for indicating that the corresponding relationship object or relationship group is migrated to the first object role;

and if the migrated relation object has the interactive information in the service interface of the main object role, migrating the existing interactive information to the service interface of the first object role.

18. The method of claim 1, wherein the first object role is any one of the N split object roles; the method further comprises the steps of:

Switching from a first object role of the target object to a third object role of the target object in response to a role switching operation; the method comprises the steps of,

displaying a service interface of the third object role, wherein the service interface of the third object role supports the target object to use the third object role for data processing;

wherein the third object character includes the master object character or any one of the N individual object characters other than the first object character.

19. The method of claim 18, wherein the service interface of the first object role comprises an account management interface of the first object role; the identification of the first object role and the identification of the third object role are displayed in an account management interface of the first object role; the switching from the first object role of the target object to the third object role of the target object in response to a role switching operation includes:

and responding to a triggering operation of the identification of the third object role displayed in the account management interface of the first object role, and switching from the first object role of the target object to the third object role of the target object.

20. The method of claim 2, wherein the method further comprises:

and prompting the object role currently being used by the target object in an account management interface of any object role.

21. The method of claim 2, wherein the method further comprises:

responding to an object adding request received by the login account, displaying an object adding interface of the main object roles, wherein the object adding interface comprises the N+1 object roles;

selecting the n+1 object roles in the object adding interface;

and adding the object requested by the object adding request to an object management list of the selected object roles in the n+1 object roles.

22. A data processing apparatus, comprising:

the display unit is used for displaying N body-divided object roles which are allowed to be used by the target object under the login account; the N split object roles are all subordinate to one main object role under the login account, and the N split object roles are mutually independent; n is a positive integer;

a processing unit configured to display a service interface of a first object character among the N split object characters in response to a selection of the first object character; the service interface of the first object role supports the target object to process data by using the first object role, and supports independent management of role data of the first object role.

23. A computer device, comprising:

a processor adapted to execute a computer program;

a computer readable storage medium having stored therein a computer program which, when executed by the processor, performs the data processing method according to any of claims 1-21.

24. A computer-readable storage medium, characterized in that the computer storage medium stores a computer program which, when executed by a processor, performs the data processing method according to any one of claims 1-21.

25. A computer program product, characterized in that the computer program product comprises a computer program which, when executed by a processor, implements the data processing method according to any of claims 1-21.