Information processing methods, apparatus, and electronic devices

Abstract

An embodiment of the present disclosure provides an information processing method, an apparatus, and an electronic device. The method includes the steps of: creating a target component in response to a received session component creation request, the session component creation request including 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 a session interface indicated by the target session identifier. The embodiment of the present disclosure realizes creating a session component in a session, instantiating the component using the service data, and displaying the component instance in a session interface corresponding to the session user, thereby displaying third-party service data of interest to the session user in the form of a component in the session interface. This reduces the operation of the session user to acquire service data and improves the efficiency with which the session user acquires service data.

Description

[Technical Field]

[0001] This application claims the priority of Chinese Patent Application No. 202310215689.9 filed on February 28, 2023, and the entire content disclosed in the above Chinese patent application is incorporated herein by reference as part of this application.

[0002] Embodiments of the present disclosure relate to an information processing method, apparatus, and electronic device. [Background Art]

[0003] With the development of communication technology, users can use instant messaging applications to communicate information. Users can launch multiple sessions using instant messaging applications. In a session, real-time information exchange is carried out with at least one contact.

[0004] Messages within a session are usually displayed in the session in the order of generation time.

[0005] All users related to a session may be interested in the same information. The above information may be information other than session content, such as information from a third-party platform. When each user checks the above information, it is necessary to open a page provided by the third-party platform and further view the above information on the page.

[0006] Specifically, the operation for a user within a session to obtain the above information is complex. It is disadvantageous for the user to quickly obtain the information of interest. Therefore, the efficiency of session users obtaining information outside the session is low. [Summary of the Invention] [Means for Solving the Problems]

[0007] The embodiments of this disclosure provide information processing methods, apparatus, and electronic devices to overcome the problem of low efficiency in acquiring information of common interest to users corresponding to a session.

[0008] In the first aspect, the embodiments of the present disclosure are as follows: A step of creating a target component in response to a received session component creation request, wherein the session component creation request includes a target session identifier and address information for service data. A step of obtaining the service data according to the address information, The steps include: instantiating the target component according to the service data; The present invention provides an information processing method that includes the step of displaying a target component instance in the session interface indicated by the target session identifier.

[0009] In a second aspect, embodiments of the present disclosure are as follows: The steps include displaying the component container in the target session's display interface, The information processing method is provided, which includes the steps of displaying at least one component instance, including a target component instance, in the component container, wherein the target component instance includes pre-configured service data.

[0010] In a third aspect, embodiments of the present disclosure are as follows: A step of generating a session component creation request, wherein the session component creation request includes address information of service data and an identifier for the target session. The steps include sending a session component creation request to the session server of the target session, causing the session server to create the target component, The present invention provides an information processing method that includes the steps of sending the service data to the session server and causing the session server to generate a target component instance in accordance with the service data.

[0011] In the fourth aspect, embodiments of the present disclosure are as follows: A creation unit used to create a target component in response to a received session component creation request, wherein the session component creation request includes a creation unit that includes a target session identifier and address information for service data, An acquisition unit used to acquire the service data according to the address information, An instantiation unit used to instantiate the target component according to the service data, The present invention provides an information processing device including a first display unit used to display a target component instance in a session interface indicated by the target session identifier.

[0012] In the fifth aspect, embodiments of the present disclosure are as follows: A second display unit used to display the component container in the display interface of the target session, The present invention provides an information processing device that includes a third display unit used to display at least one component instance, including a target component instance, in the component container, wherein the target component instance includes pre-configured service data.

[0013] In the sixth aspect, embodiments of the present disclosure are as follows: A generation unit used to generate a session component creation request, wherein the session component creation request includes a generation unit that includes service data address information and a target session identifier, A first transmission unit used to send a session component creation request to the session server of the target session and to cause the session server to create the target component, The present invention provides an information processing device including a second transmission unit used to transmit the service data to the session server and to cause the session server to generate a target component instance in accordance with the service data.

[0014] In the seventh aspect, an embodiment of the present disclosure provides an electronic device comprising a processor and a memory, wherein the memory stores computer execution instructions, and the processor executes the computer execution instructions stored in the memory, thereby causing the at least one processor to execute the first, second, and third aspects and various possible information processing methods relating to each of the above aspects.

[0015] In the eighth aspect, an embodiment of the present disclosure provides a computer-readable storage medium that stores computer execution instructions, and when a processor executes the computer execution instructions, it realizes the first aspect, the second aspect, the third aspect and various possible information processing methods relating to each of the above aspects.

[0016] In the ninth aspect, an embodiment of the present disclosure includes a computer program, which, when executed by a processor, provides a computer program product that realizes the first, second, and third aspects and various possible information processing methods relating to each of the above aspects.

[0017] To more clearly illustrate the technical concepts of the embodiments of this disclosure, the drawings that may be used in the embodiments are briefly described below. As will be apparent, the drawings in the following description are some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these without any creative work. [Brief explanation of the drawing]

[0018] [Figure 1]FIG. 1 is a flowchart 1 of an information processing method according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a flowchart 2 of an information processing method according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a flowchart 3 of an information processing method according to the present disclosure. [Figure 4A] FIG. 4A is a schematic diagram of one session interface of a target session according to the present disclosure. [Figure 4B] FIG. 4B is a schematic diagram of one session interface of a target session according to the present disclosure. [Figure 4C] FIG. 4C is a schematic diagram of one session interface of a target session according to the present disclosure. [Figure 5] FIG. 5 is a flowchart 4 of an information processing method according to the present disclosure. [Figure 6] FIG. 6 is a principle flowchart of an information processing method according to the present disclosure. [Figure 7] FIG. 7 is a block diagram of a configuration of an information processing apparatus according to an embodiment of the present disclosure. [Figure 8] FIG. 8 is a block diagram of a configuration of an information processing apparatus according to an embodiment of the present disclosure. [Figure 9] FIG. 9 is a block diagram of a configuration of an information processing apparatus according to an embodiment of the present disclosure. [Figure 10] FIG. 10 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

[0019] In order to make the objectives, technical solutions, and advantages of the embodiments of the present disclosure clearer, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings of the embodiments of the present disclosure. As is clear, the described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of the present disclosure without creative labor belong to the protection scope of the present disclosure.

[0020] In instant messaging applications, a single session typically involves at least two users. The session interface may display session details, such as at least one message from the session users.

[0021] In addition to exchanging information with other session users, session users may also be interested in some information from third-party platforms.

[0022] When a session user needs information from a third-party platform, they must access the third-party platform's page and then view the information there. If multiple users within a session are interested in the same information, they must each open the third-party platform's page on their respective devices to view it. This results in a long total time for users within a session to access the information, and a low overall efficiency in obtaining that information.

[0023] To improve the above-mentioned problems, the solution relating to this disclosure creates a target component corresponding to a session, generates a target component instance in accordance with service data other than session messages, displays the target component instance in the session interface, thereby enabling all users of the session to view the service data in the session interface and improving the efficiency of session users in obtaining service data other than session messages.

[0024] As shown in Figure 1, Figure 1 is a flowchart 1 of an information processing method according to an embodiment of the present disclosure. The method includes steps S101 to S104.

[0025] S101: Create a target component in response to a received session component creation request. The session component creation request includes the target session identifier and service data address information.

[0026] The entity executing the information processing method in this embodiment may be a session server (also known as an instant messaging application server). For example, a server that provides message transfer and message storage to each party in a session.

[0027] Furthermore, the session server can also provide the client with display layout information for each element within the session interface.

[0028] In this embodiment, the display layout information provided by the session server to the client includes information about the component container.

[0029] Multiple components may be managed using the component container described above. In the case of a component container associated with a component, the server can set the display position of each component within that component container. Each component (for example, a Widget component) is independent of each other and does not interfere with one another.

[0030] The above session component creation request is used to create a component that will be displayed in the session interface for a single target session. The target session here can be various types of sessions, such as a single session or a group session. The component to be created can be called the target component.

[0031] The above session creation request includes the target session identifier and the address information of the service data.

[0032] The target session identifier may include letters, alphabets, or symbols. The session identifier can distinguish between different sessions.

[0033] The service data referred to here may be data of interest to the majority of session users within the target session. The service data referred to here may also be data other than session messages, such as data from a third-party platform.

[0034] For example, the service data here may include, for instance, real-time stock market data.

[0035] For example, the service data here could be real-time match status data, for instance.

[0036] For example, the service data here could be real-time inventory data, for instance.

[0037] The service data here may include text, graphics, images, forms, etc.

[0038] The above address information refers to the address information that stores service data. This address information may include, for example, a Uniform Resource Locator (URL).

[0039] The above-mentioned implementing entity can obtain service data from the address indicated by the address information.

[0040] In this embodiment, the session component may be any other component. In some embodiments, the component may be, for example, a microcomponent (Widget component).

[0041] By using microcomponents, it is possible to meet user needs such as simplicity, clarity, appropriate presentation, and personalization / customization.

[0042] A microcomponent can be a structured description of a view, primarily storing configuration information related to view rendering, including layout, rendering attributes, and event response information. Typically, a microcomponent consists of three main parts: a bounding box, a framework, and the widget's shape controls and other elements.

[0043] In some embodiments, the session component creation request here may be sent by the session user to a client for conducting the session. The client may run on a terminal device. The client may also be an instant messaging application client.

[0044] In some embodiments, the session component creation request here may be sent by a server of service data of interest to the session user.

[0045] In these embodiments, the service data server can proactively send the session component creation request to the session server.

[0046] In some embodiments, step S101 above is performed First, the service data server receives a session component creation request sent through the component creation interface, Next, the process includes the step of creating a target component using the component addition interface.

[0047] In these embodiments, the execution entity can provide a component creation interface, such as a microcomponent creation interface (CreateWidget). The service data server can use the component creation interface to send a session component creation request to the session server. For example, the service data locally calls the component creation interface provided by the session server and inputs parameters such as the service data's address information and the type of the target component into the component creation interface.

[0048] The session server can create target components according to the component addition interface provided by the local side (for example, the micro-component addition interface AddChatWidgets).

[0049] In these embodiments, the session server can receive session component creation requests sent by service data through the component creation interface and create target components using the component addition interface. In other words, the session server can create target components using component processing functions pre-provided on the session server's local side, thereby increasing the speed of target component creation.

[0050] In some embodiments, step S101 includes the step of creating a target component abstract instance in response to a session component creation request.

[0051] In these embodiments, after receiving the session component creation request, the execution entity can first create a target component abstract instance according to the pre-configured abstract instance creation rules.

[0052] The target component abstract instance may include the target component's bounding box, framework, and basic controls.

[0053] In these embodiments, a target component instance can be obtained by populating an abstract instance of the target component with service data, or by populating an abstract instance of the target component with service data according to a specified display style.

[0054] S102: Retrieves service data according to address information.

[0055] The above address information may include storage addresses for service data, such as URLs, which are standard resource addresses for service data on the Internet. URLs typically include the mode (or protocol), server name (or IP address), path, and file name, for example, "protocol: / / allow / path?query". A relatively complete example of a URL is protocol: / / username:password@subdomain name.domain name.top-level domain name:port number / directory / file name.file extension?parameter=value#flags.

[0056] The above-mentioned implementing entity can obtain service data from the service data server according to the address information via a wired or wireless communication connection.

[0057] S103: Instantiate the target component based on the service data.

[0058] After obtaining the above service data, the target component can be instantiated using a pre-configured component instantiation method. During the process of instantiating the target component, the service data is populated into the target component. For example, the service data can be bound to an element (Element) that is pre-configured to transmit the above service data within the target component. Next, rendering information for each element of the target component is generated. This is how the target component instance is obtained.

[0059] S104: Displays the target component instance in the session interface indicated by the target session identifier.

[0060] The session interface here may be the session interface of the target session indicated by the target session identifier. The session interface here may also be the session interface corresponding to at least one session user of the target session.

[0061] In this embodiment, the execution entity sends the target component instance to each of the session users of the target session (for example, an instant messaging application client), and causes the clients to display the target component instance in the session interface of the target session.

[0062] In practice, the session interface described above can display the session messages and target component instances of the target session.

[0063] The above target component instance may also be displayed in the session interface's component container.

[0064] In this embodiment, a target component is created in response to a received session component creation request. The session component creation request includes a target session identifier and address information for service data. Service data is retrieved according to the address information, the target component is instantiated according to the service data, and the target component instance is displayed in the session interface indicated by the target session identifier. This realizes the creation of a session component within a session, instantiates the component using service data, and displays the component instance in the session interface corresponding to the session user. This thereby displays service data other than session messages of interest to the session user in the form of a component. This reduces the operation required for the session user to retrieve third-party service data and improves the efficiency of the session user in retrieving the service data.

[0065] As shown in Figure 2, Figure 2 is a flowchart 2 of an information processing method according to an embodiment of the present disclosure. The method includes steps 201 to 204.

[0066] S201: Creates a target component in response to a received session component creation request. The session component creation request includes the target session identifier and service data address information.

[0067] In this embodiment, the entity executing the information processing method may be a session server.

[0068] For specific implementation of steps S201 and S204, refer to steps S101 and S104 of the embodiment shown in Figure 1, and a redundant explanation will be omitted here.

[0069] S202: Retrieves display style and service data according to address information.

[0070] Service data and the display style of the service data may be stored on the service data server. The address information may include a uniform resource locator corresponding to the physical address that stores the display style and service data.

[0071] The above display style may also be the display style for service data. This includes, but is not limited to, background color, number of windows, window size, window layout, text / symbol color, text / symbol size, font, image / graphic size, etc.

[0072] The above-mentioned implementing entity can obtain the display style and service data from the service data server according to the above address information.

[0073] S203: Instantiates the target component according to the display style and service data.

[0074] The above-mentioned execution entity can instantiate the target component according to the above-mentioned display style and service data using the instantiation method, thereby obtaining a target component instance.

[0075] S204: Displays the target component instance in the session interface indicated by the target session identifier.

[0076] In this embodiment, since the service data server provides a display style for displaying the service data, the session server does not need to determine the display style for the service data. This simplifies the step of the session server generating the target component, reduces the resource consumption of the session server when generating the target component, increases the speed at which the session server generates the target component, and further improves the overall efficiency from the generation of the target component to the display of the target component instance in the session interface of the target session.

[0077] In some embodiments of the information processing method shown in Figures 1 and 2, the information processing method further includes the following steps.

[0078] First, create a preview identifier corresponding to the target component, and then associate the preview identifier with the address information.

[0079] Next, the preview identifier is sent to the target session's user client.

[0080] Step S102 in the embodiment shown in Figure 1 and step S202 in the embodiment shown in Figure 2 are, A step of receiving a view request from a client of a target session to view a target component instance, and retrieving service data according to address information, wherein the view request includes a preview identifier.

[0081] In these embodiments, the execution entity can create a target component (an abstract instance of the target component) in response to a session component creation request, and then generate a preview identifier (PreviewID) for the target component. The execution entity can associate the preview identifier with the address information. Next, it sends the preview identifier to a client that displays the target session (for example, an instant messaging application client).

[0082] The user can initiate a browsing operation to view the target component instance in the session interface of the target session described above. The client searches whether a component instance matching the preview identifier is stored locally, and if yes, it binds the local component instance to the target component and creates a target component instance.

[0083] The client may generate a browsing request if it cannot find a component instance matching the preview identifier locally, and this browsing request may include the preview identifier. The client may send the browsing request to the session server, and if the session server cannot find a component instance corresponding to the preview identifier locally, it may retrieve the address information associated with the preview identifier. Next, it retrieves service data from the service data server according to the address information.

[0084] In these embodiments, after creating the target component, a preview identifier associated with the address information is generated, and then the preview identifier is sent to the client. The client then retrieves service data locally or through the session server according to the preview identifier, thereby generating an instance of the target component, which is advantageous for managing different components.

[0085] In some embodiments of the information processing method shown in Figures 1 and 2, the information processing method further includes the following steps.

[0086] First, retrieve the updated service data and / or display style.

[0087] Next, update the target component instance according to the updated service data and / or display style.

[0088] In these embodiments, the executing entity can send an update information acquisition request to the service data server at pre-set time intervals. The service data detects whether the service data and / or display style have been updated in response to the acquisition request. If it detects that the service data and / or display style have been updated, it generates update information including the updated service data and / or display style.

[0089] The above-mentioned execution entity, after receiving the updated service data and / or display style, updates the target component instance according to the updated service data and / or display style.

[0090] In these embodiments, the session server can retrieve updated service data for the target component instance and then update the target component instance. This is advantageous for the session server to proactively update the target component instance in response to service data updates. Furthermore, it is advantageous for controlling the content within the target component instance that is displayed in the session interface of the target session.

[0091] In some embodiments of the information processing method shown in Figures 1 and 2, the information processing method is as follows: If a change in the target component instance is detected, the step of pushing information about the changed target component instance to the client of the user in the target session further includes the step of the change being generated by updated service data and / or display styles sent by the service data server.

[0092] In these embodiments, the service data server can actively detect whether the service data and / or display style have changed, for example, by detecting once at pre-set time intervals whether the service data and / or display style have changed.

[0093] If the system detects that at least one of the service data and / or display style has changed, it can send the updated service data and / or display style to the session server. The session server updates the target component instance according to the updated service data and / or display style, thereby causing a change in the target component instance. The system can then send information about the changed target component instance to the client. This information may include the updated service data and / or style within the target component instance, and information indicating the updated service data and / or style.

[0094] After the client receives information about the target component instance after the above changes, it can display the updated target component instance locally in response to the above message.

[0095] In these embodiments, when the session server detects that the target component instance has changed in response to information pushed from the service data server, it pushes information about the changed target component instance to the client, thereby enabling the client to view the updated target component instance, allowing users of the target session to access the latest service data in a timely manner within the session interface, and improving the efficiency of users in obtaining service data other than session messages.

[0096] In some embodiments of the information processing method shown in Figures 1 and 2, the information processing method is as follows: The process further includes, in response to a received command to delete a session component, deleting the component in the target session indicated by the deletion command and sending a command to the target session user's client instructing the deletion of the pre-stored information about the component.

[0097] In these embodiments, the delete command may be generated by the session user's client in response to a component delete operation issued by the session user in the session interface. The delete command includes identifier information of the component to be deleted, such as the component's preview identifier information.

[0098] After receiving the deletion command, the executing entity can locally delete component instances of components such as display styles and service data, delete the component's preview identifier and the address information associated with the preview identifier, and finally delete the component.

[0099] Furthermore, the executing entity may send a command to the client instructing it to delete the pre-stored information about the component. In response to the command, the client may delete all locally pre-stored information about the component.

[0100] In these embodiments, the above deletion command can delete components within the target session, which is advantageous for maintaining components within the session.

[0101] As shown in Figure 3, Figure 3 is a flowchart 3 of an information processing method according to an embodiment of the present disclosure. The method includes steps S301 to S302.

[0102] S301: Display the component container in the session interface of the target session.

[0103] In this embodiment, the execution entity may be a terminal device. Specifically, it may be a client capable of conducting sessions, running on a terminal device, such as an instant messaging application client.

[0104] The target session here may be any type of session, such as a single session or a group session.

[0105] The above session interface may be a session interface that displays messages for the target session, or a session interface that displays the calendar for the target session, and so on.

[0106] The component container here may be pre-created and is used to store at least one component.

[0107] In some application scenarios, the component container may be created by the session server for the target session. The session server can associate the component container with the target session and send it to the client. Depending on the association between the target session and the component container, the client displays the component container when displaying the session interface for the target session.

[0108] In some application scenarios, the above component container may be created by the session server in response to the first component creation request that creates the received target session.

[0109] In some application scenarios, the component container may be hidden within these scenarios, and the target session's session interface may include a container display control to instruct the display of the component container. The user can trigger the container display control. After detecting the user's trigger operation on the container display control, the execution entity can display the component container in the target session's session interface.

[0110] S302: Display at least one component instance in the component container, which includes the target component instance, and the target component instance contains pre-configured service data.

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

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

[0113] When the client displays the above component container, it will display at least one component instance.

[0114] In some application scenarios, the target session's session interface will also display at least some of the target session's session messages.

[0115] In one example, the session interface described above displays a session message display area and a component container display area from left to right. The message display area may display at least one session message from the target session. The component container display area may display multiple components bound to the target session.

[0116] As referenced in Figure 4A, Figure 4A shows one schematic diagram of the session interface of the target session.

[0117] As shown in Figure 4A, the session interface of the target session may include a session flow display area 401, a session message display area 402, and a component container display area 403. As shown in Figure 4A, the target session selected and displayed in the current session interface is Session 3. The session message display area 402 displays the session messages of Session 3. The component container display area 403 may display the component container identifier "Session Component" 4031, and multiple session components such as Session Component 1 and Session Component 2 in Figure 4A.

[0118] In some embodiments, the above session interface is displayed at the top of the session interface, and step S302 is performed. The process includes the step of increasing the display area of ​​the component container in the session interface and displaying the multiple component instances in the component container in response to receiving a first presentation command to display multiple component instances.

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

[0120] As referenced in Figure 4B, Figure 4B shows one schematic diagram of the session interface of the target session.

[0121] As shown in Figure 4B, the current target session is Session 3, and in the session interface 404 of the target session (Session 3), the component container 405 is displayed at the top of the session interface 404. By default, the component container 405 displays one session component, as shown in Session Component 1 in Figure 4B. In the session interface, a session message area 406 may be displayed below the component container 405, and the session message area may display at least some session messages.

[0122] For example, the component container may display a dropdown control, and when a trigger operation performed by the user on the dropdown control is received, it can be considered that the first suggestion command has been received.

[0123] After receiving the above first instruction, the session interface increases the display area of ​​the component container, for example, by extending the display length of the component container downwards. After increasing the display area, more component instances can be displayed in the component container.

[0124] As shown in Figure 4C, Figure 4C is the session interface after the first presentation command has been executed relative to Figure 4B. As shown in Figure 4C, in response to the first presentation command, the display area of ​​the component container 405 increases, that is, the component container is extended, and session components such as session component 1 and session component 2 can be displayed in the extended component container.

[0125] In these embodiments, by default, the component container is fixed to the top and displays one component instance. If the user needs to view multiple component instances, the first presentation command described above is executed, and multiple component instances can be viewed in a component container with an increased display area. This allows one or more component instances to be displayed in the session interface of the target session according to the user's needs.

[0126] The above-mentioned component instances are independent of each other and do not interfere with one another.

[0127] The target component instance described above is one of the at least one component instance described above. The target component instance may be pre-created by the session server, associated with the target session, and then sent to the session user client corresponding to the target session. The target component instance may include pre-configured service data. This pre-configured service data may be determined and obtained by the session server in response to a target component creation request received.

[0128] The service data referred to here may be data of interest to the majority of session users within the target session.

[0129] For example, the service data here may include, for instance, real-time stock market data.

[0130] For example, the service data here could be real-time match status data, for instance.

[0131] For example, the service data here could be real-time inventory data, for instance.

[0132] The above service data may include text, graphics, images, forms, etc.

[0133] In this embodiment, a component container is displayed in the session interface of the target session, and at least one component instance, including the target component instance, is displayed in the component container, with the target component instance containing pre-configured service data. The component instance is displayed in the session interface corresponding to the session user, and the component instance contains service data, thereby displaying third-party service data other than the session that the session user is interested in, in the form of a component, in the session interface. This reduces the operation required for the session user to retrieve the service data and improves the efficiency of the session user in retrieving the service data.

[0134] In some embodiments, the above information processing method further includes the following steps.

[0135] First, a component creation command is generated in response to the user's component creation operation. This component creation operation is used to create the target component for the target session, and the component creation command includes service data identifier information.

[0136] In these embodiments, the user can perform a component creation operation in the session interface of the target session. For example, the session interface may display a component creation control for creating a component. After detecting a trigger operation performed by the user on the component creation control, the user can further perform a selection operation on service data information. This service data information includes information to uniquely represent the service data, such as the service data address. The user's actions can be considered as the reception of the user's component creation operation.

[0137] The above-mentioned execution entity can generate a component creation command that includes target session information and service data identifier information in response to the above-mentioned component creation operation.

[0138] Next, a component creation command is sent to the service data server. The service data server generates a session component creation request in response to the component creation command, sends the session component creation request to the session server, and instructs the session server to create the target component.

[0139] Finally, the system receives the target component instance sent by the session server, displays it in the session interface of the target session, and generates the target component instance from the service data obtained by the session server.

[0140] After receiving the component creation command, the service data server generates a session component creation request. The session component creation request includes a target session identifier and service data address information. Next, the session data server sends the session component creation request to the session server. The session server creates the target component in response to the session component creation request and can generate a target component instance from the service data obtained by the service data server according to the address information. The session server can send the target component instance to the client of the target session, and the client will see the target component instance in the session interface of the target session.

[0141] In these embodiments, the creation of the target component may be initiated by the session user, thereby enabling user-configurable components and improving the user experience.

[0142] In some embodiments, the above information processing method further includes the following steps.

[0143] First, the session server receives the preview identifier of the target component, which is generated when the session server creates the target component.

[0144] Next, in response to detecting that no component instance matching the preview identifier exists locally, a request to obtain an instance is sent to the session server, the component instance sent by the session server is received, the component instance is bound to the target component, and a target component instance is created, or In response to detecting that a component instance matching the preview identifier exists locally, the component instance is bound to the target component, and a target component instance is created.

[0145] In these embodiments, the session server can generate a preview identifier (PreviewID) for the target component after creating it. The session server can associate the preview identifier with the address information of the service data and the created target component, respectively. The session server can send the target component and preview identifier to the execution entity. After receiving the target component and preview identifier, the execution entity can detect whether a component instance matching the preview identifier exists locally. If a component instance matching the preview identifier is found locally, the execution entity can directly bind the component instance to the target component, thereby obtaining the target component instance.

[0146] If the execution entity detects that there is no component instance locally that matches the preview identifier, it can send an instance acquisition request to the session server. The session server can search locally for whether there is a component instance that matches the preview identifier, and if yes, it sends the component instance to the execution entity. If the session server finds that there is no component instance locally that matches the preview identifier, it can send a data acquisition request to the service data server. The data acquisition request may include address information for the service data. After receiving the data acquisition request, the service data server can send the service data and / or display style that matches the preview identifier to the session server. After receiving the service data and / or display style, the session server can create a target component instance. It binds the target component instance to the preview identifier of the target component. It sends the target component instance to the execution entity.

[0147] In these embodiments, the execution entity can first locally search for a component instance that matches the target component. If the answer is yes, it directly creates the target component instance using the local component instance. If no component instance matching the target component exists locally, it retrieves a component instance from the session server, thereby quickly displaying the target component instance using the component instance stored locally on the execution entity. This can improve the speed at which the target component instance is displayed in the target session's session interface to some extent.

[0148] In some embodiments, the information processing method further includes the steps of: receiving a component deletion command sent by a user in the session interface of a target session, sending component deletion information to the session server for deleting the component indicated by the command; and deleting the locally stored information of the component.

[0149] In these embodiments, a component container is displayed in the session interface of the target session. The component container can display at least one component. For any component, the user can send a command to delete that component. For example, a delete control can be displayed in the display area of ​​each component. The user can perform a trigger operation on the delete control in the display area of ​​the component, thereby sending a component delete command to the execution entity.

[0150] The above-mentioned executing entity can generate component deletion information after receiving the component deletion command. This component deletion information may include the component identifier of the component indicated by the component deletion command. After receiving the component deletion information, the session server can discard the service data and / or display style information of the component indicated by the component identifier, as well as the information of the component.

[0151] Furthermore, the executing entity may also delete locally stored information about the component, including information such as the component's display style and / or service data.

[0152] In these embodiments, a user can delete a component on the client and session server sides using a component deletion command, thereby facilitating the user to maintain the components displayed in the session's display interface.

[0153] As shown in Figure 5, Figure 5 is a flowchart 4 of an information processing method according to an embodiment of the present disclosure. The method includes steps S501 to S503.

[0154] S501: Generates a session component creation request, which includes the address information of the service data and the target session identifier.

[0155] S502: Sends a session component creation request to the target session's session server, prompting the session server to create the target component.

[0156] In this embodiment, the entity executing the information processing method may be a service data server.

[0157] The service data server may be a different server from the session server. Different service data may be stored in the service data server. In some application scenarios, this service data may be unrelated to the messages of the target session.

[0158] The service data mentioned above may be data that is of interest to the majority of session users in the target session.

[0159] In some embodiments, a service data server can proactively generate a session component creation request in response to multiple users within a detected target session all accessing specific service data. This session component creation request includes a target session identifier and the address information of the service data. The session data server sends this request to the session server. Upon receiving the request, the session server creates the target component. The session server then binds the created target component to the target session identifier.

[0160] The above target session may be the session indicated by the target session identifier.

[0161] In some embodiments, step S501 is a step of generating a component creation request in response to receiving a target component creation command sent by a session user of the target session, wherein the command includes a target session identifier and service data identifier information.

[0162] In these embodiments, the session user may be any session user within the target session.

[0163] A session user can send the above target component creation command to the service data. For example, a session user clicks a control to create a session component in the session interface, enters the session component creation interface, and then triggers the service data (for example, by clicking the display interface corresponding to the service data), thus ensuring that the above operation carries the target session identifier and service data information. The session user's client can generate a target component creation command, which includes the target session identifier and service data information (for example, the service data identifier). The terminal device then sends the above target component creation command to the service data server.

[0164] In these embodiments, session users send component creation commands according to their needs, create components to display service data, and thereby ensure a high degree of compatibility between the created components and the user.

[0165] After receiving the above target component creation command, the service data server determines the service data address information and encapsulates the service data address information and target session identifier in a session component creation request.

[0166] The service data server can send the above session component creation request to the target session's session server (i.e., the instant messaging application server).

[0167] After receiving the above session component creation request, the session server can create the target component and then bind the target component to the target session identifier.

[0168] S503: Sends service data to the session server and causes the session server to create a target component instance according to the service data.

[0169] In some embodiments, the session server may send a service data retrieval request to the server after creating the target component. The service data server may then send service data to the session server in response to the request.

[0170] In some embodiments, the service data server can proactively send the service data to the session server.

[0171] After receiving the above service data, the session server can associate the service data with pre-configured elements of the target component, then generate rendering information for the target component, and thereby create an instance of the target component.

[0172] In some embodiments, the service data server may also send the display style of the service data to the session server. The session server generates a target component instance according to the display style and the service data.

[0173] The display style used here may also be a display style for displaying service data.

[0174] The display style here includes background color, number of windows, window size, window layout, text / symbol color, text / symbol size, font, image / shape size, etc.

[0175] In these embodiments, the service data server provides a display style for displaying the service data, so the session server does not need to determine the display style for the service data. This simplifies the step of the session server generating target component instances, reduces the resource consumption of the session server generating target components, increases the speed at which the session server generates target components, and further improves the overall efficiency from target component generation to displaying target component instances in the session interface of the target session.

[0176] In some embodiments, the above information processing method is The further step includes sending change information to the session server in response to detecting a change in service data and / or display style, causing the session server to update the target component instance.

[0177] In these embodiments, the service data server can proactively detect whether the service data and / or display style have changed for the target component in which the instance was created, for example, by detecting once at pre-configured time intervals whether the service data and / or display style have changed.

[0178] If it is detected that at least one of the service data and / or display style has been changed, change information can be generated. The change information includes update information describing the service data and / or display style.

[0179] In one example, service data has been changed. If it is detected that service data D1 has been changed to service data D2, change information is generated indicating that the service data has changed. This change information includes a description of the change from service data D1 to service data D2. In this way, after receiving the change information, the session server can replace service data D1 with service data D2 in the original target component instance, and then send the target component instance with the replaced service data D2 to the client corresponding to the session user, or send instance change information instructing the replacement of service data D1 to service data D2 in the target component instance to the client corresponding to the target session. When the client views the target session, it will display the updated target component instance.

[0180] In one example, the display style is changed. After detecting that the display style, for example, the background color, has changed from C1 to C2, change information is generated. This change information includes a description of the change from background color C1 to background color C2. After receiving the change information, the session server can replace background color C1 with background color C2 in the original target component instance and then send the target component instance with the replaced background color to the session user's client, or it can send instance change information instructing the target component to change its background color from C1 to C2 to the client corresponding to the target session, and when the client displays the target session, it will display the updated target component instance.

[0181] In these embodiments, changes in service data and / or display style are detected, change information corresponding to the changes is sent to the session server, the session server updates the target component instance, thereby enabling the target component instance displayed in the target session interface to be dynamically updated in response to changes in service data. Furthermore, users of the target session can grasp the latest service data in the session interface in a timely manner, further improving the efficiency of users in obtaining third-party service data.

[0182] In some embodiments, the above information processing method further includes the following steps.

[0183] First, the system receives a request from the session server to retrieve update information for service data and / or display styles, and detects whether the service data and / or display styles have been updated.

[0184] Next, if the detection result is YES, update information is sent to the session server, causing the session server to update the target component instance.

[0185] In these embodiments, the service data server receives the acquisition request sent by the session server and can then detect whether the service data and / or display style have been updated. If it detects that the service data and / or display style have been updated, it generates update information. The content included in this update information can refer to the change information actively generated by the service data.

[0186] In other words, in these embodiments, the service data can passively detect whether the service data and / or display style have been updated in response to a request for update information from the session server. This is advantageous for the session server to actively control the updates of the service data and / or display style. Furthermore, it is advantageous for controlling the content within the target component instance displayed in the session interface of the target session.

[0187] In these embodiments, the service data server actively or passively detects whether the service data and / or display style have been updated, and sends update or change information for the service data and / or display style to the session server to update the target component instance, thereby ensuring that the target component instance can be updated in a timely manner, and furthermore, the target session user can obtain the updated target component instance in a timely manner in the session interface.

[0188] As shown in Figure 6, this is a flowchart illustrating one principle of the information processing method of the present disclosure.

[0189] As shown in Figure 6, in step 1, the service data server can send a Widget component registration request to the session server, and the request carries a URL. This registration request can be considered a session component creation request. In step 2, the session server creates the target component in response to the session creation request. In step 3, the session server creates a preview identifier (PreviewID) for the target component, associates the preview identifier with the URL, and then stores it. In step 4, the client (e.g., an instant messaging application client) can send a component list retrieval request to the session server. In step 5, the session server can send a component list containing the target component preview identifier to the client. In step 6, after receiving the component list, the client can search for each preview identifier in the component list to see if a corresponding component instance exists locally. If YES, in step 7, the client binds the component instance to the component indicated by the matching preview identifier and creates the component instance. For component instances that do not exist locally (target component instances), the client performs step 8, sending a component instance retrieval request to the session server, and the component instance retrieval request includes the component's preview identifier. In step 9, after receiving the request to retrieve the component instance, the session server searches whether a target component instance matching the preview identifier exists locally. If it does, it executes step 12 and sends the target component instance to the client. If the session server does not find a target component instance locally, it executes step 10 and sends a request to the service data server to retrieve the display style and / or service data. This request includes address information.After receiving the above request, the service data server can extract a display style and / or service data from the local machine that matches the above address information. Next, it performs step 11 and sends the display style and / or service data that matches the address information to the session server, and the session server generates a target component instance according to the target component and the above display style and / or service data. Next, the session server performs step 12 and sends the target component instance to the client, and the client displays the target component instance in the display interface of the target session.

[0190] Corresponding to the information processing method of the embodiment shown in Figure 1 above, Figure 7 is a block diagram of the configuration of an information processing apparatus according to an embodiment of the present disclosure. For convenience of explanation, only the parts relevant to the embodiment of the present disclosure are shown. As shown in Figure 7, the apparatus 70 includes a creation unit 701, an acquisition unit 702, an instantiation unit 703, and a first display unit 704.

[0191] The creation unit 701 is used to create a target component in response to a received session component creation request, and the session component creation request includes a target session identifier and address information for service data. The acquisition unit 702 is used to acquire service data according to address information. The instantiation unit 703 is used to instantiate target components according to service data. The first display unit 704 is used to display the target component instance in the session interface indicated by the target session identifier.

[0192] In some embodiments of this disclosure, the acquisition unit 702 further It is used to obtain the display style according to the address information. The instantiation unit 703 further, It is used to instantiate target components according to their display style and service data.

[0193] In some embodiments of this disclosure, the creation unit 701 further The service data server receives session component creation requests sent through the component creation interface, It is used to create a target component using the component addition interface.

[0194] In some embodiments of this disclosure, the creation unit 701 is further used to create an abstract instance of a target component in response to a session component creation request.

[0195] In some embodiments of this disclosure, the information processing device 70 further includes an association unit (not shown), the association unit is Create a preview identifier corresponding to the target component and associate the preview identifier with the address information. It is used to send a preview identifier to the target session user's client, Acquired unit 702 further, It is used to retrieve service data according to address information in response to receiving a view request from the target session user's client to view the target component instance, and the view request includes a preview identifier.

[0196] In some embodiments of this disclosure, the information processing device further includes a first update unit (not shown). The first update unit is: Retrieving updated service data and / or display styles, It is used to update the target component instance according to updated service data and / or display style.

[0197] In some embodiments of this disclosure, the information processing device further includes a second update unit (not shown). The second update unit is When a change in the target component instance is detected, it is used to push information about the changed target component instance to the client of the user in the target session. The change is generated by updated service data and / or display styles sent by the service data server.

[0198] In some embodiments of this disclosure, the information processing device further includes a first deletion unit (not shown). The first deletion unit is: It is used to delete the component in the target session specified by the received deletion command, and to send a command to the target session user's client instructing the deletion of the pre-stored information about that component.

[0199] Corresponding to the information processing method of the embodiment shown in Figure 3 above, Figure 8 is a block diagram of the configuration of an information processing apparatus according to an embodiment of the present disclosure. For convenience of explanation, only the parts relevant to the embodiment of the present disclosure are shown. As shown in Figure 8, the apparatus 80 includes a second display unit 801 and a third display unit 802.

[0200] Corresponding to the information processing method of the above embodiment, Figure 8 is a block diagram of the configuration of a text format setting device according to an embodiment of the present disclosure. For convenience of explanation, only the parts relevant to the embodiment of the present disclosure are shown. As shown in Figure 8, the device 80 includes a second display unit 801 and a third display unit 802.

[0201] The second display unit 801 is used to display the component container in the session interface of the target session. The third display unit 802 is used to display at least one component instance, including a target component instance, in the component container, the target component instance containing pre-configured service data.

[0202] In some embodiments of the present disclosure, the second display unit 801 is further used to display at least some session messages of the target session on the session interface.

[0203] In some embodiments of this disclosure, a component container is displayed at the top of the session interface, the component container displays one component instance, and a third display unit 802 further, In response to receiving a first presentation command to display multiple component instances, the session interface increases the display area of ​​the component container, which is used to display multiple component instances within the component container.

[0204] In some embodiments of this disclosure, the information processing device further includes a first manufacturing unit (not shown), the first manufacturing unit is The process involves generating a component creation command in response to a user's component creation operation, where the component creation operation is used to create a target component for a target session, and the component creation command includes service data identifier information and target session identifier information. Sending a component creation command to the service data server, causing the service data server to generate a target component creation request in response to the component creation command, sending the target component creation request to the session server, and causing the session server to create the target component, This is used to receive a target component instance sent by the session server and display the target component instance in the session interface of the target session, where the target component instance is generated from service data obtained by the session server.

[0205] In some embodiments of this disclosure, the information processing device further includes a preview unit (not shown), the preview unit is The session server receives a preview identifier for the target component, which is generated when the session server creates the target component. In response to detecting that no component instance matching the preview identifier exists locally, the system sends an instance acquisition request to the session server, receives the component instance sent by the session server, binds the component instance to the target component, and creates a target component instance, or It is used to bind a component instance to a target component and create a target component instance in response to detecting that a component instance matching the preview identifier exists locally.

[0206] In some embodiments of this disclosure, the information processing device further includes a second deletion unit (not shown), the second deletion unit is It is used to receive a component deletion command sent by a user in the target session interface, to send component deletion information to the session server for deleting the component indicated by the command, and to delete the locally stored information about the said component.

[0207] Corresponding to the information processing method of the above embodiment, Figure 9 is a block diagram of the configuration of a text format setting device according to an embodiment of the present disclosure. For convenience of explanation, only the parts relevant to the embodiment of the present disclosure are shown. As shown in Figure 9, the device 90 includes a generation unit 901, a first transmission unit 902, and a second transmission unit 903.

[0208] The generation unit 901 is used to generate a session component creation request, which includes address information and a target session identifier for the service data. The first transmission unit 902 is used to send a session component creation request to the session server of the target session and to cause the session server to create the target component. The second transmission unit 903 is used to send service data to the session server and to cause the session server to generate target component instances according to the service data.

[0209] In some embodiments of this disclosure, the generating unit 901 further It is used to generate a component creation request in response to receiving a target component creation command sent by the session user of the target session, and the command includes the target session identifier and service data identifier information.

[0210] In some embodiments of this disclosure, the information processing device further includes a third update unit (not shown). The third update unit is In response to detecting a change in service data and / or display style, the system sends change information to the session server, causing the session server to update the target component instance, or The system receives a request from the session server to retrieve update information for service data and / or display styles, and detects whether the service data and / or display styles have been updated. If the detection result is YES, update information is sent to the session server, causing the session server to update the target component instance.

[0211] To realize the above embodiments, the embodiments of this disclosure further provide electronic devices.

[0212] As shown in Figure 10, a schematic diagram of the configuration of an electronic device 1000 applicable to realizing an embodiment of the present disclosure is provided, and the electronic device 1000 may be various terminal devices, servers, etc. Terminal devices may include, but are not limited to, mobile devices such as mobile phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (Portable Android Devices, PADs), portable multimedia players (PMPs), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. The electronic device shown in Figure 10 is merely an example and does not imply any limitation on the functions and scope of use of the embodiments of the present disclosure.

[0213] As shown in Figure 10, the electronic device 1000 may include a processing unit (e.g., a central processing unit, graphics processor, etc.) 1001 capable of performing various appropriate operations and processes in response 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 (RAM) 1003. The RAM 1003 further stores various programs and data necessary for the operation of the electronic device 1000. The processing unit 1001, ROM 1002, and RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0214] Typically, devices that can be connected to the I / O interface 1005 include input devices 1006 such as touch panels, touchpads, keyboards, mice, cameras, microphones, accelerometers, and gyroscopes; output devices 1007 such as liquid crystal displays (LCDs), speakers, and vibrators; storage devices 1008 such as tapes and hard disks; and communication devices 1009. The communication device 1009 enables the electronic device 1000 to communicate wirelessly or via wired connection with other devices to exchange data. Figure 10 shows the electronic device 1000 with various devices, but it should be understood that it is not necessary to implement or have all of the devices shown. Instead, more or fewer devices may be implemented or have been included.

[0215] In particular, according to embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product which includes a computer program mounted on a computer-readable medium, the computer program which includes program code for performing the method shown in the flowchart. In such embodiments, the computer program may be downloaded and installed from a network via a communication device 1009, installed from a storage device 1008, or installed from a ROM 1002. When the computer program is executed by the processing unit 1001, the above-described functions, limited to the methods of embodiments of the present disclosure, are performed.

[0216] The computer-readable storage medium described herein may be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. The computer-readable storage medium may be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage mediums may include, but are not limited to, electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium containing or storing a program, the program may be used by or in combination with an instruction execution system, apparatus, or device. In this disclosure, the computer-readable signal medium may include data signals propagated in the baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, and such computer-readable signal medium can transmit, propagate, or transmit programs for use by or in combination with instruction execution systems, apparatus, or devices. Program code contained in the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), or any suitable combination thereof.

[0217] The computer-readable medium described above may be included in the electronic device described above, or it may exist independently without being assembled into the electronic device.

[0218] The computer-readable medium described above contains one or more programs (computer execution instructions), and when the one or more programs described above are executed by the electronic device, the electronic device is made to execute the method shown in the above embodiment.

[0219] Computer program code for performing the operations disclosed herein can be programmed in one or more programming languages, or a combination thereof, and such programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, and further include conventional procedural programming languages ​​such as C and similar programming languages. The program code may run entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. Where a remote computer is involved, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computer (for example, connected via the Internet using an Internet service provider).

[0220] The flowcharts and block diagrams in the drawings illustrate the achievable architectures, functions, and operations of the systems, methods, and computer program products of various embodiments of this disclosure. In this regard, each block in the flowchart or block diagram may represent a module, program segment, or part of code containing one or more executable instructions for realizing a given logical function. In some alternative implementations, the functions shown in the blocks may be performed in an order different from the order shown in the drawings. For example, two consecutively shown blocks may actually be executed almost in parallel, or in some cases, in reverse order depending on the related functions. Each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs a given function or operation, or by a combination of dedicated hardware and computer instructions.

[0221] The units relating to the embodiments of this disclosure may be implemented in software form or in hardware form. In some cases, the name of the unit is not limiting to the unit itself; for example, a creation unit may be described as "a unit that creates a target component in response to a received session component creation request."

[0222] The functions described herein may be performed at least partially by one or more hardware logic components. For example, non-limiting exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SOCs), and complex-programmable logic devices (CPLDs).

[0223] In the context of this disclosure, a machine-readable medium may be a tangible medium containing or storing a program that can be used by, or in combination with, an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More specific examples of machine-readable storage media may include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0224] The above description is merely a description of preferred embodiments and the technical principles used in this disclosure. Those skilled in the art will understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above technical features, but also includes other technical solutions formed by any combination of the above technical features or equivalent features, to the extent that they do not deviate from the gist of this disclosure. For example, technical solutions formed by substituting the above features with similar functional technical features disclosed in this disclosure (but not limited to those disclosed herein).

[0225] Furthermore, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in a specific order or sequence. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above description, these should not be construed as limiting the scope of this disclosure. Some features described in the context of individual embodiments may be implemented in combination in a single embodiment. Rather, various features described in the context of a single embodiment may be implemented individually or in any suitable subcombination in multiple embodiments.

[0226] Although this subject matter has been described in language specific to the structural features and / or logical operation of the method, it should be understood that the subject matter limited in the claims is not necessarily limited to the specific features or operations described above. Rather, the specific features and operations described above are merely illustrative forms for realizing the claims.

Claims

1. Information processing method, A step of creating a target component in response to a received session component creation request, wherein the session component creation request includes a target session identifier and address information for service data. A step of obtaining the service data according to the address information, The steps include: instantiating the target component according to the service data; The step of displaying the target component instance in the session interface indicated by the target session identifier, The step of obtaining the service data according to the address information is: The step includes obtaining a display style according to the address information, The step of instantiating the target component according to the service data is: An information processing method comprising the step of instantiating the target component according to the display style and the service data.

2. The step of creating a target component in response to the received session component creation request is: The steps include receiving the session component creation request sent by the service data server through the component creation interface, The method according to claim 1, comprising the step of creating the target component using a component addition interface.

3. The step of creating a target component in response to the received session component creation request is: The steps include receiving the session component creation request sent by the service data server through the component creation interface, The method according to claim 1, comprising the step of creating the target component using a component addition interface.

4. The step of creating a target component in response to the received session component creation request is: The method according to claim 1, further comprising the step of creating a target component abstract instance in response to the session component creation request.

5. The steps include creating a preview identifier corresponding to the target component and associating the preview identifier with the address information, The step further includes sending the aforementioned preview identifier to the client of the user of the target session, The step of obtaining the service data according to the address information is: The method according to claim 1, comprising the step of obtaining the service data according to the address information in response to receiving a view request from the client for viewing the target component instance, wherein the view request includes the preview identifier.

6. The steps include obtaining the updated service data and / or display style, The method according to claim 1, further comprising the step of updating the target component instance in accordance with the updated service data and / or the display style.

7. The method according to claim 1, further comprising the step of detecting that the target component instance has changed, pushing information of the changed target component instance to the client of the user of the target session, wherein the change is generated by updated service data and / or display style transmitted by the service data server.

8. The method according to claim 1, further comprising the steps of: in response to a received deletion command for a session component, deleting the component in the target session indicated by the deletion command, and sending a command to the user's client of the target session to instruct the deletion of the pre-stored information about the component.

9. Information processing method, The steps include displaying the component container in the target session's display interface, The steps include: displaying at least one component instance, including a target component instance, in the component container, wherein the target component instance includes pre-configured service data; A step of generating a component creation command in response to a user's component creation operation, wherein the component creation operation is used to create a target component of the target session, and the component creation command includes identifier information for service data and identifier information for the target session. The steps include sending the component creation command to the service data server, causing the service data server to generate a target component creation request in response to the component creation command, sending the target component creation request to the session server, and causing the session server to create the target component, An information processing method further comprising the steps of receiving the target component instance transmitted by the session server and displaying the target component instance on the display interface of the target session, wherein the target component instance is generated from service data acquired by the session server.

10. A step of receiving a preview identifier of a target component sent by a session server, wherein the preview identifier is generated when the session server creates the target component, In response to detecting that no component instance matching the preview identifier exists locally, the system sends a request to the session server to obtain the component instance, receives the component instance sent by the session server, binds the component instance to the target component, and creates the target component instance, or The method of claim 9, further comprising the steps of: in response to detecting that a component instance matching the preview identifier exists locally, binding the component instance to the target component and generating the target component instance.

11. The method according to claim 9, further comprising the steps of: receiving a component deletion command transmitted by a user in the display interface of the target session, transmitting component deletion information to the session server for deleting the component indicated by the component deletion command; and deleting the locally stored information of the component.

12. Information processing method, A step of generating a session component creation request, wherein the session component creation request includes address information of service data and a target session identifier. The steps include sending a session component creation request to the session server of the target session, causing the session server to create the target component, The process includes the steps of sending the service data to the session server and causing the session server to generate a target component instance in accordance with the service data, The step of generating a component container creation request is: An information processing method comprising the steps of generating a component creation request in response to receiving a creation command for the target component sent by a session user of the target session, wherein the creation command includes a target session identifier and identifier information for the service data.

13. In response to detecting that the service data and / or display style has changed, the steps include sending change information to the session server and causing the session server to update the target component instance, Or, The method according to claim 12, further comprising the steps of receiving an acquisition request from the session server to acquire update information for the service data and / or display style, detecting whether the service data and / or display style has been updated, and if the detection result is YES, transmitting the update information to the session server to cause the session server to update the target component instance.

14. An information processing device, It is configured to create a target component in response to a received session component creation request, and the session component creation request includes a creation unit that includes a target session identifier and address information for service data, An acquisition unit configured to acquire service data according to the address information, including acquiring a display style according to the address information, An instantiation unit configured to instantiate the target component according to the service data, including instantiating the target component according to the display style and the service data, An information processing device including a first display unit configured to display a target component instance in a session interface indicated by the target session identifier.

15. An information processing device, A second display unit configured to display a component container in the session interface of the target session, The component container is configured to display at least one component instance, including a target component instance, and the target component instance includes a third display unit containing pre-configured service data, The process involves generating a component creation command in response to a user's component creation operation, where the component creation operation is used to create a target component for a target session, and the component creation command includes service data identifier information and target session identifier information. Sending a component creation command to the service data server, causing the service data server to generate a target component creation request in response to the component creation command, sending the target component creation request to the session server, and causing the session server to create the target component, An information processing device further includes a first creation unit arranged to perform the following: receiving a target component instance sent by a session server and displaying the target component instance in the session interface of a target session, wherein the target component instance is generated from service data obtained by the session server.

16. An electronic device, including a processor and memory, The aforementioned memory stores computer execution instructions. The processor is an electronic device that realizes the information processing method according to any one of claims 1 to 13 by executing computer execution instructions stored in the memory.

17. A computer-readable storage medium that stores computer execution instructions, and which, when a processor executes the computer execution instructions, realizes the information processing method described in any one of claims 1 to 13.

Images