WO2023243750A1

WO2023243750A1 - Electronic apparatus and database management method thereof

Info

Publication number: WO2023243750A1
Application number: PCT/KR2022/008607
Authority: WO
Inventors: 안상희; 박성진; 양아름
Original assignee: 쿠팡 주식회사
Priority date: 2022-06-14
Filing date: 2022-06-17
Publication date: 2023-12-21
Also published as: KR20230171757A; TW202349295A

Abstract

A database management method of an electronic apparatus is provided. The database management method may comprise the steps of: acquiring, from a first terminal, a status change request for a shipment; identifying, in a first database, a first order corresponding to the shipment; in response to the status change request for the shipment, identifying whether or not the first order is changed to a set status; and if the first order is changed to the set status, deleting, from the first database, data related to the first order.

Description

Electronic device and its database management method

The present disclosure relates to an electronic device and a control method for identifying data that does not need to be used in real time among data stored in a database and effectively deleting or backing up the identified data in order to maintain the data size of the database.

The trend of consumers purchasing items using online orders rather than offline orders is increasing, and accordingly, data related to orders and data on the operation of logistics centers to deliver items ordered by consumers are also increasing. However, since the capacity of data that can be stored in a database is limited, the need to manage the database more efficiently is emerging.

Meanwhile, data stored in a database can be broadly classified into cold data and hot data depending on the frequency of use or storage period. In general, cold data refers to old data that is used infrequently, and hot data refers to data that is used frequently and needs to be accessed quickly.

In order to manage a database more efficiently, technology is needed to identify data stored in the database that does not need to be used in real time and effectively delete or back up the identified data. More specifically, regarding data related to orders or data related to the operation of a logistics center that occupy a large amount of database capacity, technology is needed to newly define cold data and hot data and manage the database accordingly.

In relation to this, prior literature such as KR 10-2344661 B1 may be referred to.

The disclosed embodiments seek to provide an electronic device and a method for managing its database. More specifically, in order to maintain the data size of the database, it identifies data that does not need to be used in real time among the data stored in the database, and provides an electronic device and a control method for effectively deleting or backing up the identified data. The purpose.

The technical challenges that this embodiment aims to achieve are not limited to the technical challenges described above, and other technical challenges can be inferred from the following embodiments.

One aspect of the present disclosure is a database management method, comprising: obtaining a status change request for a shipment from a first terminal; verifying a first order corresponding to the shipment in a first database; confirming whether the first order is changed to a set state in response to a status change request for the shipment; And when the first order is changed to the set state, a database management method can be provided, including the step of deleting data related to the first order from the first database.

In addition, in one embodiment of the present disclosure, the step of checking whether the first order is changed to the set state includes loading a message about the first order into a first list; Checking the status of all shipments corresponding to the first order based on the order in which the message about the first order is loaded in the first list; and maintaining or changing the status of the first order based on the status of all shipments corresponding to the first order.

Additionally, in one embodiment of the present disclosure, the set state includes a completed state or a canceled state, and if all corresponding shipments are in the shipped state, the first order is changed to the completed state, and all corresponding shipments are in the completed state. When is in a canceled state, the first order is changed to the canceled state. A database management method may be provided.

Additionally, in an embodiment of the present disclosure, a database management method may be provided in which a request to change the status of the shipment includes a request to change the shipment status of the shipment.

In addition, in one embodiment of the present disclosure, deleting data related to the first order from the first database includes loading a message related to the first order changed to the set state into a second list; and deleting data related to at least one order included in the second list from the first database at a set time.

Additionally, in one embodiment of the present disclosure, data related to the first order includes: first order data; one or more shipment data included in the first order data; and one or more item data included in each of the one or more shipment data.

Additionally, in one embodiment of the present disclosure, deleting data related to the at least one order from the first database includes: confirming a first batch corresponding to the at least one order; and if data related to all orders corresponding to the first batch have been deleted, deleting data related to the first batch from the first database, wherein the batch includes at least one shipment ( A database management method that is a picking unit can be provided.

Additionally, in one embodiment of the present disclosure, the data related to the first batch includes first batch data; One or more batch job data included in the first batch data; One or more grouped picking data included in each of the one or more batch job data; and one or more collection data included in each of the one or more grouped collection data.

In addition, in one embodiment of the present disclosure, the database management method includes obtaining a request to change the cancellation state for the second order from the second terminal; and deleting data related to the second order from the first database.

Additionally, in one embodiment of the present disclosure, deleting data related to the first order from the first database includes: checking whether the data related to the first order needs to be backed up; And when it is confirmed that the data related to the first order is backed up, storing the data related to the first order in a second database and deleting it from the first database. A database management method can be provided. .

Additionally, in one embodiment of the present disclosure, the database management method includes obtaining a setting change request for a center management system; Checking whether the setting data of the center management system stored in the first database is backed up; And based on the confirmation result, a database management method may be provided, further comprising backing up or deleting the setting data.

Additionally, in one embodiment of the present disclosure, backing up or deleting the setting data includes, when it is confirmed that the setting data is being backed up, storing the setting data in a third database and deleting it from the first database; and deleting the setting data from the third database after a set time.

Additionally, in one embodiment of the present disclosure, the step of backing up or deleting the setting data includes deleting the setting data from the first database when it is confirmed that the setting data is being deleted. can be provided.

Another aspect of the present disclosure is a communication unit; Memory; And a control unit (controller), wherein the control unit obtains a status change request for the shipment (shipment) from the first terminal, checks the first order corresponding to the shipment in the first database, and , Check whether the first order is changed to the set state in response to a status change request for the first shipment, and when the order is changed to the set state, delete data related to the first order from the first database. An electronic device configured to do so may be provided.

Additionally, in one embodiment of the present disclosure, when checking whether the first order is changed to the set state, the control unit loads a message about the first order into the first list, and the message about the first order is stored in the first list. 1 Check the status of all shipments corresponding to the first order based on the order in which they are loaded in the list, and maintain the status of the first order based on the status of all shipments corresponding to the first order Alternatively, an electronic device configured to change may be provided.

Additionally, in one embodiment of the present disclosure, the set state includes a completed state or a canceled state, and if all corresponding shipments are in the shipped state, the first order is changed to the completed state, and all corresponding shipments are in the completed state. When is in a canceled state, the first order is changed to the canceled state, and an electronic device may be provided.

Additionally, in an embodiment of the present disclosure, an electronic device may be provided in which a request to change the status of the shipment includes a request to change the shipment to a shipped state.

In addition, in one embodiment of the present disclosure, when deleting data related to the first order from the first database, the control unit loads a message related to the first order changed to the set state into the second list, and at a set time. An electronic device configured to delete data related to at least one order included in a second list from the first database.

Additionally, in one embodiment of the present disclosure, when deleting data related to the at least one order from the first database, the control unit confirms the first batch corresponding to the at least one order, and configured to delete data associated with the first batch from the first database if all order-related data corresponding to the batch has been deleted, wherein the batch is a picking unit comprising at least one shipment. Devices can be provided.

In addition, in one embodiment of the present disclosure, the control unit is further configured to obtain a change request to a cancellation state for the second order from the second terminal and delete data related to the second order from the first database. Devices can be provided.

In addition, in one embodiment of the present disclosure, when deleting data related to the first order from the first database, the control unit determines whether the data related to the first order needs to be backed up, and the data related to the first order is If confirmed to be backed up, an electronic device configured to store data related to the first order in a second database and delete it from the first database.

In addition, in one embodiment of the present disclosure, the control unit obtains a request to change settings for the center management system, checks whether the setting data of the center management system stored in the first database is backed up, and based on the confirmation result, An electronic device further configured to back up or delete the setting data may be provided.

Additionally, in one embodiment of the present disclosure, when backing up or deleting the setting data, if it is confirmed that the setting data is being backed up, the control unit stores the setting data in a third database and deletes it from the first database, An electronic device configured to delete the setting data from the third database after a set time period may be provided.

Additionally, in one embodiment of the present disclosure, the control unit may provide an electronic device configured to delete the setting data from the first database when it is confirmed that the setting data is being deleted when backing up or deleting the setting data. You can.

Another aspect of the present disclosure may provide a computer-readable recording medium on which a program for implementing a method performed by an electronic device is recorded.

Specific details of other embodiments are included in the detailed description and drawings.

If you follow the proposed embodiment, one or more of the following effects can be expected.

According to an embodiment of the present specification, with respect to data related to orders or data related to the operation of a logistics center that occupy a large capacity of the database, cold data and hot data are newly defined and the database is managed accordingly, thereby reducing the size of the database. can be reduced.

In addition, when status change requests for multiple shipments are obtained simultaneously, the process of changing the status of each shipment, loading a list of messages about the corresponding order, and checking the status of the order is sequentially performed. The problem of concurrency can be solved by improving reliability of the order status.

In addition, by storing log data in a database based on NoSQL (not only SQL (structured query language)), storage size can be reduced and system flexibility can be improved.

The effect of the invention is not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description of the claims.

1 shows a system according to one embodiment.

Figure 2 shows a data structure according to one embodiment.

3A and 3B are diagrams for explaining a process in which an electronic device manages a database according to an embodiment.

FIGS. 4A to 4C are diagrams illustrating a process in which an electronic device checks whether an order is changed to a set state in response to a status change request for a shipment, according to an embodiment.

FIGS. 5A and 5B are diagrams illustrating a process in which an electronic device checks whether an order is changed to a set state in response to a status change request for a shipment, according to an embodiment.

FIG. 6 is a diagram illustrating a process by which an electronic device deletes order-related data from a database, according to an embodiment.

FIG. 7 is a diagram illustrating a process in which an electronic device manages a database according to an embodiment.

Figure 8 shows a flowchart of a method for managing a database of an electronic device according to an embodiment.

Figure 9 shows a block diagram of an electronic device according to an embodiment.

The terms used in the embodiments are general terms that are currently widely used as much as possible while considering the functions in the present disclosure, but this may vary depending on the intention or precedent of a person working in the art, the emergence of new technology, etc. In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the relevant description. Therefore, the terms used in this disclosure should be defined based on the meaning of the term and the overall content of this disclosure, rather than simply the name of the term.

When it is said that a part "includes" a certain element throughout the specification, this means that, unless specifically stated to the contrary, it does not exclude other elements but may further include other elements.

The expression “at least one of a, b, and c” used throughout the specification means ‘a alone’, ‘b alone’, ‘c alone’, ‘a and b’, ‘a and c’, ‘b and c ', or 'all of a, b, and c'.

The “electronic device” or “terminal” referred to below may be implemented as a computer or portable terminal that can connect to a server or other terminal through a network. Here, the computer includes, for example, a laptop, desktop, laptop, etc. equipped with a web browser, and the portable terminal is, for example, a wireless communication device that guarantees portability and mobility. , all types of communication-based terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), and LTE (Long Term Evolution), smartphones, tablet PCs, etc. It may include a handheld-based wireless communication device.

Below, with reference to the attached drawings, embodiments of the present disclosure will be described in detail so that those skilled in the art can easily practice them. However, the present disclosure may be implemented in many different forms and is not limited to the embodiments described herein.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

1 shows a system according to one embodiment.

Referring to FIG. 1 , the system may include at least one of an electronic device 100, an operator terminal 120, a user terminal 140, a database 160, and a network 180. Meanwhile, the system shown in FIG. 1 shows only components related to this embodiment. Accordingly, those skilled in the art can understand that other general-purpose components may be included in addition to the components shown in FIG. 1.

The electronic device 100 can manage the status of order-related data or setting data of the center management system and delete them from the database 160 based on each status. For example, the electronic device 100 may manage the status of the order based on the status of the shipment and delete data related to the order in the canceled or completed status from the database.

The worker terminal 120 is a terminal used by a worker, and the worker can use the worker terminal 120 to view and manage data stored in the database 160. For example, a worker can use the worker terminal 120 to change a shipment to a shipped state or change an order to a canceled state.

The user terminal 140 is a terminal used by each user, and the users can access services provided by the network 180 using their respective terminals. For example, the electronic device 100 may provide the user terminal 140 with an application for providing information related to ordering various items, and the user may purchase various items using the application installed on the user terminal 140. You can order.

The database 160 is a data structure implemented in a predetermined storage space, and functions such as storing, searching, deleting, editing, or adding data can be freely performed. For example, the database 160 may include fields or components for processing functions such as storing, searching, deleting, editing, or adding data. Additionally, the database 160 may store data related to orders or setting data of a center management system. Meanwhile, FIG. 1 shows the database 160 as existing outside the electronic device 100, but this is only an example, and the database 160 may be included in the electronic device 100.

The worker terminal 120, the user terminal 140, the database 160, and the electronic device 100 may communicate with each other within the network 180. The network 180 includes a local area network (LAN), a wide area network (WAN), a value added network (VAN), a mobile radio communication network, a satellite communication network, and their respective networks. It is a comprehensive data communication network that includes a combination and allows each network constituent shown in FIG. 1 to communicate smoothly with each other, and may include wired Internet, wireless Internet, and mobile wireless communication network. Wireless communications include, for example, wireless LAN (Wi-Fi), Bluetooth, Bluetooth low energy, ZigBee, WFD (Wi-Fi Direct), UWB (ultra wideband), and infrared communication (IrDA, infrared Data Association). ), NFC (Near Field Communication), etc., but are not limited thereto.

Figure 2 shows a data structure according to one embodiment. At this time, the line connecting the data shown in FIG. 2 indicates that data connected by one end line may include one or more data connected by three end lines.

According to one embodiment, the order data 200 is data corresponding to the order of one or more items that the user wishes to purchase through the user terminal, such as data for identifying the order, data on the characteristics of the order, or the user who requested the order. It may include data about, etc. For example, the order data 200 may include data related to the delivery of an order, data related to the packing of an order, or data regarding the status of an order.

According to one embodiment, the shipment data 210 is data corresponding to a shipment, which is a unit for delivering one or more items, and is data for identifying the shipment or data related to the items included in the shipment. It may include etc. When a user orders multiple items, one or more shipment data may be generated to efficiently pick the multiple items at the distribution center, and the multiple items may be picked and packed based on one or more shipment data. there is.

According to one embodiment, the shipment data 210 may include data about the SKU (Stock Keeping Unit) of the item ordered by the customer. In order to ship each item from the center, the SKU for the item is picked and picked. Procedures for packaging SKUs may be required. Additionally, packaging can be performed after selectively redistributing the picked SKUs. In order to effectively collect, redistribute, and package, the shipment data 210 is managed based on the orders entered into the center, and processed at once to effectively collect, redistribute, and package based on the corresponding shipment data 210. To derive a set of shipments, it is necessary to continuously search the shipment data 210 assigned to the center. Therefore, in order to effectively perform such a search, the database storing the shipment data 210 that needs to be processed must be accessible quickly, and for this, there is a need to prevent the database size from becoming larger than necessary.

According to one embodiment, the item data 220 is data corresponding to one or more items that the user wishes to purchase through the user terminal, such as data for identifying the item, data on the characteristics of the item, or data on the selection of the item. It may include etc. For example, the item data 220 may include data about the quantity of the item ordered by the user, data about the inventory quantity of the item in the distribution center, or data about the SKU, which is an item storage unit in which the item is stored. there is.

According to one embodiment, batch data 230 is data corresponding to a batch, which is a unit for a picker to collectively collect items from a distribution center, data for identifying the batch, and items included in the batch. It may include data about, data about the picker assigned to the batch, or data about the tote set for use by the picker assigned to the batch. When a picker is assigned a first batch, the picker may perform a picking task by storing a plurality of items included in the first batch in at least one tote. At this time, the tote set is a set of totes containing one or more items managed in one arrangement, and may include a single tote or a plurality of totes, depending on the characteristics of the items included in the arrangement.

According to one embodiment, the batch job data 240 is work data for each of one or more totes corresponding to the batch, including data for identifying the batch job, status data of the tote, destination data of the tote, and task of the tote. It may include location data or tote's next action data, etc.

According to one embodiment, the picking data 260 is data about the picking of items in a distribution center, including location data of the items in the distribution center and information about the worker (i.e., picker) who performs the picking. It may include data or data about the picking schedule (picking order). At this time, picking may refer to the process of confirming an order related to the purchase of a specific item from the orderer, then searching and searching for the item within the distribution center and preparing for delivery of the item.

According to one embodiment, the grouped picking data 250 is data that groups the picking data 260 in consideration of the characteristics, loading location, or inventory quantity of the picked item, and may include one or more picking data 260. You can.

Meanwhile, the above-described names of data, inclusion relationships between data, and specific examples included in the data are only one embodiment, and the present disclosure includes names of data, inclusion relationships between data, and specific examples included in the data that are different from those described above. It is obvious to those skilled in the art that this disclosure can be implemented.

The first database 310 is a structure in which various data, such as order-related data or setting data of a center management system, is stored, and may include a relational database (RDB).

The second database 320 is a database that exists separately from the first database 310, and may include S3, MOS, Elastic search, or Cassandra depending on its purpose, but is not limited thereto. According to one embodiment, data that needs to be backed up among data deleted from the first database 310 may be stored in the second database 320.

The terminal 330 represents an electronic device that exists outside the electronic device 100 and may include the worker terminal 120 or the user terminal 140 of FIG. 1 .

In step S340, the electronic device 100 may obtain order data from the terminal 330. According to one embodiment, a user may order one or more items using the terminal 330, and the terminal 330 may transmit order data entered by the user to the electronic device 100.

In step S345, the electronic device 100 may store order data obtained from the terminal 330 in the first database 310.

In step S350, the electronic device 100 may obtain a status change request for the shipment from the terminal 330. At this time, the status of the shipment may include a waiting state, a shipping state, and a cancellation state. According to one embodiment, the shipping status of the shipment indicates that the items included in the corresponding shipment have been packaged and delivered outside the distribution center, and the waiting status of the shipment indicates that the items included in the corresponding shipment have been shipped outside the distribution center. It indicates that it is before delivery, and the cancellation status of the shipment may indicate that delivery of the items included in the shipment has been cancelled.

According to one embodiment, as a specific shipment is shipped, the terminal 330 may receive an input from an operator that changes the shipment from the waiting state to the shipping state, and changes the shipment from the waiting state to the shipping state. A request may be transmitted to the electronic device 100.

According to one embodiment, the terminal 330 may receive a user's input to cancel the order of all items or some items. For example, when the user cancels the order for all items, the terminal 330 may transmit to the electronic device 100 a request to change the status of the order or all shipments corresponding to the order from the waiting state to the canceled state. You can. Alternatively, when the user cancels the order of some items, the terminal 330 may transmit a request to change the shipment corresponding to some items from the waiting state to the canceled state to the electronic device 100.

According to one embodiment, the terminal 330 may receive an operator's input to cancel an order for all items or an order for some items. For example, when the worker cancels the order for all items, the terminal 330 transmits a request to change the order status and all shipments corresponding to the order from the waiting state to the canceled state to the electronic device 100. You can. Alternatively, when the worker cancels the order of some items, the terminal 330 may transmit a request to change the shipment corresponding to some items from the waiting state to the canceled state to the electronic device 100.

According to one embodiment, in response to a status change request for a shipment obtained from the terminal 330, the electronic device 100 may change the status of the corresponding shipment. For example, when the electronic device 100 obtains a request from the terminal 300 to change the shipment to the shipped state, the electronic device 100 can change the shipment from the standby state to the shipped state. Alternatively, when the electronic device 100 obtains a request to change the shipment to the canceled state from the terminal 300, the electronic device 100 may change the shipment from the waiting state to the canceled state. However, this is only an example, and the state of the shipment may be changed by another external device other than the electronic device 100. Meanwhile, in one embodiment, some of a plurality of items included in one order may be cancelled. In this case, the electronic device 100 may process cancellation of some items the same as shipping of some items to determine cold data.

In step S355, the electronic device 100 can confirm the order corresponding to the shipment. According to one embodiment, the electronic device 100 may check the order corresponding to the shipment for which the terminal 330 has requested a status change.

In step S360, the electronic device 100 may load a message about an order corresponding to a shipment requesting a status change into a first list (status change queue). According to one embodiment, the electronic device 100 may load a message about an order into the first list based on a distributed messaging system based on a publish-subscribe model. For example, whenever the electronic device 100 obtains a request to change the status of a shipment, a Kafka message containing data about the order corresponding to the shipment is issued and sent to the broker of the Kafka system. It can be loaded into the first list corresponding to .

According to another embodiment, the electronic device 100 may load order data corresponding to a shipment requesting a status change into the first list. For example, the electronic device 100 may move order data corresponding to a shipment requesting a status change within the first database 310 to the first list.

In step S365, the electronic device 100 may check whether the order is changed to the set state. At this time, the status of the order may include a waiting status, an in progress status, a completion status, and a cancellation status, and the set status may include a completion status or a cancellation status.

According to one embodiment, the waiting state of an order may indicate that all shipments corresponding to the order are in a waiting state, and the in-process state of an order may indicate that one or more shipments corresponding to the order are in a shipping state. Additionally, the completion status of an order may indicate that all shipments corresponding to the order are in a shipped state, and the cancellation status of an order may indicate that all shipments corresponding to the order are in a canceled state.

According to one embodiment, whenever the electronic device 100 obtains a request to change the status of a shipment, the electronic device 100 sends a message corresponding to the order based on the order in which the message about the order is loaded in the first list. You can check the status of all ships. For example, each time the electronic device 100 obtains a status change request for a shipment, the electronic device 100 queries the first list and places an order based on the order in which Kafka messages are loaded into the first list. You can check whether all corresponding shipments are in shipped or canceled status. At this time, the electronic device 100 can quickly search all shipments corresponding to the order using a key (or matched index) linked between the order and the shipment. This will be described in more detail with reference to FIGS. 4A to 4C.

According to one embodiment, the electronic device 100 may maintain or change the status of an order based on the status of all shipments corresponding to the order. For example, if all shipments corresponding to an order are in a shipped state, the electronic device 100 may change the order to a completed state. Alternatively, if all shipments corresponding to an order are in a canceled state, the electronic device 100 may change the order to a canceled state. If some of the shipments corresponding to the order are in a shipped state, the electronic device 100 may maintain the corresponding order in an in-progress state. However, this is only an example, and the order status may be changed by another external device other than the electronic device 100.

In step S370, the electronic device 100 may load a message regarding an order that has been changed to the set state into the second list. According to one embodiment, the electronic device 100 may load a message about an order into a second list (cold data list) based on a distributed messaging system based on a publish-subscribe model. For example, whenever an order in the completed or canceled state is confirmed, a Kafka message containing data about the order may be issued and loaded into a second list corresponding to a broker in the Kafka system.

According to another embodiment, the electronic device 100 may load order data changed to the set state into the second list. For example, the electronic device 100 may move order data that has been changed to the state set in the first database 310 from the first list to the second list.

In step S375, the electronic device 100 may check whether data related to the order loaded on the second list needs to be backed up. According to one embodiment, the electronic device 100 stores the second database 320 before deleting data related to an order in a completed or canceled state from the first database 310 based on a worker's input or a preset condition. You can check whether to back up or not.

For example, if it is necessary to determine work history such as where the item was picked in order to solve a problem situation such as remaining stock of a shipped or canceled item, the worker may store the picking data, etc. in a second database (320 ) can be entered into the terminal 330 to back up. Accordingly, the electronic device 100 can confirm that picking data, etc., should be backed up to the second database 320 based on the operator's input. Alternatively, the electronic device 100 may check whether to back up order-related data based on preset conditions regarding various characteristics, such as the type of data or the period for which the data is stored in the first database 310.

In step S380, if it is confirmed that order-related data needs to be backed up, the electronic device 100 may store the order-related data in the second database 320. At this time, the data stored in the second database 320 can be searched using various data, such as a waybill ID that corresponds one-to-one to the shipment, as a key value. For example, if a worker wants to check the work history for a specific shipment, if he/she wants to check data after the order has been shipped, or if exception processing is required for an order that has been shipped, the worker must check the shipment identification data or Data stored in the second database 320 can be confirmed based on the waybill identification data.

In step S385, the electronic device 100 may delete data related to at least one order included in the second list from the first database 310 at set times. According to one embodiment, the electronic device 100 may check orders loaded on the second list at set times and delete data related to the confirmed orders from the first database 310. At this time, the data related to the order may include order data, one or more shipment data included in the order data, and one or more item data included in each of the one or more shipment data.

According to one embodiment, the electronic device 100 may check whether data related to the arrangement can be deleted each time an order loaded on the second list is checked. For example, the electronic device 100 checks the batch corresponding to at least one order included in the second list every time it checks an order loaded in the second list, and collects data related to all orders corresponding to the confirmed batch. If is deleted, data related to the placement may be deleted from the first database 310. At this time, the data related to the batch includes one or more batch job data included in the batch data, one or more grouped picking data included in each of the one or more batch job data, and one or more picking data included in each of the one or more grouped picking data. It can be included.

Figure 4a shows an example of order data and shipment data included in the order data. According to one embodiment, the first order data 400 may include first shipment data 410, second shipment data 420, and third shipment data 430. This may mean that a plurality of items included in the first order are divided into three

shipments

410, 420, and 430 and delivered. Meanwhile, the first order data 400 represents data corresponding to the first order, and the first shipment data 410, the second shipment data 420, and the third shipment data 430 each represent the first order. Indicates data corresponding to a shipment, a second shipment, and a third shipment.

Figures 4b and 4c show an example of a first list 440 or status change queue loaded with messages about orders.

According to one embodiment, when the electronic device 100 obtains a state change request for the first shipment, the electronic device 100 changes the state of the first shipment and changes the state of the first shipment to the first shipment. The order-related message 450 can be loaded into the first list 440. Thereafter, the electronic device 100 may check the status of all shipments corresponding to the first order based on the order in which the message 450 regarding the first order was loaded in the first list 440.

For example, when shipping of the first shipment is completed and the electronic device 100 obtains a request to change the first shipment from the standby state to the shipping state, the electronic device 100 changes the first shipment to the shipping state. The status can be changed to shipped, and the message 450 regarding the first order corresponding to the first shipment can be loaded into the first list 440. Thereafter, the electronic device 100 checks the status of all ships (first shipment, second shipment, and third shipment) corresponding to the first order, and determines that the first shipment is in the factory state and the second shipment is in the factory state. It can be confirmed that the ment and the 3rd shipment are in a standby state. Accordingly, the electronic device 100 may change the first order from the waiting state to the in-progress state.

According to one embodiment, the electronic device 100 may simultaneously obtain a status change request for the second shipment and a status change request for the third shipment. At this time, the electronic device 100 changes the status of one or more ships whose status has changed, loads a message about the order corresponding to the shipment into the list, and maintains and changes the status of the order. The process can be performed sequentially.

For example, the electronic device 100 may simultaneously obtain a request to change the second shipment from the standby state to the shipping state and a request to change the third shipment from the standby state to the shipping state. Among the second and third shipments, the electronic device 100 may first perform the process of changing the status of the third shipment, loading a list of messages about the corresponding order, and checking the status of the order. . That is, the electronic device 100 may change the status of the third shipment to the shipped state and load the message 460 regarding the first order corresponding to the third shipment into the first list 440. Thereafter, the electronic device 100 may check the status of all shipments corresponding to the first order based on the order in which the message 460 regarding the first order was loaded in the first list 440. At this time, since the state of the second shipment is before being changed to the shipping state, the electronic device 100 can confirm that the first and third shipments are in the shipping state and the second shipment is in the standby state. Accordingly, the electronic device 100 may maintain the first order in an in-progress state.

The electronic device 100 first performs the process of changing the status of the shipment, loading the list of messages related to the corresponding order, and checking the status of the order with respect to the third shipment, and then performs the same process with respect to the second shipment. You can. That is, the electronic device 100 may change the status of the second shipment to the shipped state and load the message 470 regarding the first order corresponding to the second shipment into the first list 440. Thereafter, the electronic device 100 may check the status of all shipments corresponding to the first order based on the order in which the message 470 regarding the first order was loaded in the first list 440. At this time, since the status of the third shipment has been changed to the factory state, the electronic device 100 can confirm that the first shipment, the second shipment, and the third shipment are all in the factory state. Accordingly, the electronic device 100 may change the first order from the in-progress state to the completed state.

In this way, when the electronic device 100 simultaneously obtains a status change request for the second shipment and a status change request for the third shipment, the status change of the shipment and the corresponding order are requested for each shipment. The problem of concurrency can be solved by sequentially performing the process of loading the list of related messages and checking the status of the order. In other words, even if the shipment of shipments occurs at the same time, the reliability of confirmation of shipment of all shipments included in the order can be improved by maintaining or changing the status of the order based on the order in which they are loaded on the list.

Meanwhile, Figures 4b and 4c show that the order-related message includes only data about the status of the order, but data about the progress of the order status may also be included. For example, when the electronic device 100 obtains a status change request for the first shipment, it may change the order from the waiting state to the in-progress state and store 1/3 or 33.3% as a progress value. Additionally, when the electronic device 100 obtains a status change request for the third shipment, it can store 2/3 or 66.7% as a progress value while maintaining the order in the in-progress state. When the electronic device 100 obtains a status change request for the second shipment, it may change the order from the in-process state to the completed state and store 1 or 100% as a progress value. At this time, instead of checking the status of all shipments corresponding to the first order, the electronic device 100 may change or maintain the status of the order based on the status and progress value of the existing order.

Figure 5a shows an example of order data and shipment data included in the order data. According to one embodiment, the first order data 500 may include first shipment data 510, second shipment data 520, and third shipment data 530. This may mean that a plurality of items included in the first order are divided into three

shipments

510, 520, and 530 and delivered. Meanwhile, the first order data 500 represents data corresponding to the first order, and the first shipment data 510, the second shipment data 520, and the third shipment data 530 each represent the first order. Indicates data corresponding to a shipment, a second shipment, and a third shipment.

Figure 5b shows an example of a first list 540 or status change queue loaded with messages about orders.

According to one embodiment, when a user cancels an order for all items, the electronic device 100 may obtain an order status change request or a shipment status change request.

For example, the electronic device 100 may obtain a request to change all ships (first shipment, second shipment, and third shipment) corresponding to the first order from the waiting state to the canceled state. . The electronic device 100 may change the status of the first shipment, the second shipment, and the third shipment to the canceled state, and load the message 550 regarding the first order into the first list 540. . Thereafter, the electronic device 100 may check the status of all shipments corresponding to the first order and confirm that the first shipment, the second shipment, and the third shipment are in a canceled state. Accordingly, the electronic device 100 may change the first order from the waiting state to the canceled state.

Alternatively, the electronic device 100 may obtain a request to change the status of the first order from the waiting state to the canceled state. At this time, the electronic device 100 may directly load the message regarding the first order into the second list (cold data list) instead of loading it into the first list 540.

According to one embodiment, when the user cancels the order of some items, the electronic device 100 may obtain a request to change the shipment corresponding to some items from the waiting state to the canceled state. For example, the electronic device 100 may obtain a request to change the first shipment from the standby state to the cancel state. The electronic device 100 may change the first shipment to a canceled state and load a message 550 regarding the first order corresponding to the first shipment into the first list 540. Afterwards, the electronic device 100 checks the status of all ships (first shipment, second shipment, and third shipment) corresponding to the first order, and determines that the first shipment is in a canceled state and the second shipment is in a canceled state. It can be confirmed that the ment and the 3rd shipment are in a standby state. Accordingly, the electronic device 100 may change the first order from the waiting state to the in-progress state.

According to one embodiment, the electronic device 100 may load a message about an order that has been changed to a completed state or a canceled state into the second list 600 or the cold data list. For example, the electronic device 100 may confirm that the fourth order has changed to the completed or canceled state and load the message 680 regarding the fourth order into the second list 600. Thereafter, the electronic device 100 confirms that the first order, second order, and third order have changed to the completed or canceled state, and sends a message 620 regarding the first order and a message 640 regarding the second order. And a message 660 regarding the third order may be loaded into the second list 600.

According to one embodiment, the electronic device 100 may delete data related to at least one order included in the second list 600 from the first database every set time. For example, the electronic device 100 may send a message 620 about the first order, a message 640 about the second order, and a message 660 about the third order loaded on the second list 600 at a set time. ) and the message 680 regarding the fourth order can be checked, and data related to the first to fourth orders can be deleted. At this time, the data related to the order may include order data, one or more shipment data included in the order data, and one or more item data included in each of the one or more shipment data.

Meanwhile, the electronic device 100 may check whether to back up data related to at least one order before deleting data related to at least one order included in the second list 600 at every set time. For example, the electronic device 100 may determine whether to back up data related to at least one order included in the second list 600 based on the operator's input or preset conditions, and determines whether to back up data related to at least one order included in the second list 600. Data related to the order may be stored in a second database.

FIG. 7 is a diagram illustrating a process in which an electronic device manages a database according to an embodiment. Content that overlaps with FIGS. 3A and 3B will be briefly described or omitted.

In step S740, the electronic device 100 may obtain first setting data of the center management system from the terminal 730. At this time, the warehouse management system (WMS) is a system for managing tasks such as warehousing, stacking, storage, inventory allocation, picking, or shipping that occur at a fulfillment center (FC) through convenient and detailed functions. It can mean. In addition, the setting data of the center management system refers to specific setting values for operating a logistics center, and includes data about the number of ships included in one batch or the location of a workbench for packaging items included in a specific batch. It can be included.

In step S745, the electronic device 100 may store the first setting data of the center management system obtained from the terminal 730 in the first database 710.

In step S750, the electronic device 100 may obtain a request to change the settings of the center management system from the terminal 730. According to one embodiment, when the worker wants to change the settings of the center management system, the worker can input newly set values (second setting data of the center management system) into the terminal 730, and the terminal 730 The received second setting data may be transmitted to the electronic device 100.

In step S755, the electronic device 100 may store the second setting data of the center management system obtained from the terminal 730 in the first database 710.

In step S760, the electronic device 100 may check whether backup of the first setting data is necessary. According to one embodiment, the electronic device 100 stores unused setting data of the center management system in the second database 720 before deleting it from the first database 710 based on the operator's input or preset conditions. You can check whether to back up or not.

For example, when it is necessary to determine the creation history of a batch or when there is a setting that receives many inquiries in operating a logistics center, the worker requests the terminal 730 to back up related data to the second database 720. You can enter . Accordingly, the electronic device 100 can confirm that related data should be backed up to the second database 720 based on the operator's input. Alternatively, the electronic device 100 may check whether to back up order-related data based on preset conditions regarding various characteristics, such as the type of data or the period for which the data is stored in the first database 710.

In step S765, if it is confirmed that the first setting data of the center management system needs to be backed up, the electronic device 100 may store the first setting data of the center management system in the second database 720.

In step S770, the electronic device 100 may delete first setting data of the center management system that is no longer used from the first database 710.

Figure 8 shows a flowchart of a method for managing a database of an electronic device according to an embodiment. The foregoing description may apply to overlapping content.

In step S800, the electronic device may obtain a status change request for the shipment from the first terminal.

According to one embodiment, as a specific shipment is shipped, the electronic device may obtain a request to change the shipment from the standby state to the shipped state from the first terminal. Alternatively, as the user cancels the order for all items, the electronic device may obtain a request from the first terminal to change the status of the order or all shipments corresponding to the order from the waiting state to the canceled state. As the user cancels the order of some items, the electronic device may obtain a request from the first terminal to change the shipment corresponding to some items from the waiting state to the canceled state.

In step S820, the electronic device may check the first order corresponding to the shipment in the first database.

In step S840, the electronic device may check whether the first order is changed to the set state in response to a status change request for the shipment.

According to one embodiment, the electronic device loads a message about a first order into a first list, and based on the order in which the message about the first order is loaded into the first list, all messages corresponding to the first order are stored. You can check the status of the shipment. Thereafter, the electronic device may maintain or change the status of the first order based on the status of all shipments corresponding to the first order.

For example, if all shipments corresponding to the first order are in a shipped state, the electronic device may change the first order from the in-progress state to the completed state. Alternatively, if all shipments corresponding to the first order are in a canceled state, the electronic device may change the first order from a progress state to a cancel state. If some of the shipments corresponding to the first order are in a shipped state, the electronic device may maintain the first order in an in-progress state.

According to one embodiment, the set state may include a completed state or a canceled state.

In step S860, when the first order is changed to the set state, the electronic device may delete data related to the first order from the first database.

According to one embodiment, the electronic device may load a message related to the first order that has been changed to a set state into a second list, and delete data related to at least one order included in the second list from the first database at each set time. there is. For example, the electronic device may check at least one order included in the second list at a set time and delete data related to one order from the first database. At this time, the data related to the order may include order data, one or more shipment data included in the order data, and one or more item data included in each of the one or more shipment data.

According to one embodiment, whenever the electronic device checks at least one order included in the second list, it checks the first batch corresponding to the at least one order, and stores all orders corresponding to the first batch. When related data has been deleted, data related to the first batch may be deleted from the first deletion database. At this time, it may include one or more batch job data included in the batch data, one or more grouped picking data included in each of the one or more batch job data, and one or more picking data included in each of the one or more grouped picking data.

According to one embodiment, before deleting data related to the first order from the first database, the electronic device determines whether the data related to the first order needs to be backed up, and it is confirmed that the data related to the first order is backed up. In this case, data related to the first order may be stored in the second database and deleted from the first database. For example, based on an operator's input or a preset condition, the electronic device may check whether to back up data related to an order in a completed or canceled state to a second database before deleting it from the first database.

According to one embodiment, the electronic device obtains a setting change request for the center management system, checks whether setting data of the center management system stored in the first database is backed up, and based on the verification result, backs up or It can be deleted.

For example, if it is confirmed that the setting data is being backed up, the electronic device may store the setting data in a third database and delete it from the first database, and after a set time, the setting data may be deleted from the third database. Alternatively, when it is confirmed that the setting data is being deleted, the electronic device may delete the setting data from the first database.

According to one embodiment, in order to reduce storage size and improve system flexibility by using various databases according to data characteristics, the electronic device may store log data in a database based on NoSQL (not only structured query language). Accordingly, in response to the user's read request, the request is sent to an appropriate database among several databases, so the user can obtain the same technical effect as reading data from one database.

FIG. 9 shows a block diagram of an electronic device 100 according to an embodiment.

According to one embodiment, the electronic device 100 may include a communication device 920, a memory 940, and a controller 960. The electronic device 100 shown in FIG. 9 shows only components related to this embodiment. Accordingly, those skilled in the art can understand that other general-purpose components may be included in addition to the components shown in FIG. 9. Since the electronic device 100 may include content related to the above-described server, description of overlapping content will be omitted. In an embodiment, the communication unit may include one or more transceivers. Additionally, in an embodiment, the control unit may include one or more processors.

The communication unit 920 is a device for performing wired/wireless communication and can communicate with external electronic devices. The external electronic device may be a terminal or server. In addition, communication technologies used by the communication unit 920 include Global System for Mobile communication (GSM), Code Division Multi Access (CDMA), Long Term Evolution (LTE), 5G, Wireless LAN (WLAN), and Wireless-Fidelity (Wi-Fi). ), Bluetooth, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), ZigBee, NFC (Near Field Communication), etc.

The control unit 960 can control the overall operation of the electronic device 100 and process data and signals. The control unit 960 may be composed of at least one hardware unit. Additionally, the control unit 960 may operate by one or more software modules generated by executing program codes stored in the memory 940. The control unit 960 may include a processor and a memory, and the processor may execute program codes stored in the memory to control the overall operation of the electronic device 100 and process data and signals. Additionally, in an embodiment, the control unit 960 may include at least one processor.

The control unit 960 obtains a status change request for the shipment from the first terminal, checks the first order corresponding to the shipment in the first database, and places the first order in response to the status change request for the first shipment. It is checked whether the order is changed to the set state, and if the order is changed to the set state, data related to the first order can be deleted from the first database.

The electronic device according to the above-described embodiments includes a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a touch panel, keys, buttons, etc. It may include the same user interface device, etc. Methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program instructions executable on the processor. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disk, hard disk, etc.) and optical read media (e.g., CD-ROM). ), DVD (Digital Versatile Disc), etc. The computer-readable recording medium is distributed among computer systems connected to a network, so that computer-readable code can be stored and executed in a distributed manner. The media may be readable by a computer, stored in memory, and executed by a processor.

This embodiment can be represented by functional block configurations and various processing steps. These functional blocks may be implemented in various numbers of hardware or/and software configurations that execute specific functions. For example, embodiments include integrated circuit configurations such as memory, processing, logic, look-up tables, etc. that can execute various functions under the control of one or more microprocessors or other control devices. can be hired. Similar to how the components can be implemented as software programming or software elements, the present embodiments include various algorithms implemented as combinations of data structures, processes, routines or other programming constructs, such as C, C++, Java ( It can be implemented in a programming or scripting language such as Java), assembler, etc. Functional aspects may be implemented as algorithms running on one or more processors. Additionally, this embodiment may employ conventional technologies for electronic environment settings, signal processing, and/or data processing. Terms such as “mechanism,” “element,” “means,” and “configuration” may be used broadly and are not limited to mechanical and physical configurations. The term may include the meaning of a series of software routines in connection with a processor, etc.

The above-described embodiments are merely examples and other embodiments may be implemented within the scope of the claims described below.

Claims

A method for managing a database of an electronic device, comprising:

Obtaining a status change request for a shipment from a first terminal;

verifying a first order corresponding to the shipment in a first database;

confirming whether the first order is changed to a set state in response to a status change request for the shipment; and

When the first order is changed to the set state, a database management method comprising deleting data related to the first order from the first database.
The method of claim 1, wherein the step of checking whether the first order is changed to the set state is,

loading a message about the first order into a first list;

Checking the status of all shipments corresponding to the first order based on the order in which the message about the first order is loaded in the first list; and

A database management method comprising maintaining or changing the status of the first order based on the status of all shipments corresponding to the first order.
According to clause 2,

The set state includes a completed state or a canceled state,

If all corresponding shipments are in the shipped status, the first order is changed to the completed status,

If all corresponding shipments are in a canceled state, the first order is changed to the canceled state.
The method of claim 1, wherein the status change request for the shipment is,

A database management method including a request to change the shipment status of the shipment.
The method of claim 1, wherein deleting data related to the first order from the first database comprises:

Loading a message about the first order changed to the set state into a second list; and

A database management method comprising deleting data related to at least one order included in a second list from the first database at a set time.
The method of claim 1, wherein the data related to the first order is:

first order data;

one or more shipment data included in the first order data; and

A database management method including one or more item data included in each of the one or more shipment data.
The method of claim 5, wherein deleting data related to the at least one order from the first database comprises:

identifying a first batch corresponding to the at least one order; and

If data related to all orders corresponding to the first batch have been deleted, deleting data related to the first batch from the first database,

A database management method wherein a batch is a picking unit containing at least one shipment.
The method of claim 7, wherein data related to the first batch is:

first batch data;

One or more batch job data included in the first batch data;

One or more grouped picking data included in each of the one or more batch job data; and

A database management method comprising one or more collection data included in each of the one or more grouped collection data.
The method of claim 1, wherein the database management method includes:

Obtaining a request to change the cancellation status for the second order from the second terminal; and

Database management method further comprising deleting data related to the second order from the first database.
The method of claim 1, wherein deleting data related to the first order from the first database comprises:

determining whether data related to the first order needs to be backed up; and

When it is confirmed that data related to the first order is backed up, storing the data related to the first order in a second database and deleting it from the first database.
The method of claim 1, wherein the database management method includes:

Obtaining a setting change request for the center management system;

Checking whether the setting data of the center management system stored in the first database is backed up; and

Based on the confirmation result, the database management method further includes backing up or deleting the setting data.
The method of claim 11, wherein backing up or deleting the setting data includes:

If it is confirmed that the setting data is backed up, storing the setting data in a third database and deleting it from the first database; and

A database management method comprising deleting the setting data from the third database after a set time.
The method of claim 11, wherein backing up or deleting the setting data includes:

When it is confirmed that the setting data is to be deleted, a database management method comprising deleting the setting data from the first database.
A non-transitory computer-readable recording medium that records a program for executing the method of claim 1 on a computer.
As an electronic device,

Ministry of Communications;

Memory; and

It includes a controller, wherein the controller includes:

Obtaining a status change request for a shipment from the first terminal,

Checking the first order corresponding to the shipment in the first database,

Verify that the first order is changed to the set state in response to a status change request for the first shipment,

When the order is changed to a set state, the electronic device deletes data related to the first order from the first database.