TWM562441U - Logistics order generation system - Google Patents

Abstract

A logistics order generation system is provided. The logistics order generation system has an electronic device having an event recorded application and a logistics server which is connected to the event recorded application via communication and received the information from the event recorded application. When an event record is input into the event recorded application by the user, the event recorded application automatically sends the event recorded to the logistics server. The logistics server determines a logistic distributed date according to an event type of the event record, and generates an order according to the logistic distributed date.

Description

Logistics order generation system

This new creation is about an e-commerce technology, and in particular, it relates to an event-based logistics order generation system.

In order to further understand and manage the size of life, many people have the habit of recording events. For example, a woman records a physiological cycle, and a person who likes to exercise records the date of exercise to understand the condition of her body. Or, some people will record the cycle of life, such as the filter replacement date of the air cleaner, the filter replacement date of the filter kettle, and so on. Most of these recorded events are of a recurring nature, but the nature of the date is uncertain. In addition, these events are accompanied by corresponding shopping behavior. Taking the above description as an example, when the physiological cycle ends, the woman will purchase the four drinks. Or when the exercise is over, the athletes will purchase high-protein supplements. Or, after the filter of the air cleaner and the filter element of the filter kettle are replaced, the filter and the filter cartridge must be replaced again after a certain period of time.

Although there is a correlation between recorded events and shopping, there are two steps in recording events and purchasing corresponding items. The user will record the occurrence of the event in the calendar of the notepad/handheld device, manage the time course of the shopping, and remind himself to go shopping. Therefore, in a hasty life, users are often too busy to forget, or there is no way to purchase. Based on this, how to provide a user-integrated and convenient shopping experience is a subject of the technical staff.

This new creation provides an event-based logistics order generation system to provide an integrated and convenient shopping experience.

The logistics order generating system disclosed herein has an electronic device and a logistics delivery server. The electronic device installs an event recording application. The logistics delivery server communication is connected to the electronic device and receives the information transmitted by the event recording application. When the user input event is recorded in the event recording application, the event recording application automatically transmits the event record to the logistics delivery server, so that the logistics delivery server determines the logistics delivery date according to the event type recorded by the event, and according to the logistics delivery date. Generate logistics orders.

Based on the above, the present disclosure provides an event-based logistics order generation system that integrates recording events and online shopping functions. When a user records an event through an event recording application, the event recording application automatically The upload event is recorded to the logistics delivery server. In this way, when the event occurs, the user does not need to purchase the corresponding event item in the shopping website or the physical store, and can automatically purchase and deliver the corresponding item to the delivery place designated by the user. Thereby, to provide a user-friendly shopping experience.

The above described features and advantages of the present invention will become more apparent and understood from the following description.

1 is a block diagram of an event-based logistics order generation system according to an embodiment of the present disclosure. The disclosed logistics order generation system provides a user with a record of various events and automatically sends a logistics order based on the event to enable the logistics provider to deliver the goods to the user.

This event based logistics order generation system has an electronic device 110 and a logistics delivery server 120. The electronic device 110 is a device held by a user. The electronic device 110 can be a personal computer, a notebook computer, a handheld device, etc. The electronic device 110 is not limited to a model, a brand, or an operating system, as long as the user can install an event recording application. The electronic device 110 of the program 118 can be applied to the disclosed embodiments.

The electronic device 110 has a communication unit 112, a storage unit 114, and a processing unit 116. The communication unit 112 is configured to transmit and receive signals and exchange data with the distribution server 120. In an embodiment of the disclosure, the communication unit 112 is implemented by using a communication chip, which can support Global System for Mobile communication (GSM), Personal Handy-phone System (PHS). ), Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, Long Term Evolution (LTE) system, Worldwide Interoperability for Microwave Access (Worldwide) Interoperability for Microwave Access, WiMAX) systems, Wireless Fidelity (Wi-Fi) systems, or Bluetooth signal transmission components.

The storage unit 114 is configured to store software, data, and various types of code required for operating the electronic device 110. The storage unit 114 can be any type of fixed or removable random access memory (RAM), read-only memory (ROM), flash memory, hard disk. (Hard Disk Drive, HDD), Solid State Drive (SSD) or the like or a combination of the above.

The processing unit 116 is connected to the communication unit 112 and the storage unit 114. The processing unit 116 can be a central processing unit (CPU), or other programmable general purpose or special purpose microprocessor (Microprocessor), digital signal processor (DSP), programmable The controller, the Application Specific Integrated Circuit (ASIC) or the like or a combination of the above elements, the disclosure is not limited thereto.

The logistics delivery server 120 and the electronic device 110 are connected to each other through a wired network, a wireless network, or a telecommunication network to transmit messages. The distribution server 120 has a communication unit, a storage unit and a processing unit similar to those of the electronic device 110, and details are not described herein. In the embodiment of the present disclosure, the logistics delivery server 120 stores a plurality of user purchase terms and agreed purchase materials (eg, the number of each purchase, how long after the event occurs, the goods are shipped to, etc.).

In order to provide a user-integrated and convenient shopping experience, in the disclosure, the storage unit 114 of the electronic device 110 stores an event recording application 118. When the user inputs an event record through the event recording application 118, the event recording application 118 The event record input by the user is automatically uploaded to the logistics delivery server 120, and the logistics delivery server 120 automatically generates a logistics order based on the event record, so that the logistics provider 20 delivers the goods to the user. In this way, the user can combine the two processes of managing events and online shopping to improve the convenience of the user to purchase related goods.

In detail, the event recording application 118 is installed on the electronic device 110 to provide the user with the occurrence of the recorded event and the date of occurrence. In an embodiment of the disclosure, the event recording application 118 has an input module, an event recording module, and an ordering module.

The input module provides an input interface for the user to input an event and the date of occurrence through the input interface to generate an event record. The event recording module stores the event input by the user in the storage unit 114. The event recording module also provides an event history interface, and the user can see all the recorded event records through the event history interface. The ordering module automatically instructs the communication unit 112 to transmit an event record to the logistics delivery server 120 after the user generates an event record through the input interface, without the user's instruction.

In an embodiment of the disclosure, the event recording application 118 can be an application for recording a physiological period. In this application for recording the physiological period, the input interface has a date option, and the user can input the start and end of the physiological cycle through the date option. The event history interface is displayed graphically in the beginning and end of the physiological cycle in this month.

In another embodiment of the disclosure, the event recording application 118 can be an application for managing a sports history. In this application that manages the exercise history, the input interface has a date option, and the user can enter the date of each exercise through the date option. The event history interface displays the date of the month's campaign in a graphical manner on a monthly basis.

In still another embodiment of the disclosure, the event recording application 118 may be an application for managing the replacement time of the appliance consumables, for example, recording the date of replacement of the filter of the air cleaner, the date of replacement of the filter bottle, and the like. In this appliance replacement time-of-day application, the input interface has a date option that allows the user to record the date of each filter/filter change with the date option. The event history interface displays the date of the filter/filter change in a year graphically in years.

In other embodiments of the present disclosure, the event logging application 118 can also be a comprehensive event logging application, such as an application that simultaneously records both the physiological cycle and the athletic history. In the integrated event logging application, the input interface has date options and event options. The user can enter the date of the event through the date option and record the event through the event option. The event history interface can display the events and dates of each month in a graphical manner on a monthly basis.

It should be noted that the event recording application 118 of the above different embodiments is merely an example, and the disclosure is not limited to the event recording application 118 of the above kind. In addition, the input interface of the event recording application 118 can be any different input form, and the disclosure does not limit the manner in which the input interface is presented. For example, the input interface can be a pull-down option, a slide scroll, an input field, a calendar graphical interface, etc., for the user to input the date through the touch screen of the electronic device 110. The event history interface of the event recording application 118 is not limited to the presentation manner of the above embodiment. For example, the event history interface can be displayed in units of day/week/month/year, and the event history interface can be graphically acted upon. The calendar and list of listings are presented. In addition, the event history interface can also be divided into different display interfaces according to different event types. The disclosure is not limited to the manner in which the event recording application 118 is presented.

Reference will be made to Figures 1 and 2 below to illustrate the details of the logistics order generation system of the present disclosure and its method of generating a logistics order. 2 is a flow chart of generating a logistics order according to an embodiment of the present disclosure. Before the initial execution of this logistics order generation method, the user must install the event recording application 118 on his own electronic device 110. In an embodiment of the disclosure, the event logging application 118 has a registration/login interface to prompt the user to register/log in to the logistics delivery server 120. When the user registers the account, in addition to inputting the user's account number, password, and confirming the user's legal terms, the event recording application 118 also guides the user to input the delivery information (for example, the consignee's name, address, and contact number) And inputting logistics order generation information corresponding to different event types, for example, the goods corresponding to the event record, the goods delivered after the event record is generated, the quantity of the goods, the number of automatic delivery periods, and the payment method. After the user registers/logs in to the logistics delivery server 120 through the event recording application 118, the user can begin to use the full functionality of the event recording application 118.

In another embodiment of the present disclosure, the event logging application 118 has a settings interface. The event recording application 118 generates information by guiding the user to input the distribution information and the logistics order corresponding to different event types, and stores the distribution information and the logistics order generation information in the storage unit 114. That is to say, the distribution information and the logistics order generation information may be stored in the electronic device 110 or the distribution server 120, and the disclosure is not limited thereto. Moreover, the settings and information that the user needs to fill in at the initial time can be designed according to actual needs, and the content input by the user can be modified by the event recording application 118 afterwards. The disclosure is not limited thereto.

In step S210, when the user inputs an event record through the input interface of the event recording application 118, the event recording application 118 receives the event record added by the user. At this time, the event recording application 118 stores the event record newly added by the user in the electronic device 110. Afterwards, the user can browse the event records that have been added through the event history interface of the event recording application 118, so that the user can record and manage.

While storing the event record, in step S220, the event recording application 118 automatically transmits the event record input by the user to the logistics delivery server 120. In this embodiment, the user does not need to transmit the event record to the logistics delivery server 120 through any additional button, and the event recording application 118 records the event record as a transmission event to the logistics delivery server 120. Trigger behavior. That is, when the user enters an event record and presses the save/confirm/new option to cause the input event record to be stored in the current event recording application 118, step S220 is triggered.

In step S230, when the distribution server 120 receives the event record transmitted by the event recording application 118, the logistics delivery server 120 acquires the event type of the event record, determines the logistics delivery date according to the event type, and distributes according to the logistics. The date generates a logistics order.

Specifically, in steps S220, S230, the logistics order transmitted by the logistics delivery server 120 is generated based on an order generated by the event recording application 118, or directly generated by the logistics delivery server 120. Specifically, in the case where the logistics order is generated based on the order generated by the event recording application 118, the event recording application 118 stores the shipping information input by the user and the logistics order generating information. When the user inputs the event record, the event record application 118 determines the event type corresponding to the event record, and generates an event order according to the logistics order generating information and the delivery information corresponding to the event type. And in step S220, the event recording application 118 transmits the event order to the logistics delivery server 120. The logistics delivery server 120 then retrieves the delivery information and the delivery products in the order, thereby generating a logistics order corresponding to the logistics provider.

In the case where the logistics order is generated by the logistics delivery server 120, the logistics delivery server 120 stores the user information and the logistics order generation information input when the user registers. When the event record is transmitted to the logistics delivery server 120, the logistics delivery server 120 can obtain the user identity and event type based on the source of the event record or the content entrained in the event record. For example, the logistics delivery server 120 obtains the application code by analyzing the source of the event record, thereby obtaining the identity of the user. Alternatively, the event record can be tagged with a user code or member number to enable the logistics delivery server 120 to obtain the identity of the user by event recording. After obtaining the identity of the user, the logistics delivery server 120 can find relevant information corresponding to the user identity according to the user data stored therein. Thereby, the logistics delivery server 120 searches for the logistics address and contact information corresponding to the user identity to determine the delivery information.

The logistics delivery server 120 further acquires the event type of the event record and generates a logistics order based on the information generated by the user at the time of registration. The manner in which the logistics delivery server 120 obtains the event type may be, for example, when the event recording application 118 is an application that records a single event, the processing unit 126 may obtain the event type of the event by analyzing the source of the event record. Alternatively, the event record can also carry an event code, and the logistics delivery server 120 can obtain the event type by event recording. By determining the type of event corresponding to the event record, the logistics delivery server 120 generates a logistics order based on the logistics order corresponding to the event type and the delivery information.

It should be noted that, in other embodiments of the disclosure, the event recording application 118 and the logistics delivery server 120 can also directly set preset logistics order generation information for different event types, and generate information according to preset logistics orders. Generate logistics orders. The disclosure is not limited to the manner and content of the information generated by the logistics order.

In step S230, the logistics delivery server 120 can transmit the notification message to the terminal device of the logistics provider 20 by means of email, message push, online information exchange platform or the like. Alternatively, the logistics delivery server 120 can also incorporate the shipping system of the logistics provider 20, and the logistics delivery server 120 can directly communicate the logistics order to the account or system of the logistics provider 20 in a linked or connected manner. Thereby, the logistics provider 20 can connect to the order generated by the logistics delivery server 120 through its account or distribution system. It should be noted that the disclosure does not limit the system and terminal device used by the logistics provider 20, and the manner in which the logistics delivery server 120 transmits the logistics order to the logistics provider 20 is connected in series with the logistics provider 20 according to the logistics delivery server 120. Adjusted in a manner, the disclosure is not limited thereto.

In step S240, after the logistics provider 20 receives the logistics order transmitted from the logistics delivery server 120, the logistics provider 20 can prepare the delivery according to the information of the logistics order to deliver the goods to the user.

In order to make the user easier to understand, the following is a case of concrete implementation. It should be noted that the following embodiments are merely illustrative, and the actual implementation, application range, design, and date setting are not limited thereto.

In the first embodiment of the present disclosure, the event recording application 118 is an application for recording a physiological period, and the logistics order generating information stored by the logistics delivery server 120 corresponding to the event record starting from the physiological period is: starting from the beginning of the physiological period Distribute four products in 7 days. When the user adds a record of the start of the physiological period to the event recording application 118 on October 3, 106, the event recording application 118 receives the start of the physiological period added by the user in step S210. record. In step S220, the event recording application 118 automatically transmits the event information of the beginning of the physiological period to the logistics delivery server 120. In step S230, the distribution server 120 analyzes the source of the event record, and obtains information about the user's identity, the event type is "the beginning of the physiological period", and the event date is October 3, 106. The logistics delivery server 120 generates the distribution information according to the relevant information of the user identity, and obtains the logistics order generation information according to the event type "the beginning of the physiological period" as "the delivery of the four-product product from the beginning of the physiological period", and according to the event date. For "October 3, 106", a logistics order was generated for the distribution of four products to the user-designated delivery address on October 10, 2006. Thereby, the logistics delivery server 120 will transmit the logistics order to the logistics provider, and in step S240, the logistics provider 20 will deliver the goods to the user according to the distribution logistics address displayed by the logistics order.

In the second embodiment of the present disclosure, the event recording application 118 is an application for recording the date of the movement, and the logistics order generating information stored by the logistics delivery server 120 corresponding to the event record starting from the physiological period is: after the occurrence of the sports event High-protein products are delivered in 6 hours. When the user adds a motion event record to the event recording application 118 at 6 am on October 3, 106, the event recording application 118 receives the event added by the user in step S210. recording. In step S220, the event recording application 118 automatically transmits the event information of the pen motion to the logistics delivery server 120. In step S230, the logistics delivery server 120 analyzes the source of the event record to obtain information about the user's identity, an event type of "sports", and an event date of 6 am on October 3, 106. The logistics delivery server 120 generates distribution information according to the relevant information of the user identity, and obtains the logistics order information according to the event type as "sports" to "deliver high-protein products six hours after the occurrence of the sports event", and according to the event date. At 6 o'clock on the morning of October 3, 2006, a logistics order was generated that delivered high-protein products to the user-designated delivery address at 12 noon on October 3, 2006. Thereby, the logistics delivery server 120 will transmit the logistics order to the logistics provider. In step S240, the logistics provider 20 will deliver the goods to the user according to the delivery logistics address displayed by the logistics order.

In the third embodiment of the present disclosure, the event recording application 118 is an application for recording the repair of the home appliance, and the logistics order server generates the corresponding event record of the logistics order to generate information: when the air cleaner filters After the network is replaced, the filter is automatically distributed after 90 days; when the filter element of the filter kettle is replaced, the filter element is automatically dispensed after 30 days. When the user adds an event record for replacing the filter water filter cartridge to the event recording application 118 on October 3, 106, the event recording application 118 receives the replacement filter water bottle added by the user in step S210. Event record of the filter element. In step S220, the event recording application 118 automatically transmits the event information of the pen replacement filter water filter to the logistics delivery server 120. In step S230, the logistics delivery server 120 analyzes the source of the event record to obtain related information of the user identity; the logistics delivery server 120 captures the event type entrapped in the event record as "replace the filter water filter cartridge". The event and the date of the event are October 3, 106. The logistics delivery server 120 generates the distribution information according to the information about the user's identity, and obtains the logistics order generation information according to the event type of “replacement of the filter water filter element” as “automatically distribute the filter element after the filter element of the filter water bottle is replaced after 30 days”. And according to the event date of "October 3, 106", the logistics order was generated from the delivery filter bottle on November 2, 2006 to the user-specified delivery address. Thereby, the logistics delivery server 120 will transmit the logistics order to the logistics provider, and in step S240, the logistics provider 20 will deliver the goods to the user according to the distribution logistics address displayed by the logistics order.

In summary, the present disclosure provides an event-based logistics order generation system that integrates recording events and online shopping functions. When a user records an event through an event recording application, the event recording application Event logs are automatically uploaded to the logistics delivery server. In this way, when the event occurs, the user does not need to purchase the corresponding event item in the shopping website or the physical store, and can automatically purchase and deliver the corresponding item to the delivery place designated by the user. Thereby, to provide a user-friendly shopping experience.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the novel creation, and any person skilled in the art can make some changes without departing from the spirit and scope of the novel creation. Retouching, the scope of protection of this new creation is subject to the definition of the scope of the patent application attached.

20‧‧‧Logistician
110‧‧‧Electronic devices
112‧‧‧Communication unit
114‧‧‧storage unit
116‧‧‧Processing unit
118‧‧‧Event Recording Application
120‧‧‧Logistics delivery server
S210~S240‧‧‧Steps for the production of logistics orders

1 is a block diagram of an event-based logistics order generation system according to an embodiment of the present disclosure. 2 is a flow chart of generating a logistics order according to an embodiment of the present disclosure.

Claims (8)

A logistics order generating system, comprising: an electronic device, comprising an event recording application installed in the electronic device; and a logistics delivery server connected to the electronic device and receiving information transmitted by the event recording application, wherein When the event recording application receives the event record input by the user, the event recording application automatically transmits the event record to the logistics delivery server, so that the logistics delivery server determines the logistics distribution according to the event type recorded by the event. Date, and generate logistics orders based on the logistics delivery date. The logistics order generation system of claim 1, wherein the logistics delivery server further stores the distribution information and the logistics order generation information, and the logistics delivery server further obtains the user information, the event type and the event record according to the event record. The date of the event, the logistics delivery server further obtains the delivery information corresponding to the user according to the user information, and generates information according to the logistics order corresponding to the event type and the date of the event to determine the date of delivery and the goods to be delivered. The logistics delivery server further generates the logistics order according to the delivery information, the delivery date of the logistics, and the delivered goods. The logistics order generating system of claim 2, wherein the logistics delivery server obtains the application code according to the source of the event record, and obtains the corresponding user information according to the application code. The logistics order generating system according to claim 1, wherein the event recording application further stores the distribution information and the logistics order generating information in the electronic device, and the event recording application acquires the event type of the event record. Generating an event order based on the logistics order corresponding to the event type and generating the event order, and automatically transmitting the event order including the event record to the logistics delivery server. The logistics order generating system of claim 4, wherein the logistics delivery server further determines a logistics delivery date and the delivered goods according to the event type recorded by the event and the logistics order generation information, and according to the delivery information. The delivered goods and the logistics delivery date generate the logistics order. The logistics order generating system of claim 1, wherein the logistics delivery server further transmits the logistics order to a logistics provider, so that the logistics provider delivers the delivered goods according to the logistics order. The logistics order generating system of claim 1, wherein the event type includes at least a physiological period event, a sports event, or a home appliance product maintenance event. The logistics order generating system of claim 1, wherein the event recording application further provides an event history interface to provide the user to view the event record.