Method for processing order and apparatus thereof

Abstract

Provided are technology for visualizing for a user that attempts to assign a deliverer corresponding to an order are continuously being made. A method performed by an electronic device according to an embodiment of the present disclosure may comprise the steps of: displaying a message box including a first message indicating the state of a search for a deliverer in response to a user request to search for the deliverer; determining the occurrence of a defined event on the basis of the state of the search; and dynamically updating the message box on the basis of the occurrence of the event by changing the first message included in the message box to a second message different from the first message.

Description

Method and device for processing orders

[0001] The present disclosure relates to a technology for processing orders. More specifically, it relates to a technology for visualizing to a user the ongoing attempt to assign a delivery agent to respond to an order.

[0002] The delivery service market is growing rapidly due to the expansion of contactless services driven by various environmental factors. To ensure the continued growth of this market, operators of delivery service platforms need to create platforms that satisfy all parties involved. For example, technologies are needed to efficiently assign delivery personnel to respond to orders, ensuring the satisfaction of all parties involved.

[0003] However, in the past, when assigning delivery agents to respond to orders, delays occurred due to factors such as poor weather conditions or excessive order volume. These delays could potentially lead to negative experiences for suppliers (users) of orders.

[0004] The technical challenge to be addressed by this disclosure is to provide a technology capable of preventing negative user experiences due to delays in the assignment of delivery agents.

[0005] Another technical challenge to be addressed by this disclosure is to provide a technology that can effectively reduce the cost of customer response resulting from negative user experiences.

[0006] Another technical challenge that the present disclosure seeks to address is to provide a technology that can visualize to the user that assignment is being continuously attempted even when there is a delay in the assignment of a delivery agent.

[0007] Another technical challenge to be addressed by the present disclosure is to provide a technology capable of dynamically updating the message displayed to the user when the assignment of a delivery agent is delayed.

[0008] Another technical challenge to be addressed by this disclosure is to provide a technology capable of dynamically updating the map displayed to the user when there is a delay in the assignment of a delivery agent.

[0009] Another technical challenge to be addressed through this disclosure is to provide a technology capable of dynamically updating the logic of assignment when there is a delay in the assignment of a delivery agent.

[0010] Another technical challenge to be addressed by the present disclosure is to provide a technology that can prevent unnecessary additional actions by the user (e.g., cancellation of assignment and subsequent request for assignment) that may occur when the assignment of a delivery agent is delayed.

[0011] The technical problems of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person skilled in the art of the present disclosure from the description of the specification.

[0012] A method according to one embodiment of the present disclosure may include a method performed by an electronic device, the method comprising: in response to a user request for searching for a delivery performer, displaying a message box including a first message indicating a search status for searching for the delivery performer; determining whether an event defined based on the search status has occurred; and dynamically updating the message box by changing the first message included in the message box to a second message that is distinct from the first message based on the occurrence of the event.

[0013] In one embodiment, the method may further include initiating search logic for searching for the delivery agent in response to the user request.

[0014] In one embodiment, the method may further include updating the search logic based on the occurrence of the event.

[0015] In one embodiment, the step of updating the search logic may include the step of updating the search logic to increase the benefit granted when a candidate delivery performer is assigned to the delivery performer.

[0016] In one embodiment, the step of determining whether the event has occurred may include the step of determining whether the event has occurred based on the number of times the user request has been rejected by the candidate delivery performer.

[0017] In one embodiment, the step of determining whether the event has occurred may include the step of determining whether the event has occurred based on the elapsed time since the user request was transmitted to the candidate delivery performer.

[0018] In one embodiment, the step of determining whether the event has occurred may include the step of determining whether the event has occurred based on the time of creation of an order corresponding to the user request.

[0019] In one embodiment, the step of determining whether the event has occurred may include the step of determining whether the event has occurred based on an expected completion time of an order corresponding to the user request.

[0020] In one embodiment, the step of determining whether the event has occurred may include a step of determining whether the event has occurred based on whether the assignment corresponding to the user request has been completed, and may further include a step of transmitting an alarm to an external device if the assignment has not been completed.

[0021] In one embodiment, the method may further include the step of displaying a map indicating the search status.

[0022] In one embodiment, the method may further include updating the map based on the occurrence of the event.

[0023] According to another embodiment of the present disclosure, a recording medium is a non-transitory computer-readable recording medium having recorded thereon a computer program to be executed by a processor, wherein the computer program, when executed by the processor, may be configured to cause the processor to execute any one of the above-described methods.

[0024] According to another embodiment of the present disclosure, an electronic device includes a communication interface configured to enable communication with a network, a processor configured to execute a computer program including one or more instructions, and a memory storing the computer program, wherein when the computer program is executed by the processor, the processor may be configured to execute any one of the methods described above.

[0025] According to the present disclosure, negative user experiences due to delays in the assignment of delivery agents can be prevented.

[0026] According to the present disclosure, the cost of customer response resulting from negative user experiences can be effectively reduced.

[0027] According to the present disclosure, it is possible to visualize to the user that assignment is being continuously attempted even when the assignment of the delivery agent is delayed.

[0028] According to the present disclosure, a message displayed to a user can be dynamically updated when there is a delay in the assignment of a delivery agent.

[0029] According to the present disclosure, a map exposed to a user can be dynamically updated when there is a delay in the assignment of a delivery agent.

[0030] According to the present disclosure, when there is a delay in the assignment of a delivery agent, the logic of the assignment can be dynamically updated.

[0031] According to the present disclosure, unnecessary additional actions by the user (e.g., cancellation of assignment and subsequent request for assignment) that may occur when the assignment of a delivery agent is delayed can be prevented.

[0032] The effects according to the technical idea of ​​the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person skilled in the art of the present disclosure from the description of the specification.

[0033] FIG. 1 illustrates an environment in which devices according to one embodiment of the present disclosure can be applied.

[0034] FIG. 2 illustrates a computing device capable of implementing devices according to one embodiment of the present disclosure.

[0035] FIG. 3 illustrates a flowchart illustrating a method according to one embodiment of the present disclosure.

[0036] FIG. 4 illustrates an order reception screen for an order in progress that may be referenced in various embodiments of the present disclosure.

[0037] Figure 5 illustrates a message box that may be included in the order reception screen illustrated in Figure 4.

[0038] Figures 6 and 7 illustrate a process of changing a message that can be referenced in various embodiments of the present disclosure.

[0039] FIG. 8 illustrates a flowchart illustrating a method according to another embodiment of the present disclosure.

[0040] FIG. 9 illustrates a flowchart illustrating a method according to another embodiment of the present disclosure.

[0041] The various embodiments described in this disclosure are exemplified for the purpose of clearly explaining the technical concept of this disclosure and are not intended to be limited to specific embodiments. The technical concept of this disclosure includes various modifications, equivalents, alternatives, and embodiments selectively combined from all or part of the embodiments described in this disclosure. Furthermore, the scope of the technical concept of this disclosure is not limited to the various embodiments presented below or the specific descriptions thereof.

[0042] Terms used in this disclosure, including technical or scientific terms, unless otherwise defined, may have the meaning commonly understood by a person of ordinary skill in the art to which this disclosure belongs.

[0043] The expressions "includes," "may include," "comprises," "may have," "have," and "may have" used in this disclosure indicate the presence of a target feature (e.g., a function, operation, or component), but do not exclude the presence of other additional features. In other words, such expressions should be understood as open-ended terms that imply the possibility of including other embodiments.

[0044] The singular expressions used in this disclosure may include the plural meaning unless the context clearly indicates otherwise, and the same applies to the singular expressions set forth in the claims.

[0045] As used herein, expressions such as “first,” “second,” or “first,” “second,” etc., unless the context indicates otherwise, are used to refer to multiple similar objects and to distinguish one object from another, and do not limit the order or importance among the objects.

[0046] As used herein, the expressions "A, B, and C," "A, B, or C," "at least one of A, B, and C," or "at least one of A, B, or C" 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, or (3) at least one A and at least one B.

[0047] The expression "based on" as used in this disclosure is used to describe one or more factors that influence a decision, act of judgment, or action described in a phrase or sentence containing this expression, and this expression does not exclude additional factors that influence the decision, act of judgment, or action.

[0048] As used herein, the expression that a component (e.g., a first component) is “connected” or “connected” to another component (e.g., a second component) may mean that the component is directly connected or connected to the other component, as well as connected or connected via a new other component (e.g., a third component).

[0049] The expression "configured to" used in the present disclosure may have the meanings of "set to", "having the ability to", "modified to", "made to", "capable of", etc., depending on the context. This expression is not limited to the meaning of "specifically designed in hardware", and for example, a processor configured to perform a specific operation may mean a general purpose processor that can perform the specific operation by executing software, or a special purpose computer that is structured through programming to perform the specific operation.

[0050] The term "user" used in this disclosure may refer to an entity utilizing a platform related to a delivery service. For example, a "user" may refer to any of the following: a demander of an order, a supplier of an order, or a delivery agent. However, since this disclosure focuses on technologies for inducing positive experiences for suppliers of orders, unless otherwise specifically defined, the term "user" hereinafter may be understood to refer to suppliers of orders.

[0051] The term "user interface" as used herein may refer to a physical or virtual medium designed to enable communication between a user and an object, system, machine, or computer program. According to the present disclosure, a user can utilize a platform related to a delivery service through the user interface.

[0052] Hereinafter, various embodiments of the present disclosure will be described with reference to the attached drawings. In the attached drawings and the description of the drawings, identical or substantially equivalent components may be assigned the same reference numerals. Furthermore, in the description of various embodiments below, duplicate descriptions of identical or corresponding components may be omitted, but this does not mean that such components are not included in the embodiments.

[0053] FIG. 1 illustrates an environment (100) to which devices (110, 120, 130, 141, 142) according to one embodiment of the present disclosure can be applied. The environment (100) to be described through FIG. 1 relates to an exemplary environment in which a consumer creates an order through a consumer terminal (130), a supplier receives the consumer's order through a supplier terminal (120) and prepares a product corresponding to the order, and a candidate delivery agent is assigned a delivery process corresponding to the order through a candidate delivery agent terminal (141, 142) and delivers the prepared product. In this environment (100), a platform operation server (110) can manage a platform related to a delivery service provided to the terminals (120, 130, 141, 142) of each entity.

[0054] As illustrated in FIG. 1, each entity participating in the delivery service can exchange various information related to the delivery service through their terminals (120, 130, 141, 142), and the platform operation server (110) can process and handle this various information. The operations performed by the platform operation server (110) and each entity's terminals (120, 130, 141, 142) will be described in more detail later in the specification.

[0055] Meanwhile, while FIG. 1 illustrates an example in which one supplier terminal (120), one demand terminal (130), and two candidate delivery performer terminals (141, 142) are each linked to a platform operation server (110), the number of terminals representing the number of entities participating in the delivery service may vary. Furthermore, FIG. 1 merely illustrates a preferred embodiment for achieving the purpose of the present disclosure, and some components may be added or deleted as needed.

[0056] Below, each component illustrated in Fig. 1 is described in more detail.

[0057] The platform operation server (110) can create an order based on information obtained from the consumer terminal (130). For example, information that can be used to create an order may include product details, the supplier of the product, the pickup location of the product (e.g., the supplier's address), and the delivery destination of the product (e.g., the consumer's address).

[0058] Additionally, the platform operation server (110) can transmit an order to the supplier terminal (120). When an order is transmitted to the supplier terminal (120) in this way, the supplier can identify a new order through the supplier terminal (120) and prepare a product corresponding to the order. Here, the supplier can transmit a user request to the platform operation server (110) to search for a delivery performer through the supplier terminal (120). However, alternatively, the user request may be dynamically acquired by the platform operation server (110), for example, based on the creation of an order or the transmission of an order to the supplier terminal (120).

[0059] In addition, the platform operation server (110) may, in response to a user request from a supplier terminal (120), transmit a delivery processing request for an order to at least one of one or more candidate delivery performer terminals (141, 142). Here, the process of transmitting the delivery processing request may be referred to as search logic for searching for a delivery performer corresponding to the order, and such search logic may be implemented with reference to various known matching technologies.

[0060] For example, a single delivery processing request corresponding to a single order may be transmitted to a single candidate delivery agent terminal. If the delivery processing request is accepted by the candidate delivery agent terminal to which the delivery processing request was transmitted, the platform operation server (110) may complete the assignment of delivery processing corresponding to the order. In this case, the platform operation server (110) may transmit information regarding the order to the candidate delivery agent terminal that accepted the delivery processing request, and may transmit to the supplier terminal (120) information regarding the completion of the delivery processing assignment and / or the candidate delivery agent (i.e., the delivery agent) that accepted the delivery processing request. In addition, if the candidate delivery agent terminal to which the delivery processing request was transmitted rejects the delivery processing request or does not respond to the delivery processing request for a specified period of time or longer, the platform operation server (110) may transmit the delivery processing request to another candidate delivery agent terminal. This transmission of delivery processing requests may be performed without duplication, until acceptance occurs, while being transmitted to multiple candidate delivery agent terminals.

[0061] For another example, multiple delivery processing requests corresponding to a single order may be transmitted to each of multiple candidate delivery performer terminals. If the delivery processing request is initially accepted, the platform operation server (110) may complete the delivery processing assignment to the candidate delivery performer terminal that initially accepted the delivery processing request. In this case, the platform operation server (110) may transmit order-related information to the candidate delivery performer terminal that initially accepted the delivery processing request, and may transmit to the supplier terminal (120) information regarding the completion of the delivery processing assignment and / or the candidate delivery performer (i.e., the delivery performer) that initially accepted the delivery processing request.

[0062] When delivery processing for an order is assigned to one of the multiple candidate delivery performer terminals (141, 142) through the aforementioned search logic, the delivery performer can pick up the product corresponding to the order at the pickup location and deliver the product to the delivery destination.

[0063] In addition to the operations of the platform operation server (110) described so far, the platform operation server (110) may perform various operations for processing orders by interworking with at least some of the supplier terminal (120), the demand terminal (130), and the candidate delivery performer terminals (141, 142), and may perform all operations that may be added or modified from the receipt of an order to its completion. In particular, the platform provided as a user interface to the supplier terminal (120) during the process in which the platform operation server (110) performs the search logic will be primarily described through the description of the specification later, and it should be noted that this does not exclude other operations performed by the platform operation server (110) from the scope of the present disclosure, but rather is intended to avoid obscuring the argument of the present disclosure.

[0064] The aforementioned platform operation server (110) may be implemented as one or more computing devices. For example, all functions of the platform operation server (110) may be implemented on a single computing device. For another example, the first function of the platform operation server (110) may be implemented on a first computing device, and the second function may be implemented on a second computing device. For example, the computing device may be, but is not limited to, a desktop computer, a laptop computer, an application server, a proxy server, or a cloud server, and any type of device equipped with computing functions may be a computing device.

[0065] Each of the supplier terminal (120), the demand terminal (130), and the candidate delivery performer terminals (141, 142) are terminals of each entity participating in the delivery service and can display various pages of the delivery service provided by the aforementioned platform operation server (110). These various pages of the delivery service may have a user interface defined as a function related to the delivery service applied to them. The application of such a user interface can be managed by the aforementioned platform operation server (110). In addition, each of the supplier terminal (120), the demand terminal (130), and the candidate delivery performer terminals (141, 142) can obtain inputs or requests for various pages of the delivery service, and process or transmit the inputs or requests to the platform operation server (110). Here, each of the supplier terminal (120), the demand terminal (130), and the candidate delivery performer terminals (141, 142) can perform operations defined to correspond to the inputs or requests from the platform operation server (110). As described above, in order to use the delivery service through each of the supplier terminal (120), the demand terminal (130), and the candidate delivery performer terminal (141, 142), a web browser or application may be installed on each of the supplier terminal (120), the demand terminal (130), and the candidate delivery performer terminal (141, 142).

[0066] In one embodiment, the user interfaces provided to the terminals (120, 130, 141, 142) of each subject may have at least some components (components of the user interface) implemented differently depending on the properties of each subject. Specifically, the first user interface provided to the supplier terminal (120) and the second user interface provided to the demand terminal (130) may have at least some components implemented differently depending on their properties.

[0067] The devices (110, 120, 130, 141, 142) illustrated in FIG. 1 can communicate via a network. This network can be implemented as any type of wired or wireless network, such as, for example, a local area network (LAN), a wide area network (WAN), a mobile radio communication network (MRCN), or WiBro (Wireless Broadband).

[0068] FIG. 2 illustrates a computing device (200) capable of implementing devices (110, 120, 130, 141, 142) according to one embodiment of the present disclosure. That is, the platform operation server (110), supplier terminal (120), demand terminal (130), or candidate delivery performer terminal (141, 142) illustrated in FIG. 1 may be implemented by the computing device (200) illustrated in FIG. 2. For reference, in the present disclosure, the computing device (200) may be interchangeably referred to as an electronic device.

[0069] A computing device (200) may include one or more processors (210), one or more memories (220), or a communication interface (230). In one embodiment, some components may be deleted from the computing device (200), or other components (e.g., a display or input device, etc.) may be added to the computing device (200). Additionally or alternatively, some components may be implemented in an integrated manner, or implemented as a single or multiple entities. In the present disclosure, one or more processors (210) may be referred to as a processor (210). The term “processor (210)” may mean a set of one or more processors, unless the context clearly indicates otherwise. In the present disclosure, one or more memories (220) may be referred to as a memory (220). The term “memory (220)” may mean a set of one or more memories, unless the context clearly indicates otherwise.

[0070] Below, each component illustrated in Fig. 2 will be described in more detail.

[0071] The processor (210) may perform calculations or information processing related to control or communication of each component of the computing device (200). Specifically, the processor (210) may control at least one component of the computing device (200) connected to the processor (210) by executing software (or a computer program) received from another component. As an example, the processor (210) may load a command (e.g., an instruction, a code, or a code segment) or information into the memory (220), process the command or information stored in the memory (220), and store result information according to the processing in the memory (220). In addition, the processor (210) may be operatively connected to the components of the computing device (200) to perform various operations such as calculations, processing, generation, or processing related to the present disclosure.

[0072] The memory (220) can store various information. The information stored in the memory (220) is information acquired, processed, or used by at least one component of the computing device (200), and may include software. The software may include one or more instructions that cause the processor (210) to perform operations according to various embodiments of the present disclosure when loaded into the memory (220). That is, the processor (210) may perform operations according to various embodiments of the present disclosure by executing the one or more instructions described above. The memory (220) may include, for example, volatile or non-volatile memory. In one embodiment, the program is software stored in the memory (220), and may include an operating system for controlling the resources of the computing device (200), an application, or middleware that provides various functions to the application so that the application can utilize the resources of the computing device (200).

[0073] The communication interface (230) can establish a wired or wireless communication channel with another device and transmit and receive various information with the other device. In one embodiment, the communication interface (230) may include at least one port for connecting to another device via a wired cable in order to communicate with the other device via a wired connection. In this case, the communication interface (230) can communicate with another device connected via a wired connection through the at least one port. In one embodiment, the communication interface (230) may be configured to include a cellular communication module and be connected to a cellular network (e.g., 3G, LTE, 5G, Wibro, or Wimax). In one embodiment, the communication interface (230) may include a short-range communication module and transmit and receive information with another device using short-range communication (e.g., Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), UWB). In one embodiment, the communication interface (230) may include a non-contact communication module for non-contact communication. Contactless communication may include at least one contactless proximity communication technology, such as Near Field Communication (NFC), Radio Frequency Identification (RFID), or Magnetic Secure Transmission (MST). In addition to the various examples described above, the computing device (200) may be implemented in various known ways to communicate with other devices, and the scope of the present disclosure is not limited by the examples described above.

[0074] In one embodiment, the computing device (200) may include a display. The display may display various screens (e.g., one or more pages) based on the control of the processor (210). To display screens with various interfaces applied on the display, for example, a web browser or a dedicated application may be installed on the computing device (200). In addition, the display may be a component capable of interacting with a user and may receive user input from the user. Such a display may be implemented in the form of a touch sensor panel (TSP) capable of recognizing contact or proximity of various external objects (e.g., a user's finger or stylus).

[0075] In one embodiment, the computing device (200) may include an input device (e.g., a mouse or a keyboard). The input device may receive information to be used in components of the computing device (200) from an external source (e.g., a user) of the computing device (200).

[0076] The processor (210), memory (220), and communication interface (230) illustrated in FIG. 2 are connected to each other through a bus, GPIO (General Purpose Input / Output), SPI (Serial Peripheral Interface), or MIPI (Mobile Industry Processor Interface), and can send or receive information or signals.

[0077] Below, methods according to various embodiments of the present disclosure are described in detail. While operations are depicted in a specific order in the drawings below, it should be noted that the operations do not necessarily have to be performed in the specific order depicted or in a sequential order, or that all depicted operations must be performed to achieve the desired results.

[0078] Additionally, the operations of the method described with reference to the drawings below may be performed by a computing device. In other words, the operations of the method may be implemented as one or more instructions executed by a processor of the computing device. All operations included in this method may be performed by a single physical computing device. For example, the first operation of the method may be performed by a first computing device, and the second operation of the method may be performed by a second computing device. In other words, the operations included in the method may be performed by being divided among multiple computing devices.

[0079] Hereinafter, the description will continue assuming that the operations of the aforementioned method are performed by the supplier terminal (120) illustrated in FIG. 1. In addition, for convenience of explanation, the subject of the operations included in the method may be omitted, but unless otherwise indicated in the context, it may be interpreted that the operations are performed by the supplier terminal (120).

[0080] FIG. 3 illustrates a flowchart illustrating a method according to one embodiment of the present disclosure. The operations illustrated in FIG. 3 are described in detail below.

[0081] In response to a user request, a message box may be displayed (S310). While this operation is described as being performed via the provider terminal (120), this operation may also be understood as an operation in which the platform operation server (110) transmits information corresponding to the message box to the provider terminal (120) to display the message box.

[0082] A user request may be a request from a supplier (i.e., a user) to search for a delivery agent. As described with reference to Figure 1, a user request may be generated intentionally by the supplier or dynamically based on the creation or transmission of an order.

[0083] A message box is a component of a user interface provided to a supplier terminal (120) that may include a message that can be recognized as text by a user. This message box may include a message (e.g., a first message, a second message) indicating a search status for a delivery agent.

[0084] Here, the search status can indicate the progress of the search logic that searches for a delivery agent. This search status can include, for example, the number of times a user request (or a processed delivery request) has been rejected by a candidate delivery agent, the elapsed time since the user request (or a processed delivery request) was sent to the candidate delivery agent, the elapsed time since the order was created, the remaining time until the order's expected completion, and whether the delivery processing has been completed.

[0085] In order to display the aforementioned search status as a message, continuous values ​​can be classified into multiple classes, and representative messages for each of the multiple classes can be determined in advance. For example, a rejection count of 0 to 3 can be classified into a first class, a rejection count of 4 to 6 can be classified into a second class, and a rejection count of 7 or more can be classified into a third class. In addition, for example, "A" can be determined as a representative message corresponding to the first class, "B" can be determined as a representative message corresponding to the second class, and "C" can be determined as a representative message corresponding to the third class. In this example, the supplier terminal (120) can display "A" on the display in a search status with a rejection count of 0, "B" can be displayed in a search status with a rejection count of 5, and "C" can be displayed in a search status with a rejection count of 9.

[0086] That is, by determining whether a class transition (e.g., a change from a first class to a second class) occurs or not according to the operations (S320, S330) to be described in detail later, the message included in the message box can be dynamically updated.

[0087] Based on the search status, the occurrence of a defined event can be determined (S320). While this operation is described as being performed via the provider terminal (120), the determination of the occurrence of an event can be understood as an operation performed by the platform operation server (110).

[0088] Events are defined based on the navigation state and can be rules pre-created by the platform operator involved in the delivery service to trigger results (e.g., dynamic updates to messages). Such events can be rules created to determine transitions within a defined class based on the navigation state, i.e., the progress of the navigation logic.

[0089] In one embodiment, the operation (S320) of determining whether an event has occurred may include an operation of determining whether an event has occurred based on the number of times a user request (or a delivery processing request) has been rejected by a candidate delivery performer.

[0090] For specific examples related to this embodiment, refer to the description of operation S310.

[0091] According to this embodiment, an event can be created in advance depending on the number of times a user request (or a delivery processing request) is rejected by a candidate delivery agent, and by determining whether the event occurs, a result defined to correspond to the event can be generated depending on the number of rejections.

[0092] In another embodiment, the operation (S320) of determining whether an event has occurred may include an operation of determining whether an event has occurred based on the elapsed time since the user request (or delivery processing request) was transmitted to the candidate delivery performer.

[0093] For example, if the elapsed time since the request was transmitted to multiple candidate delivery performers is less than 1 minute, it can be classified as the first class, and if the elapsed time exceeds 1 minute, it can be classified as the second class. In addition, for example, "A" can be determined as the representative message corresponding to the first class, and "B" can be determined as the representative message corresponding to the second class. In this example, the supplier terminal (120) can display "A" on the display in the search state where the elapsed time since the request was transmitted to multiple candidate delivery performers is 30 seconds, and can display "B" on the display in the search state where the elapsed time is 5 minutes. This example may be based on the search logic that transmits a user request (or delivery processing request) corresponding to one order to multiple candidate delivery performer terminals (141, 142). However, in contrast, if a search logic is applied that sequentially transmits a user request (or delivery processing request) corresponding to one order to multiple candidate delivery performer terminals (141, 142), whether an event has occurred can be determined by the sum of the elapsed time during which the request was transmitted to the multiple candidate delivery performers.

[0094] According to this embodiment, by pre-generating an event depending on the elapsed time at which a user request (or a delivery processing request) was transmitted to a candidate delivery agent and determining whether the event occurred, a result defined to correspond to the event can be generated depending on the elapsed time at which the request was transmitted to the candidate delivery agent.

[0095] In another embodiment, the operation (S320) of determining whether an event has occurred may include an operation of determining whether an event has occurred based on the time of creation of an order corresponding to a user request.

[0096] For example, if the elapsed time from the time of order creation corresponding to a user request is less than 1 minute, it can be classified as the first class, and if the elapsed time exceeds 1 minute, it can be classified as the second class. In addition, for example, "A" can be determined as the representative message corresponding to the first class, and "B" can be determined as the representative message corresponding to the second class. In this example, the supplier terminal (120) can display "A" on the display in a search state where the elapsed time from the time of order creation is 30 seconds, and can display "B" on the display in a search state where the elapsed time is 5 minutes.

[0097] According to this embodiment, by generating an event in advance depending on the time of creation of an order corresponding to a user request and determining whether the event occurs, a result defined to correspond to the event can be generated depending on the elapsed time from the time of creation of the order.

[0098] In another embodiment, the operation (S320) of determining whether an event has occurred may include an operation of determining whether an event has occurred based on the expected completion time of an order corresponding to a user request.

[0099] The expected completion time of an order can be the estimated time at which the product corresponding to the order is expected to be delivered to the customer's delivery destination. This expected completion time can be predicted based on factors such as the product details included in the order, the product's cooking time, the weather, the status of the pool of potential delivery agents, the distance between the pickup location and the delivery destination, and the distance between the delivery agent's location and the pickup location.

[0100] For example, if the remaining time until the expected completion time of an order corresponding to a user request exceeds 30 minutes, it can be classified as Class 1. If the remaining time exceeds 10 minutes and is within 30 minutes, it can be classified as Class 2. If the remaining time exceeds 5 minutes and is within 10 minutes, it can be classified as Class 3. If the remaining time is within 5 minutes, it can be classified as Class 4. In addition, for example, "A" can be determined as the representative message corresponding to Class 1, "B" can be determined as the representative message corresponding to Class 2, "C" can be determined as the representative message corresponding to Class 3, and "D" can be determined as the representative message corresponding to Class 4. For this example, the supplier terminal (120) may display "A" on the display in a search state where the remaining time until the expected completion time of the order is 35 minutes, may display "B" on the display in a search state where the remaining time is 15 minutes, may display "C" on the display in a search state where the remaining time is 6 minutes, and may display "D" on the display in a search state where the remaining time is 1 minute.

[0101] According to this embodiment, an event can be generated in advance depending on the remaining time until the expected completion time of an order corresponding to a user request, and by determining whether the event occurs, a result defined to correspond to the event can be generated depending on the remaining time.

[0102] In another embodiment, the operation (S320) of determining whether an event has occurred may include an operation of determining whether an event has occurred based on whether an assignment corresponding to a user request has been completed.

[0103] For example, if the assignment corresponding to a user request is not completed, it can be classified as a first class, and if the assignment is completed, it can be classified as a second class. Furthermore, for example, "A" can be determined as a representative message corresponding to the first class, and "B" can be determined as a representative message corresponding to the second class. In this example, the provider terminal (120) can display "A" on the display in a search state where the assignment corresponding to the user request is not completed, and can display "B" on the display in a search state where the assignment is completed.

[0104] According to this embodiment, by generating an event in advance depending on whether an assignment corresponding to a user request is completed and determining whether the event occurs, a result defined to correspond to the event can be generated depending on the completion of the assignment.

[0105] Based on the occurrence of an event, the message box can be dynamically updated (S330). While this operation is described as being performed via the provider terminal (120), this operation can also be understood as an operation in which the platform operation server (110) transmits information corresponding to the message box to the provider terminal (120) to update the message box.

[0106] Dynamic update of a message box can refer to the phenomenon of a message box automatically updating without user input. Here, the message box update can refer to various changes to the message, such as a change in message content, a change in message color, a change in message size, or a change in message layout. In other words, any change that can visually indicate a change to the user can be included in the message box update.

[0107] According to this behavior, a message box can be updated with a message corresponding to the navigation state at the time the event occurred.

[0108] An alarm may be transmitted to an external device (e.g., a platform operation server (110)) (S340). While this operation is described as being performed via a provider terminal (120), this operation may also be understood as an operation in which the platform operation server (110) acquires the alarm.

[0109] An alarm may be information that notifies the platform operator of the need for delivery processing for an order. Such an alarm may be, for example, generated by a warning sound from the speaker of the platform operation server (110) (or a device associated therewith), or by displaying a pop-up alarm or specific text on the display of the platform operation server (110) (or a device associated therewith). However, in addition to the examples described above, various known methods for notifying the platform operator of the need for delivery processing may be applied within the scope of the present disclosure.

[0110] Such an alarm may be transmitted from the supplier terminal (120) to the platform operation server (110) based on a comparison of a threshold time, such as the elapsed time since the user request (or delivery processing request) was transmitted to the candidate delivery agent, the elapsed time from the time the order was created, or the remaining time until the expected completion time of the order. For example, an alarm may be transmitted from the supplier terminal (120) to the platform operation server (110) if the elapsed time exceeds the threshold time or the remaining time is less than the threshold time. According to such an example, the platform operator may be notified of an order that specifically requires delivery processing assignment.

[0111] In one embodiment, the alarm transmission operation (S340) may be an event described in the event occurrence determination operation (S320). That is, the transmission of the alarm may be determined as the occurrence of an event, and the message box may be dynamically updated.

[0112] In another embodiment, orders may be processed by increasing the allocation priority of orders for which an alarm has been sent, for example, by sending a request for processing a delivery for an order for which an alarm has been sent to a terminal of a candidate delivery agent with a high allocation acceptance rate, or by sending a request for processing a delivery for an order for which an alarm has been sent along with a benefit that may be provided upon acceptance to the terminal of a candidate delivery agent. Such processing of orders may be performed by the platform operation server (110) illustrated in FIG. 1.

[0113] As described above with reference to FIG. 3, a message box included in a screen displayed to a user via the supplier terminal (120) can be dynamically updated. Since this update is performed in a manner that visually recognizes changes to the user, the user can visually confirm that the assignment of a delivery agent is continuously being attempted. This prevents unnecessary additional user actions that may occur when a delivery agent is assigned, such as canceling an assignment and requesting a new assignment. Furthermore, since the negative user experience resulting from the assignment delay is significantly reduced, the costs of customer service resulting from such a negative experience can also be effectively reduced.

[0114] Hereinafter, drawings that can be referenced in various embodiments of the present disclosure will be described with reference to FIGS. 4 to 7.

[0115] FIG. 4 illustrates an order reception screen (400) of an order in progress that may be referenced in various embodiments of the present disclosure.

[0116] The order reception screen (400) may be an example of a page displayed on the display of the supplier terminal (120). Referring to FIG. 4, the order reception screen (400) may include a navigation tab (410).

[0117] The navigation tab (410) may include a component that displays the default page (e.g., Home) of the order reception screen (400) and a component that displays orders categorized by their status (e.g., Pending, In Progress, Completed). When a specific component is selected by a user, a page corresponding to that specific component may be displayed to the user as the order reception screen (400).

[0118] If the "In Progress" component of the navigation tab (410) is selected, a list of orders currently to be processed by the user may be displayed on the order reception screen (400). In this case, the order reception screen (400) may include one or more message boxes (420).

[0119] A detailed description of the message box (420) is described with reference to Fig. 5.

[0120] Since FIG. 4 merely illustrates a preferred embodiment for achieving the purpose of the present disclosure, some components may be added or deleted from the order reception screen (400) as needed. Furthermore, the size or arrangement of some components may also be changed.

[0121] FIG. 5 illustrates a message box (500) that may be included in the order reception screen illustrated in FIG. 4.

[0122] A message box (500) may be a component that includes information corresponding to an order that a user is currently processing. This message box (500) may include an identifier (510) corresponding to the order, the time the order was created (520), details of products included in the order (530), user requests accompanying the order (540), an indicator (550) indicating the search status of an allocation corresponding to the order, a message (560) indicating the search status, and the remaining preparation time (570) of products corresponding to the order.

[0123] According to the method described with reference to FIG. 3, a message (560) indicating a search status can be dynamically updated. Details of the update are described with reference to FIGS. 6 and 7.

[0124] Since FIG. 5 merely illustrates a preferred embodiment for achieving the purpose of the present disclosure, some components may be added or deleted from the message box (500) as needed. In addition, the size or arrangement of some components may also be changed.

[0125] Figures 6 and 7 illustrate a process of changing a message that can be referenced in various embodiments of the present disclosure.

[0126] Referring to FIGS. 6 and 7, messages indicating a search status may be changed. Specifically, based on the occurrence of an event, the message box may be dynamically updated by changing from a first message (610, 710) to a second message (620, 720), from a second message (620, 720) to a third message (630, 730), or from a third message (630, 730) to a fourth message (640, 740).

[0127] Although FIGS. 6 and 7 illustrate changes to the content of a message, various changes to a message, such as changing the color of a message, changing the size of a message, or changing the layout of a message, may be included within the scope of the present disclosure.

[0128] Hereinafter, various methods of the present disclosure will be described with reference to FIGS. 8 and 9.

[0129] Figure 8 illustrates a flowchart illustrating a method according to another embodiment of the present disclosure. Figure 8 illustrates a method in which the target of an update based on the occurrence of an event may differ from that of Figure 3. Specifically, the method illustrated in Figure 3 may have a message box as the target of the update, while the method illustrated in Figure 8 may have a search logic as the target of the update. The operations illustrated in Figure 8 will now be described in detail.

[0130] In response to a user request, search logic for searching for a delivery agent may be initiated (S810). According to this operation, the search logic for searching for a delivery agent may be initiated in response to a user request to search for a delivery agent. If the user request is dynamically acquired by the platform operation server (110) upon order creation, the search logic may be initiated immediately upon order creation.

[0131] Based on the search status, the occurrence of a defined event can be determined (S820). This operation can be understood as being identical to the operation for determining the occurrence of an event (S320) described with reference to FIG. 3, and therefore, a detailed description of this operation is omitted.

[0132] Based on the occurrence of an event, the search logic can be updated (S830).

[0133] In one embodiment, this operation may include updating the search logic to increase the benefits (e.g., delivery fees) granted to a candidate delivery agent when assigned as a delivery agent. In this case, the increased benefits may improve the delivery acceptance rate of the candidate delivery agent. In another embodiment, this operation may include updating the search logic to increase the distance between the pickup location and the candidate delivery agent's current location. This may increase the likelihood of being assigned to a delivery process by expanding the pool of candidate delivery agents.

[0134] An alarm may be transmitted to an external device (S840). This operation can be understood as being identical to the alarm transmission operation (S840) described with reference to FIG. 3, and therefore a detailed description of this operation is omitted.

[0135] As described above with reference to FIG. 8, the logic for attempting to assign a shipping process corresponding to an order, i.e., the search logic for searching for a shipping agent, can be dynamically updated. The method illustrated in FIG. 8 can be implemented in parallel with the method illustrated in FIG. 3 , allowing the actual search logic to be updated to improve the likelihood of assigning a shipping process corresponding to an order, along with visual changes to the message box.

[0136] Figure 9 illustrates a flowchart illustrating a method according to another embodiment of the present disclosure. Figure 9 illustrates a method in which the target of an update based on the occurrence of an event may differ from that of Figure 3. Specifically, the method illustrated in Figure 3 may have a message box as the target of the update, while the method illustrated in Figure 9 may have a map as the target of the update. The operations illustrated in Figure 9 are described in detail below.

[0137] In response to a user request, a map may be displayed (S910).

[0138] The map can indicate a search status. Here, the search status can be displayed on the map as a radius within which a candidate delivery agent is searched. This radius can be an indicator of the distance limit between the pickup location and a specific point (e.g., the location of the candidate delivery agent).

[0139] According to this operation, a map indicating the search status can be displayed on the display of the supplier terminal (120) upon a user request to search for a delivery agent. If the user request is dynamically acquired by the platform operation server (110) upon order creation, the map can be displayed immediately upon order creation.

[0140] Based on the search status, the occurrence of a defined event can be determined (S920). This operation can be understood as being identical to the operation for determining the occurrence of an event (S320) described with reference to FIG. 3, and therefore, a detailed description of this operation is omitted.

[0141] Based on the occurrence of an event, the map can be updated (S930).

[0142] In one embodiment, this action may include updating the map to increase the search radius displayed on the map. In this case, the expanded pool of candidate delivery agents can be visually recognized by the user.

[0143] An alarm may be transmitted to an external device (S940). This operation can be understood as being identical to the alarm transmission operation (S840) described with reference to FIG. 3, and therefore a detailed description of this operation is omitted.

[0144] As described above with reference to Figure 9, a map indicating the search status for a delivery agent can be dynamically updated. The method illustrated in Figure 9 can be implemented in parallel with the method illustrated in Figure 3, allowing users to more effectively perceive visual changes. This maximizes the effectiveness of the method illustrated in Figure 3.

[0145] In the flowcharts of this disclosure, the operations of the method or algorithm are described in a sequential order, but may also be performed in any order that can be arbitrarily combined. The description of the flowcharts of this disclosure does not exclude variations or modifications to the method or algorithm, and does not imply that any operation is essential or desirable. In one embodiment, at least some of the operations may be performed in parallel, iteratively, or heuristically. In another embodiment, at least some of the operations may be omitted, or other operations may be added.

[0146] Various embodiments of the present disclosure may be implemented as software on a machine-readable storage medium (MRSM) that can be read by a computing device. The software may be software for implementing various embodiments of the present disclosure. The software may be inferred from various embodiments of the present disclosure by programmers skilled in the art to which the present disclosure pertains. For example, the software may be a computer program including instructions that can be read by a computing device. A computing device is a device capable of operating according to instructions called from a storage medium, and may be interchangeably referred to as, for example, an electronic device. In one embodiment, a processor of the computing device may execute the called instructions, causing components of the computing device to perform functions corresponding to the instructions. A storage medium may refer to any type of recording medium that stores information that can be read by a device. The storage medium may include, for example, ROM, RAM, CD-ROM, magnetic tape, floppy disks, or optical information storage devices. In one embodiment, the storage medium may be implemented in a distributed form, such as in a network-connected computer system. In this case, the software may be distributed, stored, and executed in the computer system. In another embodiment, the storage medium may be a non-transitory storage medium. A non-transitory storage medium refers to a medium that exists regardless of whether information is stored semi-permanently or temporarily, and does not contain signals that are propagated transitorily.

[0147] While the technical concepts of the present disclosure have been described through various embodiments, the technical concepts of the present disclosure encompass various substitutions, modifications, and variations that can be made within the scope understandable to those of ordinary skill in the art to which the present disclosure pertains. Furthermore, it should be understood that such substitutions, modifications, and variations are encompassed within the scope of the appended claims.

Claims

1. In a method performed by an electronic device, In response to a user request to search for a delivery performer, displaying a message box including a first message indicating a search status of searching for the delivery performer; A step of determining whether an event defined based on the above search status has occurred; and A method comprising the step of dynamically updating the message box by changing the first message included in the message box to a second message that is distinct from the first message based on the occurrence of the event.

2. In paragraph 1, A method further comprising the step of initiating search logic for searching for the delivery performer in response to the user request.

3. In paragraph 2, A method further comprising the step of updating the search logic based on the occurrence of the above event.

4. In paragraph 3, The steps to update the above search logic are: A method comprising the step of updating the search logic to increase the benefits granted when a candidate delivery performer is assigned to the delivery performer.

5. In paragraph 1, The step of determining whether the above event has occurred is: A method comprising the step of determining whether the event has occurred based on the number of times the user request has been rejected by the candidate delivery performer.

6. In paragraph 1, The step of determining whether the above event has occurred is: A method comprising the step of determining whether the event has occurred based on the elapsed time since the user request was transmitted to the candidate delivery performer.

7. In paragraph 1, The step of determining whether the above event has occurred is: A method comprising a step of determining whether the event has occurred based on the time of creation of an order corresponding to the user request.

8. In paragraph 1, The step of determining whether the above event has occurred is: A method comprising a step of determining whether the event has occurred based on the expected completion time of an order corresponding to the user request.

9. In paragraph 1, The step of determining whether the above event has occurred is: A step of determining whether the event has occurred based on whether the assignment corresponding to the user request has been completed, A method further comprising the step of transmitting an alarm to an external device if the above assignment is not completed.

10. In paragraph 1, A method further comprising the step of displaying a map indicating the above search status.

11. In paragraph 10, A method further comprising the step of updating the map based on the occurrence of the above event.

12. In a non-transitory computer-readable recording medium recording a computer program to be executed by a processor, A non-transitory computer-readable recording medium, wherein the computer program, when executed by the processor, is configured to cause the processor to perform a method according to any one of claims 1 to 11.

13. A communication interface configured to enable communication with a network; A processor configured to execute a computer program comprising one or more instructions; and including a memory in which the above computer program is stored, An electronic device, wherein when the computer program is executed by the processor, the processor is configured to execute a method according to any one of claims 1 to 11.

Images