Method, device and recording medium for managing progress information of item sales process

Abstract

This invention relates to a method, apparatus, and recording medium implemented in an electronic device. One embodiment of the method is an electronic device that manages progress information of an item sales process. It may include the following steps: receiving an event order related to the sale of an item, the event order including information on one or more events related to the sale of the item; obtaining rule identification information of a rule corresponding to the event order based on rule data; confirming the existence of a policy corresponding to the rule identification information based on first behavior data corresponding to the rule data, the first behavior data including information on whether a policy corresponds to each of the one or more rule identification information included in the rule data exists; and when a policy corresponding to the rule identification information exists, the method includes the following steps: confirming behavior type information of the behavior type corresponding to the event order; obtaining policy identification information of the policy corresponding to the event order based on policy data; confirming behavior information corresponding to the policy identification information and the behavior type information based on second behavior data corresponding to the policy data; and updating the event order based on the behavior information.

Description

Technical Field

[0001] This invention relates to a technique for managing progress information in the sales process of goods. More specifically, it relates to a technique that manages information on whether to interrupt the sales process of a specific item based on events that occur during operations related to the sale of the item. Prior Technology

[0002] With the development of communication and logistics technologies, various forms of business transactions are realized through e-commerce services. E-commerce service providers are seeking strategies to effectively sell various goods to their users. For example, e-commerce service providers can introduce the Andon system as one solution to improve the quality of the sales process. The Andon system refers to immediately halting the sale of an item in e-commerce services when an event occurs, until the cause is identified and resolved. However, Andon operators should comprehensively consider various policies related to the Andon system, such as the characteristics of the item, the cause of the Andon event (the reason for the process interruption), and the exception handling for special items, when handling business. That is, operators should correctly apply the rules or policies related to the Andon system and consider the organic relationships between them. However, as the types of items handled in e-commerce services become more diverse, or the classification methods or response methods for various events become more diverse, the types or complexity of rules or policies that operators need to be familiar with may increase significantly. Summary of the Invention

[0003] [The problem the invention aims to solve] One embodiment of the present invention aims to solve the technical problem of a technique for more effectively managing the data used to construct web pages that provide an authentication process.

[0004] One embodiment of the present invention aims to solve the technical problem of providing customized guidance to users at various stages in various situations based on the data required for Andon processing.

[0005] One embodiment of the present invention aims to solve the technical problem of integrating and managing various data required to improve the efficiency of the sales process of goods operated by the Andon processing system, and using such data to provide users with optimized operating guidelines for various situations.

[0006] The technical problem to be solved by one embodiment of the present invention is to provide users with optimization guidance for each stage of each situation, thereby maximizing the efficiency of the Andon system, automatically handling the required operations at each stage, and thus simultaneously achieving business automation and convenience.

[0007] The technical issues of this invention are not limited to those mentioned above. Those with common knowledge in the technical field of this invention can clearly understand other technical issues not mentioned based on the following description. [Technical means to solve the problem]

[0008] An embodiment of the present invention provides a method for managing the progress information of an item sales process using an electronic device, which may include the following steps: receiving an event ticket related to the sale of an item, wherein the event ticket includes information on one or more events related to the sale of the item; obtaining rule identification information of a rule corresponding to the event ticket based on rule data; confirming the existence of a policy corresponding to the rule identification information based on first behavior data corresponding to the rule data, wherein the first behavior data includes information on whether a policy corresponds to each of the rule identification information included in the rule data exists; and when a policy corresponding to the rule identification information exists, the method includes the following steps: confirming behavior type information of the behavior type corresponding to the event ticket; obtaining policy identification information of the policy corresponding to the event ticket based on policy data; confirming behavior information corresponding to the policy identification information and the behavior type information based on second behavior data corresponding to the policy data; and updating the event ticket based on the behavior information.

[0009] In the embodiment, the first behavior data may further include behavior type information corresponding to each of the above-mentioned rule identification information, and the step of confirming the behavior type information includes the following steps: confirming the behavior type information corresponding to the above-mentioned event sheet based on the first behavior data.

[0010] In the embodiments, the first behavioral data may further include behavioral information corresponding to each of the more than one rule identification information. When there is no policy corresponding to the rule identification information, the method includes the following steps: confirming the behavioral information corresponding to the rule identification information based on the first behavioral data; and updating the event form based on the confirmed behavioral information.

[0011] In this embodiment, the rule data may include information on one or more rule conditions corresponding to each of the one or more rule identification information. The step of obtaining rule identification information of the rule corresponding to the event sheet based on the rule data includes the following steps: confirming the one or more rule conditions included in the rule data; confirming whether the one or more rule conditions are satisfied based on the one or more event information included in the event sheet; and confirming the rule identification information, which corresponds to at least one rule condition among the one or more rule conditions that is confirmed to be satisfied.

[0012] In the embodiments, each of the above-mentioned one or more rule conditions may include: the combination type of the rule condition, the key information of the rule condition, the value information of the rule condition, and the detailed condition information.

[0013] In an embodiment, the step of confirming whether the above-mentioned rule conditions are met based on the above-mentioned event information included in the event sheet may include the following steps: extracting one or more keywords included in the above-mentioned event information; and confirming whether the extracted one or more keywords meet the above-mentioned rule conditions.

[0014] In an embodiment, the step of confirming whether the above-mentioned rule conditions are met based on the above-mentioned event information included in the event sheet may include the following steps: confirming whether the above-mentioned event information includes one or more fields and the field values ​​corresponding to the above-mentioned fields meet the above-mentioned rule conditions.

[0015] In this embodiment, the policy data may include policy identification information of one or more policies and information on one or more policy conditions corresponding to each of the policy identification information. The step of obtaining policy identification information of the policy corresponding to the event sheet based on the policy data includes the following steps: confirming the one or more policy conditions included in the policy data; confirming whether the one or more policy conditions are met based on the event information included in the event sheet; and confirming the policy identification information, which corresponds to at least one policy condition among the one or more policy conditions that is confirmed to be met.

[0016] In the embodiments, each of the above-mentioned policy conditions may include: the combination type of the policy conditions, the key information of the above-mentioned policy conditions, the value information of the above-mentioned policy conditions, and the detailed condition information.

[0017] In an embodiment, the step of confirming whether one or more policy conditions are met based on the event information included in the event sheet may include the following steps: extracting one or more keywords included in the event information; and confirming whether the extracted one or more keywords meet the one or more policy conditions.

[0018] In the embodiment, the step of confirming whether the above-mentioned policy conditions are met by including one or more event information in the event sheet may include the following steps: confirming whether one or more fields included in the event information and the field values ​​corresponding to the above-mentioned one or more fields meet the above-mentioned policy conditions.

[0019] In an embodiment, the method for managing the progress information of the sales process of the above-mentioned items may include the following steps: receiving input of policy identification information to be added to the above-mentioned policy data and one or more policy conditions corresponding to the above-mentioned policy identification information; corresponding to the above-mentioned input, adding behavioral information corresponding to the policy identification information of the added policy to the above-mentioned second behavioral data.

[0020] In an embodiment, the aforementioned behavioral information may include information that displays guidance information in the aforementioned event form, such as the processing of the aforementioned product sales process corresponding to the aforementioned event, or the status of the aforementioned product sales process that has been changed corresponding to the aforementioned event.

[0021] An electronic device according to one embodiment of the present invention may include: one or more processors; one or more memory, which store commands to be executed by the one or more processors; and the electronic device is configured such that when the commands are executed by the one or more processors, the one or more processors execute the methods of various embodiments of the present invention.

[0022] One embodiment of the present invention is a non-transitory computer-readable recording medium that records commands, when executed by one or more processors, to cause the one or more processors to perform actions. The commands can be configured to cause the one or more processors to execute methods of various embodiments of the present invention. [Effects of the Invention]

[0023] According to the present invention, customized guidance can be provided to users at various stages in various situations based on the data required for Andon processing, thereby improving the user experience and supporting the effective execution of operations.

[0024] According to the present invention, various data required to improve the efficiency of the sales process operated by the Andon processing system can be integrated and managed, and such data can be used to provide users with optimized operating guidelines for various situations, thereby improving the overall efficiency of the sales process.

[0025] According to the present invention, users can be provided with optimization guidance for each stage of each situation, thereby maximizing the efficiency of the Andon system, automatically handling the required operations at each stage, and thus simultaneously achieving business automation and convenience.

[0026] The effects of the technical concept of this invention are not limited to those mentioned above. Those with common knowledge in the technical field of this invention can clearly understand other effects not mentioned based on the description in the specification. Simple Explanation of the Diagram

[0027] Figure 1 illustrates the environment in which an electronic device, according to one embodiment of the present invention, can be applied. Figure 2 is a block diagram of an electronic device according to one embodiment of the present invention. Figure 3 is a flowchart illustrating a method according to one embodiment of the present invention. Figures 4a and 4b are event diagrams used to illustrate one embodiment of the present invention. Figure 5 is a diagram illustrating the rule data of one embodiment of the present invention. Figure 6 is a diagram illustrating the first row of data in one embodiment of the present invention. Figure 7 is a diagram illustrating policy information for one embodiment of the present invention. Figure 8 is a diagram illustrating the second row of data in one embodiment of the present invention. Figure 9 is a diagram illustrating behavioral type information of one embodiment of the present invention. Figure 10 is a diagram illustrating a method for managing process progress information according to one embodiment of the present invention. Implementation

[0028] The various embodiments described in this invention are illustrative of the technical concept of the invention and are not intended to limit them to specific implementation methods. The technical concept of this invention includes various modifications, equivalents, alternatives, and embodiments obtained by selectively combining all or part of the embodiments described herein. Furthermore, the scope of the patent application for the technical concept of this invention is not limited to the various embodiments presented below or their specific descriptions.

[0029] The terms used in this invention, including technical or scientific terms, shall have the meanings commonly understood by one of common knowledge in the technical field to which this invention pertains, unless otherwise defined.

[0030] The expressions used in this invention, such as "comprising," "may include," "possibly possess," "may possess," "have," and "may have," imply the presence of object features (e.g., functions, actions, or constituent elements), and do not exclude the existence of other additional features. That is, the expressions described above should be understood as open-ended terms that may include other embodiments.

[0031] The singular expressions used in this invention may include the meaning of the plural form unless otherwise stated in the context, and this also applies to the singular expressions described in the claims of this invention.

[0032] Unless otherwise specified in the context, the terms "first," "second," "first," "second," etc., used in this document are used to distinguish one object from others when referring to multiple objects of the same kind, and are not used to specify the order or importance of such objects.

[0033] The expressions “A, B and C”, “A, B or C”, “A, B and / or C”, “at least one of A, B and C”, “at least one of A, B or C”, “at least one of A, B and / or C”, etc., used in this document may refer to each of the listed items or all possible combinations of the listed items. For example, “at least one of A or B” may refer to (1) at least one A, (2) at least one B, (3) at least one A and at least one B.

[0034] The term "based on" used in this invention is used to describe one or more factors that affect the determination or judgment of an action or behavior described in a statement or article including the term. The term does not exclude other factors that affect the determination or judgment of an action or behavior.

[0035] In this invention, the expression "connected" or "linked" to one constituent element (e.g., the first constituent element) can mean that the first constituent element is directly connected to or linked to the second constituent element, or is connected to or linked to the second constituent element through a new constituent element (e.g., the third constituent element).

[0036] Depending on the context, the expression "configured to" used in this invention can mean "configured in a certain way," "possessing the capability of a certain method," "modified in a certain way," "made in a certain way," or "capable of performing a certain method." This expression is not limited to the meaning of "specially designed in hardware." For example, a processor configured to perform a specific action can refer to a general-purpose processor that can perform that specific action by executing software, or a special-purpose computer that is programmed to perform that specific action.

[0037] In this invention, the term "user interface" refers to a physical or virtual medium that enables communication between a user and things, systems, machines, or computer programs. Users can utilize e-commerce services through a user interface. For example, a user interface may include basic elements such as images or text for displaying specific information, and elements such as icons and buttons that can be constructed using these basic elements for receiving user input. For example, a user selecting (clicking) the user interface can be described as receiving user input corresponding to the user interface. Furthermore, elements that can display specific information to the user in the form of a combination of basic elements such as images and text and elements for receiving user input, and that can perform all functions related to receiving user input, such as interface widgets, provide a user interface.

[0038] Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings. In the drawings and descriptions thereof, the same or substantially equivalent constituent elements are given the same reference numerals. Furthermore, in the following descriptions of various embodiments, repeated descriptions of the same or corresponding constituent elements may be omitted, but this does not mean that the constituent element is not included in the embodiment.

[0039] Figure 1 illustrates an environment in which an electronic device according to one embodiment of the present invention can be applied. The electronic device 110 and the user terminal 120 can communicate with each other via a network connection.

[0040] Electronic device 110 may be a server device that manages information on a plurality of services, including e-commerce services, according to one embodiment of the present invention. That is, electronic device 110 may be a server device operating under the management of an entity managing online transactions of goods or services (e.g., an e-commerce service provider). In embodiments, electronic device 110 may be a server device that manages information on a plurality of various services other than e-commerce services. Electronic device 110 may be a server device that manages progress information of the sales process of goods in e-commerce. For example, electronic device 110 may be a server managing an Andon system. For example, electronic device 110 may include server functions such as receiving event tickets for events occurring in relation to the sale of goods, or storing, modifying, issuing, and / or updating event tickets. An event ticket may refer to data that includes and indicates one or more event information related to a specific event. In one embodiment, the event information included in each event ticket may include: information about the item where the event occurred, and information about the status or attributes of the event. Such event information can also be managed as one or more tags, fields, or comments. For example, the status or attributes of an event can be defined by the tag information included in the event form, the text and images filled in the fields included in the event form, or the text and images filled in as comments. Item attribute information may include various attributes such as: item name, category, classification, type, quantity, size, weight, whether it is food, whether it is agricultural product, etc. Item attribute information can be managed as tags, fields, comments, etc. Event status information may include: customer attribute information related to the event, the reason for the event, whether there is evidence, the content of the customer's claim, the content of the measures related to the event, the implementation status of the measures, etc. Event status or attribute information can be managed as one or more tags, fields, or comments. In one embodiment, customer attribute information may include the customer's age, gender, membership level, etc.

[0041] Electronic device 110 can manage progress information of the sales process. In one embodiment, electronic device 110 can manage event tickets in relation to the progress information of the sales process. Electronic device 110 can receive event tickets from user terminal 120 and read the event information included in the event tickets. Electronic device 110 can obtain rules or policies corresponding to the event information based on the event information. Furthermore, electronic device 110 can update event tickets. Updating can refer to inputting new event information into an event ticket, or generating a new event ticket corresponding to an event ticket that becomes the object of the update. For example, the ticket that becomes the object of the update can be called the parent ticket, and the ticket generated as the result of the update can be called the child ticket. In one embodiment, electronic device 110 can display guidance information such as the subsequent operations that the user needs to perform on the event ticket by updating the event ticket. In this case, the guidance information can also be referred to as "updated event information". In one embodiment, electronic device 110 can provide guidance information to the user by updating the event ticket. Guidance information can refer to information that instructs a user to perform a specific task. For example, information instructing a user to confirm specific information, or to perform tasks such as returns, refunds, customer service, sending emails, inspections, triage settings, setting up an Andon, executing an Andon, or introducing an Andon can be considered guidance information. In this case, setting up an Andon, executing an Andon, and introducing an Andon refer to Andon tasks that interrupt the sales process of a specified item in response to an event. On the other hand, guidance information may include information on whether to perform a task and information on the task content. The task content information may refer to information on how to perform the task. For example, for an email sending task, the task content information may include how to send the email, that is, what content to enter in the email. In one embodiment, guidance information for performing a specified task may include information such as instructing the user to enter specified information into an event ticket or a sub-ticket of an event ticket after performing the specified task, or instructing the user to generate a new event ticket associated with the event ticket to enter specified information. The specified information to be entered may include information on the task result or information on subsequent tasks.

[0042] In one embodiment, the electronic device 110 may also perform corresponding tasks on behalf of the user, rather than providing guidance for tasks required for an event. For example, when an email sending task is required for a specific event, the electronic device 110 may send an email, including information about the email sending and its result in the event form as guidance information, thereby updating the event form. As described above, the electronic device 110 may receive event forms and analyze event information, thereby providing guidance information for tasks that the user needs to perform for the event, or performing the tasks on behalf of the user. These actions performed by the electronic device 110 in response to events, providing information or performing tasks, and the actions of including new information in the event form accordingly, can all be referred to as "updating the event form actions".

[0043] In one embodiment, electronic device 110 can update event tickets based on at least a portion of rules and policies. Rules and policies may refer to rules or policies related to the Andon system. Electronic device 110 can identify the rules or policies corresponding to the event ticket and perform an "action" to update the event ticket based on the identified rules or policies.

[0044] In one embodiment, the electronic device 110 can manage rule information as rule data. Rule data may include information about one or more rules related to the product sales process. In one embodiment, rule data may include one or more rule identification information used to identify each of the one or more rules. In one embodiment, rule data may include one or more conditions corresponding to each of the one or more rule identification information, i.e., information about "rule conditions". Rule conditions may refer to conditions used to determine which rule identification information corresponds to an event based on event information included in an event form. In one embodiment, one or more rule conditions may correspond to one rule identification information. For one or more event information included in an event form, the electronic device 110 can apply one or more rule conditions determined based on rule data to obtain rule identification information corresponding to one or more rule conditions satisfied by the event form.

[0045] In one embodiment, the electronic device 110 can manage policy information as policy data. Policy data may include information on one or more policies related to the product sales process. In one embodiment, policy data may include one or more policy identification information to identify each of the one or more policies. In one embodiment, policy data may include one or more conditions corresponding to each of the one or more policy identification information, i.e., "policy conditions" information. Policy conditions may refer to conditions used to determine which policy identification information corresponds to an event based on event information included in an event list. In one embodiment, one or more policy conditions may correspond to one policy identification information. For one or more event information included in an event list, the electronic device 110 can apply one or more policy conditions confirmed based on policy data to obtain policy identification information corresponding to one or more policy conditions satisfied by the event list.

[0046] In one embodiment, rule data and policy data can be mutually independent and may differ from each other. That is, a combination of one or more rule conditions corresponding to each rule may differ from a combination of one or more policy conditions corresponding to each policy, and one or more rule conditions corresponding to specific rule identification information may differ from one or more policy conditions corresponding to specific policy identification information. In one embodiment, each rule condition and each policy condition can also be identified based on event information with different attributes. Furthermore, rule data and policy data can each be an isolated set of data. Therefore, the dependency between rule data and policy data can be minimized, thereby minimizing the impact on the other when updating or maintaining one of the rule data or policy data, and improving scalability through independent management. Moreover, independent management and improved computational speed can be achieved by minimizing the reference relationships between them.

[0047] Thus, electronic device 110 can manage various information used to manage the progress information of the product sales process. The management of information by electronic device 110 can be collectively referred to as all actions of having control over and processing the information. For example, information management may include obtaining, storing, updating, or modifying the information.

[0048] The aforementioned electronic device 110 can be implemented by one or more computing devices. For example, all functions of the electronic device 110 can be implemented in a single computing device. As another example, a first function of the electronic device 110 can be implemented in a first computing device, and a second function can be implemented in a second computing device. As yet another example, a plurality of computing devices can be used to implement all or specific functions of the electronic device 110. The aforementioned computing device can be a desktop computer, a laptop computer, an application server, a proxy server, or a cloud server, etc., but is not limited to these; all types of devices with computing capabilities can be computing devices.

[0049] User terminal 120 can be a device used by a user, i.e., a manager overseeing the e-commerce sales process, to transmit event tickets to and receive updated event tickets from electronic device 110. User terminal 120 can be a terminal capable of sending and receiving various types of information with electronic device 110 via a network. For example, user terminal 120 can be a computer, laptop, portable communication terminal (smartphone, etc.), portable multimedia device, wearable device, or HMD. However, the type of user terminal 120 is not limited to these; user terminal 120 can be any device including input / output interfaces that allow users to input or output information, and capable of communicating with electronic device 110 or other devices via a network.

[0050] User terminal 120 can provide users with information received from electronic device 110, and can receive input from users and transmit it to electronic device 110. Specifically, user terminal 120 can obtain input from users instructing them to access various pages, and generate commands to instruct them to access various pages in response to the obtained input. User terminal 120 can transmit access requests instructing them to access various pages to electronic device 110. Input obtained from users may include various forms of input such as mouse clicks, touch controls using a touchpad or touchscreen, voice recognition, and other electronic inputs. User terminal 120 can receive various pages from electronic device 110 and output the received pages.

[0051] In one embodiment, the user terminal 120 may be implemented as a terminal capable of sending and receiving various information with the electronic device 110 via a network. For example, the user terminal 120 may be one of a computer, a laptop, a portable communication terminal (such as a smartphone), a portable multimedia device, a wearable device, or an HMD. However, the type of user terminal 120 is not limited to these; the user terminal 120 may be any device including an input / output interface that allows the user to input or output information, and capable of communicating with the electronic device 110 or other devices via a network.

[0052] The network serves to connect electronic device 110 to user terminal 120 or other external devices. For example, the network provides a connection path so that user terminal 120 can connect to electronic device 110 and send and receive packet data with electronic device 110. The network can be implemented as any type of wired or wireless network, such as a Local Area Network (LAN), Wide Area Network (WAN), Mobile Radio Communication Network, or Wibro (Wireless Broadband Internet).

[0053] In one embodiment, the electronic device 110 and the user terminal 120 can operate through a single device. The user terminal 120 can be included as all or part of the constituent elements of the electronic device 110. In this case, for example, the various information transmitted and received between the electronic device 110 and the user terminal 120 via a network can be various information transmitted and received between the constituent elements within a single device.

[0054] Figure 2 is a block diagram of an electronic device according to one embodiment of the present invention. The electronic device 200 can process information for a plurality of services and authentications. In one embodiment, the electronic device 200 may include one or more processors 210, one or more memory units 220, and a communication interface 230 as constituent elements. In one embodiment, at least one of the constituent elements of the electronic device 200 may be omitted, or other constituent elements may be added to the electronic device 200. In one embodiment, some constituent elements may be added or alternatively integrated, or implemented as a single or multiple entities. In this invention, one or more processors 210 may be referred to as processor 210. Unless explicitly stated otherwise in the context, the term processor 210 may refer to a collection of one or more processors. In this invention, one or more memory units 220 may be referred to as memory units 220. Unless explicitly stated otherwise in the context, the term "memory 220" may refer to a collection of one or more memories. In one embodiment, at least some of the internal / external components of the electronic device 200 may be interconnected and transmit / receive information (data, signals, etc.) via buses, GPIO (General Purpose Input / Output), SPI (Serial Peripheral Interface), or MIPI (Mobile Industry Processor Interface).

[0055] The processor 210 can drive software (e.g., commands, programs, etc.) to control at least one component of the electronic device 200 connected to the processor 210. Furthermore, the processor 210 can perform various operations related to the present invention, such as calculations, processing, data generation, and manipulation. Also, the processor 210 can load data from memory 220 or store such data in memory 220. In one embodiment, the processor 210 can request various information from the user terminal 120 via the control communication interface 230 and receive various information from the user terminal 120.

[0056] Memory 220 can store various information (data). The information stored in memory 220 is information obtained, processed, or used by at least one component of electronic device 200, and may include software (e.g., commands, programs, etc.). Memory 220 may include volatile and / or non-volatile memory. In this invention, commands or programs are software stored in memory 220, and may include operating systems, applications, and / or middleware for controlling the resources of electronic device 200. The middleware provides various functions to the application to enable the application to utilize the resources of electronic device 200. In one embodiment, memory 220 may store commands that, when executed by processor 210, cause processor 210 to perform operations. Memory 220 may store at least a portion of information received from a database via communication interface 230 and / or information sent to a database via communication interface 230. Specifically, memory 220 can store information related to e-commerce services and commands executed by processor 210. Furthermore, memory 220 can store, for example, connection information as described below.

[0057] The communication interface 230 enables wireless or wired communication between the electronic device 200 and a database or other external electronic devices. For example, the communication interface 230 can implement wireless communication in the following ways: eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low-Latency Communications), MMTC (Massive Machine Type Communications), LTE (Long-Term Evolution), LTE-A (LTE Advance), NR (New Radio), UMTS (Universal Mobile Telecommunications System), GSM (Global System for Mobile communications), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), WiBro (Wireless Broadband), WiFi (Wireless Fidelity), Bluetooth, NFC (Near Field Communication), GPS (Global Positioning System), or GNSS (Global Navigation Satellite System), etc. For example, the communication interface 230 can implement wired communication via USB (Universal Serial Bus), HDMI (High Definition Multimedia Interface), RS-232 (Recommended Standard-232), or POTS (Plain Old Telephone Service). In one embodiment, the electronic device 200 can also be integrated with other devices. In this case, the communication interface 230 can function as a connection circuit or interface connecting the electronic device 200 with corresponding other devices.

[0058] In the following, the actions described in Figures 3 to 10 can be understood as those performed by the processor 210 of the electronic device 200 as described in Figure 2.

[0059] Figure 3 is a flowchart illustrating a method according to one embodiment of the present invention.

[0060] The method shown in Figure 3 can be understood as a series of actions that manage the progress information of the product sales process through electronic device 110.

[0061] Electronic device 110 can receive event tickets (S310). In one embodiment, electronic device 110 can receive event tickets from user terminal 120.

[0062] Electronic device 110 can obtain rule identification information corresponding to an event ticket based on rule data (S320). In one embodiment, electronic device 110 can obtain rule identification information indicating which rule the event ticket corresponds to based on rule data and event information included in the event ticket. For each rule condition included in the rule data, electronic device 110 can confirm whether it is satisfied based on the event information. Electronic device 110 can confirm one or more rule conditions included in the rule data, and confirm the satisfied rule condition among the one or more rule conditions based on the event conditions. Electronic device 110 can confirm rule identification information that corresponds to at least one rule condition among the one or more rule conditions that is confirmed to be satisfied. For example, multiple rule conditions can correspond to a first rule with rule identification information number 1, and other multiple rule conditions can correspond to a second rule with rule identification information number 2. At this time, when multiple rule conditions corresponding to the first rule are satisfied based on the event information included in the event form, the electronic device 110 can confirm that the rule corresponding to the event form is the first rule.

[0063] In one embodiment, each rule condition may include: corresponding rule identification information, condition type, condition key, condition value, and detailed condition information. Here, a detailed condition may refer to the following: whether a specific condition key or condition value exists, or whether the event sheet includes such a specific condition key or condition value. The electronic device 110 can confirm whether each rule condition is satisfied based on the detailed condition information. Furthermore, the condition type may include type information regarding how one or more rule conditions corresponding to the same rule identification information are combined. For example, the condition type may include combination conditions such as AND, OR, NOR, and XOR. When one or more rule conditions corresponding to the first rule each include the first rule condition, the second rule condition, and the third rule condition, and each condition type is "AND", the event information included in the event sheet must satisfy all three rule conditions (first, second, and third) to be recognized as corresponding to the first rule.

[0064] In one embodiment, when confirming whether one or more rule conditions are met based on event information included in an event log, the electronic device 110 can extract event information from the event log. For example, the electronic device 110 can extract keywords included in the event information by analyzing the event information, and confirm whether one or more rule conditions are met based on the extracted keywords. At this time, the electronic device 110 can extract keywords of the event information based on rule data. For example, keywords included in the event information can be extracted based on one or more condition keys, condition values, etc. included in the rule data.

[0065] In one embodiment, for event information included in an event form, the electronic device 110 can determine whether a rule condition is met based on one or more fields included in the event information and the field values ​​corresponding to those fields. For example, each field included in the event form may correspond to a specific rule condition. In this case, the electronic device 110 can determine whether the rule condition corresponding to each field is met based on the field values ​​included in each field. In one embodiment, for event information included in an event form, the electronic device 110 can determine whether a rule condition is met based on one or more tag information included in the event information. For example, it can determine whether a specific rule condition is met based on one or more tag information included in the event form.

[0066] Electronic device 110 can obtain rule identification information and, based on the first behavior data, confirm whether a policy corresponding to the rule identification information exists (S330). The first behavior data can be data on behaviors corresponding to the rule data. That is, the first behavior data may include information on the behavior to be performed corresponding to each of the rule identification information included in the rule data. As mentioned above, the information on the behavior to be performed may include information such as instructions and commands associated with the update action of the event ticket. The first behavior data may include behavior information corresponding to each rule identification information. Electronic device 110 can confirm the behavior information corresponding to the rule identification information based on the first behavior data.

[0067] In one embodiment, the first line of data may include information such as whether a policy corresponding to each rule identification information exists. The electronic device 110 may refer to the first line of data to confirm whether a policy corresponding to each rule identification information exists.

[0068] When a policy corresponding to the rule identification information exists, the electronic device 110 can confirm the behavior type information corresponding to the event ticket (S340). The behavior type information may refer to the behavior type corresponding to the specific behavior information in the second behavior data described below. For example, the second behavior data may include detailed behavior information for various behaviors. Specifically, when providing guidance related to inspections, the type of behavior actually required may differ depending on whether it is a first-time or second-time inspection. In the case of a first-time inspection and a second-time inspection, although both are inspection-related behaviors, the guidance criteria used to describe them are different. As another example, regarding the behavior information of sending emails, specifically, there may be various types of behavior, such as sending emails that require a reply or sending emails that do not require a reply. As described above, the second behavior data can correspond to different behavior information for each policy identification information and each behavior type information. In this case, each rule identification information can correspond to specific behavior type information. The first behavioral data may include behavioral type information corresponding to each rule identification information. The electronic device 110 can confirm the behavioral type information corresponding to the rule identification information based on the first behavioral data.

[0069] When a policy corresponding to the rule identification information exists, the electronic device 110 can verify the policy data. The electronic device 110 can obtain policy identification information corresponding to the event ticket based on the policy data (S350). The electronic device 110 can confirm whether a corresponding policy exists for the rule identification information confirmed to correspond to the event ticket by referring to the data in the first step. At this time, in order to confirm what kind of policy corresponds to the event ticket, it can be confirmed by referring to the policy data.

[0070] In one embodiment, the electronic device 110 can obtain policy identification information indicating which policy the event form corresponds to based on event information and policy data included in the event form. For each policy condition included in the policy data, the electronic device 110 can confirm whether it has been met based on the event information. The electronic device 110 can confirm one or more policy conditions included in the policy data, and confirm which of the policy conditions has been met based on the event conditions. The electronic device 110 can confirm rule identification information, which corresponds to at least one policy condition confirmed to be met among the one or more policy conditions. For example, multiple policy conditions may correspond to a first policy with policy identification information number 1, and other multiple policy conditions may correspond to a second policy with policy identification information number 2. In this case, when multiple policy conditions corresponding to the first policy are met based on the event information included in the event form, the electronic device 110 can confirm that the policy corresponding to the event form is the first policy.

[0071] In one embodiment, each policy condition may include: corresponding policy identification information, condition type, condition key, condition value, and detailed condition information. Here, a detailed condition may refer to the following: whether a specific condition key or condition value exists, or whether the event ticket includes such a specific condition key or condition value. The electronic device 110 can confirm whether each policy condition is satisfied based on the detailed condition information. Furthermore, the condition type may include information on how one or more policy conditions corresponding to the same policy identification information are combined. For example, the condition type may include AND, OR, NOR, XOR, and other combination conditions. When one or more policy conditions corresponding to the first policy include the first policy condition, the second policy condition, and the third policy condition, and each condition type is "AND", the event information included in the event ticket must satisfy all three policy conditions (first, second, and third) to be identified as corresponding to the first policy.

[0072] In one embodiment, when confirming whether one or more policy conditions are met based on event information included in an event log, the electronic device 110 can extract event information from the event log. For example, the electronic device 110 can extract keywords included in the event information by analyzing the event information, and confirm whether one or more policy conditions are met based on the extracted keywords. At this time, the electronic device 110 can extract keywords from the event information based on policy data. For example, keywords included in the event information can be extracted based on one or more condition keys, condition values, etc. included in the policy data.

[0073] In one embodiment, for event information included in an event form, the electronic device 110 can determine whether policy conditions are met based on one or more fields included in the event information and the field values ​​corresponding to those fields. For example, each field included in the event form may correspond to a specific policy condition. In this case, the electronic device 110 can determine whether the policy condition corresponding to each field is met based on the field values ​​included in each field. In one embodiment, for event information included in an event form, the electronic device 110 can determine whether policy conditions are met based on one or more tag information included in the event information. For example, it can determine whether a specific policy condition is met based on one or more tag information included in the event form.

[0074] Electronic device 110 can refer to the second behavioral data to confirm the behavioral information corresponding to the obtained policy identification information. Electronic device 110 can confirm the behavioral information corresponding to the obtained policy identification information based on the second behavioral data (S360). In one embodiment, the second behavioral data may include behavioral information corresponding to each policy identification information and each behavioral type information. Electronic device 110 can use the behavioral type information corresponding to the rule identification information confirmed based on the first behavioral data and the policy identification information confirmed based on the policy data to confirm the behavioral information corresponding to the policy identification information and the behavioral type information. For example, electronic device 110 can refer to the second behavioral data to confirm behavioral information where the behavioral type information corresponds to the policy identification information corresponding to the event form and the behavioral type information corresponding to the rule identification information.

[0075] In one embodiment, when it is determined based on the first behavior data that no policy corresponding to the rule identification information exists, the electronic device 110 can confirm the behavior information based on the first behavior data (S370). The first behavior data may include behavior information corresponding to each rule identification information. The electronic device 110 can confirm the behavior information in the first behavior data corresponding to the event ticket based on the rule identification information obtained in the automatic operation S320.

[0076] After performing action S360 or action S370, the electronic device 110 can update the event ticket (S380) based on the confirmed behavior information.

[0077] Figures 4a and 4b are event diagrams used to illustrate one embodiment of the present invention.

[0078] Referring to Figure 4a, an example of an event ticket received by the electronic device 110 from the user terminal 120 will be described. The event ticket 400a can be configured with category information (Brand), form information, etc., which can be understood as being included in the event information. As shown in the example of Figure 4a, the event ticket 400a can assign the category information to "Andon" and the form information to "Andon|Basic". The event ticket 400a can include more than one tag. Tag information can be understood as an instantiation of various attribute information related to the event ticket 400a. For example, as shown in the example of Figure 4a, the tag "andon_non_food" can be included in the event information of the event ticket 400a. This tag means that the event corresponding to the event ticket is not about food, but an Andon event related to an item. In one embodiment, the fields of the event ticket 400a can include field values ​​input by the user, and the field values ​​can also be updated by the electronic device 110 based on behavioral information. Referring to Figure 4b, an example of updating an event ticket will be explained. The example in Figure 4b can be an example of an event ticket 400b updated based on behavioral information, which is confirmed based on event ticket 400a in Figure 4a. The electronic device 110 can update event ticket 400a with guidance information that introduces additional work to the user (e.g., confirming whether the cause of the Andon incident is correct), thereby transmitting the updated event ticket 400b to the user terminal.

[0079] Figure 5 is a diagram illustrating the rule data of one embodiment of the present invention.

[0080] Figure 6 is a diagram illustrating the first row of data in one embodiment of the present invention.

[0081] Figure 7 is a diagram illustrating policy information for one embodiment of the present invention.

[0082] Figure 8 is a diagram illustrating the second row of data in one embodiment of the present invention.

[0083] Referring to Figure 5, rule data 500 may include one or more rule condition information corresponding to one or more rule identification information (1, 2, 3, 4, ...). Each rule condition information may include: rule identification information, condition type, condition key, detailed condition, and condition value information. Referring to the example of rule identification information "1", as the corresponding rule condition information, whether or not the category information (brand) included in the event order is included can be used as a detailed condition, including rule conditions with "Andon" as its condition value. That is, the electronic device 110 can determine whether the rule condition information is satisfied based on the rule condition information and whether the category information included in the event information includes the value "Andon". Furthermore, since the one or more rule condition information corresponding to rule identification information "1" all set their condition type to "AND" condition, it can be determined based on the condition type that all rule condition information of the "AND" type corresponding to rule identification information "1" must be satisfied for the event order to belong to rule identification information "1".

[0084] Referring to Figure 6, the first action data 600 can correspond to the rule data 500. The first action data 600 may include rule identification information, rule name, action information, whether a policy exists, and action type information. The first action data 600 may include the name of the rule corresponding to each rule identification information, action information, whether a policy exists, and action type information. The electronic device 110 can confirm whether a policy corresponding to the rule identification information exists based on the rule identification information and the first action data 600, which is confirmed based on the rule data 500. In the case where a policy exists (Y), the electronic device 110 can query the policy data 700 without performing an action. However, in the case where no policy exists, the event form 400a can be updated based on the action information confirmed based on the first action data 600.

[0085] Referring to Figure 7, policy data 700 may include one or more policy condition information corresponding to one or more policy identification information (1, 2, 3, 4, ...). Each policy condition information may include: policy identification information, condition type, condition key, detailed condition, and condition value information. Referring to the example of policy identification information "1", as one or more corresponding policy condition information, it can be confirmed that the following policy conditions must be met for an event to belong to policy identification information "1": including the condition that the custom field of the event information includes the value "agricultural products" for "20256331936665" as an "AND" type policy condition; including the condition that the label information of the event information does not include "Andon_wholesale" as an "AND" type policy condition, etc.

[0086] Referring to Figure 8, the second behavior data 800 can correspond to the policy data 700. The electronic device 110 can identify the policy identification information (e.g., "1") corresponding to the event ticket and the behavior type information (e.g., "guide to replying to email") identified based on the first behavior data 600 in the second behavior data 800. Therefore, the electronic device 110 can refer to the second behavior data 800 to identify the behavior information corresponding to the event ticket and update the event ticket based on the behavior information. At this time, the electronic device 110 can refer to the policy data 700 to identify the policy identification information and refer to the first behavior data 600 to identify the behavior type information.

[0087] Figure 9 is a diagram illustrating behavioral type information of one embodiment of the present invention.

[0088] Referring to Figure 9, the behavior type information 900 may include the "problem type" of the guidance information that categorizes the problem type of the event ticket. Furthermore, in order to manage the "safety type," the importance or risk level of the event in the guidance information through triage, the behavior type information 900 may include "triage guide 1" and "triage guide 2" for updating triage information. The "safety type" is a classification of the event ticket based on safety-related types. In addition, it includes the following behavior types as behavior type information: classifying the event ticket as a normal process behavior type, and providing a template included in the email when replying to an email ("email reply template").

[0089] Figure 10 is a diagram illustrating a method for managing process progress information according to one embodiment of the present invention.

[0090] Referring to Figure 10, an event ticket 400 can be input, and rule identification information 20 corresponding to the event information 10 included in the event ticket 400 can be confirmed based on rule data 500. Event information 10 may include information that analyzes the event ticket 400 based on rule data 500. At this time, rule identification information 20 corresponding to the event ticket 400 can be obtained based on whether the event information 10 meets the rule conditions included in rule data 500.

[0091] Furthermore, after obtaining rule identification information 20, the existence of a policy corresponding to rule identification information 20 can be confirmed by referring to the first behavior data 600. In the case where no policy exists, the event form 400 (70) can be updated based on the behavior information corresponding to rule identification information 20 confirmed by referring to the first behavior data 600.

[0092] When there is a policy that corresponds to rule identification information 20, the behavior type information 30 corresponding to rule identification information 20 can be confirmed by referring to the first behavior data 600.

[0093] When a policy corresponding to rule identification information 20 exists, policy identification information 50 corresponding to event information 40 included in event form 400 can be identified. In this case, event information 40 may include information analyzed from policy data 500 regarding event form 400. Therefore, event form 400 described with reference to FIG10 may be the same, but event information 10 input to rule data 500 and event information 40 input to policy data 700 may be different from each other.

[0094] Then, the behavioral information corresponding to the policy identification information 50 and the behavioral type information 30 can be confirmed based on the second behavioral data 800. The event form 400 (60) can be updated based on the behavioral information confirmed based on the second behavioral data 800.

[0095] In the flowcharts of this invention, the steps of the method or algorithm are described sequentially. However, in addition to performing the steps sequentially, they can also be performed in any combination possible order. The description of the sequence diagrams or flowcharts of this invention does not preclude changes or modifications to the method or algorithm, and does not imply that any step is necessary or preferred. In one embodiment, at least some steps may be performed in parallel, repeatedly, or heuristically. In another embodiment, at least some steps may be omitted, or other steps may be added.

[0096] Various embodiments of the present invention can be implemented in software form on a machine-readable storage medium. The software can be software used to implement the various embodiments described in the present invention. Programmers in the art to which this invention pertains can deduce the software based on the various embodiments described in the present invention. For example, the software can be a program that includes machine-readable commands (e.g., instructions, codes, or code segments). The machine, as a device capable of operating according to commands invoked from the storage medium, can be, for example, a computer. In one embodiment, the machine can be a computing device of the various embodiments described in the present invention. In one embodiment, the processor of the machine executes the invoked command, thereby enabling the components of the machine to perform functions corresponding to the command. The storage medium can refer to all kinds of recording media capable of being read by a machine and storing data. Storage media can include, for example, ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage devices, etc. In one embodiment, the storage medium can be implemented in the form of a distributed computer system connected to a network. At this point, the software can be distributed and stored in computer systems and executed. In another embodiment, the storage medium can be a non-transitory storage medium. A non-transitory storage medium refers to a media that actually exists and is not related to the semi-permanent or temporary storage of data, excluding transient signals.

[0097] The technical concept of the present invention has been described above based on various embodiments. However, the technical concept of the present invention includes various substitutions, variations, and modifications that can be understood by those skilled in the art within which the present invention pertains. Furthermore, it should be understood that such substitutions, variations, and modifications may be included within the scope of the appended patent applications.

[0098] 10: Event Information 20: Rule Recognition Information 30: Behavioral Type Information 40: Event Information 50: Policy Identification Information 60: Actions 70: Actions 110: Electronic devices 120: User Terminal 200: Electronic devices 210: Processor 220: Memory 230: Communication Interface 400: Incident Form 400a: Incident Form 400b: Incident Form 500: Rules and Regulations 600: First line of data 700: Policy Documents 800: Line 2 data 900: Behavioral Type Information S310: Action S320: Action S330: Action S340: Action S350: Action S360: Actions S370: Action S380: Action

Claims

1. A method for managing progress information of a product sales process, implemented by an electronic device, comprising the following steps: receiving an event order related to the sale of a product, the event order including event information of one or more events related to the sale of the product; obtaining rule identification information of a rule corresponding to the event order based on rule data; confirming, based on first behavior data corresponding to the rule data, whether a policy corresponding to the rule identification information exists, the first behavior data including information such as whether a policy corresponding to each of the one or more rule identification information included in the rule data exists; and when a policy corresponding to the rule identification information exists, the method comprises the following steps: confirming behavior type information of the behavior type corresponding to the event order; obtaining policy identification information of the policy corresponding to the event order based on policy data; confirming behavior information corresponding to the policy identification information and the behavior type information based on second behavior data corresponding to the policy data; and updating the event order based on the behavior information.

2. The method of Request 1, wherein the first behavior data further includes behavior type information corresponding to each of the above-mentioned rule identification information, and the step of confirming the behavior type information includes the following steps: confirming the behavior type information corresponding to the above-mentioned event slip based on the first behavior data.

3. The method of Request 1, wherein the first behavioral data further includes behavioral information corresponding to each of the more than one rule identification information, and in the case where there is no policy corresponding to the rule identification information, the method includes the following steps: confirming the behavioral information corresponding to the rule identification information based on the first behavioral data; and updating the event form based on the confirmed behavioral information.

4. The method of claim 1, wherein the rule data includes information on one or more rule conditions corresponding to each of the one or more rule identification information, and the step of obtaining rule identification information of the rule corresponding to the event sheet based on the rule data includes the following steps: confirming the one or more rule conditions included in the rule data; confirming whether the one or more rule conditions are satisfied based on the one or more event information included in the event sheet; and confirming the rule identification information, wherein the rule identification information corresponds to at least one rule condition among the one or more rule conditions that is confirmed to be satisfied.

5. As in request item 4, where each of the above-mentioned rule conditions includes: The combination type of the rule conditions, the key information of the above rule conditions, the value information of the above rule conditions, and the detailed condition information.

6. The method of request item 4, wherein the step of confirming whether the above-mentioned rule conditions are met based on the above-mentioned event information included in the event sheet includes the following steps: extracting one or more keywords included in the above-mentioned event information; and confirming whether the extracted one or more keywords meet the above-mentioned rule conditions.

7. The method of request item 4, wherein the step of confirming whether the above-mentioned rule conditions are met based on the above-mentioned event information included in the event sheet includes the following steps: confirming whether the above-mentioned event information includes one or more fields and the field values ​​corresponding to the above-mentioned one or more fields meet the above-mentioned rule conditions.

8. The method of claim 1, wherein the policy data includes policy identification information of one or more policies and information on one or more policy conditions corresponding to each of the policy identification information, the step of obtaining policy identification information of the policy corresponding to the event form based on the policy data includes the following steps: confirming the one or more policy conditions included in the policy data; confirming whether the one or more policy conditions are met based on the event information included in the event form; and confirming the policy identification information, wherein the policy identification information corresponds to at least one of the one or more policy conditions confirmed to be met.

9. As in request item 8, wherein each of the above-mentioned policy conditions includes: Information on the combination type of policy conditions, key information of the above policy conditions, value information of the above policy conditions, and detailed conditions.

10. The method of request item 8, wherein the step of confirming whether the above-mentioned policy conditions are met based on the above-mentioned event information included in the event form includes the following steps: extracting one or more keywords included in the above-mentioned event information; and confirming whether the extracted one or more keywords meet the above-mentioned policy conditions.

11. The method of request item 8, wherein the step of confirming whether the above-mentioned policy conditions are met by using the above-mentioned event information included in the event form includes the following steps: confirming whether the above-mentioned policy conditions are met by the above-mentioned event information including one or more fields and the field values ​​corresponding to the above-mentioned one or more fields.

12. The method of claim 1, comprising the following steps: receiving input for adding policy identification information to the above policy data and one or more policy conditions corresponding to the above policy identification information; and, corresponding to the above input, adding behavioral information corresponding to the policy identification information of the added policy to the above second behavioral data.

13. The method of request item 1, wherein the aforementioned behavioral information includes information that displays guidance in the aforementioned event form indicating: the processing of the aforementioned product sales process performed in accordance with the aforementioned event, or the status of the aforementioned product sales process changed in accordance with the aforementioned event.

14. An electronic device comprising: One or more processors; one or more memory units storing commands to be executed by the one or more processors; and the electronic device is configured such that, when the commands are executed by the one or more processors, the one or more processors perform the method of any one of claims 1 to 13.

15. A non-transitory computer-readable recording medium that records commands, when executed by one or more processors, to cause the one or more processors to perform actions, wherein the commands are configured to cause the one or more processors to perform any one of claims 1 to 13.

Images