An information transmission method and system and a flow information processing method and system

Abstract

The application provides an information transmission method and system and a process information processing method and system, and relates to the field of communication. The information transmission method comprises the following steps: obtaining an information body; displaying a brief report; and displaying detailed content in response to a sent acquisition request. The information transmission system comprises an information body acquisition module, a brief report display module and a detailed content display module. The process information processing method comprises the following steps: obtaining a user node graph; obtaining a first information body; displaying a first brief report; displaying first detailed content in response to a sent first acquisition request; and obtaining a first service state in response to a sent first trigger operation. The process information processing system comprises a user node graph acquisition module, a first information body acquisition module, a first brief report display module, a first detailed content display module and a first service state acquisition module. The information body of the application can be compatible with different types of information such as messages, to-do lists and processes, and the information transmission method based on the information body has the characteristics of being lighter, more flexible and more efficient.

Description

Technical Field

[0001] This specification relates to the field of communications, and in particular to an information transmission method and system, and a process information processing method and system. Background Art

[0002] In business systems, messages, to-do items, and processes are essential information carriers that collaboratively drive the flow of business information and the advancement of business processes between different user nodes (such as system operators and reviewers). Processes can include approval processes. In traditional business systems, messages, to-do items, and processes are typically implemented as independent subsystems. This architecture leads to the following problems: First, when business events trigger messages, to-do items, and processes simultaneously, the system must interface with each of these subsystems, resulting in complex interfaces, high development and maintenance costs, and low collaborative efficiency. Second, when these subsystems process messages containing rich media content or complex business data (for example, high-concurrency, high-volume messages, or to-do items / process items that carry detailed descriptions and documents), they face significant information transmission bottlenecks. This can easily lead to network congestion, transmission delays, and system responsiveness, severely impacting user experience and business process efficiency.

[0003] Therefore, it is necessary to provide an information transmission method and system as well as a process information processing method and system, which can make the information transmission method more lightweight, flexible and efficient while being compatible with different types of information such as messages, to-do items, and processes. Summary of the Invention

[0004] In order to be compatible with different types of information such as messages, to-do items, and processes, and to achieve lightweight, flexible, and efficient information transmission, the present invention provides an information transmission method and system, as well as a process information processing method and system.

[0005] The invention includes an information transmission method. The method includes: obtaining an information body; the information body includes a brief and detailed content, the brief data size being smaller than the detailed content; sending the brief to a front end corresponding to a target user, so that the brief is displayed on the front end; and, in response to a retrieval request sent by the front end, sending the detailed content to the front end, so that the detailed content is displayed on the front end.

[0006] In some embodiments, the detailed content further includes an interactive control; the method further includes: updating the business status corresponding to the information body in response to a trigger operation performed through the interactive control.

[0007] In some embodiments, the detailed content includes business data related to the business domain corresponding to the information body; the method further includes: updating the business data related to the business domain based on the updated business status.

[0008] In some embodiments, the information body also includes at least one delivery channel identifier; sending the briefing to the front end corresponding to the target user includes: based on the at least one delivery channel identifier, determining the front end corresponding to at least one delivery channel; and sending the briefing to the front end.

[0009] In some embodiments, the method further includes: in response to a retrieval request sent through the front end, replacing the viewing status corresponding to the information body from unread to read; and displaying the viewing status corresponding to the information body through the front end corresponding to at least one delivery channel.

[0010] The invention includes a process information processing method. The process information processing method includes obtaining a user node graph corresponding to the process; the user node graph includes nodes and edges, the nodes correspond to users involved in the process, and the edges reflect the relationship between different users involved in the process; determining a first user based on the user node graph, and obtaining a first information body corresponding to the first user; the first information body includes a first briefing and first detailed content, the data volume of the first briefing is smaller than the data volume of the first detailed content; sending the first briefing to a first front end corresponding to the first user, so as to display the first briefing on the first front end; in response to a first acquisition request sent through the first front end, sending the first detailed content to the first front end, so as to display the first detailed content on the first front end; and, in response to a first trigger operation sent through the first front end, obtaining a first business status corresponding to the first information body.

[0011] In some embodiments, the method also includes performing at least one round of information processing until a preset process termination condition is met; each round of information processing in the at least one round of information processing includes: determining a second user based on a user node graph and a first business status, and obtaining a second information body corresponding to the second user; the second information body includes a second briefing and second detailed content, and the data volume of the second briefing is smaller than the data volume of the second detailed content; sending the second briefing to a second front end corresponding to the second user to display the second briefing on the second front end; in response to a second acquisition request sent through the second front end, sending the second detailed content to the second front end to display the second detailed content on the second front end; and, in response to a second trigger operation sent through the second front end, obtaining a second business status corresponding to the second information body.

[0012] In some embodiments, the detailed content of the information body corresponding to the users involved in the process includes business data related to the same business domain.

[0013] In some embodiments, the relationship includes a logical relationship and / or a temporal relationship.

[0014] In some embodiments, the process termination condition includes that the business status of the user's information body corresponding to any node in the user node graph is rejected, or the business status of the user's information body corresponding to the last node in the user node graph is agreed, and the last node is the last node in the time sequence in the user node graph.

[0015] The invention content includes an information transmission system, which includes an information body acquisition module, configured to acquire an information body; the information body includes a briefing and detailed content, and the data volume of the briefing is smaller than the data volume of the detailed content; the briefing display module is configured to send the briefing to the front end corresponding to the target user so as to display the briefing on the front end; and, the detailed content display module is configured to send the detailed content to the front end in response to the acquisition request sent through the front end so as to display the detailed content on the front end.

[0016] The invention content includes a process information processing system, which includes a user node graph acquisition module, configured to obtain a user node graph corresponding to the process; the user node graph includes nodes and edges, the nodes correspond to users involved in the process, and the edges reflect the relationship between different users involved in the process in the process; a first information body acquisition module, configured to determine a first user based on the user node graph, and obtain a first information body corresponding to the first user; the first information body includes a first briefing and a first detailed content, and the data volume of the first briefing is smaller than the data volume of the first detailed content; a first briefing display module, configured to send the first briefing to a first front end corresponding to the first user, so as to display the first briefing on the first front end; a first detailed content display module, configured to send the first detailed content to the first front end in response to a first acquisition request sent through the first front end, so as to display the first detailed content on the first front end; and a first business status acquisition module, configured to obtain a first business status corresponding to the first information body in response to a first trigger operation sent through the first front end.

[0017] The beneficial effects brought about by the above invention include but are not limited to: (1) By using lightweight information bodies, messages are split into briefs and details, and only briefs are delivered each time, which can significantly improve delivery efficiency. (2) The sending timing of each to-do information body in the process is automatically determined based on the user node graph, and business data is automatically updated based on the to-do results, realizing intelligent driving of process to-dos and automatic updating of business data. (3) Part of the data of the detailed content comes from the business domain, and the business data in the business domain can be updated based on the updated business status, which is more timely and accurate. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] This specification will be further described in the form of exemplary embodiments, which will be described in detail with reference to the accompanying drawings. These embodiments are not limiting, and in these embodiments, like numbers represent like structures, wherein:

[0019] Figure 1 is a schematic diagram of an application scenario of an information transmission system and a process information processing system according to some embodiments of this specification;

[0020] Figure 2 is an exemplary module diagram of a processing device of an information transmission system according to some embodiments of this specification;

[0021] Figure 3 is an exemplary module diagram of a processing device of a process information processing system according to some embodiments of this specification;

[0022] Figure 4 is an exemplary flow chart of an information transmission method according to some embodiments of this specification;

[0023] Figure 5 is an exemplary flow chart of a process information processing method according to some embodiments of this specification;

[0024] Figure 6 is an exemplary schematic diagram of a user node graph according to some embodiments of this specification. DETAILED DESCRIPTION

[0025] To more clearly illustrate the technical solutions of the embodiments of this specification, the following briefly describes the drawings required for describing the embodiments. Obviously, the drawings described below are merely examples or embodiments of this specification. Those skilled in the art can apply this specification to other similar scenarios based on these drawings without inventive effort. Unless otherwise apparent from the context or otherwise noted, the same reference numerals in the figures represent the same structure or operation.

[0026] It should be understood that the terms "system," "device," "unit," and / or "module" used herein are a method for distinguishing different components, elements, parts, portions, or assemblies at different levels. However, if other terms can achieve the same purpose, the terms may be replaced by other expressions.

[0027] Unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" do not refer to the singular but include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements specifically identified, and these steps and elements do not constitute an exclusive list. A method or apparatus may also include other steps or elements.

[0028] Flowcharts are used throughout this specification to illustrate the operations performed by systems according to embodiments of this specification. It should be understood that preceding or following operations do not necessarily need to be performed in exact order. Instead, the steps may be processed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0029] Figure 1 1 is a schematic diagram of an application scenario of an information transmission system and a process information processing system according to some embodiments of this specification. In some embodiments, the application scenario 100 of the information transmission system and the process information processing system may include a processing device 110, a network 120, a storage device 130, and a user terminal 140.

[0030] The application scenarios 100 of the information transmission system and the process information processing system may include message transmission, to-do transmission, process transmission and other application scenarios.

[0031] Messages are used for one-way communication of information. The target user only needs to know the content of the message and usually does not need to perform specific actions to provide feedback or change status. Messages can carry various types of data such as text, audio, and images. The target user refers to the recipient of the message. For more information about target users, see Figure 4 and their corresponding descriptions.

[0032] To-do items represent tasks that the target user needs to be aware of and process. They not only contain task description information (which can also contain multiple data types), but also provide interactive controls (such as buttons and links) that enable the target user to perform specific operations (such as marking completion and submitting processing results) to change the business status (for example, from unprocessed status to processed status).

[0033] A process is a structured, process-based to-do collection that can be considered to be composed of multiple to-do items. It contains multiple interrelated process to-do items, each corresponding to a specific user node. These process to-do items have pre-defined logical and / or temporal relationships. For example, in the approval process, the approval process may include approval to-do items A, B, and C. Approval to-do items A and B may be set to an "or" relationship (meaning that either A or B must pass). Approval to-do item C is set as the subsequent step after A or B passes (meaning that C can only be executed after A and / or B pass).

[0034] In some embodiments, processes may include other types, for example, processes may include inspection and rectification processes, etc. For example, when the upstream business is an inspection process and the downstream business is a rectification process, when there is a problem with the upstream inspection process, the downstream rectification process may be triggered.

[0035] The processing device 110 can be used to process data related to the information transmission system and the process information processing system. For example, the processing device 110 can retrieve information bodies. The processing device 110 can send a briefing to the front-end corresponding to the target user, for display on the front-end. In response to a retrieval request sent by the front-end, the processing device 110 can send detailed content to the front-end, for display on the front-end.

[0036] In some embodiments, processing device 110 may be a single server or a server group. The server group may be centralized or distributed. In some embodiments, processing device 110 may be local or remote. In some embodiments, processing device 110 may be implemented on a cloud platform. By way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an internal cloud, a multi-layer cloud, or any combination thereof. In some embodiments, processing device 110 may be integrated with or installed on user terminal 140.

[0037] The network 120 may include any suitable wired or wireless network that can facilitate the exchange of information and / or data. For example, the processing device 110 and the user terminal 140 may communicate information and / or data via the network 120 .

[0038] Storage device 130 can store data, instructions, and / or any other information. In some embodiments, storage device 130 can store data and / or instructions related to the information transmission system and the process information processing system. For example, storage device 130 can store a body of information including a briefing and detailed content. As another example, storage device 130 can store instructions for displaying the briefing or detailed content on the front end.

[0039] In some embodiments, the storage device 130 may be connected to the network 120 to communicate with one or more other components (e.g., the processing device 110 and / or the user terminal 140) in the application scenario 100 of the information transmission system and process information processing system. One or more components in the application scenario 100 of the information transmission system and process information processing system may access data or instructions stored in the storage device 130 via the network 120. In some embodiments, the storage device 130 may be part of the processing device 110.

[0040] In some embodiments, user terminal 140 may include a mobile device 140-1, a tablet computer 140-2, a laptop computer 140-3, a virtual reality device 140-4, or any combination thereof. In some embodiments, processing device 110 may be part of user terminal 140. In some embodiments, user terminal 140 may serve as a front-end for interacting with a target user. For example, user terminal 140 may be installed with software such as an instant messaging service application, a webpage, a text messaging application, or a business system application. These software may serve as front-ends for interacting with the target user. A single user terminal 140 may include multiple front-ends, enabling multiple channels for interacting with the target user.

[0041] In some embodiments, the processing device 110 may present the briefing or detailed content to the user through a front end (such as the user terminal 140 or software installed thereon), and the user may freely browse the briefing or detailed content on the front end and may send an acquisition request through the front end.

[0042] It should be noted that the application scenarios are provided for illustrative purposes only and are not intended to limit the scope of the present invention. A person skilled in the art will appreciate that various modifications or variations can be made based on the description of the present invention. For example, the application scenarios may also include a storage device. For another example, the application scenarios may be implemented on other devices to achieve similar or different functions. However, such variations and modifications will not deviate from the scope of the present invention.

[0043] Figure 2 2 is an exemplary module diagram of an information transmission system 200 according to some embodiments of this specification. In some embodiments, the information transmission system 200 may include an information body acquisition module 210, a briefing display module 220, and a detailed content display module 230. In some embodiments, the information transmission system 200 may also include a service status update module 240. In some embodiments, the information transmission system 200 may also include a service data update module 250. In some embodiments, the information transmission system 200 may also include a review status display module 260.

[0044] The information body acquisition module 210 may be configured to acquire an information body. The information body includes a brief and detailed content, and the data volume of the brief is smaller than the data volume of the detailed content.

[0045] In some embodiments, the information body may further include at least one delivery channel identifier.

[0046] The briefing display module 220 may be configured to send the briefing to a front end corresponding to the target user so that the briefing is displayed on the front end.

[0047] In some embodiments, the briefing display module 220 may be further configured to determine the front end corresponding to at least one delivery channel based on at least one delivery channel identifier; and send the briefing to the front end.

[0048] The detailed content display module 230 may be configured to send detailed content to the front end in response to an acquisition request sent through the front end, so as to display the detailed content on the front end.

[0049] In some embodiments, the detailed content may also include interactive controls.

[0050] In some embodiments, the detailed content may include business data related to the business domain corresponding to the information body.

[0051] The service status updating module 240 may be configured to update the service status corresponding to the information body in response to a triggering operation performed through the interactive control.

[0052] The service data updating module 250 may be configured to update service data related to the service domain based on the updated service status.

[0053] The review status display module 260 can be configured to replace the review status corresponding to the information body from unread to read in response to a retrieval request sent through the front end; and display the review status corresponding to the information body through the front end corresponding to at least one delivery channel.

[0054] It should be understood that Figure 2 The system and its modules shown can be implemented in various ways. It should be noted that the above description of the information transmission system and its modules is only for convenience of description and does not limit the present invention to the scope of the embodiments. It is understandable that those skilled in the art, after understanding the principles of the system, may arbitrarily combine the modules or form subsystems connected with other modules without deviating from the principles. In some embodiments, Figure 2 The information acquisition module 210, briefing display module 220, detailed content display module 230, service status update module 240, service data update module 250, and review status display module 260 disclosed herein may be different modules within a system, or a single module may implement the functions of two or more of the aforementioned modules. For example, each module may share a storage module, or each module may have its own storage module. Such variations are within the scope of protection of the present invention.

[0055] Figure 3is an exemplary module diagram of a process information processing system 300 according to some embodiments of this specification. In some embodiments, the process information processing system 300 may include a user node graph acquisition module 310, a first information body acquisition module 320, a first briefing display module 330, a first detailed content display module 340, and a first business status acquisition module 350. In some embodiments, the process information processing system 300 may also include a loop module 360.

[0056] The user node graph acquisition module 310 may be configured to acquire a user node graph corresponding to a process. The user node graph includes nodes and edges, where nodes correspond to users involved in the process and edges reflect the relationships between different users involved in the process.

[0057] In some embodiments, the relationship may include a logical relationship and / or a temporal relationship.

[0058] The first information body acquisition module 320 may be configured to determine the first user based on the user node graph and acquire the first information body corresponding to the first user. The first information body includes a first briefing and first detailed content, and the data volume of the first briefing is smaller than the data volume of the first detailed content.

[0059] In some embodiments, the detailed content of the information body corresponding to the users involved in the process may include business data related to the same business domain.

[0060] The first briefing display module 330 may be configured to send the first briefing to a first front end corresponding to the first user, so that the first briefing is displayed on the first front end.

[0061] The first detailed content display module 340 may be configured to send the first detailed content to the first front end in response to the first acquisition request sent through the first front end, so as to display the first detailed content on the first front end.

[0062] The first service status acquisition module 350 may be configured to acquire a first service status corresponding to the first information body in response to a first trigger operation sent through the first front end.

[0063] The loop module 360 ​​can be configured to determine the second user based on the user node graph and the first business status, and obtain the second information body corresponding to the second user; the second information body includes a second briefing and second detailed content, and the data volume of the second briefing is smaller than the data volume of the second detailed content; the second briefing is sent to the second front end corresponding to the second user to display the second briefing on the second front end; in response to a second acquisition request sent through the second front end, the second detailed content is sent to the second front end to display the second detailed content on the second front end; in response to a second trigger operation sent through the second front end, the second business status corresponding to the second information body is obtained; and so on, until the preset process termination condition is met.

[0064] In some embodiments, the process termination condition may include that the business status of the user's information body corresponding to any node in the user node graph is rejected, or the business status of the user's information body corresponding to the last node in the user node graph is agreed.

[0065] It should be understood that Figure 3 The system and its modules shown can be implemented in various ways. It should be noted that the above description of the information transmission system and its modules is only for convenience of description and does not limit the present invention to the scope of the embodiments. It is understandable that those skilled in the art, after understanding the principles of the system, may arbitrarily combine the modules or form subsystems connected with other modules without deviating from the principles. In some embodiments, Figure 3 The user node graph acquisition module 310, first information body acquisition module 320, first briefing display module 330, first detailed content display module 340, first service status acquisition module 350, and loop module 360 ​​disclosed in the present disclosure may be different modules within a system, or a single module may implement the functions of two or more of the aforementioned modules. For example, each module may share a storage module, or each module may have its own storage module. Such variations are within the scope of protection of the present disclosure.

[0066] Figure 4 is an exemplary flow chart of an information transmission method according to some embodiments of this specification. Figure 4 As shown, the information transmission process 400 may include steps 410 to 430. In some embodiments, as Figure 4 As shown, the information transmission process 400 may further include step 440. In some embodiments, as Figure 4 As shown, the information transmission process 400 may further include step 450. In some embodiments, as Figure 4 As shown, the information transmission process 400 may further include steps 460 to 470. In some embodiments, Figure 4 One or more operations of the information transmission process 400 may be performed in Figure 1 The information transmission system and process information processing system are implemented in the application scenario 100 shown. For example, Figure 4 The information transmission process 400 shown may be stored in the storage device 130 in the form of instructions and called and / or executed by the processing device 110 .

[0067] Step 410 , obtaining an information body. In some embodiments, step 410 may be performed by the information body obtaining module 210 .

[0068] An information body is a data structure that, through a unified technical framework, integrates the traditionally independent subsystems corresponding to messages, tasks, and processes into a single entity, addressing issues such as low delivery efficiency and complex business integration.

[0069] In some embodiments, the information body may include a brief description and detailed content, and the data volume of the brief description is smaller than the data volume of the detailed content.

[0070] A briefing refers to the core, condensed information corresponding to an information body. In some embodiments, a briefing may include a summary of the detailed content. Summary text refers to a high-level summary of the detailed content in text format. For example, a briefing may include a sender identification (ID), a recipient identification, a message identification, a title, and a summary. The sender identification, recipient identification, and message identification are unique codes for the sender, recipient, and information body, respectively. For example, the sender identification can be the sender's identity, the recipient identification can be the recipient's identity, and the message identification can be the information body's identity. Each of these can be composed of letters, numbers, symbols, etc. The title and summary are displayed on the target user's front-end. The sender identification may or may not be displayed on the target user's front-end. When the sender identification is displayed on the front-end, the target user can further query the sender's name, position, and other profile information through the processing device based on the sender identification. The recipient identification and message identification do not need to be displayed on the front-end. The recipient identification indicates the recipient of the briefing and is used during the briefing delivery process. The message identification is a unique identifier for the information body and does not need to be displayed on the front-end.

[0071] Detailed content refers to the more comprehensive and in-depth information corresponding to the information body.

[0072] In some embodiments, the detailed content may include one or more of the following data: text, images, audio, video, graphic data, and forms. The detailed content can present the information body in a comprehensive, detailed, and vivid manner. For example, the detailed content may include information related to business event reporting in the form of text, images, audio, video, graphic data, and / or forms. Among them, the information related to business event reporting refers to the description of the business event. For example, when the pressure value of a certain section of pipeline in the construction scene exceeds the warning threshold, a pipeline warning event will be triggered. The reporting information corresponding to the pipeline warning event may include the warning indicator (for example, the pipeline pressure value), the current value of the indicator, the duration that the indicator value exceeds the warning threshold, the pipeline location, pipeline-related pictures or videos, etc., that is, the detailed content may include the above content.

[0073] It should be noted that the detailed content corresponding to the message, to-do list and process may include one or more of the following data: text, image, audio, video, graphic data, and form.

[0074] In some embodiments, the detailed content may also include interactive controls.

[0075] Interactive controls are objects in the front-end interface that can interact with the user. For example, interactive controls can include radio buttons, check boxes, drop-down menus, buttons, etc.

[0076] It should be noted that, since messages are used for one-way notification of information, the detailed content corresponding to the message does not include interactive controls. Only the detailed content corresponding to the to-do items and processes can include interactive controls.

[0077] In some embodiments, for a to-do item, the interactive control may include a completion control. The front end will display the completion control, and when the target user completes the to-do item, they can click the completion control to update the business status.

[0078] In some embodiments, for a process, the interactive controls for a single to-do item in the process may also include a completion control. When the process is an approval process, the interactive controls may include a combination of one or more of the following controls: an approval control, a rejection control, a signature control, a transfer control, a return control, and a revocation control. The front end will display the above controls, and the target object can trigger the corresponding controls according to the actual situation to update the business status of the approval to-do item and further change the process progress. For more information about the business status, please refer to the following and its corresponding description.

[0079] In some embodiments, the detailed content may also include business data related to the business domain corresponding to the information body.

[0080] A business domain is a unit that stores business data. A business system contains multiple projects and tasks. The processing device can divide the business data in the business system into multiple sub-sections based on first preset rules, each of which is referred to as a business domain. The first preset rule may be a pre-set division rule. For example, the first preset rule may include a rule for dividing business data by project and / or task. A project refers to work performed to create a unique product, service, or outcome, such as construction projects and building projects. A task refers to a specific activity, such as inspection tasks, rectification tasks, and approval tasks. In other words, business data corresponding to different types of projects / tasks is stored in different business domains. Business data may include the progress, cost, and responsible individuals for the corresponding project / task. Business data may also include other content, such as documents with jump links, process logs, personnel details, organizational information, company details, and business details.

[0081] It should be noted that the information body corresponds to a specific project and / or task, and the business data associated with the business domain corresponding to the information body refers to the business data within the business domain corresponding to that project and / or task. For example, if the information body is related to Inspection Task A, the detailed information will include the business data associated with Inspection Task A within the business domain corresponding to the inspection task. The detailed information associated with messages, to-do items, and processes can also include business data associated with the business domain corresponding to the information body.

[0082] In some embodiments, the information body may directly include the information reported by the business event.

[0083] In other embodiments, a storage device may store business event reporting information. The information body may only include the storage address of the business event reporting information in the storage device. The processing device may retrieve the business event reporting information from the storage device based on the storage address. For more information about target users, see below and the corresponding description. For more information about business event reporting information, see above and the corresponding description.

[0084] In some embodiments of this specification, the briefings corresponding to the three types of information, namely, messages, to-do items, and processes, will not contain multimedia data such as images and audio, thereby avoiding customized development of briefing pages for different information and reducing development costs.

[0085] In some embodiments, the information body may include three types: a message body, a to-do information body, and a process information body. The corresponding briefings for the three types of information bodies may be similar, differing primarily in the details. For example, the corresponding briefings for the three types of information bodies may include similar fields. For example, the corresponding briefings for the three types of information bodies may include a title, a summary, and a sender.

[0086] In some embodiments, the values ​​of the fields are different for different types of information bodies. For example, for a message information body, the title content in its briefing can reflect the title of the message and the information body type (ie, message).

[0087] In some embodiments, the information body may further include an information template, which is used to specify the delivery channel and display style corresponding to the information body. The same information body may specify at least one delivery channel and the display style under the at least one delivery channel.

[0088] A delivery channel refers to the path or medium through which information (e.g., briefings, detailed content) travels during transmission. This channel ensures that information can be delivered from one node to another. Examples of delivery channels include SMS channels, instant messaging channels, web channels, and specific information platforms. Specific information platforms include to-do workstations and approval workstations.

[0089] A presentation style refers to the format in which information (e.g., briefings, detailed content) is displayed. For example, in the chat window of an instant messaging application corresponding to an instant messaging channel, a briefing might be displayed as a card or bubble. Another example is a webpage corresponding to a webpage channel, where a briefing might be displayed in a webpage format. It is understood that one or more presentation styles can be developed or designed for different delivery channels.

[0090] In some embodiments, the message body can be created by a user (i.e., a sender) in the business system. For example, if the sender needs to send a message to a target user, the sender can enter the message content through the user terminal, and the processor can create a message message body based on the message content.

[0091] In other embodiments, information bodies can be created based on business events. For example, if the upstream business is an inspection process and the downstream business is a rectification process, when a problem occurs in the upstream inspection process, the downstream rectification process can be triggered, and the processing device automatically creates a to-do information body to notify the downstream user to make the rectification.

[0092] It is understood that one or more information bodies may be created for the same matter or business event. These multiple information bodies may be of the same or different types and have the same or different delivery channels, etc., without limitation. For example, when a problem occurs in the upstream inspection process, triggering a downstream rectification process, the processing device may automatically create a to-do information body and a message information body. The to-do information body notifies downstream users via SMS and instant messaging channels to perform rectification, while the message information body notifies upstream users via instant messaging channels that there is a problem with the inspection process.

[0093] Step 420 , sending the briefing to the front end corresponding to the target user so as to display the briefing on the front end. In some embodiments, step 420 may be performed by the briefing display module 220 .

[0094] The target user is the recipient of the message body.

[0095] In some embodiments, the processing device may send the briefing to the target user in an active push manner.

[0096] In some embodiments, the information body may further include at least one delivery channel identifier. The processing device may determine the front end corresponding to the at least one delivery channel based on the at least one delivery channel identifier, and send the briefing to the front end.

[0097] The delivery channel identifier refers to a unique code of the delivery channel. For example, the delivery channel identifier may be an identity identifier of the delivery channel, and may be composed of letters, numbers, symbols, etc.

[0098] In some embodiments, the delivery channel is specified by the initiator or pre-set by the system. After the delivery channel is determined, the processing device can automatically generate a delivery channel identifier.

[0099] In some embodiments, the processing device may determine, based on at least one delivery channel identifier and using a second preset rule, a front end corresponding to each of the at least one delivery channel. The second preset rule may be a predetermined rule that specifies different front ends corresponding to different delivery channel identifiers. For example, the second preset rule may specify that the front end corresponding to the SMS channel is an SMS application.

[0100] In some embodiments, the processing device may send the briefing to the front end of the target user via a network.

[0101] In some embodiments of the present specification, a briefing of the same information body can be sent to a target user through at least one delivery channel, thereby increasing the reliability of information transmission.

[0102] In some embodiments, the processing device may display the briefing on the target user's front end in accordance with a presentation style, wherein the processing device may display the briefing in a default presentation style or in accordance with a presentation style selected by the initiator.

[0103] Understandably, the processing system typically pushes messages directly to the target user. However, traditional to-do items or to-do items within a process require the target user to actively query them before they are received, resulting in a certain delay. For example, when the target user enters the to-do page or clicks the to-do button, the processing device queries the target user's to-do status and displays it. This to-do status may include information such as whether there are to-do items, the number of to-do items, and the specific content of the to-do items. On the other hand, if the target user remains on the to-do page for an extended period without performing any action, the processing device will not update the target user's to-do status in real time. Therefore, even if new to-do items are available, the processing device will not display them to the target user through the front-end. In this case, the target user must manually refresh the to-do page before the processing device will update the to-do status. The information body of the present invention can accommodate different information such as to-do items and processes, allowing to-do items or to-do items within a process to reach the target user instantly, just like a message. That is, to-do items or to-do items within a process can be directly delivered to the user through the front-end without the need for active query.

[0104] Step 430 : In response to the acquisition request sent by the front end, send the detailed content to the front end so that the detailed content is displayed on the front end. In some embodiments, step 430 may be performed by the detailed content display module 230 .

[0105] Get request is a request to obtain detailed content.

[0106] In some embodiments, when the target user performs operations such as clicking on a briefing in the front-end interface, clicking on a detailed content link in the briefing, or clicking on a detailed content button in the briefing, the front-end will automatically retrieve the detailed content corresponding to the briefing in the storage device based on the information identifier.

[0107] In some embodiments, when the information body directly includes the information reported by the business event, the processing device may directly use the information reported by the business event as the detailed content.

[0108] In other embodiments, when information reported by a business event is stored in a storage device, the processing device can obtain the storage address of the information reported by the business event from the information body based on the information identifier, and access the storage device based on the storage address to obtain the information reported by the business event as detailed content.

[0109] In some embodiments, when the detailed content includes business data related to the business domain corresponding to the information body, the processing device can determine the corresponding business domain identifier based on the information identifier in the acquisition request; obtain the business data related to the corresponding business domain based on the business domain identifier; and obtain the detailed content based on the business data.

[0110] A business domain identifier is a unique code for a business domain. For example, a business domain identifier can be an identification mark for the business domain and can be composed of letters, numbers, symbols, etc. As mentioned above, business data can be divided according to projects and / or tasks. Different types of projects and / or tasks correspond to different business domains, which are distinguished by different business domain identifiers.

[0111] In some embodiments, when creating an information body, the processing device may associate its information identifier with the business domain identifier to form associated information. Therefore, in response to a request sent by the front end, the processing device may determine the corresponding business domain identifier based on the information identifier and associated information in the request.

[0112] In some embodiments, the processing device may determine the corresponding business domain based on the business domain identifier, and then obtain business data from the corresponding business domain as the business data related to the corresponding business domain. For example, if an information body is related to patrol task A, after determining the business domain identifier corresponding to the patrol task, the business data related to patrol task A may be searched in the business domain (i.e., the business data storage unit) corresponding to the business domain identifier as the business data of the information body.

[0113] In some embodiments of this specification, the business data in the detailed content is obtained from the business domain based on the business domain identifier, thereby separating the information body from the complex and diverse business status. The information body does not need to adapt to the complex and changing business status, while making the detailed content more diverse.

[0114] In some embodiments, the detailed information does not include business data, but only includes a business domain identifier. The processing device can determine the corresponding business domain based on the business domain identifier, obtain business data from the corresponding business domain, and then send the business data to the front end. It can be understood that in the currently used "title + content" message model, although the title of the message usually only has text, the content of the message may contain pictures, videos, files and other content, and even include documents with jump links, process logs, personnel details, organizational information, company details, business details and other complex content. These contents are in different forms and have different interactions. The traditional "title + content" message model is completely incompatible. If the messages are forced to be compatible, different customized developments for different contents will occur, which is extremely costly. Obviously, this technical implementation method is not feasible. In addition to the innovative way of splitting the information body into a brief and details, the present invention can also store only the information identifier and business domain identifier in the information body. In response to the target user sending an acquisition request through the front end, the processing device can query the storage device for detailed content based on the information identifier, and determine the corresponding business domain based on the business domain identifier, obtain business data from the corresponding business domain, and then send the detailed content and business data to the front end, which performs temporary rendering and displays the detailed content and business data through the front end, which can effectively solve the above problems.

[0115] In some embodiments, the processing device may send detailed content to the front end via a network.

[0116] In some embodiments, when the information body corresponds to multiple delivery channels, the target user can send an acquisition request through any delivery channel or the front end corresponding to each delivery channel, and the processing device can send detailed content to the front end corresponding to the delivery channel.

[0117] In some embodiments, the processing device may display detailed content on the front end based on a presentation style specified by the information template.

[0118] When messages are transmitted through at least one delivery channel, they are characterized by high volume (for example, a user sending a greeting message to 1,000 people), high frequency (for example, 100,000 users continuously triggering messages), and immediacy (for example, each message has a business status and messages are ordered). Excessive message volume can cause the delivery channel to be occupied, delaying the timely delivery of other messages, and / or causing inconsistencies in the order in which multiple messages are sent and received. For example, if two adjacent messages are delivered through different delivery channels, and the later delivery channel is faster than the earlier one, the later message will arrive first, resulting in status confusion.

[0119] The message body consists of a brief summary and detailed content. When transmitting a message, only the very small brief summary is transmitted, resulting in extremely high transmission efficiency. The large detailed content is temporarily rendered when the target user sends a request, which only affects the loading speed of the single message and does not affect transmission efficiency.

[0120] In some embodiments, when the detailed content further includes an interactive control, the processing device may perform step 440 .

[0121] Step 440 : In response to the triggering operation executed through the interactive control, update the service status corresponding to the information body. In some embodiments, step 440 may be executed by the service status updating module 240 .

[0122] A trigger operation refers to an operation in which the target user selects or clicks an interactive control through the front-end interface. For example, the target user's front-end interface displays the details of a to-do information body, which also includes a processing control. The trigger operation can be a click on the processing control. For another example, the target user's front-end interface displays the details of a to-do information body, which also includes a processing control. The target user can click the processing control to jump to the work page corresponding to the to-do. The target user completes the corresponding work on the work page (for example, fills in the to-do content on the work page), and then clicks the Save or Done button on the work page. In this case, the trigger operation can be a click on the Save or Done button on the work page.

[0123] The business status refers to the status of the business event corresponding to the information body. For example, the business status can include unprocessed status and processed status.

[0124] In some embodiments, when the process is an approval process, the business status of the information body corresponding to the user involved in the process includes one of the following states: approval, rejection, additional signature, transfer, return, and revocation.

[0125] In some embodiments, the processing device can update the business status corresponding to the information body based on the type of interactive control that performs the triggering operation. For example, after completing a to-do item, the target user can click the processing control. After receiving the triggering operation, the processing device automatically updates the business status corresponding to the information body from unprocessed to processed. For another example, after receiving the click operation of the Save or Done button, the processing device automatically updates the business status corresponding to the information body from unprocessed to processed.

[0126] In some embodiments of this specification, the interactive controls of the to-do items or to-do items in the process are set in the detailed content, and the processing device can update the business status corresponding to the information body based on the triggering operation of the interactive controls, further simplifying the customized development of the briefing page while being compatible with the interactive features of the to-do items.

[0127] In some embodiments, when the detailed content includes business data related to the business domain corresponding to the information body, the processing device may execute step 450 .

[0128] Step 450 : Based on the updated service status, update the service data related to the service domain. In some embodiments, step 450 may be performed by the service data updating module 250 .

[0129] In some embodiments, the processing device can update business data related to the business domain in various ways based on the updated business status. For example, the processing device can update the progress of the corresponding business event in the business data based on the updated business status. In another example, the processing device can also update the cost, responsible person, and other content of the corresponding business event in the business data based on the information entered by the target user on the work page during the processing process.

[0130] In some embodiments of the present specification, part of the data of the detailed content comes from the business domain, and the business data in the business domain can be updated based on the updated business status, which is more timely and accurate.

[0131] Step 460 : In response to the acquisition request sent by the front end, the reading status corresponding to the information body is changed from unread to read. In some embodiments, step 460 may be executed by the reading status display module 260 .

[0132] The reading status refers to a status used to reflect whether the information body has been read by the target user. For example, the reading status can include unread and read.

[0133] In some embodiments, before the target user sends a retrieval request through the front end, the processing device can determine that the viewing status corresponding to the information body is unread; when the target user sends a retrieval request through the front end, the processing device can replace the viewing status corresponding to the information body from unread to read.

[0134] Step 470 : Display the search status corresponding to the information body through the front end corresponding to at least one delivery channel. In some embodiments, step 470 may be performed by the search status display module 260 .

[0135] In some embodiments, the briefing content of the information body may further include a read status, and the processing device may display the briefing including the read status on the front end. For example, before the target user sends a request to obtain the information through the front end, the processing device may display the read status of the corresponding information body as unread in the briefing; when the target user sends a request to obtain the information through the front end, the processing device may change the read status of the corresponding information body in the briefing from unread to read.

[0136] In some embodiments, the same information body may have multiple delivery channels (e.g., an instant messaging channel and a webpage channel), and the processing device may display the corresponding reading status of the information body through the front end corresponding to at least one of the delivery channels. For example, when a target user sends a retrieval request through the front end of one of the delivery channels (e.g., an instant messaging channel), the processing device may replace the reading status of the information body from unread to read in the briefing corresponding to the front end of that delivery channel. The processing device may also replace the reading status of the information body from unread to read in the briefing corresponding to the front end of another delivery channel (e.g., a webpage channel).

[0137] Currently, messages only have two states: read and unread. However, to-do items or to-do items in a process can have a variety of complex states, including "to-be-processed," "initiated by me," "withdrawn by me," and "processed by me." Even to-do items can be different for each business. Each state requires the to-do system to record who processed it, when it was processed, whether it was automatically processed by the system for the user, whether the to-do is currently valid, and whether it has been withdrawn, making the entire to-do system overly complex. If these complex details were delivered together within the to-do list, it would still clog the channel and cause delays. This invention integrates to-do items into a unified model for information bodies, reducing the reading status of information bodies to just "read" and "unread." The remaining states of to-do items are recorded using independent business states. Each time a to-do is delivered via an information body, just like a message, only a small summary is required. The corresponding business state of the information body is updated only when the target user triggers an action through an interactive control. This independent business state allows the simple information body to be separated from the complex and diverse business operations, eliminating the need for the information body to frequently record and deliver numerous state changes and rules, nor does it need to adapt to complex and ever-changing business operations. The information body always maintains the simplicity of the model to ensure the uniformity of delivery efficiency and delivery methods; and the business itself has diverse characteristics. Even if there are countless types of businesses, each with countless states and rules, the information body remains unchanged.

[0138] In some embodiments of the present specification, by displaying the corresponding viewing status of an information body through the front end corresponding to at least one delivery channel, it is possible to ensure that the status of the same information body across different delivery channels is updated synchronously, thereby avoiding confusion in the status of the information body. For example, this can avoid a situation where the detailed content of an information body is displayed as read in the viewing status corresponding to one delivery channel, while the same information body is displayed as unread in the viewing status corresponding to other delivery channels.

[0139] In some embodiments of this specification, messages are split into briefings and details through lightweight information bodies, and only briefings are delivered each time, which can significantly improve delivery efficiency. The present invention replaces the complex content and business logic of messages, to-dos, and approvals to meet high-frequency, large-scale, timely, and diverse technical requirements. To-dos and approvals also have the characteristics of messages, which improves reach efficiency, weakens their own business rules, and improves scalability. Moreover, through the unified technical framework of the information body, the three independent technical frameworks of messages, to-dos, and approvals are integrated, and any subsequent business only needs to be connected once, which can save two-thirds of the connection volume. For target users, when viewing messages, to-dos, and approval flows, the style and operation are consistent, and the learning cost is lower.

[0140] It should be noted that the above description of the information transmission process is merely for illustration and purpose, and does not limit the scope of application of the present invention. Those skilled in the art will appreciate that various modifications and alterations to the information transmission process can be made under the guidance of the present invention. However, such modifications and alterations remain within the scope of the present invention. For example, steps 460 and 470 may be performed before step 440.

[0141] In some embodiments, since a process is a collection of multiple related to-do items, when a process needs to be initiated, the processing device can obtain the user node graph and create a to-do information body corresponding to the user node based on the user node graph. The processing device records the corresponding business status, thereby realizing the autonomous driving of the process. For more information about process information processing, please refer to Figure 5 and their corresponding descriptions.

[0142] Figure 5 is an exemplary flow chart of a process information processing method according to some embodiments of this specification. In some embodiments, Figure 5 As shown, the process information processing process 500 may include steps 510 to 550. In some embodiments, as Figure 5 As shown, the process information processing process 500 may further include steps 560 to 590. In some embodiments, Figure 5 One or more operations of the process information processing flow 500 may be performed in Figure 1 The information transmission system and process information processing system are implemented in the application scenario 100 shown. For example, Figure 5 The process information processing flow 500 shown may be stored in the storage device 130 in the form of instructions and called and / or executed by the processing device 110 .

[0143] Step 510 , obtaining a user node graph corresponding to the process. In some embodiments, step 510 may be performed by the user node graph obtaining module 310 .

[0144] A process is a collection of related to-do items. A process can include to-do items corresponding to at least two target users, with certain logical and / or temporal relationships between these to-do items. For example, taking an approval process as an example, an approval process includes three to-do items, corresponding to three user nodes. The first to-do item and the second to-do item are in an "or" relationship, and the third to-do item is the subsequent to-do item after the first or second to-do item is approved. That is, when at least one of the first to-do item or the second to-do item is processed by its corresponding user node and the processing result is approved, the approval process proceeds to the third to-do item.

[0145] A user node graph is a structured graph that describes the logical relationships between to-do items corresponding to different users. User nodes can include nodes and edges.

[0146] The nodes correspond to the users involved in the process. For example, Figure 6 As shown, the nodes may include node A, node B, node C, and node D.

[0147] The users involved in the process refer to the target users corresponding to at least two to-do items in the execution process.

[0148] Edges reflect the relationships between different users involved in the process.

[0149] Relationships may include logical relationships and / or temporal relationships.

[0150] Logical relationships refer to the inherent relationships between to-do items corresponding to different users based on judgment, reasoning, and other forms of thinking. For example, logical relationships can include "or" relationships and "and" relationships. For example, the user node diagram is as follows: Figure 6 As shown, the user nodes include node A, node B, node C, and node D, corresponding to user a, user b, user c, and user d, respectively. Edge AB represents that the relationship between user a and user b in the process is an "or" relationship, that is, when at least one of the first approval to-do item corresponding to user a or the second approval to-do item corresponding to user b is processed by the corresponding user a or user b and the processing result is passed, the approval process proceeds to the third approval to-do item corresponding to user c.

[0151] The temporal relationship refers to the order of the to-do items of different users in the time series, which reflects the temporal logic of the development and change of things. For example, Figure 6As shown, edge AC represents the temporal relationship between users a and c in the process, edge BC represents the temporal relationship between users b and c, and edge CD represents the temporal relationship between users c and d. The nodes pointed by arrows are later in the process sequence. That is, user c's third approval to-do comes after user a's first approval to-do, user c's third approval to-do comes after user b's second approval to-do, and user d's fourth approval to-do comes after user c's third approval to-do.

[0152] In some embodiments, the user node graph may be prepared by the initiator, or the system may pre-establish user node graphs corresponding to different processes.

[0153] Step 520 : Determine the first user based on the user node graph and obtain a first information body corresponding to the first user. In some embodiments, step 520 may be performed by the first information body obtaining module 320 .

[0154] The first user refers to the target user corresponding to the earliest node in the process.

[0155] In some embodiments, at the beginning of the process, the processing device may determine the target user associated with the earliest node in the user node graph as the first user. Figure 6 For example, from the directed edges in the graph, it can be determined that node A and node B correspond to the earliest nodes in the time sequence. Since node A and node B are in an "or" relationship, one can be selected as the first user from user A and user B corresponding to node A and node B.

[0156] The first information body refers to the information body corresponding to the first user. The first information body includes a first briefing and a first detailed content. The data volume of the first briefing is smaller than the data volume of the first detailed content. The first information body, the first briefing and the first detailed content are similar to the information body, briefing and detailed content described above, respectively. Figure 4 and its related descriptions.

[0157] In some embodiments, the detailed content of the information body corresponding to the users involved in the process may include business data related to the same business domain. It is understandable that since the above information body corresponds to the same project and / or task, the detailed content of the information body corresponding to the users involved in the process may include business data related to the same business domain.

[0158] The method of obtaining the first information body is similar to the method of obtaining the information body described above, which can be found in Figure 4 and its related descriptions.

[0159] Step 530: Send the first briefing to the first front end corresponding to the first user, so that the first briefing is displayed on the first front end. In some embodiments, step 530 may be performed by the first briefing display module 330. The first front end refers to the front end of the first user.

[0160] Step 530 is similar to step 420, see Figure 4 and its related descriptions.

[0161] Step 540 : In response to the first acquisition request sent by the first front end, send the first detailed content to the first front end so that the first detailed content is displayed on the first front end. In some embodiments, step 540 may be performed by the first detailed content display module 340 .

[0162] The first get request is similar to the get request described above, see Figure 4 and its related descriptions.

[0163] Step 540 is similar to step 430, see Figure 4 and its related descriptions.

[0164] Step 550 : In response to the first trigger operation sent by the first front end, obtain the first service status corresponding to the first information body. In some embodiments, step 550 may be performed by the first service status obtaining module 350 .

[0165] The first trigger operation and the first service state are similar to the trigger operation and service state described above, respectively. Figure 4 and its related descriptions.

[0166] In some embodiments, when the first detailed content includes an interactive control, the first triggering operation may include an operation of triggering the interactive control.

[0167] In some embodiments, when the process is an approval process, the interactive controls may include one or more of the following: an approval control, a rejection control, a signature control, a transfer control, a return control, and a revocation control. Accordingly, the business status of the information body corresponding to the users involved in the process may include one of the following: approval, rejection, signature, transfer, return, and revocation. Agree means that the target user at the current node approves the content of the current approval process, allowing the process to proceed to the next node; reject means that the target user at the current node rejects the content of the current approval process, usually returning the process to the initiator or the target user at the previous node, requesting modification or additional information; signature means that the target user at the current node cannot make a complete decision and needs to add one or more additional users to participate in the current approval process; transfer means that the target user at the current node is unable or unwilling to handle this to-do and completely transfers the to-do to a designated other user for processing; return means returning the current approval process to a specific previous node, usually to allow the previous user to review or modify it; and revocation means that the initiator actively withdraws the approval process application they initiated before the process is completed, and the approval process will be terminated and no longer flow.

[0168] In some embodiments of this specification, all actions related to messages, pending tasks, and approvals are refined into six business states: approve, reject, transfer, sign, cancel, and return. This eliminates the need for repeated development due to business changes. Because approval tasks in the approval process correspond one-to-one with information bodies, six interactive controls are presented within the detailed content. In response to the target user executing a triggering action through the interactive controls, the corresponding business state of the information body can be directly updated.

[0169] Step 550 is similar to step 440, see Figure 4 and its related descriptions.

[0170] In some embodiments, the processing device can update the business data in the business domain based on the business status of the information body corresponding to the user involved in the process. For more information about updating business data, please refer to Figure 4 and their corresponding descriptions.

[0171] Step 560 : Determine a second user based on the user node graph and the first service state, and obtain a second information body corresponding to the second user. In some embodiments, step 560 may be performed by the loop module 360 ​​.

[0172] The second user refers to the target user corresponding to the node of the next time sequence in the process. For example, the second user may be the target user corresponding to the node of the second time sequence in the process.

[0173] In some embodiments, when the first service status changes to the processed status, the processing device may determine the user associated with the next sequential node in the user node graph as the second user. Figure 6 For example, when the first user is user A corresponding to node A, and the first service status corresponding to the first information body is approved, then based on the directed edge in the user node graph, it can be determined that user C corresponding to node C is the second user. Figure 6 For example, when the first user is user A corresponding to node A, and the first service status is transferred to user B corresponding to node B, the processing device may determine user B as the second user.

[0174] The second information body refers to the information body corresponding to the second user. The second information body includes a second briefing and second detailed content. The data volume of the second briefing is smaller than the data volume of the second detailed content. The second information body, the second briefing and the second detailed content are similar to the information body, briefing and detailed content described above, respectively. Figure 4 It can be understood that the first information body is the information body related to the business event corresponding to the earliest node in the process, and the second information body is the information body related to the business event corresponding to the next node in the process.

[0175] The method of obtaining the second information body is similar to the method of obtaining the information body described above, which can be seen in Figure 4 and its related descriptions.

[0176] Step 570: Send the second briefing to the second front end corresponding to the second user, so that the second briefing is displayed on the second front end. In some embodiments, step 570 can be performed by the loop module 360. The second front end refers to the front end of the second user.

[0177] Step 570 is similar to step 420, see Figure 4 and its related descriptions.

[0178] Step 580 : In response to the second acquisition request sent by the second front end, send the second detailed content to the second front end so as to display the second detailed content on the second front end. In some embodiments, step 580 may be performed by the loop module 360 ​​.

[0179] The second get request is similar to the get request described above, see Figure 4 and its related descriptions.

[0180] Step 580 is similar to step 430, see Figure 4 and its related descriptions.

[0181] Step 590 : In response to the second trigger operation sent by the second front end, obtain the second service state corresponding to the second information body. In some embodiments, step 590 may be performed by the loop module 360 ​​.

[0182] The process of obtaining the second service status is similar to the process of obtaining the first service status, and reference may be made to the above and related descriptions.

[0183] In some embodiments, if the preset process termination condition is not met after executing step 590, the processing device may continue to execute steps 560-590. And so on until the preset process termination condition is met. It should be noted that after executing step 590, when executing step 560 again, the processing device does not determine the second user based on the user node graph and the first business status and obtain the second information body corresponding to the second user. Instead, the processing device determines the second user based on the user node graph and the second business status determined in step 590 and obtains the second information body corresponding to the second user.

[0184] A process termination condition refers to the condition for terminating a loop. This condition occurs when the business status of the user's information body corresponding to any node in the user node graph is rejected, or when the business status of the user's information body corresponding to the last node in the user node graph is approved. If the business status of the user's information body corresponding to any node in the user node graph is rejected, the process fails and the loop can be terminated. If the business status of the user's information body corresponding to the last node in the user node graph is approved, the process passes and the loop can also be terminated.

[0185] Taking the approval process as an example, the existing approval system creates an approval task for each user involved in each approval node. The business associated with the approval must be bound to the task of each user at each node. This means that each business must be bound to the task of each user at each node for each approval, making integration complex and prone to errors. Furthermore, in addition to being bound to a large number of sub-tasks, the business must also send messages to the user corresponding to each sub-task, such as telling the user "It's your turn to approve" or notifying the user of a "change in the business status of the node." When integrating the business with the approval flow, it requires connecting to a large number of approval tasks, messages, and approval status changes to reach users. Furthermore, this rigid format makes integration difficult.

[0186] After the present invention integrates approval into a unified model of information bodies, businesses only need to interface with the processing device, and the processing device with the information body. This requires establishing a connection between the business domain identifier, approval flow identifier, and information identifier, making this integration quite simple. When the processing device initiates the approval flow, it can bind the business domain identifier and the approval flow identifier. When creating an information body, the processing device can bind the approval flow identifier and the information identifier. The processing device automatically creates tasks for each user under each node, and each task automatically creates an information body, binding the task identifier and the information identifier. The task switches are now bound to the corresponding switches in the information body. Task on, indicating that the information body is on, indicates that the user has approved and submitted the information body for approval. Task off, indicating that the information body is off, indicates that the user has completed approval and submitted the information body for approval. The approval flow identifier and task identifier are unique codes for the approval flow and task, respectively. For example, the approval flow identifier and task identifier can be identifiers for the approval flow and task, respectively, and can be composed of letters, numbers, symbols, etc.

[0187] In some embodiments of this specification, the sending timing of each to-do information body in the process is automatically determined based on the user node graph, and the business data is automatically updated based on the to-do results, thereby realizing intelligent driving of the process to-do and automatic updating of business data.

[0188] It should be noted that the above description of the process information processing flow is for illustrative purposes only and does not limit the scope of application of the present invention. Those skilled in the art will appreciate that various modifications and alterations to the process information processing flow can be made under the guidance of the present invention. However, such modifications and alterations remain within the scope of the present invention.

[0189] While the basic concepts have been described above, it will be apparent to those skilled in the art that the detailed disclosure is merely illustrative and does not limit the present invention. Although not explicitly described herein, those skilled in the art may make various modifications, improvements, and revisions to the present invention. Such modifications, improvements, and revisions are suggested in the present invention and remain within the spirit and scope of the exemplary embodiments of the present invention.

[0190] At the same time, the present invention uses specific terms to describe embodiments of the present invention. For example, "some embodiments" refers to a feature, structure, or characteristic associated with at least one embodiment of the present invention. In addition, certain features, structures, or characteristics in one or more embodiments of the present invention may be appropriately combined.

[0191] In addition, unless expressly stated in the claims, the order of the processing elements and sequences, the use of alphanumeric characters, or the use of other names described in the present invention are not intended to limit the order of the processes and methods of the present invention. Although the above disclosure discusses some embodiments of the invention that are currently considered useful through various examples, it should be understood that such details are for illustrative purposes only, and the appended claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that are consistent with the spirit and scope of the embodiments of the present invention. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing server or mobile device.

[0192] Similarly, it should be noted that, in order to simplify the presentation of the present disclosure and facilitate understanding of one or more embodiments of the invention, the foregoing descriptions of the embodiments of the invention sometimes combine multiple features into a single embodiment, figure, or description thereof. However, this disclosure method does not imply that the subject matter of the invention requires more features than those recited in the claims. In practice, an embodiment may have fewer features than the totality of the features of a single embodiment disclosed above.

[0193] Each patent, patent application, patent application publication, and other materials, such as articles, books, specifications, publications, and documents, cited herein is hereby incorporated by reference in its entirety. This excludes any application history that is inconsistent with or conflicts with the present disclosure, including any document (currently or subsequently appended to this disclosure) that limits the broadest scope of the claims of this disclosure. It should be noted that if the descriptions, definitions, and / or terminology used in the accompanying materials are inconsistent or conflicting with the present disclosure, the descriptions, definitions, and / or terminology used in this disclosure will control.

[0194] Finally, it should be understood that the embodiments described herein are intended only to illustrate the principles of the present invention. Other variations may also fall within the scope of the present invention. Therefore, by way of example and not limitation, alternative configurations of the embodiments of the present invention may be considered consistent with the teachings of the present invention. Accordingly, the embodiments of the present invention are not limited to the embodiments explicitly described and illustrated herein.

Claims

1. A process information processing method, characterized in that: include: In response to a business event that triggers a process, a to-do information body and a message information body are created. The to-do information body includes a first information body and a second information body. The message information body is sent to users involved in the business event for one-way notification of information. The detailed content of the message information body does not include interactive controls. The to-do information body is sent to users involved in the process. Obtain a user node graph corresponding to the process; the user node graph includes nodes and edges, the nodes correspond to users involved in the process, and the edges reflect the relationships between different users involved in the process in the process, including logical relationships and temporal relationships; Determining a first user based on the user node graph and obtaining a first information body corresponding to the first user; the first information body includes a first briefing and first detailed content, the first briefing having a smaller data volume than the first detailed content, the first detailed content including a first interactive control, and the first information body further including at least one delivery channel identifier; Based on the at least one delivery channel identifier, determining at least one first front end corresponding to each of the at least one delivery channel; sending the first presentation to the at least one first front end, so as to display the first presentation on the first front end; In response to a first acquisition request sent through the first front end, sending the first detailed content to the first front end so as to display the first detailed content on the first front end; In response to a first trigger operation on the first interactive control sent by the first front end, obtaining a first business status corresponding to the first information body, the first business status including one of the following states: approval, rejection, endorsement, transfer, return, and revocation; as well as Perform at least one round of information processing until the preset process termination condition is met; Each round of information processing in the at least one round of information processing includes: Determining a second user based on the user node graph and the first service state or a second service state determined in a previous round of information processing, and obtaining a second information body corresponding to the second user; the second information body includes a second briefing and second detailed content, the second briefing having a smaller data volume than the second detailed content, and the second detailed content including a second interactive control; sending the second briefing to a second front end corresponding to the second user, so as to display the second briefing on the second front end; In response to a second acquisition request sent through the second front end, sending the second detailed content to the second front end so as to display the second detailed content on the second front end; and In response to a second triggering operation on the second interactive control sent through the second front end, a second business status corresponding to the second information body is obtained.

2. The method according to claim 1, characterized in that The detailed content of the information body corresponding to the users involved in the process includes business data related to the same business domain.

3. The method according to claim 1, characterized in that The method further comprises: Based on the business status of the information body corresponding to the user involved in the process, the business data in the business domain is updated.

4. The method according to claim 1, wherein The process termination condition includes that the business status of the user's information body corresponding to any node in the user node graph is rejected, or the business status of the user's information body corresponding to the last node in the user node graph is agreed, and the last node is the last node in the user node graph in time sequence.

5. The method according to claim 1, wherein The method further comprises: In response to the first acquisition request sent by the first front end, changing the reference status corresponding to the first information body from unread to read; and The review status corresponding to the first information body is displayed through the at least one first front end corresponding to the at least one delivery channel.

6. A process information processing system, characterized in that: include: A user node graph acquisition module is configured to, in response to a business event that triggers a process, create a to-do information body and a message information body, wherein the to-do information body includes a first information body and a second information body, and the message information body is sent to users involved in the business event for one-way information notification. The detailed content of the message information body does not include interactive controls, and the to-do information body is sent to users involved in the process; obtain a user node graph corresponding to the process; the user node graph includes nodes and edges, wherein the nodes correspond to users involved in the process, and the edges reflect the relationships between different users involved in the process in the process, wherein the relationships include logical relationships and temporal relationships; a first information body acquisition module configured to determine a first user based on the user node graph and acquire a first information body corresponding to the first user; the first information body including a first briefing and first detailed content, the first briefing having a smaller data volume than the first detailed content, the first detailed content including a first interactive control, and the first information body further including at least one delivery channel identifier; A first briefing display module is configured to determine at least one first front end corresponding to each of the at least one delivery channel based on the at least one delivery channel identifier; sending the first presentation to the at least one first front end, so as to display the first presentation on the first front end; a first detailed content display module, configured to send the first detailed content to the first front end in response to a first acquisition request sent through the first front end, so as to display the first detailed content on the first front end; A first business status acquisition module is configured to, in response to a first trigger operation on the first interactive control sent by the first front end, acquire a first business status corresponding to the first information body, where the first business status includes one of the following states: approved, rejected, endorsed, transferred, returned, or revoked; as well as a loop module configured to perform at least one round of information processing until a preset process termination condition is met; Each round of information processing in the at least one round of information processing includes: determining a second user based on the user node graph and the first business state or the second business state determined in the previous round of information processing, and obtaining the second information body corresponding to the second user; the second information body includes a second briefing and second detailed content, the data volume of the second briefing is smaller than the data volume of the second detailed content, and the second detailed content includes a second interactive control; sending the second briefing to the second front end corresponding to the second user to display the second briefing on the second front end; in response to a second acquisition request sent through the second front end, sending the second detailed content to the second front end to display the second detailed content on the second front end; and, in response to a second trigger operation on the second interactive control sent through the second front end, obtaining the second business state corresponding to the second information body.

Images