A delivery recording method and electronic device

By using NFC tags with UIDs for automatic binding and recording on delivery equipment, the problems of inefficiency and lack of authenticity in existing delivery recording methods are solved, achieving efficient and reliable delivery recording.

CN123117952APending Publication Date: 2026-11-17RAJAX NETWORK &TECHNOLOGY (SHANGHAI) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611344737.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-31
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing delivery record methods are inefficient and their authenticity is difficult to guarantee. Delivery personnel have complicated procedures, which can easily lead to impersonation or incorrect records.

Method used

The delivery equipment and delivery personnel are bound together using the UID of the NFC tag. The mobile terminal reads the UID of the NFC tag and combines it with the locally cached binding status to automatically request the delivery server to perform binding or recording operations, ensuring the convenience and authenticity of delivery records.

Benefits of technology

It significantly improves the efficiency and authenticity of delivery records, simplifies operational processes, reduces the risk of false records, and significantly shortens the training and deployment cycle, especially when adding new sites.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123117952A_ABST
    Figure CN123117952A_ABST
Patent Text Reader

Abstract

This invention discloses a delivery recording method and electronic device, relating to the field of logistics and delivery. The delivery recording method includes: reading the UID of an NFC tag on a delivery device; determining the operational relationship between the currently logged-in user and the delivery device based on the read UID and the binding status of the currently logged-in user cached locally; if the operational relationship is a pending binding relationship, sending a binding request to a delivery server, so that the delivery server binds the currently logged-in user to the delivery device after verifying the binding request; if the operational relationship is a pending recording relationship, sending a recording request to the delivery server, so that the delivery server records the attendance information of the currently logged-in user after verifying the recording request. This method can improve the efficiency, authenticity, and reliability of delivery recording.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of logistics and distribution technology, specifically to a delivery recording method and electronic device. Background Technology

[0002] Delivery records are a fundamental element of logistics and on-demand delivery management, used to confirm delivery personnel's attendance, pickup activities, and delivery status. Traditional delivery record-keeping methods typically rely on manual sign-in, paper documents, or card swipes.

[0003] Currently, the most common delivery recording methods are scanning QR codes or manually entering identification codes. Specifically, QR codes are set up at delivery stations, and delivery personnel scan them using a mobile application. The system records the operation time and the delivery personnel's identity, completing the delivery record. Alternatively, some methods use identification codes (such as a string of numbers or characters). Delivery personnel need to manually enter this code in the application beforehand to complete the binding. Afterward, each time a delivery is made, the delivery personnel enter the identification code in the application and send a recording request. The system then records the corresponding delivery personnel information based on the identification code.

[0004] However, the aforementioned delivery record scheme still suffers from inefficiency and difficulty in guaranteeing the accuracy of delivery records. Delivery personnel face cumbersome procedures, and instances of impersonation or incorrect recording occur frequently. Therefore, improving the efficiency and accuracy of delivery records has become a pressing technical problem to be solved in this field. Summary of the Invention

[0005] This invention aims to address, to a certain extent, one of the technical problems in related technologies. To this end, this invention provides a delivery recording method and electronic device, which have the advantages of improving the efficiency, authenticity, and reliability of delivery records.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: A delivery recording method, applied to a mobile terminal, wherein the delivery recording method includes: Read the UID of the NFC tag on the delivery equipment; Based on the read UID and the binding status of the currently logged-in user cached locally, the operational relationship between the currently logged-in user and the delivery equipment is determined; If the operation relationship is a pending binding relationship, a binding request is sent to the delivery server so that the delivery server binds the currently logged-in user to the delivery equipment after verifying the binding request. When the operation relationship is a pending record relationship, a record request is sent to the delivery service terminal so that the delivery service terminal records the attendance information of the currently logged-in user after verifying the record request.

[0007] Optionally, the binding status includes the user ID of the currently logged-in user and the UID of the NFC tag on the corresponding delivery equipment; The step of determining the operational relationship between the currently logged-in user and the delivery equipment based on the read UID and the locally cached binding status of the currently logged-in user includes: If the UID corresponding to the user ID of the currently logged-in user is empty, it is determined that the currently logged-in user and the delivery equipment are to be bound together. If the UID corresponding to the user ID of the currently logged-in user is the read UID, then the relationship between the currently logged-in user and the delivery equipment is determined to be to be recorded.

[0008] Optionally, the delivery record method further includes: If the UID corresponding to the currently logged-in user's user ID is not empty and is not the read UID, display an error message about the delivery equipment.

[0009] Optionally, the delivery record method further includes: Receive a successful binding response from the delivery service. In the locally cached binding state, update the UID corresponding to the user ID of the currently logged-in user to the read UID.

[0010] Optionally, the method further includes: Upon detecting an NFC tag on the delivery equipment, the delivery client installed on the mobile terminal is activated according to the response rules for NFC tag discovery events pre-configured in the mobile terminal. The delivery client is invoked to read the UID of the NFC tag on the delivery equipment.

[0011] The present invention also provides a delivery recording method, applied to a delivery service, wherein the delivery recording method includes: Receive an operation request sent by a mobile terminal; wherein the operation request is sent by the mobile terminal after determining the operation relationship based on the UID of the NFC tag on the delivery equipment and the binding status of the currently logged-in user cached locally; If the operation request is the first one received within a preset time window, determine the type of the operation request; If the operation request is a binding request, the binding request is verified, and the currently logged-in user is bound to the delivery equipment after the verification is successful; If the operation request is a record request, the record request is verified, and the attendance information of the currently logged-in user is recorded after the verification is successful.

[0012] Optionally, the record request carries the UID and the user ID of the currently logged-in user; the step of verifying the record request and recording the attendance information of the currently logged-in user after successful verification includes: Based on the binding relationship stored locally, the user ID and UID of the currently logged-in user are identified; If a binding relationship is identified between the two, the matching relationship between the current time and the preset time window is identified; If the current time matches a preset time window, retrieve the attendance record for the current date; If the attendance record indicates that the currently logged-in user has not yet generated any records, the verification is deemed successful, and the attendance information of the currently logged-in user is updated in the attendance record.

[0013] Optionally, the binding request carries the UID and the user ID of the currently logged-in user; the verification of the binding request includes: Verify the login status and identity legitimacy of the currently logged-in user's user ID; If the verification passes, check if the delivery equipment corresponding to the UID exists; If the delivery equipment is not present, the binding request is rejected; If the delivery equipment exists, query the binding status of the delivery equipment; If the delivery equipment is currently in an unbound state, the verification is deemed successful. If the delivery equipment is currently in a bound state, the binding request is rejected.

[0014] Optionally, binding the currently logged-in user to the delivery equipment includes: Establish and store the binding relationship between the user ID of the currently logged-in user and the UID; Update the binding status of the delivery equipment to "bound"; A successful binding response is returned to the mobile terminal, causing the mobile terminal to update the binding status of the currently logged-in user in its local cache.

[0015] Delivery equipment is centrally located at delivery stations. Upon arrival, delivery users can tap the equipment with their mobile devices. The mobile device reads the UID of the NFC tag on the equipment and, combined with the currently logged-in user's binding status cached locally, determines the operational relationship. If binding is required, the mobile device automatically requests the delivery server to bind the currently logged-in user to the delivery equipment. If recording is required, the mobile device automatically requests the delivery server to record the currently logged-in user's attendance information. Throughout the entire process, whether it's initial binding or subsequent recording, the delivery user only needs to perform a simple operation once, significantly improving ease of use and thus significantly improving the efficiency of delivery recording.

[0016] For scenarios involving batch binding when adding new delivery stations, this method further improves the efficiency of delivery records. For example, when a new delivery station is added in a city, 50 insulated boxes with fixed NFC tags are distributed at once. Deliverymen only need to use their mobile terminals to touch their respective insulated boxes to automatically complete the binding process. The average time taken per person is no more than 15 seconds, which can significantly shorten the training and deployment cycle and improve the efficiency of delivery records.

[0017] Existing delivery record solutions typically only verify time and location, which is prone to fraudulent records: attendance cards, QR codes, and identification codes are easily copied and misused. This invention utilizes the globally unique characteristic (UID) of NFC tags to forcibly associate delivery record operations with the delivery user's linked delivery equipment. This ensures that each delivery record operation requires the simultaneous presence of the delivery user and their linked equipment, thereby guaranteeing an undeniable correspondence between the recorded result and the actual operator, thus improving the authenticity and reliability of delivery records.

[0018] Furthermore, the present invention also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the delivery record method described in any of the preceding claims.

[0019] These features and advantages of the present invention will be disclosed in detail in the following specific embodiments and accompanying drawings. The preferred embodiments or means of the present invention will be shown in detail in conjunction with the accompanying drawings, but are not intended to limit the technical solutions of the present invention. In addition, each of these features, elements and components appearing in the following text and drawings is a plurality of, and different symbols or numbers are used for convenience of representation, but all represent parts with the same or similar construction or function. Attached Figure Description

[0020] The present invention will be further described below with reference to the accompanying drawings: Figure 1 This is a flowchart illustrating one implementation of the mobile terminal-side delivery recording method provided in this invention. Figure 2This is a flowchart illustrating one implementation method for determining operational relationships provided in an embodiment of the present invention. Figure 3 This is a flowchart illustrating another implementation of the mobile terminal-side delivery recording method provided in this invention. Figure 4 This is a flowchart illustrating another implementation of the mobile terminal-side delivery recording method provided in this invention. Figure 5 This is a flowchart illustrating another embodiment of the mobile terminal-side delivery recording method provided in this invention. Figure 6 This is a flowchart illustrating one implementation of the delivery record method on the delivery service side provided in this invention. Figure 7 This is a flowchart illustrating one implementation of verifying record requests and recording attendance information provided in an embodiment of the present invention. Figure 8 This is a flowchart illustrating one implementation of the verification binding request provided in an embodiment of the present invention. Figure 9 This is a flowchart illustrating one implementation method of binding login users and delivery equipment provided in an embodiment of the present invention; Figure 10 This is a structural block diagram of the electronic device provided in an embodiment of the present invention.

[0021] Explanation of reference numerals in the attached figures 101: Processor, 102: Memory, 103: I / O interface, 104: Bus. Detailed Implementation

[0022] Embodiments of the present invention are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described are intended to explain the present invention and should not be construed as limiting the invention.

[0023] The terms "an embodiment," "example," or "trademark" used in this specification refer to a particular feature, structure, or characteristic described in connection with the embodiment itself that may be included in at least one embodiment disclosed in this invention. The phrase "in an embodiment" appearing in various places throughout the specification does not necessarily refer to the same embodiment.

[0024] Currently, existing delivery record systems still suffer from inefficiency and difficulty in ensuring the authenticity of delivery records. Delivery personnel face cumbersome procedures, and instances of impersonation or incorrect recording occur frequently.

[0025] To improve the efficiency and accuracy of delivery records, as a first aspect of this invention, a delivery record method is provided, applied to a mobile terminal, such as... Figure 1 As shown, the delivery record method includes: In step S110, the UID of the NFC tag on the delivery equipment is read; In step S120, the operational relationship between the current logged-in user and the delivery equipment is determined based on the read UID and the binding status of the currently logged-in user cached locally. In step S130, if the operation relationship is a pending binding relationship, a binding request is sent to the delivery server so that the delivery server binds the currently logged-in user to the delivery equipment after verifying the binding request. In step S140, if the operation relationship is a pending record relationship, a record request is sent to the delivery service terminal so that the delivery service terminal records the attendance information of the currently logged-in user after verifying the record request.

[0026] The technical solution of the present invention can be applied to the transaction and delivery services of instant e-commerce platforms, such as Taobao Flash Sale, Taoxianda, Ele.me takeaway and retail.

[0027] The mobile terminal is held by the delivery user, while the delivery service is the back-end management system. It can be understood that the mobile terminal has NFC functionality, and the mobile terminal and the delivery service can communicate and interact.

[0028] The delivery equipment may include helmets, work clothes, food containers, etc. This invention fixes NFC tags with UIDs onto the delivery equipment. For example, it uses NTAG215 series passive NFC tags with globally unique 7-byte UIDs, supporting password protection and WIPRO waterproof encapsulation, and withstanding temperatures from -20℃ to 80℃. These tags are fixed to non-metallic areas on the inner wall of the insulated box, helmet linings, or other concealed and wear-resistant locations to avoid signal shielding and physical damage. In the NFC tag's memory, the read-only area (Pages 0–3) stores the manufacturer information and UID, which is factory-locked to prevent tampering. The user memory area (Pages 4–12) is reserved for writing optional lightweight metadata such as binding timestamps and device codes. Lock bits are used to permanently lock the UID area to prevent cloning or rewriting.

[0029] Delivery equipment is centrally located at delivery stations. Upon arrival, delivery users can tap the equipment with their mobile devices. The mobile device reads the UID of the NFC tag on the equipment and, combined with the currently logged-in user's binding status cached locally, determines the operational relationship. If binding is required, the mobile device automatically requests the delivery server to bind the currently logged-in user to the delivery equipment. If recording is required, the mobile device automatically requests the delivery server to record the currently logged-in user's attendance information. Throughout the entire process, whether it's initial binding or subsequent recording, the delivery user only needs to perform a simple operation once, significantly improving ease of use and thus significantly improving the efficiency of delivery recording.

[0030] For scenarios involving batch binding when adding new delivery stations, this method further improves the efficiency of delivery records. For example, when a new delivery station is added in a city, 50 insulated boxes with fixed NFC tags are distributed at once. Deliverymen only need to use their mobile terminals to touch their respective insulated boxes to automatically complete the binding process. The average time taken per person is no more than 15 seconds, which can significantly shorten the training and deployment cycle and improve the efficiency of delivery records.

[0031] Existing delivery record solutions typically only verify time and location, which is prone to fraudulent records: attendance cards, QR codes, and identification codes are easily copied and misused. This invention utilizes the globally unique characteristic (UID) of NFC tags to forcibly associate delivery record operations with the delivery user's linked delivery equipment. This ensures that each delivery record operation requires the simultaneous presence of the delivery user and their linked equipment, thereby guaranteeing an undeniable correspondence between the recorded result and the actual operator, thus improving the authenticity and reliability of delivery records.

[0032] In some embodiments, the binding status includes the user ID of the currently logged-in user and the UID of the corresponding NFC tag on the delivery equipment; such as Figure 2 As shown, determining the operational relationship between the currently logged-in user and the delivery equipment based on the read UID and the locally cached binding status of the currently logged-in user includes: In step S210, if the UID corresponding to the user ID of the currently logged-in user is empty, it is determined that the currently logged-in user and the delivery equipment are to be bound. In step S220, if the UID corresponding to the user ID of the currently logged-in user is the read UID, it is determined that the currently logged-in user and the delivery equipment are in a relationship to be recorded.

[0033] If, after querying the local cached binding status, the mobile terminal finds that the UID corresponding to the currently logged-in user's user ID is empty, it means that the currently logged-in user has not bound any delivery equipment, that is, the currently logged-in user has not bound the delivery equipment it touched. At this time, it is determined that the two are in a pending binding relationship. If it is found that the UID corresponding to the currently logged-in user's user ID is consistent with the read UID, it means that the currently logged-in user has bound the delivery equipment it touched. At this time, it is determined that the two are in a pending recording relationship.

[0034] For the pending binding relationship, the mobile terminal then sends a binding request to the delivery service. For example, the following API call format can be used: POST / api / v1 / equipment / bind / / Request method and path: Sends a binding request to the server. Content-Type: application / json / / The data format of the request body is JSON. { "riderId": "R123456", / / The unique user ID of the currently logged-in rider "equipmentUid": "A1B2C3D4E5F6G7", / / UID read from the NFC tag on the delivery equipment "timestamp": "2025-12-05 08:00:00", / / Timestamp of the touch event (generated by the client) "location": { "lat": 30.2741, "lng": 120.1551} / / Geographical location (latitude and longitude) at the time of the touch, used for subsequent risk control or regional restrictions. }

[0035] For the relationship to be recorded, the mobile terminal then sends a record request to the delivery server. For example, the following API call format can be used: POST / api / v1 / attendance / clock-in / / Request method and path: Sends a record request to the server. { "riderId": "R123456", / / The unique user ID of the currently logged-in rider "equipmentUid": "A1B2C3D4E5F6G7", / / UID read from the NFC tag on the delivery equipment "timestamp": "2025-12-05 07:30:00", / / Timestamp of the touch event (generated by the client) "deviceModel": "Samung Galaxy S23" / / The device model of the mobile terminal, used to assist in risk control or auditing. }

[0036] In some embodiments, such as Figure 3 As shown, the delivery record method further includes: In step S310, if the UID corresponding to the user ID of the currently logged-in user is not empty and is not the read UID, an error message for the delivery equipment is displayed.

[0037] If, after querying the binding status in the local cache, the mobile terminal finds that the UID corresponding to the currently logged-in user's user ID is not empty, but is not the same as the read UID, it means that the delivery equipment that the currently logged-in user has bound is not the delivery equipment that the user is currently touching. In other words, the currently logged-in user is touching the delivery equipment of another delivery user. At this time, a delivery equipment error message is displayed to prompt the currently logged-in user to use their own equipment.

[0038] In some embodiments, such as Figure 4 As shown, the delivery record method further includes: In step S410, a successful binding response is received from the delivery service. In step S430, in the locally cached binding state, the UID corresponding to the user ID of the currently logged-in user is updated to the read UID.

[0039] As described above, after the binding request is verified, the delivery server binds the currently logged-in user to the delivery equipment. Upon successful binding, the delivery server returns a binding success response to the mobile terminal. The mobile terminal updates the UID corresponding to the currently logged-in user's user ID in its locally cached binding status to the read UID. Thus, when the currently logged-in user touches the same delivery equipment again using the mobile terminal, the mobile terminal can recognize that the currently logged-in user is touching the bound delivery equipment, thereby determining that there is a recordable relationship between the two.

[0040] In some embodiments, such as Figure 5 As shown, the method further includes: In step S510, when an NFC tag is detected on the delivery equipment, the delivery client installed on the mobile terminal is woken up according to the response rules for NFC tag discovery events pre-configured in the mobile terminal. In step S520, the delivery client is invoked to read the UID of the NFC tag on the delivery equipment.

[0041] The mobile terminal has a delivery client (i.e., a delivery APP) installed, and the delivery client is configured with NFC tag discovery event response rules. Thus, when the delivery user touches the delivery equipment with their mobile terminal, the mobile terminal detects the NFC tag on the delivery equipment based on its NFC function. In response to the pre-configured NFC tag discovery event response rules, the delivery client is woken up, and the delivery client reads the UID of the NFC tag on the delivery equipment, that is, the delivery record method provided by the present invention is automatically executed.

[0042] In this embodiment of the invention, the response rules for the NFC tag discovery event are not specifically limited, as long as the corresponding function is available.

[0043] Taking a mobile terminal using the Android operating system as an example, NFC permissions and functional dependencies can be declared in the AndroidManifest.xml file of the delivery client: <uses-permission android:name="android.permission.NFC" / > / / Declare that the app needs permission to access the mobile terminal's NFC hardware. <uses-feature android:name="android.hardware.nfc" android:required="true" / > / / Inform the app store that this app requires NFC to function, therefore only NFC-enabled mobile devices can install this app. You can also override the onNewIntent method in the main Activity to register a listener for the NFC tag discovery event: @Override protected void onNewIntent(Intent intent) { / / Determine if the current Intent is an NFC tag discovery event. if(NfcAdapter.ACTION_TAG_DISCOVERED.equals(intent.getAction())){ / / Retrieve the Tag object from the Intent, which contains the raw data of the NFC tag. Tag tag = intent.getParcelableExtra(NfcAdapter.EXTRA_TAG); / / Convert the Tag's unique identifier (UID) from a byte array to a hexadecimal string. String uid=bytesToHex(tag.getId()); / / Call a custom method to handle binding or attendance processes based on the UID and local cache status. handleNfcEvent(uid); } }

[0044] To improve the efficiency and accuracy of delivery records, as a second aspect of this invention, a delivery record method is provided, applied to a delivery service, such as... Figure 6 As shown, the delivery record method includes: In step S610, an operation request sent by a mobile terminal is received; wherein, the operation request is sent by the mobile terminal after determining the operation relationship based on the UID of the NFC tag on the delivery equipment and the binding status of the currently logged-in user cached locally. In step S620, if the operation request is the first one received within a preset time window, the type of the operation request is determined; In step S630, if the operation request is a binding request, the binding request is verified, and after successful verification, the currently logged-in user is bound to the delivery equipment; In step S640, if the operation request is a record request, the record request is verified, and the attendance information of the currently logged-in user is recorded after the verification is successful.

[0045] The delivery record method executed on the mobile terminal side has been explained in detail above, so it will not be repeated here.

[0046] The delivery server employs a replay attack prevention mechanism, which detects whether the mobile terminal sends multiple operation requests with the same content to the delivery server within a preset time window. If so, it prevents the data packet from being retransmitted; otherwise, it begins processing the operation request.

[0047] In this embodiment of the invention, the preset time window is not specifically limited. For example, the preset time window can be 5 seconds, 10 seconds, etc.

[0048] Delivery equipment is centrally located at delivery stations. Upon arrival, delivery users can tap the equipment with their mobile devices. The mobile device reads the UID of the NFC tag on the equipment and, combined with the currently logged-in user's binding status cached locally, determines the operational relationship. If binding is required, the mobile device automatically requests the delivery server to bind the currently logged-in user to the delivery equipment. If recording is required, the mobile device automatically requests the delivery server to record the currently logged-in user's attendance information. Throughout the entire process, whether it's initial binding or subsequent recording, the delivery user only needs to perform a simple operation once, significantly improving ease of use and thus significantly improving the efficiency of delivery recording.

[0049] For scenarios involving batch binding when adding new delivery stations, this method further improves the efficiency of delivery records. For example, when a new delivery station is added in a city, 50 insulated boxes with fixed NFC tags are distributed at once. Deliverymen only need to use their mobile terminals to touch their respective insulated boxes to automatically complete the binding process. The average time taken per person is no more than 15 seconds, which can significantly shorten the training and deployment cycle and improve the efficiency of delivery records.

[0050] Existing delivery record solutions typically only verify time and location, which is prone to fraudulent records: attendance cards, QR codes, and identification codes are easily copied and misused. This invention utilizes the globally unique characteristic (UID) of NFC tags to forcibly associate delivery record operations with the delivery user's linked delivery equipment. This ensures that each delivery record operation requires the simultaneous presence of the delivery user and their linked equipment, thereby guaranteeing an undeniable correspondence between the recorded result and the actual operator, thus improving the authenticity and reliability of delivery records.

[0051] In some embodiments, the record request carries the UID and the user ID of the currently logged-in user; such as Figure 7 As shown, the step of verifying the record request and recording the attendance information of the currently logged-in user after successful verification includes: In step S710, the user ID and UID of the currently logged-in user are identified according to the binding relationship stored locally; In step S720, if a binding relationship is identified between the two, the matching relationship between the current time and the preset time window is identified; In step S730, if the current time is found to match a preset time window, the attendance record for the current date is obtained; In step S740, if it is determined that the currently logged-in user has not yet generated a record based on the attendance record, the verification is deemed successful, and the attendance information of the currently logged-in user is updated in the attendance record.

[0052] For recording requests, the delivery server primarily verifies the binding relationship between the user ID and the NFC tag's UID, the reasonableness of the requested recording time, and whether there is duplicate recording. Specifically, the delivery server locally stores a one-to-one binding relationship between each user ID and each UID. Based on this, it identifies whether the user ID and UID carried in the recording request have a binding relationship. It verifies the reasonableness of the requested recording time by comparing the current time with a preset time window, and verifies whether there is duplicate recording for the same day by querying the day's attendance records.

[0053] If all verifications pass, the delivery server will update the attendance information of the currently logged-in user in the attendance records. For example, it will record the attendance log in the `attendance_log` table and generate a unique `record_id`. The delivery server will then send a success message to the mobile device.

[0054] In some embodiments, the binding request carries the UID and the user ID of the currently logged-in user; such as Figure 8 As shown, the verification of the binding request includes: In step S810, the login status and identity legitimacy of the currently logged-in user's user ID are verified; In step S820, if the verification passes, the system checks whether the delivery equipment corresponding to the UID exists. In step S830, if the delivery equipment does not exist, the binding request is rejected; In step S840, if the delivery equipment exists, the binding status of the delivery equipment is queried; In step S850, if the delivery equipment is currently in an unbound state, the verification is deemed successful. In step S860, if the delivery equipment is currently in a bound state, the binding request is rejected.

[0055] For binding requests, the delivery server primarily verifies the user's login status and identity legitimacy, the validity of the UID, and the UID's occupancy status (i.e., whether the corresponding delivery equipment has already been bound). Specifically, this can be achieved using pre-established user ID whitelists and UID whitelists. If the UID in the binding request does not exist in the whitelists, it means the delivery equipment does not exist, and the binding request is rejected. If the UID in the binding request exists in the whitelists and is already in use, it means the delivery equipment is currently in a bound state, and the binding request is rejected. If the UID in the binding request exists in the whitelists and is not in use, it means the delivery equipment is currently in an unbound state, the verification is successful, and the binding is performed.

[0056] In some embodiments, such as Figure 9 As shown, binding the currently logged-in user with the delivery equipment includes: In step S910, a binding relationship is established and stored between the user ID of the currently logged-in user and the UID; In step S920, the binding status of the delivery equipment is updated to a bound status; In step S930, a successful binding response is returned to the mobile terminal, so that the mobile terminal updates the binding status of the currently logged-in user in its local cache.

[0057] Upon successful verification of the binding request, the delivery server establishes and stores the binding relationship between the currently logged-in user's user ID and the UID. For example, it updates this relationship in the binding relationship table `rider_equipment_binding`, and updates the binding status of the delivery equipment to "bound." This is done by modifying the corresponding delivery equipment status to "bound" in the device database and recording the corresponding user ID. Finally, the delivery server returns a binding success response to the mobile terminal, causing the mobile terminal to update its locally cached binding status of the currently logged-in user and trigger a binding success notification on its delivery client.

[0058] As a third aspect of the present invention, this embodiment also provides an electronic device, wherein, as Figure 10 As shown, the electronic device includes: One or more processors 101; The memory 102 stores one or more computer programs that, when executed by the one or more processors 101, cause the one or more processors 101 to implement the delivery record method provided by the first or second aspect of the embodiments of the present invention.

[0059] The electronic device may also include one or more I / O interfaces 103 connected between the processor 101 and the memory 102, configured to enable information interaction between the processor 101 and the memory 102.

[0060] The processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read-write interface) is connected between the processor and the memory, enabling information exchange between the processor and the memory, including but not limited to a data bus (Bus).

[0061] In some embodiments, the processor 101, memory 102, and I / O interface 103 are interconnected via bus 104, and thus connected to other components of the computing device.

[0062] Meanwhile, embodiments of the present invention also provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the delivery record method provided by the first or second aspect of the embodiments of the present invention.

[0063] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. Accordingly, the computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can implement the methods of any of the above embodiments. Any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0064] The above are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Those skilled in the art should understand that the present invention includes, but is not limited to, the contents described in the accompanying drawings and the specific embodiments above. Any modifications that do not depart from the functional and structural principles of the present invention will be included within the scope of the claims.

Claims

1. A delivery recording method, applied to a mobile terminal, characterized in that, The delivery record method includes: Read the UID of the NFC tag on the delivery equipment; Based on the read UID and the binding status of the currently logged-in user cached locally, the operational relationship between the currently logged-in user and the delivery equipment is determined; If the operation relationship is a pending binding relationship, a binding request is sent to the delivery server so that the delivery server binds the currently logged-in user to the delivery equipment after verifying the binding request. When the operation relationship is a pending record relationship, a record request is sent to the delivery service terminal so that the delivery service terminal records the attendance information of the currently logged-in user after verifying the record request.

2. The delivery record method according to claim 1, characterized in that, The binding status includes the user ID of the currently logged-in user and the UID of the NFC tag on the corresponding delivery equipment; The step of determining the operational relationship between the currently logged-in user and the delivery equipment based on the read UID and the locally cached binding status of the currently logged-in user includes: If the UID corresponding to the user ID of the currently logged-in user is empty, it is determined that the currently logged-in user and the delivery equipment are to be bound together. If the UID corresponding to the user ID of the currently logged-in user is the read UID, then the relationship between the currently logged-in user and the delivery equipment is determined to be to be recorded.

3. The delivery record method according to claim 2, characterized in that, The delivery record method also includes: If the UID corresponding to the currently logged-in user's user ID is not empty and is not the read UID, display an error message about the delivery equipment.

4. The delivery record method according to any one of claims 1-3, characterized in that, The delivery record method also includes: Receive a successful binding response from the delivery service. In the locally cached binding state, update the UID corresponding to the user ID of the currently logged-in user to the read UID.

5. The delivery record method according to any one of claims 1-3, characterized in that, The method further includes: Upon detecting an NFC tag on the delivery equipment, the delivery client installed on the mobile terminal is activated according to the response rules for NFC tag discovery events pre-configured in the mobile terminal. The delivery client is invoked to read the UID of the NFC tag on the delivery equipment.

6. A delivery recording method, applied to a delivery service, characterized in that, The delivery record method includes: Receive an operation request sent by a mobile terminal; wherein the operation request is sent by the mobile terminal after determining the operation relationship based on the UID of the NFC tag on the delivery equipment and the binding status of the currently logged-in user cached locally; If the operation request is the first one received within a preset time window, determine the type of the operation request; If the operation request is a binding request, the binding request is verified, and the currently logged-in user is bound to the delivery equipment after the verification is successful; If the operation request is a record request, the record request is verified, and the attendance information of the currently logged-in user is recorded after the verification is successful.

7. The delivery record method according to claim 6, characterized in that, The record request carries the UID and the user ID of the currently logged-in user; the verification of the record request, and the recording of the attendance information of the currently logged-in user after successful verification, includes: Based on the binding relationship stored locally, the user ID and UID of the currently logged-in user are identified; If a binding relationship is identified between the two, the matching relationship between the current time and the preset time window is identified; If the current time matches a preset time window, retrieve the attendance record for the current date; If the attendance record indicates that the currently logged-in user has not yet generated any records, the verification is deemed successful, and the attendance information of the currently logged-in user is updated in the attendance record.

8. The delivery record method according to claim 6, characterized in that, The binding request carries the UID and the user ID of the currently logged-in user; the verification of the binding request includes: Verify the login status and identity legitimacy of the currently logged-in user's user ID; If the verification passes, check if the delivery equipment corresponding to the UID exists; If the delivery equipment is not present, the binding request is rejected; If the delivery equipment exists, query the binding status of the delivery equipment; If the delivery equipment is currently in an unbound state, the verification is deemed successful. If the delivery equipment is currently in a bound state, the binding request is rejected.

9. The delivery record method according to claim 8, characterized in that, The step of binding the currently logged-in user with the delivery equipment includes: Establish and store the binding relationship between the user ID of the currently logged-in user and the UID; Update the binding status of the delivery equipment to "bound"; A successful binding response is returned to the mobile terminal, causing the mobile terminal to update the binding status of the currently logged-in user in its local cache.

10. An electronic device, characterized in that, include: One or more processors; A memory having stored one or more computer programs thereon, which, when executed by the one or more processors, cause the one or more processors to implement the delivery record method according to any one of claims 1 to 9.