Method for providing integrated shopping information by collecting and managing shopping histories delivered to user through plurality of shopping channels and providing the user's shopping histories through single integrated platform based on ai

Abstract

A method for providing integrated shopping information is disclosed. For example, the method for providing integrated shopping information may include, using a communication interface, an operation of obtaining a first received record related to the user’s shopping activity from a user terminal at a first period, which is transmitted from a first external channel to a user terminal via a messaging service; an operation of obtaining a post-processed received record corresponding to the first received record by applying a pre-processing algorithm corresponding to duplicate message removal and representation format normalization to the first received record; an operation of classifying a plurality of messages included in the post-processed received record into one of a plurality of categories including orders, returns, and exchanges, respectively, through a rule-based classification algorithm for the plurality of messages included in the post-processed received record; an operation of providing a shopping information integration interface to the user terminal, which includes classification results and update status by the plurality of categories, in response to receiving an update request from the user terminal; and an operation of providing a customized statistical dashboard including the number of included messages and increase / decrease patterns for each of the plurality of categories at a second period longer than the first period.

Description

Technology Field

[0001] The present invention relates to a method for providing integrated shopping information that aggregates and manages shopping history delivered to a user by a plurality of shopping channels, and integrates and provides the user's shopping history through a single integrated platform. Background Technology

[0002] With the recent surge in e-commerce, users are purchasing items through various shopping platforms. Each of these platforms delivers separate notifications regarding order confirmations, shipping progress, and returns and exchanges to user devices via messaging services. However, users face the inconvenience of having to personally check and manage messages arriving individually from multiple platforms.

[0003] In particular, when the same user engages in purchasing activities across multiple shopping channels, it is difficult to manage them integrally due to differences in the format and expression of messages sent from each channel. While message history varies—such as order completion, shipping initiation, and return requests—the lack of consistency in message structure or keywords makes it difficult for users to intuitively understand them.

[0004] Previously, order history and delivery status could be checked through applications provided by individual platforms; however, managing multiple platforms simultaneously increases the management burden for users. Additionally, there is a limitation in that time-series critical information, such as delivery progress or refund completion status, cannot be integrated and displayed on a single screen.

[0005] Therefore, there is a need for technical means to integrate and manage messages delivered from multiple shopping channels on a single platform, and to organize and provide information such as orders, returns, and exchanges by category.

[0006] This enables users to manage their overall shopping activities more efficiently and identify changes in status at precise points in time. In this regard, documents such as Korean Patent Publication No. 10-2025-0084761 and Korean Patent Publication No. 10-2023-0101367 have been disclosed. The problem to be solved

[0007] According to the present invention, message management efficiency is improved by periodically acquiring messages transmitted to a user terminal from a plurality of external shopping channels and performing duplicate removal and format normalization through preprocessing. Through this, the user can check messages scattered across multiple platforms in a unified form.

[0008] According to the present invention, a rule-based classification algorithm is applied to automatically classify messages into categories such as orders, returns, and exchanges, and furthermore, an additional segmentation algorithm is applied to time-series categories for delivery stages (e.g., in transit, delivery completed, collection completed, refund completed, etc.) to provide the user with segmented details, thereby enabling the user to intuitively and systematically understand their shopping history.

[0009] According to the present invention, a customized statistical dashboard is provided periodically to visually present the number of messages and patterns of increase and decrease for each category. Accordingly, users can easily recognize trends in purchases, returns, and exchanges during a specific period and analyze shopping patterns.

[0010] According to the present invention, by supporting the sharing of information with an external terminal based on the approval of a user terminal, the effect of safely sharing delivery information with family members or third parties is provided. Through this, user convenience as well as the security and reliability of information sharing are simultaneously enhanced.

[0011] The technical problems of the present invention are not limited to those mentioned above, and other unmentioned technical problems will be clearly understood by those skilled in the art from the description below. means of solving the problem

[0012] An electronic device including a processor according to an embodiment of the present invention collects and manages shopping history transmitted to a user by a plurality of shopping channels, and provides shopping information integration by integrating the user's shopping history through a single integrated platform. The method comprises the following operations: the processor, using a communication interface, acquires a first received history related to the user's shopping activity transmitted from a first external channel to a user terminal via a messaging service at a first periodic rate; the processor, applying a preprocessing algorithm corresponding to duplicate message removal and expression format normalization to the first received history to acquire a postprocessed received history corresponding to the first received history; the processor, classifying a plurality of messages included in the postprocessed received history into one of a plurality of categories including orders, returns, and exchanges, using a rule-based classification algorithm for the plurality of messages; the processor, in response to receiving an update request from the user terminal, providing a shopping information integration interface to the user terminal that includes classification results by the plurality of categories and update status; and the processor, at a second periodic rate longer than the first periodic rate It may include an operation that provides a customized statistical dashboard including the number of included messages and increase / decrease patterns for each of multiple categories.

[0013] According to one embodiment, the shopping information integration provision method may further include: the operation of the processor applying an information extraction algorithm to the plurality of messages to verify the metadata of each of the plurality of target items corresponding to each of the plurality of messages; the operation of the processor acquiring a second reception history transmitted to the user terminal from a second external channel through the messaging service at a third period shorter than the first period; the operation of the processor verifying the delivery information of the plurality of target items using the second reception history and the metadata and updating the delivery information at the third period; and the operation of the processor providing the delivery information to the user terminal at the third period.

[0014] According to one embodiment, the shopping information integration provision method may further include the operation of the processor classifying the first message into one of two time-series categories, "in transit" and "delivery completed," based on the result of applying the rule-based classification algorithm to the first message included in the category of the delivery information and the order; the operation of the processor classifying the second message into one of three time-series categories, "return request," "collection completed," and "refund completed," based on the result of applying the rule-based classification algorithm to the second message included in the category of the delivery information and the return; and the operation of the processor classifying the third message into one of three time-series categories, "exchange request," "collection completed," and "exchange completed," based on the result of applying the rule-based classification algorithm to the third message included in the category of the delivery information and the exchange. For example, the first external channels may correspond to a shopping platform associated with e-commerce and supporting item purchase services for the user, and the second external channels may correspond to a delivery platform associated with delivery and logistics and supporting item delivery services for the user.

[0015] According to one embodiment, the first cycle may correspond to 1 day, the second cycle may correspond to 7 days, and the third cycle may correspond to 2 hours.

[0016] According to one embodiment, the shopping information integration provision method may further include: an operation in which the processor requests approval from the user terminal in response to receiving a request for information sharing with the user terminal from an external terminal; an operation in which the processor provides the delivery information together to the external terminal every third period in response to receiving an approval input from the user terminal; and an operation in which the processor updates external user delivery information corresponding to the external terminal every third period and provides it to the user terminal.

[0017] The above method for providing integrated shopping information is,

[0018] The above processor performs an operation of filtering and excluding other received records that are not received through the first external channel from among a plurality of received records received by the user terminal, based on a regular expression pattern matching and natural language processing-based classification model;

[0019] The above processor further includes the operation of identifying only messages containing a pre-set core keyword as the first reception history.

[0020] The above method for providing integrated shopping information is,

[0021] The above processor performs the operation of confirming the order completion item for which the user has completed the order, based on the first message included in the category of the order among the plurality of messages included in the post-processing reception history;

[0022] The above processor performs the operation of identifying a repeat purchase item purchased more than a predetermined number of times based on the above-mentioned completed order item; and

[0023] The above processor further includes the operation of assigning a regular purchase prediction tag to the above recurring purchase item when the above recurring purchase item is identified, and the operation of the above processor providing a list of regular purchase items including the recurring purchase item to which the regular purchase prediction tag has been assigned to a separate widget area included in the shopping information integration interface.

[0024] The above method for providing integrated shopping information is,

[0025] The above processor performs the operation of predicting the possibility of delivery delay for each of the second received records by combining real-time traffic information and weather information obtained from an external server with the delivery information; and

[0026] The above processor further includes the operation of, when a target message is identified among the second received records based on the possibility of delivery delay that the probability of the delivery time being delayed by more than a predetermined time corresponds to a probability greater than a predetermined probability, providing a “predicted delivery delay notification” for a delivery delay item corresponding to the target message to the user terminal and correcting and displaying the predicted arrival time.

[0027] The above method for providing integrated shopping information is,

[0028] The above processor performs the operation of querying validity period data by item category from an external database based on specific item information included in a specific order message of the post-processing received history; and

[0029] The above processor further includes the operation of identifying a risk item among the ordered items ordered by the user, based on the validity period data, for which the expiration date of the corresponding validity period is within a predetermined threshold period, and the operation of the processor providing a “consumption period imminent notification” or “quick use recommendation” message regarding the risk item to the user terminal.

[0030] The above method for providing integrated shopping information is,

[0031] The above processor performs the operation of normalizing the delivery address data included in the post-processing received history to automatically cluster delivery address patterns by user; and

[0032] The processor further includes the operation of detecting a delivery delay event that occurs repeatedly at a specific delivery location based on the clustering result, labeling the target delivery location corresponding to the detected delivery delay event as a “delivery vulnerable location,” and providing the labeling result to the user terminal.

[0033] The above method for providing integrated shopping information is,

[0034] The above processor performs the operation of confirming the order completion item for which the user has completed the order through the first message included in the category of the order among the messages included in the post-processing reception history;

[0035] The above processor performs the operation of matching the metadata of the order-completed item with an external image database to identify the item representative image of the order-completed item; and

[0036] The above processor further includes the operation of displaying the representative image of the item in a thumbnail form next to the first message in the shopping information integration interface provided to the user terminal. Effects of the invention

[0037] The effects of the method for providing integrated shopping information according to embodiments of the present invention are described as follows.

[0038] According to the present invention, message management efficiency is improved by periodically acquiring messages transmitted to a user terminal from a plurality of external shopping channels and performing duplicate removal and format normalization through preprocessing. Through this, the user can check messages scattered across multiple platforms in a unified form.

[0039] According to the present invention, a rule-based classification algorithm is applied to automatically classify messages into categories such as orders, returns, and exchanges, and furthermore, an additional segmentation algorithm is applied to time-series categories for delivery stages (e.g., in transit, delivery completed, collection completed, refund completed, etc.) to provide the user with segmented details, thereby enabling the user to intuitively and systematically understand their shopping history.

[0040] According to the present invention, a customized statistical dashboard is provided periodically to visually present the number of messages and patterns of increase and decrease for each category. Accordingly, users can easily recognize trends in purchases, returns, and exchanges during a specific period and analyze shopping patterns.

[0041] According to the present invention, by supporting the sharing of information with an external terminal based on the approval of a user terminal, the effect of safely sharing delivery information with family members or third parties is provided. Through this, user convenience as well as the security and reliability of information sharing are simultaneously enhanced.

[0042] In addition, various effects that can be identified directly or indirectly through this document may be provided. Brief explanation of the drawing

[0043] FIG. 1 is a block diagram showing the components of an electronic device according to one embodiment of the present invention. FIG. 2 is a block diagram showing the components of a shopping information integration provision system including an electronic device according to one embodiment of the present invention. FIG. 3 is a conceptual diagram showing one example of an information shopping information integration interface provided through a shopping information integration provision method according to one embodiment of the present invention. FIG. 4 is a diagram conceptually illustrating the operation flow of a shopping information integration provision system according to one embodiment of the present invention. FIG. 5 is a flowchart of the operation of a method for providing integrated shopping information according to one embodiment of the present invention. In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Specific details for implementing the invention

[0044] Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that in assigning reference numerals to the components of each drawing, the same components are given the same reference numeral whenever possible, even if they are shown in different drawings. Furthermore, in describing the embodiments of the present invention, if it is determined that a detailed description of related known components or functions would hinder understanding of the embodiments of the present invention, such detailed description is omitted.

[0045] In describing the components of the embodiments of the present invention, terms such as first, second, A, B, (a), (b), etc., may be used. These terms are intended merely to distinguish the components from other components, and the essence, order, or sequence of the components is not limited by the terms. Furthermore, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the present invention pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this application.

[0046] Hereinafter, embodiments of the present invention will be described in detail with reference to FIGS. 1 to 5.

[0048] FIG. 1 is a block diagram showing the components of an electronic device according to one embodiment of the present invention.

[0049] According to one embodiment, the electronic device (100) may include a memory (110), a processor (120), a communication interface (130), and / or a display device (140). The configuration of the electronic device (100) shown in FIG. 1 is exemplary and the embodiments of the present invention are not limited thereto. For example, the electronic device (100) may further include components not shown in FIG. 1 (e.g., a web crawler, a user interface, an input device, a notification unit, a sensor unit, or at least one of any combination thereof).

[0050] According to one embodiment, the memory (110) may store instructions or data. For example, the memory (110) may store one or more instructions that cause the electronic device (100) to perform various operations when executed by the processor (120).

[0051] For example, the memory (110) may be implemented as a single chipset with the processor (120). The processor (120) may include at least one of a communication processor or a modem.

[0052] For example, the memory (110) can store various information related to the electronic device (100). For example, the memory (110) can store information regarding the operation history of the processor (120). For example, the memory (110) can store input data acquired by the electronic device (100), output data output by the electronic device (100), data acquired from an external device (e.g., a user terminal and / or an external server), etc.

[0053] For example, the memory (110) may include multiple storage devices of different types. For example, the memory (110) may include volatile and / or non-volatile storage media. For example, the memory (110) may include at least one of RAM (random-access memory), ROM (read only memory), eMMC (Embedded Multi-Media Card), or any combination thereof.

[0054] The steps of the method or algorithm described in connection with the embodiments disclosed in this specification may be directly implemented in hardware, software modules, or a combination of both, executed by the processor (120). The software modules may reside in a storage medium (i.e., memory (110)) such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, or a CD-ROM.

[0055] For example, the memory (110) is coupled to a processor (120), and the processor (120) can read information from a storage medium and write information to a storage medium. Alternatively, the memory (110) may be integrated with the processor (120). The memory (110) and the processor (120) may reside within an application-specific integrated circuit (ASIC). The ASIC may reside within a user terminal. Alternatively, the memory (110) and the processor (120) may reside as separate components within the user terminal.

[0056] According to one embodiment, the processor (120) may be operatively connected to the memory (110), the communication interface (130), and / or the display device (140). For example, the processor (120) may control the operation of the memory (110), the communication interface (130), and / or the display device (140).

[0057] According to one embodiment, the communication interface (130) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an electronic device (100) and an external device (e.g., user terminal (210) of FIG. 2, external server (220), and database, etc.), and the performance of communication through the established communication channel. The communication interface (130) may include one or more communication processors that operate independently of the processor (120) (e.g., application processor) and support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication interface (130) may include a wireless communication module (e.g., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device through a first network (e.g., a short-range communication network such as Bluetooth, WiFi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (e.g., a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a long-range communication network such as a computer network (e.g., LAN or WAN). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module can identify or authenticate the electronic device (100) within a communication network, such as the first network or the second network, using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in a subscriber identification module.

[0058] According to one embodiment, the display device (140) may include at least one output device that provides various information and a user interface to the user.

[0059] For example, the display device (140) may include a display device, an audio output device, a virtual reality output device, etc.

[0060] For example, the display device (140) can provide the administrator with various types of user interfaces described in the present disclosure visually and / or audibly.

[0061] The components of the electronic device (100) illustrated in FIG. 1 are exemplary, and the embodiments of the present disclosure are not limited thereto.

[0062] At least some of the embodiments of the present disclosure may be implemented as artificial intelligence (AI) through a processor (120) and memory (110) of an electronic device (100). The processor (120) may be composed of one or more processors, and the one or more processors may be general-purpose processors such as a CPU, AP, DSP (digital signal processor), etc., graphics-dedicated processors such as a GPU, VPU (vision processing unit), or artificial intelligence-dedicated processors such as an NPU. The one or more processors may be controlled to process input data according to predefined operation rules or artificial intelligence models stored in memory (110). Alternatively, if the one or more processors are artificial intelligence-dedicated processors, the artificial intelligence-dedicated processors may be designed with a hardware structure specialized for processing a specific artificial intelligence model.

[0063] The predefined operation rules or artificial intelligence models are characterized by being created through learning. Here, being created through learning means that a predefined operation rules or artificial intelligence models configured to perform a desired characteristic (or purpose) are created by a basic artificial intelligence model being trained using a number of learning data by a learning algorithm. Such learning may be performed within the electronic device (100) itself where the artificial intelligence according to the present disclosure is performed, or it may be performed through a separate server and / or system. Examples of learning algorithms include supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but are not limited to the examples described above.

[0064] An artificial intelligence model may be composed of multiple neural network layers. Each of the multiple neural network layers has multiple weight values ​​and can perform neural network operations through operations between the results of previous layers and the multiple weights. The multiple weights possessed by the multiple neural network layers can be optimized based on the learning results of the artificial intelligence model. For example, the multiple weights can be updated so that the loss value or cost value obtained from the artificial intelligence model during the learning process is reduced or minimized. Artificial neural networks may include, but are not limited to, deep neural networks (DNN), convolutional neural networks (CNN), recurrent neural networks (RNN), restricted Boltzmann machines (RBM), deep belief networks (DBN), bidirectional recurrent deep neural networks (BRDNN), or deep Q-networks.

[0065] The artificial intelligence model may be a classification model modeled (or trained) based on the correlation between input data and output data, using, for example, reception history related to a user's shopping activity received through a messaging service as input data, and post-processed reception history corresponding to the reception history, verified by applying a pre-processing algorithm corresponding to duplicate message removal and representation format normalization to the reception history, as output data.

[0067] FIG. 2 is a block diagram showing the components of a shopping information integration provision system including an electronic device according to one embodiment of the present invention.

[0068] According to one embodiment, the shopping information integration provision system may include an electronic device (100), a user terminal (210), and an external server (220).

[0069] According to one embodiment, the electronic device (100) may be implemented as a management server of a shopping information integration provision system. The electronic device (100) may collect messaging service history transmitted to a user terminal (210) from multiple shopping channels and perform the function of managing the messages in an integrated manner. Through this, the electronic device (100) supports the user's entire shopping activity to be viewed on a single platform.

[0070] The electronic device (100) may include a processor, memory, and a communication interface. The processor applies a preprocessing algorithm to the received message to remove duplicate messages and normalize the representation format. During this process, the memory stores the post-processed message data, and the communication interface may be responsible for transmitting and receiving data with the user terminal (210) and the external server (220).

[0071] The electronic device (100) can automatically classify messages into categories such as orders, returns, and exchanges by applying a rule-based classification algorithm to post-processed messages. Furthermore, it performs subdivision by delivery stage (e.g., preparing for delivery, in transit, delivery completed) or subdivision by return stage (e.g., return request, collection completed, refund completed), thereby enabling the user to intuitively understand their shopping-related flow in real time on a single platform.

[0072] The electronic device (100) can provide a customized interface to the user terminal (210) at regular intervals based on classified messages. Additionally, at regular intervals of a second period longer than the first period, it analyzes the number of messages by category and the pattern of increase or decrease, thereby generating and providing a customized statistical dashboard so that the user can check their shopping patterns at a glance.

[0073] The electronic device (100) can collect delivery-related data, logistics events, or courier company invoice information by linking with an external server (220). At this time, the electronic device (100) can match the metadata of the user order item with the delivery information obtained from the external server (220) to provide accurate and reliable delivery status update information to the user terminal (210).

[0074] According to one embodiment, the user terminal (210) may be implemented as a smartphone, tablet, or other mobile device carried by a shopping user. The user terminal (210) is connected to an electronic device (100) to receive and display system output results in real time, such as shopping history, classification results, delivery status, and a customized statistics dashboard.

[0075] The user terminal (210) can intuitively check which category each message belongs to—order, return, or exchange—through the integrated interface received from the electronic device (100). In addition, the progress of each delivery stage or the refund processing status can also be checked in an integrated manner on the same screen.

[0076] The user terminal (210) may also manually generate an update request. For example, when the user performs a 'refresh' within the app, the electronic device (100) immediately provides the latest classification results and update status to the user terminal (210). This allows the user to obtain the latest shopping information at a desired time.

[0077] The user terminal (210) may also be provided with a customized statistical dashboard. The dashboard is visualized and displayed in the form of graphs or charts along with data such as the number of purchases, return rate, and number of exchanges over a certain period, and helps the user analyze and manage their shopping patterns.

[0078] The user terminal (210) can also respond to requests for information sharing with an external terminal. When an external terminal requests the sharing of delivery information, the user terminal (210) directly receives an input regarding approval and transmits it to the electronic device (100). Subsequently, if an approval input is obtained by the user terminal (210), the external terminal can access the user delivery information through the electronic device (100), and the user terminal (210) can check the sharing history regarding this.

[0079] According to one embodiment, the external server (220) is a server device connected to the electronic device (100) via a network and performs the role of providing data related to delivery and logistics. The external server (220) may be any one of a courier server, a logistics management server, or a cloud-based data server.

[0080] The external server (220) operates independently of the shopping platform and primarily provides data specialized in delivery information to the electronic device (100). For example, the data specialized in delivery information may include data regarding delivery-related information of an item (e.g., invoice number, delivery start time, delivery completion status, or logistics events (loss, delay, redelivery, etc.)).

[0081] The external server (220) can provide the latest delivery data in response to a request from the electronic device (100) and can transmit updated delivery information every third cycle. Through this, the electronic device (100) can provide accurate delivery status information to the user terminal (210) in conjunction with the metadata of the ordered item.

[0082] The external server (220) can also perform event-based data transmission. For example, in the event of a delay during delivery or an unexpected accident, the relevant information is immediately transmitted to the electronic device (100) so that it is reflected in the user terminal (210). Through this, the system can simultaneously ensure real-time performance and reliability.

[0083] The external server (220) may also be linked with an external terminal. For example, if an external terminal requests the sharing of user delivery information from the electronic device (100) and / or the external server (220), the external server (220) can periodically update and transmit the data through mutual communication with the electronic device (100). Through this, user delivery information can be provided in a synchronized state between the user terminal and the external terminal.

[0085] FIG. 3 is a conceptual diagram showing one example of an information shopping information integration interface provided through a shopping information integration provision method according to one embodiment of the present invention.

[0086] The interface illustrated in FIG. 3 corresponds to a shopping information integration interface provided by an electronic device (100) to a user terminal. The shopping information integration interface may be provided to the user through one screen of an application installed on the user terminal and executed by the user.

[0087] According to one embodiment, the first interface (310) is located in the top area of ​​the shopping information integration interface and specifies the “shopping information integration provision platform” so that the user can recognize that they are currently checking information through a single integrated system. This serves to provide the brand and functional identity of the platform. The left side of the first interface (310) includes a “menu tab,” and when user input (e.g., touch input) is detected in that area, the electronic device (100) can provide a menu list to the user terminal.

[0088] According to one embodiment, the second interface (320) may be implemented in the form of a search interface. Through this interface, the user can input specific keywords (e.g., “bag”, “sneakers”) to quickly view shopping information, such as order or delivery history of items corresponding to the keywords. Additionally, the electronic device (100) can enhance user convenience by supporting an auto-complete function or recent search history.

[0089] According to one embodiment, the third interface (330) is a date selection unit (or calendar navigator) for setting a period of time and provides a calendar-based visual UI. The user can move to a specific month using left and right arrows, and by clicking on a specific date, the user can view details of orders, deliveries, returns, and refund messages associated with that date.

[0090] According to one embodiment, the fourth interface (340) may be implemented in the form of a calendar interface. Through this interface, the user can intuitively check messages received for each date. For example, if multiple messages occur on a specific date, they are displayed as dots or colors, allowing the user to check the traffic pattern at a glance. Specifically, each colored dot is distinguished by categories such as orders, deliveries, returns, and refunds, thereby providing the user with intuitive and immediate interface usability.

[0091] According to one embodiment, the fifth interface (350) includes category buttons (order, delivery, return, refund) and allows the user to filter and view only messages within the desired category. This enables the user to quickly view only the necessary information from a vast amount of shopping history.

[0092] According to one embodiment, the sixth interface (360) is a space for displaying summarized status icons, each circular icon visually displays recent major events. For example, if a new event occurs on the 'shipping in progress' icon, the color may be highlighted or a badge may appear.

[0093] According to one embodiment, the seventh interface (370) is connected to functions such as a bottom navigation bar, search, home screen, user profile, and settings. This allows the user to navigate quickly and intuitively between various functions.

[0094] According to one embodiment, reference numeral 380 may be defined as an area that displays an enlarged view of a specific date among a plurality of dates included in the fourth interface (340). For example, the user can distinguish and view events customized by color by date, and the electronic device (100) visualizes that multiple category messages occurred simultaneously on the corresponding date as color dots. Through this, the user can intuitively understand the event density of a specific date.

[0096] FIG. 4 is a conceptual diagram showing the operation flow of a shopping information integration provision system according to one embodiment of the present invention.

[0097] At least one external channel (410) may include at least one shopping platform, delivery platform, or logistics management server. The external channel (410) may transmit information related to a user's shopping activity to a user terminal (210) or electronic device (100) via a messaging service. For example, information related to shopping activity may include an order completion message, a shipping start notification, a return acceptance message, etc.

[0098] The electronic device (100) can obtain message data transmitted to the user terminal (210) from at least one external channel (410) repeatedly through the user terminal (210) based on a predetermined period.

[0099] The electronic device (100) may correspond to a management server that manages the shopping information integration provision service.

[0100] The electronic device (100) can preprocess, classify, and analyze the received data to provide the user with the final integrated information.

[0101] The user terminal (210) is a mobile device such as a smartphone or tablet, and can be connected to an electronic device (100) to receive shopping integration information.

[0102] The user terminal (210) can also generate an update request to receive the latest updated data from the electronic device (100).

[0103] The user (499) is the end consumer of the system and directly receives original messages transmitted from at least one external channel (410), while simultaneously receiving integrated information processed and classified by the electronic device (100) through the user terminal (210). Through this, the user can efficiently manage their shopping activities by comparing the original information with the integrated information.

[0104] Furthermore, although not a city, the electronic device (100) is also connected to an external server (220) to periodically collect information such as tracking numbers, delivery delays, and collection completion status provided by a courier server or a logistics management server. This enables the user to check not only simple message-based information but also real-time logistics status in an integrated manner.

[0106] FIG. 5 is a flowchart of a method for providing integrated shopping information according to one embodiment of the present invention.

[0107] According to one embodiment, an electronic device (e.g., the electronic device (100) of FIG. 1) may perform the operations disclosed in FIG. 5. For example, at least some of the components included in the electronic device (e.g., the memory (110), processor (120), communication interface (130), and display device (140) of FIG. 1 may be configured to perform the operations of FIG. 5.

[0108] In the following embodiments, the operations of S510 to S550 may be performed sequentially, but are not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Additionally, content corresponding to or overlapping with the above description in relation to FIG. 5 may be briefly explained or omitted.

[0109] According to one embodiment, the processor (120) can obtain a first reception history related to the user's shopping activity, which is transmitted from a first external channel to a user terminal through a messaging service, from the user terminal at a first period (S550).

[0110] For example, the processor (120) can periodically collect messaging service details sent to the user from the user terminal from first external channels (e.g., A shopping mall, B fashion mall, C open market).

[0111] For example, the first cycle can be defined on a daily basis, and the processor (120) can check the message log stored in the user terminal at a specific time each day (e.g., 9 a.m.) and obtain new reception records.

[0112] For example, the processor (120) can filter and exclude other received records (e.g., advertising spam, bank notifications, text messages received from friends, etc.) that were not received through the first external channel from among multiple received records received by the user terminal based on regular expression (e.g., Regex) pattern matching or a natural language processing-based classification model, and obtain only messages satisfying a specific pattern as the first received records. For example, the processor (120) can filter and exclude other received records that do not include core keywords such as “order number,” “delivery,” “refund,” and “exchange” for each of the multiple received records, and extract only the first received records that include the core keywords.

[0113] Additionally, the first reception record may include metadata of the message. For example, the metadata may include the original text of the message (e.g., text), sender information (e.g., platform name, shopping mall name), time of reception, and message type (e.g., notification talk, SMS, app push, etc.). Through this, the processor (120) can not only collect text from the user terminal but also obtain the context of the message to utilize in a subsequent step.

[0114] For example, the processor (120) can extract and exclude other received records based on metadata of multiple received records. For example, the metadata may include information such as an app package name corresponding to the message, a receiving channel ID, and a notification type. As an example, the package name of a message transmitted to a user terminal through the A shopping mall app may be identified as com.mall.a.shop, and the processor (120) may obtain the metadata together when collecting the first received record from the user terminal and select only the data that matches the predefined external channel package name.

[0115] As an example, if a user ordered sneakers from Shopping Mall A and returned a bag from Shopping Mall B the previous day, at step S510, messages such as “Order Completion Notice” transmitted to the user terminal via Shopping Mall A and “Return Receipt Notification” transmitted to the user terminal via Shopping Mall B may be accumulated on the user terminal. In this case, the processor (120) can extract and receive this history in bulk from the user terminal at the first cycle.

[0116] As an example, the processor (120) can extract only the first reception record from among a plurality of reception records based on a sender DB containing a unique sender number, sender name, or app signature corresponding to at least one first external channel. For example, shopping mall A may use a unique number such as 1588-xxxx, and shopping mall B may use 1899-yyyy. Accordingly, the electronic device (100) can manage and update a sender DB in the form of a whitelist, and consider only the messages matching the whitelist among all messages collected from the user terminal as the first reception record. Through this, other reception records received from banks, friends, and spam messages can be naturally excluded from the messages received by the user terminal. For example, a user may receive 50 messages during the day, 10 of which are shopping-related messages (e.g., notification messages regarding orders, returns, or exchanges) from at least one first external channel (e.g., shopping malls A, B, and C), and the remaining 40 may be other messages such as bank OTPs, text messages from friends, coffee coupons, or spam. The processor (120) may first exclude other messages from the 50 messages using a sender DB, and may exclude other messages once again based on regular expression pattern matching. By doing so, the processor (120) does not aggregate all messages received by the user terminal, but accurately extracts only shopping-related messages, thereby minimizing data noise, increasing classification accuracy, and contributing to significantly improving the quality of normalization, classification, and statistical dashboards in subsequent steps (e.g., S520 to S550).

[0117] The implementation method of step S510 can be realized in a structure in which an application installed in the user terminal collects message logs through notification access rights or message read rights, encrypts them, and transmits them to an electronic device (100). Through this, the user can aggregate all messages into the system without having to check individual platform apps one by one.

[0118] According to one embodiment, the processor (120) can obtain a post-processed reception record corresponding to the first reception record by applying a pre-processing algorithm corresponding to duplicate message removal and representation format normalization to the first reception record (S520).

[0119] For example, the processor (120) may apply a preprocessing algorithm to the acquired first reception history, and the preprocessing algorithm may be broadly divided into duplicate message removal and representation format normalization.

[0120] Duplicate message removal can be understood as a process of filtering out cases where the same notification is received repeatedly.

[0121] For example, if a “order completed” message arrives via app push and SMS respectively for the same order at Shopping Mall B, the two messages represent the same event. Therefore, the processor (120) determines whether there is a duplicate based on the order number, sending platform, and time stamp within the message, and can identify only one representative message as the first received record.

[0122] Expression format normalization can contribute to solving the problem where message composition methods vary across platforms.

[0123] For example, regarding a notification indicating that the delivery of an ordered item has started, Mall A may use the expression “Delivery started,” while Mall B may use the expression “Items have been handed over to the courier.” The processor (120) can identify all of these as the same “Delivery started” event by referring to a keyword mapping table.

[0124] To apply the preprocessing algorithm, the processor (120) may utilize a regular expression (e.g., Regex)-based pattern recognition or a machine learning-based text normalization model. Through this, the processor (120) can classify the message into a consistent data structure in subsequent steps, and the user can no longer be confused by different representations depending on the platform.

[0125] According to one embodiment, the processor (120) can classify the multiple messages included in the post-processing reception history into one of the multiple categories including orders, returns, and exchanges through a rule-based classification algorithm (S530).

[0126] For example, the processor (120) can apply a rule-based classification algorithm to the preprocessed messages. Through this algorithm, the processor (120) can perform the function of classifying messages included in the postprocessed reception history into higher categories such as orders, returns, and exchanges.

[0127] Here, the rule-based classification algorithm refers to a procedure in which an electronic device (100) analyzes the text and metadata of a message collected from a user terminal and automatically classifies the message into a specific category, such as an order, return, or exchange, according to a predefined rule set.

[0128] The rules of a rule-based classification algorithm may include at least one of the following: (i) keyword-based rules (e.g., whether core words such as “payment completed,” “order number,” “shipping started,” “refund completed,” etc. are included), (ii) regular expression-based pattern matching (e.g., order number format [A-Z0-9]{8}, invoice number format \d{10,12}), (iii) context-based rules (e.g., distinguishing between ‘shipping preparation’ and ‘shipping completed’ based on the context before and after a specific keyword), and (iv) metadata-based rules (e.g., classification based on sender ID, message type, receiving channel ID).

[0129] For example, when a message “The product has been shipped” is collected, the electronic device (100) can detect the keyword “shipping” included in the message through a rule-based classification algorithm and classify the message into a main category corresponding to “orders” and a subcategory corresponding to “shipping” by referring to a prior rule that this keyword corresponds to the ‘shipping started’ category.

[0130] For example, when a message “Return request received” is collected, the electronic device (100) can recognize the message as a ‘Return request completed’ event through a regular expression rule and classify it into a main category corresponding to ‘Return’ and a subcategory corresponding to ‘Return request’.

[0131] As such, rule-based classification algorithms are not limited to simple keyword searches but combine multi-layered rule sets to automatically classify messages into consistent categories. These algorithms can be applied in parallel with machine learning-based classification models, and the rule sets can be periodically expanded and modified by administrators or system operators to accommodate new message formats.

[0132] As an example, if the first message included in the post-processing received history contains keywords such as “order number,” “payment completed,” or “product being prepared,” the processor (120) can classify the first message into an order category.

[0133] As an example, if the second message included in the post-processing reception history contains keywords such as “return request completed” or “collection driver scheduled to visit,” the processor (120) can classify the second message into a return category.

[0134] As an example, if the third message included in the post-processing reception history contains keywords such as “exchange request” or “delivery of replacement product,” the processor (120) can classify the third message into an exchange category.

[0135] In this process, the processor (120) may utilize a rule dictionary. The rule dictionary includes keywords, patterns, and context rules defined in a dictionary, and when a new pattern is discovered, the processor (120) may add and expand various rules through a learning process.

[0136] In addition, the processor (120) does not stop at simply matching keywords, but also analyzes the contextual structure of the message and numerical information. For example, when a fourth message containing the keyword “Refund of 30,000 won has been deposited” is confirmed, the processor (120) can determine it as a “Refund Complete Event” by including the recognition of the amount, rather than classifying it only by the keyword “Refund”.

[0137] These classification results are displayed in the user interface in a later stage, allowing users to immediately understand the nature of each message as an event.

[0138] According to one embodiment, the processor (120) may provide the user terminal with a shopping information integration interface including classification results and update status by a plurality of categories in response to receiving an update request from the user terminal (S540).

[0139] For example, when the processor (120) receives an update request from the user terminal (210), it can provide a shopping information integration interface that reflects the latest classification results and update status.

[0140] For example, the processor (120) can check for update requests received when the user performs a 'refresh' directly in the app or when automatic synchronization occurs at a specific time each day (e.g., 9 a.m., 6 p.m.) set by the user on the user terminal.

[0141] For example, the processor (120) can identify the update request and immediately reflect the message classification results obtained so far and transmit them to the user terminal. The shopping information integration interface including the message classification results can be defined as the screen shown in FIG. 3.

[0142] Specifically, the processor (120) can display the platform logo and the current synchronization time on the first interface (310) and display date-specific message events reflected as colored dots on the calendar of the fourth interface (340). Additionally, it can support a filtering function so that the user can filter and view only the desired items through the category button of the fifth interface (350). When the user selects a specific date, detailed events such as information based on messages received on the user terminal on that date (e.g., “Sneaker order completed,” “Bag return received”) can be listed. The processor (120) can provide a shopping information integration interface that includes event information in a normalized form that has undergone preprocessing and classification, rather than simply displaying the original message text.

[0143] This allows users to intuitively check all shopping events from a single interface without the need to switch between multiple apps in a complex manner.

[0144] According to one embodiment, the processor (120) can provide a customized statistical dashboard including the number of included messages and the pattern of increase or decrease for each of the multiple categories at each second cycle, which is longer than the first cycle (S550).

[0145] For example, the processor (120) can analyze the cumulative number of messages by category and the pattern of increase and decrease at each second cycle (e.g., 7 days) which is longer than the first cycle, generate a customized statistical dashboard, and provide it to the user terminal (210).

[0146] For example, when the processor (120) compiles figures such as “orders: 12, returns: 3, exchanges: 1” over the past week, the processor (120) can generate a dashboard including a statistical interface that visualizes and displays the compiled figures in the form of a bar graph, a line graph, a pie chart, etc., and provide it to the user terminal.

[0147] For example, the processor (120) can also display the week-over-week growth rate by category (e.g., “orders +20%, returns -10%) on the dashboard so that the user can immediately understand the change in their shopping patterns.

[0148] For example, the processor (120) can perform step S550 in a structure that periodically queries a database to aggregate the latest message logs, processes them into a graphic form through a data visualization module, and transmits them to a user terminal.

[0149] In particular, the dashboard can not only provide simple statistics but also present predictive insights based on time series analysis results. For example, if a specific user has a high frequency of purchases from a specific brand every weekend, the processor (120) can add a notice to the dashboard stating “Increased likelihood of future weekend orders” and provide it to the user terminal.

[0150] Through this, the processor (120) can provide the user with macro-level vision beyond simple event notifications. That is, the user can analyze their consumption patterns and return rates over a specific period to formulate future purchasing strategies or make decisions to reduce unnecessary returns.

[0151] Additionally, the processor (120) applies an information extraction algorithm to multiple messages to check the metadata of each of the multiple target items corresponding to each of the multiple messages, acquires a second reception history transmitted from a second external channel to a user terminal via a messaging service at a third period shorter than the first period, and uses the second reception history and the metadata to check the delivery information of the multiple target items, updates the delivery information at a third period, and provides the updated delivery information to the user terminal at a third period.

[0152] For example, the processor (120) calculates item-unit structured information from each message of post-processed received history that has undergone pre-processing (e.g., operation S520). Here, the metadata may include objective field data such as order identifiers (e.g., order number, sub-order number), item identifiers (e.g., product name, model name, option), quantity, price, payment method summary, seller or store identifier, scheduled carrier or invoice number candidates (e.g., if included in text), and event timestamps (e.g., order date and time, scheduled shipment date, etc.).

[0153] As an example, when a user orders “one pair of sneakers 270mm and one black backpack” simultaneously through one external channel, one external channel (or a platform corresponding to the external channel) lists multiple items within one message, and the processor (120) can identify them by breaking them down into two item records using a separator (e.g., comma, bracket, line break) and a rule dictionary.

[0154] For example, the processor (120) can convert sentence-level free text into an item-level standard schema by sequentially performing morphological analysis-based noun and numeric candidate extraction, regular expression pattern recognition (e.g., order number, size, color), dictionary matching (e.g., a dictionary defined in advance regarding brand, category, and courier name), and entity-slot matching procedures.

[0155] At this time, the processor (120) can enhance transparency by storing backtracking keys (e.g., source offset, message ID) with the original message source together, thereby enabling transparent audit trail.

[0156] For example, the second external channel may include a delivery or logistics platform (e.g., a courier server, a last-mile API gateway, etc.), and the processor (120) may acquire a delivery status event through a user terminal (210) or a relay module every third cycle (e.g., 2 hours).

[0157] As an example, in the process where the delivery status of an item changes at intervals of about 2 hours, such as “collection completed” at 10:00 AM, “arrival at terminal” at noon, and “delivery departure” at 2:00 PM, the processor (120) can obtain real-time events of the delivery status by using a polling method that performs REST queries at a set interval in accordance with the third cycle, or by using a subscription method through webhooks and push notifications.

[0158] For example, it is desirable for the processor (120) to track and update delivery information based on a delivery tracking key (e.g., invoice number and / or courier code) mapping table, rate, zone, time zone correction logic, delay queue retry policy in case of network failure (e.g., exponential backoff, maximum retry count setting), and a cache layer for responding to rate limits. This allows the processor (120) to achieve near-real-time delivery event synchronization without excessive traffic increase.

[0159] For example, the processor (120) can associate shipping events with each item record. For example, the processor (120) primarily performs the association based on tracking number and courier code matching, and if the tracking number is missing in the message, it can assist the association with an order number-tracking number cross table and multi-key proximity matching of the dispatch time / seller code / recipient zip code. Subsequently, the processor (120) can project the event onto a standardized shipping state machine (e.g., 'Dispatch Order' → 'Collection Complete' → 'In Transit' → 'Delivery Departure' → 'Delivery Complete') to calculate the current state, the time of the most recent transition, and the next expected state. If a data conflict (e.g., different status reports from two couriers) is detected, the processor (120) applies a reliability priority (official API > scraping > user submission) and, if there is a temporal discontinuity, applies an interpolation rule (e.g., normalization to the nearest parent state) to maintain a consistent “shipping information object.” This operation is repeated every third cycle, ensuring that delivery status updates are provided without delay from the user's perspective.

[0160] For example, the processor (120) can configure item-specific delivery information objects into a session-independent feed and deliver them to the user terminal (210).

[0161] As one example, the processor (120) can provide a highlight card to the user terminal with a push notification when a predefined threshold event, such as 'delivery started' or 'delivery completed', occurs, even if the user does not open the app.

[0162] When a user selects the “delivery” filter in the fifth interface (350) provided by the user terminal, the processor (120) can sort and provide the current delivery stage, last scan point, and estimated arrival time of all items within the corresponding period to the user terminal.

[0163] For example, the processor (120) can provide delivery information to the user terminal based on incremental synchronization for transmission lightweighting (e.g., only changes since the last synchronization time are transmitted), principles for minimizing personal information (e.g., masking part of the recipient's detailed address), event deduplication for preventing notification noise, and a quiet time period (Do-Not-Disturb) policy.

[0164] This allows the user to reliably receive reliable delivery status of the third cycle (e.g., 2-hour cycle).

[0166] Additionally, the processor (120) may classify the first message into either of two time-series categories, delivery in progress and delivery completed, based on the result of applying a rule-based classification algorithm to the first message included in the category of delivery information and order. Furthermore, the processor (120) may classify the second message into either of three time-series categories, return request, collection completed and refund completed, based on the result of applying a rule-based classification algorithm to the second message included in the category of delivery information and return. Moreover, the processor (120) may classify the third message into either of three time-series categories, exchange request, collection completed and exchange completed, based on the result of applying a rule-based classification algorithm to the third message included in the category of delivery information and exchange.

[0167] For example, the processor (120) can perform time-series stage reclassification by referring to a delivery information object (e.g., information determined in the operation limited to claim 2) for messages having delivery-related events among messages primarily classified into order categories.

[0168] As an example, the message “Dispatched” is classified into the 'Order' category upon initial receipt, but if a higher status such as 'Collection Completed / In Transit / Departure' is confirmed in the delivery information object, the message can be reclassified to 'In Transit' (or a subcategory is determined).

[0169] Conversely, if a 'Delivery Complete' event timestamp exists in the delivery information object, the message can be finally attributed to the 'Delivery Complete' category.

[0170] For example, it is preferable for the processor (120) to perform this operation based on a message-item-invoice trilateral linkage key, a priority / end state table of the state machine, and transaction locking / version management to prevent concurrency conflicts of multiple orders. This reclassification is reflected in alignment with the user calendar (e.g., the fourth interface (340)) so that the date-specific color dots (shipping=●, delivery completed=◆, etc.) can be automatically updated.

[0171] For example, the processor (120) can project messages belonging to the return category onto the reverse logistics event flow.

[0172] As an example, if a user requests a return on April 3, a “return received” message on April 3, a “collection completed” message after a technician visit on April 5, and a “refund completed” message due to payment cancellation on April 7 may be received on the user terminal. The processor (120) can attribute each message to the correct one of three subcategories using the return request ID (e.g., order number and return order), the return invoice number and / or courier code, and the refund method / amount / processing time as key keys.

[0173] For example, since a return may require a seller approval process to precede it, unlike forward delivery, the processor (120) can juxtapose a reverse state machine (e.g., request → collection → inspection → refund) with the delivery information object and, if the inspection stage is not specified in the message, apply a seller system delay correction rule (e.g., N days elapsed after collection completion + visualization of 'inspection in progress' when refund completion is not reached) to prevent a blank space from appearing in the user interface.

[0174] For example, since the exchange process is a dual flow combining a return (or, reverse logistics) and a forward redelivery, the processor (120) can pair map a return invoice (e.g., an invoice for returning an existing product) and a redelivery invoice (e.g., an invoice for sending a replacement product).

[0175] As an example, when a user requests a size exchange, the corresponding event and message are attributed to 'Exchange Request'; when a courier's retrieval scan is generated, the corresponding event and message are attributed to 'Collection Complete'; and when a seller ships a replacement product and 'Delivery Departed / Delivery Complete' is stamped on the new invoice, the event and corresponding message can be attributed to 'Exchange Complete'.

[0176] For example, the processor (120) can minimize misjudgment by using the 'delivery completed' event of the reshipment invoice as the final basis for determining the exchange completion, rather than a simple character keyword.

[0177] In addition, when multiple items are mixed in the same order, the exchange steps may be staggered by item, so the processor (120) can maintain a subdivided status row at the item level to clearly indicate to the user that partial exchange is complete.

[0178] In the example described above, the first external channels correspond to a shopping platform associated with e-commerce and supporting item purchase services for users, and the second external channels correspond to a delivery platform associated with delivery and logistics and supporting item delivery services for users.

[0180] Meanwhile, the first period defined in the present disclosure refers to the period during which the electronic device (100) collects messages (e.g., messages indicating order completion, shipping start, return acceptance, etc.) received from the first external channel (e.g., shopping platform) at the user terminal, and the first period may correspond to one day.

[0181] There are often cases where the same shopping platform sends the same message multiple times during the day (e.g., duplicate messages sent in the morning / afternoon). In such situations, the electronic device (100) collects the reception history at each first cycle corresponding to a day, thereby consolidating the daily logs, so that duplicate messages can be effectively removed and efficient processing is possible during the normalization and preprocessing stages.

[0182] In addition, users generally check their shopping records on a daily basis, such as checking their order history on their way to work in the morning and checking the delivery status after work. Therefore, by organizing and collecting shopping-related received records at each first cycle corresponding to a daily period, it is possible to achieve the effect of aligning the user's awareness cycle with the system's provision cycle.

[0183] Furthermore, if messages are continuously collected in minutes and hours, there is a risk that communication resources or storage resources of the electronic device (100) and user terminal will be wasted. Collecting reception records at each first cycle corresponding to one day is effective in maintaining system efficiency while ensuring a necessary and sufficient frequency.

[0184] Meanwhile, the second period defined in the present disclosure refers to a period for statistically analyzing the number of messages by category and the pattern of increase or decrease to generate a customized dashboard and provide it to a user terminal, and the second period may correspond to 7 days.

[0185] Users' shopping activities often fluctuate on a weekly basis. For example, most users tend to concentrate their shopping activities on weekends. Judging from this, an algorithm that updates user shopping statistics every second cycle, corresponding to 7 days, can significantly contribute to presenting users with more stable and meaningful trends than daily or monthly updates.

[0186] In addition, daily statistics can be visually unstable due to large fluctuations and a lot of noise, and monthly statistics have difficulty reflecting practically meaningful weekly trends. An algorithm that updates shopping-related statistics every second cycle, corresponding to a 7-day weekly period, brings about a data smoothing effect, making it easy for users to intuitively grasp trends of increase or decrease.

[0187] Furthermore, while existing platforms only provide daily order status, the present invention provides a comprehensive overview of the increase and decrease patterns and distribution of users' shopping behavior by category at every second cycle corresponding to 7 days, thereby providing a differentiated value known as a “weekly report on my shopping life.”

[0188] Meanwhile, the third cycle defined in the present disclosure refers to a cycle for obtaining delivery information updates and providing them to a user terminal, and the third cycle may correspond to 2 hours.

[0189] In most courier logistics systems for transporting items, new events related to transportation (e.g., collection, movement, start of delivery, etc.) generally occur every 1 to 2 hours. Therefore, the electronic device (100) allows the user to check the delivery status in real-time close to the actual state without using excessive resources through updates every 3rd cycle corresponding to 2 hours.

[0190] In addition, users who have purchased items are generally sensitive to information regarding the delivery of the items, and in particular, users feel a great deal of anxiety if the delivery is delayed. The electronic device (100) can check for updates regarding the delivery of automatic items every third cycle corresponding to 2 hours and provide them to the user terminal in real time, thereby enabling the user to check the latest delivery status whenever they open the app.

[0191] Furthermore, existing shopping mall apps often update delivery status only once or twice a day. On the other hand, the electronic device (100) according to the present invention provides a superior experience compared to existing platforms by simultaneously ensuring real-time performance and stability through delivery information updates at three cycles corresponding to 2-hour intervals.

[0193] Additionally, the processor (120) may, in response to receiving a request for information sharing with a user terminal from an external terminal, request approval from the user terminal, and in response to receiving an approval input from the user terminal, provide the delivery information to the external terminal at three cycles, and update and provide external user delivery information corresponding to the external terminal at three cycles to the user terminal.

[0194] For example, an external terminal refers to a third-party terminal such as a family member, a delivery agent, or a company accounting team, and the electronic device (100) can receive a sharing request token and an external terminal identifier (e.g., terminal ID, account ID, public key fingerprint) from the said external terminal (or, app or web of the external terminal).

[0195] Based on this, the processor (120) can provide a permission request UI to the user terminal (210). The UI presents a sharing scope (e.g., specific order / entire delivery information), a sharing validity period (e.g., 7 days), and a visibility level (e.g., whether to mask the address) as selectable options, and if the user explicitly presses the approval button, that fact can be stored as a signed approval record (e.g., user account, time, scope, expiration date, external terminal identifier). This operation ensures the minimization of personal information processing and transparency, and also provides flows for approval denial, approval deferral, and approval cancellation, allowing the user to control the sharing at any time.

[0196] For example, the processor (120) generates a delivery information feed for sharing within the range defined in the approval record and shares and transmits the delivery information to an external terminal every third cycle (e.g., 2 hours).

[0197] As an example, when a user approves the sharing of ‘3 orders scheduled to arrive this weekend’ to the parent’s terminal, the processor (120) can provide the external terminal corresponding to the parent’s terminal with at least the essential information for the 3 orders, such as the item name, store name, current delivery stage, estimated arrival time, and tracking number.

[0198] The processor (120) can perform this operation based on range filters (e.g., order ID, period, category), de-identification / masking rules (e.g., masking part of address and / or contact), transport security (e.g., session token, TLS), and a mechanism for reflecting immediate approval expiration / revocation. Additionally, a multi-tenancy isolation structure (e.g., separation of tenant / user key space) may be applied to handle cases where multiple users approve sharing on the same external terminal.

[0199] For example, external user shipping information may refer to shipping information (e.g., the status of external users' orders, returns, and exchanges) that an external terminal owner has agreed to share and registered through their terminal within this system.

[0200] That is, the “external user delivery information” defined in this disclosure refers to delivery-related information collected and managed by an electronic device from an external terminal corresponding to a third party (e.g., family member, colleague, customer, etc.) who is not the owner of the user terminal, when said external terminal has approved the sharing of its shopping activity history.

[0201] Specifically, external user delivery information can be generated by the electronic device (100) of the present invention using the same logic as processing user delivery information. That is, for a message received by an external terminal, the electronic device (100) can perform the same preprocessing (e.g., deduplication, format normalization), the same classification (e.g., application of a rule-based classification algorithm), and the same delivery tracking (e.g., matching of invoice numbers and logistics events through linkage with at least one second external channel) to form a delivery information object corresponding to an external user.

[0202] For example, if a family member receives “Laptop Order Complete” and “Shipping Departed” messages through their account and agrees to share them, the electronic device collects the messages, generates a post-processing receipt history following the same procedure as for general user messages, determines the shipping stage by applying a rule-based classification algorithm, and obtains tracking number-based shipping status updates from an external shipping platform. As a result, the generated external user shipping information has the same structure as the user shipping information and can be provided on the user terminal along with a distinguishable label (e.g., “Family-Hong Gil-dong”).

[0203] Therefore, external user delivery information is not merely transmitted as the original shared message, but is provided as structured information including results normalized, classified, and analyzed by the electronic device of the present invention. Through this, the user terminal can check the external user delivery status within the same interface as its own delivery status, and system consistency is maintained.

[0204] This operation operates in a mutual sharing scenario, for example, when a spouse account registers two of its own orders as shared, the electronic device (100) can synchronize and update the information to the latest state every third cycle and provide it to the user terminal (210). At this time, the items displayed on the user terminal (210) consist of an external user identification label (e.g., “Family-Spouse”), a summary of the external user’s delivery stage, and delivery status in item units when details are expanded, so that the source and scope can be clearly distinguished.

[0205] It is desirable for the processor (120) to perform this operation based on mutuality verification (e.g., existence of approval from the external user side), the shared intersection principle in case of range conflict (e.g., exposure of only items allowed by both sides), providing a previous snapshot in case of update failure, and operating a resynchronization queue. This allows the sharing of shipping information between the user and the external user to maintain safe, transparent, and reversible characteristics.

[0207] According to one embodiment, the shopping information integration provision method further comprises: the processor identifying an order-completed item for which the user has completed an order based on a first message included in the order category among the plurality of messages included in the post-processing reception history; the processor identifying a recurring purchase item purchased more than a predetermined number of times based on the order-completed item; the processor assigning a recurring purchase prediction tag to the recurring purchase item when the recurring purchase item is identified; and the processor providing a list of recurring purchase items including the recurring purchase item to which the recurring purchase prediction tag has been assigned to a separate widget area included in the shopping information integration interface.

[0208] For example, the processor (120) can recognize a pattern in which a user regularly purchases bottled water, detergent, or baby diapers of the same brand every month. When repeated purchases are confirmed more than a certain number of times, a “Regular Purchase Expected” indicator is automatically assigned to the item, and it can be viewed at a glance on a dedicated widget on the user's terminal screen. Based on this, the user can immediately connect to a regular order service or manage purchase timing without missing it.

[0210] According to one embodiment, the shopping information integration provision method further comprises: an operation in which the processor predicts the possibility of delivery delay for each of the second received records by combining real-time traffic information and weather information obtained from an external server with the delivery information; and an operation in which, based on the possibility of delivery delay, if the processor confirms a target message among the second received records where the probability of the delivery time being delayed by more than a predetermined time corresponds to a probability greater than a predetermined probability, the processor provides an “expected delivery delay notification” for a delivery delay item corresponding to the target message to the user terminal and displays a corrected expected arrival time.

[0211] For example, the processor (120) checks the delivery status of the courier company, checks the forecast of heavy rain through the weather agency API, and reflects real-time traffic congestion data in a specific section. In response to confirming that the probability of the item ordered by the user being delayed by more than 6 hours from the original date corresponds to a predetermined probability (e.g., 60%) or higher, it displays a notification message to the user terminal such as “Delivery delayed due to heavy rain, estimated arrival: 4 PM tomorrow.” Through this, the user can receive realistic arrival prediction information instead of simply the status of ‘delivery in progress’ and use it for schedule management.

[0213] According to one embodiment, the shopping information integration provision method further includes: an operation in which the processor queries an external database for validity period data by item category based on specific item information included in a specific order message of the post-processing received history; an operation in which the processor identifies a risk item among the ordered items ordered by the user, based on the validity period data, for which the expiration date of the corresponding validity period is within a predetermined threshold period; and an operation in which the processor provides a “consumption date imminent” or “quick use recommendation” message regarding the risk item to the user terminal.

[0214] For example, the processor (120) can confirm that the user has purchased milk based on the metadata of each item purchased by the user, and can extract information such as “1L milk, manufacturing date 9 / 15” as metadata for the milk order. Subsequently, the processor (120) can extract expiration date data corresponding to the milk from an external database to confirm that the recommended consumption period for the milk is 10 days. If it is confirmed that the expiration date of the milk is within a predetermined threshold period from the current date, the processor (120) can provide a notification to the user terminal stating, “The consumption period of the milk you purchased is 2 days away. Please consume the milk before it spoils.” Through this, the user can consume or dispose of forgotten food or medicine in a timely manner.

[0216] According to one embodiment, the shopping information integration provision method further includes the operation of the processor normalizing delivery address data included in the post-processing received history to automatically cluster delivery address patterns for each user, and the operation of the processor detecting a delivery delay event that occurs repeatedly at a specific delivery address based on the clustering result, labeling the target delivery address corresponding to the detected delivery delay event as a “delivery vulnerable location,” and providing the labeling result to the user terminal.

[0217] For example, the processor (120) can normalize the delivery address data included in the post-processing received history to confirm that the delivery addresses frequently used by the user include 'home', 'company', 'family address', etc. If delivery delays or loss events occur repeatedly only at a specific address (e.g., company), the processor (120) can label the address as a “delivery vulnerable location.” Subsequently, the processor (120) provides a notification to the user terminal stating, “There have been 3 consecutive delivery delays at the company address recently. Please consider an alternative delivery address,” thereby enabling the user to recognize the delivery risk and respond accordingly.

[0219] According to one embodiment, the shopping information integration provision method further includes the following operations: the processor confirming an order completed item that the user has ordered through the first message included in the order category among the messages included in the post-processing reception history; the processor confirming an item representative image of the order completed item by matching the metadata of the order completed item with an external image database; and the processor displaying the item representative image in a thumbnail form next to the first message in the shopping information integration interface provided to the user terminal.

[0220] For example, the processor (120) can extract the string “sneaker brand A, black, size 260” from a message associated with an item ordered by the user. Subsequently, the processor (120) can obtain a representative image of an item identical or similar to the completed order item through a shopping platform image server or an open API, and display the obtained image as a small thumbnail next to the corresponding message in the shopping information integration interface. Through this, the user can intuitively understand the shopping history by viewing the actual product image instead of a simple text history, and can manage it without confusion, especially when purchasing multiple items at the same time.

[0222] The above description is merely an illustrative explanation of the technical concept of the present invention, and those skilled in the art to which the present invention pertains will be able to make various modifications and variations within the scope of the essential characteristics of the present invention.

[0223] Accordingly, the embodiments disclosed in this invention are intended to illustrate, not limit, the technical concept of the invention, and the scope of the technical concept of the invention is not limited by these embodiments. The scope of protection of this invention shall be interpreted by the claims below, and all technical concepts within an equivalent scope shall be interpreted as being included within the scope of rights of this invention.

Claims

Claim 1 A method for providing integrated shopping information, wherein an electronic device including a processor collects and manages shopping history transmitted to a user by a plurality of shopping channels and integrates and provides the user's shopping history through a single integrated platform, wherein the processor performs the operation of obtaining a first received history related to the user's shopping activity from the user terminal at a first periodic interval, transmitted from a first external channel to the user terminal via a messaging service using a communication interface; the processor performs the operation of obtaining a post-processed received history corresponding to the first received history by applying a pre-processing algorithm corresponding to duplicate message removal and expression format normalization to the first received history; the processor performs the operation of classifying a plurality of messages included in the post-processed received history into one of a plurality of categories including orders, returns, and exchanges, respectively, through a rule-based classification algorithm for the plurality of messages; and the processor performs the operation of providing a shopping information integration interface to the user terminal, which includes the classification results and update status by the plurality of categories, in response to receiving an update request from the user terminal. and the processor provides a customized statistical dashboard including the number of included messages and the increase / decrease pattern of each of the plurality of categories at every second period longer than the first period; and the shopping information integration providing method comprises: the processor applying an information extraction algorithm to the plurality of messages to verify the metadata of each of the plurality of target items corresponding to each of the plurality of messages; and the processor acquiring a second reception history transmitted to the user terminal from second external channels through the messaging service at every third period shorter than the first period.The above processor further comprises the operation of verifying delivery information of the plurality of target items using the second reception history and the metadata and updating the delivery information every third period; and the operation of the processor providing the delivery information to the user terminal every third period; and the shopping information integrated provision method further comprises the operation of the processor classifying the first message into either of two time-series categories, "in transit" and "delivery completed," based on the result of applying the rule-based classification algorithm to the first message included in the delivery information and the order category; the operation of the processor classifying the second message into either of three time-series categories, "return request," "collection completed," and "refund completed," based on the result of applying the rule-based classification algorithm to the second message included in the delivery information and the return category; and the operation of the processor classifying the third message into either of three time-series categories, "exchange request," "collection completed," and "exchange completed," based on the result of applying the rule-based classification algorithm to the third message included in the delivery information and the exchange category. The method further includes, wherein the first external channels correspond to a shopping platform associated with e-commerce and supporting item purchase services for the user, and the second external channels correspond to a delivery platform associated with delivery and logistics and supporting item delivery services for the user, wherein the first cycle corresponds to 1 day, the second cycle corresponds to 7 days, and the third cycle corresponds to 2 hours, and the shopping information integration provision method comprises the operation of the processor requesting approval from the user terminal in response to receiving a request for information sharing with the user terminal from an external terminal;The above processor further comprises the operation of providing the delivery information together with the external terminal every third cycle in response to receiving an approval input from the user terminal; and the operation of the processor updating external user delivery information corresponding to the external terminal every third cycle and providing it to the user terminal; and the shopping information integration provision method further comprises the operation of the processor filtering and excluding other received records that are not received through the first external channel among a plurality of received records received by the user terminal based on a regular expression pattern matching and natural language processing-based classification model; and the operation of the processor confirming only messages containing a pre-set core keyword as the first received record; and the shopping information integration provision method further comprises the operation of the processor confirming the order completed item for which the user has completed the order based on the first message included in the order category among the plurality of messages included in the post-processing received record; and the operation of the processor confirming the recurring purchase item purchased more than a predetermined number of times based on the order completed item. and, when the processor confirms the recurring purchase item, the operation of assigning a regular purchase prediction tag to the recurring purchase item; and, when the processor provides a list of regular purchase items including the recurring purchase item to which the regular purchase prediction tag has been assigned, to a separate widget area included in the shopping information integration interface; further comprising, the shopping information integration providing method, the operation of, when the processor combines real-time traffic information and weather information obtained from an external server with the delivery information to predict the possibility of delivery delay for each of the second received records;A shopping information integrated provision method further comprising: an operation in which, if the processor confirms a target message among the second received records where the probability of the delivery time being delayed by more than a predetermined time is greater than or equal to a predetermined probability, based on the delivery delay possibility, the processor provides an "expected delivery delay notification" for a delivery delay item corresponding to the target message to the user terminal and displays a corrected estimated arrival time. Claim 2 In claim 1, the shopping information integrated provision method further comprises: an operation in which the processor queries validity period data by item category from an external database based on specific item information included in a specific order message of the post-processing received history; and an operation in which the processor identifies a risk item among the ordered items ordered by the user, based on the validity period data, wherein the expiration date of the corresponding validity period is within a predetermined threshold period; and an operation in which the processor provides a "consumption date imminent" or "quick use recommendation" message regarding the risk item to the user terminal; and the shopping information integrated provision method further comprises: an operation in which the processor normalizes delivery address data included in the post-processing received history to automatically cluster delivery address patterns by user; and an operation in which the processor detects a delivery delay event occurring repeatedly at a specific delivery address based on the clustering result, labels the target delivery address corresponding to the detected delivery delay event as a "delivery vulnerable location," and provides the labeling result to the user terminal. The shopping information integration provision method further comprises: an operation in which the processor identifies an order completed item that the user has ordered through the first message included in the order category among the messages included in the post-processing reception history; an operation in which the processor identifies an item representative image of the order completed item by matching the metadata of the order completed item with an external image database; and an operation in which the processor displays the item representative image in a thumbnail form next to the first message in the shopping information integration interface provided to the user terminal. Claim 3 delete Claim 4 delete Claim 5 delete

Images