Information sending method, device and computer equipment

Abstract

The embodiments of this specification provide a method, apparatus, and computer device for sending information. The method may include: upon receiving a transaction event notification issued by a transaction platform, constructing an event form; matching the event form in a tag library to obtain a tag corresponding to the event form, with the tag serving as a target tag; wherein the tag library includes at least one tag; executing a processing rule in a rule set with the target tag as a trigger condition for the event form to obtain output transaction information; wherein the rule set includes processing rules and trigger conditions for the processing rules; and sending the transaction information to the transaction platform. The method can improve the data flow efficiency of the transaction system.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of computer application technology, and more specifically, to an information sending method, an information sending device, and a computer device. Background Art

[0002] Transaction systems are typically divided into client-side and business-side systems. The client-side primarily serves clients and consumers, while the scope of the business-side is more ambiguous, encompassing systems used by suppliers or businesses. The starting points and priorities for building client-side and business-side systems are completely different. Business-side systems prioritize processes and modularity, emphasizing abstraction and structure, and emphasizing holistic planning and system design. C-side systems prioritize user experience, emphasizing sensory experience, and continuous data analysis. However, the data flow in transaction systems using traditional technologies needs to be improved. Summary of the Invention

[0003] In view of this, the embodiments of this specification are dedicated to providing an information sending method, apparatus, computer equipment, storage medium and computer program product to solve the technical problem that the data flow method of the transaction system in traditional technology needs to be improved.

[0004] An embodiment of the present specification provides an information sending method, which is applied to a transaction support platform, the method comprising: upon receiving a transaction event notification issued by a transaction platform, constructing an event ticket; wherein the event ticket includes the event content of the transaction event attached to the transaction event notification; matching the event ticket in a tag library to obtain a tag corresponding to the event ticket, and the tag serving as a target tag; wherein the tag library includes at least one tag; executing a processing rule in a rule set with the target tag as a trigger condition for the event ticket to obtain output transaction information; wherein the rule set includes processing rules and trigger conditions for the processing rules; and sending the transaction information to the transaction platform.

[0005] An embodiment of the present specification provides an information sending device, which is applied to a transaction support platform, and the device includes: an event ticket construction module, which is used to construct an event ticket when a transaction event notification issued by a transaction platform is received; wherein, the event ticket includes the event content of the transaction event attached to the transaction event notification; an event ticket matching module, which is used to match the event ticket in a tag library to obtain a tag corresponding to the event ticket, and the tag serves as a target tag; wherein, the tag library includes at least one tag; an event ticket processing module, which is used to execute a processing rule in a rule set with the target tag as a trigger condition for the event ticket to obtain output transaction information; wherein, the rule set includes processing rules and trigger conditions for the processing rules; and a transaction information sending module, which is used to send the transaction information to the transaction platform.

[0006] An embodiment of this specification provides a computing device including a memory and a processor, wherein the memory stores a computer program, and the processor implements the method steps in the above embodiment when executing the computer program.

[0007] An embodiment of this specification provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the method steps in the above embodiment are implemented.

[0008] An embodiment of this specification provides a computer program product, which includes instructions. When the instructions are executed by a processor of a computer device, the computer device can perform the method steps in the above embodiment.

[0009] In the implementation method of this specification, a transaction support platform receives a transaction event notification from a transaction platform, thereby constructing an event ticket, matching the event ticket with a tag library, and obtaining a target tag corresponding to the event ticket. The event ticket is then processed using a processing rule with the target tag as a trigger condition to obtain transaction information, which is then sent to the transaction platform. This changes the traditional process of using the transaction platform to process event tickets, and introduces the transaction support platform, which not only improves the efficiency of data flow in the transaction system, but also enhances the scalability of the transaction platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1a FIG2 is an example diagram of a scenario module of an information sending method in a scenario example provided in one embodiment;

[0011] Figure 1b FIG2 is a schematic diagram of an application environment of an information sending method in a scenario example provided by an embodiment;

[0012] Figure 1c FIG2 is a schematic diagram of module interaction between a transaction platform and a transaction support platform in a scenario example provided by an embodiment;

[0013] Figure 2 FIG2 is a flow chart of an information sending method provided in one embodiment of the present specification;

[0014] Figure 3 The figure shows a functional module diagram of an information sending device provided in one embodiment of this specification. DETAILED DESCRIPTION

[0015] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this specification.

[0016] In a specific scenario example, the transaction platform adopts the prescription platform and the transaction support platform adopts the rule management platform. The rule management platform can correspond to multiple transaction platforms, and the prescription platform can be just one of the multiple transaction platforms.

[0017] The rule management platform can deploy a tag library and rule set specific to the prescription platform. Tags can be understood as keywords used to describe user attributes and event attributes. Processing rules can be understood as the business logic followed when processing transaction data during transaction execution. Each tag in the tag library has an applicable rule. The applicable rule for any tag can be used to determine whether to label an object with that tag. For example, the tag could be "elderly," and the applicable rule for the tag could be age over 65. If a user is 67 years old, they could be labeled "elderly." Another example is the tag "high-risk," and the applicable rule for the tag could be age over 65 and chronic conditions. If a user is 67 years old and their medical history includes diabetes, a medical consultation event triggered by this user could be labeled "high-risk." The applicable rule for the tag "high-risk" could also be age under 16 and the purchase of psychotropic medications. If a user is 14 years old and purchases ethanoylamine, a medication purchase event triggered by this user could be labeled "high-risk."

[0018] In this scenario example, the rule management platform provides a rule configuration management interface. Through the rule configuration management interface, the transaction administrator can define transaction categories, transaction scenarios, events, tags, and processing rules. Figure 1a. Among them, transaction categories can correspond to the transaction areas involved in the transaction platform. For example, medical guidance can be understood as the functional area of guiding users to medical treatment. Transaction scenarios can correspond to transaction needs in specific scenarios within the transaction area. For example, transaction scenarios can be segmented transactions in the medical guidance field, such as hospital guidance, department guidance, and doctor guidance. Events can be understood as operations issued by users in a certain transaction scenario. For example, the application for prescription issued by users on the prescription platform, the prescription operation issued by doctors on the prescription platform, and the prescription review operation issued by pharmacists on the prescription platform. Tags can be understood as keywords used to describe user attributes and event attributes. For example, tags can be chronic disease label judgment, self-operated men's department, nighttime distribution, and whether it is high-risk. Processing rules can be understood as the transaction logic followed in the processing of transaction data during transaction execution. For example, rule entries, rule groups, and rule details.

[0019] The transaction support platform may provide a transaction customization page for the prescription platform, through which the transaction customization page may be used to configure the logical units of the labels of the prescription platform and the logical implementation of the labels.

[0020] See also Figure 1b The user client, doctor client, and pharmacist client communicate with the prescription platform. The prescription platform communicates with the rule management platform. Figure 1c The prescription platform includes a transaction layer. The transaction support platform includes an application layer, an engine layer, and an operations and maintenance layer. The platform layer provides a guidance platform service module, a transaction tag management module, a tag registration center, a transaction rule management module, a scheduling center, and a task center. The engine layer provides an event processing center, a tag verification center, and a rule engine. The operations and maintenance layer provides a link tracking module, a performance analysis module, and a transaction statistics module.

[0021] In this scenario example, the user may be a 67-year-old male elderly man with diabetes who needs to see a doctor. The user accesses the prescription platform through the user client. The prescription application page is displayed in the interface of the user client, and the name, age, gender, description of the condition and other information entered by the user are received through the prescription application page. The user client generates an application request for the prescription based on the information entered by the user and sends the application request to the prescription platform. The application request may be accompanied by the user's age, gender, medical history description, etc. The medical guidance event is triggered on the transaction layer of the prescription platform based on the application request. The medical guidance event has event content, and the event content includes the user's age, gender, medical history description, etc. In this scenario example, the event content specifically includes 67 years old, male and history of diabetes.

[0022] Please continue reading Figure 1cWhen a medical consultation event is triggered on the prescription platform, the event processing center on the rule management platform receives a notification of the medical consultation event. Based on the notification, the event processing center creates an event ticket for the medical consultation matter. The event ticket can include information such as age 67, male, and a history of diabetes.

[0023] In the label verification center, the event content of the event sheet is matched with the applicable rules of the label to obtain the target label corresponding to the medical guidance event sheet. For example, as mentioned above, the applicable rules of the label "high risk" can be that the age is greater than 65 years old and has chronic diseases. The event content "67 years old, male and history of diabetes" is matched with the applicable rule "age is greater than 65 years old and has chronic diseases", and it is obtained that 67 years old is greater than 65 years old and the history of diabetes meets the requirement of having chronic diseases, thereby determining that the event content of the medical guidance event sheet meets the applicable rules of the label "high risk". Thus, a "high risk" label is added to the event sheet.

[0024] The event sheet marked with the "high-risk" label is processed in the rule engine to obtain the corresponding transaction information. Exemplarily, the rule engine includes a rule set, and the rule set includes processing rules. The processing rule corresponding to the "high-risk" label is determined in the rule set, and the event sheet is processed using the processing rule corresponding to the "high-risk" label to obtain reminder information. The event sheet is processed using the processing rule corresponding to the "high-risk" label to obtain hospital information, department information, and doctor information suitable for the user. The obtained reminder information, hospital information, department information, and doctor information are returned to the prescription platform.

[0025] For example, the reminder message may be "This user is elderly and has a history of diabetes. Please use medication XX with caution." The hospital information may be the hospital name or hospital ID. The department information may be the department name or department ID. The doctor information may be the doctor name or doctor ID.

[0026] In this scenario, please continue to refer to Figure 1c . The rule management platform is provided with a dispatch center and a task center corresponding to the prescription platform. A dispatch form is generated according to the transaction information and the event form; wherein the dispatch form includes a platform identifier representing the prescription platform; and the dispatch form is sent to the task center of the prescription platform represented by the platform identifier. The task center sends the transaction information to the transaction platform. The transaction information may include at least one of the reminder information, hospital information, department information, and doctor information mentioned above.

[0027] It is understood that the embodiments of this specification provide an information transmission system that may include a hardware environment formed by a client and a server. The client communicates with the server via a network. The client may be an electronic device with network access capabilities. Specifically, for example, the client may be a desktop computer, tablet computer, laptop computer, smartphone, digital assistant, smart wearable device, shopping guide terminal, television, smart speaker, microphone, etc. Smart wearable devices include but are not limited to smart bracelets, smart watches, smart glasses, smart helmets, smart necklaces, etc. Alternatively, the client may be software that can run on the above-mentioned electronic devices. The server may be an electronic device with certain computing and processing capabilities. It may have a network communication module, a processor, and memory. Of course, the server may also refer to the software running on the electronic device. The server may also be a distributed server, which may be a system with multiple processors, memories, network communication modules, etc. operating in coordination. Alternatively, the server may be a server cluster formed by multiple servers. Alternatively, with the advancement of science and technology, the server may also be a new technical means capable of implementing the corresponding functions of the embodiments of this specification. For example, it may be a new form of "server" based on quantum computing.

[0028] See also Figure 2 The present disclosure provides a method for sending information. The method can be applied to a transaction support platform. The method includes the following steps.

[0029] Step S210: upon receiving a transaction event notification from the transaction platform, construct an event ticket.

[0030] In this embodiment, the event ticket may include the event content of the transaction event accompanying the transaction event notification. The event ticket can serve as an information medium for the transaction event, carrying the event content of the transaction event. Thus, during the transaction support platform's response to the transaction event notification, the event ticket can carry the event content of the transaction event and serve as data support for multiple aspects of the transaction support platform. Specifically, the event ticket may be document data describing the transaction event. The event ticket itself is used to record, process, and track the completion results of the work task corresponding to the transaction event. The event ticket includes some basic information. For example, basic information may include contextual information before and after the transaction event occurs. Contextual information may include the transaction platform's identification information, information about the operating interface involved, and information about the triggered button. In some embodiments, basic information may also include attribute information of the user who triggered the transaction event. For example, if the transaction platform is a prescription platform, attribute information may include name, gender, age, and medical history data. For example, if the transaction platform is a food delivery platform, attribute information may include name, contact information, address, and dish.

[0031] A transaction event notification can be data information proactively sent by the transaction platform to the transaction support platform to notify the transaction support platform of a transaction event. This notification can be proactively pushed from the transaction platform to the transaction support platform. Alternatively, the transaction platform can record the transaction content of transaction events that occurred over a period of time and, upon reaching the notification transmission cycle set for the transaction platform, send a transaction event notification with the event content to the transaction support platform. Alternatively, the transaction platform can record the transaction content of transaction events that occurred and, upon receiving a notification request from the transaction support platform, generate a transaction event notification based on the recorded transaction content and send it to the transaction support platform.

[0032] In some implementations, the transaction platform can respond to transaction events according to a predefined response process. The transaction platform sends a transaction event notification to the transaction support platform, prompting the transaction support platform to respond to the transaction event notification. The transaction platform's response to the transaction event and the issuance of the transaction event notification to the transaction support platform can be asynchronous.

[0033] Transaction events can be events related to actual transactions that occur in the transaction platform. Specifically, for example, the operation of a user ordering takeout on a takeout platform. Or, for example, a medical guidance event, a prescription event, a prescription review event, etc. triggered by a user on a prescription platform. Or, for example, a travel destination recommendation event triggered on a travel platform. In this embodiment, a transaction event can trigger the transaction response process of the transaction platform and trigger the event response processing process of the transaction support platform. For example, when a transaction event occurs on the transaction platform, it can cause a response pre-set by the transaction support platform. In response to the occurrence of a transaction event, the transaction support platform can generate a corresponding transaction data stream.

[0034] A transaction platform is an abstract implementation of a specific transaction domain. It can quickly address most transactional needs within that domain and provide open extension interfaces. It abstracts the fundamental elements, core concepts, core objects, and core values of a specific transaction domain, thereby extracting a limited number of transactional components and continuously optimizing them. Transactional needs are met through the orchestration of these components. A transaction platform can be used in the healthcare industry, for food delivery services, or for travel services.

[0035] Data communication can be carried out between the transaction platform and the transaction support platform. When the transaction platform receives a request instruction triggered by a user for a transaction event, in order to respond to the transaction event triggered by the user in a timely and rapid manner, the transaction platform can proactively send a transaction event notification to the transaction support platform. The transaction event notification is accompanied by a transaction event, and the transaction event corresponds to the event content. The transaction support platform has an event processing function center, which triggers an event mechanism through the event processing center and generates an event form based on the event content. In some embodiments, a corresponding embedding point can be pre-set in the operation interface of the user client for triggering a transaction event. The embedding point monitors the transaction event triggered by the user and provides a transaction event notification to the transaction support platform, so that it can establish an event form.

[0036] Step S220: Match the event list in the tag library to obtain a tag corresponding to the event list, and use the tag as the target tag.

[0037] In this embodiment, the tag library may include at least one tag. The tag library can be understood as a database for storing tags, or as a tag set consisting of several tags. A tag can be understood as a keyword used to describe user attributes or event attributes.

[0038] The transaction support platform may have a label verification center. The label corresponding to the event list is obtained through the label verification center. In some embodiments, since the correspondence between transaction events and labels has been defined in advance, the transaction event may correspond to at least one label, and the event list can be matched with the label corresponding to the transaction event to obtain the label corresponding to the event list. The label corresponding to the event list is determined as the target label. In some embodiments, the label corresponding to the event list can be determined in the label library based on the semantic similarity between the label in the label library and the event content of the event list, and the label corresponding to the event list is determined as the target label.

[0039] Step S230: executing a processing rule in a rule set with the target tag as a trigger condition for the event ticket to obtain output transaction information.

[0040] In this embodiment, the rule set may include processing rules and triggering conditions of the processing rules. The processing rules can be understood as the business logic followed in the processing of transaction data during the execution of the transaction event. The triggering conditions of the processing rules can be the starting conditions that can trigger the corresponding processing rules to process the event form. Transaction information is the information related to the transaction obtained by processing the event form using the processing rules. In some embodiments, the transaction information can also be the result information obtained after the event form is processed. The transaction information can also be a reminder message generated for the processing result of the event form. The transaction information can also be a label generated for the processing result of the event form.

[0041] The transaction support platform may have a rule engine. The event list is obtained through the rule engine to perform transaction rule calculations. In order to respond to the results caused by the transaction event triggered by the user, after determining the target tag corresponding to the event list, it is necessary to call the processing rules to process the event list to obtain further transaction messages. Specifically, the rule set may include at least one processing rule. Each processing rule has a corresponding triggering condition. The triggering condition of the processing rule is related to the tag, and the target tag corresponding to the event list is matched with the triggering condition corresponding to each processing rule, and the processing rule with the target tag as the triggering condition is determined in the rule set. The event list is used as input, and the transaction rule is calculated on the time list using the processing rules to obtain the transaction information of the event list.

[0042] Step S240: Send the transaction information to the transaction platform.

[0043] In this embodiment, in order to present the transaction information to the user's operation interface, the user can know the result of the transaction event triggered by it. After receiving the transaction message, the transaction support platform can send the transaction information to the transaction platform separately. The transaction support platform can also return the processed event form to the transaction platform, and the transaction platform can add the transaction information to the event form to show the user the content of the final event form. In some embodiments, the event form can be stored on the transaction support platform after being constructed by the event processing center of the transaction support platform. In this way, after obtaining the transaction information, the transaction support platform can fill the transaction information into the event form to form the final event form. The transaction support platform sends the final event form with the transaction information to the transaction platform. Of course, in some embodiments, the transaction support platform can use other forms to feed back the transaction information to the transaction platform, and is not limited to providing the event form to the transaction platform after adding the transaction information to the event form.

[0044] The above-mentioned information transmission method receives transaction event notifications from the transaction platform through the transaction support platform, which then constructs an event ticket and matches the event ticket with a tag library to obtain a target tag corresponding to the event ticket. The event ticket is then processed using a processing rule that uses the target tag as a trigger condition to obtain transaction information, which is then sent to the transaction platform. This changes the traditional process of using the transaction platform to process event tickets. Introducing the transaction support platform not only improves the efficiency of data flow in the transaction system but also enhances the scalability of the transaction platform.

[0045] In some embodiments, tags in the tag library correspond to applicable rules. Accordingly, matching the event ticket with the tag library to obtain a tag corresponding to the event ticket, with the tag serving as the target tag, includes matching the event content of the event ticket with the applicable rules of the tag to obtain the target tag. The event content of the event ticket complies with the applicable rules of the target tag.

[0046] In this embodiment, an applicable rule can be a logical condition used to determine whether to label a data object. An applicable rule can be a single condition. For example, the label can be "elderly," and the applicable rule for the label "elderly" can be age greater than 65. An applicable rule can also be a complex condition. For example, the label can be "baby boy," and the applicable rule for the label "boy" can be gender male and age less than 22 months.

[0047] The transaction support platform may include a tag verification center. Tags corresponding to event tickets are obtained through the tag verification center. In some embodiments, tags in the tag library correspond to applicable rules. The event content of the event ticket is matched with the applicable rules of each tag in the tag library to determine whether the event content of the event ticket meets the logical conditions required by the applicable rules of each tag. If the event content of the event ticket meets the applicable rules of a particular tag, the tag corresponding to the applicable rule is determined as the target tag.

[0048] In this embodiment, by setting applicable rules for the tags in the tag library, the event content of the event form is matched with the applicable rules of the tag, and the target tag corresponding to the event form is determined based on the matching results, thereby improving the matching degree between the tag of the event form and the transaction event, labeling the transaction tag more accurately, and improving the credibility of the transaction information.

[0049] In some embodiments, the transaction support platform corresponds to multiple transaction platforms, and each transaction support platform is provided with a label library corresponding to each transaction platform, with the label libraries for each transaction platform being different. Accordingly, the step of matching the event ticket with the label library to obtain a label corresponding to the event ticket, and using the label as the target label, may include: matching the event ticket with the label library corresponding to the transaction platform to obtain a label corresponding to the event ticket, and using the label as the target label.

[0050] In some cases, the transaction support platform can serve as a foundational platform supporting multiple transaction platforms. This allows developers working on different transaction platforms to focus on the transaction processing workflow for front-end transactions. The transaction support platform can support multiple transaction platforms, improving overall development efficiency.

[0051] In this embodiment, the transaction support platform can serve as a rule management platform and can configure corresponding processing rules for different transaction platforms. Specifically, the transaction support platform can configure a tag library for each transaction platform. This allows the tags in the tag library to be highly targeted. Furthermore, matching event tickets with the tag library corresponding to the transaction platform can reduce the computational complexity of tag matching for event tickets to a certain extent.

[0052] In some embodiments, the tag library is divided into multiple tag categories based on transaction type. Accordingly, when matching the event ticket with the tag library to obtain a tag corresponding to the event ticket, using the tag as the target tag, the method may include: determining a target tag category for the event ticket from among the multiple tag categories in the tag library; and matching the event ticket with tags included in the target tag category to obtain a target tag corresponding to the event ticket.

[0053] In some cases, to further reduce the computational effort required to match event tickets with tags, the tags in the tag library can be categorized based on the transaction type of the transaction event. This allows matching operations to be performed on event tickets with tags of the corresponding transaction type.

[0054] In this embodiment, transaction types can be divided according to the actual transactions of the transaction platform. Specifically, for example, the transaction platform can be a medical guidance platform, which is divided into multiple transaction stages according to the transaction process. The transaction stages can be divided into the medical guidance stage, the order dispatching stage, the prescription issuance stage, the prescription review stage, and the write-off stage. The actual transactions in each transaction stage can be different. For example, the medical guidance stage performs medical guidance transactions, and the order dispatching stage performs order dispatching transactions. In this way, different transactions perform different transaction events and have corresponding requirements for tags. Multiple transaction types can be divided according to the transaction stages. Furthermore, tag types can be divided according to the transaction types. For example, tag types can include medical guidance tag types, order dispatching tag types, prescription issuance tag types, prescription review tag types, and write-off tag types. Different tag types each include multiple tags. Furthermore, when matching event forms with tags, the target tag category can be determined first, and then further matching can be performed to obtain the target tag.

[0055] In some embodiments, the method of determining the target label category may include: each label type may be provided with a type characterization vector, and an event characterization vector representing the content of the event list is generated based on the event list. The vector distance between the type characterization vector and the event characterization vector may be calculated, and the label category corresponding to the type characterization vector with the smallest distance may be determined as the target label category. Alternatively, the probability that the event list belongs to each label category is calculated, and the label category with the largest probability is determined as the target label category. Alternatively, the number of labels in each label category included in the event list is counted separately, and the label category with the largest number is determined as the target label category. Of course, those skilled in the art may also adopt other technical solutions, which will not be repeated here.

[0056] In some embodiments, the tag library binds multiple tags to the transaction event. Accordingly, matching the event ticket with the tag library to obtain a tag corresponding to the event ticket, using the tag as the target tag, includes: matching the event ticket with the multiple tags bound to the transaction event to obtain a target tag corresponding to the event ticket.

[0057] In this embodiment, a transaction event can be bound to multiple tags. A transaction event may not specifically refer to a certain event, but may be used to represent a type or category of events. A transaction event can be bound to multiple tags, so that a tag can be added to each specific transaction event according to the event content of each specific transaction event. Specifically, for example, a transaction event may be a transaction event notification sent to a transaction support platform after the transaction platform receives an application request for generating a prescription. The transaction support platform may determine the multiple tags corresponding to the transaction event based on the content of the transaction event notification. Furthermore, the target tag is obtained by matching the multiple tags corresponding to the transaction event based on the event content.

[0058] In some embodiments, the event content includes tags. The information sending method may further include: if the transaction event targeted by the transaction event notification is a tag addition event, adding the tags included in the event content to the tag library; or, if the event content includes a specified tag, adding the tags included in the event content to the tag library.

[0059] In this embodiment, the transaction support platform may have a tag registration center. The transaction support platform may call the tag registration center to add tags to the tag library. Specifically, for example, the transaction support platform may determine whether a transaction event is a tag addition event based on a transaction event notification. Specifically, the transaction event notification may carry an event type identifier of the transaction event. The transaction support platform may determine whether the transaction event corresponding to the transaction event notification is a tag addition event based on the event type identifier. Thus, when it is determined that the transaction event is a tag addition event, the transaction support platform may identify the newly added tags in the event content attached to the transaction event notification. In some embodiments, the newly added tags in the event content may have a specific format or be marked with specified symbols. For example, "#tag#", and the content between the two "#" symbols is regarded as a tag.

[0060] In some embodiments, it may be determined whether there are newly added tags in the event content by whether there is a specified tag in the event content. The specified tag may be a pre-set tag. Specifically, for example, the specified tag may be "@add tag". Thus, when the transaction support platform discovers that the event content has "@add tag", it is considered that there are newly added tags in the transaction event notification. Specifically, for example, after the transaction support platform discovers that the event content has "@add tag", it registers the multiple strings starting with "@" after "@add tag" as multiple tags.

[0061] In some embodiments, when the transaction event targeted by the transaction event notification is a tag editing event, the tags in the tag library and / or the applicable rules corresponding to the tags are edited according to the event content; wherein, the editing includes but is not limited to: modifying or deleting the tags in the tag library.

[0062] In this embodiment, the transaction support platform may determine whether the transaction event targeted by the transaction event notification is a tag editing event based on the event content attached to the transaction event notification. Specifically, the event content may have an event type identifier. The transaction support platform may determine whether the transaction event is a tag editing event based on the event type identifier. Of course, the tag editing event may have a specified event type identifier. Further, it may be indicated which specific tag is targeted by setting a specified tag in the event content. Specifically, for example, when the event content has "@edit@high-risk patients@high-risk patients", it is considered that the tag "high-risk patients" needs to be edited and modified to "high-risk patients". For example, when the event content has "@delete@low-risk personnel", it may indicate that the tag "low-risk personnel" is to be deleted.

[0063] In some cases, the tag editing event can also indicate that the applicable rules for the tag should be edited. Specifically, different symbols or formats can be used in the event content to indicate the specific content that needs to be modified. For example, if the event content contains "@Edit@High-risk patient#Age>60", the transaction support platform can set the applicable condition of the tag "High-risk patient" to "Age>60", that is, the age is greater than 60 years old. Alternatively, if the event content contains "@Delete@High-risk patient#Gender=Male", it can indicate the deletion of the applicable condition "Gender=Male" of the tag "High-risk patient".

[0064] In some embodiments, the tag corresponds to an operation rule; the processing rule is composed of one or more tags; and the trigger condition includes: the processing rule includes at least some of the target tags. Accordingly, the step of executing a processing rule in a rule set with the target tag as a trigger condition on the event ticket to obtain output transaction information includes: when the processing rule includes at least some of the target tags of the event ticket, executing the operation rule for the tag included in the processing rule on the event ticket to obtain output transaction information.

[0065] In this embodiment, a label can serve as a programming primitive. Each label corresponds to a program written in machine instructions that performs a specific function. Thus, a label itself can represent a specific operation rule. In some cases, the operation rule corresponding to a label can also be composed of multiple labels, and the operation rules composed of multiple labels can be integrated into a single label operation rule.

[0066] The target tag may include multiple tags. The processing rule may include multiple tags. In some embodiments, the processing rule itself may be formed by multiple tags. The transaction support platform may check the processing rules, and if the processing rules include some or all of the tags in the target tag, the processing rules may be executed for the event. Specifically, for example, the target tag may include two tags, namely "drug allergy" and "asthma". The transaction support platform executes the processing rules including "drug allergy" and / or "asthma".

[0067] In some embodiments, the trigger condition includes: a target tag includes a specified tag. Accordingly, executing a processing rule in a rule set with the target tag as a trigger condition on the event ticket to obtain output transaction information includes: when the target tag includes the specified tag, executing the processing rule corresponding to the trigger condition on the event ticket to obtain output transaction information.

[0068] In this embodiment, the transaction support platform may record trigger conditions for corresponding processing rules. The trigger conditions may be designated tags. When the designated tags of the processing rules are included in the target tags of the event ticket, the processing rules are executed. In some embodiments, the processing rules themselves may be formed by tags, and the tags included in the processing rules may be different from the designated tags. In this way, designated tags can be used as trigger conditions for processing rules, but are not limited to tags included in the processing rules. Of course, in some embodiments, tags included in the processing rules may also include designated tags as trigger conditions.

[0069] In some embodiments, the information transmission method may further include the following steps: counting the number of identical tag combinations in target tags of different event tickets; and if the number exceeds a set threshold, combining the processing rules corresponding to the tags in the tag combination into one processing rule, wherein the triggering condition of the processing rule is set to include the tags in the tag combination in the target tags.

[0070] In some cases, in order to improve the processing efficiency of the transaction support platform. In this embodiment, the target tags included in multiple event tickets may be partially the same. If several tags are repeated in the target tags included in multiple event tickets, these tags can form a tag combination. When the statistical number of this tag combination exceeds the set threshold, the transaction support platform determines that the processing rules of the tags in the tag combination can form a new processing rule. The transaction support platform can use the processing rules formed by the overall combination of the processing rules corresponding to the tags in the tag combination as the newly added processing rules. Furthermore, the tags included in the tag combination can be used as the triggering conditions for the newly added processing rules. In this way, when the target tags of the event ticket include the tag combination, the newly added processing rule is executed.

[0071] In some embodiments, the transaction support platform is provided with a task center corresponding to the transaction platform, and different transaction platforms have different task centers. Accordingly, the step of sending the transaction information to the transaction platform may include: sending the transaction information to the task center of the transaction platform.

[0072] In this embodiment, the transaction support platform can set up task centers corresponding to different transaction platforms. In this way, the transaction support platform can send transaction information to the task center of the transaction platform corresponding to the event ticket. The task center can provide the transaction information to the transaction platform according to the communication mechanism between the transaction platform and the transaction platform. In some embodiments, the transaction support platform can provide the transaction information and the event content included in the event ticket to the task center together. This facilitates further response processing by the task center.

[0073] In some embodiments, the step of sending the transaction information to the task center of the transaction platform may include: generating a scheduling form based on the transaction information and the event form; wherein the scheduling form includes a platform identifier representing the transaction platform; and sending the scheduling form to the task center of the transaction platform represented by the platform identifier.

[0074] In this embodiment, the transaction support platform may be provided with a dispatch center. The dispatch center may generate a dispatch form based on transaction information and event forms. Specifically, the dispatch form may include both transaction information and the event content from the event form. The dispatch center then provides the dispatch form to the task center, which in turn provides feedback to the transaction platform. In this embodiment, the dispatch form may include the platform identifier of the transaction platform. Thus, the dispatch center can identify the task center corresponding to the dispatch form based on the platform identifier.

[0075] In this embodiment, by setting up a unified dispatch center on the transaction support platform, the overall data processing efficiency can be improved. Furthermore, the transaction platform sets up a corresponding task center to achieve data isolation between different transaction platforms.

[0076] In some embodiments, when a transaction event notification is received from a transaction platform, before the step of constructing an event ticket, the information sending method may further include the following steps: receiving an addition request from the transaction platform; wherein the addition request corresponds to a tag library and a rule set of the transaction platform; and storing the tag library and the rule set.

[0077] In this embodiment, the transaction support platform can correspond to multiple transaction platforms. Furthermore, the transaction support platform can support the dynamic addition of corresponding transaction platforms. Specifically, the management end can issue an addition request to the transaction support platform to instruct the transaction support platform to add the corresponding transaction platform.

[0078] An add request can correspond to a newly added transaction platform's tag library and rule set. Specifically, the add request can specify the path to the tag library and rule set. This allows the transaction support platform to obtain the tag library and rule set for the newly added transaction platform, thereby completing the configuration of the newly added transaction platform. In some cases, the transaction platform add request itself can also directly include data such as the tag library and rule set. The transaction support platform can receive the tag library and rule set when receiving the add request.

[0079] In this embodiment, after the transaction support platform obtains the tag library and rule set of the newly added transaction platform, it will store the tag library and rule set in the corresponding transaction platform. In this way, when receiving a transaction event notification from the transaction platform, the corresponding tag library and rule set can be read.

[0080] It should be understood that, although the various steps in the above flow chart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the above flow chart may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0081] See also Figure 3 The embodiment of this specification provides an information sending device. The information sending device includes an event form construction module, an event form matching module, an event form processing module and a transaction information sending module.

[0082] The event ticket building module is used to build an event ticket when receiving a transaction event notification issued by the transaction platform; wherein the event ticket includes the event content of the transaction event attached to the transaction event notification.

[0083] The event ticket matching module is used to match the event ticket in the tag library to obtain a tag corresponding to the event ticket, and the tag is used as a target tag; wherein the tag library includes at least one tag.

[0084] The event ticket processing module is used to execute the processing rule in the rule set with the target tag as the trigger condition for the event ticket to obtain output transaction information; wherein, the rule set includes processing rules and trigger conditions of the processing rules.

[0085] The transaction information sending module is used to send the transaction information to the transaction platform.

[0086] For the specific definition of the information sending device, please refer to the definition of the information sending method above and will not be repeated here. Each module in the above-mentioned information sending device can be implemented in whole or in part through software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each of the above modules.

[0087] In some embodiments, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the method steps in the above embodiments when executing the computer program.

[0088] In some embodiments, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method steps in the above embodiments are implemented.

[0089] In some embodiments, a computer program product is further provided, wherein the computer program product includes instructions, and the instructions can be executed by a processor of a computer device to implement the method steps in the above embodiments.

[0090] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the various embodiments provided in this specification may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0091] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0092] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent replacements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A method for sending information, characterized in that: Applied to a transaction support platform, the transaction support platform corresponds to multiple transaction platforms, the multiple transaction platforms including a platform for the medical industry, a platform providing food delivery services, or a platform providing travel services, the method comprising: Upon receiving a transaction event notification from the transaction platform, an event ticket is constructed; wherein the event ticket includes the event content of the transaction event attached to the transaction event notification; the event ticket is used to record, process, and track the completion results of the work task corresponding to the transaction event; the event ticket includes contextual information involved before and after the transaction event occurs; Matching the event sheet in a tag library to obtain a tag corresponding to the event sheet, and using the tag as a target tag; wherein the tag library includes at least one tag; Executing a processing rule in a rule set with the target tag as a trigger condition for the event single to obtain output transaction information; wherein the rule set includes processing rules and trigger conditions for the processing rules; Sending the transaction information to the transaction platform; Wherein, in the case of receiving a transaction event notification issued by the transaction platform, before the step of constructing an event ticket, the method further includes: Receive an addition request from a transaction platform; wherein the addition request corresponds to a tag library and a rule set of the transaction platform; store the tag library and the rule set; The transaction support platform is provided with a task center corresponding to the transaction platform, and different transaction platforms have different task centers. Accordingly, the step of sending the transaction information to the transaction platform includes: A dispatch sheet is generated based on the transaction information and the event sheet; wherein the dispatch sheet includes a platform identifier representing the transaction platform; the dispatch sheet is sent to a task center of the transaction platform represented by the platform identifier; wherein the task center is used to achieve data isolation between different transaction platforms.

2. The method according to claim 1, characterized in that The tags in the tag library correspond to applicable rules; accordingly, the event sheet is matched in the tag library to obtain a tag corresponding to the event sheet, and the tag is used as a target tag, including: Match the event content of the event sheet with the applicable rules of the tag to obtain a target tag; wherein the event content of the event sheet complies with the applicable rules of the target tag.

3. The method according to claim 1, characterized in that The transaction support platform corresponds to multiple transaction platforms, and the transaction support platform is respectively provided with a label library corresponding to different transaction platforms, and the label libraries of different transaction platforms are different; accordingly, the step of matching the event form in the label library to obtain a label corresponding to the event form, and using the label as the target label includes: The event sheet is matched with a tag library corresponding to the transaction platform to obtain a tag corresponding to the event sheet, and the tag is used as a target tag.

4. The method according to claim 1, wherein The tag library is divided into multiple tag categories according to transaction types; accordingly, when the event form is matched in the tag library, a tag corresponding to the event form is obtained, and the tag is used as a target tag, including: Determining a target tag category involved in the event single from among multiple tag categories in the tag library; The event list is matched with tags included in the target tag category to obtain a target tag corresponding to the event list.

5. The method according to claim 1, wherein The tag library binds multiple tags to the transaction event; accordingly, when the event single is matched in the tag library, a tag corresponding to the event single is obtained, and the tag is used as a target tag, including: The event list is matched with multiple tags bound to the transaction event to obtain a target tag corresponding to the event list.

6. The method according to claim 1, characterized in that The event content includes a tag; the method further includes: In a case where the transaction event targeted by the transaction event notification is a tag adding event, adding the tag included in the event content to the tag library; or, In a case where the event content includes a designated tag, the tag included in the event content is added to the tag library.

7. The method according to claim 1, characterized in that The method further comprises: In the case where the transaction event targeted by the transaction event notification is a tag editing event, the tags in the tag library and / or the applicable rules corresponding to the tags are edited according to the event content; wherein the editing includes but is not limited to: modifying or deleting the tags in the tag library.

8. The method according to claim 1, characterized in that The tag corresponds to an operation rule; the processing rule is composed of one or more tags; the trigger condition includes: the processing rule includes at least part of the target tag; accordingly, the step of executing the processing rule in the rule set with the target tag as the trigger condition for the event ticket to obtain output transaction information includes: In the case where the processing rule includes at least part of the target tags of the event ticket, the operation rule of the tags included in the processing rule is executed on the event ticket to obtain output transaction information.

9. The method according to claim 1, characterized in that The trigger condition includes: the target tag includes a specified tag; accordingly, executing a processing rule in the rule set with the target tag as the trigger condition for the event ticket to obtain output transaction information, including: In the case where the target tag includes the designated tag, a processing rule corresponding to the trigger condition is executed for the event ticket to obtain output transaction information.

10. The method according to claim 1, characterized in that The method further comprises: Count the number of identical tag combinations in target tags of different event orders; When the number exceeds a set threshold, the processing rules corresponding to the tags in the tag combination are combined into one processing rule, and the triggering condition of the processing rule is set to that the target tag includes the tags in the tag combination.

11. An information sending device, characterized in that: Applied to a transaction support platform, the transaction support platform corresponds to multiple transaction platforms, the multiple transaction platforms including a platform for the medical industry, a platform providing food delivery services, or a platform providing travel services, the device includes: An event ticket construction module is configured to construct an event ticket upon receiving a transaction event notification from the transaction platform; wherein the event ticket includes the event content of the transaction event accompanying the transaction event notification; the event ticket is used to record, process, and track the completion results of the work task corresponding to the transaction event; and the event ticket includes contextual information before and after the transaction event occurs; An event ticket matching module is used to match the event ticket in a tag library to obtain a tag corresponding to the event ticket, and the tag is used as a target tag; wherein the tag library includes at least one tag; An event ticket processing module, configured to execute a processing rule in a rule set with the target tag as a trigger condition for the event ticket, to obtain output transaction information; wherein the rule set includes processing rules and trigger conditions for the processing rules; A transaction information sending module, configured to send the transaction information to the transaction platform; Wherein, when receiving the transaction event notification issued by the transaction platform, before the step of constructing the event ticket, the device is further used to: Receive an addition request from a transaction platform; wherein the addition request corresponds to a tag library and a rule set of the transaction platform; store the tag library and the rule set; The transaction support platform is provided with a task center corresponding to the transaction platform, and different transaction platforms have different task centers. Accordingly, the step of the transaction information sending module sending the transaction information to the transaction platform includes: A dispatch sheet is generated based on the transaction information and the event sheet; wherein the dispatch sheet includes a platform identifier representing the transaction platform; the dispatch sheet is sent to a task center of the transaction platform represented by the platform identifier; wherein the task center is used to achieve data isolation between different transaction platforms.

12. A computer device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the information sending method according to any one of claims 1 to 10.

Images