CN116233041A

CN116233041A - Information processing method and device and electronic equipment

Info

Publication number: CN116233041A
Application number: CN202310215689.9A
Authority: CN
Inventors: 王重; 石峰娟; 张超; 赵家琛; 俞柳源; 熊力; 史庭盛
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2023-02-28
Filing date: 2023-02-28
Publication date: 2023-06-06

Abstract

The embodiment of the disclosure provides an information processing method, an information processing device and electronic equipment, wherein the method comprises the following steps: creating a target component according to a received session component creation request, wherein the session component creation request comprises a target session identifier and address information of service data; acquiring the service data according to the address information; instantiating the target component according to the service data; and displaying the target component instance in the session interface indicated by the target session identification. The method and the device realize the establishment of the session component in the session, instantiate the component by using the service data, and display the component instance on the session interface corresponding to the session user, so that the service data of the third party concerned by the session user is displayed in the session interface in the mode of the component. The operation of the session user for acquiring the service data is reduced, and the efficiency of the session user for acquiring the service data is improved.

Description

Information processing method and device and electronic equipment

Technical Field

The embodiment of the disclosure relates to the technical field of computers, in particular to an information processing method, an information processing device and electronic equipment.

Background

With the development of communication technology, users can use instant messaging applications to communicate information. The user may develop multiple sessions using the instant messaging application. And carrying out real-time information communication with at least one contact person in the session.

Messages in a conversation are typically displayed in the conversation in chronological order of production.

The session related users may all be concerned with the same information. The information may be other than the content of the session, such as information from a third party platform. In the related art, when each user looks up the information, the page provided by the third party platform needs to be opened, and then the information is browsed in the page.

That is, the operation of acquiring the above information by the user in the session is complicated. The method is unfavorable for the user to quickly acquire the information of interest, so that the efficiency of acquiring the information outside the session by the session user is lower.

Disclosure of Invention

The embodiment of the disclosure provides an information processing method, an information processing device and electronic equipment, which are used for solving the problem that the efficiency of acquiring commonly focused information by users corresponding to a session in the related technology is low.

In a first aspect, an embodiment of the present disclosure provides an information processing method, including:

creating a target component according to a received session component creation request, wherein the session component creation request comprises a target session identifier and address information of service data;

acquiring the service data according to the address information;

Instantiating the target component according to the service data;

and displaying the target component instance in the session interface indicated by the target session identification.

In a second aspect, an embodiment of the present disclosure provides an information processing method, including:

displaying the component container in a display interface of the target session;

displaying at least one component instance comprising a target component instance in the component container; the target component example comprises preset service data.

In a third aspect, an embodiment of the present disclosure provides an information processing method, including:

generating a session component creation request, wherein the session component creation request comprises address information of service data and an identification of a target session;

sending the session component creation request to a session server of the target session so that the session server creates a target component;

transmitting the service data to the session server; so that the session server generates a target component instance according to the service data.

In a fourth aspect, an embodiment of the present disclosure provides an information processing apparatus including:

the system comprises a creation unit, a service data acquisition unit and a service data acquisition unit, wherein the creation unit is used for creating a target component according to a received session component creation request, and the session component creation request comprises a target session identifier and address information of the service data;

The acquisition unit is used for acquiring the service data according to the address information;

an instantiation unit, configured to instantiate the target component according to the service data;

and the first display unit is used for displaying the target component instance in the session interface indicated by the target session identification.

In a fifth aspect, an embodiment of the present disclosure provides an information processing apparatus including:

a second display unit for displaying the component container in a display interface of the target session;

a third display unit for displaying at least one component instance including a target component instance in the component container; the target component example comprises preset service data.

In a sixth aspect, an embodiment of the present disclosure provides an information processing apparatus including:

a generation unit, configured to generate a session component creation request, where the session component creation request includes address information of service data and an identifier of a target session;

a first sending unit, configured to send the session component creation request to a session server of the target session, so that the session server creates a target component;

a second sending unit, configured to send the service data to the session server; so that the session server generates a target component instance according to the service data.

In a seventh aspect, embodiments of the present disclosure provide an electronic device, including: a processor and a memory; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored by the memory to cause the at least one processor to perform the first, second, third aspects described above, as well as the various information processing methods that may be involved in the aspects described above.

In an eighth aspect, embodiments of the present disclosure provide a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement the above-described first aspect, second aspect, third aspect, and various information processing methods that may be involved in the above-described aspects.

In a ninth aspect, embodiments of the present disclosure provide a computer program product comprising a computer program which, when executed by a processor, implements the above first, second, third aspects and various possible information processing methods of the above aspects.

According to the information processing method, the information processing device and the electronic equipment, the target component is created according to the received session component creation request, and the session component creation request comprises the target session identifier and the address information of the service data; acquiring the service data according to the address information; instantiating the target component according to the service data; the method comprises the steps of displaying a target component instance in a session interface indicated by the target session identifier, creating a session component in a session, instantiating the component by using service data, and displaying the component instance in the session interface corresponding to a session user, so that the service data of a third party except a session message focused by the session user is displayed in the session interface in a component mode. The operation of the session user for acquiring the service data is reduced, and the efficiency of the session user for acquiring the service data is improved.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the solutions in the prior art, a brief description will be given below of the drawings that are needed in the embodiments or the description of the prior art, it being obvious that the drawings in the following description are some embodiments of the present disclosure, and that other drawings may be obtained from these drawings without inventive effort to a person of ordinary skill in the art.

Fig. 1 is a schematic flow chart of an information processing method according to an embodiment of the disclosure;

fig. 2 is a second flow chart of an information processing method according to an embodiment of the disclosure;

FIG. 3 is a flow chart III of an information processing method according to the present disclosure;

FIG. 4A is a schematic illustration of a session interface for a target session provided in accordance with the present disclosure;

FIG. 4B is a schematic illustration of a session interface for a target session provided in accordance with the present disclosure;

FIG. 4C is a schematic illustration of a session interface for a target session provided in accordance with the present disclosure;

fig. 5 is a flow chart diagram of an information processing method according to the present disclosure;

FIG. 6 is a schematic flow chart diagram of an information processing method according to the present disclosure;

Fig. 7 is a block diagram of an information processing apparatus according to an embodiment of the present disclosure;

fig. 8 is a block diagram of an information processing apparatus according to an embodiment of the present disclosure;

fig. 9 is a block diagram of an information processing apparatus according to an embodiment of the present disclosure;

fig. 10 is a schematic hardware structure of an electronic device according to an embodiment of the disclosure.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are some embodiments of the present disclosure, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without inventive effort, based on the embodiments in this disclosure are intended to be within the scope of this disclosure.

In instant messaging applications, a session typically involves at least two users. Session detail information, such as at least one message of the session user, etc., may be displayed in the session interface.

In addition to information communication with other conversational users, conversational users may also be interested in some information from third party platforms.

If the session user needs information from the third party platform, the session user needs to enter a page of the third party platform and then browse the information in the page. For the users in the session, if the users in the session pay attention to the information, the users need to use respective terminal devices to open the pages of the third-party platform respectively to browse the information. In this way, the total duration of the user in the session for acquiring the information is longer, so that the efficiency of the user in the session for acquiring the information is lower.

In order to improve the above problem, the solution provided by the present disclosure creates a target component corresponding to a session, generates a target component instance according to service data outside a session message, and displays the target component instance in a session interface, so that all users of the session can browse the service data in the session interface, and the efficiency of the session user to acquire the service data outside the session message can be improved.

Referring to fig. 1, fig. 1 is a flowchart illustrating an information processing method according to an embodiment of the disclosure. The method comprises the following steps:

s101: and creating a target component according to the received session component creation request, wherein the session component creation request comprises the target session identification and the address information of the service data.

The execution subject of the information processing method of the present embodiment may be a session server (may also be referred to as an instant messaging application server). Such as servers that provide message forwarding and message storage for parties to the session.

In addition, the session server may also provide the client with display layout information of each element in the session interface.

In this embodiment, the information of the component container is included in the display layout information provided by the session server to the client.

The above component containers can be used to manage a plurality of components, respectively. For component containers to which components have been associated, the server may set a display position thereof in the component container for each component. For each component (e.g., the Widget component), the components are independent of each other and do not interfere with each other.

The session component creation request is used to create a component for a target session that is displayed on the session interface. The target session herein may be various sessions, such as a single chat session, a group chat session, etc. The component to be created may be referred to herein as a target component.

The session creation request includes the target session identification and address information of the service data.

The target session identification may include text, letters, symbols, or the like. The session identification may distinguish between different sessions.

The traffic data here may be data of interest to most of the session users in the target session. The traffic data here may be data other than session messages, such as data from a third party platform.

Illustratively, the business data herein may include real-time stock market quotation data, for example.

The traffic data here may be illustratively real-time race data or the like.

The business data here may illustratively be real-time inventory data or the like.

The business data herein may include text, graphics, images, tables, and the like.

The address information refers to address information of the service data storage. The address information may include, for example, a uniform resource locator (Uniform Resource Locator, URL).

The execution body may acquire the service data from the address indicated by the address information.

In this embodiment, the session component may be various components. In some embodiments, the components described above may be, for example, micro-components (Widget components).

The following requirements of users can be met by using micro-components: simple, clear, proper display and personalized customization.

A micro-component may be a structured description of a view, primarily storing configuration information about view rendering, including layout, rendering attributes, event response information. Generally, the micro-assembly has three main components: a limit frame, a frame, and a graphic control of the Widget and other elements.

In some embodiments, the session component creation request herein may be issued by the client through which the session user is using to conduct the session. The client may be running in a terminal device. The client may be an instant messaging application client.

In some embodiments, the session component creation request herein may be issued by a server of business data of interest to the session user.

In these embodiments, the business data server may actively send the session component creation request described above to the session server.

In some embodiments, the step S101 includes:

firstly, receiving a session component creation request sent by a service data server through a component creation interface;

second, a target component is created using the component add interface.

In these embodiments, the execution subject described above may provide a component creation interface, such as a micro component creation interface (CreatWidget). The service data server may send a session component creation request to the session server using the component creation interface described above. Such as the service data invoking the component creation interface provided by the session server locally, and inputting parameters such as address information of the service data and the type of the target component in the component creation interface.

The session server may create the target component from a component add interface provided by the home terminal (e.g., the micro component add interface addhatwidgets).

In these embodiments, the session server may receive a session component creation request sent by the service data through the component creation interface, and create the target component using the component addition interface, that is, the session server may create the target component using a component processing function provided in advance at the local end of the session server, so that the speed of creating the target component may be increased.

In some embodiments, the step S101 includes: a target component abstract instance is created from the session component creation request.

In these embodiments, after receiving the session component creation request, the executing entity may first create the target component abstract instance according to a preset abstract instance creation rule.

Limiting frames, basic controls, etc. of the target component may be included in the target component abstract instance.

In these embodiments, the target component instance may be obtained after filling the business data into the abstract instance of the target component; alternatively, or after filling the business data into the abstract instance of the target component according to the specified display style, the target component instance may be obtained.

S102: and acquiring service data according to the address information.

The address information may include a storage address of the service data, for example, an address of a standard resource of the service data on the internet: a URL. For URLs, one may typically include a schema (or protocol), a server name (or IP address), a path, and a file name, such as "protocol:// authorization/path? And (5) inquiring. The more complete URL is illustrated as follows: protocol:// username: password @ subdomain name:. Domain name: port number/directory/filename? Parameter = value # flag.

The execution body may acquire service data from the service data server according to the address information through a wired or wireless communication connection.

S103: the target component is instantiated from the business data.

After the service data is acquired, the target component may be instantiated using a preset component instantiation method. In instantiating the target component, the business data is populated into the target component. In one example, the service data may be bound to an Element (Element) in the target component that is preset to carry the service data. Rendering information for each element of the target component is then generated. Thereby obtaining the target component instance.

S104: and displaying the target component instance in the session interface indicated by the target session identification.

The session interface herein may be a session interface of a target session indicated by the target session identification. The session interface may be a session interface corresponding to at least one session user of the target session.

In this embodiment, the executing body may send the target component instance to a client (e.g., an instant messaging application client) corresponding to each session user of the target session, so that the client displays the target component instance on a session interface of the target session.

In practice, the session message and the target component instance of the target session may be displayed in the upper session interface.

The target component instance described above may be displayed in a component container of the session interface.

In this embodiment, a target component is created according to a received session component creation request, where the session component creation request includes a target session identifier and address information of service data; acquiring service data according to the address information; instantiating a target component according to the service data; and displaying the target component instance in the session interface indicated by the target session identification. The method and the device realize the establishment of the session component in the session, instantiate the component by using the service data, and display the component instance on the session interface corresponding to the session user, so that the service data except the session message focused by the session user is displayed in the session interface in a component mode. The operation of the session user for acquiring the third-party service data is reduced, and the efficiency of the session user for acquiring the service data is improved.

Referring to fig. 2, fig. 2 is a flow chart of a second information processing method according to an embodiment of the disclosure. The method comprises the following steps:

s201: and creating a target component according to the received session component creation request, wherein the session component creation request comprises the target session identification and the address information of the service data.

In this embodiment, the execution subject of the information processing method may be a session server.

The specific implementation of step S201 and step S204 may refer to step S101 and step S104 in the embodiment shown in fig. 1, which is not described in detail here.

S202: and acquiring the display style and the service data according to the address information.

The service data and the display style of the service data may be stored in a service data server. The address information may include a uniform resource locator corresponding to a physical address storing the display style and the service data.

The display style may be a display style of service data. Including but not limited to: background color, number of windows, window size, window layout, text/symbol color, text/symbol size, font, image/graphic size, etc.

The execution body may acquire the display style and the service data from the service data server according to the address information.

S203: the target component is instantiated according to the display style and the business data.

By using the instantiation method, the execution body can instantiate the target component according to the display style by using the service data, thereby obtaining the target component instance.

S204: and displaying the target component instance in the session interface indicated by the target session identification.

In this embodiment, the above service data server provides a display style for displaying service data, so that the session server does not need to determine the display style of the service data, thereby simplifying the step of generating the target component by the session server, reducing the resource consumption of generating the target component by the session server, improving the speed of generating the target component by the session server, and further improving the overall efficiency of generating the target component to display the target component instance on the session interface of the target session.

In some embodiments of the information processing method shown in fig. 1 and 2, the above-described information processing method further includes:

first, a preview identifier corresponding to a target component is created, and the preview identifier is associated with address information.

Second, the preview identification is sent to the client of the user of the target session. and

Step S102 of the embodiment shown in fig. 1 and step S202 of the embodiment shown in fig. 2 include:

responding to a browsing request sent by a client of a user receiving a target session and used for browsing a target component instance, and acquiring service data according to address information; wherein the browse request includes a preview identification.

In these embodiments, the execution body may generate a preview identification (PreviewID) of the target component after creating the target component (target component abstract instance) according to the session component creation request. The execution body may associate a preview identification with the address information. The preview identification is then sent to the client (e.g., instant messaging application client) displaying the target session.

The user can initiate a browsing operation of browsing the target component instance on the session interface of the target session. The client can search whether the component instance matched with the preview identifier is stored locally, if so, the local component instance is bound with the target component to generate the target component instance.

The client may generate a browse request that may include the preview identifier without locally finding a component instance that matches the preview identifier. The client may send the browsing request to the session server, where the session server may search for address information associated with the preview identifier if the component instance corresponding to the preview identifier is not found locally. And then acquiring service data from the service data server according to the address information.

In these embodiments, after the target component is created, a preview identifier associated with the address information is generated, and then the preview identifier is sent to the client, so that the client obtains service data locally or through the session server according to the preview identifier to generate a target component instance, which is beneficial to management of different components.

In some embodiments of the information processing method shown in fig. 1 and 2, the information processing method further includes the steps of:

first, updated service data and/or display patterns are acquired.

And secondly, updating the target component instance according to the updated service data and/or the display style.

In these embodiments, the execution body may send the update information acquisition request to the service data server at preset time intervals. The service data may detect whether the service data and/or the display style is updated according to the acquisition request. If the service data and/or the display pattern are detected to be updated, generating update information comprising the updated service data and/or display pattern.

And after receiving the updated service data and/or the display style, the execution main body updates the target component instance according to the updated service data and/or the display style.

In these embodiments, the session server may obtain updated business data for the target component instance and then update the target component instance. Thereby being beneficial to the conversation server to actively update the target component instance according to the service data. Thereby facilitating control of content in the target component instance displayed at the session interface of the target session.

detecting that the target component instance changes, and pushing information of the changed target component instance to a client of a user of the target session; wherein the changes are generated by updated service data and/or display patterns sent by the service data server.

In these embodiments, the service data server may actively detect whether the service data and/or the display pattern changes, for example, at intervals of a preset time.

When it is detected that at least one of the service data and the display style is changed, the updated service data and/or display style may be transmitted to the session server. The session server updates the target component instance according to the updated service data and/or the display style, thereby causing the target component instance to change. The execution body may send information of the changed target component instance to the client. The information may include information indicating which service data and/or patterns are updated in the target component instance, and the service data and/or patterns after the service data and/or patterns are updated.

After receiving the information of the changed target component instance, the client can display the updated target component instance at the local end according to the information.

In these embodiments, the session server detects that the target component instance changes according to the information pushed by the service data server, and pushes the changed information of the target component instance to the client, so that the client can display the updated target component instance, and the user of the target session can timely learn the latest service data in the session interface, thereby improving the efficiency of the user to acquire the service data outside the session message.

and according to the received deleting instruction of the session component, deleting the component in the target session indicated by the deleting instruction, and sending an instruction for indicating to delete the prestored information of the component to the client of the target session user.

In these embodiments, the deletion instruction may be generated by the client of the session user according to a component deletion operation issued by the session user at the session interface. The deletion instruction includes identification information of the component to be deleted, such as preview identification information of the component, and the like.

After receiving the deletion instruction, the execution body may delete the component instance of the component locally, for example, display style, service data, etc., delete the preview identifier of the component, address information associated with the preview identifier, etc., and finally delete the component.

In addition, the execution body may send an instruction for instructing to delete the pre-stored information of the component to the client. The client can delete all the locally pre-stored information of the component according to the instruction.

In these embodiments, the components in the target session may be deleted by the deletion instruction described above, thereby facilitating maintenance of the components in the session.

Referring to fig. 3, fig. 3 is a flowchart illustrating a method for processing information according to an embodiment of the disclosure. The method comprises the following steps.

S301: the component container is displayed in a session interface of the target session.

The execution subject in the present embodiment may be a terminal device. Specifically, the client which runs on the terminal device and can perform the session, such as an instant messaging application client.

The target session herein may be various sessions, such as a single chat session, a group chat session.

The session interface may be a session interface for displaying a message of the target session, a session interface for displaying a calendar of the target session, or the like.

The component container herein may be pre-created for housing at least one component.

In some application scenarios, the component container described above may be created for the target session by a session server. The session server may associate the component container with the target session and send the component container to the client. And the client displays the component container when displaying the session interface of the target session according to the association relation between the target session and the component container.

In some application scenarios, the component container may be created by the session server according to the received first component creation request to create the target session.

In some application scenarios, the component container may be hidden, and in these application scenarios, a container display control for indicating to display the component container may be included in a session interface of the target session. The user may trigger the container display control described above. After detecting the triggering operation of the user on the container display control, the execution body can display the component container in the session interface of the target session.

S302: displaying at least one component instance comprising a target component instance in a component container; the target component example comprises preset service data.

The at least one component instance may be pre-generated and bound to the target session. The at least one component instance may have an association relationship with the component container in advance.

For example, the session server may create a component in advance according to the session component creation request, bind the component with the target session, generate a component instance (including session component instance rendering information), and send the component instance to the client.

The client displays at least one component instance while displaying the component container.

In some application scenarios, the session interface of the target session also displays at least a portion of the session message of the target session.

In one example, the conversation message display area and the component container display area are displayed from left to right in the conversation interface described above. The message display area may display at least one session message of the target session. The component container display area may display a plurality of components bound to the target session.

Referring to fig. 4A, fig. 4A shows a schematic diagram of a session interface of a target session.

As shown in fig. 4A, a session flow display area 401, a session message display area 402, and a component container display area 403 may be included in the session interface of the target session. As shown in fig. 4A, the target session selected for display in the current session interface is session 3. Session message display area 402 displays session messages for session 3. In the component container display area 403, a component container identification "session component" 4031 and a plurality of session components, such as session component 1 and session component 2 in fig. 4A, and the like, can be displayed.

In some embodiments, in the session interface, the component container is displayed on top of the session interface, and the step S302 includes:

in response to receiving a first presentation instruction to display a plurality of component instances, increasing a display area of a component container at a session interface and displaying the plurality of component instances in the component container.

In these embodiments, the default component container is displayed at the top of the session interface and at least one session message may be displayed below the component container.

Referring to fig. 4B, fig. 4B shows a schematic diagram of a session interface of a target session.

As shown in fig. 4B, the current target session is session 3, and in the session interface 404 of the target session 3, the component container 405 is displayed on top of the session interface 404. 1 session component is displayed in the default component container 405, such as session component 1 in fig. 4B. In the session interface, a session message area 406 may be displayed below the component container 405, which may display at least a portion of the session message.

In one example, a drop-down control may be displayed in the component container, and when a trigger operation performed on the drop-down control by a user is received, the drop-down control may be regarded as receiving a first display instruction.

After receiving the first display instruction, increasing the display area of the component container in the session interface, for example, extending the display length of the component container downwards. After the above display area is increased, more component instances can be displayed in the above component container.

Referring to fig. 4C, fig. 4C is a session interface after the first presentation instruction is executed in fig. 4B. As shown in fig. 4C, according to the first display instruction, the display area of the component container 405 is increased, that is, the component container is elongated, so that session components such as session component 1 and session component 2 may be displayed in the elongated component container.

In these embodiments, by default, the component container is set to top display a single component instance, and when a user needs to browse multiple component instances, the first exhibition instruction may be executed, so as to browse multiple component instances in the component container with increased display area. So that one or more component instances may be displayed in the session interface of the target session according to the needs of the user.

The component examples are independent and do not interfere with each other.

The target component instance is one of the at least one component instances. The target component instance may be pre-created by the session server and associated with the target session and then sent to the session user client to which the target session corresponds. The target component example may include preset service data. The preset service data may be determined and acquired by the session server according to the received target component creation request.

The traffic data here may be data of interest to most of the session users in the target session.

In one example, the business data herein may include real-time stock market quotation data, for example.

In one example, the business data herein may be real-time event data or the like.

In one example, the business data herein may be real-time inventory data or the like.

The service data may include text, graphics, images, tables, and the like.

In this embodiment, the component container is displayed in the session interface of the target session; displaying at least one component instance comprising a target component instance in a component container; the target component example comprises preset service data. The method and the device realize that the component instance is displayed in the session interface corresponding to the session user, and the component instance comprises the service data, so that the third-party service data except the session focused by the session user is displayed in the session interface in a component mode. The operation of the session user for acquiring the service data is reduced, and the efficiency of the session user for acquiring the service data is improved.

In some embodiments, the above information processing method further includes the steps of:

firstly, generating a component creation instruction according to a component creation operation of a user; the component creation operation is used for creating a target component of the target session, and the component creation instruction comprises identification information of the service data.

In these embodiments, the user may perform the component creation operation in the session interface of the target session. Illustratively, a component creation control for creating a component may be displayed in the session interface described above. After detecting the triggering operation of the user on the component creation control, the user can also execute the selection operation on the information of the service data to execute the selection operation. The information of the service data includes information for uniquely representing the service data, such as address information of the service data. The above-described operation of the user can be regarded as a component creation operation of the received user.

The execution body may generate the component creation instruction including the identification information of the target session information and the service data according to the component creation operation.

And secondly, sending a component creation instruction to the service data server so that the service data server generates a session component creation request according to the component creation instruction, and sending the session component creation request to the session server so that the session server creates the target component.

And finally, receiving the target component instance sent by the session server, displaying the target component instance on a session interface of the target session, and generating the target component instance for the service data acquired by the session server.

The service data server generates a session component creation request after receiving the component creation instruction. The session component creation request includes the target session identification and address information of the service data. The session component creation request is then sent to the session server. The session server may create the target component according to the session component creation request, and generate the target component instance according to the service data acquired from the service data server according to the address information. The session server may send the target component instance to a client of the target session to cause the client to display the target component instance in a session interface of the target session.

In these embodiments, creation of the target component may be initiated by the session user, thereby enabling user configurability of the component, which may enhance the user experience.

In some embodiments, the above information processing method further includes:

first, a preview identification of a target component sent by a session server is received, the preview identification being generated by the session server when the target component is created.

Secondly, in response to detecting that the local component instance which is not matched with the preview identification is detected, sending a request for obtaining the instance to a session server, receiving the component instance sent by the session server, binding the component instance with a target component, and generating the target component instance; or alternatively

And in response to detecting that the local component instances with the preview identifications are matched, binding the component instances with the target component to generate the target component instance.

In these embodiments, the session server may generate a preview identification (PreviewID) of the target component after the target component is created. The session server may associate the preview identification with address information of the service data and the created target component, respectively. The session server may send the target component and the preview identifier to the execution body. After receiving the target component and the preview identifier, the execution body may locally detect whether there is a component instance matching the preview identifier. If the component instance matched with the preview identifier is found locally, the component instance can be directly bound with the target component, so that the execution body obtains the target component instance.

If no component instance matching the preview identifier is detected locally, the executing entity may send a request to the session server to obtain the instance. The session server may locally search for whether there is a component instance matching the preview identifier, and if so, send the component instance to the execution body. If the session server does not find a component instance matching the preview identifier locally, a data acquisition request may be sent to the service data server. The data acquisition request may include address information of the service data. The service data server may send the service data and/or the display style matching the preview identifier to the session server after receiving the data acquisition request. The session server may generate the target component instance after receiving the service data and/or the display style. Binding the target component instance with the preview identification of the target component. And sending the target component instance to the execution body.

In these embodiments, the execution body may first find locally whether the component instance matches the target component, and if so, directly generate the target component instance using the local component instance. If there is no component instance matching the target component locally, the component instance is obtained from the session server, so that the target component instance can be quickly displayed by using the component instance stored locally by the execution body. The speed of displaying the target component instance in the session interface of the target session may be improved to some extent.

In some embodiments, the above information processing method further includes: in response to receiving an instruction for deleting a component sent by a user on a session interface of a target session, sending component deleting information for deleting the component indicated by the instruction to a session server; and deleting the stored information of the component locally.

In these embodiments, the component container is displayed in the session interface of the target session described above. At least one component may be displayed in the component container. For any one component, the user may issue an instruction to delete the component. For example, a delete control may be displayed in the display area of each component. The user can execute triggering operation on the deletion control of the display area of the component, so as to send a component deletion instruction of the component to the execution body.

The execution body may generate the component deletion information after receiving the component deletion instruction. The component deletion information may include a component identification of the component indicated by the instruction to delete the component. After receiving the component deletion information, the session server may destroy the service data and/or the information of the display style of the component indicated by the component identifier and the information of the component in the session server.

In addition, the execution body may delete the locally stored information of the component, including information such as a display style and/or service data of the component.

In these embodiments, the user may delete the component indicated by the instruction at the client and at the session server, so as to provide convenience for the user to maintain the component displayed in the display interface of the session.

Referring to fig. 5, fig. 5 is a flowchart illustrating a method for processing information according to an embodiment of the disclosure. The method comprises the following steps:

s501: a session component creation request is generated, the session component creation request including address information of the service data and a target session identification.

S502: a session component creation request is sent to a session server of the target session to cause the session server to create the target component.

In this embodiment, the execution subject of the information processing method may be a service data server.

The traffic data server may be a different server than the session server. The service data server may store different service data. In some application scenarios, these traffic data may be data that is not related to the messages of the target session.

The traffic data may be data of interest to a majority of session users of the target session.

In some embodiments, the service data server may access certain service data according to a plurality of users in the detected target session, and may actively generate a session component creation request. The session component creation request includes the target session identification and address information of the service data. And sends the session component creation request to the session server. The session server creates the target component after receiving the session component creation request. The session server may bind the created target component with the target session identification.

The target session may be a session indicated by a target session identification.

In some embodiments, the step S501 includes: and generating a component creation request in response to receiving an instruction for creating the target component sent by a session user of the target session, wherein the instruction comprises a target session identifier and identification information of service data.

In these embodiments, the session user may be any session user in the target session.

The session user may issue the create target component instruction described above to the business data. For example, the session user clicks a control for creating the session component in the session interface, enters the session component creation interface, and then triggers the service data (for example, clicks a display interface corresponding to the service data), so that the above operations carry the information of the target session identifier and the service data. The client of the session user may generate a create target component instruction that includes a target session identification and information for the business data (e.g., an identification of the business data). And the terminal equipment sends the instruction for creating the target component to a service data server.

In these embodiments, the session user may issue a component creation instruction according to the requirement to create a component for displaying service data, so that the created component has a high degree of matching with the user.

After receiving the instruction for creating the target component, the service data server determines the address information of the service data and encapsulates the address information of the service data and the target session identifier into a session component creation request.

The service data server may send the session component creation request to a session server (i.e., an instant messaging application server) of the target session.

After receiving the session component creation request, the session server may create a target component and then bind the target component with the target session identifier.

S503: transmitting service data to a session server; so that the session server generates the target component instance from the service data.

In some embodiments, the session server may issue a service data acquisition request to the server after the target component is created. The service data server may send the service data to the session server according to the request.

In some embodiments, the service data server may actively send the service data to the session server.

After receiving the service data, the session server may associate the service data with a preset element of the target component, and then generate rendering information of the target component, thereby generating a target component instance.

In some embodiments, the service data server may further send a display style of the service data to the session server. So that the session server generates a target component instance according to the display style and the service data.

The display style herein may be a display style for displaying service data.

The display style herein includes background color, number of windows, window size, window layout, character/symbol color, character/symbol size, font, image/graphic size, and the like.

In these embodiments, the service data server provides a display style for displaying service data, so that the session server does not need to determine the display style of the service data, thereby simplifying the step of generating the target component instance by the session server, reducing the resource consumption of generating the target component by the session server, improving the speed of generating the target component by the session server, and further improving the overall efficiency of generating the target component until the target component instance is displayed on the session interface of the target session.

In some embodiments, the above information processing method further includes:

in response to detecting the change in the business data and/or the display style, change information is sent to the session server to cause the session server to update the target component instance.

In these embodiments, for the target component for which an instance has been generated, the service data server may actively detect whether the service data and/or the display pattern changes, for example, at intervals of a preset time.

When it is detected that at least one of the service data and the display style is changed, change information may be generated. The change information includes update information describing service data and/or a display style.

In one example, the business data is changed. When it is detected that the service data D1 is changed to the service data D2, change information of the service data is generated. The change information includes description information of the change of the service data D1 to the service data D2. In this way, after receiving the change information, the session server can replace the service data D1 in the original target component instance with the service data D2, and then send the target component instance with the service data D2 replaced to the client corresponding to the session user; or sending the instance change information indicating that the service data D1 in the target component instance is replaced by the service data D2 to the client corresponding to the target session. So that the client displays the updated target component instance when displaying the target session.

In one example, the display style is changed. When it is detected that the display style is changed from C1 to C2, for example, the background color is changed, change information is generated. The change information includes description information of the change of the background color from C1 to C2. After receiving the change information, the session server may replace the background color C1 in the original target component instance with the background color C2, and then send the target component instance with the replaced background color to the client of the session user, or send the instance change information indicating that the background color C1 of the target component is replaced with the background color C2 to the client corresponding to the target session, so that the client displays the updated target component instance when displaying the target session.

In these embodiments, by detecting that the service data and/or the display style changes, the change information corresponding to the change is sent to the session server, and the session server updates the target component instance, so that the target component instance displayed on the target session interface can be dynamically updated according to the change of the service data, and further, the user of the target session can timely learn about the latest service data in the session interface, and the efficiency of the user to acquire the third-party service data can be further improved.

In some embodiments, the above information processing method further includes:

firstly, receiving an acquisition request for acquiring update information of service data and/or display patterns sent by a session server, and detecting whether the service data and/or the display patterns are updated.

And if the detection result is yes, sending the update information to the session server so that the session server updates the target component container instance.

In these embodiments, the service data server may receive the above-described acquisition request sent by the session server, and then detect whether the service data and/or the display style is updated. And if the service data and/or the display style are/is detected to be updated, generating update information. The content included in the update information may refer to the change information actively generated by the service data.

That is, in these embodiments, the service data may passively detect whether the service data and/or the display style is updated according to the acquisition request of the update information from the session server. Thereby being beneficial to actively controlling the updating of the service data and/or the display style by the session server. Thereby facilitating control of content in the target component instance displayed at the session interface of the target session.

In these embodiments, whether the service data and/or the display style are updated is actively or passively detected by the service data server, and update information or change information of the service data and/or the display style is sent to the session server to update the target component instance, so that the target component instance can be ensured to be updated in time, and further, the target session user can acquire the updated target component instance in time in the session interface.

Referring to fig. 6, a schematic flow chart of the information processing method of the present disclosure is shown.

As shown in fig. 6, the service data server in step 1 may send a Widget component registration request to the session server, where the request carries a URL. The registration request may be considered a session component creation request. And 2, the session server creates a target component according to the session creation request. And 3, the session server creates a preview identifier (preview ID) of the target component, associates the preview identifier with the URL and stores the association. In step 4, a client (e.g., an instant messaging application client) may send a get component list request to a session server. In step 5, the session server may send a component list including the target component preview identification to the client. After receiving the component list, the client may locally find out, for each preview identifier in the component list, whether there is a corresponding component instance. If yes, step 7, binding the component instance into the component indicated by the matched preview identification, and generating the component instance. For locally missing component instances (target component instances), the client performs step 8, sending a component instance acquisition request to the session server, the component instance acquisition request including a preview identification of the component. Step 9, after receiving the component instance obtaining request, the session server searches the target component instance matching with the preview identifier locally, if yes, step 12 is executed, and the target component instance is sent to the client. If the session server lacks the target component instance locally, step 10 is performed, and a display style and/or a service data acquisition request is sent to the service data server. The request includes address information. After receiving the request, the service data server may locally extract the display style and/or service data matching the address information, and then execute step 11, send the display style and/or service data matching the address information to the session server, and generate, by the session server, the target component instance according to the target component and the display style and/or service data. The session server then performs step 12 of sending the target component instance to the client to cause the client to display the target component instance in the display interface of the target session.

Fig. 7 is a block diagram of an information processing apparatus according to an embodiment of the present disclosure, corresponding to the information processing method of the embodiment shown in fig. 1 above. For ease of illustration, only portions relevant to embodiments of the present disclosure are shown. Referring to fig. 7, the apparatus 70 includes: a creation unit 701, an acquisition unit 702, an instantiation unit 703, and a first display unit 704. Wherein:

a creating unit 701, configured to create a target component according to a received session component creation request, where the session component creation request includes a target session identifier and address information of service data;

an obtaining unit 702, configured to obtain service data according to address information;

an instantiation unit 703, configured to instantiate a target component according to service data;

a first display unit 704, configured to display the target component instance in the session interface indicated by the target session identifier.

In some embodiments of the present disclosure, the obtaining unit 702 is further configured to:

acquiring a display style according to the address information; and

the instantiation unit 703 is further configured to:

the target component is instantiated according to the display style and the business data.

In some embodiments of the present disclosure, the creation unit 701 is further configured to:

receiving a session component creation request sent by a service data server through a component creation interface;

The target component is created using the component add interface.

In some embodiments of the present disclosure, the creation unit 701 is further configured to: a target component abstract instance is created from the session component creation request.

In some embodiments of the present disclosure, the information processing apparatus 70 further includes an association unit (not shown in the drawings) for:

creating a preview identifier corresponding to the target component, and associating the preview identifier with the address information;

transmitting the preview identification to a client of a user of the target session; and

the acquisition unit 702 is further configured to:

In some embodiments of the present disclosure, the information processing apparatus further includes a first updating unit (not shown in the drawings). The first updating unit is used for:

acquiring updated service data and/or display patterns;

and updating the target component instance according to the updated service data and/or the display style.

In some embodiments of the present disclosure, the information processing apparatus further includes a second updating unit (not shown in the drawings). The second updating unit is used for:

In some embodiments of the present disclosure, the information processing apparatus further includes a first deletion unit (not shown in the drawings). The first deleting unit is used for:

Fig. 8 is a block diagram of an information processing apparatus according to an embodiment of the present disclosure, corresponding to the information processing method of the embodiment shown in fig. 3 above. For ease of illustration, only portions relevant to embodiments of the present disclosure are shown. Referring to fig. 8, the apparatus 80 includes: a second display unit 801 and a second display unit 802. Wherein:

fig. 8 is a block diagram of a text format setting apparatus according to an embodiment of the present disclosure, corresponding to the information processing method of the above embodiment. For ease of illustration, only portions relevant to embodiments of the present disclosure are shown. Referring to fig. 8, the apparatus 80 includes: a second display unit 801 and a second display unit 802. Wherein:

A second display unit 801 for displaying the component container in a session interface of the target session;

a third display unit 802 for displaying at least one component instance including the target component instance in the component container; the target component example comprises preset service data.

In some embodiments of the present disclosure, the second display unit 801 is further configured to: the session interface also displays at least a portion of the session message for the target session.

In some embodiments of the present disclosure, a component container is displayed at the top of the session interface, with a single component instance displayed in the component container; the third display unit 802 is further configured to:

In some embodiments of the present disclosure, the information processing apparatus further includes a first creation unit (not shown in the drawings) for:

generating a component creation instruction according to the component creation operation of the user; the component creation operation is used for creating a target component of the target session, and the component creation instruction comprises identification information of service data and identification information of the target session;

Sending a component creation instruction to the service data server so that the service data server generates a target component creation request according to the component creation instruction, and sending the target component creation request to the session server so that the session server creates a target component;

and receiving a target component instance sent by the session server, displaying the target component instance on a session interface of the target session, and generating the target component instance for service data acquired by the session server.

In some embodiments of the present disclosure, the information processing apparatus further includes a preview unit (not shown in the drawings) for:

receiving a preview identification of a target component sent by a session server, wherein the preview identification is generated by the session server when the target component is created;

responding to the detection that the local component instance which is not matched with the preview identification is not available, sending a request for obtaining the instance to a session server, receiving the component instance sent by the session server, binding the component instance with a target component, and generating the target component instance; or alternatively

In some embodiments of the present disclosure, the information processing apparatus further includes a second deletion unit (not shown in the drawing) for:

in response to receiving an instruction for deleting a component sent by a user on a target session interface, sending component deleting information for deleting the component indicated by the instruction to a session server; and deleting the stored information of the component locally.

Fig. 9 is a block diagram of a text format setting apparatus according to an embodiment of the present disclosure, corresponding to the information processing method of the above embodiment. For ease of illustration, only portions relevant to embodiments of the present disclosure are shown. Referring to fig. 9, the apparatus 90 includes: a generating unit 901, a first transmitting unit 902 and a second transmitting unit 903. Wherein:

a generating unit 901, configured to generate a session component creation request, where the session component creation request includes address information of service data and a target session identifier;

a first sending unit 902, configured to send a session component creation request to a session server of a target session, so that the session server creates the target component;

a second sending unit 903, configured to send service data to a session server; so that the session server generates the target component instance from the service data.

In some embodiments of the present disclosure, the generating unit 901 is further configured to:

and generating a component creation request in response to receiving an instruction for creating the target component sent by a session user of the target session, wherein the instruction comprises a target session identifier and identification information of service data.

In some embodiments of the present disclosure, the information processing apparatus further includes a third updating unit (not shown in the figure). The third updating unit is used for:

in response to detecting the change of the service data and/or the display style, sending change information to the session server so that the session server updates the target component instance; or alternatively

Receiving an acquisition request for acquiring update information of service data and/or display patterns sent by a session server, and detecting whether the service data and/or the display patterns are updated or not;

if the detection result is yes, the updating information is sent to the session server, so that the session server updates the target component container instance.

In order to achieve the above embodiments, the embodiments of the present disclosure further provide an electronic device.

Referring to fig. 10, there is shown a schematic structural diagram of an electronic device 1000 suitable for implementing embodiments of the present disclosure, where the electronic device 1000 may be various terminal devices, servers. The terminal device may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a personal digital assistant (Personal Digital Assistant, PDA for short), a tablet (Portable Android Device, PAD for short), a portable multimedia player (Portable Media Player, PMP for short), an in-vehicle terminal (e.g., an in-vehicle navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. Etc. The electronic device shown in fig. 10 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 10, the electronic apparatus 1000 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 1001 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1002 or a program loaded from a storage device 1008 into a random access Memory (Random Access Memory, RAM) 1003. In the RAM 1003, various programs and data necessary for the operation of the electronic apparatus 1000 are also stored. The processing device 1001, the ROM 1002, and the RAM 1003 are connected to each other by a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.

In general, the following devices may be connected to the I/O interface 1005: input devices 1006 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 1007 including, for example, a liquid crystal display (Liquid Crystal Display, LCD for short), a speaker, a vibrator, and the like; storage 1008 including, for example, magnetic tape, hard disk, etc.; and communication means 1009. The communication means 1009 may allow the electronic device 1000 to communicate wirelessly or by wire with other devices to exchange data. While fig. 10 shows an electronic device 1000 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via the communication device 1009, or installed from the storage device 1008, or installed from the ROM 1002. The above-described functions defined in the method of the embodiment of the present disclosure are performed when the computer program is executed by the processing device 1001.

It should be noted that the computer readable storage medium described above in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The computer-readable medium carries one or more programs (computer-executable instructions) that, when executed by the electronic device, cause the electronic device to perform the methods shown in the above-described embodiments.

Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (Local Area Network, LAN for short) or a wide area network (Wide Area Network, WAN for short), or it may be connected to an external computer (e.g., connected via the internet using an internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. Where the name of the unit does not constitute a limitation of the unit itself in some cases, for example, the creation unit may also be described as "a unit that creates a target component from a received session component creation request".

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).

Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.

Claims

1. An information processing method, comprising:

acquiring the service data according to the address information;

instantiating the target component according to the service data;

2. The method of claim 1, wherein said obtaining said service data from said address information further comprises:

acquiring a display style according to the address information; and

said instantiating said target component from said business data comprising:

and instantiating the target component according to the display style and the service data.

3. The method of claim 1, wherein creating the target component from the received session component creation request comprises:

Receiving the session component creation request sent by a service data server through a component creation interface;

the target component is created using the component add interface.

4. The method of claim 1, wherein creating the target component from the received session component creation request comprises:

and creating a target component abstract instance according to the session component creation request.

5. The method according to claim 1, wherein the method further comprises:

the obtaining the service data according to the address information includes:

responding to a browsing request sent by the client for browsing the target component instance, and acquiring the service data according to the address information; wherein the browse request includes the preview identification.

6. The method according to claim 1, wherein the method further comprises:

acquiring updated service data and/or display patterns;

7. The method according to claim 1, wherein the method further comprises:

8. The method according to claim 1, wherein the method further comprises:

and deleting the components in the target session indicated by the deleting instruction according to the received deleting instruction of the session components, and sending an instruction for indicating to delete the prestored information of the components to the client of the target session user.

9. An information processing method, comprising:

10. The method according to claim 9, wherein the method further comprises:

The component creation instruction is sent to a service data server, so that the service data server generates a target component creation request according to the component creation instruction, and the target component creation request is sent to a session server, so that the session server creates a target component;

and receiving the target component instance sent by the session server, displaying the target component instance on a display interface of the target session, and generating the target component instance for the service data acquired by the session server.

11. The method according to claim 9, wherein the method further comprises:

responding to the detection that the local component instance which is not matched with the preview identification is not available, sending a request for obtaining the instance to the session server, receiving the component instance sent by the session server, binding the component instance with the target component, and generating a target component instance; or alternatively

And in response to detecting that the local component instances with preview identification matching, binding the component instances with the target component to generate target component instances.

12. The method according to claim 9, wherein the method further comprises:

in response to receiving an instruction of deleting a component sent by a user on the target session interface, sending component deleting information for deleting the component indicated by the instruction to a session server; and deleting the stored information of the component locally.

13. An information processing method, comprising:

generating a session component creation request, wherein the session component creation request comprises address information of service data and a target session identifier;

sending the session component creation request to a session server of a target session so that the session server creates a target component;

14. The method of claim 13, wherein generating a component container creation request comprises:

15. The method of claim 13, wherein the method further comprises:

In response to detecting the change of the service data and/or the display style, sending change information to the session server so that the session server can update the target component instance;

or alternatively, the process may be performed,

receiving an acquisition request for acquiring update information of service data and/or display patterns sent by a session server, and detecting whether the service data and/or the display patterns are updated or not; and if the detection result is yes, sending the updating information to a session server so that the session server updates the target component container instance.

16. An information processing apparatus comprising:

17. An information processing apparatus comprising:

a second display unit for displaying the component container in a session interface of the target session;

18. An electronic device, comprising: a processor and a memory;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory, causing the processor to perform the information processing method according to any one of claims 1 to 15.

19. A computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement the information processing method of any one of claims 1 to 15.