Method for accessing items by a delivery robot

Abstract

Embodiments of the present application disclose a method for a robot to access an article. The method comprises: obtaining a delivery destination address corresponding to an article of a waybill and a first string input by a storage user, querying, by a server, whether there is a matching relationship between the address information and the first string in the address information or the relevant record of the storage user identity of the historical waybill or the registration information of the delivery destination, and if the matching relationship is found, controlling the robot to provide an open-door storage function; and if the matching relationship is not found, providing a page for the storage user to input a complete user identity of a pickup user corresponding to the delivery address as a second string. Correspondingly, when picking up the article, the pickup user only needs to input a third string to cooperate with the first string for verification, or the pickup user authorizes the use of the identity to verify the second string input by the storage user, and the robot opens the cargo compartment where the article is located after the verification is passed. The present disclosure reduces the workload and input error rate of the storage user, and improves the efficiency of using the robot to access the article and the user experience.

Description

Technical Field

[0001] This manual pertains to the field of intelligent delivery robots, and more specifically, to the methods for storing and retrieving items using delivery robots and the robot system. Background Technology

[0002] With the continuous development of technology, delivery robots have been widely used, for example, in parks or indoor and outdoor areas to deliver goods and complete last-mile delivery tasks from delivery personnel or merchants to users. Currently, the process of using robots to store and retrieve items is inconvenient for both users and those retrieving items, with several cumbersome procedures leading to errors. Due to privacy and security concerns, users are reluctant to disclose their contact information, making it difficult for storage users to obtain their phone numbers or other contact details. Furthermore, remembering long phone numbers is challenging, and users entering information while listening can easily lead to errors or omissions. This creates significant obstacles for the robot in notifying users to retrieve their items upon arrival and for the verification process. Retrieval notifications may not reach users accurately, users may not know the delivery time, robots may wait for extended periods, and users may struggle to successfully retrieve their items, resulting in low efficiency, poor user experience, and a series of other problems. Summary of the Invention

[0003] One objective of this disclosure is to provide a new robotic storage and retrieval method for both storage and retrieval users, which significantly reduces the retrieval obstacle rate and item retention rate caused by incorrect input by storage users, thereby improving the overall efficiency of storage and retrieval.

[0004] According to a first aspect of this disclosure, a method for storing items in a delivery robot includes:

[0005] Based on the user's scanning of the barcode on the delivery robot, the system determines the delivery robot's need to deliver the items indicated by the barcode.

[0006] Obtain the delivery destination address information corresponding to the waybill item entered by the storage user and the first string, the first string being a string formed by the first preset number of digits starting from the first specified position in the identity identifier of the pickup user corresponding to the waybill item to be delivered;

[0007] The server retrieves the address information and the first string, and then queries the records related to the address information of the delivery destination or the identity of the pickup user to see if there is a matching relationship between the address information and the first string formed by the first preset number of digits.

[0008] If the address information entered by the user and the first string are found to match, the delivery robot is instructed to open the door and store the item.

[0009] The delivery robot opens the empty compartment door that is not yet filled with items and accepts the storage operation of the user;

[0010] After the delivery door closes, the delivery robot performs the task of delivering the items.

[0011] Optionally, if no match is found between the address information and the first string, an information input interface is provided for the depositor to input the user identification of the pickup user corresponding to the waybill item. The user identification is a second string consisting of a second preset number of characters, and the second preset number of characters in the second string corresponding to the user identification is longer than the first preset number of characters in the first string. The second string is associated with and stored with the delivery destination address information. This is used to notify the pickup user and to verify the pickup user's identity during pickup.

[0012] Optionally, querying records related to the delivery destination address information or the pickup user identification string to determine if there is a matching relationship between the address information and the first string formed by the first preset number of digits, including:

[0013] Check if there are any records in historical delivery orders completed manually or by robots that are associated with the first string; and / or

[0014] The query retrieves records from completed delivery records or other online shopping history that contain address information bound to the first string; and / or

[0015] Check if there are any records in the historical waybills where the destination address information is associated with the first string, based on the binding relationship between the information entered by the user when depositing the package or the information entered by the user when setting up the pickup.

[0016] Optionally, if no match is found between the address information and the first string, including:

[0017] In historical delivery orders completed manually or by robots, the address information of the delivery destination entered by the user or the first string identifying the user picking up the package was not found; and / or

[0018] In historical delivery orders completed manually or by robots, the address information of the delivery destination entered by the depositor or the first string representing the identity of the pickup user does not have a matching relationship.

[0019] According to a second aspect of this disclosure, a method for picking up packages using a delivery robot is provided, comprising:

[0020] After the delivery robot delivers the order to the delivery destination address, it obtains the pickup request from the user.

[0021] Output the pickup page. The pickup page provides an input area for the pickup user to input a pickup verification character that matches the waybill item. The pickup page displays a third string formed by a third preset number of digits. The third string corresponds to the user identifier of the pickup user of the waybill item corresponding to the destination address where the delivery robot stops. The third string is a part of the first string input by the storage user.

[0022] Get the fourth string input by the pickup user. The fourth string is used to combine with the third string to form a string verification to see if it matches the first string corresponding to the delivery order item at the destination address where the delivery robot stops. The first string is the first string that is associated with the delivery destination address information of the delivery order item when the user puts the delivery order item into the delivery robot.

[0023] If the string formed by combining the fourth and third strings passes the verification check against the first string, it is confirmed that the pickup user matches the waybill item with the destination address information, and the door of the delivery robot compartment corresponding to the waybill item to be picked up is opened for the pickup user to pick up the item.

[0024] Optionally, it further includes: if the string formed by the combination of the fourth string and the third string fails to match the first string, displaying a pickup graphic code page or prompting the pickup user to scan the pickup graphic code using the user identity used when placing the order for the item in the target application.

[0025] According to a third aspect of this disclosure, a method for picking up packages using a delivery robot is provided, comprising:

[0026] After the delivery robot delivers the order to the delivery destination address, the user accepting the pickup uses the target application to scan the delivery robot's pickup graphic code.

[0027] Obtain the authorization credentials of the pickup user to log in to the target application using the pickup user's identity;

[0028] If authorization is obtained to log in to the target application using the pickup user's identity, the pickup user's identity for using the target application is obtained;

[0029] If the identity identifier obtained by the pickup user through scanning the code is determined to meet the predetermined matching consistency condition with the identity identifier of the pickup user corresponding to the waybill item confirmed by the storage user when storing the item, the pickup user is confirmed to match the waybill item at the destination address where the delivery robot is currently parked, and the door of the compartment corresponding to the waybill item to be picked up is opened for the pickup user to pick up the item.

[0030] Optionally, for cases where the pickup user's identity corresponding to the waybill item meets predetermined matching consistency conditions, including:

[0031] The identification identifier obtained by the pickup user through scanning the code is compared bit by bit with the identifier entered by the storage user for the item on the waybill.

[0032] If the identity identifier obtained by the pickup user through scanning the code matches the second string of the identity identifier of the pickup user corresponding to the waybill item entered by the deposit user, or if the number of matching digits exceeds a threshold condition, it is determined that the predetermined matching consistency condition is met.

[0033] Optionally, if the server receives a result indicating that the identity identifier obtained by the pickup user through scanning the code does not meet the predetermined matching consistency condition with the identity identifier of the pickup user corresponding to the waybill item entered by the user when storing the item, a prompt page is provided to prompt the pickup user to switch to the identity identifier used when placing the order to log in to the target application to scan the code and pick up the item.

[0034] Optionally, embodiments of this disclosure may further include the following steps:

[0035] Provide a delivery address input page to obtain the delivery destination address information entered by the user picking up the package;

[0036] Determine the user's identity information when the pickup user logs into the robot delivery target application;

[0037] The server establishes a mapping association between the user's identity when logging into the robot delivery target application and the delivery destination address information. This mapping association is used to verify the consistency between the user's identity and the delivery destination address information when storing the item.

[0038] According to a fourth aspect of this disclosure, a method for picking up packages using a delivery robot is provided, comprising:

[0039] After the delivery robot delivers the order to the delivery destination address, it obtains the pickup request from the user.

[0040] Output the pickup page, which provides an input area for the pickup user to enter pickup verification characters that match the items on the waybill;

[0041] The fifth string input by the pickup user is obtained. The fifth string is used to verify whether the string formed by combining with the first string matches the identity of the pickup user corresponding to the delivery order item at the destination address where the delivery robot is parked. The first string is the first string that is associated with the delivery destination address information of the delivery order item when the storage user puts the delivery order item into the delivery robot. The identity of the pickup user is determined based on the delivery destination address information and / or the first string.

[0042] If the string formed by combining the fifth string and the first string matches the identity identifier of the pickup user, it is confirmed that the pickup user matches the waybill item with the destination address information, and the door of the delivery robot compartment corresponding to the waybill item to be picked up is opened for the pickup user to retrieve the corresponding item.

[0043] According to a fifth aspect of this disclosure, a method for storing and retrieving items using a delivery robot is provided, comprising:

[0044] Based on the user's scanning of the barcode on the delivery robot, the system determines the delivery robot's need to deliver the items indicated by the barcode.

[0045] Obtain the delivery destination address information corresponding to the waybill item entered by the storage user and the first string, the first string being a string formed by the first preset number of digits starting from the first specified position in the identity identifier of the pickup user corresponding to the waybill item to be delivered;

[0046] The server retrieves the address information and the first string, and then queries the information records related to the address information of the delivery destination or the identity of the pickup user to see if there is a matching relationship between the address information and the first string formed by the first preset number of digits.

[0047] If the address information entered by the user and the first string are found to match, the delivery robot is instructed to open the door and store the item.

[0048] The delivery robot opens the empty compartment door that is not yet filled with items and accepts the deposit operation from the user.

[0049] After the delivery door closes, the delivery robot performs the task of delivering the items;

[0050] After the delivery robot delivers the order to the delivery destination address, it obtains the pickup request from the user.

[0051] Output the pickup page. The pickup page provides an input area for the pickup user to input a pickup verification character that matches the item on the waybill. The pickup page displays a third string formed by a third preset number of digits. The third string corresponds to a portion of the first string input by the storage user.

[0052] Get the fourth string input by the pickup user. The fourth string is used to combine with the third string to form a string verification to see if it matches the first string corresponding to the destination address information where the delivery robot stops. The first string is the first string that the user confirms when storing the waybill item in the delivery robot and has a mapping relationship with the delivery destination address information of the waybill item.

[0053] If the verification and matching are successful, the system confirms that the pickup user matches the waybill item with the destination address information, and controls the opening of the door of the delivery robot compartment corresponding to the waybill item to be picked up, allowing the pickup user to retrieve the item.

[0054] According to a sixth aspect of this disclosure, a method for storing and retrieving items using a delivery robot is provided, comprising:

[0055] Based on the user's scanning of the barcode on the delivery robot, the system determines the delivery robot's need to deliver the items indicated by the barcode.

[0056] Obtain the delivery destination address information corresponding to the waybill item entered by the storage user and the first string, the first string being a string formed by the first preset number of digits starting from the first specified position in the identity identifier of the pickup user corresponding to the waybill item to be delivered;

[0057] If, based on the address information and the input first string, the server does not find a match between the address information and the first string formed by the first preset number of characters in the information records related to the address information of the delivery destination or the identity of the pickup user, it provides an information input interface for the storage user to input a second string consisting of a second preset number of characters representing the user identity of the pickup user corresponding to the waybill item. The second preset number of characters in the second string is longer than the first preset number of characters in the first string, and the second string is used to be associated with and stored with the delivery destination address information.

[0058] The delivery robot opens the empty compartment door that is not yet filled with items and accepts the storage operation of the user;

[0059] After the delivery door closes, the delivery robot performs the task of delivering the items;

[0060] After the delivery robot delivers the order to the delivery destination address, it obtains the pickup request from the user by scanning the pickup graphic code on the delivery robot using the target application.

[0061] If authorization is obtained to log in to the target application using the pickup user's identity, the pickup user's identity for using the target application is obtained;

[0062] If the identification of the pickup user obtained by scanning the code and the second string corresponding to the waybill item entered by the user when storing the item meet the predetermined matching consistency conditions, the pickup user is confirmed to match the waybill item at the destination address where the delivery robot is currently parked, and the door of the compartment corresponding to the waybill item to be picked up is opened for the pickup user to pick up the item.

[0063] The robot package storage and retrieval method disclosed in this embodiment requires only a small amount of string input from the user. The robot delivery system's backend queries the delivery destination address and matches it with the user's contact information to provide confirmation to the user. This reduces the amount of input required from the user and eliminates the tedious step of calling each contact to obtain complete contact information, significantly reducing the probability of input errors. Simultaneously, it improves the success rate of user verification for package retrieval, allowing users to choose a quick and convenient verification method, thus enhancing verification success rate and security, optimizing user experience, and improving the overall efficiency of using the robot for package storage and retrieval. Attached Figure Description

[0064] The accompanying drawings, which are included to provide a further understanding of this specification and form part of this specification, illustrate exemplary embodiments and are used to explain this specification, but do not constitute an undue limitation thereof. In the drawings:

[0065] Figure 1A This is a flowchart illustrating a method for storing parts using a robot, as provided in Embodiment 1 of this application.

[0066] Figure 1B A flowchart illustrating another method for storing parts using a robot, provided in Embodiment 1 of this application;

[0067] Figure 2A This is a flowchart illustrating a method for retrieving items using a robot, provided in Embodiment 2 of this application.

[0068] Figure 2B This is a flowchart illustrating another method for retrieving items using a robot, as provided in Embodiment 2 of this application.

[0069] Figure 3 This is a flowchart illustrating yet another method for retrieving items using a robot, as provided in Embodiment 3 of this application.

[0070] Figure 4 This is a flowchart illustrating another method for retrieving items using a robot, as provided in Embodiment 4 of this application. Detailed Implementation

[0071] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0072] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0073] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, they should be considered part of the specification.

[0074] In all the examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0075] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0076] It should be noted that all actions involving the acquisition of signals, instructions, information, or data in this disclosure are carried out in compliance with the relevant data protection laws and policies of the country where the location is situated, and with authorization from the owner of the relevant equipment.

[0077] To address the following issues identified by the applicant, before the application date, when users deposit packages using delivery robots, it is essential to obtain and input the complete identity or contact information of the user seeking delivery into the robot system. This is because the robot relies on the complete user identity or contact information to notify the user to come out of the room to collect the package upon arrival at the destination, and also uses this information to verify whether the person seeking delivery is the correct recipient for the item on the waybill. However, it is very inconvenient for users to simultaneously make a phone call and input the information. Due to the numerous digits in the identity information, users often cannot hear clearly or remember it incorrectly, leading to input errors. This causes significant trouble for the subsequent pickup process, resulting in users not receiving notifications or being unable to collect their packages, resulting in a high delivery failure rate. To solve this problem, the applicant proposes the following optimized methods for package deposit and retrieval.

[0078] Hardware configuration and application scenarios. The robot-based item storage and retrieval method of this disclosure includes robot docking points, also known as robot relay points, set up in an area. These can be robot charging stations or robot waiting areas. Item storage users can scan a graphic code deployed or displayed on the robot or the item storage application to send a robot delivery request to the management server. The robot receives the item from the delivery person and delivers it to the final delivery destination indicated on the waybill.

[0079] This disclosure provides a robot delivery system according to an embodiment. The robot delivery system may include a server 1000, a terminal device 2000 used by users storing items, a robot 3000, and a terminal device 4000 used by users picking up items. The server 1000 is a server that manages the platform to which the robot 3000 belongs.

[0080] Terminal device 2000, terminal device 4000 and robot 3000 can communicate with server 1000 through the same network or different networks to achieve information exchange.

[0081] Terminal devices 2000 and 4000 can be mobile phones, tablets, or other portable devices, and are not limited here. The target application runs on terminal devices 2000 and 4000; it can be a local application or a mini-program. Users can log in to the target application to perform robot-assisted storage or retrieval of items. Buyers select goods or food items on the platform and place orders. The buyer and the recipient can be the same person, or they can be different people; the buyer places an order on the platform, and another person picks up the item on their behalf. When placing an order, users can choose to use robot delivery, or, without specific specification, the store will default to robot delivery for orders meeting certain conditions. After the buyer places an order, the terminal device 4000 will send the order information to the server corresponding to the buyer's client. In the case that the buyer's client and the robot 3000 are on the same platform, the server is the server 1000 corresponding to the robot 3000. The order information includes item information and the recipient information entered by the ordering user. The recipient information includes the recipient's name, phone number, and delivery address (i.e., the delivery destination of the order).

[0082] The terminal device 2000 runs a client application for users who can be delivery personnel. Based on the waybill address, the delivery person first delivers the item to the first-level area of ​​that address, typically a region such as an apartment building or hotel. The delivery person then stores the item in the robot's available storage compartment, and the robot continues delivery to the detailed destination address, including the specific floor and room number (e.g., floor and room number). This allows for a relay-style delivery between the delivery person and the robot within the building. Alternatively, users can be store staff. After receiving an order from a customer and preparing the goods, the robot moves to the store's location according to the order instructions and waits for pickup. The store then stores the goods in the robot's available storage compartment, and the robot delivers them directly to the detailed destination address, enabling direct automated delivery from the store to the customer. Third-party users can also store items to be delivered into the robot's available storage compartment. The robot then creates a delivery task for that item and delivers it to the destination address.

[0083] At least one robot 3000 is deployed in the delivery area, and the robot 3000 communicates with the server 1000. Under the control of the server 1000, the robot 3000 can receive items to be delivered at relay points or other locations and deliver them to the final delivery destination within the delivery area. The robot 3000 is equipped with one or more storage compartments. The robot 3000 can open the doors of the corresponding storage compartments according to door opening commands, allowing users to store items in the storage compartments. After receiving the items to be delivered, the robot 3000 moves to the delivery destination of the waybill. The user, after verification, opens the door of the robot 3000's storage compartment to retrieve the delivered items.

[0084] Server 1000 is a service point providing processing, database, and communication facilities. Server 1000 can be a monolithic server, a distributed server spanning multiple computers, a computer data center, a cloud server, or a server cluster deployed in the cloud. Order management and delivery management on the same platform can be handled by the same device in the server cluster or by different devices in the server cluster; this is not limited here. Server 1000 can also be used solely for delivery management, meaning it can provide relay delivery services for orders from other platforms outside its own. Servers can be of various types, such as, but not limited to, web servers, scheduling servers, message servers, file servers, application servers, interactive servers, database servers, or proxy servers. In some embodiments, each server may include hardware, software, or embedded logical components for performing suitable functions supported or implemented by the server, or a combination of two or more such components. For example, servers may be blade servers, cloud servers, etc., or a server group may consist of multiple servers, including one or more of the types of servers described above.

[0085] In some embodiments, server 1000 may include processor 1100, memory 1200, interface device 1300, and communication device 1400.

[0086] Processor 1100 is used to execute computer programs. Memory 1200 includes, for example, ROM (Read-Only Memory), RAM (Random Access Memory), and non-volatile memory such as a hard disk. Interface device 1300 includes, for example, various bus interfaces, such as serial bus interfaces (including USB interfaces), parallel bus interfaces, etc. Communication device 1400 is capable of wired or wireless communication; communication device 1400 may include, for example, any module for WLAN, GPRS, 3G / 4G / 5G remote communication.

[0087] In some embodiments, the memory 1200 of the server 1000 is used to store a computer program for controlling the processor 1100 to operate in order to implement the robot delivery method according to embodiments of the present disclosure. Those skilled in the art can design instructions based on the disclosed solutions.

[0088] In some embodiments, the terminal device 2000 may include a processor 2100, a memory 2200, an interface device 2300, a communication device 2400, a display device 2500, an input device 2600, a speaker 2700, a microphone 2800, etc.

[0089] In some embodiments, the memory 2200 of the terminal device 2000 is used to store a computer program for controlling the processor 2100 to operate in order to execute the robot delivery method according to embodiments of the present disclosure. The terminal device 4000 may have a similar hardware structure, which will not be described in detail here.

[0090] The robot 3000 has a motion mechanism, enabling it to move from a relay point or docking point within the delivery area to the delivery destination. The robot 3000 includes at least one storage compartment with a controllable opening and closing door. It also features an interaction device for interacting with users during storage and retrieval, allowing for information input and output. For example, the interaction device can be a touchscreen displaying waybill information, a storage graphic code, and a retrieval graphic code for users to scan to initiate storage or retrieval requests. It also displays an information input area for entering the delivery destination address, including room number or floor number, and contact information for the retrieval user. The device accepts user-inputted information related to the waybill delivery and receives confirmation from the user to open the compartment for storage or retrieval. Alternatively, the interaction device can be an audio input / output device that receives user voice input, recognizes it, executes commands, and outputs prompt voice announcements.

[0091] The robot 3000 may include a processor 3100, a memory 3200, an interface device 3300, a communication device 3400, a display device 3500, an input device 3600, a speaker 3700, and a microphone 3800. The processor 3100 executes computer programs, which can be written using instruction sets based on architectures such as x86, Arm, RISC, MIPS, and SSE. The memory 3200 includes, for example, ROM (Read-Only Memory), RAM (Random Access Memory), and non-volatile memory such as a hard disk. The interface device 3300 includes, for example, a USB interface and a headphone jack. The communication device 3400 is capable of wired or wireless communication, and may include at least one short-range communication module, such as any module that performs short-range wireless communication based on short-range wireless communication protocols such as Hilink, WiFi (IEEE 802.11), Mesh, Bluetooth, ZigBee, Thread, Z-Wave, NFC, UWB, and LiFi. The communication device 3400 may also include a long-range communication module, such as any module that performs WLAN, GPRS, or 2G / 3G / 4G / 5G long-range communication. The display device 3500 is, for example, an LCD screen or a touch screen. The input device 3600 may include, for example, a touch screen or a keyboard. The speaker 3700 is used to output audio signals. The microphone 3800 is used to acquire audio signals.

[0092] In some embodiments, the memory 3200 of the robot 3000 is used to store a computer program for controlling the processor 3100 to perform operations, such as performing corresponding display operations, movement operations, controlling the opening of the storage compartment, controlling the closing of the storage compartment, etc., to execute the robot delivery method according to the embodiments of this disclosure.

[0093] It should be understood that although the above examples show one server 1000, one terminal device 2000, one robot 3000, and one terminal device 4000, it does not mean that the number of each is limited. The item delivery system can contain multiple servers, multiple terminal devices, multiple robots, etc.

[0094] Method Example 1, Figure 1A and Figure 1B A schematic flowchart illustrating a method for storing items using a robot, according to some embodiments, is shown. Users can store items to be delivered into a specific robot for delivery.

[0095] Step S110: Based on the user's scanning operation of the storage item graphic code on the delivery robot, determine the delivery robot's need to deliver the order item indicated by the graphic code.

[0096] Specifically, a storage graphic code is affixed to the robot, displayed on the robot's screen, or a waiting page is displayed on the robot's screen. After the user operates the storage service, the storage graphic code is displayed on the robot's screen. This graphic code can be, for example, a QR code or a barcode, etc., and this embodiment of the disclosure is not limited to this. When the user arrives at the robot, submits a request, and determines the delivery robot indicated by the graphic code to deliver the order by scanning the code. The storage graphic code indicates the robot's number; each robot has a unique mapping number. By scanning the code, it can be determined which robot the user intends to use for storage. Each robot has a corresponding activity range, and the robot's location can be obtained through the storage graphic code.

[0097] After a user scans a code using the client application, they send a command. The backend server receives the robot's delivery request and identifies the user based on the account identifier of the storage application or client. If the user is a delivery person, the server identifies the delivery person's orders whose destination is within the delivery area as the target order. In some embodiments, the delivery person's identifier may be, for example, their mobile phone number. After determining the delivery person's mobile phone number based on the account identifier of the storage client or application, the server searches for that delivery person's mobile phone number within the platform system.

[0098] If the server finds the delivery person's mobile phone number, it retrieves the delivery person's delivery orders. From the delivery person's delivery orders, it identifies orders whose delivery destination is within the delivery area as target orders. The order information of the target order may include, for example, the order number of the target order, the address information of the delivery destination, the name and full identification or contact information of the recipient (i.e., the user picking up the package), and the delivery person's mobile phone number.

[0099] If the server cannot find the phone number of the user who stored the package, or the delivery person, or cannot retrieve any orders for that delivery person based on their phone number, it means the order the delivery person wants to deliver does not belong to the service platform to which Robot 3000 belongs. In this case, a target order can be created using the target robot. The target order created using the target robot does not yet contain the complete user identification, or contact information, of the pickup user. The user who stored the package can only see encrypted contact information, such as a virtual phone number. They can use a dedicated application to call the virtual number to contact the pickup user, obtain, and enter the pickup user's real phone number.

[0100] Step S120: Obtain the delivery destination address information and the first string corresponding to the waybill item entered by the storage user. The first string corresponds to the string formed by the first preset number of digits starting from the first specified position in the identity identifier of the pickup user corresponding to the waybill item to be delivered.

[0101] Output a delivery recipient information input page. This page can be displayed on the robot screen or on the storage user application client. The example of displaying it on the robot screen is similar; displaying the input page on the client is similar.

[0102] The recipient information input page includes a delivery destination address input area, prompting the user to enter the room number of the delivery destination. The room number is entered in numeric form according to preset rules, typically displaying the floor information and the specific room number, such as 301. If the room number does not display floor information, the floor number and room number must be entered according to the rules, such as 10th floor, room 01. If the delivery area is larger and has more levels, such as including area information or building information, such as Zone 10A and Building B, then the address must also be entered according to preset address rules. The recipient information input page has a keyboard with both numbers and letters, supporting the input of detailed addresses. Input can also be done using a drop-down list, allowing users to select the delivery destination area, building, floor, and room number level by level.

[0103] The recipient information input page also includes a recipient contact information input area for entering a first string. This first string corresponds to the string formed by the first preset number of digits starting from the first specified position in the recipient's identity identifier for the item on the delivery slip. For example, the first string may be shorter than the complete recipient identity identifier, so the recipient does not need to enter a longer string. The recipient's identity identifier is information that identifies the recipient, such as their contact information (e.g., mobile phone number), account number, or other identifying information, used for notifying and verifying the recipient's identity. The first string is associated with the recipient's identity identifier. For example, if the identity identifier is the customer's (i.e., the recipient's) mobile phone number, the first string is the last four digits of the mobile phone number. The page prompts the recipient to enter part of their mobile phone number, guiding them to input the four digits using the keyboard. The last four digits of the user's mobile phone number can be obtained from the delivery slip or receipt. For user security and privacy, the user's mobile phone number may be displayed as a virtual number or an obfuscated number, but the last four digits are usually the actual last four digits. The last four digits of the user's mobile phone number can also be obtained by the user calling the virtual number on the delivery slip or waybill to contact the customer picking up the package. The first string can be obtained by the user entering it on the input page. Alternatively, the user can activate the terminal's optical scanning device to scan the barcode or number on the order slip to quickly obtain the first string, which can then be directly entered into the user's package storage application.

[0104] The recipient information input page can be one or more pages, providing input for different types of information. Multiple pages can be displayed simultaneously, or the next input page can be displayed after one page is completed. The input area for the delivery destination address and the first string input area can be displayed separately on the same page or on different input pages. After the user scans the code, the delivery destination address input area is displayed first, followed by the contact information input area after the user completes the input. The display order of the address and contact information pages can be adjusted as needed; they can be entered on the same page or sequentially on different pages. The recipient information input page also provides guidance on the step-by-step process, using different font colors, brightness, and boldness, or flowchart symbols such as lines and arrows, to indicate the current input item and subsequent items to be entered. When entering the current content, the content entered in the previous step is displayed in the corresponding position on the current page for the user to check. For example, after entering the room number, when entering the contact information, the previously entered room number information is displayed in the room number field on the page. After entering information, the page also provides editing controls so that the user can correct the information entered and supports modifications to the content entered in the current step or any previous step.

[0105] Step S130: Obtain address information and a first string. The server queries the records related to the address information of the delivery destination or the identity of the pickup user to see if there is a matching relationship between the address information and the first string formed by the first preset number of digits.

[0106] After the user enters the address information of the delivery destination and a first string through the robot screen or client, the above information is sent to the server. The server searches the entire network database to see if there is a matching relationship between the address information of the destination and the first string.

[0107] In some implementations, the server queries historical delivery orders completed manually or robotically to determine if there are records where the address information is associated with the first string. Historical delivery orders include those delivered manually (e.g., by delivery personnel) or robotically. Manual delivery corresponds to a manual delivery order database, and robotic delivery corresponds to a robotic delivery order database. The query checks if the address information or the first string exists in the historical delivery orders. This includes not only delivery records from this platform but also records from other order service platforms or delivery service platforms that placed the order on this platform. It also includes queries from third-party platform servers to find the destination address information or the first string as part of the user's contact information in the online shopping order history. This could be because the third-party platform records the destination address and user contact information, but orders for which the third-party platform did not participate in delivery are also included in the query scope. Alternatively, orders for which the third-party platform participated in delivery, but was not the platform from which the order was placed, are also included in the query scope. This can be limited to successfully delivered orders to ensure that the destination address and the first string have a true correspondence. Considering that for orders placed too long ago, the resident may have moved away and the address and contact information may no longer be valid, a time threshold can be set for historical orders, such as within six months or within one year. For historical orders that exceed the time threshold, the system will give a prompt, reminding the depositor to check whether the correspondence is valid.

[0108] In some implementations, the server can query records that establish a binding association between the delivery destination address information and the pickup user's identity information, entered by other users when depositing packages or set up pickup information before the current delivery. For example, other users might not have been able to find the contact information for the user at the delivery address previously. They contacted the pickup user at that destination using the contact information on the delivery waybill, such as a virtual phone number, and obtained the pickup user's complete phone number, which was then entered into the robot service system. This could be done by entering the same delivery address as the current delivery in the address field on the robot screen or the package deposit page of the delivery client, and entering the user's identity information for that destination address in the contact information field. In this way, the complete user identity information is not only used to complete the previous delivery task but is also stored together in a binding association. Another example is that a new pickup user can set the pickup destination address and complete contact information and identity information before placing an order for robot delivery. The robot delivery system establishes a binding association record between the address and identity information for the new user. The identity information and contact information can be the same or different information.

[0109] In some implementations, the server query for the matching relationship between the pickup user's mobile phone number and room number, and the registration method of the information, can include the following: the room number and contact number are stored in the same service platform as the delivery robot or in other service platforms; or the contact number and room number entered by the user who stored the package for the pickup user. Conditions can also be set such that the order has been picked up independently by the user, and the order is automatically converted to the user's registered contact number and room number based on the user's complete identity or contact information notification without any abnormalities leading to empty or delayed packages; support for users to independently register and fill in their contact number and room number through the application, for example, by scanning a QR code; and the matching relationship between historical manual or robot delivery orders and room numbers. The server query can proceed by first querying the destination address and room number information, then entering partial fields of contact information, such as the last few digits of the mobile phone number. If neither of these is found, the user who stored the package needs to obtain the pickup user's complete identity, such as the complete mobile phone number. The order of the query steps can be flexibly set and adjusted according to requirements.

[0110] Step S140, Figure 1A If the address information entered by the user and the first string are found to match, the delivery robot is instructed to open the door and store the item.

[0111] The system retrieves a destination address matching the user's input from historical records or established binding records. It also retrieves the user's complete identity or contact information (e.g., phone number) for that destination address. The first string entered by the user is a part of the retrieved user's complete identity or contact information (e.g., phone number), and the destination address matches this first string. This matching relationship can occur within the same delivery record or the same delivery settings record. For example, if the room number of the item ordered by the user matches the user's identity (e.g., phone number) in the same record, it proves that the first string of the user's identity and the delivery destination address entered by the user are accurate and represent valid and reachable contact information and address. The system can directly control the delivery robot to open the door for package storage. Alternatively, the matching relationship between the retrieved address and identity can be presented to the user on the robot screen or in the application, for example, through automatic input or a pop-up window. After confirmation by the user, the robot opens the corresponding hatch for package storage.

[0112] Optionally, the waybill delivered by the user and the user belong to the same platform. When the user uses the robot to deposit the package, the waybill corresponding to the user is displayed on the robot screen or the user's client. After the user confirms and verifies, the robot system obtains the destination address of the delivery waybill and the identity of the user picking up the package. In this case, the user only needs to confirm the identity of the user picking up the package corresponding to the waybill, saving a lot of data entry work and avoiding situations where incorrect data entry leads to failure to notify the user to pick up the package.

[0113] Step S141, Figure 1B If no match is found between the address information and the first string, an information input interface is provided to receive the user identifier of the pickup user corresponding to the waybill item from the storage user. The user identifier is a second string consisting of a second preset number of characters. The second preset number of characters in the second string corresponding to the user identifier is more than the first preset number of characters in the first string. The second string is associated with and stored with the delivery destination address information.

[0114] In some implementations, situations where no matching relationship is found between the destination address and the first string in historical records or established binding association records include, for example, the address information or the first string of the delivery destination entered by the user being stored being not found in historical order records completed manually or by robots. That is, neither the destination address nor the string has a historical record, or either one of them has a historical record; for example, no delivery order record for that address or no delivery order record for that user's identity is found. The corresponding real-world situation might be that the delivery address or the pickup user has never used online ordering before, or that they are a new user or a new address. Situations where no matching relationship is found also include situations where no record of the destination address and user identity is found in the binding association records established when other users stored items or when the pickup user set up their items. Situations where no match was found include instances where no records of destination address and user identification were found among online orders placed on the same platform or a third-party platform as the robot delivery service. These situations indicate that the user did not purchase any items at that delivery destination address. Since the system does not retain any record of the user at that destination, the user needs to manually enter the complete delivery destination and user identification or contact information.

[0115] In some implementations, the failure to find a match between the destination address and the first string may also include situations where, although at least one of the destination address or string is found in the historical records or established binding association records, neither matches the information entered by the user storing the package. For example, under the same room number, the record shows the corresponding user identifier or contact information mobile phone number as A, while the first string representing the user identifier or contact information entered by the user storing the package is B. B is not composed of any part of the string in A, and B does not correspond to A. This may be due to a change of occupant in the same room at the hotel or apartment, a change of address for the user picking up the package, or an incorrect address or user identifier entered by the user storing the package. In such cases, it will also be determined that no match was found.

[0116] If no match is found between the address information and the first string, it indicates that the address information entered by the user does not have a valid delivery record with the first string, such as the last four digits of the recipient's phone number. The system does not store the complete phone number of the recipient at that destination address. The user only entered the first string, which serves only as part of their identification or contact information, and cannot effectively notify the recipient to pick up the package. This will cause inconvenience for the recipient. Therefore, it is necessary to input the complete identification of the recipient, such as their complete phone number. An information input interface should be provided on the robot screen or the user's application to receive the complete user identification of the recipient. The complete user identification consists of a second string of a second preset number of characters, with the second preset number of characters exceeding the first preset number of characters in the first string. This second string is associated with the delivery destination address information and stored for verifying the recipient's identity during pickup.

[0117] In some implementations, after failing to find a match between the address information and the first string, a page or pop-up window appears, prompting "No last four digits found, please try again, or enter the complete mobile number." The page or pop-up window provides selection controls A and B. Control A corresponds to re-entry; upon triggering, the page redirects to the input page for re-entering the first string. It receives the last four digits of the customer's (i.e., the pickup user's) mobile phone number as the first string, and then checks again for historical or linked records by combining the re-entered first string with the destination address information. Based on the query results, the corresponding page is displayed again. Control B corresponds to inputting a complete mobile phone number. Upon triggering, the page redirects to the page for entering the customer's complete mobile phone number. A numeric keypad is provided, accepting the complete identity information of the customer (i.e., the pickup user) entered by the user who stored the package, such as their mobile phone number. The user who stored the package can contact the pickup user via a virtual phone call or other means to obtain the pickup user's complete mobile phone number, which is then entered as a second string into the information page. This second string, serving as the complete user identity, is associated with and stored with the delivery destination address information, forming a record for future deliveries. If the user accurately enters a delivery address and the first string (e.g., the last four digits of the mobile phone number) in the future, the system will find that the first string matches a portion of the pickup user's complete user identity information at that delivery destination address. This confirms the match, and the system can then directly use the entered complete user identity for pickup notification and verification. This eliminates the need to repeatedly ask for the pickup user's detailed address and contact information for future deliveries, improving subsequent delivery efficiency.

[0118] When the system finds a matching record for the address information after the first string re-entered by the user, or after confirming the second string of the user's complete identity information, the system can obtain the complete identity information or contact information of the user who picks up the package at the destination address. Thus, the system can effectively notify the user who picks up the package. At this point, the robot continues to execute the subsequent steps S150 and S160.

[0119] In step S150, the delivery robot opens the empty compartment door assigned to this delivery and accepts the delivery user's deposit operation. The delivery user places the item into the robot's compartment. After a predetermined time, the robot compartment door closes. Alternatively, the delivery user can close the robot compartment door by operating on the robot screen or the delivery client, for example, by clicking the close button.

[0120] In step S160, after the delivery door is closed, the delivery robot performs the task of delivering the items.

[0121] The delivery robot executes the delivery task according to the destination address information entered by the user and the route planned for the robot by the scheduling system. It travels to the floor and room number indicated in the address information.

[0122] The robot package storage method disclosed in this embodiment requires only a small amount of information from the user: the delivery address and a first string. The robot delivery system automatically retrieves the complete user contact information from historical order records or registration records. This eliminates the need for the user to contact the customer for each order, saving significant time by using a virtual phone to inquire about the user's real identity and contact information. This significantly reduces the workload and improves storage efficiency. Testing showed that before using this method, storing an order via the robot took at least 3 minutes, wasting considerable time waiting for the recipient to answer the phone. The error rate was high when the user entered the recipient's contact information while on the phone. After using this method, more than two-thirds of the time is saved, and storing an order can be completed in less than 1 minute. The failure rate of customer verification due to input errors has also decreased significantly. Furthermore, the retrieval process is smoother. By scanning a code or entering only a few characters, the retrieval process is more efficient and convenient, reducing user concerns about disclosing their contact information.

[0123] Method Example 2, Figure 2A and Figure 2B A flowchart illustrating a method for a user to quickly retrieve a package using a robot, according to some embodiments, is shown.

[0124] Step S210: After the delivery robot delivers the waybill items to the delivery destination address, obtain the pickup request from the pickup user for the waybill items.

[0125] When the delivery robot arrives at or is about to arrive at the delivery destination, the system will notify the pickup user to open the door and retrieve their package via voice or text message, based on the user's complete identification information, such as their full mobile phone number. The complete mobile phone number used for notification is retrieved by the system from historical order records or linked records based on the first string entered by the user and the destination address, or it can be a second string entered by the user after contacting the pickup user.

[0126] The user requests to pick up their package by interacting with the robot's screen or through their robot delivery app. After the robot docks at the destination address, a pickup graphic code is displayed on its screen. The user can scan this code using their terminal. Alternatively, the user can interact with the robot's screen to display the graphic code, then scan it to initiate a pickup request to the robot service system. Alternatively, the user can launch an application, such as a mini-program embedded in a third-party platform, and interact with the application to initiate a pickup request to the robot service system.

[0127] Step S220: Respond to the pickup request and output the pickup page. The pickup page provides an input area for the pickup user to input pickup verification characters that match the items on the waybill.

[0128] A pickup page is displayed on the robot screen or the pickup user's application. This page displays a third string consisting of a third preset number of digits. This third string corresponds to a portion of the user's identifier for the waybill at the destination address where the delivery robot has stopped. The third string is a subset of the first string entered by the user who stored the item. For example, if the user enters a four-digit first string for the waybill and it is confirmed, after the robot reaches the destination address area, it identifies the waybill corresponding to that address, determines the first string, and displays a portion of that first string, forming the third string. The remaining characters of the first string are left for the pickup user to input; for example, two characters from the first string are displayed on the page, thus displaying the third string, leaving two empty input fields for the pickup user. The displayed and empty character fields can be preset by rules.

[0129] Step S230: Obtain the fourth string entered by the user on the pickup page on the robot screen or the user's target application. The server combines the obtained fourth string with the displayed third string to form a string, which is used to verify whether the combined string matches the first string corresponding to the delivery order item at the destination address where the delivery robot is docked. The first string is the first string associated with the delivery destination address information of the delivery order item, confirmed by the user when storing the delivery order item in the delivery robot. This verification process can be performed locally on the robot, or the fourth string can be sent to the robot server, where the server compares the string combining the fourth string and the third string entered by the user with the first string. In other cases, only a portion of the first string may be displayed during pickup; that is, the user may need to fill in the full length of the first string in the input area, and the fourth string entered by the user may be compared and verified with the first string entered and stored by the user.

[0130] Step S240, Figure 2A The system performs a consistency check between the string formed by combining the fourth and third strings and the first string on the robot or server side. If the match is successful, it confirms that the pickup user matches the waybill item with the destination address information. For example, if the combined string matches the first string bit by bit, or if the number of inconsistent bits is below a predetermined error tolerance threshold, it confirms that the pickup user matches the waybill item with the destination address information, and opens the door of the delivery robot compartment corresponding to the waybill item for the pickup user to retrieve.

[0131] This reduces the memory burden on users picking up their packages. Users only need to remember a shorter fourth string, which is combined with the displayed third string and then verified against the first string entered by the user, ensuring both security and accuracy. This reduces the probability of users being unable to pick up their packages due to remembering or entering the wrong pickup code, making the pickup process simple and fast, improving efficiency and user experience. It also reduces the risk of users revealing their contact information.

[0132] Step S241, Figure 2BIf the combined string fails to match the first string in the validation process (e.g., the difference in the number of bits exceeds a threshold), the system will display a pickup graphic code page or prompt the user to scan the pickup graphic code using the user identification used when placing the order. Alternatively, if the user misremembers the pickup string, and the combination of the pickup string and the displayed third string does not match the first string entered by the user, the system will display a pickup graphic code on the robot screen or client, or display a prompt to retrieve the code at the user's request. The user can then scan the code to verify and retrieve the item. Alternatively, if the validation fails, the system can prompt the user of the failure, clear the input area, and allow the user to re-enter the code. A threshold can be set for the number of failed validation attempts before displaying or prompting the user to scan the pickup graphic code to retrieve the item. The combined string failed verification against the first string, which could be due to incorrect input by the user, the user having multiple phone numbers and remembering the wrong one, the user entering the wrong contact information, or errors in system recording or registration. This method escalates the verification level when the user's input string fails verification a certain number of times. It compares the verified identity with the user's authorized identity verified during storage, typically using a longer string than the user's input. This higher verification level prevents unauthorized users from attempting to change the password and steal it.

[0133] Example 3, Figure 3 According to some embodiments, a flowchart illustrating yet another method for a user to retrieve an item using a robot is provided.

[0134] In step S310, after the delivery robot delivers the order to the delivery destination address, a pickup graphic code is displayed on the robot's screen. The user then scans the pickup graphic code on the delivery robot using the target application. The target application can be a specific application, such as the same application used to place the order, or a third-party platform application, such as WeChat or Alipay, using the WeChat or Alipay scan function, or a business service mini-program embedded in a third-party platform application. No restrictions are imposed here.

[0135] Step S320: If authorization is obtained to log in to the target application using the pickup user's identity, the pickup user's identity for using the target application is obtained.

[0136] In some cases, it is also necessary to obtain authorization credentials for the pickup user to log in to the target application using their user identity. These credentials can be submitted by the pickup user when logging into the target application, authorizing the application to use the user identity. Once the user identity is authorized, the target application can store the login status of that user identity. When the pickup user uses the target application again, they can directly access the account corresponding to that identity to display and query relevant information. The user identity can be an identifier that identifies the user, such as the user's complete mobile phone number, ID card number, or unique registration number on the target application. The user identity can be stored on the business server or client side and is also used for verification, matching, and contacting the user.

[0137] After the user grants authorization, the target application logs into the user account with the user's identity ID, and the server obtains the user's identity ID.

[0138] Step S330: If it is determined that the identity identifier obtained by the pickup user through scanning the code and the identity identifier of the pickup user corresponding to the waybill item entered or confirmed by the storage user when storing the item meet the predetermined matching consistency conditions, the pickup user is confirmed to match the waybill item at the destination address where the delivery robot is currently parked.

[0139] By scanning a QR code, the client sends the complete user identity identifier authorized by the target application to the robot delivery system server or to the robot itself. This determines whether the robot's delivery order contains a complete user identity identifier matching the delivery address. The server or robot then checks the waybills in the delivery task to see if a pickup user identity identifier matches the one obtained from the QR code. If found, it confirms that the QR code authorization identifier corresponds to the delivery item. Alternatively, the server can query waybills parked at the delivery destination to confirm the corresponding user identity identifier. When a QR code authorization identifier is obtained, it compares it to the user identifier of the waybill. If they match, verification confirms that the scanned user identifier matches the waybill item. Finally, it determines that the robot carries the order item corresponding to the pickup user's complete identity identifier.

[0140] For situations where the user storing the package enters the complete identity and contact information of the user picking up the package, the user can scan a pickup graphic code to send their identity information, obtained by the application, to the server or robot for verification against the complete identity and contact information entered by the user storing the package. Typically, the string used for identity verification is longer than the string entered by the user, resulting in a higher level of verification and greater security. This also adds detailed verification of the complete identity of the user entering the pickup information during the pickup process to prevent errors. If the verification of the complete identity of the user picking up the package passes, it means that the complete identity of the user entering the pickup information during storage is accurate and can be stored on the server for matching with the delivery address during subsequent delivery.

[0141] Optionally, when a user deposits a package, they only enter the first string. The robot system then queries the destination address of the delivery order that matches the first string. When the user scans the code, after the target application used by the user authorizes and obtains the user's identity identifier, the system matches the obtained identity identifier against the first string. If a portion of the characters in the first string match the identity identifier, or if the number of identical characters in the first string and the identity identifier exceeds a threshold after a character-by-character comparison, then the identity identifier meets the matching consistency condition. For example, if the delivery order delivered by the user belongs to the same platform as the user, when the user deposits a package using the robot, the corresponding delivery order is displayed on the robot screen or the user's client. After the user confirms and verifies, the robot system obtains the destination address of the delivery order and the user's identity identifier. In this case, the user only needs to confirm the identity identifier of the user corresponding to the delivery order, saving a large amount of character input and avoiding situations where incorrect input leads to failure to notify the user to pick up the package.

[0142] Optionally, users can retrieve their packages by scanning a QR code. This can be used when no historical record or previously registered address or contact information was found when the package was stored. In this case, the user enters their complete user identity or contact information into the robot system after being contacted by the recipient. Since this is the first time the user's complete user identity or contact information has been entered into the robot delivery system, its accuracy needs to be verified. There is a possibility that the user may have misheard or mistyped the information. Therefore, the user needs to log in to the target application using their user identity and then retrieve the package by scanning a QR code. The application then uses the user identity information obtained from the QR code to verify the correctness of the complete user identity or contact information entered by the robot user.

[0143] Optionally, users can pick up their packages by scanning a QR code. Alternatively, the delivery order can be linked to a user who belongs to the same platform as the user who placed the package. The user can then verify the delivery order displayed on the robot screen or their client app. In this case, the system obtains the destination address and the user's identification from the service platform. The user can then pick up their package directly by scanning the QR code.

[0144] Optionally, when determining whether the complete identity identifier used by the pickup user to scan the code matches the complete identity identifier entered by the storage user, the identity identifier obtained by the pickup user through scanning is compared digit by digit with the identity identifier of the pickup user corresponding to the waybill item entered by the storage user. The consistency condition is determined to be met when the identity identifier obtained by scanning the code is completely consistent with the second string of the pickup user's identity identifier entered by the storage user. Alternatively, considering practical considerations, it can be allowed for the storage user to misenter one digit or reverse two digits. To allow for flexibility, a matching threshold above a certain number of digits can be set to determine if the match is consistent. For example, setting the similarity between the scanned identity identifier or mobile phone number and the identity identifier or mobile phone number entered by the storage user to greater than 80%, or setting the number to be misentered by two digits or less, can determine if the matching consistency condition is met and the hatch is opened. If a user authorizes the pickup using a complete user identifier when scanning the code, the server, based on the user's authorized identifier, will automatically correct the contact information entered by the user (the second string) to match the identifier used for pickup if the error rate is below the tolerance threshold (e.g., allowing a maximum of two incorrect digits). This corrects the user's input of the complete identifier to the identifier authorized for pickup. Furthermore, the server will also correct the match between the destination address and the second string identifier to the accurate identifier before storing it. This approach is more flexible and adaptable to real-world situations, simplifies the process, improves pickup efficiency, and provides a secondary verification of information. The pickup process not only verifies the match between the pickup user and the item but also identifies and corrects errors made by the user who entered the identifier, increasing information accuracy.

[0145] Optionally, if the identity identifier obtained by the server or robot through scanning does not meet the predetermined matching consistency condition after comparison and verification with the identity identifier of the pickup user corresponding to the item when the package was stored, a prompt page will be provided on the pickup user's application, prompting the pickup user to switch to the identity identifier used when placing the order to log in to the target application for scanning and pickup, or to contact maintenance personnel. For example, the prompt page may display "xxxxx (the mobile phone number used by the user to scan the code) does not match the number entered by the rider. Please scan the code with the mobile phone number used to place the order or contact maintenance personnel." The prompt page may also pop up after one or a predetermined number of scans that do not match. The prompt page may be displayed on the robot screen or on the user's mobile client, without limitation.

[0146] In step S340, if the matching consistency condition is met, the robot opens the door of the compartment corresponding to the item on the waybill under instruction, allowing the user to retrieve the item. The user then takes their item to complete the retrieval process.

[0147] In some embodiments, before picking up a package, the user can register and fill in the delivery destination address and identity information, such as during new user registration. This allows the server to jointly store the address and identity information, establishing a corresponding matching relationship between the delivery address and the identity. The user logs into the robot delivery application, such as a mini-program, and enters the frequently used delivery address maintenance page. They fill in the building and room number of their frequently used delivery address, supporting selection from a drop-down list. The user can enable location services and enter or select the building information and room number. Users can also fill in identity information, such as a contact mobile phone number; alternatively, users can authorize the use of their identity, such as their mobile phone number, when logging into the robot delivery application, and directly store that mobile phone number as the contact method matching the delivery address. The server establishes a mapping association between the user's identity when logging into the robot delivery application and the delivery destination address information. This mapping association serves as a record related to the user's identity and is used to verify the consistency of the user's identity and delivery destination address information when storing the package. This address and contact information are bound to the user's identity, allowing users to maintain and modify the information. The system provides the function for users to actively register and maintain their identity, contact information, and delivery address.

[0148] Example 4, Figure 4 According to some embodiments, a flowchart illustrating yet another method for a user to retrieve an item using a robot is provided.

[0149] When the user storing the item is not on the same platform as the robot delivery service, or when the user storing the item is not on the same platform as the delivery order, or when the delivery order is not on the same platform as the robot delivery service, the user storing the item cannot find the order to be delivered in their own delivery tasks. The user storing the item does not have the complete identity of the person picking up the item. The user storing the item deposits it into the robot's compartment by entering a first string. After receiving the first string, such as the last four digits of a mobile phone number, the robot delivery server searches for the complete user identity corresponding to the first string in the historical waybill or record information. The system uses the complete user identity as the contact information for the person picking up the item for that waybill. In this case, the item can be picked up using the following methods.

[0150] In step S410, when the delivery robot arrives at or approaches the delivery destination address with the delivered item, the robot delivery system sends a message or makes a phone call to the user using their identification, such as a mobile phone number, to notify them to pick up the item. The user then approaches the robot and, through the touchscreen, clicks "pick up," or scans the QR code on the screen, obtains their pickup request for the delivered item. Alternatively, the robot can remain at the destination address and receive the user's action within a predetermined waiting time, which is considered as obtaining the user's pickup request.

[0151] Step S420: Output the pickup page. The pickup page provides an input area for the pickup user to input pickup verification characters that match the items on the waybill. The pickup page can be displayed on the robot screen or on the pickup user's application client.

[0152] Step S430: Obtain the fifth string input by the pickup user on the robot screen or the pickup user's target application. The fifth string can be a complete user identification, such as a complete mobile phone number excluding the first string. The fifth string is sent to the server. The server, based on the waybill information, finds the waybill for the item to be picked up corresponding to the destination address and determines the first string input by the user. The fifth string and the first string are combined to verify whether they match the identification of the pickup user corresponding to the delivery waybill item at the destination address where the delivery robot is docked. The first string is a string associated with the delivery destination address information of the waybill item, confirmed by the user when depositing the waybill item into the delivery robot. For example, the first string is the last four digits of the pickup user's mobile phone number entered by the user storing the package, such as "5678". Based on this, the system retrieves the pickup user's complete identity identifier from historical waybills or registration records, such as an 11-digit mobile phone number, "13512345678". The fifth string that the user needs to enter when picking up the package is a predetermined number of characters from the complete identity identifier, starting from a predetermined number of digits, such as from the fourth to the seventh digit, "1234". To verify the pickup user's identity, the robot delivery service system combines the obtained fifth string "1234" with the first string "5678" entered by the user storing the package in a predetermined order and number to form the string "12345678", and performs a consistency check against the pickup user's complete identity identifier "13512345678" corresponding to the waybill to be picked up.

[0153] Step S440: If the string formed by combining the fifth string and the first string matches the identity identifier of the pickup user, it is confirmed that the pickup user matches the waybill item at the destination address. For the same waybill, the fifth string entered by the pickup user and the first string entered by the storage user are combined according to certain preset rules. The number of characters in the combined string is the same as or less than the number of characters in the identity identifier. If the combined string is a partial character of the user's identity identifier corresponding to the queried waybill, then the combined string matches the pickup user's identity identifier. Other matching rules can also be set, or the matching consistency condition is considered met when the number of matching characters exceeds a threshold condition. In this case, it is confirmed that the pickup user matches the waybill item at the destination address. If the number of matching characters in the string formed by combining the first string and the fifth string does not reach the threshold or the required number of matching characters when compared character by character with the complete user identity identifier of the pickup user, it is determined that the pickup user does not match the waybill item at that address. A prompt will pop up on the robot screen or the pickup user application, prompting the user to re-enter the correct fifth string or contact staff to pick up the item. The robot screen displays a pickup graphic code, prompting the user to scan the code to retrieve their item. Alternatively, a message can be displayed instructing the user to scan the graphic code after the initial operation.

[0154] Step S450: After confirming that the pickup user matches the waybill item at the destination address, the door of the delivery robot compartment corresponding to the waybill item to be picked up is opened so that the pickup user can retrieve the corresponding item.

[0155] To balance convenience and security in package retrieval, the different retrieval methods correspond to different storage methods. When a user enters the first string, the server retrieves historical order records or registration records showing the first string and the delivery destination address. The robot delivery system's server then obtains the user's complete identity. When retrieving the package, the user only needs to enter the fourth string, which is combined with the third string displayed on the system interface. The combined string is then checked for consistency with the first string. Because the server stores matching relationships and complete identity records, and has reliable records of successful deliveries or user-filled information during registration, only a few digits need to be verified. This ensures verification accuracy, simplifies the package entry process, and allows users to retrieve packages without their phones, improving convenience and robot package retrieval efficiency. When a user enters the first string and the server finds no historical waybill or registration record for that string and the delivery destination address, the user must contact the pickup user via virtual phone or text message to verify the pickup user's complete identity. The user then enters this complete identity information into the server's database, such as a complete mobile phone number. This database serves as a mapping record between the delivery address and the complete mobile phone number, simplifying the user's data entry process and verifying the pickup user's identity upon pickup. Upon pickup, the user needs to scan a QR code using a mobile application, sending the complete pickup user identity information authorized for the application. The server then compares this scanned identity with the one entered during storage to determine if the pickup user is the correct recipient for the item on the waybill. In implementation, the storage and retrieval methods can be combined in other ways as needed. For example, when storing an item, if the storage user inputs a first string and the server finds a match between the retrieval user's complete identity and the delivery address, the retrieval user can scan a QR code from a robot and send it to the server. This allows the authorized application's complete identity to be compared with stored identity records in the service area, such as historical orders or registration information, to verify whether the retrieval user is the recipient of the delivered item. Alternatively, if the storage user inputs a first string and the server finds a match between the retrieval user's complete identity and the delivery address, the retrieval user can contact the retrieval user by phone to enter their complete identity. When retrieving the item, the retrieval user inputs a partial string to verify their identity.

[0156] This pickup verification method involves both the pickup user and the storage user entering different fields corresponding to the pickup user's complete identity and contact information at different stages of storage and pickup. This makes the verification more rigorous and adds a secondary verification of the first string entered by the storage user. If the storage user's first string is incorrect, even if the pickup user's fifth string (their own part) is correct, the system can be configured to allow the pickup user to retrieve their item, or it can be configured to prompt the pickup user to re-enter or scan the pickup graphic code. At this point, the delivery system can identify who made the mistake and correct or prompt for correction of the contact information related to the delivery address stored in the database, thus achieving multi-party verification to maintain the accuracy of user identity information.

[0157] Example 5 provides a method for storing and retrieving items using a delivery robot.

[0158] Step S510: Based on the user's scanning operation of the storage item graphic code on the delivery robot, determine the delivery robot's need to deliver the waybill item indicated by the graphic code.

[0159] Step S520: Obtain the delivery destination address information and the first string corresponding to the waybill item entered by the storage user. The first string corresponds to the string formed by the first preset number of digits starting from the first specified position in the identity identifier of the pickup user corresponding to the waybill item to be delivered.

[0160] In step S530, the address information and the first string are sent to the server. The server queries the information records related to the address information of the delivery destination or the identity of the pickup user to see if there is a matching relationship between the address information and the first string formed by the first preset number of digits.

[0161] Step S530: If the address information entered by the user and the first string are found to match, the delivery robot is instructed to open the door and store the item.

[0162] In step S540, the delivery robot opens the empty compartment door that is not yet filled with items and accepts the storage operation from the user.

[0163] In step S550, after the delivery door is closed, the delivery robot performs the task of delivering the items.

[0164] Step S560: When the delivery robot delivers the waybill items to the vicinity of the delivery destination address, the pickup user is notified to pick up the items based on the complete user identity identifier corresponding to the waybill, and the pickup user's pickup request for the waybill items is obtained.

[0165] Step S570: Output a pickup page on the robot screen or the pickup user application terminal. The pickup page provides an input area for the pickup user to input pickup verification characters that match the waybill items. The pickup page displays a third string formed by a third preset number of digits, which corresponds to a portion of the first string input by the storage user.

[0166] Step S580: Obtain the fourth string input by the pickup user. The fourth string is used to verify whether the string formed by combining with the third string matches the first string corresponding to the destination address information where the delivery robot stops. The first string is the first string that is mapped to the delivery destination address information of the waybill item when the user puts the waybill item into the delivery robot.

[0167] Step S590: If the verification and matching pass, confirm that the pickup user matches the waybill item with the destination address information, and open the door of the delivery robot compartment corresponding to the waybill item to be picked up for the pickup user to pick up the item.

[0168] The robot package storage and retrieval method disclosed in this embodiment requires only a small amount of information, such as the delivery address and a first string, for the package storage user to input. The robot delivery system then retrieves the complete user contact information, reducing the number of times the storage user has to ask the retrieval user for complete identification and contact information for each package. It also reduces the error rate caused by the storage user typing information while on the phone, thus reducing the workload of package storage and improving efficiency. Simultaneously, the retrieval process is smoother, requiring less input from the retrieval user, making the retrieval process more efficient and convenient, providing a better user experience, and reducing the retrieval user's concerns about disclosing their contact information.

[0169] Example 6 provides another method for storing and retrieving items using a delivery robot.

[0170] In step S610, the user who stored the item comes to the robot. Based on the user's scanning of the item's graphic code on the delivery robot, the system determines the delivery robot's need to deliver the item indicated by the graphic code.

[0171] Step S620: Obtain the delivery destination address information and the first string corresponding to the waybill item entered by the storage user from the robot screen or the storage application terminal. The first string corresponds to the string formed by the first preset number of digits starting from the first specified position in the identity identifier of the pickup user corresponding to the waybill item to be delivered.

[0172] In step S630, if the server finds no matching relationship between the address information and the first string formed by the first preset number of characters in the information records related to the address information of the delivery destination or the identity of the pickup user, based on the address information and the input first string, it provides an information input interface for the storage user to input a second string consisting of a second preset number of characters representing the user identity of the pickup user corresponding to the waybill item. The second preset number of characters in the second string is longer than the first preset number of characters in the first string. The second string can be a complete user identity, such as a complete mobile phone number. The second string is used to associate and store with the delivery destination address information, and to verify whether the identity of the pickup user corresponds to the waybill item when picking up the package.

[0173] In step S640, the delivery robot opens the empty compartment door that is not yet filled with items and accepts the storage operation from the user.

[0174] In step S650, after the delivery door is closed, the delivery robot performs the task of delivering the items.

[0175] Step S660: After the delivery robot delivers the waybill item to the delivery destination address, obtain the pickup request submitted by the pickup user through the scanning operation of the pickup graphic code of the delivery robot using the target application.

[0176] Step S670: If authorization is obtained to log in to the target application using the pickup user's identity, the pickup user's identity for using the target application is obtained.

[0177] Step S680: If it is determined that the pickup user's identity identifier obtained by scanning the code and the second string corresponding to the waybill item entered by the storage user when storing the item meet the predetermined matching consistency conditions, the pickup user is confirmed to match the waybill item at the destination address where the delivery robot is currently parked, and the door of the compartment corresponding to the waybill item to be picked up is opened for the pickup user to pick up the item.

[0178] The robot package storage and retrieval method of this disclosure only requires the storage user to call and inquire about the retrieval user's real identity or contact information if no matching delivery address and retrieval user's identity and contact information are found in the system. This reduces the number of phone calls and improves storage efficiency. Simultaneously, during retrieval, the complete identity obtained through the application is compared and verified against the retrieval user's input, effectively performing a second verification and enhancing the security of the verification. Furthermore, the retrieval process is smoother and more efficient, providing a better user experience and reducing the retrieval user's concerns about disclosing their contact information.

[0179] In some implementations, if the user cannot complete the verification process to open the robot's compartment and retrieve the goods by scanning a code or entering a partial string, or if the user fails to retrieve the goods in time, causing the items to remain in the robot for an extended period, the robot will return the unretrieved items to a fixed location. Upon return, the items will remain in the robot's compartment for a certain period; alternatively, staff at the fixed location will retrieve the items for re-delivery. Alternatively, the robot can cooperate with a smart delivery station at a fixed location. The robot will transport the unretrieved items to the smart delivery station via a connection point. The smart delivery station will then use a lifting mechanism to transfer the items to designated storage compartments, awaiting retrieval by the user at the self-pickup point. The smart delivery station combines storage compartments and robot access points. The storage compartments are used by personnel to place items into the assigned compartments of the delivery locker, and by users to unlock and retrieve the items after correctly entering the retrieval code or verifying the correspondence between the item and the user. When the robot transports items to the smart delivery station, it opens the corresponding item's compartment door, aligning the bottom plane of the item with the bottom plane of the smart delivery station's storage / retrieval channel. The robot then transports the item through the channel into the delivery station. The delivery station receives the item from the channel and passes it to a lifting platform. This platform can move vertically and in at least one dimension perpendicular to the vertical plane, thus delivering the item to a storage compartment. The server sends a notification to the user that the pickup was not completed. Upon receiving the notification, the user can schedule a re-delivery via the application or pick up the item at a designated location according to the notification instructions. For example, once the item is stored at the delivery station, the user can go to the smart delivery station, find the corresponding storage compartment, complete the verification, and retrieve their item.

[0180] In embodiment seven, this disclosure also provides a robot. The robot 110 includes a chassis, a mobile device, a cargo compartment, a communication device, and a screen device. The screen device can display pages, such as graphic codes, including storage graphic codes or retrieval graphic codes, and can also display an input area. The screen device can operablely receive information input, such as address information, contact information, etc. The robot also includes a memory 1102 and a processor 1101. The memory 1102 stores a computer program, and the processor 1101 is used, under the control of the computer program, to execute relevant steps in the robot storage, retrieval, and delivery method according to any embodiment.

[0181] This disclosure also provides an electronic device including a memory and a processor. The memory stores a computer program, and the processor, under the control of the computer program, executes relevant steps in a robot delivery method according to any embodiment of the method. The electronic device may be any one of a server 1000, a terminal device 2000, a terminal device 4000, or a terminal device 5000.

[0182] This disclosure also provides an embodiment of a computer-readable storage medium storing a computer program that, when executed by a processor, implements a robot access method according to any embodiment of this disclosure.

[0183] This invention can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of the invention.

[0184] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination thereof. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0185] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0186] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0187] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0188] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0189] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions. It will be known to those skilled in the art that implementation in hardware, implementation in software, and implementation using a combination of software and hardware are equivalent.

[0190] The various embodiments of the present invention have been described above. These descriptions are exemplary and not exhaustive, and are not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or technical improvements to the embodiments in the market, or to enable others skilled in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.

Claims

1. A method for storing and retrieving items using a delivery robot, characterized in that, The method includes: Based on the user's scanning of the storage item's graphic code on the delivery robot, the system determines the delivery robot's need to deliver the item indicated by the graphic code. Obtain the delivery destination address information corresponding to the waybill item input by the storage user and a first string, wherein the first string corresponds to the string formed by the first preset number of digits starting from the first specified position in the identity identifier of the pickup user corresponding to the waybill item to be delivered; The server queries the information records related to the address information of the delivery destination or the identity of the pickup user to see if there is a matching relationship between the address information and the first string formed by the first preset number of digits; If the address information entered by the user and the first string are found to match, the delivery robot is instructed to open the door and store the item. The delivery robot opens the empty compartment door that is not yet filled with items and accepts the storage operation of the user. The delivery robot performs the delivery task of the items after the hatch is closed; After the delivery robot delivers the order to the delivery destination address, it obtains the pickup request from the user. The pickup page provides an input area for the pickup user to input a pickup verification character that matches the item on the waybill. The pickup page displays a third string formed by a third preset number of digits, which corresponds to a portion of the first string input by the storage user. Obtain the fourth string input by the pickup user. The fourth string is used to combine with the third string to form a string verification to see if it matches the first string corresponding to the destination address information where the delivery robot stops. The first string is the first string that is mapped to the delivery destination address information of the waybill item when the storage user stores the waybill item into the delivery robot. If the verification and matching are successful, it is confirmed that the pickup user matches the waybill item with the destination address information, and the door of the delivery robot compartment corresponding to the waybill item to be picked up is opened for the pickup user to pick up the item.

2. A method of accessing an item by a delivery robot, the method comprising: The method includes: Based on the user's scanning of the storage item's graphic code on the delivery robot, the system determines the delivery robot's need to deliver the item indicated by the graphic code. Obtain the delivery destination address information corresponding to the waybill item input by the storage user and a first string, wherein the first string corresponds to the string formed by the first preset number of digits starting from the first specified position in the identity identifier of the pickup user corresponding to the waybill item to be delivered; Based on the address information and the input first string, if no matching relationship is found between the address information and the first string formed by the first preset number of characters in the information records related to the address information of the delivery destination or the identity of the pickup user, the server provides an information input interface for the storage user to input a second string composed of a second preset number of characters that represents the user identity of the pickup user corresponding to the waybill item. The second preset number of characters in the second string is more than the first preset number of characters in the first string. The second string is used for associated storage with the address information of the delivery destination. The delivery robot opens the empty compartment door that is not yet filled with items and accepts the storage operation of the user. The delivery robot performs the delivery task of the items after the hatch is closed; After the delivery robot delivers the waybill items to the delivery destination address, it obtains the pickup request from the user by scanning the pickup graphic code of the delivery robot using the target application. If authorization is obtained to log in to the target application using the pickup user's identity identifier, the pickup user's identity identifier for using the target application is obtained; If the identification of the pickup user obtained by scanning the code and the second string corresponding to the waybill item entered by the user when storing the item meet the predetermined matching consistency conditions, it is confirmed that the pickup user matches the waybill item at the destination address where the delivery robot is currently parked, and the door of the compartment corresponding to the waybill item to be picked up is opened for the pickup user to pick up the item.

3. A storage method of a delivery robot characterized by comprising: The method includes: Based on the user's scanning of the storage item's graphic code on the delivery robot, the system determines the delivery robot's need to deliver the item indicated by the graphic code. Obtain the delivery destination address information corresponding to the waybill item input by the storage user and a first string, wherein the first string corresponds to the string formed by the first preset number of digits starting from the first specified position in the identity identifier of the pickup user corresponding to the waybill item to be delivered; The server queries records related to the address information of the delivery destination or the identity of the pickup user to see if there is a matching relationship between the address information and the first string formed by the first preset number of digits. If the address information entered by the user and the first string are found to match, the delivery robot is instructed to open the door and store the item. The delivery robot opens the empty compartment door that is not yet filled with items and accepts the storage operation of the user. The delivery robot performs the delivery task of the items after the hatch is closed.

4. The method of claim 3, further comprising: If no matching relationship is found between the address information and the first string, an information input interface is provided for the deposit user to input the user identity identifier of the pickup user corresponding to the waybill item. The user identity identifier is a second string composed of a second preset number of characters. The second preset number of characters of the second string corresponding to the user identity identifier is more than the first preset number of characters of the first string. The second string is associated with and stored with the delivery destination address information.

5. The method according to claim 3, wherein querying in records related to the address information of the delivery destination or the identity of the pickup user whether there exists a matching relationship between the address information and the first string formed by the first preset number of digits, comprises: Check if there is a record in the historical delivery orders completed by manual or robotic delivery that is associated with the address information and the first string; and / or Check whether there is a record in the historical waybill where the address information of the delivery destination is associated with the first string, which was entered by the user when storing the package or by the user when setting up the pickup.

6. The method according to claim 4, wherein if no matching relationship is found between the address information and the first string, it includes: In historical delivery orders completed manually or by robots, the address information of the delivery destination entered by the user who stored the package, or the first string identifying the user who picked up the package, was not found; and / or In historical delivery orders completed manually or by robots, the address information of the delivery destination entered by the user who stored the package or the first string representing the identity of the user picking up the package do not have a matching relationship.

7. The method of claim 3, wherein: The first string is obtained in the following way: The first string is obtained by querying the delivery waybill or delivery slip; or The first string is obtained by contacting the customer who picked up the package by dialing the virtual number on the delivery slip or waybill and then entering it into the input page. or The first string is obtained by scanning the barcode or number on the order slip using a terminal optical scanning device.

8. The method of claim 3, wherein, The step of querying records related to the delivery destination address information or the pickup user's identity to determine if there is a matching relationship between the address information and the first string formed by the first preset number of digits includes: The first string containing the destination address information or as part of the user's contact information can be found in the waybill data records of orders placed on this platform or by other order service platforms or delivery service platforms, or by querying the online shopping waybill history through a third-party platform server; or The condition is set that the consignment note user has independently completed the pick-up. Based on the complete user identity or contact information, the consignment note without abnormalities is automatically converted into the contact phone number and room number registered by the user, and the address information of the delivery destination is queried in the record information of the contact phone number and room number. The matching relationship associated with the first string is matched.

9. The method of claim 4, wherein: The second string input by the storage user as a complete user identity is associated with the delivery destination address information and stored for future delivery as a query record range. The complete user identity is used for pick-up notification and pick-up verification.

10. A method of picking up an item by a delivery robot, characterized by, The method comprises: After the delivery robot arrives at the delivery destination address, the pick-up user's pick-up request for the consignment note item is obtained; A pick-up page is output, and an input area for the pick-up user to input pick-up verification characters matching the consignment note item is provided on the pick-up page. A third string formed by a third preset number of characters is displayed on the pick-up page. The third string is a part of the first string input by the storage user. The first string is the first string associated with the delivery destination address information of the consignment note item when the consignment note item is stored in the delivery robot. The first string corresponds to a string formed by a first preset number of characters from a first specified position in the pick-up user identity corresponding to the consignment note item to be delivered. The association refers to the matching relationship between the delivery destination address information and the first string found in the information record associated with the delivery destination address information or the pick-up user identity when storing, or the mapping record of the pick-up user identity and the delivery destination address supplemented by the storage user in the case where the matching relationship between the delivery destination address information and the first string is not found in the historical consignment note or registration record when storing; The fourth string input by the pick-up user is obtained. The fourth string is used to verify whether the string formed by combining the third string matches the first string of the delivery consignment note item corresponding to the destination address where the delivery robot stops; If the string formed by combining the fourth string and the third string matches the first string, it is confirmed that the pick-up user matches the consignment note item of the destination address information, and the hatch of the delivery robot cabin corresponding to the consignment note item to be picked up is controlled to be opened for the pick-up user to pick up.

11. The method of claim 10, further comprising: If the string formed by combining the fourth string and the third string does not match the first string, a pick-up graphic code page is displayed or the pick-up user is prompted to use the user identity used when ordering the consignment note item to log in to the target application program to scan the pick-up graphic code for pick-up.

12. A method of picking up an item by a delivery robot, characterized by, The method comprises: After the delivery robot arrives at the delivery destination address, the pick-up user uses the target application program to scan the pick-up graphic code of the delivery robot; In the case of obtaining authorization for the pickup user to log in to the target application program, the pickup user identity of the pickup user using the target application program is obtained; in the case that the identity obtained by the pickup user through scanning the code and the pickup user identity corresponding to the delivery order article input or confirmed by the storage user at the time of storage meet the predetermined matching consistency condition, it is confirmed that the pickup user matches the delivery order article at the destination address currently stopped by the delivery robot, and the door of the cabin corresponding to the delivery order article to be picked up is opened to provide the pickup user with the pickup service, wherein the identity of the pickup user is determined according to the delivery destination address information or the first string query at the time of storage, or is the identity information of the pickup user associated with the delivery destination address information input or confirmed by the user in the case that no matching relationship between the delivery destination address information and the first string is found in the information record related to the delivery destination address information or the pickup user identity at the time of storage, and the first string corresponds to the string formed by the first preset number of positions in the pickup user identity corresponding to the delivery order article to be delivered from the first specified position.

13. The method of claim 12, wherein the pickup user identity corresponding to the delivery order article meets the predetermined matching consistency condition, comprising: comparing the identity obtained by the pickup user through scanning the code with the pickup user identity corresponding to the delivery order article input by the storage user bit by bit, in the case that the identity obtained by the pickup user through scanning the code is consistent with the second string representing the pickup user identity corresponding to the delivery order article input by the storage user, or the number of consistent bits exceeds the threshold condition, it is determined that the predetermined matching consistency condition is met.

14. The method of claim 12, wherein the server sends a result of determining that the identity obtained by the pickup user through scanning the code does not meet the predetermined matching consistency condition with the pickup user identity corresponding to the delivery order article input by the storage user at the time of storage, and provides a prompt page to prompt the pickup user to switch to the identity used to log in to the target application program for scanning pickup when the following order is used.

15. The method of claim 10 or 12, further comprising: providing a delivery address input page to obtain the delivery destination address information input by the pickup user; determining the user identity information of the pickup user logging in to the robot delivery target application program; the server establishes the mapping association of the user identity of the pickup user logging in to the robot delivery target application program as contact information with the delivery destination address information, which is used to verify the matching consistency of the user identity and the delivery destination address information according to the mapping association at the time of storage.

16. The method of claim 15, wherein: The determination of the user identity information of the pickup user logging in to the robot delivery target application program comprises: filling in the identity information by the user to make the server establish the corresponding matching relationship between the delivery address and the identity; or, The method comprises:

17. A method of picking up an item by a delivery robot, characterized by The method comprises: After the delivery robot carrying the delivery order arrives at the delivery destination address, the pickup user's pickup request for the delivery order is obtained; The pickup page is output, and the pickup user is provided with an input area on the pickup page to input the pickup verification character matched with the delivery order; The fifth string input by the pickup user is obtained, and the fifth string is used to check whether the string formed by combining the first string matches the identity of the pickup user corresponding to the delivery order at the destination address where the delivery robot stops, wherein the first string is the first string confirmed by the storage user when storing the delivery order in the delivery robot, which is associated with the delivery destination address information of the delivery order, and the identity of the pickup user is determined according to the delivery destination address information and / or the first string; If the string formed by combining the fifth string and the first string matches the identity of the pickup user, it is confirmed that the pickup user matches the delivery order at the destination address, and the hatch of the delivery robot cabin corresponding to the delivery order to be picked up is opened for the pickup user to take out the corresponding goods.

Images