Logistics transfer processing method, electronic device, storage medium, and program product

Abstract

The application relates to the field of intelligent logistics and electronic commerce logistics management, in particular to a logistics transfer processing method, an electronic device, a storage medium and a program product. In view of the problems that, in the prior art, after the change of a receiving address, the historical address is still easy to be used, the user needs to apply for readdressing manually afterwards, the processing is lagged and the misdelivery and stagnation are easy to occur, the following scheme is provided: in a logistics service platform, the receiving user and the original receiving address corresponding to a logistics waybill are acquired in a waybill address identification stage, and matching judgment is performed based on the association relationship between the original receiving address and the pre-set receiving address of the receiving user; when there is an associated transfer address, the waybill receiving address is automatically switched to the corresponding transfer address, so as to guide the subsequent transportation route adjustment of the package. The scheme can correct the address in advance in the early stage of logistics circulation, reduce the user remedial operation, improve the timeliness, accuracy and processing continuity of the transfer in the address change scenario, and reduce the risk of misdelivery and stagnation.

Description

Technical Field

[0001] This application relates to the technical field, and in particular to a logistics transfer and processing method, electronic equipment, storage medium, and program product. Background Technology

[0002] In the express delivery and logistics sector, the handling of packages after a user's delivery address has changed is usually done through methods such as manually applying for forwarding, modifying historical addresses across platforms, or coordinating changes to delivery information before delivery.

[0003] However, the above methods generally rely on users to actively discover and handle the package after it is ordered or transferred, lacking pre-management of the continuous use of historical addresses, resulting in a long operation chain and easy omissions; at the same time, the forwarding judgment usually lacks sufficient verification of factors such as address validity and package suitability for forwarding, making it difficult to balance processing timeliness and delivery stability.

[0004] Therefore, how to improve the efficiency of parcel forwarding in scenarios where the recipient's address changes has become an urgent technical problem to be solved. Summary of the Invention

[0005] This application provides a logistics transfer processing method, electronic device, storage medium, and program product to solve the aforementioned technical problems. This method addresses the processing needs of logistics waybills in scenarios where the recipient address changes. It identifies and processes the recipient address of the package to be delivered, based on the relationship between the logistics waybill, the recipient, and the recipient address. This allows for timely response to logistics transfer needs even when the user's historical recipient address is continuously used, reducing additional user intervention during package transfer and improving the accuracy and stability of transfer processing in address change scenarios.

[0006] In a first aspect, embodiments of this application provide a logistics transfer processing method, including:

[0007] Determine the recipient and primary delivery address information for the logistics waybill;

[0008] When the first delivery address information has associated transit address information, the first delivery address information of the logistics waybill will be modified to the transit address information, which is the delivery address preset by the recipient.

[0009] In one possible embodiment, it also includes:

[0010] Obtain the address association instruction from the recipient. The address association instruction is used to associate one or more second delivery address information with a transit address information.

[0011] Execute the address association instruction.

[0012] In one possible embodiment, before modifying the first delivery address information of the logistics waybill to the transit address information, at least one of the following is included:

[0013] Verify the association between the primary delivery address information and the transit address information;

[0014] Verify the transit address information;

[0015] Verify the package type on the logistics waybill;

[0016] Verify the cost information for transferring goods from the first delivery address to the transfer address.

[0017] In one possible embodiment, modifying the first delivery address information of the logistics waybill to the transit address information includes:

[0018] Send a transfer notification to the first terminal device of the sender corresponding to the logistics waybill;

[0019] Receive transfer permission information sent by the first terminal device. The transfer permission information is used to indicate whether the sender agrees or disagrees to change the first delivery address information of the logistics waybill to the transfer address information.

[0020] When the transfer permission information indicates that the sender agrees to change the first delivery address information of the logistics waybill to the transfer address information, the first delivery address information of the logistics waybill will be changed to the transfer address information.

[0021] In one possible embodiment, it also includes:

[0022] Send a successful transfer notification and forwarding record information to the recipient's second terminal device.

[0023] In one possible embodiment, the first delivery address information includes associated transit address information, including:

[0024] Semantic parsing is performed on the first delivery address information to obtain the first semantic information;

[0025] Determine the semantic similarity between the first semantic information and the second delivery address information;

[0026] When the semantic similarity is greater than a preset first threshold, it is determined that the first delivery address information has associated transit address information.

[0027] In one possible embodiment, it also includes:

[0028] Generate and store the address change log of the logistics waybill. The address change log includes at least one of the following: waybill identifier, first receiving address information, transit address information, change time, and verification result.

[0029] Secondly, embodiments of this application provide a logistics transfer and processing apparatus, comprising:

[0030] The determination module is used to determine the recipient and primary delivery address information for the logistics waybill;

[0031] The processing module is used to modify the first delivery address information of the logistics waybill to the transit address information when the first delivery address information has associated transit address information. The transit address information is the delivery address preset by the receiving user.

[0032] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0033] The memory stores the instructions that the computer executes;

[0034] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0035] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0036] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0037] The logistics transfer processing method, electronic device, storage medium, and program product provided in this application, by determining the recipient and first delivery address information of the logistics waybill, and modifying the first delivery address information of the logistics waybill to the transfer address information when the first delivery address information has associated transfer address information, can promptly adjust the waybill address based on the delivery address pre-set by the recipient, reducing the manual processing burden on users after placing an order or during the transfer process, thereby improving the timeliness, accuracy, and delivery stability of logistics transfer processing. Attached Figure Description

[0038] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0039] Figure 1 This is a schematic diagram of a logistics transfer process provided in an embodiment of this application;

[0040] Figure 2 A flowchart illustrating the logistics transfer processing method provided in the embodiments of this application. Figure 1 ;

[0041] Figure 3 A flowchart illustrating the logistics transfer processing method provided in the embodiments of this application. Figure 2 ;

[0042] Figure 4 This is a schematic diagram of the structure of the logistics transfer and processing device provided in the embodiments of this application;

[0043] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0044] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0045] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0046] In the field of express logistics technology, handling parcels with changed recipient addresses is a common business scenario. Users, sending platforms, and logistics service platforms typically collaborate through client-side and back-end services to complete waybill generation, address identification, transportation scheduling, and delivery processing.

[0047] Figure 1 This is a schematic diagram of a logistics transfer process provided in the embodiments of this application, such as... Figure 1 As shown, it includes:

[0048] When the recipient relocates, changes their workplace, or receives packages in a long-term, remote location, the historical delivery address (such as...) Figure 1 Address B in the original delivery address may still be reused by e-commerce platforms, social platforms, or the sender, causing newly generated logistics orders to continue to point to the original delivery address B. The old addresses A and B of the recipient can be pre-associated with the new address C by the recipient on a specific APP.

[0049] In current practices, after a package is sent to the old address, the recipient usually requests a manual reshipment upon discovering the anomaly, or modifies the historical address information on different platforms. There are also practices where the delivery address is adjusted by contacting the logistics personnel closer to delivery. The typical workflow involves making subsequent corrections based on the new address temporarily submitted by the user after the waybill is generated or even after the package has entered the circulation process.

[0050] This type of processing relies on users continuously monitoring order and logistics status, resulting in a long operational chain, involvement of multiple platforms, and a high risk of omissions. Some shipping actions directly use historical addresses, meaning that even if the recipient updates their address book on one platform, they may still be unable to prevent the old address from being used. By the time the address is changed at the last-mile delivery stage, the package has often already entered its predetermined transportation route, impacting processing time and scheduling stability.

[0051] Meanwhile, existing forwarding judgments mostly revolve around whether a manual application has been submitted, lacking prior identification of whether a new address can be used as a subsequent delivery address, and failing to fully utilize the continuous association between the recipient in the waybill and their historical delivery address. This can easily lead to forwarding delays, misdeliveries, and delays, affecting package delivery efficiency and logistics processing security.

[0052] Based on the above-mentioned technical issues, the processing path after the recipient address is changed is moved forward to the waybill address identification stage. The recipient address set in advance by the recipient is used as the transit address. In the collaborative architecture between the client and back-end services of the logistics service platform, the recipient of the logistics waybill and the first recipient address information are first determined, and then it is determined whether the first recipient address information has associated transit address information.

[0053] The technical solution of this application and how it solves the above-mentioned technical problems will be described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0054] Figure 2 A flowchart illustrating the logistics transfer and processing method provided in the embodiments of this application. Figure 1 The methods described above in the embodiments of this application can be applied to any electronic device. For example... Figure 2 As shown, the method includes:

[0055] S201. Determine the recipient and primary delivery address information for the logistics waybill.

[0056] In this step, the logistics waybill serves as the basic data carrier for address transfer processing, recording key information related to delivery during the package's transit process. This includes at least the waybill number, recipient identifier, recipient contact person, contact number, and the currently registered delivery address. The recipient is the user entity corresponding to the package receipt action and is also the entity subsequently used to determine the associated transfer address information. This identification can be done through user account identifiers or through one or more combinations of normalized name, mobile phone number, and identification document. The primary delivery address information is the original delivery address corresponding to the logistics waybill at the current processing moment. It is the starting address data used by the system to determine whether to enter the transfer processing stage. This can be the address filled in by the sender when placing the order, the order address pushed by a third-party platform, or the address field synchronously imported by the logistics service platform when receiving external waybills. Specifically, upon receiving a newly generated logistics waybill, an imported historical logistics waybill, or a logistics task awaiting distribution, the logistics service platform's server first parses the waybill data, extracting the recipient identifier information and the primary delivery address information from the waybill data message, structured fields, or order mapping table. The determination of the recipient can be accomplished in several ways. In one possible embodiment, the server matches the recipient's mobile phone number in the waybill with the platform's registered user database. If a unique match is found, the corresponding platform registered account is identified as the recipient. In another possible embodiment, the server performs similarity matching based on the combined features of the recipient's name, mobile phone number, and detailed address, and filters out a unique target user through a preset threshold. In yet another possible embodiment, if the logistics waybill itself carries the recipient's user ID in the logistics service platform, the user ID is directly used to complete the identification. The determination of the first delivery address information includes two steps: address acquisition and address standardization. After extracting one or more of the province, city, district / county, street, house number, building unit, and postal code, the server performs rule-based completion of missing fields, uniformly maps irregular abbreviations, aliases, and historical administrative division names, and forms a standard address text or address structured object that can be matched. For example, after receiving a logistics waybill, the server extracts the recipient's identifier and the first delivery address information from the waybill. It then performs word segmentation, administrative division correction, standard address encoding conversion, and redundancy removal on the first delivery address information. Finally, it establishes a binding identification relationship between the standardized first delivery address information and the recipient, generating the basic data record required for subsequent transshipment determination. This basic data record includes at least the waybill number, the recipient's internal identifier, the original address text, the standard address encoding, and a processing timestamp, so that it can be directly retrieved when searching for related relationships later.Based on the above analysis, it can be seen that by determining the recipient and primary delivery address information early in the logistics waybill's circulation process and establishing a binding identification result between the user and address, subsequent association matching can be based on a unified data format. This allows address association judgment to be executed immediately after the waybill is generated, without waiting for the package to enter the last-mile delivery stage. It should be understood that the above example is for demonstration purposes only and is not a limitation.

[0057] In this application, the specific implementation of S201 is not limited to a single data source. For example, the logistics service platform can receive waybill creation requests from e-commerce platforms, social delivery platforms, and enterprise delivery systems via open interfaces, directly parsing the recipient's external identifier and address field in the request message; alternatively, when the sender creates an order on the logistics service platform client, the front-end page can synchronously send the completed address data to the back-end service, which then identifies the recipient and the first delivery address information based on this; furthermore, when a waybill has been generated but the package has not yet been loaded, the waybill master file can be read through the distribution center's waybill synchronization system, and supplementary identification can be performed. In cases where the recipient cannot be directly identified from a single field, the server can call the user profile database and historical delivery record database to compare the similarity between the first delivery address information and the historical address set. If a user has a delivery record with the same or similar address within a preset time window, and the user's contact information matches the waybill information, then the user is identified as the recipient. If the same logistics waybill subsequently receives supplementary address entries, revised address entries, or retransmitted data from the upstream platform, the system can select the latest set of recipient and first recipient address information as valid data based on the waybill version number and timestamp. Based on the above processing, this step not only identifies the waybill processing object but also provides a unified, searchable, and comparable data foundation for subsequently determining whether the first recipient address information has associated transit address information, thereby enabling the entire logistics transit process to be automatically connected on the backend service side.

[0058] S202. When the first delivery address information has associated transit address information, the first delivery address information of the logistics waybill is modified to the transit address information, which is the delivery address preset by the receiving user.

[0059] In this step, the transit address information is new address data used to replace the first delivery address information. It belongs to the delivery address pre-set by the recipient and stored by the system, representing the location the recipient hopes the package will actually be delivered to in the event of an address change. The existence of associated transit address information for the first delivery address indicates that a correspondence already exists between the recipient's first delivery address and the transit address information in the system. This relationship can be one-to-one or a one-to-many relationship where multiple historical addresses correspond to the same transit address. Specifically, after completing user and address identification in S201, the server queries the corresponding transit address information based on the recipient's identifier and matches the first delivery address information in the logistics waybill with the existing association. The matching method can be a complete match of standard address codes, or a match is determined when the house number, building number, street code, and contact information match. For cases where the same location has abbreviations, aliases, or historical community names, they can be converted to a unified address code through an address standardization mapping table before performing the association judgment. If the determination result indicates the existence of a related transit address, the server updates the delivery address field in the waybill master file from the first delivery address information to the corresponding transit address information. For example, if the first delivery address information registered in the current logistics waybill is the recipient's old residential address before relocation, and the system already has a new residential address corresponding to that old address as a transit address, the server replaces the delivery address field of the logistics waybill with the new residential address after successful matching. If the determination result indicates the absence of a related transit address, the first delivery address information in the logistics waybill remains unchanged. Based on the above analysis, this step, by calling existing address associations, moves the address change action forward to the early processing stage of the waybill, allowing the package to complete destination correction before entering the fixed transportation route. It should be understood that the above example is for demonstration purposes only and is not limiting.

[0060] In this application, the association in S202 can be a pre-stored correspondence between the recipient's address and the recipient's address in the system. When a recipient has multiple transit address information, the system can select the target transit address information based on the association corresponding to the first recipient address information. Based on the above processing, it can be seen that the system can update the waybill address on the basis of established address associations, enabling the logistics transit process to be completed in a closed loop at the waybill level.

[0061] Based on the above analysis, this application provides a logistics transshipment processing method, including determining the recipient user and first delivery address information of the logistics waybill; when the first delivery address information has associated transshipment address information, the first delivery address information of the logistics waybill is modified to the transshipment address information, which is the delivery address preset by the recipient user. In this application, the backend service first performs user identification and address standardization processing on the logistics waybill, and then matches and judges the first delivery address information in the waybill according to the address association relationship corresponding to the recipient user, and completes the address replacement when the association is established. Through the above processing, the logistics waybill corresponding to the old address can complete the destination correction before entering the predetermined transportation route. The waybill processing link no longer relies on temporary manual applications after the package arrives at the final stage. The transshipment judgment node is moved forward, and the address modification action is continuously connected with waybill identification and association matching, which can cope with the problems of forwarding delay, misdelivery, and retention in the scenario of delivery address change. It should be understood that the above example is only for demonstration and not a limitation.

[0062] Figure 3 A flowchart illustrating the logistics transfer processing method provided in the embodiments of this application. Figure 2 .like Figure 3 As shown, the method includes:

[0063] S301. Obtain the address association instruction of the receiving user. The address association instruction is used to associate one or more second receiving address information with a transit address information.

[0064] When executing an address association instruction, the backend service writes one or more second delivery address information into the association record corresponding to the transit address information based on the association object in the instruction, and establishes a mapping relationship for subsequent logistics order identification. This mapping relationship can be stored in the address association database and can be bound to a user account to ensure that subsequent logistics orders generated by the same recipient can access the corresponding transit address information when a second delivery address is matched. If a recipient requests association for multiple historical delivery addresses, the backend service can uniformly associate multiple second delivery address information with the same transit address information, thus forming an association structure where one transit address corresponds to multiple historical addresses.

[0065] In one specific implementation, the address association instruction is generated by the client based on user input and sent to the backend service via an interface request. After completing identity verification, address format verification, and association permission verification, the backend service executes the address association instruction and synchronously updates the association result to the address cache and persistent storage. After the address association instruction is executed, the system returns a successful association flag and records the association time, association status, and corresponding address identifier, so that subsequent logistics waybills can directly call the established association relationship during the address recognition stage.

[0066] S302, Execute address association instruction.

[0067] S303. Determine the recipient and primary delivery address information for the logistics waybill.

[0068] S304. When the first delivery address information has associated transit address information, the first delivery address information of the logistics waybill is modified to the transit address information, which is the delivery address preset by the receiving user.

[0069] By acquiring and executing address association instructions, the system can pre-establish the correspondence between historical addresses and transit addresses when the receiving user submits an address management operation. This allows subsequent logistics waybills to directly trigger address association matching when they identify a second receiving address, thereby completing the receiving address switching process. Since the association relationship is written into the system before the logistics waybill is transferred, subsequent address change processing can be completed in a pre-processing manner, improving the continuity of address identification and the consistency of waybill routing processing.

[0070] In one possible implementation, before modifying the first delivery address information of the logistics waybill to the transit address information, at least one of the following is included: verifying the association between the first delivery address information and the transit address information; verifying the transit address information; verifying the package type of the logistics waybill; and verifying the cost information for transferring the first delivery address information to the transit address information.

[0071] After receiving an address modification request, the system first reads the first delivery address information and the transit address information from the waybill information database and the address association database, and compares the correspondence between the two to confirm that the transit address information has indeed been associated with the first delivery address information. Then, it verifies the information integrity, regional validity, and deliverability of the transit address information. At the same time, it reads the package attributes in the logistics waybill and determines whether it belongs to the type that is allowed to be transited. Finally, it calculates the cost information based on transit rules, distance parameters, service level, and payment conditions. Only when the corresponding verification results meet the preset conditions is it allowed to modify the first delivery address information to the transit address information.

[0072] In actual operation, the association verification can be achieved through address mapping tables, user address books, or historical delivery records. The system can confirm the consistency of address identification codes, user identifications, and association validity periods. The transit address information verification can be completed through geocoding parsing, administrative region matching, and service network coverage judgment to confirm that the target address is within the delivery range. The package type verification can be determined based on the package type, temperature control level, dangerous goods label, or prohibited label registered in the logistics waybill. If the package is identified as unsuitable for transit, the address modification will be terminated. The fee information verification can generate a fee result based on the routing difference between the transit address information and the first delivery address information, additional service fees, and settlement status, and output a modification permission instruction after the fee meets the payment or deduction conditions.

[0073] This processing method performs multi-dimensional verification before address switching, ensuring that address modifications are triggered only when the association is valid, the address is reachable, the package is compatible, and the cost is acceptable. This allows logistics waybills to update the delivery address early in the process and synchronize subsequent transportation routes to the transit address information. This ensures consistency between address changes and package transit, reducing invalid transits, address mismatches, and mid-journey returns, thus improving the continuity and accuracy of logistics processing.

[0074] Based on the aforementioned embodiments, further modifying the first delivery address information of the logistics waybill to the transit address information includes: sending transit notification information to the first terminal device of the sender corresponding to the logistics waybill; receiving transit permission information sent by the first terminal device, the transit permission information being used to indicate whether the sender agrees or disagrees to modify the first delivery address information of the logistics waybill to the transit address information; when the transit permission information indicates that the sender agrees to modify the first delivery address information of the logistics waybill to the transit address information, modifying the first delivery address information of the logistics waybill to the transit address information.

[0075] In its implementation, after identifying a logistics waybill to be transferred, the logistics service platform retrieves the corresponding sender's identifier and its associated first terminal device identifier based on the waybill identifier. The platform then sends a transfer notification to the first terminal device via push notification or SMS. The notification may include the waybill number, the current primary delivery address, and the proposed revised transfer address for the sender to verify. Upon receiving the notification, the first terminal device encapsulates the sender's confirmation on the interface into transfer permission information and sends it back to the server. The server parses the transfer permission information; if the parsing result indicates that the sender agrees to the modification, it calls the waybill address update interface to replace the original primary delivery address with the transfer address information and simultaneously updates the routing data relied upon for subsequent sorting and delivery.

[0076] When the sender disagrees with the modification, the system retains the original primary delivery address information and records the transit permission information in the waybill status information for later retrieval. This approach directly links waybill address modification with the sender's confirmation, enabling authorization verification before address change and writing the confirmed transit address information into the waybill data, thus ensuring that subsequent transportation scheduling reads consistent address information. This implementation method provides a clear basis for user confirmation during the waybill address modification process, reduces unauthorized address changes, and ensures consistency between waybill routing data and the sender's permission.

[0077] One possible implementation also includes sending a successful transfer notification and forwarding record information to the recipient's second terminal device.

[0078] In its implementation, after modifying the initial delivery address information to the transit address information, the logistics service platform generates a transit result message based on the waybill identifier. The successful transit notification and the forwarding record information are either encapsulated in the same message body or separately as two separate message bodies, and sent to the recipient's corresponding second terminal device via a message push interface. The message push interface can be implemented using in-app notifications, SMS notifications, site message notifications, or system pop-up notifications. When the second terminal device is online, messages can be pushed directly to the client; when the second terminal device is offline, messages can be written to a message queue or notification center and resent after the terminal reconnects to the network. The forwarding record information can be automatically generated by the backend service based on the logistics waybill data before and after the address change and stored in the transit record table so that the second terminal device can synchronously display historical transit details upon receiving the notification. The model of the second terminal device can be a smartphone, tablet, or other terminal with message receiving capabilities, depending on the application scenario. In practical applications, other models can also be selected for this component; this application does not limit this choice.

[0079] By sending successful transit notifications and forwarding records to the recipient's second terminal device, the recipient can be promptly informed of the address modification result after transit is completed and can query the corresponding forwarding history on the terminal side, thus creating a closed-loop feedback for the transit processing results. Since the successful transit notification and forwarding record information are sent simultaneously, the recipient no longer needs to manually check the logistics waybill status; they can directly obtain information on the package's trajectory and historical processing information, thereby improving the visibility of transit results and the efficiency of subsequent verification.

[0080] Based on the aforementioned embodiments, further, the first delivery address information has associated transit address information, including: performing semantic parsing on the first delivery address information to obtain first semantic information; determining the semantic similarity between the first semantic information and the second delivery address information; when the semantic similarity is greater than a preset first threshold, determining that the first delivery address information has associated transit address information.

[0081] Semantic parsing is used to break down the first delivery address information into comparable address elements, and the first semantic information is an intermediate semantic representation formed by combining address elements. After receiving the first delivery address information in the background service of the logistics service platform, the system performs word segmentation, entity recognition, and address standardization on the address text, extracting and mapping elements such as province, city, district, street, building, room number, and house number into a unified format to form the first semantic information.

[0082] When calculating semantic similarity, the system can quantify the similarity based on the matching degree of address elements, the distance between weight vectors or text embedding vectors, to obtain a similarity result representing the semantic consistency between the two. The first threshold can be preset based on address recognition accuracy, regional hierarchical differences, and historical transit records, and stored in the platform configuration parameters. When the aforementioned semantic similarity is greater than the first threshold, the system outputs a judgment result indicating a correlation between the first and second delivery address information, and accordingly determines the transit address information associated with the first delivery address information. In practical applications, the semantic similarity calculation module can also use other semantic matching models, which are not limited in this application.

[0083] During operation, the system first converts the delivery address to be processed into a unified semantic representation, and then compares it with candidate transshipment address information. Only when the two reach a preset consistency level at the address element level is the candidate address confirmed as a transshipment address that can be used for transshipment. Since the judgment is based on the address elements after semantic parsing and their semantic similarity results, the system can complete address association identification before the logistics waybill enters the circulation process and provide the identification results to the subsequent address modification processing.

[0084] After adopting this implementation method, the association judgment between the first delivery address information and the transit address information is transformed from text surface matching to semantic level comparison, which can improve the consistency of address recognition under different expression methods, and enable the system to confirm the transit address relationship in a timely manner when the first threshold condition is met, thereby providing a reliable basis for subsequent logistics waybill address switching.

[0085] Building upon the aforementioned embodiments, the system further includes: generating and storing an address change log for the logistics waybill. The address change log includes at least one of the following: waybill identifier, first receiving address information, transit address information, change time, and verification result. Log data can be automatically generated by the logistics service platform's backend service after processing the address modification instruction and written to a relational database, log database, or distributed storage unit. Log record fields can be organized according to a preset data table structure or persistently stored in key-value pairs for subsequent querying, tracking, and auditing. The waybill identifier can be a waybill number, waybill number, or internal tracking code. When writing to the log, the system binds and associates it with the original address, transit address information, and verification conclusion, facilitating rapid location of the corresponding record in case of transit disputes, address verification, or abnormal shipment tracking. The verification result can be saved as pass, fail, or a specific error code. In practical applications, this record field can also correspond to other encoding methods, which this application does not limit. Based on the above address change log, the system can retain the address change trajectory without changing the waybill master data query method and provide data basis for subsequent anomaly analysis, responsibility tracking, and status retrospection. By synchronously storing waybill identifiers, address information, change times, and verification results, a stable mapping can be established between address change behavior and corresponding logistics waybills, thereby improving the traceability of transit records and the verifiability of verification results.

[0086] This application provides a logistics transfer processing method. In the express delivery service scenario, a user's delivery address changes due to relocation, but the sender, such as an e-commerce platform merchant, still uses the old address to place orders and ship goods, resulting in the package not being delivered. After moving from a community in City A to a community in City B, the user accesses the address transfer settings page through the logistics service platform's APP client. They select the old address (No. 123, Community 1, City A) and the new address (No. 456, Community 1, City B) from the address book. A second terminal device submits an address association instruction to the platform. The address association instruction includes one or more second delivery address information and corresponding transfer address information associated with these second delivery address information. No. 123, Community 1, City A serves as the second delivery address, and No. 456, Community 1, City B, is the user's pre-set delivery address and also serves as the transfer address. While establishing a one-to-one mapping relationship between the old address (No. 123, Community 1, City A) and the new address (No. 456, Community 1, City B), the user simultaneously activates the "automatic forwarding after pickup" switch. The platform establishes and saves address association relationships based on address association instructions, and stores these relationships in a database. The database includes attributes such as old address identifier, new address identifier, automatic forwarding switch status, and setting time.

[0087] When processing logistics waybills, an e-commerce platform merchant generates a new waybill and ships a package based on the user's historical address, No. 123, a certain community in City A. The platform identifies the recipient and the first delivery address information corresponding to this waybill, which is the delivery address No. 123, a certain community in City A listed on the waybill. The platform extracts the delivery address information from the waybill in real time, performs semantic analysis on the first delivery address information to obtain first semantic information, and then extracts the second delivery address information from the saved address association relationships, calculating the semantic similarity between the first semantic information and the second delivery address information. Since the delivery address on the waybill is consistent with the old address No. 123, a certain community in City A in the user's association relationship, and the automatic forwarding function is enabled, when the semantic similarity is greater than a preset first threshold, the platform determines that the first delivery address information has an associated transit address, No. 456, a certain community in City B, and marks the waybill as a "waybill to be automatically forwarded," thus automatically recognizing the change of old address and executing forwarding after the package is picked up.

[0088] After the courier completes the pickup operation for the "pending automatic forwarding waybill" package, the platform automatically triggers the forwarding process. Before modifying the address, the platform verifies the association between the first receiving address (No. 123, a certain community in City A) and the forwarding address (No. 456, a certain community in City B), checking whether the association was established by the corresponding recipient and is valid. It also verifies the validity and activation of the automatic forwarding instruction by checking the automatic forwarding switch status. The platform also verifies the forwarding address information, checking the address format, completeness, and deliverability, and confirming that the new address (No. 456, a certain community in City B) is a domestic address excluding Hong Kong, Macau, Taiwan, and international addresses. The platform verifies the package type of the logistics waybill, determining whether it meets the forwarding conditions and checking if the package is unsuitable for forwarding, such as perishable goods or fragile items. The platform also verifies the cost information for forwarding from the first receiving address to the forwarding address, calculating the forwarding fee and confirming that the fee rules, payment status, or affordability status meet the forwarding requirements, including verifying whether the user's account balance is sufficient. If the above-mentioned verification of association, instruction, address, package type, and fee all pass, the platform will enter the forwarding execution stage.

[0089] After verification, the platform sends a transfer notification to the first terminal device of the sender corresponding to the logistics waybill. If the sender is an e-commerce platform merchant, the transfer notification includes the waybill identifier, the original first delivery address (No. 123, a certain community in City A), the transfer address (No. 456, a certain community in City B), and relevant transfer instructions. It also provides the merchant with the option to "agree to transfer" or "reject with one click." The platform receives the transfer permission information returned by the first terminal device. This permission information indicates whether the sender agrees or disagrees to change the first delivery address on the logistics waybill to the transfer address. If the merchant chooses to agree to transfer, the transfer permission information indicates the sender's consent, and the platform automatically generates a transfer instruction, changing the package's destination from the old address (No. 123, a certain community in City A) to the new address (No. 456, a certain community in City B). This transfer instruction is then sent to the logistics dispatch system. The logistics dispatch system plans a delivery route based on the new address, and the courier delivers the package to the new address. If the merchant chooses to reject with one click, the transfer permission information indicates the sender's disagreement, the system cancels the transfer process, and the package is delivered to the original address.

[0090] When the forwarding permission information indicates that the sender agrees, the platform modifies the first delivery address information in the logistics waybill to the forwarding address information, No. 456, a certain community in City B, and generates and stores an address change log. The address change log records at least one of the following: waybill identifier, first delivery address information, No. 123, a certain community in City A, forwarding address information, No. 456, a certain community in City B, change time, and verification result. After the address is modified, the platform sends a forwarding success notification and forwarding record information to the recipient's second terminal device, informing them that the package has been forwarded to No. 456, a certain community in City B, and updates the forwarding record of the address association. Users can view historical forwarding details through the client, forming a complete status feedback loop.

[0091] Figure 4 This is a schematic diagram of the structure of the logistics transfer and processing device provided in the embodiments of this application, as shown below. Figure 4 As shown, the logistics transfer processing device 40 provided in this embodiment includes a determination module 401 and a processing module 402.

[0092] The determination module 401 is used to determine the recipient and the first delivery address information of the logistics waybill;

[0093] The processing module 402 is used to modify the first delivery address information of the logistics waybill to the transit address information when the first delivery address information has associated transit address information. The transit address information is the delivery address preset by the delivery user.

[0094] In one possible embodiment, the processing module 402 is further configured to:

[0095] Obtain the address association instruction from the recipient. The address association instruction is used to associate one or more second delivery address information with a transit address information.

[0096] Execute the address association instruction.

[0097] In one possible embodiment, the processing module 402 is further configured to:

[0098] Verify the association between the primary delivery address information and the transit address information;

[0099] Verify the transit address information;

[0100] Verify the package type on the logistics waybill;

[0101] Verify the cost information for transferring goods from the first delivery address to the transfer address.

[0102] In one possible embodiment, the processing module 402 is used for:

[0103] Send a transfer notification to the first terminal device of the sender corresponding to the logistics waybill;

[0104] Receive transfer permission information sent by the first terminal device. The transfer permission information is used to indicate whether the sender agrees or disagrees to change the first delivery address information of the logistics waybill to the transfer address information.

[0105] When the transfer permission information indicates that the sender agrees to change the first delivery address information of the logistics waybill to the transfer address information, the first delivery address information of the logistics waybill will be changed to the transfer address information.

[0106] In one possible embodiment, the processing module 402 is further configured to:

[0107] Send a successful transfer notification and forwarding record information to the recipient's second terminal device.

[0108] In one possible embodiment, the processing module 402 is further configured to:

[0109] Semantic parsing is performed on the first delivery address information to obtain the first semantic information;

[0110] Determine the semantic similarity between the first semantic information and the second delivery address information;

[0111] When the semantic similarity is greater than a preset first threshold, it is determined that the first delivery address information has associated transit address information.

[0112] In one possible embodiment, the processing module 402 is further configured to:

[0113] Generate and store the address change log of the logistics waybill. The address change log includes at least one of the following: waybill identifier, first receiving address information, transit address information, change time, and verification result.

[0114] The logistics transfer and processing device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0115] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5 As shown, the electronic device 50 provided in this embodiment includes at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. The processor 501, memory 502, and communication component 503 are connected via a bus.

[0116] In a specific implementation, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to perform the above-described method.

[0117] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0118] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0119] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0120] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0121] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0122] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0123] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0124] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0125] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0126] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0127] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0128] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0129] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disk, or optical disk.

[0130] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A logistics transfer and processing method, characterized in that, include: Determine the recipient and primary delivery address information for the logistics waybill; When the first delivery address information has associated transit address information, the first delivery address information of the logistics waybill is modified to the transit address information, which is the delivery address preset by the receiving user.

2. The method according to claim 1, characterized in that, Also includes: Obtain the address association instruction of the receiving user, the address association instruction being used to associate one or more second receiving address information to a transit address information; Execute the address association instruction.

3. The method according to claim 1, characterized in that, Before modifying the first delivery address information of the logistics waybill to the transit address information, at least one of the following is included: The association between the first delivery address information and the transit address information is verified; The transit address information is verified; Verify the package type of the logistics waybill; The cost information for transferring the goods from the first delivery address information to the transfer address information is verified.

4. The method according to claim 1, characterized in that, The step of modifying the first delivery address information of the logistics waybill to the transit address information includes: Send a transfer notification message to the first terminal device of the sender corresponding to the logistics waybill; The system receives transfer permission information sent by the first terminal device. The transfer permission information is used to indicate whether the sender agrees or disagrees to modify the first delivery address information of the logistics waybill to the transfer address information. When the transfer permission information indicates that the sender agrees to change the first delivery address information of the logistics waybill to the transfer address information, the first delivery address information of the logistics waybill is changed to the transfer address information.

5. The method according to claim 4, characterized in that, Also includes: Send a successful transfer notification and forwarding record information to the recipient's second terminal device.

6. The method according to claim 2, characterized in that, The first delivery address information has associated transit address information, including: Semantic parsing is performed on the first delivery address information to obtain the first semantic information; Determine the semantic similarity between the first semantic information and the second delivery address information; When the semantic similarity is greater than a preset first threshold, it is determined that the first delivery address information has associated transit address information.

7. The method according to claim 3, characterized in that, Also includes: Generate and store the address change log of the logistics waybill, the address change log including at least one of the following: waybill identifier, first receiving address information, transshipment address information, change time, and verification result.

8. A logistics transfer and processing device, characterized in that, include: The determination module is used to determine the recipient and primary delivery address information for the logistics waybill; The processing module is used to modify the first delivery address information of the logistics waybill to the transit address information when the first delivery address information has associated transit address information, wherein the transit address information is the delivery address preset by the receiving user.

9. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-7.

11. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-7.

Images