System and method for order management
A browser extension for order management in live streaming and e-commerce environments addresses inefficiencies by automating order confirmation and inventory management, enhancing user experience through machine learning-driven order analysis.
Patent Information
- Application Number
- JP2024090992
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-04-08
- Filing Date
- 2024-06-04
- Publication Date
- 2025-10-21
- Estimated Expiration
- 2044-06-04
AI Technical Summary
Online retail providers face challenges in improving the shopping experience for buyers and the selling experience for sellers through efficient order management systems, particularly in live streaming and e-commerce environments.
A browser extension that integrates with user terminals to facilitate order management by detecting user interactions on sales sites, analyzing purchase comments, and automating order confirmation processes using machine learning models to determine item selection and inventory availability.
Enhances order management efficiency by automatically extracting and confirming orders, improving user experience and reducing manual errors in live streaming and e-commerce transactions.
Smart Images

Figure 2025159679000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to order management, and more particularly to order management using browser extensions. [Background technology]
[0002] Online sales and shopping, including social media and e-commerce sites, have become a part of everyday life. A variety of platforms and providers offer online sales and order management services, and competition is fierce. It is important for providers to provide the services users want.
[0003] Taiwan Patent Application Publication No. 108111269 discloses a system for order management. Summary of the Invention
[0004] A method for order management according to one embodiment of the present invention is executed by one or more computers and includes the steps of displaying an object associated with a post on a website supported by a first server on a user terminal of a first user, detecting that the first user has selected the object, and transmitting a purchase comment from a second user associated with the post to a second server, the first server being different from the second server.
[0005] A terminal according to one embodiment of the present invention is a terminal for order management that includes one or more processors, wherein the one or more computer processors execute a browser plug-in to display an object associated with a post on a website supported by a first server on a user terminal of a first user, detect that the first user has selected the object, and send a purchase comment from a second user associated with the post to a second server, the first server being different from the second server.
[0006] A non-transitory computer-readable medium including a plug-in program that causes one or more computers to perform the following steps: displaying an object associated with a post on a website supported by a first server on a user terminal of a first user; detecting that the first user has selected the object; and transmitting a purchase comment from a second user associated with the post to a second server, the first server being different from the second server. [Brief explanation of the drawings]
[0007] [Figure 1] 1 is a schematic diagram illustrating the configuration of a live streaming system 1 according to some embodiments of the present invention. [Figure 2] 2 is a block diagram illustrating the functionality and configuration of user terminal 30 of FIG. 1 in accordance with some embodiments of the present invention. [Figure 3] 2 is a block diagram illustrating the functionality and configuration of the server of FIG. 1 in accordance with some embodiments of the present invention. [Figure 4] 4 is a table illustrating an exemplary data structure of the stream DB 310 of FIG. 3. [Figure 5] 4 is a table illustrating an exemplary data structure of the user DB 312 of FIG. 3. [Figure 6] 4 is a table illustrating an example data structure of the gift DB 314 of FIG. 3. [Figure 7] 1 is a table showing an exemplary data structure of an item DB 250. [Figure 8] 10 is a table showing an exemplary data structure of an order DB 350. [Figure 9] 10 is a table illustrating an exemplary data structure of an inventory DB 352. [Figure 10] 1 is a flowchart illustrating an exemplary flow according to some embodiments of the present invention. [Figure 11] 1 is an example of a social media page from an administrator's perspective in accordance with some embodiments of the present invention. [Figure 12]1 is an example of a social media page from an administrator's perspective in accordance with some embodiments of the present invention. [Figure 13] 1 is an example of a social media page from an administrator's perspective in accordance with some embodiments of the present invention. [Figure 14] 1 is an example of a social media page from an administrator's perspective in accordance with some embodiments of the present invention. [Figure 15] 1 is an example of a social media page from a buyer's perspective according to some embodiments of the present invention. [Figure 16] 1 is an example of a social media page from a buyer's perspective according to some embodiments of the present invention. [Figure 17] 1 is an example of a social media page from a buyer's perspective according to some embodiments of the present invention. [Figure 18] 1 is an example of a social media page from a buyer's perspective according to some embodiments of the present invention. [Figure 19] 1 is an example of a social media page from a buyer's perspective according to some embodiments of the present invention. [Figure 20] 1 is a block diagram showing an example of a hardware configuration of an information processing device according to some embodiments of the present invention. [Figure 21] 1 is an example of a social media page according to some embodiments of the present invention. [Figure 22] 10 is a flowchart illustrating a process for generating data from comments at a user terminal using a browser plug-in according to some embodiments of the present invention. [Figure 23] 7 is a table illustrating an exemplary data structure of an extracted order list 702. [Figure 24] 7 is a table illustrating an example data structure of an extracted product list 704. DETAILED DESCRIPTION OF THE INVENTION
[0008] Hereinafter, identical or similar components, parts, steps, or signals shown in each drawing will be denoted by the same reference numerals in all drawings, and redundant explanations will be omitted as appropriate. In addition, some parts that are not important in the explanation of each drawing will be omitted.
[0009] Online retail providers (or order management service providers) want to improve the shopping experience for buyers (e.g., automatic order confirmation) and the selling experience for sellers (e.g., order management).
[0010] FIG. 1 is a schematic diagram illustrating the configuration of a live streaming system 1 according to some embodiments of the present invention. The live streaming system 1 provides a live streaming service for streaming broadcasters (also referred to as live broadcasters, anchors, streamers, or live broadcasters) LV and viewers (also referred to as audiences) AU (AU1, AU2, ...) to interact or communicate in real time. As shown in FIG. 1, the live streaming system 1 includes a server 10, a user terminal 20, and a user terminal 30 (30a, 30b, ...). In some embodiments, the broadcasters and viewers may be collectively referred to as users. The server 10 may include one or more information processing devices connected to a network NW. The user terminals 20 and 30 may be, for example, mobile terminal devices such as smartphones, tablets, laptops, recorders, portable game consoles, and wearable devices, or stationary devices such as desktop PCs. The server 10, the user terminals 20, and the user terminals 30 are connected to each other so as to be able to communicate with each other via various wired or wireless networks NW.
[0011] The live streaming system 1 includes a broadcaster LV, a viewer AU, and an administrator (or app provider, not shown) who manages the server 10. The broadcaster LV records content on his / her user terminal 20 and directly or indirectly uploads it to the server 10, thereby broadcasting the content in real time. Examples of the content include the broadcaster's own singing, talking, performance, gameplay, or any other content. The administrator provides a platform for live broadcasting the content on the server 10 and mediates or manages real-time interactions between the broadcaster LV and the viewer AU. The viewer AU accesses the platform with his / her user terminal 30, selects and watches desired content, and performs operations such as commenting, cheering, and sending gifts via the user terminal 30 during the live broadcast of the selected content. The broadcaster LV, who is broadcasting the content, may respond to the comments, cheers, or gifts. The response is transmitted to the viewer AU via video and / or audio, establishing two-way communication.
[0012] The term "live streaming" refers to a data transmission mode that enables content recorded by a user terminal 20 of the distributor LV to be played back and viewed on a user terminal 30 of the viewer AU in substantially real time, or to live broadcasting realized by such a transmission mode. The live distribution may be realized using existing live distribution technologies such as HTTP live streaming, CMAF (Common Media Application Format), WebRTC (Web Real-Time Communications), RTMP (Real-Time Messaging Protocol), etc. Live distribution includes a transmission mode that allows the viewer AU to view content simultaneously with a predetermined delay as the content is recorded by the distributor LV. The delay may be long enough to allow interaction between the distributor LV and the viewer AU. Note that live distribution is distinguished from so-called on-demand distribution, in which all recorded data of the content is stored on a server and then provided to users from the server upon their request.
[0013] The term "video data" as used herein refers to data including image data (also referred to as video data) generated using the imaging function of the user terminal 20 or 30 and audio data generated using the audio input function of the user terminal 20 or 30. The video data is played on the user terminal 20 or 30 so that the user can view the content. In some embodiments, it is assumed that processing to change the format, size, or data specifications of the video data, such as compression, decompression, encoding, decoding, or transcoding, is performed on the video data between the generation of the video data on the distributor's user terminal and the playback of the video data on the viewer's user terminal. However, since the content (e.g., video and audio) represented by the video data remains substantially unchanged before and after such processing, the video data after such processing is referred to herein as being identical to the video data before such processing. In other words, when video data is generated on the distributor's user terminal and then played on the viewer's user terminal via the server 10, the video data generated on the distributor's user terminal, the video data passing through the server 10, and the video data received and played on the viewer's user terminal are all the same video data.
[0014] In the example shown in Fig. 1, the distributor LV provides live streaming data. The user terminal 20 of the distributor LV records video and audio of the distributor LV to generate the streaming data, and the generated data is transmitted to the server 10 via the network NW. At the same time, the user terminal 20 displays the recorded video VD of the distributor LV on the display of the user terminal 20, allowing the user to check the live streaming content currently being distributed by the distributor LV.
[0015] The user terminals 30a and 30b of the viewers AU1 and AU2 who have requested to view the live streaming of the broadcaster LV on the platform receive video data related to the live streaming (hereinafter, may be referred to as "live streaming video data") via the network NW, play the received video data, display the videos VD1 and VD2 on the display, and output audio from the speakers. The videos VD1 and VD2 displayed on the user terminals 30a and 30b are substantially the same as the video VD captured by the user terminal 20 of the broadcaster LV, and the audio output from the user terminals 30a and 30b is substantially the same as the audio recorded by the user terminal 20 of the broadcaster LV.
[0016] The recording of video and audio on the user terminal 20 of the distributor LV and the playback of video data on the user terminals 30a and 30b of the viewers AU1 and AU2 are performed substantially simultaneously. When the viewer AU1 inputs a comment about the content provided by the distributor LV to the user terminal 30a, the server 10 displays the comment in real time on the user terminal 20 of the distributor LV and also displays the comment on the user terminals 30a and 30b of the viewers AU1 and AU2, respectively. When the distributor LV reads the comment and engages in a conversation corresponding to the comment, the video and audio of the conversation are displayed on the user terminals 30a and 30b of the viewers AU1 and AU2, respectively. This interactive behavior is recognized as a conversation between the distributor LV and the viewer AU1. This allows the live streaming system 1 to realize live streaming that enables two-way communication rather than one-way communication.
[0017] FIG. 2 is a block diagram illustrating the functions and configuration of the user terminal 30 of FIG. 1 according to some embodiments of the present invention. The user terminal 20 has the same or similar functions and configuration as the user terminal 30. Each block in FIG. 2 and the subsequent block diagrams may be realized by hardware elements such as a computer CPU or a mechanical device, or by software elements such as a computer program. The functional blocks may be realized by cooperative operations between these elements. Therefore, those skilled in the art will understand that these functional blocks may be realized in various forms using a combination of hardware and software.
[0018] The distributor LV and the viewer AU may download a live streaming application program (hereinafter referred to as a live streaming application) from a download site via the network NW and install it on the user terminals 20 and 30. Alternatively, the live streaming application may be pre-installed on the user terminals 20 and 30. When the live streaming application is executed on the user terminals 20 and 30, the user terminals 20 and 30 communicate with the server 10 via the network NW and implement or execute various functions. Hereinafter, functions implemented by the user terminals 20 and 30 (processors such as CPUs) on which the live streaming application is executed are described as functions of the user terminals 20 and 30. These functions are actually realized by the live streaming application on the user terminals 20 and 30. In some embodiments, these functions may be written in a programming language such as HTML (HyperText Markup Language), transmitted from the server 10 to a web browser on the user terminals 20 and 30 via the network NW, and implemented by a computer program executed by the web browser.
[0019] The user terminal 30 includes a distribution unit 100 and a viewing unit 200. The distribution unit 100 generates video data in which video and audio of the user (or user side) are recorded, and provides the video data to the server 10. The viewing unit 200 receives video data from the server 10 and plays the video data. The user starts the distribution unit 100 when live streaming, and starts the viewing unit 200 when watching video. The user terminal on which the distribution unit 100 is started is the distributor's terminal, i.e., the user terminal that generates the video data. The user terminal on which the viewing unit 200 is started is the viewer's terminal, i.e., the user terminal on which the video data is reproduced and played.
[0020] The distribution unit 100 includes an imaging control unit 102, an audio control unit 104, a video transmission unit 106, and a distributor-side UI control unit 108. The imaging control unit 102 is connected to a camera (not shown in FIG. 2) and controls imaging performed by the camera. The imaging control unit 102 acquires image data from the camera. The audio control unit 104 is connected to a microphone (not shown in FIG. 2) and controls audio input from the microphone. The audio control unit 104 acquires audio data from the microphone. The video transmission unit 106 transmits video data including the image data acquired by the imaging control unit 102 and the audio data acquired by the audio control unit 104 to the server 10 via the network NW. The video data is transmitted in real time by the video transmission unit 106. That is, the generation of the video data by the imaging control unit 102 and the audio control unit 104 and the transmission of the generated video data by the video transmission unit 106 are performed substantially simultaneously. The distributor-side UI control unit 108 controls the UI (user interface) of the distributor. The distributor-side UI control unit 108 may be connected to a display (not shown in FIG. 2 ) and displays a video on the display by playing the video data transmitted by the video transmission unit 106. The distributor-side UI control unit 108 may display an operation object or an instruction permission object on the display and receive input from the distributor who taps on the object.
[0021] The viewing unit 200 includes a viewer-side UI control unit 202, an overlay information generation unit 204, and an input information transmission unit 206. The viewing unit 200 receives video data related to a live broadcast, in which the broadcaster, the viewer who is the user of the user terminal 30, and other viewers participate, from the server 10 via the network NW. The viewer-side UI control unit 202 controls the viewer's UI. The viewer-side UI control unit 202 is connected to a display and a speaker (not shown in FIG. 2 ) and plays the received video data, displays the video on the display, and outputs the audio from the speaker. The state in which the video is output to the display and the audio is output from the speaker can be referred to as a state in which "video data is being played." The viewer-side UI control unit 202 is also connected to an input means (not shown in FIG. 2 ), such as a touch panel, keyboard, or display, and acquires user input via the input means. The overlay information generation unit 204 overlays a predetermined frame image on an image generated from video data from the server 10. The frame image includes various user interface objects (hereinafter simply referred to as "objects") for receiving input from the user, comments entered by the viewer, and / or information acquired from the server 10. The input information transmission unit 206 transmits the user input acquired by the viewer-side UI control unit 202 to the server 10 via the network NW.
[0022] In some embodiments, the user terminal 20 may be a terminal used by a seller (or administrator, or merchant) to sell items on a sales site (or e-commerce site, or social media page with sales functionality). Sales activities may include creating sales posts on the sales site. In some embodiments, the posts may include live streaming content. In some embodiments, the user terminal 30 may be a terminal used by a buyer (or visitor) to purchase or browse items on the sales site or e-commerce site. Purchasing activities may include leaving comments on the sales posts.
[0023] The user terminal 30 (or the user terminal 20) also includes an acquisition unit 230, a display unit 232, a processing unit 234, an item DB 250, and a machine learning DB 252. The user terminal 30 communicates with a platform server 270 and a download server 280.
[0024] The platform server 270 is a server (or third-party server) that supports or operates a sales site, and may include any e-commerce platform or social media platform such as Facebook or Instagram.
[0025] The download server 280 is a server from which programs, applications, plug-ins, or program extensions can be downloaded. For example, it may be a server for the Google Play Store, the Apple Store, or an extension download space. The extension download space may be a location where browser extensions, such as Chrome extensions, can be accessed.
[0026] In some embodiments, the acquisition unit 230 and / or the display unit 232, the processing unit 234, the item DB 250, and the machine learning DB 252 may be implemented in (or included in) an extension downloaded from the download server 280. In some embodiments, the extension may be installed in an application such as a browser on the user terminal 30 (or the user terminal 20).
[0027] 7 is a table illustrating an exemplary data structure of the item DB 250. The item DB 250 stores data on items sold on a sales site. The item DB 250 stores item IDs and item names in association with each other. In some embodiments, the data included in the item DB 250 may be set by a seller using the user terminal 20 to match sales posts on the sales site. In some embodiments, the data in the item DB 250 may be set by the acquisition unit 230 or the processing unit 234 by extracting the data from the sales posts on the sales site.
[0028] The machine learning DB 252 may include various AI or machine learning models, such as large-scale language models (LLMs), including, for example, ChatGPT.
[0029] The acquiring unit 230 is configured to acquire website data or e-commerce data from the platform server 270 .
[0030] The display unit 232 is configured to display a website supported or operated by the platform server 270 based on the website data acquired by the acquisition unit 230. The website may include one or more sales posts. In some embodiments, the display function may be performed by the viewing unit 200. In some embodiments, the website is accessed by a browser of the user terminal 20, and the extension including the display unit 232 is installed on the browser.
[0031] The processing unit 234 is configured to determine whether content on the website meets a predetermined criterion. For example, the processing unit 234 may crawl / extract / scan data from the website (or webpage) to determine whether the user accessing the website is a seller / administrator on the website. The predetermined criterion may require that the content contain a keyword, such as "administrator" or "seller," indicating that the user is a seller on the website. In some embodiments, the user must first log in to the website as a seller / administrator. The keyword may vary for different websites and can be set according to actual operations.
[0032] If it is determined that the user is a seller, the display unit 232 displays a login object / interface configured for the user to log in to the order management service provided by the server 10. During the login process, the obtaining unit 230 obtains an identifier from the seller, which is associated with the sales site (or the sales post) and the post management service provided by the server 10. In some embodiments, the identifier may be the seller's user ID on the sales site. In some embodiments, the identifier may be the seller's user ID on the order management service system.
[0033] In response to or after a successful login to the order management service, the display unit 232 displays export objects associated with sales posts on the website, which may be displayed along with the sales posts.
[0034] The processing unit 234 is configured to detect that the seller has selected the export object. The processing unit 234 may then extract one or more purchase comments associated with the sales post and send the purchase comments to the order management server 10 for subsequent order management. The purchase comments may be tied to or linked to the identifier of the seller. The purchase comments may have been left by other users or buyers on the website. The processing unit 234 may also extract other order information and send the order information to the server 10 for order management. The order information may include, for example, the sales post's post ID, a seller user ID, a buyer user ID, and / or an order time (or comment time).
[0035] In some embodiments, the processing unit 234 may analyze and determine the purchase information from the purchase comments using the machine learning DB 252. For example, the processing unit 234 may use the LLM from the machine learning DB 252 to reference the item DB 250 and determine which items and how many items the purchaser wants based on the purchaser's comments. In some embodiments, the processing unit 234 may send the determined purchase information (including the determined item names and quantities) to the server 10 instead of sending the original purchase comments.
[0036] In some embodiments, the processing unit 234 may find or determine that a portion of the purchase comment does not match the set of items in the item DB 250. In that case, the processing unit 234 may use the machine learning DB 252 to determine candidate items among the set of items in the item DB 250 that are correlated (or most correlated) with the portion of the purchase comment. The processing unit 234 may then generate a confirmation comment for the post (or for the purchase comment) that includes the candidate items.
[0037] 3 is a block diagram illustrating the functions and configuration of the server 10 of FIG. 1 according to some embodiments of the present invention. The server 10 includes a distribution information providing unit 302, a relay unit 304, a gift processing unit 306, a payment processing unit 308, a stream DB 310, a user DB 312, a gift DB 314, an order processing unit 320, a notification unit 322, an order DB 350, an inventory DB 352, and a machine learning DB 354.
[0038] When a notification or request for the start of live streaming is received from the user terminal 20 on the distributor side via the network NW, the streaming information providing unit 302 registers in the stream DB 310 a stream ID for identifying this live streaming and the distributor ID of the distributor performing the live streaming.
[0039] When the distribution information providing unit 302 receives a request for information about live distribution from the viewing unit 200 of the user terminal 30 on the viewer side via the network NW, the distribution information providing unit 302 obtains or checks currently available live distributions from the stream DB 310 and creates a list of available live distributions. The distribution information providing unit 302 then transmits the created list to the requesting user terminal 30 via the network NW. The viewer-side UI control unit 202 of the requesting user terminal 30 generates a live distribution selection screen based on the received list and displays it on the display of the user terminal 30.
[0040] When the input information transmitting unit 206 of the user terminal 30 receives the viewer's selection on the live streaming selection screen, the input information transmitting unit 206 generates a streaming request including the stream ID of the selected live streaming and transmits the request to the server 10 via the network NW. The streaming information providing unit 302 starts providing the live streaming specified by the stream ID included in the received streaming request to the requesting user terminal 30. The streaming information providing unit 302 updates the stream DB 310 so that the viewer ID of (or the corresponding) the stream ID includes the user ID of the viewer of the requesting user terminal 30.
[0041] The relay unit 304 relays the video data from the user terminal 20 on the broadcaster side to the user terminal 30 on the viewer side during the live broadcast started by the broadcast information providing unit 302. The relay unit 304 receives a signal representing a user input by a viewer from the input information transmitting unit 206 during the live broadcast or playback of the video data. The signal representing the user input may be an object designation signal that designates an object displayed on the display of the user terminal 30. The object designation signal may include the viewer ID of the viewer, the broadcaster ID of the broadcaster of the live broadcast being watched by the viewer, and an object ID that identifies the object. When the object is a gift, the object ID is a gift ID. Similarly, the relay unit 304 receives a signal representing a user input made by the broadcaster during playback of the video data (or during live broadcast) from the broadcast unit 100 of the user terminal 20. The signal may be an object designation signal.
[0042] Furthermore, the signal representing the user input may be a comment input signal containing a comment entered by the viewer into the user terminal 30 and the viewer ID of the viewer. Upon receiving the comment input signal, the relay unit 304 transmits the comment and the viewer ID contained in the signal to the user terminal 20 of the distributor and the user terminals 30 of other viewers. In these user terminals 20, 30, the viewer-side UI control unit 202 and the overlay information generation unit 204 display the received comment on a display associated with the received viewer ID.
[0043] The gift processing unit 306 increases the points of the broadcaster based on the points of the gift identified by the gift ID included in the object designation signal, and updates the user DB 312. Specifically, the gift processing unit 306 refers to the gift DB 314 to identify the points to be assigned to the gift ID included in the received object designation signal. Then, the gift processing unit 306 updates the user DB 312 and adds the identified points to the points of the broadcaster ID (or corresponding to the broadcaster ID) included in the object designation signal.
[0044] In response to receiving the object designation signal, the payment processing unit 308 processes payment for the gift from the viewer. Specifically, the payment processing unit 308 refers to the gift DB 314 to determine the price points of the gift identified by the gift ID included in the object designation signal. Then, the payment processing unit 308 updates the user DB 312 and subtracts the determined price points from the points of the viewer identified by the viewer ID included in the object designation signal.
[0045] FIG. 4 is a table illustrating an exemplary data structure of the stream DB 310 in FIG. 3. The stream DB 310 holds information about currently running live broadcasts. The stream DB 310 stores a stream ID, a broadcaster ID, and a viewer ID in association with each other. The stream ID is an ID for identifying a live broadcast on the live streaming platform provided by the live streaming system 1. The broadcaster ID is a user ID for identifying the broadcaster providing the live broadcast. The viewer ID is a user ID for identifying a viewer of the live broadcast. In the live streaming platform provided by the live streaming system 1 according to some embodiments, when a user starts a live broadcast, the user becomes a broadcaster, and when the same user watches a live broadcast broadcast by another user, the user also becomes a viewer. Therefore, the distinction between a broadcaster and a viewer is not fixed, and a user ID registered as a broadcaster ID at one time may be registered as a viewer ID at another time.
[0046] FIG. 5 is a table illustrating an exemplary data structure of the user DB 312 of FIG. 3. The user DB 312 holds information about users. The user DB 312 stores user IDs and points in association with each other. The user ID identifies a user. The points correspond to points held by the corresponding user. The points are electronic value circulated within the live streaming platform. In some embodiments, when a streamer receives a gift from a viewer during a live broadcast, the streamer's points increase by a value corresponding to the gift. The points are used, for example, to determine the amount of compensation (e.g., money) that the streamer receives from an administrator of the live streaming platform. In some embodiments, when the streamer receives a gift from a viewer, an amount corresponding to the gift may be given instead of the points.
[0047] FIG. 6 is a table illustrating an exemplary data structure of the gift DB 314 of FIG. 3. The gift DB 314 stores information about gifts available to viewers during the live broadcast. Gifts are electronic data. Gifts may be purchased with points or money, or may be provided free of charge. Viewers can give gifts to broadcasters. Giving a gift to a broadcaster is also referred to as using a gift, sending a gift, or throwing a gift. Some gifts can be used immediately upon purchase, while others can be used later by the viewer who purchased them. When a viewer gives a gift to a broadcaster, the broadcaster is awarded a number of points corresponding to the gift. When a gift is used, an effect related to the gift may be generated. For example, an effect (such as a visual or auditory effect) corresponding to the gift may be displayed on the live broadcast screen.
[0048] The gift DB 314 stores gift IDs, awarded points, and price points in association with one another. The gift ID is used to identify a gift. The awarded points are the amount of points awarded to a broadcaster when the gift is given to the broadcaster. The price points are the amount of points paid for using (purchasing) a gift. While watching a live broadcast, a viewer can give a desired gift to a broadcaster by paying the price points of the desired gift. The price points can be paid using an appropriate electronic payment method. For example, the viewer may pay the price points to the administrator. Alternatively, payment may be made by bank transfer or credit card. The administrator can arbitrarily set the relationship between the awarded points and the price points. For example, the awarded points may be set to equal the price points. Alternatively, the price points may be set to the amount obtained by multiplying the awarded points by a predetermined coefficient such as 1.2, or the amount obtained by adding a predetermined handling fee to the awarded points.
[0049] In some embodiments, the server 10 may be a server running an order management service system that may be configured to assist a merchant / administrator of a sales site in managing order data on the sales site.
[0050] The machine learning DB 354 may include various AI or machine learning models, such as large-scale language models (LLMs), including, for example, ChatGPT.
[0051] 8 is a table showing an example data structure of the order DB 350. The order DB 350 stores the post ID, seller user ID, sales site purchaser user ID, order management purchaser user ID, and order data in association with each other. The order data includes an item ID, item name, order quantity, and order time.
[0052] The post ID is configured to identify the sales post on the sales site. The seller user ID is the user ID of the seller of the sales post (or the sales site). The sales site buyer user ID is the user ID of the buyer of the sales post. The order management buyer user ID is a user ID in the order management service system provided by the server 10. For example, using the order management buyer user ID, the server 10 may access another database for corresponding user data such as the user's name, address, and billing. The matching between the sales site buyer user ID and the order management buyer user ID can be achieved in advance in various ways depending on actual circumstances.
[0053] The data in the order DB 350 may be acquired, processed, analyzed, and stored in the order DB 350 by the order processing unit 320. For example, the order processing unit 320 acquires purchase comments on sales posts and order information (post ID, seller user ID, purchaser user ID, etc.) from the seller-side processing unit 234. For example, the order processing unit 320 may use the machine learning DB 354 to analyze the purchase comments and extract the item ID, item name, order quantity, and / or order time.
[0054] 9 is a table showing an exemplary data structure of the inventory DB 352. The inventory DB 352 stores the item ID, the cumulative order quantity, and the inventory quantity in association with each other.
[0055] The cumulative order number may be calculated, for example, by the order processing unit 320 from the order DB 350. The inventory number indicates how many items remain for sale.
[0056] FIG. 10 shows a flowchart illustrating an exemplary flow according to some embodiments of the present invention.
[0057] In step S1000, the user opens the sales site and uses the browser of the user terminal to log in. A plug-in (or an extension) for order management is installed in the browser.
[0058] In step S1002, the plugin determines whether the user is a merchant (or administrator) for the sales site based on the content of the website. If yes, flow proceeds to step S1004. If no, flow proceeds to step S1012.
[0059] In step S1004, the plug-in displays a seller screen having a login interface for the user to log in to the order management system operated by the order management server 10.
[0060] In step S1006, after successful login, the plug-in displays an "Export" button (or object) along with the sales posts on the sales site, allowing the user to extract data related to the sales posts.
[0061] In step S1008, the plug-in detects that the user has selected the "Export" button.
[0062] In step S1010, the plug-in sends the order data (including the post ID, the seller ID, the buyer ID, the purchase comment, or the extracted purchase information) to the order management server 10. The order is then confirmed and executed.
[0063] If the flow proceeds to step S1012, it means that the user who logged in to the sales site in step S1000 is not a seller but a purchaser.
[0064] In step S1012, the user terminal of the purchaser displays (or remains displayed) a seller screen that does not have a login interface for the order management system. The user terminal of the purchaser also acquires purchase comments regarding the sales posting on the sales site.
[0065] In step S1014, a seller-side plug-in acquires and analyzes the purchase comments on the sales site. The seller-side plug-in is installed in the browser of the user terminal of the seller who is the seller / administrator of the sales post (or the sales site).
[0066] In step S1016, the seller plug-in checks whether the order details are clear. For example, the seller processing unit 234 uses the machine learning DB 252 and the item DB 250 to analyze the purchase comments and determine whether the buyer left a clear order message. If yes, the flow proceeds to step S1018. If no, the flow proceeds to step S1022.
[0067] In step S1022, the seller plugin generates an order confirmation comment for the sales post and confirms the order details with the buyer. The flow then returns to step S1012 to retrieve the buyer's purchase comment (or modified purchase comment).
[0068] In step S1018, the seller plug-in checks whether the item's inventory is sufficient for the new order. For example, the seller processing unit 234 may access the order DB 350 and / or the inventory DB 352 on the order management server 10 to check whether the order can be fulfilled. If yes, the flow proceeds to step S1020. If no, the flow proceeds to step S1024.
[0069] In step S1024, the seller plugin generates an order confirmation comment for the sales post and confirms the order details with the buyer. The confirmation comment includes inventory information. The flow then returns to step S1012 to retrieve the buyer's purchase comment (or modified purchase comment).
[0070] In step S1020, the seller's plug-in sends the order data (including the post ID, the seller ID, the buyer ID, the purchase comment, or the extracted purchase information) to the order management server 10. The order is then confirmed and executed.
[0071] 11 illustrates an example of a social media page from an administrator's perspective according to some embodiments of the present invention. FIG. 11 may correspond to steps S1000, S1002, and S1004 in FIG.
[0072] The social media page includes a sales posting area, a comment display area, and a comment input area. The sales posting area includes sales posting content, including the name of the seller / seller, the product name, and the product price. The comment display area is an area where comments related to the sales posting are displayed. The comment input area is for inputting comments. The social media page is operated by a social media server. The social media may be, for example, Facebook, Instagram, TikTok, or X (formerly known as Twitter).
[0073] Since user U1 is an administrator (or seller / vendor) on the social media page, after logging in to the social media page, the content "Administrator U1" is displayed on the page. Then, a plug-in installed in the browser of user U1's user terminal determines that user U1 is the administrator of the social media page based on the content "Administrator". Then, the plug-in displays a "Log in to Order Management" option for user U1 to log in to the order management system supported by the order management server 10.
[0074] 12 illustrates an example of a social media page from an administrator's perspective according to some embodiments of the present invention. FIG. 12 may correspond to step S1004 in FIG.
[0075] When user U1 selects "Log in to order management" in Fig. 11, the plug-in displays a login interface for user U1 to log in to the order management service. User U1 may log in by entering his / her own identifier in the order management system.
[0076] 13 illustrates an example of a social media page from an administrator's perspective according to some embodiments of the present invention. FIG. 13 may correspond to step S1006 in FIG.
[0077] After successfully logging into the order management system, the plugin displays the sales post along with an "Export" button. User U1 may select the button to extract and send the order data to the order management server 10 for further analysis and order preparation. The order data may include the post ID, user U1's user ID, the post content, the comment data, and the user ID of the user who left the comment data.
[0078] The plugin may display the number of new comments, which are comments newly left since the last export operation. In some embodiments, the plugin may automatically export any new comments upon detecting that there are new comments.
[0079] Figure 14 illustrates an example of a social media page from an administrator's perspective in accordance with some embodiments of the present invention. Figure 14 is similar to Figure 13, except that the sales post includes live-streamed content where the broadcaster or seller is making a live sale within the post.
[0080] 15 illustrates an example of a social media page from a buyer's perspective according to some embodiments of the present invention. FIG. 15 may correspond to steps S1000, S1002, and S1012 in FIG.
[0081] The user U5 is not an administrator of the social media page (or associated with the sales post), but a buyer / visitor, and therefore after logging into the social media page, the content "Administrator" does not appear on the page.
[0082] The plugin installed in the browser of the user U5's device determines that the user U5 is a buyer / visitor of the social media page because there is no "administrator" for the content. Therefore, the plugin does not display the "Log in to Order Management" option to log in to the order management system. The user U5 enters the comment "White Coffee M+1" and places an order.
[0083] In some embodiments, the user U5 may not have the plug-in installed on the user terminal for communicating with the order management server 10. In that case, step S1002 does not exist, and the flow proceeds from step S1000 to step S1012 in FIG.
[0084] 16 illustrates an example of a social media page from the buyer's perspective according to some embodiments of the present invention. FIG. 16 may correspond to steps S1014, S1016, S1022, and S1012 in FIG.
[0085] The purchase comment "White Coffee M+1" from user U5 is displayed in the comment display area. A plugin on the user device of user U1 (the seller of the sales post) analyzes the comment and finds that it does not match the data in the item database. The plugin then uses the machine learning database to find the item that user U5 most likely meant, "White Coffee Pack L," and generates a confirmation comment to confirm with user U5.
[0086] User U5 may then reply to the confirmation comment to clarify the order. User U5 may then leave a comment saying "Yes," which will be displayed in the comment display area. The seller (user U1) plugin then determines (e.g., with the assistance of an LLM) that a confirmation result regarding the confirmation comment was generated by the buyer U5 on the website (or for the sales post). The seller plugin then transmits the confirmation result to the order management server.
[0087] 17 illustrates an example of a social media page from the buyer's perspective according to some embodiments of the present invention. FIG. 17 may correspond to steps S1014, S1016, S1018, S1024, and S1012 in FIG.
[0088] The purchase comment "White Coffee L+6" from user U5 is displayed in the comment display area. A plugin on the user terminal of user U1 (the seller of the sales post) analyzes the comment and determines the purchased item. The plugin accesses the inventory DB in the order management server and determines that there is not enough stock to fulfill the order. Therefore, the plugin generates a confirmation message including inventory information for user U5 to confirm. User U5 may then reply to the confirmation message and modify the order. In some embodiments, the processing unit 234 on the seller's user terminal may access the inventory DB 352 on the server 10 to determine the number of orders that can be accepted from the buyer (or new buyer). This process may be performed automatically or periodically, or may be performed each time a new order is received.
[0089] In some embodiments, the seller plugin performs a comparison between multiple purchase comments from multiple buyers associated with the sales post and the inventory data. The seller plugin then generates a result for the sales post. For example, the result may be a comment indicating that there is insufficient stock for a new order. Or, the result may be a comment indicating how many items are left.
[0090] FIG. 18 illustrates an example of a social media page from a buyer's perspective according to some embodiments of the present invention.
[0091] FIG. 18 is similar to FIG. 16, except that the analysis / confirmation of the purchase comment is performed by a plugin installed on the user terminal of user U5 (the purchaser). The buyer-side plugin analyzes the comment and detects that it does not match the item DB (which may be on user U5's user terminal). In response, the buyer-side plugin generates a confirmation interface for user U5 to confirm the order. User U5 may click "Yes" in the interface to confirm the order or modify the purchase.
[0092] FIG. 19 illustrates an example of a social media page from a buyer's perspective according to some embodiments of the present invention.
[0093] FIG. 19 is similar to FIG. 17, except that the analysis / confirmation of the purchase comment is performed by a plugin installed on the user terminal of user U5 (the purchaser). The buyer-side plugin accesses the inventory database of the order management server and detects that there is insufficient stock for the order. In response, the buyer-side plugin generates a confirmation interface for user U5 to confirm the order. User U5 may click "Yes" in the interface to confirm the new order or modify the purchase details.
[0094] In some embodiments, the plug-in or extension may be generated and / or stored on the order management server 10. The plug-in may then be uploaded to the download server 280 for download by the user terminal 20 or 30. In some embodiments, the order management server 10 may include a notification unit that notifies the merchant to download the plug-in to the user terminal in order to use the order management service.
[0095] On existing social networking services such as Facebook and Instagram, some SNS users sell products through posts, chats, and videos. SNSs themselves typically do not provide tools for e-commerce, such as order management and transactions. Therefore, users are directed to sellers' websites that offer e-commerce functionality, or use specialized software (such as OrderPally) to manage orders on SNSs.
[0096] The dedicated software communicates directly with the server hosting the SNS via an API (application programming interface) provided by the SNS, thereby obtaining text data from the conversation between the seller and the buyer.
[0097] This scheme is convenient because it allows SNS users to easily conduct e-commerce transactions on the SNS without having to implement e-commerce functionality in the SNS itself. However, as a provider of dedicated software, there is a risk that the API may become unavailable for some reason, such as increased costs or service termination. Regardless of the SNS's API, an alternative solution to dedicated software is needed to continue providing services to users.
[0098] Some embodiments of the present invention provide an extension program for a web browser on a user terminal. When the extension program is installed, an "Export" button appears on a social networking post rendered by the web browser on the seller's terminal. The "Export" button does not appear on a social networking post rendered by the web browser on the buyer's terminal. When the extension program detects that the export button has been selected, it acquires the HTML data of the social networking post on which the export button is installed and analyzes the HTML data to extract comments from the buyer. The extension program then transmits the extracted comments or any data obtained from the extracted comments via a network to a server separate from the server hosting the social networking site. The server receives the extracted comments and registers, updates, or deletes order information based on the content of the extracted comments.
[0099] In some embodiments of the present invention, a seller on an SNS has a group consisting of multiple posts, each of which is associated with one or more products. In one embodiment, an export button may be implemented in each post in the group of the seller so that the seller can select the post / product for which they want to manage orders. In another embodiment, there is only one export button on the top page of the group on the SNS. When the export button is specified, the extension program automatically retrieves HTML data for all posts under the group.
[0100] The hardware configuration of the information processing device will be described with reference to Fig. 20. Fig. 20 is a block diagram showing an example of the hardware configuration of an information processing device based on some embodiments of the present invention. The information processing device 900 shown in the figure can realize, for example, the server 10 and / or the user terminals 20 and 30 in some embodiments.
[0101] The information processing device 900 includes a CPU 901, a ROM (read-only memory) 903, and a RAM (random access memory) 905. The information processing device 900 may also include a host bus 907, a bridge 909, an external bus 911, an interface 913, an input device 915, an output device 917, a storage device 919, a drive 921, a connection port 925, and a communication device 929. The information processing device 900 also includes an imaging device such as a camera (not shown). The information processing device 900 may also include a DSP (digital signal processor) or an ASIC (application-specific integrated circuit) in addition to or instead of the CPU 901.
[0102] The CPU 901 functions as an arithmetic processing device and control device, controlling all or part of the operation of the information processing device 900 in accordance with various programs stored in the ROM 903, the RAM 905, the storage device 919, or the removable recording medium 923. For example, the CPU 901 controls the overall operation of each functional unit included in the server 10 and the user terminals 20 and 30 in some embodiments. The ROM 903 stores programs and calculation parameters used by the CPU 901. The RAM 905 functions as a main storage device that stores programs used during execution by the CPU 901 and parameters that change appropriately during execution. The CPU 901, ROM 903, and RAM 905 are interconnected by a host bus 907, which may be an internal bus such as a CPU bus. Furthermore, the host bus 907 is connected to an external bus 911, such as a PCI (Peripheral Component Interconnect / Interface) bus, via a bridge 909.
[0103] The input device 915 may be a device operated by a user, such as a mouse, keyboard, touch panel, button, switch, or lever, or a device that converts a physical quantity into an electrical signal, such as a sound sensor typified by a microphone, an acceleration sensor, a tilt sensor, an infrared sensor, a depth sensor, a temperature sensor, or a humidity sensor. The input device 915 may be, for example, a remote control device that uses radio waves such as infrared, or an external connection device 927 such as a mobile phone that supports operation of the information processing device 900. The input device 915 includes an input control circuit that generates an input signal based on information input by the user or a detected physical quantity and outputs the signal to the CPU 901. The user operates the input device 915 to input various data to the information processing device 900 and instruct it to operate.
[0104] The output device 917 is a device that can visually or audibly notify the user of acquired information. The output device 917 may be, for example, a display such as an LCD, PDP, or OLED, an audio output device such as a speaker or headphones, or a printer. The output device 917 outputs the processing results of the information processing device 900 as video such as text or an image, or audio such as voice.
[0105] The storage device 919 is a data storage device and is configured as an example of a storage unit of the information processing device 900. The storage device 919 is, for example, a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device, an optical storage device, or a magneto-optical storage device. The storage device 919 stores programs executed by the CPU 901, various data, various data acquired from the outside, and the like.
[0106] The drive 921 is a reader / writer of a removable recording medium 923 such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory, and is built into or externally attached to the information processing device 900. The drive 921 reads information recorded on the attached removable recording medium 923 and outputs it to the RAM 905. Furthermore, the drive 921 writes information to the attached removable recording medium 923.
[0107] The connection port 925 is a port for directly connecting a device to the information processing device 900. The connection port 925 may be, for example, a USB (Universal Serial Bus) port, an IEEE 1394 port, or a SCSI (Small Computer System Interface) port. Furthermore, the connection port 925 may be an RS-232C port, an optical audio terminal, an HDMI (High-Definition Multimedia Interface) port, or the like. By connecting the external connection device 927 to the connection port 925, various data can be exchanged between the information processing device 900 and the external connection device 927.
[0108] The communication device 929 is, for example, a communication interface formed by a communication device for connecting to the network NW. The communication device 929 may be, for example, a communication card for a wired or wireless local area network (LAN), Bluetooth (trademark), or wireless USB (WUSB). Furthermore, the communication device 929 may be a router for optical communication, a router for ADSL (asymmetric digital subscriber line), or a modem for various communications. The communication device 929 transmits and receives signals, etc., over the Internet or with other communication devices using a predetermined protocol such as TCP / IP. The communication network NW connected to the communication device 929 is a wired or wireless network, such as the Internet, a home LAN, infrared communication, radio wave communication, or satellite communication. The communication device 929 functions as a communication device.
[0109] The imaging device (not shown) is a device that captures an image of real space using an imaging element such as a CCD (charge-coupled device) or a CMOS (complementary metal-oxide semiconductor), and various components such as a lens for controlling the formation of a subject image on the imaging element, and generates a captured image. The imaging device may capture either a still image or a moving image.
[0110] The above describes the configuration and operation of the live streaming system 1 according to this embodiment. This embodiment is merely an example, and it will be understood by those skilled in the art that various modifications are possible with respect to the combination of each component and each process, and that such modifications are also within the scope of the present invention.
[0111] The processes and procedures described in the present invention, in addition to those explicitly described, can be implemented by software, hardware, or any combination thereof. For example, the processes and procedures described herein can be implemented by implementing logic corresponding to the processes and procedures in media such as integrated circuits, volatile memory, non-volatile memory, non-transitory computer-readable media, magnetic disks, etc. Furthermore, the processes and procedures described herein can be implemented as computer programs corresponding to the processes and procedures, and can be executed by various types of computers.
[0112] Furthermore, the system or method described in the above embodiments may be integrated into a program stored in a non-transitory computer-readable medium such as a solid-state storage device, an optical disk storage device, a magnetic disk storage device, etc. Alternatively, the program may be downloaded from a server via the Internet and executed by a processor.
[0113] Although the technical contents and features of the present invention have been described above, those skilled in the art can still make many variations and modifications without departing from the teachings and disclosure of the present invention. Therefore, the scope of the present invention is not limited to the embodiments already disclosed, but is within the scope of the claims, including other variations and modifications that do not depart from the present invention.
[0114] Figure 21 illustrates an example of a social media page according to some embodiments of the present invention. The user interface may correspond to an administrator (or seller / vendor) screen or a buyer screen.
[0115] The post is created by user U1 and includes general information about the product being sold. The comment display area has multiple layers. The seller, for example, user U1, may create a sales comment in layer 1 that includes product information. The sales comment begins in layer 1, and the product information may include specifications and images for multiple products. A buyer, for example, U3, U4, U6, or U7, may create an order comment by replying to the sales comment in a subsequent layer. User U3, The order comment from U4 or U6 starts at layer 2 and includes order information, including the product name and order number. The order comment from user U7 starts at layer 3 because user U7 created the order comment by replying to the order comment from user U6. User U7 does not need to specify the details of the order information because the order information is analyzed based on the comment that user U7 replies to.
[0116] The processing unit 234 on the user terminal may extract / analyze the webpage data (e.g., HTML data) of the social media page to determine the sales and order information and send the information to the server 10. The processing unit 234 may use / analyze the information of the layers and the content of each comment to determine whether the comment is a sales comment or an order comment. For example, a comment that starts in layer 1 and / or includes sales information (e.g., sales / product-related keywords) may be determined to be a sales comment. For example, a comment that starts in layer 2 or 3 and / or includes order information (e.g., product-related keywords / order number) may be determined to be an order comment. Then, the processing unit 234 may send all the order information to the server 10.
[0117] In some embodiments, comments initiated on different layers may have different tags or prefixes in the web page data, which may be used by the processing unit 234 to distinguish between different layers of comments. In some embodiments, users who are not registered as sellers / administrators cannot leave comments on layer 1.
[0118] 22 shows a flowchart illustrating a process for generating data from comments at a user terminal using a browser plug-in according to some embodiments of the present invention. In step S2002, the plug-in in the user terminal may perform a login process described herein with reference to, for example, Figures 10, 11, and 12. In step S2004, the plug-in in the user terminal may detect that an export button has been pressed, as described herein with reference to Figure 13.
[0119] In step S2006, in response to detecting that the export button has been pressed, the plug-in in the user terminal may extract a comment portion of the HTML file of the social media page, as shown in FIG. 21 . The extracted comment portion corresponds to the comment display area of the social media page. In step S2008, the plug-in may parse the extracted portion into individual comments. Data for each extracted comment may include (i) the body / content of the comment, (ii) the user ID of the user who posted the comment, (iii) a timestamp indicating when the comment was posted, (iv) the layer or depth to which the comment belongs, and (v) relationships between the comment and other comments. The relationships may include dependencies. The layer and dependencies of the comments may be obtained by the plug-in analyzing the extracted portion using, for example, a Document Object Model (DOM).
[0120] After the decomposition in step S2008, steps S2010, S2012 / S2014, and S2016 may be repeated for each comment until all comments have been processed. In step S2010, the plug-in in the user terminal may determine the attribute of the comment. In some embodiments, the attribute of the comment is either seller-type or buyer-type. Assuming this, when the seller first provides a post / comment indicating product information (price, photo, inventory, details, etc.) in the comment display area of the social media page and a buyer who wishes to purchase the product replies to the post / comment, the plug-in determines that the comment belonging to layer 1 is a seller-type comment candidate. Then, the plug-in determines whether the seller-type comment candidate is a seller-type comment by keyword matching. If the keyword matching result indicates that the comment is not seller-type, the plug-in determines that the comment is a buyer-type comment candidate. The plugin determines whether this potential buyer-type comment (belonging to layer 1) is a buyer-type comment by keyword matching. If it is determined that the comment is neither a seller-type nor a buyer-type comment, the comment is ignored and not processed further. The plugin determines that a comment belonging to layer 2 or a deeper layer is a buyer-type comment candidate. Then, the plugin determines whether this potential buyer-type comment is a buyer-type comment by keyword matching. If the keyword matching result shows that the comment is not a buyer-type comment, the plugin determines that the comment is a seller-type comment candidate. The plugin determines whether this potential seller-type comment (belonging to layer 2 or a deeper layer) is a seller-type comment by keyword matching. If it is determined that the comment is neither a seller-type nor a buyer-type comment, the comment is ignored and not processed further.
[0121] In the process of determining the attribute of the comment, the user ID of the comment (which indicates the poster of the comment) may or may not be used. In one embodiment, a criterion may be used in which all comments by the seller are classified as seller type and the remaining comments are classified as buyer type. In another embodiment, the seller may collaborate with another user (helper) to sell products on social media, and in that case, users with user IDs other than the seller may not necessarily be buyers. In such cases, a combination of the above-mentioned layer / depth and keyword matching may be used.
[0122] If the comment is determined to be merchant-type in step S2010, the process proceeds to step S2012, where the plug-in applies a merchant algorithm to the comment to extract information from the comment. In some embodiments, the merchant algorithm is configured to determine from the comment: (i) a product ID identifying the product sold by the merchant, (ii) a description of the product, and (iii) the number of items in stock for the product. In step S2016, the plug-in records the extracted information in an extracted product list 704. Figure 24 is a table illustrating an exemplary data structure for extracted product list 704. The extracted product list 704 associates and stores the product ID, description, and number of items in stock for the product.
[0123] If step S2010 determines that the comment is buyer-type, the process proceeds to step S2014, where the plugin applies a buyer algorithm to the comment to extract information from the comment. In some embodiments, the buyer algorithm is configured to determine from the comment: (i) a product ID identifying the product sold to the buyer, (ii) the buyer's user ID, (iii) the number of orders, and (iv) a timestamp indicating when the comment corresponding to the order was made. The buyer algorithm determines the buyer's user ID using the user ID of the user who posted the comment. The buyer algorithm determines the product ID using relationships between comments. For example, if a buyer-type comment depends on a parent seller-type comment, the product ID of the seller-type comment is determined to be the product ID associated with the parent seller-type comment. In step S2016, the plugin records the extracted information in an extracted orders list 702. FIG. 23 is a table illustrating an exemplary data structure for extracted orders list 702. The extracted order list 702 stores the product ID of the sold product, the user ID of the purchaser, the number of orders, and a timestamp in association with each other.
[0124] In step S2018, the plug-in of the user terminal may transmit the extracted information list (including the extracted product list 704 and the extracted order list 702) to the order management server.
[0125] By determining the attributes of the comment and extracting information from the comment using an algorithm corresponding to the determined attributes, it is possible to extract the required information with greater accuracy and completeness. For example, even if the comment display area has multiple layers, the plug-in can classify the comment as a seller type or a buyer type and extract the required order information according to the classification.
[0126] In other embodiments, any attribute may be used, such as helper type, male / female, frequent buyer / new buyer, young / old, etc. An algorithm for analyzing the comments may be selected according to the determined attributes.
[0127] In other embodiments, the functions implemented in the user terminal may be implemented in the order management server. For example, any or any combination of steps S2006, S2008, S2010, S2012, S2014, and S2016 may be implemented in the order management system. In this case, the html file of the social media page, or a portion of the html file corresponding to the comment display area or the comment, may be transmitted to the order management server by the plug-in of the browser of the user terminal. [Explanation of symbols]
[0128] 1. Communication Systems 10 Servers 20 User terminal 30, 30a, 30b User terminal LV Streamer AU1, AU2 viewers VD, VD1, VD2 video NW Network 30 User terminals 100 delivery units 102 Imaging control unit 104 Audio control unit 106 Video Transmission Unit 108 Streamer UI Control Unit 200 viewing units 202 Viewer-side UI control unit 204 Superposition Information Generation Unit 206 Input information transmission unit 302 Distribution Information Provision Unit 304 Relay unit 306 Gift Processing Unit 308 Payment Processing Unit 310 Stream DB 312 User DB 314 Gift DB 230 Acquisition Units 232 Display Unit 234 Processing Unit 250 item database 252 Machine Learning DB 270 Platform Server 280 Download Server 320 Order Processing Unit 320 350 Order DB 352 Inventory DB 354 Machine Learning DB 900 Information Processing Equipment 901 CPU 903 ROM 905 RAM 907 Host Bus 909 Bridge 911 External Bus 913 Interface 915 Input Device 917 Output Device 919 Storage Device 921 Drive 923 Removable Recording Media 925 connection port 927 External Connection Device 929 Communication Equipment
Claims
1. 1. A method for order management via a plug-in, comprising: displaying, on a user terminal of the first user, an object associated with a post on a website supported by the first server; detecting that the first user has selected the object; sending a purchase comment from a second user associated with the post to a second server; wherein the first server is different from the second server.
2. 2. The method of claim 1, wherein the website is accessed by an application on the user terminal of the first user and the plug-in installed in the application.
3. The method of claim 1 , wherein the object is displayed with the post on the website.
4. further determining that content on the website meets predetermined criteria; displaying the object in response to the content being determined to meet the predetermined criteria; 2. The method of claim 1, comprising:
5. further comprising obtaining from the first user an identifier associated with the website and the second server; 5. The method of claim 4, wherein displaying the object associated with the post on the website occurs in response to obtaining the identifier.
6. further determining that a portion of the purchase comments does not match a set of items; determining that a first item in the set of items is correlated with the portion of the purchase comment; and generating a review comment regarding the post that includes the first item.
7. further determining that the confirmation result regarding the confirmation comment was generated by the second user on the website; transmitting the confirmation result to the second server; 7. The method of claim 6, comprising:
8. further acquiring inventory data from the second server; performing a comparison between a plurality of purchase comments from a plurality of users associated with the post and the inventory data; generating a result of performing the comparison on the website; 2. The method of claim 1, comprising:
9. 10. The method of claim 1, wherein the first server is a social media server and the second server is an order management server.
10. A terminal for order management, comprising one or more processors, wherein the one or more processors execute a browser plug-in to: displaying, on a user terminal of the first user, an object associated with a post on a website supported by the first server; detecting that the first user has selected the object; sending a purchase comment from a second user associated with the post to a second server; and wherein the first server is different from the second server.
11. 1. A non-transitory computer-readable medium containing a plug-in program for order management, wherein the plug-in program is configured to: displaying, on a user terminal of the first user, an object associated with a post on a website supported by the first server; detecting that the first user has selected the object; sending a purchase comment from a second user associated with the post to a second server; wherein the first server is different from the second server.
Citation Information
Patent Citations
Broadcast system, live broadcast device, live broadcast method, and program
JP2021129205A
Video distribution type commodity sales system
JP2023124028A
Video streaming device, video streaming method, and video streaming program
JP2023151294A
Competitive shopping platform
US20190095976A1
Server device and electronic commerce method
WO2021106034A1