CN109857762B

CN109857762B - User data processing method, sharing message processing method and computer equipment

Info

Publication number: CN109857762B
Application number: CN201910086102.2A
Authority: CN
Inventors: 陈晓波; 罗程; 李斌
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-01-29
Filing date: 2019-01-29
Publication date: 2021-08-17
Anticipated expiration: 2039-01-29
Also published as: CN109857762A

Abstract

The application relates to a user data processing method, a shared message processing method and computer equipment. The user data processing method can directly inquire the user data of the target user from the user information management system by utilizing the user data inquiry entry and the target user identification without switching among a plurality of systems and a plurality of accounts, and the inquired user data is obtained according to the user data from the user information management system and the application platform respectively. The sharing message processing method can receive the shared first sub-application page message through the target sub-application running in the first application, further acquire and display the shared data from the user information management system, and can efficiently realize data sharing. By adopting the scheme provided by the application, the user data can be efficiently and comprehensively inquired and the data can be shared.

Description

User data processing method, sharing message processing method and computer equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a user data processing method, an apparatus, a computer-readable storage medium, and a computer device, and a shared message processing method, an apparatus, a computer-readable storage medium, and a computer device.

Background

With the development of computer technology, instant messaging tools have become an important bridge for people-to-people communication through networks, for example, more and more workers in enterprises are used to communicate with customers through communication tools, so that the time cost for the workers to communicate with multiple customers in a telephone or on-the-spot manner is saved. However, when the staff is in the face of communicating with a plurality of clients, different clients are easily confused because the user data of each client cannot be queried immediately.

In a traditional user data query mode, a worker needs to log in a user information management system of an enterprise and then input the name of a client to be queried from the user information management system to check the user data of the client. For example, a salesperson a certain sales-type enterprise communicates with a client B through a communication tool, and if the salesperson a wants to check the characteristics of the client B (characteristics of the client B, such as characters, favorite product types, etc.) in advance, the salesperson a certain sales-type enterprise must log in a user information management system of the sales-type enterprise to check the information of the client by using a personal employee account, and then returns to the communication tool to communicate with the client B after checking.

However, in the conventional user data query method, when there are a large number of clients, the instant messaging tool and the user information management system need to be switched over repeatedly through different account numbers, and different names of clients to be queried need to be input into the user information management system repeatedly, which results in low query efficiency for querying the user data.

Disclosure of Invention

In view of the foregoing, it is necessary to provide a user profile processing method, a shared message processing method, an apparatus, a computer-readable storage medium, and a computer device for solving the technical problem of low query efficiency in querying a user profile.

A method of user profile processing, the method comprising:

when a user data query entry for querying user data from a user information management system is triggered, acquiring a target user identifier to be queried;

sending a query request carrying the target user identifier to the user information management system;

receiving user data fed back by the user information management system in response to the query request; the feedback user data is obtained according to the user data which are respectively from the user information management system and the application platform and respectively correspond to the target user identification;

and displaying the received user data.

A user profile processing apparatus, the apparatus comprising:

the target user identification acquisition module is used for acquiring a target user identification to be inquired when a user data inquiry inlet for inquiring user data from the user information management system is triggered;

the query request sending module is used for sending a query request carrying the target user identifier to the user information management system;

the user data receiving module is used for receiving the user data fed back by the user information management system in response to the query request; the feedback user data is obtained according to the user data which are respectively from the user information management system and the application platform and respectively correspond to the target user identification;

and the user data display module is used for displaying the received user data.

A computer-readable storage medium storing a computer program which, when executed by a processor, causes the processor to perform the steps of:

and displaying the received user data.

A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of:

and displaying the received user data.

According to the user data processing method, the user data processing device, the computer readable storage medium and the computer equipment, the user data of the target user can be directly inquired from the user information management system by utilizing the user data inquiry entrance and the target user identification without switching among a plurality of systems and a plurality of accounts, and the inquired user data is obtained according to the user data from the user information management system and the user data from the application platform respectively, so that the user data can be inquired efficiently and comprehensively.

A shared message processing method comprises the following steps:

receiving a shared first sub-application page message; the first sub-application page message specifies a first sub-application page of a first target sub-application;

displaying, by a first target sub-application running in an environment provided by the first application, a first sub-application page of the first target sub-application;

requesting, from a user information management system, shared data corresponding to a first sub-application page of the first target sub-application and associated with a local user identifier;

and displaying the shared data on a first sub-application page of the first target sub-application.

A shared message processing apparatus, the apparatus comprising:

the message receiving module is used for receiving the shared first sub-application page message; the first sub-application page message specifies a first sub-application page of a first target sub-application;

the page display module is used for displaying a first sub-application page of a first target sub-application through the first target sub-application running in an environment provided by the first application;

the shared data request module is used for requesting shared data which corresponds to a first sub-application page of the first target sub-application and is associated with a local user identifier from the user information management system;

and the shared data display module is used for displaying the shared data on a first sub-application page of the first target sub-application.

According to the sharing message processing method and device, the computer readable storage medium and the computer device, the shared first sub-application page message can be received through the target sub-application running in the first application, the shared data is acquired and displayed from the user information management system, and the data sharing can be efficiently realized. In addition, the sharing party only needs to share the same first sub-application page message to different users, and after receiving the same first sub-application page message, the different users all display sharing data related to the sharing party, so that the safety of user information is guaranteed, and high efficiency and convenience of data sharing can be guaranteed.

Drawings

FIG. 1 is a schematic diagram of a user data processing system in one embodiment;

FIG. 2 is a schematic diagram of a user profile processing system in accordance with another embodiment;

FIG. 3 is a flowchart illustrating a user profile processing method according to an embodiment;

FIG. 4 is a flowchart illustrating a method for processing a shared message according to an embodiment;

fig. 5 is a flowchart illustrating a method for processing a shared message according to another embodiment;

FIG. 6 is a timing diagram illustrating a method for processing user profiles in one embodiment;

FIG. 7 is an interface diagram of a sub-application configuration page in one embodiment;

FIG. 8 is an interface diagram that illustrates associating a referral page in one embodiment;

FIG. 9 is a schematic diagram of an interface for a user management page in one embodiment;

FIG. 10 is a schematic diagram illustrating an interface of a user profile query entry configuration page in one embodiment;

FIG. 11 is a schematic diagram of an interface to a base document page in one embodiment;

FIG. 12 is a timing diagram illustrating a method for sharing messages in one embodiment;

FIG. 13 is an interface diagram of a configuration page for a second target sub-application in one embodiment;

FIG. 14 is an interface diagram of a workbench page in one embodiment;

FIG. 15 is an interface diagram of a configuration page of a second target sub-application in another embodiment;

FIG. 16 is a diagram illustrating an interface of an attachment list in one embodiment;

FIG. 17 is an interface diagram that illustrates a sharing list of sub-application pages, according to one embodiment;

FIG. 18 is a diagram illustrating an interface to a dialog box in one embodiment;

FIG. 19 is a schematic diagram illustrating an interface for a local user to identify a sharing list of sub-application pages for which sharing rights exist, according to an embodiment;

FIG. 20 is a schematic diagram illustrating an interface for a second sub-application page message in one embodiment;

FIG. 21 is a schematic diagram of an interface for a second sub-application page message in another embodiment;

fig. 22 is an interface schematic diagram illustrating that the generated second sub application page message is shared to the terminal corresponding to the shared object identifier through a dialog box in another embodiment;

fig. 23 is an interface diagram illustrating that a terminal corresponding to a shared object identifier receives a second sub-application page message shared by a local terminal through a dialog box in another embodiment;

FIG. 24 is a block diagram showing the structure of a user profile processing apparatus according to an embodiment;

fig. 25 is a block diagram showing a configuration of a shared message processing apparatus according to another embodiment;

FIG. 26 is a block diagram showing a configuration of a computer device in one embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

FIG. 1 is a diagram of an embodiment of a user profile processing method. Referring to fig. 1, the user profile processing method is applied to a user profile processing system. The user profile processing system includes a local terminal 110, a user information management system 120, and an application platform 130. The local terminal 110, the user information management system 120, and the application platform 130 are connected through a network.

The local terminal 110 may be a desktop terminal or a mobile terminal, and the mobile terminal may be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The user information management system 120 is a system for managing user information, for example, the user information management system 120 may specifically be a CRM (customer Relationship management) system, which is a system for selecting and managing valuable customers and relationships thereof, and of course, the user information management system 120 may also be another system for managing user information. The application platform 130 may be implemented as a stand-alone server or as a server cluster comprised of multiple servers.

Based on the user profile processing system, when the local terminal 110 detects that a user profile query entry for querying the user profile from the user information management system 120 is triggered, the local terminal 110 obtains a target user identifier to be queried; the local terminal 110 sends a query request carrying a target user identifier to the user information management system 120; the user information management system 120 feeds back user data to the local terminal 110 in response to the query request, the local terminal 110 receives the user data fed back by the user information management system 120 in response to the query request, and the fed back user data are obtained by the user information management system 120 according to the user data which are respectively from the user information management system 120 and the application platform 130 and respectively correspond to the target user identifier; the local terminal 110 displays the received user profile.

The application platform 130 corresponds to one of a first application and a second application, the second application being different from the first application. The first application corresponds to a first application platform and the second application corresponds to a second application platform. When the application platform 130 corresponds to the first application, the fed back user profile is obtained by the user information management system 120 according to the user profiles respectively from the user information management system 120 and the first application platform and respectively corresponding to the target user identifier. When the application platform 130 corresponds to the second application, the fed back user profile is obtained by the user information management system 120 according to the user profiles respectively from the user information management system 120 and the second application platform and respectively corresponding to the target user identifier.

As shown in fig. 2, the first application may be an instant messaging tool used by a collective user, the second application may be an instant messaging tool used by an individual user, and the first application platform may be a collective user application platform and the second application platform may be an individual user application platform. The user profile processing system may specifically include a local terminal 210, a collective user application platform 220, a terminal 230 corresponding to an administrator user identification, an interworking platform 240, an individual user application platform 250, and a terminal 260 corresponding to a target user identification.

Among them, collective users are corporate or non-corporate organizations, etc., corporate organizations refer to national organs, social groups, enterprises, and public works, etc., which enjoy civil rights and undertake civil obligations, and illegal organizations refer to organizations which do not have legal qualifications but can perform civil activities on their own behalf. Individual users such as natural people, which refers to the most basic civil subject.

The local terminal 210 is equipped with an instant messaging facility for use by the collective user. When the target object id corresponds to the instant messenger used by the individual user, the terminal 260 corresponding to the target object id is installed with the instant messenger used by the individual user. When the target object identifier corresponds to the instant messaging tool used by the collective user, the instant messaging tool used by the collective user should be installed in the terminal 260 corresponding to the target object identifier.

The local terminal 210, the terminal 230 corresponding to the administrator user identifier, and the terminal 260 corresponding to the target user identifier may specifically be a desktop terminal or a mobile terminal, and the mobile terminal may specifically be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The collective user application platform 220, the interworking platform 240, and the individual user application platform 250 may be implemented as individual servers or as a server cluster comprised of a plurality of servers.

The local terminal 210 communicates with the collective user application platform 220 over a network. The terminal 230 corresponding to the administrator user identification communicates with the collective user application platform 220 through the network. The collective user application platform 220 communicates with the individual user application platforms 250 through the interworking platform 240. When the target object identification corresponds to the instant messaging tool used by the individual user, the terminal 260 corresponding to the target user identification communicates with the individual user application platform 250 through the network. When the target object identification corresponds to the instant messaging tool used by the collective user, the terminal 260 corresponding to the target object identification communicates with the collective user application platform 220 through the network.

In one embodiment, as shown in FIG. 3, a user profile processing method is provided. The present embodiment is mainly illustrated by applying the method to the local terminal 110 in fig. 1. Referring to fig. 3, the user profile processing method specifically includes the following steps:

s302, when a user data query entrance for querying the user data from the user information management system is triggered, a target user identifier to be queried is acquired.

The user data query entry refers to an entry for querying user data from the user information management system, and the entry may be presented in the form of characters, where the form of characters includes at least one of a text form, a number form and an alphabet form, and the user data query entry may be presented as a "user data query" by taking the entry as an example that the entry is presented in the form of characters. The target user identifier refers to a mark for identifying a target user corresponding to the user profile to be queried, for example, the target user identifier may specifically be a user ID (identification), and the user ID may include at least one of characters such as numbers, symbols, and letters.

Specifically, the local terminal may present a user profile query entry for querying the user profile from the user information management system on the profile page of the target user. And when the local terminal monitors that the current display page is the basic data page, monitoring a user data query entrance of the basic data page. When the local terminal monitors that the user data query entry of the basic data page is triggered, the target user identification corresponding to the basic data page to which the triggered user data query entry belongs is obtained. Further, the user profile query entry of the profile page may be triggered by a touch operation detected by the local terminal.

In one embodiment, when a user profile query entry for querying a user profile from a user information management system is triggered, before acquiring a target user identifier to be queried, the user profile processing method further includes: and the local terminal displays a basic data page corresponding to the target user identification. The local terminal sends a correlation confirmation request to a first application platform corresponding to the currently logged-in first application, wherein the correlation confirmation request is used for indicating the first application platform to confirm whether a set to which the currently logged-in local user identifier belongs is associated with a user information management system in the first application. For example, if the local user identifier is an employee account used by an employee of enterprise a in the first application, the group to which the local user identifier belongs refers to enterprise a.

When the first application platform confirms that the group to which the local user identifier which logs in currently belongs is associated with the user information management system in the first application, the first application platform feeds back associated configuration information corresponding to the association of the first application and the user information management system to the local terminal. The associated configuration information refers to sub-application configuration information of a sub-application associated with the user information management system or web page configuration information of a web page associated with the user information management system. The local terminal receives the association configuration information fed back by the first application platform in response to the association confirmation request, and displays a user data query entry for querying user data from the user information management system on a basic data page of the target user according to the association configuration information.

In one embodiment, the first application is an application belonging to a community. The first application can be an instant messaging tool used by the collective user, and the first application platform is a collective user application platform corresponding to the instant messaging tool used by the collective user.

In one embodiment, a description is given by taking an example of a collective user application platform corresponding to an instant messaging tool used by a first application as a collective user and an instant messaging tool used by a first application platform as a collective user. And the local terminal determines a target user identification selected from a user list displayed by the instant messaging tool used by the collective user and displays a basic data page corresponding to the target user identification. The local terminal sends an association confirmation request to a collective user application platform of the instant messaging tool used by the collective user, wherein the association confirmation request is used for indicating the collective user application platform to confirm whether the group to which the local user identifier currently logged in by the local terminal belongs is associated with the user information management system in the instant messaging tool used by the collective user.

When the collective user application platform confirms that the instant messaging tool of the collective user, to which the local user identifier currently logged in, belongs, is associated with the user information management system, the collective user application platform determines associated configuration information for associating the instant messaging tool of the collective user with the user information management system, and feeds the associated configuration information back to the local terminal. And the local terminal receives the association configuration information fed back by the collective user application platform in response to the association confirmation request, and displays a user data query entry for querying user data from the user information management system in a basic data page corresponding to the target user identifier displayed by the instant messaging tool used by the collective user according to the association configuration information.

S304, sending a query request carrying the target user identification to the user information management system.

Specifically, the local terminal generates a query request carrying a target user identifier according to the obtained target user identifier to be queried, and determines a user information management system associated with the currently logged-in first application. And sending a query request carrying a target user identifier to a user information management system associated with the currently logged-in first application.

In one embodiment, the query request sent by the local terminal to the user information management system is used to instruct the user information management system to obtain the user data to be fed back to the local terminal according to the user data respectively from the user information management system and the application platform and respectively corresponding to the target user identifier.

In one embodiment, the user profiles respectively from the user information management system and the application platform and respectively corresponding to the target user identifier comprise a first user profile from the user information management system and a second user profile from the application platform.

In one embodiment, the user information management system stores a first user profile of the target user in correspondence with the target user identification, the first user profile being a user profile associated with a corresponding community of user information management systems. For example, if the user information management system corresponds to an enterprise that is collectively a sales-type enterprise, the first user data corresponding to the target user identifier may include data such as a type of a product that the target user likes, a price of a product purchased historically, and a character characteristic. The application platform is an application platform to which the target user identifier belongs, the application platform stores second user data of the target user in a corresponding manner according to the target user identifier, and the second user data is user data associated with the application platform to which the target user identifier belongs. For example, the second user profile may include the profile of the avatar, gender, age, nickname, etc. used by the target user in the application platform to which the target user belongs.

In one embodiment, the user information management system obtains the user data to be fed back to the local terminal according to the user data respectively from the user information management system and the application platform and respectively corresponding to the target user identifier, and specifically includes the following steps: the user information management system determines a target user identifier from user identifiers stored in the user information management system, and acquires first user data stored corresponding to the target user identifier. And the user information management system acquires the second user data corresponding to the target user identification from the application platform to which the target user identification belongs through the open interface provided by the first application platform. And the user information management system obtains the user data to be fed back to the local terminal according to the obtained first user data and the second user data.

In one embodiment, the instant messaging tool used by the first application as the collective user and the first application platform as the collective user application platform are taken as examples for explanation. The local terminal generates a query request carrying the target user identification according to the acquired target user identification to be queried, and determines a user information management system associated with the instant messaging tool used by the currently logged collective user. And sending a query request carrying a target user identifier to a user information management system associated with the instant messaging tool used by the currently logged collective user.

And the user information management system responds to the query request, determines a target user identifier from the user identifiers stored in the user information management system, and acquires the first user data stored corresponding to the target user identifier. And the user information management system acquires second user data corresponding to the target user identification from the application platform to which the target user identification belongs through an open interface provided by the collective user application platform. And the user information management system obtains the user data to be fed back to the local terminal according to the first user data and the second user data.

S306, receiving user data fed back by the user information management system in response to the query request; the feedback user data is obtained according to the user data which are respectively from the user information management system and the application platform and respectively correspond to the target user identification.

Specifically, the local terminal receives the user profile fed back by the user information management system in response to the query request. The feedback user data is obtained by the user information management system according to the acquired first user data and the second user data. The user information management system for acquiring the first user data comprises the following steps: the user information management system determines a target user identifier from user identifiers stored in the user information management system, and acquires first user data stored corresponding to the target user identifier. The user information management system acquiring the second user data comprises the following steps: and the user information management system acquires the second user data corresponding to the target user identification from the application platform to which the target user identification belongs through the open interface provided by the first application platform.

In one embodiment, the feedback user profile is obtained by combining the acquired first user profile and second user profile by the user information management system.

In one embodiment, if the application platform identifies the application platform to which the target user belongs, the user information management system acquiring the second user profile includes the following steps: and the user information management system sends a second user data acquisition request to the first application platform, wherein the second user data acquisition request is used for indicating the first application platform to confirm whether the second user data acquisition permission of the target user identification exists in the set corresponding to the local user identification. When the first application platform confirms the acquisition permission of the second user data which is corresponding to the local user identification and collectively has the target user identification, the user information management system can acquire the second user data corresponding to the target user identification from the application platform to which the target user identification belongs through the first application platform.

In one embodiment, the application platform identifies the application platform to which the target user belongs, and the application platform to which the target user belongs may be the first application platform or the second application platform. The step of acquiring the second user profile by the user information management system comprises the following steps: and when the application platform to which the target user identifier belongs is the first application platform, acquiring second user data corresponding to the target user identifier from the first application platform through an open interface provided by the first application platform. And when the application platform to which the target user identification belongs is the second application platform, the user information management system acquires second user data corresponding to the target user identification from the second application platform by using the intercommunication platform through the open interface provided by the first application platform.

In one embodiment, the second application may be an instant messaging tool used by the individual user, and the second application platform is an individual user application platform corresponding to the instant messaging tool used by the individual user.

In one embodiment, the instant messaging tool used by the first application as the collective user, the instant messaging tool used by the first application platform as the collective user application platform, the instant messaging tool used by the second application as the individual user, and the individual user application platform as the second application platform are exemplified. And the local terminal receives the user data fed back by the user information management system in response to the query request. The feedback user data is obtained by combining the acquired first user data and the second user data by the user information management system.

The user information management system for acquiring the first user data comprises the following steps: the user information management system determines a target user identifier from user identifiers stored in the user information management system, and acquires first user data stored corresponding to the target user identifier. The user information management system acquiring the second user data comprises the following steps: and when the application platform to which the target user identification belongs is the collective user application platform, acquiring second user data corresponding to the target user identification from the collective user application platform through an open interface provided by the collective user application platform. And when the application platform to which the target user identifier belongs is the individual user application platform, acquiring second user data corresponding to the target user identifier from the individual user application platform to which the target user identifier belongs by using the intercommunication platform through an open interface provided by the collective user application platform.

S308, displaying the received user data.

Specifically, when the local terminal receives the user data fed back by the user information management system in response to the query request, the page jump instruction is acquired. And jumping to a user data page of the target user identifier according to the page jump instruction, and displaying the received user data on the user data page of the target user identifier.

In one embodiment, the local terminal may be provided with a plurality of display modes, and the local terminal displays the received user profile on the user profile page of the target user identifier according to a target display mode selected from the plurality of display modes. The display mode may be, for example, a display mode in which the first user data is displayed above and the second user data is displayed below, or a display mode in which the first user data is displayed below and the second user data is displayed above, or a display mode in which the first user data and the second user data are interleaved, or a display mode in which part of the data in the user data is highlighted, or the like.

In one embodiment, the manner in which portions of the user profile are highlighted is illustrated. For example, the user data includes the favorite product type of the target user corresponding to the target user identifier, the price and the character characteristics of the historical purchased products, and the nickname, age, sex and other data of the target user corresponding to the target user identifier on the application platform, and the nickname, the favorite product type and the character characteristics in the user data can be set for highlighting, so that the important data in the user data can be displayed more clearly.

According to the user data processing method, the user data of the target user can be directly inquired from the user information management system by utilizing the user data inquiry inlet and the target user identification without switching among a plurality of systems and a plurality of accounts, and the inquired user data is obtained according to the user data from the user information management system and the application platform respectively, so that the user data can be inquired efficiently and comprehensively.

In one embodiment, the user profile query entry can be triggered after logging into the first application with the local user identification; the application platform corresponds to one of the first application and the second application; the second application is different from the first application.

The local user identifier refers to a user identifier used for logging in the first application installed in the local terminal, for example, the local user identifier may specifically be a user ID (identification), and the user ID may include at least one of characters such as numbers, symbols, and letters.

Specifically, the local terminal presents a user profile query entry for querying a user profile from the user information management system in a first application installed in the local terminal. When the local terminal logs in the first application installed on the local terminal by using the local user identification, the user data query entrance can be triggered. The application platform is an application platform to which the target user identifier belongs, and the application platform to which the target user identifier belongs corresponds to one of the first application and the second application; the second application is different from the first application.

In one embodiment, after the local terminal logs in the first application with the local user identifier, the user identifiers of a plurality of users may be displayed on a user list page of the first application. And the local terminal triggers a selection instruction according to the selection operation detected from the user list page. And the local terminal jumps to a basic data page corresponding to the target user identification from a target user identification in the plurality of user identifications displayed in the user list page according to the selected instruction. The profile page exhibits a user profile query entry for querying a user profile from a user information management system, which may be triggered at the profile page.

In one embodiment, the first application corresponds to a first application platform and the second application corresponds to a second application platform. And when the application platform to which the target user identification belongs corresponds to the first application, the application platform to which the target user identification belongs is the first application platform. And when the application platform to which the target user identification belongs corresponds to the second application, the application platform to which the target user identification belongs is the second application platform.

In one embodiment, the first application may be an instant messaging tool used by the collective user, and the first application platform corresponding to the first application is a collective user application platform corresponding to the instant messaging tool used by the collective user. The second application may be an instant messaging tool used by an individual user, and the second application platform corresponding to the second application is an individual user application platform corresponding to the instant messaging tool used by the individual user.

And when the application platform to which the target user identification belongs corresponds to the instant messaging tool used by the collective user, the application platform to which the target user identification belongs is the collective user application platform. And when the application platform to which the target user identification belongs corresponds to the instant messaging tool used by the individual user, the application platform to which the target user identification belongs is the individual user application platform.

In the above embodiment, the application platform may correspond to one of the first application and the second application, and the second application is different from the first application, that is, the second user profile in the fed-back user profile is from the first application platform corresponding to the first application or the second application platform corresponding to the second application, and since the second application is different from the first application, the second application platform is also different from the first application platform. When it is determined that the application platform to which the target user identifier belongs corresponds to the first application, the second user profile of the fed-back user profiles may be acquired from the first application platform. When the application platform to which the target user identifier belongs is determined to correspond to the second application, the second user profile in the fed-back user profiles can still be obtained from the second application platform.

In one embodiment, displaying the received user profile includes: entering a sub-application running in an environment provided by a first application; displaying a user profile page in the sub-application; and displaying the received user data on a user data page.

The sub-application refers to an application running in an environment provided by the parent application, the first application is used as the parent application in the embodiment, and the sub-application runs in the environment provided by the first application. For example, the sub-application may be an application that can be used without downloading. The application that can be used without downloading refers to a sub-application that can generate a sub-application page through common page configuration information and display page content acquired from a specified path to the sub-application page.

Specifically, the local terminal enters a sub-application running in an environment provided by the first application, acquires user profile page configuration information of a user profile page of the sub-application from the first application platform, and displays the user profile page in the sub-application according to the user profile page configuration information. And displaying the user data fed back by the user information management system in a user data page.

In one embodiment, the sub-application running in the environment provided by the first application is a sub-application associated with a user information management system. The user profile page configuration information may be a user profile page path.

In the embodiment, the user data page of the sub-application running in the environment provided by the first application is used for displaying the received user data fed back by the user information management system, switching among a plurality of systems and a plurality of accounts is not needed, and the user data fed back by the user information management system is obtained according to the user data respectively from the user information management system and the application platform, so that the user data can be efficiently and comprehensively inquired.

In one embodiment, displaying the user profile page in the sub-application includes: inquiring a sub application page identifier corresponding to the user information management system configuration; when the sub-application page identification is inquired, entering a user data page corresponding to the sub-application page identification in the sub-application; and when the page identifier of the sub-application is not inquired, entering a default page in the sub-application, and entering a user data page according to a user instruction when the user instruction is received.

The sub-application page identifier refers to a page identifier of a page belonging to the sub-application, and the sub-application page identifier in this embodiment is a page identifier of a user profile page of the sub-application. The default page refers to a default page belonging to the sub-application, for example, the default page may be specifically a top page of the sub-application. The user instruction refers to an instruction triggered by a user through a preset operation, for example, the user instruction may be an instruction triggered by the user through a touch operation.

Specifically, the terminal corresponding to the administrator user identifier may be configured with the sub-application page identifier of the user profile page corresponding to the user information management system in advance. The administrator user identification is a user identification used in the first application by an administrator of a group to which the user information management system belongs. The local terminal may query the first application platform for a sub-application page identification corresponding to the user information management system configuration. When the local terminal inquires the sub application page identification corresponding to the user information management system configuration from the first application platform, the user data page configuration information corresponding to the sub application page identification is obtained from the first application platform. And the local terminal enters a user data page corresponding to the sub-application page identifier in the sub-application according to the acquired user data page configuration information.

When the local terminal does not inquire the sub-application page identification corresponding to the configuration of the user information management system from the first application platform, the fact that the administrator of the user information management system does not configure the sub-application page identification of the sub-application page corresponding to the configuration of the user information management system in the first application platform is indicated. The local terminal acquires default page configuration information corresponding to the default page from the first application platform. And the local terminal enters the default page of the sub-application according to the acquired default page configuration information. The default page can be provided with a user data page entry for entering the user data page, the local terminal triggers the user data page entry for entering the user data page in the default page according to a user instruction detected in the default page, and the user data page entry is used for entering the user data page.

In one embodiment, the method for configuring the sub-application page identifier of the user profile page by the user information management system includes the following steps:

and the terminal corresponding to the administrator user identification acquires a sub-application page configuration request, wherein the sub-application page configuration request carries user data page configuration information of the sub-application associated with the user information management system. The user profile page configuration information includes a sub-application page identification of the user profile page. And the terminal corresponding to the administrator user identification sends a sub-application page configuration request to the first application platform. And the first application platform responds to the sub-application page configuration request, writes the user data page configuration information into a sub-application page configuration file of the user information management system, and completes the configuration of the sub-application page identifier.

In one embodiment, the sub-application associated with the user information management system is associated with the user information management system, and specifically includes the following steps:

and the terminal corresponding to the administrator user identification acquires a sub-application association request, wherein the sub-application association request carries the sub-application configuration information. And the terminal corresponding to the administrator user identification sends a sub-application association request to the first application platform. And the first application platform responds to the sub-application association request, writes the sub-application configuration information into a sub-application configuration file of the user information management system, and completes the association of the sub-application and the user information management system.

In the embodiment, the user data page can be directly accessed through the sub-application page identifier corresponding to the user information management system configuration, the local terminal does not inquire the sub-application page identifier corresponding to the user information management system configuration, the user data page can also be accessed through the default page, the user data corresponding to the target user identifier is checked on the user data page, switching among a plurality of systems and a plurality of accounts is not needed, and the user data fed back by the user information management system is obtained according to the user data respectively from the user information management system and the application platform, so that the user data can be efficiently and comprehensively inquired.

In one embodiment, displaying the received user profile includes: acquiring a page type configured by a corresponding user information management system; entering a user data page matched with the page type; and displaying the received user data on a user data page.

The page type refers to a type of a page corresponding to the user information management system configuration, and for example, the page type may specifically be a sub-application page type or a web page type.

Specifically, the first application that the local terminal logs in with the local user identifier may be associated with the user information management system through a sub-application or a web page running in an environment provided by the first application. When the local terminal determines that the first application is associated with the user information management system through the sub-application, the page type which is acquired by the local terminal and corresponds to the user information management system configuration is the sub-application page type corresponding to the sub-application. And the local terminal enters a user data page matched with the type of the sub-application page and displays the received user data on the user data page matched with the type of the sub-application page.

When the local terminal determines that the first application is associated with the user information management system through the webpage, the page type acquired by the local terminal and corresponding to the user information management system configuration is the webpage type corresponding to the webpage. And the local terminal enters a user data page matched with the webpage type and displays the received user data on the user data page matched with the webpage type. Further, the web page associated with the user information management system may specifically be an H5(HTML5) web page, and H5 is an advanced web page technology capable of supporting multimedia on the mobile device.

In the embodiment, according to the page type configured by the corresponding user information management system, the user data page matched with the page type is entered from the first application, the received user data is displayed on the user data page, switching among a plurality of systems and a plurality of accounts is not needed, and the user data fed back by the user information management system is obtained according to the user data respectively from the user information management system and the application platform, so that the user data can be efficiently and comprehensively inquired.

In one embodiment, the user profile processing method further comprises: acquiring a user data modification instruction; modifying the displayed user data belonging to the user information management system according to the user data modification instruction; and synchronizing the modified user profile to the user information management system corresponding to the target user identification.

Specifically, the local user account logged in the first application may have a modification right for modifying the user profile displayed on the local terminal, where the modification right is in a range of modifying the displayed first user profile belonging to the user information management system. The local terminal can acquire a user modification instruction according to the detected touch operation, and modify a first user profile from the user information management system in the displayed user profiles according to the user profile modification instruction. And synchronously updating the modified user profile to the user information management system corresponding to the target user identification.

In one embodiment, modifying the displayed first user profile belonging to the user information management system according to the user profile modification instruction comprises: determining a modification mode corresponding to a user modification instruction; and modifying the first user profile from the user information management system in the displayed user profiles according to the determined modification mode.

In one embodiment, the modification mode may be a preset modification mode, and the preset modification mode may be determined according to the content of the first user profile from the user information management system in the displayed user profile. For example, the first user profile from the user information management system includes the favorite product type of the corresponding target user, the price of the historical purchased product, the character feature, and the like, and the modification manner may include changing the favorite product type of the user and increasing the character feature of the user. And if the modification mode corresponding to the user modification instruction is to increase the personality characteristics of the user, the local terminal increases the personality characteristics of the user according to the modification mode. The added personality traits of the user may be determined based on personality traits selected from a list of personalities displayed by the local terminal, or may be determined based on entered text detected by the local terminal.

In the above embodiment, the user profile corresponding to the target user identifier may be directly modified in the first application, and the modified user profile is synchronously updated to the user information management system corresponding to the target user identifier, so that the local user corresponding to the local user identifier may better manage the user profile corresponding to the target user identifier, and at the same time, other local users may query the updated user profile, thereby implementing efficient and comprehensive management of the user profile.

In one embodiment, the user profile query entry can be triggered after logging in the first application with the local user identifier belonging to the group and when the local user identifier and the target user identifier have a social relationship; the user information management system corresponds to a group.

The social relationship refers to a relationship between people that can communicate information with each other by using a certain communication method or communication tool. For example, the social relationship may be a friend relationship established between people by using a social account of the instant messaging tool.

Specifically, when the local terminal detects that the first application is logged in with the local user identifier belonging to the group, the local terminal can determine the group identifier of the group to which the local user identifier belongs. The local terminal can acquire the association configuration information associated with the first application and the user information management system according to the collective identification. When the local terminal detects that the local user identifier and the target user identifier establish a social relationship, the local terminal can display the target user identifier in a social relationship list of a first application logged in by the local user identifier. And when the local terminal detects that the target user identification in the social relationship list is triggered, displaying a basic data page corresponding to the target user identification.

In one embodiment, the local terminal obtaining association configuration information of the first application associated with the user information management system according to the collective identification includes: and sending a correlation confirmation request carrying the collective identification to a first application platform corresponding to a first application logged in by a local user account belonging to the collective. The association confirmation request is used for instructing the first application platform to confirm whether the collective represented by the collective identification is associated with the user information management system in the first application.

When the first application platform confirms that the group represented by the group identification is associated with the user information management system in the first application, the first application platform feeds back associated configuration information for associating the first application with the user information management system to the local terminal. And the local terminal receives the association configuration information fed back by the first application platform in response to the association confirmation request.

In one embodiment, the step of establishing a social relationship between the local user identifier and the target user identifier specifically includes the following steps: the local terminal sends a social relationship establishment instruction carrying a local user identifier and a target user identifier to a first application platform corresponding to the first application, the social relationship establishment request is used for indicating the first application platform to send the social relationship establishment request carrying the local user identifier to the terminal corresponding to the target user identifier, and response information fed back by the terminal corresponding to the target user identifier in response to the social relationship establishment request is returned to the local terminal. The response information pointer is information to be replied to by the social relationship establishment request, and for example, the response information may be "agreement" or "rejection" or an interim session message. And the local terminal receives response information fed back by the first application platform in response to the social relationship establishment instruction. And when the content represented by the response information agrees to establish the social relationship, the local user identification and the target user identification establish the social relationship.

In one embodiment, the steps of sending, by the first application platform, a social relationship establishment request carrying a local user identifier to a terminal corresponding to the target user identifier, and returning response information fed back by the terminal corresponding to the target user identifier in response to the social relationship establishment request to the local terminal specifically include: the first application platform determines the application platform to which the target user identifier belongs. When the application platform to which the target user identifier belongs is the first application platform, the first application platform sends a social relationship establishment request carrying the local user identifier to the terminal corresponding to the target user identifier, and response information fed back by the terminal corresponding to the target user identifier in response to the social relationship establishment request is returned to the local terminal.

When the application platform to which the target user identifier belongs is a second application platform, the first application platform is communicated with the second application platform corresponding to the target user identifier through the intercommunication platform, and the first application platform sends a social relationship establishment request carrying the local user identifier to the terminal corresponding to the target user identifier by using the second application platform communicated with the first application platform. And the first application platform acquires response information fed back by the terminal corresponding to the target user identification in response to the social relationship establishment request from the second application platform through the intercommunication platform, and returns the response information fed back by the terminal corresponding to the target user identification in response to the social relationship establishment request to the local terminal.

In the above embodiment, the user profile query entry must be triggered after logging in the first application by using the local user identifier belonging to the group and when the local user identifier and the target user identifier have a social relationship, so that the security of obtaining the user profile corresponding to the target user identifier is improved.

As shown in fig. 4, in one embodiment, the user profile processing method further includes the steps of:

s402, receiving a shared first sub application page message; the first sub-application page message specifies a first sub-application page of the first target sub-application.

The first sub-application page message refers to a message shared by sub-applications running in an environment provided by the first application. The first target sub-application refers to a sub-application running in an environment provided by the first application, which is utilized for sharing the first sub-application page message. The first sub-application page refers to a page belonging to the first target sub-application.

Specifically, the local terminal receives a first sub-application page message shared to a local user account through a first application. The first sub-application page message specifies a first sub-application page of a first target sub-application, the first sub-application page configured by an application platform to which the sharer user identifier belongs corresponding to a first target sub-application associated with a user information management system of a group to which the sharer user identifier belongs. The sharing party user identifier refers to a user identifier used by a sharing party sending sharing data on an application platform to which the sharing party belongs.

In an embodiment, when the local terminal receives the shared first sub-application page message, the local terminal may display the first sub-application page message in a dialog box in the first application, where the dialog box includes the local user identifier and the sharer user identifier.

In one embodiment, the group to which the sharer user identifier belongs is different from the group to which the local user identifier of the local terminal belongs. The application platform to which the sharing party user identifier belongs may be the same as the application platform to which the local user identifier belongs, and the application platform to which the sharing party user identifier belongs may be the first application platform.

In one embodiment, the application platform to which the sharer user identifier belongs is the first application platform. The method specifically comprises the following steps that an application platform to which a sharer user identifier belongs configures a first sub-application page corresponding to a group to which the sharer user identifier belongs:

the terminal corresponding to the administrator of the group to which the sharing party user identification belongs can log in the first application through the first administrator user identification. The first administrator user identifier refers to a user identifier used in the first application by an administrator of a group to which the sharing party user identifier belongs. When the terminal corresponding to the first administrator user identifier detects that the user identifier for logging in the first application is the first administrator user identifier, the terminal corresponding to the first administrator user identifier can enter the sub-application page configuration page through the sub-application page configuration entry belonging to the first administrator user identifier in the first application. The terminal corresponding to the first administrator user identification selects a first sub-application page identification of the first sub-application page in a sub-application page configuration page, and sends a first sub-application page configuration request carrying the selected first sub-application page identification to the first application platform.

The first sub-application page configuration request is used for instructing the first application platform to write first sub-application page configuration data corresponding to the first sub-application page identifier into a sub-application page configuration file of the first target sub-application, and configuration of the first sub-application page is completed. The first target sub-application is associated with a user information management system of a group to which the sharing party user identification belongs, the group to which the sharing party user identification belongs is the same as the group to which the first administrator user identification belongs, and the user information management system of the group to which the sharing party user identification belongs is different from the user information management system of the group to which the local user identification of the local terminal logs in.

S404, displaying a first sub-application page of the first target sub-application through the first target sub-application running in the environment provided by the first application.

Specifically, the local terminal displays the received first sub-application page message in a dialog box which is in the first application and includes the local user identifier and the sharer user identifier at the same time. The sharing party user identification may be multiple. When the local terminal detects that the first sub-application page message is triggered in a dialog box comprising the local user identifier and the sharing party user identifier, a first sub-application page of the first target sub-application is displayed through a first target sub-application corresponding to the first sub-application page message.

S406, shared data which corresponds to the first sub-application page of the first target sub-application and is associated with the local user identifier is requested from the user information management system.

The shared data is data of a local user identifier which is required to be shared to the local terminal by the user account of the sharing party. For example, the shared data may be questionnaires, product introduction information, historical shopping information, and the like.

Specifically, the local terminal sends a first shared data acquisition request carrying a first sub-application page identifier of the first sub-application page and the local user identifier to the user information management system of the group to which the sharing party user identifier belongs. The first shared data acquisition request is used for indicating a user information management system of a group to which the user identifier of the sharing party belongs to determine shared data which corresponds to a first sub-application page of the first target sub-application and is associated with the local user identifier. And the local terminal receives the shared data fed back by the user information management system of the group to which the user identifier of the sharing party belongs in response to the first shared data acquisition request.

For example, the shared data corresponding to the first sub-application page of the first target sub-application is product introduction information, and the product introduction information includes product introduction information a, product introduction information B, and product introduction information C. The user information management system of the group to which the sharing party user identifier belongs can determine the priority of the product introduction information of each product according to the degree of the local user identifier to the favorite product type. For example, the local user identification ranks the preference degrees for the type of a product, the type of B product, and the type of C product from high to low as: the type of product B, the type of product C and the type of product A. The contents in the product introduction information determined by the user information management system of the group to which the sharing party user identifier belongs are arranged in the following order: product introduction information B, product introduction information C and product introduction information A. The degree of the local user identifier to the favorite product type can be obtained according to historical monitoring data stored corresponding to the local user identifier by a user information management system of a group to which the sharing party user identifier belongs. The historical monitoring data stored corresponding to the local user identifier may be stored in a user information management system of a group to which the sharing party user identifier belongs.

For example, the shared data corresponding to the first sub-application page of the first target sub-application is historical shopping information, and the historical shopping information refers to a product list of products purchased at a historical time. The user information management system of the group to which the sharing party user identifier belongs can obtain historical shopping information associated with the local user identifier according to the products purchased by the local user identifier in the historical time period. For example, if the local user identifier is a product a and a product B purchased in a historical time period, the historical shopping information determined by the user information management system of the group to which the sharing user identifier belongs includes the product information of the product a and the product information of the product B. For example, if the products purchased by the local user identifier in the historical time period are the product C and the product D, the historical shopping information determined by the user information management system of the group to which the sharing user identifier belongs includes the product information of the product C and the product information of the product D. For products purchased by the local user identifier in a historical time period, the user information management system of the group to which the sharing party user identifier belongs can obtain the products according to historical monitoring data stored corresponding to the local user identifier.

S408, displaying the shared data on a first sub-application page of the first target sub-application.

Specifically, the local terminal displays the shared data fed back by the user information management system in response to the shared data acquisition request in a first sub-application page displayed by a first target sub-application running in an environment provided by the first application.

In one embodiment, the shared data displayed by the first sub-application page, such as the first target sub-application, is editable shared data, such as a questionnaire. The local terminal can acquire a shared data editing instruction and edit the displayed shared data according to the shared data editing instruction; and synchronizing the edited shared data to a user information management system of a group to which the user identification of the sharing party belongs corresponding to the local user identification.

In the embodiment, the shared first sub-application page message can be received through the first target sub-application running in the first application, the shared data can be acquired and displayed from the user information management system, and the data can be efficiently shared while efficiently and comprehensively inquiring user data. In addition, the sharing party only needs to share the same first sub-application page message to different users, and after receiving the same first sub-application page message, the different users all display sharing data related to the sharing party, so that the safety of user information is guaranteed, and high efficiency and convenience of data sharing can be guaranteed.

As shown in fig. 5, in one embodiment, the user profile processing method further includes:

and S502, acquiring a sharing object identifier.

The sharing object identifier refers to a user identifier used by the sharing object on an application platform to which the sharing object belongs. The application platform to which the sharing object belongs is the first application platform or the second application platform.

Specifically, the local terminal may be provided with a sub-application page sharing entry in a dialog box that includes the local user identifier and the sharing object identifier in the first application. The sharing user identifier obtained by the local terminal may be a sharing object identifier included in the dialog box. The number of the shared object identifications can be multiple.

In an embodiment, the local terminal may also display a social relationship list corresponding to the local user identifier in the first application, and the local terminal may obtain the selected sharing object identifier from the social relationship list according to a selection operation detected from the social relationship list.

S504, obtaining a second sub application page message to be shared; the second sub-application page message specifies a second sub-application page of a second target sub-application.

The second sub-application page message refers to a message shared by sub-applications running in the environment provided by the first application. The second target sub-application refers to a sub-application running in the environment provided by the first application, which is utilized for sharing the second sub-application page message. The second sub-application page refers to a page belonging to a second target sub-application. It will be appreciated that the "second" of the second sub-application page message is to be distinguished from the first sub-application page message. The "second" of the second target sub-application is to distinguish from the first target sub-application. The "second" in the second sub application page is to distinguish from the first sub application page.

Specifically, when the local terminal detects that a sub-application page sharing entry in the first application is triggered, the local terminal displays a sub-application page sharing list in the first application. And the local terminal selects a second sub-application page identifier of a second target sub-application from the sub-application page sharing list. And the local terminal acquires a second sub application page message from the first application platform according to the selected second sub application page identifier, wherein the acquired second sub application page message designates a second sub application page of a second target sub application. The second sub-application page is configured by the first application platform corresponding to a second target sub-application associated with the user information management system of the collective user identification.

In one embodiment, the first application platform configures a second sub-application page corresponding to a second sub-application associated with the user information management system of the group to which the local user identifier belongs, and specifically includes the following steps:

the administrator of the group to which the local user identity belongs can log in the first application of the local terminal with the second administrator user identity. The second administrator user identity refers to a user identity used in the first application by an administrator of the group to which the local user identity belongs. When the local terminal detects that the user identifier of the first application is the second administrator user identifier, the local terminal can enter the sub-application page configuration page through the sub-application page configuration entry belonging to the second administrator user identifier in the first application. And the local terminal selects a second sub-application page identifier of a second sub-application page in the sub-application page configuration page, and sends a second sub-application page configuration request carrying the selected second sub-application page identifier to the first application platform.

The second sub-application page configuration request is used for instructing the first application platform to write second sub-application page configuration data corresponding to the second sub-application page identifier into a sub-application page configuration file of the second target sub-application, and configuration of the second sub-application page is completed. The second target sub-application is associated with a user information management system of a group to which the local user identifier belongs, and the group to which the local user identifier belongs is the same as the group to which the second administrator user identifier belongs.

S506, sharing the second sub application page message to a terminal corresponding to the sharing object identifier; the second sub-application page message is used for instructing the terminal to acquire shared data corresponding to a second sub-application page of a second target sub-application and associated with the user identity corresponding to the terminal, and the shared data is displayed through the second target sub-application running in an environment provided by the second application.

The user identity corresponding to the terminal refers to the user identity of the shared object identifier.

Specifically, the application platform to which the shared object identifier belongs is the second application platform. And the terminal corresponding to the sharing object identifier is provided with a second application. The second application is different from the first application, and the second application platform is different from the first application platform. The local terminal can send the page message sharing instruction carrying the second sub-application page message and the sharing object identifier to the first application platform through the first application logged in by the local user account. The page message sharing instruction is used for indicating the first application platform to request the second application platform to send the second sub-application page message to the terminal corresponding to the sharing object identifier. The second sub-application page message is used for instructing the terminal corresponding to the shared object identifier to send a second shared data acquisition request carrying the second sub-application page identifier of the second sub-application page and the shared object identifier to the user information management system of the local user identifier belonging group.

The second shared data acquisition request is used for indicating the user information management system of the group to which the local user identifier belongs to determine shared data which corresponds to a second sub-application page of the second target sub-application and is associated with the shared object identifier. And the terminal corresponding to the sharing object identifier receives the sharing data fed back by the user information management system of the group to which the local user identifier belongs in response to the second sharing data acquisition request, and displays the sharing data through a second target sub-application running in the environment provided by the second application.

For example, the shared data corresponding to the second sub-application page of the second target sub-application is product introduction information, and the product introduction information includes product introduction information a, product introduction information B, and product introduction information C. The user information management system of the group to which the local user identifier belongs may determine the priority for the product introduction information of each product according to the degree of the sharing object identifier to the favorite product type.

For example, the sharing object identifiers rank the preference degrees of the type of the product A, the type of the product B and the type of the product C from high to low as: the type of product B, the type of product C and the type of product A. The content in the product introduction information determined by the user information management system of the local user identifier belongs to the collective user identifier is arranged according to the following sequence: product introduction information B, product introduction information C and product introduction information A. The degree of the sharing object identifier to the favorite product type can be obtained according to historical monitoring data stored corresponding to the sharing object identifier by the user information management system of the group to which the local user identifier belongs. The historical monitoring data stored corresponding to the shared object identifier can be stored in the user information management system of the local user identifier belonging to the group.

For example, the shared data corresponding to the second sub-application page of the second target sub-application is historical shopping information, and the historical shopping information refers to a product list of products purchased at a historical time. The user information management system of the group to which the local user identifier belongs can obtain historical shopping information associated with the shared object identifier according to the products purchased by the shared object identifier in the historical time period.

For example, if the shared object identifier identifies that the products purchased in the historical time period are the product a and the product B, the historical shopping information determined by the user information management system of the local user identifier belonging to the group includes the product information of the product a and the product information of the product B. For example, if the shared object identifier indicates that the products purchased in the historical time period are the product C and the product D, the historical shopping information determined by the user information management system of the local user identifier belongs to the group includes the product information of the product C and the product information of the product D. For products purchased by the sharing object identifier in a historical time period, the user information management system of the group to which the local user identifier belongs can obtain the products according to historical monitoring data stored corresponding to the sharing object identifier.

In one embodiment, the first application is an instant messaging tool used by a collective user, the first application platform is a collective user application platform corresponding to the instant messaging tool used by the collective user, the second application is an instant messaging tool used by an individual user, and the second application platform is an individual user application platform corresponding to the instant messaging tool used by the individual user.

In the embodiment, the page message of the first sub-application can be shared to the terminal corresponding to the sharing object identifier through the second target sub-application running in the first application, and then the terminal corresponding to the sharing object identifier can acquire and display the sharing data from the user information management system, so that the user data can be efficiently and comprehensively inquired, and meanwhile, the data can be efficiently shared. Moreover, users corresponding to the local user identifiers only need to share the same second sub-application page messages with different sharing object identifiers, and after receiving the same second sub-application page messages, users corresponding to different sharing object identifiers all display sharing data related to the users, so that the safety of user information is guaranteed, and high efficiency and convenience in data sharing can be guaranteed.

In one embodiment, the obtaining of the second sub-application page message to be shared includes: acquiring a sub-application page sharing list with sharing authority relative to a local user identifier; selecting a sub-application page of a second target sub-application from the sub-application page sharing list according to a user selection instruction; a second sub-application page message is generated specifying a second sub-application page of a second target sub-application.

The sub-application page sharing list refers to a list comprising one or more application page identifiers.

Specifically, the administrator of the user information management system of the group to which the local user identifier belongs may log in the first application with the second administrator user identifier in advance. The first application is provided with a plurality of target sub-applications associated with the user information management system. An administrator of the user information management system of the local user identification belonging to the collective may set the visibility range of each target sub-application at the first application. The visible range comprises one or more user accounts, and the user accounts in the visible range can share the sub-application page of the corresponding target sub-application to the terminal corresponding to the sharing object identifier at the terminal for logging in the first application. For example, the visible range of the second target sub-application includes a plurality of local user accounts, such as a local user account a, a local user account B, a local user account C, and the like, and the local user account a, the local user account B, and the local user account C can share a second sub-application page of the second target sub-application to a terminal corresponding to the shared object identifier at a terminal logging in the first application.

The local terminal can determine the sharing authority of the local user identifier according to the visible range of each target sub-application, and obtains a sub-application page sharing list corresponding to the local user identifier according to the sharing authority of the local user identifier. The sub-application page sharing list comprises sub-application page identifications of sub-applications with sharing rights of local user identifications. For example, the local user identifier belongs to the visible range of the target sub application a, the visible range of the target sub application B, and the visible range of the target sub application C, and the sharing authority of the local user identifier includes the sub application page a of the target sub application a, the sub application page B of the target sub application B, and the sub application page B of the target sub application C. The sub-application page sharing list corresponding to the local user identifier comprises an application page identifier A, an application page identifier B and an application page identifier C.

And the local terminal selects a second sub-application page identifier of a second target sub-application from the sub-application page sharing list according to the detected user selection instruction, and determines a second sub-application page of the second target sub-application according to the second sub-application page identifier of the second target sub-application. And the local terminal generates a second sub-application page message for specifying a second sub-application page of a second target sub-application according to the determined second sub-application page.

In the embodiment, the local terminal logging in the first application by using the local user account can only select the sub-application page to be shared to the terminal corresponding to the sharing object identifier from the sub-application page sharing list of the local user identifier with the sharing authority, so that the security is high.

In an embodiment, as shown in fig. 6, the user profile processing method may specifically include the following steps:

s602, the local terminal determines a target user identifier selected from the user list of the first application, and displays a basic data page corresponding to the target user identifier.

S604, the local terminal sends a correlation confirmation request to the first application platform.

S606, the first application platform confirms whether the set corresponding to the local user identification of the current login is associated with the user information management system in the first application. If yes, the process proceeds to S608.

S608, the first application platform feeds back the association configuration information of the first application and the association of the user information management system to the local terminal.

S610, the local terminal displays a user data query entrance for querying the user data from the user information management system on the basic data page corresponding to the target user identification according to the associated configuration information.

And S612, when the local terminal monitors that the user data query entrance is triggered, acquiring a target user identifier of a target user.

S614, the local terminal sends the inquiry request carrying the target user identification to the user information management system associated with the first application.

S616, the user information management system determines the target user identification from the user identifications stored in the user information management system, and acquires the first user data stored corresponding to the target user identification.

S618, the user information management system sends the query request to the first application platform through the open interface provided by the first application platform.

S620, the first application platform confirms whether the collective user to which the user information management system belongs has the acquisition authority of acquiring the second user data corresponding to the target user identification. If yes, the process proceeds to S622.

S622, the first application platform determines the application platform to which the target user identifier belongs. And when the application platform to which the target user identifier belongs is the second application platform, the process goes to S624.

S624, the first application platform sends the query request to the second application platform through the intercommunication platform.

S626, the second application platform feeds back the second user data corresponding to the target user identification to the first application platform through the intercommunication platform.

And S628, the first application platform returns the second user data corresponding to the target user identifier to the user information and feeds the second user data back to the user information management system.

S630, the user information management system combines the first user data and the second user data to obtain the user data.

S632, the user information management system feeds back the obtained user data to the local terminal.

S634, the local terminal displays the user data of the user feedback information management system on the user data page of the target user identification.

In one embodiment, the user profile processing method is further described. When the terminal corresponding to the administrator user identifier detects that the "association guide" in the sub-application configuration page shown in fig. 7 is selected, the association guide page shown in fig. 8 is displayed. The terminal corresponding to the administrator user identifier may add the sub-application that needs to be associated with the user information management system through the "associated sub-application" in the sub-application configuration page as shown in fig. 7.

The terminal corresponding to the administrator user identifier may also display a user management page as shown in fig. 9. When the terminal corresponding to the administrator user identifier detects that the "edit" in the user management page is triggered, the terminal jumps to the user profile query entry configuration page shown in fig. 10.

The terminal corresponding to the administrator user id may input the name of the user profile query entry in the "page name" of the user profile query entry configuration page shown in fig. 10, for example, if the "user information management system" is input, the "user information management system" may query the name of the entry for the user profile. The terminal corresponding to the administrator user id may select "sub-application" in "page type" in the user profile query entry configuration page as shown in fig. 10, and a second target sub-application associated with the user information management system is required in "sub-application option". Of course, the terminal corresponding to the administrator user identifier may also select a "web page" in the "page type" in the user profile query entry configuration page, and select a target web page that needs to be associated with the user information management system in the "web page option".

The terminal corresponding to the administrator user id may input the sub-application page id corresponding to the user profile page of the second target sub-application in the "page path" of the user profile query entry configuration page as shown in fig. 10, so as to determine the user profile page path of the user profile page according to the sub-application page id. The administrator user identification and the local user identification belong to the same group.

The local terminal logs in the first application through the local user identifier, displays a target user identifier with a social relationship with the local user identifier in a social relationship list of the first application, and jumps to a basic data page corresponding to the target user identifier when the local terminal detects that the target user identifier in the social relationship list is triggered. And the local terminal sends a correlation confirmation request to a first application platform corresponding to the first application. Since the terminal corresponding to the administrator user identifier has previously configured the sub-application associated with the user information management system as the second target sub-application in the user profile query entry configuration page as shown in fig. 10, the first application platform responds to the association confirmation request to confirm that the collective user information management system corresponding to the local user identifier and the first application are associated with the second target sub-application, and then transmits the sub-application configuration information of the second target sub-application to the local terminal.

The local terminal displays a user profile query entry "user information management system" for querying user profiles from the user information management system on a basic profile page corresponding to the target user identifier according to the sub-application configuration information fed back by the first application platform, as shown in fig. 11. When detecting that the user information management system is triggered as shown in fig. 11, the local terminal acquires a target user identifier to be queried, sends a query request carrying the target user identifier to the user information management system, and receives user data fed back by the user information management system in response to the query request; the feedback user data is obtained according to the user data which are respectively from the user information management system and the application platform and respectively correspond to the target user identification.

Since the terminal corresponding to the administrator user id is configured in advance in the user profile query entry configuration page shown in fig. 10, the sub-application page id of the user profile page of the sub-application corresponding to the user profile query entry is configured in the user information management system. Therefore, the local terminal can enter the user data page corresponding to the sub-application page identifier in the sub-application associated with the user information management system through the user data page path determined according to the sub-application page identifier, and the user data fed back by the user information management system is displayed on the user data page.

As shown in fig. 4, in one embodiment, a shared message handling method is provided. The present embodiment is mainly illustrated by applying the method to the local terminal 110 in fig. 1. Referring to fig. 4, the method for processing a shared message specifically includes the following steps:

As shown in fig. 5, in an embodiment, the user profile processing method further includes the following steps of sharing the second sub application page message to a terminal corresponding to the shared object identifier:

and S502, acquiring a sharing object identifier.

In one embodiment, as shown in fig. 12, the shared message processing method may further include the following steps:

and S1202, the local terminal opens a dialog box of any one of the first applications, wherein the dialog box comprises a local user identifier and a sharing object identifier, and a sub-application page sharing entry is displayed in the dialog box.

And S1204, when the local terminal detects that the sub-application page sharing entry in the dialog box is triggered, acquiring a sub-application page sharing list with sharing authority relative to the local user identifier.

And S1206, the local terminal sends the sharing object identifier and a second sub-application page identifier selected from the sub-application page sharing list to the first application platform.

S1208, the first application platform generates a second sub-application page message for specifying a second sub-application page of a second target sub-application.

And S1210, when the application platform to which the sharing object identifier belongs is the first application platform, the first application platform directly sends the second sub application page message to the terminal corresponding to the sharing object identifier.

And S1212, when the application platform to which the shared object identifier belongs is the second application platform, the first application platform sends the second sub-application page message to the second application platform to which the shared object identifier belongs through the intercommunication background, and the second application platform sends the second sub-application page message to the terminal corresponding to the shared object identifier.

And S1214, when the application platform to which the sharing object identifier belongs is the first application platform, the terminal corresponding to the sharing object identifier triggers the second sub-application page message in the first application.

S1216, when the application platform to which the shared object identifier belongs is a second application platform, triggering, by the terminal corresponding to the shared object identifier, a second sub-application page message in the second application.

And S1218, the terminal corresponding to the sharing object identifier sends the sharing object identifier and the second sub-application page identifier of the second sub-application page specified by the second sub-application page message to the user information management system associated with the second target sub-application.

S1220, the user information management system feeds back the shared data corresponding to the second sub-application page identifier and associated with the shared object identifier to the terminal corresponding to the shared object identifier.

S1222, when the application platform to which the sharing object identifier belongs is the first application platform, the terminal corresponding to the sharing party identifier displays the shared data through the second target sub-application running in the environment provided by the first application.

S1224, when the application platform to which the sharing object identifier belongs is the second application platform, displaying, by the terminal corresponding to the sharing party identifier, the shared data through the second target sub-application running in the environment provided by the second application.

In one embodiment, the shared message handling method is further described. The terminal corresponding to the administrator user identifier may display the configuration page of the second target sub-application as shown in fig. 13, and the terminal corresponding to the administrator user identifier may set the visible range of the second target sub-application in the configuration page of the second target sub-application as shown in fig. 13, and add the local user identifier to the visible range of the second target sub-application. The terminal corresponding to the administrator user identifier may display a workbench page as shown in fig. 14, and when the "second target sub-application" associated with the user information management system in the workbench page is triggered, the terminal corresponding to the administrator user identifier displays a configuration page of the second target sub-application as shown in fig. 15. When the sub-application page configuration entry "attachment bar" in the configuration page of the second target sub-application shown in fig. 15 is triggered, the terminal corresponding to the administrator user identifier displays an attachment list shown in fig. 16, and the configured identifier of the sub-application page belonging to the second target sub-application is displayed in the attachment list. When the "add sub application page" in the attachment list is triggered, the sub application page sharing list shown in fig. 17 is displayed, and the terminal corresponding to the administrator user identifier can preview the second sub application page by selecting the "second sub application page" in the sub application page sharing list. The terminal corresponding to the administrator user identifier can add the selected second sub-application page to the attachment list through the 'add to attachment column'.

The local terminal logging in the first application with the local user identifier displays the sub-application page sharing entry "sub-application" in the dialog box including the local user identifier and the sharing object identifier, as shown in fig. 18. The local terminal acquires the sharing object identifier of the 3-bit sharing object included in the dialog box, and of course, when the dialog box includes only one-bit sharing object, the local terminal acquires the sharing object identifier of the one-bit sharing object. When the local terminal detects that the sub-application page sharing entry 'sub-application' is triggered, a sub-application page sharing list with sharing authority relative to the local user identifier is obtained and displayed, as shown in fig. 19.

The local terminal may select one or more sub-application page identifiers from the sub-application page sharing list shown in fig. 19, for example, if the local terminal selects two second sub-application page identifiers of the second target sub-application from the sub-application page sharing list shown in fig. 19, the local terminal generates the second sub-application page messages shown in fig. 20 and fig. 21 corresponding to the two selected second sub-application page identifiers, respectively. The local terminal shares the generated second sub-application page message to the terminal corresponding to the sharing object identifier through the dialog box, as shown in fig. 22. The terminal corresponding to the sharing object identifier receives the second sub application page message shared by the local terminal through the dialog box, as shown in fig. 23.

Fig. 2 to 4 are schematic flowcharts illustrating a user profile processing method and a shared message processing method according to an embodiment. It should be understood that although the steps in the flowcharts of fig. 2 to 4 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-4 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

As shown in fig. 24, in one embodiment, there is provided a user profile processing apparatus 2400, which includes a target user identifier obtaining module 2401, a query request sending module 2402, a user profile receiving module 2403, and a user profile displaying module 2404, wherein:

a target user identifier obtaining module 2401, configured to obtain a target user identifier to be queried when a user profile query entry for querying a user profile from the user information management system is triggered.

A query request sending module 2402, configured to send a query request carrying a target user identifier to a user information management system.

A user data receiving module 2403, configured to receive user data fed back by the user information management system in response to the query request; the feedback user data is obtained according to the user data which are respectively from the user information management system and the application platform and respectively correspond to the target user identification.

A user data display module 2404, configured to display the received user data.

The user data processing device can directly query the user data of the target user from the user information management system by utilizing the user data query entry and the target user identification without switching among a plurality of systems and a plurality of accounts, and the queried user data is obtained according to the user data from the user information management system and the application platform respectively, so that the user data can be efficiently and comprehensively queried.

In one embodiment, user profile display module 2404 is also used to enter a sub-application running in an environment provided by the first application; displaying a user profile page in the sub-application; and displaying the received user data on a user data page.

In one embodiment, the user profile display module 2404 is further configured to query the sub-application page identification corresponding to the user information management system configuration; when the sub-application page identification is inquired, entering a user data page corresponding to the sub-application page identification in the sub-application; and when the page identifier of the sub-application is not inquired, entering a default page in the sub-application, and entering a user data page according to a user instruction when the user instruction is received.

In one embodiment, the user profile display module 2404 is further configured to obtain a page type corresponding to the user information management system configuration; entering a user data page matched with the page type; and displaying the received user data on a user data page.

In one embodiment, the user profile processing apparatus further comprises a user profile modification module, wherein the user profile modification module is configured to obtain a user profile modification instruction; modifying the displayed user data belonging to the user information management system according to the user data modification instruction; and synchronizing the modified user profile to the user information management system corresponding to the target user identification.

In one embodiment, the user profile processing apparatus further includes a message receiving module, a page display module, a shared data request module, and a shared data display module, wherein:

the message receiving module is used for receiving the shared first sub-application page message; the first sub-application page message specifies a first sub-application page of the first target sub-application;

the shared data request module is used for requesting shared data which corresponds to a first sub-application page of the first target sub-application and is associated with the local user identifier from the user information management system;

In one embodiment, the user data processing apparatus further includes a message sharing module, configured to obtain a shared object identifier; acquiring a second sub application page message to be shared; the second sub-application page message specifies a second sub-application page of a second target sub-application; sharing the second sub application page message to a terminal corresponding to the sharing object identifier; the second sub-application page message is used for instructing the terminal to acquire shared data corresponding to a second sub-application page of a second target sub-application and associated with the user identity corresponding to the terminal, and the shared data is displayed through the second target sub-application running in an environment provided by the second application.

In one embodiment, the message sharing module is further configured to obtain a sub-application page sharing list having a sharing right with respect to the local user identifier; selecting a sub-application page of a second target sub-application from the sub-application page sharing list according to a user selection instruction; a second sub-application page message is generated specifying a second sub-application page of a second target sub-application.

As shown in fig. 25, in one embodiment, a shared message processing apparatus 2500 is provided, which includes a message receiving module 2501, a page display module 2502, a shared data request module 2503, and a shared data display module 2504, wherein:

a message receiving module 2501, configured to receive a shared first sub-application page message; the first sub-application page message specifies a first sub-application page of the first target sub-application;

a page display module 2502, configured to display a first sub-application page of a first target sub-application through the first target sub-application running in an environment provided by the first application;

a shared data request module 2503, configured to request, from the user information management system, shared data that corresponds to a first sub-application page of the first target sub-application and is associated with the local user identifier;

the shared data display module 2504 is configured to display the shared data on a first sub-application page of the first target sub-application.

According to the sharing message processing device, the shared first sub-application page message can be received through the target sub-application running in the first application, shared data is acquired and displayed from the user information management system, and data sharing can be efficiently achieved. In addition, the sharing party only needs to share the same first sub-application page message to different users, and after receiving the same first sub-application page message, the different users all display sharing data related to the sharing party, so that the safety of user information is guaranteed, and high efficiency and convenience of data sharing can be guaranteed.

In one embodiment, the shared message processing apparatus further includes a message sharing module, configured to obtain a shared object identifier; acquiring a second sub application page message to be shared; the second sub-application page message specifies a second sub-application page of a second target sub-application; sharing the second sub application page message to a terminal corresponding to the sharing object identifier; the second sub-application page message is used for instructing the terminal to acquire shared data corresponding to a second sub-application page of a second target sub-application and associated with the user identity corresponding to the terminal, and the shared data is displayed through the second target sub-application running in an environment provided by the second application.

FIG. 26 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be the local terminal 110 in fig. 1. As shown in fig. 26, the computer apparatus includes a processor, a memory, a network interface, an input device, and a display screen connected through a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may further store a computer program, which, when executed by the processor, causes the processor to implement a user profile processing method or a shared message processing method. The internal memory may also store a computer program, and the computer program, when executed by the processor, may cause the processor to perform a user data processing method or a shared message processing method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the architecture shown in fig. 26 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, the user profile processing apparatus or the shared message processing apparatus provided in the present application may be implemented in the form of a computer program, and the computer program may be executed on a computer device as shown in fig. 26. The memory of the computer device may store various program modules constituting the user profile processing apparatus or the shared message processing apparatus, for example, the user identifier obtaining module 2401, the query request sending module 2402, the user profile receiving module 2403, and the user profile display module 2404 shown in fig. 24, and the message receiving module 2501, the page display module 2502, the shared data requesting module 2503, and the shared data display module 2504 shown in fig. 25. The computer program formed by the program modules enables the processor to execute the steps in the user data processing method or the shared message processing method according to the embodiments of the present application described in the present specification.

For example, the computer device shown in fig. 26 may execute, by the user identifier obtaining module 2401 in the user profile processing apparatus shown in fig. 24, obtaining a target user identifier to be queried when a user profile query entry for querying a user profile from the user information management system is triggered. The computer device may execute sending the query request carrying the target user identifier to the user information management system through the query request sending module 2402. The computer device can receive the user data fed back by the user information management system in response to the query request through the user data receiving module 2403; the feedback user data is obtained according to the user data which are respectively from the user information management system and the application platform and respectively correspond to the target user identification. The computer device may perform displaying the received user profile through the user profile display module 2404.

For example, the computer device shown in fig. 26 may execute receiving the shared first sub application page message through the message receiving module 2501 in the shared message processing apparatus shown in fig. 25; the first sub-application page message specifies a first sub-application page of the first target sub-application. The computer device may display a first sub-application page of a first target sub-application by executing the first target sub-application running in an environment provided by the first application through the page display module 2502. The computer device may request, from the user information management system, shared data corresponding to a first sub-application page of the first target sub-application and associated with the local user identifier through the shared data request module 2503. The computer device may display the shared data on the first sub-application page of the first target sub-application through the shared data display module 2504.

In one embodiment, a computer device is provided, which includes a memory and a processor, the memory stores a computer program, and the computer program, when executed by the processor, causes the processor to execute the steps of the user data processing method or the shared message processing method. Here, the steps of the user profile processing method or the shared message processing method may be steps of the user profile processing method or the shared message processing method in the foregoing embodiments.

In one embodiment, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the processor executes the steps of the user data processing method or the shared message processing method. Here, the steps of the user profile processing method or the shared message processing method may be steps of the user profile processing method or the shared message processing method in the foregoing embodiments.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method of user profile processing, the method comprising:

when a user data query entry for querying user data from a user information management system is triggered, acquiring a target user identifier to be queried; the user profile query entry is triggered by logging in a local user identifier of a first application, and a group to which the local user identifier belongs is associated with the user information management system in the first application;

receiving user data fed back by the user information management system in response to the query request; the feedback user data is obtained by the user information management system according to the first user data and the second user data; the first user data is acquired by the user information management system from a self storage according to the target user identification, and the second user data is acquired by the user information management system from an application platform to which the target user identification belongs through an open interface provided by a first application platform based on the target user identification;

and displaying the received user data.

2. The method of claim 1, wherein the user profile query entry can be triggered after logging into the first application with a local user identification; the application platform corresponds to one of a first application and a second application; the second application is different from the first application.

3. The method of claim 2, wherein displaying the received user profile comprises:

entering a sub-application running in an environment provided by the first application;

displaying a user profile page in the sub-application;

and displaying the received user data on the user data page.

4. The method of claim 3, wherein displaying a user profile page in the sub-application comprises:

inquiring a sub application page identifier corresponding to the user information management system configuration;

when the sub-application page identification is inquired, entering a user data page corresponding to the sub-application page identification in the sub-application;

and when the page identifier of the sub-application is not inquired, entering a default page in the sub-application, and entering a user data page according to a user instruction when the user instruction is received.

5. The method of claim 1, wherein displaying the received user profile comprises:

acquiring a page type configured corresponding to the user information management system;

entering a user data page matched with the page type;

and displaying the received user data on the user data page.

6. The method of claim 1, further comprising:

acquiring a user data modification instruction;

modifying the displayed user data belonging to the user information management system according to the user data modification instruction;

and synchronizing the modified user profile to the user information management system corresponding to the target user identification.

7. The method according to any one of claims 1 to 6, wherein the user profile query entry can be triggered after logging in the first application with a local user identifier belonging to a group and when the local user identifier has a social relationship with the target user identifier; the user information management system corresponds to the group.

8. The method according to any one of claims 1 to 6, further comprising:

requesting, from the user information management system, shared data corresponding to a first sub-application page of the first target sub-application and associated with a local user identifier;

9. The method according to any one of claims 1 to 6, further comprising:

acquiring a sharing object identifier;

acquiring a second sub application page message to be shared; the second sub-application page message specifies a second sub-application page of a second target sub-application;

sharing the second sub application page message to a terminal corresponding to the sharing object identifier; the second sub-application page message is used for instructing the terminal to acquire shared data corresponding to a second sub-application page of the second target sub-application and associated with the user identity corresponding to the terminal, and displaying the shared data through the second target sub-application running in an environment provided by the second application.

10. The method according to claim 9, wherein the obtaining the second sub application page message to be shared comprises:

acquiring a sub-application page sharing list with sharing authority relative to a local user identifier;

selecting a second sub-application page of a second target sub-application from the sub-application page sharing list according to a user selection instruction;

generating a second sub-application page message specifying a second sub-application page of the second target sub-application.

11. A shared message processing method comprises the following steps:

the local terminal receives a shared first sub-application page message through a first application; the first sub-application is a message shared by sub-applications running in an environment provided by the first application; the first sub-application page message specifies a first sub-application page of a first target sub-application;

requesting, from a user information management system of a group to which a sharer user identifier belongs, shared data corresponding to a first sub-application page of the first target sub-application and associated with a local user identifier; the user information management system of the group to which the sharing party user identification belongs is different from the user information management system of the group to which the local user identification of the local terminal logs in;

12. The method of claim 11, further comprising:

acquiring a sharing object identifier;

13. The method according to claim 12, wherein the obtaining the second sub application page message to be shared comprises:

selecting a sub application page of a second target sub application from the sub application page sharing list according to a user selection instruction;

14. A user profile processing apparatus, said apparatus comprising:

and the user data display module is used for displaying the received user data.

15. The apparatus of claim 14, wherein the user profile query entry is capable of being triggered upon logging into the first application with a local user identification; the application platform corresponds to one of a first application and a second application; the second application is different from the first application.

16. The apparatus of claim 15, wherein the user profile display module is further configured to:

displaying a user profile page in the sub-application;

and displaying the received user data on the user data page.

17. The apparatus of claim 16, wherein the user profile display module is further configured to:

18. The apparatus of claim 14, wherein the user profile display module is further configured to:

entering a user data page matched with the page type;

and displaying the received user data on the user data page.

19. The apparatus of claim 14, further comprising a user profile modification module configured to:

acquiring a user data modification instruction;

20. The apparatus according to any one of claims 14 to 19, wherein the user profile query portal is capable of being triggered after logging in the first application with a local user identifier belonging to a group and when the local user identifier has a social relationship with the target user identifier; the user information management system corresponds to the group.

21. The apparatus of any one of claims 14 to 19, further comprising:

22. The apparatus according to any one of claims 14 to 19, further comprising a message sharing module configured to:

acquiring a sharing object identifier;

23. The apparatus of claim 22, wherein the message sharing module is further configured to:

24. A shared message processing apparatus, the apparatus comprising:

the message receiving module is used for receiving the shared first sub-application page message by the local terminal through the first application; the first sub-application is a message shared by sub-applications running in an environment provided by the first application; the first sub-application page message specifies a first sub-application page of a first target sub-application;

the shared data request module is used for requesting shared data which corresponds to a first sub-application page of the first target sub-application and is associated with the local user identification from a user information management system of a group to which the sharer user identification belongs; the user information management system of the group to which the sharing party user identification belongs is different from the user information management system of the group to which the local user identification of the local terminal logs in;

25. The apparatus of claim 24, further comprising a message sharing module configured to:

acquiring a sharing object identifier;

26. The apparatus of claim 25, wherein the message sharing module is further configured to:

27. A computer-readable storage medium, storing a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 13.

28. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any one of claims 1 to 13.